From 6a0759e7fbcb58f2baf2866e0ebbf0258eddc9a5 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 23 Feb 2022 05:45:45 +0000 Subject: [PATCH] Update content of files --- data/contest.com.html | 291 + data/core.telegram.org.html | 253 + data/core.telegram.org/api.html | 253 + .../api/account-deletion.html | 129 + .../api/animated-emojis.html | 187 + data/core.telegram.org/api/auth.html | 202 + data/core.telegram.org/api/bots.html | 142 + data/core.telegram.org/api/bots/buttons.html | 242 + data/core.telegram.org/api/bots/commands.html | 140 + data/core.telegram.org/api/bots/games.html | 171 + data/core.telegram.org/api/bots/inline.html | 215 + data/core.telegram.org/api/channel.html | 154 + data/core.telegram.org/api/config.html | 422 + data/core.telegram.org/api/datacenter.html | 152 + data/core.telegram.org/api/dice.html | 149 + data/core.telegram.org/api/discussion.html | 151 + data/core.telegram.org/api/drafts.html | 131 + data/core.telegram.org/api/end-to-end.html | 244 + .../core.telegram.org/api/end-to-end/pfs.html | 176 + .../api/end-to-end/seq_no.html | 173 + .../api/end-to-end/video-calls.html | 215 + .../api/end-to-end/voice-calls.html | 178 + data/core.telegram.org/api/end-to-end_v1.html | 225 + data/core.telegram.org/api/entities.html | 137 + data/core.telegram.org/api/errors.html | 189 + .../core.telegram.org/api/file_reference.html | 125 + data/core.telegram.org/api/files.html | 568 + data/core.telegram.org/api/folders.html | 179 + data/core.telegram.org/api/geochats.html | 115 + data/core.telegram.org/api/import.html | 173 + data/core.telegram.org/api/invoking.html | 154 + data/core.telegram.org/api/layers.html | 2499 +++++ data/core.telegram.org/api/live-location.html | 178 + data/core.telegram.org/api/mentions.html | 152 + data/core.telegram.org/api/min.html | 142 + .../api/obtaining_api_id.html | 140 + data/core.telegram.org/api/offsets.html | 170 + data/core.telegram.org/api/optimisation.html | 150 + data/core.telegram.org/api/passport.html | 674 ++ data/core.telegram.org/api/pattern.html | 122 + data/core.telegram.org/api/payments.html | 366 + data/core.telegram.org/api/pfs.html | 138 + data/core.telegram.org/api/pin.html | 149 + data/core.telegram.org/api/poll.html | 199 + data/core.telegram.org/api/push-updates.html | 1009 ++ data/core.telegram.org/api/qr-login.html | 154 + .../core.telegram.org/api/recent-actions.html | 154 + data/core.telegram.org/api/rights.html | 133 + .../api/scheduled-messages.html | 156 + data/core.telegram.org/api/search.html | 179 + .../api/sponsored-messages.html | 146 + data/core.telegram.org/api/srp.html | 307 + data/core.telegram.org/api/terms.html | 133 + data/core.telegram.org/api/threads.html | 182 + data/core.telegram.org/api/top-rating.html | 145 + data/core.telegram.org/api/updates.html | 226 + .../api/url-authorization.html | 160 + data/core.telegram.org/api/web-events.html | 177 + data/core.telegram.org/apple_privacy.html | 118 + ...hemes-interactive-emoji-read-receipts.html | 115 + data/core.telegram.org/bots.html | 437 + .../core.telegram.org/bots/api-changelog.html | 670 ++ data/core.telegram.org/bots/api.html | 9488 +++++++++++++++++ data/core.telegram.org/bots/faq.html | 243 + data/core.telegram.org/bots/games.html | 185 + data/core.telegram.org/bots/inline.html | 182 + data/core.telegram.org/bots/samples.html | 249 + .../bots/samples/hellobot.html | 287 + data/core.telegram.org/bots/self-signed.html | 161 + data/core.telegram.org/bots/webhooks.html | 827 ++ data/core.telegram.org/cdn.html | 210 + data/core.telegram.org/cdn/faq_ir.html | 142 + data/core.telegram.org/cdn/faq_ir/durov.html | 133 + .../constructor/account.authorizationForm | 174 + .../constructor/account.authorizations | 147 + .../constructor/account.autoDownloadSettings | 157 + .../constructor/account.chatThemes | 155 + .../constructor/account.chatThemesNotModified | 132 + .../constructor/account.contentSettings | 157 + .../constructor/account.password | 213 + .../constructor/account.passwordInputSettings | 176 + .../constructor/account.passwordSettings | 161 + .../constructor/account.privacyRules | 157 + .../account.resetPasswordFailedWait | 147 + .../constructor/account.resetPasswordOk | 132 + .../account.resetPasswordRequestedWait | 147 + .../constructor/account.sentChangePhoneCode | 161 + .../constructor/account.sentEmailCode | 155 + .../constructor/account.takeout | 147 + .../constructor/account.themes | 155 + .../constructor/account.wallPapers | 155 + .../constructor/account.wallPapersNotModified | 132 + .../constructor/account.webAuthorizations | 152 + .../constructor/accountDaysTTL.html | 147 + .../constructor/auth.authorization | 159 + .../auth.authorizationSignUpRequired | 155 + .../constructor/auth.codeTypeCall | 132 + .../constructor/auth.codeTypeFlashCall | 132 + .../constructor/auth.codeTypeSms | 132 + .../constructor/auth.exportedAuthorization | 152 + .../constructor/auth.loginToken | 155 + .../constructor/auth.loginTokenMigrateTo | 152 + .../constructor/auth.loginTokenSuccess | 147 + .../constructor/auth.passwordRecovery | 152 + .../constructor/auth.sentAppCode | 163 + .../constructor/auth.sentCode | 172 + .../constructor/auth.sentCodeTypeApp | 147 + .../constructor/auth.sentCodeTypeCall | 147 + .../constructor/auth.sentCodeTypeFlashCall | 150 + .../constructor/auth.sentCodeTypeSms | 147 + .../constructor/authorization.html | 225 + .../constructor/autoDownloadSettings.html | 187 + .../constructor/bankCardOpenUrl.html | 152 + .../constructor/baseThemeArctic.html | 132 + .../constructor/baseThemeClassic.html | 132 + .../constructor/baseThemeDay.html | 132 + .../constructor/baseThemeNight.html | 132 + .../constructor/baseThemeTinted.html | 132 + .../constructor/boolFalse.html | 132 + .../constructor/boolTrue.html | 132 + .../botCommandScopeChatAdmins.html | 135 + .../constructor/botCommandScopeChats.html | 135 + .../constructor/botCommandScopeDefault.html | 132 + .../constructor/botCommandScopePeer.html | 147 + .../botCommandScopePeerAdmins.html | 150 + .../constructor/botCommandScopePeerUser.html | 155 + .../constructor/botCommandScopeUsers.html | 132 + .../constructor/botInfo.html | 157 + .../constructor/botInlineMediaResult.html | 186 + .../botInlineMessageMediaAuto.html | 167 + .../botInlineMessageMediaContact.html | 172 + .../constructor/botInlineMessageMediaGeo.html | 175 + .../botInlineMessageMediaInvoice.html | 189 + .../botInlineMessageMediaVenue.html | 182 + .../constructor/botInlineMessageText.html | 170 + .../constructor/botInlineResult.html | 189 + .../constructor/cdnConfig.html | 149 + .../constructor/cdnPublicKey.html | 154 + .../constructor/channel.html | 289 + .../constructor/channelAdminLogEvent.html | 162 + ...channelAdminLogEventActionChangeAbout.html | 152 + ...elAdminLogEventActionChangeHistoryTTL.html | 152 + ...elAdminLogEventActionChangeLinkedChat.html | 152 + ...nnelAdminLogEventActionChangeLocation.html | 152 + ...channelAdminLogEventActionChangePhoto.html | 152 + ...elAdminLogEventActionChangeStickerSet.html | 152 + ...channelAdminLogEventActionChangeTitle.html | 152 + ...nnelAdminLogEventActionChangeUsername.html | 152 + ...dminLogEventActionDefaultBannedRights.html | 155 + ...annelAdminLogEventActionDeleteMessage.html | 147 + ...elAdminLogEventActionDiscardGroupCall.html | 147 + ...channelAdminLogEventActionEditMessage.html | 152 + ...minLogEventActionExportedInviteDelete.html | 147 + ...AdminLogEventActionExportedInviteEdit.html | 152 + ...minLogEventActionExportedInviteRevoke.html | 147 + ...lAdminLogEventActionParticipantInvite.html | 147 + ...nelAdminLogEventActionParticipantJoin.html | 132 + ...LogEventActionParticipantJoinByInvite.html | 150 + ...elAdminLogEventActionParticipantLeave.html | 132 + ...nelAdminLogEventActionParticipantMute.html | 147 + ...minLogEventActionParticipantToggleBan.html | 155 + ...lAdminLogEventActionParticipantUnmute.html | 147 + ...lAdminLogEventActionParticipantVolume.html | 147 + ...nnelAdminLogEventActionStartGroupCall.html | 147 + .../channelAdminLogEventActionStopPoll.html | 147 + ...nLogEventActionToggleGroupCallSetting.html | 147 + ...annelAdminLogEventActionToggleInvites.html | 147 + ...nLogEventActionTogglePreHistoryHidden.html | 150 + ...elAdminLogEventActionToggleSignatures.html | 147 + ...nnelAdminLogEventActionToggleSlowMode.html | 155 + ...hannelAdminLogEventActionUpdatePinned.html | 147 + .../channelAdminLogEventsFilter.html | 266 + .../constructor/channelForbidden.html | 177 + .../constructor/channelFull.html | 363 + .../constructor/channelLocation.html | 152 + .../constructor/channelLocationEmpty.html | 132 + .../constructor/channelMessagesFilter.html | 157 + .../channelMessagesFilterEmpty.html | 132 + .../constructor/channelParticipant.html | 152 + .../constructor/channelParticipantAdmin.html | 190 + .../constructor/channelParticipantBanned.html | 175 + .../channelParticipantCreator.html | 162 + .../constructor/channelParticipantLeft.html | 147 + .../constructor/channelParticipantSelf.html | 157 + .../channelParticipantsAdmins.html | 132 + .../channelParticipantsBanned.html | 147 + .../constructor/channelParticipantsBots.html | 132 + .../channelParticipantsContacts.html | 147 + .../channelParticipantsKicked.html | 147 + .../channelParticipantsMentions.html | 161 + .../channelParticipantsRecent.html | 132 + .../channelParticipantsSearch.html | 147 + .../constructor/channels.adminLogResults | 157 + .../constructor/channels.channelParticipant | 157 + .../constructor/channels.channelParticipants | 162 + .../channels.channelParticipantsNotModified | 132 + data/core.telegram.org/constructor/chat.html | 227 + .../constructor/chatAdminRights.html | 205 + .../constructor/chatBannedRights.html | 216 + .../constructor/chatEmpty.html | 147 + .../constructor/chatForbidden.html | 152 + .../constructor/chatFull.html | 231 + .../constructor/chatInvite.html | 190 + .../constructor/chatInviteAlready.html | 147 + .../constructor/chatInviteExported.html | 192 + .../constructor/chatInviteImporter.html | 152 + .../constructor/chatInvitePeek.html | 152 + .../constructor/chatOnlines.html | 147 + .../constructor/chatParticipant.html | 157 + .../constructor/chatParticipantAdmin.html | 157 + .../constructor/chatParticipantCreator.html | 147 + .../constructor/chatParticipants.html | 157 + .../chatParticipantsForbidden.html | 157 + .../constructor/chatPhoto.html | 170 + .../constructor/chatPhotoEmpty.html | 132 + .../constructor/chatTheme.html | 157 + .../constructor/codeSettings.html | 166 + .../core.telegram.org/constructor/config.html | 420 + .../constructor/contact.html | 152 + .../constructor/contactStatus.html | 152 + .../constructor/contacts.blockedSlice | 162 + .../constructor/contacts.contacts | 157 + .../constructor/contacts.contactsNotModified | 132 + .../constructor/contacts.found | 162 + .../constructor/contacts.importedContacts | 165 + .../constructor/contacts.resolvedPeer | 157 + .../constructor/contacts.topPeers | 157 + .../constructor/contacts.topPeersDisabled | 132 + .../constructor/contacts.topPeersNotModified | 132 + .../constructor/dataJSON.html | 147 + .../constructor/dcOption.html | 197 + .../constructor/decryptedMessage.html | 217 + .../decryptedMessageActionAbortKey.html | 148 + .../decryptedMessageActionAcceptKey.html | 160 + .../decryptedMessageActionCommitKey.html | 155 + .../decryptedMessageActionDeleteMessages.html | 148 + .../decryptedMessageActionFlushHistory.html | 133 + .../decryptedMessageActionNoop.html | 133 + .../decryptedMessageActionNotifyLayer.html | 151 + .../decryptedMessageActionReadMessages.html | 148 + .../decryptedMessageActionRequestKey.html | 155 + .../decryptedMessageActionResend.html | 155 + ...ryptedMessageActionScreenshotMessages.html | 148 + .../decryptedMessageActionSetMessageTTL.html | 149 + .../decryptedMessageActionTyping.html | 148 + .../constructor/decryptedMessageLayer.html | 173 + .../decryptedMessageMediaAudio.html | 174 + .../decryptedMessageMediaContact.html | 163 + .../decryptedMessageMediaDocument.html | 191 + .../decryptedMessageMediaEmpty.html | 133 + ...decryptedMessageMediaExternalDocument.html | 183 + .../decryptedMessageMediaGeoPoint.html | 153 + .../decryptedMessageMediaPhoto.html | 191 + .../decryptedMessageMediaVenue.html | 173 + .../decryptedMessageMediaVideo.html | 207 + .../decryptedMessageMediaWebPage.html | 148 + .../constructor/decryptedMessageService.html | 156 + .../core.telegram.org/constructor/dialog.html | 214 + .../constructor/dialogFilter.html | 220 + .../constructor/dialogFilterSuggested.html | 155 + .../constructor/dialogFolder.html | 187 + .../constructor/dialogPeer.html | 147 + .../constructor/dialogPeerFolder.html | 150 + .../constructor/disabledFeature.html | 163 + .../constructor/document.html | 200 + .../documentAttributeAnimated.html | 132 + .../constructor/documentAttributeAudio.html | 172 + .../documentAttributeFilename.html | 147 + .../documentAttributeHasStickers.html | 132 + .../documentAttributeImageSize.html | 152 + .../constructor/documentAttributeSticker.html | 167 + .../constructor/documentAttributeVideo.html | 172 + .../constructor/documentEmpty.html | 147 + .../constructor/draftMessage.html | 177 + .../constructor/draftMessageEmpty.html | 152 + .../constructor/emojiKeyword.html | 152 + .../constructor/emojiKeywordDeleted.html | 152 + .../constructor/emojiKeywordsDifference.html | 162 + .../constructor/emojiLanguage.html | 147 + .../constructor/emojiURL.html | 147 + .../constructor/encryptedChatDiscarded.html | 157 + .../constructor/encryptedChatEmpty.html | 147 + .../constructor/encryptedChatRequested.html | 185 + .../constructor/encryptedChatWaiting.html | 167 + .../constructor/encryptedFileEmpty.html | 132 + .../constructor/encryptedMessage.html | 170 + .../constructor/encryptedMessageService.html | 165 + data/core.telegram.org/constructor/error.html | 152 + .../constructor/exportedMessageLink.html | 152 + .../constructor/fileHash.html | 171 + .../constructor/fileLocation.html | 182 + .../constructor/fileLocationUnavailable.html | 179 + .../core.telegram.org/constructor/folder.html | 177 + data/core.telegram.org/constructor/game.html | 182 + .../constructor/geoPoint.html | 167 + .../constructor/geoPointEmpty.html | 132 + .../constructor/globalPrivacySettings.html | 152 + .../constructor/groupCallDiscarded.html | 157 + .../constructor/groupCallParticipant.html | 247 + .../groupCallParticipantVideo.html | 167 + .../groupCallParticipantVideoSourceGroup.html | 152 + .../constructor/help.countriesList | 155 + .../constructor/help.countriesListNotModified | 132 + .../constructor/help.country | 172 + .../constructor/help.countryCode | 162 + .../constructor/help.deepLinkInfo | 165 + .../constructor/help.deepLinkInfoEmpty | 132 + .../constructor/help.noAppUpdate | 132 + .../constructor/help.passportConfig | 156 + .../help.passportConfigNotModified | 132 + .../constructor/help.promoData | 182 + .../constructor/help.promoDataEmpty | 147 + .../constructor/help.recentMeUrls | 157 + .../constructor/help.support | 152 + .../constructor/help.supportName | 147 + .../constructor/help.termsOfService | 175 + .../constructor/help.termsOfServiceUpdate | 157 + .../help.termsOfServiceUpdateEmpty | 150 + .../constructor/help.userInfo | 165 + .../constructor/help.userInfoEmpty | 132 + .../constructor/highScore.html | 157 + .../constructor/inlineBotSwitchPM.html | 152 + .../inlineQueryPeerTypeBroadcast.html | 135 + .../constructor/inlineQueryPeerTypeChat.html | 135 + .../inlineQueryPeerTypeMegagroup.html | 135 + .../constructor/inlineQueryPeerTypePM.html | 132 + .../inlineQueryPeerTypeSameBotPM.html | 132 + .../constructor/inputAppEvent.html | 162 + .../inputBotInlineMessageGame.html | 152 + .../constructor/inputBotInlineMessageID.html | 157 + .../inputBotInlineMessageID64.html | 162 + .../inputBotInlineMessageMediaAuto.html | 165 + .../inputBotInlineMessageMediaContact.html | 172 + .../inputBotInlineMessageMediaGeo.html | 175 + .../inputBotInlineMessageMediaInvoice.html | 187 + .../inputBotInlineMessageMediaVenue.html | 182 + .../inputBotInlineMessageText.html | 170 + .../constructor/inputBotInlineResult.html | 189 + .../inputBotInlineResultDocument.html | 179 + .../constructor/inputBotInlineResultGame.html | 157 + .../inputBotInlineResultPhoto.html | 164 + .../constructor/inputChannel.html | 155 + .../constructor/inputChannelEmpty.html | 132 + .../constructor/inputChannelFromMessage.html | 160 + .../constructor/inputChatPhoto.html | 147 + .../constructor/inputChatPhotoEmpty.html | 132 + .../constructor/inputChatUploadedPhoto.html | 165 + .../constructor/inputCheckPasswordEmpty.html | 132 + .../constructor/inputCheckPasswordSRP.html | 160 + .../constructor/inputClientProxy.html | 154 + .../constructor/inputDialogPeer.html | 147 + .../constructor/inputDialogPeerFolder.html | 150 + .../constructor/inputDocument.html | 162 + .../constructor/inputDocumentEmpty.html | 132 + .../inputDocumentFileLocation.html | 167 + .../constructor/inputEncryptedChat.html | 159 + .../constructor/inputEncryptedFile.html | 155 + .../inputEncryptedFileBigUploaded.html | 160 + .../constructor/inputEncryptedFileEmpty.html | 132 + .../inputEncryptedFileLocation.html | 155 + .../inputEncryptedFileUploaded.html | 162 + .../constructor/inputFile.html | 165 + .../constructor/inputFileBig.html | 160 + .../constructor/inputFileLocation.html | 165 + .../constructor/inputFolderPeer.html | 155 + .../constructor/inputGameID.html | 155 + .../constructor/inputGameShortName.html | 152 + .../constructor/inputGeoPoint.html | 162 + .../constructor/inputGroupCall.html | 152 + .../constructor/inputGroupCallStream.html | 172 + .../inputKeyboardButtonUrlAuth.html | 176 + .../constructor/inputMediaContact.html | 162 + .../constructor/inputMediaDice.html | 150 + .../constructor/inputMediaDocument.html | 162 + .../inputMediaDocumentExternal.html | 157 + .../constructor/inputMediaEmpty.html | 132 + .../constructor/inputMediaGame.html | 147 + .../constructor/inputMediaGeoLive.html | 175 + .../constructor/inputMediaGeoPoint.html | 147 + .../constructor/inputMediaInvoice.html | 189 + .../constructor/inputMediaPhoto.html | 157 + .../constructor/inputMediaPoll.html | 170 + .../inputMediaUploadedDocument.html | 190 + .../constructor/inputMediaUploadedPhoto.html | 165 + .../inputMediaUploadedThumbDocument.html | 176 + .../constructor/inputMediaVenue.html | 172 + .../inputMessageCallbackQuery.html | 152 + .../inputMessageEntityMentionName.html | 162 + .../constructor/inputMessageID.html | 147 + .../constructor/inputMessagePinned.html | 132 + .../constructor/inputMessageReplyTo.html | 147 + .../inputMessagesFilterChatPhotos.html | 132 + .../inputMessagesFilterContacts.html | 132 + .../inputMessagesFilterDocument.html | 132 + .../constructor/inputMessagesFilterEmpty.html | 132 + .../constructor/inputMessagesFilterGif.html | 132 + .../constructor/inputMessagesFilterMusic.html | 132 + .../inputMessagesFilterMyMentions.html | 135 + .../inputMessagesFilterPhoneCalls.html | 152 + .../inputMessagesFilterPhotoVideo.html | 132 + .../inputMessagesFilterPhotos.html | 132 + .../inputMessagesFilterPinned.html | 132 + .../inputMessagesFilterRoundVideo.html | 132 + .../inputMessagesFilterRoundVoice.html | 132 + .../constructor/inputMessagesFilterUrl.html | 132 + .../constructor/inputMessagesFilterVideo.html | 132 + .../constructor/inputMessagesFilterVoice.html | 132 + .../constructor/inputNotifyChats.html | 132 + .../constructor/inputNotifyPeer.html | 147 + .../constructor/inputNotifyUsers.html | 132 + .../constructor/inputPaymentCredentials.html | 157 + .../inputPaymentCredentialsApplePay.html | 147 + .../inputPaymentCredentialsGooglePay.html | 147 + .../inputPaymentCredentialsSaved.html | 152 + .../constructor/inputPeerChannel.html | 155 + .../inputPeerChannelFromMessage.html | 160 + .../constructor/inputPeerChat.html | 147 + .../constructor/inputPeerEmpty.html | 132 + .../inputPeerPhotoFileLocation.html | 162 + .../constructor/inputPeerSelf.html | 132 + .../constructor/inputPeerUser.html | 155 + .../constructor/inputPeerUserFromMessage.html | 160 + .../constructor/inputPhoneCall.html | 152 + .../constructor/inputPhoneContact.html | 166 + .../constructor/inputPhoto.html | 162 + .../constructor/inputPhotoEmpty.html | 132 + .../constructor/inputPhotoFileLocation.html | 171 + .../inputPhotoLegacyFileLocation.html | 172 + .../inputPrivacyKeyAddedByPhone.html | 132 + .../inputPrivacyKeyChatInvite.html | 132 + .../constructor/inputPrivacyKeyForwards.html | 132 + .../constructor/inputPrivacyKeyPhoneCall.html | 132 + .../inputPrivacyKeyPhoneNumber.html | 132 + .../constructor/inputPrivacyKeyPhoneP2P.html | 132 + .../inputPrivacyKeyProfilePhoto.html | 132 + .../inputPrivacyKeyStatusTimestamp.html | 132 + .../inputPrivacyValueAllowAll.html | 132 + ...nputPrivacyValueAllowChatParticipants.html | 147 + .../inputPrivacyValueAllowUsers.html | 147 + .../inputPrivacyValueDisallowAll.html | 132 + ...tPrivacyValueDisallowChatParticipants.html | 147 + .../inputPrivacyValueDisallowContacts.html | 132 + .../inputPrivacyValueDisallowUsers.html | 147 + .../inputReportReasonChildAbuse.html | 132 + .../inputReportReasonCopyright.html | 132 + .../constructor/inputReportReasonFake.html | 132 + .../constructor/inputReportReasonOther.html | 132 + .../inputReportReasonPornography.html | 132 + .../constructor/inputReportReasonSpam.html | 132 + .../inputReportReasonViolence.html | 132 + .../constructor/inputSecureFile.html | 155 + .../constructor/inputSecureFileLocation.html | 156 + .../constructor/inputSecureFileUploaded.html | 169 + .../constructor/inputSecureValue.html | 190 + .../constructor/inputSingleMedia.html | 174 + .../inputStickerSetAnimatedEmoji.html | 132 + ...nputStickerSetAnimatedEmojiAnimations.html | 132 + .../constructor/inputStickerSetDice.html | 150 + .../constructor/inputStickerSetEmpty.html | 132 + .../constructor/inputStickerSetID.html | 152 + .../constructor/inputStickerSetItem.html | 162 + .../constructor/inputStickerSetShortName.html | 147 + .../constructor/inputStickerSetThumb.html | 155 + .../inputStickeredMediaDocument.html | 147 + .../constructor/inputStickeredMediaPhoto.html | 147 + .../constructor/inputTakeoutFileLocation.html | 132 + .../constructor/inputTheme.html | 152 + .../constructor/inputThemeSettings.html | 182 + .../constructor/inputThemeSlug.html | 147 + .../constructor/inputUser.html | 155 + .../constructor/inputUserEmpty.html | 132 + .../constructor/inputUserFromMessage.html | 160 + .../constructor/inputUserSelf.html | 132 + .../constructor/inputWallPaper.html | 152 + .../constructor/inputWallPaperNoFile.html | 150 + .../constructor/inputWallPaperSlug.html | 147 + .../constructor/inputWebDocument.html | 165 + .../inputWebFileGeoPointLocation.html | 172 + .../constructor/invoice.html | 209 + .../constructor/jsonArray.html | 147 + .../constructor/jsonBool.html | 147 + .../constructor/jsonNull.html | 132 + .../constructor/jsonNumber.html | 147 + .../constructor/jsonObject.html | 147 + .../constructor/jsonObjectValue.html | 152 + .../constructor/jsonString.html | 147 + .../constructor/keyboardButton.html | 147 + .../constructor/keyboardButtonBuy.html | 147 + .../constructor/keyboardButtonCallback.html | 167 + .../constructor/keyboardButtonGame.html | 147 + .../keyboardButtonRequestGeoLocation.html | 147 + .../keyboardButtonRequestPhone.html | 147 + .../keyboardButtonRequestPoll.html | 157 + .../constructor/keyboardButtonRow.html | 147 + .../keyboardButtonSwitchInline.html | 162 + .../constructor/keyboardButtonUrl.html | 152 + .../constructor/keyboardButtonUrlAuth.html | 179 + .../constructor/labeledPrice.html | 154 + .../constructor/langPackDifference.html | 162 + .../constructor/langPackLanguage.html | 202 + .../constructor/langPackStringDeleted.html | 147 + .../constructor/langPackStringPluralized.html | 182 + .../constructor/maskCoords.html | 169 + .../constructor/message.html | 302 + .../constructor/messageActionBotAllowed.html | 149 + .../messageActionChannelCreate.html | 147 + .../messageActionChannelMigrateFrom.html | 155 + .../constructor/messageActionChatAddUser.html | 147 + .../constructor/messageActionChatCreate.html | 152 + .../messageActionChatDeletePhoto.html | 132 + .../messageActionChatDeleteUser.html | 147 + .../messageActionChatEditPhoto.html | 147 + .../messageActionChatEditTitle.html | 147 + .../messageActionChatJoinedByLink.html | 147 + .../messageActionChatMigrateTo.html | 150 + .../messageActionContactSignUp.html | 132 + .../messageActionCustomAction.html | 147 + .../constructor/messageActionEmpty.html | 132 + .../constructor/messageActionGameScore.html | 152 + .../messageActionGeoProximityReached.html | 160 + .../constructor/messageActionGroupCall.html | 157 + .../messageActionGroupCallScheduled.html | 152 + .../messageActionHistoryClear.html | 132 + .../messageActionInviteToGroupCall.html | 152 + .../constructor/messageActionPaymentSent.html | 154 + .../messageActionPaymentSentMe.html | 179 + .../constructor/messageActionPhoneCall.html | 167 + .../constructor/messageActionPinMessage.html | 132 + .../messageActionScreenshotTaken.html | 132 + .../messageActionSecureValuesSent.html | 149 + .../messageActionSecureValuesSentMe.html | 154 + .../messageActionSetChatTheme.html | 147 + .../messageActionSetMessagesTTL.html | 147 + .../constructor/messageEmpty.html | 157 + .../constructor/messageEntityBankCard.html | 152 + .../constructor/messageEntityBlockquote.html | 152 + .../constructor/messageEntityBold.html | 152 + .../constructor/messageEntityBotCommand.html | 152 + .../constructor/messageEntityCashtag.html | 152 + .../constructor/messageEntityCode.html | 152 + .../constructor/messageEntityEmail.html | 152 + .../constructor/messageEntityHashtag.html | 152 + .../constructor/messageEntityItalic.html | 152 + .../constructor/messageEntityMention.html | 155 + .../constructor/messageEntityMentionName.html | 162 + .../constructor/messageEntityPhone.html | 152 + .../constructor/messageEntityPre.html | 157 + .../constructor/messageEntityTextUrl.html | 160 + .../constructor/messageEntityUnderline.html | 152 + .../constructor/messageEntityUnknown.html | 152 + .../constructor/messageEntityUrl.html | 155 + .../constructor/messageFwdHeader.html | 195 + .../messageInteractionCounters.html | 157 + .../constructor/messageMediaAudio.html | 147 + .../constructor/messageMediaContact.html | 167 + .../constructor/messageMediaDice.html | 155 + .../constructor/messageMediaDocument.html | 157 + .../constructor/messageMediaEmpty.html | 132 + .../constructor/messageMediaGame.html | 147 + .../constructor/messageMediaGeo.html | 147 + .../constructor/messageMediaGeoLive.html | 170 + .../constructor/messageMediaInvoice.html | 198 + .../constructor/messageMediaPhoto.html | 157 + .../constructor/messageMediaPoll.html | 152 + .../constructor/messageMediaUnsupported.html | 132 + .../constructor/messageMediaVenue.html | 172 + .../constructor/messageMediaVideo.html | 147 + .../constructor/messageMediaWebPage.html | 147 + .../constructor/messageRange.html | 152 + .../constructor/messageReplies.html | 189 + .../constructor/messageReplyHeader.html | 165 + .../constructor/messageService.html | 212 + .../constructor/messageUserVote.html | 157 + .../messageUserVoteInputOption.html | 155 + .../constructor/messageViews.html | 165 + .../messages.affectedFoundMessages | 165 + .../constructor/messages.affectedHistory | 157 + .../constructor/messages.affectedMessages | 155 + .../constructor/messages.allStickers | 155 + .../messages.allStickersNotModified | 132 + .../constructor/messages.archivedStickers | 152 + .../constructor/messages.botCallbackAnswer | 177 + .../constructor/messages.botResults | 182 + .../constructor/messages.channelMessages | 185 + .../messages.chatAdminsWithInvites | 152 + .../constructor/messages.chatFull | 157 + .../constructor/messages.chatInviteImporters | 157 + .../constructor/messages.chats | 147 + .../constructor/messages.chatsSlice | 155 + .../messages.checkedHistoryImportPeer | 150 + .../constructor/messages.dhConfig | 162 + .../constructor/messages.dhConfigNotModified | 147 + .../constructor/messages.dialogs | 162 + .../constructor/messages.dialogsNotModified | 147 + .../constructor/messages.dialogsSlice | 167 + .../constructor/messages.discussionMessage | 185 + .../constructor/messages.exportedChatInvite | 152 + .../messages.exportedChatInviteReplaced | 157 + .../constructor/messages.exportedChatInvites | 157 + .../constructor/messages.favedStickers | 160 + .../messages.favedStickersNotModified | 132 + .../constructor/messages.featuredStickers | 165 + .../messages.featuredStickersNotModified | 147 + .../constructor/messages.foundStickerSets | 155 + .../messages.foundStickerSetsNotModified | 132 + .../constructor/messages.highScores | 152 + .../constructor/messages.historyImport | 150 + .../constructor/messages.historyImportParsed | 166 + .../constructor/messages.inactiveChats | 157 + .../constructor/messages.messageEditData | 152 + .../constructor/messages.messageViews | 157 + .../constructor/messages.messages | 157 + .../constructor/messages.messagesNotModified | 147 + .../constructor/messages.messagesSlice | 185 + .../constructor/messages.peerDialogs | 170 + .../constructor/messages.recentStickers | 165 + .../messages.recentStickersNotModified | 132 + .../constructor/messages.savedGifs | 155 + .../constructor/messages.savedGifsNotModified | 132 + .../constructor/messages.searchCounter | 165 + .../constructor/messages.sentEncryptedFile | 152 + .../constructor/messages.sentEncryptedMessage | 147 + .../constructor/messages.sentMessageLink | 167 + .../constructor/messages.sponsoredMessages | 157 + .../constructor/messages.statedMessageLink | 172 + .../constructor/messages.statedMessagesLinks | 172 + .../constructor/messages.stickerSet | 157 + .../messages.stickerSetInstallResultArchive | 147 + .../messages.stickerSetInstallResultSuccess | 132 + .../constructor/messages.stickers | 155 + .../constructor/messages.stickersNotModified | 132 + .../constructor/messages.votesList | 170 + .../constructor/nearestDc.html | 157 + .../constructor/notifyBroadcasts.html | 132 + .../constructor/notifyChats.html | 132 + .../constructor/notifyPeer.html | 147 + .../constructor/notifyUsers.html | 132 + data/core.telegram.org/constructor/null.html | 132 + data/core.telegram.org/constructor/page.html | 190 + .../constructor/pageBlockAnchor.html | 147 + .../constructor/pageBlockAudio.html | 155 + .../constructor/pageBlockAuthorDate.html | 152 + .../constructor/pageBlockBlockquote.html | 152 + .../constructor/pageBlockChannel.html | 147 + .../constructor/pageBlockCollage.html | 152 + .../constructor/pageBlockCover.html | 147 + .../constructor/pageBlockDetails.html | 162 + .../constructor/pageBlockDivider.html | 132 + .../constructor/pageBlockEmbed.html | 187 + .../constructor/pageBlockEmbedPost.html | 177 + .../constructor/pageBlockFooter.html | 147 + .../constructor/pageBlockHeader.html | 147 + .../constructor/pageBlockKicker.html | 147 + .../constructor/pageBlockList.html | 147 + .../constructor/pageBlockMap.html | 167 + .../constructor/pageBlockOrderedList.html | 147 + .../constructor/pageBlockParagraph.html | 147 + .../constructor/pageBlockPhoto.html | 167 + .../constructor/pageBlockPreformatted.html | 152 + .../constructor/pageBlockPullquote.html | 152 + .../constructor/pageBlockRelatedArticles.html | 152 + .../constructor/pageBlockSlideshow.html | 152 + .../constructor/pageBlockSubheader.html | 147 + .../constructor/pageBlockSubtitle.html | 147 + .../constructor/pageBlockTitle.html | 147 + .../constructor/pageBlockUnsupported.html | 132 + .../constructor/pageBlockVideo.html | 167 + .../constructor/pageCaption.html | 152 + .../constructor/pageListItemBlocks.html | 147 + .../constructor/pageListItemText.html | 147 + .../pageListOrderedItemBlocks.html | 152 + .../constructor/pageListOrderedItemText.html | 152 + .../constructor/pageRelatedArticle.html | 182 + .../constructor/pageTableCell.html | 187 + .../constructor/pageTableRow.html | 147 + ...BKDF2HMACSHA512iter100000SHA256ModPow.html | 165 + .../constructor/passwordKdfAlgoUnknown.html | 132 + .../constructor/paymentCharge.html | 152 + .../constructor/paymentRequestedInfo.html | 167 + .../paymentSavedCredentialsCard.html | 152 + .../payments.ValidatedRequestedInfo | 145 + .../constructor/payments.bankCardData | 152 + .../constructor/payments.paymentForm | 210 + .../constructor/payments.paymentReceipt | 219 + .../constructor/payments.paymentResult | 147 + .../payments.paymentVerificationNeeded | 147 + .../constructor/payments.savedInfo | 157 + .../constructor/peerBlocked.html | 152 + .../constructor/peerChannel.html | 147 + .../constructor/peerChat.html | 147 + .../constructor/peerLocated.html | 157 + .../constructor/peerNotifySettings.html | 182 + .../constructor/peerSelfLocated.html | 147 + .../constructor/peerSettings.html | 197 + .../constructor/phone.exportedGroupCallInvite | 147 + .../constructor/phone.groupCall | 170 + .../constructor/phone.groupParticipants | 175 + .../constructor/phone.joinAsPeers | 157 + .../constructor/phone.phoneCall | 152 + .../constructor/phoneCall.html | 209 + .../constructor/phoneCallAccepted.html | 189 + .../phoneCallDiscardReasonBusy.html | 132 + .../phoneCallDiscardReasonDisconnect.html | 132 + .../phoneCallDiscardReasonHangup.html | 132 + .../phoneCallDiscardReasonMissed.html | 132 + .../constructor/phoneCallDiscarded.html | 182 + .../constructor/phoneCallEmpty.html | 147 + .../constructor/phoneCallProtocol.html | 179 + .../constructor/phoneCallRequested.html | 189 + .../constructor/phoneCallWaiting.html | 187 + .../constructor/phoneConnection.html | 167 + .../constructor/phoneConnectionWebrtc.html | 187 + data/core.telegram.org/constructor/photo.html | 192 + .../constructor/photoCachedSize.html | 167 + .../constructor/photoPathSize.html | 155 + .../constructor/photoSize.html | 167 + .../constructor/photoSizeEmpty.html | 150 + .../constructor/photoSizeProgressive.html | 167 + .../constructor/photoStrippedSize.html | 159 + .../constructor/photos.photo | 152 + .../constructor/photos.photos | 152 + .../constructor/photos.photosSlice | 157 + data/core.telegram.org/constructor/poll.html | 195 + .../constructor/pollAnswer.html | 155 + .../constructor/pollAnswerVoters.html | 170 + .../constructor/pollResults.html | 184 + .../constructor/popularContact.html | 152 + .../constructor/postAddress.html | 172 + .../constructor/privacyKeyAddedByPhone.html | 132 + .../constructor/privacyKeyChatInvite.html | 132 + .../constructor/privacyKeyForwards.html | 132 + .../constructor/privacyKeyPhoneCall.html | 132 + .../constructor/privacyKeyPhoneP2P.html | 132 + .../privacyKeyStatusTimestamp.html | 132 + .../constructor/privacyValueAllowAll.html | 132 + .../privacyValueAllowChatParticipants.html | 147 + .../privacyValueAllowContacts.html | 132 + .../privacyValueDisallowChatParticipants.html | 147 + .../privacyValueDisallowContacts.html | 132 + .../privacyValueDisallowUsers.html | 147 + .../constructor/receivedNotifyMessage.html | 152 + .../constructor/recentMeUrlChat.html | 152 + .../constructor/recentMeUrlChatInvite.html | 152 + .../constructor/recentMeUrlStickerSet.html | 152 + .../constructor/recentMeUrlUnknown.html | 147 + .../constructor/recentMeUrlUser.html | 152 + .../constructor/replyInlineMarkup.html | 147 + .../constructor/replyKeyboardForceReply.html | 162 + .../constructor/replyKeyboardHide.html | 152 + .../constructor/restrictionReason.html | 158 + .../constructor/savedPhoneContact.html | 162 + .../secureCredentialsEncrypted.html | 159 + .../constructor/secureData.html | 160 + .../constructor/secureFile.html | 180 + .../constructor/secureFileEmpty.html | 132 + ...wordKdfAlgoPBKDF2HMACSHA512iter100000.html | 147 + .../securePasswordKdfAlgoSHA512.html | 147 + .../securePasswordKdfAlgoUnknown.html | 132 + .../constructor/securePlainEmail.html | 150 + .../constructor/securePlainPhone.html | 150 + .../constructor/secureRequiredType.html | 167 + .../constructor/secureRequiredTypeOneOf.html | 147 + .../constructor/secureSecretSettings.html | 157 + .../constructor/secureValue.html | 194 + .../constructor/secureValueError.html | 157 + .../constructor/secureValueErrorData.html | 175 + .../constructor/secureValueErrorFile.html | 168 + .../constructor/secureValueErrorFiles.html | 168 + .../secureValueErrorFrontSide.html | 166 + .../secureValueErrorReverseSide.html | 162 + .../constructor/secureValueErrorSelfie.html | 166 + .../secureValueErrorTranslationFile.html | 178 + .../secureValueErrorTranslationFiles.html | 178 + .../constructor/secureValueHash.html | 152 + .../constructor/secureValueTypeAddress.html | 132 + .../secureValueTypeBankStatement.html | 132 + .../secureValueTypeDriverLicense.html | 132 + .../constructor/secureValueTypeEmail.html | 132 + .../secureValueTypeIdentityCard.html | 132 + .../secureValueTypeInternalPassport.html | 134 + .../constructor/secureValueTypePassport.html | 132 + .../secureValueTypePassportRegistration.html | 134 + .../secureValueTypePersonalDetails.html | 132 + .../constructor/secureValueTypePhone.html | 132 + .../secureValueTypeRentalAgreement.html | 132 + .../secureValueTypeTemporaryRegistration.html | 132 + .../secureValueTypeUtilityBill.html | 132 + .../constructor/sendMessageCancelAction.html | 132 + .../sendMessageChooseContactAction.html | 132 + .../sendMessageChooseStickerAction.html | 132 + .../sendMessageEmojiInteraction.html | 160 + .../sendMessageEmojiInteractionSeen.html | 150 + .../sendMessageGamePlayAction.html | 132 + .../sendMessageGeoLocationAction.html | 132 + .../sendMessageHistoryImportAction.html | 147 + .../sendMessageRecordAudioAction.html | 132 + .../sendMessageRecordRoundAction.html | 132 + .../sendMessageRecordVideoAction.html | 132 + .../constructor/sendMessageTypingAction.html | 132 + .../sendMessageUploadAudioAction.html | 147 + .../sendMessageUploadDocumentAction.html | 147 + .../sendMessageUploadPhotoAction.html | 147 + .../sendMessageUploadRoundAction.html | 147 + .../sendMessageUploadVideoAction.html | 147 + .../constructor/shippingOption.html | 157 + .../speakingInGroupCallAction.html | 132 + .../constructor/sponsoredMessage.html | 178 + .../constructor/stats.broadcastStats | 220 + .../constructor/stats.megagroupStats | 230 + .../constructor/stats.messageStats | 147 + .../constructor/statsAbsValueAndPrev.html | 152 + .../constructor/statsDateRangeDays.html | 155 + .../constructor/statsGraph.html | 160 + .../constructor/statsGraphAsync.html | 152 + .../constructor/statsGraphError.html | 150 + .../constructor/statsGroupTopAdmin.html | 165 + .../constructor/statsGroupTopPoster.html | 160 + .../constructor/statsPercentValue.html | 156 + .../constructor/statsURL.html | 147 + .../constructor/stickerPack.html | 156 + .../constructor/stickerSet.html | 217 + .../constructor/stickerSetCovered.html | 152 + .../constructor/stickerSetMultiCovered.html | 152 + .../constructor/stickers.suggestedShortName | 147 + .../constructor/storage.fileGif | 132 + .../constructor/storage.fileJpeg | 132 + .../constructor/storage.fileMov | 132 + .../constructor/storage.fileMp3 | 132 + .../constructor/storage.fileMp4 | 132 + .../constructor/storage.filePartial | 132 + .../constructor/storage.filePdf | 132 + .../constructor/storage.filePng | 132 + .../constructor/storage.fileUnknown | 132 + .../constructor/storage.fileWebp | 132 + .../constructor/textAnchor.html | 152 + .../constructor/textBold.html | 147 + .../constructor/textConcat.html | 147 + .../constructor/textEmail.html | 152 + .../constructor/textEmpty.html | 132 + .../constructor/textFixed.html | 147 + .../constructor/textImage.html | 157 + .../constructor/textItalic.html | 147 + .../constructor/textMarked.html | 147 + .../constructor/textPhone.html | 152 + .../constructor/textPlain.html | 147 + .../constructor/textStrike.html | 147 + .../constructor/textSubscript.html | 147 + .../constructor/textSuperscript.html | 147 + .../constructor/textUnderline.html | 147 + .../constructor/textUrl.html | 157 + .../constructor/themeSettings.html | 177 + .../constructor/topPeer.html | 155 + .../topPeerCategoryBotsInline.html | 132 + .../constructor/topPeerCategoryBotsPM.html | 132 + .../constructor/topPeerCategoryChannels.html | 132 + .../topPeerCategoryCorrespondents.html | 132 + .../topPeerCategoryForwardChats.html | 132 + .../topPeerCategoryForwardUsers.html | 132 + .../constructor/topPeerCategoryGroups.html | 132 + .../constructor/topPeerCategoryPeers.html | 157 + .../topPeerCategoryPhoneCalls.html | 132 + data/core.telegram.org/constructor/true.html | 134 + .../constructor/updateBotCallbackQuery.html | 182 + .../constructor/updateBotCommands.html | 159 + .../constructor/updateBotInlineQuery.html | 177 + .../constructor/updateBotInlineSend.html | 172 + .../updateBotPrecheckoutQuery.html | 184 + .../constructor/updateBotShippingQuery.html | 162 + .../constructor/updateBotStopped.html | 165 + .../constructor/updateBotWebhookJSON.html | 147 + .../updateBotWebhookJSONQuery.html | 157 + .../constructor/updateChannel.html | 147 + .../updateChannelAvailableMessages.html | 155 + .../updateChannelMessageViews.html | 157 + .../constructor/updateChannelParticipant.html | 192 + .../updateChannelReadMessagesContents.html | 155 + .../constructor/updateChannelTooLong.html | 161 + .../constructor/updateChannelUserTyping.html | 172 + .../constructor/updateChannelWebPage.html | 167 + .../constructor/updateChat.html | 147 + .../updateChatDefaultBannedRights.html | 160 + .../constructor/updateChatParticipant.html | 192 + .../constructor/updateChatParticipantAdd.html | 167 + .../updateChatParticipantAdmin.html | 165 + .../updateChatParticipantDelete.html | 157 + .../constructor/updateChatParticipants.html | 147 + .../constructor/updateChatUserTyping.html | 160 + .../constructor/updateConfig.html | 135 + .../constructor/updateContactsReset.html | 132 + .../constructor/updateDcOptions.html | 147 + .../updateDeleteChannelMessages.html | 167 + .../constructor/updateDeleteMessages.html | 160 + .../updateDeleteScheduledMessages.html | 155 + .../constructor/updateDialogFilter.html | 160 + .../constructor/updateDialogFilterOrder.html | 150 + .../constructor/updateDialogFilters.html | 135 + .../constructor/updateDialogPinned.html | 165 + .../constructor/updateDialogUnreadMark.html | 157 + .../constructor/updateDraftMessage.html | 155 + .../constructor/updateEditChannelMessage.html | 162 + .../constructor/updateEditMessage.html | 160 + .../updateEncryptedChatTyping.html | 147 + .../updateEncryptedMessagesRead.html | 157 + .../constructor/updateEncryption.html | 152 + .../constructor/updateFavedStickers.html | 135 + .../constructor/updateFolderPeers.html | 162 + .../constructor/updateGeoLiveViewed.html | 152 + .../constructor/updateGroupCall.html | 155 + .../updateGroupCallConnection.html | 157 + .../updateGroupCallParticipants.html | 157 + .../updateInlineBotCallbackQuery.html | 177 + .../constructor/updateLangPack.html | 147 + .../constructor/updateLangPackTooLong.html | 150 + .../constructor/updateLoginToken.html | 132 + .../constructor/updateMessageID.html | 155 + .../constructor/updateMessagePoll.html | 162 + .../constructor/updateMessagePollVote.html | 165 + .../constructor/updateNewChannelMessage.html | 162 + .../updateNewEncryptedMessage.html | 155 + .../constructor/updateNewMessage.html | 157 + .../updateNewScheduledMessage.html | 150 + .../constructor/updateNewStickerSet.html | 147 + .../constructor/updateNotifySettings.html | 152 + .../constructor/updatePeerBlocked.html | 152 + .../constructor/updatePeerHistoryTTL.html | 157 + .../constructor/updatePeerLocated.html | 147 + .../constructor/updatePeerSettings.html | 152 + .../constructor/updatePhoneCall.html | 147 + .../updatePhoneCallSignalingData.html | 152 + .../updatePinnedChannelMessages.html | 177 + .../constructor/updatePinnedDialogs.html | 160 + .../constructor/updatePinnedMessages.html | 175 + .../constructor/updatePrivacy.html | 152 + .../constructor/updatePtsChanged.html | 135 + .../updateReadChannelDiscussionOutbox.html | 162 + .../constructor/updateReadChannelInbox.html | 179 + .../constructor/updateReadChannelOutbox.html | 155 + .../updateReadFeaturedStickers.html | 132 + .../constructor/updateReadHistoryInbox.html | 182 + .../constructor/updateReadHistoryOutbox.html | 165 + .../updateReadMessagesContents.html | 160 + .../constructor/updateRecentStickers.html | 132 + .../constructor/updateSavedGifs.html | 132 + .../updateServiceNotification.html | 183 + .../constructor/updateShort.html | 152 + .../constructor/updateShortMessage.html | 229 + .../constructor/updateShortSentMessage.html | 192 + .../constructor/updateStickerSets.html | 132 + .../constructor/updateStickerSetsOrder.html | 157 + .../constructor/updateTheme.html | 147 + .../constructor/updateUserBlocked.html | 159 + .../constructor/updateUserName.html | 167 + .../constructor/updateUserPhone.html | 152 + .../constructor/updateUserPhoto.html | 165 + .../constructor/updateUserStatus.html | 152 + .../constructor/updateUserTyping.html | 155 + .../constructor/updateWebPage.html | 160 + .../constructor/updates.channelDifference | 185 + .../updates.channelDifferenceEmpty | 165 + .../updates.channelDifferenceTooLong | 190 + .../constructor/updates.difference | 172 + .../constructor/updates.differenceEmpty | 152 + .../constructor/updates.differenceSlice | 175 + .../constructor/updates.differenceTooLong | 150 + .../constructor/updates.html | 167 + .../constructor/updates.state | 172 + .../constructor/updatesCombined.html | 172 + .../constructor/updatesTooLong.html | 135 + .../constructor/upload.cdnFile | 149 + .../constructor/upload.cdnFileReuploadNeeded | 149 + .../core.telegram.org/constructor/upload.file | 157 + .../constructor/upload.fileCdnRedirect | 169 + .../constructor/upload.webFile | 170 + .../constructor/urlAuthResultAccepted.html | 150 + .../constructor/urlAuthResultDefault.html | 135 + .../constructor/urlAuthResultRequest.html | 165 + data/core.telegram.org/constructor/user.html | 287 + .../constructor/userEmpty.html | 147 + .../constructor/userFull.html | 239 + .../constructor/userProfilePhoto.html | 172 + .../constructor/userProfilePhotoEmpty.html | 132 + .../constructor/userStatusEmpty.html | 132 + .../constructor/userStatusLastMonth.html | 132 + .../constructor/userStatusLastWeek.html | 132 + .../constructor/userStatusOffline.html | 147 + .../constructor/userStatusOnline.html | 147 + .../constructor/userStatusRecently.html | 132 + .../core.telegram.org/constructor/vector.html | 134 + .../constructor/videoSize.html | 175 + .../constructor/wallPaper.html | 192 + .../constructor/wallPaperNoFile.html | 171 + .../constructor/wallPaperSettings.html | 187 + .../constructor/wallPaperSolid.html | 162 + .../constructor/webAuthorization.html | 189 + .../constructor/webDocument.html | 167 + .../constructor/webDocumentNoProxy.html | 165 + .../constructor/webPage.html | 240 + .../constructor/webPageAttributeTheme.html | 157 + .../constructor/webPageEmpty.html | 147 + .../constructor/webPageNotModified.html | 152 + .../constructor/webPagePending.html | 152 + data/core.telegram.org/contest300K.html | 237 + data/core.telegram.org/import-stickers.html | 159 + .../method/account.acceptAuthorization | 170 + .../method/account.cancelPasswordEmail | 138 + .../method/account.changePhone | 190 + .../method/account.checkUsername | 167 + .../method/account.confirmPasswordEmail | 175 + .../method/account.confirmPhone | 180 + .../method/account.createTheme | 186 + .../method/account.declinePasswordReset | 155 + .../method/account.deleteAccount | 170 + .../method/account.deleteSecureValue | 153 + .../method/account.finishTakeoutSession | 172 + .../method/account.getAccountTTL | 134 + .../method/account.getAllSecureValues | 136 + .../method/account.getAuthorizationForm | 176 + .../method/account.getAuthorizations | 134 + .../method/account.getAutoDownloadSettings | 134 + .../method/account.getChatThemes | 153 + .../account.getContactSignUpNotification | 135 + .../method/account.getContentSettings | 134 + .../method/account.getGlobalPrivacySettings | 134 + .../method/account.getMultiWallPapers | 148 + .../method/account.getNotifyExceptions | 165 + .../method/account.getNotifySettings | 166 + .../method/account.getPasswordSettings | 170 + .../method/account.getPrivacy | 166 + .../method/account.getSecureValue | 151 + .../core.telegram.org/method/account.getTheme | 181 + .../method/account.getThemes | 158 + .../method/account.getTmpPassword | 176 + .../method/account.getWallPaper | 167 + .../method/account.getWallPapers | 153 + .../method/account.getWebAuthorizations | 136 + .../method/account.initTakeoutSession | 204 + .../method/account.installTheme | 165 + .../method/account.installWallPaper | 172 + .../method/account.registerDevice | 217 + .../method/account.reportPeer | 182 + .../method/account.reportProfilePhoto | 165 + .../method/account.resendPasswordEmail | 138 + .../method/account.resetAuthorization | 175 + .../method/account.resetNotifySettings | 135 + .../method/account.resetPassword | 139 + .../method/account.resetWallPapers | 135 + .../method/account.resetWebAuthorization | 171 + .../method/account.resetWebAuthorizations | 137 + .../method/account.saveAutoDownloadSettings | 165 + .../method/account.saveSecureValue | 174 + .../method/account.saveTheme | 155 + .../method/account.saveWallPaper | 177 + .../method/account.sendChangePhoneCode | 186 + .../method/account.sendConfirmPhoneCode | 174 + .../method/account.sendVerifyEmailCode | 168 + .../method/account.sendVerifyPhoneCode | 173 + .../method/account.setAccountTTL | 167 + .../account.setContactSignUpNotification | 150 + .../method/account.setContentSettings | 172 + .../method/account.setGlobalPrivacySettings | 166 + .../method/account.setPrivacy | 181 + .../method/account.unregisterDevice | 180 + .../method/account.updateDeviceLocked | 153 + .../method/account.updateNotifySettings | 192 + .../method/account.updatePasswordSettings | 207 + .../method/account.updateProfile | 187 + .../method/account.updateStatus | 155 + .../method/account.updateTheme | 196 + .../method/account.updateUsername | 182 + .../method/account.uploadTheme | 190 + .../method/account.uploadWallPaper | 182 + .../method/account.verifyEmail | 179 + .../method/account.verifyPhone | 191 + .../method/auth.acceptLoginToken | 171 + .../method/auth.bindTempAuthKey | 252 + data/core.telegram.org/method/auth.cancelCode | 180 + .../method/auth.checkPassword | 180 + data/core.telegram.org/method/auth.checkPhone | 176 + .../method/auth.checkRecoveryPassword | 174 + .../method/auth.dropTempAuthKeys | 151 + .../method/auth.exportAuthorization | 167 + .../method/auth.exportLoginToken | 183 + .../method/auth.importAuthorization | 178 + .../method/auth.importBotAuthorization | 205 + .../method/auth.importLoginToken | 187 + data/core.telegram.org/method/auth.logOut | 140 + .../method/auth.recoverPassword | 187 + .../method/auth.requestPasswordRecovery | 159 + data/core.telegram.org/method/auth.resendCode | 191 + .../method/auth.resetAuthorizations | 156 + data/core.telegram.org/method/auth.sendCall | 175 + data/core.telegram.org/method/auth.sendCode | 236 + .../core.telegram.org/method/auth.sendInvites | 157 + data/core.telegram.org/method/auth.sendSms | 167 + data/core.telegram.org/method/auth.signIn | 219 + data/core.telegram.org/method/auth.signUp | 236 + .../method/bots.answerWebhookJSONQuery | 178 + .../method/bots.getBotCommands | 154 + .../method/bots.resetBotCommands | 156 + .../method/bots.sendCustomRequest | 177 + .../method/bots.setBotCommands | 188 + .../method/channels.checkUsername | 190 + .../method/channels.convertToGigagroup | 177 + .../method/channels.createChannel | 232 + .../method/channels.deleteChannel | 200 + .../method/channels.deleteHistory | 180 + .../method/channels.deleteMessages | 190 + .../method/channels.deleteUserHistory | 199 + .../method/channels.editAdmin | 301 + .../method/channels.editBanned | 241 + .../method/channels.editCreator | 225 + .../method/channels.editLocation | 180 + .../method/channels.editPhoto | 221 + .../method/channels.editTitle | 206 + .../method/channels.exportMessageLink | 204 + .../method/channels.getAdminLog | 226 + .../method/channels.getAdminedPublicChannels | 191 + .../method/channels.getChannels | 181 + .../method/channels.getFullChannel | 187 + .../method/channels.getGroupsForDiscussion | 144 + .../method/channels.getInactiveChannels | 134 + .../method/channels.getLeftChannels | 172 + .../method/channels.getMessages | 193 + .../method/channels.getParticipant | 205 + .../method/channels.getParticipants | 203 + .../method/channels.getSponsoredMessages | 154 + .../method/channels.inviteToChannel | 262 + .../method/channels.joinChannel | 227 + .../method/channels.leaveChannel | 201 + .../method/channels.readHistory | 185 + .../method/channels.readMessageContents | 185 + .../method/channels.setDiscussionGroup | 200 + .../method/channels.setStickers | 183 + .../method/channels.togglePreHistoryHidden | 202 + .../method/channels.toggleSignatures | 187 + .../method/channels.toggleSlowMode | 190 + .../method/channels.updateUsername | 212 + .../method/contacts.acceptContact | 190 + .../method/contacts.addContact | 217 + data/core.telegram.org/method/contacts.block | 182 + .../method/contacts.blockFromReplies | 178 + .../method/contacts.deleteByPhones | 150 + .../method/contacts.deleteContacts | 155 + .../method/contacts.getBlocked | 155 + .../method/contacts.getContactIDs | 151 + .../method/contacts.getContacts | 155 + .../method/contacts.getLocated | 197 + .../method/contacts.getSaved | 150 + .../method/contacts.getStatuses | 133 + .../method/contacts.getTopPeers | 226 + .../method/contacts.importContacts | 154 + .../method/contacts.resetSaved | 135 + .../method/contacts.resetTopPeerRating | 175 + .../method/contacts.resolveUsername | 182 + data/core.telegram.org/method/contacts.search | 178 + .../method/contacts.toggleTopPeers | 153 + .../core.telegram.org/method/contacts.unblock | 182 + .../method/folders.deleteFolder | 175 + .../method/folders.editPeerFolders | 175 + .../method/help.acceptTermsOfService | 150 + .../method/help.dismissSuggestion | 160 + .../method/help.editUserInfo | 180 + .../method/help.getAppChangelog | 162 + .../method/help.getAppConfig | 142 + .../method/help.getAppUpdate | 150 + .../method/help.getCdnConfig | 154 + data/core.telegram.org/method/help.getConfig | 192 + .../method/help.getCountriesList | 158 + .../method/help.getDeepLinkInfo | 150 + .../method/help.getInviteText | 134 + .../method/help.getNearestDc | 134 + .../method/help.getPassportConfig | 154 + .../method/help.getPromoData | 135 + .../method/help.getProxyData | 132 + .../method/help.getRecentMeUrls | 149 + data/core.telegram.org/method/help.getSupport | 134 + .../method/help.getSupportName | 151 + .../method/help.getTermsOfServiceUpdate | 135 + .../core.telegram.org/method/help.getUserInfo | 167 + .../method/help.hidePromoData | 150 + data/core.telegram.org/method/help.saveAppLog | 150 + .../method/help.setBotUpdatesStatus | 156 + .../method/initConnection.html | 216 + .../method/invokeAfterMsg.html | 154 + .../method/invokeAfterMsgs.html | 154 + .../method/invokeWithLayer.html | 204 + .../method/invokeWithMessagesRange.html | 154 + .../method/invokeWithTakeout.html | 154 + .../method/invokeWithoutUpdates.html | 154 + .../method/langpack.getDifference | 176 + .../method/langpack.getLangPack | 171 + .../method/langpack.getLanguage | 154 + .../method/langpack.getLanguages | 165 + .../method/langpack.getStrings | 175 + .../method/messages.acceptEncryption | 190 + .../method/messages.addChatUser | 237 + .../method/messages.checkChatInvite | 178 + .../method/messages.checkHistoryImport | 152 + .../method/messages.checkHistoryImportPeer | 172 + .../method/messages.clearAllDrafts | 138 + .../method/messages.clearRecentStickers | 155 + .../method/messages.createChat | 197 + .../method/messages.deleteChat | 170 + .../method/messages.deleteChatUser | 208 + .../method/messages.deleteExportedChatInvite | 155 + .../method/messages.deleteHistory | 206 + .../method/messages.deleteMessages | 177 + .../method/messages.deletePhoneCallHistory | 154 + .../messages.deleteRevokedExportedChatInvites | 155 + .../method/messages.deleteScheduledMessages | 160 + .../method/messages.discardEncryption | 187 + .../method/messages.editChatAbout | 216 + .../method/messages.editChatAdmin | 195 + .../messages.editChatDefaultBannedRights | 206 + .../method/messages.editChatPhoto | 203 + .../method/messages.editChatTitle | 193 + .../method/messages.editExportedChatInvite | 193 + .../method/messages.editInlineBotMessage | 206 + .../method/messages.editMessage | 338 + .../method/messages.exportChatInvite | 217 + .../method/messages.faveSticker | 172 + .../method/messages.forwardMessage | 177 + .../method/messages.forwardMessages | 363 + .../method/messages.getAdminsWithInvites | 149 + .../method/messages.getAllChats | 150 + .../method/messages.getAllDrafts | 143 + .../method/messages.getAllStickers | 153 + .../method/messages.getArchivedStickers | 167 + .../method/messages.getAttachedStickers | 148 + .../method/messages.getBotCallbackAnswer | 226 + .../method/messages.getChatInviteImporters | 172 + .../method/messages.getChats | 173 + .../method/messages.getCommonChats | 185 + .../method/messages.getDhConfig | 175 + .../method/messages.getDialogFilters | 136 + .../method/messages.getDialogUnreadMarks | 133 + .../method/messages.getDialogs | 213 + .../method/messages.getDiscussionMessage | 183 + .../method/messages.getDocumentByHash | 178 + .../method/messages.getEmojiKeywords | 149 + .../messages.getEmojiKeywordsDifference | 154 + .../method/messages.getEmojiURL | 149 + .../method/messages.getExportedChatInvite | 155 + .../method/messages.getFavedStickers | 153 + .../method/messages.getFeaturedStickers | 153 + .../method/messages.getFullChat | 172 + .../method/messages.getGameHighScores | 187 + .../method/messages.getInlineBotResults | 226 + .../method/messages.getInlineGameHighScores | 177 + .../method/messages.getMaskStickers | 153 + .../method/messages.getMessageEditData | 186 + .../method/messages.getMessageReactionsList | 178 + .../messages.getMessageReadParticipants | 173 + .../method/messages.getMessages | 153 + .../method/messages.getMessagesReactions | 153 + .../method/messages.getMessagesViews | 199 + .../method/messages.getOldFeaturedStickers | 163 + .../method/messages.getOnlines | 171 + .../method/messages.getPeerDialogs | 181 + .../method/messages.getPeerSettings | 171 + .../method/messages.getPinnedDialogs | 169 + .../method/messages.getPollResults | 177 + .../method/messages.getPollVotes | 204 + .../method/messages.getRecentLocations | 165 + .../method/messages.getRecentStickers | 163 + .../method/messages.getReplies | 217 + .../method/messages.getSavedGifs | 153 + .../method/messages.getScheduledHistory | 182 + .../method/messages.getSearchCounters | 173 + .../method/messages.getSplitRanges | 133 + .../method/messages.getStickerSet | 172 + .../method/messages.getStickers | 175 + .../method/messages.getSuggestedDialogFilters | 136 + .../method/messages.getUnreadMentions | 212 + .../method/messages.getWebPage | 177 + .../method/messages.getWebPagePreview | 191 + .../method/messages.hidePeerSettingsBar | 153 + .../method/messages.importChatInvite | 227 + .../method/messages.initHistoryImport | 191 + .../method/messages.installStickerSet | 172 + .../method/messages.markDialogUnread | 160 + .../method/messages.migrateChat | 190 + .../method/messages.readDiscussion | 180 + .../method/messages.readEncryptedHistory | 172 + .../method/messages.readFeaturedStickers | 150 + .../method/messages.readHistory | 186 + .../method/messages.readMentions | 181 + .../method/messages.readMessageContents | 149 + .../method/messages.receivedMessages | 148 + .../method/messages.receivedQueue | 170 + .../method/messages.reorderPinnedDialogs | 185 + .../method/messages.reorderStickerSets | 160 + data/core.telegram.org/method/messages.report | 187 + .../method/messages.reportEncryptedSpam | 167 + .../method/messages.reportSpam | 180 + .../method/messages.requestEncryption | 185 + .../method/messages.requestUrlAuth | 174 + .../method/messages.saveDraft | 202 + .../core.telegram.org/method/messages.saveGif | 172 + .../method/messages.saveRecentSticker | 182 + data/core.telegram.org/method/messages.search | 291 + .../method/messages.searchGifs | 177 + .../method/messages.searchGlobal | 226 + .../method/messages.searchStickerSets | 168 + .../method/messages.sendBroadcast | 145 + .../method/messages.sendEncrypted | 210 + .../method/messages.sendEncryptedFile | 215 + .../method/messages.sendEncryptedService | 205 + .../method/messages.sendInlineBotResult | 344 + .../method/messages.sendMedia | 518 + .../method/messages.sendMessage | 398 + .../method/messages.sendMultiMedia | 263 + .../method/messages.sendReaction | 185 + .../method/messages.sendScheduledMessages | 182 + .../messages.sendScreenshotNotification | 187 + .../method/messages.sendVote | 220 + .../method/messages.setBotCallbackAnswer | 203 + .../method/messages.setBotPrecheckoutResults | 188 + .../method/messages.setBotShippingResults | 186 + .../method/messages.setChatTheme | 185 + .../method/messages.setEncryptedTyping | 177 + .../method/messages.setGameScore | 218 + .../method/messages.setHistoryTTL | 182 + .../method/messages.setInlineBotResults | 358 + .../method/messages.setInlineGameScore | 198 + .../method/messages.setTyping | 240 + .../method/messages.startBot | 224 + .../method/messages.toggleDialogPin | 187 + .../method/messages.toggleStickerSets | 170 + .../method/messages.uninstallStickerSet | 167 + .../method/messages.unpinAllMessages | 153 + .../method/messages.updateDialogFilter | 190 + .../method/messages.updateDialogFiltersOrder | 153 + .../method/messages.updatePinnedMessage | 233 + .../method/messages.uploadEncryptedFile | 155 + .../method/messages.uploadImportedMedia | 181 + .../method/messages.uploadMedia | 264 + .../method/payments.clearSavedInfo | 160 + .../method/payments.getBankCardData | 166 + .../method/payments.getPaymentForm | 181 + .../method/payments.getPaymentReceipt | 171 + .../method/payments.getSavedInfo | 134 + .../method/payments.sendPaymentForm | 206 + .../method/payments.validateRequestedInfo | 186 + .../core.telegram.org/method/phone.acceptCall | 193 + .../method/phone.checkGroupCall | 154 + .../method/phone.confirmCall | 188 + .../method/phone.createGroupCall | 200 + .../method/phone.discardCall | 202 + .../method/phone.discardGroupCall | 155 + .../method/phone.editGroupCallMember | 167 + .../method/phone.editGroupCallParticipant | 225 + .../method/phone.editGroupCallTitle | 160 + .../method/phone.exportGroupCallInvite | 159 + .../method/phone.getCallConfig | 134 + .../method/phone.getGroupCall | 157 + .../method/phone.getGroupCallJoinAs | 149 + .../method/phone.getGroupParticipants | 174 + .../method/phone.inviteToGroupCall | 177 + .../method/phone.joinGroupCall | 202 + .../method/phone.joinGroupCallPresentation | 180 + .../method/phone.leaveGroupCall | 160 + .../method/phone.leaveGroupCallPresentation | 155 + .../method/phone.receivedCall | 172 + .../method/phone.requestCall | 213 + .../method/phone.saveCallDebug | 177 + .../method/phone.saveDefaultGroupCallJoinAs | 155 + .../method/phone.sendSignalingData | 155 + .../method/phone.setCallRating | 192 + .../method/phone.startScheduledGroupCall | 155 + .../method/phone.toggleGroupCallRecord | 180 + .../phone.toggleGroupCallStartSubscription | 160 + .../method/photos.deletePhotos | 148 + .../method/photos.getUserPhotos | 193 + .../method/photos.updateProfilePhoto | 196 + .../method/photos.uploadProfilePhoto | 221 + .../method/stats.getBroadcastStats | 194 + .../method/stats.getMegagroupStats | 191 + .../method/stats.getMessagePublicForwards | 212 + .../method/stats.getMessageStats | 189 + .../method/stats.loadAsyncGraph | 193 + .../method/stickers.addStickerToSet | 187 + .../method/stickers.changeStickerPosition | 177 + .../method/stickers.checkShortName | 172 + .../method/stickers.createStickerSet | 282 + .../method/stickers.removeStickerFromSet | 172 + .../method/stickers.setStickerSetThumb | 182 + .../method/stickers.suggestShortName | 166 + .../method/updates.getChannelDifference | 247 + .../method/updates.getDifference | 225 + .../core.telegram.org/method/updates.getState | 135 + .../method/upload.getCdnFile | 162 + .../method/upload.getCdnFileHashes | 178 + data/core.telegram.org/method/upload.getFile | 252 + .../method/upload.getFileHashes | 171 + .../method/upload.getWebFile | 176 + .../method/upload.reuploadCdnFile | 173 + .../method/upload.saveBigFilePart | 208 + .../method/upload.saveFilePart | 183 + .../method/users.getFullUser | 177 + data/core.telegram.org/method/users.getUsers | 191 + .../method/users.setSecureValueErrors | 176 + data/core.telegram.org/methods.html | 2306 ++++ data/core.telegram.org/mtproto.html | 260 + .../mtproto/TL-abstract-types.html | 202 + .../mtproto/TL-combinators.html | 251 + .../mtproto/TL-dependent.html | 236 + data/core.telegram.org/mtproto/TL-formal.html | 319 + .../core.telegram.org/mtproto/TL-optargs.html | 151 + .../mtproto/TL-patterns.html | 129 + .../mtproto/TL-polymorph.html | 170 + data/core.telegram.org/mtproto/TL-tl.html | 308 + data/core.telegram.org/mtproto/TL-types.html | 124 + data/core.telegram.org/mtproto/TL.html | 210 + data/core.telegram.org/mtproto/auth_key.html | 262 + .../mtproto/description.html | 238 + .../mtproto/description_v1.html | 205 + .../mtproto/mtproto-transports.html | 280 + .../mtproto/samples-auth_key.html | 748 ++ .../mtproto/security_guidelines.html | 177 + .../mtproto/security_guidelines_v1.html | 175 + data/core.telegram.org/mtproto/serialize.html | 240 + .../mtproto/service_messages.html | 195 + .../service_messages_about_messages.html | 185 + data/core.telegram.org/mtproto_v1.html | 229 + data/core.telegram.org/passport.html | 690 ++ .../passport/encryption.html | 606 ++ data/core.telegram.org/passport/example.html | 585 + .../passport/sdk-android.html | 180 + .../passport/sdk-ios-mac.html | 246 + .../passport/sdk-javascript.html | 258 + .../reproducible-builds.html | 488 + data/core.telegram.org/schema.html | 1800 ++++ .../schema/end-to-end-json.html | 1 + data/core.telegram.org/schema/end-to-end.html | 225 + data/core.telegram.org/schema/json.html | 1 + data/core.telegram.org/schema/mtproto.html | 204 + data/core.telegram.org/stickers.html | 249 + .../stickers/webm-vp9-encoding.html | 159 + data/core.telegram.org/tdlib.html | 147 + .../tdlib/getting-started.html | 198 + .../tdlib/notification-api.html | 210 + data/core.telegram.org/tdlib/options.html | 501 + data/core.telegram.org/techfaq.html | 333 + data/core.telegram.org/themes.html | 143 + .../type/AccountDaysTTL.html | 162 + data/core.telegram.org/type/Audio.html | 128 + .../core.telegram.org/type/Authorization.html | 162 + .../type/AutoDownloadSettings.html | 143 + .../type/BankCardOpenUrl.html | 143 + data/core.telegram.org/type/BaseTheme.html | 163 + data/core.telegram.org/type/Bool.html | 718 ++ data/core.telegram.org/type/BotCommand.html | 143 + .../type/BotCommandScope.html | 176 + data/core.telegram.org/type/BotInfo.html | 143 + .../type/BotInlineMessage.html | 168 + .../type/BotInlineResult.html | 148 + data/core.telegram.org/type/CdnConfig.html | 164 + data/core.telegram.org/type/CdnPublicKey.html | 145 + .../type/ChannelAdminLogEventsFilter.html | 143 + .../type/ChannelLocation.html | 148 + .../type/ChannelMessagesFilter.html | 148 + .../type/ChannelParticipant.html | 168 + .../type/ChannelParticipantsFilter.html | 178 + data/core.telegram.org/type/Chat.html | 163 + .../type/ChatAdminRights.html | 146 + .../type/ChatAdminWithInvites.html | 143 + .../type/ChatBannedRights.html | 146 + data/core.telegram.org/type/ChatFull.html | 148 + data/core.telegram.org/type/ChatInvite.html | 172 + .../type/ChatInviteImporter.html | 143 + data/core.telegram.org/type/ChatOnlines.html | 162 + .../type/ChatParticipant.html | 153 + .../type/ChatParticipants.html | 148 + data/core.telegram.org/type/ChatPhoto.html | 148 + data/core.telegram.org/type/ChatTheme.html | 143 + data/core.telegram.org/type/CodeSettings.html | 143 + data/core.telegram.org/type/Config.html | 162 + data/core.telegram.org/type/Contact.html | 143 + .../core.telegram.org/type/ContactStatus.html | 143 + data/core.telegram.org/type/DataJSON.html | 168 + data/core.telegram.org/type/DcOption.html | 143 + .../type/DecryptedDataBlock.html | 128 + .../type/DecryptedMessage.html | 140 + .../type/DecryptedMessageAction.html | 145 + .../type/DecryptedMessageLayer.html | 129 + .../type/DecryptedMessageMedia.html | 149 + data/core.telegram.org/type/Dialog.html | 148 + data/core.telegram.org/type/DialogFilter.html | 143 + .../type/DialogFilterSuggested.html | 143 + .../type/DisabledFeature.html | 128 + data/core.telegram.org/type/Document.html | 173 + .../type/DocumentAttribute.html | 173 + data/core.telegram.org/type/DraftMessage.html | 151 + data/core.telegram.org/type/EmojiKeyword.html | 148 + .../type/EmojiKeywordsDifference.html | 167 + .../core.telegram.org/type/EmojiLanguage.html | 143 + data/core.telegram.org/type/EmojiURL.html | 162 + .../core.telegram.org/type/EncryptedChat.html | 187 + .../core.telegram.org/type/EncryptedFile.html | 167 + .../type/EncryptedMessage.html | 148 + data/core.telegram.org/type/Error.html | 143 + .../type/ExportedChatInvite.html | 162 + .../type/ExportedMessageLink.html | 162 + data/core.telegram.org/type/FileHash.html | 143 + data/core.telegram.org/type/FileLocation.html | 128 + data/core.telegram.org/type/Folder.html | 143 + data/core.telegram.org/type/FolderPeer.html | 143 + data/core.telegram.org/type/Game.html | 143 + data/core.telegram.org/type/GeoPoint.html | 148 + .../type/GlobalPrivacySettings.html | 167 + data/core.telegram.org/type/GroupCall.html | 148 + .../type/GroupCallParticipant.html | 143 + .../type/GroupCallParticipantVideo.html | 143 + .../GroupCallParticipantVideoSourceGroup.html | 143 + data/core.telegram.org/type/HighScore.html | 143 + .../type/ImportedContact.html | 143 + .../type/InlineQueryPeerType.html | 163 + .../core.telegram.org/type/InputAppEvent.html | 143 + .../type/InputBotInlineMessage.html | 173 + .../type/InputBotInlineMessageID.html | 148 + .../type/InputBotInlineResult.html | 158 + data/core.telegram.org/type/InputChannel.html | 153 + .../type/InputChatPhoto.html | 153 + .../type/InputCheckPasswordSRP.html | 151 + .../type/InputClientProxy.html | 145 + data/core.telegram.org/type/InputContact.html | 143 + .../type/InputDialogPeer.html | 148 + .../core.telegram.org/type/InputDocument.html | 148 + .../type/InputEncryptedChat.html | 143 + .../type/InputEncryptedFile.html | 158 + data/core.telegram.org/type/InputFile.html | 148 + .../type/InputFileLocation.html | 188 + .../type/InputFolderPeer.html | 143 + data/core.telegram.org/type/InputGame.html | 148 + .../core.telegram.org/type/InputGeoPoint.html | 148 + .../type/InputGroupCall.html | 143 + data/core.telegram.org/type/InputMedia.html | 213 + data/core.telegram.org/type/InputMessage.html | 158 + .../type/InputNotifyPeer.html | 158 + .../type/InputPaymentCredentials.html | 158 + data/core.telegram.org/type/InputPeer.html | 173 + .../type/InputPeerNotifySettings.html | 143 + .../type/InputPhoneCall.html | 143 + data/core.telegram.org/type/InputPhoto.html | 148 + .../type/InputPrivacyKey.html | 178 + .../type/InputPrivacyRule.html | 178 + .../type/InputSecureFile.html | 151 + .../type/InputSecureValue.html | 145 + .../type/InputSingleMedia.html | 148 + .../type/InputStickerSet.html | 168 + .../type/InputStickerSetItem.html | 143 + .../type/InputStickeredMedia.html | 148 + data/core.telegram.org/type/InputTheme.html | 148 + .../type/InputThemeSettings.html | 143 + data/core.telegram.org/type/InputUser.html | 158 + .../type/InputWallPaper.html | 153 + .../type/InputWebDocument.html | 143 + .../type/InputWebFileLocation.html | 148 + data/core.telegram.org/type/Invoice.html | 143 + .../type/JSONObjectValue.html | 143 + data/core.telegram.org/type/JSONValue.html | 187 + .../type/KeyboardButton.html | 193 + .../type/KeyboardButtonRow.html | 143 + data/core.telegram.org/type/LabeledPrice.html | 143 + .../type/LangPackDifference.html | 167 + .../type/LangPackLanguage.html | 162 + .../type/LangPackString.html | 153 + data/core.telegram.org/type/MaskCoords.html | 143 + data/core.telegram.org/type/Message.html | 153 + .../core.telegram.org/type/MessageAction.html | 283 + .../core.telegram.org/type/MessageEntity.html | 233 + .../type/MessageFwdHeader.html | 143 + .../type/MessageInteractionCounters.html | 143 + data/core.telegram.org/type/MessageMedia.html | 232 + data/core.telegram.org/type/MessageRange.html | 143 + .../type/MessageReactionsList.html | 128 + .../type/MessageReplies.html | 146 + .../type/MessageUserVote.html | 153 + data/core.telegram.org/type/MessageViews.html | 143 + .../type/MessagesFilter.html | 223 + data/core.telegram.org/type/NearestDc.html | 162 + data/core.telegram.org/type/NotifyPeer.html | 158 + data/core.telegram.org/type/Null.html | 143 + data/core.telegram.org/type/Page.html | 143 + data/core.telegram.org/type/PageBlock.html | 283 + data/core.telegram.org/type/PageCaption.html | 143 + data/core.telegram.org/type/PageListItem.html | 148 + .../type/PageListOrderedItem.html | 148 + .../type/PageRelatedArticle.html | 143 + .../core.telegram.org/type/PageTableCell.html | 143 + data/core.telegram.org/type/PageTableRow.html | 143 + .../type/PasswordKdfAlgo.html | 151 + .../core.telegram.org/type/PaymentCharge.html | 143 + .../type/PaymentRequestedInfo.html | 143 + .../type/PaymentSavedCredentials.html | 143 + data/core.telegram.org/type/Peer.html | 153 + data/core.telegram.org/type/PeerBlocked.html | 143 + data/core.telegram.org/type/PeerLocated.html | 148 + .../type/PeerNotifySettings.html | 162 + data/core.telegram.org/type/PeerSettings.html | 162 + data/core.telegram.org/type/PhoneCall.html | 168 + .../type/PhoneCallDiscardReason.html | 158 + .../type/PhoneCallProtocol.html | 143 + .../type/PhoneConnection.html | 148 + data/core.telegram.org/type/Photo.html | 148 + data/core.telegram.org/type/PhotoSize.html | 168 + data/core.telegram.org/type/Poll.html | 143 + data/core.telegram.org/type/PollAnswer.html | 146 + .../type/PollAnswerVoters.html | 143 + data/core.telegram.org/type/PollResults.html | 143 + .../type/PopularContact.html | 143 + data/core.telegram.org/type/PostAddress.html | 143 + data/core.telegram.org/type/PrivacyKey.html | 178 + data/core.telegram.org/type/PrivacyRule.html | 178 + .../type/ReceivedNotifyMessage.html | 143 + data/core.telegram.org/type/RecentMeUrl.html | 163 + data/core.telegram.org/type/ReplyMarkup.html | 158 + data/core.telegram.org/type/ReportReason.html | 178 + .../type/RestrictionReason.html | 143 + data/core.telegram.org/type/RichText.html | 218 + data/core.telegram.org/type/SavedContact.html | 143 + .../type/SecureCredentialsEncrypted.html | 143 + data/core.telegram.org/type/SecureData.html | 146 + data/core.telegram.org/type/SecureFile.html | 151 + .../type/SecurePlainData.html | 150 + .../type/SecureRequiredType.html | 148 + .../type/SecureSecretSettings.html | 145 + data/core.telegram.org/type/SecureValue.html | 162 + .../type/SecureValueError.html | 183 + .../type/SecureValueHash.html | 143 + .../type/SecureValueType.html | 203 + .../type/SendMessageAction.html | 228 + .../type/ShippingOption.html | 143 + .../type/SponsoredMessage.html | 143 + .../type/StatsAbsValueAndPrev.html | 143 + .../type/StatsDateRangeDays.html | 143 + data/core.telegram.org/type/StatsGraph.html | 172 + .../type/StatsGroupTopAdmin.html | 146 + .../type/StatsGroupTopInviter.html | 146 + .../type/StatsGroupTopPoster.html | 146 + .../type/StatsPercentValue.html | 143 + data/core.telegram.org/type/StatsURL.html | 143 + data/core.telegram.org/type/StickerSet.html | 143 + .../type/StickerSetCovered.html | 148 + data/core.telegram.org/type/Theme.html | 172 + .../core.telegram.org/type/ThemeSettings.html | 143 + data/core.telegram.org/type/TopPeer.html | 143 + .../type/TopPeerCategory.html | 178 + .../type/TopPeerCategoryPeers.html | 143 + data/core.telegram.org/type/True.html | 145 + data/core.telegram.org/type/Update.html | 603 ++ data/core.telegram.org/type/Updates.html | 508 + .../core.telegram.org/type/UrlAuthResult.html | 177 + data/core.telegram.org/type/User.html | 177 + data/core.telegram.org/type/UserFull.html | 162 + .../type/UserProfilePhoto.html | 148 + data/core.telegram.org/type/UserStatus.html | 168 + data/core.telegram.org/type/Vector t.html | 143 + data/core.telegram.org/type/Video.html | 128 + data/core.telegram.org/type/VideoSize.html | 143 + data/core.telegram.org/type/WallPaper.html | 172 + .../type/WallPaperSettings.html | 143 + .../type/WebAuthorization.html | 143 + data/core.telegram.org/type/WebDocument.html | 148 + data/core.telegram.org/type/WebPage.html | 177 + .../type/WebPageAttribute.html | 143 + .../type/account.AuthorizationForm | 162 + .../type/account.Authorizations | 162 + .../type/account.AutoDownloadSettings | 162 + .../core.telegram.org/type/account.ChatThemes | 167 + .../type/account.ContentSettings | 162 + data/core.telegram.org/type/account.Password | 162 + .../type/account.PasswordInputSettings | 146 + .../type/account.PasswordSettings | 164 + .../type/account.PrivacyRules | 167 + .../type/account.ResetPasswordResult | 175 + .../type/account.SentChangePhoneCode | 128 + .../type/account.SentEmailCode | 162 + data/core.telegram.org/type/account.Takeout | 162 + data/core.telegram.org/type/account.Themes | 167 + .../type/account.TmpPassword | 162 + .../core.telegram.org/type/account.WallPapers | 167 + .../type/account.WebAuthorizations | 162 + .../core.telegram.org/type/auth.Authorization | 192 + data/core.telegram.org/type/auth.CheckedPhone | 128 + data/core.telegram.org/type/auth.CodeType | 153 + .../type/auth.ExportedAuthorization | 162 + data/core.telegram.org/type/auth.LoginToken | 177 + .../type/auth.PasswordRecovery | 165 + data/core.telegram.org/type/auth.SentCode | 183 + data/core.telegram.org/type/auth.SentCodeType | 158 + data/core.telegram.org/type/bytes.html | 125 + .../type/channels.AdminLogResults | 162 + .../type/channels.ChannelParticipant | 162 + .../type/channels.ChannelParticipants | 167 + data/core.telegram.org/type/contacts.Blocked | 167 + data/core.telegram.org/type/contacts.Contacts | 167 + data/core.telegram.org/type/contacts.Found | 162 + .../type/contacts.ImportedContacts | 162 + data/core.telegram.org/type/contacts.Link | 128 + .../type/contacts.ResolvedPeer | 162 + data/core.telegram.org/type/contacts.TopPeers | 172 + data/core.telegram.org/type/double.html | 118 + data/core.telegram.org/type/help.AppUpdate | 167 + .../core.telegram.org/type/help.CountriesList | 167 + data/core.telegram.org/type/help.Country | 143 + data/core.telegram.org/type/help.CountryCode | 143 + data/core.telegram.org/type/help.DeepLinkInfo | 167 + data/core.telegram.org/type/help.InviteText | 162 + .../type/help.PassportConfig | 169 + data/core.telegram.org/type/help.PromoData | 167 + data/core.telegram.org/type/help.ProxyData | 130 + data/core.telegram.org/type/help.RecentMeUrls | 162 + data/core.telegram.org/type/help.Support | 162 + data/core.telegram.org/type/help.SupportName | 162 + .../type/help.TermsOfService | 143 + .../type/help.TermsOfServiceUpdate | 167 + data/core.telegram.org/type/help.UserInfo | 172 + data/core.telegram.org/type/int.html | 118 + data/core.telegram.org/type/long.html | 118 + .../type/messages.AffectedFoundMessages | 162 + .../type/messages.AffectedHistory | 178 + .../type/messages.AffectedMessages | 178 + .../type/messages.AllStickers | 172 + .../type/messages.ArchivedStickers | 162 + .../type/messages.BotCallbackAnswer | 162 + .../type/messages.BotResults | 162 + .../type/messages.ChatAdminsWithInvites | 162 + .../type/messages.ChatInviteImporters | 162 + data/core.telegram.org/type/messages.Chats | 198 + .../type/messages.CheckedHistoryImportPeer | 165 + data/core.telegram.org/type/messages.DhConfig | 167 + data/core.telegram.org/type/messages.Dialogs | 172 + .../type/messages.DiscussionMessage | 162 + .../type/messages.ExportedChatInvite | 172 + .../type/messages.ExportedChatInvites | 162 + .../type/messages.FavedStickers | 167 + .../type/messages.FeaturedStickers | 172 + .../core.telegram.org/type/messages.FoundGifs | 128 + .../type/messages.FoundStickerSets | 167 + .../type/messages.HighScores | 167 + .../type/messages.HistoryImport | 165 + .../type/messages.HistoryImportParsed | 162 + .../type/messages.InactiveChats | 162 + .../type/messages.MessageEditData | 162 + .../type/messages.MessageViews | 162 + data/core.telegram.org/type/messages.Messages | 229 + .../type/messages.PeerDialogs | 167 + .../type/messages.RecentStickers | 167 + .../type/messages.SearchCounter | 143 + .../type/messages.SentEncryptedMessage | 177 + .../type/messages.SentMessage | 128 + .../type/messages.SponsoredMessages | 166 + .../type/messages.StatedMessage | 128 + .../type/messages.StatedMessages | 128 + .../type/messages.StickerSet | 188 + .../type/messages.StickerSetInstallResult | 167 + data/core.telegram.org/type/messages.Stickers | 167 + .../core.telegram.org/type/messages.VotesList | 162 + .../type/payments.BankCardData | 162 + .../type/payments.PaymentForm | 162 + .../type/payments.PaymentReceipt | 162 + .../type/payments.PaymentResult | 167 + .../core.telegram.org/type/payments.SavedInfo | 162 + .../type/payments.ValidatedRequestedInfo | 162 + .../type/phone.ExportedGroupCallInvite | 162 + data/core.telegram.org/type/phone.GroupCall | 162 + .../type/phone.GroupParticipants | 162 + data/core.telegram.org/type/phone.JoinAsPeers | 162 + data/core.telegram.org/type/phone.PhoneCall | 172 + data/core.telegram.org/type/photos.Photo | 167 + data/core.telegram.org/type/photos.Photos | 167 + .../type/stats.BroadcastStats | 162 + .../type/stats.MegagroupStats | 162 + .../core.telegram.org/type/stats.MessageStats | 162 + .../type/stickers.SuggestedShortName | 162 + data/core.telegram.org/type/storage.FileType | 188 + data/core.telegram.org/type/string.html | 126 + .../type/updates.ChannelDifference | 172 + .../core.telegram.org/type/updates.Difference | 177 + data/core.telegram.org/type/updates.State | 162 + data/core.telegram.org/type/upload.CdnFile | 167 + data/core.telegram.org/type/upload.File | 167 + data/core.telegram.org/type/upload.WebFile | 162 + data/core.telegram.org/video_stickers.html | 115 + data/core.telegram.org/widgets.html | 141 + .../core.telegram.org/widgets/discussion.html | 226 + data/core.telegram.org/widgets/login.html | 404 + data/core.telegram.org/widgets/post.html | 240 + data/core.telegram.org/widgets/share.html | 250 + data/corefork.telegram.org.html | 253 + data/corefork.telegram.org/api.html | 253 + .../api/account-deletion.html | 129 + .../api/animated-emojis.html | 187 + data/corefork.telegram.org/api/auth.html | 202 + data/corefork.telegram.org/api/bots.html | 142 + .../api/bots/buttons.html | 242 + .../api/bots/commands.html | 140 + .../corefork.telegram.org/api/bots/games.html | 171 + .../api/bots/inline.html | 215 + data/corefork.telegram.org/api/channel.html | 154 + data/corefork.telegram.org/api/config.html | 422 + .../corefork.telegram.org/api/datacenter.html | 148 + data/corefork.telegram.org/api/dice.html | 149 + .../corefork.telegram.org/api/discussion.html | 151 + data/corefork.telegram.org/api/drafts.html | 131 + .../corefork.telegram.org/api/end-to-end.html | 244 + .../api/end-to-end/pfs.html | 176 + .../api/end-to-end/seq_no.html | 173 + .../api/end-to-end/video-calls.html | 215 + .../api/end-to-end/voice-calls.html | 178 + .../api/end-to-end_v1.html | 225 + data/corefork.telegram.org/api/entities.html | 137 + data/corefork.telegram.org/api/errors.html | 189 + .../api/file_reference.html | 125 + data/corefork.telegram.org/api/files.html | 568 + data/corefork.telegram.org/api/geochats.html | 115 + data/corefork.telegram.org/api/import.html | 173 + data/corefork.telegram.org/api/invoking.html | 154 + data/corefork.telegram.org/api/layers.html | 2499 +++++ .../api/live-location.html | 178 + data/corefork.telegram.org/api/mentions.html | 152 + data/corefork.telegram.org/api/min.html | 142 + .../api/obtaining_api_id.html | 140 + data/corefork.telegram.org/api/offsets.html | 170 + .../api/optimisation.html | 150 + data/corefork.telegram.org/api/passport.html | 674 ++ data/corefork.telegram.org/api/pattern.html | 122 + data/corefork.telegram.org/api/payments.html | 366 + data/corefork.telegram.org/api/pfs.html | 138 + data/corefork.telegram.org/api/pin.html | 149 + data/corefork.telegram.org/api/poll.html | 199 + .../api/push-updates.html | 1009 ++ data/corefork.telegram.org/api/qr-login.html | 154 + .../api/recent-actions.html | 154 + data/corefork.telegram.org/api/rights.html | 133 + .../api/scheduled-messages.html | 156 + data/corefork.telegram.org/api/search.html | 179 + .../api/sponsored-messages.html | 146 + data/corefork.telegram.org/api/srp.html | 307 + data/corefork.telegram.org/api/stats.html | 297 + data/corefork.telegram.org/api/terms.html | 133 + data/corefork.telegram.org/api/threads.html | 182 + .../corefork.telegram.org/api/top-rating.html | 145 + data/corefork.telegram.org/api/updates.html | 226 + .../api/url-authorization.html | 160 + .../corefork.telegram.org/api/web-events.html | 175 + ...hemes-interactive-emoji-read-receipts.html | 115 + data/corefork.telegram.org/bots.html | 420 + .../corefork.telegram.org/bots/2-0-intro.html | 230 + .../bots/api-changelog.html | 670 ++ data/corefork.telegram.org/bots/api.html | 9288 ++++++++++++++++ data/corefork.telegram.org/bots/faq.html | 243 + data/corefork.telegram.org/bots/games.html | 185 + data/corefork.telegram.org/bots/inline.html | 181 + data/corefork.telegram.org/bots/samples.html | 249 + .../bots/samples/hellobot.html | 287 + .../bots/self-signed.html | 161 + data/corefork.telegram.org/bots/webhooks.html | 827 ++ data/corefork.telegram.org/cdn.html | 210 + .../constructor/account.authorizationForm | 174 + .../constructor/account.authorizations | 147 + .../constructor/account.autoDownloadSettings | 157 + .../constructor/account.chatThemes | 155 + .../constructor/account.chatThemesNotModified | 132 + .../constructor/account.contentSettings | 157 + .../constructor/account.password | 213 + .../constructor/account.passwordInputSettings | 176 + .../constructor/account.passwordSettings | 161 + .../constructor/account.privacyRules | 157 + .../account.resetPasswordFailedWait | 147 + .../constructor/account.resetPasswordOk | 132 + .../account.resetPasswordRequestedWait | 147 + .../constructor/account.sentChangePhoneCode | 161 + .../constructor/account.sentEmailCode | 155 + .../constructor/account.takeout | 147 + .../constructor/account.themes | 155 + .../constructor/account.themesNotModified | 132 + .../constructor/account.tmpPassword | 152 + .../constructor/account.wallPapers | 155 + .../constructor/account.wallPapersNotModified | 132 + .../constructor/account.webAuthorizations | 152 + .../constructor/accountDaysTTL.html | 147 + .../constructor/auth.authorization | 159 + .../auth.authorizationSignUpRequired | 155 + .../constructor/auth.codeTypeCall | 132 + .../constructor/auth.codeTypeFlashCall | 132 + .../constructor/auth.codeTypeMissedCall | 115 + .../constructor/auth.codeTypeSms | 132 + .../constructor/auth.exportedAuthorization | 152 + .../constructor/auth.loggedOut | 115 + .../constructor/auth.loginToken | 155 + .../constructor/auth.loginTokenMigrateTo | 152 + .../constructor/auth.loginTokenSuccess | 147 + .../constructor/auth.passwordRecovery | 152 + .../constructor/auth.sentAppCode | 163 + .../constructor/auth.sentCode | 172 + .../constructor/auth.sentCodeTypeApp | 147 + .../constructor/auth.sentCodeTypeCall | 147 + .../constructor/auth.sentCodeTypeFlashCall | 150 + .../constructor/auth.sentCodeTypeMissedCall | 115 + .../constructor/auth.sentCodeTypeSms | 147 + .../constructor/authorization.html | 225 + .../constructor/autoDownloadSettings.html | 187 + .../constructor/availableReaction.html | 115 + .../constructor/bankCardOpenUrl.html | 152 + .../constructor/baseThemeArctic.html | 132 + .../constructor/baseThemeClassic.html | 132 + .../constructor/baseThemeDay.html | 132 + .../constructor/baseThemeNight.html | 132 + .../constructor/baseThemeTinted.html | 132 + .../constructor/boolFalse.html | 132 + .../constructor/boolTrue.html | 132 + .../constructor/botCommand.html | 152 + .../botCommandScopeChatAdmins.html | 135 + .../constructor/botCommandScopeChats.html | 135 + .../constructor/botCommandScopeDefault.html | 132 + .../constructor/botCommandScopePeer.html | 147 + .../constructor/botCommandScopePeerUser.html | 155 + .../constructor/botCommandScopeUsers.html | 132 + .../constructor/botInfo.html | 157 + .../constructor/botInlineMediaResult.html | 186 + .../botInlineMessageMediaAuto.html | 167 + .../botInlineMessageMediaContact.html | 172 + .../constructor/botInlineMessageMediaGeo.html | 175 + .../botInlineMessageMediaInvoice.html | 189 + .../botInlineMessageMediaVenue.html | 182 + .../constructor/botInlineMessageText.html | 170 + .../constructor/botInlineResult.html | 189 + .../constructor/cdnConfig.html | 149 + .../constructor/cdnPublicKey.html | 154 + .../constructor/channel.html | 289 + .../constructor/channelAdminLogEvent.html | 162 + ...channelAdminLogEventActionChangeAbout.html | 152 + ...ogEventActionChangeAvailableReactions.html | 115 + ...elAdminLogEventActionChangeHistoryTTL.html | 152 + ...elAdminLogEventActionChangeLinkedChat.html | 152 + ...nnelAdminLogEventActionChangeLocation.html | 152 + ...channelAdminLogEventActionChangePhoto.html | 152 + ...elAdminLogEventActionChangeStickerSet.html | 152 + ...channelAdminLogEventActionChangeTitle.html | 152 + ...nnelAdminLogEventActionChangeUsername.html | 152 + ...dminLogEventActionDefaultBannedRights.html | 155 + ...annelAdminLogEventActionDeleteMessage.html | 147 + ...elAdminLogEventActionDiscardGroupCall.html | 147 + ...channelAdminLogEventActionEditMessage.html | 152 + ...minLogEventActionExportedInviteDelete.html | 147 + ...AdminLogEventActionExportedInviteEdit.html | 152 + ...minLogEventActionExportedInviteRevoke.html | 147 + ...lAdminLogEventActionParticipantInvite.html | 147 + ...nelAdminLogEventActionParticipantJoin.html | 132 + ...LogEventActionParticipantJoinByInvite.html | 150 + ...ogEventActionParticipantJoinByRequest.html | 115 + ...elAdminLogEventActionParticipantLeave.html | 132 + ...nelAdminLogEventActionParticipantMute.html | 147 + ...nLogEventActionParticipantToggleAdmin.html | 155 + ...minLogEventActionParticipantToggleBan.html | 155 + ...lAdminLogEventActionParticipantUnmute.html | 147 + ...lAdminLogEventActionParticipantVolume.html | 147 + ...channelAdminLogEventActionSendMessage.html | 115 + ...nnelAdminLogEventActionStartGroupCall.html | 147 + .../channelAdminLogEventActionStopPoll.html | 147 + ...nLogEventActionToggleGroupCallSetting.html | 147 + ...annelAdminLogEventActionToggleInvites.html | 147 + ...elAdminLogEventActionToggleNoForwards.html | 115 + ...nLogEventActionTogglePreHistoryHidden.html | 150 + ...elAdminLogEventActionToggleSignatures.html | 147 + ...nnelAdminLogEventActionToggleSlowMode.html | 155 + ...hannelAdminLogEventActionUpdatePinned.html | 147 + .../channelAdminLogEventsFilter.html | 266 + .../constructor/channelForbidden.html | 177 + .../constructor/channelFull.html | 363 + .../constructor/channelLocation.html | 152 + .../constructor/channelLocationEmpty.html | 132 + .../constructor/channelMessagesFilter.html | 157 + .../channelMessagesFilterEmpty.html | 132 + .../constructor/channelParticipant.html | 152 + .../constructor/channelParticipantAdmin.html | 190 + .../constructor/channelParticipantBanned.html | 175 + .../channelParticipantCreator.html | 162 + .../constructor/channelParticipantLeft.html | 147 + .../constructor/channelParticipantSelf.html | 157 + .../channelParticipantsAdmins.html | 132 + .../channelParticipantsBanned.html | 147 + .../constructor/channelParticipantsBots.html | 132 + .../channelParticipantsContacts.html | 147 + .../channelParticipantsKicked.html | 147 + .../channelParticipantsMentions.html | 161 + .../channelParticipantsRecent.html | 132 + .../channelParticipantsSearch.html | 147 + .../constructor/channels.adminLogResults | 157 + .../constructor/channels.channelParticipant | 157 + .../constructor/channels.channelParticipants | 162 + .../channels.channelParticipantsNotModified | 132 + .../constructor/channels.sendAsPeers | 115 + .../constructor/chat.html | 227 + .../constructor/chatAdminRights.html | 205 + .../constructor/chatAdminWithInvites.html | 157 + .../constructor/chatBannedRights.html | 216 + .../constructor/chatEmpty.html | 147 + .../constructor/chatForbidden.html | 152 + .../constructor/chatFull.html | 231 + .../constructor/chatInvite.html | 190 + .../constructor/chatInviteAlready.html | 147 + .../constructor/chatInviteExported.html | 192 + .../constructor/chatInviteImporter.html | 152 + .../constructor/chatInvitePeek.html | 152 + .../constructor/chatOnlines.html | 147 + .../constructor/chatParticipant.html | 157 + .../constructor/chatParticipantAdmin.html | 157 + .../constructor/chatParticipantCreator.html | 147 + .../constructor/chatParticipants.html | 157 + .../chatParticipantsForbidden.html | 157 + .../constructor/chatPhoto.html | 170 + .../constructor/chatPhotoEmpty.html | 132 + .../constructor/chatTheme.html | 157 + .../constructor/codeSettings.html | 166 + .../constructor/config.html | 420 + .../constructor/contact.html | 152 + .../constructor/contactStatus.html | 152 + .../constructor/contacts.blocked | 157 + .../constructor/contacts.blockedSlice | 162 + .../constructor/contacts.contacts | 157 + .../constructor/contacts.contactsNotModified | 132 + .../constructor/contacts.found | 162 + .../constructor/contacts.importedContacts | 165 + .../constructor/contacts.resolvedPeer | 157 + .../constructor/contacts.topPeers | 157 + .../constructor/contacts.topPeersDisabled | 132 + .../constructor/contacts.topPeersNotModified | 132 + .../constructor/dataJSON.html | 147 + .../constructor/dcOption.html | 197 + .../constructor/decryptedMessage.html | 217 + .../decryptedMessageActionAbortKey.html | 148 + .../decryptedMessageActionAcceptKey.html | 160 + .../decryptedMessageActionCommitKey.html | 155 + .../decryptedMessageActionDeleteMessages.html | 148 + .../decryptedMessageActionFlushHistory.html | 133 + .../decryptedMessageActionNoop.html | 133 + .../decryptedMessageActionNotifyLayer.html | 151 + .../decryptedMessageActionReadMessages.html | 148 + .../decryptedMessageActionRequestKey.html | 155 + .../decryptedMessageActionResend.html | 155 + ...ryptedMessageActionScreenshotMessages.html | 148 + .../decryptedMessageActionSetMessageTTL.html | 149 + .../decryptedMessageActionTyping.html | 148 + .../constructor/decryptedMessageLayer.html | 173 + .../decryptedMessageMediaAudio.html | 174 + .../decryptedMessageMediaContact.html | 163 + .../decryptedMessageMediaDocument.html | 191 + .../decryptedMessageMediaEmpty.html | 133 + ...decryptedMessageMediaExternalDocument.html | 183 + .../decryptedMessageMediaGeoPoint.html | 153 + .../decryptedMessageMediaPhoto.html | 191 + .../decryptedMessageMediaVenue.html | 173 + .../decryptedMessageMediaVideo.html | 207 + .../decryptedMessageMediaWebPage.html | 148 + .../constructor/decryptedMessageService.html | 156 + .../constructor/dialog.html | 214 + .../constructor/dialogFilter.html | 220 + .../constructor/dialogFilterSuggested.html | 155 + .../constructor/dialogFolder.html | 187 + .../constructor/dialogPeer.html | 147 + .../constructor/dialogPeerFolder.html | 150 + .../constructor/disabledFeature.html | 163 + .../constructor/document.html | 200 + .../documentAttributeAnimated.html | 132 + .../constructor/documentAttributeAudio.html | 172 + .../documentAttributeFilename.html | 147 + .../documentAttributeHasStickers.html | 132 + .../documentAttributeImageSize.html | 152 + .../constructor/documentAttributeSticker.html | 167 + .../constructor/documentAttributeVideo.html | 172 + .../constructor/documentEmpty.html | 147 + .../constructor/draftMessage.html | 177 + .../constructor/draftMessageEmpty.html | 152 + .../constructor/emojiKeyword.html | 152 + .../constructor/emojiKeywordDeleted.html | 152 + .../constructor/emojiKeywordsDifference.html | 162 + .../constructor/emojiLanguage.html | 147 + .../constructor/emojiURL.html | 147 + .../constructor/encryptedChat.html | 177 + .../constructor/encryptedChatDiscarded.html | 157 + .../constructor/encryptedChatEmpty.html | 147 + .../constructor/encryptedChatRequested.html | 185 + .../constructor/encryptedChatWaiting.html | 167 + .../constructor/encryptedFile.html | 167 + .../constructor/encryptedFileEmpty.html | 132 + .../constructor/encryptedMessage.html | 170 + .../constructor/encryptedMessageService.html | 165 + .../constructor/error.html | 152 + .../constructor/exportedMessageLink.html | 152 + .../constructor/fileHash.html | 171 + .../constructor/fileLocation.html | 182 + .../constructor/fileLocationUnavailable.html | 179 + .../constructor/folder.html | 177 + .../constructor/folderPeer.html | 155 + .../constructor/game.html | 182 + .../constructor/geoPoint.html | 167 + .../constructor/geoPointEmpty.html | 132 + .../constructor/globalPrivacySettings.html | 152 + .../constructor/groupCall.html | 230 + .../constructor/groupCallDiscarded.html | 157 + .../constructor/groupCallParticipant.html | 247 + .../groupCallParticipantVideo.html | 167 + .../groupCallParticipantVideoSourceGroup.html | 152 + .../constructor/help.appUpdate | 190 + .../constructor/help.countriesList | 155 + .../constructor/help.countriesListNotModified | 132 + .../constructor/help.country | 172 + .../constructor/help.countryCode | 162 + .../constructor/help.deepLinkInfo | 165 + .../constructor/help.deepLinkInfoEmpty | 132 + .../constructor/help.inviteText | 147 + .../constructor/help.noAppUpdate | 132 + .../constructor/help.passportConfig | 156 + .../help.passportConfigNotModified | 132 + .../constructor/help.promoData | 182 + .../constructor/help.promoDataEmpty | 147 + .../constructor/help.recentMeUrls | 157 + .../constructor/help.support | 152 + .../constructor/help.supportName | 147 + .../constructor/help.termsOfService | 175 + .../constructor/help.termsOfServiceUpdate | 157 + .../help.termsOfServiceUpdateEmpty | 150 + .../constructor/help.userInfo | 165 + .../constructor/help.userInfoEmpty | 132 + .../constructor/highScore.html | 157 + .../constructor/importedContact.html | 155 + .../constructor/inlineBotSwitchPM.html | 152 + .../inlineQueryPeerTypeBroadcast.html | 135 + .../constructor/inlineQueryPeerTypeChat.html | 135 + .../inlineQueryPeerTypeMegagroup.html | 135 + .../constructor/inlineQueryPeerTypePM.html | 132 + .../inlineQueryPeerTypeSameBotPM.html | 132 + .../constructor/inputAppEvent.html | 162 + .../inputBotInlineMessageGame.html | 152 + .../constructor/inputBotInlineMessageID.html | 157 + .../inputBotInlineMessageID64.html | 162 + .../inputBotInlineMessageMediaAuto.html | 165 + .../inputBotInlineMessageMediaContact.html | 172 + .../inputBotInlineMessageMediaGeo.html | 175 + .../inputBotInlineMessageMediaInvoice.html | 187 + .../inputBotInlineMessageMediaVenue.html | 182 + .../inputBotInlineMessageText.html | 170 + .../constructor/inputBotInlineResult.html | 189 + .../inputBotInlineResultDocument.html | 179 + .../inputBotInlineResultPhoto.html | 164 + .../constructor/inputChannel.html | 155 + .../constructor/inputChannelEmpty.html | 132 + .../constructor/inputChannelFromMessage.html | 160 + .../constructor/inputChatPhoto.html | 147 + .../constructor/inputChatPhotoEmpty.html | 132 + .../constructor/inputChatUploadedPhoto.html | 165 + .../constructor/inputCheckPasswordEmpty.html | 132 + .../constructor/inputCheckPasswordSRP.html | 160 + .../constructor/inputClientProxy.html | 154 + .../constructor/inputDialogPeer.html | 147 + .../constructor/inputDialogPeerFolder.html | 150 + .../constructor/inputDocument.html | 162 + .../constructor/inputDocumentEmpty.html | 132 + .../inputDocumentFileLocation.html | 167 + .../constructor/inputEncryptedChat.html | 159 + .../constructor/inputEncryptedFile.html | 155 + .../inputEncryptedFileBigUploaded.html | 160 + .../constructor/inputEncryptedFileEmpty.html | 132 + .../inputEncryptedFileLocation.html | 155 + .../inputEncryptedFileUploaded.html | 162 + .../constructor/inputFile.html | 165 + .../constructor/inputFileLocation.html | 165 + .../constructor/inputFolderPeer.html | 155 + .../constructor/inputGameID.html | 155 + .../constructor/inputGameShortName.html | 152 + .../constructor/inputGeoPoint.html | 162 + .../constructor/inputGeoPointEmpty.html | 132 + .../constructor/inputGroupCall.html | 152 + .../constructor/inputGroupCallStream.html | 172 + .../inputKeyboardButtonUrlAuth.html | 176 + .../inputKeyboardButtonUserProfile.html | 115 + .../constructor/inputMediaContact.html | 162 + .../constructor/inputMediaDice.html | 150 + .../constructor/inputMediaDocument.html | 162 + .../inputMediaDocumentExternal.html | 157 + .../constructor/inputMediaEmpty.html | 132 + .../constructor/inputMediaGame.html | 147 + .../constructor/inputMediaGeoLive.html | 175 + .../constructor/inputMediaGeoPoint.html | 147 + .../constructor/inputMediaInvoice.html | 189 + .../constructor/inputMediaPhoto.html | 157 + .../constructor/inputMediaPhotoExternal.html | 157 + .../constructor/inputMediaPoll.html | 170 + .../inputMediaUploadedDocument.html | 190 + .../constructor/inputMediaUploadedPhoto.html | 165 + .../inputMediaUploadedThumbDocument.html | 176 + .../constructor/inputMediaVenue.html | 172 + .../inputMessageCallbackQuery.html | 152 + .../inputMessageEntityMentionName.html | 162 + .../constructor/inputMessageID.html | 147 + .../constructor/inputMessagePinned.html | 132 + .../constructor/inputMessageReplyTo.html | 147 + .../inputMessagesFilterChatPhotos.html | 132 + .../inputMessagesFilterContacts.html | 132 + .../inputMessagesFilterDocument.html | 132 + .../constructor/inputMessagesFilterEmpty.html | 132 + .../constructor/inputMessagesFilterGeo.html | 132 + .../constructor/inputMessagesFilterGif.html | 132 + .../constructor/inputMessagesFilterMusic.html | 132 + .../inputMessagesFilterMyMentions.html | 135 + .../inputMessagesFilterPhoneCalls.html | 152 + .../inputMessagesFilterPhotoVideo.html | 132 + .../inputMessagesFilterPhotos.html | 132 + .../inputMessagesFilterPinned.html | 132 + .../inputMessagesFilterRoundVideo.html | 132 + .../inputMessagesFilterRoundVoice.html | 132 + .../constructor/inputMessagesFilterUrl.html | 132 + .../constructor/inputMessagesFilterVideo.html | 132 + .../constructor/inputMessagesFilterVoice.html | 132 + .../constructor/inputNotifyBroadcasts.html | 135 + .../constructor/inputNotifyChats.html | 132 + .../constructor/inputNotifyPeer.html | 147 + .../constructor/inputNotifyUsers.html | 132 + .../constructor/inputPaymentCredentials.html | 157 + .../inputPaymentCredentialsApplePay.html | 147 + .../inputPaymentCredentialsGooglePay.html | 147 + .../inputPaymentCredentialsSaved.html | 152 + .../inputPeerChannelFromMessage.html | 160 + .../constructor/inputPeerChat.html | 147 + .../constructor/inputPeerNotifySettings.html | 167 + .../inputPeerPhotoFileLocation.html | 162 + .../constructor/inputPeerSelf.html | 132 + .../constructor/inputPeerUser.html | 155 + .../constructor/inputPeerUserFromMessage.html | 160 + .../constructor/inputPhoneCall.html | 152 + .../constructor/inputPhoneContact.html | 166 + .../constructor/inputPhoto.html | 162 + .../constructor/inputPhotoEmpty.html | 132 + .../constructor/inputPhotoFileLocation.html | 171 + .../inputPhotoLegacyFileLocation.html | 172 + .../inputPrivacyKeyAddedByPhone.html | 132 + .../inputPrivacyKeyChatInvite.html | 132 + .../constructor/inputPrivacyKeyForwards.html | 132 + .../constructor/inputPrivacyKeyPhoneCall.html | 132 + .../inputPrivacyKeyPhoneNumber.html | 132 + .../constructor/inputPrivacyKeyPhoneP2P.html | 132 + .../inputPrivacyKeyProfilePhoto.html | 132 + .../inputPrivacyKeyStatusTimestamp.html | 132 + .../inputPrivacyValueAllowAll.html | 132 + ...nputPrivacyValueAllowChatParticipants.html | 147 + .../inputPrivacyValueAllowContacts.html | 132 + .../inputPrivacyValueAllowUsers.html | 147 + .../inputPrivacyValueDisallowAll.html | 132 + ...tPrivacyValueDisallowChatParticipants.html | 147 + .../inputPrivacyValueDisallowContacts.html | 132 + .../inputPrivacyValueDisallowUsers.html | 147 + .../inputReportReasonChildAbuse.html | 132 + .../inputReportReasonCopyright.html | 132 + .../constructor/inputReportReasonFake.html | 132 + .../inputReportReasonGeoIrrelevant.html | 132 + .../constructor/inputReportReasonOther.html | 132 + .../inputReportReasonPornography.html | 132 + .../constructor/inputReportReasonSpam.html | 132 + .../inputReportReasonViolence.html | 132 + .../constructor/inputSecureFile.html | 155 + .../constructor/inputSecureFileLocation.html | 156 + .../constructor/inputSecureFileUploaded.html | 169 + .../constructor/inputSecureValue.html | 190 + .../constructor/inputSingleMedia.html | 174 + .../inputStickerSetAnimatedEmoji.html | 132 + ...nputStickerSetAnimatedEmojiAnimations.html | 132 + .../constructor/inputStickerSetEmpty.html | 132 + .../constructor/inputStickerSetID.html | 152 + .../constructor/inputStickerSetItem.html | 162 + .../constructor/inputStickerSetShortName.html | 147 + .../constructor/inputStickerSetThumb.html | 155 + .../inputStickeredMediaDocument.html | 147 + .../constructor/inputStickeredMediaPhoto.html | 147 + .../constructor/inputTakeoutFileLocation.html | 132 + .../constructor/inputTheme.html | 152 + .../constructor/inputThemeSettings.html | 182 + .../constructor/inputThemeSlug.html | 147 + .../constructor/inputUser.html | 155 + .../constructor/inputUserEmpty.html | 132 + .../constructor/inputUserFromMessage.html | 160 + .../constructor/inputWallPaper.html | 152 + .../constructor/inputWallPaperNoFile.html | 150 + .../constructor/inputWallPaperSlug.html | 147 + .../constructor/inputWebDocument.html | 165 + .../inputWebFileGeoPointLocation.html | 172 + .../constructor/inputWebFileLocation.html | 152 + .../constructor/invoice.html | 209 + .../constructor/jsonArray.html | 147 + .../constructor/jsonNull.html | 132 + .../constructor/jsonNumber.html | 147 + .../constructor/jsonObject.html | 147 + .../constructor/jsonObjectValue.html | 152 + .../constructor/jsonString.html | 147 + .../constructor/keyboardButton.html | 147 + .../constructor/keyboardButtonBuy.html | 147 + .../constructor/keyboardButtonCallback.html | 167 + .../constructor/keyboardButtonGame.html | 147 + .../keyboardButtonRequestGeoLocation.html | 147 + .../keyboardButtonRequestPhone.html | 147 + .../keyboardButtonRequestPoll.html | 157 + .../constructor/keyboardButtonRow.html | 147 + .../keyboardButtonSwitchInline.html | 162 + .../constructor/keyboardButtonUrl.html | 152 + .../constructor/keyboardButtonUrlAuth.html | 179 + .../keyboardButtonUserProfile.html | 115 + .../constructor/labeledPrice.html | 154 + .../constructor/langPackDifference.html | 162 + .../constructor/langPackLanguage.html | 202 + .../constructor/langPackString.html | 152 + .../constructor/langPackStringDeleted.html | 147 + .../constructor/langPackStringPluralized.html | 182 + .../constructor/maskCoords.html | 169 + .../constructor/message.html | 302 + .../constructor/messageActionBotAllowed.html | 149 + .../messageActionChannelCreate.html | 147 + .../messageActionChannelMigrateFrom.html | 155 + .../constructor/messageActionChatAddUser.html | 147 + .../constructor/messageActionChatCreate.html | 152 + .../messageActionChatDeletePhoto.html | 132 + .../messageActionChatDeleteUser.html | 147 + .../messageActionChatEditPhoto.html | 147 + .../messageActionChatEditTitle.html | 147 + .../messageActionChatJoinedByLink.html | 147 + .../messageActionChatJoinedByRequest.html | 115 + .../messageActionChatMigrateTo.html | 150 + .../messageActionContactSignUp.html | 132 + .../messageActionCustomAction.html | 147 + .../constructor/messageActionGameScore.html | 152 + .../messageActionGeoProximityReached.html | 160 + .../constructor/messageActionGroupCall.html | 157 + .../messageActionGroupCallScheduled.html | 152 + .../messageActionHistoryClear.html | 132 + .../messageActionInviteToGroupCall.html | 152 + .../constructor/messageActionPaymentSent.html | 154 + .../messageActionPaymentSentMe.html | 179 + .../constructor/messageActionPhoneCall.html | 167 + .../constructor/messageActionPinMessage.html | 132 + .../messageActionScreenshotTaken.html | 132 + .../messageActionSecureValuesSent.html | 149 + .../messageActionSecureValuesSentMe.html | 154 + .../messageActionSetChatTheme.html | 147 + .../messageActionSetMessagesTTL.html | 147 + .../constructor/messageEmpty.html | 157 + .../constructor/messageEntityBankCard.html | 152 + .../constructor/messageEntityBlockquote.html | 152 + .../constructor/messageEntityBold.html | 152 + .../constructor/messageEntityBotCommand.html | 152 + .../constructor/messageEntityCashtag.html | 152 + .../constructor/messageEntityCode.html | 152 + .../constructor/messageEntityEmail.html | 152 + .../constructor/messageEntityItalic.html | 152 + .../constructor/messageEntityMentionName.html | 162 + .../constructor/messageEntityPhone.html | 152 + .../constructor/messageEntityPre.html | 157 + .../constructor/messageEntitySpoiler.html | 115 + .../constructor/messageEntityStrike.html | 152 + .../constructor/messageEntityTextUrl.html | 160 + .../constructor/messageEntityUnderline.html | 152 + .../constructor/messageEntityUnknown.html | 152 + .../constructor/messageEntityUrl.html | 155 + .../constructor/messageFwdHeader.html | 195 + .../messageInteractionCounters.html | 157 + .../constructor/messageMediaAudio.html | 147 + .../constructor/messageMediaContact.html | 167 + .../constructor/messageMediaDice.html | 155 + .../constructor/messageMediaDocument.html | 157 + .../constructor/messageMediaEmpty.html | 132 + .../constructor/messageMediaGame.html | 147 + .../constructor/messageMediaGeo.html | 147 + .../constructor/messageMediaGeoLive.html | 170 + .../constructor/messageMediaInvoice.html | 198 + .../constructor/messageMediaPhoto.html | 157 + .../constructor/messageMediaPoll.html | 152 + .../constructor/messageMediaUnsupported.html | 132 + .../constructor/messageMediaVenue.html | 172 + .../constructor/messageMediaVideo.html | 147 + .../constructor/messageMediaWebPage.html | 147 + .../constructor/messagePeerReaction.html | 115 + .../constructor/messageRange.html | 152 + .../constructor/messageReactions.html | 162 + .../constructor/messageReplies.html | 189 + .../constructor/messageReplyHeader.html | 165 + .../constructor/messageService.html | 212 + .../constructor/messageUserVote.html | 157 + .../messageUserVoteInputOption.html | 155 + .../constructor/messageUserVoteMultiple.html | 157 + .../constructor/messageViews.html | 165 + .../messages.affectedFoundMessages | 165 + .../constructor/messages.affectedHistory | 157 + .../constructor/messages.affectedMessages | 155 + .../constructor/messages.allStickers | 155 + .../messages.allStickersNotModified | 132 + .../constructor/messages.archivedStickers | 152 + .../constructor/messages.availableReactions | 115 + .../messages.availableReactionsNotModified | 115 + .../constructor/messages.botCallbackAnswer | 177 + .../constructor/messages.botResults | 182 + .../constructor/messages.channelMessages | 185 + .../messages.chatAdminsWithInvites | 152 + .../constructor/messages.chatFull | 157 + .../constructor/messages.chatInviteImporters | 157 + .../constructor/messages.chats | 147 + .../constructor/messages.chatsSlice | 155 + .../messages.checkedHistoryImportPeer | 150 + .../constructor/messages.dhConfig | 162 + .../constructor/messages.dhConfigNotModified | 147 + .../constructor/messages.dialogs | 162 + .../constructor/messages.dialogsSlice | 167 + .../constructor/messages.discussionMessage | 185 + .../constructor/messages.exportedChatInvite | 152 + .../messages.exportedChatInviteReplaced | 157 + .../constructor/messages.exportedChatInvites | 157 + .../constructor/messages.favedStickers | 160 + .../messages.favedStickersNotModified | 132 + .../constructor/messages.featuredStickers | 165 + .../messages.featuredStickersNotModified | 147 + .../constructor/messages.foundStickerSets | 155 + .../messages.foundStickerSetsNotModified | 132 + .../constructor/messages.highScores | 152 + .../constructor/messages.historyImport | 150 + .../constructor/messages.historyImportParsed | 166 + .../constructor/messages.inactiveChats | 157 + .../constructor/messages.messageEditData | 152 + .../constructor/messages.messageReactionsList | 115 + .../constructor/messages.messageViews | 157 + .../constructor/messages.messages | 157 + .../constructor/messages.messagesNotModified | 147 + .../constructor/messages.messagesSlice | 185 + .../constructor/messages.peerDialogs | 170 + .../constructor/messages.peerSettings | 115 + .../constructor/messages.recentStickers | 165 + .../messages.recentStickersNotModified | 132 + .../constructor/messages.savedGifs | 155 + .../constructor/messages.savedGifsNotModified | 132 + .../constructor/messages.searchCounter | 165 + .../messages.searchResultsCalendar | 115 + .../messages.searchResultsPositions | 115 + .../constructor/messages.sentEncryptedFile | 152 + .../constructor/messages.sentEncryptedMessage | 147 + .../constructor/messages.sentMessageLink | 167 + .../constructor/messages.sponsoredMessages | 157 + .../constructor/messages.statedMessageLink | 172 + .../constructor/messages.statedMessagesLinks | 172 + .../constructor/messages.stickerSet | 157 + .../messages.stickerSetInstallResultArchive | 147 + .../messages.stickerSetInstallResultSuccess | 132 + .../constructor/messages.stickers | 155 + .../constructor/messages.stickersNotModified | 132 + .../constructor/messages.translateNoResult | 115 + .../constructor/messages.translateResultText | 115 + .../constructor/messages.votesList | 170 + .../constructor/nearestDc.html | 157 + .../constructor/notifyBroadcasts.html | 132 + .../constructor/notifyChats.html | 132 + .../constructor/notifyPeer.html | 147 + .../constructor/notifyUsers.html | 132 + .../constructor/null.html | 132 + .../constructor/page.html | 190 + .../constructor/pageBlockAnchor.html | 147 + .../constructor/pageBlockAudio.html | 155 + .../constructor/pageBlockAuthorDate.html | 152 + .../constructor/pageBlockBlockquote.html | 152 + .../constructor/pageBlockChannel.html | 147 + .../constructor/pageBlockCollage.html | 152 + .../constructor/pageBlockCover.html | 147 + .../constructor/pageBlockDetails.html | 162 + .../constructor/pageBlockDivider.html | 132 + .../constructor/pageBlockEmbed.html | 187 + .../constructor/pageBlockEmbedPost.html | 177 + .../constructor/pageBlockFooter.html | 147 + .../constructor/pageBlockHeader.html | 147 + .../constructor/pageBlockKicker.html | 147 + .../constructor/pageBlockList.html | 147 + .../constructor/pageBlockMap.html | 167 + .../constructor/pageBlockOrderedList.html | 147 + .../constructor/pageBlockParagraph.html | 147 + .../constructor/pageBlockPhoto.html | 167 + .../constructor/pageBlockPreformatted.html | 152 + .../constructor/pageBlockPullquote.html | 152 + .../constructor/pageBlockRelatedArticles.html | 152 + .../constructor/pageBlockSlideshow.html | 152 + .../constructor/pageBlockSubheader.html | 147 + .../constructor/pageBlockSubtitle.html | 147 + .../constructor/pageBlockTable.html | 167 + .../constructor/pageBlockTitle.html | 147 + .../constructor/pageBlockUnsupported.html | 132 + .../constructor/pageBlockVideo.html | 167 + .../constructor/pageCaption.html | 152 + .../constructor/pageListItemBlocks.html | 147 + .../constructor/pageListItemText.html | 147 + .../constructor/pageListOrderedItemText.html | 152 + .../constructor/pageRelatedArticle.html | 182 + .../constructor/pageTableCell.html | 187 + .../constructor/pageTableRow.html | 147 + ...BKDF2HMACSHA512iter100000SHA256ModPow.html | 165 + .../constructor/passwordKdfAlgoUnknown.html | 132 + .../constructor/paymentCharge.html | 152 + .../constructor/paymentRequestedInfo.html | 167 + .../paymentSavedCredentialsCard.html | 152 + .../payments.ValidatedRequestedInfo | 145 + .../constructor/payments.bankCardData | 152 + .../constructor/payments.paymentForm | 210 + .../constructor/payments.paymentReceipt | 219 + .../constructor/payments.paymentResult | 147 + .../payments.paymentVerificationNeeded | 147 + .../constructor/payments.savedInfo | 157 + .../constructor/peerBlocked.html | 152 + .../constructor/peerChannel.html | 147 + .../constructor/peerChat.html | 147 + .../constructor/peerLocated.html | 157 + .../constructor/peerNotifySettings.html | 182 + .../constructor/peerSelfLocated.html | 147 + .../constructor/peerSettings.html | 197 + .../constructor/peerUser.html | 147 + .../constructor/phone.exportedGroupCallInvite | 147 + .../constructor/phone.groupCall | 170 + .../constructor/phone.groupParticipants | 175 + .../constructor/phone.joinAsPeers | 157 + .../constructor/phone.phoneCall | 152 + .../constructor/phoneCall.html | 209 + .../constructor/phoneCallAccepted.html | 189 + .../phoneCallDiscardReasonBusy.html | 132 + .../phoneCallDiscardReasonDisconnect.html | 132 + .../phoneCallDiscardReasonHangup.html | 132 + .../phoneCallDiscardReasonMissed.html | 132 + .../constructor/phoneCallDiscarded.html | 182 + .../constructor/phoneCallEmpty.html | 147 + .../constructor/phoneCallProtocol.html | 179 + .../constructor/phoneCallRequested.html | 189 + .../constructor/phoneCallWaiting.html | 187 + .../constructor/phoneConnection.html | 167 + .../constructor/phoneConnectionWebrtc.html | 187 + .../constructor/photo.html | 192 + .../constructor/photoCachedSize.html | 167 + .../constructor/photoEmpty.html | 147 + .../constructor/photoPathSize.html | 155 + .../constructor/photoSize.html | 167 + .../constructor/photoSizeEmpty.html | 150 + .../constructor/photoSizeProgressive.html | 167 + .../constructor/photoStrippedSize.html | 159 + .../constructor/photos.photo | 152 + .../constructor/photos.photos | 152 + .../constructor/photos.photosSlice | 157 + .../constructor/poll.html | 195 + .../constructor/pollAnswer.html | 155 + .../constructor/pollAnswerVoters.html | 170 + .../constructor/pollResults.html | 184 + .../constructor/popularContact.html | 152 + .../constructor/postAddress.html | 172 + .../constructor/privacyKeyAddedByPhone.html | 132 + .../constructor/privacyKeyChatInvite.html | 132 + .../constructor/privacyKeyForwards.html | 132 + .../constructor/privacyKeyPhoneNumber.html | 132 + .../constructor/privacyKeyPhoneP2P.html | 132 + .../constructor/privacyKeyProfilePhoto.html | 132 + .../privacyKeyStatusTimestamp.html | 132 + .../constructor/privacyValueAllowAll.html | 132 + .../privacyValueAllowChatParticipants.html | 147 + .../privacyValueAllowContacts.html | 132 + .../constructor/privacyValueAllowUsers.html | 147 + .../constructor/privacyValueDisallowAll.html | 132 + .../privacyValueDisallowChatParticipants.html | 147 + .../privacyValueDisallowContacts.html | 132 + .../privacyValueDisallowUsers.html | 147 + .../constructor/reactionCount.html | 162 + .../constructor/receivedNotifyMessage.html | 152 + .../constructor/recentMeUrlChat.html | 152 + .../constructor/recentMeUrlChatInvite.html | 152 + .../constructor/recentMeUrlStickerSet.html | 152 + .../constructor/recentMeUrlUnknown.html | 147 + .../constructor/recentMeUrlUser.html | 152 + .../constructor/replyInlineMarkup.html | 147 + .../constructor/replyKeyboardForceReply.html | 162 + .../constructor/replyKeyboardHide.html | 152 + .../constructor/replyKeyboardMarkup.html | 172 + .../constructor/restrictionReason.html | 158 + .../constructor/savedPhoneContact.html | 162 + .../secureCredentialsEncrypted.html | 159 + .../constructor/secureData.html | 160 + .../constructor/secureFile.html | 180 + .../constructor/secureFileEmpty.html | 132 + ...wordKdfAlgoPBKDF2HMACSHA512iter100000.html | 147 + .../securePasswordKdfAlgoSHA512.html | 147 + .../securePasswordKdfAlgoUnknown.html | 132 + .../constructor/securePlainEmail.html | 150 + .../constructor/securePlainPhone.html | 150 + .../constructor/secureRequiredType.html | 167 + .../constructor/secureRequiredTypeOneOf.html | 147 + .../constructor/secureSecretSettings.html | 157 + .../constructor/secureValue.html | 194 + .../constructor/secureValueError.html | 157 + .../constructor/secureValueErrorData.html | 175 + .../constructor/secureValueErrorFile.html | 168 + .../constructor/secureValueErrorFiles.html | 168 + .../secureValueErrorFrontSide.html | 166 + .../constructor/secureValueErrorSelfie.html | 166 + .../secureValueErrorTranslationFile.html | 178 + .../secureValueErrorTranslationFiles.html | 178 + .../constructor/secureValueHash.html | 152 + .../constructor/secureValueTypeAddress.html | 132 + .../secureValueTypeBankStatement.html | 132 + .../secureValueTypeDriverLicense.html | 132 + .../constructor/secureValueTypeEmail.html | 132 + .../secureValueTypeIdentityCard.html | 132 + .../secureValueTypeInternalPassport.html | 134 + .../constructor/secureValueTypePassport.html | 132 + .../secureValueTypePassportRegistration.html | 134 + .../secureValueTypePersonalDetails.html | 132 + .../constructor/secureValueTypePhone.html | 132 + .../secureValueTypeRentalAgreement.html | 132 + .../secureValueTypeTemporaryRegistration.html | 132 + .../secureValueTypeUtilityBill.html | 132 + .../constructor/sendMessageCancelAction.html | 132 + .../sendMessageChooseContactAction.html | 132 + .../sendMessageChooseStickerAction.html | 132 + .../sendMessageEmojiInteraction.html | 160 + .../sendMessageEmojiInteractionSeen.html | 150 + .../sendMessageGamePlayAction.html | 132 + .../sendMessageGeoLocationAction.html | 132 + .../sendMessageHistoryImportAction.html | 147 + .../sendMessageRecordAudioAction.html | 132 + .../sendMessageRecordRoundAction.html | 132 + .../sendMessageRecordVideoAction.html | 132 + .../constructor/sendMessageTypingAction.html | 132 + .../sendMessageUploadAudioAction.html | 147 + .../sendMessageUploadDocumentAction.html | 147 + .../sendMessageUploadPhotoAction.html | 147 + .../sendMessageUploadRoundAction.html | 147 + .../sendMessageUploadVideoAction.html | 147 + .../constructor/shippingOption.html | 157 + .../speakingInGroupCallAction.html | 132 + .../constructor/sponsoredMessage.html | 178 + .../constructor/stats.broadcastStats | 220 + .../constructor/stats.megagroupStats | 230 + .../constructor/stats.messageStats | 147 + .../constructor/statsAbsValueAndPrev.html | 152 + .../constructor/statsDateRangeDays.html | 155 + .../constructor/statsGraph.html | 160 + .../constructor/statsGraphAsync.html | 152 + .../constructor/statsGraphError.html | 150 + .../constructor/statsGroupTopAdmin.html | 165 + .../constructor/statsGroupTopInviter.html | 155 + .../constructor/statsGroupTopPoster.html | 160 + .../constructor/statsPercentValue.html | 156 + .../constructor/statsURL.html | 147 + .../constructor/stickerPack.html | 156 + .../constructor/stickerSet.html | 217 + .../constructor/stickerSetCovered.html | 152 + .../constructor/stickerSetMultiCovered.html | 152 + .../constructor/stickers.suggestedShortName | 147 + .../constructor/storage.fileGif | 132 + .../constructor/storage.fileJpeg | 132 + .../constructor/storage.fileMov | 132 + .../constructor/storage.fileMp3 | 132 + .../constructor/storage.fileMp4 | 132 + .../constructor/storage.filePartial | 132 + .../constructor/storage.filePdf | 132 + .../constructor/storage.filePng | 132 + .../constructor/storage.fileUnknown | 132 + .../constructor/storage.fileWebp | 132 + .../constructor/textAnchor.html | 152 + .../constructor/textBold.html | 147 + .../constructor/textConcat.html | 147 + .../constructor/textEmail.html | 152 + .../constructor/textEmpty.html | 132 + .../constructor/textFixed.html | 147 + .../constructor/textImage.html | 157 + .../constructor/textItalic.html | 147 + .../constructor/textMarked.html | 147 + .../constructor/textPhone.html | 152 + .../constructor/textPlain.html | 147 + .../constructor/textStrike.html | 147 + .../constructor/textSubscript.html | 147 + .../constructor/textSuperscript.html | 147 + .../constructor/textUnderline.html | 147 + .../constructor/textUrl.html | 157 + .../constructor/theme.html | 197 + .../constructor/themeSettings.html | 177 + .../constructor/topPeer.html | 155 + .../topPeerCategoryBotsInline.html | 132 + .../constructor/topPeerCategoryBotsPM.html | 132 + .../constructor/topPeerCategoryChannels.html | 132 + .../topPeerCategoryCorrespondents.html | 132 + .../topPeerCategoryForwardChats.html | 132 + .../topPeerCategoryForwardUsers.html | 132 + .../constructor/topPeerCategoryGroups.html | 132 + .../constructor/topPeerCategoryPeers.html | 157 + .../topPeerCategoryPhoneCalls.html | 132 + .../constructor/true.html | 134 + .../constructor/updateBotCallbackQuery.html | 182 + .../updateBotChatInviteRequester.html | 115 + .../constructor/updateBotCommands.html | 159 + .../constructor/updateBotInlineQuery.html | 177 + .../constructor/updateBotInlineSend.html | 172 + .../updateBotPrecheckoutQuery.html | 184 + .../constructor/updateBotShippingQuery.html | 162 + .../constructor/updateBotStopped.html | 165 + .../constructor/updateBotWebhookJSON.html | 147 + .../updateBotWebhookJSONQuery.html | 157 + .../constructor/updateChannel.html | 147 + .../updateChannelAvailableMessages.html | 155 + .../updateChannelMessageForwards.html | 157 + .../updateChannelMessageViews.html | 157 + .../constructor/updateChannelParticipant.html | 192 + .../updateChannelReadMessagesContents.html | 155 + .../constructor/updateChannelTooLong.html | 161 + .../constructor/updateChannelUserTyping.html | 172 + .../constructor/updateChannelWebPage.html | 167 + .../updateChatDefaultBannedRights.html | 160 + .../constructor/updateChatParticipant.html | 192 + .../constructor/updateChatParticipantAdd.html | 167 + .../updateChatParticipantAdmin.html | 165 + .../updateChatParticipantDelete.html | 157 + .../constructor/updateChatParticipants.html | 147 + .../constructor/updateConfig.html | 135 + .../constructor/updateContactsReset.html | 132 + .../constructor/updateDcOptions.html | 147 + .../updateDeleteChannelMessages.html | 167 + .../constructor/updateDeleteMessages.html | 160 + .../updateDeleteScheduledMessages.html | 155 + .../constructor/updateDialogFilter.html | 160 + .../constructor/updateDialogFilterOrder.html | 150 + .../constructor/updateDialogFilters.html | 135 + .../constructor/updateDialogPinned.html | 165 + .../constructor/updateDialogUnreadMark.html | 157 + .../constructor/updateDraftMessage.html | 155 + .../constructor/updateEditChannelMessage.html | 162 + .../updateEncryptedChatTyping.html | 147 + .../updateEncryptedMessagesRead.html | 157 + .../constructor/updateEncryption.html | 152 + .../constructor/updateFavedStickers.html | 135 + .../constructor/updateFolderPeers.html | 162 + .../constructor/updateGeoLiveViewed.html | 152 + .../constructor/updateGroupCall.html | 155 + .../updateGroupCallConnection.html | 157 + .../updateGroupCallParticipants.html | 157 + .../updateInlineBotCallbackQuery.html | 177 + .../constructor/updateLangPack.html | 147 + .../constructor/updateLangPackTooLong.html | 150 + .../constructor/updateMessageID.html | 155 + .../constructor/updateMessagePoll.html | 162 + .../constructor/updateMessagePollVote.html | 165 + .../constructor/updateMessageReactions.html | 157 + .../constructor/updateNewChannelMessage.html | 162 + .../updateNewEncryptedMessage.html | 155 + .../constructor/updateNewMessage.html | 157 + .../updateNewScheduledMessage.html | 150 + .../constructor/updateNewStickerSet.html | 147 + .../constructor/updatePeerBlocked.html | 152 + .../constructor/updatePeerHistoryTTL.html | 157 + .../constructor/updatePeerLocated.html | 147 + .../constructor/updatePeerSettings.html | 152 + .../updatePendingJoinRequests.html | 115 + .../constructor/updatePhoneCall.html | 147 + .../updatePhoneCallSignalingData.html | 152 + .../updatePinnedChannelMessages.html | 177 + .../constructor/updatePinnedDialogs.html | 160 + .../constructor/updatePinnedMessages.html | 175 + .../constructor/updatePrivacy.html | 152 + .../constructor/updatePtsChanged.html | 135 + .../updateReadChannelDiscussionInbox.html | 177 + .../updateReadChannelDiscussionOutbox.html | 162 + .../constructor/updateReadChannelInbox.html | 179 + .../constructor/updateReadChannelOutbox.html | 155 + .../updateReadFeaturedStickers.html | 132 + .../constructor/updateReadHistoryInbox.html | 182 + .../constructor/updateReadHistoryOutbox.html | 165 + .../updateReadMessagesContents.html | 160 + .../constructor/updateRecentStickers.html | 132 + .../updateServiceNotification.html | 183 + .../constructor/updateShort.html | 152 + .../constructor/updateShortChatMessage.html | 232 + .../constructor/updateShortMessage.html | 229 + .../constructor/updateShortSentMessage.html | 192 + .../constructor/updateStickerSets.html | 132 + .../constructor/updateStickerSetsOrder.html | 157 + .../constructor/updateTheme.html | 147 + .../constructor/updateUserBlocked.html | 159 + .../constructor/updateUserName.html | 167 + .../constructor/updateUserPhone.html | 152 + .../constructor/updateUserPhoto.html | 165 + .../constructor/updateUserStatus.html | 152 + .../constructor/updateUserTyping.html | 155 + .../constructor/updateWebPage.html | 160 + .../constructor/updates.channelDifference | 185 + .../updates.channelDifferenceEmpty | 165 + .../updates.channelDifferenceTooLong | 190 + .../constructor/updates.difference | 172 + .../constructor/updates.differenceEmpty | 152 + .../constructor/updates.differenceSlice | 175 + .../constructor/updates.differenceTooLong | 150 + .../constructor/updates.html | 167 + .../constructor/updates.state | 172 + .../constructor/updatesCombined.html | 172 + .../constructor/updatesTooLong.html | 135 + .../constructor/upload.cdnFile | 149 + .../constructor/upload.cdnFileReuploadNeeded | 149 + .../constructor/upload.file | 157 + .../constructor/upload.fileCdnRedirect | 169 + .../constructor/upload.webFile | 170 + .../constructor/urlAuthResultAccepted.html | 150 + .../constructor/urlAuthResultDefault.html | 135 + .../constructor/urlAuthResultRequest.html | 165 + .../constructor/user.html | 287 + .../constructor/userEmpty.html | 147 + .../constructor/userFull.html | 239 + .../constructor/userProfilePhoto.html | 172 + .../constructor/userProfilePhotoEmpty.html | 132 + .../constructor/userStatusEmpty.html | 132 + .../constructor/userStatusLastMonth.html | 132 + .../constructor/userStatusLastWeek.html | 132 + .../constructor/userStatusOffline.html | 147 + .../constructor/userStatusOnline.html | 147 + .../constructor/userStatusRecently.html | 132 + .../constructor/users.userFull | 115 + .../constructor/vector.html | 134 + .../constructor/wallPaper.html | 192 + .../constructor/wallPaperNoFile.html | 171 + .../constructor/wallPaperSettings.html | 187 + .../constructor/wallPaperSolid.html | 162 + .../constructor/webAuthorization.html | 189 + .../constructor/webDocument.html | 167 + .../constructor/webDocumentNoProxy.html | 165 + .../constructor/webPage.html | 240 + .../constructor/webPageAttributeTheme.html | 157 + .../constructor/webPageEmpty.html | 147 + .../constructor/webPageNotModified.html | 152 + .../constructor/webPagePending.html | 152 + .../corefork.telegram.org/getProxyConfig.html | 24 + .../import-stickers.html | 159 + .../method/account.acceptAuthorization | 170 + .../method/account.cancelPasswordEmail | 138 + .../account.changeAuthorizationSettings | 115 + .../method/account.changePhone | 190 + .../method/account.checkUsername | 167 + .../method/account.confirmPasswordEmail | 175 + .../method/account.confirmPhone | 180 + .../method/account.createTheme | 186 + .../method/account.declinePasswordReset | 155 + .../method/account.deleteAccount | 170 + .../method/account.finishTakeoutSession | 172 + .../method/account.getAccountTTL | 134 + .../method/account.getAllSecureValues | 136 + .../method/account.getAuthorizationForm | 176 + .../method/account.getAuthorizations | 134 + .../method/account.getAutoDownloadSettings | 134 + .../method/account.getChatThemes | 153 + .../account.getContactSignUpNotification | 135 + .../method/account.getContentSettings | 134 + .../method/account.getGlobalPrivacySettings | 134 + .../method/account.getMultiWallPapers | 148 + .../method/account.getNotifyExceptions | 165 + .../method/account.getNotifySettings | 166 + .../method/account.getPassword | 134 + .../method/account.getPrivacy | 166 + .../method/account.getSecureValue | 151 + .../method/account.getTheme | 181 + .../method/account.getThemes | 158 + .../method/account.getTmpPassword | 176 + .../method/account.getWallPaper | 167 + .../method/account.getWallPapers | 153 + .../method/account.getWebAuthorizations | 136 + .../method/account.initTakeoutSession | 204 + .../method/account.installTheme | 165 + .../method/account.installWallPaper | 172 + .../method/account.registerDevice | 217 + .../method/account.reportPeer | 182 + .../method/account.reportProfilePhoto | 165 + .../method/account.resendPasswordEmail | 138 + .../method/account.resetAuthorization | 175 + .../method/account.resetNotifySettings | 135 + .../method/account.resetPassword | 139 + .../method/account.resetWallPapers | 135 + .../method/account.resetWebAuthorization | 171 + .../method/account.resetWebAuthorizations | 137 + .../method/account.saveAutoDownloadSettings | 166 + .../method/account.saveSecureValue | 174 + .../method/account.sendChangePhoneCode | 186 + .../method/account.sendConfirmPhoneCode | 174 + .../method/account.sendVerifyEmailCode | 168 + .../method/account.sendVerifyPhoneCode | 173 + .../method/account.setAccountTTL | 167 + .../method/account.setAuthorizationTTL | 115 + .../account.setContactSignUpNotification | 150 + .../method/account.setContentSettings | 172 + .../method/account.setGlobalPrivacySettings | 166 + .../method/account.setPrivacy | 181 + .../method/account.unregisterDevice | 180 + .../method/account.updateDeviceLocked | 153 + .../method/account.updateNotifySettings | 192 + .../method/account.updatePasswordSettings | 207 + .../method/account.updateProfile | 187 + .../method/account.updateStatus | 155 + .../method/account.updateTheme | 196 + .../method/account.updateUsername | 182 + .../method/account.uploadTheme | 190 + .../method/account.uploadWallPaper | 182 + .../method/account.verifyEmail | 179 + .../method/account.verifyPhone | 191 + .../method/auth.acceptLoginToken | 171 + .../method/auth.bindTempAuthKey | 252 + .../method/auth.cancelCode | 180 + .../method/auth.checkPassword | 180 + .../method/auth.checkPhone | 176 + .../method/auth.checkRecoveryPassword | 174 + .../method/auth.dropTempAuthKeys | 151 + .../method/auth.exportAuthorization | 167 + .../method/auth.exportLoginToken | 183 + .../method/auth.importAuthorization | 178 + .../method/auth.importBotAuthorization | 205 + .../method/auth.importLoginToken | 187 + data/corefork.telegram.org/method/auth.logOut | 139 + .../method/auth.recoverPassword | 187 + .../method/auth.requestPasswordRecovery | 159 + .../method/auth.resendCode | 191 + .../method/auth.resetAuthorizations | 156 + .../method/auth.sendCall | 175 + .../method/auth.sendCode | 236 + .../method/auth.sendInvites | 157 + .../corefork.telegram.org/method/auth.sendSms | 167 + data/corefork.telegram.org/method/auth.signIn | 219 + data/corefork.telegram.org/method/auth.signUp | 236 + .../method/bots.answerWebhookJSONQuery | 178 + .../method/bots.getBotCommands | 154 + .../method/bots.resetBotCommands | 156 + .../method/bots.sendCustomRequest | 177 + .../method/bots.setBotCommands | 188 + .../method/channels.checkUsername | 190 + .../method/channels.convertToGigagroup | 177 + .../method/channels.createChannel | 232 + .../method/channels.deleteChannel | 200 + .../method/channels.deleteHistory | 180 + .../method/channels.deleteMessages | 190 + .../method/channels.deleteParticipantHistory | 115 + .../method/channels.deleteUserHistory | 197 + .../method/channels.editAdmin | 301 + .../method/channels.editBanned | 241 + .../method/channels.editCreator | 225 + .../method/channels.editLocation | 180 + .../method/channels.editPhoto | 221 + .../method/channels.exportMessageLink | 204 + .../method/channels.getAdminLog | 226 + .../method/channels.getAdminedPublicChannels | 191 + .../method/channels.getChannels | 181 + .../method/channels.getFullChannel | 187 + .../method/channels.getGroupsForDiscussion | 144 + .../method/channels.getInactiveChannels | 134 + .../method/channels.getLeftChannels | 172 + .../method/channels.getMessages | 193 + .../method/channels.getParticipant | 205 + .../method/channels.getParticipants | 203 + .../method/channels.getSendAs | 115 + .../method/channels.getSponsoredMessages | 154 + .../method/channels.inviteToChannel | 262 + .../method/channels.joinChannel | 227 + .../method/channels.leaveChannel | 201 + .../method/channels.readHistory | 185 + .../method/channels.readMessageContents | 185 + .../method/channels.reportSpam | 192 + .../method/channels.setDiscussionGroup | 200 + .../method/channels.setStickers | 183 + .../method/channels.togglePreHistoryHidden | 202 + .../method/channels.toggleSignatures | 187 + .../method/channels.toggleSlowMode | 190 + .../method/channels.updateUsername | 212 + .../method/channels.viewSponsoredMessage | 177 + .../method/contacts.acceptContact | 190 + .../method/contacts.addContact | 217 + .../method/contacts.block | 182 + .../method/contacts.deleteByPhones | 150 + .../method/contacts.deleteContacts | 155 + .../method/contacts.getBlocked | 155 + .../method/contacts.getContactIDs | 151 + .../method/contacts.getContacts | 155 + .../method/contacts.getLocated | 197 + .../method/contacts.getSaved | 150 + .../method/contacts.getStatuses | 133 + .../method/contacts.getTopPeers | 226 + .../method/contacts.importContacts | 154 + .../method/contacts.resetSaved | 135 + .../method/contacts.resetTopPeerRating | 175 + .../method/contacts.resolveUsername | 182 + .../method/contacts.search | 178 + .../method/contacts.toggleTopPeers | 153 + .../method/contacts.unblock | 182 + .../method/folders.deleteFolder | 175 + .../method/folders.editPeerFolders | 175 + .../method/help.acceptTermsOfService | 150 + .../method/help.dismissSuggestion | 160 + .../method/help.editUserInfo | 180 + .../method/help.getAppChangelog | 162 + .../method/help.getAppConfig | 142 + .../method/help.getAppUpdate | 150 + .../method/help.getCdnConfig | 154 + .../method/help.getConfig | 192 + .../method/help.getCountriesList | 158 + .../method/help.getDeepLinkInfo | 150 + .../method/help.getInviteText | 134 + .../method/help.getNearestDc | 134 + .../method/help.getPassportConfig | 154 + .../method/help.getPromoData | 135 + .../method/help.getProxyData | 132 + .../method/help.getRecentMeUrls | 149 + .../method/help.getSupport | 134 + .../method/help.getSupportName | 151 + .../method/help.getTermsOfServiceUpdate | 135 + .../method/help.getUserInfo | 167 + .../method/help.hidePromoData | 150 + .../method/help.saveAppLog | 150 + .../method/help.setBotUpdatesStatus | 156 + .../method/initConnection.html | 216 + .../method/invokeAfterMsg.html | 154 + .../method/invokeAfterMsgs.html | 154 + .../method/invokeWithLayer.html | 204 + .../method/invokeWithMessagesRange.html | 154 + .../method/invokeWithTakeout.html | 154 + .../method/invokeWithoutUpdates.html | 154 + .../method/langpack.getDifference | 176 + .../method/langpack.getLangPack | 171 + .../method/langpack.getLanguage | 154 + .../method/langpack.getLanguages | 165 + .../method/langpack.getStrings | 175 + .../method/messages.acceptEncryption | 190 + .../method/messages.acceptUrlAuth | 179 + .../method/messages.addChatUser | 237 + .../method/messages.checkChatInvite | 178 + .../method/messages.checkHistoryImport | 152 + .../method/messages.checkHistoryImportPeer | 172 + .../method/messages.clearAllDrafts | 138 + .../method/messages.clearRecentStickers | 155 + .../method/messages.createChat | 197 + .../method/messages.deleteChat | 170 + .../method/messages.deleteChatUser | 208 + .../method/messages.deleteExportedChatInvite | 155 + .../method/messages.deleteHistory | 206 + .../method/messages.deleteMessages | 177 + .../method/messages.deletePhoneCallHistory | 154 + .../messages.deleteRevokedExportedChatInvites | 155 + .../method/messages.deleteScheduledMessages | 160 + .../method/messages.discardEncryption | 187 + .../method/messages.editChatAbout | 216 + .../method/messages.editChatAdmin | 195 + .../messages.editChatDefaultBannedRights | 206 + .../method/messages.editChatPhoto | 203 + .../method/messages.editChatTitle | 193 + .../method/messages.editExportedChatInvite | 193 + .../method/messages.editInlineBotMessage | 206 + .../method/messages.editMessage | 338 + .../method/messages.exportChatInvite | 217 + .../method/messages.faveSticker | 172 + .../method/messages.forwardMessage | 177 + .../method/messages.forwardMessages | 363 + .../method/messages.getAdminsWithInvites | 149 + .../method/messages.getAllChats | 150 + .../method/messages.getAllDrafts | 143 + .../method/messages.getAllStickers | 153 + .../method/messages.getArchivedStickers | 167 + .../method/messages.getAttachedStickers | 148 + .../method/messages.getAvailableReactions | 115 + .../method/messages.getBotCallbackAnswer | 226 + .../method/messages.getChatInviteImporters | 172 + .../method/messages.getChats | 173 + .../method/messages.getCommonChats | 185 + .../method/messages.getDhConfig | 175 + .../method/messages.getDialogFilters | 136 + .../method/messages.getDialogUnreadMarks | 133 + .../method/messages.getDiscussionMessage | 183 + .../method/messages.getDocumentByHash | 178 + .../method/messages.getEmojiKeywords | 149 + .../messages.getEmojiKeywordsDifference | 154 + .../method/messages.getEmojiKeywordsLanguages | 148 + .../method/messages.getEmojiURL | 149 + .../method/messages.getExportedChatInvite | 155 + .../method/messages.getExportedChatInvites | 182 + .../method/messages.getFavedStickers | 153 + .../method/messages.getFeaturedStickers | 153 + .../method/messages.getFullChat | 172 + .../method/messages.getGameHighScores | 187 + .../method/messages.getHistory | 232 + .../method/messages.getInlineBotResults | 226 + .../method/messages.getInlineGameHighScores | 177 + .../method/messages.getMaskStickers | 153 + .../method/messages.getMessageEditData | 186 + .../method/messages.getMessageReactionsList | 180 + .../messages.getMessageReadParticipants | 173 + .../method/messages.getMessages | 153 + .../method/messages.getMessagesReactions | 161 + .../method/messages.getMessagesViews | 199 + .../method/messages.getOldFeaturedStickers | 163 + .../method/messages.getOnlines | 171 + .../method/messages.getPeerDialogs | 181 + .../method/messages.getPeerSettings | 171 + .../method/messages.getPinnedDialogs | 169 + .../method/messages.getPollResults | 177 + .../method/messages.getPollVotes | 204 + .../method/messages.getRecentLocations | 165 + .../method/messages.getRecentStickers | 163 + .../method/messages.getReplies | 217 + .../method/messages.getSavedGifs | 153 + .../method/messages.getScheduledHistory | 182 + .../method/messages.getScheduledMessages | 179 + .../method/messages.getSearchCounters | 173 + .../method/messages.getSearchResultsCalendar | 115 + .../method/messages.getSearchResultsPositions | 115 + .../method/messages.getStickerSet | 173 + .../method/messages.getStickers | 175 + .../method/messages.getSuggestedDialogFilters | 136 + .../method/messages.getUnreadMentions | 212 + .../method/messages.getUnreadReactions | 115 + .../method/messages.getWebPage | 177 + .../method/messages.getWebPagePreview | 191 + .../method/messages.hideAllChatJoinRequests | 115 + .../method/messages.hideChatJoinRequest | 115 + .../method/messages.hidePeerSettingsBar | 153 + .../method/messages.importChatInvite | 227 + .../method/messages.initHistoryImport | 191 + .../method/messages.installStickerSet | 172 + .../method/messages.markDialogUnread | 160 + .../method/messages.migrateChat | 190 + .../method/messages.readDiscussion | 180 + .../method/messages.readEncryptedHistory | 172 + .../method/messages.readFeaturedStickers | 150 + .../method/messages.readHistory | 186 + .../method/messages.readMentions | 181 + .../method/messages.readMessageContents | 149 + .../method/messages.readReactions | 115 + .../method/messages.receivedMessages | 148 + .../method/messages.receivedQueue | 170 + .../method/messages.reorderPinnedDialogs | 185 + .../method/messages.reorderStickerSets | 160 + .../method/messages.report | 187 + .../method/messages.reportEncryptedSpam | 167 + .../method/messages.reportSpam | 180 + .../method/messages.requestEncryption | 185 + .../method/messages.requestUrlAuth | 174 + .../method/messages.saveDefaultSendAs | 115 + .../method/messages.saveDraft | 202 + .../method/messages.saveGif | 172 + .../method/messages.saveRecentSticker | 182 + .../method/messages.search | 291 + .../method/messages.searchGifs | 177 + .../method/messages.searchGlobal | 226 + .../method/messages.searchStickerSets | 168 + .../method/messages.sendBroadcast | 145 + .../method/messages.sendEncrypted | 210 + .../method/messages.sendEncryptedFile | 215 + .../method/messages.sendEncryptedService | 205 + .../method/messages.sendInlineBotResult | 344 + .../method/messages.sendMedia | 518 + .../method/messages.sendMessage | 398 + .../method/messages.sendMultiMedia | 263 + .../method/messages.sendReaction | 193 + .../method/messages.sendScheduledMessages | 182 + .../messages.sendScreenshotNotification | 187 + .../method/messages.sendVote | 220 + .../method/messages.setBotCallbackAnswer | 203 + .../method/messages.setBotPrecheckoutResults | 188 + .../method/messages.setBotShippingResults | 186 + .../method/messages.setChatAvailableReactions | 115 + .../method/messages.setChatTheme | 185 + .../method/messages.setDefaultReaction | 115 + .../method/messages.setEncryptedTyping | 177 + .../method/messages.setGameScore | 218 + .../method/messages.setHistoryTTL | 182 + .../method/messages.setInlineBotResults | 358 + .../method/messages.setInlineGameScore | 198 + .../method/messages.setTyping | 240 + .../method/messages.startBot | 224 + .../method/messages.startHistoryImport | 180 + .../method/messages.toggleDialogPin | 187 + .../method/messages.toggleNoForwards | 115 + .../method/messages.toggleStickerSets | 170 + .../method/messages.translateText | 115 + .../method/messages.uninstallStickerSet | 167 + .../method/messages.unpinAllMessages | 153 + .../method/messages.updateDialogFilter | 190 + .../method/messages.updateDialogFiltersOrder | 153 + .../method/messages.updatePinnedMessage | 238 + .../method/messages.uploadEncryptedFile | 155 + .../method/messages.uploadImportedMedia | 181 + .../method/messages.uploadMedia | 264 + .../method/payments.clearSavedInfo | 160 + .../method/payments.getPaymentForm | 181 + .../method/payments.getPaymentReceipt | 171 + .../method/payments.getSavedInfo | 134 + .../method/payments.sendPaymentForm | 206 + .../method/phone.acceptCall | 193 + .../method/phone.checkGroupCall | 154 + .../method/phone.confirmCall | 188 + .../method/phone.createGroupCall | 200 + .../method/phone.discardCall | 202 + .../method/phone.discardGroupCall | 155 + .../method/phone.editGroupCallMember | 167 + .../method/phone.editGroupCallParticipant | 225 + .../method/phone.editGroupCallTitle | 160 + .../method/phone.exportGroupCallInvite | 159 + .../method/phone.getCallConfig | 134 + .../method/phone.getGroupCall | 157 + .../method/phone.getGroupCallJoinAs | 149 + .../method/phone.getGroupParticipants | 174 + .../method/phone.inviteToGroupCall | 177 + .../method/phone.joinGroupCall | 202 + .../method/phone.joinGroupCallPresentation | 180 + .../method/phone.leaveGroupCall | 160 + .../method/phone.leaveGroupCallPresentation | 155 + .../method/phone.receivedCall | 172 + .../method/phone.saveCallDebug | 177 + .../method/phone.saveDefaultGroupCallJoinAs | 155 + .../method/phone.sendSignalingData | 155 + .../method/phone.setCallRating | 192 + .../method/phone.startScheduledGroupCall | 155 + .../method/phone.toggleGroupCallRecord | 180 + .../method/phone.toggleGroupCallSettings | 187 + .../method/photos.deletePhotos | 148 + .../method/photos.getUserPhotos | 193 + .../method/photos.updateProfilePhoto | 196 + .../method/photos.uploadProfilePhoto | 221 + .../method/stats.getBroadcastStats | 194 + .../method/stats.getMegagroupStats | 191 + .../method/stats.getMessageStats | 189 + .../method/stats.loadAsyncGraph | 193 + .../method/stickers.addStickerToSet | 188 + .../method/stickers.changeStickerPosition | 178 + .../method/stickers.checkShortName | 172 + .../method/stickers.createStickerSet | 283 + .../method/stickers.removeStickerFromSet | 173 + .../method/stickers.setStickerSetThumb | 183 + .../method/stickers.suggestShortName | 166 + .../method/updates.getChannelDifference | 247 + .../method/updates.getDifference | 225 + .../method/updates.getState | 135 + .../method/upload.getCdnFile | 162 + .../method/upload.getCdnFileHashes | 178 + .../method/upload.getFile | 252 + .../method/upload.getFileHashes | 171 + .../method/upload.getWebFile | 176 + .../method/upload.reuploadCdnFile | 173 + .../method/upload.saveBigFilePart | 208 + .../method/upload.saveFilePart | 183 + .../method/users.getFullUser | 177 + .../method/users.getUsers | 191 + .../method/users.setSecureValueErrors | 176 + data/corefork.telegram.org/methods.html | 2306 ++++ data/corefork.telegram.org/mtproto.html | 260 + .../mtproto/TL-abstract-types.html | 202 + .../mtproto/TL-combinators.html | 251 + .../mtproto/TL-dependent.html | 236 + .../mtproto/TL-formal.html | 319 + .../mtproto/TL-optargs.html | 151 + .../mtproto/TL-patterns.html | 129 + .../mtproto/TL-polymorph.html | 170 + data/corefork.telegram.org/mtproto/TL-tl.html | 308 + .../mtproto/TL-types.html | 124 + data/corefork.telegram.org/mtproto/TL.html | 210 + .../mtproto/auth_key.html | 210 + .../mtproto/description.html | 238 + .../mtproto/description_v1.html | 205 + .../mtproto/mtproto-transports.html | 281 + .../mtproto/samples-auth_key.html | 748 ++ .../mtproto/security_guidelines.html | 177 + .../mtproto/security_guidelines_v1.html | 175 + .../mtproto/serialize.html | 240 + .../service_messages_about_messages.html | 185 + data/corefork.telegram.org/mtproto_v1.html | 229 + data/corefork.telegram.org/passport.html | 690 ++ .../passport/encryption.html | 606 ++ .../passport/example.html | 585 + .../passport/sdk-android.html | 180 + .../passport/sdk-ios-mac.html | 246 + .../passport/sdk-javascript.html | 258 + data/corefork.telegram.org/schema.html | 1859 ++++ .../schema/end-to-end-json.html | 1 + .../schema/end-to-end.html | 225 + data/corefork.telegram.org/schema/json.html | 1 + .../schema/mtproto-json.html | 1 + .../corefork.telegram.org/schema/mtproto.html | 204 + data/corefork.telegram.org/themes.html | 143 + .../type/AccountDaysTTL.html | 162 + data/corefork.telegram.org/type/Audio.html | 128 + .../type/Authorization.html | 162 + .../type/AutoDownloadSettings.html | 143 + .../type/AvailableReaction.html | 115 + .../type/BankCardOpenUrl.html | 143 + .../corefork.telegram.org/type/BaseTheme.html | 163 + data/corefork.telegram.org/type/Bool.html | 721 ++ .../type/BotCommand.html | 143 + .../type/BotCommandScope.html | 176 + data/corefork.telegram.org/type/BotInfo.html | 143 + .../type/BotInlineResult.html | 148 + .../corefork.telegram.org/type/CdnConfig.html | 164 + .../type/CdnPublicKey.html | 145 + .../type/ChannelAdminLogEvent.html | 143 + .../type/ChannelAdminLogEventAction.html | 302 + .../type/ChannelAdminLogEventsFilter.html | 143 + .../type/ChannelLocation.html | 148 + .../type/ChannelMessagesFilter.html | 148 + .../type/ChannelParticipant.html | 168 + .../type/ChannelParticipantsFilter.html | 178 + data/corefork.telegram.org/type/Chat.html | 163 + .../type/ChatAdminRights.html | 146 + .../type/ChatAdminWithInvites.html | 143 + .../type/ChatBannedRights.html | 146 + data/corefork.telegram.org/type/ChatFull.html | 148 + .../type/ChatInvite.html | 172 + .../type/ChatInviteImporter.html | 143 + .../type/ChatOnlines.html | 162 + .../type/ChatParticipant.html | 153 + .../type/ChatParticipants.html | 148 + .../corefork.telegram.org/type/ChatPhoto.html | 148 + .../corefork.telegram.org/type/ChatTheme.html | 143 + .../type/CodeSettings.html | 143 + data/corefork.telegram.org/type/Config.html | 162 + data/corefork.telegram.org/type/Contact.html | 143 + .../type/ContactStatus.html | 143 + data/corefork.telegram.org/type/DataJSON.html | 168 + data/corefork.telegram.org/type/DcOption.html | 143 + .../type/DecryptedDataBlock.html | 128 + .../type/DecryptedMessage.html | 140 + .../type/DecryptedMessageAction.html | 145 + .../type/DecryptedMessageLayer.html | 129 + data/corefork.telegram.org/type/Dialog.html | 148 + .../type/DialogFilter.html | 143 + .../type/DialogFilterSuggested.html | 143 + .../type/DialogPeer.html | 148 + .../type/DisabledFeature.html | 128 + data/corefork.telegram.org/type/Document.html | 173 + .../type/DocumentAttribute.html | 173 + .../type/DraftMessage.html | 151 + .../type/EmojiKeyword.html | 148 + .../type/EmojiKeywordsDifference.html | 167 + .../type/EmojiLanguage.html | 143 + data/corefork.telegram.org/type/EmojiURL.html | 162 + .../type/EncryptedChat.html | 187 + .../type/EncryptedMessage.html | 148 + .../type/ExportedChatInvite.html | 162 + .../type/ExportedMessageLink.html | 162 + data/corefork.telegram.org/type/FileHash.html | 143 + .../type/FileLocation.html | 128 + data/corefork.telegram.org/type/Folder.html | 143 + .../type/FolderPeer.html | 143 + data/corefork.telegram.org/type/Game.html | 143 + data/corefork.telegram.org/type/GeoPoint.html | 148 + .../type/GlobalPrivacySettings.html | 167 + .../corefork.telegram.org/type/GroupCall.html | 148 + .../type/GroupCallParticipant.html | 143 + .../type/GroupCallParticipantVideo.html | 143 + .../GroupCallParticipantVideoSourceGroup.html | 143 + .../corefork.telegram.org/type/HighScore.html | 143 + .../type/ImportedContact.html | 143 + .../type/InlineQueryPeerType.html | 163 + .../type/InputAppEvent.html | 143 + .../type/InputBotInlineMessage.html | 173 + .../type/InputBotInlineMessageID.html | 148 + .../type/InputBotInlineResult.html | 158 + .../type/InputChannel.html | 153 + .../type/InputChatPhoto.html | 153 + .../type/InputCheckPasswordSRP.html | 151 + .../type/InputClientProxy.html | 145 + .../type/InputContact.html | 143 + .../type/InputDialogPeer.html | 148 + .../type/InputDocument.html | 148 + .../type/InputEncryptedChat.html | 143 + .../type/InputEncryptedFile.html | 158 + .../corefork.telegram.org/type/InputFile.html | 148 + .../type/InputFileLocation.html | 188 + .../type/InputFolderPeer.html | 143 + .../corefork.telegram.org/type/InputGame.html | 148 + .../type/InputGeoPoint.html | 148 + .../type/InputGroupCall.html | 143 + .../type/InputMedia.html | 213 + .../type/InputMessage.html | 158 + .../type/InputNotifyPeer.html | 158 + .../type/InputPaymentCredentials.html | 158 + .../corefork.telegram.org/type/InputPeer.html | 173 + .../type/InputPeerNotifySettings.html | 143 + .../type/InputPhoneCall.html | 143 + .../type/InputPhoto.html | 148 + .../type/InputPrivacyKey.html | 178 + .../type/InputPrivacyRule.html | 178 + .../type/InputSecureFile.html | 151 + .../type/InputSecureValue.html | 145 + .../type/InputSingleMedia.html | 148 + .../type/InputStickerSet.html | 168 + .../type/InputStickerSetItem.html | 143 + .../type/InputStickeredMedia.html | 148 + .../type/InputThemeSettings.html | 143 + .../corefork.telegram.org/type/InputUser.html | 158 + .../type/InputWallPaper.html | 153 + .../type/InputWebDocument.html | 143 + .../type/InputWebFileLocation.html | 148 + data/corefork.telegram.org/type/Invoice.html | 143 + .../type/JSONObjectValue.html | 143 + .../corefork.telegram.org/type/JSONValue.html | 187 + .../type/KeyboardButton.html | 195 + .../type/KeyboardButtonRow.html | 143 + .../type/LabeledPrice.html | 143 + .../type/LangPackDifference.html | 167 + .../type/LangPackLanguage.html | 162 + .../type/LangPackString.html | 153 + .../type/MaskCoords.html | 143 + data/corefork.telegram.org/type/Message.html | 153 + .../type/MessageAction.html | 284 + .../type/MessageEntity.html | 234 + .../type/MessageFwdHeader.html | 143 + .../type/MessageInteractionCounters.html | 143 + .../type/MessageMedia.html | 232 + .../type/MessagePeerReaction.html | 115 + .../type/MessageRange.html | 143 + .../type/MessageReactions.html | 128 + .../type/MessageReactionsList.html | 128 + .../type/MessageReplies.html | 146 + .../type/MessageUserVote.html | 153 + .../type/MessageViews.html | 143 + .../type/MessagesFilter.html | 223 + .../corefork.telegram.org/type/NearestDc.html | 162 + .../type/NotifyPeer.html | 158 + data/corefork.telegram.org/type/Null.html | 143 + data/corefork.telegram.org/type/Page.html | 143 + .../corefork.telegram.org/type/PageBlock.html | 283 + .../type/PageCaption.html | 143 + .../type/PageListItem.html | 148 + .../type/PageListOrderedItem.html | 148 + .../type/PageRelatedArticle.html | 143 + .../type/PageTableCell.html | 143 + .../type/PageTableRow.html | 143 + .../type/PasswordKdfAlgo.html | 151 + .../type/PaymentCharge.html | 143 + .../type/PaymentRequestedInfo.html | 143 + .../type/PaymentSavedCredentials.html | 143 + data/corefork.telegram.org/type/Peer.html | 153 + .../type/PeerBlocked.html | 143 + .../type/PeerLocated.html | 148 + .../type/PeerNotifySettings.html | 162 + .../type/PeerSettings.html | 158 + .../type/PhoneCallDiscardReason.html | 158 + .../type/PhoneCallProtocol.html | 143 + .../type/PhoneConnection.html | 148 + data/corefork.telegram.org/type/Photo.html | 148 + .../corefork.telegram.org/type/PhotoSize.html | 168 + data/corefork.telegram.org/type/Poll.html | 143 + .../type/PollAnswer.html | 146 + .../type/PollAnswerVoters.html | 143 + .../type/PollResults.html | 143 + .../type/PopularContact.html | 143 + .../type/PostAddress.html | 143 + .../type/PrivacyKey.html | 178 + .../type/PrivacyRule.html | 178 + .../type/ReactionCount.html | 128 + .../type/ReceivedNotifyMessage.html | 143 + .../type/RecentMeUrl.html | 163 + .../type/ReplyMarkup.html | 158 + .../type/ReportReason.html | 178 + .../type/RestrictionReason.html | 143 + data/corefork.telegram.org/type/RichText.html | 218 + .../type/SavedContact.html | 143 + .../type/SearchResultsCalendarPeriod.html | 115 + .../type/SearchResultsPosition.html | 115 + .../type/SecureCredentialsEncrypted.html | 143 + .../type/SecureData.html | 146 + .../type/SecureFile.html | 151 + .../type/SecurePasswordKdfAlgo.html | 155 + .../type/SecurePlainData.html | 150 + .../type/SecureRequiredType.html | 148 + .../type/SecureSecretSettings.html | 145 + .../type/SecureValue.html | 162 + .../type/SecureValueError.html | 183 + .../type/SecureValueHash.html | 143 + .../type/SecureValueType.html | 203 + .../type/SendMessageAction.html | 228 + .../type/ShippingOption.html | 143 + .../type/SponsoredMessage.html | 143 + .../type/StatsAbsValueAndPrev.html | 143 + .../type/StatsDateRangeDays.html | 143 + .../type/StatsGraph.html | 172 + .../type/StatsGroupTopInviter.html | 146 + .../type/StatsGroupTopPoster.html | 146 + .../type/StatsPercentValue.html | 143 + data/corefork.telegram.org/type/StatsURL.html | 143 + .../type/StickerPack.html | 143 + .../type/StickerSetCovered.html | 148 + data/corefork.telegram.org/type/Theme.html | 172 + .../type/ThemeSettings.html | 143 + .../type/TopPeerCategory.html | 178 + .../type/TopPeerCategoryPeers.html | 143 + data/corefork.telegram.org/type/True.html | 145 + data/corefork.telegram.org/type/Update.html | 606 ++ data/corefork.telegram.org/type/Updates.html | 514 + .../type/UrlAuthResult.html | 177 + data/corefork.telegram.org/type/User.html | 177 + data/corefork.telegram.org/type/UserFull.html | 158 + .../type/UserProfilePhoto.html | 148 + .../type/UserStatus.html | 168 + data/corefork.telegram.org/type/Vector t.html | 143 + data/corefork.telegram.org/type/Video.html | 128 + .../corefork.telegram.org/type/VideoSize.html | 143 + .../type/WallPaperSettings.html | 143 + .../type/WebAuthorization.html | 143 + .../type/WebDocument.html | 148 + data/corefork.telegram.org/type/WebPage.html | 177 + .../type/WebPageAttribute.html | 143 + .../type/account.AuthorizationForm | 162 + .../type/account.Authorizations | 162 + .../type/account.AutoDownloadSettings | 162 + .../type/account.ChatThemes | 162 + .../type/account.ContentSettings | 162 + .../type/account.Password | 162 + .../type/account.PasswordInputSettings | 146 + .../type/account.PasswordSettings | 164 + .../type/account.PrivacyRules | 167 + .../type/account.ResetPasswordResult | 175 + .../type/account.SentChangePhoneCode | 128 + .../type/account.SentEmailCode | 162 + .../type/account.Takeout | 162 + .../corefork.telegram.org/type/account.Themes | 168 + .../type/account.TmpPassword | 162 + .../type/account.WallPapers | 167 + .../type/account.WebAuthorizations | 162 + .../type/auth.Authorization | 192 + .../type/auth.CheckedPhone | 128 + data/corefork.telegram.org/type/auth.CodeType | 154 + .../type/auth.ExportedAuthorization | 162 + .../corefork.telegram.org/type/auth.LoggedOut | 115 + .../type/auth.LoginToken | 177 + .../type/auth.PasswordRecovery | 165 + data/corefork.telegram.org/type/auth.SentCode | 183 + .../type/auth.SentCodeType | 159 + data/corefork.telegram.org/type/bytes.html | 125 + .../type/channels.AdminLogResults | 162 + .../type/channels.ChannelParticipant | 162 + .../type/channels.ChannelParticipants | 167 + .../type/channels.SendAsPeers | 115 + .../type/contacts.Blocked | 167 + .../type/contacts.Contacts | 167 + .../corefork.telegram.org/type/contacts.Found | 162 + .../type/contacts.ImportedContacts | 162 + data/corefork.telegram.org/type/contacts.Link | 128 + .../type/contacts.ResolvedPeer | 162 + .../type/contacts.TopPeers | 172 + data/corefork.telegram.org/type/double.html | 118 + .../corefork.telegram.org/type/help.AppUpdate | 167 + .../type/help.CountriesList | 167 + .../type/help.CountryCode | 143 + .../type/help.DeepLinkInfo | 167 + .../type/help.InviteText | 162 + .../corefork.telegram.org/type/help.PromoData | 167 + .../corefork.telegram.org/type/help.ProxyData | 130 + .../type/help.RecentMeUrls | 162 + data/corefork.telegram.org/type/help.Support | 162 + .../type/help.SupportName | 162 + .../type/help.TermsOfService | 143 + .../type/help.TermsOfServiceUpdate | 167 + data/corefork.telegram.org/type/help.UserInfo | 172 + data/corefork.telegram.org/type/int.html | 118 + data/corefork.telegram.org/type/long.html | 118 + .../type/messages.AffectedFoundMessages | 162 + .../type/messages.AffectedHistory | 179 + .../type/messages.AffectedMessages | 178 + .../type/messages.AllStickers | 172 + .../type/messages.ArchivedStickers | 162 + .../type/messages.AvailableReactions | 115 + .../type/messages.BotCallbackAnswer | 162 + .../type/messages.BotResults | 162 + .../type/messages.ChatAdminsWithInvites | 162 + .../type/messages.ChatFull | 168 + .../type/messages.ChatInviteImporters | 162 + .../corefork.telegram.org/type/messages.Chats | 198 + .../type/messages.CheckedHistoryImportPeer | 165 + .../type/messages.DhConfig | 167 + .../type/messages.Dialogs | 172 + .../type/messages.DiscussionMessage | 162 + .../type/messages.ExportedChatInvite | 172 + .../type/messages.ExportedChatInvites | 162 + .../type/messages.FavedStickers | 167 + .../type/messages.FeaturedStickers | 172 + .../type/messages.FoundGifs | 128 + .../type/messages.FoundStickerSets | 167 + .../type/messages.HighScores | 167 + .../type/messages.HistoryImport | 165 + .../type/messages.HistoryImportParsed | 162 + .../type/messages.InactiveChats | 162 + .../type/messages.MessageEditData | 162 + .../type/messages.MessageReactionsList | 115 + .../type/messages.MessageViews | 162 + .../type/messages.Messages | 230 + .../type/messages.PeerDialogs | 167 + .../type/messages.RecentStickers | 167 + .../type/messages.SavedGifs | 167 + .../type/messages.SearchCounter | 143 + .../type/messages.SearchResultsCalendar | 115 + .../type/messages.SearchResultsPositions | 115 + .../type/messages.SentEncryptedMessage | 177 + .../type/messages.SentMessage | 128 + .../type/messages.SponsoredMessages | 166 + .../type/messages.StatedMessage | 128 + .../type/messages.StatedMessages | 128 + .../type/messages.StickerSet | 189 + .../type/messages.StickerSetInstallResult | 167 + .../type/messages.Stickers | 167 + .../type/messages.TranslatedText | 115 + .../type/messages.VotesList | 162 + .../type/payments.BankCardData | 162 + .../type/payments.PaymentForm | 162 + .../type/payments.PaymentReceipt | 162 + .../type/payments.PaymentResult | 167 + .../type/payments.SavedInfo | 162 + .../type/payments.ValidatedRequestedInfo | 162 + .../type/phone.ExportedGroupCallInvite | 162 + .../type/phone.GroupCall | 162 + .../type/phone.GroupParticipants | 162 + .../type/phone.JoinAsPeers | 162 + .../type/phone.PhoneCall | 172 + data/corefork.telegram.org/type/photos.Photo | 167 + data/corefork.telegram.org/type/photos.Photos | 167 + .../type/stats.BroadcastStats | 162 + .../type/stats.MegagroupStats | 162 + .../type/stats.MessageStats | 162 + .../type/stickers.SuggestedShortName | 162 + .../type/storage.FileType | 188 + data/corefork.telegram.org/type/string.html | 126 + .../type/updates.ChannelDifference | 172 + .../type/updates.Difference | 177 + data/corefork.telegram.org/type/updates.State | 162 + .../corefork.telegram.org/type/upload.CdnFile | 167 + data/corefork.telegram.org/type/upload.File | 167 + .../corefork.telegram.org/type/upload.WebFile | 162 + .../corefork.telegram.org/type/users.UserFull | 115 + data/corefork.telegram.org/widgets.html | 141 + .../widgets/discussion.html | 226 + data/corefork.telegram.org/widgets/login.html | 404 + data/corefork.telegram.org/widgets/post.html | 240 + data/corefork.telegram.org/widgets/share.html | 250 + data/desktop.telegram.org.html | 76 + data/instantview.telegram.org.html | 293 + data/instantview.telegram.org/docs.html | 1527 +++ data/instantview.telegram.org/samples.html | 395 + data/instantview.telegram.org/templates.html | 1253 +++ data/macos.telegram.org.html | 521 + data/promote.telegram.org/auth.html | 206 + data/promote.telegram.org/basics.html | 205 + .../promote.telegram.org/getting-started.html | 321 + data/promote.telegram.org/guidelines.html | 313 + data/promote.telegram.org/tos.html | 253 + data/telegram.org.html | 283 + data/telegram.org/android.html | 79 + data/telegram.org/blog.html | 268 + data/telegram.org/blog/200-million.html | 222 + data/telegram.org/blog/6-years.html | 1355 +++ data/telegram.org/blog/admin-revolution.html | 261 + .../blog/albums-saved-messages.html | 268 + data/telegram.org/blog/android-2-0.html | 257 + data/telegram.org/blog/android-gif.html | 218 + data/telegram.org/blog/android-themes.html | 246 + data/telegram.org/blog/android-wear-2-0.html | 224 + .../blog/animated-backgrounds.html | 302 + data/telegram.org/blog/animated-stickers.html | 261 + data/telegram.org/blog/apple-watch.html | 225 + .../blog/archive-and-new-design.html | 318 + data/telegram.org/blog/autodelete-inv2.html | 299 + data/telegram.org/blog/autoplay.html | 245 + data/telegram.org/blog/backgrounds-2-0.html | 231 + data/telegram.org/blog/bot-revolution.html | 279 + data/telegram.org/blog/bots-2-0.html | 260 + .../telegram.org/blog/cache-and-stickers.html | 231 + data/telegram.org/blog/calls.html | 266 + data/telegram.org/blog/captions-places.html | 244 + data/telegram.org/blog/channels-2-0.html | 246 + data/telegram.org/blog/channels.html | 224 + ...hemes-interactive-emoji-read-receipts.html | 297 + .../blog/contacts-local-groups.html | 272 + data/telegram.org/blog/coronavirus.html | 254 + .../crowdsourcing-a-more-secure-future.html | 212 + .../telegram.org/blog/cryptocontest-ends.html | 214 + data/telegram.org/blog/cryptocontest.html | 224 + data/telegram.org/blog/desktop-1-0.html | 250 + data/telegram.org/blog/desktop-compact.html | 213 + .../blog/discover-stickers-and-more.html | 246 + data/telegram.org/blog/drafts.html | 242 + data/telegram.org/blog/edit.html | 245 + data/telegram.org/blog/encrypted-cdns.html | 228 + data/telegram.org/blog/export-and-more.html | 238 + data/telegram.org/blog/files-on-steroids.html | 240 + .../filters-anonymous-admins-comments.html | 261 + data/telegram.org/blog/folders.html | 298 + data/telegram.org/blog/games.html | 264 + data/telegram.org/blog/gifs.html | 223 + data/telegram.org/blog/group-video-calls.html | 264 + data/telegram.org/blog/inline-bots.html | 234 + data/telegram.org/blog/instant-camera.html | 229 + data/telegram.org/blog/instant-view.html | 268 + data/telegram.org/blog/invite-links.html | 217 + data/telegram.org/blog/link-preview.html | 217 + data/telegram.org/blog/live-locations.html | 243 + .../live-streams-forwarding-next-channel.html | 285 + data/telegram.org/blog/login.html | 257 + data/telegram.org/blog/move-history.html | 284 + data/telegram.org/blog/now-you-see-me.html | 235 + data/telegram.org/blog/passport.html | 233 + .../payments-2-0-scheduled-voice-chats.html | 319 + data/telegram.org/blog/payments.html | 253 + .../blog/permissions-groups-undo.html | 265 + .../blog/photo-editor-and-passcodes.html | 252 + data/telegram.org/blog/pin-and-ifttt.html | 263 + .../pinned-messages-locations-playlists.html | 282 + .../world.html | 278 + data/telegram.org/blog/polls-2-0-vmq.html | 271 + data/telegram.org/blog/polls.html | 230 + .../blog/privacy-discussions-web-bots.html | 284 + .../telegram.org/blog/privacy-revolution.html | 226 + ...profile-videos-people-nearby-and-more.html | 315 + ...ected-content-delete-by-date-and-more.html | 324 + .../blog/reactions-spoilers-translations.html | 300 + .../blog/replies-mentions-hashtags.html | 238 + .../blog/replies-mentions-stickers.html | 257 + .../blog/scheduled-reminders-themes.html | 264 + data/telegram.org/blog/search-and-media.html | 232 + .../sessions-and-2-step-verification.html | 220 + data/telegram.org/blog/share-preview.html | 269 + data/telegram.org/blog/shared-files.html | 231 + data/telegram.org/blog/shared-links.html | 221 + ...lling-calendar-join-requests-and-more.html | 343 + .../blog/silent-messages-slow-mode.html | 296 + .../blog/stickers-meet-art-and-history.html | 338 + .../blog/stickers-revolution.html | 231 + data/telegram.org/blog/stickers.html | 225 + data/telegram.org/blog/supergroups.html | 251 + data/telegram.org/blog/supergroups5k.html | 232 + data/telegram.org/blog/tdlib.html | 228 + data/telegram.org/blog/telegram-5-ios.html | 268 + .../telegram-me-change-number-and-pfs.html | 228 + data/telegram.org/blog/telegram-x.html | 262 + data/telegram.org/blog/telegraph.html | 238 + data/telegram.org/blog/themes-accounts.html | 247 + data/telegram.org/blog/translations-iv2.html | 276 + data/telegram.org/blog/trending-stickers.html | 262 + data/telegram.org/blog/unread-replace-2x.html | 259 + data/telegram.org/blog/unsend-and-usage.html | 273 + .../blog/unsend-privacy-emoji.html | 261 + .../blog/usernames-and-secret-chats-v2.html | 222 + .../blog/verifiable-apps-and-more.html | 392 + data/telegram.org/blog/video-1000.html | 354 + data/telegram.org/blog/video-calls.html | 234 + .../blog/video-messages-and-telescope.html | 247 + .../blog/video-stickers-better-reactions.html | 273 + data/telegram.org/blog/voice-2-secret-3.html | 245 + .../blog/voice-chats-on-steroids.html | 275 + data/telegram.org/blog/voice-chats.html | 311 + .../blog/winter-contest-ends.html | 224 + data/telegram.org/evolution.html | 1801 ++++ data/telegram.org/faq.html | 705 ++ data/telegram.org/faq_channels.html | 165 + data/telegram.org/faq_spam.html | 163 + data/telegram.org/jobs.html | 156 + data/telegram.org/press.html | 194 + data/telegram.org/privacy.html | 299 + data/telegram.org/privacy/gmailbot.html | 161 + data/telegram.org/support.html | 141 + data/telegram.org/teststore.html | 283 + data/telegram.org/tos.html | 133 + data/telegram.org/tour.html | 144 + data/telegram.org/tour/channels.html | 294 + data/telegram.org/tour/groups.html | 266 + .../what-can-you-do-with-Telegram.html | 283 + data/themes.telegram.org/auth.html | 163 + data/translations.telegram.org/en.html | 335 + data/translations.telegram.org/en/ios.html | 390 + data/translations.telegram.org/en/macos.html | 390 + data/tsf.telegram.org/auth.html | 241 + data/tsf.telegram.org/manuals.html | 224 + .../manuals/answering_questions.html | 265 + data/tsf.telegram.org/manuals/bios.html | 331 + .../tsf.telegram.org/manuals/bug_herding.html | 334 + data/tsf.telegram.org/manuals/bugs.html | 460 + .../tsf.telegram.org/manuals/come-and-go.html | 229 + data/tsf.telegram.org/manuals/e2ee.html | 202 + 3778 files changed, 679134 insertions(+) create mode 100644 data/contest.com.html create mode 100644 data/core.telegram.org.html create mode 100644 data/core.telegram.org/api.html create mode 100644 data/core.telegram.org/api/account-deletion.html create mode 100644 data/core.telegram.org/api/animated-emojis.html create mode 100644 data/core.telegram.org/api/auth.html create mode 100644 data/core.telegram.org/api/bots.html create mode 100644 data/core.telegram.org/api/bots/buttons.html create mode 100644 data/core.telegram.org/api/bots/commands.html create mode 100644 data/core.telegram.org/api/bots/games.html create mode 100644 data/core.telegram.org/api/bots/inline.html create mode 100644 data/core.telegram.org/api/channel.html create mode 100644 data/core.telegram.org/api/config.html create mode 100644 data/core.telegram.org/api/datacenter.html create mode 100644 data/core.telegram.org/api/dice.html create mode 100644 data/core.telegram.org/api/discussion.html create mode 100644 data/core.telegram.org/api/drafts.html create mode 100644 data/core.telegram.org/api/end-to-end.html create mode 100644 data/core.telegram.org/api/end-to-end/pfs.html create mode 100644 data/core.telegram.org/api/end-to-end/seq_no.html create mode 100644 data/core.telegram.org/api/end-to-end/video-calls.html create mode 100644 data/core.telegram.org/api/end-to-end/voice-calls.html create mode 100644 data/core.telegram.org/api/end-to-end_v1.html create mode 100644 data/core.telegram.org/api/entities.html create mode 100644 data/core.telegram.org/api/errors.html create mode 100644 data/core.telegram.org/api/file_reference.html create mode 100644 data/core.telegram.org/api/files.html create mode 100644 data/core.telegram.org/api/folders.html create mode 100644 data/core.telegram.org/api/geochats.html create mode 100644 data/core.telegram.org/api/import.html create mode 100644 data/core.telegram.org/api/invoking.html create mode 100644 data/core.telegram.org/api/layers.html create mode 100644 data/core.telegram.org/api/live-location.html create mode 100644 data/core.telegram.org/api/mentions.html create mode 100644 data/core.telegram.org/api/min.html create mode 100644 data/core.telegram.org/api/obtaining_api_id.html create mode 100644 data/core.telegram.org/api/offsets.html create mode 100644 data/core.telegram.org/api/optimisation.html create mode 100644 data/core.telegram.org/api/passport.html create mode 100644 data/core.telegram.org/api/pattern.html create mode 100644 data/core.telegram.org/api/payments.html create mode 100644 data/core.telegram.org/api/pfs.html create mode 100644 data/core.telegram.org/api/pin.html create mode 100644 data/core.telegram.org/api/poll.html create mode 100644 data/core.telegram.org/api/push-updates.html create mode 100644 data/core.telegram.org/api/qr-login.html create mode 100644 data/core.telegram.org/api/recent-actions.html create mode 100644 data/core.telegram.org/api/rights.html create mode 100644 data/core.telegram.org/api/scheduled-messages.html create mode 100644 data/core.telegram.org/api/search.html create mode 100644 data/core.telegram.org/api/sponsored-messages.html create mode 100644 data/core.telegram.org/api/srp.html create mode 100644 data/core.telegram.org/api/terms.html create mode 100644 data/core.telegram.org/api/threads.html create mode 100644 data/core.telegram.org/api/top-rating.html create mode 100644 data/core.telegram.org/api/updates.html create mode 100644 data/core.telegram.org/api/url-authorization.html create mode 100644 data/core.telegram.org/api/web-events.html create mode 100644 data/core.telegram.org/apple_privacy.html create mode 100644 data/core.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html create mode 100644 data/core.telegram.org/bots.html create mode 100644 data/core.telegram.org/bots/api-changelog.html create mode 100644 data/core.telegram.org/bots/api.html create mode 100644 data/core.telegram.org/bots/faq.html create mode 100644 data/core.telegram.org/bots/games.html create mode 100644 data/core.telegram.org/bots/inline.html create mode 100644 data/core.telegram.org/bots/samples.html create mode 100644 data/core.telegram.org/bots/samples/hellobot.html create mode 100644 data/core.telegram.org/bots/self-signed.html create mode 100644 data/core.telegram.org/bots/webhooks.html create mode 100644 data/core.telegram.org/cdn.html create mode 100644 data/core.telegram.org/cdn/faq_ir.html create mode 100644 data/core.telegram.org/cdn/faq_ir/durov.html create mode 100644 data/core.telegram.org/constructor/account.authorizationForm create mode 100644 data/core.telegram.org/constructor/account.authorizations create mode 100644 data/core.telegram.org/constructor/account.autoDownloadSettings create mode 100644 data/core.telegram.org/constructor/account.chatThemes create mode 100644 data/core.telegram.org/constructor/account.chatThemesNotModified create mode 100644 data/core.telegram.org/constructor/account.contentSettings create mode 100644 data/core.telegram.org/constructor/account.password create mode 100644 data/core.telegram.org/constructor/account.passwordInputSettings create mode 100644 data/core.telegram.org/constructor/account.passwordSettings create mode 100644 data/core.telegram.org/constructor/account.privacyRules create mode 100644 data/core.telegram.org/constructor/account.resetPasswordFailedWait create mode 100644 data/core.telegram.org/constructor/account.resetPasswordOk create mode 100644 data/core.telegram.org/constructor/account.resetPasswordRequestedWait create mode 100644 data/core.telegram.org/constructor/account.sentChangePhoneCode create mode 100644 data/core.telegram.org/constructor/account.sentEmailCode create mode 100644 data/core.telegram.org/constructor/account.takeout create mode 100644 data/core.telegram.org/constructor/account.themes create mode 100644 data/core.telegram.org/constructor/account.wallPapers create mode 100644 data/core.telegram.org/constructor/account.wallPapersNotModified create mode 100644 data/core.telegram.org/constructor/account.webAuthorizations create mode 100644 data/core.telegram.org/constructor/accountDaysTTL.html create mode 100644 data/core.telegram.org/constructor/auth.authorization create mode 100644 data/core.telegram.org/constructor/auth.authorizationSignUpRequired create mode 100644 data/core.telegram.org/constructor/auth.codeTypeCall create mode 100644 data/core.telegram.org/constructor/auth.codeTypeFlashCall create mode 100644 data/core.telegram.org/constructor/auth.codeTypeSms create mode 100644 data/core.telegram.org/constructor/auth.exportedAuthorization create mode 100644 data/core.telegram.org/constructor/auth.loginToken create mode 100644 data/core.telegram.org/constructor/auth.loginTokenMigrateTo create mode 100644 data/core.telegram.org/constructor/auth.loginTokenSuccess create mode 100644 data/core.telegram.org/constructor/auth.passwordRecovery create mode 100644 data/core.telegram.org/constructor/auth.sentAppCode create mode 100644 data/core.telegram.org/constructor/auth.sentCode create mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeApp create mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeCall create mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall create mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeSms create mode 100644 data/core.telegram.org/constructor/authorization.html create mode 100644 data/core.telegram.org/constructor/autoDownloadSettings.html create mode 100644 data/core.telegram.org/constructor/bankCardOpenUrl.html create mode 100644 data/core.telegram.org/constructor/baseThemeArctic.html create mode 100644 data/core.telegram.org/constructor/baseThemeClassic.html create mode 100644 data/core.telegram.org/constructor/baseThemeDay.html create mode 100644 data/core.telegram.org/constructor/baseThemeNight.html create mode 100644 data/core.telegram.org/constructor/baseThemeTinted.html create mode 100644 data/core.telegram.org/constructor/boolFalse.html create mode 100644 data/core.telegram.org/constructor/boolTrue.html create mode 100644 data/core.telegram.org/constructor/botCommandScopeChatAdmins.html create mode 100644 data/core.telegram.org/constructor/botCommandScopeChats.html create mode 100644 data/core.telegram.org/constructor/botCommandScopeDefault.html create mode 100644 data/core.telegram.org/constructor/botCommandScopePeer.html create mode 100644 data/core.telegram.org/constructor/botCommandScopePeerAdmins.html create mode 100644 data/core.telegram.org/constructor/botCommandScopePeerUser.html create mode 100644 data/core.telegram.org/constructor/botCommandScopeUsers.html create mode 100644 data/core.telegram.org/constructor/botInfo.html create mode 100644 data/core.telegram.org/constructor/botInlineMediaResult.html create mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaAuto.html create mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaContact.html create mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaGeo.html create mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaInvoice.html create mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaVenue.html create mode 100644 data/core.telegram.org/constructor/botInlineMessageText.html create mode 100644 data/core.telegram.org/constructor/botInlineResult.html create mode 100644 data/core.telegram.org/constructor/cdnConfig.html create mode 100644 data/core.telegram.org/constructor/cdnPublicKey.html create mode 100644 data/core.telegram.org/constructor/channel.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEvent.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventsFilter.html create mode 100644 data/core.telegram.org/constructor/channelForbidden.html create mode 100644 data/core.telegram.org/constructor/channelFull.html create mode 100644 data/core.telegram.org/constructor/channelLocation.html create mode 100644 data/core.telegram.org/constructor/channelLocationEmpty.html create mode 100644 data/core.telegram.org/constructor/channelMessagesFilter.html create mode 100644 data/core.telegram.org/constructor/channelMessagesFilterEmpty.html create mode 100644 data/core.telegram.org/constructor/channelParticipant.html create mode 100644 data/core.telegram.org/constructor/channelParticipantAdmin.html create mode 100644 data/core.telegram.org/constructor/channelParticipantBanned.html create mode 100644 data/core.telegram.org/constructor/channelParticipantCreator.html create mode 100644 data/core.telegram.org/constructor/channelParticipantLeft.html create mode 100644 data/core.telegram.org/constructor/channelParticipantSelf.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsAdmins.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsBanned.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsBots.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsContacts.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsKicked.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsMentions.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsRecent.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsSearch.html create mode 100644 data/core.telegram.org/constructor/channels.adminLogResults create mode 100644 data/core.telegram.org/constructor/channels.channelParticipant create mode 100644 data/core.telegram.org/constructor/channels.channelParticipants create mode 100644 data/core.telegram.org/constructor/channels.channelParticipantsNotModified create mode 100644 data/core.telegram.org/constructor/chat.html create mode 100644 data/core.telegram.org/constructor/chatAdminRights.html create mode 100644 data/core.telegram.org/constructor/chatBannedRights.html create mode 100644 data/core.telegram.org/constructor/chatEmpty.html create mode 100644 data/core.telegram.org/constructor/chatForbidden.html create mode 100644 data/core.telegram.org/constructor/chatFull.html create mode 100644 data/core.telegram.org/constructor/chatInvite.html create mode 100644 data/core.telegram.org/constructor/chatInviteAlready.html create mode 100644 data/core.telegram.org/constructor/chatInviteExported.html create mode 100644 data/core.telegram.org/constructor/chatInviteImporter.html create mode 100644 data/core.telegram.org/constructor/chatInvitePeek.html create mode 100644 data/core.telegram.org/constructor/chatOnlines.html create mode 100644 data/core.telegram.org/constructor/chatParticipant.html create mode 100644 data/core.telegram.org/constructor/chatParticipantAdmin.html create mode 100644 data/core.telegram.org/constructor/chatParticipantCreator.html create mode 100644 data/core.telegram.org/constructor/chatParticipants.html create mode 100644 data/core.telegram.org/constructor/chatParticipantsForbidden.html create mode 100644 data/core.telegram.org/constructor/chatPhoto.html create mode 100644 data/core.telegram.org/constructor/chatPhotoEmpty.html create mode 100644 data/core.telegram.org/constructor/chatTheme.html create mode 100644 data/core.telegram.org/constructor/codeSettings.html create mode 100644 data/core.telegram.org/constructor/config.html create mode 100644 data/core.telegram.org/constructor/contact.html create mode 100644 data/core.telegram.org/constructor/contactStatus.html create mode 100644 data/core.telegram.org/constructor/contacts.blockedSlice create mode 100644 data/core.telegram.org/constructor/contacts.contacts create mode 100644 data/core.telegram.org/constructor/contacts.contactsNotModified create mode 100644 data/core.telegram.org/constructor/contacts.found create mode 100644 data/core.telegram.org/constructor/contacts.importedContacts create mode 100644 data/core.telegram.org/constructor/contacts.resolvedPeer create mode 100644 data/core.telegram.org/constructor/contacts.topPeers create mode 100644 data/core.telegram.org/constructor/contacts.topPeersDisabled create mode 100644 data/core.telegram.org/constructor/contacts.topPeersNotModified create mode 100644 data/core.telegram.org/constructor/dataJSON.html create mode 100644 data/core.telegram.org/constructor/dcOption.html create mode 100644 data/core.telegram.org/constructor/decryptedMessage.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionNoop.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionResend.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionTyping.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageLayer.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaAudio.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaContact.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaDocument.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaVenue.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaVideo.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageService.html create mode 100644 data/core.telegram.org/constructor/dialog.html create mode 100644 data/core.telegram.org/constructor/dialogFilter.html create mode 100644 data/core.telegram.org/constructor/dialogFilterSuggested.html create mode 100644 data/core.telegram.org/constructor/dialogFolder.html create mode 100644 data/core.telegram.org/constructor/dialogPeer.html create mode 100644 data/core.telegram.org/constructor/dialogPeerFolder.html create mode 100644 data/core.telegram.org/constructor/disabledFeature.html create mode 100644 data/core.telegram.org/constructor/document.html create mode 100644 data/core.telegram.org/constructor/documentAttributeAnimated.html create mode 100644 data/core.telegram.org/constructor/documentAttributeAudio.html create mode 100644 data/core.telegram.org/constructor/documentAttributeFilename.html create mode 100644 data/core.telegram.org/constructor/documentAttributeHasStickers.html create mode 100644 data/core.telegram.org/constructor/documentAttributeImageSize.html create mode 100644 data/core.telegram.org/constructor/documentAttributeSticker.html create mode 100644 data/core.telegram.org/constructor/documentAttributeVideo.html create mode 100644 data/core.telegram.org/constructor/documentEmpty.html create mode 100644 data/core.telegram.org/constructor/draftMessage.html create mode 100644 data/core.telegram.org/constructor/draftMessageEmpty.html create mode 100644 data/core.telegram.org/constructor/emojiKeyword.html create mode 100644 data/core.telegram.org/constructor/emojiKeywordDeleted.html create mode 100644 data/core.telegram.org/constructor/emojiKeywordsDifference.html create mode 100644 data/core.telegram.org/constructor/emojiLanguage.html create mode 100644 data/core.telegram.org/constructor/emojiURL.html create mode 100644 data/core.telegram.org/constructor/encryptedChatDiscarded.html create mode 100644 data/core.telegram.org/constructor/encryptedChatEmpty.html create mode 100644 data/core.telegram.org/constructor/encryptedChatRequested.html create mode 100644 data/core.telegram.org/constructor/encryptedChatWaiting.html create mode 100644 data/core.telegram.org/constructor/encryptedFileEmpty.html create mode 100644 data/core.telegram.org/constructor/encryptedMessage.html create mode 100644 data/core.telegram.org/constructor/encryptedMessageService.html create mode 100644 data/core.telegram.org/constructor/error.html create mode 100644 data/core.telegram.org/constructor/exportedMessageLink.html create mode 100644 data/core.telegram.org/constructor/fileHash.html create mode 100644 data/core.telegram.org/constructor/fileLocation.html create mode 100644 data/core.telegram.org/constructor/fileLocationUnavailable.html create mode 100644 data/core.telegram.org/constructor/folder.html create mode 100644 data/core.telegram.org/constructor/game.html create mode 100644 data/core.telegram.org/constructor/geoPoint.html create mode 100644 data/core.telegram.org/constructor/geoPointEmpty.html create mode 100644 data/core.telegram.org/constructor/globalPrivacySettings.html create mode 100644 data/core.telegram.org/constructor/groupCallDiscarded.html create mode 100644 data/core.telegram.org/constructor/groupCallParticipant.html create mode 100644 data/core.telegram.org/constructor/groupCallParticipantVideo.html create mode 100644 data/core.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html create mode 100644 data/core.telegram.org/constructor/help.countriesList create mode 100644 data/core.telegram.org/constructor/help.countriesListNotModified create mode 100644 data/core.telegram.org/constructor/help.country create mode 100644 data/core.telegram.org/constructor/help.countryCode create mode 100644 data/core.telegram.org/constructor/help.deepLinkInfo create mode 100644 data/core.telegram.org/constructor/help.deepLinkInfoEmpty create mode 100644 data/core.telegram.org/constructor/help.noAppUpdate create mode 100644 data/core.telegram.org/constructor/help.passportConfig create mode 100644 data/core.telegram.org/constructor/help.passportConfigNotModified create mode 100644 data/core.telegram.org/constructor/help.promoData create mode 100644 data/core.telegram.org/constructor/help.promoDataEmpty create mode 100644 data/core.telegram.org/constructor/help.recentMeUrls create mode 100644 data/core.telegram.org/constructor/help.support create mode 100644 data/core.telegram.org/constructor/help.supportName create mode 100644 data/core.telegram.org/constructor/help.termsOfService create mode 100644 data/core.telegram.org/constructor/help.termsOfServiceUpdate create mode 100644 data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty create mode 100644 data/core.telegram.org/constructor/help.userInfo create mode 100644 data/core.telegram.org/constructor/help.userInfoEmpty create mode 100644 data/core.telegram.org/constructor/highScore.html create mode 100644 data/core.telegram.org/constructor/inlineBotSwitchPM.html create mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html create mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeChat.html create mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html create mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypePM.html create mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html create mode 100644 data/core.telegram.org/constructor/inputAppEvent.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageGame.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageID.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageID64.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageText.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineResult.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineResultDocument.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineResultGame.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineResultPhoto.html create mode 100644 data/core.telegram.org/constructor/inputChannel.html create mode 100644 data/core.telegram.org/constructor/inputChannelEmpty.html create mode 100644 data/core.telegram.org/constructor/inputChannelFromMessage.html create mode 100644 data/core.telegram.org/constructor/inputChatPhoto.html create mode 100644 data/core.telegram.org/constructor/inputChatPhotoEmpty.html create mode 100644 data/core.telegram.org/constructor/inputChatUploadedPhoto.html create mode 100644 data/core.telegram.org/constructor/inputCheckPasswordEmpty.html create mode 100644 data/core.telegram.org/constructor/inputCheckPasswordSRP.html create mode 100644 data/core.telegram.org/constructor/inputClientProxy.html create mode 100644 data/core.telegram.org/constructor/inputDialogPeer.html create mode 100644 data/core.telegram.org/constructor/inputDialogPeerFolder.html create mode 100644 data/core.telegram.org/constructor/inputDocument.html create mode 100644 data/core.telegram.org/constructor/inputDocumentEmpty.html create mode 100644 data/core.telegram.org/constructor/inputDocumentFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputEncryptedChat.html create mode 100644 data/core.telegram.org/constructor/inputEncryptedFile.html create mode 100644 data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html create mode 100644 data/core.telegram.org/constructor/inputEncryptedFileEmpty.html create mode 100644 data/core.telegram.org/constructor/inputEncryptedFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputEncryptedFileUploaded.html create mode 100644 data/core.telegram.org/constructor/inputFile.html create mode 100644 data/core.telegram.org/constructor/inputFileBig.html create mode 100644 data/core.telegram.org/constructor/inputFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputFolderPeer.html create mode 100644 data/core.telegram.org/constructor/inputGameID.html create mode 100644 data/core.telegram.org/constructor/inputGameShortName.html create mode 100644 data/core.telegram.org/constructor/inputGeoPoint.html create mode 100644 data/core.telegram.org/constructor/inputGroupCall.html create mode 100644 data/core.telegram.org/constructor/inputGroupCallStream.html create mode 100644 data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html create mode 100644 data/core.telegram.org/constructor/inputMediaContact.html create mode 100644 data/core.telegram.org/constructor/inputMediaDice.html create mode 100644 data/core.telegram.org/constructor/inputMediaDocument.html create mode 100644 data/core.telegram.org/constructor/inputMediaDocumentExternal.html create mode 100644 data/core.telegram.org/constructor/inputMediaEmpty.html create mode 100644 data/core.telegram.org/constructor/inputMediaGame.html create mode 100644 data/core.telegram.org/constructor/inputMediaGeoLive.html create mode 100644 data/core.telegram.org/constructor/inputMediaGeoPoint.html create mode 100644 data/core.telegram.org/constructor/inputMediaInvoice.html create mode 100644 data/core.telegram.org/constructor/inputMediaPhoto.html create mode 100644 data/core.telegram.org/constructor/inputMediaPoll.html create mode 100644 data/core.telegram.org/constructor/inputMediaUploadedDocument.html create mode 100644 data/core.telegram.org/constructor/inputMediaUploadedPhoto.html create mode 100644 data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html create mode 100644 data/core.telegram.org/constructor/inputMediaVenue.html create mode 100644 data/core.telegram.org/constructor/inputMessageCallbackQuery.html create mode 100644 data/core.telegram.org/constructor/inputMessageEntityMentionName.html create mode 100644 data/core.telegram.org/constructor/inputMessageID.html create mode 100644 data/core.telegram.org/constructor/inputMessagePinned.html create mode 100644 data/core.telegram.org/constructor/inputMessageReplyTo.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterContacts.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterDocument.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterEmpty.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterGif.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterMusic.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhotos.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPinned.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterUrl.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterVideo.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterVoice.html create mode 100644 data/core.telegram.org/constructor/inputNotifyChats.html create mode 100644 data/core.telegram.org/constructor/inputNotifyPeer.html create mode 100644 data/core.telegram.org/constructor/inputNotifyUsers.html create mode 100644 data/core.telegram.org/constructor/inputPaymentCredentials.html create mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html create mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsGooglePay.html create mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html create mode 100644 data/core.telegram.org/constructor/inputPeerChannel.html create mode 100644 data/core.telegram.org/constructor/inputPeerChannelFromMessage.html create mode 100644 data/core.telegram.org/constructor/inputPeerChat.html create mode 100644 data/core.telegram.org/constructor/inputPeerEmpty.html create mode 100644 data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputPeerSelf.html create mode 100644 data/core.telegram.org/constructor/inputPeerUser.html create mode 100644 data/core.telegram.org/constructor/inputPeerUserFromMessage.html create mode 100644 data/core.telegram.org/constructor/inputPhoneCall.html create mode 100644 data/core.telegram.org/constructor/inputPhoneContact.html create mode 100644 data/core.telegram.org/constructor/inputPhoto.html create mode 100644 data/core.telegram.org/constructor/inputPhotoEmpty.html create mode 100644 data/core.telegram.org/constructor/inputPhotoFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyForwards.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowContacts.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonChildAbuse.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonCopyright.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonFake.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonOther.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonPornography.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonSpam.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonViolence.html create mode 100644 data/core.telegram.org/constructor/inputSecureFile.html create mode 100644 data/core.telegram.org/constructor/inputSecureFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputSecureFileUploaded.html create mode 100644 data/core.telegram.org/constructor/inputSecureValue.html create mode 100644 data/core.telegram.org/constructor/inputSingleMedia.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetAnimatedEmoji.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetDice.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetEmpty.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetID.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetItem.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetShortName.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetThumb.html create mode 100644 data/core.telegram.org/constructor/inputStickeredMediaDocument.html create mode 100644 data/core.telegram.org/constructor/inputStickeredMediaPhoto.html create mode 100644 data/core.telegram.org/constructor/inputTakeoutFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputTheme.html create mode 100644 data/core.telegram.org/constructor/inputThemeSettings.html create mode 100644 data/core.telegram.org/constructor/inputThemeSlug.html create mode 100644 data/core.telegram.org/constructor/inputUser.html create mode 100644 data/core.telegram.org/constructor/inputUserEmpty.html create mode 100644 data/core.telegram.org/constructor/inputUserFromMessage.html create mode 100644 data/core.telegram.org/constructor/inputUserSelf.html create mode 100644 data/core.telegram.org/constructor/inputWallPaper.html create mode 100644 data/core.telegram.org/constructor/inputWallPaperNoFile.html create mode 100644 data/core.telegram.org/constructor/inputWallPaperSlug.html create mode 100644 data/core.telegram.org/constructor/inputWebDocument.html create mode 100644 data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html create mode 100644 data/core.telegram.org/constructor/invoice.html create mode 100644 data/core.telegram.org/constructor/jsonArray.html create mode 100644 data/core.telegram.org/constructor/jsonBool.html create mode 100644 data/core.telegram.org/constructor/jsonNull.html create mode 100644 data/core.telegram.org/constructor/jsonNumber.html create mode 100644 data/core.telegram.org/constructor/jsonObject.html create mode 100644 data/core.telegram.org/constructor/jsonObjectValue.html create mode 100644 data/core.telegram.org/constructor/jsonString.html create mode 100644 data/core.telegram.org/constructor/keyboardButton.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonBuy.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonCallback.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonGame.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestPhone.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestPoll.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonRow.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonSwitchInline.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonUrl.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonUrlAuth.html create mode 100644 data/core.telegram.org/constructor/labeledPrice.html create mode 100644 data/core.telegram.org/constructor/langPackDifference.html create mode 100644 data/core.telegram.org/constructor/langPackLanguage.html create mode 100644 data/core.telegram.org/constructor/langPackStringDeleted.html create mode 100644 data/core.telegram.org/constructor/langPackStringPluralized.html create mode 100644 data/core.telegram.org/constructor/maskCoords.html create mode 100644 data/core.telegram.org/constructor/message.html create mode 100644 data/core.telegram.org/constructor/messageActionBotAllowed.html create mode 100644 data/core.telegram.org/constructor/messageActionChannelCreate.html create mode 100644 data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html create mode 100644 data/core.telegram.org/constructor/messageActionChatAddUser.html create mode 100644 data/core.telegram.org/constructor/messageActionChatCreate.html create mode 100644 data/core.telegram.org/constructor/messageActionChatDeletePhoto.html create mode 100644 data/core.telegram.org/constructor/messageActionChatDeleteUser.html create mode 100644 data/core.telegram.org/constructor/messageActionChatEditPhoto.html create mode 100644 data/core.telegram.org/constructor/messageActionChatEditTitle.html create mode 100644 data/core.telegram.org/constructor/messageActionChatJoinedByLink.html create mode 100644 data/core.telegram.org/constructor/messageActionChatMigrateTo.html create mode 100644 data/core.telegram.org/constructor/messageActionContactSignUp.html create mode 100644 data/core.telegram.org/constructor/messageActionCustomAction.html create mode 100644 data/core.telegram.org/constructor/messageActionEmpty.html create mode 100644 data/core.telegram.org/constructor/messageActionGameScore.html create mode 100644 data/core.telegram.org/constructor/messageActionGeoProximityReached.html create mode 100644 data/core.telegram.org/constructor/messageActionGroupCall.html create mode 100644 data/core.telegram.org/constructor/messageActionGroupCallScheduled.html create mode 100644 data/core.telegram.org/constructor/messageActionHistoryClear.html create mode 100644 data/core.telegram.org/constructor/messageActionInviteToGroupCall.html create mode 100644 data/core.telegram.org/constructor/messageActionPaymentSent.html create mode 100644 data/core.telegram.org/constructor/messageActionPaymentSentMe.html create mode 100644 data/core.telegram.org/constructor/messageActionPhoneCall.html create mode 100644 data/core.telegram.org/constructor/messageActionPinMessage.html create mode 100644 data/core.telegram.org/constructor/messageActionScreenshotTaken.html create mode 100644 data/core.telegram.org/constructor/messageActionSecureValuesSent.html create mode 100644 data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html create mode 100644 data/core.telegram.org/constructor/messageActionSetChatTheme.html create mode 100644 data/core.telegram.org/constructor/messageActionSetMessagesTTL.html create mode 100644 data/core.telegram.org/constructor/messageEmpty.html create mode 100644 data/core.telegram.org/constructor/messageEntityBankCard.html create mode 100644 data/core.telegram.org/constructor/messageEntityBlockquote.html create mode 100644 data/core.telegram.org/constructor/messageEntityBold.html create mode 100644 data/core.telegram.org/constructor/messageEntityBotCommand.html create mode 100644 data/core.telegram.org/constructor/messageEntityCashtag.html create mode 100644 data/core.telegram.org/constructor/messageEntityCode.html create mode 100644 data/core.telegram.org/constructor/messageEntityEmail.html create mode 100644 data/core.telegram.org/constructor/messageEntityHashtag.html create mode 100644 data/core.telegram.org/constructor/messageEntityItalic.html create mode 100644 data/core.telegram.org/constructor/messageEntityMention.html create mode 100644 data/core.telegram.org/constructor/messageEntityMentionName.html create mode 100644 data/core.telegram.org/constructor/messageEntityPhone.html create mode 100644 data/core.telegram.org/constructor/messageEntityPre.html create mode 100644 data/core.telegram.org/constructor/messageEntityTextUrl.html create mode 100644 data/core.telegram.org/constructor/messageEntityUnderline.html create mode 100644 data/core.telegram.org/constructor/messageEntityUnknown.html create mode 100644 data/core.telegram.org/constructor/messageEntityUrl.html create mode 100644 data/core.telegram.org/constructor/messageFwdHeader.html create mode 100644 data/core.telegram.org/constructor/messageInteractionCounters.html create mode 100644 data/core.telegram.org/constructor/messageMediaAudio.html create mode 100644 data/core.telegram.org/constructor/messageMediaContact.html create mode 100644 data/core.telegram.org/constructor/messageMediaDice.html create mode 100644 data/core.telegram.org/constructor/messageMediaDocument.html create mode 100644 data/core.telegram.org/constructor/messageMediaEmpty.html create mode 100644 data/core.telegram.org/constructor/messageMediaGame.html create mode 100644 data/core.telegram.org/constructor/messageMediaGeo.html create mode 100644 data/core.telegram.org/constructor/messageMediaGeoLive.html create mode 100644 data/core.telegram.org/constructor/messageMediaInvoice.html create mode 100644 data/core.telegram.org/constructor/messageMediaPhoto.html create mode 100644 data/core.telegram.org/constructor/messageMediaPoll.html create mode 100644 data/core.telegram.org/constructor/messageMediaUnsupported.html create mode 100644 data/core.telegram.org/constructor/messageMediaVenue.html create mode 100644 data/core.telegram.org/constructor/messageMediaVideo.html create mode 100644 data/core.telegram.org/constructor/messageMediaWebPage.html create mode 100644 data/core.telegram.org/constructor/messageRange.html create mode 100644 data/core.telegram.org/constructor/messageReplies.html create mode 100644 data/core.telegram.org/constructor/messageReplyHeader.html create mode 100644 data/core.telegram.org/constructor/messageService.html create mode 100644 data/core.telegram.org/constructor/messageUserVote.html create mode 100644 data/core.telegram.org/constructor/messageUserVoteInputOption.html create mode 100644 data/core.telegram.org/constructor/messageViews.html create mode 100644 data/core.telegram.org/constructor/messages.affectedFoundMessages create mode 100644 data/core.telegram.org/constructor/messages.affectedHistory create mode 100644 data/core.telegram.org/constructor/messages.affectedMessages create mode 100644 data/core.telegram.org/constructor/messages.allStickers create mode 100644 data/core.telegram.org/constructor/messages.allStickersNotModified create mode 100644 data/core.telegram.org/constructor/messages.archivedStickers create mode 100644 data/core.telegram.org/constructor/messages.botCallbackAnswer create mode 100644 data/core.telegram.org/constructor/messages.botResults create mode 100644 data/core.telegram.org/constructor/messages.channelMessages create mode 100644 data/core.telegram.org/constructor/messages.chatAdminsWithInvites create mode 100644 data/core.telegram.org/constructor/messages.chatFull create mode 100644 data/core.telegram.org/constructor/messages.chatInviteImporters create mode 100644 data/core.telegram.org/constructor/messages.chats create mode 100644 data/core.telegram.org/constructor/messages.chatsSlice create mode 100644 data/core.telegram.org/constructor/messages.checkedHistoryImportPeer create mode 100644 data/core.telegram.org/constructor/messages.dhConfig create mode 100644 data/core.telegram.org/constructor/messages.dhConfigNotModified create mode 100644 data/core.telegram.org/constructor/messages.dialogs create mode 100644 data/core.telegram.org/constructor/messages.dialogsNotModified create mode 100644 data/core.telegram.org/constructor/messages.dialogsSlice create mode 100644 data/core.telegram.org/constructor/messages.discussionMessage create mode 100644 data/core.telegram.org/constructor/messages.exportedChatInvite create mode 100644 data/core.telegram.org/constructor/messages.exportedChatInviteReplaced create mode 100644 data/core.telegram.org/constructor/messages.exportedChatInvites create mode 100644 data/core.telegram.org/constructor/messages.favedStickers create mode 100644 data/core.telegram.org/constructor/messages.favedStickersNotModified create mode 100644 data/core.telegram.org/constructor/messages.featuredStickers create mode 100644 data/core.telegram.org/constructor/messages.featuredStickersNotModified create mode 100644 data/core.telegram.org/constructor/messages.foundStickerSets create mode 100644 data/core.telegram.org/constructor/messages.foundStickerSetsNotModified create mode 100644 data/core.telegram.org/constructor/messages.highScores create mode 100644 data/core.telegram.org/constructor/messages.historyImport create mode 100644 data/core.telegram.org/constructor/messages.historyImportParsed create mode 100644 data/core.telegram.org/constructor/messages.inactiveChats create mode 100644 data/core.telegram.org/constructor/messages.messageEditData create mode 100644 data/core.telegram.org/constructor/messages.messageViews create mode 100644 data/core.telegram.org/constructor/messages.messages create mode 100644 data/core.telegram.org/constructor/messages.messagesNotModified create mode 100644 data/core.telegram.org/constructor/messages.messagesSlice create mode 100644 data/core.telegram.org/constructor/messages.peerDialogs create mode 100644 data/core.telegram.org/constructor/messages.recentStickers create mode 100644 data/core.telegram.org/constructor/messages.recentStickersNotModified create mode 100644 data/core.telegram.org/constructor/messages.savedGifs create mode 100644 data/core.telegram.org/constructor/messages.savedGifsNotModified create mode 100644 data/core.telegram.org/constructor/messages.searchCounter create mode 100644 data/core.telegram.org/constructor/messages.sentEncryptedFile create mode 100644 data/core.telegram.org/constructor/messages.sentEncryptedMessage create mode 100644 data/core.telegram.org/constructor/messages.sentMessageLink create mode 100644 data/core.telegram.org/constructor/messages.sponsoredMessages create mode 100644 data/core.telegram.org/constructor/messages.statedMessageLink create mode 100644 data/core.telegram.org/constructor/messages.statedMessagesLinks create mode 100644 data/core.telegram.org/constructor/messages.stickerSet create mode 100644 data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive create mode 100644 data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess create mode 100644 data/core.telegram.org/constructor/messages.stickers create mode 100644 data/core.telegram.org/constructor/messages.stickersNotModified create mode 100644 data/core.telegram.org/constructor/messages.votesList create mode 100644 data/core.telegram.org/constructor/nearestDc.html create mode 100644 data/core.telegram.org/constructor/notifyBroadcasts.html create mode 100644 data/core.telegram.org/constructor/notifyChats.html create mode 100644 data/core.telegram.org/constructor/notifyPeer.html create mode 100644 data/core.telegram.org/constructor/notifyUsers.html create mode 100644 data/core.telegram.org/constructor/null.html create mode 100644 data/core.telegram.org/constructor/page.html create mode 100644 data/core.telegram.org/constructor/pageBlockAnchor.html create mode 100644 data/core.telegram.org/constructor/pageBlockAudio.html create mode 100644 data/core.telegram.org/constructor/pageBlockAuthorDate.html create mode 100644 data/core.telegram.org/constructor/pageBlockBlockquote.html create mode 100644 data/core.telegram.org/constructor/pageBlockChannel.html create mode 100644 data/core.telegram.org/constructor/pageBlockCollage.html create mode 100644 data/core.telegram.org/constructor/pageBlockCover.html create mode 100644 data/core.telegram.org/constructor/pageBlockDetails.html create mode 100644 data/core.telegram.org/constructor/pageBlockDivider.html create mode 100644 data/core.telegram.org/constructor/pageBlockEmbed.html create mode 100644 data/core.telegram.org/constructor/pageBlockEmbedPost.html create mode 100644 data/core.telegram.org/constructor/pageBlockFooter.html create mode 100644 data/core.telegram.org/constructor/pageBlockHeader.html create mode 100644 data/core.telegram.org/constructor/pageBlockKicker.html create mode 100644 data/core.telegram.org/constructor/pageBlockList.html create mode 100644 data/core.telegram.org/constructor/pageBlockMap.html create mode 100644 data/core.telegram.org/constructor/pageBlockOrderedList.html create mode 100644 data/core.telegram.org/constructor/pageBlockParagraph.html create mode 100644 data/core.telegram.org/constructor/pageBlockPhoto.html create mode 100644 data/core.telegram.org/constructor/pageBlockPreformatted.html create mode 100644 data/core.telegram.org/constructor/pageBlockPullquote.html create mode 100644 data/core.telegram.org/constructor/pageBlockRelatedArticles.html create mode 100644 data/core.telegram.org/constructor/pageBlockSlideshow.html create mode 100644 data/core.telegram.org/constructor/pageBlockSubheader.html create mode 100644 data/core.telegram.org/constructor/pageBlockSubtitle.html create mode 100644 data/core.telegram.org/constructor/pageBlockTitle.html create mode 100644 data/core.telegram.org/constructor/pageBlockUnsupported.html create mode 100644 data/core.telegram.org/constructor/pageBlockVideo.html create mode 100644 data/core.telegram.org/constructor/pageCaption.html create mode 100644 data/core.telegram.org/constructor/pageListItemBlocks.html create mode 100644 data/core.telegram.org/constructor/pageListItemText.html create mode 100644 data/core.telegram.org/constructor/pageListOrderedItemBlocks.html create mode 100644 data/core.telegram.org/constructor/pageListOrderedItemText.html create mode 100644 data/core.telegram.org/constructor/pageRelatedArticle.html create mode 100644 data/core.telegram.org/constructor/pageTableCell.html create mode 100644 data/core.telegram.org/constructor/pageTableRow.html create mode 100644 data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html create mode 100644 data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html create mode 100644 data/core.telegram.org/constructor/paymentCharge.html create mode 100644 data/core.telegram.org/constructor/paymentRequestedInfo.html create mode 100644 data/core.telegram.org/constructor/paymentSavedCredentialsCard.html create mode 100644 data/core.telegram.org/constructor/payments.ValidatedRequestedInfo create mode 100644 data/core.telegram.org/constructor/payments.bankCardData create mode 100644 data/core.telegram.org/constructor/payments.paymentForm create mode 100644 data/core.telegram.org/constructor/payments.paymentReceipt create mode 100644 data/core.telegram.org/constructor/payments.paymentResult create mode 100644 data/core.telegram.org/constructor/payments.paymentVerificationNeeded create mode 100644 data/core.telegram.org/constructor/payments.savedInfo create mode 100644 data/core.telegram.org/constructor/peerBlocked.html create mode 100644 data/core.telegram.org/constructor/peerChannel.html create mode 100644 data/core.telegram.org/constructor/peerChat.html create mode 100644 data/core.telegram.org/constructor/peerLocated.html create mode 100644 data/core.telegram.org/constructor/peerNotifySettings.html create mode 100644 data/core.telegram.org/constructor/peerSelfLocated.html create mode 100644 data/core.telegram.org/constructor/peerSettings.html create mode 100644 data/core.telegram.org/constructor/phone.exportedGroupCallInvite create mode 100644 data/core.telegram.org/constructor/phone.groupCall create mode 100644 data/core.telegram.org/constructor/phone.groupParticipants create mode 100644 data/core.telegram.org/constructor/phone.joinAsPeers create mode 100644 data/core.telegram.org/constructor/phone.phoneCall create mode 100644 data/core.telegram.org/constructor/phoneCall.html create mode 100644 data/core.telegram.org/constructor/phoneCallAccepted.html create mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html create mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html create mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html create mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html create mode 100644 data/core.telegram.org/constructor/phoneCallDiscarded.html create mode 100644 data/core.telegram.org/constructor/phoneCallEmpty.html create mode 100644 data/core.telegram.org/constructor/phoneCallProtocol.html create mode 100644 data/core.telegram.org/constructor/phoneCallRequested.html create mode 100644 data/core.telegram.org/constructor/phoneCallWaiting.html create mode 100644 data/core.telegram.org/constructor/phoneConnection.html create mode 100644 data/core.telegram.org/constructor/phoneConnectionWebrtc.html create mode 100644 data/core.telegram.org/constructor/photo.html create mode 100644 data/core.telegram.org/constructor/photoCachedSize.html create mode 100644 data/core.telegram.org/constructor/photoPathSize.html create mode 100644 data/core.telegram.org/constructor/photoSize.html create mode 100644 data/core.telegram.org/constructor/photoSizeEmpty.html create mode 100644 data/core.telegram.org/constructor/photoSizeProgressive.html create mode 100644 data/core.telegram.org/constructor/photoStrippedSize.html create mode 100644 data/core.telegram.org/constructor/photos.photo create mode 100644 data/core.telegram.org/constructor/photos.photos create mode 100644 data/core.telegram.org/constructor/photos.photosSlice create mode 100644 data/core.telegram.org/constructor/poll.html create mode 100644 data/core.telegram.org/constructor/pollAnswer.html create mode 100644 data/core.telegram.org/constructor/pollAnswerVoters.html create mode 100644 data/core.telegram.org/constructor/pollResults.html create mode 100644 data/core.telegram.org/constructor/popularContact.html create mode 100644 data/core.telegram.org/constructor/postAddress.html create mode 100644 data/core.telegram.org/constructor/privacyKeyAddedByPhone.html create mode 100644 data/core.telegram.org/constructor/privacyKeyChatInvite.html create mode 100644 data/core.telegram.org/constructor/privacyKeyForwards.html create mode 100644 data/core.telegram.org/constructor/privacyKeyPhoneCall.html create mode 100644 data/core.telegram.org/constructor/privacyKeyPhoneP2P.html create mode 100644 data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html create mode 100644 data/core.telegram.org/constructor/privacyValueAllowAll.html create mode 100644 data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html create mode 100644 data/core.telegram.org/constructor/privacyValueAllowContacts.html create mode 100644 data/core.telegram.org/constructor/privacyValueDisallowChatParticipants.html create mode 100644 data/core.telegram.org/constructor/privacyValueDisallowContacts.html create mode 100644 data/core.telegram.org/constructor/privacyValueDisallowUsers.html create mode 100644 data/core.telegram.org/constructor/receivedNotifyMessage.html create mode 100644 data/core.telegram.org/constructor/recentMeUrlChat.html create mode 100644 data/core.telegram.org/constructor/recentMeUrlChatInvite.html create mode 100644 data/core.telegram.org/constructor/recentMeUrlStickerSet.html create mode 100644 data/core.telegram.org/constructor/recentMeUrlUnknown.html create mode 100644 data/core.telegram.org/constructor/recentMeUrlUser.html create mode 100644 data/core.telegram.org/constructor/replyInlineMarkup.html create mode 100644 data/core.telegram.org/constructor/replyKeyboardForceReply.html create mode 100644 data/core.telegram.org/constructor/replyKeyboardHide.html create mode 100644 data/core.telegram.org/constructor/restrictionReason.html create mode 100644 data/core.telegram.org/constructor/savedPhoneContact.html create mode 100644 data/core.telegram.org/constructor/secureCredentialsEncrypted.html create mode 100644 data/core.telegram.org/constructor/secureData.html create mode 100644 data/core.telegram.org/constructor/secureFile.html create mode 100644 data/core.telegram.org/constructor/secureFileEmpty.html create mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html create mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html create mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html create mode 100644 data/core.telegram.org/constructor/securePlainEmail.html create mode 100644 data/core.telegram.org/constructor/securePlainPhone.html create mode 100644 data/core.telegram.org/constructor/secureRequiredType.html create mode 100644 data/core.telegram.org/constructor/secureRequiredTypeOneOf.html create mode 100644 data/core.telegram.org/constructor/secureSecretSettings.html create mode 100644 data/core.telegram.org/constructor/secureValue.html create mode 100644 data/core.telegram.org/constructor/secureValueError.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorData.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorFile.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorFiles.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorFrontSide.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorReverseSide.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorSelfie.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorTranslationFile.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html create mode 100644 data/core.telegram.org/constructor/secureValueHash.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeAddress.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeBankStatement.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeDriverLicense.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeEmail.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeIdentityCard.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeInternalPassport.html create mode 100644 data/core.telegram.org/constructor/secureValueTypePassport.html create mode 100644 data/core.telegram.org/constructor/secureValueTypePassportRegistration.html create mode 100644 data/core.telegram.org/constructor/secureValueTypePersonalDetails.html create mode 100644 data/core.telegram.org/constructor/secureValueTypePhone.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeUtilityBill.html create mode 100644 data/core.telegram.org/constructor/sendMessageCancelAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageChooseContactAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageChooseStickerAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageEmojiInteraction.html create mode 100644 data/core.telegram.org/constructor/sendMessageEmojiInteractionSeen.html create mode 100644 data/core.telegram.org/constructor/sendMessageGamePlayAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageGeoLocationAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageHistoryImportAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageRecordAudioAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageRecordRoundAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageRecordVideoAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageTypingAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageUploadAudioAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageUploadRoundAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageUploadVideoAction.html create mode 100644 data/core.telegram.org/constructor/shippingOption.html create mode 100644 data/core.telegram.org/constructor/speakingInGroupCallAction.html create mode 100644 data/core.telegram.org/constructor/sponsoredMessage.html create mode 100644 data/core.telegram.org/constructor/stats.broadcastStats create mode 100644 data/core.telegram.org/constructor/stats.megagroupStats create mode 100644 data/core.telegram.org/constructor/stats.messageStats create mode 100644 data/core.telegram.org/constructor/statsAbsValueAndPrev.html create mode 100644 data/core.telegram.org/constructor/statsDateRangeDays.html create mode 100644 data/core.telegram.org/constructor/statsGraph.html create mode 100644 data/core.telegram.org/constructor/statsGraphAsync.html create mode 100644 data/core.telegram.org/constructor/statsGraphError.html create mode 100644 data/core.telegram.org/constructor/statsGroupTopAdmin.html create mode 100644 data/core.telegram.org/constructor/statsGroupTopPoster.html create mode 100644 data/core.telegram.org/constructor/statsPercentValue.html create mode 100644 data/core.telegram.org/constructor/statsURL.html create mode 100644 data/core.telegram.org/constructor/stickerPack.html create mode 100644 data/core.telegram.org/constructor/stickerSet.html create mode 100644 data/core.telegram.org/constructor/stickerSetCovered.html create mode 100644 data/core.telegram.org/constructor/stickerSetMultiCovered.html create mode 100644 data/core.telegram.org/constructor/stickers.suggestedShortName create mode 100644 data/core.telegram.org/constructor/storage.fileGif create mode 100644 data/core.telegram.org/constructor/storage.fileJpeg create mode 100644 data/core.telegram.org/constructor/storage.fileMov create mode 100644 data/core.telegram.org/constructor/storage.fileMp3 create mode 100644 data/core.telegram.org/constructor/storage.fileMp4 create mode 100644 data/core.telegram.org/constructor/storage.filePartial create mode 100644 data/core.telegram.org/constructor/storage.filePdf create mode 100644 data/core.telegram.org/constructor/storage.filePng create mode 100644 data/core.telegram.org/constructor/storage.fileUnknown create mode 100644 data/core.telegram.org/constructor/storage.fileWebp create mode 100644 data/core.telegram.org/constructor/textAnchor.html create mode 100644 data/core.telegram.org/constructor/textBold.html create mode 100644 data/core.telegram.org/constructor/textConcat.html create mode 100644 data/core.telegram.org/constructor/textEmail.html create mode 100644 data/core.telegram.org/constructor/textEmpty.html create mode 100644 data/core.telegram.org/constructor/textFixed.html create mode 100644 data/core.telegram.org/constructor/textImage.html create mode 100644 data/core.telegram.org/constructor/textItalic.html create mode 100644 data/core.telegram.org/constructor/textMarked.html create mode 100644 data/core.telegram.org/constructor/textPhone.html create mode 100644 data/core.telegram.org/constructor/textPlain.html create mode 100644 data/core.telegram.org/constructor/textStrike.html create mode 100644 data/core.telegram.org/constructor/textSubscript.html create mode 100644 data/core.telegram.org/constructor/textSuperscript.html create mode 100644 data/core.telegram.org/constructor/textUnderline.html create mode 100644 data/core.telegram.org/constructor/textUrl.html create mode 100644 data/core.telegram.org/constructor/themeSettings.html create mode 100644 data/core.telegram.org/constructor/topPeer.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryBotsInline.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryBotsPM.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryChannels.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryForwardChats.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryGroups.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryPeers.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html create mode 100644 data/core.telegram.org/constructor/true.html create mode 100644 data/core.telegram.org/constructor/updateBotCallbackQuery.html create mode 100644 data/core.telegram.org/constructor/updateBotCommands.html create mode 100644 data/core.telegram.org/constructor/updateBotInlineQuery.html create mode 100644 data/core.telegram.org/constructor/updateBotInlineSend.html create mode 100644 data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html create mode 100644 data/core.telegram.org/constructor/updateBotShippingQuery.html create mode 100644 data/core.telegram.org/constructor/updateBotStopped.html create mode 100644 data/core.telegram.org/constructor/updateBotWebhookJSON.html create mode 100644 data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html create mode 100644 data/core.telegram.org/constructor/updateChannel.html create mode 100644 data/core.telegram.org/constructor/updateChannelAvailableMessages.html create mode 100644 data/core.telegram.org/constructor/updateChannelMessageViews.html create mode 100644 data/core.telegram.org/constructor/updateChannelParticipant.html create mode 100644 data/core.telegram.org/constructor/updateChannelReadMessagesContents.html create mode 100644 data/core.telegram.org/constructor/updateChannelTooLong.html create mode 100644 data/core.telegram.org/constructor/updateChannelUserTyping.html create mode 100644 data/core.telegram.org/constructor/updateChannelWebPage.html create mode 100644 data/core.telegram.org/constructor/updateChat.html create mode 100644 data/core.telegram.org/constructor/updateChatDefaultBannedRights.html create mode 100644 data/core.telegram.org/constructor/updateChatParticipant.html create mode 100644 data/core.telegram.org/constructor/updateChatParticipantAdd.html create mode 100644 data/core.telegram.org/constructor/updateChatParticipantAdmin.html create mode 100644 data/core.telegram.org/constructor/updateChatParticipantDelete.html create mode 100644 data/core.telegram.org/constructor/updateChatParticipants.html create mode 100644 data/core.telegram.org/constructor/updateChatUserTyping.html create mode 100644 data/core.telegram.org/constructor/updateConfig.html create mode 100644 data/core.telegram.org/constructor/updateContactsReset.html create mode 100644 data/core.telegram.org/constructor/updateDcOptions.html create mode 100644 data/core.telegram.org/constructor/updateDeleteChannelMessages.html create mode 100644 data/core.telegram.org/constructor/updateDeleteMessages.html create mode 100644 data/core.telegram.org/constructor/updateDeleteScheduledMessages.html create mode 100644 data/core.telegram.org/constructor/updateDialogFilter.html create mode 100644 data/core.telegram.org/constructor/updateDialogFilterOrder.html create mode 100644 data/core.telegram.org/constructor/updateDialogFilters.html create mode 100644 data/core.telegram.org/constructor/updateDialogPinned.html create mode 100644 data/core.telegram.org/constructor/updateDialogUnreadMark.html create mode 100644 data/core.telegram.org/constructor/updateDraftMessage.html create mode 100644 data/core.telegram.org/constructor/updateEditChannelMessage.html create mode 100644 data/core.telegram.org/constructor/updateEditMessage.html create mode 100644 data/core.telegram.org/constructor/updateEncryptedChatTyping.html create mode 100644 data/core.telegram.org/constructor/updateEncryptedMessagesRead.html create mode 100644 data/core.telegram.org/constructor/updateEncryption.html create mode 100644 data/core.telegram.org/constructor/updateFavedStickers.html create mode 100644 data/core.telegram.org/constructor/updateFolderPeers.html create mode 100644 data/core.telegram.org/constructor/updateGeoLiveViewed.html create mode 100644 data/core.telegram.org/constructor/updateGroupCall.html create mode 100644 data/core.telegram.org/constructor/updateGroupCallConnection.html create mode 100644 data/core.telegram.org/constructor/updateGroupCallParticipants.html create mode 100644 data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html create mode 100644 data/core.telegram.org/constructor/updateLangPack.html create mode 100644 data/core.telegram.org/constructor/updateLangPackTooLong.html create mode 100644 data/core.telegram.org/constructor/updateLoginToken.html create mode 100644 data/core.telegram.org/constructor/updateMessageID.html create mode 100644 data/core.telegram.org/constructor/updateMessagePoll.html create mode 100644 data/core.telegram.org/constructor/updateMessagePollVote.html create mode 100644 data/core.telegram.org/constructor/updateNewChannelMessage.html create mode 100644 data/core.telegram.org/constructor/updateNewEncryptedMessage.html create mode 100644 data/core.telegram.org/constructor/updateNewMessage.html create mode 100644 data/core.telegram.org/constructor/updateNewScheduledMessage.html create mode 100644 data/core.telegram.org/constructor/updateNewStickerSet.html create mode 100644 data/core.telegram.org/constructor/updateNotifySettings.html create mode 100644 data/core.telegram.org/constructor/updatePeerBlocked.html create mode 100644 data/core.telegram.org/constructor/updatePeerHistoryTTL.html create mode 100644 data/core.telegram.org/constructor/updatePeerLocated.html create mode 100644 data/core.telegram.org/constructor/updatePeerSettings.html create mode 100644 data/core.telegram.org/constructor/updatePhoneCall.html create mode 100644 data/core.telegram.org/constructor/updatePhoneCallSignalingData.html create mode 100644 data/core.telegram.org/constructor/updatePinnedChannelMessages.html create mode 100644 data/core.telegram.org/constructor/updatePinnedDialogs.html create mode 100644 data/core.telegram.org/constructor/updatePinnedMessages.html create mode 100644 data/core.telegram.org/constructor/updatePrivacy.html create mode 100644 data/core.telegram.org/constructor/updatePtsChanged.html create mode 100644 data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html create mode 100644 data/core.telegram.org/constructor/updateReadChannelInbox.html create mode 100644 data/core.telegram.org/constructor/updateReadChannelOutbox.html create mode 100644 data/core.telegram.org/constructor/updateReadFeaturedStickers.html create mode 100644 data/core.telegram.org/constructor/updateReadHistoryInbox.html create mode 100644 data/core.telegram.org/constructor/updateReadHistoryOutbox.html create mode 100644 data/core.telegram.org/constructor/updateReadMessagesContents.html create mode 100644 data/core.telegram.org/constructor/updateRecentStickers.html create mode 100644 data/core.telegram.org/constructor/updateSavedGifs.html create mode 100644 data/core.telegram.org/constructor/updateServiceNotification.html create mode 100644 data/core.telegram.org/constructor/updateShort.html create mode 100644 data/core.telegram.org/constructor/updateShortMessage.html create mode 100644 data/core.telegram.org/constructor/updateShortSentMessage.html create mode 100644 data/core.telegram.org/constructor/updateStickerSets.html create mode 100644 data/core.telegram.org/constructor/updateStickerSetsOrder.html create mode 100644 data/core.telegram.org/constructor/updateTheme.html create mode 100644 data/core.telegram.org/constructor/updateUserBlocked.html create mode 100644 data/core.telegram.org/constructor/updateUserName.html create mode 100644 data/core.telegram.org/constructor/updateUserPhone.html create mode 100644 data/core.telegram.org/constructor/updateUserPhoto.html create mode 100644 data/core.telegram.org/constructor/updateUserStatus.html create mode 100644 data/core.telegram.org/constructor/updateUserTyping.html create mode 100644 data/core.telegram.org/constructor/updateWebPage.html create mode 100644 data/core.telegram.org/constructor/updates.channelDifference create mode 100644 data/core.telegram.org/constructor/updates.channelDifferenceEmpty create mode 100644 data/core.telegram.org/constructor/updates.channelDifferenceTooLong create mode 100644 data/core.telegram.org/constructor/updates.difference create mode 100644 data/core.telegram.org/constructor/updates.differenceEmpty create mode 100644 data/core.telegram.org/constructor/updates.differenceSlice create mode 100644 data/core.telegram.org/constructor/updates.differenceTooLong create mode 100644 data/core.telegram.org/constructor/updates.html create mode 100644 data/core.telegram.org/constructor/updates.state create mode 100644 data/core.telegram.org/constructor/updatesCombined.html create mode 100644 data/core.telegram.org/constructor/updatesTooLong.html create mode 100644 data/core.telegram.org/constructor/upload.cdnFile create mode 100644 data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded create mode 100644 data/core.telegram.org/constructor/upload.file create mode 100644 data/core.telegram.org/constructor/upload.fileCdnRedirect create mode 100644 data/core.telegram.org/constructor/upload.webFile create mode 100644 data/core.telegram.org/constructor/urlAuthResultAccepted.html create mode 100644 data/core.telegram.org/constructor/urlAuthResultDefault.html create mode 100644 data/core.telegram.org/constructor/urlAuthResultRequest.html create mode 100644 data/core.telegram.org/constructor/user.html create mode 100644 data/core.telegram.org/constructor/userEmpty.html create mode 100644 data/core.telegram.org/constructor/userFull.html create mode 100644 data/core.telegram.org/constructor/userProfilePhoto.html create mode 100644 data/core.telegram.org/constructor/userProfilePhotoEmpty.html create mode 100644 data/core.telegram.org/constructor/userStatusEmpty.html create mode 100644 data/core.telegram.org/constructor/userStatusLastMonth.html create mode 100644 data/core.telegram.org/constructor/userStatusLastWeek.html create mode 100644 data/core.telegram.org/constructor/userStatusOffline.html create mode 100644 data/core.telegram.org/constructor/userStatusOnline.html create mode 100644 data/core.telegram.org/constructor/userStatusRecently.html create mode 100644 data/core.telegram.org/constructor/vector.html create mode 100644 data/core.telegram.org/constructor/videoSize.html create mode 100644 data/core.telegram.org/constructor/wallPaper.html create mode 100644 data/core.telegram.org/constructor/wallPaperNoFile.html create mode 100644 data/core.telegram.org/constructor/wallPaperSettings.html create mode 100644 data/core.telegram.org/constructor/wallPaperSolid.html create mode 100644 data/core.telegram.org/constructor/webAuthorization.html create mode 100644 data/core.telegram.org/constructor/webDocument.html create mode 100644 data/core.telegram.org/constructor/webDocumentNoProxy.html create mode 100644 data/core.telegram.org/constructor/webPage.html create mode 100644 data/core.telegram.org/constructor/webPageAttributeTheme.html create mode 100644 data/core.telegram.org/constructor/webPageEmpty.html create mode 100644 data/core.telegram.org/constructor/webPageNotModified.html create mode 100644 data/core.telegram.org/constructor/webPagePending.html create mode 100644 data/core.telegram.org/contest300K.html create mode 100644 data/core.telegram.org/import-stickers.html create mode 100644 data/core.telegram.org/method/account.acceptAuthorization create mode 100644 data/core.telegram.org/method/account.cancelPasswordEmail create mode 100644 data/core.telegram.org/method/account.changePhone create mode 100644 data/core.telegram.org/method/account.checkUsername create mode 100644 data/core.telegram.org/method/account.confirmPasswordEmail create mode 100644 data/core.telegram.org/method/account.confirmPhone create mode 100644 data/core.telegram.org/method/account.createTheme create mode 100644 data/core.telegram.org/method/account.declinePasswordReset create mode 100644 data/core.telegram.org/method/account.deleteAccount create mode 100644 data/core.telegram.org/method/account.deleteSecureValue create mode 100644 data/core.telegram.org/method/account.finishTakeoutSession create mode 100644 data/core.telegram.org/method/account.getAccountTTL create mode 100644 data/core.telegram.org/method/account.getAllSecureValues create mode 100644 data/core.telegram.org/method/account.getAuthorizationForm create mode 100644 data/core.telegram.org/method/account.getAuthorizations create mode 100644 data/core.telegram.org/method/account.getAutoDownloadSettings create mode 100644 data/core.telegram.org/method/account.getChatThemes create mode 100644 data/core.telegram.org/method/account.getContactSignUpNotification create mode 100644 data/core.telegram.org/method/account.getContentSettings create mode 100644 data/core.telegram.org/method/account.getGlobalPrivacySettings create mode 100644 data/core.telegram.org/method/account.getMultiWallPapers create mode 100644 data/core.telegram.org/method/account.getNotifyExceptions create mode 100644 data/core.telegram.org/method/account.getNotifySettings create mode 100644 data/core.telegram.org/method/account.getPasswordSettings create mode 100644 data/core.telegram.org/method/account.getPrivacy create mode 100644 data/core.telegram.org/method/account.getSecureValue create mode 100644 data/core.telegram.org/method/account.getTheme create mode 100644 data/core.telegram.org/method/account.getThemes create mode 100644 data/core.telegram.org/method/account.getTmpPassword create mode 100644 data/core.telegram.org/method/account.getWallPaper create mode 100644 data/core.telegram.org/method/account.getWallPapers create mode 100644 data/core.telegram.org/method/account.getWebAuthorizations create mode 100644 data/core.telegram.org/method/account.initTakeoutSession create mode 100644 data/core.telegram.org/method/account.installTheme create mode 100644 data/core.telegram.org/method/account.installWallPaper create mode 100644 data/core.telegram.org/method/account.registerDevice create mode 100644 data/core.telegram.org/method/account.reportPeer create mode 100644 data/core.telegram.org/method/account.reportProfilePhoto create mode 100644 data/core.telegram.org/method/account.resendPasswordEmail create mode 100644 data/core.telegram.org/method/account.resetAuthorization create mode 100644 data/core.telegram.org/method/account.resetNotifySettings create mode 100644 data/core.telegram.org/method/account.resetPassword create mode 100644 data/core.telegram.org/method/account.resetWallPapers create mode 100644 data/core.telegram.org/method/account.resetWebAuthorization create mode 100644 data/core.telegram.org/method/account.resetWebAuthorizations create mode 100644 data/core.telegram.org/method/account.saveAutoDownloadSettings create mode 100644 data/core.telegram.org/method/account.saveSecureValue create mode 100644 data/core.telegram.org/method/account.saveTheme create mode 100644 data/core.telegram.org/method/account.saveWallPaper create mode 100644 data/core.telegram.org/method/account.sendChangePhoneCode create mode 100644 data/core.telegram.org/method/account.sendConfirmPhoneCode create mode 100644 data/core.telegram.org/method/account.sendVerifyEmailCode create mode 100644 data/core.telegram.org/method/account.sendVerifyPhoneCode create mode 100644 data/core.telegram.org/method/account.setAccountTTL create mode 100644 data/core.telegram.org/method/account.setContactSignUpNotification create mode 100644 data/core.telegram.org/method/account.setContentSettings create mode 100644 data/core.telegram.org/method/account.setGlobalPrivacySettings create mode 100644 data/core.telegram.org/method/account.setPrivacy create mode 100644 data/core.telegram.org/method/account.unregisterDevice create mode 100644 data/core.telegram.org/method/account.updateDeviceLocked create mode 100644 data/core.telegram.org/method/account.updateNotifySettings create mode 100644 data/core.telegram.org/method/account.updatePasswordSettings create mode 100644 data/core.telegram.org/method/account.updateProfile create mode 100644 data/core.telegram.org/method/account.updateStatus create mode 100644 data/core.telegram.org/method/account.updateTheme create mode 100644 data/core.telegram.org/method/account.updateUsername create mode 100644 data/core.telegram.org/method/account.uploadTheme create mode 100644 data/core.telegram.org/method/account.uploadWallPaper create mode 100644 data/core.telegram.org/method/account.verifyEmail create mode 100644 data/core.telegram.org/method/account.verifyPhone create mode 100644 data/core.telegram.org/method/auth.acceptLoginToken create mode 100644 data/core.telegram.org/method/auth.bindTempAuthKey create mode 100644 data/core.telegram.org/method/auth.cancelCode create mode 100644 data/core.telegram.org/method/auth.checkPassword create mode 100644 data/core.telegram.org/method/auth.checkPhone create mode 100644 data/core.telegram.org/method/auth.checkRecoveryPassword create mode 100644 data/core.telegram.org/method/auth.dropTempAuthKeys create mode 100644 data/core.telegram.org/method/auth.exportAuthorization create mode 100644 data/core.telegram.org/method/auth.exportLoginToken create mode 100644 data/core.telegram.org/method/auth.importAuthorization create mode 100644 data/core.telegram.org/method/auth.importBotAuthorization create mode 100644 data/core.telegram.org/method/auth.importLoginToken create mode 100644 data/core.telegram.org/method/auth.logOut create mode 100644 data/core.telegram.org/method/auth.recoverPassword create mode 100644 data/core.telegram.org/method/auth.requestPasswordRecovery create mode 100644 data/core.telegram.org/method/auth.resendCode create mode 100644 data/core.telegram.org/method/auth.resetAuthorizations create mode 100644 data/core.telegram.org/method/auth.sendCall create mode 100644 data/core.telegram.org/method/auth.sendCode create mode 100644 data/core.telegram.org/method/auth.sendInvites create mode 100644 data/core.telegram.org/method/auth.sendSms create mode 100644 data/core.telegram.org/method/auth.signIn create mode 100644 data/core.telegram.org/method/auth.signUp create mode 100644 data/core.telegram.org/method/bots.answerWebhookJSONQuery create mode 100644 data/core.telegram.org/method/bots.getBotCommands create mode 100644 data/core.telegram.org/method/bots.resetBotCommands create mode 100644 data/core.telegram.org/method/bots.sendCustomRequest create mode 100644 data/core.telegram.org/method/bots.setBotCommands create mode 100644 data/core.telegram.org/method/channels.checkUsername create mode 100644 data/core.telegram.org/method/channels.convertToGigagroup create mode 100644 data/core.telegram.org/method/channels.createChannel create mode 100644 data/core.telegram.org/method/channels.deleteChannel create mode 100644 data/core.telegram.org/method/channels.deleteHistory create mode 100644 data/core.telegram.org/method/channels.deleteMessages create mode 100644 data/core.telegram.org/method/channels.deleteUserHistory create mode 100644 data/core.telegram.org/method/channels.editAdmin create mode 100644 data/core.telegram.org/method/channels.editBanned create mode 100644 data/core.telegram.org/method/channels.editCreator create mode 100644 data/core.telegram.org/method/channels.editLocation create mode 100644 data/core.telegram.org/method/channels.editPhoto create mode 100644 data/core.telegram.org/method/channels.editTitle create mode 100644 data/core.telegram.org/method/channels.exportMessageLink create mode 100644 data/core.telegram.org/method/channels.getAdminLog create mode 100644 data/core.telegram.org/method/channels.getAdminedPublicChannels create mode 100644 data/core.telegram.org/method/channels.getChannels create mode 100644 data/core.telegram.org/method/channels.getFullChannel create mode 100644 data/core.telegram.org/method/channels.getGroupsForDiscussion create mode 100644 data/core.telegram.org/method/channels.getInactiveChannels create mode 100644 data/core.telegram.org/method/channels.getLeftChannels create mode 100644 data/core.telegram.org/method/channels.getMessages create mode 100644 data/core.telegram.org/method/channels.getParticipant create mode 100644 data/core.telegram.org/method/channels.getParticipants create mode 100644 data/core.telegram.org/method/channels.getSponsoredMessages create mode 100644 data/core.telegram.org/method/channels.inviteToChannel create mode 100644 data/core.telegram.org/method/channels.joinChannel create mode 100644 data/core.telegram.org/method/channels.leaveChannel create mode 100644 data/core.telegram.org/method/channels.readHistory create mode 100644 data/core.telegram.org/method/channels.readMessageContents create mode 100644 data/core.telegram.org/method/channels.setDiscussionGroup create mode 100644 data/core.telegram.org/method/channels.setStickers create mode 100644 data/core.telegram.org/method/channels.togglePreHistoryHidden create mode 100644 data/core.telegram.org/method/channels.toggleSignatures create mode 100644 data/core.telegram.org/method/channels.toggleSlowMode create mode 100644 data/core.telegram.org/method/channels.updateUsername create mode 100644 data/core.telegram.org/method/contacts.acceptContact create mode 100644 data/core.telegram.org/method/contacts.addContact create mode 100644 data/core.telegram.org/method/contacts.block create mode 100644 data/core.telegram.org/method/contacts.blockFromReplies create mode 100644 data/core.telegram.org/method/contacts.deleteByPhones create mode 100644 data/core.telegram.org/method/contacts.deleteContacts create mode 100644 data/core.telegram.org/method/contacts.getBlocked create mode 100644 data/core.telegram.org/method/contacts.getContactIDs create mode 100644 data/core.telegram.org/method/contacts.getContacts create mode 100644 data/core.telegram.org/method/contacts.getLocated create mode 100644 data/core.telegram.org/method/contacts.getSaved create mode 100644 data/core.telegram.org/method/contacts.getStatuses create mode 100644 data/core.telegram.org/method/contacts.getTopPeers create mode 100644 data/core.telegram.org/method/contacts.importContacts create mode 100644 data/core.telegram.org/method/contacts.resetSaved create mode 100644 data/core.telegram.org/method/contacts.resetTopPeerRating create mode 100644 data/core.telegram.org/method/contacts.resolveUsername create mode 100644 data/core.telegram.org/method/contacts.search create mode 100644 data/core.telegram.org/method/contacts.toggleTopPeers create mode 100644 data/core.telegram.org/method/contacts.unblock create mode 100644 data/core.telegram.org/method/folders.deleteFolder create mode 100644 data/core.telegram.org/method/folders.editPeerFolders create mode 100644 data/core.telegram.org/method/help.acceptTermsOfService create mode 100644 data/core.telegram.org/method/help.dismissSuggestion create mode 100644 data/core.telegram.org/method/help.editUserInfo create mode 100644 data/core.telegram.org/method/help.getAppChangelog create mode 100644 data/core.telegram.org/method/help.getAppConfig create mode 100644 data/core.telegram.org/method/help.getAppUpdate create mode 100644 data/core.telegram.org/method/help.getCdnConfig create mode 100644 data/core.telegram.org/method/help.getConfig create mode 100644 data/core.telegram.org/method/help.getCountriesList create mode 100644 data/core.telegram.org/method/help.getDeepLinkInfo create mode 100644 data/core.telegram.org/method/help.getInviteText create mode 100644 data/core.telegram.org/method/help.getNearestDc create mode 100644 data/core.telegram.org/method/help.getPassportConfig create mode 100644 data/core.telegram.org/method/help.getPromoData create mode 100644 data/core.telegram.org/method/help.getProxyData create mode 100644 data/core.telegram.org/method/help.getRecentMeUrls create mode 100644 data/core.telegram.org/method/help.getSupport create mode 100644 data/core.telegram.org/method/help.getSupportName create mode 100644 data/core.telegram.org/method/help.getTermsOfServiceUpdate create mode 100644 data/core.telegram.org/method/help.getUserInfo create mode 100644 data/core.telegram.org/method/help.hidePromoData create mode 100644 data/core.telegram.org/method/help.saveAppLog create mode 100644 data/core.telegram.org/method/help.setBotUpdatesStatus create mode 100644 data/core.telegram.org/method/initConnection.html create mode 100644 data/core.telegram.org/method/invokeAfterMsg.html create mode 100644 data/core.telegram.org/method/invokeAfterMsgs.html create mode 100644 data/core.telegram.org/method/invokeWithLayer.html create mode 100644 data/core.telegram.org/method/invokeWithMessagesRange.html create mode 100644 data/core.telegram.org/method/invokeWithTakeout.html create mode 100644 data/core.telegram.org/method/invokeWithoutUpdates.html create mode 100644 data/core.telegram.org/method/langpack.getDifference create mode 100644 data/core.telegram.org/method/langpack.getLangPack create mode 100644 data/core.telegram.org/method/langpack.getLanguage create mode 100644 data/core.telegram.org/method/langpack.getLanguages create mode 100644 data/core.telegram.org/method/langpack.getStrings create mode 100644 data/core.telegram.org/method/messages.acceptEncryption create mode 100644 data/core.telegram.org/method/messages.addChatUser create mode 100644 data/core.telegram.org/method/messages.checkChatInvite create mode 100644 data/core.telegram.org/method/messages.checkHistoryImport create mode 100644 data/core.telegram.org/method/messages.checkHistoryImportPeer create mode 100644 data/core.telegram.org/method/messages.clearAllDrafts create mode 100644 data/core.telegram.org/method/messages.clearRecentStickers create mode 100644 data/core.telegram.org/method/messages.createChat create mode 100644 data/core.telegram.org/method/messages.deleteChat create mode 100644 data/core.telegram.org/method/messages.deleteChatUser create mode 100644 data/core.telegram.org/method/messages.deleteExportedChatInvite create mode 100644 data/core.telegram.org/method/messages.deleteHistory create mode 100644 data/core.telegram.org/method/messages.deleteMessages create mode 100644 data/core.telegram.org/method/messages.deletePhoneCallHistory create mode 100644 data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites create mode 100644 data/core.telegram.org/method/messages.deleteScheduledMessages create mode 100644 data/core.telegram.org/method/messages.discardEncryption create mode 100644 data/core.telegram.org/method/messages.editChatAbout create mode 100644 data/core.telegram.org/method/messages.editChatAdmin create mode 100644 data/core.telegram.org/method/messages.editChatDefaultBannedRights create mode 100644 data/core.telegram.org/method/messages.editChatPhoto create mode 100644 data/core.telegram.org/method/messages.editChatTitle create mode 100644 data/core.telegram.org/method/messages.editExportedChatInvite create mode 100644 data/core.telegram.org/method/messages.editInlineBotMessage create mode 100644 data/core.telegram.org/method/messages.editMessage create mode 100644 data/core.telegram.org/method/messages.exportChatInvite create mode 100644 data/core.telegram.org/method/messages.faveSticker create mode 100644 data/core.telegram.org/method/messages.forwardMessage create mode 100644 data/core.telegram.org/method/messages.forwardMessages create mode 100644 data/core.telegram.org/method/messages.getAdminsWithInvites create mode 100644 data/core.telegram.org/method/messages.getAllChats create mode 100644 data/core.telegram.org/method/messages.getAllDrafts create mode 100644 data/core.telegram.org/method/messages.getAllStickers create mode 100644 data/core.telegram.org/method/messages.getArchivedStickers create mode 100644 data/core.telegram.org/method/messages.getAttachedStickers create mode 100644 data/core.telegram.org/method/messages.getBotCallbackAnswer create mode 100644 data/core.telegram.org/method/messages.getChatInviteImporters create mode 100644 data/core.telegram.org/method/messages.getChats create mode 100644 data/core.telegram.org/method/messages.getCommonChats create mode 100644 data/core.telegram.org/method/messages.getDhConfig create mode 100644 data/core.telegram.org/method/messages.getDialogFilters create mode 100644 data/core.telegram.org/method/messages.getDialogUnreadMarks create mode 100644 data/core.telegram.org/method/messages.getDialogs create mode 100644 data/core.telegram.org/method/messages.getDiscussionMessage create mode 100644 data/core.telegram.org/method/messages.getDocumentByHash create mode 100644 data/core.telegram.org/method/messages.getEmojiKeywords create mode 100644 data/core.telegram.org/method/messages.getEmojiKeywordsDifference create mode 100644 data/core.telegram.org/method/messages.getEmojiURL create mode 100644 data/core.telegram.org/method/messages.getExportedChatInvite create mode 100644 data/core.telegram.org/method/messages.getFavedStickers create mode 100644 data/core.telegram.org/method/messages.getFeaturedStickers create mode 100644 data/core.telegram.org/method/messages.getFullChat create mode 100644 data/core.telegram.org/method/messages.getGameHighScores create mode 100644 data/core.telegram.org/method/messages.getInlineBotResults create mode 100644 data/core.telegram.org/method/messages.getInlineGameHighScores create mode 100644 data/core.telegram.org/method/messages.getMaskStickers create mode 100644 data/core.telegram.org/method/messages.getMessageEditData create mode 100644 data/core.telegram.org/method/messages.getMessageReactionsList create mode 100644 data/core.telegram.org/method/messages.getMessageReadParticipants create mode 100644 data/core.telegram.org/method/messages.getMessages create mode 100644 data/core.telegram.org/method/messages.getMessagesReactions create mode 100644 data/core.telegram.org/method/messages.getMessagesViews create mode 100644 data/core.telegram.org/method/messages.getOldFeaturedStickers create mode 100644 data/core.telegram.org/method/messages.getOnlines create mode 100644 data/core.telegram.org/method/messages.getPeerDialogs create mode 100644 data/core.telegram.org/method/messages.getPeerSettings create mode 100644 data/core.telegram.org/method/messages.getPinnedDialogs create mode 100644 data/core.telegram.org/method/messages.getPollResults create mode 100644 data/core.telegram.org/method/messages.getPollVotes create mode 100644 data/core.telegram.org/method/messages.getRecentLocations create mode 100644 data/core.telegram.org/method/messages.getRecentStickers create mode 100644 data/core.telegram.org/method/messages.getReplies create mode 100644 data/core.telegram.org/method/messages.getSavedGifs create mode 100644 data/core.telegram.org/method/messages.getScheduledHistory create mode 100644 data/core.telegram.org/method/messages.getSearchCounters create mode 100644 data/core.telegram.org/method/messages.getSplitRanges create mode 100644 data/core.telegram.org/method/messages.getStickerSet create mode 100644 data/core.telegram.org/method/messages.getStickers create mode 100644 data/core.telegram.org/method/messages.getSuggestedDialogFilters create mode 100644 data/core.telegram.org/method/messages.getUnreadMentions create mode 100644 data/core.telegram.org/method/messages.getWebPage create mode 100644 data/core.telegram.org/method/messages.getWebPagePreview create mode 100644 data/core.telegram.org/method/messages.hidePeerSettingsBar create mode 100644 data/core.telegram.org/method/messages.importChatInvite create mode 100644 data/core.telegram.org/method/messages.initHistoryImport create mode 100644 data/core.telegram.org/method/messages.installStickerSet create mode 100644 data/core.telegram.org/method/messages.markDialogUnread create mode 100644 data/core.telegram.org/method/messages.migrateChat create mode 100644 data/core.telegram.org/method/messages.readDiscussion create mode 100644 data/core.telegram.org/method/messages.readEncryptedHistory create mode 100644 data/core.telegram.org/method/messages.readFeaturedStickers create mode 100644 data/core.telegram.org/method/messages.readHistory create mode 100644 data/core.telegram.org/method/messages.readMentions create mode 100644 data/core.telegram.org/method/messages.readMessageContents create mode 100644 data/core.telegram.org/method/messages.receivedMessages create mode 100644 data/core.telegram.org/method/messages.receivedQueue create mode 100644 data/core.telegram.org/method/messages.reorderPinnedDialogs create mode 100644 data/core.telegram.org/method/messages.reorderStickerSets create mode 100644 data/core.telegram.org/method/messages.report create mode 100644 data/core.telegram.org/method/messages.reportEncryptedSpam create mode 100644 data/core.telegram.org/method/messages.reportSpam create mode 100644 data/core.telegram.org/method/messages.requestEncryption create mode 100644 data/core.telegram.org/method/messages.requestUrlAuth create mode 100644 data/core.telegram.org/method/messages.saveDraft create mode 100644 data/core.telegram.org/method/messages.saveGif create mode 100644 data/core.telegram.org/method/messages.saveRecentSticker create mode 100644 data/core.telegram.org/method/messages.search create mode 100644 data/core.telegram.org/method/messages.searchGifs create mode 100644 data/core.telegram.org/method/messages.searchGlobal create mode 100644 data/core.telegram.org/method/messages.searchStickerSets create mode 100644 data/core.telegram.org/method/messages.sendBroadcast create mode 100644 data/core.telegram.org/method/messages.sendEncrypted create mode 100644 data/core.telegram.org/method/messages.sendEncryptedFile create mode 100644 data/core.telegram.org/method/messages.sendEncryptedService create mode 100644 data/core.telegram.org/method/messages.sendInlineBotResult create mode 100644 data/core.telegram.org/method/messages.sendMedia create mode 100644 data/core.telegram.org/method/messages.sendMessage create mode 100644 data/core.telegram.org/method/messages.sendMultiMedia create mode 100644 data/core.telegram.org/method/messages.sendReaction create mode 100644 data/core.telegram.org/method/messages.sendScheduledMessages create mode 100644 data/core.telegram.org/method/messages.sendScreenshotNotification create mode 100644 data/core.telegram.org/method/messages.sendVote create mode 100644 data/core.telegram.org/method/messages.setBotCallbackAnswer create mode 100644 data/core.telegram.org/method/messages.setBotPrecheckoutResults create mode 100644 data/core.telegram.org/method/messages.setBotShippingResults create mode 100644 data/core.telegram.org/method/messages.setChatTheme create mode 100644 data/core.telegram.org/method/messages.setEncryptedTyping create mode 100644 data/core.telegram.org/method/messages.setGameScore create mode 100644 data/core.telegram.org/method/messages.setHistoryTTL create mode 100644 data/core.telegram.org/method/messages.setInlineBotResults create mode 100644 data/core.telegram.org/method/messages.setInlineGameScore create mode 100644 data/core.telegram.org/method/messages.setTyping create mode 100644 data/core.telegram.org/method/messages.startBot create mode 100644 data/core.telegram.org/method/messages.toggleDialogPin create mode 100644 data/core.telegram.org/method/messages.toggleStickerSets create mode 100644 data/core.telegram.org/method/messages.uninstallStickerSet create mode 100644 data/core.telegram.org/method/messages.unpinAllMessages create mode 100644 data/core.telegram.org/method/messages.updateDialogFilter create mode 100644 data/core.telegram.org/method/messages.updateDialogFiltersOrder create mode 100644 data/core.telegram.org/method/messages.updatePinnedMessage create mode 100644 data/core.telegram.org/method/messages.uploadEncryptedFile create mode 100644 data/core.telegram.org/method/messages.uploadImportedMedia create mode 100644 data/core.telegram.org/method/messages.uploadMedia create mode 100644 data/core.telegram.org/method/payments.clearSavedInfo create mode 100644 data/core.telegram.org/method/payments.getBankCardData create mode 100644 data/core.telegram.org/method/payments.getPaymentForm create mode 100644 data/core.telegram.org/method/payments.getPaymentReceipt create mode 100644 data/core.telegram.org/method/payments.getSavedInfo create mode 100644 data/core.telegram.org/method/payments.sendPaymentForm create mode 100644 data/core.telegram.org/method/payments.validateRequestedInfo create mode 100644 data/core.telegram.org/method/phone.acceptCall create mode 100644 data/core.telegram.org/method/phone.checkGroupCall create mode 100644 data/core.telegram.org/method/phone.confirmCall create mode 100644 data/core.telegram.org/method/phone.createGroupCall create mode 100644 data/core.telegram.org/method/phone.discardCall create mode 100644 data/core.telegram.org/method/phone.discardGroupCall create mode 100644 data/core.telegram.org/method/phone.editGroupCallMember create mode 100644 data/core.telegram.org/method/phone.editGroupCallParticipant create mode 100644 data/core.telegram.org/method/phone.editGroupCallTitle create mode 100644 data/core.telegram.org/method/phone.exportGroupCallInvite create mode 100644 data/core.telegram.org/method/phone.getCallConfig create mode 100644 data/core.telegram.org/method/phone.getGroupCall create mode 100644 data/core.telegram.org/method/phone.getGroupCallJoinAs create mode 100644 data/core.telegram.org/method/phone.getGroupParticipants create mode 100644 data/core.telegram.org/method/phone.inviteToGroupCall create mode 100644 data/core.telegram.org/method/phone.joinGroupCall create mode 100644 data/core.telegram.org/method/phone.joinGroupCallPresentation create mode 100644 data/core.telegram.org/method/phone.leaveGroupCall create mode 100644 data/core.telegram.org/method/phone.leaveGroupCallPresentation create mode 100644 data/core.telegram.org/method/phone.receivedCall create mode 100644 data/core.telegram.org/method/phone.requestCall create mode 100644 data/core.telegram.org/method/phone.saveCallDebug create mode 100644 data/core.telegram.org/method/phone.saveDefaultGroupCallJoinAs create mode 100644 data/core.telegram.org/method/phone.sendSignalingData create mode 100644 data/core.telegram.org/method/phone.setCallRating create mode 100644 data/core.telegram.org/method/phone.startScheduledGroupCall create mode 100644 data/core.telegram.org/method/phone.toggleGroupCallRecord create mode 100644 data/core.telegram.org/method/phone.toggleGroupCallStartSubscription create mode 100644 data/core.telegram.org/method/photos.deletePhotos create mode 100644 data/core.telegram.org/method/photos.getUserPhotos create mode 100644 data/core.telegram.org/method/photos.updateProfilePhoto create mode 100644 data/core.telegram.org/method/photos.uploadProfilePhoto create mode 100644 data/core.telegram.org/method/stats.getBroadcastStats create mode 100644 data/core.telegram.org/method/stats.getMegagroupStats create mode 100644 data/core.telegram.org/method/stats.getMessagePublicForwards create mode 100644 data/core.telegram.org/method/stats.getMessageStats create mode 100644 data/core.telegram.org/method/stats.loadAsyncGraph create mode 100644 data/core.telegram.org/method/stickers.addStickerToSet create mode 100644 data/core.telegram.org/method/stickers.changeStickerPosition create mode 100644 data/core.telegram.org/method/stickers.checkShortName create mode 100644 data/core.telegram.org/method/stickers.createStickerSet create mode 100644 data/core.telegram.org/method/stickers.removeStickerFromSet create mode 100644 data/core.telegram.org/method/stickers.setStickerSetThumb create mode 100644 data/core.telegram.org/method/stickers.suggestShortName create mode 100644 data/core.telegram.org/method/updates.getChannelDifference create mode 100644 data/core.telegram.org/method/updates.getDifference create mode 100644 data/core.telegram.org/method/updates.getState create mode 100644 data/core.telegram.org/method/upload.getCdnFile create mode 100644 data/core.telegram.org/method/upload.getCdnFileHashes create mode 100644 data/core.telegram.org/method/upload.getFile create mode 100644 data/core.telegram.org/method/upload.getFileHashes create mode 100644 data/core.telegram.org/method/upload.getWebFile create mode 100644 data/core.telegram.org/method/upload.reuploadCdnFile create mode 100644 data/core.telegram.org/method/upload.saveBigFilePart create mode 100644 data/core.telegram.org/method/upload.saveFilePart create mode 100644 data/core.telegram.org/method/users.getFullUser create mode 100644 data/core.telegram.org/method/users.getUsers create mode 100644 data/core.telegram.org/method/users.setSecureValueErrors create mode 100644 data/core.telegram.org/methods.html create mode 100644 data/core.telegram.org/mtproto.html create mode 100644 data/core.telegram.org/mtproto/TL-abstract-types.html create mode 100644 data/core.telegram.org/mtproto/TL-combinators.html create mode 100644 data/core.telegram.org/mtproto/TL-dependent.html create mode 100644 data/core.telegram.org/mtproto/TL-formal.html create mode 100644 data/core.telegram.org/mtproto/TL-optargs.html create mode 100644 data/core.telegram.org/mtproto/TL-patterns.html create mode 100644 data/core.telegram.org/mtproto/TL-polymorph.html create mode 100644 data/core.telegram.org/mtproto/TL-tl.html create mode 100644 data/core.telegram.org/mtproto/TL-types.html create mode 100644 data/core.telegram.org/mtproto/TL.html create mode 100644 data/core.telegram.org/mtproto/auth_key.html create mode 100644 data/core.telegram.org/mtproto/description.html create mode 100644 data/core.telegram.org/mtproto/description_v1.html create mode 100644 data/core.telegram.org/mtproto/mtproto-transports.html create mode 100644 data/core.telegram.org/mtproto/samples-auth_key.html create mode 100644 data/core.telegram.org/mtproto/security_guidelines.html create mode 100644 data/core.telegram.org/mtproto/security_guidelines_v1.html create mode 100644 data/core.telegram.org/mtproto/serialize.html create mode 100644 data/core.telegram.org/mtproto/service_messages.html create mode 100644 data/core.telegram.org/mtproto/service_messages_about_messages.html create mode 100644 data/core.telegram.org/mtproto_v1.html create mode 100644 data/core.telegram.org/passport.html create mode 100644 data/core.telegram.org/passport/encryption.html create mode 100644 data/core.telegram.org/passport/example.html create mode 100644 data/core.telegram.org/passport/sdk-android.html create mode 100644 data/core.telegram.org/passport/sdk-ios-mac.html create mode 100644 data/core.telegram.org/passport/sdk-javascript.html create mode 100644 data/core.telegram.org/reproducible-builds.html create mode 100644 data/core.telegram.org/schema.html create mode 100644 data/core.telegram.org/schema/end-to-end-json.html create mode 100644 data/core.telegram.org/schema/end-to-end.html create mode 100644 data/core.telegram.org/schema/json.html create mode 100644 data/core.telegram.org/schema/mtproto.html create mode 100644 data/core.telegram.org/stickers.html create mode 100644 data/core.telegram.org/stickers/webm-vp9-encoding.html create mode 100644 data/core.telegram.org/tdlib.html create mode 100644 data/core.telegram.org/tdlib/getting-started.html create mode 100644 data/core.telegram.org/tdlib/notification-api.html create mode 100644 data/core.telegram.org/tdlib/options.html create mode 100644 data/core.telegram.org/techfaq.html create mode 100644 data/core.telegram.org/themes.html create mode 100644 data/core.telegram.org/type/AccountDaysTTL.html create mode 100644 data/core.telegram.org/type/Audio.html create mode 100644 data/core.telegram.org/type/Authorization.html create mode 100644 data/core.telegram.org/type/AutoDownloadSettings.html create mode 100644 data/core.telegram.org/type/BankCardOpenUrl.html create mode 100644 data/core.telegram.org/type/BaseTheme.html create mode 100644 data/core.telegram.org/type/Bool.html create mode 100644 data/core.telegram.org/type/BotCommand.html create mode 100644 data/core.telegram.org/type/BotCommandScope.html create mode 100644 data/core.telegram.org/type/BotInfo.html create mode 100644 data/core.telegram.org/type/BotInlineMessage.html create mode 100644 data/core.telegram.org/type/BotInlineResult.html create mode 100644 data/core.telegram.org/type/CdnConfig.html create mode 100644 data/core.telegram.org/type/CdnPublicKey.html create mode 100644 data/core.telegram.org/type/ChannelAdminLogEventsFilter.html create mode 100644 data/core.telegram.org/type/ChannelLocation.html create mode 100644 data/core.telegram.org/type/ChannelMessagesFilter.html create mode 100644 data/core.telegram.org/type/ChannelParticipant.html create mode 100644 data/core.telegram.org/type/ChannelParticipantsFilter.html create mode 100644 data/core.telegram.org/type/Chat.html create mode 100644 data/core.telegram.org/type/ChatAdminRights.html create mode 100644 data/core.telegram.org/type/ChatAdminWithInvites.html create mode 100644 data/core.telegram.org/type/ChatBannedRights.html create mode 100644 data/core.telegram.org/type/ChatFull.html create mode 100644 data/core.telegram.org/type/ChatInvite.html create mode 100644 data/core.telegram.org/type/ChatInviteImporter.html create mode 100644 data/core.telegram.org/type/ChatOnlines.html create mode 100644 data/core.telegram.org/type/ChatParticipant.html create mode 100644 data/core.telegram.org/type/ChatParticipants.html create mode 100644 data/core.telegram.org/type/ChatPhoto.html create mode 100644 data/core.telegram.org/type/ChatTheme.html create mode 100644 data/core.telegram.org/type/CodeSettings.html create mode 100644 data/core.telegram.org/type/Config.html create mode 100644 data/core.telegram.org/type/Contact.html create mode 100644 data/core.telegram.org/type/ContactStatus.html create mode 100644 data/core.telegram.org/type/DataJSON.html create mode 100644 data/core.telegram.org/type/DcOption.html create mode 100644 data/core.telegram.org/type/DecryptedDataBlock.html create mode 100644 data/core.telegram.org/type/DecryptedMessage.html create mode 100644 data/core.telegram.org/type/DecryptedMessageAction.html create mode 100644 data/core.telegram.org/type/DecryptedMessageLayer.html create mode 100644 data/core.telegram.org/type/DecryptedMessageMedia.html create mode 100644 data/core.telegram.org/type/Dialog.html create mode 100644 data/core.telegram.org/type/DialogFilter.html create mode 100644 data/core.telegram.org/type/DialogFilterSuggested.html create mode 100644 data/core.telegram.org/type/DisabledFeature.html create mode 100644 data/core.telegram.org/type/Document.html create mode 100644 data/core.telegram.org/type/DocumentAttribute.html create mode 100644 data/core.telegram.org/type/DraftMessage.html create mode 100644 data/core.telegram.org/type/EmojiKeyword.html create mode 100644 data/core.telegram.org/type/EmojiKeywordsDifference.html create mode 100644 data/core.telegram.org/type/EmojiLanguage.html create mode 100644 data/core.telegram.org/type/EmojiURL.html create mode 100644 data/core.telegram.org/type/EncryptedChat.html create mode 100644 data/core.telegram.org/type/EncryptedFile.html create mode 100644 data/core.telegram.org/type/EncryptedMessage.html create mode 100644 data/core.telegram.org/type/Error.html create mode 100644 data/core.telegram.org/type/ExportedChatInvite.html create mode 100644 data/core.telegram.org/type/ExportedMessageLink.html create mode 100644 data/core.telegram.org/type/FileHash.html create mode 100644 data/core.telegram.org/type/FileLocation.html create mode 100644 data/core.telegram.org/type/Folder.html create mode 100644 data/core.telegram.org/type/FolderPeer.html create mode 100644 data/core.telegram.org/type/Game.html create mode 100644 data/core.telegram.org/type/GeoPoint.html create mode 100644 data/core.telegram.org/type/GlobalPrivacySettings.html create mode 100644 data/core.telegram.org/type/GroupCall.html create mode 100644 data/core.telegram.org/type/GroupCallParticipant.html create mode 100644 data/core.telegram.org/type/GroupCallParticipantVideo.html create mode 100644 data/core.telegram.org/type/GroupCallParticipantVideoSourceGroup.html create mode 100644 data/core.telegram.org/type/HighScore.html create mode 100644 data/core.telegram.org/type/ImportedContact.html create mode 100644 data/core.telegram.org/type/InlineQueryPeerType.html create mode 100644 data/core.telegram.org/type/InputAppEvent.html create mode 100644 data/core.telegram.org/type/InputBotInlineMessage.html create mode 100644 data/core.telegram.org/type/InputBotInlineMessageID.html create mode 100644 data/core.telegram.org/type/InputBotInlineResult.html create mode 100644 data/core.telegram.org/type/InputChannel.html create mode 100644 data/core.telegram.org/type/InputChatPhoto.html create mode 100644 data/core.telegram.org/type/InputCheckPasswordSRP.html create mode 100644 data/core.telegram.org/type/InputClientProxy.html create mode 100644 data/core.telegram.org/type/InputContact.html create mode 100644 data/core.telegram.org/type/InputDialogPeer.html create mode 100644 data/core.telegram.org/type/InputDocument.html create mode 100644 data/core.telegram.org/type/InputEncryptedChat.html create mode 100644 data/core.telegram.org/type/InputEncryptedFile.html create mode 100644 data/core.telegram.org/type/InputFile.html create mode 100644 data/core.telegram.org/type/InputFileLocation.html create mode 100644 data/core.telegram.org/type/InputFolderPeer.html create mode 100644 data/core.telegram.org/type/InputGame.html create mode 100644 data/core.telegram.org/type/InputGeoPoint.html create mode 100644 data/core.telegram.org/type/InputGroupCall.html create mode 100644 data/core.telegram.org/type/InputMedia.html create mode 100644 data/core.telegram.org/type/InputMessage.html create mode 100644 data/core.telegram.org/type/InputNotifyPeer.html create mode 100644 data/core.telegram.org/type/InputPaymentCredentials.html create mode 100644 data/core.telegram.org/type/InputPeer.html create mode 100644 data/core.telegram.org/type/InputPeerNotifySettings.html create mode 100644 data/core.telegram.org/type/InputPhoneCall.html create mode 100644 data/core.telegram.org/type/InputPhoto.html create mode 100644 data/core.telegram.org/type/InputPrivacyKey.html create mode 100644 data/core.telegram.org/type/InputPrivacyRule.html create mode 100644 data/core.telegram.org/type/InputSecureFile.html create mode 100644 data/core.telegram.org/type/InputSecureValue.html create mode 100644 data/core.telegram.org/type/InputSingleMedia.html create mode 100644 data/core.telegram.org/type/InputStickerSet.html create mode 100644 data/core.telegram.org/type/InputStickerSetItem.html create mode 100644 data/core.telegram.org/type/InputStickeredMedia.html create mode 100644 data/core.telegram.org/type/InputTheme.html create mode 100644 data/core.telegram.org/type/InputThemeSettings.html create mode 100644 data/core.telegram.org/type/InputUser.html create mode 100644 data/core.telegram.org/type/InputWallPaper.html create mode 100644 data/core.telegram.org/type/InputWebDocument.html create mode 100644 data/core.telegram.org/type/InputWebFileLocation.html create mode 100644 data/core.telegram.org/type/Invoice.html create mode 100644 data/core.telegram.org/type/JSONObjectValue.html create mode 100644 data/core.telegram.org/type/JSONValue.html create mode 100644 data/core.telegram.org/type/KeyboardButton.html create mode 100644 data/core.telegram.org/type/KeyboardButtonRow.html create mode 100644 data/core.telegram.org/type/LabeledPrice.html create mode 100644 data/core.telegram.org/type/LangPackDifference.html create mode 100644 data/core.telegram.org/type/LangPackLanguage.html create mode 100644 data/core.telegram.org/type/LangPackString.html create mode 100644 data/core.telegram.org/type/MaskCoords.html create mode 100644 data/core.telegram.org/type/Message.html create mode 100644 data/core.telegram.org/type/MessageAction.html create mode 100644 data/core.telegram.org/type/MessageEntity.html create mode 100644 data/core.telegram.org/type/MessageFwdHeader.html create mode 100644 data/core.telegram.org/type/MessageInteractionCounters.html create mode 100644 data/core.telegram.org/type/MessageMedia.html create mode 100644 data/core.telegram.org/type/MessageRange.html create mode 100644 data/core.telegram.org/type/MessageReactionsList.html create mode 100644 data/core.telegram.org/type/MessageReplies.html create mode 100644 data/core.telegram.org/type/MessageUserVote.html create mode 100644 data/core.telegram.org/type/MessageViews.html create mode 100644 data/core.telegram.org/type/MessagesFilter.html create mode 100644 data/core.telegram.org/type/NearestDc.html create mode 100644 data/core.telegram.org/type/NotifyPeer.html create mode 100644 data/core.telegram.org/type/Null.html create mode 100644 data/core.telegram.org/type/Page.html create mode 100644 data/core.telegram.org/type/PageBlock.html create mode 100644 data/core.telegram.org/type/PageCaption.html create mode 100644 data/core.telegram.org/type/PageListItem.html create mode 100644 data/core.telegram.org/type/PageListOrderedItem.html create mode 100644 data/core.telegram.org/type/PageRelatedArticle.html create mode 100644 data/core.telegram.org/type/PageTableCell.html create mode 100644 data/core.telegram.org/type/PageTableRow.html create mode 100644 data/core.telegram.org/type/PasswordKdfAlgo.html create mode 100644 data/core.telegram.org/type/PaymentCharge.html create mode 100644 data/core.telegram.org/type/PaymentRequestedInfo.html create mode 100644 data/core.telegram.org/type/PaymentSavedCredentials.html create mode 100644 data/core.telegram.org/type/Peer.html create mode 100644 data/core.telegram.org/type/PeerBlocked.html create mode 100644 data/core.telegram.org/type/PeerLocated.html create mode 100644 data/core.telegram.org/type/PeerNotifySettings.html create mode 100644 data/core.telegram.org/type/PeerSettings.html create mode 100644 data/core.telegram.org/type/PhoneCall.html create mode 100644 data/core.telegram.org/type/PhoneCallDiscardReason.html create mode 100644 data/core.telegram.org/type/PhoneCallProtocol.html create mode 100644 data/core.telegram.org/type/PhoneConnection.html create mode 100644 data/core.telegram.org/type/Photo.html create mode 100644 data/core.telegram.org/type/PhotoSize.html create mode 100644 data/core.telegram.org/type/Poll.html create mode 100644 data/core.telegram.org/type/PollAnswer.html create mode 100644 data/core.telegram.org/type/PollAnswerVoters.html create mode 100644 data/core.telegram.org/type/PollResults.html create mode 100644 data/core.telegram.org/type/PopularContact.html create mode 100644 data/core.telegram.org/type/PostAddress.html create mode 100644 data/core.telegram.org/type/PrivacyKey.html create mode 100644 data/core.telegram.org/type/PrivacyRule.html create mode 100644 data/core.telegram.org/type/ReceivedNotifyMessage.html create mode 100644 data/core.telegram.org/type/RecentMeUrl.html create mode 100644 data/core.telegram.org/type/ReplyMarkup.html create mode 100644 data/core.telegram.org/type/ReportReason.html create mode 100644 data/core.telegram.org/type/RestrictionReason.html create mode 100644 data/core.telegram.org/type/RichText.html create mode 100644 data/core.telegram.org/type/SavedContact.html create mode 100644 data/core.telegram.org/type/SecureCredentialsEncrypted.html create mode 100644 data/core.telegram.org/type/SecureData.html create mode 100644 data/core.telegram.org/type/SecureFile.html create mode 100644 data/core.telegram.org/type/SecurePlainData.html create mode 100644 data/core.telegram.org/type/SecureRequiredType.html create mode 100644 data/core.telegram.org/type/SecureSecretSettings.html create mode 100644 data/core.telegram.org/type/SecureValue.html create mode 100644 data/core.telegram.org/type/SecureValueError.html create mode 100644 data/core.telegram.org/type/SecureValueHash.html create mode 100644 data/core.telegram.org/type/SecureValueType.html create mode 100644 data/core.telegram.org/type/SendMessageAction.html create mode 100644 data/core.telegram.org/type/ShippingOption.html create mode 100644 data/core.telegram.org/type/SponsoredMessage.html create mode 100644 data/core.telegram.org/type/StatsAbsValueAndPrev.html create mode 100644 data/core.telegram.org/type/StatsDateRangeDays.html create mode 100644 data/core.telegram.org/type/StatsGraph.html create mode 100644 data/core.telegram.org/type/StatsGroupTopAdmin.html create mode 100644 data/core.telegram.org/type/StatsGroupTopInviter.html create mode 100644 data/core.telegram.org/type/StatsGroupTopPoster.html create mode 100644 data/core.telegram.org/type/StatsPercentValue.html create mode 100644 data/core.telegram.org/type/StatsURL.html create mode 100644 data/core.telegram.org/type/StickerSet.html create mode 100644 data/core.telegram.org/type/StickerSetCovered.html create mode 100644 data/core.telegram.org/type/Theme.html create mode 100644 data/core.telegram.org/type/ThemeSettings.html create mode 100644 data/core.telegram.org/type/TopPeer.html create mode 100644 data/core.telegram.org/type/TopPeerCategory.html create mode 100644 data/core.telegram.org/type/TopPeerCategoryPeers.html create mode 100644 data/core.telegram.org/type/True.html create mode 100644 data/core.telegram.org/type/Update.html create mode 100644 data/core.telegram.org/type/Updates.html create mode 100644 data/core.telegram.org/type/UrlAuthResult.html create mode 100644 data/core.telegram.org/type/User.html create mode 100644 data/core.telegram.org/type/UserFull.html create mode 100644 data/core.telegram.org/type/UserProfilePhoto.html create mode 100644 data/core.telegram.org/type/UserStatus.html create mode 100644 data/core.telegram.org/type/Vector t.html create mode 100644 data/core.telegram.org/type/Video.html create mode 100644 data/core.telegram.org/type/VideoSize.html create mode 100644 data/core.telegram.org/type/WallPaper.html create mode 100644 data/core.telegram.org/type/WallPaperSettings.html create mode 100644 data/core.telegram.org/type/WebAuthorization.html create mode 100644 data/core.telegram.org/type/WebDocument.html create mode 100644 data/core.telegram.org/type/WebPage.html create mode 100644 data/core.telegram.org/type/WebPageAttribute.html create mode 100644 data/core.telegram.org/type/account.AuthorizationForm create mode 100644 data/core.telegram.org/type/account.Authorizations create mode 100644 data/core.telegram.org/type/account.AutoDownloadSettings create mode 100644 data/core.telegram.org/type/account.ChatThemes create mode 100644 data/core.telegram.org/type/account.ContentSettings create mode 100644 data/core.telegram.org/type/account.Password create mode 100644 data/core.telegram.org/type/account.PasswordInputSettings create mode 100644 data/core.telegram.org/type/account.PasswordSettings create mode 100644 data/core.telegram.org/type/account.PrivacyRules create mode 100644 data/core.telegram.org/type/account.ResetPasswordResult create mode 100644 data/core.telegram.org/type/account.SentChangePhoneCode create mode 100644 data/core.telegram.org/type/account.SentEmailCode create mode 100644 data/core.telegram.org/type/account.Takeout create mode 100644 data/core.telegram.org/type/account.Themes create mode 100644 data/core.telegram.org/type/account.TmpPassword create mode 100644 data/core.telegram.org/type/account.WallPapers create mode 100644 data/core.telegram.org/type/account.WebAuthorizations create mode 100644 data/core.telegram.org/type/auth.Authorization create mode 100644 data/core.telegram.org/type/auth.CheckedPhone create mode 100644 data/core.telegram.org/type/auth.CodeType create mode 100644 data/core.telegram.org/type/auth.ExportedAuthorization create mode 100644 data/core.telegram.org/type/auth.LoginToken create mode 100644 data/core.telegram.org/type/auth.PasswordRecovery create mode 100644 data/core.telegram.org/type/auth.SentCode create mode 100644 data/core.telegram.org/type/auth.SentCodeType create mode 100644 data/core.telegram.org/type/bytes.html create mode 100644 data/core.telegram.org/type/channels.AdminLogResults create mode 100644 data/core.telegram.org/type/channels.ChannelParticipant create mode 100644 data/core.telegram.org/type/channels.ChannelParticipants create mode 100644 data/core.telegram.org/type/contacts.Blocked create mode 100644 data/core.telegram.org/type/contacts.Contacts create mode 100644 data/core.telegram.org/type/contacts.Found create mode 100644 data/core.telegram.org/type/contacts.ImportedContacts create mode 100644 data/core.telegram.org/type/contacts.Link create mode 100644 data/core.telegram.org/type/contacts.ResolvedPeer create mode 100644 data/core.telegram.org/type/contacts.TopPeers create mode 100644 data/core.telegram.org/type/double.html create mode 100644 data/core.telegram.org/type/help.AppUpdate create mode 100644 data/core.telegram.org/type/help.CountriesList create mode 100644 data/core.telegram.org/type/help.Country create mode 100644 data/core.telegram.org/type/help.CountryCode create mode 100644 data/core.telegram.org/type/help.DeepLinkInfo create mode 100644 data/core.telegram.org/type/help.InviteText create mode 100644 data/core.telegram.org/type/help.PassportConfig create mode 100644 data/core.telegram.org/type/help.PromoData create mode 100644 data/core.telegram.org/type/help.ProxyData create mode 100644 data/core.telegram.org/type/help.RecentMeUrls create mode 100644 data/core.telegram.org/type/help.Support create mode 100644 data/core.telegram.org/type/help.SupportName create mode 100644 data/core.telegram.org/type/help.TermsOfService create mode 100644 data/core.telegram.org/type/help.TermsOfServiceUpdate create mode 100644 data/core.telegram.org/type/help.UserInfo create mode 100644 data/core.telegram.org/type/int.html create mode 100644 data/core.telegram.org/type/long.html create mode 100644 data/core.telegram.org/type/messages.AffectedFoundMessages create mode 100644 data/core.telegram.org/type/messages.AffectedHistory create mode 100644 data/core.telegram.org/type/messages.AffectedMessages create mode 100644 data/core.telegram.org/type/messages.AllStickers create mode 100644 data/core.telegram.org/type/messages.ArchivedStickers create mode 100644 data/core.telegram.org/type/messages.BotCallbackAnswer create mode 100644 data/core.telegram.org/type/messages.BotResults create mode 100644 data/core.telegram.org/type/messages.ChatAdminsWithInvites create mode 100644 data/core.telegram.org/type/messages.ChatInviteImporters create mode 100644 data/core.telegram.org/type/messages.Chats create mode 100644 data/core.telegram.org/type/messages.CheckedHistoryImportPeer create mode 100644 data/core.telegram.org/type/messages.DhConfig create mode 100644 data/core.telegram.org/type/messages.Dialogs create mode 100644 data/core.telegram.org/type/messages.DiscussionMessage create mode 100644 data/core.telegram.org/type/messages.ExportedChatInvite create mode 100644 data/core.telegram.org/type/messages.ExportedChatInvites create mode 100644 data/core.telegram.org/type/messages.FavedStickers create mode 100644 data/core.telegram.org/type/messages.FeaturedStickers create mode 100644 data/core.telegram.org/type/messages.FoundGifs create mode 100644 data/core.telegram.org/type/messages.FoundStickerSets create mode 100644 data/core.telegram.org/type/messages.HighScores create mode 100644 data/core.telegram.org/type/messages.HistoryImport create mode 100644 data/core.telegram.org/type/messages.HistoryImportParsed create mode 100644 data/core.telegram.org/type/messages.InactiveChats create mode 100644 data/core.telegram.org/type/messages.MessageEditData create mode 100644 data/core.telegram.org/type/messages.MessageViews create mode 100644 data/core.telegram.org/type/messages.Messages create mode 100644 data/core.telegram.org/type/messages.PeerDialogs create mode 100644 data/core.telegram.org/type/messages.RecentStickers create mode 100644 data/core.telegram.org/type/messages.SearchCounter create mode 100644 data/core.telegram.org/type/messages.SentEncryptedMessage create mode 100644 data/core.telegram.org/type/messages.SentMessage create mode 100644 data/core.telegram.org/type/messages.SponsoredMessages create mode 100644 data/core.telegram.org/type/messages.StatedMessage create mode 100644 data/core.telegram.org/type/messages.StatedMessages create mode 100644 data/core.telegram.org/type/messages.StickerSet create mode 100644 data/core.telegram.org/type/messages.StickerSetInstallResult create mode 100644 data/core.telegram.org/type/messages.Stickers create mode 100644 data/core.telegram.org/type/messages.VotesList create mode 100644 data/core.telegram.org/type/payments.BankCardData create mode 100644 data/core.telegram.org/type/payments.PaymentForm create mode 100644 data/core.telegram.org/type/payments.PaymentReceipt create mode 100644 data/core.telegram.org/type/payments.PaymentResult create mode 100644 data/core.telegram.org/type/payments.SavedInfo create mode 100644 data/core.telegram.org/type/payments.ValidatedRequestedInfo create mode 100644 data/core.telegram.org/type/phone.ExportedGroupCallInvite create mode 100644 data/core.telegram.org/type/phone.GroupCall create mode 100644 data/core.telegram.org/type/phone.GroupParticipants create mode 100644 data/core.telegram.org/type/phone.JoinAsPeers create mode 100644 data/core.telegram.org/type/phone.PhoneCall create mode 100644 data/core.telegram.org/type/photos.Photo create mode 100644 data/core.telegram.org/type/photos.Photos create mode 100644 data/core.telegram.org/type/stats.BroadcastStats create mode 100644 data/core.telegram.org/type/stats.MegagroupStats create mode 100644 data/core.telegram.org/type/stats.MessageStats create mode 100644 data/core.telegram.org/type/stickers.SuggestedShortName create mode 100644 data/core.telegram.org/type/storage.FileType create mode 100644 data/core.telegram.org/type/string.html create mode 100644 data/core.telegram.org/type/updates.ChannelDifference create mode 100644 data/core.telegram.org/type/updates.Difference create mode 100644 data/core.telegram.org/type/updates.State create mode 100644 data/core.telegram.org/type/upload.CdnFile create mode 100644 data/core.telegram.org/type/upload.File create mode 100644 data/core.telegram.org/type/upload.WebFile create mode 100644 data/core.telegram.org/video_stickers.html create mode 100644 data/core.telegram.org/widgets.html create mode 100644 data/core.telegram.org/widgets/discussion.html create mode 100644 data/core.telegram.org/widgets/login.html create mode 100644 data/core.telegram.org/widgets/post.html create mode 100644 data/core.telegram.org/widgets/share.html create mode 100644 data/corefork.telegram.org.html create mode 100644 data/corefork.telegram.org/api.html create mode 100644 data/corefork.telegram.org/api/account-deletion.html create mode 100644 data/corefork.telegram.org/api/animated-emojis.html create mode 100644 data/corefork.telegram.org/api/auth.html create mode 100644 data/corefork.telegram.org/api/bots.html create mode 100644 data/corefork.telegram.org/api/bots/buttons.html create mode 100644 data/corefork.telegram.org/api/bots/commands.html create mode 100644 data/corefork.telegram.org/api/bots/games.html create mode 100644 data/corefork.telegram.org/api/bots/inline.html create mode 100644 data/corefork.telegram.org/api/channel.html create mode 100644 data/corefork.telegram.org/api/config.html create mode 100644 data/corefork.telegram.org/api/datacenter.html create mode 100644 data/corefork.telegram.org/api/dice.html create mode 100644 data/corefork.telegram.org/api/discussion.html create mode 100644 data/corefork.telegram.org/api/drafts.html create mode 100644 data/corefork.telegram.org/api/end-to-end.html create mode 100644 data/corefork.telegram.org/api/end-to-end/pfs.html create mode 100644 data/corefork.telegram.org/api/end-to-end/seq_no.html create mode 100644 data/corefork.telegram.org/api/end-to-end/video-calls.html create mode 100644 data/corefork.telegram.org/api/end-to-end/voice-calls.html create mode 100644 data/corefork.telegram.org/api/end-to-end_v1.html create mode 100644 data/corefork.telegram.org/api/entities.html create mode 100644 data/corefork.telegram.org/api/errors.html create mode 100644 data/corefork.telegram.org/api/file_reference.html create mode 100644 data/corefork.telegram.org/api/files.html create mode 100644 data/corefork.telegram.org/api/geochats.html create mode 100644 data/corefork.telegram.org/api/import.html create mode 100644 data/corefork.telegram.org/api/invoking.html create mode 100644 data/corefork.telegram.org/api/layers.html create mode 100644 data/corefork.telegram.org/api/live-location.html create mode 100644 data/corefork.telegram.org/api/mentions.html create mode 100644 data/corefork.telegram.org/api/min.html create mode 100644 data/corefork.telegram.org/api/obtaining_api_id.html create mode 100644 data/corefork.telegram.org/api/offsets.html create mode 100644 data/corefork.telegram.org/api/optimisation.html create mode 100644 data/corefork.telegram.org/api/passport.html create mode 100644 data/corefork.telegram.org/api/pattern.html create mode 100644 data/corefork.telegram.org/api/payments.html create mode 100644 data/corefork.telegram.org/api/pfs.html create mode 100644 data/corefork.telegram.org/api/pin.html create mode 100644 data/corefork.telegram.org/api/poll.html create mode 100644 data/corefork.telegram.org/api/push-updates.html create mode 100644 data/corefork.telegram.org/api/qr-login.html create mode 100644 data/corefork.telegram.org/api/recent-actions.html create mode 100644 data/corefork.telegram.org/api/rights.html create mode 100644 data/corefork.telegram.org/api/scheduled-messages.html create mode 100644 data/corefork.telegram.org/api/search.html create mode 100644 data/corefork.telegram.org/api/sponsored-messages.html create mode 100644 data/corefork.telegram.org/api/srp.html create mode 100644 data/corefork.telegram.org/api/stats.html create mode 100644 data/corefork.telegram.org/api/terms.html create mode 100644 data/corefork.telegram.org/api/threads.html create mode 100644 data/corefork.telegram.org/api/top-rating.html create mode 100644 data/corefork.telegram.org/api/updates.html create mode 100644 data/corefork.telegram.org/api/url-authorization.html create mode 100644 data/corefork.telegram.org/api/web-events.html create mode 100644 data/corefork.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html create mode 100644 data/corefork.telegram.org/bots.html create mode 100644 data/corefork.telegram.org/bots/2-0-intro.html create mode 100644 data/corefork.telegram.org/bots/api-changelog.html create mode 100644 data/corefork.telegram.org/bots/api.html create mode 100644 data/corefork.telegram.org/bots/faq.html create mode 100644 data/corefork.telegram.org/bots/games.html create mode 100644 data/corefork.telegram.org/bots/inline.html create mode 100644 data/corefork.telegram.org/bots/samples.html create mode 100644 data/corefork.telegram.org/bots/samples/hellobot.html create mode 100644 data/corefork.telegram.org/bots/self-signed.html create mode 100644 data/corefork.telegram.org/bots/webhooks.html create mode 100644 data/corefork.telegram.org/cdn.html create mode 100644 data/corefork.telegram.org/constructor/account.authorizationForm create mode 100644 data/corefork.telegram.org/constructor/account.authorizations create mode 100644 data/corefork.telegram.org/constructor/account.autoDownloadSettings create mode 100644 data/corefork.telegram.org/constructor/account.chatThemes create mode 100644 data/corefork.telegram.org/constructor/account.chatThemesNotModified create mode 100644 data/corefork.telegram.org/constructor/account.contentSettings create mode 100644 data/corefork.telegram.org/constructor/account.password create mode 100644 data/corefork.telegram.org/constructor/account.passwordInputSettings create mode 100644 data/corefork.telegram.org/constructor/account.passwordSettings create mode 100644 data/corefork.telegram.org/constructor/account.privacyRules create mode 100644 data/corefork.telegram.org/constructor/account.resetPasswordFailedWait create mode 100644 data/corefork.telegram.org/constructor/account.resetPasswordOk create mode 100644 data/corefork.telegram.org/constructor/account.resetPasswordRequestedWait create mode 100644 data/corefork.telegram.org/constructor/account.sentChangePhoneCode create mode 100644 data/corefork.telegram.org/constructor/account.sentEmailCode create mode 100644 data/corefork.telegram.org/constructor/account.takeout create mode 100644 data/corefork.telegram.org/constructor/account.themes create mode 100644 data/corefork.telegram.org/constructor/account.themesNotModified create mode 100644 data/corefork.telegram.org/constructor/account.tmpPassword create mode 100644 data/corefork.telegram.org/constructor/account.wallPapers create mode 100644 data/corefork.telegram.org/constructor/account.wallPapersNotModified create mode 100644 data/corefork.telegram.org/constructor/account.webAuthorizations create mode 100644 data/corefork.telegram.org/constructor/accountDaysTTL.html create mode 100644 data/corefork.telegram.org/constructor/auth.authorization create mode 100644 data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired create mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeCall create mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeFlashCall create mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeMissedCall create mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeSms create mode 100644 data/corefork.telegram.org/constructor/auth.exportedAuthorization create mode 100644 data/corefork.telegram.org/constructor/auth.loggedOut create mode 100644 data/corefork.telegram.org/constructor/auth.loginToken create mode 100644 data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo create mode 100644 data/corefork.telegram.org/constructor/auth.loginTokenSuccess create mode 100644 data/corefork.telegram.org/constructor/auth.passwordRecovery create mode 100644 data/corefork.telegram.org/constructor/auth.sentAppCode create mode 100644 data/corefork.telegram.org/constructor/auth.sentCode create mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeApp create mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeCall create mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeFlashCall create mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeMissedCall create mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeSms create mode 100644 data/corefork.telegram.org/constructor/authorization.html create mode 100644 data/corefork.telegram.org/constructor/autoDownloadSettings.html create mode 100644 data/corefork.telegram.org/constructor/availableReaction.html create mode 100644 data/corefork.telegram.org/constructor/bankCardOpenUrl.html create mode 100644 data/corefork.telegram.org/constructor/baseThemeArctic.html create mode 100644 data/corefork.telegram.org/constructor/baseThemeClassic.html create mode 100644 data/corefork.telegram.org/constructor/baseThemeDay.html create mode 100644 data/corefork.telegram.org/constructor/baseThemeNight.html create mode 100644 data/corefork.telegram.org/constructor/baseThemeTinted.html create mode 100644 data/corefork.telegram.org/constructor/boolFalse.html create mode 100644 data/corefork.telegram.org/constructor/boolTrue.html create mode 100644 data/corefork.telegram.org/constructor/botCommand.html create mode 100644 data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html create mode 100644 data/corefork.telegram.org/constructor/botCommandScopeChats.html create mode 100644 data/corefork.telegram.org/constructor/botCommandScopeDefault.html create mode 100644 data/corefork.telegram.org/constructor/botCommandScopePeer.html create mode 100644 data/corefork.telegram.org/constructor/botCommandScopePeerUser.html create mode 100644 data/corefork.telegram.org/constructor/botCommandScopeUsers.html create mode 100644 data/corefork.telegram.org/constructor/botInfo.html create mode 100644 data/corefork.telegram.org/constructor/botInlineMediaResult.html create mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaAuto.html create mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaContact.html create mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaGeo.html create mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaInvoice.html create mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaVenue.html create mode 100644 data/corefork.telegram.org/constructor/botInlineMessageText.html create mode 100644 data/corefork.telegram.org/constructor/botInlineResult.html create mode 100644 data/corefork.telegram.org/constructor/cdnConfig.html create mode 100644 data/corefork.telegram.org/constructor/cdnPublicKey.html create mode 100644 data/corefork.telegram.org/constructor/channel.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEvent.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAvailableReactions.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionEditMessage.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByRequest.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionSendMessage.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionStopPoll.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleNoForwards.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventsFilter.html create mode 100644 data/corefork.telegram.org/constructor/channelForbidden.html create mode 100644 data/corefork.telegram.org/constructor/channelFull.html create mode 100644 data/corefork.telegram.org/constructor/channelLocation.html create mode 100644 data/corefork.telegram.org/constructor/channelLocationEmpty.html create mode 100644 data/corefork.telegram.org/constructor/channelMessagesFilter.html create mode 100644 data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipant.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantAdmin.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantBanned.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantCreator.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantLeft.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantSelf.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsAdmins.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsBanned.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsBots.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsContacts.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsKicked.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsMentions.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsRecent.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsSearch.html create mode 100644 data/corefork.telegram.org/constructor/channels.adminLogResults create mode 100644 data/corefork.telegram.org/constructor/channels.channelParticipant create mode 100644 data/corefork.telegram.org/constructor/channels.channelParticipants create mode 100644 data/corefork.telegram.org/constructor/channels.channelParticipantsNotModified create mode 100644 data/corefork.telegram.org/constructor/channels.sendAsPeers create mode 100644 data/corefork.telegram.org/constructor/chat.html create mode 100644 data/corefork.telegram.org/constructor/chatAdminRights.html create mode 100644 data/corefork.telegram.org/constructor/chatAdminWithInvites.html create mode 100644 data/corefork.telegram.org/constructor/chatBannedRights.html create mode 100644 data/corefork.telegram.org/constructor/chatEmpty.html create mode 100644 data/corefork.telegram.org/constructor/chatForbidden.html create mode 100644 data/corefork.telegram.org/constructor/chatFull.html create mode 100644 data/corefork.telegram.org/constructor/chatInvite.html create mode 100644 data/corefork.telegram.org/constructor/chatInviteAlready.html create mode 100644 data/corefork.telegram.org/constructor/chatInviteExported.html create mode 100644 data/corefork.telegram.org/constructor/chatInviteImporter.html create mode 100644 data/corefork.telegram.org/constructor/chatInvitePeek.html create mode 100644 data/corefork.telegram.org/constructor/chatOnlines.html create mode 100644 data/corefork.telegram.org/constructor/chatParticipant.html create mode 100644 data/corefork.telegram.org/constructor/chatParticipantAdmin.html create mode 100644 data/corefork.telegram.org/constructor/chatParticipantCreator.html create mode 100644 data/corefork.telegram.org/constructor/chatParticipants.html create mode 100644 data/corefork.telegram.org/constructor/chatParticipantsForbidden.html create mode 100644 data/corefork.telegram.org/constructor/chatPhoto.html create mode 100644 data/corefork.telegram.org/constructor/chatPhotoEmpty.html create mode 100644 data/corefork.telegram.org/constructor/chatTheme.html create mode 100644 data/corefork.telegram.org/constructor/codeSettings.html create mode 100644 data/corefork.telegram.org/constructor/config.html create mode 100644 data/corefork.telegram.org/constructor/contact.html create mode 100644 data/corefork.telegram.org/constructor/contactStatus.html create mode 100644 data/corefork.telegram.org/constructor/contacts.blocked create mode 100644 data/corefork.telegram.org/constructor/contacts.blockedSlice create mode 100644 data/corefork.telegram.org/constructor/contacts.contacts create mode 100644 data/corefork.telegram.org/constructor/contacts.contactsNotModified create mode 100644 data/corefork.telegram.org/constructor/contacts.found create mode 100644 data/corefork.telegram.org/constructor/contacts.importedContacts create mode 100644 data/corefork.telegram.org/constructor/contacts.resolvedPeer create mode 100644 data/corefork.telegram.org/constructor/contacts.topPeers create mode 100644 data/corefork.telegram.org/constructor/contacts.topPeersDisabled create mode 100644 data/corefork.telegram.org/constructor/contacts.topPeersNotModified create mode 100644 data/corefork.telegram.org/constructor/dataJSON.html create mode 100644 data/corefork.telegram.org/constructor/dcOption.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessage.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionAbortKey.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionAcceptKey.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionCommitKey.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionDeleteMessages.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionFlushHistory.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionNoop.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionNotifyLayer.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionReadMessages.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionRequestKey.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionResend.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionTyping.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageLayer.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaAudio.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaContact.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaDocument.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaEmpty.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaExternalDocument.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaVenue.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageService.html create mode 100644 data/corefork.telegram.org/constructor/dialog.html create mode 100644 data/corefork.telegram.org/constructor/dialogFilter.html create mode 100644 data/corefork.telegram.org/constructor/dialogFilterSuggested.html create mode 100644 data/corefork.telegram.org/constructor/dialogFolder.html create mode 100644 data/corefork.telegram.org/constructor/dialogPeer.html create mode 100644 data/corefork.telegram.org/constructor/dialogPeerFolder.html create mode 100644 data/corefork.telegram.org/constructor/disabledFeature.html create mode 100644 data/corefork.telegram.org/constructor/document.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeAnimated.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeAudio.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeFilename.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeHasStickers.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeImageSize.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeSticker.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeVideo.html create mode 100644 data/corefork.telegram.org/constructor/documentEmpty.html create mode 100644 data/corefork.telegram.org/constructor/draftMessage.html create mode 100644 data/corefork.telegram.org/constructor/draftMessageEmpty.html create mode 100644 data/corefork.telegram.org/constructor/emojiKeyword.html create mode 100644 data/corefork.telegram.org/constructor/emojiKeywordDeleted.html create mode 100644 data/corefork.telegram.org/constructor/emojiKeywordsDifference.html create mode 100644 data/corefork.telegram.org/constructor/emojiLanguage.html create mode 100644 data/corefork.telegram.org/constructor/emojiURL.html create mode 100644 data/corefork.telegram.org/constructor/encryptedChat.html create mode 100644 data/corefork.telegram.org/constructor/encryptedChatDiscarded.html create mode 100644 data/corefork.telegram.org/constructor/encryptedChatEmpty.html create mode 100644 data/corefork.telegram.org/constructor/encryptedChatRequested.html create mode 100644 data/corefork.telegram.org/constructor/encryptedChatWaiting.html create mode 100644 data/corefork.telegram.org/constructor/encryptedFile.html create mode 100644 data/corefork.telegram.org/constructor/encryptedFileEmpty.html create mode 100644 data/corefork.telegram.org/constructor/encryptedMessage.html create mode 100644 data/corefork.telegram.org/constructor/encryptedMessageService.html create mode 100644 data/corefork.telegram.org/constructor/error.html create mode 100644 data/corefork.telegram.org/constructor/exportedMessageLink.html create mode 100644 data/corefork.telegram.org/constructor/fileHash.html create mode 100644 data/corefork.telegram.org/constructor/fileLocation.html create mode 100644 data/corefork.telegram.org/constructor/fileLocationUnavailable.html create mode 100644 data/corefork.telegram.org/constructor/folder.html create mode 100644 data/corefork.telegram.org/constructor/folderPeer.html create mode 100644 data/corefork.telegram.org/constructor/game.html create mode 100644 data/corefork.telegram.org/constructor/geoPoint.html create mode 100644 data/corefork.telegram.org/constructor/geoPointEmpty.html create mode 100644 data/corefork.telegram.org/constructor/globalPrivacySettings.html create mode 100644 data/corefork.telegram.org/constructor/groupCall.html create mode 100644 data/corefork.telegram.org/constructor/groupCallDiscarded.html create mode 100644 data/corefork.telegram.org/constructor/groupCallParticipant.html create mode 100644 data/corefork.telegram.org/constructor/groupCallParticipantVideo.html create mode 100644 data/corefork.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html create mode 100644 data/corefork.telegram.org/constructor/help.appUpdate create mode 100644 data/corefork.telegram.org/constructor/help.countriesList create mode 100644 data/corefork.telegram.org/constructor/help.countriesListNotModified create mode 100644 data/corefork.telegram.org/constructor/help.country create mode 100644 data/corefork.telegram.org/constructor/help.countryCode create mode 100644 data/corefork.telegram.org/constructor/help.deepLinkInfo create mode 100644 data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty create mode 100644 data/corefork.telegram.org/constructor/help.inviteText create mode 100644 data/corefork.telegram.org/constructor/help.noAppUpdate create mode 100644 data/corefork.telegram.org/constructor/help.passportConfig create mode 100644 data/corefork.telegram.org/constructor/help.passportConfigNotModified create mode 100644 data/corefork.telegram.org/constructor/help.promoData create mode 100644 data/corefork.telegram.org/constructor/help.promoDataEmpty create mode 100644 data/corefork.telegram.org/constructor/help.recentMeUrls create mode 100644 data/corefork.telegram.org/constructor/help.support create mode 100644 data/corefork.telegram.org/constructor/help.supportName create mode 100644 data/corefork.telegram.org/constructor/help.termsOfService create mode 100644 data/corefork.telegram.org/constructor/help.termsOfServiceUpdate create mode 100644 data/corefork.telegram.org/constructor/help.termsOfServiceUpdateEmpty create mode 100644 data/corefork.telegram.org/constructor/help.userInfo create mode 100644 data/corefork.telegram.org/constructor/help.userInfoEmpty create mode 100644 data/corefork.telegram.org/constructor/highScore.html create mode 100644 data/corefork.telegram.org/constructor/importedContact.html create mode 100644 data/corefork.telegram.org/constructor/inlineBotSwitchPM.html create mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html create mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html create mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html create mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html create mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html create mode 100644 data/corefork.telegram.org/constructor/inputAppEvent.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageGame.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageID.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageID64.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaAuto.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaGeo.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaVenue.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageText.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineResult.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineResultDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineResultPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputChannel.html create mode 100644 data/corefork.telegram.org/constructor/inputChannelEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputChannelFromMessage.html create mode 100644 data/corefork.telegram.org/constructor/inputChatPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputChatPhotoEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputCheckPasswordSRP.html create mode 100644 data/corefork.telegram.org/constructor/inputClientProxy.html create mode 100644 data/corefork.telegram.org/constructor/inputDialogPeer.html create mode 100644 data/corefork.telegram.org/constructor/inputDialogPeerFolder.html create mode 100644 data/corefork.telegram.org/constructor/inputDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputDocumentEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputDocumentFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputEncryptedChat.html create mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFile.html create mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFileBigUploaded.html create mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFileEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html create mode 100644 data/corefork.telegram.org/constructor/inputFile.html create mode 100644 data/corefork.telegram.org/constructor/inputFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputFolderPeer.html create mode 100644 data/corefork.telegram.org/constructor/inputGameID.html create mode 100644 data/corefork.telegram.org/constructor/inputGameShortName.html create mode 100644 data/corefork.telegram.org/constructor/inputGeoPoint.html create mode 100644 data/corefork.telegram.org/constructor/inputGeoPointEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/inputGroupCallStream.html create mode 100644 data/corefork.telegram.org/constructor/inputKeyboardButtonUrlAuth.html create mode 100644 data/corefork.telegram.org/constructor/inputKeyboardButtonUserProfile.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaContact.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaDice.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaDocumentExternal.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaGame.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaGeoLive.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaGeoPoint.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaInvoice.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaPhotoExternal.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaPoll.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaUploadedDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaUploadedPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaUploadedThumbDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaVenue.html create mode 100644 data/corefork.telegram.org/constructor/inputMessageCallbackQuery.html create mode 100644 data/corefork.telegram.org/constructor/inputMessageEntityMentionName.html create mode 100644 data/corefork.telegram.org/constructor/inputMessageID.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagePinned.html create mode 100644 data/corefork.telegram.org/constructor/inputMessageReplyTo.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterContacts.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterGif.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterMusic.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterMyMentions.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterPhoneCalls.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterPhotoVideo.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterPhotos.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterPinned.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterRoundVideo.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterRoundVoice.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterUrl.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterVoice.html create mode 100644 data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html create mode 100644 data/corefork.telegram.org/constructor/inputNotifyChats.html create mode 100644 data/corefork.telegram.org/constructor/inputNotifyPeer.html create mode 100644 data/corefork.telegram.org/constructor/inputNotifyUsers.html create mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentials.html create mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentialsApplePay.html create mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html create mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerChat.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerNotifySettings.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerSelf.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerUser.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html create mode 100644 data/corefork.telegram.org/constructor/inputPhoneCall.html create mode 100644 data/corefork.telegram.org/constructor/inputPhoneContact.html create mode 100644 data/corefork.telegram.org/constructor/inputPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputPhotoEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputPhotoFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyChatInvite.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyForwards.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueAllowAll.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueAllowContacts.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueAllowUsers.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueDisallowAll.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueDisallowContacts.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueDisallowUsers.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonChildAbuse.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonCopyright.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonFake.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonGeoIrrelevant.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonOther.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonPornography.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonSpam.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonViolence.html create mode 100644 data/corefork.telegram.org/constructor/inputSecureFile.html create mode 100644 data/corefork.telegram.org/constructor/inputSecureFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputSecureFileUploaded.html create mode 100644 data/corefork.telegram.org/constructor/inputSecureValue.html create mode 100644 data/corefork.telegram.org/constructor/inputSingleMedia.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmoji.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetID.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetItem.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetShortName.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetThumb.html create mode 100644 data/corefork.telegram.org/constructor/inputStickeredMediaDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputStickeredMediaPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputTakeoutFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputTheme.html create mode 100644 data/corefork.telegram.org/constructor/inputThemeSettings.html create mode 100644 data/corefork.telegram.org/constructor/inputThemeSlug.html create mode 100644 data/corefork.telegram.org/constructor/inputUser.html create mode 100644 data/corefork.telegram.org/constructor/inputUserEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputUserFromMessage.html create mode 100644 data/corefork.telegram.org/constructor/inputWallPaper.html create mode 100644 data/corefork.telegram.org/constructor/inputWallPaperNoFile.html create mode 100644 data/corefork.telegram.org/constructor/inputWallPaperSlug.html create mode 100644 data/corefork.telegram.org/constructor/inputWebDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputWebFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/invoice.html create mode 100644 data/corefork.telegram.org/constructor/jsonArray.html create mode 100644 data/corefork.telegram.org/constructor/jsonNull.html create mode 100644 data/corefork.telegram.org/constructor/jsonNumber.html create mode 100644 data/corefork.telegram.org/constructor/jsonObject.html create mode 100644 data/corefork.telegram.org/constructor/jsonObjectValue.html create mode 100644 data/corefork.telegram.org/constructor/jsonString.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButton.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonBuy.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonCallback.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonGame.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonRequestGeoLocation.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonRequestPhone.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonRequestPoll.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonRow.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonSwitchInline.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonUrl.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonUrlAuth.html create mode 100644 data/corefork.telegram.org/constructor/keyboardButtonUserProfile.html create mode 100644 data/corefork.telegram.org/constructor/labeledPrice.html create mode 100644 data/corefork.telegram.org/constructor/langPackDifference.html create mode 100644 data/corefork.telegram.org/constructor/langPackLanguage.html create mode 100644 data/corefork.telegram.org/constructor/langPackString.html create mode 100644 data/corefork.telegram.org/constructor/langPackStringDeleted.html create mode 100644 data/corefork.telegram.org/constructor/langPackStringPluralized.html create mode 100644 data/corefork.telegram.org/constructor/maskCoords.html create mode 100644 data/corefork.telegram.org/constructor/message.html create mode 100644 data/corefork.telegram.org/constructor/messageActionBotAllowed.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChannelCreate.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatAddUser.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatCreate.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatDeletePhoto.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatDeleteUser.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatEditPhoto.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatEditTitle.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatJoinedByLink.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatJoinedByRequest.html create mode 100644 data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html create mode 100644 data/corefork.telegram.org/constructor/messageActionContactSignUp.html create mode 100644 data/corefork.telegram.org/constructor/messageActionCustomAction.html create mode 100644 data/corefork.telegram.org/constructor/messageActionGameScore.html create mode 100644 data/corefork.telegram.org/constructor/messageActionGeoProximityReached.html create mode 100644 data/corefork.telegram.org/constructor/messageActionGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/messageActionGroupCallScheduled.html create mode 100644 data/corefork.telegram.org/constructor/messageActionHistoryClear.html create mode 100644 data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/messageActionPaymentSent.html create mode 100644 data/corefork.telegram.org/constructor/messageActionPaymentSentMe.html create mode 100644 data/corefork.telegram.org/constructor/messageActionPhoneCall.html create mode 100644 data/corefork.telegram.org/constructor/messageActionPinMessage.html create mode 100644 data/corefork.telegram.org/constructor/messageActionScreenshotTaken.html create mode 100644 data/corefork.telegram.org/constructor/messageActionSecureValuesSent.html create mode 100644 data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html create mode 100644 data/corefork.telegram.org/constructor/messageActionSetChatTheme.html create mode 100644 data/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html create mode 100644 data/corefork.telegram.org/constructor/messageEmpty.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityBankCard.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityBlockquote.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityBold.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityBotCommand.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityCashtag.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityCode.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityEmail.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityItalic.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityMentionName.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityPhone.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityPre.html create mode 100644 data/corefork.telegram.org/constructor/messageEntitySpoiler.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityStrike.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityTextUrl.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityUnderline.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityUnknown.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityUrl.html create mode 100644 data/corefork.telegram.org/constructor/messageFwdHeader.html create mode 100644 data/corefork.telegram.org/constructor/messageInteractionCounters.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaAudio.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaContact.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaDice.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaDocument.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaEmpty.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaGame.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaGeo.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaGeoLive.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaInvoice.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaPhoto.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaPoll.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaUnsupported.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaVenue.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaVideo.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaWebPage.html create mode 100644 data/corefork.telegram.org/constructor/messagePeerReaction.html create mode 100644 data/corefork.telegram.org/constructor/messageRange.html create mode 100644 data/corefork.telegram.org/constructor/messageReactions.html create mode 100644 data/corefork.telegram.org/constructor/messageReplies.html create mode 100644 data/corefork.telegram.org/constructor/messageReplyHeader.html create mode 100644 data/corefork.telegram.org/constructor/messageService.html create mode 100644 data/corefork.telegram.org/constructor/messageUserVote.html create mode 100644 data/corefork.telegram.org/constructor/messageUserVoteInputOption.html create mode 100644 data/corefork.telegram.org/constructor/messageUserVoteMultiple.html create mode 100644 data/corefork.telegram.org/constructor/messageViews.html create mode 100644 data/corefork.telegram.org/constructor/messages.affectedFoundMessages create mode 100644 data/corefork.telegram.org/constructor/messages.affectedHistory create mode 100644 data/corefork.telegram.org/constructor/messages.affectedMessages create mode 100644 data/corefork.telegram.org/constructor/messages.allStickers create mode 100644 data/corefork.telegram.org/constructor/messages.allStickersNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.archivedStickers create mode 100644 data/corefork.telegram.org/constructor/messages.availableReactions create mode 100644 data/corefork.telegram.org/constructor/messages.availableReactionsNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.botCallbackAnswer create mode 100644 data/corefork.telegram.org/constructor/messages.botResults create mode 100644 data/corefork.telegram.org/constructor/messages.channelMessages create mode 100644 data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites create mode 100644 data/corefork.telegram.org/constructor/messages.chatFull create mode 100644 data/corefork.telegram.org/constructor/messages.chatInviteImporters create mode 100644 data/corefork.telegram.org/constructor/messages.chats create mode 100644 data/corefork.telegram.org/constructor/messages.chatsSlice create mode 100644 data/corefork.telegram.org/constructor/messages.checkedHistoryImportPeer create mode 100644 data/corefork.telegram.org/constructor/messages.dhConfig create mode 100644 data/corefork.telegram.org/constructor/messages.dhConfigNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.dialogs create mode 100644 data/corefork.telegram.org/constructor/messages.dialogsSlice create mode 100644 data/corefork.telegram.org/constructor/messages.discussionMessage create mode 100644 data/corefork.telegram.org/constructor/messages.exportedChatInvite create mode 100644 data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced create mode 100644 data/corefork.telegram.org/constructor/messages.exportedChatInvites create mode 100644 data/corefork.telegram.org/constructor/messages.favedStickers create mode 100644 data/corefork.telegram.org/constructor/messages.favedStickersNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.featuredStickers create mode 100644 data/corefork.telegram.org/constructor/messages.featuredStickersNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.foundStickerSets create mode 100644 data/corefork.telegram.org/constructor/messages.foundStickerSetsNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.highScores create mode 100644 data/corefork.telegram.org/constructor/messages.historyImport create mode 100644 data/corefork.telegram.org/constructor/messages.historyImportParsed create mode 100644 data/corefork.telegram.org/constructor/messages.inactiveChats create mode 100644 data/corefork.telegram.org/constructor/messages.messageEditData create mode 100644 data/corefork.telegram.org/constructor/messages.messageReactionsList create mode 100644 data/corefork.telegram.org/constructor/messages.messageViews create mode 100644 data/corefork.telegram.org/constructor/messages.messages create mode 100644 data/corefork.telegram.org/constructor/messages.messagesNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.messagesSlice create mode 100644 data/corefork.telegram.org/constructor/messages.peerDialogs create mode 100644 data/corefork.telegram.org/constructor/messages.peerSettings create mode 100644 data/corefork.telegram.org/constructor/messages.recentStickers create mode 100644 data/corefork.telegram.org/constructor/messages.recentStickersNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.savedGifs create mode 100644 data/corefork.telegram.org/constructor/messages.savedGifsNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.searchCounter create mode 100644 data/corefork.telegram.org/constructor/messages.searchResultsCalendar create mode 100644 data/corefork.telegram.org/constructor/messages.searchResultsPositions create mode 100644 data/corefork.telegram.org/constructor/messages.sentEncryptedFile create mode 100644 data/corefork.telegram.org/constructor/messages.sentEncryptedMessage create mode 100644 data/corefork.telegram.org/constructor/messages.sentMessageLink create mode 100644 data/corefork.telegram.org/constructor/messages.sponsoredMessages create mode 100644 data/corefork.telegram.org/constructor/messages.statedMessageLink create mode 100644 data/corefork.telegram.org/constructor/messages.statedMessagesLinks create mode 100644 data/corefork.telegram.org/constructor/messages.stickerSet create mode 100644 data/corefork.telegram.org/constructor/messages.stickerSetInstallResultArchive create mode 100644 data/corefork.telegram.org/constructor/messages.stickerSetInstallResultSuccess create mode 100644 data/corefork.telegram.org/constructor/messages.stickers create mode 100644 data/corefork.telegram.org/constructor/messages.stickersNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.translateNoResult create mode 100644 data/corefork.telegram.org/constructor/messages.translateResultText create mode 100644 data/corefork.telegram.org/constructor/messages.votesList create mode 100644 data/corefork.telegram.org/constructor/nearestDc.html create mode 100644 data/corefork.telegram.org/constructor/notifyBroadcasts.html create mode 100644 data/corefork.telegram.org/constructor/notifyChats.html create mode 100644 data/corefork.telegram.org/constructor/notifyPeer.html create mode 100644 data/corefork.telegram.org/constructor/notifyUsers.html create mode 100644 data/corefork.telegram.org/constructor/null.html create mode 100644 data/corefork.telegram.org/constructor/page.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockAnchor.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockAudio.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockAuthorDate.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockBlockquote.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockChannel.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockCollage.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockCover.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockDetails.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockDivider.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockEmbed.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockEmbedPost.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockFooter.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockHeader.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockKicker.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockList.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockMap.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockOrderedList.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockParagraph.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockPhoto.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockPreformatted.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockPullquote.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockRelatedArticles.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockSlideshow.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockSubheader.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockSubtitle.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockTable.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockTitle.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockUnsupported.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockVideo.html create mode 100644 data/corefork.telegram.org/constructor/pageCaption.html create mode 100644 data/corefork.telegram.org/constructor/pageListItemBlocks.html create mode 100644 data/corefork.telegram.org/constructor/pageListItemText.html create mode 100644 data/corefork.telegram.org/constructor/pageListOrderedItemText.html create mode 100644 data/corefork.telegram.org/constructor/pageRelatedArticle.html create mode 100644 data/corefork.telegram.org/constructor/pageTableCell.html create mode 100644 data/corefork.telegram.org/constructor/pageTableRow.html create mode 100644 data/corefork.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html create mode 100644 data/corefork.telegram.org/constructor/passwordKdfAlgoUnknown.html create mode 100644 data/corefork.telegram.org/constructor/paymentCharge.html create mode 100644 data/corefork.telegram.org/constructor/paymentRequestedInfo.html create mode 100644 data/corefork.telegram.org/constructor/paymentSavedCredentialsCard.html create mode 100644 data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo create mode 100644 data/corefork.telegram.org/constructor/payments.bankCardData create mode 100644 data/corefork.telegram.org/constructor/payments.paymentForm create mode 100644 data/corefork.telegram.org/constructor/payments.paymentReceipt create mode 100644 data/corefork.telegram.org/constructor/payments.paymentResult create mode 100644 data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded create mode 100644 data/corefork.telegram.org/constructor/payments.savedInfo create mode 100644 data/corefork.telegram.org/constructor/peerBlocked.html create mode 100644 data/corefork.telegram.org/constructor/peerChannel.html create mode 100644 data/corefork.telegram.org/constructor/peerChat.html create mode 100644 data/corefork.telegram.org/constructor/peerLocated.html create mode 100644 data/corefork.telegram.org/constructor/peerNotifySettings.html create mode 100644 data/corefork.telegram.org/constructor/peerSelfLocated.html create mode 100644 data/corefork.telegram.org/constructor/peerSettings.html create mode 100644 data/corefork.telegram.org/constructor/peerUser.html create mode 100644 data/corefork.telegram.org/constructor/phone.exportedGroupCallInvite create mode 100644 data/corefork.telegram.org/constructor/phone.groupCall create mode 100644 data/corefork.telegram.org/constructor/phone.groupParticipants create mode 100644 data/corefork.telegram.org/constructor/phone.joinAsPeers create mode 100644 data/corefork.telegram.org/constructor/phone.phoneCall create mode 100644 data/corefork.telegram.org/constructor/phoneCall.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallAccepted.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonBusy.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonMissed.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscarded.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallEmpty.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallProtocol.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallRequested.html create mode 100644 data/corefork.telegram.org/constructor/phoneCallWaiting.html create mode 100644 data/corefork.telegram.org/constructor/phoneConnection.html create mode 100644 data/corefork.telegram.org/constructor/phoneConnectionWebrtc.html create mode 100644 data/corefork.telegram.org/constructor/photo.html create mode 100644 data/corefork.telegram.org/constructor/photoCachedSize.html create mode 100644 data/corefork.telegram.org/constructor/photoEmpty.html create mode 100644 data/corefork.telegram.org/constructor/photoPathSize.html create mode 100644 data/corefork.telegram.org/constructor/photoSize.html create mode 100644 data/corefork.telegram.org/constructor/photoSizeEmpty.html create mode 100644 data/corefork.telegram.org/constructor/photoSizeProgressive.html create mode 100644 data/corefork.telegram.org/constructor/photoStrippedSize.html create mode 100644 data/corefork.telegram.org/constructor/photos.photo create mode 100644 data/corefork.telegram.org/constructor/photos.photos create mode 100644 data/corefork.telegram.org/constructor/photos.photosSlice create mode 100644 data/corefork.telegram.org/constructor/poll.html create mode 100644 data/corefork.telegram.org/constructor/pollAnswer.html create mode 100644 data/corefork.telegram.org/constructor/pollAnswerVoters.html create mode 100644 data/corefork.telegram.org/constructor/pollResults.html create mode 100644 data/corefork.telegram.org/constructor/popularContact.html create mode 100644 data/corefork.telegram.org/constructor/postAddress.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyAddedByPhone.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyChatInvite.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyForwards.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyPhoneNumber.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyProfilePhoto.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowAll.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowContacts.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowUsers.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowAll.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowChatParticipants.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowContacts.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html create mode 100644 data/corefork.telegram.org/constructor/reactionCount.html create mode 100644 data/corefork.telegram.org/constructor/receivedNotifyMessage.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlChat.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlUnknown.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlUser.html create mode 100644 data/corefork.telegram.org/constructor/replyInlineMarkup.html create mode 100644 data/corefork.telegram.org/constructor/replyKeyboardForceReply.html create mode 100644 data/corefork.telegram.org/constructor/replyKeyboardHide.html create mode 100644 data/corefork.telegram.org/constructor/replyKeyboardMarkup.html create mode 100644 data/corefork.telegram.org/constructor/restrictionReason.html create mode 100644 data/corefork.telegram.org/constructor/savedPhoneContact.html create mode 100644 data/corefork.telegram.org/constructor/secureCredentialsEncrypted.html create mode 100644 data/corefork.telegram.org/constructor/secureData.html create mode 100644 data/corefork.telegram.org/constructor/secureFile.html create mode 100644 data/corefork.telegram.org/constructor/secureFileEmpty.html create mode 100644 data/corefork.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html create mode 100644 data/corefork.telegram.org/constructor/securePasswordKdfAlgoSHA512.html create mode 100644 data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html create mode 100644 data/corefork.telegram.org/constructor/securePlainEmail.html create mode 100644 data/corefork.telegram.org/constructor/securePlainPhone.html create mode 100644 data/corefork.telegram.org/constructor/secureRequiredType.html create mode 100644 data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html create mode 100644 data/corefork.telegram.org/constructor/secureSecretSettings.html create mode 100644 data/corefork.telegram.org/constructor/secureValue.html create mode 100644 data/corefork.telegram.org/constructor/secureValueError.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorData.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorFile.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorFiles.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorSelfie.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorTranslationFile.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorTranslationFiles.html create mode 100644 data/corefork.telegram.org/constructor/secureValueHash.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeAddress.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeDriverLicense.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeEmail.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeIdentityCard.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeInternalPassport.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypePassport.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypePassportRegistration.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypePhone.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeRentalAgreement.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeUtilityBill.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageCancelAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageChooseContactAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageChooseStickerAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageGamePlayAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageHistoryImportAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageRecordAudioAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageRecordRoundAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageRecordVideoAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageTypingAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadRoundAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadVideoAction.html create mode 100644 data/corefork.telegram.org/constructor/shippingOption.html create mode 100644 data/corefork.telegram.org/constructor/speakingInGroupCallAction.html create mode 100644 data/corefork.telegram.org/constructor/sponsoredMessage.html create mode 100644 data/corefork.telegram.org/constructor/stats.broadcastStats create mode 100644 data/corefork.telegram.org/constructor/stats.megagroupStats create mode 100644 data/corefork.telegram.org/constructor/stats.messageStats create mode 100644 data/corefork.telegram.org/constructor/statsAbsValueAndPrev.html create mode 100644 data/corefork.telegram.org/constructor/statsDateRangeDays.html create mode 100644 data/corefork.telegram.org/constructor/statsGraph.html create mode 100644 data/corefork.telegram.org/constructor/statsGraphAsync.html create mode 100644 data/corefork.telegram.org/constructor/statsGraphError.html create mode 100644 data/corefork.telegram.org/constructor/statsGroupTopAdmin.html create mode 100644 data/corefork.telegram.org/constructor/statsGroupTopInviter.html create mode 100644 data/corefork.telegram.org/constructor/statsGroupTopPoster.html create mode 100644 data/corefork.telegram.org/constructor/statsPercentValue.html create mode 100644 data/corefork.telegram.org/constructor/statsURL.html create mode 100644 data/corefork.telegram.org/constructor/stickerPack.html create mode 100644 data/corefork.telegram.org/constructor/stickerSet.html create mode 100644 data/corefork.telegram.org/constructor/stickerSetCovered.html create mode 100644 data/corefork.telegram.org/constructor/stickerSetMultiCovered.html create mode 100644 data/corefork.telegram.org/constructor/stickers.suggestedShortName create mode 100644 data/corefork.telegram.org/constructor/storage.fileGif create mode 100644 data/corefork.telegram.org/constructor/storage.fileJpeg create mode 100644 data/corefork.telegram.org/constructor/storage.fileMov create mode 100644 data/corefork.telegram.org/constructor/storage.fileMp3 create mode 100644 data/corefork.telegram.org/constructor/storage.fileMp4 create mode 100644 data/corefork.telegram.org/constructor/storage.filePartial create mode 100644 data/corefork.telegram.org/constructor/storage.filePdf create mode 100644 data/corefork.telegram.org/constructor/storage.filePng create mode 100644 data/corefork.telegram.org/constructor/storage.fileUnknown create mode 100644 data/corefork.telegram.org/constructor/storage.fileWebp create mode 100644 data/corefork.telegram.org/constructor/textAnchor.html create mode 100644 data/corefork.telegram.org/constructor/textBold.html create mode 100644 data/corefork.telegram.org/constructor/textConcat.html create mode 100644 data/corefork.telegram.org/constructor/textEmail.html create mode 100644 data/corefork.telegram.org/constructor/textEmpty.html create mode 100644 data/corefork.telegram.org/constructor/textFixed.html create mode 100644 data/corefork.telegram.org/constructor/textImage.html create mode 100644 data/corefork.telegram.org/constructor/textItalic.html create mode 100644 data/corefork.telegram.org/constructor/textMarked.html create mode 100644 data/corefork.telegram.org/constructor/textPhone.html create mode 100644 data/corefork.telegram.org/constructor/textPlain.html create mode 100644 data/corefork.telegram.org/constructor/textStrike.html create mode 100644 data/corefork.telegram.org/constructor/textSubscript.html create mode 100644 data/corefork.telegram.org/constructor/textSuperscript.html create mode 100644 data/corefork.telegram.org/constructor/textUnderline.html create mode 100644 data/corefork.telegram.org/constructor/textUrl.html create mode 100644 data/corefork.telegram.org/constructor/theme.html create mode 100644 data/corefork.telegram.org/constructor/themeSettings.html create mode 100644 data/corefork.telegram.org/constructor/topPeer.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryBotsInline.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryBotsPM.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryChannels.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryCorrespondents.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryForwardChats.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryGroups.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryPeers.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryPhoneCalls.html create mode 100644 data/corefork.telegram.org/constructor/true.html create mode 100644 data/corefork.telegram.org/constructor/updateBotCallbackQuery.html create mode 100644 data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html create mode 100644 data/corefork.telegram.org/constructor/updateBotCommands.html create mode 100644 data/corefork.telegram.org/constructor/updateBotInlineQuery.html create mode 100644 data/corefork.telegram.org/constructor/updateBotInlineSend.html create mode 100644 data/corefork.telegram.org/constructor/updateBotPrecheckoutQuery.html create mode 100644 data/corefork.telegram.org/constructor/updateBotShippingQuery.html create mode 100644 data/corefork.telegram.org/constructor/updateBotStopped.html create mode 100644 data/corefork.telegram.org/constructor/updateBotWebhookJSON.html create mode 100644 data/corefork.telegram.org/constructor/updateBotWebhookJSONQuery.html create mode 100644 data/corefork.telegram.org/constructor/updateChannel.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelMessageForwards.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelMessageViews.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelParticipant.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelTooLong.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelUserTyping.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelWebPage.html create mode 100644 data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html create mode 100644 data/corefork.telegram.org/constructor/updateChatParticipant.html create mode 100644 data/corefork.telegram.org/constructor/updateChatParticipantAdd.html create mode 100644 data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html create mode 100644 data/corefork.telegram.org/constructor/updateChatParticipantDelete.html create mode 100644 data/corefork.telegram.org/constructor/updateChatParticipants.html create mode 100644 data/corefork.telegram.org/constructor/updateConfig.html create mode 100644 data/corefork.telegram.org/constructor/updateContactsReset.html create mode 100644 data/corefork.telegram.org/constructor/updateDcOptions.html create mode 100644 data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html create mode 100644 data/corefork.telegram.org/constructor/updateDeleteMessages.html create mode 100644 data/corefork.telegram.org/constructor/updateDeleteScheduledMessages.html create mode 100644 data/corefork.telegram.org/constructor/updateDialogFilter.html create mode 100644 data/corefork.telegram.org/constructor/updateDialogFilterOrder.html create mode 100644 data/corefork.telegram.org/constructor/updateDialogFilters.html create mode 100644 data/corefork.telegram.org/constructor/updateDialogPinned.html create mode 100644 data/corefork.telegram.org/constructor/updateDialogUnreadMark.html create mode 100644 data/corefork.telegram.org/constructor/updateDraftMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateEditChannelMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html create mode 100644 data/corefork.telegram.org/constructor/updateEncryptedMessagesRead.html create mode 100644 data/corefork.telegram.org/constructor/updateEncryption.html create mode 100644 data/corefork.telegram.org/constructor/updateFavedStickers.html create mode 100644 data/corefork.telegram.org/constructor/updateFolderPeers.html create mode 100644 data/corefork.telegram.org/constructor/updateGeoLiveViewed.html create mode 100644 data/corefork.telegram.org/constructor/updateGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/updateGroupCallConnection.html create mode 100644 data/corefork.telegram.org/constructor/updateGroupCallParticipants.html create mode 100644 data/corefork.telegram.org/constructor/updateInlineBotCallbackQuery.html create mode 100644 data/corefork.telegram.org/constructor/updateLangPack.html create mode 100644 data/corefork.telegram.org/constructor/updateLangPackTooLong.html create mode 100644 data/corefork.telegram.org/constructor/updateMessageID.html create mode 100644 data/corefork.telegram.org/constructor/updateMessagePoll.html create mode 100644 data/corefork.telegram.org/constructor/updateMessagePollVote.html create mode 100644 data/corefork.telegram.org/constructor/updateMessageReactions.html create mode 100644 data/corefork.telegram.org/constructor/updateNewChannelMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateNewEncryptedMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateNewMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateNewScheduledMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateNewStickerSet.html create mode 100644 data/corefork.telegram.org/constructor/updatePeerBlocked.html create mode 100644 data/corefork.telegram.org/constructor/updatePeerHistoryTTL.html create mode 100644 data/corefork.telegram.org/constructor/updatePeerLocated.html create mode 100644 data/corefork.telegram.org/constructor/updatePeerSettings.html create mode 100644 data/corefork.telegram.org/constructor/updatePendingJoinRequests.html create mode 100644 data/corefork.telegram.org/constructor/updatePhoneCall.html create mode 100644 data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html create mode 100644 data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html create mode 100644 data/corefork.telegram.org/constructor/updatePinnedDialogs.html create mode 100644 data/corefork.telegram.org/constructor/updatePinnedMessages.html create mode 100644 data/corefork.telegram.org/constructor/updatePrivacy.html create mode 100644 data/corefork.telegram.org/constructor/updatePtsChanged.html create mode 100644 data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html create mode 100644 data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html create mode 100644 data/corefork.telegram.org/constructor/updateReadChannelInbox.html create mode 100644 data/corefork.telegram.org/constructor/updateReadChannelOutbox.html create mode 100644 data/corefork.telegram.org/constructor/updateReadFeaturedStickers.html create mode 100644 data/corefork.telegram.org/constructor/updateReadHistoryInbox.html create mode 100644 data/corefork.telegram.org/constructor/updateReadHistoryOutbox.html create mode 100644 data/corefork.telegram.org/constructor/updateReadMessagesContents.html create mode 100644 data/corefork.telegram.org/constructor/updateRecentStickers.html create mode 100644 data/corefork.telegram.org/constructor/updateServiceNotification.html create mode 100644 data/corefork.telegram.org/constructor/updateShort.html create mode 100644 data/corefork.telegram.org/constructor/updateShortChatMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateShortMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateShortSentMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateStickerSets.html create mode 100644 data/corefork.telegram.org/constructor/updateStickerSetsOrder.html create mode 100644 data/corefork.telegram.org/constructor/updateTheme.html create mode 100644 data/corefork.telegram.org/constructor/updateUserBlocked.html create mode 100644 data/corefork.telegram.org/constructor/updateUserName.html create mode 100644 data/corefork.telegram.org/constructor/updateUserPhone.html create mode 100644 data/corefork.telegram.org/constructor/updateUserPhoto.html create mode 100644 data/corefork.telegram.org/constructor/updateUserStatus.html create mode 100644 data/corefork.telegram.org/constructor/updateUserTyping.html create mode 100644 data/corefork.telegram.org/constructor/updateWebPage.html create mode 100644 data/corefork.telegram.org/constructor/updates.channelDifference create mode 100644 data/corefork.telegram.org/constructor/updates.channelDifferenceEmpty create mode 100644 data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong create mode 100644 data/corefork.telegram.org/constructor/updates.difference create mode 100644 data/corefork.telegram.org/constructor/updates.differenceEmpty create mode 100644 data/corefork.telegram.org/constructor/updates.differenceSlice create mode 100644 data/corefork.telegram.org/constructor/updates.differenceTooLong create mode 100644 data/corefork.telegram.org/constructor/updates.html create mode 100644 data/corefork.telegram.org/constructor/updates.state create mode 100644 data/corefork.telegram.org/constructor/updatesCombined.html create mode 100644 data/corefork.telegram.org/constructor/updatesTooLong.html create mode 100644 data/corefork.telegram.org/constructor/upload.cdnFile create mode 100644 data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded create mode 100644 data/corefork.telegram.org/constructor/upload.file create mode 100644 data/corefork.telegram.org/constructor/upload.fileCdnRedirect create mode 100644 data/corefork.telegram.org/constructor/upload.webFile create mode 100644 data/corefork.telegram.org/constructor/urlAuthResultAccepted.html create mode 100644 data/corefork.telegram.org/constructor/urlAuthResultDefault.html create mode 100644 data/corefork.telegram.org/constructor/urlAuthResultRequest.html create mode 100644 data/corefork.telegram.org/constructor/user.html create mode 100644 data/corefork.telegram.org/constructor/userEmpty.html create mode 100644 data/corefork.telegram.org/constructor/userFull.html create mode 100644 data/corefork.telegram.org/constructor/userProfilePhoto.html create mode 100644 data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html create mode 100644 data/corefork.telegram.org/constructor/userStatusEmpty.html create mode 100644 data/corefork.telegram.org/constructor/userStatusLastMonth.html create mode 100644 data/corefork.telegram.org/constructor/userStatusLastWeek.html create mode 100644 data/corefork.telegram.org/constructor/userStatusOffline.html create mode 100644 data/corefork.telegram.org/constructor/userStatusOnline.html create mode 100644 data/corefork.telegram.org/constructor/userStatusRecently.html create mode 100644 data/corefork.telegram.org/constructor/users.userFull create mode 100644 data/corefork.telegram.org/constructor/vector.html create mode 100644 data/corefork.telegram.org/constructor/wallPaper.html create mode 100644 data/corefork.telegram.org/constructor/wallPaperNoFile.html create mode 100644 data/corefork.telegram.org/constructor/wallPaperSettings.html create mode 100644 data/corefork.telegram.org/constructor/wallPaperSolid.html create mode 100644 data/corefork.telegram.org/constructor/webAuthorization.html create mode 100644 data/corefork.telegram.org/constructor/webDocument.html create mode 100644 data/corefork.telegram.org/constructor/webDocumentNoProxy.html create mode 100644 data/corefork.telegram.org/constructor/webPage.html create mode 100644 data/corefork.telegram.org/constructor/webPageAttributeTheme.html create mode 100644 data/corefork.telegram.org/constructor/webPageEmpty.html create mode 100644 data/corefork.telegram.org/constructor/webPageNotModified.html create mode 100644 data/corefork.telegram.org/constructor/webPagePending.html create mode 100644 data/corefork.telegram.org/getProxyConfig.html create mode 100644 data/corefork.telegram.org/import-stickers.html create mode 100644 data/corefork.telegram.org/method/account.acceptAuthorization create mode 100644 data/corefork.telegram.org/method/account.cancelPasswordEmail create mode 100644 data/corefork.telegram.org/method/account.changeAuthorizationSettings create mode 100644 data/corefork.telegram.org/method/account.changePhone create mode 100644 data/corefork.telegram.org/method/account.checkUsername create mode 100644 data/corefork.telegram.org/method/account.confirmPasswordEmail create mode 100644 data/corefork.telegram.org/method/account.confirmPhone create mode 100644 data/corefork.telegram.org/method/account.createTheme create mode 100644 data/corefork.telegram.org/method/account.declinePasswordReset create mode 100644 data/corefork.telegram.org/method/account.deleteAccount create mode 100644 data/corefork.telegram.org/method/account.finishTakeoutSession create mode 100644 data/corefork.telegram.org/method/account.getAccountTTL create mode 100644 data/corefork.telegram.org/method/account.getAllSecureValues create mode 100644 data/corefork.telegram.org/method/account.getAuthorizationForm create mode 100644 data/corefork.telegram.org/method/account.getAuthorizations create mode 100644 data/corefork.telegram.org/method/account.getAutoDownloadSettings create mode 100644 data/corefork.telegram.org/method/account.getChatThemes create mode 100644 data/corefork.telegram.org/method/account.getContactSignUpNotification create mode 100644 data/corefork.telegram.org/method/account.getContentSettings create mode 100644 data/corefork.telegram.org/method/account.getGlobalPrivacySettings create mode 100644 data/corefork.telegram.org/method/account.getMultiWallPapers create mode 100644 data/corefork.telegram.org/method/account.getNotifyExceptions create mode 100644 data/corefork.telegram.org/method/account.getNotifySettings create mode 100644 data/corefork.telegram.org/method/account.getPassword create mode 100644 data/corefork.telegram.org/method/account.getPrivacy create mode 100644 data/corefork.telegram.org/method/account.getSecureValue create mode 100644 data/corefork.telegram.org/method/account.getTheme create mode 100644 data/corefork.telegram.org/method/account.getThemes create mode 100644 data/corefork.telegram.org/method/account.getTmpPassword create mode 100644 data/corefork.telegram.org/method/account.getWallPaper create mode 100644 data/corefork.telegram.org/method/account.getWallPapers create mode 100644 data/corefork.telegram.org/method/account.getWebAuthorizations create mode 100644 data/corefork.telegram.org/method/account.initTakeoutSession create mode 100644 data/corefork.telegram.org/method/account.installTheme create mode 100644 data/corefork.telegram.org/method/account.installWallPaper create mode 100644 data/corefork.telegram.org/method/account.registerDevice create mode 100644 data/corefork.telegram.org/method/account.reportPeer create mode 100644 data/corefork.telegram.org/method/account.reportProfilePhoto create mode 100644 data/corefork.telegram.org/method/account.resendPasswordEmail create mode 100644 data/corefork.telegram.org/method/account.resetAuthorization create mode 100644 data/corefork.telegram.org/method/account.resetNotifySettings create mode 100644 data/corefork.telegram.org/method/account.resetPassword create mode 100644 data/corefork.telegram.org/method/account.resetWallPapers create mode 100644 data/corefork.telegram.org/method/account.resetWebAuthorization create mode 100644 data/corefork.telegram.org/method/account.resetWebAuthorizations create mode 100644 data/corefork.telegram.org/method/account.saveAutoDownloadSettings create mode 100644 data/corefork.telegram.org/method/account.saveSecureValue create mode 100644 data/corefork.telegram.org/method/account.sendChangePhoneCode create mode 100644 data/corefork.telegram.org/method/account.sendConfirmPhoneCode create mode 100644 data/corefork.telegram.org/method/account.sendVerifyEmailCode create mode 100644 data/corefork.telegram.org/method/account.sendVerifyPhoneCode create mode 100644 data/corefork.telegram.org/method/account.setAccountTTL create mode 100644 data/corefork.telegram.org/method/account.setAuthorizationTTL create mode 100644 data/corefork.telegram.org/method/account.setContactSignUpNotification create mode 100644 data/corefork.telegram.org/method/account.setContentSettings create mode 100644 data/corefork.telegram.org/method/account.setGlobalPrivacySettings create mode 100644 data/corefork.telegram.org/method/account.setPrivacy create mode 100644 data/corefork.telegram.org/method/account.unregisterDevice create mode 100644 data/corefork.telegram.org/method/account.updateDeviceLocked create mode 100644 data/corefork.telegram.org/method/account.updateNotifySettings create mode 100644 data/corefork.telegram.org/method/account.updatePasswordSettings create mode 100644 data/corefork.telegram.org/method/account.updateProfile create mode 100644 data/corefork.telegram.org/method/account.updateStatus create mode 100644 data/corefork.telegram.org/method/account.updateTheme create mode 100644 data/corefork.telegram.org/method/account.updateUsername create mode 100644 data/corefork.telegram.org/method/account.uploadTheme create mode 100644 data/corefork.telegram.org/method/account.uploadWallPaper create mode 100644 data/corefork.telegram.org/method/account.verifyEmail create mode 100644 data/corefork.telegram.org/method/account.verifyPhone create mode 100644 data/corefork.telegram.org/method/auth.acceptLoginToken create mode 100644 data/corefork.telegram.org/method/auth.bindTempAuthKey create mode 100644 data/corefork.telegram.org/method/auth.cancelCode create mode 100644 data/corefork.telegram.org/method/auth.checkPassword create mode 100644 data/corefork.telegram.org/method/auth.checkPhone create mode 100644 data/corefork.telegram.org/method/auth.checkRecoveryPassword create mode 100644 data/corefork.telegram.org/method/auth.dropTempAuthKeys create mode 100644 data/corefork.telegram.org/method/auth.exportAuthorization create mode 100644 data/corefork.telegram.org/method/auth.exportLoginToken create mode 100644 data/corefork.telegram.org/method/auth.importAuthorization create mode 100644 data/corefork.telegram.org/method/auth.importBotAuthorization create mode 100644 data/corefork.telegram.org/method/auth.importLoginToken create mode 100644 data/corefork.telegram.org/method/auth.logOut create mode 100644 data/corefork.telegram.org/method/auth.recoverPassword create mode 100644 data/corefork.telegram.org/method/auth.requestPasswordRecovery create mode 100644 data/corefork.telegram.org/method/auth.resendCode create mode 100644 data/corefork.telegram.org/method/auth.resetAuthorizations create mode 100644 data/corefork.telegram.org/method/auth.sendCall create mode 100644 data/corefork.telegram.org/method/auth.sendCode create mode 100644 data/corefork.telegram.org/method/auth.sendInvites create mode 100644 data/corefork.telegram.org/method/auth.sendSms create mode 100644 data/corefork.telegram.org/method/auth.signIn create mode 100644 data/corefork.telegram.org/method/auth.signUp create mode 100644 data/corefork.telegram.org/method/bots.answerWebhookJSONQuery create mode 100644 data/corefork.telegram.org/method/bots.getBotCommands create mode 100644 data/corefork.telegram.org/method/bots.resetBotCommands create mode 100644 data/corefork.telegram.org/method/bots.sendCustomRequest create mode 100644 data/corefork.telegram.org/method/bots.setBotCommands create mode 100644 data/corefork.telegram.org/method/channels.checkUsername create mode 100644 data/corefork.telegram.org/method/channels.convertToGigagroup create mode 100644 data/corefork.telegram.org/method/channels.createChannel create mode 100644 data/corefork.telegram.org/method/channels.deleteChannel create mode 100644 data/corefork.telegram.org/method/channels.deleteHistory create mode 100644 data/corefork.telegram.org/method/channels.deleteMessages create mode 100644 data/corefork.telegram.org/method/channels.deleteParticipantHistory create mode 100644 data/corefork.telegram.org/method/channels.deleteUserHistory create mode 100644 data/corefork.telegram.org/method/channels.editAdmin create mode 100644 data/corefork.telegram.org/method/channels.editBanned create mode 100644 data/corefork.telegram.org/method/channels.editCreator create mode 100644 data/corefork.telegram.org/method/channels.editLocation create mode 100644 data/corefork.telegram.org/method/channels.editPhoto create mode 100644 data/corefork.telegram.org/method/channels.exportMessageLink create mode 100644 data/corefork.telegram.org/method/channels.getAdminLog create mode 100644 data/corefork.telegram.org/method/channels.getAdminedPublicChannels create mode 100644 data/corefork.telegram.org/method/channels.getChannels create mode 100644 data/corefork.telegram.org/method/channels.getFullChannel create mode 100644 data/corefork.telegram.org/method/channels.getGroupsForDiscussion create mode 100644 data/corefork.telegram.org/method/channels.getInactiveChannels create mode 100644 data/corefork.telegram.org/method/channels.getLeftChannels create mode 100644 data/corefork.telegram.org/method/channels.getMessages create mode 100644 data/corefork.telegram.org/method/channels.getParticipant create mode 100644 data/corefork.telegram.org/method/channels.getParticipants create mode 100644 data/corefork.telegram.org/method/channels.getSendAs create mode 100644 data/corefork.telegram.org/method/channels.getSponsoredMessages create mode 100644 data/corefork.telegram.org/method/channels.inviteToChannel create mode 100644 data/corefork.telegram.org/method/channels.joinChannel create mode 100644 data/corefork.telegram.org/method/channels.leaveChannel create mode 100644 data/corefork.telegram.org/method/channels.readHistory create mode 100644 data/corefork.telegram.org/method/channels.readMessageContents create mode 100644 data/corefork.telegram.org/method/channels.reportSpam create mode 100644 data/corefork.telegram.org/method/channels.setDiscussionGroup create mode 100644 data/corefork.telegram.org/method/channels.setStickers create mode 100644 data/corefork.telegram.org/method/channels.togglePreHistoryHidden create mode 100644 data/corefork.telegram.org/method/channels.toggleSignatures create mode 100644 data/corefork.telegram.org/method/channels.toggleSlowMode create mode 100644 data/corefork.telegram.org/method/channels.updateUsername create mode 100644 data/corefork.telegram.org/method/channels.viewSponsoredMessage create mode 100644 data/corefork.telegram.org/method/contacts.acceptContact create mode 100644 data/corefork.telegram.org/method/contacts.addContact create mode 100644 data/corefork.telegram.org/method/contacts.block create mode 100644 data/corefork.telegram.org/method/contacts.deleteByPhones create mode 100644 data/corefork.telegram.org/method/contacts.deleteContacts create mode 100644 data/corefork.telegram.org/method/contacts.getBlocked create mode 100644 data/corefork.telegram.org/method/contacts.getContactIDs create mode 100644 data/corefork.telegram.org/method/contacts.getContacts create mode 100644 data/corefork.telegram.org/method/contacts.getLocated create mode 100644 data/corefork.telegram.org/method/contacts.getSaved create mode 100644 data/corefork.telegram.org/method/contacts.getStatuses create mode 100644 data/corefork.telegram.org/method/contacts.getTopPeers create mode 100644 data/corefork.telegram.org/method/contacts.importContacts create mode 100644 data/corefork.telegram.org/method/contacts.resetSaved create mode 100644 data/corefork.telegram.org/method/contacts.resetTopPeerRating create mode 100644 data/corefork.telegram.org/method/contacts.resolveUsername create mode 100644 data/corefork.telegram.org/method/contacts.search create mode 100644 data/corefork.telegram.org/method/contacts.toggleTopPeers create mode 100644 data/corefork.telegram.org/method/contacts.unblock create mode 100644 data/corefork.telegram.org/method/folders.deleteFolder create mode 100644 data/corefork.telegram.org/method/folders.editPeerFolders create mode 100644 data/corefork.telegram.org/method/help.acceptTermsOfService create mode 100644 data/corefork.telegram.org/method/help.dismissSuggestion create mode 100644 data/corefork.telegram.org/method/help.editUserInfo create mode 100644 data/corefork.telegram.org/method/help.getAppChangelog create mode 100644 data/corefork.telegram.org/method/help.getAppConfig create mode 100644 data/corefork.telegram.org/method/help.getAppUpdate create mode 100644 data/corefork.telegram.org/method/help.getCdnConfig create mode 100644 data/corefork.telegram.org/method/help.getConfig create mode 100644 data/corefork.telegram.org/method/help.getCountriesList create mode 100644 data/corefork.telegram.org/method/help.getDeepLinkInfo create mode 100644 data/corefork.telegram.org/method/help.getInviteText create mode 100644 data/corefork.telegram.org/method/help.getNearestDc create mode 100644 data/corefork.telegram.org/method/help.getPassportConfig create mode 100644 data/corefork.telegram.org/method/help.getPromoData create mode 100644 data/corefork.telegram.org/method/help.getProxyData create mode 100644 data/corefork.telegram.org/method/help.getRecentMeUrls create mode 100644 data/corefork.telegram.org/method/help.getSupport create mode 100644 data/corefork.telegram.org/method/help.getSupportName create mode 100644 data/corefork.telegram.org/method/help.getTermsOfServiceUpdate create mode 100644 data/corefork.telegram.org/method/help.getUserInfo create mode 100644 data/corefork.telegram.org/method/help.hidePromoData create mode 100644 data/corefork.telegram.org/method/help.saveAppLog create mode 100644 data/corefork.telegram.org/method/help.setBotUpdatesStatus create mode 100644 data/corefork.telegram.org/method/initConnection.html create mode 100644 data/corefork.telegram.org/method/invokeAfterMsg.html create mode 100644 data/corefork.telegram.org/method/invokeAfterMsgs.html create mode 100644 data/corefork.telegram.org/method/invokeWithLayer.html create mode 100644 data/corefork.telegram.org/method/invokeWithMessagesRange.html create mode 100644 data/corefork.telegram.org/method/invokeWithTakeout.html create mode 100644 data/corefork.telegram.org/method/invokeWithoutUpdates.html create mode 100644 data/corefork.telegram.org/method/langpack.getDifference create mode 100644 data/corefork.telegram.org/method/langpack.getLangPack create mode 100644 data/corefork.telegram.org/method/langpack.getLanguage create mode 100644 data/corefork.telegram.org/method/langpack.getLanguages create mode 100644 data/corefork.telegram.org/method/langpack.getStrings create mode 100644 data/corefork.telegram.org/method/messages.acceptEncryption create mode 100644 data/corefork.telegram.org/method/messages.acceptUrlAuth create mode 100644 data/corefork.telegram.org/method/messages.addChatUser create mode 100644 data/corefork.telegram.org/method/messages.checkChatInvite create mode 100644 data/corefork.telegram.org/method/messages.checkHistoryImport create mode 100644 data/corefork.telegram.org/method/messages.checkHistoryImportPeer create mode 100644 data/corefork.telegram.org/method/messages.clearAllDrafts create mode 100644 data/corefork.telegram.org/method/messages.clearRecentStickers create mode 100644 data/corefork.telegram.org/method/messages.createChat create mode 100644 data/corefork.telegram.org/method/messages.deleteChat create mode 100644 data/corefork.telegram.org/method/messages.deleteChatUser create mode 100644 data/corefork.telegram.org/method/messages.deleteExportedChatInvite create mode 100644 data/corefork.telegram.org/method/messages.deleteHistory create mode 100644 data/corefork.telegram.org/method/messages.deleteMessages create mode 100644 data/corefork.telegram.org/method/messages.deletePhoneCallHistory create mode 100644 data/corefork.telegram.org/method/messages.deleteRevokedExportedChatInvites create mode 100644 data/corefork.telegram.org/method/messages.deleteScheduledMessages create mode 100644 data/corefork.telegram.org/method/messages.discardEncryption create mode 100644 data/corefork.telegram.org/method/messages.editChatAbout create mode 100644 data/corefork.telegram.org/method/messages.editChatAdmin create mode 100644 data/corefork.telegram.org/method/messages.editChatDefaultBannedRights create mode 100644 data/corefork.telegram.org/method/messages.editChatPhoto create mode 100644 data/corefork.telegram.org/method/messages.editChatTitle create mode 100644 data/corefork.telegram.org/method/messages.editExportedChatInvite create mode 100644 data/corefork.telegram.org/method/messages.editInlineBotMessage create mode 100644 data/corefork.telegram.org/method/messages.editMessage create mode 100644 data/corefork.telegram.org/method/messages.exportChatInvite create mode 100644 data/corefork.telegram.org/method/messages.faveSticker create mode 100644 data/corefork.telegram.org/method/messages.forwardMessage create mode 100644 data/corefork.telegram.org/method/messages.forwardMessages create mode 100644 data/corefork.telegram.org/method/messages.getAdminsWithInvites create mode 100644 data/corefork.telegram.org/method/messages.getAllChats create mode 100644 data/corefork.telegram.org/method/messages.getAllDrafts create mode 100644 data/corefork.telegram.org/method/messages.getAllStickers create mode 100644 data/corefork.telegram.org/method/messages.getArchivedStickers create mode 100644 data/corefork.telegram.org/method/messages.getAttachedStickers create mode 100644 data/corefork.telegram.org/method/messages.getAvailableReactions create mode 100644 data/corefork.telegram.org/method/messages.getBotCallbackAnswer create mode 100644 data/corefork.telegram.org/method/messages.getChatInviteImporters create mode 100644 data/corefork.telegram.org/method/messages.getChats create mode 100644 data/corefork.telegram.org/method/messages.getCommonChats create mode 100644 data/corefork.telegram.org/method/messages.getDhConfig create mode 100644 data/corefork.telegram.org/method/messages.getDialogFilters create mode 100644 data/corefork.telegram.org/method/messages.getDialogUnreadMarks create mode 100644 data/corefork.telegram.org/method/messages.getDiscussionMessage create mode 100644 data/corefork.telegram.org/method/messages.getDocumentByHash create mode 100644 data/corefork.telegram.org/method/messages.getEmojiKeywords create mode 100644 data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference create mode 100644 data/corefork.telegram.org/method/messages.getEmojiKeywordsLanguages create mode 100644 data/corefork.telegram.org/method/messages.getEmojiURL create mode 100644 data/corefork.telegram.org/method/messages.getExportedChatInvite create mode 100644 data/corefork.telegram.org/method/messages.getExportedChatInvites create mode 100644 data/corefork.telegram.org/method/messages.getFavedStickers create mode 100644 data/corefork.telegram.org/method/messages.getFeaturedStickers create mode 100644 data/corefork.telegram.org/method/messages.getFullChat create mode 100644 data/corefork.telegram.org/method/messages.getGameHighScores create mode 100644 data/corefork.telegram.org/method/messages.getHistory create mode 100644 data/corefork.telegram.org/method/messages.getInlineBotResults create mode 100644 data/corefork.telegram.org/method/messages.getInlineGameHighScores create mode 100644 data/corefork.telegram.org/method/messages.getMaskStickers create mode 100644 data/corefork.telegram.org/method/messages.getMessageEditData create mode 100644 data/corefork.telegram.org/method/messages.getMessageReactionsList create mode 100644 data/corefork.telegram.org/method/messages.getMessageReadParticipants create mode 100644 data/corefork.telegram.org/method/messages.getMessages create mode 100644 data/corefork.telegram.org/method/messages.getMessagesReactions create mode 100644 data/corefork.telegram.org/method/messages.getMessagesViews create mode 100644 data/corefork.telegram.org/method/messages.getOldFeaturedStickers create mode 100644 data/corefork.telegram.org/method/messages.getOnlines create mode 100644 data/corefork.telegram.org/method/messages.getPeerDialogs create mode 100644 data/corefork.telegram.org/method/messages.getPeerSettings create mode 100644 data/corefork.telegram.org/method/messages.getPinnedDialogs create mode 100644 data/corefork.telegram.org/method/messages.getPollResults create mode 100644 data/corefork.telegram.org/method/messages.getPollVotes create mode 100644 data/corefork.telegram.org/method/messages.getRecentLocations create mode 100644 data/corefork.telegram.org/method/messages.getRecentStickers create mode 100644 data/corefork.telegram.org/method/messages.getReplies create mode 100644 data/corefork.telegram.org/method/messages.getSavedGifs create mode 100644 data/corefork.telegram.org/method/messages.getScheduledHistory create mode 100644 data/corefork.telegram.org/method/messages.getScheduledMessages create mode 100644 data/corefork.telegram.org/method/messages.getSearchCounters create mode 100644 data/corefork.telegram.org/method/messages.getSearchResultsCalendar create mode 100644 data/corefork.telegram.org/method/messages.getSearchResultsPositions create mode 100644 data/corefork.telegram.org/method/messages.getStickerSet create mode 100644 data/corefork.telegram.org/method/messages.getStickers create mode 100644 data/corefork.telegram.org/method/messages.getSuggestedDialogFilters create mode 100644 data/corefork.telegram.org/method/messages.getUnreadMentions create mode 100644 data/corefork.telegram.org/method/messages.getUnreadReactions create mode 100644 data/corefork.telegram.org/method/messages.getWebPage create mode 100644 data/corefork.telegram.org/method/messages.getWebPagePreview create mode 100644 data/corefork.telegram.org/method/messages.hideAllChatJoinRequests create mode 100644 data/corefork.telegram.org/method/messages.hideChatJoinRequest create mode 100644 data/corefork.telegram.org/method/messages.hidePeerSettingsBar create mode 100644 data/corefork.telegram.org/method/messages.importChatInvite create mode 100644 data/corefork.telegram.org/method/messages.initHistoryImport create mode 100644 data/corefork.telegram.org/method/messages.installStickerSet create mode 100644 data/corefork.telegram.org/method/messages.markDialogUnread create mode 100644 data/corefork.telegram.org/method/messages.migrateChat create mode 100644 data/corefork.telegram.org/method/messages.readDiscussion create mode 100644 data/corefork.telegram.org/method/messages.readEncryptedHistory create mode 100644 data/corefork.telegram.org/method/messages.readFeaturedStickers create mode 100644 data/corefork.telegram.org/method/messages.readHistory create mode 100644 data/corefork.telegram.org/method/messages.readMentions create mode 100644 data/corefork.telegram.org/method/messages.readMessageContents create mode 100644 data/corefork.telegram.org/method/messages.readReactions create mode 100644 data/corefork.telegram.org/method/messages.receivedMessages create mode 100644 data/corefork.telegram.org/method/messages.receivedQueue create mode 100644 data/corefork.telegram.org/method/messages.reorderPinnedDialogs create mode 100644 data/corefork.telegram.org/method/messages.reorderStickerSets create mode 100644 data/corefork.telegram.org/method/messages.report create mode 100644 data/corefork.telegram.org/method/messages.reportEncryptedSpam create mode 100644 data/corefork.telegram.org/method/messages.reportSpam create mode 100644 data/corefork.telegram.org/method/messages.requestEncryption create mode 100644 data/corefork.telegram.org/method/messages.requestUrlAuth create mode 100644 data/corefork.telegram.org/method/messages.saveDefaultSendAs create mode 100644 data/corefork.telegram.org/method/messages.saveDraft create mode 100644 data/corefork.telegram.org/method/messages.saveGif create mode 100644 data/corefork.telegram.org/method/messages.saveRecentSticker create mode 100644 data/corefork.telegram.org/method/messages.search create mode 100644 data/corefork.telegram.org/method/messages.searchGifs create mode 100644 data/corefork.telegram.org/method/messages.searchGlobal create mode 100644 data/corefork.telegram.org/method/messages.searchStickerSets create mode 100644 data/corefork.telegram.org/method/messages.sendBroadcast create mode 100644 data/corefork.telegram.org/method/messages.sendEncrypted create mode 100644 data/corefork.telegram.org/method/messages.sendEncryptedFile create mode 100644 data/corefork.telegram.org/method/messages.sendEncryptedService create mode 100644 data/corefork.telegram.org/method/messages.sendInlineBotResult create mode 100644 data/corefork.telegram.org/method/messages.sendMedia create mode 100644 data/corefork.telegram.org/method/messages.sendMessage create mode 100644 data/corefork.telegram.org/method/messages.sendMultiMedia create mode 100644 data/corefork.telegram.org/method/messages.sendReaction create mode 100644 data/corefork.telegram.org/method/messages.sendScheduledMessages create mode 100644 data/corefork.telegram.org/method/messages.sendScreenshotNotification create mode 100644 data/corefork.telegram.org/method/messages.sendVote create mode 100644 data/corefork.telegram.org/method/messages.setBotCallbackAnswer create mode 100644 data/corefork.telegram.org/method/messages.setBotPrecheckoutResults create mode 100644 data/corefork.telegram.org/method/messages.setBotShippingResults create mode 100644 data/corefork.telegram.org/method/messages.setChatAvailableReactions create mode 100644 data/corefork.telegram.org/method/messages.setChatTheme create mode 100644 data/corefork.telegram.org/method/messages.setDefaultReaction create mode 100644 data/corefork.telegram.org/method/messages.setEncryptedTyping create mode 100644 data/corefork.telegram.org/method/messages.setGameScore create mode 100644 data/corefork.telegram.org/method/messages.setHistoryTTL create mode 100644 data/corefork.telegram.org/method/messages.setInlineBotResults create mode 100644 data/corefork.telegram.org/method/messages.setInlineGameScore create mode 100644 data/corefork.telegram.org/method/messages.setTyping create mode 100644 data/corefork.telegram.org/method/messages.startBot create mode 100644 data/corefork.telegram.org/method/messages.startHistoryImport create mode 100644 data/corefork.telegram.org/method/messages.toggleDialogPin create mode 100644 data/corefork.telegram.org/method/messages.toggleNoForwards create mode 100644 data/corefork.telegram.org/method/messages.toggleStickerSets create mode 100644 data/corefork.telegram.org/method/messages.translateText create mode 100644 data/corefork.telegram.org/method/messages.uninstallStickerSet create mode 100644 data/corefork.telegram.org/method/messages.unpinAllMessages create mode 100644 data/corefork.telegram.org/method/messages.updateDialogFilter create mode 100644 data/corefork.telegram.org/method/messages.updateDialogFiltersOrder create mode 100644 data/corefork.telegram.org/method/messages.updatePinnedMessage create mode 100644 data/corefork.telegram.org/method/messages.uploadEncryptedFile create mode 100644 data/corefork.telegram.org/method/messages.uploadImportedMedia create mode 100644 data/corefork.telegram.org/method/messages.uploadMedia create mode 100644 data/corefork.telegram.org/method/payments.clearSavedInfo create mode 100644 data/corefork.telegram.org/method/payments.getPaymentForm create mode 100644 data/corefork.telegram.org/method/payments.getPaymentReceipt create mode 100644 data/corefork.telegram.org/method/payments.getSavedInfo create mode 100644 data/corefork.telegram.org/method/payments.sendPaymentForm create mode 100644 data/corefork.telegram.org/method/phone.acceptCall create mode 100644 data/corefork.telegram.org/method/phone.checkGroupCall create mode 100644 data/corefork.telegram.org/method/phone.confirmCall create mode 100644 data/corefork.telegram.org/method/phone.createGroupCall create mode 100644 data/corefork.telegram.org/method/phone.discardCall create mode 100644 data/corefork.telegram.org/method/phone.discardGroupCall create mode 100644 data/corefork.telegram.org/method/phone.editGroupCallMember create mode 100644 data/corefork.telegram.org/method/phone.editGroupCallParticipant create mode 100644 data/corefork.telegram.org/method/phone.editGroupCallTitle create mode 100644 data/corefork.telegram.org/method/phone.exportGroupCallInvite create mode 100644 data/corefork.telegram.org/method/phone.getCallConfig create mode 100644 data/corefork.telegram.org/method/phone.getGroupCall create mode 100644 data/corefork.telegram.org/method/phone.getGroupCallJoinAs create mode 100644 data/corefork.telegram.org/method/phone.getGroupParticipants create mode 100644 data/corefork.telegram.org/method/phone.inviteToGroupCall create mode 100644 data/corefork.telegram.org/method/phone.joinGroupCall create mode 100644 data/corefork.telegram.org/method/phone.joinGroupCallPresentation create mode 100644 data/corefork.telegram.org/method/phone.leaveGroupCall create mode 100644 data/corefork.telegram.org/method/phone.leaveGroupCallPresentation create mode 100644 data/corefork.telegram.org/method/phone.receivedCall create mode 100644 data/corefork.telegram.org/method/phone.saveCallDebug create mode 100644 data/corefork.telegram.org/method/phone.saveDefaultGroupCallJoinAs create mode 100644 data/corefork.telegram.org/method/phone.sendSignalingData create mode 100644 data/corefork.telegram.org/method/phone.setCallRating create mode 100644 data/corefork.telegram.org/method/phone.startScheduledGroupCall create mode 100644 data/corefork.telegram.org/method/phone.toggleGroupCallRecord create mode 100644 data/corefork.telegram.org/method/phone.toggleGroupCallSettings create mode 100644 data/corefork.telegram.org/method/photos.deletePhotos create mode 100644 data/corefork.telegram.org/method/photos.getUserPhotos create mode 100644 data/corefork.telegram.org/method/photos.updateProfilePhoto create mode 100644 data/corefork.telegram.org/method/photos.uploadProfilePhoto create mode 100644 data/corefork.telegram.org/method/stats.getBroadcastStats create mode 100644 data/corefork.telegram.org/method/stats.getMegagroupStats create mode 100644 data/corefork.telegram.org/method/stats.getMessageStats create mode 100644 data/corefork.telegram.org/method/stats.loadAsyncGraph create mode 100644 data/corefork.telegram.org/method/stickers.addStickerToSet create mode 100644 data/corefork.telegram.org/method/stickers.changeStickerPosition create mode 100644 data/corefork.telegram.org/method/stickers.checkShortName create mode 100644 data/corefork.telegram.org/method/stickers.createStickerSet create mode 100644 data/corefork.telegram.org/method/stickers.removeStickerFromSet create mode 100644 data/corefork.telegram.org/method/stickers.setStickerSetThumb create mode 100644 data/corefork.telegram.org/method/stickers.suggestShortName create mode 100644 data/corefork.telegram.org/method/updates.getChannelDifference create mode 100644 data/corefork.telegram.org/method/updates.getDifference create mode 100644 data/corefork.telegram.org/method/updates.getState create mode 100644 data/corefork.telegram.org/method/upload.getCdnFile create mode 100644 data/corefork.telegram.org/method/upload.getCdnFileHashes create mode 100644 data/corefork.telegram.org/method/upload.getFile create mode 100644 data/corefork.telegram.org/method/upload.getFileHashes create mode 100644 data/corefork.telegram.org/method/upload.getWebFile create mode 100644 data/corefork.telegram.org/method/upload.reuploadCdnFile create mode 100644 data/corefork.telegram.org/method/upload.saveBigFilePart create mode 100644 data/corefork.telegram.org/method/upload.saveFilePart create mode 100644 data/corefork.telegram.org/method/users.getFullUser create mode 100644 data/corefork.telegram.org/method/users.getUsers create mode 100644 data/corefork.telegram.org/method/users.setSecureValueErrors create mode 100644 data/corefork.telegram.org/methods.html create mode 100644 data/corefork.telegram.org/mtproto.html create mode 100644 data/corefork.telegram.org/mtproto/TL-abstract-types.html create mode 100644 data/corefork.telegram.org/mtproto/TL-combinators.html create mode 100644 data/corefork.telegram.org/mtproto/TL-dependent.html create mode 100644 data/corefork.telegram.org/mtproto/TL-formal.html create mode 100644 data/corefork.telegram.org/mtproto/TL-optargs.html create mode 100644 data/corefork.telegram.org/mtproto/TL-patterns.html create mode 100644 data/corefork.telegram.org/mtproto/TL-polymorph.html create mode 100644 data/corefork.telegram.org/mtproto/TL-tl.html create mode 100644 data/corefork.telegram.org/mtproto/TL-types.html create mode 100644 data/corefork.telegram.org/mtproto/TL.html create mode 100644 data/corefork.telegram.org/mtproto/auth_key.html create mode 100644 data/corefork.telegram.org/mtproto/description.html create mode 100644 data/corefork.telegram.org/mtproto/description_v1.html create mode 100644 data/corefork.telegram.org/mtproto/mtproto-transports.html create mode 100644 data/corefork.telegram.org/mtproto/samples-auth_key.html create mode 100644 data/corefork.telegram.org/mtproto/security_guidelines.html create mode 100644 data/corefork.telegram.org/mtproto/security_guidelines_v1.html create mode 100644 data/corefork.telegram.org/mtproto/serialize.html create mode 100644 data/corefork.telegram.org/mtproto/service_messages_about_messages.html create mode 100644 data/corefork.telegram.org/mtproto_v1.html create mode 100644 data/corefork.telegram.org/passport.html create mode 100644 data/corefork.telegram.org/passport/encryption.html create mode 100644 data/corefork.telegram.org/passport/example.html create mode 100644 data/corefork.telegram.org/passport/sdk-android.html create mode 100644 data/corefork.telegram.org/passport/sdk-ios-mac.html create mode 100644 data/corefork.telegram.org/passport/sdk-javascript.html create mode 100644 data/corefork.telegram.org/schema.html create mode 100644 data/corefork.telegram.org/schema/end-to-end-json.html create mode 100644 data/corefork.telegram.org/schema/end-to-end.html create mode 100644 data/corefork.telegram.org/schema/json.html create mode 100644 data/corefork.telegram.org/schema/mtproto-json.html create mode 100644 data/corefork.telegram.org/schema/mtproto.html create mode 100644 data/corefork.telegram.org/themes.html create mode 100644 data/corefork.telegram.org/type/AccountDaysTTL.html create mode 100644 data/corefork.telegram.org/type/Audio.html create mode 100644 data/corefork.telegram.org/type/Authorization.html create mode 100644 data/corefork.telegram.org/type/AutoDownloadSettings.html create mode 100644 data/corefork.telegram.org/type/AvailableReaction.html create mode 100644 data/corefork.telegram.org/type/BankCardOpenUrl.html create mode 100644 data/corefork.telegram.org/type/BaseTheme.html create mode 100644 data/corefork.telegram.org/type/Bool.html create mode 100644 data/corefork.telegram.org/type/BotCommand.html create mode 100644 data/corefork.telegram.org/type/BotCommandScope.html create mode 100644 data/corefork.telegram.org/type/BotInfo.html create mode 100644 data/corefork.telegram.org/type/BotInlineResult.html create mode 100644 data/corefork.telegram.org/type/CdnConfig.html create mode 100644 data/corefork.telegram.org/type/CdnPublicKey.html create mode 100644 data/corefork.telegram.org/type/ChannelAdminLogEvent.html create mode 100644 data/corefork.telegram.org/type/ChannelAdminLogEventAction.html create mode 100644 data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html create mode 100644 data/corefork.telegram.org/type/ChannelLocation.html create mode 100644 data/corefork.telegram.org/type/ChannelMessagesFilter.html create mode 100644 data/corefork.telegram.org/type/ChannelParticipant.html create mode 100644 data/corefork.telegram.org/type/ChannelParticipantsFilter.html create mode 100644 data/corefork.telegram.org/type/Chat.html create mode 100644 data/corefork.telegram.org/type/ChatAdminRights.html create mode 100644 data/corefork.telegram.org/type/ChatAdminWithInvites.html create mode 100644 data/corefork.telegram.org/type/ChatBannedRights.html create mode 100644 data/corefork.telegram.org/type/ChatFull.html create mode 100644 data/corefork.telegram.org/type/ChatInvite.html create mode 100644 data/corefork.telegram.org/type/ChatInviteImporter.html create mode 100644 data/corefork.telegram.org/type/ChatOnlines.html create mode 100644 data/corefork.telegram.org/type/ChatParticipant.html create mode 100644 data/corefork.telegram.org/type/ChatParticipants.html create mode 100644 data/corefork.telegram.org/type/ChatPhoto.html create mode 100644 data/corefork.telegram.org/type/ChatTheme.html create mode 100644 data/corefork.telegram.org/type/CodeSettings.html create mode 100644 data/corefork.telegram.org/type/Config.html create mode 100644 data/corefork.telegram.org/type/Contact.html create mode 100644 data/corefork.telegram.org/type/ContactStatus.html create mode 100644 data/corefork.telegram.org/type/DataJSON.html create mode 100644 data/corefork.telegram.org/type/DcOption.html create mode 100644 data/corefork.telegram.org/type/DecryptedDataBlock.html create mode 100644 data/corefork.telegram.org/type/DecryptedMessage.html create mode 100644 data/corefork.telegram.org/type/DecryptedMessageAction.html create mode 100644 data/corefork.telegram.org/type/DecryptedMessageLayer.html create mode 100644 data/corefork.telegram.org/type/Dialog.html create mode 100644 data/corefork.telegram.org/type/DialogFilter.html create mode 100644 data/corefork.telegram.org/type/DialogFilterSuggested.html create mode 100644 data/corefork.telegram.org/type/DialogPeer.html create mode 100644 data/corefork.telegram.org/type/DisabledFeature.html create mode 100644 data/corefork.telegram.org/type/Document.html create mode 100644 data/corefork.telegram.org/type/DocumentAttribute.html create mode 100644 data/corefork.telegram.org/type/DraftMessage.html create mode 100644 data/corefork.telegram.org/type/EmojiKeyword.html create mode 100644 data/corefork.telegram.org/type/EmojiKeywordsDifference.html create mode 100644 data/corefork.telegram.org/type/EmojiLanguage.html create mode 100644 data/corefork.telegram.org/type/EmojiURL.html create mode 100644 data/corefork.telegram.org/type/EncryptedChat.html create mode 100644 data/corefork.telegram.org/type/EncryptedMessage.html create mode 100644 data/corefork.telegram.org/type/ExportedChatInvite.html create mode 100644 data/corefork.telegram.org/type/ExportedMessageLink.html create mode 100644 data/corefork.telegram.org/type/FileHash.html create mode 100644 data/corefork.telegram.org/type/FileLocation.html create mode 100644 data/corefork.telegram.org/type/Folder.html create mode 100644 data/corefork.telegram.org/type/FolderPeer.html create mode 100644 data/corefork.telegram.org/type/Game.html create mode 100644 data/corefork.telegram.org/type/GeoPoint.html create mode 100644 data/corefork.telegram.org/type/GlobalPrivacySettings.html create mode 100644 data/corefork.telegram.org/type/GroupCall.html create mode 100644 data/corefork.telegram.org/type/GroupCallParticipant.html create mode 100644 data/corefork.telegram.org/type/GroupCallParticipantVideo.html create mode 100644 data/corefork.telegram.org/type/GroupCallParticipantVideoSourceGroup.html create mode 100644 data/corefork.telegram.org/type/HighScore.html create mode 100644 data/corefork.telegram.org/type/ImportedContact.html create mode 100644 data/corefork.telegram.org/type/InlineQueryPeerType.html create mode 100644 data/corefork.telegram.org/type/InputAppEvent.html create mode 100644 data/corefork.telegram.org/type/InputBotInlineMessage.html create mode 100644 data/corefork.telegram.org/type/InputBotInlineMessageID.html create mode 100644 data/corefork.telegram.org/type/InputBotInlineResult.html create mode 100644 data/corefork.telegram.org/type/InputChannel.html create mode 100644 data/corefork.telegram.org/type/InputChatPhoto.html create mode 100644 data/corefork.telegram.org/type/InputCheckPasswordSRP.html create mode 100644 data/corefork.telegram.org/type/InputClientProxy.html create mode 100644 data/corefork.telegram.org/type/InputContact.html create mode 100644 data/corefork.telegram.org/type/InputDialogPeer.html create mode 100644 data/corefork.telegram.org/type/InputDocument.html create mode 100644 data/corefork.telegram.org/type/InputEncryptedChat.html create mode 100644 data/corefork.telegram.org/type/InputEncryptedFile.html create mode 100644 data/corefork.telegram.org/type/InputFile.html create mode 100644 data/corefork.telegram.org/type/InputFileLocation.html create mode 100644 data/corefork.telegram.org/type/InputFolderPeer.html create mode 100644 data/corefork.telegram.org/type/InputGame.html create mode 100644 data/corefork.telegram.org/type/InputGeoPoint.html create mode 100644 data/corefork.telegram.org/type/InputGroupCall.html create mode 100644 data/corefork.telegram.org/type/InputMedia.html create mode 100644 data/corefork.telegram.org/type/InputMessage.html create mode 100644 data/corefork.telegram.org/type/InputNotifyPeer.html create mode 100644 data/corefork.telegram.org/type/InputPaymentCredentials.html create mode 100644 data/corefork.telegram.org/type/InputPeer.html create mode 100644 data/corefork.telegram.org/type/InputPeerNotifySettings.html create mode 100644 data/corefork.telegram.org/type/InputPhoneCall.html create mode 100644 data/corefork.telegram.org/type/InputPhoto.html create mode 100644 data/corefork.telegram.org/type/InputPrivacyKey.html create mode 100644 data/corefork.telegram.org/type/InputPrivacyRule.html create mode 100644 data/corefork.telegram.org/type/InputSecureFile.html create mode 100644 data/corefork.telegram.org/type/InputSecureValue.html create mode 100644 data/corefork.telegram.org/type/InputSingleMedia.html create mode 100644 data/corefork.telegram.org/type/InputStickerSet.html create mode 100644 data/corefork.telegram.org/type/InputStickerSetItem.html create mode 100644 data/corefork.telegram.org/type/InputStickeredMedia.html create mode 100644 data/corefork.telegram.org/type/InputThemeSettings.html create mode 100644 data/corefork.telegram.org/type/InputUser.html create mode 100644 data/corefork.telegram.org/type/InputWallPaper.html create mode 100644 data/corefork.telegram.org/type/InputWebDocument.html create mode 100644 data/corefork.telegram.org/type/InputWebFileLocation.html create mode 100644 data/corefork.telegram.org/type/Invoice.html create mode 100644 data/corefork.telegram.org/type/JSONObjectValue.html create mode 100644 data/corefork.telegram.org/type/JSONValue.html create mode 100644 data/corefork.telegram.org/type/KeyboardButton.html create mode 100644 data/corefork.telegram.org/type/KeyboardButtonRow.html create mode 100644 data/corefork.telegram.org/type/LabeledPrice.html create mode 100644 data/corefork.telegram.org/type/LangPackDifference.html create mode 100644 data/corefork.telegram.org/type/LangPackLanguage.html create mode 100644 data/corefork.telegram.org/type/LangPackString.html create mode 100644 data/corefork.telegram.org/type/MaskCoords.html create mode 100644 data/corefork.telegram.org/type/Message.html create mode 100644 data/corefork.telegram.org/type/MessageAction.html create mode 100644 data/corefork.telegram.org/type/MessageEntity.html create mode 100644 data/corefork.telegram.org/type/MessageFwdHeader.html create mode 100644 data/corefork.telegram.org/type/MessageInteractionCounters.html create mode 100644 data/corefork.telegram.org/type/MessageMedia.html create mode 100644 data/corefork.telegram.org/type/MessagePeerReaction.html create mode 100644 data/corefork.telegram.org/type/MessageRange.html create mode 100644 data/corefork.telegram.org/type/MessageReactions.html create mode 100644 data/corefork.telegram.org/type/MessageReactionsList.html create mode 100644 data/corefork.telegram.org/type/MessageReplies.html create mode 100644 data/corefork.telegram.org/type/MessageUserVote.html create mode 100644 data/corefork.telegram.org/type/MessageViews.html create mode 100644 data/corefork.telegram.org/type/MessagesFilter.html create mode 100644 data/corefork.telegram.org/type/NearestDc.html create mode 100644 data/corefork.telegram.org/type/NotifyPeer.html create mode 100644 data/corefork.telegram.org/type/Null.html create mode 100644 data/corefork.telegram.org/type/Page.html create mode 100644 data/corefork.telegram.org/type/PageBlock.html create mode 100644 data/corefork.telegram.org/type/PageCaption.html create mode 100644 data/corefork.telegram.org/type/PageListItem.html create mode 100644 data/corefork.telegram.org/type/PageListOrderedItem.html create mode 100644 data/corefork.telegram.org/type/PageRelatedArticle.html create mode 100644 data/corefork.telegram.org/type/PageTableCell.html create mode 100644 data/corefork.telegram.org/type/PageTableRow.html create mode 100644 data/corefork.telegram.org/type/PasswordKdfAlgo.html create mode 100644 data/corefork.telegram.org/type/PaymentCharge.html create mode 100644 data/corefork.telegram.org/type/PaymentRequestedInfo.html create mode 100644 data/corefork.telegram.org/type/PaymentSavedCredentials.html create mode 100644 data/corefork.telegram.org/type/Peer.html create mode 100644 data/corefork.telegram.org/type/PeerBlocked.html create mode 100644 data/corefork.telegram.org/type/PeerLocated.html create mode 100644 data/corefork.telegram.org/type/PeerNotifySettings.html create mode 100644 data/corefork.telegram.org/type/PeerSettings.html create mode 100644 data/corefork.telegram.org/type/PhoneCallDiscardReason.html create mode 100644 data/corefork.telegram.org/type/PhoneCallProtocol.html create mode 100644 data/corefork.telegram.org/type/PhoneConnection.html create mode 100644 data/corefork.telegram.org/type/Photo.html create mode 100644 data/corefork.telegram.org/type/PhotoSize.html create mode 100644 data/corefork.telegram.org/type/Poll.html create mode 100644 data/corefork.telegram.org/type/PollAnswer.html create mode 100644 data/corefork.telegram.org/type/PollAnswerVoters.html create mode 100644 data/corefork.telegram.org/type/PollResults.html create mode 100644 data/corefork.telegram.org/type/PopularContact.html create mode 100644 data/corefork.telegram.org/type/PostAddress.html create mode 100644 data/corefork.telegram.org/type/PrivacyKey.html create mode 100644 data/corefork.telegram.org/type/PrivacyRule.html create mode 100644 data/corefork.telegram.org/type/ReactionCount.html create mode 100644 data/corefork.telegram.org/type/ReceivedNotifyMessage.html create mode 100644 data/corefork.telegram.org/type/RecentMeUrl.html create mode 100644 data/corefork.telegram.org/type/ReplyMarkup.html create mode 100644 data/corefork.telegram.org/type/ReportReason.html create mode 100644 data/corefork.telegram.org/type/RestrictionReason.html create mode 100644 data/corefork.telegram.org/type/RichText.html create mode 100644 data/corefork.telegram.org/type/SavedContact.html create mode 100644 data/corefork.telegram.org/type/SearchResultsCalendarPeriod.html create mode 100644 data/corefork.telegram.org/type/SearchResultsPosition.html create mode 100644 data/corefork.telegram.org/type/SecureCredentialsEncrypted.html create mode 100644 data/corefork.telegram.org/type/SecureData.html create mode 100644 data/corefork.telegram.org/type/SecureFile.html create mode 100644 data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html create mode 100644 data/corefork.telegram.org/type/SecurePlainData.html create mode 100644 data/corefork.telegram.org/type/SecureRequiredType.html create mode 100644 data/corefork.telegram.org/type/SecureSecretSettings.html create mode 100644 data/corefork.telegram.org/type/SecureValue.html create mode 100644 data/corefork.telegram.org/type/SecureValueError.html create mode 100644 data/corefork.telegram.org/type/SecureValueHash.html create mode 100644 data/corefork.telegram.org/type/SecureValueType.html create mode 100644 data/corefork.telegram.org/type/SendMessageAction.html create mode 100644 data/corefork.telegram.org/type/ShippingOption.html create mode 100644 data/corefork.telegram.org/type/SponsoredMessage.html create mode 100644 data/corefork.telegram.org/type/StatsAbsValueAndPrev.html create mode 100644 data/corefork.telegram.org/type/StatsDateRangeDays.html create mode 100644 data/corefork.telegram.org/type/StatsGraph.html create mode 100644 data/corefork.telegram.org/type/StatsGroupTopInviter.html create mode 100644 data/corefork.telegram.org/type/StatsGroupTopPoster.html create mode 100644 data/corefork.telegram.org/type/StatsPercentValue.html create mode 100644 data/corefork.telegram.org/type/StatsURL.html create mode 100644 data/corefork.telegram.org/type/StickerPack.html create mode 100644 data/corefork.telegram.org/type/StickerSetCovered.html create mode 100644 data/corefork.telegram.org/type/Theme.html create mode 100644 data/corefork.telegram.org/type/ThemeSettings.html create mode 100644 data/corefork.telegram.org/type/TopPeerCategory.html create mode 100644 data/corefork.telegram.org/type/TopPeerCategoryPeers.html create mode 100644 data/corefork.telegram.org/type/True.html create mode 100644 data/corefork.telegram.org/type/Update.html create mode 100644 data/corefork.telegram.org/type/Updates.html create mode 100644 data/corefork.telegram.org/type/UrlAuthResult.html create mode 100644 data/corefork.telegram.org/type/User.html create mode 100644 data/corefork.telegram.org/type/UserFull.html create mode 100644 data/corefork.telegram.org/type/UserProfilePhoto.html create mode 100644 data/corefork.telegram.org/type/UserStatus.html create mode 100644 data/corefork.telegram.org/type/Vector t.html create mode 100644 data/corefork.telegram.org/type/Video.html create mode 100644 data/corefork.telegram.org/type/VideoSize.html create mode 100644 data/corefork.telegram.org/type/WallPaperSettings.html create mode 100644 data/corefork.telegram.org/type/WebAuthorization.html create mode 100644 data/corefork.telegram.org/type/WebDocument.html create mode 100644 data/corefork.telegram.org/type/WebPage.html create mode 100644 data/corefork.telegram.org/type/WebPageAttribute.html create mode 100644 data/corefork.telegram.org/type/account.AuthorizationForm create mode 100644 data/corefork.telegram.org/type/account.Authorizations create mode 100644 data/corefork.telegram.org/type/account.AutoDownloadSettings create mode 100644 data/corefork.telegram.org/type/account.ChatThemes create mode 100644 data/corefork.telegram.org/type/account.ContentSettings create mode 100644 data/corefork.telegram.org/type/account.Password create mode 100644 data/corefork.telegram.org/type/account.PasswordInputSettings create mode 100644 data/corefork.telegram.org/type/account.PasswordSettings create mode 100644 data/corefork.telegram.org/type/account.PrivacyRules create mode 100644 data/corefork.telegram.org/type/account.ResetPasswordResult create mode 100644 data/corefork.telegram.org/type/account.SentChangePhoneCode create mode 100644 data/corefork.telegram.org/type/account.SentEmailCode create mode 100644 data/corefork.telegram.org/type/account.Takeout create mode 100644 data/corefork.telegram.org/type/account.Themes create mode 100644 data/corefork.telegram.org/type/account.TmpPassword create mode 100644 data/corefork.telegram.org/type/account.WallPapers create mode 100644 data/corefork.telegram.org/type/account.WebAuthorizations create mode 100644 data/corefork.telegram.org/type/auth.Authorization create mode 100644 data/corefork.telegram.org/type/auth.CheckedPhone create mode 100644 data/corefork.telegram.org/type/auth.CodeType create mode 100644 data/corefork.telegram.org/type/auth.ExportedAuthorization create mode 100644 data/corefork.telegram.org/type/auth.LoggedOut create mode 100644 data/corefork.telegram.org/type/auth.LoginToken create mode 100644 data/corefork.telegram.org/type/auth.PasswordRecovery create mode 100644 data/corefork.telegram.org/type/auth.SentCode create mode 100644 data/corefork.telegram.org/type/auth.SentCodeType create mode 100644 data/corefork.telegram.org/type/bytes.html create mode 100644 data/corefork.telegram.org/type/channels.AdminLogResults create mode 100644 data/corefork.telegram.org/type/channels.ChannelParticipant create mode 100644 data/corefork.telegram.org/type/channels.ChannelParticipants create mode 100644 data/corefork.telegram.org/type/channels.SendAsPeers create mode 100644 data/corefork.telegram.org/type/contacts.Blocked create mode 100644 data/corefork.telegram.org/type/contacts.Contacts create mode 100644 data/corefork.telegram.org/type/contacts.Found create mode 100644 data/corefork.telegram.org/type/contacts.ImportedContacts create mode 100644 data/corefork.telegram.org/type/contacts.Link create mode 100644 data/corefork.telegram.org/type/contacts.ResolvedPeer create mode 100644 data/corefork.telegram.org/type/contacts.TopPeers create mode 100644 data/corefork.telegram.org/type/double.html create mode 100644 data/corefork.telegram.org/type/help.AppUpdate create mode 100644 data/corefork.telegram.org/type/help.CountriesList create mode 100644 data/corefork.telegram.org/type/help.CountryCode create mode 100644 data/corefork.telegram.org/type/help.DeepLinkInfo create mode 100644 data/corefork.telegram.org/type/help.InviteText create mode 100644 data/corefork.telegram.org/type/help.PromoData create mode 100644 data/corefork.telegram.org/type/help.ProxyData create mode 100644 data/corefork.telegram.org/type/help.RecentMeUrls create mode 100644 data/corefork.telegram.org/type/help.Support create mode 100644 data/corefork.telegram.org/type/help.SupportName create mode 100644 data/corefork.telegram.org/type/help.TermsOfService create mode 100644 data/corefork.telegram.org/type/help.TermsOfServiceUpdate create mode 100644 data/corefork.telegram.org/type/help.UserInfo create mode 100644 data/corefork.telegram.org/type/int.html create mode 100644 data/corefork.telegram.org/type/long.html create mode 100644 data/corefork.telegram.org/type/messages.AffectedFoundMessages create mode 100644 data/corefork.telegram.org/type/messages.AffectedHistory create mode 100644 data/corefork.telegram.org/type/messages.AffectedMessages create mode 100644 data/corefork.telegram.org/type/messages.AllStickers create mode 100644 data/corefork.telegram.org/type/messages.ArchivedStickers create mode 100644 data/corefork.telegram.org/type/messages.AvailableReactions create mode 100644 data/corefork.telegram.org/type/messages.BotCallbackAnswer create mode 100644 data/corefork.telegram.org/type/messages.BotResults create mode 100644 data/corefork.telegram.org/type/messages.ChatAdminsWithInvites create mode 100644 data/corefork.telegram.org/type/messages.ChatFull create mode 100644 data/corefork.telegram.org/type/messages.ChatInviteImporters create mode 100644 data/corefork.telegram.org/type/messages.Chats create mode 100644 data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer create mode 100644 data/corefork.telegram.org/type/messages.DhConfig create mode 100644 data/corefork.telegram.org/type/messages.Dialogs create mode 100644 data/corefork.telegram.org/type/messages.DiscussionMessage create mode 100644 data/corefork.telegram.org/type/messages.ExportedChatInvite create mode 100644 data/corefork.telegram.org/type/messages.ExportedChatInvites create mode 100644 data/corefork.telegram.org/type/messages.FavedStickers create mode 100644 data/corefork.telegram.org/type/messages.FeaturedStickers create mode 100644 data/corefork.telegram.org/type/messages.FoundGifs create mode 100644 data/corefork.telegram.org/type/messages.FoundStickerSets create mode 100644 data/corefork.telegram.org/type/messages.HighScores create mode 100644 data/corefork.telegram.org/type/messages.HistoryImport create mode 100644 data/corefork.telegram.org/type/messages.HistoryImportParsed create mode 100644 data/corefork.telegram.org/type/messages.InactiveChats create mode 100644 data/corefork.telegram.org/type/messages.MessageEditData create mode 100644 data/corefork.telegram.org/type/messages.MessageReactionsList create mode 100644 data/corefork.telegram.org/type/messages.MessageViews create mode 100644 data/corefork.telegram.org/type/messages.Messages create mode 100644 data/corefork.telegram.org/type/messages.PeerDialogs create mode 100644 data/corefork.telegram.org/type/messages.RecentStickers create mode 100644 data/corefork.telegram.org/type/messages.SavedGifs create mode 100644 data/corefork.telegram.org/type/messages.SearchCounter create mode 100644 data/corefork.telegram.org/type/messages.SearchResultsCalendar create mode 100644 data/corefork.telegram.org/type/messages.SearchResultsPositions create mode 100644 data/corefork.telegram.org/type/messages.SentEncryptedMessage create mode 100644 data/corefork.telegram.org/type/messages.SentMessage create mode 100644 data/corefork.telegram.org/type/messages.SponsoredMessages create mode 100644 data/corefork.telegram.org/type/messages.StatedMessage create mode 100644 data/corefork.telegram.org/type/messages.StatedMessages create mode 100644 data/corefork.telegram.org/type/messages.StickerSet create mode 100644 data/corefork.telegram.org/type/messages.StickerSetInstallResult create mode 100644 data/corefork.telegram.org/type/messages.Stickers create mode 100644 data/corefork.telegram.org/type/messages.TranslatedText create mode 100644 data/corefork.telegram.org/type/messages.VotesList create mode 100644 data/corefork.telegram.org/type/payments.BankCardData create mode 100644 data/corefork.telegram.org/type/payments.PaymentForm create mode 100644 data/corefork.telegram.org/type/payments.PaymentReceipt create mode 100644 data/corefork.telegram.org/type/payments.PaymentResult create mode 100644 data/corefork.telegram.org/type/payments.SavedInfo create mode 100644 data/corefork.telegram.org/type/payments.ValidatedRequestedInfo create mode 100644 data/corefork.telegram.org/type/phone.ExportedGroupCallInvite create mode 100644 data/corefork.telegram.org/type/phone.GroupCall create mode 100644 data/corefork.telegram.org/type/phone.GroupParticipants create mode 100644 data/corefork.telegram.org/type/phone.JoinAsPeers create mode 100644 data/corefork.telegram.org/type/phone.PhoneCall create mode 100644 data/corefork.telegram.org/type/photos.Photo create mode 100644 data/corefork.telegram.org/type/photos.Photos create mode 100644 data/corefork.telegram.org/type/stats.BroadcastStats create mode 100644 data/corefork.telegram.org/type/stats.MegagroupStats create mode 100644 data/corefork.telegram.org/type/stats.MessageStats create mode 100644 data/corefork.telegram.org/type/stickers.SuggestedShortName create mode 100644 data/corefork.telegram.org/type/storage.FileType create mode 100644 data/corefork.telegram.org/type/string.html create mode 100644 data/corefork.telegram.org/type/updates.ChannelDifference create mode 100644 data/corefork.telegram.org/type/updates.Difference create mode 100644 data/corefork.telegram.org/type/updates.State create mode 100644 data/corefork.telegram.org/type/upload.CdnFile create mode 100644 data/corefork.telegram.org/type/upload.File create mode 100644 data/corefork.telegram.org/type/upload.WebFile create mode 100644 data/corefork.telegram.org/type/users.UserFull create mode 100644 data/corefork.telegram.org/widgets.html create mode 100644 data/corefork.telegram.org/widgets/discussion.html create mode 100644 data/corefork.telegram.org/widgets/login.html create mode 100644 data/corefork.telegram.org/widgets/post.html create mode 100644 data/corefork.telegram.org/widgets/share.html create mode 100644 data/desktop.telegram.org.html create mode 100644 data/instantview.telegram.org.html create mode 100644 data/instantview.telegram.org/docs.html create mode 100644 data/instantview.telegram.org/samples.html create mode 100644 data/instantview.telegram.org/templates.html create mode 100644 data/macos.telegram.org.html create mode 100644 data/promote.telegram.org/auth.html create mode 100644 data/promote.telegram.org/basics.html create mode 100644 data/promote.telegram.org/getting-started.html create mode 100644 data/promote.telegram.org/guidelines.html create mode 100644 data/promote.telegram.org/tos.html create mode 100644 data/telegram.org.html create mode 100644 data/telegram.org/android.html create mode 100644 data/telegram.org/blog.html create mode 100644 data/telegram.org/blog/200-million.html create mode 100644 data/telegram.org/blog/6-years.html create mode 100644 data/telegram.org/blog/admin-revolution.html create mode 100644 data/telegram.org/blog/albums-saved-messages.html create mode 100644 data/telegram.org/blog/android-2-0.html create mode 100644 data/telegram.org/blog/android-gif.html create mode 100644 data/telegram.org/blog/android-themes.html create mode 100644 data/telegram.org/blog/android-wear-2-0.html create mode 100644 data/telegram.org/blog/animated-backgrounds.html create mode 100644 data/telegram.org/blog/animated-stickers.html create mode 100644 data/telegram.org/blog/apple-watch.html create mode 100644 data/telegram.org/blog/archive-and-new-design.html create mode 100644 data/telegram.org/blog/autodelete-inv2.html create mode 100644 data/telegram.org/blog/autoplay.html create mode 100644 data/telegram.org/blog/backgrounds-2-0.html create mode 100644 data/telegram.org/blog/bot-revolution.html create mode 100644 data/telegram.org/blog/bots-2-0.html create mode 100644 data/telegram.org/blog/cache-and-stickers.html create mode 100644 data/telegram.org/blog/calls.html create mode 100644 data/telegram.org/blog/captions-places.html create mode 100644 data/telegram.org/blog/channels-2-0.html create mode 100644 data/telegram.org/blog/channels.html create mode 100644 data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html create mode 100644 data/telegram.org/blog/contacts-local-groups.html create mode 100644 data/telegram.org/blog/coronavirus.html create mode 100644 data/telegram.org/blog/crowdsourcing-a-more-secure-future.html create mode 100644 data/telegram.org/blog/cryptocontest-ends.html create mode 100644 data/telegram.org/blog/cryptocontest.html create mode 100644 data/telegram.org/blog/desktop-1-0.html create mode 100644 data/telegram.org/blog/desktop-compact.html create mode 100644 data/telegram.org/blog/discover-stickers-and-more.html create mode 100644 data/telegram.org/blog/drafts.html create mode 100644 data/telegram.org/blog/edit.html create mode 100644 data/telegram.org/blog/encrypted-cdns.html create mode 100644 data/telegram.org/blog/export-and-more.html create mode 100644 data/telegram.org/blog/files-on-steroids.html create mode 100644 data/telegram.org/blog/filters-anonymous-admins-comments.html create mode 100644 data/telegram.org/blog/folders.html create mode 100644 data/telegram.org/blog/games.html create mode 100644 data/telegram.org/blog/gifs.html create mode 100644 data/telegram.org/blog/group-video-calls.html create mode 100644 data/telegram.org/blog/inline-bots.html create mode 100644 data/telegram.org/blog/instant-camera.html create mode 100644 data/telegram.org/blog/instant-view.html create mode 100644 data/telegram.org/blog/invite-links.html create mode 100644 data/telegram.org/blog/link-preview.html create mode 100644 data/telegram.org/blog/live-locations.html create mode 100644 data/telegram.org/blog/live-streams-forwarding-next-channel.html create mode 100644 data/telegram.org/blog/login.html create mode 100644 data/telegram.org/blog/move-history.html create mode 100644 data/telegram.org/blog/now-you-see-me.html create mode 100644 data/telegram.org/blog/passport.html create mode 100644 data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html create mode 100644 data/telegram.org/blog/payments.html create mode 100644 data/telegram.org/blog/permissions-groups-undo.html create mode 100644 data/telegram.org/blog/photo-editor-and-passcodes.html create mode 100644 data/telegram.org/blog/pin-and-ifttt.html create mode 100644 data/telegram.org/blog/pinned-messages-locations-playlists.html create mode 100644 data/telegram.org/blog/pinned-messages-locations-playlists/world.html create mode 100644 data/telegram.org/blog/polls-2-0-vmq.html create mode 100644 data/telegram.org/blog/polls.html create mode 100644 data/telegram.org/blog/privacy-discussions-web-bots.html create mode 100644 data/telegram.org/blog/privacy-revolution.html create mode 100644 data/telegram.org/blog/profile-videos-people-nearby-and-more.html create mode 100644 data/telegram.org/blog/protected-content-delete-by-date-and-more.html create mode 100644 data/telegram.org/blog/reactions-spoilers-translations.html create mode 100644 data/telegram.org/blog/replies-mentions-hashtags.html create mode 100644 data/telegram.org/blog/replies-mentions-stickers.html create mode 100644 data/telegram.org/blog/scheduled-reminders-themes.html create mode 100644 data/telegram.org/blog/search-and-media.html create mode 100644 data/telegram.org/blog/sessions-and-2-step-verification.html create mode 100644 data/telegram.org/blog/share-preview.html create mode 100644 data/telegram.org/blog/shared-files.html create mode 100644 data/telegram.org/blog/shared-links.html create mode 100644 data/telegram.org/blog/shared-media-scrolling-calendar-join-requests-and-more.html create mode 100644 data/telegram.org/blog/silent-messages-slow-mode.html create mode 100644 data/telegram.org/blog/stickers-meet-art-and-history.html create mode 100644 data/telegram.org/blog/stickers-revolution.html create mode 100644 data/telegram.org/blog/stickers.html create mode 100644 data/telegram.org/blog/supergroups.html create mode 100644 data/telegram.org/blog/supergroups5k.html create mode 100644 data/telegram.org/blog/tdlib.html create mode 100644 data/telegram.org/blog/telegram-5-ios.html create mode 100644 data/telegram.org/blog/telegram-me-change-number-and-pfs.html create mode 100644 data/telegram.org/blog/telegram-x.html create mode 100644 data/telegram.org/blog/telegraph.html create mode 100644 data/telegram.org/blog/themes-accounts.html create mode 100644 data/telegram.org/blog/translations-iv2.html create mode 100644 data/telegram.org/blog/trending-stickers.html create mode 100644 data/telegram.org/blog/unread-replace-2x.html create mode 100644 data/telegram.org/blog/unsend-and-usage.html create mode 100644 data/telegram.org/blog/unsend-privacy-emoji.html create mode 100644 data/telegram.org/blog/usernames-and-secret-chats-v2.html create mode 100644 data/telegram.org/blog/verifiable-apps-and-more.html create mode 100644 data/telegram.org/blog/video-1000.html create mode 100644 data/telegram.org/blog/video-calls.html create mode 100644 data/telegram.org/blog/video-messages-and-telescope.html create mode 100644 data/telegram.org/blog/video-stickers-better-reactions.html create mode 100644 data/telegram.org/blog/voice-2-secret-3.html create mode 100644 data/telegram.org/blog/voice-chats-on-steroids.html create mode 100644 data/telegram.org/blog/voice-chats.html create mode 100644 data/telegram.org/blog/winter-contest-ends.html create mode 100644 data/telegram.org/evolution.html create mode 100644 data/telegram.org/faq.html create mode 100644 data/telegram.org/faq_channels.html create mode 100644 data/telegram.org/faq_spam.html create mode 100644 data/telegram.org/jobs.html create mode 100644 data/telegram.org/press.html create mode 100644 data/telegram.org/privacy.html create mode 100644 data/telegram.org/privacy/gmailbot.html create mode 100644 data/telegram.org/support.html create mode 100644 data/telegram.org/teststore.html create mode 100644 data/telegram.org/tos.html create mode 100644 data/telegram.org/tour.html create mode 100644 data/telegram.org/tour/channels.html create mode 100644 data/telegram.org/tour/groups.html create mode 100644 data/telegram.org/what-can-you-do-with-Telegram.html create mode 100644 data/themes.telegram.org/auth.html create mode 100644 data/translations.telegram.org/en.html create mode 100644 data/translations.telegram.org/en/ios.html create mode 100644 data/translations.telegram.org/en/macos.html create mode 100644 data/tsf.telegram.org/auth.html create mode 100644 data/tsf.telegram.org/manuals.html create mode 100644 data/tsf.telegram.org/manuals/answering_questions.html create mode 100644 data/tsf.telegram.org/manuals/bios.html create mode 100644 data/tsf.telegram.org/manuals/bug_herding.html create mode 100644 data/tsf.telegram.org/manuals/bugs.html create mode 100644 data/tsf.telegram.org/manuals/come-and-go.html create mode 100644 data/tsf.telegram.org/manuals/e2ee.html diff --git a/data/contest.com.html b/data/contest.com.html new file mode 100644 index 0000000000..2ffb45b45d --- /dev/null +++ b/data/contest.com.html @@ -0,0 +1,291 @@ + + + + + Developer Challenges + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+ +
+
+
+
+
+ +
+

Recent News

+

Subscribe to the Telegram Contests channel for the latest updates and information about ongoing competitions.

+

About this Platform

+

Everybody is welcome to try out works submitted by the contestants and create issues (with supporting videos and screenshots) if they encounter any problems.

+


+ +

Contestants can respond to issues. They appear on the platform under animal aliases to ensure fairness and transparency in testing. Admins will be around to do their own checks on the apps and tally up the results.

+


+ +

If you're looking for information about contests that are currently open, check the Telegram Contests channel.

+
+
+
+ +

Contests

+ +
Windows 11 Design Contest. $40,000New
+
Dec 30, 2021 – Jan 22
+
+
GIF Contest, Round 2. $50,000New
+
Sep 8 – Nov 9, 2021
+
+
November 2021 Android Contest, Round 2. $50,000
+
Nov 26 – Dec 6, 2021
+
+
November 2021 Android Contest. $50,000
+
Nov 5 – Nov 15, 2021
+
+
Android Design Contest. $30,000
+
Jul 8 – Aug 1, 2021
+
+
Sticker App Contest. $50,000
+
Jun 25 – Jul 4, 2021
+
+
iOS Contest, Round 3 (watchOS)
+
May 19 – Jun 6, 2021
+
+
Data Clustering Contest 2021, Round 2. $50,000
+
Apr 17 – May 2, 2021
+
+
Android Contest 2021, Round 2. $50,000
+
Mar 19 – Apr 4, 2021
+
+
GIF Contest, Round 1. $50,000
+
Mar 17 – Mar 31, 2021
+
+
Animated Sticker Contest 2021. $50,000
+
Mar 11 – Mar 26, 2021
+
+
watchOS Contest 2021. $47,000
+
Mar 5 – Mar 21, 2021
+
+
Android Contest 2021. $60,000
+
Jan 30 – Feb 14, 2021
+
+
iOS Animation Contest 2021. $50,000
+
Jan 15 – Jan 31, 2021
+
+
Aptitude Test Contest. €250,000
+
Dec 31, 2020 – Jan 9, 2021
+
+
JavaScript Contest, Bonus Round
+
Aug 18 – Sep 1, 2020
+
+
JavaScript Contest, Stage 3
+
May 30 – Jun 20, 2020
+
+
Data Clustering Contest, Stage 2. €100,000
+
May 11 – May 25, 2020
+
+
VoIP Contest, Stage 3. €50,000
+
Mar 9 – Mar 30, 2020
+
+
Blockchain Contest, Stage 2: Bonus Prize €80,000
+
Mar 6 – Mar 20, 2020
+
+
JavaScript Contest, Stage 2
+
Jan 31 – Feb 15, 2020
+
+
VoIP Contest, Stage 2. $75,000
+
Jan 14 – Jan 29, 2020
+
+
Blockchain Contest, Stage 2. $100,000
+
Dec 7 – Dec 22, 2019
+
+
Data Clustering Contest. $100,000
+
Nov 18 – Dec 2, 2019
+
+
Javascript Contest, Stage 1. $80,000+
+
Nov 3 – Nov 17, 2019
+
+
VoIP Contest, Stage 1. $50,000+
+
Oct 15 – Oct 26, 2019
+
+
Theme Design Contest. $25,000+
+
Oct 5 – Oct 20, 2019
+
+
Animated Stickers Contest. $25,000+
+
Oct 5 – Oct 20, 2019
+
+
Blockchain Contest. $200,000–400,000
+
Sep 24 – Oct 15, 2019
+
+
Bugs on Telegram
+
Jun 14 – Jun 23, 2019
+
+
Android Chart Competition. $50,000
+
Apr 7 – Apr 15, 2019
+
+
iOS Chart Competition. $50,000
+
Apr 7 – Apr 15, 2019
+
+
JavaScript Chart Competition. $50,000
+
Apr 7 – Apr 15, 2019
+
+
+
+ + + + + + + + + + + + + + diff --git a/data/core.telegram.org.html b/data/core.telegram.org.html new file mode 100644 index 0000000000..f6775268b5 --- /dev/null +++ b/data/core.telegram.org.html @@ -0,0 +1,253 @@ + + + + + Telegram APIs + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram APIs

+ +

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

+

You can also add Telegram Widgets to your website.

+

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

+
+

Bot API

+
+ +
+

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

+

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

+
+

Learn more about the Bot API here »

+
+

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

+
+

TDLib – build your own Telegram

+

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

+

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

+

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

+
+

Learn more about TDLib here »

+
+
+

Telegram API

+

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

+ +

Getting started

+

Creating an application

+

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

+

User authorization

+

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

+

Two-factor authentication

+

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

+

QR code login

+

QR code login flow

+

Error handling

+

How to handle API return errors correctly.

+

Handling different data centers

+

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

+

Handling updates

+

How to subscribe to updates and handle them properly.

+

Handling PUSH-notifications

+

How to subscribe and handle them properly.

+

Channels, supergroups and groups

+

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

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

Calling methods

+

Additional options for calling methods.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

Pagination

+

How to fetch results from large lists of objects.

+

Client configuration

+

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

+

Security

+

Secret chats, end-to-end encryption

+

End-to-end-encrypted messaging.

+

Security guidelines

+

Important checks required in your client application.

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

End-to-End Encryption in Voice and Video Calls

+

End-to-end-encrypted calls.

+

Optimization

+

Client optimization

+

Ways to boost API interactions.

+

API methods

+

Available method list

+

A list of available high-level methods.

+

API TL-schema, as JSON

+

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

+

Available layer list

+

A list of available schema versions.

+

Other articles

+

Working with bots, using the MTProto API

+

How to work with bots using the MTProto API.

+

Commands

+

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

+

Buttons

+

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

+

Inline queries

+

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

+

Games

+

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

+

Search & filters

+

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

+

Polls

+

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

+

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

+

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

+

Discussion groups

+

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

+

Channel comments and message threads

+

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

+

Admin log

+

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

+

Pinned messages

+

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

+

Mentions

+

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

+

Scheduled messages

+

Telegram allows scheduling messages.

+

Live geolocations

+

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

+

Min constructors

+

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

+

Account deletion

+

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

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

Telegram Passport

+

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

+

Telegram Payments

+

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

+

Styled text with message entities

+

How to create styled text with message entities

+

Working with animated emojis

+

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

+

Working with animated dice

+

Telegram supports sending animated dice emojis.

+

Message drafts

+

How to handle message drafts

+

Folders

+

Working with folders

+

Top peer rating

+

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

+

Handling file references

+

How to handle file references.

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+

Web events

+

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

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

Telegram APIs

+ +

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

+

You can also add Telegram Widgets to your website.

+

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

+
+

Bot API

+
+ +
+

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

+

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

+
+

Learn more about the Bot API here »

+
+

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

+
+

TDLib – build your own Telegram

+

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

+

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

+

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

+
+

Learn more about TDLib here »

+
+
+

Telegram API

+

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

+ +

Getting started

+

Creating an application

+

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

+

User authorization

+

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

+

Two-factor authentication

+

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

+

QR code login

+

QR code login flow

+

Error handling

+

How to handle API return errors correctly.

+

Handling different data centers

+

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

+

Handling updates

+

How to subscribe to updates and handle them properly.

+

Handling PUSH-notifications

+

How to subscribe and handle them properly.

+

Channels, supergroups and groups

+

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

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

Calling methods

+

Additional options for calling methods.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

Pagination

+

How to fetch results from large lists of objects.

+

Client configuration

+

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

+

Security

+

Secret chats, end-to-end encryption

+

End-to-end-encrypted messaging.

+

Security guidelines

+

Important checks required in your client application.

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

End-to-End Encryption in Voice and Video Calls

+

End-to-end-encrypted calls.

+

Optimization

+

Client optimization

+

Ways to boost API interactions.

+

API methods

+

Available method list

+

A list of available high-level methods.

+

API TL-schema, as JSON

+

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

+

Available layer list

+

A list of available schema versions.

+

Other articles

+

Working with bots, using the MTProto API

+

How to work with bots using the MTProto API.

+

Commands

+

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

+

Buttons

+

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

+

Inline queries

+

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

+

Games

+

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

+

Search & filters

+

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

+

Polls

+

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

+

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

+

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

+

Discussion groups

+

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

+

Channel comments and message threads

+

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

+

Admin log

+

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

+

Pinned messages

+

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

+

Mentions

+

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

+

Scheduled messages

+

Telegram allows scheduling messages.

+

Live geolocations

+

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

+

Min constructors

+

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

+

Account deletion

+

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

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

Telegram Passport

+

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

+

Telegram Payments

+

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

+

Styled text with message entities

+

How to create styled text with message entities

+

Working with animated emojis

+

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

+

Working with animated dice

+

Telegram supports sending animated dice emojis.

+

Message drafts

+

How to handle message drafts

+

Folders

+

Working with folders

+

Top peer rating

+

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

+

Handling file references

+

How to handle file references.

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+

Web events

+

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

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

Account deletion

+ +

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

+

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

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

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

+

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

+

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

+

Related articles

+

User Authorization

+

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

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

Animated Emojis

+ +

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

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

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

+

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

+

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

+

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

+

Emojis with sounds

+

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

+

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

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

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

+

Emoji reactions

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

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

+

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

+

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

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

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

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

User Authorization

+ +
+ +

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

+

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

+

Sending a verification code

+

Example implementations: telegram for android, tdlib.

+

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

+

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

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

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

+

The returned auth.SentCode object will contain multiple parameters:

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

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

+

Sign in/sign up

+

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

+

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

+

2FA

+

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

+

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

+

Test Accounts

+

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

+

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

+

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

+

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

+

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

+
+

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

+
+

We are authorized

+

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

+

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

+ +

Other methods will result in an error: 401 UNAUTHORIZED.

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

Bots

+ +
+ +

Working with bots, using the MTProto API.

+

See here for more info about bots.

+

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

+

Login

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

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

+

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

+

Commands

+

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

+

Buttons

+

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

+

Inline queries

+

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

+

Games

+

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

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

Buttons

+ +
+ +

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

+

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

+

Buttons

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

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

+ +

Pressing buttons

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

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

+

Buttons available only in reply keyboards:

+ +

Buttons available only in inline keyboards:

+ +

Callback queries

+

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

+

Sending a callback query

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

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

+

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

+

The returned messages.botCallbackAnswer constructor contains:

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

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

+

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

+

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

+

Answering a callback query

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

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

+

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

+ +

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

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

Commands

+ +
+ +

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

+

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

+

Getting commands

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

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

+

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

+

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

+

Setting commands

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

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

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

Games

+ +
+ +

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

+

Sending a game

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

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

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

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

+

Starting a game

+

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

+

Setting highscores

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

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

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

Getting highscores

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

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

+

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

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

Inline

+ +
+ +

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

+

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

+

Making an inline query

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

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

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

Answering to an inline query

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

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

+

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

+

Sending the inline query result

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

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

+

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

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

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

+

Inline feedback

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

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

+

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

+

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

+

The updateBotInlineSend will contain:

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

Editing sent inline messages

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

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

+

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

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

Channels

+ +
+ +

Channels, chats, supergroups & gigagroups

+

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

+

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

+

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

+

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

+

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

+

Migration

+

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

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

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

+

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

+

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

+

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

+

Rights

+

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

+

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

+

Pinned messages

+

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

+

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

+

Discussion

+

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

+

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

+

Recent actions

+

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

+

See here » for more info.

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

Client configuration

+ +
+ +

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

+

MTProto configuration

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

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

+

Client configuration

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

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

+

Typical fields included in the resulting JSON object are:

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

Example value:

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

Suggestions

+

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

+

Basic suggestions

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

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

+ +

Channel suggestions

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

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

+ +

Dismissing suggestions

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

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

+

App-specific configuration

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

Terms of service

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

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

+

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

+

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

+

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

+

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

+

Telegram support info

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

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

+ +

Country information and login phone patterns

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

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

+

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

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

Working with Different Data Centers

+ +

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

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

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

+

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

+

Registration/Authorization

+

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

+

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

+

Testing Redirects

+

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

+

File Access

+

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

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

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

+

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

+

User Migration

+

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

+

Authorization Transfer

+

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

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

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

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

Dice

+ +

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

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

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

+

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

+

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

+

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

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

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

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

Discussion groups

+ +
+ +

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

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

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

+

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

+

Linking a discussion group

+

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

+

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

+

Schema:

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

Message drafts

+ +
+ +

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

+

Drafts

+

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

+

Saving drafts

+

Drafts can be saved using the messages.saveDraft method.

+

Downloading drafts

+

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

+

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

+

Clearing drafts

+

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

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/end-to-end.html b/data/core.telegram.org/api/end-to-end.html new file mode 100644 index 0000000000..40675ab00d --- /dev/null +++ b/data/core.telegram.org/api/end-to-end.html @@ -0,0 +1,244 @@ + + + + + End-to-End Encryption, Secret Chats + + + + + + + + + + + + + +
+ +
+
+
+ +

End-to-End Encryption, Secret Chats

+ +
+ +
+

This article on MTProto's End-to-End encryption is meant for advanced users. +If you want to learn more about Secret Chats from a less intimidating source, kindly see our general FAQ.

+
+
+

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. +MTProto v.1.0 is deprecated and is currently being phased out.

+
+
+
Related articles
+

+
+

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

+
+ +
+

A note on MTProto 2.0

+

This article describes the end-to-end encryption layer in the MTProto protocol version 2.0. +The principal differences from version 1.0 (described here for reference) are as follows:

+
    +
  • SHA-256 is used instead of SHA-1;
  • +
  • Padding bytes are involved in the computation of msg_key;
  • +
  • msg_key depends not only on the message to be encrypted, but on a portion of the secret chat key as well;
  • +
  • 12..1024 padding bytes are used instead of 0..15 padding bytes in v.1.0.
  • +
+

See also: MTProto 2.0: Cloud Chats, server-client encryption

+

Key Generation

+

Keys are generated using the Diffie-Hellman protocol.

+

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

+

Sending a Request

+

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

+

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

+

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

+

If the client needs additional entropy for the random number generator, it can pass the random_length parameter (random_length> 0) so the server generates its own random sequence random of the appropriate length. +Important: using the server’s random sequence in its raw form may be unsafe, it must be combined with a client sequence.

+

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

+

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

+

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

+

Accepting a Request

+

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

+

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

+

Note 1: in this particular case SHA1 is used here even for MTProto 2.0 secret chats.

+

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

+

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

+

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

+

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

+

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

+

Perfect Forward Secrecy

+

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

+
+

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

+
+

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

+

Sending and Receiving Messages in a Secret Chat

+

Serialization and Encryption of Outgoing Messages

+

A TL object of type DecryptedMessage is created and contains the message in plain text. For backward compatibility, the object must be wrapped in the constructor decryptedMessageLayer with an indication of the supported layer (starting with 46).

+
+

The TL-Schema for the contents of end-to-end encrypted messages is available here »

+
+

The resulting construct is serialized as an array of bytes using generic TL rules. The resulting array is prepended by 4 bytes containing the array length not counting these 4 bytes.

+

The byte array is padded with 12 to 1024 random padding bytes to make its length divisible by 16 bytes. (In the older MTProto 1.0 encryption, only 0 to 15 padding bytes were used.)

+

Message key, msg_key, is computed as the 128 middle bits of the SHA256 of the data obtained in the previous step, prepended by 32 bytes from the shared key key. (For the older MTProto 1.0 encryption, msg_key was computed differently, as the 128 lower bits of SHA1 of the data obtained in the previous steps, excluding the padding bytes.)

+

For MTProto 2.0, the AES key aes_key and initialization vector aes_iv are computed ( key is the shared key obtained during Key Generation ) as follows:

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

For MTProto 2.0, x=0 for messages from the originator of the secret chat, x=8 for the messages in the opposite direction.

+

For the obsolete MTProto 1.0, msg_key, aes_key, and aes_iv were computed differently (see this document for reference).

+

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

+

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

+

Upgrading to MTProto 2.0 from MTProto 1.0

+

As soon as both parties in a secret chat are using at least Layer 73, they should only use MTProto 2.0 for all outgoing messages. Some of the first received messages may use MTProto 1.0, if a sufficiently high starting layer has not been negotiated during the creation of the secret chat. After the first message encrypted with MTProto 2.0 (or the first message with Layer 73 or higher) is received, all messages with higher sequence numbers must be encrypted with MTProto 2.0 as well.

+

As long as the current layer is lower than 73, each party should try to decrypt received messages with MTProto 1.0, and if this is not successfull (msg_key does not match), try MTProto 2.0. Once the first MTProto 2.0-encrypted message arrives (or the layer is upgraded to 73), there is no need to try MTProto 1.0 decryption for any of the further messages (unless the client is still waiting for some gaps to be closed).

+

Decrypting an Incoming Message

+

The steps above are performed in reverse order. +When an encrypted message is received, you must check that msg_key is in fact equal to the 128 middle bits of the SHA256 hash of the decrypted message, prepended by 32 bytes taken from the shared key. +If the message layer is greater than the one supported by the client, the user must be notified that the client version is out of date and prompted to update.

+

Sequence numbers

+

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

+
+

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

+
+

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

+

Sending Encrypted Files

+

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

+

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

+

The key fingerprint is computed as follows:

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

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

+

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

+

Working with an Update Box

+

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

+

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

+

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

+

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

+

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

+

Updating to new layers

+

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

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

Notifying the remote client about your local layer

+

In order to notify the remote client of your local layer, your client must send a message of the decryptedMessageActionNotifyLayer type. This notification must be wrapped in a constructor of an appropriate layer.

+

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

+
    +
  1. As soon as a new secret chat has been created, immediately after the secret key has been successfully exchanged.
  2. +
  3. Immediately after the local client has been updated to support a new secret chat layer. In this case notifications must be sent to all currently existing secret chats. Note that this is only necessary when updating to new layers that contain changes in the secret chats implementation (e.g. you don’t need to do this when your client is updated from Layer 46 to Layer 47).
  4. +
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/end-to-end/pfs.html b/data/core.telegram.org/api/end-to-end/pfs.html new file mode 100644 index 0000000000..8da37768e9 --- /dev/null +++ b/data/core.telegram.org/api/end-to-end/pfs.html @@ -0,0 +1,176 @@ + + + + + Perfect Forward Secrecy + + + + + + + + + + + + + +
+ +
+
+
+ +

Perfect Forward Secrecy

+ +
+

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

+
+

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

+

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

+

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

+

Re-keying protocol

+

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

+
1. decryptedMessageActionRequestKey
+

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

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

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

+
2. decryptedMessageActionAcceptKey
+

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

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

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

+

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

+
3. decryptedMessageActionCommitKey
+

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

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

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

+

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

+
4. Final step
+

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

+

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

+

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

+

Aborting protocol

+

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

+
decryptedMessageActionAbortKey exchange_id:long = DecryptedMessageAction;
+

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

+

Discarding Previous Keys

+

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

+
decryptedMessageActionNoop = DecryptedMessageAction;
+

Concurrent Re-Keying

+

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

+

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

+

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

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

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

+
+

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

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

Sequence numbers in Secret Chats

+ +

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

+

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

+ + + + + + + + + + + + + + + + + +
in_seq_noout_seq_no
secret chat initiated by sender01
secret chat initiated by recipient10
+

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

+
+

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

+
+

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

+

Preventing gaps

+

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

+

Security checks

+

Checking out_seq_no

+

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

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

Proper handling of gaps

+

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

+

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

+

Special cases:

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

Avoiding concurrent gaps

+

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

+

Checking and handling in_seq_no

+

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

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

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

+

Deleting unacknowledged messages

+

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

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

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

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

End-to-End Encrypted Voice and Video Calls

+ +

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

+
Related Articles
+

+ +
+

Establishing Calls

+

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

+

Key Generation

+

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

+

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

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

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

+

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

+

Encryption

+
+

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

+
+

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

+

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

+

The library starts working with:

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

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

+

Encrypting Call Data

+

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

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

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

+

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

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

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

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

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

+

The resulting aes_key and aes_iv are used to encrypt decrypted_body:

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

The packet that gets sent consists of msg_key and encrypted_body:

+
    +
  • packet_bytes = msg_key + encrypted_body
  • +
+

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

+

Protecting Against Replay Attacks

+

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

+

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

+

Key Verification

+

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

+

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

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

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

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

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

+

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

+

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

+
+

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

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

End-to-End Encrypted Voice Calls

+ +
+

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

+
+
Related articles
+

+ +

Establishing voice calls

+

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

+

Key Generation

+

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

+

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

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

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

+

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

+

Encryption of voice data

+

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

+

Encapsulation of low-level voice data

+

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

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

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

+

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

+

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

+

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

+

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

+

MTProto encryption

+

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

+

Key Verification

+

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

+

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

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

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

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

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

+

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

+

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

+
+

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

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

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

+ +
+

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

+
+
Related articles
+

+
+

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

+
+ +
+

Key Generation

+

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

+

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

+

Sending a Request

+

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

+

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

+

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

+

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

+

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

+

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

+

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

+

Accepting a Request

+

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

+

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

+

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

+

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

+

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

+

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

+

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

+

Perfect Forward Secrecy

+

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

+
+

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

+
+

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

+

Sending and Receiving Messages in a Secret Chat

+

Serialization and Encryption of Outgoing Messages

+

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

+

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

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

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

+

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

+

Decrypting an Incoming Message

+

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

+

Sequence numbers

+

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

+
+

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

+
+

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

+

Sending Encrypted Files

+

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

+

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

+

The key fingerprint is computed as follows:

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

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

+

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

+

Working with an Update Box

+

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

+

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

+

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

+

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

+

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

+

Updating to new layers

+

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

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

Notifying the remote client about your local layer

+

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

+

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

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

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

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

Styled text with message entities

+ +

Telegram supports styled text using message entities.

+

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

+

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

+

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

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

The following entities can also be used to mention users:

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

Error handling

+ +

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

+

An error is characterized by several parameters:

+

Error Code

+

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

+

Error Type

+

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

+
+

Error Constructors

+

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

+

Below is a list of error codes and their meanings:

+

303 SEE_OTHER

+

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

+

Examples of Errors:

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

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

+

400 BAD_REQUEST

+

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

+

Examples of Errors:

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

401 UNAUTHORIZED

+

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

+

Examples of Errors:

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

403 FORBIDDEN

+

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

+

404 NOT_FOUND

+

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

+

406 NOT_ACCEPTABLE

+

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

+

420 FLOOD

+

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

+

Error Example:

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

500 INTERNAL

+

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

+

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

+

Other Error Codes

+

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

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

File references

+ +

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

+

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

+

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

+

Another example:

+

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

+

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

+

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

+

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

+

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

+

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

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

Uploading and Downloading Files

+ +
+ +

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

+

Uploading files

+

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

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

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

+

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

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

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

+

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

+

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

+

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

+

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

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

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

+ +

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

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

Albums, grouped media

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

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

+

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

+

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

+

Re-using pre-uploaded files

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

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

+

Uploading profile or chat pictures

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

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

+

Animated profile pictures

+

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

+

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

+

Downloading files

+

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

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

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

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

    For photos, inputPhotoFileLocation is used:

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

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

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

    For documents, inputDocumentFileLocation is used:

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

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

    + +
  • +
  • +

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

    +
  • +
  • +

    For livestream chunks, inputGroupCallStream is used:

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

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

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

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

+

If precise flag is not specified, then

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

If precise is specified, then

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

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

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

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

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

Verifying downloaded chunks

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

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

+

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

+

Handling audio, video and vector previews

+

Schema:

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

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

+

Image thumbnail types

+

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

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

Special types:

+ + + + + + + + + + + + + + + + + +
TypeImage filter
istrip
joutline
+

Stripped thumbnails

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

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

+

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

+

Vector thumbnails

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

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

+

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

+

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

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

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

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

Video types

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

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

+ + + + + + + + + + + + + + + + + + + + +
TypeDescriptionFormat
uAnimated profile pictureMPEG4
vVideo previewMPEG4
+

Downloading webfiles

+

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

+

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

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

The InputWebFileLocation constructor is generated as follows.

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

General Considerations

+

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

+

Related articles

+

Handling file references

+

How to handle file references.

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

Folders

+ +
+ +

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

+

Schema:

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

Folders

+

On startup, clients call:

+ +

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

+

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

+

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

+

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

+

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

+

Peer folders

+

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

+

Schema:

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

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

+

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

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

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

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

Nope

+ +

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

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

Imported messages

+ +
+ +

Telegram allows importing messages and media from foreign chat apps.

+
+

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

+
+

1. Validate the chat export file

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

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

+

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

+

2. Choosing a destination Telegram chat

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

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

+

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

+

3. Initialize the import

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

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

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

4. Uploading media

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

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

+

5. Finalize the import

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

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

+

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

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

Calling API Methods

+ +
+ +

Layers

+

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

+

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

+

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

+

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

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

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

+

List of Available Layers

+

Saving Client Info

+

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

+

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

+

initConnection must also be called after each auth.bindTempAuthKey.

+

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

+

Disabling updates

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

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

+

Sequential Requests

+

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

+
+

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

+
+

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

+

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

+

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

+

Helper Method Sequence

+

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

+

Data Compression

+

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

+

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

+

Data Compression when Making a Request

+

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

+

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

+

Uncompressing Data

+

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

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/layers.html b/data/core.telegram.org/api/layers.html new file mode 100644 index 0000000000..d7b1d7a012 --- /dev/null +++ b/data/core.telegram.org/api/layers.html @@ -0,0 +1,2499 @@ + + + + + Layers + + + + + + + + + + + + + +
+ +
+
+
+ +

Layers

+ +
+ +

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+

Layer 133

+

Group message receipts, animated emoji reactions » and switch to 64-bit identifiers for users, groups, supergroups and channels.

+

Over 160 constructors and methods were changed, changing parameter types from int to long, including user, chat and channel: the full changelog is elided for space reasons.
You can visit the schema for an updated list of constructors.

+

Also note that the hashing algorithm for pagination was also changed to account for 64-bit IDs.

+

Changes

+ +

Layer 132

+

Chat themes and sponsored messages, save video recordings of group calls and livestreams.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+
    +
  • Added theme_emoticon parameter in chatFull
  • +
  • Added theme_emoticon parameter in userFull
  • +
  • Added theme_emoticon parameter in channelFull
  • +
  • Added for_chat parameter, changed type of installs_count from int to flags.4?int in theme
  • +
  • Added message_colors_animated, message_colors parameters, removed message_top_color, message_bottom_color parameters in inputThemeSettings
  • +
  • Added message_colors_animated, message_colors parameters, removed message_top_color, message_bottom_color parameters in themeSettings
  • +
  • Added unread_count parameter in messages.discussionMessage
  • +
  • Added flags, video_channel, video_quality parameters in inputGroupCallStream
  • +
+

Schema

+
chatFull#49a0a5d9 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int 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;\
+
+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;\
+
+channelFull#2f532f3c 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:int 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?int 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?int 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;\
+
+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;\
+
+inputThemeSettings#ff38f912 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;\
+
+themeSettings#8db4e76c flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;\
+
+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;\
+
+inputGroupCallStream#0598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;\
+
+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;\
+
+messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;\
+
+sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
+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---\
+
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;\
+
+account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;\
+
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;\
+
+channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;\
+
+ + + +

Layer 131

+

2FA password reset for logged-in accounts, add a method to check the validity of the e-mail recovery code before use.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;\
+
+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;
+groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;\
+
+account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;\
+
+updateBotCommands#cf7e0873 peer:Peer bot_id:int commands:Vector<BotCommand> = Update;\
+
+---functions---\
+
+auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;\
+
+phone.getGroupCall#041845db call:InputGroupCall limit:int = phone.GroupCall;\
+
+account.resetPassword#9308ce1b = account.ResetPasswordResult;
+account.declinePasswordReset#4c9409f6 = Bool;
+auth.checkRecoveryPassword#0d36bf79 code:string = Bool;\
+
+ + + +

Layer 130

+

Custom placeholder for bot reply keyboards.

+

Schema changes

+
Changed Constructors
+ +

Schema

+
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;\
+
+ + + +

Layer 129

+

Group call screen sharing, short name suggestions for stickerpacks, scoped bot commands, imported stickers, wallpaper and group call improvements.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
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;\
+
+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;\
+
+inputWallPaperNoFile#967a462e id:long = InputWallPaper;\
+
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;\
+
+updateMessagePollVote#37f69f0b poll_id:long user_id:int options:Vector<bytes> qts:int = Update;\
+
+groupCall#653dbaad 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 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 version:int = GroupCall;
+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;
+groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;
+groupCallParticipantVideo#78e41663 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> = GroupCallParticipantVideo;\
+
+updateGroupCallConnection#0b783982 flags:# presentation:flags.0?true params:DataJSON = Update;\
+
+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#0a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;\
+
+---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;\
+
+bots.setBotCommands#0517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;\
+
+phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;
+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.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
+phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;\
+
+stickers.checkShortName#284b3639 short_name:string = Bool;
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;\
+
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
+bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;\
+
+ + + +

Layer 128

+

Deprecate legacy profile picture locations, group call improvements.
See the file documentation article for more info on the new file constructors ».

+

Schema changes

+
Changed Methods
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed fileLocationToBeDeprecated
  • +
+

Schema

+
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;\
+
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#021e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;\
+
+inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
+inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;\
+
+videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;\
+
+photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;\
+
+---functions---\
+
+phone.editGroupCallParticipant#aec610e4 flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_muted:flags.3?Bool = Updates;\
+
+ + + +

Layer 127

+

Scheduled group calls, payments in channels, payment tips, stripped profile picture thumbnails.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
userProfilePhoto#cc656077 flags:# has_video:flags.0?true photo_id:long photo_small:FileLocation photo_big:FileLocation stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;\
+
+chatPhoto#4790ee05 flags:# has_video:flags.0?true photo_small:FileLocation photo_big:FileLocation stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;\
+
+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;\
+
+invoice#0cd886e0 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;\
+
+payments.paymentForm#8d0b2415 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:int invoice:Invoice provider_id:int 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.paymentReceipt#10b555d0 flags:# date:int bot_id:int provider_id:int 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;\
+
+groupCall#c95c6654 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 id:long access_hash:long participants_count:int params:flags.0?DataJSON title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int version:int = GroupCall;
+groupCallParticipant#b96b25ee 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 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 params:flags.6?DataJSON = GroupCallParticipant;\
+
+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;\
+
+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;\
+
+messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;\
+
+---functions---\
+
+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;
+phone.createGroupCall#48cdc6d8 flags:# peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
+phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;\
+
+ + + +

Layer 126

+

Ban channels in chats.

+

Schema changes

+
Changed Methods
+ +
Changed Constructors
+ +

Schema

+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+channelParticipantBanned#50a1dfd6 flags:# left:flags.0?true peer:Peer kicked_by:int date:int banned_rights:ChatBannedRights = ChannelParticipant;
+channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;\
+
+---functions---\
+
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;
+channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;\
+
+ + + +

Layer 125

+

Voice chats in channels.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
Deleted Methods
+
    +
  • Removed phone.editGroupCallMember
  • +
+
New Constructors
+ +
Changed Constructors
+ +

Schema

+
chatFull#8a1e2983 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int 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 = ChatFull;\
+
+updateChatUserTyping#86cadb6c chat_id:int from_id:Peer action:SendMessageAction = Update;\
+
+channelFull#548c3f93 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:int 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?int 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?int 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 = ChatFull;\
+
+updateChannelUserTyping#6b171718 flags:# channel_id:int top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;\
+
+groupCall#c0c2052e flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true id:long access_hash:long participants_count:int params:flags.0?DataJSON title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int version:int = GroupCall;
+groupCallParticipant#19adba89 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 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 = 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;\
+
+inputGroupCallStream#bba51639 call:InputGroupCall time_ms:long scale:int = InputFileLocation;\
+
+phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;\
+
+---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;\
+
+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.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
+phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;
+phone.toggleGroupCallRecord#c02a66d7 flags:# start:flags.0?true call:InputGroupCall title:flags.1?string = Updates;
+phone.editGroupCallParticipant#d975eb80 flags:# muted:flags.0?true call:InputGroupCall participant:InputPeer volume:flags.1?int raise_hand:flags.2?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;\
+
+ + + +

Layer 124

+

Expiring invite links, self-destruction settings for all messages in a chat, gigagroups, chat import improvements.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
chatFull#f06c4018 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int 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 = ChatFull;\
+
+message#bce383d2 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?int 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;\
+
+inputReportReasonOther#c1e4a2b1 = ReportReason;\
+
+userFull#139a9a77 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 = UserFull;
+updateShortMessage#faeff833 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:int message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?int reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#1157b858 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:int chat_id:int message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?int reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;\
+
+channelFull#2548c037 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:int 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?int 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?int 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> = ChatFull;\
+
+messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;\
+
+updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
+updateChatParticipant#f3b3781f flags:# chat_id:int date:int actor_id:int user_id:int prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateChannelParticipant#7fecb1ec flags:# channel_id:int date:int actor_id:int user_id:int prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateBotStopped#07f9488a user_id:int date:int stopped:Bool qts:int = Update;\
+
+chatInviteImporter#1e3e6680 user_id:int 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#dfd2330f admin_id:int invites_count:int revoked_invites_count:int = ChatAdminWithInvites;\
+
+messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;\
+
+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;\
+
+messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;\
+
+---functions---\
+
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;\
+
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
+messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;\
+
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = 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#02e4ffbe 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;\
+
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;\
+
+channels.convertToGigagroup#0b290c69 channel:InputChannel = Updates;\
+
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;\
+
+ + + +

Layer 123

+

Import messages from foreign chat apps, delete history for both users upon deletion of a secret chat, delete phone call history, group call improvements.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+
    +
  • Changed type of exported_invite from ExportedChatInvite to flags.13?ExportedChatInvite in chatFull
  • +
  • Added flags, peer_id parameters in messageEmpty
  • +
  • Added flags, history_deleted parameters in encryptedChatDiscarded
  • +
  • Added flags, revoked, permanent, admin_id, date, start_date, expire_date, usage_limit, usage parameters in chatInviteExported
  • +
  • Added fake parameter in user
  • +
  • Added fake, gigagroup parameters in channel
  • +
  • Changed type of exported_invite from ExportedChatInvite to flags.23?ExportedChatInvite in channelFull
  • +
  • Added min, muted_by_you, volume_by_admin, volume parameters in groupCallParticipant
  • +
+
Deleted Constructors
+
    +
  • Removed chatInviteEmpty
  • +
  • Removed inputPaymentCredentialsAndroidPay
  • +
+

Schema

+
chatFull#f3474af6 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int 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 = ChatFull;\
+
+messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;\
+
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;\
+
+chatInviteExported#6e24fc9d flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:int date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;\
+
+user#938458c1 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:int 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;\
+
+channel#d31a961e 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 id:int access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int version: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;
+channelFull#7a7de4f7 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:int 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?int 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?int 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 = ChatFull;\
+
+groupCallParticipant#64c62a15 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 user_id:int date:int active_date:flags.3?int source:int volume:flags.7?int = GroupCallParticipant;\
+
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;\
+
+messages.historyImport#1662af0b id:long = messages.HistoryImport;\
+
+sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;\
+
+messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;\
+
+inputReportReasonFake#f5ddd6e7 = ReportReason;\
+
+messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;\
+
+---functions---\
+
+messages.deleteChatUser#c534459a flags:# revoke_history:flags.0?true chat_id:int user_id:InputUser = Updates;
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;\
+
+phone.editGroupCallMember#a5e76cd8 flags:# muted:flags.0?true call:InputGroupCall user_id:InputUser volume:flags.1?int = Updates;\
+
+messages.deleteChat#83247d11 chat_id:int = 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;\
+
+ + + +

Layer 122

+

Group calls.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed updateChannelParticipant
  • +
+

PUSH notification changes

+
New PUSH notifications
+ +
Changed PUSH notifications
+
    +
  • Changed template from {1} posted a map to {1} posted a location in CHANNEL_MESSAGE_GEO
  • +
  • Changed template from {1} posted a {2}sticker to {1} posted a {2} sticker in CHANNEL_MESSAGE_STICKER
  • +
  • Changed template from {1} kicked {3} from the group {2} to {1} removed {3} from the group {2} in CHAT_DELETE_MEMBER
  • +
  • Changed template from {1} kicked you from the group {2} to {1} removed you from the group {2} in CHAT_DELETE_YOU
  • +
  • Changed template from {1} has joined the group {2} to {1} joined the group {2} in CHAT_JOINED
  • +
  • Changed template from {1} has left the group {2} to {1} left the group {2} in CHAT_LEFT
  • +
  • Changed template from {1} invited the group {2} to play {3}. to {1} invited the group {2} to play {3} in CHAT_MESSAGE_GAME
  • +
  • Changed template from {1} sent a map to the group {2} to {1} sent a location to the group {2} in CHAT_MESSAGE_GEO
  • +
  • Changed template from {1} started sharing their live location with {2} to {1} shared a live location with the group {2} in CHAT_MESSAGE_GEOLIVE
  • +
  • Changed template from {1} sent a {3}sticker to the group {2} to {1} sent a {3} sticker to the group {2} in CHAT_MESSAGE_STICKER
  • +
  • Changed template from {1}@{2}: {3} to {1} @ {2}: {3} in CHAT_MESSAGE_TEXT
  • +
  • Changed template from {1} edited the group's {2} photo to {1} changed the group photo for {2} in CHAT_PHOTO_EDITED
  • +
  • Changed template from {1} has returned to the group {2} to {1} returned to the group {2} in CHAT_RETURNED
  • +
  • Changed template from {1} edited the group's {2} name to {1} renamed the group {2} in CHAT_TITLE_EDITED
  • +
  • Changed template from {1} sent you a map to {1} sent you a location in MESSAGE_GEO
  • +
  • Changed template from {1} started sharing their live location to {1} sent you a live location in MESSAGE_GEOLIVE
  • +
  • Changed template from {1} sent you a {2}sticker to {1} sent you a {2} sticker in MESSAGE_STICKER
  • +
  • Changed template from {1} pinned a {2}sticker to {1} pinned a {2} sticker in PINNED_STICKER
  • +
+

Schema

+
chat#3bda1bde 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 id:int 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;
+chatFull#0dc8c181 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall = ChatFull;\
+
+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;\
+
+inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;\
+
+stickerSet#40e237a8 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 count:int hash:int = StickerSet;\
+
+channel#d31a961e 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 id:int access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int version: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;
+channelFull#ef3a6acd 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:int 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:ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?int 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?int 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 = ChatFull;\
+
+updateBotInlineQuery#3f2038db flags:# query_id:long user_id:int query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;\
+
+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;\
+
+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;
+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;\
+
+speakingInGroupCallAction#d92c2285 = SendMessageAction;\
+
+groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
+groupCall#55903081 flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true id:long access_hash:long participants_count:int params:flags.0?DataJSON version:int = GroupCall;\
+
+inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;\
+
+messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
+messageActionInviteToGroupCall#76b9f11a call:InputGroupCall users:Vector<int> = MessageAction;\
+
+groupCallParticipant#56b087c9 flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true user_id:int date:int active_date:flags.3?int source:int = GroupCallParticipant;\
+
+updateChat#1330a196 chat_id:int = Update;
+updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
+updateGroupCall#a45eb99b chat_id:int call:GroupCall = Update;\
+
+phone.groupCall#66ab0bfc call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string users:Vector<User> = phone.GroupCall;
+phone.groupParticipants#9cfeb92d count:int participants:Vector<GroupCallParticipant> next_offset:string users:Vector<User> version:int = phone.GroupParticipants;\
+
+inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
+inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
+inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
+inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
+inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;\
+
+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;\
+
+---functions---\
+
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;\
+
+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;\
+
+phone.createGroupCall#bd3dabe0 peer:InputPeer random_id:int = Updates;
+phone.joinGroupCall#5f9c8e62 flags:# muted:flags.0?true call:InputGroupCall params:DataJSON = Updates;
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
+phone.editGroupCallMember#63146ae4 flags:# muted:flags.0?true call:InputGroupCall user_id:InputUser = Updates;
+phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
+phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
+phone.toggleGroupCallSettings#74bbb43d flags:# call:InputGroupCall join_muted:flags.0?Bool = Updates;
+phone.getGroupCall#0c7cb017 call:InputGroupCall = phone.GroupCall;
+phone.getGroupParticipants#c9f1d285 call:InputGroupCall ids:Vector<int> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;
+phone.checkGroupCall#b74a7bea call:InputGroupCall source:int = Bool;\
+
+ + + +

Layer 121

+

Added SVG path previews for animated stickers.

+

Schema changes

+
New Constructors
+
    +
  • Added photoPathSize - Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.
  • +
+

Schema

+
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;\
+
+ + + +

Layer 120

+

Added message statistics, and a method to unpin all pinned messages in a chat.

+

Schema changes

+
New Methods
+ +
Changed Methods
+
    +
  • Changed type of from_id from flags.0?InputUser to flags.0?InputPeer in messages.search
  • +
+
New Constructors
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed updateChannelPinnedMessage
  • +
  • Removed updateUserPinnedMessage
  • +
  • Removed updateChatPinnedMessage
  • +
+

PUSH notification changes

+
New PUSH notifications
+ +

Schema

+
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;\
+
+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;\
+
+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;\
+
+botInlineMessageMediaGeo#051846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;\
+
+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;\
+
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;\
+
+inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;\
+
+channelParticipantLeft#c3c6796b user_id:int = ChannelParticipant;
+channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;\
+
+updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
+updatePinnedChannelMessages#8588878b flags:# pinned:flags.0?true channel_id:int messages:Vector<int> pts:int pts_count:int = Update;\
+
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;\
+
+stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;\
+
+messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;\
+
+---functions---\
+
+messages.search#0c352eec 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:int = messages.Messages;\
+
+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;\
+
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;\
+
+ + + +

Layer 119

+

Added message threads and comment sections in channel posts.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+
    +
  • Added pinned, peer_id, reply_to, forwards, replies parameters, removed to_id, reply_to_msg_id parameters, changed type of from_id from flags.8?int to flags.8?Peer in message
  • +
  • Added peer_id, reply_to parameters, removed to_id, reply_to_msg_id parameters, changed type of from_id from flags.8?int to flags.8?Peer in messageService
  • +
  • Added chats parameter, changed type of blocked from Vector<ContactBlocked> to Vector<PeerBlocked> in contacts.blocked
  • +
  • Added chats parameter, changed type of blocked from Vector<ContactBlocked> to Vector<PeerBlocked> in contacts.blockedSlice
  • +
  • Added reply_to parameter, removed reply_to_msg_id parameter in updateShortMessage
  • +
  • Added reply_to parameter, removed reply_to_msg_id parameter in updateShortChatMessage
  • +
  • Added admin_rights parameter in channelParticipantCreator
  • +
  • Removed channel_id parameter, changed type of from_id from flags.0?int to flags.0?Peer in messageFwdHeader
  • +
+
Deleted Constructors
+
    +
  • Removed contactBlocked
  • +
  • Removed updateUserBlocked
  • +
+

Schema

+
message#58ae39c9 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?int 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> = Message;
+messageService#286fa604 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 = Message;\
+
+contacts.blocked#0ade1591 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;\
+
+updateShortMessage#2296d2c8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:int message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?int reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> = Updates;
+updateShortChatMessage#402d5dbb flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:int chat_id:int message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?int reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> = Updates;\
+
+channelParticipantCreator#447dca4b flags:# user_id:int admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;\
+
+messageFwdHeader#5f777dce flags:# 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;
+messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;\
+
+updateChannelMessageForwards#6e8a84df channel_id:int id:int forwards:int = Update;\
+
+photoSizeProgressive#5aa86a51 type:string location:FileLocation w:int h:int sizes:Vector<int> = PhotoSize;\
+
+messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;\
+
+updateReadChannelDiscussionInbox#1cc7de54 flags:# channel_id:int top_msg_id:int read_max_id:int broadcast_id:flags.0?int broadcast_post:flags.0?int = Update;
+updateReadChannelDiscussionOutbox#4638a26c channel_id:int top_msg_id:int read_max_id:int = Update;\
+
+messages.discussionMessage#f5dd8f9d flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?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#4128faac flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?int max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;\
+
+updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;\
+
+peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;\
+
+updateChannelUserTyping#ff2abe9f flags:# channel_id:int top_msg_id:flags.0?int user_id:int action:SendMessageAction = Update;\
+
+---functions---\
+
+contacts.block#68cc1411 id:InputPeer = Bool;
+contacts.unblock#bea65d50 id:InputPeer = Bool;\
+
+messages.search#4e17810b flags:# peer:InputPeer q:string from_id:flags.0?InputUser 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:int = messages.Messages;
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;
+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;\
+
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;\
+
+messages.getReplies#24b581ba peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:int = 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;\
+
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;\
+
+ + + +

Layer 118

+

Added method for fetching country names and phone patterns.

+

Schema changes

+
New Methods
+
    +
  • Added help.getCountriesList - Get name, ISO code, localized name and phone codes/patterns of all available countries
  • +
+
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;\
+
+help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
+help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
+help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;\
+
+---functions---\
+
+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.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;\
+
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;\
+
+ + + +

Layer 117

+

Added WebRTC endpoint constructors.

+

Schema changes

+
New Constructors
+ +

Schema

+
phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;\
+
+ + + +

Layer 116

+

Added supergroup statistics and global privacy settings.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;\
+
+userProfilePhoto#69d3ab26 flags:# has_video:flags.0?true photo_id:long photo_small:FileLocation photo_big:FileLocation dc_id:int = UserProfilePhoto;\
+
+chatPhoto#d20b9f3c flags:# has_video:flags.0?true photo_small:FileLocation photo_big:FileLocation dc_id:int = ChatPhoto;\
+
+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;
+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 geo_distance:flags.6?int = PeerSettings;\
+
+encryptedChatRequested#62718a82 flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:int participant_id:int g_a:bytes = EncryptedChat;\
+
+videoSize#e831c556 flags:# type:string location:FileLocation w:int h:int size:int video_start_ts:flags.0?double = VideoSize;\
+
+statsGroupTopPoster#18f3d0f7 user_id:int messages:int avg_chars:int = StatsGroupTopPoster;
+statsGroupTopAdmin#6014f412 user_id:int deleted:int kicked:int banned:int = StatsGroupTopAdmin;
+statsGroupTopInviter#31962a4c user_id:int 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;\
+
+updateChannelParticipant#65d2b464 flags:# channel_id:int date:int user_id:int prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant qts:int = Update;\
+
+---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;\
+
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;\
+
+account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
+account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;\
+
+help.dismissSuggestion#077fa99f suggestion:string = Bool;\
+
+ + + +

Layer 115

+

Added a chat invitation that also allows peeking into the group to read messages without joining it.

+

Schema changes

+
New Constructors
+
    +
  • Added chatInvitePeek - A chat invitation that also allows peeking into the group to read messages without joining it.
  • +
+

Schema

+
chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;\
+
+ + + +

Layer 114

+

Added WebRTC signaling methods.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
Deleted Methods
+
    +
  • Removed messages.searchGifs
  • +
+
New Constructors
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed foundGif
  • +
  • Removed foundGifCached
  • +
  • Removed inputMediaGifExternal
  • +
  • Removed messages.foundGifs
  • +
+

Schema

+
userFull#edf17c12 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 = UserFull;\
+
+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;\
+
+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;\
+
+user#938458c1 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 id:int 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;\
+
+channelFull#f0e6672a 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:int 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:ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?int 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?int location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int = ChatFull;\
+
+phoneCallWaiting#1b8f4ad1 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:int participant_id:int protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
+phoneCallRequested#87eabb53 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:int participant_id:int g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCallAccepted#997c454a flags:# video:flags.6?true id:long access_hash:long date:int admin_id:int participant_id:int g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCall#8742ae7f flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:int participant_id:int 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;\
+
+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 = ChatAdminRights;\
+
+videoSize#435bb987 type:string location:FileLocation w:int h:int size:int = VideoSize;\
+
+updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;\
+
+---functions---\
+
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;\
+
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;\
+
+ + + +

Layer 113

+

Public Service Announcement constructors and better PUSH notifications.
Notice that all PINNED_* PUSH notifications have two variants: one for groups, and one for channels.

+

Schema changes

+
New Methods
+ +
Deleted Methods
+
    +
  • Removed help.getProxyData
  • +
+
New Constructors
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed help.proxyDataEmpty
  • +
  • Removed help.proxyDataPromo
  • +
+

PUSH notification changes

+
New PUSH notifications
+ +
Changed PUSH notifications
+ +

Schema

+
messageFwdHeader#353a686b flags:# from_id:flags.0?int from_name:flags.5?string date:int channel_id:flags.1?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;\
+
+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;
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;\
+
+ + + +

Layer 112

+

Schema changes

+
New Methods
+ +
Changed Constructors
+ +

Schema

+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#b6abc341 hash:int count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;\
+
+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;
+pollResults#badcc1a3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<int> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;\
+
+inputMediaPoll#0f94e5f1 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;\
+
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;\
+
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;\
+
+---functions---\
+
+initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;\
+
+messages.getOldFeaturedStickers#5fe7025b offset:int limit:int hash:int = messages.FeaturedStickers;\
+
+ + + +

Layer 111

+

Folders, channel stats, bot and sticker improvements

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
channelFull#f0e6672a 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_view_stats:flags.12?true can_set_location:flags.16?true has_scheduled:flags.19?true id:int 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:ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?int 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?int location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int = ChatFull;\
+
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;\
+
+phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;
+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;\
+
+dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;
+dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;\
+
+updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
+updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
+updateDialogFilters#3504914f = Update;\
+
+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;\
+
+inputMediaDice#aeffa807 = InputMedia;\
+
+messageMediaDice#638fe46b value:int = MessageMedia;\
+
+inputStickerSetDice#79e21a53 = InputStickerSet;\
+
+---functions---\
+
+initConnection#785188b8 {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;\
+
+stickers.createStickerSet#f1036780 flags:# masks:flags.0?true animated:flags.1?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> = messages.StickerSet;\
+
+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;\
+
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;\
+
+bots.setBotCommands#805d46f6 commands:Vector<BotCommand> = Bool;\
+
+ + + +

Layer 110

+

Credit card information

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +

Schema

+
messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;\
+
+bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;\
+
+payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
+peerSelfLocated#f8ec284b expires:int = PeerLocated;\
+
+---functions---\
+
+initConnection#785188b8 {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 query:!X = X;\
+
+contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;\
+
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;\
+
+ + + +

Layer 109

+

Non-anonymous polls, improved sticker management

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
pollResults#c87024a2 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<int> = PollResults;\
+
+inputMediaPoll#abe9ca25 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> = InputMedia;\
+
+updateMessagePollVote#42f88f2c poll_id:long user_id:int options:Vector<bytes> = Update;\
+
+messageUserVote#a28e5559 user_id:int option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#36377430 user_id:int date:int = MessageUserVote;
+messageUserVoteMultiple#0e8fe0de user_id:int options:Vector<bytes> date:int = MessageUserVote;
+messages.votesList#0823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;\
+
+keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;\
+
+---functions---\
+
+initConnection#785188b8 {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;\
+
+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;\
+
+ + + +

Layer 108

+

Login with QR-code, sensitive content settings, quizes, multiple-choice and public polls, get inactive chats, improved wallpapers and themes.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+
    +
  • Added attributes parameter, removed documents parameter in webPage
  • +
  • Added public_voters, multiple_choice, quiz parameters in poll
  • +
  • Added correct parameter in pollAnswerVoters
  • +
  • Added second_background_color, rotation parameters in wallPaperSettings
  • +
  • Added video_upload_maxbitrate parameter in autoDownloadSettings
  • +
  • Added settings parameter in theme
  • +
+
Deleted Constructors
+
    +
  • Removed themeDocumentNotModified
  • +
+

Schema

+
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;\
+
+poll#d5529d06 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> = Poll;
+pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;\
+
+wallPaperSettings#05086cf8 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?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;\
+
+inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;\
+
+theme#028f1114 flags:# creator:flags.0?true default:flags.1?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:int = Theme;\
+
+updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
+updateLoginToken#564fe691 = Update;\
+
+auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#068e9916 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;\
+
+inputWallPaperNoFile#8427bbac = InputWallPaper;\
+
+wallPaperNoFile#8af40b25 flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;\
+
+inputThemeSettings#bd507cd1 flags:# base_theme:BaseTheme accent_color:int message_top_color:flags.0?int message_bottom_color:flags.0?int wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;\
+
+themeSettings#9c14984a flags:# base_theme:BaseTheme accent_color:int message_top_color:flags.0?int message_bottom_color:flags.0?int wallpaper:flags.1?WallPaper = ThemeSettings;\
+
+webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;\
+
+---functions---\
+
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;\
+
+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;
+auth.exportLoginToken#b1b41517 api_id:int api_hash:string except_ids:Vector<int> = auth.LoginToken;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
+account.getContentSettings#8b9b4dae = account.ContentSettings;\
+
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;\
+
+account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;\
+
+ + + +

Layer 105

+

The API underwent huge changes, a full reread of the documentation is required.

+

Layer 23

+

Schema changes

+
New Methods
+ +
Deleted Methods
+
    +
  • Removed invokeWithLayer18
  • +
+
New Constructors
+ +
Changed Constructors
+ +

Schema

+
contactStatus#d3680c61 user_id:int status:UserStatus = ContactStatus;
+config#7dae33e0 date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> chat_big_size:int chat_size_max:int broadcast_size_max:int disabled_features:Vector<DisabledFeature> = Config;\
+
+inputMediaUploadedDocument#ffe76b78 file:InputFile mime_type:string attributes:Vector<DocumentAttribute> = InputMedia;
+inputMediaUploadedThumbDocument#41481486 file:InputFile thumb:InputFile mime_type:string attributes:Vector<DocumentAttribute> = InputMedia;\
+
+document#f9a39f4f id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = Document;\
+
+userStatusRecently#e26f42f1 = UserStatus;
+userStatusLastWeek#07bf09fc = UserStatus;
+userStatusLastMonth#77ebc742 = UserStatus;
+updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;\
+
+inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;\
+
+privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;\
+
+inputPrivacyValueAllowContacts#0d09e07b = InputPrivacyRule;
+inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
+inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueDisallowContacts#0ba52007 = InputPrivacyRule;
+inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
+inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;\
+
+privacyValueAllowContacts#fffe1bac = PrivacyRule;
+privacyValueAllowAll#65427b82 = PrivacyRule;
+privacyValueAllowUsers#4d5bbe0c users:Vector<int> = PrivacyRule;
+privacyValueDisallowContacts#f888fa1a = PrivacyRule;
+privacyValueDisallowAll#8b73e763 = PrivacyRule;
+privacyValueDisallowUsers#0c7f49b7 users:Vector<int> = PrivacyRule;\
+
+account.privacyRules#554abb6f rules:Vector<PrivacyRule> users:Vector<User> = account.PrivacyRules;
+accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+account.sentChangePhoneCode#a4f58c4c phone_code_hash:string send_call_timeout:int = account.SentChangePhoneCode;\
+
+updateUserPhone#12b9417b user_id:int phone:string = Update;\
+
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#fb0a5727 = DocumentAttribute;
+documentAttributeVideo#5910cccb duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#051448e5 duration:int = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;\
+
+messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#8a8ecd32 hash:string stickers:Vector<Document> = messages.Stickers;\
+
+stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;\
+
+messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#dcef3102 hash:string packs:Vector<StickerPack> documents:Vector<Document> = messages.AllStickers;\
+
+disabledFeature#ae636f24 feature:string description:string = DisabledFeature;\
+
+---functions---\
+
+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#08fc711d = AccountDaysTTL;
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;\
+
+invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;\
+
+contacts.resolveUsername#0bf0131c username:string = User;\
+
+account.sendChangePhoneCode#a407a8f4 phone_number:string = account.SentChangePhoneCode;
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;\
+
+messages.getStickers#ae22e045 emoticon:string hash:string = messages.Stickers;
+messages.getAllStickers#aa3bc868 hash:string = messages.AllStickers;\
+
+account.updateDeviceLocked#38df3532 period:int = Bool;\
+
+ +

End-to-end schema changes

+
New Constructors
+ +

End-to-end schema

+
===20===\
+
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
+decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;\
+
+===23===
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#fb0a5727 = DocumentAttribute;
+documentAttributeVideo#5910cccb duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#051448e5 duration:int = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;\
+
+photoSizeEmpty#0e17e23c type:string = PhotoSize;
+photoSize#77bfb61b type:string location:FileLocation w:int h:int size:int = PhotoSize;
+photoCachedSize#e9a734fa type:string location:FileLocation w:int h:int bytes:bytes = PhotoSize;\
+
+fileLocationUnavailable#7c596b46 volume_id:long local_id:int secret:long = FileLocation;
+fileLocation#53d69076 dc_id:int volume_id:long local_id:int secret:long = FileLocation;\
+
+decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;\
+
+ +

Layer 18

+

Added username support and a new type of updates for service messages.

+

Schema changes

+ +

Schema

+
contactFound user_id:int = ContactFound;
+
+contacts.found results:Vector<ContactFound> users:Vector<User> = contacts.Found;
+
+updateUserName user_id:int first_name:string last_name:string username:string = Update;
+
+userSelf id:int first_name:string last_name:string username:string phone:string photo:UserProfilePhoto status:UserStatus inactive:Bool = User;
+userContact id:int first_name:string last_name:string username:string access_hash:long phone:string photo:UserProfilePhoto status:UserStatus = User;
+userRequest id:int first_name:string last_name:string username:string access_hash:long phone:string photo:UserProfilePhoto status:UserStatus = User;
+userForeign id:int first_name:string last_name:string username:string access_hash:long photo:UserProfilePhoto status:UserStatus = User;
+userDeleted id:int first_name:string last_name:string username:string = User;
+
+updateServiceNotification type:string message:string media:MessageMedia popup:Bool = Update;
+
+---functions---
+
+account.checkUsername username:string = Bool;
+account.updateUsername username:string = User;
+
+contacts.search q:string limit:int = contacts.Found;
+
+invokeWithLayer18#1c900537 {X:Type} query:!X = X;
+

Layer 17

+

Added new events for recording and uploading media, selecting contacts and locations to share.

+

Read status for multimedia (messages containing messageMediaVideo or messageMediaAudio) was moved to the new method messages.readMessageContents. In case read_contents is not passed or messages.readHistory is used with an older layer, messages will be marked as read in the traditional way.

+

Schema changes

+
    +
  • Added new type SendMessageAction for user actions aside from typing (recording, uploading media, etc.). It is used in updates updateUserTyping, updateChatUserTyping, in the method messages.setTyping, and in the new encrypted service message decryptedMessageActionTyping.
  • +
  • unread and out parameters in the constructors of the Message type were joined to form the new flags parameter, containing a flag mask.
  • +
  • Added new method messages.readMessageContents, to be called once the user listened to a voice message or watched a video.
  • +
  • Added parameters for end-to-end encrypted messages in_seq_no, out_seq_no and ttl.
  • +
  • Added mime_type field to secret chat audio and video constructors.
  • +
+

Schema

+
sendMessageTypingAction = SendMessageAction;
+sendMessageCancelAction = SendMessageAction;
+sendMessageRecordVideoAction = SendMessageAction;
+sendMessageUploadVideoAction = SendMessageAction;
+sendMessageRecordAudioAction = SendMessageAction;
+sendMessageUploadAudioAction = SendMessageAction;
+sendMessageUploadPhotoAction = SendMessageAction;
+sendMessageUploadDocumentAction = SendMessageAction;
+sendMessageGeoLocationAction = SendMessageAction;
+sendMessageChooseContactAction = SendMessageAction;
+
+updateUserTyping user_id:int action:SendMessageAction = Update;
+updateChatUserTyping chat_id:int user_id:int action:SendMessageAction = Update;
+
+// Message object
+message flags:int id:int from_id:int to_id:Peer date:int message:string media:MessageMedia = Message;
+messageForwarded flags:int id:int fwd_from_id:int fwd_date:int from_id:int to_id:Peer date:int message:string media:MessageMedia = Message;
+messageService flags:int id:int from_id:int to_id:Peer date:int action:MessageAction = Message;
+
+---functions---
+
+messages.setTyping peer:InputPeer action:SendMessageAction = Bool;
+
+messages.readHistory peer:InputPeer max_id:int offset:int read_contents:Bool = messages.AffectedHistory;
+messages.readMessageContents id:Vector<int> = Vector<int>;
+
+invokeWithLayer17#50858a19 {X:Type} query:!X = X;
+

End-to-end schema

+
===17===
+
+
+// Layer
+decryptedMessageLayer random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;
+
+decryptedMessageMediaAudio duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaVideo thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+sendMessageTypingAction = SendMessageAction;
+sendMessageCancelAction = SendMessageAction;
+sendMessageRecordVideoAction = SendMessageAction;
+sendMessageUploadVideoAction = SendMessageAction;
+sendMessageRecordAudioAction = SendMessageAction;
+sendMessageUploadAudioAction = SendMessageAction;
+sendMessageUploadPhotoAction = SendMessageAction;
+sendMessageUploadDocumentAction = SendMessageAction;
+sendMessageGeoLocationAction = SendMessageAction;
+sendMessageChooseContactAction = SendMessageAction;
+
+decryptedMessageActionNotifyLayer layer:int = DecryptedMessageAction;
+decryptedMessageActionTyping action:SendMessageAction = DecryptedMessageAction;
+
+decryptedMessage random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService random_id:long action:DecryptedMessageAction = DecryptedMessage;
+

Layer 16

+

Added new sms_type = 5 in the method auth.sendCode.

+

Schema changes

+
    +
  • Added new constructor: auth.sentAppCode to determine whether a code was sent via Telegram.
  • +
  • Added new method auth.sendSms to force re-sending a code via SMS.
  • +
+

Schema

+
auth.sentAppCode phone_registered:Bool phone_code_hash:string send_call_timeout:int is_password:Bool = auth.SentCode;
+
+---functions---
+
+auth.sendSms phone_number:string phone_code_hash:string = Bool;
+
+invokeWithLayer16#cf5f0987 {X:Type} query:!X = X;
+

Layer 15

+

Modified behavior of the offset parameter in the method messages.getHistory. From now on it's possible to combine message_id offset and a numeric offset.

+

Schema

+
invokeWithLayer15#b4418b64 {X:Type} query:!X = X;
+

Layer 14

+

Schema changes

+ +

Schema

+
notifyPeer peer:Peer = NotifyPeer;
+notifyUsers = NotifyPeer;
+notifyChats = NotifyPeer;
+notifyAll = NotifyPeer;
+
+dialog peer:Peer top_message:int unread_count:int notify_settings:PeerNotifySettings = Dialog;
+
+updateUserBlocked user_id:int blocked:Bool = Update;
+updateNotifySettings peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
+
+---functions---
+
+invokeWithLayer14#2b9b08fa {X:Type} query:!X = X;
+

Layer 13

+

Schema changes

+
    +
  • Added mime_type field to all audio and video constructors.
  • +
  • Added new service message types in secret chats: messages read, messages deleted, screenshot taken, chat history cleared and API layer used by client notifications.
  • +
  • Added retry_contacts field to the contacts.importedContacts constructor: ids of contacts, that will have to be imported at a later date.
  • +
+

Schema

+
contacts.importedContacts imported:Vector<ImportedContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+
+inputMediaUploadedAudio file:InputFile duration:int mime_type:string = InputMedia;
+inputMediaUploadedVideo file:InputFile duration:int w:int h:int mime_type:string = InputMedia;
+inputMediaUploadedThumbVideo file:InputFile thumb:InputFile duration:int w:int h:int mime_type:string = InputMedia;
+
+audio id:long access_hash:long user_id:int date:int duration:int mime_type:string size:int dc_id:int = Audio;
+video id:long access_hash:long user_id:int date:int caption:string duration:int mime_type:string size:int thumb:PhotoSize dc_id:int w:int h:int = Video;
+
+---functions---
+
+invokeWithLayer13#427c8ea2 {X:Type} query:!X = X;
+

Layer 12

+

Schema changes

+
    +
  • Added method help.getSupport for obtaining support user id.
  • +
  • Added broadcast_size_max field to the constructor config, contaning maximum number of broadcast recipients.
  • +
  • Added send_call_timeout field to the constructor auth.sentCode, containing required delay before calling auth.sendCall. New field is_password in the same constructor.
  • +
+

Schema

+
auth.sentCode phone_registered:Bool phone_code_hash:string send_call_timeout:int is_password:Bool = auth.SentCode;
+
+config date:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> chat_size_max:int broadcast_size_max:int = Config;
+
+help.support phone_number:string user:User = help.Support;
+
+---functions---
+
+help.getSupport = help.Support;
+
+invokeWithLayer12#dda60d3c {X:Type} query:!X = X;
+

Layer 11

+

Schema changes

+
    +
  • The nonce parameter was removed from secret chat constructors. For purposes of backward compatibility, in all previous layers this field will contain empty bytes.
  • +
+

Schema

+
encryptedChatRequested id:int access_hash:long date:int admin_id:int participant_id:int g_a:bytes = EncryptedChat;
+encryptedChat id:int access_hash:long date:int admin_id:int participant_id:int g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+
+---functions---
+
+invokeWithLayer11#a6b88fdf {X:Type} query:!X = X;
+

Layer 10

+

Added brief constructors for editing group members. Added new attachment types for ordinary and secret chats.

+

Schema changes

+ +

Schema

+
updateChatParticipantAdd chat_id:int user_id:int inviter_id:int version:int = Update;
+updateChatParticipantDelete chat_id:int user_id:int version:int = Update;
+
+
+inputMediaUploadedAudio file:InputFile duration:int = InputMedia;
+inputMediaAudio id:InputAudio = InputMedia;
+
+inputMediaUploadedDocument file:InputFile file_name:string mime_type:string = InputMedia;
+inputMediaUploadedThumbDocument file:InputFile thumb:InputFile file_name:string mime_type:string = InputMedia;
+inputMediaDocument id:InputDocument = InputMedia;
+
+messageMediaDocument document:Document = MessageMedia;
+messageMediaAudio audio:Audio = MessageMedia;
+
+// Input Audio
+inputAudioEmpty = InputAudio;
+inputAudio id:long access_hash:long = InputAudio;
+
+// Input Document
+inputDocumentEmpty = InputDocument;
+inputDocument id:long access_hash:long = InputDocument;
+
+// Input location
+inputAudioFileLocation id:long access_hash:long = InputFileLocation;
+inputDocumentFileLocation id:long access_hash:long = InputFileLocation;
+
+
+decryptedMessageMediaDocument thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+
+// Audio object
+audioEmpty id:long = Audio;
+audio id:long access_hash:long user_id:int date:int duration:int size:int dc_id:int = Audio;
+
+// Video object
+documentEmpty id:long = Document;
+document id:long access_hash:long user_id:int date:int file_name:string mime_type:string size:int thumb:PhotoSize dc_id:int = Document;
+
+---functions---
+
+invokeWithLayer10#39620c41 {X:Type} query:!X = X;
+

Push-notifications

+

Added MESSAGE_DOC, MESSAGE_AUDIO notifications — a message with document or audio received Added CHAT_MESSAGE_DOC, CHAT_MESSAGE_AUDIO notifications — a message with document or audio received in a group

+

Layer 9

+

Increased efficiency when loading big files. Added important checks for certain methods.

+

Schema changes

+ +

Schema

+
inputFileBig id:long parts:int name:string = InputFile;
+
+inputEncryptedFileBigUploaded id:long parts:int key_fingerprint:int = InputEncryptedFile;
+
+---functions---
+
+upload.saveBigFilePart file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
+
+initConnection#69796de9 {X:Type} api_id:int device_model:string system_version:string app_version:string lang_code:string query:!X = X;
+
+invokeWithLayer9#76715a63 {X:Type} query:!X = X;
+

Layer 8

+

Added support for end-to-end encryption in secret chats. More…

+

Schema changes

+
    +
  • Added many constructors and methods for secret chats.
  • +
  • Added qts field in constructor updates.state.
  • +
  • Added 4 new constructors of Update type
  • +
+

Schema

+
updateNewEncryptedMessage message:EncryptedMessage qts:int = Update;
+updateEncryptedChatTyping chat_id:int = Update;
+updateEncryption chat:EncryptedChat date:int = Update;
+updateEncryptedMessagesRead chat_id:int max_date:int = Update;
+
+// EncryptedChat object
+encryptedChatEmpty id:int = EncryptedChat;
+encryptedChatWaiting id:int access_hash:long date:int admin_id:int participant_id:int = EncryptedChat;
+encryptedChatRequested id:int access_hash:long date:int admin_id:int participant_id:int g_a:bytes = EncryptedChat;
+encryptedChat id:int access_hash:long date:int admin_id:int participant_id:int g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded id:int = EncryptedChat;
+
+inputEncryptedChat chat_id:int access_hash:long = InputEncryptedChat;
+
+// EncryptedFile object
+encryptedFileEmpty = EncryptedFile;
+encryptedFile id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+inputEncryptedFileEmpty = InputEncryptedFile;
+inputEncryptedFileUploaded id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
+inputEncryptedFile id:long access_hash:long = InputEncryptedFile;
+
+inputEncryptedFileLocation id:long access_hash:long = InputFileLocation;
+
+// Encrypted message
+encryptedMessage random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;
+
+// Diffie-Hellman config
+messages.dhConfigNotModified random:bytes = messages.DhConfig;
+messages.dhConfig g:int p:bytes version:int random:bytes = messages.DhConfig;
+
+messages.sentEncryptedMessage date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile date:int file:EncryptedFile = messages.SentEncryptedMessage;
+
+// Updated state with qts
+updates.state pts:int qts:int date:int seq:int unread_count:int = updates.State;
+updates.difference 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 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;
+
+---functions---
+
+messages.getDhConfig version:int random_length:int = messages.DhConfig;
+messages.requestEncryption user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
+messages.acceptEncryption peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;
+messages.discardEncryption chat_id:int = Bool;
+
+messages.setEncryptedTyping peer:InputEncryptedChat typing:Bool = Bool;
+messages.readEncryptedHistory peer:InputEncryptedChat max_date:int = Bool;
+messages.sendEncrypted peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.sendEncryptedFile peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
+messages.sendEncryptedService peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.receivedQueue max_qts:int = Vector<long>;
+
+updates.getDifference pts:int date:int qts:int = updates.Difference;
+
+invokeWithLayer8#e9abd9fd {X:Type} query:!X = X;
+

Push-notifications

+
    +
  • Added notification of ENCRYPTION_REQUEST type — a contact requested secret chat creation
  • +
  • Added notification of ENCRYPTION_ACCEPT type — a contact confirmed secret chat creation
  • +
  • Added notification of ENCRYPTED_MESSAGE type — a contact sent message in a secret chat
  • +
+

End-to-end schema

+
===8===
+decryptedMessage random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+
+decryptedMessageMediaEmpty = DecryptedMessageMedia;
+decryptedMessageMediaPhoto thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaVideo thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaGeoPoint lat:double long:double = DecryptedMessageMedia;
+decryptedMessageMediaContact phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
+
+decryptedMessageActionSetMessageTTL ttl_seconds:int = DecryptedMessageAction;
+
+decryptedMessageMediaDocument thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+decryptedMessageActionReadMessages random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionDeleteMessages random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionScreenshotMessages random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionFlushHistory = DecryptedMessageAction;
+

Layer 7

+

Added wallpaper constructor wallPaperSolid.

+

Schema

+
wallPaperSolid id:int title:string bg_color:int color:int = WallPaper;
+---functions---
+invokeWithLayer7#a5be56d3 {X:Type} query:!X = X;
+

Layer 6

+

Added location identifiers from foursquare.

+

Schema

+
geoChat id:int access_hash:long title:string address:string venue:string geo:GeoPoint photo:ChatPhoto participants_count:int date:int checked_in:Bool version:int = Chat;
+---functions---
+geochats.createGeoChat title:string geo_point:InputGeoPoint address:string venue:string = geochats.StatedMessage;
+
+invokeWithLayer6#3a64d54d {X:Type} query:!X = X;
+

Layer 5

+

Added parameters for internationalization.

+

Schema changes

+ +

Schema

+
---functions---
+auth.sendCode phone_number:string sms_type:int api_id:int api_hash:string lang_code:string = auth.SentCode;
+account.registerDevice token_type:int token:string device_model:string system_version:string app_version:string app_sandbox:Bool lang_code:string = Bool;
+
+invokeWithLayer5#417a57ae {X:Type} query:!X = X;
+

Layer 4

+

Added geochats. More…

+

Schema changes

+
    +
  • Added many constructors and methods for geochats.
  • +
  • Added friends_unread_count field to constructor updates.state.
  • +
+

Schema

+
inputGeoChat chat_id:int access_hash:long = InputGeoChat;
+
+geoChat id:int access_hash:long title:string address:string geo:GeoPoint photo:ChatPhoto participants_count:int date:int left:Bool version:int = Chat;
+
+geoChatMessageEmpty chat_id:int id:int = GeoChatMessage;
+geoChatMessage chat_id:int id:int from_id:int date:int message:string media:MessageMedia = GeoChatMessage;
+geoChatMessageService chat_id:int id:int from_id:int date:int action:MessageAction = GeoChatMessage;
+
+geochats.statedMessage message:GeoChatMessage chats:Vector<Chat> users:Vector<User> seq:int = geochats.StatedMessage;
+
+geochats.located results:Vector<ChatLocated> messages:Vector<GeoChatMessage> chats:Vector<Chat> users:Vector<User> = geochats.Located;
+
+geochats.messages messages:Vector<GeoChatMessage> chats:Vector<Chat> users:Vector<User> = geochats.Messages;
+geochats.messagesSlice count:int messages:Vector<GeoChatMessage> chats:Vector<Chat> users:Vector<User> = geochats.Messages;
+
+messageActionGeoChatCreate title:string address:string = MessageAction;
+messageActionGeoChatCheckin = MessageAction;
+updateNewGeoChatMessage message:GeoChatMessage = Update;
+updates.state pts:int date:int seq:int unread_count:int friends_unread_count:int = updates.State;
+
+---functions---
+
+geochats.getLocated geo_point:InputGeoPoint radius:int limit:int = geochats.Located;
+geochats.checkin peer:InputGeoChat = geochats.StatedMessage;
+geochats.getFullChat peer:InputGeoChat = messages.ChatFull;
+geochats.editChatTitle peer:InputGeoChat title:string address:string = geochats.StatedMessage;
+geochats.editChatPhoto peer:InputGeoChat photo:InputChatPhoto = geochats.StatedMessage;
+geochats.search peer:InputGeoChat q:string filter:MessagesFilter min_date:int max_date:int offset:int max_id:int limit:int = geochats.Messages;
+geochats.getHistory peer:InputGeoChat offset:int max_id:int limit:int = geochats.Messages;
+geochats.setTyping peer:InputGeoChat typing:Bool = Bool;
+geochats.sendMessage peer:InputGeoChat message:string random_id:long = geochats.StatedMessage;
+geochats.sendMedia peer:InputGeoChat media:InputMedia random_id:long = geochats.StatedMessage;
+geochats.createGeoChat title:string geo_point:InputGeoPoint address:string = geochats.StatedMessage;
+
+invokeWithLayer4#dea0d430 {X:Type} query:!X = X;
+

Push-notifications

+
    +
  • Added notification of GEOCHAT_CHECKIN type — a user has checked-in in a geochat.
  • +
+

Layer 3

+

Support for link changes for a contact when a message is sent. Now, if user X has user Y in the contact list and if user Y writes a message to user X, number X will become available for him.

+

Schema changes

+ +

Schema

+
messages.statedMessagesLinks messages:Vector<Message> chats:Vector<Chat> users:Vector<User> links:Vector<contacts.Link> pts:int seq:int = messages.StatedMessages;
+messages.statedMessageLink message:Message chats:Vector<Chat> users:Vector<User> links:Vector<contacts.Link> pts:int seq:int = messages.StatedMessage;
+messages.sentMessageLink id:int date:int pts:int seq:int links:Vector<contacts.Link> = messages.SentMessage;
+
+---functions---
+
+messages.forwardMessage peer:InputPeer id:int random_id:long = messages.StatedMessage;
+messages.sendBroadcast contacts:Vector<InputUser> message:string media:InputMedia = messages.StatedMessages;
+
+invokeWithLayer3#b7475268 {X:Type} query:!X = X;
+

Layer 2

+

Support for notifications on changes of contact profile images. It is assumed that receiving such image changed notification a client will add a record on this event in the message history with this contact.

+

Schema changes

+ +

Schema

+
inputPeerNotifySettings mute_until:int sound:string show_previews:Bool events_mask:int = InputPeerNotifySettings;
+peerNotifySettings mute_until:int sound:string show_previews:Bool events_mask:int = PeerNotifySettings;
+updateUserPhoto user_id:int date:int photo:UserProfilePhoto previous:Bool = Update;
+userProfilePhoto photo_id:long photo_small:FileLocation photo_big:FileLocation = UserProfilePhoto;
+
+---functions---
+
+photos.getUserPhotos user_id:InputUser offset:int max_id:int limit:int = photos.Photos;
+
+invokeWithLayer2#289dd1f6 {X:Type} query:!X = X;
+

Push-notifications

+
    +
  • Added notification of CONTACT_PHOTO type — a contact has changed profile image.
  • +
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/live-location.html b/data/core.telegram.org/api/live-location.html new file mode 100644 index 0000000000..088510459a --- /dev/null +++ b/data/core.telegram.org/api/live-location.html @@ -0,0 +1,178 @@ + + + + + Live geolocation + + + + + + + + + + + + + +
+ +
+
+
+ +

Live geolocation

+ +
+ +

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

+

Sending live locations

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

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

+

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

+

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

+

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

+

Receiving live locations

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

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

+

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

+

Live location previews

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

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

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

The image is then downloaded as specified here »

+

Proximity alert

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

If:

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

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

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

Mentions

+ +
+ +

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

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

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

+ +

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

+

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

+

Dialog mentions

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

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

+

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

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

Min constructors

+ +

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

+

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

+

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

+

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

+ +

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

+

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

+

Example

+

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

+

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

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

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

+

The same can be done with min channels.

+

Example implementations: Telegram for iOS, tdlib.

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

Creating your Telegram Application

+ +

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

+
+

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

+
+

Obtaining api_id

+

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

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

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

+

Using the api_id

+

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

+

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

+

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

+

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

+

Using Telegram's open source code

+

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

+
+

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

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

Pagination in the API

+ +
+ +

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

+

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

+

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

+

limit parameter

+

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

+

offset-based pagination

+

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

+

offset_id-based pagination

+

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

+

Sample use cases:

+
    +
  • +

    Loading 20 messages, older than message with ID MSGID:

    +

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

    +
  • +
  • +

    Loading 20 messages, newer than message with ID MSGID:

    +

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

    +
  • +
  • +

    Loading 20 messages around message with ID MSGID:

    +

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

    +
  • +
+

Additional filtering

+

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

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

Hash generation

+

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

+

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

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

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

+

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

+

Example methods

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

Client-Side Optimization

+ +

Simplified Acknowledgment of Message Delivery

+

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

+

Server Salt

+

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

+

Downloading Files and Uploading Data to the Server

+

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

+

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

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

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

+

Sending Messages in Bulk

+

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

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

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

+

Grouping Updates

+

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

+

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

+

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

+

Setting the Typing Status

+

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

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

Telegram passport

+ +
+ +

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

+

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

+

Overview

+

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

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

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

+

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

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

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

+

As a bot

+

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

+

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

+
+

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

+
+

Setting Up Telegram Passport

+

As per the bot API.

+

Requesting Information

+

As per the bot API.

+

Receiving information

+

Schema:

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

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

+

Decrypting data

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

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

+
    +
  1. +

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

    +
  2. +
  3. +

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

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

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

    +
  6. +
  7. +

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

    +
  8. +
+
+

Note that all hashes are raw binary data, not hexits

+
+

Credentials

+

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

+

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

+

Fixing errors

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

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

+

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

+

As a user

+

Receiving requests

+

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

+

URI format

+

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

+
tg://resolve?params
+

With the following query string parameters:

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

Example URI, generated by the Telegram Passport Example page:

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

UriPassportScope

+

This object represents the data to be requested.

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

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

+ +

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

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

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

+

UriPassportScopeElementOneOfSeveral

+

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

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

UriPassportScopeElementOne

+

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

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

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

+

Setting up Telegram Passport

+

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

+

Fetching the passport form

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

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

+

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

+

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

+

Submitting the passport form

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

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

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

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

+

Handling invalid forms

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

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

+

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

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

Pattern matching

+ +

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

+

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

+

Same with email verification codes.

+

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

+

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

+

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

+

Example implementation: telegram for android.

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

Payments API

+ +
+ +

You can accept payments from Telegram users via Telegram Bots.

+
+

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

+
+

Introducing Payments

+

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

+

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

+
+

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

+
+

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

+

Then, we work with payments as follows.

+

1. Create Invoice

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

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

+

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

+

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

+

2. Order information

+

2.1 Invoice message

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

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

+

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

+

2.2 Getting invoice info about the product

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

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

+

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

+

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

+

2.3 Verifying information

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

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

+

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

+

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

+

If any errors are found in the submmitted data, a service notification will be sent to the user, with a description of the error from the bot.

+

2.3.1 Autofill

+
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
+
+---functions---
+
+payments.getSavedInfo#227d824b = payments.SavedInfo;
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
+

The requested fields can be autofilled with the info provided in the saved_info field of the payment form, or with the info fetched manually using payments.getSavedInfo.

+

Saved order information can also be cleared using payments.clearSavedInfo.

+

2.4 Select delivery option

+
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
+
+shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;
+
+updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
+
+---functions---
+
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
+

If a shipping address was requested and the bot included the parameter flexible, when the user validates order information the Telegram API will send an updateBotShippingQuery to the bot. +The bot must respond using messages.setBotShippingResults either with a list of possible delivery options and the relevant delivery prices, or with an error (for example, if delivery to the specified address is not possible).

+

The returned shipping options or the shipping error will be returned to the user while validating order information.

+

3. Payment

+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
+
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+

3.1 Web payment

+
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+

Typically, payment takes place by opening the url in the specified payment form, which leads to a payment form on the website of the payment gateway. +Once the user finishes entering their payment credentials, a payment_form_submit web event is generated by the payment gateway, containing data and title JSON fields.

+

The title is used by the client app to represent the payment credentials (typically a censored version of credit card information). +The data is used to generate an inputPaymentCredentials constructor. +Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.

+

Telegram does not have access to your card information. Credit card details will be handled only by the payment system.

+

3.2 Native payment

+
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+

Most telegram apps support working natively with the native APIs of some payment providers, without opening the website of the payment and receiving a JS event.

+

This is done using the JSON native_params parameters field of the payments.paymentForm constructor, which contains an object, which can contain one or more of the following fields:

+
    +
  • publishable_key: Stripe API publishable key
  • +
  • apple_pay_merchant_id: Apple Pay merchant ID
  • +
  • android_pay_public_key: Android Pay public key
  • +
  • android_pay_bgcolor: Android Pay form background color
  • +
  • android_pay_inverse: Whether to use the dark theme in the Android Pay form
  • +
  • need_country: True, if the user country must be provided,
  • +
  • need_zip: True, if the user ZIP/postal code must be provided,
  • +
  • need_cardholder_name: True, if the cardholder name must be provided
  • +
+

The payment gateway to use is decided based on the value of the native_provider field.

+
3.2.1 Stripe
+
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+

If the native_provider field is set and equal to stripe, the client can make use of the native Stripe token APIs with the publishable_key from the native_params to add a payment method to Stripe, and then use the token type and id to generate a JSON object:

+
{"type":"token.type", "id":"token.id"}"
+

The generated JSON object can then be passed to the data field of the inputPaymentCredentials. +Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.

+

Telegram does not have access to your card information. Credit card details will be handled only by the payment system.

+

Example implementation: Telegram for Android.

+

3.3 Apple pay

+
inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+

On iOS devices, Apple Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsApplePay constructor.

+

Example implementation: Telegram for iOS.

+

3.4 Android pay

+
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
+

On Android devices, Google Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsGooglePay constructor.

+

Example implementation: Telegram for Android.

+

3.5 Using saved payment credentials

+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+
+paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+
+account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+
+---functions---
+
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;
+

To reuse saved payment methods, the saved_credentials field of the payment form is used. +The title of the paymentSavedCredentialsCard can be used to preview a censored version of credit card info. +The id field is provided by the payment provider directly to the Telegram servers when saving the payment method, and identifies the payment method. +Full credit card info is not saved on Telegram Servers, and cannot be fetched by the user.

+

In order to use the saved payment method, 2FA must be enabled: the user must verify their identity by entering their 2FA password, which is then used as described in the SRP docs to generate SRP parameters which must be passed to account.getTmpPassword.

+

The generated temporary password can then be used to make payments using the saved credentials using the inputPaymentCredentialsSaved constructor.

+ +

Example implementation: Telegram for Android.

+

4. Pre-Checkout

+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
+
+payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
+payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
+
+---functions---
+
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
+

After verifying order information, the final step for the client is to call payments.sendPaymentForm, with the following parameters:

+
    +
  • The msg_id is set to the ID of the invoice message
  • +
  • requested_info_id is set to the id of the verified order information, if it was requested
  • +
  • shipping_option_id is set to the selected delivery option, if shipping was requested.
  • +
  • credentials are the payment credentials generated by the payment provider, required to complete the order.
  • +
+

Payment method info can also be saved to the Telegram Servers and reused, by setting the save flag of inputPaymentCredentials when sending the form. +This is only possible on accounts with 2FA enabled.

+

The bot then replies to the received precheckout query, finally the user proceeds to checkout.

+

Please note that if the result of the method is a payments.paymentVerificationNeeded, before proceeding to checkout the payment provider requires the user to verify his identity by opening the provided url and following instructions. +Once the user finishes working with the webpage, the client can proceed to checkout.

+

Eventual errors are returned in the form of RPC errors, with the description of the error by the bot contained in service updates.

+

4.1 Receiving pre-checkout query

+
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
+
+updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
+
+---functions---
+
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
+

The user enters their payment information as described above and presses the final pay button. +At this moment the Telegram API sends an updateBotPrecheckoutQuery constructor that contains all the available information about the order to the bot. +The bot must reply using messages.setBotPrecheckoutResults within 10 seconds after receiving this update or the transaction is canceled.

+

The bot may return an error if it can‘t process the order for any reason. We highly recommend specifying a reason for failure to complete the order in human readable form (e.g. "Sorry, we’re all out of rubber ducks! Would you be interested in a steel bear instead?"). Telegram will display this reason to the user.

+

5. Checkout

+
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+
+keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
+
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+
+payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+
+---functions---
+
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;
+

In case the bot confirms the order, Telegram requests the payment provider to complete the transaction. If the payment information was entered correctly and the payment goes through, the Telegram API will modify the invoice message and send a service message as described below. Once your bot receives this message, it should proceed with delivering the goods or services purchased by the user.

+

If all is OK, the user receives a payments.paymentResult in reply to the payments.sendPaymentForm query, containing info about the updated invoice message in the form of an updateEditMessage.

+

The invoice message will be updated as follows: the attached messageMediaInvoice will now have a receipt_msg_id field. +Clients should treat invoice messages with a receipt_msg_id field as receipt messages, locally modifying the label of the keyboardButtonBuy button to a localized version of the word Receipt. +From this point, clicking on the Receipt button should trigger a call to payments.getPaymentReceipt, providing the receipt_msg_id to the msg_id field, which will return info about the transaction.

+

The payment will also generate one service message of type messageActionPaymentSent or messageActionPaymentSentMe, replying to the invoice. +For bots, the service message will be of type messageActionPaymentSentMe, for users it will be a messageActionPaymentSent.

+
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
+messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/pfs.html b/data/core.telegram.org/api/pfs.html new file mode 100644 index 0000000000..7f03a3eeee --- /dev/null +++ b/data/core.telegram.org/api/pfs.html @@ -0,0 +1,138 @@ + + + + + Perfect Forward Secrecy + + + + + + + + + + + + + +
+ +
+
+
+ +

Perfect Forward Secrecy

+ +
Related articles
+

+
+

This article is about Perfect Forward Secrecy in cloud chats, see also PFS in Secret Chats.

+
+
+

Telegram supports Perfect Forward Secrecy (PFS).

+

To make this possible, the client generates a permanent authorization key using p_q_inner_data and a temporary key using p_q_inner_data_temp. (See Creating an Authorization Key for more info.) These 2 operations may be done in parallel and even using the same connection. The client must save an expires_at unix timestamp expires_at = time + expires_in.

+

Important: in order to achieve PFS, the client must never use the permanent auth_key_id directly. Every message that is sent to MTProto, must be encrypted by a temp_auth_key_id, that was bound to the perm_auth_key_id.

+

An unbound temp_auth_key_id may only be used with the following methods:

+ +

In order to bind a temporary authorization key to the permanent key the client creates a special binding message and executes the auth.bindTempAuthKey method using temp_auth_key. Once auth.bindTempAuthKey has been executed successfully, the client may signUp / signIn using other auth.* methods and continue using the API as usual; the client must also rewrite client info using initConnection after each binding. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

+

Once the temporary key expires, the client needs to generate a new temporary key using p_q_inner_data_temp. Then it needs to re-bind that new temporary key to the initial permanent key. A new key can also be generated in advance, so that the client has a new key ready by the time the old one has expired.

+

For additional security, the client can store the temporary authorization key in RAM only and never save it in persistent storage.

+

A temporary authorization key may expire at any moment before expires_at, since such keys are also stored only in the RAM on the server-side. Be prepared to handle resulting MTProto errors correctly (non-existent auth_key_id results in a 404 error).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/pin.html b/data/core.telegram.org/api/pin.html new file mode 100644 index 0000000000..b5528f5a39 --- /dev/null +++ b/data/core.telegram.org/api/pin.html @@ -0,0 +1,149 @@ + + + + + Pinned messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Pinned messages

+ +
+ +

Telegram allows pinning multiple messages on top of a specific chat.

+
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
+updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+
+---functions---
+
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
+
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
+

The messages.updatePinnedMessage method can be used to pin or unpin a specific message in an arbitrary chat.
+The unpin flags specifies whether to unpin or pin the message, and pm_oneside specifies whether the message should only be pinned on the local side of a one-to-one chat.

+

messages.unpinAllMessages can be used to unpin all messages in a chat.

+

When (un)pinning messages, a updatePinnedMessages or updatePinnedChannelMessages update will be emitted, containing IDs of pinned or unpinned messages.

+

Pinned messages will also have the will also have the pinned flag of message set.

+

Getting pinned messages

+
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
+chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
+channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
+
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;
+
+---functions---
+
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+

The pinned_msg_id of userFull, chatFull, channelFull contains the ID of only the latest pinned message.
+To obtain a full list, use messages.search with inputMessagesFilterPinned filter.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/poll.html b/data/core.telegram.org/api/poll.html new file mode 100644 index 0000000000..e12f1e5996 --- /dev/null +++ b/data/core.telegram.org/api/poll.html @@ -0,0 +1,199 @@ + + + + + Poll + + + + + + + + + + + + + +
+ +
+
+
+ +

Poll

+ +
+ +

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

+

Sending a poll

+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+
+---functions---
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

To send a poll in a chat, call messages.sendMedia, providing an inputMediaPoll:

+
    +
  • +

    poll is the actual poll constructor, containing:

    +
      +
    • question - The poll title, aka the poll's title
    • +
    • answers - A vector of possible answers (2-10), each with a visible title text , and a unique option identifier (1-100 bytes)
    • +
    • closed - Whether the poll is closed
    • +
    • public_voters - Whether cast votes are publicly visible to all users (non-anonymous poll)
    • +
    • multiple_choice - Whether multiple options can be chosen as answer
    • +
    • quiz - Whether this is a quiz with correct answer IDs specified in inputMediaPoll.correct_answers
    • +
    • close_period - Amount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date .
    • +
    • close_date - Point in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period .
      +These last two parameters are exactly the same, except that one uses absolute, the other relative unixtime.
    • +
    +
  • +
  • +

    correct_answers - For quizes, option ID of the only correct answer

    +
  • +
  • +

    solution - Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds

    +
  • +
  • +

    solution_entities - Styled text message entities for the solution explanation

    +
  • +
+

In order to prematurely close the poll, preventing further votes, use messages.editMessage, setting the poll.closed flag to true.

+

Voting in polls

+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+
+---functions---
+
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
+

When receiving a message with a messageMediaPoll, users can vote in it using messages.sendVote, specifying the chosen option identifiers.

+

The method will return an updateMessagePoll, containing an updated pollResults constructor, with the chosen flag set on the options we chose, and the correct flag set on the correct answers.

+

Getting poll votes

+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+
+---functions---
+
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
+

Regularly, if new users have voted in polls available to the user, they will receive an updateMessagePoll, with updated pollResults.

+

The same constructor can also be fetched manually using messages.getPollResults.

+

Getting poll voters in non-anonymous polls

+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
+
+messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList; 
+
+updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
+
+---functions---
+
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList; 
+

messages.getPollVotes can be used to get poll results for non-anonymous polls, to see how each user voted for a poll option.
+Bots will also receive an updateMessagePollVote every time a user their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/push-updates.html b/data/core.telegram.org/api/push-updates.html new file mode 100644 index 0000000000..0deaeb8156 --- /dev/null +++ b/data/core.telegram.org/api/push-updates.html @@ -0,0 +1,1009 @@ + + + + + Handling PUSH-notifications + + + + + + + + + + + + + +
+ +
+
+
+ +

Handling PUSH-notifications

+ +
+ +

Configuring the application

+

To be able to send APNS notifications to Apple servers or GCM notifications to Google servers, application certificates (APNS) or an application key (GCM) must be specified in the application settings.

+

Subscribing to notifications

+

To subscribe to notifications, the client must invoke the account.registerDevice query, passing in token_type and token as parameters that identify the current device. It is useful to repeat this query at least once every 24 hours or when restarting the application. Use account.unregisterDevice to unsubscribe.

+

The following modes are supported:

+
    +
  • 1 - APNS (device token for apple push)
  • +
  • 2 - FCM (firebase token for google firebase)
  • +
  • 3 - MPNS (channel URI for microsoft push)
  • +
  • 4 - Deprecated: Simple push (endpoint for firefox's simple push API)
  • +
  • 5 - Ubuntu phone (token for ubuntu push)
  • +
  • 6 - Blackberry (token for blackberry push)
  • +
  • 7 - MTProto separate session
  • +
  • 8 - WNS (windows push)
  • +
  • 9 - APNS VoIP (token for apple push VoIP)
  • +
  • 10 - Web push (web push, see below)
  • +
  • 11 - MPNS VoIP (token for microsoft push VoIP)
  • +
  • 12 - Tizen (token for tizen push)
  • +
+

For 10 web push, the token must be a JSON-encoded object with the following keys:

+
    +
  • endpoint: Absolute URL exposed by the push service where the application server can send push messages
  • +
  • keys: P-256 elliptic curve Diffie-Hellman parameters in the following object
      +
    • p256dh: Base64url-encoded P-256 elliptic curve Diffie-Hellman public key
    • +
    • auth: Base64url-encoded authentication secret
    • +
    +
  • +
+

Notification encryption

+

For FCM and APNS VoIP, an optional encryption key used to encrypt push notifications can be passed to account.registerDevice (secret). This key (auth_key) is used to encrypt the payloads using MTProto v2.

+

The FCM payload will be a JSON payload, containing a p field with the base64-encoded encrypted MTProto payload. After decryption, the result will be a JSON object, prefixed by a 32-bit little-endian integer with the length of the JSON payload. As usual, make sure to follow all security checks as described in the MTProto docs.

+

Example implementation.

+

As mentioned above, payloads can also be encrypted using P-256 Elliptic Curve Diffie-Hellman when using web push.

+

Notification structure

+

An (optionally encrypted) notification is provided as a JSON object in the following format:

+
{
+  "data": {
+    "loc_key": "CHAT_MESSAGE_CONTACT",
+    "loc_args": ["John Doe", "My magical group", "Contact Exchange"],
+    "user_id": 14124122,
+    "custom": {
+      "chat_id": 241233,
+      "msg_id": 123
+    },
+    "sound": "sound1.mp3",
+  }
+}
+

Each notification has several parameters that describe it.

+

Notification type

+

data.loc_key - A string literal in the form /[A-Z_0-9]+/, which summarizes the notification. For example, CHAT_MESSAGE_TEXT.

+

Notification text arguments

+

data.loc_args - A list or arguments which, when inserted into a template, produce a readable notification.

+

Custom parameters

+

data.custom - Parameters which are be passed into the application when a notification is opened.

+

Sound

+

data.sound - The name of an audio file to be played.

+

User id

+

data.user_id - ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

+

Processing notifications

+

In principle, data.loc_key, data.custom, and an Internet connection are sufficient to generate a notification. Obviously, if possible, when generating a visual notification you need not use all of the transmitted data and may rely on the information already stored on the client. But if a user or a chat is not cached locally, the values passed in loc_args may also be used. data.user_id is the ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

+

Service notifications

+

The following notifications can be used to update app settings.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeExtra custom argumentsDescription
DC_UPDATEdc - number of the data-center
addr - server address with port number in the format 111.112.113.114:443
In case the client gets this notification, it is necessary to add the received server address to the list of possible addresses. In case the address of the first DC was passed (dc=1), it is recommended to call it immediately using help.getConfig to update dc-configuration.
MESSAGE_DELETEDchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
messages: Comma-separated IDs of messages that were deleted
Messages were deleted, remove multiple notifications for this chat
READ_HISTORYchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
max_id: Maximum ID of read messages
Message history was read, remove multiple notifications for this chat
GEO_LIVE_PENDING Any of the live locations currently being shared should be updated
SESSION_REVOKE Logout and remove DB for specified session by data.user_id, only apply if coming from an MTProto-encrypted payload
MESSAGE_MUTED Sent rarely, every 10th message in chats or once per 15 sec in PM, to update badge or download messages
+

Possible Notifications

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeTemplate exampleArgumentsExtra custom arguments
AUTH_REGIONNew login from unrecognized device {1}, location: {2}1. Device name
2. Location
 
AUTH_UNKNOWNNew login from unrecognized device {1}1. Device name 
CHANNEL_MESSAGES{1} posted an album1. Message authorattachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_AUDIO{1} posted a voice message1. Message authorattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_CONTACT{1} posted a contact {2}1. Message author
2. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_DOC{1} posted a file1. Message authorattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_DOCS{1} posted {2} files1. Channel name
2. Number of documents that were posted
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_FWDS{1} posted {2} forwarded messages1. Message author
2. Number of forwarded messages
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_GAME{1} invited you to play {2}1. Message author
2. Game name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GAME_SCORE{1} scored {3} in game {2}1. User
2. Game name
3. Score
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GEO{1} posted a location1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GEOLIVE{1} posted a live location1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GIF{1} posted a GIF1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_NOTEXT{1} posted a message1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_PHOTO{1} posted a photo1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_PHOTOS{1} posted {2} photos1. Channel name
2. Number of photos that was sent
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_PLAYLIST{1} posted {2} music files1. Channel name
2. Number of audio files that were posted
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_POLL{1} posted a poll {2}1. Channel name
2. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_QUIZ{1} posted a quiz {2}1. Channel name
2. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_ROUND{1} posted a video message1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_STICKER{1} posted a {2} sticker1. Channel name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_TEXT{1}: {2}1. Channel name
2. Message body
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_VIDEO{1} posted a video1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_VIDEOS{1} posted {2} videos1. Channel name
2. Number of videos that were posted
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_ADD_MEMBER{1} invited {3} to the group {2}1. Message author
2. Chat name
3. New participant name
chat_id: chat identifier
CHAT_ADD_YOU{1} invited you to the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_CREATED{1} invited you to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_DELETE_MEMBER{1} removed {3} from the group {2}1. Message author
2. Chat name
3. Dropped participant name
chat_id: chat identifier
CHAT_DELETE_YOU{1} removed you from the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_JOINED{1} joined the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_LEFT{1} left the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_MESSAGES{1} sent an album to the group {2}1. User name
2. Group name
chat_from_id: Message author identifier
chat_id: chat identifier
mention: Whether the user was mentioned in the message
CHAT_MESSAGE_AUDIO{1} sent a voice message to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_CONTACT{1} shared a contact {3} in the group {2}1. User name
2. Group name
3. Contact name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_DOC{1} sent a file to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_DOCS{1} sent {3} files to the group {2}1. User name
2. Group name
3. Number of documents that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_FWDS{1} forwarded {3} messages to the group {2}1. User name
2. Group name
3. Number of messages that were forwarded
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_GAME{1} invited the group {2} to play {3}1. User name
2. Group name
3. Game name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GAME_SCORE{1} scored {4} in game {3} in the group {2}1. User name
2. Group name
3. Game name
4. Score
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GEO{1} sent a location to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GEOLIVE{1} shared a live location with the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GIF{1} sent a GIF to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_INVOICE{1} sent an invoice to the group {2} for {3}1. User name
2. Group name
3. Product name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_NOTEXT{1} sent a message to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_PHOTO{1} sent a photo to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_PHOTOS{1} sent {3} photos to the group {2}1. User name
2. Group name
3. Number of photos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_PLAYLIST{1} sent {3} music files to the group {2}1. User name
2. Group name
3. Number of audio files that were sent
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_POLL{1} sent a poll {3} to the group {2}1. User name
2. Group name
3. Poll name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_QUIZ{1} sent a quiz {3} to the group {2}1. User name
2. Group name
3. Quiz name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_ROUND{1} sent a video message to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_STICKER{1} sent a {3} sticker to the group {2}1. User name
2. Group name
3. Sticker emoji
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_TEXT{1} @ {2}: {3}1. Message author
2. Chat name
3. Message body
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_VIDEO{1} sent a video to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_VIDEOS{1} sent {3} videos to the group {2}1. User name
2. Group name
3. Number of videos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_PHOTO_EDITED{1} changed the group photo for {2}1. Message author
2. Chat name
chat_from_id: Message author identifier
chat_id: chat identifier
msg_id: ID of the message
CHAT_RETURNED{1} returned to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_TITLE_EDITED{1} renamed the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_VOICECHAT_END{1} ended a voice chat in the group {2}1. User name
2. Chat name
 
CHAT_VOICECHAT_INVITE{1} invited {3} to a voice chat in the group {2}1. User name
2. Chat name
3. Invited users
 
CHAT_VOICECHAT_INVITE_YOU{1} invited you to a voice chat in the group {2}1. User name
2. Chat name
 
CHAT_VOICECHAT_START{1} started a voice chat in the group {2}1. User name
2. Chat name
 
CONTACT_JOINED{1} joined Telegram!1. Contact namecontact_id: contact identifier
ENCRYPTED_MESSAGEYou have a new message encryption_id: secret chat identifier
random_id: message identifier
ENCRYPTION_ACCEPTYou have a new message encryption_id: secret chat identifier
ENCRYPTION_REQUESTYou have a new message encryption_id: secret chat identifier
LOCKED_MESSAGEYou have a new message  
MESSAGES{1} sent you an album1. User namefrom_id: author identifier
MESSAGE_ANNOUNCEMENT{1}1. Announcementannouncement: Announcement: roughly equivalent to a message received from the service notifications (Telegram Notifications, id 777000) user, but must be delivered via push notifications, without contacting the API.
MESSAGE_AUDIO{1} sent you a voice message1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_CONTACT{1} shared a contact {2} with you1. User name
2. Contact name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_DOC{1} sent you a file1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_DOCS{1} sent you {2} files1. User name
2. Number of documents that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_FWDS{1} forwarded you {2} messages1. User name
2. Number of messages that were forwarded
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_GAME{1} invited you to play {2}1. User name
2. Game name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GAME_SCORE{1} scored {3} in game {2}1. User name
2. Game name
3. Score
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GEO{1} sent you a location1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GEOLIVE{1} sent you a live location1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GIF{1} sent you a GIF1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_INVOICE{1} sent you an invoice for {2}1. User name
2. Product
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_NOTEXT{1} sent you a message1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PHOTO{1} sent you a photo1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PHOTOS{1} sent you {2} photos1. User name
2. Number of photos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_PHOTO_SECRET{1} sent you a self-destructing photo1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PLAYLIST{1} sent you {2} music files1. User name
2. Number of audio files that were sent
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_POLL{1} sent you a poll {2}1. User name
2. Poll name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_QUIZ{1} sent you a quiz {2}1. User name
2. Quiz name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_ROUND{1} sent you a video message1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_SCREENSHOT{1} took a screenshot1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_STICKER{1} sent you a {2} sticker1. User name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_TEXT{1}: {2}1. Message author
2. Message body
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_VIDEO{1} sent you a video1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_VIDEOS{1} sent you {2} videos1. User name
2. Number of videos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_VIDEO_SECRET{1} sent you a self-destructing video1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
PHONE_CALL_MISSEDYou missed a call from {1}1. User name 
PHONE_CALL_REQUEST{1} is calling you!1. User namecall_ah: Call access hash
call_id: Call ID
PINNED_AUDIO{1} pinned a voice message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_AUDIO{1} pinned a voice message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_CONTACT{1} pinned a contact {2}1. User name
2. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_CONTACT{1} pinned a contact {3} in the group {2}1. User name
2. Group name
3. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_DOC{1} pinned a file1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_DOC{1} pinned a file in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME{1} pinned a game1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME{1} pinned a game in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME_SCORE{1} pinned a game score1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME_SCORE{1} pinned a game score in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEO{1} pinned a map1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEO{1} pinned a map in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEOLIVE{1} pinned a live location1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEOLIVE{1} pinned a live location in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GIF{1} pinned a GIF1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GIF{1} pinned a GIF in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_INVOICE{1} pinned an invoice1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_INVOICE{1} pinned an invoice in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_NOTEXT{1} pinned a message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_NOTEXT{1} pinned a message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_PHOTO{1} pinned a photo1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_PHOTO{1} pinned a photo in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_POLL{1} pinned a poll {2}1. User name
2. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_POLL{1} pinned a poll {3} in the group {2}1. User name
2. Group name
3. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_QUIZ{1} pinned a quiz {2}1. User name
2. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_QUIZ{1} pinned a quiz {3} in the group {2}1. User name
2. Group name
3. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_ROUND{1} pinned a video message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_ROUND{1} pinned a video message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_STICKER{1} pinned a {2} sticker1. User name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_STICKER{1} pinned a {3} sticker in the group {2}1. User name
2. Group name
3. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_TEXT{1} pinned "{2}"1. User name
2. Message body
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_TEXT{1} pinned "{3}" in the group {2}1. User name
2. Group name
3. Message body
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_VIDEO{1} pinned a video1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_VIDEO{1} pinned a video in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/qr-login.html b/data/core.telegram.org/api/qr-login.html new file mode 100644 index 0000000000..7995ef9f72 --- /dev/null +++ b/data/core.telegram.org/api/qr-login.html @@ -0,0 +1,154 @@ + + + + + Login via QR code + + + + + + + + + + + + + +
+ +
+
+
+ +

Login via QR code

+ +
+ +

QR code login flow.

+

Related TL schema:

+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+
+updateLoginToken#564fe691 = Update;
+
+authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+
+---functions---
+
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
+

Exporting a login token

+

First of all, auth.exportLoginToken must be called by the app that wants to log in to an existing Telegram account.
+The method will return an auth.loginToken constructor, containing a binary login token and an expiry date (usually 30 seconds).

+

The login token must be encoded using base64url, embedded in a tg://login?token=base64encodedtoken URL and shown in the form of a QR code to the user.
+After the expiration of the current QR code, the auth.exportLoginToken method must be recalled and a new QR code must be generated automatically.

+

Accepting a login token

+

In order to log in, the QR code must be scanned and accepted by an already logged-in Telegram app using auth.acceptLoginToken.
+The token must be extracted from the tg://login URI and base64url-decoded before using it in the method.

+

Possible errors returned by the method are:

+
    +
  • 400 - AUTH_TOKEN_INVALID, an invalid authorization token was provided
  • +
  • 400 - AUTH_TOKEN_EXPIRED, the provided authorization token has expired and the updated QR-code must be re-scanned
  • +
  • 400 - AUTH_TOKEN_ALREADY_ACCEPTED, the authorization token was already used
  • +
+

The method will return an authorization object, containing info about the app and session that we just authorized.

+

Confirming (importing) the login token

+

After the logged-in app calls auth.acceptLoginToken and accepts the login token, the app that is trying to login will receive an updateLoginToken update, which should trigger a second call to the auth.exportLoginToken method.

+

This second call should then return an auth.loginTokenSuccess constructor, indicating successful login, essentially allowing further authorized interaction with the API.

+

If, however, there is a DC mismatch between the two apps, auth.loginTokenMigrateTo is returned instead, to which the app that is trying to login should respond by calling auth.importLoginToken with the specified token, to the specified DC.

+

This call should then finally return a auth.loginTokenSuccess constructor.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/recent-actions.html b/data/core.telegram.org/api/recent-actions.html new file mode 100644 index 0000000000..d36347c2d5 --- /dev/null +++ b/data/core.telegram.org/api/recent-actions.html @@ -0,0 +1,154 @@ + + + + + Admin log + + + + + + + + + + + + + +
+ +
+
+
+ +

Admin log

+ +
+ +

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

+
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
+channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
+channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
+
+channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;
+
+channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+
+channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true = ChannelAdminLogEventsFilter;
+
+---functions---
+
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;
+

channels.getAdminLog can be used to list recent admin activity.
+A channelAdminLogEventsFilter can be used to filter out actions of a certain type, and the admins field can be used to show only actions by certain admins.
+q can also be used to filter only logs matching a query string.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/rights.html b/data/core.telegram.org/api/rights.html new file mode 100644 index 0000000000..a581b8cf79 --- /dev/null +++ b/data/core.telegram.org/api/rights.html @@ -0,0 +1,133 @@ + + + + + Admin, banned, default rights + + + + + + + + + + + + + +
+ +
+
+
+ +

Admin, banned, default rights

+ +
+ +

Channels and supergroups allow setting granular permissions both for admins and specific users. +Channels, supergroups and legacy groups also allow setting global granular permissions for users.

+

They can be modified as follows:

+

Admin rights

+

channels.editAdmin can be used to modify the admin rights of a user in a channel or supergroup. +Legacy groups do not allow setting granular admin permissions, messages.editChatAdmin has to be used, instead.

+

Permissions are defined by the chatAdminRights constructor, some admin rights can only be used for channels, others both for channels and supergroups (see the constructor page).

+

Banned rights

+

channels.editBanned can be used to modify the rights of a user in a channel or supergroup, to ban/kick a user from the group, or restrict the user from doing certain things. +Legacy groups do not allow setting granular user permissions for single users, single users can only be removed from groups using messages.deleteChatUser: however, setting global granular permissions with legacy groups is supported.

+

Permissions are defined by the chatBannedRights constructor, for more info see the constructor page.

+

Default rights

+

messages.editChatDefaultBannedRights can be used to modify the rights of all users in a channel, supergroup or legacy group, to restrict them from doing certain things.

+

Permissions are defined by the chatBannedRights constructor: all flags can be used except for view_messages, for more info see the constructor page.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/scheduled-messages.html b/data/core.telegram.org/api/scheduled-messages.html new file mode 100644 index 0000000000..f1e0fdf7c1 --- /dev/null +++ b/data/core.telegram.org/api/scheduled-messages.html @@ -0,0 +1,156 @@ + + + + + Scheduled messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Scheduled messages

+ +

Telegram allows scheduling messages.

+
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updateNewScheduledMessage#39a51dfb message:Message = Update;
+updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
+
+---functions---
+
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

To schedule a message, simply provide a future unixtime in the schedule_date flag of messages.sendMessage or messages.sendMedia.

+

The specified message or media will be added to a server-side schedule queue for the current chat, and will be automatically sent at the specified time.
+The method call generates the following updates:

+
    +
  • Immediately, an updateNewScheduledMessage, with ID equal to the ID of the message in the schedule queue for the current chat (each PM, chat, supergroup and channel has its own schedule queue and ID sequence).
  • +
  • At schedule_date, an updateNewMessage or updateNewChannelMessage with the from_scheduled flag set, indicating to the sender that the specified scheduled message was sent.
  • +
  • At schedule_date, an updateDeleteScheduledMessages, indicating that the message was flushed from the schedule queue.
  • +
+

If the schedule_date is less than 10 seconds in the future, the message will be sent immediately, generating a normal updateNewMessage/updateNewChannelMessage .

+

Manipulating the schedule queue

+
updateNewScheduledMessage#39a51dfb message:Message = Update;
+updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
+
+---functions---
+
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
+messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
+messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
+
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
+

Clients can manually edit the schedule queue of a certain chat, providing the scheduled message ID obtained from updateNewScheduledMessage.

+ +

Modifying scheduled messages will generate an updateNewScheduledMessage with the same ID, and updated information.
+Deleting scheduled messages will generate an updateDeleteScheduledMessages.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/search.html b/data/core.telegram.org/api/search.html new file mode 100644 index 0000000000..7fb69193a6 --- /dev/null +++ b/data/core.telegram.org/api/search.html @@ -0,0 +1,179 @@ + + + + + Search + + + + + + + + + + + + + +
+ +
+
+
+ +

Search

+ +
+ +

Telegram allows applying detailed message filters while looking for messages in chats.

+

Search filters

+
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
+inputMessagesFilterPhotos#9609a51c = MessagesFilter;
+inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
+inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
+inputMessagesFilterDocument#9eddf188 = MessagesFilter;
+inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
+inputMessagesFilterGif#ffc86587 = MessagesFilter;
+inputMessagesFilterVoice#50f5c392 = MessagesFilter;
+inputMessagesFilterMusic#3751b49e = MessagesFilter;
+inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
+inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
+inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
+inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
+inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
+inputMessagesFilterGeo#e7026d0d = MessagesFilter;
+inputMessagesFilterContacts#e062db83 = MessagesFilter;
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;
+
+messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+
+---functions---
+
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
+

When using messages.search or messages.searchGlobal, a certain message filter may be applied.
+This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more. +Available filters:

+ +

The returned messages.Messages constructors contain parameters for pagination, the messages themselves and two offset_id_offset/count parameters that can be used to display a progress/total counter like photo 134 of 200.
+For example, when displaying the chat photo gallery, we could display a photo ${offset_id_offset} of ${count} indicator on top.

+

Search counters

+
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;
+
+---functions---
+
+messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;
+

Chat counters with filters can also be returned without fetching the actual messages, as seen in the schema above.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/sponsored-messages.html b/data/core.telegram.org/api/sponsored-messages.html new file mode 100644 index 0000000000..eac5fe507b --- /dev/null +++ b/data/core.telegram.org/api/sponsored-messages.html @@ -0,0 +1,146 @@ + + + + + Sponsored messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Sponsored messages

+ +

Related TL schema:

+
sponsoredMessage flags:# random_id:bytes from_id:Peer channel_post:flags.2?int start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;
+messages.sponsoredMessages messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+
+---functions---
+
+channels.getSponsoredMessages channel:InputChannel = messages.SponsoredMessages;
+channels.viewSponsoredMessage channel:InputChannel random_id:bytes = Bool;
+

Getting sponsored messages

+

Each time the user opens a channel, channels.getSponsoredMessages must be called to receive sponsored messages available for this channel. The result must be cached for 5 minutes.

+
+

More about sponsored messages on Telegram

+
+

Displaying sponsored messages

+

Sponsored messages must be displayed below all other posts in the channel, after the user scrolls futher down, past the last message. The promoted channel or bot specified in the from_id field must be displayed as the author of the message. The message should also contain one of the following buttons at the bottom:

+
    +
  • View Bot — if a bot is being promoted. Tapping the button must open the chat with the bot. If start_param is specified, the app must use the deep linking mechanism to open the bot.
  • +
  • View Channel — if a channel is being promoted. Tapping the button must open the channel.
  • +
  • View Post — if a channel is being promoted and channel_post is specified. Tapping the button must open the particular channel post.
  • +
+

Counting sponsored message views

+

Once the entire text is shown on the screen (excluding the button), channels.viewSponsoredMessage must be called with the random_id of this sponsored message.

+

Testing sponsored messages

+

For the channel https://t.me/SecretAdTestChannel the system will always return a sponsored message: promoting either a channel, a particular message in a channel, or a bot with a start parameter.

+
+

Sponsored messages in third-party apps

+

Telegram continues to grow worldwide, in part thanks to third-party apps using the Telegram API. To cover the increasing costs that come with this growth, Telegram added sponsored messages – a paid privacy-friendly way to promote bots and channels.

+

If their app allows its users to access content from Telegram channels, third-party developers using the Telegam API are required to support and properly display official sponsored messages in their apps by January 1, 2022. Unfortunately, Telegram cannot financially sustain third-party apps that do not display sponsored messages and they will have to be disconnected.

+

Telegram's API usage will continue to be free of charge for all developers. The rules regarding monetization in third-party apps remain the same: developers are allowed to monetize their coding efforts through advertising of their own or other legitimate means, provided that all the methods of monetization used in their apps are prominently mentioned in their app store descriptions.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/srp.html b/data/core.telegram.org/api/srp.html new file mode 100644 index 0000000000..7ea2c7a89e --- /dev/null +++ b/data/core.telegram.org/api/srp.html @@ -0,0 +1,307 @@ + + + + + Two-factor authentication + + + + + + + + + + + + + +
+ +
+
+
+ +

Two-factor authentication

+ +
+ +

Telegram uses the Secure Remote Password protocol version 6a to implement 2FA.

+

Example impementation: tdlib.

+

Checking the password with SRP

+

To login to an account protected by a 2FA password or to perform some other actions (like changing channel owner), you will need to verify the user's knowledge of the current 2FA account password.

+

To do this, first the client needs to obtain SRP parameters and the KDF algorithm to use to check the validity of the password via account.getPassword method. For now, only the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow algorithm is supported, so we'll only explain that.

+

Then, after the user provides a password, the client should generate an InputCheckPasswordSRP object using SRP and a specific KDF algorithm as shown below and pass it to appropriate method (e.g. auth.checkPassword in case of authorization).

+

This extension of the SRP protocol uses the password-based PBKDF2 with 100000 iterations using sha512 (PBKDF2HMACSHA512iter100000). +PBKDF2 is used to additionally rehash the x parameter, obtained using a method similar to the one described in RFC 2945 (H(s | H ( I | password | I) | s) instead of H(s | H ( I | ":" | password)) (see below).

+

Here, | denotes concatenation and + denotes the arithmetical operator +. +In all cases where concatenation of numbers passed to hashing functions is done, the numbers must be used in big-endian form, padded to 2048 bits; all maths is modulo p. +Instead of I, salt1 will be used (see SRP protocol). +Instead of s, salt2 will be used (see SRP protocol).

+

The main hashing function H is sha256:

+
    +
  • H(data) := sha256(data)
  • +
+

The salting hashing function SH is defined as follows:

+
    +
  • SH(data, salt) := H(salt | data | salt)
  • +
+

The primary password hashing function is defined as follows:

+
    +
  • PH1(password, salt1, salt2) := SH(SH(password, salt1), salt2)
  • +
+

The secondary password hashing function is defined as follows:

+
    +
  • PH2(password, salt1, salt2) := SH(pbkdf2(sha512, PH1(password, salt1, salt2), salt1, 100000), salt2)
  • +
+

Client-side, the following parameters are extracted from the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow object, contained in the account.password object.

+
    +
  • +

    g := algo.g

    +
  • +
  • +

    p := algo.p +The client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

    +

    If the client has an inadequate random number generator, it makes sense to use the secure_random of account.password as additional seed.

    +
  • +
  • +

    password := (user-provided password)

    +
  • +
  • +

    salt1 := algo.salt1

    +
  • +
  • +

    salt2 := algo.salt2

    +
  • +
  • +

    g_b := srp_B +srp_B and srp_id are extracted from the account.password object.

    +
  • +
+

The k parameter is generated, both on client and server:

+
    +
  • k := H(p | g)
  • +
+

The shared param u is generated: the client does this, and the server does the same with the g_a we will send him later (see below)

+
    +
  • u := H(g_a | g_b)
  • +
+

The final parameters are generated client-side only:

+
    +
  • x := PH2(password, salt1, salt2)
  • +
  • v := pow(g, x) mod p
  • +
+

The server already has v, from when we set the password.

+

A final shared param is generated, for commodity:

+
    +
  • k_v := (k * v) mod p
  • +
+

Finally, the key exchange process starts on both parties.

+

The client computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and generates:

+
    +
  • g_a := pow(g, a) mod p.
  • +
+

The server computes a 2048-bit number b using sufficient entropy and generates the g_b parameter that was sent to us (see above).

+
    +
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • +
+

Finally, the SRP session keys are generated:

+

Client side:

+
    +
  • t := (g_b - k_v) mod p (positive modulo, if the result is negative increment by p)
  • +
  • s_a := pow(t, a + u * x) mod p
  • +
  • k_a := H(s_a)
  • +
+

Server side:

+
    +
  • s_b := pow(g_a * (pow(v, u) mod p), b) mod p
  • +
  • k_b := H(s_b)
  • +
+

Since:

+
    +
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • +
  • t := (g_b - k_v) mod p
  • +
  • t := ((k_v + (pow(g, b) mod p)) - k_v) mod p
  • +
  • t := pow(g, b) mod p
  • +
  • s_a := pow(t, a + u * x) mod p
  • +
  • s_a := pow(pow(g, b) mod p, a + u * x) mod p
  • +
+

And:

+
    +
  • +

    g_a := pow(g, a) mod p

    +
  • +
  • +

    v := pow(g, x) mod p

    +
  • +
  • +

    s_b := pow(g_a * (pow(v, u) mod p), b) mod p

    +
  • +
  • +

    s_b := pow((pow(g, a) mod p) * (pow(pow(g, x) mod p, u) mod p), b) mod p

    +
  • +
  • +

    s_b := pow(pow(g, a + x * u) mod p, b) mod p

    +
  • +
  • +

    s_b := pow(pow(g, b) mod p, a + u * x) mod p

    +
  • +
  • +

    s_a := pow(pow(g, b) mod p, a + u * x) mod p

    +
  • +
+

This means:

+
    +
  • s_b === s_a
  • +
  • k_b === k_a
  • +
+

Finally, as per SRP:

+
    +
  • M1 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_a)
  • +
+

M1 is passed to inputCheckPasswordSRP, along with g_a (as A parameter) and the srp_id, extracted from the account.password object.

+

The server then computes:

+
    +
  • M2 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_b)
  • +
+

Since we said that:

+
    +
  • s_b === s_a
  • +
  • k_b === k_a
  • +
+

This means, if everything was done correctly,

+
    +
  • M1 === M2
  • +
+

If the password isn't correct, 400 PASSWORD_HASH_INVALID will be returned.

+

Setting a new 2FA password

+

To set a new 2FA password use the account.updatePasswordSettings method.
+If a password is already set, generate an InputCheckPasswordSRP object as per checking passwords with SRP, and insert it in the password field of the account.updatePasswordSettings method.
+To remove the current password, pass an empty new_password_hash in the account.PasswordInputSettings object.

+

To set a new password, use the SRP parameters and the KDF algorithm obtained using account.getPassword when generating the password field. +Then generate a new new_password_hash using the KDF algorithm specified in the new_settings, just append 32 sufficiently random bytes to the salt1, first. +Proceed as for checking passwords with SRP, just stop at the generation of the v parameter, and use it as new_password_hash:

+
    +
  • v := pow(g, x) mod p
  • +
+

As usual in big endian form, padded to 2048 bits.

+

Email verification

+

When setting up two-factor authorization, it is recommended to set up a recovery email, to allow recovery of the password through the user's email address, in case they forget it.

+

To set up a recovery email, it must first be verified. +This can be done directly when setting the new password using account.updatePasswordSettings by setting the email parameter and flag in the account.passwordInputSettings constructor. +If the email isn't verified, an EMAIL_UNCONFIRMED_X 400 error will be returned, where X is the length of the verification code that was just sent to the email. +Use account.confirmPasswordEmail to enter the received verification code and enable the recovery email. +Use account.resendPasswordEmail to resend the verification code. +Use account.cancelPasswordEmail to cancel the verification code.

+

To get the current recovery email, use account.getPasswordSettings.

+

Email recovery

+

In order to recover a forgotten 2FA password, an email must be sent to the previously specified address using the auth.requestPasswordRecovery method.
+Use auth.checkRecoveryPassword to make sure that the user provided a valid code.
+Then use auth.recoverPassword with the received code to delete the current 2FA password, to set a new one follow these instructions.

+

Password reset

+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+
+---functions---
+
+account.resetPassword#9308ce1b = account.ResetPasswordResult;
+account.declinePasswordReset#4c9409f6 = Bool;
+

If the user is already logged in and has forgotten their 2FA password, account.resetPassword can be used to initiate a password reset.
+On success, the call will initially return a account.resetPasswordRequestedWait constructor and start a 7-day server-side timer, during which the user can abort the reset process using a button sent by the Telegram service account or directly in-UI using account.declinePasswordReset.

+

When the time comes, account.resetPassword is invoked once more, returning a account.resetPasswordOk to indicate that the password was successfully reset.

+

If the user recently requested a password reset that was canceled, account.resetPasswordFailedWait will be returned by the initial account.resetPassword call, and they must wait until the specified date before requesting another reset.

+

Note that if the user already knows their 2FA password and simply wants to disable 2FA, the same process used to enable the password must also be used to disable it ».

+

Related pages

+

SRP design

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/terms.html b/data/core.telegram.org/api/terms.html new file mode 100644 index 0000000000..20985c7cf7 --- /dev/null +++ b/data/core.telegram.org/api/terms.html @@ -0,0 +1,133 @@ + + + + + Telegram API Terms of Service + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram API Terms of Service

+ +
+ +

We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge. In order to ensure consistency and security across the Telegram ecosystem, all third-party client apps must comply with the following Terms of Service.

+

1. Privacy & Security

+

1.1. Telegram is a privacy-oriented platform. All client apps must, therefore, guard their users' privacy with utmost care and comply with our Security Guidelines.
1.2. Developers are welcome to add new features or improve and extend existing Telegram features provided that these modifications do not violate these Terms of Service.
1.3. As a client developer, you must make sure that all the basic features of the main Telegram apps function correctly and in an expected way both in your app and when users of your app communicate with other Telegram users. It is forbidden to force users of other Telegram clients to download your app in order to view certain messages and content sent using your app.
1.4. It is forbidden to interfere with the basic functionality of Telegram. This includes but is not limited to: making actions on behalf of the user without the user's knowledge and consent, preventing self-destructing content from disappearing, preventing last seen and online statuses from being displayed correctly, tampering with the 'read' statuses of messages (e.g. implementing a 'ghost mode'), preventing typing statuses from being sent/displayed, etc.

+

2. Transparency

+

2.1. You must obtain your own api_id for your application.
2.2. We offer our API free of charge, but your users must be aware of the fact that your app uses the Telegram API and is part of the Telegram ecosystem. This fact must be featured prominently in the app's description in the app stores and in the in-app intro if your app has it.
2.3. To avoid confusion, the title of your app must not include the word “Telegram”. An exception can be made if the word “Telegram” is preceded with the word “Unofficial” in the title.
2.4. You must not use the official Telegram logo for your app. Both the Telegram brand and its logo are registered trademarks protected by law in almost every country.

+

3. Advertising & Monetization

+

3.1. Developers are allowed to monetize their coding efforts through advertising or other legitimate means.
3.2. If you decide to monetize your app, you must clearly mention all the methods of monetization that are used in your app in all its app store descriptions.
3.3. If your app allows accessing content from Telegram channels, you must include support for official sponsored messages in Telegram channels and may not interefere with this functionality.

+

4. Breach of terms

+

4.1. If your app violates these terms, we will notify the Telegram account responsible for the app about the breach of terms.
4.2. If you do not update the app to fix the highlighted issues within 10 days, we will have to discontinue your access to Telegram API and contact the app stores about the removal of your apps that are using the Telegram API in violation of these terms.

+

We reserve the right to expand these terms and guidelines as the need arises. We will inform client developers of such changes via an in-app notification to their accounts connected to the app in question.

+
+

Back to Creating Your Telegram Application »

+
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/threads.html b/data/core.telegram.org/api/threads.html new file mode 100644 index 0000000000..ff7a9930f8 --- /dev/null +++ b/data/core.telegram.org/api/threads.html @@ -0,0 +1,182 @@ + + + + + Threads + + + + + + + + + + + + + +
+ +
+
+
+ +

Threads

+ +
+ +

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Message threads

+

Schema:

+
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
+
+messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+---functions---
+
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+

Threads are usually automatically created when replying to any message in a group.
+For example, all replies to a message with ID 420 are associated to thread with ID 420, unique to this group; this thread ID is contained in the reply_to_top_id field of reply_to messageReplyHeader, along with an eventual reply_to_msg_id, for replies to messages within a thread.
+Replies to messages in a thread are part of the same thread, and do not spawn new threads.

+

When receiving a message from a group that is also the top of a thread (the message with ID 420), the replies optional field will contain a messageReplies constructor, containing the message ID and PTS of the latest reply in the thread, and the message ID of the latest read thread reply, along with the total number of replies in the thread.

+

Replies to a thread can also be manually fetched using messages.search, providing to top_msg_id the thread ID.

+

Channel comments

+
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
+

The same messageReplies constructor seen above will also be contained in channel posts, this time containing information about the comment section of a specific channel post.
+The comment section of a channel post is simply the message thread of the automatically forwarded channel message in the linked discussion supergroup; the ID of the linked discussion supergroup will be contained in the messageReplies.channel_id field.

+

For channel posts, the recent_repliers field will also contain information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.

+

@replies

+
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
+
+messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
+
+---functions---
+
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
+
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
+

Since a user can comment in channel posts without joining the actual discussion supergroup, there must be a way for them to receive notifications about replies in comment sections.
+For this reason, a special @replies username is provided. +Its ID for main and testing endpoints can be seen in the tdlib sources.

+

When someone replies to one of our messages in the comment section of a channel post, and the user is not subscribed to the discussion group, the client will receive two updates:

+
    +
  • An updateNewChannelMessage from the discussion group itself, structured just like any other update coming from a subscribed group, with:
      +
    • id set to the ID of the reply
    • +
    • from_id set to the peer that replied to us
    • +
    • peer_id set to the peer of the discussion group
    • +
    • reply_to.reply_to_msg_id set to the ID of our message
    • +
    • reply_to.reply_to_top_id set to the thread ID.
    • +
    +
  • +
  • An updateNewMessage
      +
    • id set to the common ID sequence for users
    • +
    • from_id set to the peer of @replies
    • +
    • peer_id set to our own peer
    • +
    • fwd_from.saved_from_msg_id set to the ID of the reply
    • +
    • fwd_from.from_id set to the the peer that replied to us
    • +
    • reply_to.reply_to_peer_id set to the peer of the discussion group
    • +
    • reply_to.reply_to_msg_id set to the ID of our message
    • +
    • reply_to.reply_to_top_id set to the thread ID
    • +
    +
  • +
+

Clients should display messages coming from @replies as a read-only supergroup, with each reply displayed as a separate message from the author of the reply, with a "View in chat" button like for channel comments.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/top-rating.html b/data/core.telegram.org/api/top-rating.html new file mode 100644 index 0000000000..ae7b246332 --- /dev/null +++ b/data/core.telegram.org/api/top-rating.html @@ -0,0 +1,145 @@ + + + + + Top peer rating + + + + + + + + + + + + + +
+ +
+
+
+ +

Top peer rating

+ +

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+

Schema:

+
topPeer#edcdc05b peer:Peer rating:double = TopPeer;
+
+topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
+topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
+topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
+topPeerCategoryGroups#bd17a14a = TopPeerCategory;
+topPeerCategoryChannels#161d9628 = TopPeerCategory;
+topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
+topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
+topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;
+
+topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;
+
+contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+
+---functions---
+
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;
+

The rate delta is computed by taking the time delta between the last time the user used a certain peer and the last time the rating for that peer was received and dividing it by the exponential decay from config.

+

Example: +Client-side, every time a user opens chat 123456789 the following operation must be done on the cached top peer info.

+
    +
  • dateOpened indicates when was the peer used
  • +
  • normalizeRate is an arbitrary time in the recent past. +When ratings are received from the server using contacts.getTopPeers and the schema described above, it is the time when they were received.
  • +
+
topPeer.rating += e^((dateOpened - normalizeRate) / config.rating_e_decay)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/updates.html b/data/core.telegram.org/api/updates.html new file mode 100644 index 0000000000..4a314b97ea --- /dev/null +++ b/data/core.telegram.org/api/updates.html @@ -0,0 +1,226 @@ + + + + + Working with Updates + + + + + + + + + + + + + +
+ +
+
+
+ +

Working with Updates

+ +
+ +

When a client is being actively used, events will occur that affect the current user and that they must learn about as soon as possible, e.g. when a new message is received. To eliminate the need for the client itself to periodically download these events, there is an update delivery mechanism in which the server sends the user notifications over one of its available connections with the client.

+

Subscribing to Updates

+

Update events are sent to an authorized user into the last active connection (except for connections needed for downloading / uploading files).

+

So to start receiving updates the client needs to init connection and call API method, e.g. to fetch current state.

+

Event sequences

+

All events are received from the socket as a sequence of TL-serialized Updates objects, which might be optionally gzip-compressed in the same way as responses to queries.

+

Each Updates object may contain single or multiple Update objects, representing different events happening.

+

In order to apply all updates in precise order and to guarantee that no update is missed or applied twice there is seq attribute in Updates constructors, and pts (with pts_count) or qts attributes in Update constructors. The client must use those attributes values in combination with locally stored state to correctly apply incoming updates.

+

When a gap in updates sequence occurs, it must be filled via calling one of the API methods. More below »

+

Updates sequence

+

As said earlier, each payload with updates has a TL-type Updates. It can be seen from the schema below that this type has several constructors.

+
updatesTooLong#e317af7e = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+

updatesTooLong indicates that there are too many events pending to be pushed to the client, so one needs to fetch them manually.

+

Events inside updateShort constructors, normally, have lower priority and are broadcast to a large number of users, i.e. one of the chat participants started entering text in a big conversation (updateChatUserTyping).

+

The updateShortMessage, updateShortSentMessage and updateShortChatMessage constructors are redundant but help significantly reduce the transmitted message size for 90% of the updates. They should be transformed to updateShort upon receiving.

+

Two remaining constructors updates and updatesCombined are part of the Updates sequence. Both of them have seq attribute, which indicates the remote Updates state after the generation of the Updates, and seq_start indicates the remote Updates state after the first of the Updates in the packet is generated. For updates, seq_start attribute is omitted, because it is assumed that it is always equal to seq.

+

Message-related event sequences

+

Each event related to a message box (message created, message edited, message deleted, etc) is identified by a unique autoincremented pts, or qts in case of secret chat updates, certain bot updates, etc.

+

Each message box can be considered as some server-side DB table that stores messages and events associated with them. +All boxes are completely independent, and each pts sequence is tied to just one box (see below).

+

Update object may contain info about multiple events (for example, updateDeleteMessages). +That's why all single updates might have pts_count parameter indicating the number of events contained in the received update (with some exceptions, in this case, the pts_count is considered to be 0).

+

Each channel and supergroup has its message box and its event sequence as a result; private chats and legacy groups of one user have another common event sequence. +Secret chats, certain bot events and other kinds of updates have yet another common secondary event sequence.

+

To recap, the client has to take care of the integrity of the following sequences to properly handle updates:

+
    +
  • Updates sequence (seq)
      +
    • Common message box sequence (pts)
    • +
    • Secondary event sequence (qts)
    • +
    • Channel message box sequence 1 (pts)
    • +
    • Channel message box sequence 2 (pts)
    • +
    • Channel message box sequence 3 (pts)
    • +
    • and so on...
    • +
    +
  • +
+

Fetching state

+

The common update state is represented by the updates.State constructor. +When the user logs in for the first time, call to updates.getState has to be made to store the latest update state (which will not be the absolute initial state, just the latest state at the current time). +The common update state can also be fetched from updates.differenceTooLong.

+

The channel update state is represented simply by the pts of the event sequence: when first logging in, the initial channel state can be obtained from the dialog constructor when fetching dialogs, from the full channel info, or it can be received as an updateChannelTooLong update.

+

The secondary update state is represented by the qts of the secret event sequence, it is contained in the updates.State of the common update state.

+

The Updates sequence state is represented by the date and seq of the Updates sequence, it is contained in the updates.State of the common update state.

+

Update handling

+

Update handling in Telegram clients consists of receiving events, making sure there were no gaps and no events were missed based on the locally stored state of the correspondent event sequence, and then updating the locally stored state based on the parameters received.

+

When the client receives payload with serialized updates, first of all, it needs to walk through all of the nested Update objects and check if they belong to any of message box sequences (have pts or qts parameters). Those updates need to be handled separately according to corresponding local state and new pts/qts values. Details below »

+

After message box updates are handled, if there are any other updates remaining the client needs to handle them with respect to seq. Details below »

+

pts: checking and applying

+

Here, local_pts will be the local state, pts will be the remote state, pts_count will be the number of events in the update.

+

If local_pts + pts_count === pts, the update can be applied. +If local_pts + pts_count > pts, the update was already applied, and must be ignored. +If local_pts + pts_count < pts, there's an update gap that must be filled.

+

For example, let's assume the client has the following local state for the channel 123456789:

+
local_pts = 131
+

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. +Since local_pts + pts_count === pts, the total number of events since the last stored state is, in fact, equal to pts_count: this means the update can be safely accepted and the remote pts applied:

+
local_pts = 132
+

Since:

+
    +
  • pts indicates the server state after the new channel message events are generated
  • +
  • pts_count indicates the number of events in the new channel update
  • +
  • The server state before the new channel message event was generated has to be: pts_before = pts - pts_count = 131, which is, in fact, equal to our local state.
  • +
+

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. +Since local_pts + pts_count > pts (133 > 132), the update is skipped because we've already handled this update (in fact, our current local_pts was set by this same update, and it was resent twice due to network issues or other issues).

+

Now let's assume an updateDeleteChannelMessages from channel 123456789 is received with pts = 140 and pts_count=5. +Since local_pts + pts_count < pts (137 < 140), this means that updates were missed, and the gap must be recovered.

+
Secret chats & bots
+

The whole process is very similar for secret chats and certain bot updates, but there is qts instead of pts, and events are never grouped, so it's assumed that qts_count is always equal to 1.

+

seq: checking and applying

+

On top level when handling received updates and updatesCombined there are three possible cases: +If local_seq + 1 === seq_start, the updates can be applied. +If local_seq + 1 > seq_start, the updates were already applied, and must be ignored. +If local_seq + 1 < seq_start, there's an updates gap that must be filled (updates.getDifference must be used as with common and secret event sequences).

+

If the updates were applied, local Updates state must be updated with seq and date from the constructor.

+

For all the other Updates type constructors there is no need to check seq or change a local state.

+

Recovering gaps

+

To do this, updates.getDifference (common/secret state) or updates.getChannelDifference (channel state) with the respective local states must be called. +These methods should also be called on startup, to fetch new updates (preferably with some flags to reduce server load, see the method's docs). +Manually obtaining updates is also required in the following situations:

+
    +
  • Loss of sync: a gap was found in seq / pts / qts (as described above). It may be useful to wait up to 0.5 seconds in this situation and abort the sync in case a new update arrives, that fills the gap.
  • +
  • Session loss on the server: the client receives a new session created notification. This can be caused by garbage collection on the MTProto server or a server reboot.
  • +
  • Incorrect update: the client cannot deserialize the received data.
  • +
  • Incomplete update: the client is missing data about a chat/user from one of the shortened constructors, such as updateShortChatMessage, etc.
  • +
  • Long period without updates: no updates for 15 minutes or longer.
  • +
  • The server requests the client to fetch the difference using updateChannelTooLong or updatesTooLong.
  • +
+

When calling updates.getDifference if the updates.differenceSlice constructor is returned in response, the full difference was too large to be received in one request. The intermediate status, intermediate_state, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

+

To fetch the updates difference of a channel, updates.getChannelDifference is used. +If the difference is too large to be received in one request, the final flag of the result is not set (see docs). +The intermediate status, represented by the pts, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

+

For perfomance reasons and for better user experience, client can set maximum gap size to be filled: pts_total_limit parameter of updates.getDifference and limit parameter for updates.getChannelDifference can be used.

+

If the gap is too large and there are too many updates to fetch, a *TooLong constructor will be returned. In this case, the client must re-fetch the state, re-start fetching updates from that state and follow the instructions that can be found here.

+

It is recommended to use limit 10-100 for channels and 1000-10000 otherwise.

+

Example implementations

+

Implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence.

+

Example implementations: tdlib, MadelineProto.

+

An interesting and easy way this can be implemented, instead of using various locks, is by running background loops, like in MadelineProto ».

+

PUSH Notifications about Updates

+

If a client does not have an active connection at the time of an event, PUSH Notifications will also be useful.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/url-authorization.html b/data/core.telegram.org/api/url-authorization.html new file mode 100644 index 0000000000..5e711e4cd3 --- /dev/null +++ b/data/core.telegram.org/api/url-authorization.html @@ -0,0 +1,160 @@ + + + + + Seamless Telegram Login + + + + + + + + + + + + + +
+ +
+
+
+ +

Seamless Telegram Login

+ +
+ +

Bots or Telegram websites may ask users to login to a certain website via Telegram when clicking on certain links or URL buttons in inline keyboards.

+

Bot URL authorization

+

When the user clicks on keyboardButtonUrlAuth, messages.requestUrlAuth should be called, providing the button_id of the button and the ID and peer of the container message. +The returned urlAuthResultRequest object will contain more details about the authorization request:

+
    +
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • +
  • The bot parameter will contain info about the bot which will be used for user authorization (example: DiscussBot).
  • +
  • The request_write_access will be set if the bot would like to send messages to the user.
  • +
+

The info should be shown in a prompt:

+
+ TITLE +
+

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). +The result will be a urlAuthResultAccepted with the final URL to open, which will include a query string with the requested info and a hash that must be verified upon receival by the service.

+

urlAuthResultDefault could also be returned, instead, in which case the url of the keyboardButtonUrlAuth must be opened, instead. +The same must be done if the user opens the link while refusing the authorization request.

+

Link URL authorization

+

Telegram supports automatic authorization on certain websites upon opening an HTTP URL in-app, upon clicking a link in a message or clicking on a keyboardButtonUrl.

+

Automatic authorization

+

Clients should automatically authenticate users when opening official Telegram websites, listed in the url_auth_domains key of the client configuration object ».

+

Upon clicking a link, the URL must be modified by appending the autologin_token from the client configuration object » to the query string, like so:

+

Original URL: https://somedomain.telegram.org/path?query=string#fragment=value
+Modified URL: https://somedomain.telegram.org/path?query=string&autologin_token=$autologin_token#fragment=value

+

Make sure that the used autologin_token is no more than 10000 seconds old, if it is older it must be refetched before use as described in the client configuration section ».

+

Manual authorization

+

Clients should show a confirmation prompt similar to the one used for bots, to authenticate users when opening certain Telegram websites, listed in the url_auth_domains key of the client configuration object ».

+

messages.requestUrlAuth should be called, providing only the original url. +The returned urlAuthResultRequest object will contain more details about the authorization request:

+
    +
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • +
  • The request_write_access will be set if the website would like to send messages to the user.
  • +
+

The info should be shown in a prompt.

+

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). +The result will be a urlAuthResultAccepted with the final URL to open.

+

urlAuthResultDefault could also be returned, instead, in which case the original URL must be opened, instead. +The same must be done if the user opens the link while refusing the authorization request.

+

Related articles

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/web-events.html b/data/core.telegram.org/api/web-events.html new file mode 100644 index 0000000000..fd612b4c95 --- /dev/null +++ b/data/core.telegram.org/api/web-events.html @@ -0,0 +1,177 @@ + + + + + Web events + + + + + + + + + + + + + +
+ +
+
+
+ +

Web events

+ +
+ +

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose APIs to allow receiving data and events from the websites.

+

Event APIs

+

Games and payment gateways can generate events that are meant to be received by the Telegram apps. +Typically events are generated by using the postEvent method of the GamingCommunication library. +The postEvent function will try sending the event to the Telegram app in a number of different ways.

+

WebviewProxy

+

In mobile apps, the event receiver API should be typically exposed as a window.TelegramWebviewProxy object with a postEvent method.

+
window.TelegramWebviewProxy.postEvent(eventType, eventData)
+

window.external

+

Alternatively, a window.external.notify method can be exposed, accepting a string JSON payload with the event type and payload:

+
window.external.notify(JSON.stringify({eventType: eventType, eventData: eventData}));
+

postMessage API

+

Finally, web MTProto clients that need to open a game or process a payment in an iframe can use the postMessage API to receive events from iframes. +The GamingCommunication library by defaultwill use '*' as targetOrigin, sending messages to parent pages regardless of the origin of the embedder.

+
window.parent.postMessage(JSON.stringify({eventType: eventType, eventData: eventData}), targetOrigin);
+

Event types

+

eventType is a simple string indicating the event type, and eventData is a payload with an object that will be parsed by the Telegram app.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
eventTypeeventDataDescription
payment_form_submitJSON object with data and title fieldstitle is the censored credit card title.
data is a service-specific JSON payload with information about the payment credentials provided by the user to the payment system.
Neither Telegram, nor bots will have access to your credit card information.
Credit card details will be handled only by the payment system.
share_scorenullWill be called by games when the user explicitly clicks on the share score button to share the game, along with his score.
Typically done by using messages.forwardMessages on the game message with the with_my_score flag.
share_gamenullWill be called by games when the user explicitly clicks on the share game button to share the game, without sharing his score.
Typically done by using messages.forwardMessages on the game message without the with_my_score flag, or by sharing the game's short URL.
game_overnullCan be called by games when the user loses a game
game_loadednullCan be called by games once the game fully loads
resize_frameJSON object with height fieldCalled by supported pages inside of IV iframe embeds, indicates the new size of the embed frame.
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/apple_privacy.html b/data/core.telegram.org/apple_privacy.html new file mode 100644 index 0000000000..749930f957 --- /dev/null +++ b/data/core.telegram.org/apple_privacy.html @@ -0,0 +1,118 @@ + + + + + Page moved + + + + + + + + + + + + + +
+ +
+
+
+
+

Page moved

+ +

This is not the droid you're looking for.
The page has been moved.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html b/data/core.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html new file mode 100644 index 0000000000..abf48687bc --- /dev/null +++ b/data/core.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+
+

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/bots.html b/data/core.telegram.org/bots.html new file mode 100644 index 0000000000..fa4bec195b --- /dev/null +++ b/data/core.telegram.org/bots.html @@ -0,0 +1,437 @@ + + + + + Bots: An introduction for developers + + + + + + + + + + + + + +
+ +
+
+
+
+

Bots: An introduction for developers

+ +
+ +

Bots are third-party applications that run inside Telegram. Users can interact with bots by sending them messages, commands and inline requests. You control your bots using HTTPS requests to Telegram's Bot API.

+
+

The full API reference for developers is available here.

+
+

1. What can I do with bots?

+
+ +
+ +

To name just a few things, you could use bots to:

+
    +
  • Get customized notifications and news. A bot can act as a smart newspaper, sending you relevant content as soon as it's published.

    +
  • +
  • Integrate with other services. A bot can enrich Telegram chats with content from external services.
    Gmail Bot, GIF bot, IMDB bot, Wiki bot, Music bot, Youtube bot, GitHubBot

    +
  • +
  • Accept payments from Telegram users. A bot can offer paid services or work as a virtual storefront. Read more »
    Demo Shop Bot, Demo Store

    +
  • +
  • Create custom tools. A bot may provide you with alerts, weather forecasts, translations, formatting or other services.
    Markdown bot, Sticker bot, Vote bot, Like bot

    +
  • +
  • Build single- and multiplayer games. A bot can offer rich HTML5 experiences, from simple arcades and puzzles to 3D-shooters and real-time strategy games.
    GameBot, Gamee

    +
  • +
  • Build social services. A bot could connect people looking for conversation partners based on common interests or proximity.

    +
  • +
  • Do virtually anything else. Except for dishes — bots are terrible at doing the dishes.

    +
  • +
+

2. How do bots work?

+

At the core, Telegram Bots are special accounts that do not require an additional phone number to set up. Users can interact with bots in two ways:

+
    +
  • Send messages and commands to bots by opening a chat with them or by adding them to groups.
  • +
  • Send requests directly from the input field by typing the bot's @username and a query. This allows sending content from inline bots directly into any chat, group or channel.
  • +
+

Messages, commands and requests sent by users are passed to the software running on your servers. Our intermediary server handles all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API. We call that interface our Bot API.

+
+

A detailed description of the Bot API is available on this page »

+
+

3. How do I create a bot?

+
+ +
+ +

There's a… bot for that. Just talk to BotFather (described below) and follow a few simple steps. Once you've created a bot and received your authentication token, head down to the Bot API manual to see what you can teach your bot to do.

+
+

You may also like to check out some code examples here »

+
+

4. How are bots different from humans?

+
    +
  • Bots have no online status and no last seen timestamps, the interface shows the label 'bot' instead.
  • +
  • Bots have limited cloud storage — older messages may be removed by the server shortly after they have been processed.
  • +
  • Bots can't initiate conversations with users. A user must either add them to a group or send them a message first. People can use t.me/<bot_username> links or username search to find your bot.
  • +
  • Bot usernames always end in 'bot' (e.g. @TriviaBot, @GitHub_bot).
  • +
  • When added to a group, bots do not receive all messages by default (see Privacy mode).
  • +
  • Bots never eat, sleep or complain (unless expressly programmed otherwise).
  • +
+
+

5. Bot perks

+

Telegram bots are unique in many ways — we offer two kinds of keyboards, additional interfaces for default commands and deep linking as well as text formatting, integrated payments and more.

+

Inline mode

+ + +

Users can interact with your bot via inline queries straight from the text input field in any chat. All they need to do is start a message with your bot's username and then type a query.

+

Having received the query, your bot can return some results. As soon as the user taps one of them, it is sent to the user's currently opened chat. This way, people can request content from your bot in any of their chats, groups or channels.

+

Check out this blog to see a sample inline bot in action. You can also try the @sticker and @music bots to see for yourself.

+
+
+ +
+ +

We've also implemented an easy way for your bot to switch between inline and PM modes.

+
+

Read more about the Inline Mode »

+
+

Payment platform

+ + +

You can use bots to accept payments from Telegram users around the world.

+
    +
  • Send invoices to any chat, including to groups and channels.
  • +
  • Create invoices that can be forwarded and used by multiple buyers to order things.
  • +
  • Use inline mode to help users show your goods and services to their friends and communities.
  • +
  • Allow tips from users with preset and custom amounts.
  • +
  • Accept payments from users on mobile or desktop apps.
  • +
  • Try @ShopBot to create a test invoice – or start a message with @ShopBot ... in any chat for an inline invoice.
  • +
  • Check out Demo Shop for an example of a Telegram Channel used as virtual storefront.
  • +
+
+ +
+ +
+

Read more about the Payments Platform »

+
+

Gaming platform

+

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. The platform allows your bot to keep track of high scores for every game played in every chat. Whenever there’s a new leader in the game, other playing members in the chat are notified that they need to step it up.

+
+ + +
+
+ +

Since the underlying technology is HTML5, the games can be anything from simple arcades and puzzles to multiplayer 3D-shooters and real-time strategy games. Our team has created a couple of simple demos for you to try out:

+ +

You can also check out the @gamee bot that has more than 20 games.

+
+

Read more about the Gaming Platform »

+
+

Keyboards

+

Traditional chat bots can of course be taught to understand human language. But sometimes you want some more formal input from the user — and this is where custom keyboards can become extremely useful.

+

Whenever your bot sends a message, it can pass along a special keyboard with predefined reply options (see ReplyKeyboardMarkup). Telegram apps that receive the message will display your keyboard to the user. Tapping any of the buttons will immediately send the respective command. This way you can drastically simplify user interaction with your bot.

+

We currently support text and emoji for your buttons. Here are some custom keyboard examples:

+
+
+ + + + + + + +
+ +
+

For more technical information on custom keyboards, please consult the Bot API manual (see sendMessage).

+
+

Inline keyboards and on-the-fly updating

+

There are times when you'd prefer to do things without sending any messages to the chat. For example, when your user is changing settings or flipping through search results. In such cases you can use Inline Keyboards that are integrated directly into the messages they belong to.

+

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

+
+ + + + +
+ +
+ +

When callback buttons are used, your bot can update its existing messages (or just their keyboards) so that the chat remains tidy. Check out these sample bots to see inline keyboards in action: @music, @vote, @like.

+
+

Read more about inline keyboards and on-the-fly editing »

+
+

Commands

+

Commands present a more flexible way to communicate with your bot. The following syntax may be used:

+
/command
+

A command must always start with the '/' symbol and may not be longer than 32 characters. Commands can use latin letters, numbers and underscores. Here are a few examples:

+
/get_messages_stats
+/set_timer 10min Alarm!
+/get_timezone London, UK
+

Messages that start with a slash are always passed to the bot (along with replies to its messages and messages that @mention the bot by username). Telegram apps will:

+
    +
  • Suggest a list of supported commands with descriptions when the user enters a '/' (for this to work, you need to have provided a list of commands to the BotFather). Tapping on a command in the list immediately sends the command.
  • +
  • Show an additional (/) button in the input field in all chats with bots. Tapping it types a '/' and shows the list of commands.
  • +
  • Highlight /commands in messages. When the user taps a highlighted command, the command is sent at once.
  • +
+
+ + + + + + + +
+ + +

If multiple bots are in a group, it is possible to add bot usernames to commands in order to avoid confusion:

+
/start@TriviaBot
+/start@ApocalypseBot
+

This is done automatically when commands are selected via the list of suggestions. Please remember that your bot needs to be able to process commands that are followed by its username.

+
Global commands
+

In order to make it easier for users to navigate the bot multiverse, we ask all developers to support a few basic commands. Telegram apps will have interface shortcuts for these commands.

+
    +
  • /start - begins interaction with the user, e.g., by sending a greeting message. This command can also be used to pass additional parameters to the bot (see Deep linking)
  • +
  • /help - returns a help message. It can be a short text about what your bot can do and a list of commands.
  • +
  • /settings - (if applicable) returns the bot's settings for this user and suggests commands to edit these settings.
  • +
+

Users will see a Start button when they first open a conversation with your bot. Help and Settings links will be available in the menu on the bot's profile page.

+
+ + + + +
+ +

Formatting: bold, italic, fixed-width text and inline links

+

You can use bold, italic or fixed-width text, as well as inline links in your bots' messages. Telegram clients will render them accordingly.

+
+

Read more in the Bot API manual »

+
+

Privacy mode

+

Bots are frequently added to groups in order to augment communication between human users, e.g. by providing news, notifications from external services or additional search functionality. This is especially true for work-related groups. Now, when you share a group with a bot, you tend to ask yourself “How can I be sure that the little rascal isn't selling my chat history to my competitors?” The answer is — privacy mode.

+

A bot running in privacy mode will not receive all messages that people send to the group. Instead, it will only receive:

+
    +
  • Messages that start with a slash '/' (see Commands above)
  • +
  • Replies to the bot's own messages
  • +
  • Service messages (people added or removed from the group, etc.)
  • +
  • Messages from channels where it's a member
  • +
+

On one hand, this helps some of us sleep better at night (in our tinfoil nightcaps), on the other — it allows the bot developer to save a lot of resources, since they won't need to process tens of thousands irrelevant messages each day.

+

Privacy mode is enabled by default for all bots, except bots that were added to the group as admins (bot admins always receive all messages). It can be disabled, so that the bot receives all messages like an ordinary user (the bot will need to be re-added to the group for this change to take effect). We only recommend doing this in cases where it is absolutely necessary for your bot to work — users can always see a bot's current privacy setting in the group members list. In most cases, using the force reply option for the bot's messages should be more than enough.

+

So what messages exactly will my bot get? »

+

Deep linking

+

Telegram bots have a deep linking mechanism, that allows for passing additional parameters to the bot on startup. It could be a command that launches the bot — or an authentication token to connect the user's Telegram account to their account on some external service.

+

Each bot has a link that opens a conversation with it in Telegram — https://t.me/<bot username>. You can add the parameters start or startgroup to this link, with values up to 64 characters long. For example:

+
https://t.me/triviabot?startgroup=test
+

A-Z, a-z, 0-9, _ and - are allowed. We recommend using base64url to encode parameters with binary and other types of content.

+

Following a link with the start parameter will open a one-on-one conversation with the bot, showing a START button in the place of the input field. If the startgroup parameter is used, the user is prompted to select a group to add the bot to. As soon as a user confirms the action (presses the START button in their app or selects a group to add the bot to), your bot will receive a message from that user in this format:

+
/start PAYLOAD
+

PAYLOAD stands for the value of the start or startgroup parameter that was passed in the link.

+
Deep linking Example
+

Suppose the website example.com would like to send notifications to its users via a Telegram bot. Here's what they could do to enable notifications for a user with the ID 123.

+
    +
  1. Create a bot with a suitable username, e.g. @ExampleComBot
  2. +
  3. Set up a webhook for incoming messages
  4. +
  5. Generate a random string of a sufficient length, e.g. $memcache_key = "vCH1vGWJxfSeofSAs0K5PA"
  6. +
  7. Put the value 123 with the key $memcache_key into Memcache for 3600 seconds (one hour)
  8. +
  9. Show our user the button https://t.me/ExampleComBot?start=vCH1vGWJxfSeofSAs0K5PA
  10. +
  11. Configure the webhook processor to query Memcached with the parameter that is passed in incoming messages beginning with /start. If the key exists, record the chat_id passed to the webhook as telegram_chat_id for the user 123. Remove the key from Memcache.
  12. +
  13. Now when we want to send a notification to the user 123, check if they have the field telegram_chat_id. If yes, use the sendMessage method in the Bot API to send them a message in Telegram.
  14. +
+

Location and Number

+

Some bots need extra data from the user to work properly. For example, knowing the user's location helps provide more relevant geo-specific results. The user's phone number can be very useful for integrations with other services, like banks, etc.

+

Bots can ask a user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

+
+
+ +
+ +

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

+
+

Manual: Number and location buttons »

+
+
+

6. BotFather

+
+

Jump to top to learn everything about Telegram bots »

+
+

BotFather is the one bot to rule them all. It will help you create new bots and change settings for existing ones.

+

Creating a new bot

+

Use the /newbot command to create a new bot. The BotFather will ask you for a name and username, then generate an authentication token for your new bot.

+

The name of your bot is displayed in contact details and elsewhere.

+

The Username is a short name, to be used in mentions and t.me links. Usernames are 5-32 characters long and are case insensitive, but may only include Latin characters, numbers, and underscores. Your bot's username must end in 'bot', e.g. 'tetris_bot' or 'TetrisBot'.

+

The token is a string along the lines of 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw that is required to authorize the bot and send requests to the Bot API. Keep your token secure and store it safely, it can be used by anyone to control your bot.

+

Generating an authentication token

+

If your existing token is compromised or you lost it for some reason, use the /token command to generate a new one.

+

Botfather commands

+

The remaining commands are pretty self-explanatory:

+
    +
  • /mybots — returns a list of your bots with handy controls to edit their settings
  • +
  • /mygames — does the same for your games
  • +
+

Edit bots

+
    +
  • /setname – change your bot's name.
  • +
  • /setdescription — change the bot's description, a short text of up to 512 characters, describing your bot. Users will see this text at the beginning of the conversation with the bot, titled 'What can this bot do?'.
  • +
  • /setabouttext — change the bot's about info, an even shorter text of up to 120 characters. Users will see this text on the bot's profile page. When they share your bot with someone, this text is sent together with the link.
  • +
  • /setuserpic — change the bot's profile pictures. It's always nice to put a face to a name.
  • +
  • /setcommands — change the list of commands supported by your bot. Users will see these commands as suggestions when they type / in the chat with your bot. Each command has a name (must start with a slash ‘/’, alphanumeric plus underscores, no more than 32 characters, case-insensitive), parameters, and a text description. Users will see the list of commands whenever they type '/' in a conversation with your bot.
  • +
  • /deletebot — delete your bot and free its username.
  • +
+

Edit settings

+
    +
  • /setinline — toggle inline mode for your bot.
  • +
  • /setinlinegeo - request location data to provide location-based inline results.
  • +
  • /setjoingroups — toggle whether your bot can be added to groups or not. Any bot must be able to process private messages, but if your bot was not designed to work in groups, you can disable this.
  • +
  • /setprivacy — set which messages your bot will receive when added to a group. With privacy mode disabled, the bot will receive all messages. We recommend leaving privacy mode enabled. You will need to re-add the bot to existing groups for this change to take effect.
  • +
+

Manage games

+
    +
  • /newgame — create a new game.
  • +
  • /listgames — get a list of your games.
  • +
  • /editgame — edit a game.
  • +
  • /deletegame — delete an existing game.
  • +
+
+

Please note, that it may take a few minutes for changes to take effect.

+
+

Status alerts

+

Millions choose Telegram for its speed. To stay competitive in this environment, your bot also needs to be responsive. In order to help developers keep their bots in shape, Botfather will send status alerts if it sees something is wrong.

+

We will be checking the number of replies and the request/response conversion rate for popular bots (~300 requests per minute: but don't write this down as the value may change in the future). If we get abnormally low readings, you will receive a notification from Botfather.

+
Responding to alerts
+

By default, you will only get one alert per bot per hour. Each alert has the following buttons:

+
    +
  • Fixed. Use this if you found an issue with your bot and fixed it. If you press the fix button, we will resume sending alerts in the regular way so that you can see if your fix worked within 5-10 minutes instead of having to wait for an hour.
  • +
  • Support. Use this to open a chat with @BotSupport if you don't see any issues with your bot or if you think the problem is on our side.
  • +
  • Mute for 8h/1w. Use this if you can't fix your bot at the moment. This will disable all alerts for the bot in question for the specified period of time. We do not recommend using this option since your users may migrate to a more stable bot. You can unmute alerts in your bot's settings via Botfather.
  • +
+
Monitored issues
+

We will currently notify you about the following issues:

+

1.

+
Too few **private messages** are sent compared to previous weeks: **{value}**
+

Your bot is sending much fewer messages than it did in the previous weeks. This is useful for newsletter-style bots that send out messages without prompts from the users. The larger the value, the more significant the difference.

+

2.

+
Too few replies to incoming **private messages**. Conversion rate: **{value}**
+

Your bot is not replying to all messages that are being sent to it (the request/response conversion rate for your bot was too low for at least two of the last three 5-minute periods). To provide a good user experience, please respond to all messages that are sent to your bot. Respond to message updates by calling send… methods (e.g. sendMessage).

+

3.

+
Too few answers to **inline queries**. Conversion rate: **{value}**
+

Your bot is not replying to all inline queries that are being sent to it, calculated in the same way as above. Respond to inline_query updates by calling answerInlineQuery.

+

4.

+
Too few answers to **callback queries**. Conversion rate: **{value}**
+Too few answers to **callback game queries**. Conversion rate: **{value}**
+

Your bot is not replying to all callback queries that are being sent to it (with or without games), calculated in the same way as above. Respond to callback_query updates by calling answerCallbackQuery.

+
+

Please note that the status alerts feature is still being tested and will be improved in the future.

+
+
+

That's it for the introduction. You are now definitely ready to proceed to the BOT API MANUAL.

+

If you've got any questions, please check out our Bot FAQ »

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/bots/api-changelog.html b/data/core.telegram.org/bots/api-changelog.html new file mode 100644 index 0000000000..c515fad459 --- /dev/null +++ b/data/core.telegram.org/bots/api-changelog.html @@ -0,0 +1,670 @@ + + + + + Bot API changelog + + + + + + + + + + + + + +
+ +
+
+
+
+

Bot API changelog

+ +
+ +
+

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots »

+
+

You will find all changes to our Bot API on this page.

+

Recent changes

+
+

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

+
+

January 31, 2022

+

Bot API 5.7

+ +

December 30, 2021

+

Bot API 5.6

+ +

December 7, 2021

+

Bot API 5.5

+
    +
  • Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
  • +
  • Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
  • +
  • Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
  • +
  • Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
  • +
  • Added the field has_protected_content to the classes Chat and Message.
  • +
  • Added the field is_automatic_forward to the class Message.
  • +
+

Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.

+

Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.

+

Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.

+

November 5, 2021

+

Bot API 5.4

+ +
+
+

⚠️ WARNING! ⚠️
User identifiers will become bigger than 2^31 - 1 before the end of this year and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

June 25, 2021

+

Bot API 5.3

+

Personalized Commands

+
    +
  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • +
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • +
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • +
  • Added the parameters scope and language_code to the method getMyCommands.
  • +
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • +
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
  • +
+

Custom Placeholders

+ +

And More

+
    +
  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • +
  • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
  • +
  • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
  • +
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
  • +
+
+
+

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

April 26, 2021

+

Bot API 5.2

+
    +
  • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
  • +
  • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
  • +
  • Allowed sending invoices to group, supergroup and channel chats.
  • +
  • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
  • +
  • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
  • +
  • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
  • +
  • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
  • +
  • Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
  • +
+
+
+

⚠️ WARNING! ⚠️
After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

+
+
+
+

⚠️ WARNING! ⚠️
Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.

+
+
+
+

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

March 9, 2021

+

Bot API 5.1

+

Added two new update types

+
    +
  • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
  • +
+

Improved Invite Links

+
    +
  • Added the class ChatInviteLink, representing an invite link to a chat.
  • +
  • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
  • +
  • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
  • +
  • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
  • +
+

Voice Chat Info

+ +

And More

+
    +
  • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
  • +
  • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
  • +
  • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
  • +
  • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
  • +
+
+
+

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

November 4, 2020

+

Introducing Bot API 5.0

+

Run Your Own Bot API Server

+
    +
  • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance.
  • +
  • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
  • +
  • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
  • +
+

Transfer Bot Ownership

+
    +
  • You can now use @BotFather to transfer your existing bots to another Telegram account.
  • +
+

Webhooks

+
    +
  • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
  • +
  • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
  • +
  • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
  • +
+

Working with Groups

+
    +
  • The getChat request now returns the user's bio for private chats if available.
  • +
  • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
  • +
  • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
  • +
  • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
  • +
+

Working with Files

+
    +
  • Added the field file_name to the classes Audio and Video, containing the name of the original file.
  • +
  • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
  • +
+

Multiple Pinned Messages

+
    +
  • Added the ability to pin messages in private chats.
  • +
  • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
  • +
  • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
  • +
+

File Albums

+
    +
  • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
  • +
+

Live Locations

+ +

Anonymous Admins

+
    +
  • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
  • +
  • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
  • +
  • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
  • +
  • Added the custom title of an anonymous message sender to the class Message as author_signature.
  • +
+

And More

+ +

And Last but not Least

+
    +
  • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
  • +
+

June 4, 2020

+

Bot API 4.9

+
    +
  • Added the new field via_bot to the Message object. You can now know which bot was used to send a message.
  • +
  • Supported video thumbnails for inline GIF and MPEG4 animations.
  • +
  • Supported the new basketball animation for the random dice. Choose between different animations (dice, darts, basketball) by specifying the emoji parameter in the method sendDice.
  • +
+

April 24, 2020

+

Bot API 4.8

+
    +
  • Supported explanations for Quizzes 2.0. Add explanations by specifying the parameters explanation and explanation_parse_mode in the method sendPoll.
  • +
  • Added the fields explanation and explanation_entities to the Poll object.
  • +
  • Supported timed polls that automatically close at a certain date and time. Set up by specifying the parameter open_period or close_date in the method sendPoll.
  • +
  • Added the fields open_period and close_date to the Poll object.
  • +
  • Supported the new darts animation for the dice mini-game. Choose between the default dice animation and darts animation by specifying the parameter emoji in the method sendDice.
  • +
  • Added the field emoji to the Dice object.
  • +
+

March 30, 2020

+

Bot API 4.7

+
    +
  • Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the “proper” singular of die. But it's awkward, and we decided to help it change. One dice at a time!)
  • +
  • Added the field dice to the Message object.
  • +
  • Added the method getMyCommands for getting the current list of the bot's commands.
  • +
  • Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather.
  • +
  • Added the ability to create animated sticker sets by specifying the parameter tgs_sticker instead of png_sticker in the method createNewStickerSet.
  • +
  • Added the ability to add animated stickers to sets created by the bot by specifying the parameter tgs_sticker instead of png_sticker in the method addStickerToSet.
  • +
  • Added the field thumb to the StickerSet object.
  • +
  • Added the ability to change thumbnails of sticker sets created by the bot using the method setStickerSetThumb.
  • +
+

January 23, 2020

+

Bot API 4.6

+
    +
  • Supported Polls 2.0.
  • +
  • Added the ability to send non-anonymous, multiple answer, and quiz-style polls: added the parameters is_anonymous, type, allows_multiple_answers, correct_option_id, is_closed options to the method sendPoll.
  • +
  • Added the object KeyboardButtonPollType and the field request_poll to the object KeyboardButton.
  • +
  • Added updates about changes of user answers in non-anonymous polls, represented by the object PollAnswer and the field poll_answer in the Update object.
  • +
  • Added the fields total_voter_count, is_anonymous, type, allows_multiple_answers, correct_option_id to the Poll object.
  • +
  • Bots can now send polls to private chats.
  • +
  • Added more information about the bot in response to the getMe request: added the fields can_join_groups, can_read_all_group_messages and supports_inline_queries to the User object.
  • +
  • Added the optional field language to the MessageEntity object.
  • +
+

December 31, 2019

+

Bot API 4.5

+
    +
  • Added support for two new MessageEntity types, underline and strikethrough.
  • +
  • Added support for nested MessageEntity objects. Entities can now contain other entities. If two entities have common characters then one of them is fully contained inside the other.
  • +
  • Added support for nested entities and the new tags <u>/<ins> (for underlined text) and <s>/<strike>/<del> (for strikethrough text) in parse mode HTML.
  • +
  • Added a new parse mode, MarkdownV2, which supports nested entities and two new entities __ (for underlined text) and ~ (for strikethrough text). Parse mode Markdown remains unchanged for backward compatibility.
  • +
  • Added the field file_unique_id to the objects Animation, Audio, Document, PassportFile, PhotoSize, Sticker, Video, VideoNote, Voice, File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto. The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
  • +
  • Added the field custom_title to the ChatMember object.
  • +
  • Added the new method setChatAdministratorCustomTitle to manage the custom titles of administrators promoted by the bot.
  • +
  • Added the field slow_mode_delay to the Chat object.
  • +
+

July 29, 2019

+

Bot API 4.4

+
    +
  • Added support for animated stickers. New field is_animated in Sticker and StickerSet objects, animated stickers can now be used in sendSticker and InlineQueryResultCachedSticker.
  • +
  • Added support for default permissions in groups. New object ChatPermissions, containing actions which a member can take in a chat. New field permissions in the Chat object; new method setChatPermissions.
  • +
  • The field all_members_are_administrators has been removed from the documentation for the Chat object. The field is still returned in the object for backward compatibility, but new bots should use the permissions field instead.
  • +
  • Added support for more permissions for group and supergroup members: added the new field can_send_polls to ChatMember object, added can_change_info, can_invite_users, can_pin_messages in ChatMember object for restricted users (previously available only for administrators).
  • +
  • The method restrictChatMember now takes the new user permissions in a single argument of the type ChatPermissions. The old way of passing parameters will keep working for a while for backward compatibility.
  • +
  • Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method.
  • +
  • Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
  • +
  • File identifiers from the ChatPhoto object are now invalidated and can no longer be used whenever the photo is changed.
  • +
  • All webhook requests from the Bot API are now coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • +
  • As of the next Bot API update (version 4.5), nested MessageEntity objects will be allowed in message texts and captions. Please make sure that your code can correctly handle such entities.
  • +
+

May 31, 2019

+

Bot API 4.3

+
    +
  • Added support for Seamless Telegram Login on external websites.
  • +
  • Added the new object LoginUrl and the new field login_url to the InlineKeyboardButton object which allows to automatically authorize users before they go to a URL specified by the bot. Users will be asked to confirm authorization in their Telegram app (needs version 5.7 or higher) when they press the button:
  • +
+
+ TITLE +
+ +

Also in this update:

+
    +
  • Added the field reply_markup to the Message object, containing the inline keyboard attached to the message.
  • +
  • If a message with an inline keyboard is forwarded, the forwarded message will now have an inline keyboard if the keyboard contained only url and login_url buttons or if the message was sent via a bot and the keyboard contained only url, login_url, switch_inline_query or switch_inline_query_current_chat buttons. In the latter case, switch_inline_query_current_chat buttons are replaced with switch_inline_query buttons.
  • +
  • Bots now receive the edited_message Update even if only Message.reply_markup has changed.
  • +
  • Bots that have the can_edit_messages right in a channel can now use the method editMessageReplyMarkup for messages written by other administrators forever without the 48 hours limit.
  • +
  • Don't forget that starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • +
+

April 14, 2019

+

Bot API 4.2

+
    +
  • Added support for native polls: added the object Poll, the methods sendPoll and stopPoll and the field poll in the Message and Update objects.
  • +
  • The method deleteMessage can now be used to delete messages sent by a user to the bot in private chats within 48 hours.
  • +
  • Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage, and receive the pinned group message in Chat object.
  • +
  • Added the field is_member to the ChatMember object, which can be used to find whether a restricted user is a member of the chat.
  • +
  • Added the field forward_sender_name to the Message object, containing name of the sender who has opted to hide their account.
  • +
  • Starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • +
  • Document thumbnails now should be inscribed in a 320x320 square instead of 90x90.
  • +
+

August 27, 2018

+

Bot API 4.1

+ +

July 26, 2018

+

Bot API 4.0.

+
    +
  • Added support for Telegram Passport. See the official announcement on the blog and the manual for details.
  • +
  • Added support for editing the media content of messages: added the method editMessageMedia and new types InputMediaAnimation, InputMediaAudio, and InputMediaDocument.
  • +
  • Added the field thumb to the Audio object to contain the thumbnail of the album cover to which the music file belongs.
  • +
  • Added support for attaching custom thumbnails to uploaded files. For animations, audios, videos and video notes, which are less than 10 MB in size, thumbnails are generated automatically.
  • +
  • tg:// URLs now can be used in inline keyboard url buttons and text_link message entities.
  • +
  • Added the method sendAnimation, which can be used instead of sendDocument to send animations, specifying their duration, width and height.
  • +
  • Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set.
  • +
  • Added two new MessageEntity types: cashtag and phone_number.
  • +
  • Added support for Foursquare venues: added the new field foursquare_type to the objects Venue, InlineQueryResultVenue and InputVenueMessageContent, and the parameter foursquare_type to the sendVenue method.
  • +
  • You can now create inline mentions of users, who have pressed your bot's callback buttons.
  • +
  • You can now use the Retry-After response header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook.
  • +
  • If a webhook returns the HTTP error 410 Gone for all requests for more than 23 hours successively, it can be automatically removed.
  • +
  • Added vCard support when sharing contacts: added the field vcard to the objects Contact, InlineQueryResultContact, InputContactMessageContent and the method sendContact.
  • +
+

February 13, 2018

+

Bot API 3.6.

+
    +
  • Supported text formatting in media captions. Specify the desired parse_mode (Markdown or HTML) when you provide a caption.
  • +
  • In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot).
  • +
  • Added the new field connected_website to Message. The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
  • +
  • Added the new parameter supports_streaming to the sendVideo method and a field with the same name to the InputMediaVideo object.
  • +
+

November 17, 2017

+

Bot API 3.5.

+ +

October 11, 2017

+

Bot API 3.4.

+ +

August 23, 2017

+

Bot API 3.3.

+
    +
  • Bots can now mention users via inline mentions, without using usernames.
  • +
  • getChat now also returns pinned messages in supergroups, if present. Added the new field pinned_message to the Chat object.
  • +
  • Added the new fields author_signature and forward_signature to the Message object.
  • +
  • Added the new field is_bot to the User object.
  • +
+

July 21, 2017

+

Bot API 3.2. Teach your bot to handle stickers and sticker sets.

+ +

June 30, 2017

+

Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:

+ +

May 18, 2017

+

Introducing Bot API 3.0.

+

NEW Payment Platform

+

See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.

+ +

NEW Video Messages

+
    +
  • As of Telegram v.4.0, users can send short rounded video messages, using an interface similar to that of voice notes.
  • +
  • Added the sendVideoNote method, the new field video_note to Message, the fields record_video_note or upload_video_note to sendChatAction.
  • +
+

NEW Multilingual Bots

+
    +
  • The User object now may have a language_code field that contains the IETF language tag of the user's language.
  • +
  • Thanks to this, your bot can now offer localized responses to users that speak different languages.
  • +
+

More power to admin bots

+
    +
  • unbanChatMemeber now also works in channels!
  • +
  • New method deleteMessage that allows the bot to delete its own messages, as well as messages posted by other in groups and channels where the bot is an administrator.
  • +
+

Minor Changes

+
    +
  • Replaced the field new_chat_member in Message with new_chat_members (the old field will still be available for a while for compatibility purposes).
  • +
  • Inline keyboards with switch_inline_query and switch_inline_query_current_chat can no longer be sent to channels because they are useless there.
  • +
  • New fields gif_duration in InlineQueryResultGif and mpeg4_duration in InlineQueryResultMpeg4Gif.
  • +
+

December 4, 2016

+

Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.

+
    +
  • Use the new field max_connections in setWebhook to optimize your bot's server load
  • +
  • Use allowed_updates in setWebhook and getUpdates to selectively subscribe to updates of a certain type. Among other things, this allows you to stop getting updates about new posts in channels where your bot is an admin.
  • +
  • deleteWebhook moved out of setWebhook to get a whole separate method for itself.
  • +
+

November 21, 2016

+

Bot API 2.3

+
    +
  • Modified bot privacy mode for the sake of consistency.
  • +
  • Your bot can now get updates about posts in channels. Added new fields channel_post and edited_channel_post to Update.

    +
  • +
  • You can now update high scores to a lower value by using the new force parameter in setGameScore. Handy for punishing cheaters or fixing errors in your game's High Score table.

    +
  • +
  • Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
  • +
  • The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
  • +
  • Added the new field forward_from_message_id to Message.
  • +
  • Added the new parameter cache_time to answerCallbackQuery. Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
  • +
  • Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
  • +
+

October 3, 2016

+

Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.

+ +

Other changes

+ +
    +
  • New field all_members_are_administrators in the Chat object.
  • +
  • Certain server responses may now contain the new parameters field with expanded info on errors that occurred while processing your requests.
  • +
+

May 25, 2016

+ +

May 22, 2016

+ +

May 12, 2016

+ +

May 6, 2016

+
    +
  • Added the field emoji to the Sticker object. Your bot can now know the emoji a sticker corresponds to.
  • +
  • Added the field forward_from_chat to the Message object for messages forwarded from channels.
  • +
+

April 9, 2016

+

Introducing Bot API 2.0. Check out this page for a review of this major update.

+ +

Inline bots

+
    +
  • Added support for all content types available on Telegram. 19 types of InlineQueryResult objects are now supported.
  • +
  • Inline bots can now substitute all kinds of content with text. Added 4 types of InputMessageContent objects.
  • +
  • Your inline bot can also ask users for permission to use their location. Added the new Botfather command /setinlinegeo, added field location to the InlineQuery object, added fields location and inline_message_id to the ChosenInlineResult object.
  • +
  • Added an easy way to switch between inline mode and a private chat with the bot – useful for settings, establishing external connections and teaching users how to use your bot in inline mode. Added parameters switch_pm_text and switch_pm_parameter to the method answerInlineQuery.
  • +
+

Miscellaneous

+ +

February 20, 2016

+
    +
  • Added the disable_notification parameter to all methods that send messages or any kind.
  • +
  • Removed backward compatibility from the method sendAudio. Voice messages now must be sent using the method sendVoice. There is no more need to specify a non-empty title or performer while sending the audio by file_id.
  • +
+

January 20, 2016

+
    +
  • By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
  • +
+

January 14, 2016

+
    +
  • You can now collect feedback on which results provided by your inline bot get chosen by the users. Added the setinlinefeedback command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object.
  • +
+

January 4, 2016

+ +

November, 2015

+
    +
  • Added support for supergroups. The Type field in the Chat object can now contain 'supergroup'.
  • +
  • New optional fields added to the Message object: supergroup_chat_created, migrate_to_chat_id, migrate_from_chat_id and channel_chat_created.
  • +
+

October 8, 2015

+
    +
  • Added initial channel support for bots (no Telegram clients support this at the moment, please wait for updates):
  • +
  • The Chat field in the Message is now of the new type Chat.
  • +
  • You can now pass a channel username (in the format @channelusername) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).
  • +
+

September 18, 2015

+
    +
  • Bots can now download files and media sent by users.
  • +
  • Added getFile and File.
  • +
+

September 7, 2015

+
    +
  • You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
  • +
  • Added very basic markdown support. New field parse_mode added to sendMessage. For the moment messages with markdown will be displayed correctly only in Telegram for Android. Other official apps will catch up soon.
  • +
+

August 29, 2015

+
    +
  • Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.
  • +
  • You can now make new requests when responding to webhook updates.
  • +
+

August 15, 2015

+
    +
  • Added new type Voice and new method sendVoice for sending voice messages.
  • +
  • Earlier Audio and sendAudio should now be used for sending music files. Telegram clients will show such files in the in-app music player. If you were using sendAudio for your bot to send voice messages, please use sendVoice instead.
  • +
  • Added optional fields performer, title to the Audio object and sendAudio method.
  • +
  • Added optional field voice to the Message object.
  • +
+

July 2015

+
    +
  • The thumb field is now optional for Video, Sticker and Document objects
  • +
  • The API now supports both video and photo captions. The caption field has been removed from the Video object and added to the Message object instead.
  • +
  • caption and duration optional fields have been added to the sendVideo method.
  • +
  • Fixed typo: user_id in the Contact object is now correctly labeled as Integer, not String
  • +
+

June 24, 2015

+

The bot platform was officially launched.

+
+

Back to the Bot API Manual »

+
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/bots/api.html b/data/core.telegram.org/bots/api.html new file mode 100644 index 0000000000..b80cdfcfc8 --- /dev/null +++ b/data/core.telegram.org/bots/api.html @@ -0,0 +1,9488 @@ + + + + + Telegram Bot API + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram Bot API

+ +
+ +
+

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots and Bot FAQ.

+
+

Recent changes

+
+

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

+
+

January 31, 2022

+

Bot API 5.7

+ +

December 30, 2021

+

Bot API 5.6

+ +

December 7, 2021

+

Bot API 5.5

+
    +
  • Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
  • +
  • Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
  • +
  • Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
  • +
  • Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
  • +
  • Added the field has_protected_content to the classes Chat and Message.
  • +
  • Added the field is_automatic_forward to the class Message.
  • +
+

Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.

+

Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.

+

Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.

+

November 5, 2021

+

Bot API 5.4

+ +

See earlier changes »

+

Authorizing your bot

+

Each bot is given a unique authentication token when it is created. The token looks something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11, but we'll use simply <token> in this document instead. You can learn about obtaining tokens and generating new ones in this document.

+

Making requests

+

All queries to the Telegram Bot API must be served over HTTPS and need to be presented in this form: https://api.telegram.org/bot<token>/METHOD_NAME. Like this for example:

+
https://api.telegram.org/bot123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11/getMe
+

We support GET and POST HTTP methods. We support four ways of passing parameters in Bot API requests:

+
    +
  • URL query string
  • +
  • application/x-www-form-urlencoded
  • +
  • application/json (except for uploading files)
  • +
  • multipart/form-data (use to upload files)
  • +
+

The response contains a JSON object, which always has a Boolean field 'ok' and may have an optional String field 'description' with a human-readable description of the result. If 'ok' equals True, the request was successful and the result of the query can be found in the 'result' field. In case of an unsuccessful request, 'ok' equals false and the error is explained in the 'description'. An Integer 'error_code' field is also returned, but its contents are subject to change in the future. Some errors may also have an optional field 'parameters' of the type ResponseParameters, which can help to automatically handle the error.

+
    +
  • All methods in the Bot API are case-insensitive.
  • +
  • All queries must be made using UTF-8.
  • +
+

Making requests when getting updates

+

If you're using webhooks, you can perform a request to the Bot API while sending an answer to the webhook. Use either application/json or application/x-www-form-urlencoded or multipart/form-data response content type for passing parameters. Specify the method to be invoked in the method parameter of the request. It's not possible to know that such a request was successful or get its result.

+
+

Please see our FAQ for examples.

+
+

Using a Local Bot API Server

+

The Bot API server source code is available at telegram-bot-api. You can run it locally and send the requests to your own server instead of https://api.telegram.org. If you switch to a local Bot API server, your bot will be able to:

+
    +
  • Download files without a size limit.
  • +
  • Upload files up to 2000 MB.
  • +
  • Upload files using their local path and the file URI scheme.
  • +
  • Use an HTTP URL for the webhook.
  • +
  • Use any local IP address for the webhook.
  • +
  • Use any port for the webhook.
  • +
  • Set max_webhook_connections up to 100000.
  • +
  • Receive the absolute local path as a value of the file_path field without the need to download the file after a getFile request.
  • +
+

Do I need a Local Bot API Server

+

The majority of bots will be OK with the default configuration, running on our servers. But if you feel that you need one of these features, you're welcome to switch to your own at any time.

+

Getting updates

+

There are two mutually exclusive ways of receiving updates for your bot — the getUpdates method on one hand and Webhooks on the other. Incoming updates are stored on the server until the bot receives them either way, but they will not be kept longer than 24 hours.

+

Regardless of which option you choose, you will receive JSON-serialized Update objects as a result.

+

Update

+

This object represents an incoming update.
At most one of the optional parameters can be present in any given update.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
update_idIntegerThe update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using Webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.
messageMessageOptional. New incoming message of any kind — text, photo, sticker, etc.
edited_messageMessageOptional. New version of a message that is known to the bot and was edited
channel_postMessageOptional. New incoming channel post of any kind — text, photo, sticker, etc.
edited_channel_postMessageOptional. New version of a channel post that is known to the bot and was edited
inline_queryInlineQueryOptional. New incoming inline query
chosen_inline_resultChosenInlineResultOptional. The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
callback_queryCallbackQueryOptional. New incoming callback query
shipping_queryShippingQueryOptional. New incoming shipping query. Only for invoices with flexible price
pre_checkout_queryPreCheckoutQueryOptional. New incoming pre-checkout query. Contains full information about checkout
pollPollOptional. New poll state. Bots receive only updates about stopped polls and polls, which are sent by the bot
poll_answerPollAnswerOptional. A user changed their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.
my_chat_memberChatMemberUpdatedOptional. The bot's chat member status was updated in a chat. For private chats, this update is received only when the bot is blocked or unblocked by the user.
chat_memberChatMemberUpdatedOptional. A chat member's status was updated in a chat. The bot must be an administrator in the chat and must explicitly specify “chat_member” in the list of allowed_updates to receive these updates.
chat_join_requestChatJoinRequestOptional. A request to join the chat has been sent. The bot must have the can_invite_users administrator right in the chat to receive these updates.
+

getUpdates

+

Use this method to receive incoming updates using long polling (wiki). An Array of Update objects is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
offsetIntegerOptionalIdentifier of the first update to be returned. Must be greater by one than the highest among the identifiers of previously received updates. By default, updates starting with the earliest unconfirmed update are returned. An update is considered confirmed as soon as getUpdates is called with an offset higher than its update_id. The negative offset can be specified to retrieve updates starting from -offset update from the end of the updates queue. All previous updates will forgotten.
limitIntegerOptionalLimits the number of updates to be retrieved. Values between 1-100 are accepted. Defaults to 100.
timeoutIntegerOptionalTimeout in seconds for long polling. Defaults to 0, i.e. usual short polling. Should be positive, short polling should be used for testing purposes only.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify [“message”, “edited_channel_post”, “callback_query”] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.

Please note that this parameter doesn't affect updates created before the call to the getUpdates, so unwanted updates may be received for a short period of time.
+
+

Notes
1. This method will not work if an outgoing webhook is set up.
2. In order to avoid getting duplicate updates, recalculate offset after each server response.

+
+

setWebhook

+

Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized Update. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns True on success.

+

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. https://www.example.com/<token>. Since nobody else knows your bot's token, you can be pretty sure it's us.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
urlStringYesHTTPS url to send updates to. Use an empty string to remove webhook integration
certificateInputFileOptionalUpload your public key certificate so that the root certificate in use can be checked. See our self-signed guide for details.
ip_addressStringOptionalThe fixed IP address which will be used to send webhook requests instead of the IP address resolved through DNS
max_connectionsIntegerOptionalMaximum allowed number of simultaneous HTTPS connections to the webhook for update delivery, 1-100. Defaults to 40. Use lower values to limit the load on your bot's server, and higher values to increase your bot's throughput.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify [“message”, “edited_channel_post”, “callback_query”] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.
Please note that this parameter doesn't affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time.
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
+
+

Notes
1. You will not be able to receive updates using getUpdates for as long as an outgoing webhook is set up.
2. To use a self-signed certificate, you need to upload your public key certificate using certificate parameter. Please upload as InputFile, sending a String will not work.
3. Ports currently supported for Webhooks: 443, 80, 88, 8443.

+

NEW! If you're having any trouble setting up webhooks, please check out this amazing guide to Webhooks.

+
+

deleteWebhook

+

Use this method to remove webhook integration if you decide to switch back to getUpdates. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
+

getWebhookInfo

+

Use this method to get current webhook status. Requires no parameters. On success, returns a WebhookInfo object. If the bot is using getUpdates, will return an object with the url field empty.

+

WebhookInfo

+

Contains information about the current status of a webhook.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
urlStringWebhook URL, may be empty if webhook is not set up
has_custom_certificateBooleanTrue, if a custom certificate was provided for webhook certificate checks
pending_update_countIntegerNumber of updates awaiting delivery
ip_addressStringOptional. Currently used webhook IP address
last_error_dateIntegerOptional. Unix time for the most recent error that happened when trying to deliver an update via webhook
last_error_messageStringOptional. Error message in human-readable format for the most recent error that happened when trying to deliver an update via webhook
max_connectionsIntegerOptional. Maximum allowed number of simultaneous HTTPS connections to the webhook for update delivery
allowed_updatesArray of StringOptional. A list of update types the bot is subscribed to. Defaults to all update types except chat_member
+

Available types

+

All types used in the Bot API responses are represented as JSON-objects.

+

It is safe to use 32-bit signed integers for storing all Integer fields unless otherwise noted.

+
+

Optional fields may be not returned when irrelevant.

+
+

User

+

This object represents a Telegram user or bot.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idIntegerUnique identifier for this user or bot. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
is_botBooleanTrue, if this user is a bot
first_nameStringUser's or bot's first name
last_nameStringOptional. User's or bot's last name
usernameStringOptional. User's or bot's username
language_codeStringOptional. IETF language tag of the user's language
can_join_groupsBooleanOptional. True, if the bot can be invited to groups. Returned only in getMe.
can_read_all_group_messagesBooleanOptional. True, if privacy mode is disabled for the bot. Returned only in getMe.
supports_inline_queriesBooleanOptional. True, if the bot supports inline queries. Returned only in getMe.
+

Chat

+

This object represents a chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idIntegerUnique identifier for this chat. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
typeStringType of chat, can be either “private”, “group”, “supergroup” or “channel”
titleStringOptional. Title, for supergroups, channels and group chats
usernameStringOptional. Username, for private chats, supergroups and channels if available
first_nameStringOptional. First name of the other party in a private chat
last_nameStringOptional. Last name of the other party in a private chat
photoChatPhotoOptional. Chat photo. Returned only in getChat.
bioStringOptional. Bio of the other party in a private chat. Returned only in getChat.
has_private_forwardsTrueOptional. True, if privacy settings of the other party in the private chat allows to use tg://user?id=<user_id> links only in chats with the user. Returned only in getChat.
descriptionStringOptional. Description, for groups, supergroups and channel chats. Returned only in getChat.
invite_linkStringOptional. Primary invite link, for groups, supergroups and channel chats. Returned only in getChat.
pinned_messageMessageOptional. The most recent pinned message (by sending date). Returned only in getChat.
permissionsChatPermissionsOptional. Default chat member permissions, for groups and supergroups. Returned only in getChat.
slow_mode_delayIntegerOptional. For supergroups, the minimum allowed delay between consecutive messages sent by each unpriviledged user; in seconds. Returned only in getChat.
message_auto_delete_timeIntegerOptional. The time after which all messages sent to the chat will be automatically deleted; in seconds. Returned only in getChat.
has_protected_contentTrueOptional. True, if messages from the chat can't be forwarded to other chats. Returned only in getChat.
sticker_set_nameStringOptional. For supergroups, name of group sticker set. Returned only in getChat.
can_set_sticker_setTrueOptional. True, if the bot can change the group sticker set. Returned only in getChat.
linked_chat_idIntegerOptional. Unique identifier for the linked chat, i.e. the discussion group identifier for a channel and vice versa; for supergroups and channel chats. This identifier may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier. Returned only in getChat.
locationChatLocationOptional. For supergroups, the location to which the supergroup is connected. Returned only in getChat.
+

Message

+

This object represents a message.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
message_idIntegerUnique message identifier inside this chat
fromUserOptional. Sender of the message; empty for messages sent to channels. For backward compatibility, the field contains a fake sender user in non-channel chats, if the message was sent on behalf of a chat.
sender_chatChatOptional. Sender of the message, sent on behalf of a chat. For example, the channel itself for channel posts, the supergroup itself for messages from anonymous group administrators, the linked channel for messages automatically forwarded to the discussion group. For backward compatibility, the field from contains a fake sender user in non-channel chats, if the message was sent on behalf of a chat.
dateIntegerDate the message was sent in Unix time
chatChatConversation the message belongs to
forward_fromUserOptional. For forwarded messages, sender of the original message
forward_from_chatChatOptional. For messages forwarded from channels or from anonymous administrators, information about the original sender chat
forward_from_message_idIntegerOptional. For messages forwarded from channels, identifier of the original message in the channel
forward_signatureStringOptional. For forwarded messages that were originally sent in channels or by an anonymous chat administrator, signature of the message sender if present
forward_sender_nameStringOptional. Sender's name for messages forwarded from users who disallow adding a link to their account in forwarded messages
forward_dateIntegerOptional. For forwarded messages, date the original message was sent in Unix time
is_automatic_forwardTrueOptional. True, if the message is a channel post that was automatically forwarded to the connected discussion group
reply_to_messageMessageOptional. For replies, the original message. Note that the Message object in this field will not contain further reply_to_message fields even if it itself is a reply.
via_botUserOptional. Bot through which the message was sent
edit_dateIntegerOptional. Date the message was last edited in Unix time
has_protected_contentTrueOptional. True, if the message can't be forwarded
media_group_idStringOptional. The unique identifier of a media message group this message belongs to
author_signatureStringOptional. Signature of the post author for messages in channels, or the custom title of an anonymous group administrator
textStringOptional. For text messages, the actual UTF-8 text of the message, 0-4096 characters
entitiesArray of MessageEntityOptional. For text messages, special entities like usernames, URLs, bot commands, etc. that appear in the text
animationAnimationOptional. Message is an animation, information about the animation. For backward compatibility, when this field is set, the document field will also be set
audioAudioOptional. Message is an audio file, information about the file
documentDocumentOptional. Message is a general file, information about the file
photoArray of PhotoSizeOptional. Message is a photo, available sizes of the photo
stickerStickerOptional. Message is a sticker, information about the sticker
videoVideoOptional. Message is a video, information about the video
video_noteVideoNoteOptional. Message is a video note, information about the video message
voiceVoiceOptional. Message is a voice message, information about the file
captionStringOptional. Caption for the animation, audio, document, photo, video or voice, 0-1024 characters
caption_entitiesArray of MessageEntityOptional. For messages with a caption, special entities like usernames, URLs, bot commands, etc. that appear in the caption
contactContactOptional. Message is a shared contact, information about the contact
diceDiceOptional. Message is a dice with random value
gameGameOptional. Message is a game, information about the game. More about games »
pollPollOptional. Message is a native poll, information about the poll
venueVenueOptional. Message is a venue, information about the venue. For backward compatibility, when this field is set, the location field will also be set
locationLocationOptional. Message is a shared location, information about the location
new_chat_membersArray of UserOptional. New members that were added to the group or supergroup and information about them (the bot itself may be one of these members)
left_chat_memberUserOptional. A member was removed from the group, information about them (this member may be the bot itself)
new_chat_titleStringOptional. A chat title was changed to this value
new_chat_photoArray of PhotoSizeOptional. A chat photo was change to this value
delete_chat_photoTrueOptional. Service message: the chat photo was deleted
group_chat_createdTrueOptional. Service message: the group has been created
supergroup_chat_createdTrueOptional. Service message: the supergroup has been created. This field can't be received in a message coming through updates, because bot can't be a member of a supergroup when it is created. It can only be found in reply_to_message if someone replies to a very first message in a directly created supergroup.
channel_chat_createdTrueOptional. Service message: the channel has been created. This field can't be received in a message coming through updates, because bot can't be a member of a channel when it is created. It can only be found in reply_to_message if someone replies to a very first message in a channel.
message_auto_delete_timer_changedMessageAutoDeleteTimerChangedOptional. Service message: auto-delete timer settings changed in the chat
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
migrate_from_chat_idIntegerOptional. The supergroup has been migrated from a group with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
pinned_messageMessageOptional. Specified message was pinned. Note that the Message object in this field will not contain further reply_to_message fields even if it is itself a reply.
invoiceInvoiceOptional. Message is an invoice for a payment, information about the invoice. More about payments »
successful_paymentSuccessfulPaymentOptional. Message is a service message about a successful payment, information about the payment. More about payments »
connected_websiteStringOptional. The domain name of the website on which the user has logged in. More about Telegram Login »
passport_dataPassportDataOptional. Telegram Passport data
proximity_alert_triggeredProximityAlertTriggeredOptional. Service message. A user in the chat triggered another user's proximity alert while sharing Live Location.
voice_chat_scheduledVoiceChatScheduledOptional. Service message: voice chat scheduled
voice_chat_startedVoiceChatStartedOptional. Service message: voice chat started
voice_chat_endedVoiceChatEndedOptional. Service message: voice chat ended
voice_chat_participants_invitedVoiceChatParticipantsInvitedOptional. Service message: new participants invited to a voice chat
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message. login_url buttons are represented as ordinary url buttons.
+

MessageId

+

This object represents a unique message identifier.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
message_idIntegerUnique message identifier
+

MessageEntity

+

This object represents one special entity in a text message. For example, hashtags, usernames, URLs, etc.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the entity. Currently, can be “mention” (@username), “hashtag” (#hashtag), “cashtag” ($USD), “bot_command” (/start@jobs_bot), “url” (https://telegram.org), “email” (do-not-reply@telegram.org), “phone_number” (+1-212-555-0123), “bold” (bold text), “italic” (italic text), “underline” (underlined text), “strikethrough” (strikethrough text), “spoiler” (spoiler message), “code” (monowidth string), “pre” (monowidth block), “text_link” (for clickable text URLs), “text_mention” (for users without usernames)
offsetIntegerOffset in UTF-16 code units to the start of the entity
lengthIntegerLength of the entity in UTF-16 code units
urlStringOptional. For “text_link” only, url that will be opened after user taps on the text
userUserOptional. For “text_mention” only, the mentioned user
languageStringOptional. For “pre” only, the programming language of the entity text
+

PhotoSize

+

This object represents one size of a photo or a file / sticker thumbnail.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerPhoto width
heightIntegerPhoto height
file_sizeIntegerOptional. File size in bytes
+

Animation

+

This object represents an animation file (GIF or H.264/MPEG-4 AVC video without sound).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerVideo width as defined by sender
heightIntegerVideo height as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Animation thumbnail as defined by sender
file_nameStringOptional. Original animation filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
+

Audio

+

This object represents an audio file to be treated as music by the Telegram clients.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
durationIntegerDuration of the audio in seconds as defined by sender
performerStringOptional. Performer of the audio as defined by sender or by audio tags
titleStringOptional. Title of the audio as defined by sender or by audio tags
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
thumbPhotoSizeOptional. Thumbnail of the album cover to which the music file belongs
+

Document

+

This object represents a general file (as opposed to photos, voice messages and audio files).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
thumbPhotoSizeOptional. Document thumbnail as defined by sender
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
+

Video

+

This object represents a video file.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerVideo width as defined by sender
heightIntegerVideo height as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Video thumbnail
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. Mime type of a file as defined by sender
file_sizeIntegerOptional. File size in bytes
+

VideoNote

+

This object represents a video message (available in Telegram apps as of v.4.0).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
lengthIntegerVideo width and height (diameter of the video message) as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Video thumbnail
file_sizeIntegerOptional. File size in bytes
+

Voice

+

This object represents a voice note.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
durationIntegerDuration of the audio in seconds as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
+

Contact

+

This object represents a phone contact.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
user_idIntegerOptional. Contact's user identifier in Telegram. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
vcardStringOptional. Additional data about the contact in the form of a vCard
+

Dice

+

This object represents an animated emoji that displays a random value.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
emojiStringEmoji on which the dice throw animation is based
valueIntegerValue of the dice, 1-6 for “🎲”, “🎯” and “🎳” base emoji, 1-5 for “🏀” and “⚽” base emoji, 1-64 for “🎰” base emoji
+

PollOption

+

This object contains information about one answer option in a poll.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringOption text, 1-100 characters
voter_countIntegerNumber of users that voted for this option
+

PollAnswer

+

This object represents an answer of a user in a non-anonymous poll.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
poll_idStringUnique poll identifier
userUserThe user, who changed the answer to the poll
option_idsArray of Integer0-based identifiers of answer options, chosen by the user. May be empty if the user retracted their vote.
+

Poll

+

This object contains information about a poll.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique poll identifier
questionStringPoll question, 1-300 characters
optionsArray of PollOptionList of poll options
total_voter_countIntegerTotal number of users that voted in the poll
is_closedBooleanTrue, if the poll is closed
is_anonymousBooleanTrue, if the poll is anonymous
typeStringPoll type, currently can be “regular” or “quiz”
allows_multiple_answersBooleanTrue, if the poll allows multiple answers
correct_option_idIntegerOptional. 0-based identifier of the correct answer option. Available only for polls in the quiz mode, which are closed, or was sent (not forwarded) by the bot or to the private chat with the bot.
explanationStringOptional. Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters
explanation_entitiesArray of MessageEntityOptional. Special entities like usernames, URLs, bot commands, etc. that appear in the explanation
open_periodIntegerOptional. Amount of time in seconds the poll will be active after creation
close_dateIntegerOptional. Point in time (Unix timestamp) when the poll will be automatically closed
+

Location

+

This object represents a point on the map.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
longitudeFloatLongitude as defined by sender
latitudeFloatLatitude as defined by sender
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Time relative to the message sending date, during which the location can be updated; in seconds. For active live locations only.
headingIntegerOptional. The direction in which user is moving, in degrees; 1-360. For active live locations only.
proximity_alert_radiusIntegerOptional. Maximum distance for proximity alerts about approaching another chat member, in meters. For sent live locations only.
+

Venue

+

This object represents a venue.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
locationLocationVenue location. Can't be a live location
titleStringName of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue
foursquare_typeStringOptional. Foursquare type of the venue. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
+

ProximityAlertTriggered

+

This object represents the content of a service message, sent whenever a user in the chat triggers a proximity alert set by another user.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
travelerUserUser that triggered the alert
watcherUserUser that set the alert
distanceIntegerThe distance between the users
+

MessageAutoDeleteTimerChanged

+

This object represents a service message about a change in auto-delete timer settings.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
message_auto_delete_timeIntegerNew auto-delete time for messages in the chat; in seconds
+

VoiceChatScheduled

+

This object represents a service message about a voice chat scheduled in the chat.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
start_dateIntegerPoint in time (Unix timestamp) when the voice chat is supposed to be started by a chat administrator
+

VoiceChatStarted

+

This object represents a service message about a voice chat started in the chat. Currently holds no information.

+

VoiceChatEnded

+

This object represents a service message about a voice chat ended in the chat.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
durationIntegerVoice chat duration in seconds
+

VoiceChatParticipantsInvited

+

This object represents a service message about new members invited to a voice chat.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
usersArray of UserOptional. New members that were invited to the voice chat
+

UserProfilePhotos

+

This object represent a user's profile pictures.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
total_countIntegerTotal number of profile pictures the target user has
photosArray of Array of PhotoSizeRequested profile pictures (in up to 4 sizes each)
+

File

+

This object represents a file ready to be downloaded. The file can be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile.

+
+

Maximum file size to download is 20 MB

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
file_sizeIntegerOptional. File size in bytes, if known
file_pathStringOptional. File path. Use https://api.telegram.org/file/bot<token>/<file_path> to get the file.
+

ReplyKeyboardMarkup

+

This object represents a custom keyboard with reply options (see Introduction to bots for details and examples).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
keyboardArray of Array of KeyboardButtonArray of button rows, each represented by an Array of KeyboardButton objects
resize_keyboardBooleanOptional. Requests clients to resize the keyboard vertically for optimal fit (e.g., make the keyboard smaller if there are just two rows of buttons). Defaults to false, in which case the custom keyboard is always of the same height as the app's standard keyboard.
one_time_keyboardBooleanOptional. Requests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again. Defaults to false.
input_field_placeholderStringOptional. The placeholder to be shown in the input field when the keyboard is active; 1-64 characters
selectiveBooleanOptional. Use this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user requests to change the bot's language, bot replies to the request with a keyboard to select the new language. Other users in the group don't see the keyboard.
+

KeyboardButton

+

This object represents one button of the reply keyboard. For simple text buttons String can be used instead of this object to specify text of the button. Optional fields request_contact, request_location, and request_poll are mutually exclusive.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringText of the button. If none of the optional fields are used, it will be sent as a message when the button is pressed
request_contactBooleanOptional. If True, the user's phone number will be sent as a contact when the button is pressed. Available in private chats only
request_locationBooleanOptional. If True, the user's current location will be sent when the button is pressed. Available in private chats only
request_pollKeyboardButtonPollTypeOptional. If specified, the user will be asked to create a poll and send it to the bot when the button is pressed. Available in private chats only
+

Note: request_contact and request_location options will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.
Note: request_poll option will only work in Telegram versions released after 23 January, 2020. Older clients will display unsupported message.

+

KeyboardButtonPollType

+

This object represents type of a poll, which is allowed to be created and sent when the corresponding button is pressed.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringOptional. If quiz is passed, the user will be allowed to create only polls in the quiz mode. If regular is passed, only regular polls will be allowed. Otherwise, the user will be allowed to create a poll of any type.
+

ReplyKeyboardRemove

+

Upon receiving a message with this object, Telegram clients will remove the current custom keyboard and display the default letter-keyboard. By default, custom keyboards are displayed until a new keyboard is sent by a bot. An exception is made for one-time keyboards that are hidden immediately after the user presses a button (see ReplyKeyboardMarkup).

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
remove_keyboardTrueRequests clients to remove the custom keyboard (user will not be able to summon this keyboard; if you want to hide the keyboard from sight but keep it accessible, use one_time_keyboard in ReplyKeyboardMarkup)
selectiveBooleanOptional. Use this parameter if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet.
+

InlineKeyboardMarkup

+

This object represents an inline keyboard that appears right next to the message it belongs to.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
inline_keyboardArray of Array of InlineKeyboardButtonArray of button rows, each represented by an Array of InlineKeyboardButton objects
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.

+

InlineKeyboardButton

+

This object represents one button of an inline keyboard. You must use exactly one of the optional fields.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringLabel text on the button
urlStringOptional. HTTP or tg:// url to be opened when the button is pressed. Links tg://user?id=<user_id> can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings.
login_urlLoginUrlOptional. An HTTP URL used to automatically authorize the user. Can be used as a replacement for the Telegram Login Widget.
callback_dataStringOptional. Data to be sent in a callback query to the bot when button is pressed, 1-64 bytes
switch_inline_queryStringOptional. If set, pressing the button will prompt the user to select one of their chats, open that chat and insert the bot's username and the specified inline query in the input field. Can be empty, in which case just the bot's username will be inserted.

Note: This offers an easy way for users to start using your bot in inline mode when they are currently in a private chat with it. Especially useful when combined with switch_pm… actions – in this case the user will be automatically returned to the chat they switched from, skipping the chat selection screen.
switch_inline_query_current_chatStringOptional. If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. Can be empty, in which case only the bot's username will be inserted.

This offers a quick way for the user to open your bot in inline mode in the same chat – good for selecting something from multiple options.
callback_gameCallbackGameOptional. Description of the game that will be launched when the user presses the button.

NOTE: This type of button must always be the first button in the first row.
payBooleanOptional. Specify True, to send a Pay button.

NOTE: This type of button must always be the first button in the first row and can only be used in invoice messages.
+

LoginUrl

+

This object represents a parameter of the inline keyboard button used to automatically authorize a user. Serves as a great replacement for the Telegram Login Widget when the user is coming from Telegram. All the user needs to do is tap/click a button and confirm that they want to log in:

+
+ TITLE +
+ +

Telegram apps support these buttons as of version 5.7.

+
+

Sample bot: @discussbot

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
urlStringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
forward_textStringOptional. New text of the button in forwarded messages.
bot_usernameStringOptional. Username of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
request_write_accessBooleanOptional. Pass True to request the permission for your bot to send messages to the user.
+

CallbackQuery

+

This object represents an incoming callback query from a callback button in an inline keyboard. If the button that originated the query was attached to a message sent by the bot, the field message will be present. If the button was attached to a message sent via the bot (in inline mode), the field inline_message_id will be present. Exactly one of the fields data or game_short_name will be present.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique identifier for this query
fromUserSender
messageMessageOptional. Message with the callback button that originated the query. Note that message content and message date will not be available if the message is too old
inline_message_idStringOptional. Identifier of the message sent via the bot in inline mode, that originated the query.
chat_instanceStringGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataStringOptional. Data associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
game_short_nameStringOptional. Short name of a Game to be returned, serves as the unique identifier for the game
+
+

NOTE: After the user presses a callback button, Telegram clients will display a progress bar until you call answerCallbackQuery. It is, therefore, necessary to react by calling answerCallbackQuery even if no notification to the user is needed (e.g., without specifying any of the optional parameters).

+
+

ForceReply

+

Upon receiving a message with this object, Telegram clients will display a reply interface to the user (act as if the user has selected the bot's message and tapped 'Reply'). This can be extremely useful if you want to create user-friendly step-by-step interfaces without having to sacrifice privacy mode.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
force_replyTrueShows reply interface to the user, as if they manually selected the bot's message and tapped 'Reply'
input_field_placeholderStringOptional. The placeholder to be shown in the input field when the reply is active; 1-64 characters
selectiveBooleanOptional. Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
+
+

Example: A poll bot for groups runs in privacy mode (only receives commands, replies to its messages and mentions). There could be two ways to create a new poll:

+
    +
  • Explain the user how to send a command with parameters (e.g. /newpoll question answer1 answer2). May be appealing for hardcore users but lacks modern day polish.
  • +
  • Guide the user through a step-by-step process. 'Please send me your question', 'Cool, now let's add the first answer option', 'Great. Keep adding answer options, then send /done when you're ready'.
  • +
+

The last option is definitely more attractive. And if you use ForceReply in your bot's questions, it will receive the user's answers even if it only receives replies, commands and mentions — without any extra work for the user.

+
+

ChatPhoto

+

This object represents a chat photo.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
small_file_idStringFile identifier of small (160x160) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
small_file_unique_idStringUnique file identifier of small (160x160) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
big_file_idStringFile identifier of big (640x640) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
big_file_unique_idStringUnique file identifier of big (640x640) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
+

ChatInviteLink

+

Represents an invite link for a chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
invite_linkStringThe invite link. If the link was created by another chat administrator, then the second part of the link will be replaced with “…”.
creatorUserCreator of the link
creates_join_requestBooleanTrue, if users joining the chat via the link need to be approved by chat administrators
is_primaryBooleanTrue, if the link is primary
is_revokedBooleanTrue, if the link is revoked
nameStringOptional. Invite link name
expire_dateIntegerOptional. Point in time (Unix timestamp) when the link will expire or has been expired
member_limitIntegerOptional. Maximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
pending_join_request_countIntegerOptional. Number of pending join requests created using this link
+

ChatMember

+

This object contains information about one member of a chat. Currently, the following 6 types of chat members are supported:

+ +

ChatMemberOwner

+

Represents a chat member that owns the chat and has all administrator privileges.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always “creator”
userUserInformation about the user
is_anonymousBooleanTrue, if the user's presence in the chat is hidden
custom_titleStringOptional. Custom title for this user
+

ChatMemberAdministrator

+

Represents a chat member that has some additional privileges.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always “administrator”
userUserInformation about the user
can_be_editedBooleanTrue, if the bot is allowed to edit administrator privileges of that user
is_anonymousBooleanTrue, if the user's presence in the chat is hidden
can_manage_chatBooleanTrue, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
can_delete_messagesBooleanTrue, if the administrator can delete messages of other users
can_manage_voice_chatsBooleanTrue, if the administrator can manage voice chats
can_restrict_membersBooleanTrue, if the administrator can restrict, ban or unban chat members
can_promote_membersBooleanTrue, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by the user)
can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
can_post_messagesBooleanOptional. True, if the administrator can post in the channel; channels only
can_edit_messagesBooleanOptional. True, if the administrator can edit messages of other users and can pin messages; channels only
can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages; groups and supergroups only
custom_titleStringOptional. Custom title for this user
+

ChatMemberMember

+

Represents a chat member that has no additional privileges or restrictions.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always “member”
userUserInformation about the user
+

ChatMemberRestricted

+

Represents a chat member that is under certain restrictions in the chat. Supergroups only.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always “restricted”
userUserInformation about the user
is_memberBooleanTrue, if the user is a member of the chat at the moment of the request
can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
can_pin_messagesBooleanTrue, if the user is allowed to pin messages
can_send_messagesBooleanTrue, if the user is allowed to send text messages, contacts, locations and venues
can_send_media_messagesBooleanTrue, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes
can_send_pollsBooleanTrue, if the user is allowed to send polls
can_send_other_messagesBooleanTrue, if the user is allowed to send animations, games, stickers and use inline bots
can_add_web_page_previewsBooleanTrue, if the user is allowed to add web page previews to their messages
until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is restricted forever
+

ChatMemberLeft

+

Represents a chat member that isn't currently a member of the chat, but may join it themselves.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always “left”
userUserInformation about the user
+

ChatMemberBanned

+

Represents a chat member that was banned in the chat and can't return to the chat or view chat messages.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always “kicked”
userUserInformation about the user
until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is banned forever
+

ChatMemberUpdated

+

This object represents changes in the status of a chat member.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
chatChatChat the user belongs to
fromUserPerformer of the action, which resulted in the change
dateIntegerDate the change was done in Unix time
old_chat_memberChatMemberPrevious information about the chat member
new_chat_memberChatMemberNew information about the chat member
invite_linkChatInviteLinkOptional. Chat invite link, which was used by the user to join the chat; for joining by invite link events only.
+

ChatJoinRequest

+

Represents a join request sent to a chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
chatChatChat to which the request was sent
fromUserUser that sent the join request
dateIntegerDate the request was sent in Unix time
bioStringOptional. Bio of the user.
invite_linkChatInviteLinkOptional. Chat invite link that was used by the user to send the join request
+

ChatPermissions

+

Describes actions that a non-administrator user is allowed to take in a chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
can_send_messagesBooleanOptional. True, if the user is allowed to send text messages, contacts, locations and venues
can_send_media_messagesBooleanOptional. True, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes, implies can_send_messages
can_send_pollsBooleanOptional. True, if the user is allowed to send polls, implies can_send_messages
can_send_other_messagesBooleanOptional. True, if the user is allowed to send animations, games, stickers and use inline bots, implies can_send_media_messages
can_add_web_page_previewsBooleanOptional. True, if the user is allowed to add web page previews to their messages, implies can_send_media_messages
can_change_infoBooleanOptional. True, if the user is allowed to change the chat title, photo and other settings. Ignored in public supergroups
can_invite_usersBooleanOptional. True, if the user is allowed to invite new users to the chat
can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages. Ignored in public supergroups
+

ChatLocation

+

Represents a location to which a chat is connected.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
locationLocationThe location to which the supergroup is connected. Can't be a live location.
addressStringLocation address; 1-64 characters, as defined by the chat owner
+

BotCommand

+

This object represents a bot command.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
commandStringText of the command; 1-32 characters. Can contain only lowercase English letters, digits and underscores.
descriptionStringDescription of the command; 1-256 characters.
+

BotCommandScope

+

This object represents the scope to which bot commands are applied. Currently, the following 7 scopes are supported:

+ +

Determining list of commands

+

The following algorithm is used to determine the list of commands for a particular user viewing the bot menu. The first list of commands which is set is returned:

+

Commands in the chat with the bot

+
    +
  • botCommandScopeChat + language_code
  • +
  • botCommandScopeChat
  • +
  • botCommandScopeAllPrivateChats + language_code
  • +
  • botCommandScopeAllPrivateChats
  • +
  • botCommandScopeDefault + language_code
  • +
  • botCommandScopeDefault
  • +
+

Commands in group and supergroup chats

+
    +
  • botCommandScopeChatMember + language_code
  • +
  • botCommandScopeChatMember
  • +
  • botCommandScopeChatAdministrators + language_code (administrators only)
  • +
  • botCommandScopeChatAdministrators (administrators only)
  • +
  • botCommandScopeChat + language_code
  • +
  • botCommandScopeChat
  • +
  • botCommandScopeAllChatAdministrators + language_code (administrators only)
  • +
  • botCommandScopeAllChatAdministrators (administrators only)
  • +
  • botCommandScopeAllGroupChats + language_code
  • +
  • botCommandScopeAllGroupChats
  • +
  • botCommandScopeDefault + language_code
  • +
  • botCommandScopeDefault
  • +
+

BotCommandScopeDefault

+

Represents the default scope of bot commands. Default commands are used if no commands with a narrower scope are specified for the user.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be default
+

BotCommandScopeAllPrivateChats

+

Represents the scope of bot commands, covering all private chats.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be all_private_chats
+

BotCommandScopeAllGroupChats

+

Represents the scope of bot commands, covering all group and supergroup chats.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be all_group_chats
+

BotCommandScopeAllChatAdministrators

+

Represents the scope of bot commands, covering all group and supergroup chat administrators.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be all_chat_administrators
+

BotCommandScopeChat

+

Represents the scope of bot commands, covering a specific chat.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be chat
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
+

BotCommandScopeChatAdministrators

+

Represents the scope of bot commands, covering all administrators of a specific group or supergroup chat.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be chat_administrators
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
+

BotCommandScopeChatMember

+

Represents the scope of bot commands, covering a specific member of a group or supergroup chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be chat_member
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerUnique identifier of the target user
+

ResponseParameters

+

Contains information about why a request was unsuccessful.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
retry_afterIntegerOptional. In case of exceeding flood control, the number of seconds left to wait before the request can be repeated
+

InputMedia

+

This object represents the content of a media message to be sent. It should be one of

+ +

InputMediaPhoto

+

Represents a photo to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be photo
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
+

InputMediaVideo

+

Represents a video to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be video
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
widthIntegerOptional. Video width
heightIntegerOptional. Video height
durationIntegerOptional. Video duration in seconds
supports_streamingBooleanOptional. Pass True, if the uploaded video is suitable for streaming
+

InputMediaAnimation

+

Represents an animation file (GIF or H.264/MPEG-4 AVC video without sound) to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be animation
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the animation to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the animation caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
widthIntegerOptional. Animation width
heightIntegerOptional. Animation height
durationIntegerOptional. Animation duration in seconds
+

InputMediaAudio

+

Represents an audio file to be treated as music to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be audio
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the audio to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptional. Duration of the audio in seconds
performerStringOptional. Performer of the audio
titleStringOptional. Title of the audio
+

InputMediaDocument

+

Represents a general file to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be document
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
disable_content_type_detectionBooleanOptional. Disables automatic server-side content type detection for files uploaded using multipart/form-data. Always True, if the document is sent as part of an album.
+

InputFile

+

This object represents the contents of a file to be uploaded. Must be posted using multipart/form-data in the usual way that files are uploaded via the browser.

+

Sending files

+

There are three ways to send files (photos, stickers, audio, media, etc.):

+
    +
  1. If the file is already stored somewhere on the Telegram servers, you don't need to reupload it: each file object has a file_id field, simply pass this file_id as a parameter instead of uploading. There are no limits for files sent this way.
  2. +
  3. Provide Telegram with an HTTP URL for the file to be sent. Telegram will download and send the file. 5 MB max size for photos and 20 MB max for other types of content.
  4. +
  5. Post the file using multipart/form-data in the usual way that files are uploaded via the browser. 10 MB max size for photos, 50 MB for other files.
  6. +
+

Sending by file_id

+
    +
  • It is not possible to change the file type when resending by file_id. I.e. a video can't be sent as a photo, a photo can't be sent as a document, etc.
  • +
  • It is not possible to resend thumbnails.
  • +
  • Resending a photo by file_id will send all of its sizes.
  • +
  • file_id is unique for each individual bot and can't be transferred from one bot to another.
  • +
  • file_id uniquely identifies a file, but a file can have different valid file_ids even for the same bot.
  • +
+

Sending by URL

+
    +
  • When sending by URL the target file must have the correct MIME type (e.g., audio/mpeg for sendAudio, etc.).
  • +
  • In sendDocument, sending by URL will currently only work for GIF, PDF and ZIP files.
  • +
  • To use sendVoice, the file must have the type audio/ogg and be no more than 1MB in size. 1-20MB voice notes will be sent as files.
  • +
  • Other configurations may work but we can't guarantee that they will.
  • +
+

Inline mode objects

+

Objects and methods used in the inline mode are described in the Inline mode section.

+

Available methods

+
+

All methods in the Bot API are case-insensitive. We support GET and POST HTTP methods. Use either URL query string or application/json or application/x-www-form-urlencoded or multipart/form-data for passing parameters in Bot API requests.
On successful call, a JSON-object containing the result will be returned.

+
+

getMe

+

A simple method for testing your bot's authentication token. Requires no parameters. Returns basic information about the bot in form of a User object.

+

logOut

+

Use this method to log out from the cloud Bot API server before launching the bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive updates. After a successful call, you can immediately log in on a local server, but will not be able to log in back to the cloud Bot API server for 10 minutes. Returns True on success. Requires no parameters.

+

close

+

Use this method to close the bot instance before moving it from one local server to another. You need to delete the webhook before calling this method to ensure that the bot isn't launched again after server restart. The method will return error 429 in the first 10 minutes after the bot is launched. Returns True on success. Requires no parameters.

+

sendMessage

+

Use this method to send text messages. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
textStringYesText of the message to be sent, 1-4096 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptionalDisables link previews for links in this message
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

Formatting options

+

The Bot API supports basic formatting for messages. You can use bold, italic, underlined, strikethrough, and spoiler text, as well as inline links and pre-formatted code in your bots' messages. Telegram clients will render them accordingly. You can use either markdown-style or HTML-style formatting.

+

Note that Telegram clients will display an alert to the user before opening an inline link ('Open this link?' together with the full URL).

+

Message entities can be nested, providing following restrictions are met:
- If two entities have common characters then one of them is fully contained inside another.
- bold, italic, underline, strikethrough, and spoiler entities can contain and can be part of any other entities, except pre and code.
- All other entities can't contain each other.

+

Links tg://user?id=<user_id> can be used to mention a user by their ID without using a username. Please note:

+
    +
  • These links will work only if they are used inside an inline link or in an inline keyboard button. For example, they will not work, when used in a message text.
  • +
  • These mentions are only guaranteed to work if the user has contacted the bot in the past, has sent a callback query to the bot via an inline button or is a member in the group where he was mentioned.
  • +
+
MarkdownV2 style
+

To use this mode, pass MarkdownV2 in the parse_mode field. Use the following syntax in your message:

+
*bold \*text*
+_italic \*text_
+__underline__
+~strikethrough~
+||spoiler||
+*bold _italic bold ~italic bold strikethrough ||italic bold strikethrough spoiler||~ __underline italic bold___ bold*
+[inline URL](http://www.example.com/)
+[inline mention of a user](tg://user?id=123456789)
+`inline fixed-width code`
+```
+pre-formatted fixed-width code block
+```
+```python
+pre-formatted fixed-width code block written in the Python programming language
+```
+

Please note:

+
    +
  • Any character with code between 1 and 126 inclusively can be escaped anywhere with a preceding '\' character, in which case it is treated as an ordinary character and not a part of the markup. This implies that '\' character usually must be escaped with a preceding '\' character.
  • +
  • Inside pre and code entities, all '`' and '\' characters must be escaped with a preceding '\' character.
  • +
  • Inside (...) part of inline link definition, all ')' and '\' must be escaped with a preceding '\' character.
  • +
  • In all other places characters '_', '*', '[', ']', '(', ')', '~', '`', '>', '#', '+', '-', '=', '|', '{', '}', '.', '!' must be escaped with the preceding character '\'.
  • +
  • In case of ambiguity between italic and underline entities __ is always greadily treated from left to right as beginning or end of underline entity, so instead of ___italic underline___ use ___italic underline_\r__, where \r is a character with code 13, which will be ignored.
  • +
+
HTML style
+

To use this mode, pass HTML in the parse_mode field. The following tags are currently supported:

+
<b>bold</b>, <strong>bold</strong>
+<i>italic</i>, <em>italic</em>
+<u>underline</u>, <ins>underline</ins>
+<s>strikethrough</s>, <strike>strikethrough</strike>, <del>strikethrough</del>
+<span class="tg-spoiler">spoiler</span>, <tg-spoiler>spoiler</tg-spoiler>
+<b>bold <i>italic bold <s>italic bold strikethrough <span class="tg-spoiler">italic bold strikethrough spoiler</span></s> <u>underline italic bold</u></i> bold</b>
+<a href="http://www.example.com/">inline URL</a>
+<a href="tg://user?id=123456789">inline mention of a user</a>
+<code>inline fixed-width code</code>
+<pre>pre-formatted fixed-width code block</pre>
+<pre><code class="language-python">pre-formatted fixed-width code block written in the Python programming language</code></pre>
+

Please note:

+
    +
  • Only the tags mentioned above are currently supported.
  • +
  • All <, > and & symbols that are not a part of a tag or an HTML entity must be replaced with the corresponding HTML entities (< with &lt;, > with &gt; and & with &amp;).
  • +
  • All numerical HTML entities are supported.
  • +
  • The API currently supports only the following named HTML entities: &lt;, &gt;, &amp; and &quot;.
  • +
  • Use nested pre and code tags, to define programming language for pre entity.
  • +
  • Programming language can't be specified for standalone code tags.
  • +
+
Markdown style
+

This is a legacy mode, retained for backward compatibility. To use this mode, pass Markdown in the parse_mode field. Use the following syntax in your message:

+
*bold text*
+_italic text_
+[inline URL](http://www.example.com/)
+[inline mention of a user](tg://user?id=123456789)
+`inline fixed-width code`
+```
+pre-formatted fixed-width code block
+```
+```python
+pre-formatted fixed-width code block written in the Python programming language
+```
+

Please note:

+
    +
  • Entities must not be nested, use parse mode MarkdownV2 instead.
  • +
  • There is no way to specify underline and strikethrough entities, use parse mode MarkdownV2 instead.
  • +
  • To escape characters '_', '*', '`', '[' outside of an entity, prepend the characters '\' before them.
  • +
  • Escaping inside entities is not allowed, so entity must be closed first and reopened again: use _snake_\__case_ for italic snake_case and *2*\**2=4* for bold 2*2=4.
  • +
+

forwardMessage

+

Use this method to forward messages of any kind. Service messages can't be forwarded. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the forwarded message from forwarding and saving
message_idIntegerYesMessage identifier in the chat specified in from_chat_id
+

copyMessage

+

Use this method to copy messages of any kind. Service messages and invoice messages can't be copied. The method is analogous to the method forwardMessage, but the copied message doesn't have a link to the original message. Returns the MessageId of the sent message on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
message_idIntegerYesMessage identifier in the chat specified in from_chat_id
captionStringOptionalNew caption for media, 0-1024 characters after entities parsing. If not specified, the original caption is kept
parse_modeStringOptionalMode for parsing entities in the new caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the new caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendPhoto

+

Use this method to send photos. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
photoInputFile or StringYesPhoto to send. Pass a file_id as String to send a photo that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a photo from the Internet, or upload a new photo using multipart/form-data. The photo must be at most 10 MB in size. The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20. More info on Sending Files »
captionStringOptionalPhoto caption (may also be used when resending photos by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendAudio

+

Use this method to send audio files, if you want Telegram clients to display them in the music player. Your audio must be in the .MP3 or .M4A format. On success, the sent Message is returned. Bots can currently send audio files of up to 50 MB in size, this limit may be changed in the future.

+

For sending voice messages, use the sendVoice method instead.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
audioInputFile or StringYesAudio file to send. Pass a file_id as String to send an audio file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an audio file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
captionStringOptionalAudio caption, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptionalDuration of the audio in seconds
performerStringOptionalPerformer
titleStringOptionalTrack name
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendDocument

+

Use this method to send general files. On success, the sent Message is returned. Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
documentInputFile or StringYesFile to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalDocument caption (may also be used when resending documents by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_content_type_detectionBooleanOptionalDisables automatic server-side content type detection for files uploaded using multipart/form-data
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendVideo

+

Use this method to send video files, Telegram clients support mp4 videos (other formats may be sent as Document). On success, the sent Message is returned. Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
videoInputFile or StringYesVideo to send. Pass a file_id as String to send a video that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a video from the Internet, or upload a new video using multipart/form-data. More info on Sending Files »
durationIntegerOptionalDuration of sent video in seconds
widthIntegerOptionalVideo width
heightIntegerOptionalVideo height
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalVideo caption (may also be used when resending videos by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
supports_streamingBooleanOptionalPass True, if the uploaded video is suitable for streaming
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendAnimation

+

Use this method to send animation files (GIF or H.264/MPEG-4 AVC video without sound). On success, the sent Message is returned. Bots can currently send animation files of up to 50 MB in size, this limit may be changed in the future.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
animationInputFile or StringYesAnimation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an animation from the Internet, or upload a new animation using multipart/form-data. More info on Sending Files »
durationIntegerOptionalDuration of sent animation in seconds
widthIntegerOptionalAnimation width
heightIntegerOptionalAnimation height
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalAnimation caption (may also be used when resending animation by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the animation caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendVoice

+

Use this method to send audio files, if you want Telegram clients to display the file as a playable voice message. For this to work, your audio must be in an .OGG file encoded with OPUS (other formats may be sent as Audio or Document). On success, the sent Message is returned. Bots can currently send voice messages of up to 50 MB in size, this limit may be changed in the future.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
voiceInputFile or StringYesAudio file to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
captionStringOptionalVoice message caption, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptionalDuration of the voice message in seconds
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendVideoNote

+

As of v.4.0, Telegram clients support rounded square mp4 videos of up to 1 minute long. Use this method to send video messages. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
video_noteInputFile or StringYesVideo note to send. Pass a file_id as String to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. More info on Sending Files ». Sending video notes by a URL is currently unsupported
durationIntegerOptionalDuration of sent video in seconds
lengthIntegerOptionalVideo width and height, i.e. diameter of the video message
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendMediaGroup

+

Use this method to send a group of photos, videos, documents or audios as an album. Documents and audio files can be only grouped in an album with messages of the same type. On success, an array of Messages that were sent is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
mediaArray of InputMediaAudio, InputMediaDocument, InputMediaPhoto and InputMediaVideoYesA JSON-serialized array describing messages to be sent, must include 2-10 items
disable_notificationBooleanOptionalSends messages silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent messages from forwarding and saving
reply_to_message_idIntegerOptionalIf the messages are a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
+

sendLocation

+

Use this method to send point on the map. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
latitudeFloat numberYesLatitude of the location
longitudeFloat numberYesLongitude of the location
horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptionalPeriod in seconds for which the location will be updated (see Live Locations, should be between 60 and 86400.
headingIntegerOptionalFor live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptionalFor live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

editMessageLiveLocation

+

Use this method to edit live location messages. A location can be edited until its live_period expires or editing is explicitly disabled by a call to stopMessageLiveLocation. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
latitudeFloat numberYesLatitude of new location
longitudeFloat numberYesLongitude of new location
horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
headingIntegerOptionalDirection in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptionalMaximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
+

stopMessageLiveLocation

+

Use this method to stop updating a live location message before live_period expires. On success, if the message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message with live location to stop
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
+

sendVenue

+

Use this method to send information about a venue. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
latitudeFloat numberYesLatitude of the venue
longitudeFloat numberYesLongitude of the venue
titleStringYesName of the venue
addressStringYesAddress of the venue
foursquare_idStringOptionalFoursquare identifier of the venue
foursquare_typeStringOptionalFoursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
google_place_idStringOptionalGoogle Places identifier of the venue
google_place_typeStringOptionalGoogle Places type of the venue. (See supported types.)
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendContact

+

Use this method to send phone contacts. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
phone_numberStringYesContact's phone number
first_nameStringYesContact's first name
last_nameStringOptionalContact's last name
vcardStringOptionalAdditional data about the contact in the form of a vCard, 0-2048 bytes
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove keyboard or to force a reply from the user.
+

sendPoll

+

Use this method to send a native poll. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
questionStringYesPoll question, 1-300 characters
optionsArray of StringYesA JSON-serialized list of answer options, 2-10 strings 1-100 characters each
is_anonymousBooleanOptionalTrue, if the poll needs to be anonymous, defaults to True
typeStringOptionalPoll type, “quiz” or “regular”, defaults to “regular”
allows_multiple_answersBooleanOptionalTrue, if the poll allows multiple answers, ignored for polls in quiz mode, defaults to False
correct_option_idIntegerOptional0-based identifier of the correct answer option, required for polls in quiz mode
explanationStringOptionalText that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds after entities parsing
explanation_parse_modeStringOptionalMode for parsing entities in the explanation. See formatting options for more details.
explanation_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the poll explanation, which can be specified instead of parse_mode
open_periodIntegerOptionalAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateIntegerOptionalPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future. Can't be used together with open_period.
is_closedBooleanOptionalPass True, if the poll needs to be immediately closed. This can be useful for poll preview.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendDice

+

Use this method to send an animated emoji that will display a random value. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
emojiStringOptionalEmoji on which the dice throw animation is based. Currently, must be one of “🎲”, “🎯”, “🏀”, “⚽”, “🎳”, or “🎰”. Dice can have values 1-6 for “🎲”, “🎯” and “🎳”, values 1-5 for “🏀” and “⚽”, and values 1-64 for “🎰”. Defaults to “🎲
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendChatAction

+

Use this method when you need to tell the user that something is happening on the bot's side. The status is set for 5 seconds or less (when a message arrives from your bot, Telegram clients clear its typing status). Returns True on success.

+
+

Example: The ImageBot needs some time to process a request and upload the image. Instead of sending a text message along the lines of “Retrieving image, please wait…”, the bot may use sendChatAction with action = upload_photo. The user will see a “sending photo” status for the bot.

+
+

We only recommend using this method when a response from the bot will take a noticeable amount of time to arrive.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
actionStringYesType of action to broadcast. Choose one, depending on what the user is about to receive: typing for text messages, upload_photo for photos, record_video or upload_video for videos, record_voice or upload_voice for voice notes, upload_document for general files, choose_sticker for stickers, find_location for location data, record_video_note or upload_video_note for video notes.
+

getUserProfilePhotos

+

Use this method to get a list of profile pictures for a user. Returns a UserProfilePhotos object.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUnique identifier of the target user
offsetIntegerOptionalSequential number of the first photo to be returned. By default, all photos are returned.
limitIntegerOptionalLimits the number of photos to be retrieved. Values between 1-100 are accepted. Defaults to 100.
+

getFile

+

Use this method to get basic info about a file and prepare it for downloading. For the moment, bots can download files of up to 20MB in size. On success, a File object is returned. The file can then be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>, where <file_path> is taken from the response. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile again.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
file_idStringYesFile identifier to get info about
+

Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type and name (if available) when the File object is received.

+

banChatMember

+

Use this method to ban a user in a group, a supergroup or a channel. In the case of supergroups and channels, the user will not be able to return to the chat on their own using invite links, etc., unless unbanned first. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
until_dateIntegerOptionalDate when the user will be unbanned, unix time. If user is banned for more than 366 days or less than 30 seconds from the current time they are considered to be banned forever. Applied for supergroups and channels only.
revoke_messagesBooleanOptionalPass True to delete all messages from the chat for the user that is being removed. If False, the user will be able to see messages in the group that were sent before the user was removed. Always True for supergroups and channels.
+

unbanChatMember

+

Use this method to unban a previously banned user in a supergroup or channel. The user will not return to the group or channel automatically, but will be able to join via link, etc. The bot must be an administrator for this to work. By default, this method guarantees that after the call the user is not a member of the chat, but will be able to join it. So if the user is a member of the chat they will also be removed from the chat. If you don't want this, use the parameter only_if_banned. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
only_if_bannedBooleanOptionalDo nothing if the user is not banned
+

restrictChatMember

+

Use this method to restrict a user in a supergroup. The bot must be an administrator in the supergroup for this to work and must have the appropriate administrator rights. Pass True for all permissions to lift restrictions from a user. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerYesUnique identifier of the target user
permissionsChatPermissionsYesA JSON-serialized object for new user permissions
until_dateIntegerOptionalDate when restrictions will be lifted for the user, unix time. If user is restricted for more than 366 days or less than 30 seconds from the current time, they are considered to be restricted forever
+

promoteChatMember

+

Use this method to promote or demote a user in a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Pass False for all boolean parameters to demote a user. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
is_anonymousBooleanOptionalPass True, if the administrator's presence in the chat is hidden
can_manage_chatBooleanOptionalPass True, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
can_post_messagesBooleanOptionalPass True, if the administrator can create channel posts, channels only
can_edit_messagesBooleanOptionalPass True, if the administrator can edit messages of other users and can pin messages, channels only
can_delete_messagesBooleanOptionalPass True, if the administrator can delete messages of other users
can_manage_voice_chatsBooleanOptionalPass True, if the administrator can manage voice chats
can_restrict_membersBooleanOptionalPass True, if the administrator can restrict, ban or unban chat members
can_promote_membersBooleanOptionalPass True, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by him)
can_change_infoBooleanOptionalPass True, if the administrator can change chat title, photo and other settings
can_invite_usersBooleanOptionalPass True, if the administrator can invite new users to the chat
can_pin_messagesBooleanOptionalPass True, if the administrator can pin messages, supergroups only
+

setChatAdministratorCustomTitle

+

Use this method to set a custom title for an administrator in a supergroup promoted by the bot. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerYesUnique identifier of the target user
custom_titleStringYesNew custom title for the administrator; 0-16 characters, emoji are not allowed
+

banChatSenderChat

+

Use this method to ban a channel chat in a supergroup or a channel. Until the chat is unbanned, the owner of the banned chat won't be able to send messages on behalf of any of their channels. The bot must be an administrator in the supergroup or channel for this to work and must have the appropriate administrator rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
sender_chat_idIntegerYesUnique identifier of the target sender chat
+

unbanChatSenderChat

+

Use this method to unban a previously banned channel chat in a supergroup or channel. The bot must be an administrator for this to work and must have the appropriate administrator rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
sender_chat_idIntegerYesUnique identifier of the target sender chat
+

setChatPermissions

+

Use this method to set default chat permissions for all members. The bot must be an administrator in the group or a supergroup for this to work and must have the can_restrict_members administrator rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
permissionsChatPermissionsYesA JSON-serialized object for new default chat permissions
+

exportChatInviteLink

+

Use this method to generate a new primary invite link for a chat; any previously generated primary link is revoked. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the new invite link as String on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
+
+

Note: Each administrator in a chat generates their own invite links. Bots can't use invite links generated by other administrators. If you want your bot to work with invite links, it will need to generate its own link using exportChatInviteLink or by calling the getChat method. If your bot needs to generate a new primary invite link replacing its previous one, use exportChatInviteLink again.

+
+

createChatInviteLink

+

Use this method to create an additional invite link for a chat. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. The link can be revoked using the method revokeChatInviteLink. Returns the new invite link as ChatInviteLink object.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
nameStringOptionalInvite link name; 0-32 characters
expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
creates_join_requestBooleanOptionalTrue, if users joining the chat via the link need to be approved by chat administrators. If True, member_limit can't be specified
+

editChatInviteLink

+

Use this method to edit a non-primary invite link created by the bot. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the edited invite link as a ChatInviteLink object.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
invite_linkStringYesThe invite link to edit
nameStringOptionalInvite link name; 0-32 characters
expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
creates_join_requestBooleanOptionalTrue, if users joining the chat via the link need to be approved by chat administrators. If True, member_limit can't be specified
+

revokeChatInviteLink

+

Use this method to revoke an invite link created by the bot. If the primary link is revoked, a new link is automatically generated. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the revoked invite link as ChatInviteLink object.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier of the target chat or username of the target channel (in the format @channelusername)
invite_linkStringYesThe invite link to revoke
+

approveChatJoinRequest

+

Use this method to approve a chat join request. The bot must be an administrator in the chat for this to work and must have the can_invite_users administrator right. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
+

declineChatJoinRequest

+

Use this method to decline a chat join request. The bot must be an administrator in the chat for this to work and must have the can_invite_users administrator right. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
+

setChatPhoto

+

Use this method to set a new profile photo for the chat. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
photoInputFileYesNew chat photo, uploaded using multipart/form-data
+

deleteChatPhoto

+

Use this method to delete a chat photo. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
+

setChatTitle

+

Use this method to change the title of a chat. Titles can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
titleStringYesNew chat title, 1-255 characters
+

setChatDescription

+

Use this method to change the description of a group, a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
descriptionStringOptionalNew chat description, 0-255 characters
+

pinChatMessage

+

Use this method to add a message to the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of a message to pin
disable_notificationBooleanOptionalPass True, if it is not necessary to send a notification to all chat members about the new pinned message. Notifications are always disabled in channels and private chats.
+

unpinChatMessage

+

Use this method to remove a message from the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalIdentifier of a message to unpin. If not specified, the most recent pinned message (by sending date) will be unpinned.
+

unpinAllChatMessages

+

Use this method to clear the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
+

leaveChat

+

Use this method for your bot to leave a group, supergroup or channel. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
+

getChat

+

Use this method to get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.). Returns a Chat object on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
+

getChatAdministrators

+

Use this method to get a list of administrators in a chat. On success, returns an Array of ChatMember objects that contains information about all chat administrators except other bots. If the chat is a group or a supergroup and no administrators were appointed, only the creator will be returned.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
+

getChatMemberCount

+

Use this method to get the number of members in a chat. Returns Int on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
+

getChatMember

+

Use this method to get information about a member of a chat. Returns a ChatMember object on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
+

setChatStickerSet

+

Use this method to set a new group sticker set for a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
sticker_set_nameStringYesName of the sticker set to be set as the group sticker set
+

deleteChatStickerSet

+

Use this method to delete a group sticker set from a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
+

answerCallbackQuery

+

Use this method to send answers to callback queries sent from inline keyboards. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. On success, True is returned.

+
+

Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via @Botfather and accept the terms. Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
callback_query_idStringYesUnique identifier for the query to be answered
textStringOptionalText of the notification. If not specified, nothing will be shown to the user, 0-200 characters
show_alertBooleanOptionalIf True, an alert will be shown by the client instead of a notification at the top of the chat screen. Defaults to false.
urlStringOptionalURL that will be opened by the user's client. If you have created a Game and accepted the conditions via @Botfather, specify the URL that opens your game — note that this will only work if the query comes from a callback_game button.

Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.
cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the callback query may be cached client-side. Telegram apps will support caching starting in version 3.14. Defaults to 0.
+

setMyCommands

+

Use this method to change the list of the bot's commands. See https://core.telegram.org/bots#commands for more details about bot commands. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
commandsArray of BotCommandYesA JSON-serialized list of bot commands to be set as the list of the bot's commands. At most 100 commands can be specified.
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
+

deleteMyCommands

+

Use this method to delete the list of the bot's commands for the given scope and user language. After deletion, higher level commands will be shown to affected users. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
+

getMyCommands

+

Use this method to get the current list of the bot's commands for the given scope and user language. Returns Array of BotCommand on success. If commands aren't set, an empty list is returned.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code or an empty string
+

Inline mode methods

+

Methods and objects used in the inline mode are described in the Inline mode section.

+

Updating messages

+

The following methods allow you to change an existing message in the message history instead of sending a new one with a result of an action. This is most useful for messages with inline keyboards using callback queries, but can also help reduce clutter in conversations with regular chat bots.

+

Please note, that it is currently only possible to edit messages without reply_markup or with inline keyboards.

+

editMessageText

+

Use this method to edit text and game messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
textStringYesNew text of the message, 1-4096 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptionalDisables link previews for links in this message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
+

editMessageCaption

+

Use this method to edit captions of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
captionStringOptionalNew caption of the message, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
+

editMessageMedia

+

Use this method to edit animation, audio, document, photo, or video messages. If a message is part of a message album, then it can be edited only to an audio for audio albums, only to a document for document albums and to a photo or a video otherwise. When an inline message is edited, a new file can't be uploaded; use a previously uploaded file via its file_id or specify a URL. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
mediaInputMediaYesA JSON-serialized object for a new media content of the message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
+

editMessageReplyMarkup

+

Use this method to edit only the reply markup of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
+

stopPoll

+

Use this method to stop a poll which was sent by the bot. On success, the stopped Poll is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of the original message with the poll
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new message inline keyboard.
+

deleteMessage

+

Use this method to delete a message, including service messages, with the following limitations:
- A message can only be deleted if it was sent less than 48 hours ago.
- A dice message in a private chat can only be deleted if it was sent more than 24 hours ago.
- Bots can delete outgoing messages in private chats, groups, and supergroups.
- Bots can delete incoming messages in private chats.
- Bots granted can_post_messages permissions can delete outgoing messages in channels.
- If the bot is an administrator of a group, it can delete any message there.
- If the bot has can_delete_messages permission in a supergroup or a channel, it can delete any message there.
Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of the message to delete
+

Stickers

+

The following methods and objects allow your bot to handle stickers and sticker sets.

+

Sticker

+

This object represents a sticker.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerSticker width
heightIntegerSticker height
is_animatedBooleanTrue, if the sticker is animated
is_videoBooleanTrue, if the sticker is a video sticker
thumbPhotoSizeOptional. Sticker thumbnail in the .WEBP or .JPG format
emojiStringOptional. Emoji associated with the sticker
set_nameStringOptional. Name of the sticker set to which the sticker belongs
mask_positionMaskPositionOptional. For mask stickers, the position where the mask should be placed
file_sizeIntegerOptional. File size in bytes
+

StickerSet

+

This object represents a sticker set.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
nameStringSticker set name
titleStringSticker set title
is_animatedBooleanTrue, if the sticker set contains animated stickers
is_videoBooleanTrue, if the sticker set contains video stickers
contains_masksBooleanTrue, if the sticker set contains masks
stickersArray of StickerList of all set stickers
thumbPhotoSizeOptional. Sticker set thumbnail in the .WEBP, .TGS, or .WEBM format
+

MaskPosition

+

This object describes the position on faces where a mask should be placed by default.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
pointStringThe part of the face relative to which the mask should be placed. One of “forehead”, “eyes”, “mouth”, or “chin”.
x_shiftFloat numberShift by X-axis measured in widths of the mask scaled to the face size, from left to right. For example, choosing -1.0 will place mask just to the left of the default mask position.
y_shiftFloat numberShift by Y-axis measured in heights of the mask scaled to the face size, from top to bottom. For example, 1.0 will place the mask just below the default mask position.
scaleFloat numberMask scaling coefficient. For example, 2.0 means double size.
+

sendSticker

+

Use this method to send static .WEBP, animated .TGS, or video .WEBM stickers. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
stickerInputFile or StringYesSticker to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a .WEBP file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

getStickerSet

+

Use this method to get a sticker set. On success, a StickerSet object is returned.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
nameStringYesName of the sticker set
+

uploadStickerFile

+

Use this method to upload a .PNG file with a sticker for later use in createNewStickerSet and addStickerToSet methods (can be used multiple times). Returns the uploaded File on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of sticker file owner
png_stickerInputFileYesPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. More info on Sending Files »
+

createNewStickerSet

+

Use this method to create a new sticker set owned by a user. The bot will be able to edit the sticker set thus created. You must use exactly one of the fields png_sticker, tgs_sticker, or webm_sticker. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of created sticker set owner
nameStringYesShort name of sticker set, to be used in t.me/addstickers/ URLs (e.g., animals). Can contain only english letters, digits and underscores. Must begin with a letter, can't contain consecutive underscores and must end in “_by_<bot username>”. <bot_username> is case insensitive. 1-64 characters.
titleStringYesSticker set title, 1-64 characters
png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#animated-sticker-requirements for technical requirements
webm_stickerInputFileOptionalWEBM video with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#video-sticker-requirements for technical requirements
emojisStringYesOne or more emoji corresponding to the sticker
contains_masksBooleanOptionalPass True, if a set of mask stickers should be created
mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
+

addStickerToSet

+

Use this method to add a new sticker to a set created by the bot. You must use exactly one of the fields png_sticker, tgs_sticker, or webm_sticker. Animated stickers can be added to animated sticker sets and only to them. Animated sticker sets can have up to 50 stickers. Static sticker sets can have up to 120 stickers. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of sticker set owner
nameStringYesSticker set name
png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#animated-sticker-requirements for technical requirements
webm_stickerInputFileOptionalWEBM video with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#video-sticker-requirements for technical requirements
emojisStringYesOne or more emoji corresponding to the sticker
mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
+

setStickerPositionInSet

+

Use this method to move a sticker in a set created by the bot to a specific position. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
stickerStringYesFile identifier of the sticker
positionIntegerYesNew sticker position in the set, zero-based
+

deleteStickerFromSet

+

Use this method to delete a sticker from a set created by the bot. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
stickerStringYesFile identifier of the sticker
+

setStickerSetThumb

+

Use this method to set the thumbnail of a sticker set. Animated thumbnails can be set for animated sticker sets only. Video thumbnails can be set only for video sticker sets only. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
nameStringYesSticker set name
user_idIntegerYesUser identifier of the sticker set owner
thumbInputFile or StringOptionalA PNG image with the thumbnail, must be up to 128 kilobytes in size and have width and height exactly 100px, or a TGS animation with the thumbnail up to 32 kilobytes in size; see https://core.telegram.org/stickers#animated-sticker-requirements for animated sticker technical requirements, or a WEBM video with the thumbnail up to 32 kilobytes in size; see https://core.telegram.org/stickers#video-sticker-requirements for video sticker technical requirements. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files ». Animated sticker set thumbnails can't be uploaded via HTTP URL.
+

Inline mode

+

The following methods and objects allow your bot to work in inline mode.
Please see our Introduction to Inline bots for more details.

+

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot's name.

+

InlineQuery

+

This object represents an incoming inline query. When the user sends an empty query, your bot could return some default or trending results.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique identifier for this query
fromUserSender
queryStringText of the query (up to 256 characters)
offsetStringOffset of the results to be returned, can be controlled by the bot
chat_typeStringOptional. Type of the chat, from which the inline query was sent. Can be either “sender” for a private chat with the inline query sender, “private”, “group”, “supergroup”, or “channel”. The chat type should be always known for requests sent from official clients and most third-party clients, unless the request was sent from a secret chat
locationLocationOptional. Sender location, only for bots that request user location
+

answerInlineQuery

+

Use this method to send answers to an inline query. On success, True is returned.
No more than 50 results per query are allowed.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
inline_query_idStringYesUnique identifier for the answered query
resultsArray of InlineQueryResultYesA JSON-serialized array of results for the inline query
cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
is_personalBooleanOptionalPass True, if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
next_offsetStringOptionalPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don't support pagination. Offset length can't exceed 64 bytes.
switch_pm_textStringOptionalIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with the parameter switch_pm_parameter
switch_pm_parameterStringOptionalDeep-linking parameter for the /start message sent to the bot when user presses the switch button. 1-64 characters, only A-Z, a-z, 0-9, _ and - are allowed.

Example: An inline bot that sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even before showing any. The user presses the button, switches to a private chat with the bot and, in doing so, passes a start parameter that instructs the bot to return an OAuth link. Once done, the bot can offer a switch_inline button so that the user can easily return to the chat where they wanted to use the bot's inline capabilities.
+

InlineQueryResult

+

This object represents one result of an inline query. Telegram clients currently support results of the following 20 types:

+ +

Note: All URLs passed in inline query results will be available to end users and therefore must be assumed to be public.

+

InlineQueryResultArticle

+

Represents a link to an article or web page.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be article
idStringUnique identifier for this result, 1-64 Bytes
titleStringTitle of the result
input_message_contentInputMessageContentContent of the message to be sent
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
urlStringOptional. URL of the result
hide_urlBooleanOptional. Pass True, if you don't want the URL to be shown in the message
descriptionStringOptional. Short description of the result
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

InlineQueryResultPhoto

+

Represents a link to a photo. By default, this photo will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be photo
idStringUnique identifier for this result, 1-64 bytes
photo_urlStringA valid URL of the photo. Photo must be in JPEG format. Photo size must not exceed 5MB
thumb_urlStringURL of the thumbnail for the photo
photo_widthIntegerOptional. Width of the photo
photo_heightIntegerOptional. Height of the photo
titleStringOptional. Title for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
+

InlineQueryResultGif

+

Represents a link to an animated GIF file. By default, this animated GIF file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be gif
idStringUnique identifier for this result, 1-64 bytes
gif_urlStringA valid URL for the GIF file. File size must not exceed 1MB
gif_widthIntegerOptional. Width of the GIF
gif_heightIntegerOptional. Height of the GIF
gif_durationIntegerOptional. Duration of the GIF in seconds
thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of “image/jpeg”, “image/gif”, or “video/mp4”. Defaults to “image/jpeg”
titleStringOptional. Title for the result
captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
+

InlineQueryResultMpeg4Gif

+

Represents a link to a video animation (H.264/MPEG-4 AVC video without sound). By default, this animated MPEG-4 file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be mpeg4_gif
idStringUnique identifier for this result, 1-64 bytes
mpeg4_urlStringA valid URL for the MP4 file. File size must not exceed 1MB
mpeg4_widthIntegerOptional. Video width
mpeg4_heightIntegerOptional. Video height
mpeg4_durationIntegerOptional. Video duration in seconds
thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of “image/jpeg”, “image/gif”, or “video/mp4”. Defaults to “image/jpeg”
titleStringOptional. Title for the result
captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
+

InlineQueryResultVideo

+

Represents a link to a page containing an embedded video player or a video file. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

+
+

If an InlineQueryResultVideo message contains an embedded video (e.g., YouTube), you must replace its content using input_message_content.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be video
idStringUnique identifier for this result, 1-64 bytes
video_urlStringA valid URL for the embedded video player or video file
mime_typeStringMime type of the content of video url, “text/html” or “video/mp4”
thumb_urlStringURL of the thumbnail (JPEG only) for the video
titleStringTitle for the result
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
video_widthIntegerOptional. Video width
video_heightIntegerOptional. Video height
video_durationIntegerOptional. Video duration in seconds
descriptionStringOptional. Short description of the result
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video. This field is required if InlineQueryResultVideo is used to send an HTML-page as a result (e.g., a YouTube video).
+

InlineQueryResultAudio

+

Represents a link to an MP3 audio file. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be audio
idStringUnique identifier for this result, 1-64 bytes
audio_urlStringA valid URL for the audio file
titleStringTitle
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
performerStringOptional. Performer
audio_durationIntegerOptional. Audio duration in seconds
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultVoice

+

Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be voice
idStringUnique identifier for this result, 1-64 bytes
voice_urlStringA valid URL for the voice recording
titleStringRecording title
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
voice_durationIntegerOptional. Recording duration in seconds
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice recording
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultDocument

+

Represents a link to a file. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. Currently, only .PDF and .ZIP files can be sent using this method.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be document
idStringUnique identifier for this result, 1-64 bytes
titleStringTitle for the result
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
document_urlStringA valid URL for the file
mime_typeStringMime type of the content of the file, either “application/pdf” or “application/zip”
descriptionStringOptional. Short description of the result
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
thumb_urlStringOptional. URL of the thumbnail (JPEG only) for the file
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultLocation

+

Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be location
idStringUnique identifier for this result, 1-64 Bytes
latitudeFloat numberLocation latitude in degrees
longitudeFloat numberLocation longitude in degrees
titleStringLocation title
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the location
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultVenue

+

Represents a venue. By default, the venue will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the venue.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be venue
idStringUnique identifier for this result, 1-64 Bytes
latitudeFloatLatitude of the venue location in degrees
longitudeFloatLongitude of the venue location in degrees
titleStringTitle of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue if known
foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the venue
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultContact

+

Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be contact
idStringUnique identifier for this result, 1-64 Bytes
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the contact
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultGame

+

Represents a Game.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be game
idStringUnique identifier for this result, 1-64 bytes
game_short_nameStringShort name of the game
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
+

Note: This will only work in Telegram versions released after October 1, 2016. Older clients will not display any inline results if a game result is among them.

+

InlineQueryResultCachedPhoto

+

Represents a link to a photo stored on the Telegram servers. By default, this photo will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be photo
idStringUnique identifier for this result, 1-64 bytes
photo_file_idStringA valid file identifier of the photo
titleStringOptional. Title for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
+

InlineQueryResultCachedGif

+

Represents a link to an animated GIF file stored on the Telegram servers. By default, this animated GIF file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with specified content instead of the animation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be gif
idStringUnique identifier for this result, 1-64 bytes
gif_file_idStringA valid file identifier for the GIF file
titleStringOptional. Title for the result
captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
+

InlineQueryResultCachedMpeg4Gif

+

Represents a link to a video animation (H.264/MPEG-4 AVC video without sound) stored on the Telegram servers. By default, this animated MPEG-4 file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be mpeg4_gif
idStringUnique identifier for this result, 1-64 bytes
mpeg4_file_idStringA valid file identifier for the MP4 file
titleStringOptional. Title for the result
captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
+

InlineQueryResultCachedSticker

+

Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be sticker
idStringUnique identifier for this result, 1-64 bytes
sticker_file_idStringA valid file identifier of the sticker
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the sticker
+

Note: This will only work in Telegram versions released after 9 April, 2016 for static stickers and after 06 July, 2019 for animated stickers. Older clients will ignore them.

+

InlineQueryResultCachedDocument

+

Represents a link to a file stored on the Telegram servers. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be document
idStringUnique identifier for this result, 1-64 bytes
titleStringTitle for the result
document_file_idStringA valid file identifier for the file
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultCachedVideo

+

Represents a link to a video file stored on the Telegram servers. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be video
idStringUnique identifier for this result, 1-64 bytes
video_file_idStringA valid file identifier for the video file
titleStringTitle for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video
+

InlineQueryResultCachedVoice

+

Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be voice
idStringUnique identifier for this result, 1-64 bytes
voice_file_idStringA valid file identifier for the voice message
titleStringVoice message title
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice message
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultCachedAudio

+

Represents a link to an MP3 audio file stored on the Telegram servers. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be audio
idStringUnique identifier for this result, 1-64 bytes
audio_file_idStringA valid file identifier for the audio file
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InputMessageContent

+

This object represents the content of a message to be sent as a result of an inline query. Telegram clients currently support the following 5 types:

+ +

InputTextMessageContent

+

Represents the content of a text message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
message_textStringText of the message to be sent, 1-4096 characters
parse_modeStringOptional. Mode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptional. List of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptional. Disables link previews for links in the sent message
+

InputLocationMessageContent

+

Represents the content of a location message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
latitudeFloatLatitude of the location in degrees
longitudeFloatLongitude of the location in degrees
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
+

InputVenueMessageContent

+

Represents the content of a venue message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
latitudeFloatLatitude of the venue in degrees
longitudeFloatLongitude of the venue in degrees
titleStringName of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue, if known
foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
+

InputContactMessageContent

+

Represents the content of a contact message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
+

InputInvoiceMessageContent

+

Represents the content of an invoice message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
titleStringProduct name, 1-32 characters
descriptionStringProduct description, 1-255 characters
payloadStringBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
provider_tokenStringPayment provider token, obtained via Botfather
currencyStringThree-letter ISO 4217 currency code, see more on currencies
pricesArray of LabeledPricePrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountIntegerOptional. The maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies). Defaults to 0
suggested_tip_amountsArray of IntegerOptional. A JSON-serialized array of suggested amounts of tip in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
provider_dataStringOptional. A JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
photo_urlStringOptional. URL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
photo_sizeIntegerOptional. Photo size
photo_widthIntegerOptional. Photo width
photo_heightIntegerOptional. Photo height
need_nameBooleanOptional. Pass True, if you require the user's full name to complete the order
need_phone_numberBooleanOptional. Pass True, if you require the user's phone number to complete the order
need_emailBooleanOptional. Pass True, if you require the user's email address to complete the order
need_shipping_addressBooleanOptional. Pass True, if you require the user's shipping address to complete the order
send_phone_number_to_providerBooleanOptional. Pass True, if user's phone number should be sent to provider
send_email_to_providerBooleanOptional. Pass True, if user's email address should be sent to provider
is_flexibleBooleanOptional. Pass True, if the final price depends on the shipping method
+

ChosenInlineResult

+

Represents a result of an inline query that was chosen by the user and sent to their chat partner.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
result_idStringThe unique identifier for the result that was chosen
fromUserThe user that chose the result
locationLocationOptional. Sender location, only for bots that require user location
inline_message_idStringOptional. Identifier of the sent inline message. Available only if there is an inline keyboard attached to the message. Will be also received in callback queries and can be used to edit the message.
queryStringThe query that was used to obtain the result
+

Note: It is necessary to enable inline feedback via @Botfather in order to receive these objects in updates.

+

Payments

+

Your bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot. Please note that users will need Telegram v.4.0 or higher to use payments (released on May 18, 2017).

+

sendInvoice

+

Use this method to send invoices. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
titleStringYesProduct name, 1-32 characters
descriptionStringYesProduct description, 1-255 characters
payloadStringYesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
provider_tokenStringYesPayments provider token, obtained via Botfather
currencyStringYesThree-letter ISO 4217 currency code, see more on currencies
pricesArray of LabeledPriceYesPrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountIntegerOptionalThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies). Defaults to 0
suggested_tip_amountsArray of IntegerOptionalA JSON-serialized array of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
start_parameterStringOptionalUnique deep-linking parameter. If left empty, forwarded copies of the sent message will have a Pay button, allowing multiple users to pay directly from the forwarded message, using the same invoice. If non-empty, forwarded copies of the sent message will have a URL button with a deep link to the bot (instead of a Pay button), with the value used as the start parameter
provider_dataStringOptionalA JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
photo_urlStringOptionalURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
photo_sizeIntegerOptionalPhoto size
photo_widthIntegerOptionalPhoto width
photo_heightIntegerOptionalPhoto height
need_nameBooleanOptionalPass True, if you require the user's full name to complete the order
need_phone_numberBooleanOptionalPass True, if you require the user's phone number to complete the order
need_emailBooleanOptionalPass True, if you require the user's email address to complete the order
need_shipping_addressBooleanOptionalPass True, if you require the user's shipping address to complete the order
send_phone_number_to_providerBooleanOptionalPass True, if user's phone number should be sent to provider
send_email_to_providerBooleanOptionalPass True, if user's email address should be sent to provider
is_flexibleBooleanOptionalPass True, if the final price depends on the shipping method
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Pay total price' button will be shown. If not empty, the first button must be a Pay button.
+

answerShippingQuery

+

If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the Bot API will send an Update with a shipping_query field to the bot. Use this method to reply to shipping queries. On success, True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
shipping_query_idStringYesUnique identifier for the query to be answered
okBooleanYesSpecify True if delivery to the specified address is possible and False if there are any problems (for example, if delivery to the specified address is not possible)
shipping_optionsArray of ShippingOptionOptionalRequired if ok is True. A JSON-serialized array of available shipping options.
error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
+

answerPreCheckoutQuery

+

Once the user has confirmed their payment and shipping details, the Bot API sends the final confirmation in the form of an Update with the field pre_checkout_query. Use this method to respond to such pre-checkout queries. On success, True is returned. Note: The Bot API must receive an answer within 10 seconds after the pre-checkout query was sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
pre_checkout_query_idStringYesUnique identifier for the query to be answered
okBooleanYesSpecify True if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order. Use False if there are any problems.
error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
+

LabeledPrice

+

This object represents a portion of the price for goods or services.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
labelStringPortion label
amountIntegerPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Invoice

+

This object contains basic information about an invoice.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
titleStringProduct name
descriptionStringProduct description
start_parameterStringUnique bot deep-linking parameter that can be used to generate this invoice
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

ShippingAddress

+

This object represents a shipping address.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
country_codeStringISO 3166-1 alpha-2 country code
stateStringState, if applicable
cityStringCity
street_line1StringFirst line for the address
street_line2StringSecond line for the address
post_codeStringAddress post code
+

OrderInfo

+

This object represents information about an order.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
nameStringOptional. User name
phone_numberStringOptional. User's phone number
emailStringOptional. User email
shipping_addressShippingAddressOptional. User shipping address
+

ShippingOption

+

This object represents one shipping option.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringShipping option identifier
titleStringOption title
pricesArray of LabeledPriceList of price portions
+

SuccessfulPayment

+

This object contains basic information about a successful payment.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
invoice_payloadStringBot specified invoice payload
shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
order_infoOrderInfoOptional. Order info provided by the user
telegram_payment_charge_idStringTelegram payment identifier
provider_payment_charge_idStringProvider payment identifier
+

ShippingQuery

+

This object contains information about an incoming shipping query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique query identifier
fromUserUser who sent the query
invoice_payloadStringBot specified invoice payload
shipping_addressShippingAddressUser specified shipping address
+

PreCheckoutQuery

+

This object contains information about an incoming pre-checkout query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique query identifier
fromUserUser who sent the query
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
invoice_payloadStringBot specified invoice payload
shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
order_infoOrderInfoOptional. Order info provided by the user
+

Telegram Passport

+

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Please see the manual for details.

+

PassportData

+

Contains information about Telegram Passport data shared with the bot by the user.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dataArray of EncryptedPassportElementArray with information about documents and other Telegram Passport elements that was shared with the bot
credentialsEncryptedCredentialsEncrypted credentials required to decrypt the data
+

PassportFile

+

This object represents a file uploaded to Telegram Passport. Currently all Telegram Passport files are in JPEG format when decrypted and don't exceed 10MB.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
file_sizeIntegerFile size in bytes
file_dateIntegerUnix time when the file was uploaded
+

EncryptedPassportElement

+

Contains information about documents or other Telegram Passport elements shared with the bot by the user.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringElement type. One of “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport”, “address”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”, “phone_number”, “email”.
dataStringOptional. Base64-encoded encrypted Telegram Passport element data provided by the user, available for “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport” and “address” types. Can be decrypted and verified using the accompanying EncryptedCredentials.
phone_numberStringOptional. User's verified phone number, available only for “phone_number” type
emailStringOptional. User's verified email address, available only for “email” type
filesArray of PassportFileOptional. Array of encrypted files with documents provided by the user, available for “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration” and “temporary_registration” types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
front_sidePassportFileOptional. Encrypted file with the front side of the document, provided by the user. Available for “passport”, “driver_license”, “identity_card” and “internal_passport”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
reverse_sidePassportFileOptional. Encrypted file with the reverse side of the document, provided by the user. Available for “driver_license” and “identity_card”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
selfiePassportFileOptional. Encrypted file with the selfie of the user holding a document, provided by the user; available for “passport”, “driver_license”, “identity_card” and “internal_passport”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
translationArray of PassportFileOptional. Array of encrypted files with translated versions of documents provided by the user. Available if requested for “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration” and “temporary_registration” types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
hashStringBase64-encoded element hash for using in PassportElementErrorUnspecified
+

EncryptedCredentials

+

Contains data required for decrypting and authenticating EncryptedPassportElement. See the Telegram Passport Documentation for a complete description of the data decryption and authentication processes.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dataStringBase64-encoded encrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication
hashStringBase64-encoded data hash for data authentication
secretStringBase64-encoded secret, encrypted with the bot's public RSA key, required for data decryption
+

setPassportDataErrors

+

Informs a user that some of the Telegram Passport elements they provided contains errors. The user will not be able to re-submit their Passport to you until the errors are fixed (the contents of the field for which you returned the error must change). Returns True on success.

+

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier
errorsArray of PassportElementErrorYesA JSON-serialized array describing the errors
+

PassportElementError

+

This object represents an error in the Telegram Passport element which was submitted that should be resolved by the user. It should be one of:

+ +

PassportElementErrorDataField

+

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be data
typeStringThe section of the user's Telegram Passport which has the error, one of “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport”, “address”
field_nameStringName of the data field which has the error
data_hashStringBase64-encoded data hash
messageStringError message
+

PassportElementErrorFrontSide

+

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be front_side
typeStringThe section of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”
file_hashStringBase64-encoded hash of the file with the front side of the document
messageStringError message
+

PassportElementErrorReverseSide

+

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be reverse_side
typeStringThe section of the user's Telegram Passport which has the issue, one of “driver_license”, “identity_card”
file_hashStringBase64-encoded hash of the file with the reverse side of the document
messageStringError message
+

PassportElementErrorSelfie

+

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be selfie
typeStringThe section of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”
file_hashStringBase64-encoded hash of the file with the selfie
messageStringError message
+

PassportElementErrorFile

+

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be file
typeStringThe section of the user's Telegram Passport which has the issue, one of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
file_hashStringBase64-encoded file hash
messageStringError message
+

PassportElementErrorFiles

+

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be files
typeStringThe section of the user's Telegram Passport which has the issue, one of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
file_hashesArray of StringList of base64-encoded file hashes
messageStringError message
+

PassportElementErrorTranslationFile

+

Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be translation_file
typeStringType of element of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
file_hashStringBase64-encoded file hash
messageStringError message
+

PassportElementErrorTranslationFiles

+

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation change.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be translation_files
typeStringType of element of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
file_hashesArray of StringList of base64-encoded file hashes
messageStringError message
+

PassportElementErrorUnspecified

+

Represents an issue in an unspecified place. The error is considered resolved when new data is added.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be unspecified
typeStringType of element of the user's Telegram Passport which has the issue
element_hashStringBase64-encoded element hash
messageStringError message
+

Games

+

Your bot can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Create games via @BotFather using the /newgame command. Please note that this kind of power requires responsibility: you will need to accept the terms for each game that your bots will be offering.

+
    +
  • Games are a new type of content on Telegram, represented by the Game and InlineQueryResultGame objects.
  • +
  • Once you've created a game via BotFather, you can send games to chats as regular messages using the sendGame method, or use inline mode with InlineQueryResultGame.
  • +
  • If you send the game message without any buttons, it will automatically have a 'Play GameName' button. When this button is pressed, your bot gets a CallbackQuery with the game_short_name of the requested game. You provide the correct URL for this particular user and the app opens the game in the in-app browser.
  • +
  • You can manually add multiple buttons to your game message. Please note that the first button in the first row must always launch the game, using the field callback_game in InlineKeyboardButton. You can add extra buttons according to taste: e.g., for a description of the rules, or to open the game's official community.
  • +
  • To make your game more attractive, you can upload a GIF animation that demostrates the game to the users via BotFather (see Lumberjack for example).
  • +
  • A game message will also display high scores for the current chat. Use setGameScore to post high scores to the chat with the game, add the edit_message parameter to automatically update the message with the current scoreboard.
  • +
  • Use getGameHighScores to get data for in-game high score tables.
  • +
  • You can also add an extra sharing button for users to share their best score to different chats.
  • +
  • For examples of what can be done using this new stuff, check the @gamebot and @gamee bots.
  • +
+

sendGame

+

Use this method to send a game. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idIntegerYesUnique identifier for the target chat
game_short_nameStringYesShort name of the game, serves as the unique identifier for the game. Set up your games via Botfather.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Play game_title' button will be shown. If not empty, the first button must launch the game.
+

Game

+

This object represents a game. Use BotFather to create and edit games, their short names will act as unique identifiers.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
titleStringTitle of the game
descriptionStringDescription of the game
photoArray of PhotoSizePhoto that will be displayed in the game message in chats.
textStringOptional. Brief description of the game or high scores included in the game message. Can be automatically edited to include current high scores for the game when the bot calls setGameScore, or manually edited using editMessageText. 0-4096 characters.
text_entitiesArray of MessageEntityOptional. Special entities that appear in text, such as usernames, URLs, bot commands, etc.
animationAnimationOptional. Animation that will be displayed in the game message in chats. Upload via BotFather
+

CallbackGame

+

A placeholder, currently holds no information. Use BotFather to set up your game.

+

setGameScore

+

Use this method to set the score of the specified user in a game message. On success, if the message is not an inline message, the Message is returned, otherwise True is returned. Returns an error, if the new score is not greater than the user's current score in the chat and force is False.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier
scoreIntegerYesNew score, must be non-negative
forceBooleanOptionalPass True, if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
disable_edit_messageBooleanOptionalPass True, if the game message should not be automatically edited to include the current scoreboard
chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
+

getGameHighScores

+

Use this method to get data for high score tables. Will return the score of the specified user and several of their neighbors in a game. On success, returns an Array of GameHighScore objects.

+
+

This method will currently return scores for the target user, plus two of their closest neighbors on each side. Will also return the top three users if the user and his neighbors are not among them. Please note that this behavior is subject to change.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesTarget user id
chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
+

GameHighScore

+

This object represents one row of the high scores table for a game.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
positionIntegerPosition in high score table for the game
userUserUser
scoreIntegerScore
+
+

And that's about all we've got for now.
If you've got any questions, please check out our Bot FAQ »

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/bots/faq.html b/data/core.telegram.org/bots/faq.html new file mode 100644 index 0000000000..223b0a9eea --- /dev/null +++ b/data/core.telegram.org/bots/faq.html @@ -0,0 +1,243 @@ + + + + + Bots FAQ + + + + + + + + + + + + + +
+ +
+
+
+ +

Bots FAQ

+ +
+

If you are new to Telegram bots, we recommend checking out our Introduction to Bots first.
You may also find the Bot API Manual useful.

+
+

+ +
+

General Questions

+

How do I create a bot?

+

Creating Telegram bots is super-easy, but you will need at least some skills at computer programming. In order for a bot to work, set up a bot account with @BotFather, then connect it to your backend server via our API.

+

Unfortunately, there are no out-of-the-box ways to create a working bot if you are not a developer. But we're sure you'll soon find plenty of bots created by other people to play with.

+

I'm a developer. Where can I find some examples?

+

Here are two sample bots, both written in PHP:

+
    +
  • Hello Bot demonstrates the basics of the Telegram bot API.
  • +
  • Simple Poll bot is a more complete example, it supports both long-polling and Webhooks for updates.
  • +
+
+

Many members of our community are building bots and publishing sources.
We're collecting them on this page »

+
+

Ping us on @BotSupport if you've built a bot and would like to share it with others.

+

Will you add X to the Bot API?

+

The bot API is still pretty young. There are many potential features to consider and implement. We'll be studying what people do with their bots for a while to see which directions will be most important for the platform.

+

All bot developers are welcome to share ideas for our Bot API with our @BotSupport account.

+

What messages will my bot get?

+

1. All bots, regardless of settings, will receive:

+
    +
  • All service messages.
  • +
  • All messages from private chats with users.
  • +
  • All messages from channels where they are a member.
  • +
+

2. Bot admins and bots with privacy mode disabled will receive all messages except messages sent by other bots.

+

3. Bots with privacy mode enabled will receive:

+
    +
  • Commands explicitly meant for them (e.g., /command@this_bot).
  • +
  • General commands from users (e.g. /start) if the bot was the last bot to send a message to the group.
  • +
  • Messages sent via this bot.
  • +
  • Replies to any messages implicitly or explicitly meant for this bot.
  • +
+

Note that each particular message can only be available to one privacy-enabled bot at a time, i.e., a reply to bot A containing an explicit command for bot B or sent via bot C will only be available to bot A. Replies have the highest priority.

+

Why doesn't my bot see messages from other bots?

+

Bots talking to each other could potentially get stuck in unwelcome loops. To avoid this, we decided that bots will not be able to see messages from other bots regardless of mode.

+

Getting Updates

+

How do I get updates?

+

There are currently two ways of getting updates. You can either use long polling or Webhooks. Please note that it's not possible to get updates via long polling while an outgoing Webhook is set.

+

Long polling gives me the same updates again and again!

+

The getUpdates method returns the earliest 100 unconfirmed updates. To confirm an update, use the offset parameter when calling getUpdates like this:

+
offset = update_id of last processed update + 1
+

All updates with update_id less than or equal to offset will be marked as confirmed on the server and will no longer be returned.

+

I'm having problems with Webhooks.

+

If you've set up your webhook successfully, but are not getting any updates, please remember:

+
    +
  • You need a valid SSL certificate for webhooks to work.
  • +
  • To use a self-signed certificate, you need to upload your public key certificate using the certificate parameter in setWebhook. Please upload as InputFile, sending a String will not work.
  • +
  • Ports currently supported for Webhooks: 443, 80, 88, 8443.
  • +
  • Wildcard certificates may not be supported.
  • +
  • Redirects are not supported.
  • +
  • CN must exactly match your domain.
  • +
+
+

Please check out this new WEBHOOK GUIDE to learn all there is to know about webhooks!

+
+

I'm having trouble with my self-signed certificate!

+

Please take a look at this self-signed certificate guide we made just for you. If you've read it and still have a question, ping us on botsupport.

+

How can I make sure that Webhook requests are coming from Telegram?

+

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL you give us, e.g. www.example.com/your_token. Since nobody else knows your bot's token, you can be pretty sure it's us.

+

How can I make requests in response to updates?

+

This is possible if you're using webhooks. The upside is that you need less requests, the downside — that in this case it's not possible to know that such a request was successful or get its result.

+

Whenever you receive a webhook update, you have two options:

+

1. Issue POST to https://api.telegram.org/bot<token>/method

+
+ +
+ +

2. Reply directly and give method as JSON payload in the reply

+
+
+ +
+

You may also want to look at our sample HelloBot, it offers a PHP implementation of this.

+
+

Handling Media

+

How do I download files?

+

Use the getFile method. Please note that this will only work with files of up to 20 MB in size.

+

How do I upload a large file?

+

Bots can currently send files of any type of up to 50 MB in size, so yes, very large files won't work for now. Sorry. This limit may be changed in the future.

+

Can I count on file_ids to be persistent?

+

Yes, file_ids can be treated as persistent.

+

Broadcasting to Users

+

My bot is hitting limits, how do I avoid this?

+

When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.

+

If you're sending bulk notifications to multiple users, the API will not allow more than 30 messages per second or so. Consider spreading out notifications over large intervals of 8—12 hours for best results.

+

Also note that your bot will not be able to send more than 20 messages per minute to the same group.

+

How can I message all of my bot's subscribers at once?

+

Unfortunately, at this moment we don't have methods for sending bulk messages, e.g. notifications. We may add something along these lines in the future.

+

In order to avoid hitting our limits when sending out mass notifications, consider spreading them over longer intervals, e.g. 8-12 hours. The API will not allow bulk notifications to more than ~30 users per second, if you go over that, you'll start getting 429 errors.

+

See also: How to avoid hitting limits?

+
+
+

If you've got questions that are not answered on this page, ping us at @BotSupport in Telegram.
We welcome any suggestions for the Bot Platform and API.

+
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/bots/games.html b/data/core.telegram.org/bots/games.html new file mode 100644 index 0000000000..201d45f947 --- /dev/null +++ b/data/core.telegram.org/bots/games.html @@ -0,0 +1,185 @@ + + + + + Gaming Platform + + + + + + + + + + + + + +
+ +
+
+
+ +

Gaming Platform

+ +
+ +
+ +
+ +

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Games are a new type of content on Telegram that your bot can send to users.

+
+

+
+ +
+

This introduction is meant for bot developers. Click here, in case you'd like something more user-friendly.
Check out the @gamebot and @gamee bots for examples of what you can do using the new Gaming Platform.

+
+

Creating a Game

+

To get started, send the /newgame command to @BotFather.You will be prompted for a description text and a photo. You can also upload an optional GIF animation that demostrates your game to the users to make messages with the game more attractive (check out Lumberjack or Corsairs for examples).

+

Launching the Game

+

Once the game is created, your bot can send it to chats as regular messages, or offer them via inline mode. The game message will always have an inline Play button.

+

When this button is pressed, your bot gets a callback query that indicates the requested game. You provide the correct URL for this particular user and the app automatically opens the game in the in-app browser.

+

Adding Buttons

+

If you send the game message without any buttons, it will automatically have a 'Play GameName' button. You can manually add multiple buttons to your game message. Please note that the first button in the first row must always be the one that launches the game. You can add more buttons: e.g., for a description of the rules, or a button that links to the game's official community.

+

Tracking High Scores

+

The message with your game will also display high scores for the current chat. When a new high score is set, a service message will be sent to the chat and the message with the current scoreboard will be updated. You can also request the necessary data for building in-game high score tables.

+
+
+ +

+ +

+ +

Sharing Your Game to Telegram Chats

+

There are many way for users to spread your game virally if they like it. The interface will always have the standard system button for sharing the game in the top right corner:

+
+ + +

+ +
+ + + +

You can also create an additional Share button inside your HTML page. Pressing this button will send the game to a desired chat along with the user's best score in the game.

+
+ + + + + +

+ + +

To add the sharing button, include this script at the end of the <body> tag on your page:

+
<script src="https://telegram.org/js/games.js"></script>
+

Then use the method TelegramGameProxy.shareScore() to call the sharing option.

+
+

Warning: Do not call this method without consent and direct action from the user.

+
+

Example:

+
<button onclick="TelegramGameProxy.shareScore()">Share score</button>
+

This library will only work when launched from inside Telegram, so please don't use it on ordinary web pages.

+

Using URL Parameters

+

If your URL is using a fragment identifier, please note that Telegram Apps could add certain service parameters to the fragment id. The names for such parameters will start in tg (you can check the code that adds them here). Use the TelegramGameProxy.initParams object if you need to read your own parameters from the fragment id.

+

Creating a Great HTML5 Experience

+

Please make sure that your HTML5 page is responsive and works well on all Telegram apps and supported platforms. If you find it impossible to support certain conditions or platforms, don't leave your users hanging and at least provide a notification.

+
+

See the Bot API Manual for the relevant methods and objects.

+
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/bots/inline.html b/data/core.telegram.org/bots/inline.html new file mode 100644 index 0000000000..3bf2192115 --- /dev/null +++ b/data/core.telegram.org/bots/inline.html @@ -0,0 +1,182 @@ + + + + + Inline Bots + + + + + + + + + + + + + +
+ +
+
+
+ +

Inline Bots

+ +
+ +
+ +
+ +

Beyond sending commands in private messages or groups, users can interact with your bot via inline queries. If inline queries are enabled, users can call your bot by typing its username and a query in the text input field in any chat. The query is sent to your bot in an update. This way, people can request content from your bot in any of their chats, groups, or channels without sending any messages at all.

+
+
+
+ + +

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot’s name.

+
+

See the Bot API Manual for the relevant methods and objects.

+
+

Inline results

+

Inline bots support all types of content available in Telegram (20 in all). They are capable of sending stickers, videos, music, locations, documents and more.

+
+

+
+ +

Clients can display the results with vertical or horizontal scrolling, depending on the type of content:

+
+ + + + + +
+
+ +

As soon as the user taps on an item, it's immediately sent to the recipient, and the input field is cleared.

+

Switching inline/PM modes

+

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

+
+

+
+ +

You can display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

+

Sample bots
@youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.

+
+

Manual: Switch to PM

+
+

Location-based results

+

Inline bots can request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

+

Sample bot
@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

+

Spreading virally

+

Messages sent with the help of your bot will show its username next to the sender's name.

+
+ + + + + +

+ +

When a user taps on the bot username in the message header, the mention is automatically inserted into the input field. Entering the @ symbol in the input field brings up a list of suggestions, featuring recently used inline bots.

+

Collecting feedback

+

To know which of the provided results your users are sending to their chat partners, send @Botfather the /setinlinefeedback command. With this enabled, you will receive updates on the results chosen by your users.

+

Please note that this can create load issues for popular bots – you may receive more results than actual requests due to caching (see the cache_time parameter in answerInlineQuery). For these cases, we recommend adjusting the probability setting to receive 1/10, 1/100 or 1/1000 of the results.

+

Inline bot samples

+

Here are some sample inline bots, in case you’re curious to see one in action. Try any of these:
@gif – GIF search
@vid – Video search
@pic – Yandex image search
@bing – Bing image search
@wiki – Wikipedia search
@imdb – IMDB search
@bold – Make bold, italic or fixed sys text

+

NEW
@youtube - Connect your account for personalized results
@music - Search and send classical music
@foursquare – Find and send venue addresses
@sticker – Find and send stickers based on emoji

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/bots/samples.html b/data/core.telegram.org/bots/samples.html new file mode 100644 index 0000000000..7cc5729af4 --- /dev/null +++ b/data/core.telegram.org/bots/samples.html @@ -0,0 +1,249 @@ + + + + + Bot Code Examples + + + + + + + + + + + + + +
+ +
+
+
+ +

Bot Code Examples

+ +
+

If you want to learn more about Telegram bots, start with our Introduction to Bots »
Check out the FAQ, if you have questions.

+
+

Many members of our community are building bots and libraries and publishing their source code. We collect these examples here. Ping us on BotSupport if you've built a bot and would like to share its code with others.

+

PHP

+ +

Node.js

+ +

Rust

+ +

Python

+ +

Ruby

+ +

Swift

+ +

Kotlin

+ +

Java

+ +

Go

+ +

Other Languages

+ +
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/bots/samples/hellobot.html b/data/core.telegram.org/bots/samples/hellobot.html new file mode 100644 index 0000000000..9aaf3fa190 --- /dev/null +++ b/data/core.telegram.org/bots/samples/hellobot.html @@ -0,0 +1,287 @@ + + + + + Hellobot + + + + + + + + + + + + + +
+ +
+
+
+ +

Hellobot

+ +
+

This sample PHP bot demonstrates the basics of the Telegram Bot API.
If you have questions, try our FAQ or check out this page for more examples.

+
+

+ +
<?php
+
+define('BOT_TOKEN', '12345678:replace-me-with-real-token');
+define('API_URL', 'https://api.telegram.org/bot'.BOT_TOKEN.'/');
+
+function apiRequestWebhook($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  $parameters["method"] = $method;
+
+  $payload = json_encode($parameters);
+  header('Content-Type: application/json');
+  header('Content-Length: '.strlen($payload));
+  echo $payload;
+
+  return true;
+}
+
+function exec_curl_request($handle) {
+  $response = curl_exec($handle);
+
+  if ($response === false) {
+    $errno = curl_errno($handle);
+    $error = curl_error($handle);
+    error_log("Curl returned error $errno: $error\n");
+    curl_close($handle);
+    return false;
+  }
+
+  $http_code = intval(curl_getinfo($handle, CURLINFO_HTTP_CODE));
+  curl_close($handle);
+
+  if ($http_code >= 500) {
+    // do not wat to DDOS server if something goes wrong
+    sleep(10);
+    return false;
+  } else if ($http_code != 200) {
+    $response = json_decode($response, true);
+    error_log("Request has failed with error {$response['error_code']}: {$response['description']}\n");
+    if ($http_code == 401) {
+      throw new Exception('Invalid access token provided');
+    }
+    return false;
+  } else {
+    $response = json_decode($response, true);
+    if (isset($response['description'])) {
+      error_log("Request was successful: {$response['description']}\n");
+    }
+    $response = $response['result'];
+  }
+
+  return $response;
+}
+
+function apiRequest($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  foreach ($parameters as $key => &$val) {
+    // encoding to JSON array parameters, for example reply_markup
+    if (!is_numeric($val) && !is_string($val)) {
+      $val = json_encode($val);
+    }
+  }
+  $url = API_URL.$method.'?'.http_build_query($parameters);
+
+  $handle = curl_init($url);
+  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
+  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
+  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
+
+  return exec_curl_request($handle);
+}
+
+function apiRequestJson($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  $parameters["method"] = $method;
+
+  $handle = curl_init(API_URL);
+  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
+  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
+  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
+  curl_setopt($handle, CURLOPT_POST, true);
+  curl_setopt($handle, CURLOPT_POSTFIELDS, json_encode($parameters));
+  curl_setopt($handle, CURLOPT_HTTPHEADER, array("Content-Type: application/json"));
+
+  return exec_curl_request($handle);
+}
+
+function processMessage($message) {
+  // process incoming message
+  $message_id = $message['message_id'];
+  $chat_id = $message['chat']['id'];
+  if (isset($message['text'])) {
+    // incoming text message
+    $text = $message['text'];
+
+    if (strpos($text, "/start") === 0) {
+      apiRequestJson("sendMessage", array('chat_id' => $chat_id, "text" => 'Hello', 'reply_markup' => array(
+        'keyboard' => array(array('Hello', 'Hi')),
+        'one_time_keyboard' => true,
+        'resize_keyboard' => true)));
+    } else if ($text === "Hello" || $text === "Hi") {
+      apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'Nice to meet you'));
+    } else if (strpos($text, "/stop") === 0) {
+      // stop now
+    } else {
+      apiRequestWebhook("sendMessage", array('chat_id' => $chat_id, "reply_to_message_id" => $message_id, "text" => 'Cool'));
+    }
+  } else {
+    apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'I understand only text messages'));
+  }
+}
+
+
+define('WEBHOOK_URL', 'https://my-site.example.com/secret-path-for-webhooks/');
+
+if (php_sapi_name() == 'cli') {
+  // if run from console, set or delete webhook
+  apiRequest('setWebhook', array('url' => isset($argv[1]) && $argv[1] == 'delete' ? '' : WEBHOOK_URL));
+  exit;
+}
+
+
+$content = file_get_contents("php://input");
+$update = json_decode($content, true);
+
+if (!$update) {
+  // receive wrong update, must not happen
+  exit;
+}
+
+if (isset($update["message"])) {
+  processMessage($update["message"]);
+}
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/bots/self-signed.html b/data/core.telegram.org/bots/self-signed.html new file mode 100644 index 0000000000..ec670a6a4b --- /dev/null +++ b/data/core.telegram.org/bots/self-signed.html @@ -0,0 +1,161 @@ + + + + + Using self-signed certificates + + + + + + + + + + + + + +
+ +
+
+
+ +

Using self-signed certificates

+ +

Upload your certificate using the certificate parameter in the setWebhook method. The certificate supplied should be PEM encoded (ASCII BASE64), the pem file should only contain the public key (including BEGIN and END portions). When converting from a bundle format, please split the file to only include the public key.

+

Generating a self-signed certificate pair (PEM):

+

Openssl

+
+

Windows binaries for Openssl are available online

+
+

openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"

+

YOURPUBLIC.pem has to be used as input for setting the self-signed webhook.

+

You can inspect the generated certificate with:
openssl x509 -text -noout -in YOURPUBLIC.pem

+

Converting from a previously generated DER:
openssl x509 -inform der -in YOURDER.der -out YOURPEM.pem

+

Converting from a previously generated PKCS12:
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

+
+

More information: https://www.openssl.org/

+
+

Java keystore

+

Generate self-signed JKS:
keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

+

Converting JKS to pkcs12 (intermediate step for conversion to PEM):
keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

+

Convert PKCS12 to PEM (requires openssl):
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

+
+

More information: https://docs.oracle.com

+
+

Windows

+

Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.

+

On the commandline:
certreq -new TEMPLATE.txt RequestFileOut

+

TEMPLATE.txt example file:

+
[NewRequest]
+
+; At least one value must be set in this section
+Subject = "CN=DOMAIN.EXAMPLE"
+KeyLength = 2048
+KeyAlgorithm = RSA
+HashAlgorithm = sha256
+;MachineKeySet = true
+RequestType = Cert
+UseExistingKeySet=false ;generates a new private key (for export)
+Exportable = true ;makes the private key exportable with the PFX
+

A self-signed certificate will be generated and installed, to view the certificate:
certutil -store -user my

+

To export in DER format (intermediate step for conversion to PEM)
certutil -user -store -split my SERIALNUMBER YOURDER.crt

+

Converting to PEM (used for setting the webhook)
certutil -encode YOURDER.crt YOURPEM.cer

+

To delete a certificate from your store:
certutil -delstore -user my SERIALNUMBER (from view)

+

To export in PFX(PKCS12) format
certutil -exportpfx -user YOURDOMAIN.EXAMPLE YOURPKCS.pfx NoChain

+
+

More information: https://technet.microsoft.com

+
+

Converting YOURPKCS.pfx to PEM including the private key is best done with OpenSSL:
openssl pkcs12 -in YOURPKCS.pfx -out YOURPEM.cer

+

Remember that only the public key is needed as input for the self-signed webhook certificate parameter. certmgr.msc can also be used as a GUI to export the public part of self-signed certificates to PEM.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/bots/webhooks.html b/data/core.telegram.org/bots/webhooks.html new file mode 100644 index 0000000000..f2a08082c7 --- /dev/null +++ b/data/core.telegram.org/bots/webhooks.html @@ -0,0 +1,827 @@ + + + + + Marvin's Marvellous Guide to All Things Webhook + + + + + + + + + + + + + +
+ +
+
+
+ +

Marvin's Marvellous Guide to All Things Webhook

+ +
+ +

We currently support two ways of processing bot updates, getUpdates and setWebhook. getUpdates is a pull mechanism, setwebhook is push. Although the concept of a webhook is fairly simple, the setup of the individual components has proven to be tricky for many. This guide provides some extra information for those of you brave enough to venture into the art of the webhook.

+

There are some advantages of using a webhook over getUpdates. As soon as an update arrives, we’ll kindly deliver it to your bot for processing.

+

This:

+
1. Avoids your bot having to ask for updates frequently.
+2. Avoids the need for some kind of polling mechanism in your code.
+

Other advantages may include saving some potential CPU cycles and an increase in response time, these things however depend heavily on the usage pattern of your bot.

+

Setting a webhook means you supplying Telegram with a location in the form of a URL, on which your bot listens for updates. We need to be able to connect and post updates to that URL.

+

To ensure that we can do that, there are some basic requirements:

+

The short version

+

You'll need a server that:

+
    +
  • Supports IPv4, IPv6 is currently not supported for webhooks.
  • +
  • Accepts incoming POSTs from subnets 149.154.160.0/20 and 91.108.4.0/22 on port 443, 80, 88, or 8443.
  • +
  • Is able to handle TLS1.2(+) HTTPS-traffic.
  • +
  • Provides a supported, verified or self-signed certificate.
  • +
  • Uses a CN or SAN that matches the domain you’ve supplied on setup.
  • +
  • Supplies all intermediate certificates to complete a verification chain.
  • +
+

That’s almost all there’s to it.
If you decide to limit traffic to our specific range of addresses, keep an eye on this document whenever you seem to run into trouble. Our IP-range might change in the future.

+

The longer version

+
    +
  • A domain name

    +

    Setting a webhook needs a URL for us to post to. For that you'll need a server with a domain name. If you don't have one, you'll need to obtain one first. Telegram currently doesn't offer hosting or domain name services. There are quite a few VPS/Web hosting providers around the internet, feel free to pick one to your liking.
    If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    How do I get a server with a domain name?

    +
  • +
  • An open port

    +

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    +
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
    +Whenever something stops working in the future, please check this document again as 
    +the range might expand or change.
    +

    How do I check for open ports or limit access to my bot?

    +
  • +
  • Always SSL/TLS

    +

    A webhook requires SSL/TLS encryption, no matter which port is used. It's not possible to use a plain-text HTTP webhook. You shouldn't want to either, for the sake of your bot and users.
    SSL/TLS, why do I have to handle this for a webhook?

    +
  • +
  • Not all SSL/TLS is equal

    +

    We support any SSL/TLS version TLS1.2 and up for your webhook. This means that SSLV2/3/TLS1.0/TSL1.1 are NOT supported, due to security issues associated with those older versions.
    How do I check that I’m handling the right version?

    +
  • +
  • SSL needs a certificate

    +

    The common name (CN) of your certificate (self-signed or verified) has to match the domain name where your bot is hosted. You may also use a subject alternative name (SAN), that matches the domain for your webhook. Server Name Indication (SNI)-routing is supported. If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    A certificate, where do I get one, and how?

    +
  • +
  • Verified or self-signed

    +

    A certificate can either be verified or self-signed. Setting a webhook with a self-signed certificate differs a little from setting a webhook with a verified certificate. Ensure you're using the correct setup for the type of certificate you've chosen for your webhook.
    How do I set a webhook for either type?

    +
  • +
  • Supported certificates

    +

    Not all verified certificates are supported. Certificates are based on a network of trust and come in a chain. Trusting your verified certificate means we have to trust the provider of that certificate, the Certificate Authority (and hence its root certificate). Before you pick a certificate provider, Check this list to make sure that we actually trust their root certificate.
    What if my root certificate isn’t on that list?

    +
  • +
  • An Untrusted root

    +

    Ok, so you already had a certificate installed and just discovered it’s not on our list.
    Start by ignoring it, and just try to set it. We occasionally add extra root certificates to keep up with popular demand, so the list isn't always exhaustive. Unlucky after all? We'll allow you to supply an unsupported root certificate when setting the webhook. This method is nearly identical to setting a self-signed certificate webhook. Instead of your self-signed certificate you'll be sending us the root certificate as inputFile.
    Setting a verified webhook with an untrusted root

    +
  • +
  • Intermediate certificates

    +

    Some verified certificates require an intermediate certificate. In this construction the provider of your verified certificate has used their root certificate to sign an intermediate certificate. This intermediate certificate is then used to sign your verified certificate. You'll need to provide the intermediate certificate for us to be able to verify the chain of trust. CA's that use this type of chain supply an intermediate certificate.
    Supplying an intermediate certificate

    +
  • +
  • More information

    +

    Since we know webhooks can be a tad overwhelming, we’re working on a little digital assistant that’ll try and help you with the most common problems, it's not nearly perfect, but you may try using @CanOfWormsBot to check if your chain of certificates is installed correctly before contacting support.

    +
  • +
  • Testing your bot

    +

    We took the liberty of adding a set of example updates. They come in handy when testing your bot, no matter which method of getting updates you might be using.

    +
  • +
  • Don't panic.

    +

    If by now you're looking for your fishing gear because we've mentioned ports and hooks or you're about to Google what kind of bait URL and TLS exactly are, this guide might not be completely for you. You’re quite likely still a brilliant bot programmer, don’t worry. Perhaps this whole webhook thing is just new to you, not all is lost. If you currently have a working getUpdates situation, it's a good idea to pick up this guide again on a rainy Sunday afternoon and take your time to read up on some subjects around the internet. This guide can only contain a finite amount of information after all.

    +
  • +
+

The verbose version

+
How do I get a server with a domain name?
+

If you use a webhook, we have to deliver requests to your bot to a server we can reach. So yes, you need a server we can connect to. It can be anywhere in the galaxy, if you ensure we can reach the server by domain name (or at least via IP for a self-signed certificate), it will work just fine.

+

There are quite a few ways to get this done, as a novice however it's likely that you're not directly jumping at the chance of crafting this from scratch. Actually, as a novice, we recommend you don't. It's likely to be a complex and long ride.

+

If you got stuck here, make a choice:

+
    +
  • You use getUpdates at the moment and it works, keep it that way. Especially if you're running your bot from a nice machine that does well. There is nothing wrong with using getUpdates.

    +
  • +
  • Go with a hosted service and let a bunch of professionals worry about things like registering a domain, setting up DNS, a web server, securing it and so on.

    +
  • +
+
If you're going with a hosted service, make sure to look for a hosting provider that 
+not only supports your code’s needs, for example: support for your PHP version,
+but one that also handles SSL and allows you to create/deploy certificates.
+
    +
  • Go crazy, dive on the internet and start reading. Once you’re confident that you’ve got all the basic theories down, find yourself a nice hosted VPS or roll your own machine at home and get back to us here.
  • +
+
How do I check for open ports or limit access to my bot?
+

So you have the hosting thing down and all is good so far, however, when you enter the address of your bot in your browser it seems unreachable.

+

Explaining every firewall or web server solution in detail isn't possible for us, which we hope you understand. If you’re running a hosted solution, you’re more likely to have a nice UI where you configure these settings. Head to your configuration panel and check all of them. If you’re on a Linux based VPS with shell access, we have some tips for you:

+
    +
  • Make sure your bot process is indeed configured to listen on the port you're using.
    netstat –ln | grep portnumber
    Shows you if your bot is actually listening for incoming requests on the port you expect.
    sudo lsof -i | grep process name
    Is a simple way to check if that’s actually being listened on by the process your bot is using.
  • +
+
    +
  • Make sure it’s listening correctly.
    Your bot has to listen on the address you’ve exposed to the outside (your public IP), it can also listen on all addresses (*: or 0.0.0.0).
    The netstat and lsof-commands mentioned above assist in checking this. If nothing shows up, it is time to check your configuration and fix it. Set the correct IP, make sure it’s listening on a supported port and fire away! Just use a Web Browser to check if you’re reachable. The problem can be in the configuration of your bot, your web server virtual host configuration, or the servers binding configuration.
  • +
+
    +
  • If you still can’t reach your address, check your firewall.
    sudo iptables –L
    OR
    sudo ufw status verbose (Ubuntu)
    Gives you some insight in the current firewall settings.

    +
  • +
  • If it looks like you’re blocking incoming traffic, let’s fix that.
    sudo iptables –A INPUT –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow portnumber/tcp
    Allows incoming traffic on all interfaces to the specified tcp port.
    sudo iptables –A INPUT –i interfacename –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp
    Allows incoming traffic to a specific interface and a specific port from everywhere.
    sudo ifconfig
    Helps you find the interface with the public address you’re going to use.

    +
  • +
+
If you use iptables, make sure to actually SAVE after changing the configuration.
+On a Debian based system the iptables-persistent package is be a good option.
+RHEL/CentOS offers a service iptables save -command.
+A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.
+
    +
  • If you’re just looking for some hints on how to limit incoming traffic:
    sudo iptables –A INPUT –i interfacename –p tcp –m iprange –src-range 149.154.167.197-149.154.167.233 –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp from 149.154.167.192/26
    Allows incoming traffic to a specific interface and a specific port from a specific range of addresses. (ufw is using a subnet mask in the example, ranging from 192-255)
  • +
+

That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

+
SSL/TLS, what is it and why do I have to handle this for a webhook?
+

You’re already familiar with it in some form or another. Whenever you see that (nicely green) lock in your browser bar, you know it’s reasonably safe to assume that you’ve landed on the site you actually wanted to visit. If you see the green lock, that's SSL/TLS in action. If you want to learn more about how SSL/TLS works in general, it's best to search the internet.

+

The main difference between getUpdates and a webhook is the way the connection takes place. getUpdates means you'll connect to our server, a webhook means we'll be connecting to your server instead. Connecting to your server has to be done secure, we have to know for sure it's you we're talking to after all. This means you'll have to handle all that server side encryption stuff, virtually presenting us with a green lock. If you use a web server for us to post to, you need to support SSL/TLS handling on the port/virtual host of your choice. An online search for “YOURWEBSERVER enable HTTPS” will help you.

+

Not using a regular web server? Have a look at our example page, most examples there include code for handling SSL/TLS in a webhook setup.

+
How do I check that I’m handling the right version?
+

You just read up on the whole SSL/TLS stuff, figured out that it’s not all that bad to setup and we add some more requirements. Here are some tips to check if you’re indeed supporting at least TLS1.2.

+
    +
  • Several online services exist that allow you to check your certificate installation,
    They give you an overview of your supported TLS versions/Cipher suites and other details. Search online for Symantec crypto report or Qualys ssl. Both supply tools to verify your setup.

    +
  • +
  • Checking locally can also be done, in several ways, here are three options,

    +
      +
    • Go simple:
      Using Chrome as a browser? Open up the URL to your bot and inspect the certificate details. If you’re supporting TLS Chrome tells you so in the security overview tab. Other browsers are likely able to give you similar basic information.

      +
    • +
    • Using curl:
      curl --tlsv1.2 -v -k https://yourbotdomain:yourbotport/
      You can add --tlsv1.2 to force curl into using TLS1.2 when trying to connect. -k is optional and used to check against a self-signed certificate. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using.

      +
    • +
    • Using OpenSSL
      openssl s_client -tls1_2 -connect yourbotdomain:yourbotport -servername yourbotdomain
      You can add -tls1_2 to force OpenSSL into using TLS1.2 when trying to connect. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using. Note that https:// isn’t used for OpenSSL. -servername is optional, and included here for some shared hosters, which use SNI to route traffic to the correct domain. When SNI is used you’ll notice that your server appears to be returning a certificate for a different domain than your own. Adding -servername yourbotdomain ensures that SNI negotiation is done, and the correct certificate is returned.

      +
    • +
    +
  • +
  • Some additional configuration pointers

    +
      +
    • Forcing TLS in your virtual host on Apache:
      SSLProtocol -all +TLSv1.2
    • +
    • Forcing TLS in your virtual host on Nginx:
      ssl_protocols TLSv1.2;
    • +
    • Force TLS for your Java virtual machine through system properties:
      -Dhttps.protocols=TLSv1.2 -Djdk.tls.client.protocols=TLSv1.2
    • +
    • Enabling ssl debug for your JVM:
      -Djavax.net.debug=ssl,handshake,record
    • +
    +
  • +
  • Other tools that may help in debugging issues:

    +
      +
    • Wireshark: excellent packet capturing
    • +
    • Tcpdump: equally excellent and doesn’t need a GUI
    • +
    • Charles: web debugging proxy
    • +
    • Fiddler: web debugging proxy
    • +
    +
  • +
+
A certificate, where do I get one and how?
+

You need a certificate, pick on of these types;

+
    +
  • A verified, supported certificate
  • +
  • A self-signed certificate

    +
  • +
  • A verified, supported certificate
    +

    Using a verified certificate means you already have, or will obtain, a certificate backed by a trusted certificate authority (CA). There are many ways to acquire a verified certificate, paid or free. Two popular examples of free suppliers are StartSSL and Let’s Encrypt. You’re welcome to pick another. Just make sure first the supplier is likely to be supported.
    Check this list before selecting a CA.
    Once you’ve picked a CA and validated your identity with them, you can craft your certificate. This frequently starts by generating a CSR (Certificate Signing Request). Generating a CSR is done either through your host machine, or online via the tools provided by the CA.

    +
  • +
  • Here is an example (PEM format output).

    +
      +
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -keyout yourprivatekey.key -out yoursigningrequest.csr
    • +
    +
  • +
+
----
+Generating a 2048 bit RSA private keywriting new private key to yourprivatekey.key
+Enter PEM pass phrase: enter a password for your key here 
+Verifying - Enter PEM pass phrase: confirm the entered password
+-----
+You are about to be asked to enter information that will be incorporated
+into your certificate request.
+What you are about to enter is what is called a Distinguished Name or a DN.
+There are quite a few fields but you can leave some blank
+For some fields there will be a default value,If you enter '.',
+the field will be left blank.-----
+Country Name (2 letter code) [AU]:
+State or Province Name (full name) [Some-State]:
+Locality Name (eg, city) []:
+Organization Name (eg, company) [Internet Widgits Pty Ltd]:
+Organizational Unit Name (eg, section) []:
+Common Name (e.g. server FQDN or YOUR name) []: yourbotdomainname
+Email Address []:
+Please enter the following 'extra' attributes
+to be sent with your certificate request
+A challenge password []:
+An optional company name []:
+---
+
    +
  • Another example:

    +
      +
    • Using Java keytool:
      keytool -genkey -alias yourbotdomainname -keyalg RSA -keystore yourkeystore.jks -keysize 2048
    • +
    +
  • +
+
---
+Enter keystore password:  
+Re-enter new password: 
+What is your first and last name?  [Unknown]: yourbotdomainname
+What is the name of your organizational unit?  [Unknown]:  
+What is the name of your organization?  [Unknown]:  
+What is the name of your City or Locality?  [Unknown]:  
+What is the name of your State or Province?  [Unknown]:  
+What is the two-letter country code for this unit?  [Unknown]:  
+Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?  
+[no]:  yes
+Enter key password for yourbotdomainname   
+(RETURN if same as keystore password): 
+---
+

This generates the initial keystore, from which you can then create a CSR like this:

+

keytool -certreq -alias yourbotdomainname -keystore yourkeystore.jks -file yourbotdomainname.csr

+
---
+Enter keystore password:
+---
+

To validate your certificate the Common Name (CN) has to match your webhook domain. Example, if you’re using https://www.example.com/example.php as a webhook address, the certificate CN has to be www.example.com.
So you need an exact match of the FQDN you’re setting for the webhook

+

There is an exception, if you’re using a SAN (Subject Alternative Name) the webhook address can either match the CN of your certificate, OR one of the SANs provided in the certificate. In most cases you’ll be using the CN.

+

Create your CSR and supply the contents of the file to your CA. Most CA’s are kind enough to give you an example command of the input format they expect.

+

cat yoursigningrequest.csr or cat yourbotdomainname.csr
Lets you have a look at the CSR we just generated:

+
+ +
+ +

That doesn’t seem to informative, but we can deduce that the file is in PEM format (ASCII base64 encoded) and contains a certificate signing request. Luckily it is possible to look at the human readable contents of the CSR. Use the following commands to double check if all fields are set correctly.

+
    +
  • Using OpenSSL
    openssl req -text -noout -verify -in yoursigningrequest.csr

    +
  • +
  • Using Java keytool
    keytool -printcertreq -v -file yourbotdomainname.csr

    +
  • +
+

Verify your CSR and supply it to your CA to get a certificate. We’ll use StartSSL as an example here. StartSSL allows you to set up to 5 names (SAN), Their intermediate certificate is also needed for a webhook to work, which makes for a nice complete example.

+

Go to the certificates wizard, enter the required hostname(s) for your SSL certificate (this is the CN you’ve also set in the CSR and an optional SAN).

+
+ +
+ +

In the example above we’ve chosen to set a CN (test.telegram.org), but also a SAN (sanexample.telegram.org) The CN given has to match the CN used for generating the CSR.
Set your CN (and optional SAN) and copy the contents of the yoursigningrequest.csr file.

+
+ +
+ +

Paste the contents, submit and you’re done.

+
+ +
+ +

Now you can download the created certificate directly. In the example used above you’ll receive a zip file with several PEM certificates. The root, intermediate and yourdomain certificate.
You need the intermediate and yourdomain to set a webhook with a StartSSL certificate.

+

You can inspect the set of certificates you’ve just downloaded.

+
    +
  • Here are some example commands:

    +
      +
    • Using OpenSSL:
      openssl x509 -in yourdomain.crt -text -noout

      +
    • +
    • Using Java keytool:
      keytool -printcert -v -yourdomain.crt

      +
    • +
    • Using Windows:
      StartSSL supplies certificates in PEM format with a .crt extension, on Windows you can view the contents of them with a quick double click. Extract the files or open the “Otherserver.zip” and double click each of the certificates for inspection. The details tab supplies you with extra information.
      Make sure you have a correct CN in the Subject-field of the yourdomain-certificate. If you're using a SAN, make sure that it is listed in the Subject Alternative Name-field.

      +
    • +
    +
  • +
+
+ +
+ +

With your fresh certificates at hand, you can now continue setting your webhook.

+
    +
  • A self-signed certificate
    +

    Using a self-signed certificate means you’ll forfeit on the chain of trust backed by a CA. Instead you are the CA. For this to work, a slight difference in setup is required. Because Telegram will have no chain of trust to verify your certificate, you have to use the generated public certificate as an input file when setting the webhook. Keep in mind that the certificate file has to be uploaded as multipart/form data in PEM encoded (ASCII BASE64) format.

    +
  • +
  • First let’s generate some certificates:

    +
      +
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"
      You’ll end up with 2 files, a private key and the public certificate file. Use YOURPUBLIC.PEM as input file for setting the webhook.

      +
    • +
    • Using Java keytool:
      keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

      +
      What is your first and last name?
      +[test.telegram.org]:
      +What is the name of your organizational unit?
      +[Unknown]:  
      +What is the name of your organization?
      +[Unknown]:  
      +What is the name of your City or Locality?
      +[Unknown]:  
      +What is the name of your State or Province?
      +[Unknown]:  
      +What is the two-letter country code for this unit?
      +[Unknown]:  
      +Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
      +[no]: yes
      +

      Once done you’ll need 2 more commands to export the public certificate file from the generated store (you’ll be using the store for your JVM and the PEM for setting the webhook)

      +
    • +
    • Convert the JKS to pkcs12 (intermediate step for conversion to PEM):
      keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

      +
    • +
    • Convert PKCS12 to PEM (requires OpenSSL)
      openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem -nokeys

      +
    • +
    • Using Windows:
      Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.
      certreq -new TEMPLATE.txt RequestFileOut generates a CSR.

      +
    • +
    • TEMPLATE.txt example file:

      +
      [NewRequest]
      +; At least one value must be set in this section
      +Subject = "CN=DOMAIN.EXAMPLE"
      +KeyLength = 2048
      +KeyAlgorithm = RSA
      +HashAlgorithm = sha256
      +;MachineKeySet = true
      +RequestType = Cert
      +UseExistingKeySet=false ;generates a new private key (for export)
      +Exportable = true ;makes the private key exportable with the PFX
      +
    • +
    +
  • +
+

A self-signed certificate is generated and installed, to use the certificate for a self-signed webhook you'll have to export it in PEM format.

+
    +
  • Windows continued:

    +
      +
    • You can have a look at the certificates in your store with:
      certutil -store -user my

      +
    • +
    • To export the installed certificate in DER format (intermediate step for conversion to PEM):
      certutil -user -store -split my SERIALNUMBER YOURDER.der

      +
    • +
    • Now you can convert the certificate to PEM:
      certutil -encode YOURDER.der YOURPEM.pem
      Remember that only the public certificate is needed as input for the self-signed webhook certificate parameter.
      certmgr.msc can also be used as a GUI to export the public part of self-signed certificate to PEM.

      +
    • +
    +
  • +
+

After following the above you'll end up with a nice self-signed certificate. You’ll still have to set the webhook, and handle SSL correctly.

+
How do I set a webhook for either type?
+

The setWebhook method is needed for both types. For a verified certificate with a trusted root CA, it’s enough to use the setWebhook method with just the URL parameter.

+
    +
  • A curl example for a verified certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

For a self-signed certificate an extra parameter is needed, certificate, with the public certificate in PEM format as data.

+
    +
  • A curl example for a self-signed certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" -F "certificate=@<YOURCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

The -F means we’re using the multipart/form-data-type to supply the certificate, the type of the certificate parameter is inputFile. Make sure that you’re supplying the correct type.

+

Both parameters for the setWebhook method are classed as optional. Calling the method with an empty URL parameter can be used to clear a previously set webhook.

+
    +
  • A curl example to clear a previous webhook :
    curl -F "url=" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

Keep in mind that the URL parameter starts with https:// when setting a webhook. By default that means we’re knocking at your door on port 443. If you want to use another port (80,88 or 8443), you’ll have to specify the port in the URL parameter.

+
    +
  • Example:
    url=https://<YOURDOMAIN.EXAMPLE>:88/<WEBHOOKLOCATION>
  • +
+
Setting a verified webhook with an untrusted root
+

If you already have a verified certificate and our servers don’t trust your root CA, we have an alternative way for you to set a webhook. Instead of using the setWebhook method without the certificate parameter, you can use the self-signed method. Your CA's root certificate has to be used as an inputFile for the certificate parameter.

+
    +
  • A curl example to supply an untrusted root certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>" -F "certificate=@<YOURCAROOTCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
    Before you can do this, you need the root certificate of your certificate’s CA. Most CA’s supply their root certificates in several different formats (PEM/DER/etc.). Visit your CA’s website, and download the Root certificate indicated for your verified certificate.
  • +
+

You can use these commands to quickly convert a DER formatted root certificate to PEM:

+
    +
  • Using OpenSSL:
    openssl x509 -inform der -in root.cer -out root.pem

    +
  • +
  • Using Java keytool:
    keytool -import -alias Root -keystore YOURKEYSTORE.JKS -trustcacerts -file ROOTCERT.CER
    The root certificate needs to be imported in your keystore first:
    keytool -exportcert -alias Root -file <YOURROOTPEMFILE.PEM> -rfc -keystore YOURKEYSTORE.JKS

    +
  • +
+

Once done, set your webhook with the root-pem-file and you’ll be good to go. If you need more pointers, have a look at the self-signed part of this guide.

+
Supplying an intermediate certificate
+

Once you’ve crafted your certificate, your CA might present you with a nice bundle. Most bundles contain a root certificate, your public certificate and sometimes an intermediate certificate. StartSSL is one of many CA’s that’ll supply such an intermediate beast. This certificate has to be supplied in the chain of certificates you’re presenting to us when we connect to your server. If an intermediate was used to sign your certificate but isn’t supplied to our servers, we won’t be able to verify the chain of trust and your webhook will not work.

+

If your webhook isn’t working and you’re wondering if the chain is complete:

+
    +
  • Check with your certificate provider if you need an intermediate certificate.
  • +
  • Verify your certificate chain.
    Search online for Symantec crypto report or Qualys ssl. 
    +Both supply tools to verify your setup.
    +
  • +
+

Here’s an example of a complete chain, note that in this case 2 intermediate certificates have been supplied.

+
+ +
+ +

Even though your browser might not complain when visiting your page, an incomplete chain will not work for your webhook. If your chain is incomplete we have some tips to add them to your current setup:

+
    +
  • Apache:
    Add the intermediate certificate to the end of the file configured in the SSLCertificateFile directive of your virtual host configuration. If you’re using an older version than Apache 2.4.8, you may use the SSLCertificateChainFile directive instead.

    +
  • +
  • Nginx:
    Add the intermediate certificate to the end of the file configured in the ssl_certificate_key directive of your virtual host configuration.

    +
  • +
  • A quick command for doing this correctly:
    cat your_domain_name.pem intermediate.pem >> bundle.pem
    Make sure the order is correct, expect failure otherwise.

    +
  • +
  • Java keytool:
    keytool -import -trustcacerts -alias intermediate -file intermediate.pem -keystore YOURKEYSTORE.jks

    +
  • +
+

The end result of all this is a complete certificate chain, backed by either a root certificate we trust or, in the case of an untrusted root, a root certificate you're supplying to us. Make sure to verify your setup again after adding the intermediate, once done, you're good to go!

+
Testing your bot with updates
+
    +
  • Update examples
    A set of example updates, which comes in handy for testing your bot.

    +
      +
    • Message with text using curl:

      +
      curl --tlsv1.2 -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test",
      +     "username":"Test"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test",
      +     "username":"Test"
      +  },
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +

      --tlsv1.2 will force using TLS1.2.

      +
    • +
    • Message with text using Postman:

      +
      + +
      +
    • +
    +
  • +
  • More examples in curl:

    +
      +
    • Message with text:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "type": "private",
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Forwarded message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "type": "private",
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "forward_from": {
      +     "last_name":"Forward Lastname",
      +     "id": 222222,
      +     "first_name":"Forward Firstname"
      +  },
      +  "forward_date":1441645550,
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Forwarded channel message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "forward_from": {
      +     "id": -10000000000,
      +     "type": "channel",
      +     "title": "Test channel"
      +  },
      +  "forward_date":1441645550,
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with a reply:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"/start",
      +  "reply_to_message":{
      +      "date":1441645000,
      +      "chat":{
      +          "last_name":"Reply Lastname",
      +          "type": "private",
      +          "id":1111112,
      +          "first_name":"Reply Firstname",
      +          "username":"Testusername"
      +      },
      +      "message_id":1334,
      +      "text":"Original"
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Edited message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"edited_message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"Edited text",
      +  "edit_date": 1441646600
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with entities:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"Bold and italics",
      +  "entities": [
      +      {
      +          "type": "italic",
      +          "offset": 9,
      +          "length": 7
      +      },
      +      {
      +          "type": "bold",
      +          "offset": 0,
      +          "length": 4
      +      }
      +      ]
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with audio:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "audio": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "duration": 243,
      +      "mime_type": "audio/mpeg",
      +      "file_size": 3897500,
      +      "title": "Test music file"
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Voice message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "voice": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "duration": 5,
      +      "mime_type": "audio/ogg",
      +      "file_size": 23000
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with a document:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "document": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "file_name": "Testfile.pdf",
      +      "mime_type": "application/pdf",
      +      "file_size": 536392
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"inline_query":{
      +  "id": 134567890097,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "query": "inline query",
      +  "offset": ""
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Chosen inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"chosen_inline_result":{
      +  "result_id": "12",
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "query": "inline query",
      +  "inline_message_id": "1234csdbsk4839"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Callback query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"callback_query":{
      +  "id": "4382bfdwdsb323b2d9",
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "data": "Data from button callback",
      +  "inline_message_id": "1234csdbsk4839"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +That's all we have for now!
    • +
    +
  • +
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/cdn.html b/data/core.telegram.org/cdn.html new file mode 100644 index 0000000000..197bb8e0e2 --- /dev/null +++ b/data/core.telegram.org/cdn.html @@ -0,0 +1,210 @@ + + + + + Encrypted CDNs for Speed and Security + + + + + + + + + + + + + +
+ +
+
+
+
+

Encrypted CDNs for Speed and Security

+ +

Following the launch of version 4.2 of the official apps, Telegram client apps may be required to download popular files that were published in public channels with more than 100,000 members from secondary Content Delivery Network data centers. These CDN DCs are located in regions with significant Telegram traffic where we wouldn't want to place Telegram servers for various reasons.

+

The CDN DCs are not a part of the Telegram cloud and should be considered enemy territory. For this reason, each file that is to be sent to these CDN DCs is encrypted with a unique key using AES-256-CTR encryption. The CDN can't access the data it stores because these keys are only accessible to the main MTProto server and to the authorized client.

+
+

See also: More about CDNs and governments in the Advanced FAQ

+
+

How this works

+

When a file from a public channel with ~100,000 members becomes popular in a particular region, the Telegram server may encrypt this file with a unique AES-256-CTR key and send it to a relevant CDN DC for storage.

+

When a file is stored in a CDN DC close to the end user, the download speed will be much higher because the data needs to travel smaller distances and will likely avoid many bottlenecks that exist between regions.

+

This is secure because CDN DCs are treated the same way as internet providers / random third parties:

+
    +
  • CDN DCs don‘t have the keys to decrypt files that are stored there, so they can’t access the data even if a DC becomes compromised.
  • +
  • Encrypted files fragments are protected from tampering by their SHA-256 hash which is checked on the client upon receipt.
  • +
  • No private data is stored in or passed to the CDN DCs.
  • +
  • The server only allows media from public channels with more than 100,000 subscribers to be cached in CDN DCs (this includes media forwarded from those channels and viral media that originated from other large public channels).
  • +
+
+ +
+ +

CDNs are very limited when it comes to communication: the master data center only uploads encrypted files for storage and will accept no data from the CDN. The client apps only download encrypted files and accept no other updates. The client apps obtain the keys necessary to decrypt the file from the main Telegram server and verify the integrity of the file by its hash, which means that the CDN may only supply the correct file – anything different will be immediately discarded by the client.

+

CDN DCs do not store files on hard disks – only in memory. When a CDN server runs out of memory, a simple LRU algorithm is used to replace the least popular files with new ones.

+

How CDN DCs are different from the master DCs

+
    +
  • CDNs may not be trusted.
  • +
  • Client developers can use help.getCdnConfig to obtain a list of public RSA keys for CDN DCs, which are different from public RSA keys of the master DCs.
  • +
  • CDNs support only the following methods: upload.getCdnFile, initConnection, invokeWithLayer.
  • +
  • When working with CDNs, client developers must remember that auth_key may be deleted at any given moment (resulting in a -404 error, in which case a new key must be generated).
  • +
  • Client apps must not accept updates from CDN DCs (apps should only accept updates from their main connection to the master DC).
  • +
  • Clients must not allow the CDN DCs to substitute replies to queries sent to other DCs.
  • +
  • Clients must not send private user info that is passed in initConnection to the CDNs.
  • +
+

Getting files from a CDN

+

The API may return the upload.fileCdnRedirect constructor after an upload.getFile query. In this case, the client must request the required file from a CDN DC. The dc_id in the response is the id of the new CDN. The IP address for the connection will be available in help.getConfig, same as with the master DCs. The corresponding dcOption will have the flag cdn:flags.3?true.

+

Once a successful connection to the CDN-dc_id is established, the client must generate an auth_key (after confirming that the public RSA MTProto key of the CDN DC matches one from the list returned in help.getCdnConfig). Then the client must perform an upload.getCdnFile for each offset. For files of an unknown size it is necessary to repeat the query until an empty reply is returned.

+

upload.getCdnFile may return the upload.cdnFileReuploadNeeded constructor. In this case, the client needs to send an upload.reuploadCdnFile request to the DC that got the original upload.getFile request. Once upload.reuploadCdnFile is successfull, the app needs to request the file from the CDN DC again.

+

The main DC for a file is the DC where its main copy is stored (not to be confused with the main DC of the user) – either userProfilePhoto.dc_id, chatPhoto.dc_id, photo.dc_id, or document.dc_id.

+

Decrypting files

+

In upload.fileCdnRedirect, the server sends a decryption key and IV for the file (the fields encryption_key:bytes and encryption_iv:bytes respectively).

+

Having received a portion of encrypted data from the CDN DC inside upload.cdnFile, the client must decrypt this data using AES-256-CTR. For IV, it should use the value of encryption_iv, modified in the following manner: for each offset replace the last 4 bytes of the encryption_iv with offset / 16 in big-endian. This allows to effectively decrypt a file and to use random access to a file's content (e.g., for streaming).

+

Verifying files

+

In order to confirm that the CDN DC passed an untampered file, clients must verify hashes for each downloaded part. upload.fileCdnRedirect, upload.reuploadCdnFile and upload.getCdnFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

+

Before saving each portion of the data received from the CDN DC into the file, the client must confirm that its hash matches the hash that was received from the master DC. If missing a hash for any file part, client developers must use the upload.getCdnFileHashes method to obtain the missing hash.

+

Schema

+
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
+
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+
+
+dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+
+cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
+
+
+cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
+
+---functions---
+
+// CDN DC
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
+
+// Master DC
+upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
+upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
+
+help.getCdnConfig#52029342 = CdnConfig;
+

Restrictions on upload.getFile and upload.getCdnFile parameters

+
    +
  • offset must be divisible by 4096 bytes
  • +
  • limit must be divisible by 4096 bytes
  • +
  • 1048576 (1MB) must be divisible by limit
  • +
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024)
    (file parts that are being downloaded must always be inside the same megabyte-sized fragment)
  • +
+

Possible errors and their meanings

+ + + + + + + + + + + + + + + + + + +
upload.getCdnFileFILE_TOKEN_INVALIDThe CDN DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileFILE_TOKEN_INVALIDThe master DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileREQUEST_TOKEN_INVALIDThe master DC did not accept the request_token from the CDN DC. Continue downloading the file from the master DC using upload.getFile.
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/cdn/faq_ir.html b/data/core.telegram.org/cdn/faq_ir.html new file mode 100644 index 0000000000..0ba8a4f1a6 --- /dev/null +++ b/data/core.telegram.org/cdn/faq_ir.html @@ -0,0 +1,142 @@ + + + + + شبکه‌های تحویل محتوا (CDN) رمزنگاری شده + + + + + + + + + + + + + +
+ +
+
+
+
+

شبکه‌های تحویل محتوا (CDN) رمزنگاری شده

+ +
+ + +

از نسخهٔ ۴.۲ تلگرام ما از CDN رمزنگاری شده برای ذخیره فایل‌های کانال های عمومی با بیش از ۱۰۰٫۰۰۰ عضو پشتیبانی می‌کنیم. نقاط ذخیره سازی CDN در مناطقی در نظر گرفته شده اند که تلگرام ترافیک زیادی دارد ولی ما به دلایل مختلف تمایلی به قرارگیری سرورهای تلگرام در آن مناطق نداریم.

+
+

برای اطلاعات فنی در خصوص نحوه پیاده سازی، رمزنگاری و تایید اعتبار داده‌ها راهنمای CDN در این لینک را ببینید. همچنین برای توضیحات سیستم از طرف پاول دورُف به این پست مراجعه کنید.

+
+

سوال: چرا تصمیم به استفاده از CDN گرفتید؟

+

ما از سرور‌های توزیع شده خود برای افزایش سرعت دانلود در مناطق بدون سانسور که در آنها آزادی بیان تضمین شده‌است استفاده می‌کنیم. و حتی در آن مناطق نیز به آنها اعتماد نمی‌کنیم. اما وقتی تلگرام در مناطق دیگر به شدت محبوب می‌شود، فقط می‌توانیم روی CDNها تکیه کنیم؛ که با آنها از نقطه نظر فنی مانند سرویس‌دهنده‌‌های اینترنت (ISP) رفتار می‌کنیم و آنها فقط داده‌های رمزنگاری شده‌ای را که قادر به کشف رمز آن نیستند دریافت می‌کنند.
به لطف این فناوری، سرعت دانلود عکس‌ها و فیلم‌هایی که به صورت عمومی منتشر می‌شوند در مناطقی نظیر ترکیه، اندونزی،‌ عربستان سعودی، هند، ایران و عراق به مراتب افزایش می‌یابد، بدون اینکه کمترین خدشه‌ای به امنیت وارد شود.

+

سوال: آیا CDN می‌تواند فایل‌ها را رمزگشایی کند؟

+

خیر. هر فایلی که به مراکز داده CDN ارسال می‌شود، با یک کلید منحصر به فرد با استفاده از تکنولوژی AES-256-CTR رمزگذاری می‌شود. CDN دسترسی به اطلاعاتی که ذخیره می‌کند ندارد، چرا که این کلید‌ها تنها در سرور MTProto (سرور رمزگذاری) اصلی و دستگاه کاربر قابل دسترسی هستند.

+

سوال: آیا CDNها می‌توانند اطلاعات را با اطلاعات دلخواه خودشان جایگزین کنند؟

+

خیر. اطلاعات و داده‌های دانلود شده (دریافتی)‌ از سمت نقاط ذخیره سازی CDN همیشه از طرف Telegram بوسیله رمزنگاری hash تایید و بررسی می‌شود: بدين ترتیب هکرها یا افراد متجاوز نمی‌توانند هیچ فایلی را جایگزین کنند.

+

سوال: آيا CDN مى‌تواند هر نوع فايل را حذف كند؟

+

خير. CDNها فقط كپى‌ فايل هاى رمزنگارى شده را ذخيره مى‌كنند، فايل‌هاى اصلي در سرورهای تلگرام ذخيره مى‌شوند. كاربر تنها اعلان دريافت فايل را از طريق سرور تلگرام مى‌گيرد. اگر كه CDN فايل مورد نظر را به كاربر ارسال نكند، كاربر اين فايل را مستقيماً از سرور تلگرام دريافت خواهد كرد.

+

سوال: آيا CDN ها مى توانند برای سانسور استفاده بشوند؟

+

خير. تمامى فايل‌هاى اصلي در سرورهای تلگرام ذخيره مى‌شوند. CDN ها فقط داده هاى رمزگذاري شده را دريافت مى‌كنند و قادر نيستند آن را رمزگشايى و يا هيچ گونه داده را جايگزين كنند. اگر مشكلى پيش آيد، فايل مورد نظر مستقيما از سرور هاى تلگرام به كاربران ارسال می‌شود. كاربران هميشه داده هایشان را دريافت مى‌كنند و هيچ كس نمى‌تواند مانع آنها بشود.

+

سوال: آیا می‌توانم این موضوع را بررسی کنم؟

+

بله. همه می‌توانند روش ما برای پیاده‌سازی CDN را با بررسی کد‌های Source Code برنامه‌های تلگرام و بررسی ترافیک داده بررسی کنند.

+

سوال: آیا این شامل اطلاعات خصوصی هم می‌شود؟

+

خیر. نقاط ذخیره سازی CDN بخشی از سرور اَبری تلگرام نیستند. CDNها فقط برای ذخیره‌سازی فایل‌های پر طرفدار از کانال‌های پر بازدید استفاده می‌شوند. اطلاعات خصوصی و شخصی هرگز به آنها راه پیدا نمی‌کنند.

+

سوال: آیا این با درخواست‌های دولت‌ها برای انتقال اطلاعات خصوصی به قلمرو آن‌ها مرتبط هست؟

+

خیر. ما وارد هیچ توافق یا تفاهمی با دولت‌ها در این مورد نشده‌ایم و CDNها بخشی از هیچ معامله‌ای نیستند. این به دلیل غیر منطقی بودن قوانین محلی نیست – ما هیچ‌گاه سرورهایمان را به کشوری با سابقه سانسور اینترنتی انتقال نمی‌دهیم.

+

تنها هدف استفاده از CDNها این است که کیفیت اتصال در مناطق با تقاضای بالا، که تلگرام نمی‌تواند سرورهای خود را به آنجا منتقل کند، با روشی ایمن، افزایش یابد.

+

سوال: آیا این موضوع می‌تواند به برخی کشورها، قدرت تسلط بر تلگرام بدهد؟

+

خیر. ما احتیاط ویژه‌ای به خرج داده‌ایم تا مطمئن شویم هیچ کشوری از طریق نقاط ذخیره سازی CDN به قدرت نفوذ روی تلگرام دست نیابد:
- CDNها و نقاط آن به تلگرام تعلق نداشته و همه ریسک آن به گردن شرکت ثالثی که نقاط ذخیره سازی CDN در سراسر دنیا را برای ما تامین می‌کند خواهد بود.
- ما هیچ سرمایه‌گذاری‌ای روی این CDNها انجام نمی‌دهیم و تنها بابت ترافیک مصرفی برای انتقال موارد ذخیره شده از خوشهٔ کامپیوترهای اصلی خودمان به کاربر نهایی، هزینه پرداخت می‌کنیم.

+

در نتیجه، اگر کشوری تصمیم به دستکاری CDN در منطقه خودش بگیرد، به چیزی جز پایین آوردن کیفیت اتصال شهروندان خودشان دست نمی‌یابد – و تلگرام هیچ چیز با ارزشی را از دست نخواهد داد.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/cdn/faq_ir/durov.html b/data/core.telegram.org/cdn/faq_ir/durov.html new file mode 100644 index 0000000000..606b94f25a --- /dev/null +++ b/data/core.telegram.org/cdn/faq_ir/durov.html @@ -0,0 +1,133 @@ + + + + + توضيحات CDNهاى رمزنگارى شده + + + + + + + + + + + + + +
+ +
+
+
+
+

توضيحات CDNهاى رمزنگارى شده

+ +
+ +
+

ترجمه فارسى اين پست از كانال رسمى پاول دورُف در تلگرام در زير آمده است:

+
+

همانطور که پیشتر قول داده بودم، جزئیات بیشتری درباره اینکه چطور نقاط ذخیره سازی CDN ثالث می‌توانند سرعت دانلود محتوای عمومیِ پربازدید را در مناطقی که تلگرام تمایل به نصب سرورهای خود در آنجا ندارد، به روشی امن بالا ببرد، منتشر می‌کنم.

+ +

همانطور که مشاهده می‌کنید، نقاط ذخیره سازی CDN هیچ ارتباطی با مساله انتقال سرورهای تلگرام یا رعایت قوانین غیر منطقی محلی ندارند. CDNها صرفا ابزاری جهت ارتقا کیفیت اتصال میلیون‌ها کاربر، به روشی امن، هستند. ما با این نقاط CDN دقیقا همانطور رفتار می‌کنیم که با مراکز تامین کننده اینترنت (ISP) شما رفتار می‌کنیم. آنها صرفا مشتی دادهٔ رمزنگاری شده دریافت می‌کنند که قادر به کشف رمز آن نخواهند بود.

+

خوبی تلگرام این است که وقتی بحث امنیت مطرح می‌شود، لازم نیست صرفا روی گفته‌های من حساب کنید. هر کسی می‌تواند نحوه اجرای نقاط CDN در نسخه بروز شده تلگرام برای iOS و اندروید را بررسی کند. همچنین اگر تمایل داشته‌باشید می‌توانید نگاهی به اسناد ما در لینک فوق بیندازید، تا مطمئن شوید همه چیز امن است.

+

ما با یک تامین کننده بین‌المللی CDN همکاری می‌کنیم که با نقاط ذخیره سازی خود در سراسر دنیا به ما کمک می‌کند. اگر یک دولت محلی تصمیم به توقیف یک نقطه ذخیره سازی در مرزهای خود بگیرد، تلگرام چیزی از دست نخواهد داد؛ چرا که آن CDN جز اموال ما نیست و حتی در تئوری کوچکترین اطلاعات خصوصی تحت تاثیر این عمل قرار نخواهد گرفت. بنابراین به قوانین و دولت‌های محلی وابستگی پیدا نمی‌کنیم و هیچ ریسک حقوقی یا مالی نخواهیم داشت، اما سرعت دانلود محتوای عمومی را بطور چشمگیری افزایش می‌دهیم.

+

چنانچه، با وجود توضیحات فوق، باز هم برخی رسانه‌ها از تیتر های جنجالی مانند «تلگرام سرورهایش را به کره شمالی انتقال داد» استفاده کردند، لطفا مارا با اطلاع رسانی در مورد حقیقت ماجرا که در لینک‌های این پیام آمده است، یاری کنید. بابت مطالعه این مطلب از شما تشکر می‌کنم و مثل همیشه، در همین کانال، شما را از هر خبر بین المللی در مورد تلگرام مطلع خواهم کرد.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.authorizationForm b/data/core.telegram.org/constructor/account.authorizationForm new file mode 100644 index 0000000000..f12161fe65 --- /dev/null +++ b/data/core.telegram.org/constructor/account.authorizationForm @@ -0,0 +1,174 @@ + + + + + account.authorizationForm + + + + + + + + + + + + + +
+ +
+
+
+ +

account.authorizationForm

+ +

Telegram Passport authorization form

+

+ +
+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
required_typesVector<SecureRequiredType>Required Telegram Passport documents
valuesVector<SecureValue>Already submitted Telegram Passport documents
errorsVector<SecureValueError>Telegram Passport errors
usersVector<User>Info about the bot to which the form will be submitted
privacy_policy_urlflags.0?stringURL of the service's privacy policy
+

Type

+

account.AuthorizationForm

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.authorizations b/data/core.telegram.org/constructor/account.authorizations new file mode 100644 index 0000000000..6f44355f75 --- /dev/null +++ b/data/core.telegram.org/constructor/account.authorizations @@ -0,0 +1,147 @@ + + + + + account.authorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.authorizations

+ +

Logged-in sessions

+

+ +
+
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
authorizationsVector<Authorization>Logged-in sessions
+

Type

+

account.Authorizations

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.autoDownloadSettings b/data/core.telegram.org/constructor/account.autoDownloadSettings new file mode 100644 index 0000000000..e9d893123b --- /dev/null +++ b/data/core.telegram.org/constructor/account.autoDownloadSettings @@ -0,0 +1,157 @@ + + + + + account.autoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.autoDownloadSettings

+ +

Media autodownload settings

+

+ +
+
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lowAutoDownloadSettingsLow data usage preset
mediumAutoDownloadSettingsMedium data usage preset
highAutoDownloadSettingsHigh data usage preset
+

Type

+

account.AutoDownloadSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.chatThemes b/data/core.telegram.org/constructor/account.chatThemes new file mode 100644 index 0000000000..77eac280a5 --- /dev/null +++ b/data/core.telegram.org/constructor/account.chatThemes @@ -0,0 +1,155 @@ + + + + + account.chatThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.chatThemes

+ +

Available chat themes

+

+ +
+
account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
themesVector<ChatTheme>Available chat themes
+

Type

+

account.ChatThemes

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.chatThemesNotModified b/data/core.telegram.org/constructor/account.chatThemesNotModified new file mode 100644 index 0000000000..6c8eb40de5 --- /dev/null +++ b/data/core.telegram.org/constructor/account.chatThemesNotModified @@ -0,0 +1,132 @@ + + + + + account.chatThemesNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

account.chatThemesNotModified

+ +

The available chat themes were not modified

+

+ +
+
account.chatThemesNotModified#e011e1c4 = account.ChatThemes;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

account.ChatThemes

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.contentSettings b/data/core.telegram.org/constructor/account.contentSettings new file mode 100644 index 0000000000..898494bafa --- /dev/null +++ b/data/core.telegram.org/constructor/account.contentSettings @@ -0,0 +1,157 @@ + + + + + account.contentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.contentSettings

+ +

Sensitive content settings

+

+ +
+
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueWhether viewing of sensitive (NSFW) content is enabled
sensitive_can_changeflags.1?trueWhether the current client can change the sensitive content settings to view NSFW content
+

Type

+

account.ContentSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.password b/data/core.telegram.org/constructor/account.password new file mode 100644 index 0000000000..a6d3dc0217 --- /dev/null +++ b/data/core.telegram.org/constructor/account.password @@ -0,0 +1,213 @@ + + + + + account.password + + + + + + + + + + + + + +
+ +
+
+
+ +

account.password

+ +

Configuration for two-factor authorization

+

+ +
+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_recoveryflags.0?trueWhether the user has a recovery method configured
has_secure_valuesflags.1?trueWhether telegram passport is enabled
has_passwordflags.2?trueWhether the user has a password
current_algoflags.2?PasswordKdfAlgoThe KDF algorithm for SRP two-factor authentication of the current password
srp_Bflags.2?bytesSrp B param for SRP authorization
srp_idflags.2?longSrp ID param for SRP authorization
hintflags.3?stringText hint for the password
email_unconfirmed_patternflags.4?stringA password recovery email with the specified pattern is still awaiting verification
new_algoPasswordKdfAlgoThe KDF algorithm for SRP two-factor authentication to use when creating new passwords
new_secure_algoSecurePasswordKdfAlgoThe KDF algorithm for telegram passport
secure_randombytesSecure random string
pending_reset_dateflags.5?intThe 2FA password will be automatically removed at this date, unless the user cancels the operation
+

Type

+

account.Password

+

Related pages

+

Telegram Passport Manual

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.passwordInputSettings b/data/core.telegram.org/constructor/account.passwordInputSettings new file mode 100644 index 0000000000..a0f05063c4 --- /dev/null +++ b/data/core.telegram.org/constructor/account.passwordInputSettings @@ -0,0 +1,176 @@ + + + + + account.passwordInputSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.passwordInputSettings

+ +

Settings for setting up a new password

+

+ +
+
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
new_algoflags.0?PasswordKdfAlgoThe SRP algorithm to use
new_password_hashflags.0?bytesThe computed password hash
hintflags.0?stringText hint for the password
emailflags.1?stringPassword recovery email
new_secure_settingsflags.2?SecureSecretSettingsTelegram passport settings
+

Type

+

account.PasswordInputSettings

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.passwordSettings b/data/core.telegram.org/constructor/account.passwordSettings new file mode 100644 index 0000000000..195be40875 --- /dev/null +++ b/data/core.telegram.org/constructor/account.passwordSettings @@ -0,0 +1,161 @@ + + + + + account.passwordSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.passwordSettings

+ +

Private info associated to the password info (recovery email, telegram passport info & so on)

+

+ +
+
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
emailflags.0?string2FA Recovery email
secure_settingsflags.1?SecureSecretSettingsTelegram passport settings
+

Type

+

account.PasswordSettings

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.privacyRules b/data/core.telegram.org/constructor/account.privacyRules new file mode 100644 index 0000000000..46337ebbae --- /dev/null +++ b/data/core.telegram.org/constructor/account.privacyRules @@ -0,0 +1,157 @@ + + + + + account.privacyRules + + + + + + + + + + + + + +
+ +
+
+
+ +

account.privacyRules

+ +

Privacy rules

+

+ +
+
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
rulesVector<PrivacyRule>Privacy rules
chatsVector<Chat>Chats to which the rules apply
usersVector<User>Users to which the rules apply
+

Type

+

account.PrivacyRules

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.resetPasswordFailedWait b/data/core.telegram.org/constructor/account.resetPasswordFailedWait new file mode 100644 index 0000000000..4a83d90f5d --- /dev/null +++ b/data/core.telegram.org/constructor/account.resetPasswordFailedWait @@ -0,0 +1,147 @@ + + + + + account.resetPasswordFailedWait + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPasswordFailedWait

+ +

You recently requested a password reset that was canceled, please wait until the specified date before requesting another reset.

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
retry_dateintWait until this date before requesting another reset.
+

Type

+

account.ResetPasswordResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.resetPasswordOk b/data/core.telegram.org/constructor/account.resetPasswordOk new file mode 100644 index 0000000000..017da1a3ab --- /dev/null +++ b/data/core.telegram.org/constructor/account.resetPasswordOk @@ -0,0 +1,132 @@ + + + + + account.resetPasswordOk + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPasswordOk

+ +

The 2FA password was reset successfully.

+

+ +
+
account.resetPasswordOk#e926d63e = account.ResetPasswordResult;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

account.ResetPasswordResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.resetPasswordRequestedWait b/data/core.telegram.org/constructor/account.resetPasswordRequestedWait new file mode 100644 index 0000000000..4eec3d9720 --- /dev/null +++ b/data/core.telegram.org/constructor/account.resetPasswordRequestedWait @@ -0,0 +1,147 @@ + + + + + account.resetPasswordRequestedWait + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPasswordRequestedWait

+ +

You successfully requested a password reset, please wait until the specified date before finalizing the reset.

+

+ +
+
account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
until_dateintWait until this date before finalizing the reset.
+

Type

+

account.ResetPasswordResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.sentChangePhoneCode b/data/core.telegram.org/constructor/account.sentChangePhoneCode new file mode 100644 index 0000000000..ff48a68f29 --- /dev/null +++ b/data/core.telegram.org/constructor/account.sentChangePhoneCode @@ -0,0 +1,161 @@ + + + + + account.sentChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sentChangePhoneCode

+ +

Sent change phone code

+

+ +
+
Constructor schema is available as of layer 50. Switch »

+

Parameters

+ + + + + + + + + + + + + +
phone_code_hashstringChange phone code hash
send_call_timeoutintCall timeout
+

Type

+

account.SentChangePhoneCode

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.sentEmailCode b/data/core.telegram.org/constructor/account.sentEmailCode new file mode 100644 index 0000000000..9827a5cb18 --- /dev/null +++ b/data/core.telegram.org/constructor/account.sentEmailCode @@ -0,0 +1,155 @@ + + + + + account.sentEmailCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sentEmailCode

+ +

The sent email code

+

+ +
+
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
email_patternstringThe email (to which the code was sent) must match this pattern
lengthintThe length of the verification code
+

Type

+

account.SentEmailCode

+

Related pages

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.takeout b/data/core.telegram.org/constructor/account.takeout new file mode 100644 index 0000000000..3f1dea5d51 --- /dev/null +++ b/data/core.telegram.org/constructor/account.takeout @@ -0,0 +1,147 @@ + + + + + account.takeout + + + + + + + + + + + + + +
+ +
+
+
+ +

account.takeout

+ +

Takout info

+

+ +
+
account.takeout#4dba4501 id:long = account.Takeout;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongTakeout ID
+

Type

+

account.Takeout

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.themes b/data/core.telegram.org/constructor/account.themes new file mode 100644 index 0000000000..08714a793a --- /dev/null +++ b/data/core.telegram.org/constructor/account.themes @@ -0,0 +1,155 @@ + + + + + account.themes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.themes

+ +

Installed themes

+

+ +
+
account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
themesVector<Theme>Themes
+

Type

+

account.Themes

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.wallPapers b/data/core.telegram.org/constructor/account.wallPapers new file mode 100644 index 0000000000..8eb2dd9d90 --- /dev/null +++ b/data/core.telegram.org/constructor/account.wallPapers @@ -0,0 +1,155 @@ + + + + + account.wallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.wallPapers

+ +

Installed wallpapers

+

+ +
+
account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
wallpapersVector<WallPaper>Wallpapers
+

Type

+

account.WallPapers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.wallPapersNotModified b/data/core.telegram.org/constructor/account.wallPapersNotModified new file mode 100644 index 0000000000..47da3801ad --- /dev/null +++ b/data/core.telegram.org/constructor/account.wallPapersNotModified @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..cb093d4cd7 --- /dev/null +++ b/data/core.telegram.org/constructor/account.webAuthorizations @@ -0,0 +1,152 @@ + + + + + account.webAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.webAuthorizations

+ +

Web authorizations

+

+ +
+
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
authorizationsVector<WebAuthorization>Web authorization list
usersVector<User>Users
+

Type

+

account.WebAuthorizations

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/accountDaysTTL.html b/data/core.telegram.org/constructor/accountDaysTTL.html new file mode 100644 index 0000000000..c0ef3668e3 --- /dev/null +++ b/data/core.telegram.org/constructor/accountDaysTTL.html @@ -0,0 +1,147 @@ + + + + + accountDaysTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

accountDaysTTL

+ +

Time to live in days of the current account

+

+ +
+
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
daysintThis account will self-destruct in the specified number of days
+

Type

+

AccountDaysTTL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.authorization b/data/core.telegram.org/constructor/auth.authorization new file mode 100644 index 0000000000..6c17405da0 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.authorization @@ -0,0 +1,159 @@ + + + + + auth.authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.authorization

+ +

Contains user authorization info.

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
tmp_sessionsflags.0?intTemporary passport sessions
userUserInfo on authorized user
+

Type

+

auth.Authorization

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.authorizationSignUpRequired b/data/core.telegram.org/constructor/auth.authorizationSignUpRequired new file mode 100644 index 0000000000..d66bde469d --- /dev/null +++ b/data/core.telegram.org/constructor/auth.authorizationSignUpRequired @@ -0,0 +1,155 @@ + + + + + auth.authorizationSignUpRequired + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.authorizationSignUpRequired

+ +

An account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up

+

+ +
+
auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
terms_of_serviceflags.0?help.TermsOfServiceTelegram's terms of service: the user must read and accept the terms of service before signing up to telegram
+

Type

+

auth.Authorization

+

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.codeTypeCall b/data/core.telegram.org/constructor/auth.codeTypeCall new file mode 100644 index 0000000000..bceaa717e7 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.codeTypeCall @@ -0,0 +1,132 @@ + + + + + auth.codeTypeCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.codeTypeCall

+ +

Type of verification code that will be sent next if you call the resendCode method: SMS code

+

+ +
+
auth.codeTypeCall#741cd3e3 = auth.CodeType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

auth.CodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.codeTypeFlashCall b/data/core.telegram.org/constructor/auth.codeTypeFlashCall new file mode 100644 index 0000000000..9a3b9150f6 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.codeTypeFlashCall @@ -0,0 +1,132 @@ + + + + + auth.codeTypeFlashCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.codeTypeFlashCall

+ +

Type of verification code that will be sent next if you call the resendCode method: SMS code

+

+ +
+
auth.codeTypeFlashCall#226ccefb = auth.CodeType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

auth.CodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.codeTypeSms b/data/core.telegram.org/constructor/auth.codeTypeSms new file mode 100644 index 0000000000..4929e6b1f8 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.codeTypeSms @@ -0,0 +1,132 @@ + + + + + auth.codeTypeSms + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.codeTypeSms

+ +

Type of verification code that will be sent next if you call the resendCode method: SMS code

+

+ +
+
auth.codeTypeSms#72a3158c = auth.CodeType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

auth.CodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.exportedAuthorization b/data/core.telegram.org/constructor/auth.exportedAuthorization new file mode 100644 index 0000000000..9e01321cea --- /dev/null +++ b/data/core.telegram.org/constructor/auth.exportedAuthorization @@ -0,0 +1,152 @@ + + + + + auth.exportedAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.exportedAuthorization

+ +

Data for copying of authorization between data centres.

+

+ +
+
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongcurrent user identifier
bytesbytesauthorizes key
+

Type

+

auth.ExportedAuthorization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.loginToken b/data/core.telegram.org/constructor/auth.loginToken new file mode 100644 index 0000000000..c487be56f4 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.loginToken @@ -0,0 +1,155 @@ + + + + + auth.loginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.loginToken

+ +

Login token (for QR code login)

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
expiresintExpiry date of QR code
tokenbytesToken to render in QR code
+

Type

+

auth.LoginToken

+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.loginTokenMigrateTo b/data/core.telegram.org/constructor/auth.loginTokenMigrateTo new file mode 100644 index 0000000000..64b21065c3 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.loginTokenMigrateTo @@ -0,0 +1,152 @@ + + + + + auth.loginTokenMigrateTo + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.loginTokenMigrateTo

+ +

Repeat the query to the specified DC

+

+ +
+
auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintDC ID
tokenbytesToken to use for login
+

Type

+

auth.LoginToken

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.loginTokenSuccess b/data/core.telegram.org/constructor/auth.loginTokenSuccess new file mode 100644 index 0000000000..887407b1fa --- /dev/null +++ b/data/core.telegram.org/constructor/auth.loginTokenSuccess @@ -0,0 +1,147 @@ + + + + + auth.loginTokenSuccess + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.loginTokenSuccess

+ +

Login via token (QR code) succeded!

+

+ +
+
auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
authorizationauth.AuthorizationAuthorization info
+

Type

+

auth.LoginToken

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.passwordRecovery b/data/core.telegram.org/constructor/auth.passwordRecovery new file mode 100644 index 0000000000..be4437c0a7 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.passwordRecovery @@ -0,0 +1,152 @@ + + + + + auth.passwordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.passwordRecovery

+ +

Recovery info of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
email_patternstringThe email to which the recovery code was sent must match this pattern.
+

Type

+

auth.PasswordRecovery

+

Related pages

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.sentAppCode b/data/core.telegram.org/constructor/auth.sentAppCode new file mode 100644 index 0000000000..2c38b96ecc --- /dev/null +++ b/data/core.telegram.org/constructor/auth.sentAppCode @@ -0,0 +1,163 @@ + + + + + auth.sentAppCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentAppCode

+ +

Contains info on a confirmation code message sent via Telegram.

+

You can force resending the message via SMS by invoking the method auth.sendSms.

+

+ +
+
Constructor schema is available as of layer 50. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_registeredBoolThe given number corresponds to a registered Telegram user
phone_code_hashstringMessage identifier
send_call_timeoutintDelay in seconds before calling auth.sendCall
is_passwordBoolThe sent code is a text password
+

Type

+

auth.SentCode

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.sentCode b/data/core.telegram.org/constructor/auth.sentCode new file mode 100644 index 0000000000..53413116fa --- /dev/null +++ b/data/core.telegram.org/constructor/auth.sentCode @@ -0,0 +1,172 @@ + + + + + auth.sentCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCode

+ +

Contains info about a sent verification code.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
+

Type

+

auth.SentCode

+

Related pages

+

auth.signIn

+

Signs in a user with a validated phone number.

+

auth.resendCode

+

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeApp b/data/core.telegram.org/constructor/auth.sentCodeTypeApp new file mode 100644 index 0000000000..cacd6caff5 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.sentCodeTypeApp @@ -0,0 +1,147 @@ + + + + + auth.sentCodeTypeApp + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeApp

+ +

The code was sent through the telegram app

+

+ +
+
auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lengthintLength of the code in bytes
+

Type

+

auth.SentCodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeCall b/data/core.telegram.org/constructor/auth.sentCodeTypeCall new file mode 100644 index 0000000000..cd48946fb9 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.sentCodeTypeCall @@ -0,0 +1,147 @@ + + + + + auth.sentCodeTypeCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeCall

+ +

The code will be sent via a phone call: a synthesized voice will tell the user which verification code to input.

+

+ +
+
auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lengthintLength of the verification code
+

Type

+

auth.SentCodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall b/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall new file mode 100644 index 0000000000..0ad15e1f94 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall @@ -0,0 +1,150 @@ + + + + + auth.sentCodeTypeFlashCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeFlashCall

+ +

The code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.

+

+ +
+
auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
patternstringpattern to match
+

Type

+

auth.SentCodeType

+

Related pages

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeSms b/data/core.telegram.org/constructor/auth.sentCodeTypeSms new file mode 100644 index 0000000000..e6519bbea3 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.sentCodeTypeSms @@ -0,0 +1,147 @@ + + + + + auth.sentCodeTypeSms + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeSms

+ +

The code was sent via SMS

+

+ +
+
auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lengthintLength of the code in bytes
+

Type

+

auth.SentCodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/authorization.html b/data/core.telegram.org/constructor/authorization.html new file mode 100644 index 0000000000..7b703daa9e --- /dev/null +++ b/data/core.telegram.org/constructor/authorization.html @@ -0,0 +1,225 @@ + + + + + authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

authorization

+ +

Logged-in session

+

+ +
+
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
currentflags.0?trueWhether this is the current session
official_appflags.1?trueWhether the session is from an official app
password_pendingflags.2?trueWhether the session is still waiting for a 2FA password
hashlongIdentifier
device_modelstringDevice model
platformstringPlatform
system_versionstringSystem version
api_idintAPI ID
app_namestringApp name
app_versionstringApp version
date_createdintWhen was the session created
date_activeintWhen was the session last active
ipstringLast known IP
countrystringCountry determined from IP
regionstringRegion determined from IP
+

Type

+

Authorization

+

Related pages

+

Creating your Telegram Application

+

How to get your application identifier and create a new Telegram app.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/autoDownloadSettings.html b/data/core.telegram.org/constructor/autoDownloadSettings.html new file mode 100644 index 0000000000..b5e409b811 --- /dev/null +++ b/data/core.telegram.org/constructor/autoDownloadSettings.html @@ -0,0 +1,187 @@ + + + + + autoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

autoDownloadSettings

+ +

Autodownload settings

+

+ +
+
autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
disabledflags.0?trueDisable automatic media downloads?
video_preload_largeflags.1?trueWhether to preload the first seconds of videos larger than the specified limit
audio_preload_nextflags.2?trueWhether to preload the next audio track when you're listening to music
phonecalls_less_dataflags.3?trueWhether to enable data saving mode in phone calls
photo_size_maxintMaximum size of photos to preload
video_size_maxintMaximum size of videos to preload
file_size_maxintMaximum size of other files to preload
video_upload_maxbitrateintMaximum suggested bitrate for uploading videos
+

Type

+

AutoDownloadSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/bankCardOpenUrl.html b/data/core.telegram.org/constructor/bankCardOpenUrl.html new file mode 100644 index 0000000000..131cda896e --- /dev/null +++ b/data/core.telegram.org/constructor/bankCardOpenUrl.html @@ -0,0 +1,152 @@ + + + + + bankCardOpenUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

bankCardOpenUrl

+ +

Credit card info URL provided by the bank

+

+ +
+
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringInfo URL
namestringBank name
+

Type

+

BankCardOpenUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/baseThemeArctic.html b/data/core.telegram.org/constructor/baseThemeArctic.html new file mode 100644 index 0000000000..4fa0e7d848 --- /dev/null +++ b/data/core.telegram.org/constructor/baseThemeArctic.html @@ -0,0 +1,132 @@ + + + + + baseThemeArctic + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeArctic

+ +

Arctic theme

+

+ +
+
baseThemeArctic#5b11125a = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/baseThemeClassic.html b/data/core.telegram.org/constructor/baseThemeClassic.html new file mode 100644 index 0000000000..2e602c05e4 --- /dev/null +++ b/data/core.telegram.org/constructor/baseThemeClassic.html @@ -0,0 +1,132 @@ + + + + + baseThemeClassic + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeClassic

+ +

Classic theme

+

+ +
+
baseThemeClassic#c3a12462 = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/baseThemeDay.html b/data/core.telegram.org/constructor/baseThemeDay.html new file mode 100644 index 0000000000..7fa0ff7124 --- /dev/null +++ b/data/core.telegram.org/constructor/baseThemeDay.html @@ -0,0 +1,132 @@ + + + + + baseThemeDay + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeDay

+ +

Day theme

+

+ +
+
baseThemeDay#fbd81688 = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/baseThemeNight.html b/data/core.telegram.org/constructor/baseThemeNight.html new file mode 100644 index 0000000000..bbf39cc335 --- /dev/null +++ b/data/core.telegram.org/constructor/baseThemeNight.html @@ -0,0 +1,132 @@ + + + + + baseThemeNight + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeNight

+ +

Night theme

+

+ +
+
baseThemeNight#b7b31ea8 = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/baseThemeTinted.html b/data/core.telegram.org/constructor/baseThemeTinted.html new file mode 100644 index 0000000000..bc4dea5385 --- /dev/null +++ b/data/core.telegram.org/constructor/baseThemeTinted.html @@ -0,0 +1,132 @@ + + + + + baseThemeTinted + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeTinted

+ +

Tinted theme

+

+ +
+
baseThemeTinted#6d5f77ee = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/boolFalse.html b/data/core.telegram.org/constructor/boolFalse.html new file mode 100644 index 0000000000..316e0e24f5 --- /dev/null +++ b/data/core.telegram.org/constructor/boolFalse.html @@ -0,0 +1,132 @@ + + + + + boolFalse + + + + + + + + + + + + + +
+ +
+
+
+ +

boolFalse

+ +

Constructor may be interpreted as a booleanfalse value.

+

+ +
+
boolFalse#bc799737 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/boolTrue.html b/data/core.telegram.org/constructor/boolTrue.html new file mode 100644 index 0000000000..76b69b97b1 --- /dev/null +++ b/data/core.telegram.org/constructor/boolTrue.html @@ -0,0 +1,132 @@ + + + + + boolTrue + + + + + + + + + + + + + +
+ +
+
+
+ +

boolTrue

+ +

The constructor can be interpreted as a booleantrue value.

+

+ +
+
boolTrue#997275b5 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botCommandScopeChatAdmins.html b/data/core.telegram.org/constructor/botCommandScopeChatAdmins.html new file mode 100644 index 0000000000..d2304a64f2 --- /dev/null +++ b/data/core.telegram.org/constructor/botCommandScopeChatAdmins.html @@ -0,0 +1,135 @@ + + + + + botCommandScopeChatAdmins + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeChatAdmins

+ +

The specified bot commands will be valid only for chat administrators, in all groups and supergroups.

+

+ +
+
botCommandScopeChatAdmins#b9aa606a = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botCommandScopeChats.html b/data/core.telegram.org/constructor/botCommandScopeChats.html new file mode 100644 index 0000000000..bf42ab91e4 --- /dev/null +++ b/data/core.telegram.org/constructor/botCommandScopeChats.html @@ -0,0 +1,135 @@ + + + + + botCommandScopeChats + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeChats

+ +

The specified bot commands will be valid in all groups and supergroups.

+

+ +
+
botCommandScopeChats#6fe1a881 = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botCommandScopeDefault.html b/data/core.telegram.org/constructor/botCommandScopeDefault.html new file mode 100644 index 0000000000..4316af87eb --- /dev/null +++ b/data/core.telegram.org/constructor/botCommandScopeDefault.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..19416fbb6f --- /dev/null +++ b/data/core.telegram.org/constructor/botCommandScopePeer.html @@ -0,0 +1,147 @@ + + + + + botCommandScopePeer + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopePeer

+ +

The specified bot commands will be valid only in a specific dialog.

+

+ +
+
botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
+

Type

+

BotCommandScope

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html b/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html new file mode 100644 index 0000000000..09ed3db8d4 --- /dev/null +++ b/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html @@ -0,0 +1,150 @@ + + + + + botCommandScopePeerAdmins + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopePeerAdmins

+ +

The specified bot commands will be valid for all admins of the specified group or supergroup.

+

+ +
+
botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat
+

Type

+

BotCommandScope

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botCommandScopePeerUser.html b/data/core.telegram.org/constructor/botCommandScopePeerUser.html new file mode 100644 index 0000000000..b9e1f1945f --- /dev/null +++ b/data/core.telegram.org/constructor/botCommandScopePeerUser.html @@ -0,0 +1,155 @@ + + + + + botCommandScopePeerUser + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopePeerUser

+ +

The specified bot commands will be valid only for a specific user in the specified group or supergroup.

+

+ +
+
botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat
user_idInputUserThe user
+

Type

+

BotCommandScope

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botCommandScopeUsers.html b/data/core.telegram.org/constructor/botCommandScopeUsers.html new file mode 100644 index 0000000000..ff03cb3e3b --- /dev/null +++ b/data/core.telegram.org/constructor/botCommandScopeUsers.html @@ -0,0 +1,132 @@ + + + + + botCommandScopeUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeUsers

+ +

The specified bot commands will only be valid in all private chats with users.

+

+ +
+
botCommandScopeUsers#3c4f04d8 = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInfo.html b/data/core.telegram.org/constructor/botInfo.html new file mode 100644 index 0000000000..8a8fa43226 --- /dev/null +++ b/data/core.telegram.org/constructor/botInfo.html @@ -0,0 +1,157 @@ + + + + + botInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

botInfo

+ +

Info about bots (available bot commands, etc)

+

+ +
+
botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongID of the bot
descriptionstringDescription of the bot
commandsVector<BotCommand>Bot commands that can be used in the chat
+

Type

+

BotInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInlineMediaResult.html b/data/core.telegram.org/constructor/botInlineMediaResult.html new file mode 100644 index 0000000000..5543f348d4 --- /dev/null +++ b/data/core.telegram.org/constructor/botInlineMediaResult.html @@ -0,0 +1,186 @@ + + + + + botInlineMediaResult + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMediaResult

+ +

Media result

+

+ +
+
botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
photoflags.0?PhotoIf type is photo, the photo to send
documentflags.1?DocumentIf type is document, the document to send
titleflags.2?stringResult title
descriptionflags.3?stringDescription
send_messageBotInlineMessageDepending on the type and on the constructor, contains the caption of the media or the content of the message to be sent instead of the media
+

Type

+

BotInlineResult

+

Related pages

+

Telegram Bot API

+

BotInlineMessage

+

Inline message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html b/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html new file mode 100644 index 0000000000..fafae10d6a --- /dev/null +++ b/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html @@ -0,0 +1,167 @@ + + + + + botInlineMessageMediaAuto + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaAuto

+ +

Send whatever media is attached to the botInlineMediaResult

+

+ +
+
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

botInlineMediaResult

+

Media result

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaContact.html b/data/core.telegram.org/constructor/botInlineMessageMediaContact.html new file mode 100644 index 0000000000..401a5f6d9f --- /dev/null +++ b/data/core.telegram.org/constructor/botInlineMessageMediaContact.html @@ -0,0 +1,172 @@ + + + + + botInlineMessageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaContact

+ +

Send a contact

+

+ +
+
botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html b/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html new file mode 100644 index 0000000000..d106e79ba5 --- /dev/null +++ b/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html @@ -0,0 +1,175 @@ + + + + + botInlineMessageMediaGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaGeo

+ +

Send a geolocation

+

+ +
+
botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360.
periodflags.1?intValidity period
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000).
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+

Related pages

+

Live geolocation

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaInvoice.html b/data/core.telegram.org/constructor/botInlineMessageMediaInvoice.html new file mode 100644 index 0000000000..7fdade1179 --- /dev/null +++ b/data/core.telegram.org/constructor/botInlineMessageMediaInvoice.html @@ -0,0 +1,189 @@ + + + + + botInlineMessageMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaInvoice

+ +

Send an invoice

+

+ +
+
botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueSet this flag if you require the user's shipping address to complete the order
testflags.3?trueTest invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentProduct photo
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html b/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html new file mode 100644 index 0000000000..9f6a86b39f --- /dev/null +++ b/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html @@ -0,0 +1,182 @@ + + + + + botInlineMessageMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaVenue

+ +

Send a venue

+

+ +
+
botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInlineMessageText.html b/data/core.telegram.org/constructor/botInlineMessageText.html new file mode 100644 index 0000000000..9fb7d1d5aa --- /dev/null +++ b/data/core.telegram.org/constructor/botInlineMessageText.html @@ -0,0 +1,170 @@ + + + + + botInlineMessageText + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageText

+ +

Send a simple text message

+

+ +
+
botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringThe message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botInlineResult.html b/data/core.telegram.org/constructor/botInlineResult.html new file mode 100644 index 0000000000..fc0c46a83b --- /dev/null +++ b/data/core.telegram.org/constructor/botInlineResult.html @@ -0,0 +1,189 @@ + + + + + botInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineResult

+ +

Generic result

+

+ +
+
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of article or webpage
thumbflags.4?WebDocumentThumbnail for the result
contentflags.5?WebDocumentContent of the result
send_messageBotInlineMessageMessage to send
+

Type

+

BotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/cdnConfig.html b/data/core.telegram.org/constructor/cdnConfig.html new file mode 100644 index 0000000000..1157b7340e --- /dev/null +++ b/data/core.telegram.org/constructor/cdnConfig.html @@ -0,0 +1,149 @@ + + + + + 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 new file mode 100644 index 0000000000..d6eaa0e16a --- /dev/null +++ b/data/core.telegram.org/constructor/cdnPublicKey.html @@ -0,0 +1,154 @@ + + + + + cdnPublicKey + + + + + + + + + + + + + +
+ +
+
+
+ +

cdnPublicKey

+ +

Public key to use only during handshakes to CDN DCs.

+

+ +
+
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintCDN DC ID
public_keystringRSA public key
+

Type

+

CdnPublicKey

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channel.html b/data/core.telegram.org/constructor/channel.html new file mode 100644 index 0000000000..73ec97d243 --- /dev/null +++ b/data/core.telegram.org/constructor/channel.html @@ -0,0 +1,289 @@ + + + + + channel + + + + + + + + + + + + + +
+ +
+
+
+ +

channel

+ +

Channel/supergroup info

+

+ +
+
channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of this channel
leftflags.2?trueWhether the current user has left this channel
broadcastflags.5?trueIs this a channel?
verifiedflags.7?trueIs this channel verified by telegram?
megagroupflags.8?trueIs this a supergroup?
restrictedflags.9?trueWhether viewing/writing in this channel for a reason (see restriction_reason
signaturesflags.11?trueWhether signatures are enabled (channels)
minflags.12?trueSee min
scamflags.19?trueThis channel/supergroup is probably a scam
has_linkflags.20?trueWhether this channel has a private join link
has_geoflags.21?trueWhether this chanel has a geoposition
slowmode_enabledflags.22?trueWhether slow mode is enabled for groups to prevent flood in chat
call_activeflags.23?trueWhether a group call or livestream is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call or livestream
fakeflags.25?trueIf set, this supergroup/channel was reported by many users as a fake or scam: be careful when interacting with it.
gigagroupflags.26?trueWhether this supergroup is a gigagroup
idlongID of the channel
access_hashflags.13?longAccess hash
titlestringTitle
usernameflags.6?stringUsername
photoChatPhotoProfile photo
dateintDate when the user joined the supergroup/channel, or if the user isn't a member, its creation date
restriction_reasonflags.9?Vector<RestrictionReason>Contains the reason why access to this channel must be restricted.
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in this channel (see rights)
banned_rightsflags.15?ChatBannedRightsBanned rights of the user in this channel (see rights)
default_banned_rightsflags.18?ChatBannedRightsDefault chat rights (see rights)
participants_countflags.17?intParticipant count
+

Type

+

Chat

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEvent.html b/data/core.telegram.org/constructor/channelAdminLogEvent.html new file mode 100644 index 0000000000..08d01a45ca --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEvent.html @@ -0,0 +1,162 @@ + + + + + channelAdminLogEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEvent

+ +

Admin log event

+

+ +
+
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongEvent ID
dateintDate
user_idlongUser ID
actionChannelAdminLogEventActionAction
+

Type

+

ChannelAdminLogEvent

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html new file mode 100644 index 0000000000..c9fe0ac9d8 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeAbout + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeAbout

+ +

The description was changed

+

+ +
+
channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuestringPrevious description
new_valuestringNew description
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html new file mode 100644 index 0000000000..234d968fe8 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeHistoryTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeHistoryTTL

+ +

The Time-To-Live of messages in this chat was changed

+

+ +
+
channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valueintPrevious value
new_valueintNew value
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html new file mode 100644 index 0000000000..d8470afca7 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeLinkedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeLinkedChat

+ +

The linked chat was changed

+

+ +
+
channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuelongPrevious linked chat
new_valuelongNew linked chat
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html new file mode 100644 index 0000000000..827058690a --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeLocation

+ +

The geogroup location was changed

+

+ +
+
channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valueChannelLocationPrevious location
new_valueChannelLocationNew location
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html new file mode 100644 index 0000000000..305046f1b5 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangePhoto

+ +

The channel/supergroup's picture was changed

+

+ +
+
channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_photoPhotoPrevious picture
new_photoPhotoNew picture
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html new file mode 100644 index 0000000000..d0d6c768cf --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeStickerSet

+ +

The supergroup's stickerset was changed

+

+ +
+
channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_stickersetInputStickerSetPrevious stickerset
new_stickersetInputStickerSetNew stickerset
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html new file mode 100644 index 0000000000..f2699fa673 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeTitle

+ +

Channel/supergroup title was changed

+

+ +
+
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuestringPrevious title
new_valuestringNew title
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html new file mode 100644 index 0000000000..6c4edcbca6 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeUsername

+ +

Channel/supergroup username was changed

+

+ +
+
channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuestringOld username
new_valuestringNew username
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html b/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html new file mode 100644 index 0000000000..455200c451 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html @@ -0,0 +1,155 @@ + + + + + channelAdminLogEventActionDefaultBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionDefaultBannedRights

+ +

The default banned rights were modified

+

+ +
+
channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_banned_rightsChatBannedRightsPrevious global banned rights
new_banned_rightsChatBannedRightsNew glboal banned rights.
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html b/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html new file mode 100644 index 0000000000..374aec1406 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionDeleteMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionDeleteMessage

+ +

A message was deleted

+

+ +
+
channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe message that was deleted
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html b/data/core.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html new file mode 100644 index 0000000000..6eb96f8f9e --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionDiscardGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionDiscardGroupCall

+ +

A group call was terminated

+

+ +
+
channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call that was terminated
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html b/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html new file mode 100644 index 0000000000..e5d68279d7 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionEditMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionEditMessage

+ +

A message was edited

+

+ +
+
channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_messageMessageOld message
new_messageMessageNew message
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html new file mode 100644 index 0000000000..2d9c9fab07 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionExportedInviteDelete + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionExportedInviteDelete

+ +

A chat invite was deleted

+

+ +
+
channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteThe deleted chat invite
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html new file mode 100644 index 0000000000..4f69d5962c --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionExportedInviteEdit + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionExportedInviteEdit

+ +

A chat invite was edited

+

+ +
+
channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_inviteExportedChatInvitePrevious chat invite information
new_inviteExportedChatInviteNew chat invite information
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html new file mode 100644 index 0000000000..ce1bc6f620 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionExportedInviteRevoke + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionExportedInviteRevoke

+ +

A specific invite link was revoked

+

+ +
+
channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteThe invite link that was revoked
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html new file mode 100644 index 0000000000..eb0f9a9a7b --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionParticipantInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantInvite

+ +

A user was invited to the group

+

+ +
+
channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantChannelParticipantThe user that was invited
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html new file mode 100644 index 0000000000..70fa7b1339 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html @@ -0,0 +1,132 @@ + + + + + channelAdminLogEventActionParticipantJoin + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantJoin

+ +

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

+

+ +
+
channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html new file mode 100644 index 0000000000..f37e737a11 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html @@ -0,0 +1,150 @@ + + + + + channelAdminLogEventActionParticipantJoinByInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantJoinByInvite

+ +

A user joined the supergroup/channel using a specific invite link

+

+ +
+
channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteThe invite link used to join the supergroup/channel
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html new file mode 100644 index 0000000000..85bda0a29b --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html @@ -0,0 +1,132 @@ + + + + + channelAdminLogEventActionParticipantLeave + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantLeave

+ +

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

+

+ +
+
channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html new file mode 100644 index 0000000000..aa90572c70 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionParticipantMute + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantMute

+ +

A group call participant was muted

+

+ +
+
channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantGroupCallParticipantThe participant that was muted
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html new file mode 100644 index 0000000000..63b91a8939 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html @@ -0,0 +1,155 @@ + + + + + channelAdminLogEventActionParticipantToggleBan + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantToggleBan

+ +

The banned rights of a user were changed

+

+ +
+
channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_participantChannelParticipantOld banned rights of user
new_participantChannelParticipantNew banned rights of user
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html new file mode 100644 index 0000000000..186a54135e --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionParticipantUnmute + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantUnmute

+ +

A group call participant was unmuted

+

+ +
+
channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantGroupCallParticipantThe participant that was unmuted
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html new file mode 100644 index 0000000000..dd5da9c53b --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html @@ -0,0 +1,147 @@ + + + + + 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/core.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html b/data/core.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html new file mode 100644 index 0000000000..cbd6939d24 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionStartGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionStartGroupCall

+ +

A group call was started

+

+ +
+
channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html b/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html new file mode 100644 index 0000000000..1be11cb8f5 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionStopPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionStopPoll

+ +

A poll was stopped

+

+ +
+
channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe poll that was stopped
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html new file mode 100644 index 0000000000..998071cb0a --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionToggleGroupCallSetting + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleGroupCallSetting

+ +

Group call settings were changed

+

+ +
+
channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
join_mutedBoolWhether all users are muted by default upon joining
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html new file mode 100644 index 0000000000..ae10df6bbd --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionToggleInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleInvites

+ +

Invites were enabled/disabled

+

+ +
+
channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
new_valueBoolNew value
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html b/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html new file mode 100644 index 0000000000..7ad1f45bd9 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html @@ -0,0 +1,150 @@ + + + + + channelAdminLogEventActionTogglePreHistoryHidden + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionTogglePreHistoryHidden

+ +

The hidden prehistory setting was changed

+

+ +
+
channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
new_valueBoolNew value
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

channels.togglePreHistoryHidden

+

Hide/unhide message history for new channel/supergroup users

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html new file mode 100644 index 0000000000..16da2eb601 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionToggleSignatures + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleSignatures

+ +

Channel signatures were enabled/disabled

+

+ +
+
channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
new_valueBoolNew value
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html new file mode 100644 index 0000000000..41157ff1ab --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html @@ -0,0 +1,155 @@ + + + + + channelAdminLogEventActionToggleSlowMode + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleSlowMode

+ +

Slow mode setting for supergroups was changed

+

+ +
+
channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valueintPrevious slow mode value
new_valueintNew slow mode value
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

channels.toggleSlowMode

+

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html b/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html new file mode 100644 index 0000000000..00e54c411c --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionUpdatePinned + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionUpdatePinned

+ +

A message was pinned

+

+ +
+
channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe message that was pinned
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html b/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html new file mode 100644 index 0000000000..dd094a41a3 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html @@ -0,0 +1,266 @@ + + + + + channelAdminLogEventsFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventsFilter

+ +

Filter only certain admin log events

+

+ +
+
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
joinflags.0?trueJoin events
leaveflags.1?trueLeave events
inviteflags.2?trueInvite events
banflags.3?trueBan events
unbanflags.4?trueUnban events
kickflags.5?trueKick events
unkickflags.6?trueUnkick events
promoteflags.7?trueAdmin promotion events
demoteflags.8?trueAdmin demotion events
infoflags.9?trueInfo change events (when about, linked chat, location, photo, stickerset, title or username data of a channel gets modified)
settingsflags.10?trueSettings change events (invites, hidden prehistory, signatures, default banned rights)
pinnedflags.11?trueMessage pin events
editflags.12?trueMessage edit events
deleteflags.13?trueMessage deletion events
group_callflags.14?trueGroup call events
invitesflags.15?trueInvite events
+

Type

+

ChannelAdminLogEventsFilter

+

Related pages

+

channelAdminLogEventActionParticipantJoin

+

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

+

channelAdminLogEventActionParticipantLeave

+

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

+

channelAdminLogEventActionParticipantInvite

+

A user was invited to the group

+

channelAdminLogEventActionParticipantToggleBan

+

The banned rights of a user were changed

+

channelAdminLogEventActionParticipantToggleAdmin

+

The admin rights of a user were changed

+

channelAdminLogEventActionChangeAbout

+

The description was changed

+

channelAdminLogEventActionChangeLinkedChat

+

The linked chat was changed

+

channelAdminLogEventActionChangeLocation

+

The geogroup location was changed

+

channelAdminLogEventActionChangePhoto

+

The channel/supergroup's picture was changed

+

channelAdminLogEventActionChangeStickerSet

+

The supergroup's stickerset was changed

+

channelAdminLogEventActionChangeTitle

+

Channel/supergroup title was changed

+

channelAdminLogEventActionChangeUsername

+

Channel/supergroup username was changed

+

channelAdminLogEventActionToggleInvites

+

Invites were enabled/disabled

+

channelAdminLogEventActionTogglePreHistoryHidden

+

The hidden prehistory setting was changed

+

channelAdminLogEventActionToggleSignatures

+

Channel signatures were enabled/disabled

+

channelAdminLogEventActionDefaultBannedRights

+

The default banned rights were modified

+

channelAdminLogEventActionUpdatePinned

+

A message was pinned

+

channelAdminLogEventActionEditMessage

+

A message was edited

+

channelAdminLogEventActionDeleteMessage

+

A message was deleted

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelForbidden.html b/data/core.telegram.org/constructor/channelForbidden.html new file mode 100644 index 0000000000..e972d470e7 --- /dev/null +++ b/data/core.telegram.org/constructor/channelForbidden.html @@ -0,0 +1,177 @@ + + + + + channelForbidden + + + + + + + + + + + + + +
+ +
+
+
+ +

channelForbidden

+ +

Indicates a channel/supergroup we can't access because we were banned, or for some other reason.

+

+ +
+
channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.5?trueIs this a channel
megagroupflags.8?trueIs this a supergroup
idlongChannel ID
access_hashlongAccess hash
titlestringTitle
until_dateflags.16?intThe ban is valid until the specified date
+

Type

+

Chat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelFull.html b/data/core.telegram.org/constructor/channelFull.html new file mode 100644 index 0000000000..54ada2ff22 --- /dev/null +++ b/data/core.telegram.org/constructor/channelFull.html @@ -0,0 +1,363 @@ + + + + + channelFull + + + + + + + + + + + + + +
+ +
+
+
+ +

channelFull

+ +

Full info about a channel/supergroup

+

+ +
+
channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_view_participantsflags.3?trueCan we vew the participant list?
can_set_usernameflags.6?trueCan we set the channel's username?
can_set_stickersflags.7?trueCan we associate a stickerpack to the supergroup?
hidden_prehistoryflags.10?trueIs the history before we joined hidden to us?
can_set_locationflags.16?trueCan we set the geolocation of this group (for geogroups)
has_scheduledflags.19?trueWhether scheduled messages are available
can_view_statsflags.20?trueCan the user view channel/supergroup statistics
blockedflags.22?trueWhether any anonymous admin of this supergroup was blocked: if set, you won't receive messages from anonymous group admins in discussion replies via @replies
idlongID of the channel
aboutstringInfo about the channel
participants_countflags.0?intNumber of participants of the channel
admins_countflags.1?intNumber of channel admins
kicked_countflags.2?intNumber of users kicked from the channel
banned_countflags.2?intNumber of users banned from the channel
online_countflags.13?intNumber of users currently online
read_inbox_max_idintPosition up to which all incoming messages are read.
read_outbox_max_idintPosition up to which all outgoing messages are read.
unread_countintCount of unread messages
chat_photoPhotoChannel picture
notify_settingsPeerNotifySettingsNotification settings
exported_inviteflags.23?ExportedChatInviteInvite link
bot_infoVector<BotInfo>Info about bots in the channel/supergrup
migrated_from_chat_idflags.4?longThe chat ID from which this group was migrated
migrated_from_max_idflags.4?intThe message ID in the original chat at which this group was migrated
pinned_msg_idflags.5?intMessage ID of the last pinned message
stickersetflags.8?StickerSetAssociated stickerset
available_min_idflags.9?intIdentifier of a maximum unavailable message in a channel due to hidden history.
folder_idflags.11?intPeer folder ID, for more info click here
linked_chat_idflags.14?longID of the linked discussion chat for channels
locationflags.15?ChannelLocationLocation of the geogroup
slowmode_secondsflags.17?intIf specified, users in supergroups will only be able to send one message every slowmode_seconds seconds
slowmode_next_send_dateflags.18?intIndicates when the user will be allowed to send another message in the supergroup (unixdate)
stats_dcflags.12?intIf set, specifies the DC to use for fetching channel statistics
ptsintLatest PTS for this channel
callflags.21?InputGroupCallLivestream or group call information
ttl_periodflags.24?intTime-To-Live of messages in this channel or supergroup
pending_suggestionsflags.25?Vector<string>A list of suggested actions for the supergroup admin, see here for more info ».
groupcall_default_join_asflags.26?PeerWhen using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default.
theme_emoticonflags.27?stringEmoji representing a specific chat theme
+

Type

+

ChatFull

+

Related pages

+

channels.setStickers

+

Associate a stickerset to the supergroup

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+

phone.getGroupCallJoinAs

+

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelLocation.html b/data/core.telegram.org/constructor/channelLocation.html new file mode 100644 index 0000000000..90a018d887 --- /dev/null +++ b/data/core.telegram.org/constructor/channelLocation.html @@ -0,0 +1,152 @@ + + + + + channelLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

channelLocation

+ +

Geographical location of supergroup (geogroups)

+

+ +
+
channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointGeoPointGeographical location of supergrup
addressstringTextual description of the address
+

Type

+

ChannelLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelLocationEmpty.html b/data/core.telegram.org/constructor/channelLocationEmpty.html new file mode 100644 index 0000000000..2483d6968d --- /dev/null +++ b/data/core.telegram.org/constructor/channelLocationEmpty.html @@ -0,0 +1,132 @@ + + + + + channelLocationEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

channelLocationEmpty

+ +

No location (normal supergroup)

+

+ +
+
channelLocationEmpty#bfb5ad8b = ChannelLocation;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelMessagesFilter.html b/data/core.telegram.org/constructor/channelMessagesFilter.html new file mode 100644 index 0000000000..1e12608d09 --- /dev/null +++ b/data/core.telegram.org/constructor/channelMessagesFilter.html @@ -0,0 +1,157 @@ + + + + + channelMessagesFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

channelMessagesFilter

+ +

Filter for getting only certain types of channel messages

+

+ +
+
channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_new_messagesflags.1?trueWhether to exclude new messages from the search
rangesVector<MessageRange>A range of messages to fetch
+

Type

+

ChannelMessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html b/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html new file mode 100644 index 0000000000..be6ba03f36 --- /dev/null +++ b/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html @@ -0,0 +1,132 @@ + + + + + channelMessagesFilterEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

channelMessagesFilterEmpty

+ +

No filter

+

+ +
+
channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelMessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipant.html b/data/core.telegram.org/constructor/channelParticipant.html new file mode 100644 index 0000000000..2cb702153b --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipant.html @@ -0,0 +1,152 @@ + + + + + channelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipant

+ +

Channel/supergroup participant

+

+ +
+
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongPariticipant user ID
dateintDate joined
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantAdmin.html b/data/core.telegram.org/constructor/channelParticipantAdmin.html new file mode 100644 index 0000000000..74db228270 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantAdmin.html @@ -0,0 +1,190 @@ + + + + + channelParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantAdmin

+ +

Admin

+

+ +
+
channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_editflags.0?trueCan this admin promote other admins with the same permissions?
selfflags.1?trueIs this the current user
user_idlongAdmin user ID
inviter_idflags.1?longUser that invited the admin to the channel/group
promoted_bylongUser that promoted the user to admin
dateintWhen did the user join
admin_rightsChatAdminRightsAdmin rights
rankflags.2?stringThe role (rank) of the admin in the group: just an arbitrary string, admin by default
+

Type

+

ChannelParticipant

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantBanned.html b/data/core.telegram.org/constructor/channelParticipantBanned.html new file mode 100644 index 0000000000..6a5e362583 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantBanned.html @@ -0,0 +1,175 @@ + + + + + channelParticipantBanned + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantBanned

+ +

Banned/kicked user

+

+ +
+
channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
leftflags.0?trueWhether the user has left the group
peerPeerThe banned peer
kicked_bylongUser was kicked by the specified admin
dateintWhen did the user join the group
banned_rightsChatBannedRightsBanned rights
+

Type

+

ChannelParticipant

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantCreator.html b/data/core.telegram.org/constructor/channelParticipantCreator.html new file mode 100644 index 0000000000..d644a8b090 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantCreator.html @@ -0,0 +1,162 @@ + + + + + channelParticipantCreator + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantCreator

+ +

Channel/supergroup creator

+

+ +
+
channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_idlongUser ID
admin_rightsChatAdminRightsCreator admin rights
rankflags.0?stringThe role (rank) of the group creator in the group: just an arbitrary string, admin by default
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantLeft.html b/data/core.telegram.org/constructor/channelParticipantLeft.html new file mode 100644 index 0000000000..96911d5117 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantLeft.html @@ -0,0 +1,147 @@ + + + + + channelParticipantLeft + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantLeft

+ +

A participant that left the channel/supergroup

+

+ +
+
channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe peer that left
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantSelf.html b/data/core.telegram.org/constructor/channelParticipantSelf.html new file mode 100644 index 0000000000..4024f25e89 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantSelf.html @@ -0,0 +1,157 @@ + + + + + channelParticipantSelf + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantSelf

+ +

Myself

+

+ +
+
channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
inviter_idlongUser that invited me to the channel/supergroup
dateintWhen did I join the channel/supergroup
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsAdmins.html b/data/core.telegram.org/constructor/channelParticipantsAdmins.html new file mode 100644 index 0000000000..62aa8fe76b --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsAdmins.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsAdmins + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsAdmins

+ +

Fetch only admin participants

+

+ +
+
channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsBanned.html b/data/core.telegram.org/constructor/channelParticipantsBanned.html new file mode 100644 index 0000000000..26e1c21347 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsBanned.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsBanned + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsBanned

+ +

Fetch only banned participants

+

+ +
+
channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringOptional filter for searching banned participants by name (otherwise empty)
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsBots.html b/data/core.telegram.org/constructor/channelParticipantsBots.html new file mode 100644 index 0000000000..3792f73fe1 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsBots.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsBots + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsBots

+ +

Fetch only bot participants

+

+ +
+
channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsContacts.html b/data/core.telegram.org/constructor/channelParticipantsContacts.html new file mode 100644 index 0000000000..2563dfc7ee --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsContacts.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsContacts

+ +

Fetch only participants that are also contacts

+

+ +
+
channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringOptional search query for searching contact participants by name
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsKicked.html b/data/core.telegram.org/constructor/channelParticipantsKicked.html new file mode 100644 index 0000000000..4d7d23f656 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsKicked.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsKicked + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsKicked

+ +

Fetch only kicked participants

+

+ +
+
channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringOptional filter for searching kicked participants by name (otherwise empty)
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsMentions.html b/data/core.telegram.org/constructor/channelParticipantsMentions.html new file mode 100644 index 0000000000..2ed49b9ee6 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsMentions.html @@ -0,0 +1,161 @@ + + + + + channelParticipantsMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsMentions

+ +

This filter is used when looking for supergroup members to mention.
+This filter will automatically remove anonymous admins, and return even non-participant users that replied to a specific thread through the comment section of a channel.

+

+ +
+
channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
qflags.0?stringFilter by user name or username
top_msg_idflags.1?intLook only for users that posted in this thread
+

Type

+

ChannelParticipantsFilter

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsRecent.html b/data/core.telegram.org/constructor/channelParticipantsRecent.html new file mode 100644 index 0000000000..9bd1b9de9b --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsRecent.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsRecent + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsRecent

+ +

Fetch only recent participants

+

+ +
+
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsSearch.html b/data/core.telegram.org/constructor/channelParticipantsSearch.html new file mode 100644 index 0000000000..543589d2d9 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsSearch.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsSearch + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsSearch

+ +

Query participants by name

+

+ +
+
channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringSearch query
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channels.adminLogResults b/data/core.telegram.org/constructor/channels.adminLogResults new file mode 100644 index 0000000000..4e5cccbfe5 --- /dev/null +++ b/data/core.telegram.org/constructor/channels.adminLogResults @@ -0,0 +1,157 @@ + + + + + channels.adminLogResults + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.adminLogResults

+ +

Admin log events

+

+ +
+
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
eventsVector<ChannelAdminLogEvent>Admin log events
chatsVector<Chat>Chats mentioned in events
usersVector<User>Users mentioned in events
+

Type

+

channels.AdminLogResults

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channels.channelParticipant b/data/core.telegram.org/constructor/channels.channelParticipant new file mode 100644 index 0000000000..44fb5b5322 --- /dev/null +++ b/data/core.telegram.org/constructor/channels.channelParticipant @@ -0,0 +1,157 @@ + + + + + channels.channelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.channelParticipant

+ +

Represents a channel participant

+

+ +
+
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
participantChannelParticipantThe channel participant
chatsVector<Chat>Mentioned chats
usersVector<User>Users
+

Type

+

channels.ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channels.channelParticipants b/data/core.telegram.org/constructor/channels.channelParticipants new file mode 100644 index 0000000000..5993ce565d --- /dev/null +++ b/data/core.telegram.org/constructor/channels.channelParticipants @@ -0,0 +1,162 @@ + + + + + channels.channelParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.channelParticipants

+ +

Represents multiple channel participants

+

+ +
+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of participants that correspond to the given query
participantsVector<ChannelParticipant>Participants
chatsVector<Chat>Mentioned chats
usersVector<User>Users mentioned in participant info
+

Type

+

channels.ChannelParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channels.channelParticipantsNotModified b/data/core.telegram.org/constructor/channels.channelParticipantsNotModified new file mode 100644 index 0000000000..407af45564 --- /dev/null +++ b/data/core.telegram.org/constructor/channels.channelParticipantsNotModified @@ -0,0 +1,132 @@ + + + + + channels.channelParticipantsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.channelParticipantsNotModified

+ +

No new participant info could be found

+

+ +
+
channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

channels.ChannelParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chat.html b/data/core.telegram.org/constructor/chat.html new file mode 100644 index 0000000000..124814f17f --- /dev/null +++ b/data/core.telegram.org/constructor/chat.html @@ -0,0 +1,227 @@ + + + + + chat + + + + + + + + + + + + + +
+ +
+
+
+ +

chat

+ +

Info about a group

+

+ +
+
chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of the group
kickedflags.1?trueWhether the current user was kicked from the group
leftflags.2?trueWhether the current user has left the group
deactivatedflags.5?trueWhether the group was migrated
call_activeflags.23?trueWhether a group call is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call
idlongID of the group
titlestringTitle
photoChatPhotoChat photo
participants_countintParticipant count
dateintDate of creation of the group
versionintUsed in basic groups to reorder updates and make sure that all of them were received.
migrated_toflags.6?InputChannelMeans this chat was upgraded to a supergroup
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in the group
default_banned_rightsflags.18?ChatBannedRightsDefault banned rights of all users in the group
+

Type

+

Chat

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatAdminRights.html b/data/core.telegram.org/constructor/chatAdminRights.html new file mode 100644 index 0000000000..531393d8c2 --- /dev/null +++ b/data/core.telegram.org/constructor/chatAdminRights.html @@ -0,0 +1,205 @@ + + + + + chatAdminRights + + + + + + + + + + + + + +
+ +
+
+
+ +

chatAdminRights

+ +

Represents the rights of an admin in a channel/supergroup.

+

+ +
+
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
change_infoflags.0?trueIf set, allows the admin to modify the description of the channel/supergroup
post_messagesflags.1?trueIf set, allows the admin to post messages in the channel
edit_messagesflags.2?trueIf set, allows the admin to also edit messages from other admins in the channel
delete_messagesflags.3?trueIf set, allows the admin to also delete messages from other admins in the channel
ban_usersflags.4?trueIf set, allows the admin to ban users from the channel/supergroup
invite_usersflags.5?trueIf set, allows the admin to invite users in the channel/supergroup
pin_messagesflags.7?trueIf set, allows the admin to pin messages in the channel/supergroup
add_adminsflags.9?trueIf set, allows the admin to add other admins with the same (or more limited) permissions in the channel/supergroup
anonymousflags.10?trueWhether this admin is anonymous
manage_callflags.11?trueIf set, allows the admin to change group call/livestream settings
otherflags.12?trueSet this flag if none of the other flags are set, but you stil want the user to be an admin.
+

Type

+

ChatAdminRights

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatBannedRights.html b/data/core.telegram.org/constructor/chatBannedRights.html new file mode 100644 index 0000000000..c211ebffd1 --- /dev/null +++ b/data/core.telegram.org/constructor/chatBannedRights.html @@ -0,0 +1,216 @@ + + + + + chatBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

chatBannedRights

+ +

Represents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.

+

+ +
+
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
view_messagesflags.0?trueIf set, does not allow a user to view messages in a supergroup/channel/chat
send_messagesflags.1?trueIf set, does not allow a user to send messages in a supergroup/chat
send_mediaflags.2?trueIf set, does not allow a user to send any media in a supergroup/chat
send_stickersflags.3?trueIf set, does not allow a user to send stickers in a supergroup/chat
send_gifsflags.4?trueIf set, does not allow a user to send gifs in a supergroup/chat
send_gamesflags.5?trueIf set, does not allow a user to send games in a supergroup/chat
send_inlineflags.6?trueIf set, does not allow a user to use inline bots in a supergroup/chat
embed_linksflags.7?trueIf set, does not allow a user to embed links in the messages of a supergroup/chat
send_pollsflags.8?trueIf set, does not allow a user to send polls in a supergroup/chat
change_infoflags.10?trueIf set, does not allow any user to change the description of a supergroup/chat
invite_usersflags.15?trueIf set, does not allow any user to invite users in a supergroup/chat
pin_messagesflags.17?trueIf set, does not allow any user to pin messages in a supergroup/chat
until_dateintValidity of said permissions (it is considered forever any value less then 30 seconds or more then 366 days).
+

Type

+

ChatBannedRights

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatEmpty.html b/data/core.telegram.org/constructor/chatEmpty.html new file mode 100644 index 0000000000..59eb91e223 --- /dev/null +++ b/data/core.telegram.org/constructor/chatEmpty.html @@ -0,0 +1,147 @@ + + + + + chatEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

chatEmpty

+ +

Empty constructor, group doesn't exist

+

+ +
+
chatEmpty#29562865 id:long = Chat;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongGroup identifier
+

Type

+

Chat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatForbidden.html b/data/core.telegram.org/constructor/chatForbidden.html new file mode 100644 index 0000000000..65ebd13046 --- /dev/null +++ b/data/core.telegram.org/constructor/chatForbidden.html @@ -0,0 +1,152 @@ + + + + + chatForbidden + + + + + + + + + + + + + +
+ +
+
+
+ +

chatForbidden

+ +

A group to which the user has no access. E.g., because the user was kicked from the group.

+

+ +
+
chatForbidden#6592a1a7 id:long title:string = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongUser identifier
titlestringGroup name
+

Type

+

Chat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatFull.html b/data/core.telegram.org/constructor/chatFull.html new file mode 100644 index 0000000000..107d414c47 --- /dev/null +++ b/data/core.telegram.org/constructor/chatFull.html @@ -0,0 +1,231 @@ + + + + + chatFull + + + + + + + + + + + + + +
+ +
+
+
+ +

chatFull

+ +

Detailed chat info

+

+ +
+
chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_set_usernameflags.7?trueCan we change the username of this chat
has_scheduledflags.8?trueWhether scheduled messages are available
idlongID of the chat
aboutstringAbout string for this chat
participantsChatParticipantsParticipant list
chat_photoflags.2?PhotoChat photo
notify_settingsPeerNotifySettingsNotification settings
exported_inviteflags.13?ExportedChatInviteChat invite
bot_infoflags.3?Vector<BotInfo>Info about bots that are in this chat
pinned_msg_idflags.6?intMessage ID of the last pinned message
folder_idflags.11?intPeer folder ID, for more info click here
callflags.12?InputGroupCallGroup call information
ttl_periodflags.14?intTime-To-Live of messages sent by the current user to this chat
groupcall_default_join_asflags.15?PeerWhen using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default.
theme_emoticonflags.16?stringEmoji representing a specific chat theme
+

Type

+

ChatFull

+

Related pages

+

Scheduled messages

+

Telegram allows scheduling messages

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

phone.getGroupCallJoinAs

+

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatInvite.html b/data/core.telegram.org/constructor/chatInvite.html new file mode 100644 index 0000000000..a09dd853cf --- /dev/null +++ b/data/core.telegram.org/constructor/chatInvite.html @@ -0,0 +1,190 @@ + + + + + chatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInvite

+ +

Chat invite info

+

+ +
+
chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channelflags.0?trueWhether this is a channel/supergroup or a normal group
broadcastflags.1?trueWhether this is a channel
publicflags.2?trueWhether this is a public channel/supergroup
megagroupflags.3?trueWhether this is a supergroup
titlestringChat/supergroup/channel title
photoPhotoChat/supergroup/channel photo
participants_countintParticipant count
participantsflags.4?Vector<User>A few of the participants that are in the group
+

Type

+

ChatInvite

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatInviteAlready.html b/data/core.telegram.org/constructor/chatInviteAlready.html new file mode 100644 index 0000000000..02c6e303a8 --- /dev/null +++ b/data/core.telegram.org/constructor/chatInviteAlready.html @@ -0,0 +1,147 @@ + + + + + chatInviteAlready + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInviteAlready

+ +

The user has already joined this chat

+

+ +
+
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatChatThe chat connected to the invite
+

Type

+

ChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatInviteExported.html b/data/core.telegram.org/constructor/chatInviteExported.html new file mode 100644 index 0000000000..8d44404a2a --- /dev/null +++ b/data/core.telegram.org/constructor/chatInviteExported.html @@ -0,0 +1,192 @@ + + + + + chatInviteExported + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInviteExported

+ +

Exported chat invite

+

+ +
+
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.0?trueWhether this chat invite was revoked
permanentflags.5?trueWhether this chat invite has no expiration
linkstringChat invitation link
admin_idlongID of the admin that created this chat invite
dateintWhen was this chat invite created
start_dateflags.4?intWhen was this chat invite last modified
expire_dateflags.1?intWhen does this chat invite expire
usage_limitflags.2?intMaximum number of users that can join using this link
usageflags.3?intHow many users joined using this link
+

Type

+

ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatInviteImporter.html b/data/core.telegram.org/constructor/chatInviteImporter.html new file mode 100644 index 0000000000..4d8a380fca --- /dev/null +++ b/data/core.telegram.org/constructor/chatInviteImporter.html @@ -0,0 +1,152 @@ + + + + + chatInviteImporter + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInviteImporter

+ +

When and which user joined the chat using a chat invite

+

+ +
+
chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongThe user
dateintWhen did the user join
+

Type

+

ChatInviteImporter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatInvitePeek.html b/data/core.telegram.org/constructor/chatInvitePeek.html new file mode 100644 index 0000000000..bf275ef208 --- /dev/null +++ b/data/core.telegram.org/constructor/chatInvitePeek.html @@ -0,0 +1,152 @@ + + + + + chatInvitePeek + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInvitePeek

+ +

A chat invitation that also allows peeking into the group to read messages without joining it.

+

+ +
+
chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chatChatChat information
expiresintRead-only anonymous access to this group will be revoked at this date
+

Type

+

ChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatOnlines.html b/data/core.telegram.org/constructor/chatOnlines.html new file mode 100644 index 0000000000..f1810aecd3 --- /dev/null +++ b/data/core.telegram.org/constructor/chatOnlines.html @@ -0,0 +1,147 @@ + + + + + chatOnlines + + + + + + + + + + + + + +
+ +
+
+
+ +

chatOnlines

+ +

Number of online users in a chat

+

+ +
+
chatOnlines#f041e250 onlines:int = ChatOnlines;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
onlinesintNumber of online users
+

Type

+

ChatOnlines

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatParticipant.html b/data/core.telegram.org/constructor/chatParticipant.html new file mode 100644 index 0000000000..10418304e6 --- /dev/null +++ b/data/core.telegram.org/constructor/chatParticipant.html @@ -0,0 +1,157 @@ + + + + + chatParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipant

+ +

Group member.

+

+ +
+
chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongMember user ID
inviter_idlongID of the user that added the member to the group
dateintDate added to the group
+

Type

+

ChatParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatParticipantAdmin.html b/data/core.telegram.org/constructor/chatParticipantAdmin.html new file mode 100644 index 0000000000..5847d665ae --- /dev/null +++ b/data/core.telegram.org/constructor/chatParticipantAdmin.html @@ -0,0 +1,157 @@ + + + + + chatParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipantAdmin

+ +

Chat admin

+

+ +
+
chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongID of a group member that is admin
inviter_idlongID of the user that added the member to the group
dateintDate when the user was added
+

Type

+

ChatParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatParticipantCreator.html b/data/core.telegram.org/constructor/chatParticipantCreator.html new file mode 100644 index 0000000000..85d70ec86c --- /dev/null +++ b/data/core.telegram.org/constructor/chatParticipantCreator.html @@ -0,0 +1,147 @@ + + + + + chatParticipantCreator + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipantCreator

+ +

Represents the creator of the group

+

+ +
+
chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongID of the user that created the group
+

Type

+

ChatParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatParticipants.html b/data/core.telegram.org/constructor/chatParticipants.html new file mode 100644 index 0000000000..f85fedd61c --- /dev/null +++ b/data/core.telegram.org/constructor/chatParticipants.html @@ -0,0 +1,157 @@ + + + + + chatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipants

+ +

Group members.

+

+ +
+
chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup identifier
participantsVector<ChatParticipant>List of group members
versionintGroup version number
+

Type

+

ChatParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatParticipantsForbidden.html b/data/core.telegram.org/constructor/chatParticipantsForbidden.html new file mode 100644 index 0000000000..f0e86df249 --- /dev/null +++ b/data/core.telegram.org/constructor/chatParticipantsForbidden.html @@ -0,0 +1,157 @@ + + + + + chatParticipantsForbidden + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipantsForbidden

+ +

Info on members is unavailable

+

+ +
+
chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
chat_idlongGroup ID
self_participantflags.0?ChatParticipantInfo about the group membership of the current user
+

Type

+

ChatParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatPhoto.html b/data/core.telegram.org/constructor/chatPhoto.html new file mode 100644 index 0000000000..870530a858 --- /dev/null +++ b/data/core.telegram.org/constructor/chatPhoto.html @@ -0,0 +1,170 @@ + + + + + chatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

chatPhoto

+ +

Group profile photo.

+

+ +
+
chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether the user has an animated profile picture
photo_idlongPhoto ID
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC where this photo is stored
+

Type

+

ChatPhoto

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatPhotoEmpty.html b/data/core.telegram.org/constructor/chatPhotoEmpty.html new file mode 100644 index 0000000000..676b2b3f0d --- /dev/null +++ b/data/core.telegram.org/constructor/chatPhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + chatPhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

chatPhotoEmpty

+ +

Group photo is not set.

+

+ +
+
chatPhotoEmpty#37c1011c = ChatPhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChatPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatTheme.html b/data/core.telegram.org/constructor/chatTheme.html new file mode 100644 index 0000000000..3d671d7b26 --- /dev/null +++ b/data/core.telegram.org/constructor/chatTheme.html @@ -0,0 +1,157 @@ + + + + + chatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

chatTheme

+ +

A chat theme

+

+ +
+
chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji, identifying this specific chat theme
themeThemeTheme
dark_themeThemeDark mode theme
+

Type

+

ChatTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/codeSettings.html b/data/core.telegram.org/constructor/codeSettings.html new file mode 100644 index 0000000000..e12acdc731 --- /dev/null +++ b/data/core.telegram.org/constructor/codeSettings.html @@ -0,0 +1,166 @@ + + + + + codeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

codeSettings

+ +

Settings used by telegram servers for sending the confirm code.

+

Example implementations: telegram for android, tdlib.

+

+ +
+
codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
allow_flashcallflags.0?trueWhether to allow phone verification via phone calls.
current_numberflags.1?truePass true if the phone number is used on the current device. Ignored if allow_flashcall is not set.
allow_app_hashflags.4?trueIf a token that will be included in eventually sent SMSs is required: required in newer versions of android, to use the android SMS receiver APIs
+

Type

+

CodeSettings

+

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/config.html b/data/core.telegram.org/constructor/config.html new file mode 100644 index 0000000000..8ff611def8 --- /dev/null +++ b/data/core.telegram.org/constructor/config.html @@ -0,0 +1,420 @@ + + + + + config + + + + + + + + + + + + + +
+ +
+
+
+ +

config

+ +

Current configuration

+

+ +
+
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
phonecalls_enabledflags.1?trueWhether phone calls can be used
default_p2p_contactsflags.3?trueWhether the client should use P2P by default for phone calls with contacts
preload_featured_stickersflags.4?trueWhether the client should preload featured stickers
ignore_phone_entitiesflags.5?trueWhether the client should ignore phone entities
revoke_pm_inboxflags.6?trueWhether incoming private messages can be deleted for both participants
blocked_modeflags.8?trueIndicates that telegram is probably censored by governments/ISPs in the current region
pfs_enabledflags.13?trueWhether pfs was used
dateintCurrent date at the server
expiresintExpiration date of this config: when it expires it'll have to be refetched using help.getConfig
test_modeBoolWhether we're connected to the test DCs
this_dcintID of the DC that returned the reply
dc_optionsVector<DcOption>DC IP list
dc_txt_domain_namestringDomain name for fetching encrypted DC list from DNS TXT record
chat_size_maxintMaximum member count for normal groups
megagroup_size_maxintMaximum member count for supergroups
forwarded_count_maxintMaximum number of messages that can be forwarded at once using messages.forwardMessages.
online_update_period_msintThe client should update its online status every N milliseconds
offline_blur_timeout_msintDelay before offline status needs to be sent to the server
offline_idle_timeout_msintTime without any user activity after which it should be treated offline
online_cloud_timeout_msintIf we are offline, but were online from some other client in last online_cloud_timeout_ms milliseconds after we had gone offline, then delay offline notification for notify_cloud_delay_ms milliseconds.
notify_cloud_delay_msintIf we are offline, but online from some other client then delay sending the offline notification for notify_cloud_delay_ms milliseconds.
notify_default_delay_msintIf some other client is online, then delay notification for notification_default_delay_ms milliseconds
push_chat_period_msintNot for client use
push_chat_limitintNot for client use
saved_gifs_limitintMaximum count of saved gifs
edit_time_limitintOnly messages with age smaller than the one specified can be edited
revoke_time_limitintOnly channel/supergroup messages with age smaller than the specified can be deleted
revoke_pm_time_limitintOnly private messages with age smaller than the specified can be deleted
rating_e_decayintExponential decay rate for computing top peer rating
stickers_recent_limitintMaximum number of recent stickers
stickers_faved_limitintMaximum number of faved stickers
channels_read_media_periodintIndicates that round videos (video notes) and voice messages sent in channels and older than the specified period must be marked as read
tmp_sessionsflags.0?intTemporary passport sessions
pinned_dialogs_count_maxintMaximum count of pinned dialogs
pinned_infolder_count_maxintMaximum count of dialogs per folder
call_receive_timeout_msintMaximum allowed outgoing ring time in VoIP calls: if the user we're calling doesn't reply within the specified time (in milliseconds), we should hang up the call
call_ring_timeout_msintMaximum allowed incoming ring time in VoIP calls: if the current user doesn't reply within the specified time (in milliseconds), the call will be automatically refused
call_connect_timeout_msintVoIP connection timeout: if the instance of libtgvoip on the other side of the call doesn't connect to our instance of libtgvoip within the specified time (in milliseconds), the call must be aborted
call_packet_timeout_msintIf during a VoIP call a packet isn't received for the specified period of time, the call must be aborted
me_url_prefixstringThe domain to use to parse in-app links.
For example t.me indicates that t.me/username links should parsed to @username, t.me/addsticker/name should be parsed to the appropriate stickerset and so on...
autoupdate_url_prefixflags.7?stringURL to use to auto-update the current app
gif_search_usernameflags.9?stringUsername of the bot to use to search for GIFs
venue_search_usernameflags.10?stringUsername of the bot to use to search for venues
img_search_usernameflags.11?stringUsername of the bot to use for image search
static_maps_providerflags.12?stringID of the map provider to use for venues
caption_length_maxintMaximum length of caption (length in utf8 codepoints)
message_length_maxintMaximum length of messages (length in utf8 codepoints)
webfile_dc_idintDC ID to use to download webfiles
suggested_lang_codeflags.2?stringSuggested language code
lang_pack_versionflags.2?intLanguage pack version
base_lang_pack_versionflags.2?intBasic language pack version
+

Type

+

Config

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

help.getConfig

+

Returns current configuration, including data center configuration.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

messages.forwardMessages

+

Forwards messages by their IDs.

+

account.updateStatus

+

Updates online user status.

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+

Telegram Passport Manual

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contact.html b/data/core.telegram.org/constructor/contact.html new file mode 100644 index 0000000000..f2ebed910e --- /dev/null +++ b/data/core.telegram.org/constructor/contact.html @@ -0,0 +1,152 @@ + + + + + contact + + + + + + + + + + + + + +
+ +
+
+
+ +

contact

+ +

A contact of the current user that is registered in the system.

+

+ +
+
contact#145ade0b user_id:long mutual:Bool = Contact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
mutualBoolCurrent user is in the user's contact list
+

Type

+

Contact

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contactStatus.html b/data/core.telegram.org/constructor/contactStatus.html new file mode 100644 index 0000000000..92d5afcf34 --- /dev/null +++ b/data/core.telegram.org/constructor/contactStatus.html @@ -0,0 +1,152 @@ + + + + + contactStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

contactStatus

+ +

Contact status: online / offline.

+

+ +
+
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
statusUserStatusOnline status
+

Type

+

ContactStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.blockedSlice b/data/core.telegram.org/constructor/contacts.blockedSlice new file mode 100644 index 0000000000..29af09b856 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.blockedSlice @@ -0,0 +1,162 @@ + + + + + contacts.blockedSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.blockedSlice

+ +

Incomplete list of blocked users.

+

+ +
+
contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of elements in the list
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
+

Type

+

contacts.Blocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.contacts b/data/core.telegram.org/constructor/contacts.contacts new file mode 100644 index 0000000000..0470e98560 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.contacts @@ -0,0 +1,157 @@ + + + + + contacts.contacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.contacts

+ +

The current user's contact list and info on users.

+

+ +
+
contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
contactsVector<Contact>Contact list
saved_countintNumber of contacts that were saved successfully
usersVector<User>User list
+

Type

+

contacts.Contacts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.contactsNotModified b/data/core.telegram.org/constructor/contacts.contactsNotModified new file mode 100644 index 0000000000..bb513a2e67 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.contactsNotModified @@ -0,0 +1,132 @@ + + + + + contacts.contactsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.contactsNotModified

+ +

Contact list on the server is the same as the list on the client.

+

+ +
+
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

contacts.Contacts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.found b/data/core.telegram.org/constructor/contacts.found new file mode 100644 index 0000000000..69c2e79636 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.found @@ -0,0 +1,162 @@ + + + + + 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.importedContacts b/data/core.telegram.org/constructor/contacts.importedContacts new file mode 100644 index 0000000000..ecd6004dd5 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.importedContacts @@ -0,0 +1,165 @@ + + + + + contacts.importedContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.importedContacts

+ +

Info on succesfully imported contacts.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
importedVector<ImportedContact>List of succesfully imported contacts
popular_invitesVector<PopularContact>Popular contacts
retry_contactsVector<long>List of contact ids that could not be imported due to system limitation and will need to be imported at a later date.
Parameter added in Layer 13
usersVector<User>List of users
+

Type

+

contacts.ImportedContacts

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.resolvedPeer b/data/core.telegram.org/constructor/contacts.resolvedPeer new file mode 100644 index 0000000000..a29b89dc96 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.resolvedPeer @@ -0,0 +1,157 @@ + + + + + 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 new file mode 100644 index 0000000000..7a12dc54f6 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.topPeers @@ -0,0 +1,157 @@ + + + + + contacts.topPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.topPeers

+ +

Top peers

+

+ +
+
contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
categoriesVector<TopPeerCategoryPeers>Top peers by top peer category
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

contacts.TopPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.topPeersDisabled b/data/core.telegram.org/constructor/contacts.topPeersDisabled new file mode 100644 index 0000000000..033541c269 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.topPeersDisabled @@ -0,0 +1,132 @@ + + + + + contacts.topPeersDisabled + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.topPeersDisabled

+ +

Top peers disabled

+

+ +
+
contacts.topPeersDisabled#b52c939d = contacts.TopPeers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

contacts.TopPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.topPeersNotModified b/data/core.telegram.org/constructor/contacts.topPeersNotModified new file mode 100644 index 0000000000..1e6a36f955 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.topPeersNotModified @@ -0,0 +1,132 @@ + + + + + contacts.topPeersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.topPeersNotModified

+ +

Top peer info hasn't changed

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

contacts.TopPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dataJSON.html b/data/core.telegram.org/constructor/dataJSON.html new file mode 100644 index 0000000000..a31c1532b9 --- /dev/null +++ b/data/core.telegram.org/constructor/dataJSON.html @@ -0,0 +1,147 @@ + + + + + dataJSON + + + + + + + + + + + + + +
+ +
+
+
+ +

dataJSON

+ +

Represents a json-encoded object

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
datastringJSON-encoded object
+

Type

+

DataJSON

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dcOption.html b/data/core.telegram.org/constructor/dcOption.html new file mode 100644 index 0000000000..e1c99b2723 --- /dev/null +++ b/data/core.telegram.org/constructor/dcOption.html @@ -0,0 +1,197 @@ + + + + + dcOption + + + + + + + + + + + + + +
+ +
+
+
+ +

dcOption

+ +

Data centre

+

+ +
+
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
ipv6flags.0?trueWhether the specified IP is an IPv6 address
media_onlyflags.1?trueWhether this DC should only be used to download or upload files
tcpo_onlyflags.2?trueWhether this DC only supports connection with transport obfuscation
cdnflags.3?trueWhether this is a CDN DC.
staticflags.4?trueIf set, this IP should be used when connecting through a proxy
idintDC ID
ip_addressstringIP address of DC
portintPort
secretflags.10?bytesIf the tcpo_only flag is set, specifies the secret to use when connecting using transport obfuscation
+

Type

+

DcOption

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

MTProto transports

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessage.html b/data/core.telegram.org/constructor/decryptedMessage.html new file mode 100644 index 0000000000..a22553d1cf --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessage.html @@ -0,0 +1,217 @@ + + + + + decryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessage

+ +

Contents of an encrypted message.

+

+ +
+
===8===
+decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+
+===17===
+decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+
+===45===
+decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
+
+===73===
+decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields (added in layer 45)
no_webpageflags.1?trueWhether the webpage preview is disabled
silentflags.5?trueWhether this is a silent message (no notification triggered)
random_idlongRandom message ID, assigned by the author of message.
Must be equal to the ID passed to sending method.
ttlintMessage lifetime. Has higher priority than decryptedMessageActionSetMessageTTL.
Parameter added in Layer 17.
messagestringMessage text
mediaflags.9?DecryptedMessageMediaMedia content
entitiesflags.7?Vector<MessageEntity>Message entities for styled text (parameter added in layer 45)
via_bot_nameflags.11?stringSpecifies the ID of the inline bot that generated the message (parameter added in layer 45)
reply_to_random_idflags.3?longRandom message ID of the message this message replies to (parameter added in layer 45)
grouped_idflags.17?longRandom group ID, assigned by the author of message.
Multiple encrypted messages with a photo attached and with the same group ID indicate an album or grouped media (parameter added in layer 45)
+

Type

+

DecryptedMessage

+

Related pages

+

decryptedMessageActionSetMessageTTL

+

Setting of a message lifetime after reading.

+

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+

Styled text with message entities

+

How to create styled text with message entities

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html b/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html new file mode 100644 index 0000000000..c0e215340b --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionAbortKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionAbortKey

+ +

Abort rekeying

+

+ +
+
===20===
+decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html b/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html new file mode 100644 index 0000000000..b6c5fb406f --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html @@ -0,0 +1,160 @@ + + + + + decryptedMessageActionAcceptKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionAcceptKey

+ +

Accept new key

+

+ +
+
===20===
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID
g_bbytesB parameter, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
+

Type

+

DecryptedMessageAction

+

Related pages

+

Perfect Forward Secrecy

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html b/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html new file mode 100644 index 0000000000..51a021301c --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html @@ -0,0 +1,155 @@ + + + + + decryptedMessageActionCommitKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionCommitKey

+ +

Commit new key, see rekeying process

+

+ +
+
===20===
+decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
+

Type

+

DecryptedMessageAction

+

Related pages

+

Perfect Forward Secrecy

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html new file mode 100644 index 0000000000..694a95b7da --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionDeleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionDeleteMessages

+ +

Deleted messages.

+

+ +
+
===8===
+decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
random_idsVector<long>List of deleted message IDs
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html b/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html new file mode 100644 index 0000000000..429be2b493 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html @@ -0,0 +1,133 @@ + + + + + decryptedMessageActionFlushHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionFlushHistory

+ +

The entire message history has been deleted.

+

+ +
+
===8===
+decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionNoop.html b/data/core.telegram.org/constructor/decryptedMessageActionNoop.html new file mode 100644 index 0000000000..9ddff65b0d --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionNoop.html @@ -0,0 +1,133 @@ + + + + + decryptedMessageActionNoop + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionNoop

+ +

NOOP action

+

+ +
+
===20===
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html b/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html new file mode 100644 index 0000000000..23af64d198 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html @@ -0,0 +1,151 @@ + + + + + decryptedMessageActionNotifyLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionNotifyLayer

+ +

A notification stating the API layer that is used by the client. You should use your current layer and take notice of the layer used on the other side of a conversation when sending messages.

+

+ +
+
===17===
+decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
layerintLayer number, must be 17 or higher (this contructor was introduced in Layer 17).
+

Type

+

DecryptedMessageAction

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html new file mode 100644 index 0000000000..c02f0bce9d --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionReadMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionReadMessages

+ +

Messages marked as read.

+

+ +
+
===8===
+decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
random_idsVector<long>List of message IDs
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html b/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html new file mode 100644 index 0000000000..c6169d8bad --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html @@ -0,0 +1,155 @@ + + + + + decryptedMessageActionRequestKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionRequestKey

+ +

Request rekeying, see rekeying process

+

+ +
+
===20===
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID
g_abytesg_a, see rekeying process
+

Type

+

DecryptedMessageAction

+

Related pages

+

Perfect Forward Secrecy

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionResend.html b/data/core.telegram.org/constructor/decryptedMessageActionResend.html new file mode 100644 index 0000000000..27ca55189a --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionResend.html @@ -0,0 +1,155 @@ + + + + + decryptedMessageActionResend + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionResend

+ +

Request for the other party in a Secret Chat to automatically resend a contiguous range of previously sent messages, as explained in Sequence number is Secret Chats.

+

+ +
+
===17===
+decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
start_seq_nointout_seq_no of the first message to be resent, with correct parity
end_seq_nointout_seq_no of the last message to be resent, with same parity.
+

Type

+

DecryptedMessageAction

+

Related pages

+

Sequence numbers in Secret Chats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html new file mode 100644 index 0000000000..887a7e164e --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionScreenshotMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionScreenshotMessages

+ +

A screenshot was taken.

+

+ +
+
===8===
+decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
random_idsVector<long>List of affected message ids (that appeared on the screenshot)
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html b/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html new file mode 100644 index 0000000000..2d4194974c --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html @@ -0,0 +1,149 @@ + + + + + decryptedMessageActionSetMessageTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionSetMessageTTL

+ +

Setting of a message lifetime after reading.

+

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

+

+ +
+
===8===
+decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
ttl_secondsintLifetime in seconds
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionTyping.html b/data/core.telegram.org/constructor/decryptedMessageActionTyping.html new file mode 100644 index 0000000000..b6dee6a583 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionTyping.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionTyping

+ +

User is preparing a message: typing, recording, uploading, etc.

+

+ +
+
===17===
+decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
actionSendMessageActionType of action
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageLayer.html b/data/core.telegram.org/constructor/decryptedMessageLayer.html new file mode 100644 index 0000000000..c73f0aa007 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageLayer.html @@ -0,0 +1,173 @@ + + + + + decryptedMessageLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageLayer

+ +

Sets the layer number for the contents of an encrypted message.

+

+ +
+
===17===
+decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_bytesbytesSet of random bytes to prevent content recognition in short encrypted messages.
Clients are required to check that there are at least 15 random bytes included in each message. Messages with less than 15 random bytes must be ignored.
Parameter moved here from decryptedMessage in Layer 17.
layerintLayer number. Mimimal value - 17 (the layer in which the constructor was added).
in_seq_noint2x the number of messages in the sender's inbox (including deleted and service messages), incremented by 1 if current user was not the chat creator
Parameter added in Layer 17.
out_seq_noint2x the number of messages in the recipient's inbox (including deleted and service messages), incremented by 1 if current user was the chat creator
Parameter added in Layer 17.
messageDecryptedMessageThe content of message itself
+

Type

+

DecryptedMessageLayer

+

Related pages

+

decryptedMessage

+

Contents of an encrypted message.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html b/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html new file mode 100644 index 0000000000..8bd08c313d --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html @@ -0,0 +1,174 @@ + + + + + decryptedMessageMediaAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaAudio

+ +

Audio file attached to a secret chat message.

+

+ +
+
===8===
+decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===17===
+decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
durationintAudio duration in seconds
mime_typestringMIME-type of the audio file
Parameter added in Layer 13.
sizeintFile size
keybytesKey to decrypt the attached media file
ivbytesInitialization vector
+

Type

+

DecryptedMessageMedia

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaContact.html b/data/core.telegram.org/constructor/decryptedMessageMediaContact.html new file mode 100644 index 0000000000..b308706c91 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaContact.html @@ -0,0 +1,163 @@ + + + + + decryptedMessageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaContact

+ +

Contact attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
user_idintTelegram User ID of signed-up contact
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html b/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html new file mode 100644 index 0000000000..7db8d51194 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html @@ -0,0 +1,191 @@ + + + + + decryptedMessageMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaDocument

+ +

Document attached to a message in a secret chat.

+

+ +
+
===8===
+decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
thumbbytesThumbnail-file contents (JPEG-file, quality 55, set in a 90x90 square)
thumb_wintThumbnail width
thumb_hintThumbnail height
mime_typestringFile MIME-type
sizeintDocument size
keybytesKey to decrypt the attached document file
ivbytesInitialization
attributesVector<DocumentAttribute>Document attributes for media types
captionstringCaption
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html b/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html new file mode 100644 index 0000000000..6fafcb2463 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html @@ -0,0 +1,133 @@ + + + + + decryptedMessageMediaEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaEmpty

+ +

Empty constructor, no media content.

+

+ +
+
===8===
+decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html b/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html new file mode 100644 index 0000000000..32baa84ad4 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html @@ -0,0 +1,183 @@ + + + + + decryptedMessageMediaExternalDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaExternalDocument

+ +

Non-e2e documented forwarded from non-secret chat

+

+ +
+
===23===
+decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID
access_hashlongaccess hash
dateintDate
mime_typestringMime type
sizeintSize
thumbPhotoSizeThumbnail
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes for media types
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html b/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html new file mode 100644 index 0000000000..6bd97831ff --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html @@ -0,0 +1,153 @@ + + + + + decryptedMessageMediaGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaGeoPoint

+ +

GeoPont attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
latdoubleLatitude of point
longdoubleLongtitude of point
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html b/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html new file mode 100644 index 0000000000..e3f1ac7a70 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html @@ -0,0 +1,191 @@ + + + + + decryptedMessageMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaPhoto

+ +

Photo attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
thumbbytesContent of thumbnail file (JPEGfile, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
wintPhoto width
hintPhoto height
sizeintSize of the photo in bytes
keybytesKey to decrypt an attached file with a full version
ivbytesInitialization vector
captionstringCaption
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html b/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html new file mode 100644 index 0000000000..c330e81f7c --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html @@ -0,0 +1,173 @@ + + + + + decryptedMessageMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaVenue

+ +

Venue

+

+ +
+
===45===
+decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
latdoubleLatitude of venue
longdoubleLongitude of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html b/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html new file mode 100644 index 0000000000..d57b799699 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html @@ -0,0 +1,207 @@ + + + + + decryptedMessageMediaVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaVideo

+ +

Video attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===17===
+decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
thumbbytesContent of thumbnail file (JPEG file, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
durationintDuration of video in seconds
mime_typestringMIME-type of the video file
Parameter added in Layer 17.
wintImage width
hintImage height
sizeintFile size
keybytesKey to decrypt the attached video file
ivbytesInitialization vector
captionstringCaption
+

Type

+

DecryptedMessageMedia

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html b/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html new file mode 100644 index 0000000000..ede7a98af5 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageMediaWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaWebPage

+ +

Webpage preview

+

+ +
+
===45===
+decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL of webpage
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageService.html b/data/core.telegram.org/constructor/decryptedMessageService.html new file mode 100644 index 0000000000..de1faa372b --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageService.html @@ -0,0 +1,156 @@ + + + + + decryptedMessageService + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageService

+ +

Contents of an encrypted service message.

+

+ +
+
===8===
+decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+
+===17===
+decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_idlongRandom message ID, assigned by the message author.
Must be equal to the ID passed to the sending method.
actionDecryptedMessageActionAction relevant to the service message
+

Type

+

DecryptedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dialog.html b/data/core.telegram.org/constructor/dialog.html new file mode 100644 index 0000000000..5b957328f0 --- /dev/null +++ b/data/core.telegram.org/constructor/dialog.html @@ -0,0 +1,214 @@ + + + + + dialog + + + + + + + + + + + + + +
+ +
+
+
+ +

dialog

+ +

Chat

+

+ +
+
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs the dialog pinned
unread_markflags.3?trueWhether the chat was manually marked as unread
peerPeerThe chat
top_messageintThe latest message ID
read_inbox_max_idintPosition up to which all incoming messages are read.
read_outbox_max_idintPosition up to which all outgoing messages are read.
unread_countintNumber of unread messages
unread_mentions_countintNumber of unread mentions
notify_settingsPeerNotifySettingsNotification settings
ptsflags.0?intPTS
draftflags.1?DraftMessageMessage draft
folder_idflags.4?intPeer folder ID, for more info click here
+

Type

+

Dialog

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dialogFilter.html b/data/core.telegram.org/constructor/dialogFilter.html new file mode 100644 index 0000000000..79d611da43 --- /dev/null +++ b/data/core.telegram.org/constructor/dialogFilter.html @@ -0,0 +1,220 @@ + + + + + dialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogFilter

+ +

Dialog filter AKA folder

+

+ +
+
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to include all contacts in this folder
non_contactsflags.1?trueWhether to include all non-contacts in this folder
groupsflags.2?trueWhether to include all groups in this folder
broadcastsflags.3?trueWhether to include all channels in this folder
botsflags.4?trueWhether to include all bots in this folder
exclude_mutedflags.11?trueWhether to exclude muted chats from this folder
exclude_readflags.12?trueWhether to exclude read chats from this folder
exclude_archivedflags.13?trueWhether to exclude archived chats from this folder
idintFolder ID
titlestringFolder name
emoticonflags.25?stringFolder emoticon
pinned_peersVector<InputPeer>Pinned chats, folders can have unlimited pinned chats
include_peersVector<InputPeer>Include the following chats in this folder
exclude_peersVector<InputPeer>Exclude the following chats from this folder
+

Type

+

DialogFilter

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dialogFilterSuggested.html b/data/core.telegram.org/constructor/dialogFilterSuggested.html new file mode 100644 index 0000000000..d7e5df87c6 --- /dev/null +++ b/data/core.telegram.org/constructor/dialogFilterSuggested.html @@ -0,0 +1,155 @@ + + + + + dialogFilterSuggested + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogFilterSuggested

+ +

Suggested folders

+

+ +
+
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
filterDialogFilterFolder info
descriptionstringFolder description
+

Type

+

DialogFilterSuggested

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dialogFolder.html b/data/core.telegram.org/constructor/dialogFolder.html new file mode 100644 index 0000000000..772045e45a --- /dev/null +++ b/data/core.telegram.org/constructor/dialogFolder.html @@ -0,0 +1,187 @@ + + + + + dialogFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogFolder

+ +

Dialog in folder

+

+ +
+
dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs this folder pinned
folderFolderThe folder
peerPeerPeer in folder
top_messageintLatest message ID of dialog
unread_muted_peers_countintNumber of unread muted peers in folder
unread_unmuted_peers_countintNumber of unread unmuted peers in folder
unread_muted_messages_countintNumber of unread messages from muted peers in folder
unread_unmuted_messages_countintNumber of unread messages from unmuted peers in folder
+

Type

+

Dialog

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dialogPeer.html b/data/core.telegram.org/constructor/dialogPeer.html new file mode 100644 index 0000000000..46835a4ddb --- /dev/null +++ b/data/core.telegram.org/constructor/dialogPeer.html @@ -0,0 +1,147 @@ + + + + + dialogPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogPeer

+ +

Peer

+

+ +
+
dialogPeer#e56dbf05 peer:Peer = DialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
+

Type

+

DialogPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dialogPeerFolder.html b/data/core.telegram.org/constructor/dialogPeerFolder.html new file mode 100644 index 0000000000..807726ff5f --- /dev/null +++ b/data/core.telegram.org/constructor/dialogPeerFolder.html @@ -0,0 +1,150 @@ + + + + + dialogPeerFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogPeerFolder

+ +

Peer folder

+

+ +
+
dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Type

+

DialogPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/disabledFeature.html b/data/core.telegram.org/constructor/disabledFeature.html new file mode 100644 index 0000000000..7f0d00308b --- /dev/null +++ b/data/core.telegram.org/constructor/disabledFeature.html @@ -0,0 +1,163 @@ + + + + + disabledFeature + + + + + + + + + + + + + +
+ +
+
+
+ +

disabledFeature

+ +

A disabled feature

+

+ +
+
Constructor schema is available as of layer 76. Switch »

+

Parameters

+ + + + + + + + + + + + + +
featurestringThe feature that was disabled
descriptionstringDescription
+

Type

+

DisabledFeature

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/document.html b/data/core.telegram.org/constructor/document.html new file mode 100644 index 0000000000..9b220ccb40 --- /dev/null +++ b/data/core.telegram.org/constructor/document.html @@ -0,0 +1,200 @@ + + + + + document + + + + + + + + + + + + + +
+ +
+
+
+ +

document

+ +

Document

+

+ +
+
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idlongDocument ID
access_hashlongCheck sum, dependant on document ID
file_referencebytesFile reference
dateintCreation date
mime_typestringMIME type
sizeintSize
thumbsflags.0?Vector<PhotoSize>Thumbnails
video_thumbsflags.1?Vector<VideoSize>Video thumbnails
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes
+

Type

+

Document

+

Related pages

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeAnimated.html b/data/core.telegram.org/constructor/documentAttributeAnimated.html new file mode 100644 index 0000000000..bd8055a20d --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeAnimated.html @@ -0,0 +1,132 @@ + + + + + documentAttributeAnimated + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeAnimated

+ +

Defines an animated GIF

+

+ +
+
documentAttributeAnimated#11b58939 = DocumentAttribute;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeAudio.html b/data/core.telegram.org/constructor/documentAttributeAudio.html new file mode 100644 index 0000000000..6fc246cc23 --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeAudio.html @@ -0,0 +1,172 @@ + + + + + documentAttributeAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeAudio

+ +

Represents an audio file

+

+ +
+
documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
voiceflags.10?trueWhether this is a voice message
durationintDuration in seconds
titleflags.0?stringName of song
performerflags.1?stringPerformer
waveformflags.2?bytesWaveform
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeFilename.html b/data/core.telegram.org/constructor/documentAttributeFilename.html new file mode 100644 index 0000000000..5adfd817a0 --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeFilename.html @@ -0,0 +1,147 @@ + + + + + documentAttributeFilename + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeFilename

+ +

A simple document with a file name

+

+ +
+
documentAttributeFilename#15590068 file_name:string = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
file_namestringThe file name
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeHasStickers.html b/data/core.telegram.org/constructor/documentAttributeHasStickers.html new file mode 100644 index 0000000000..08ea716327 --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeHasStickers.html @@ -0,0 +1,132 @@ + + + + + documentAttributeHasStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeHasStickers

+ +

Whether the current document has stickers attached

+

+ +
+
documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeImageSize.html b/data/core.telegram.org/constructor/documentAttributeImageSize.html new file mode 100644 index 0000000000..b172bc339c --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeImageSize.html @@ -0,0 +1,152 @@ + + + + + documentAttributeImageSize + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeImageSize

+ +

Defines the width and height of an image uploaded as document

+

+ +
+
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
wintWidth of image
hintHeight of image
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeSticker.html b/data/core.telegram.org/constructor/documentAttributeSticker.html new file mode 100644 index 0000000000..681385d0c7 --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeSticker.html @@ -0,0 +1,167 @@ + + + + + documentAttributeSticker + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeSticker

+ +

Defines a sticker

+

+ +
+
documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
maskflags.1?trueWhether this is a mask sticker
altstringAlternative emoji representation of sticker
stickersetInputStickerSetAssociated stickerset
mask_coordsflags.0?MaskCoordsMask coordinates (if this is a mask sticker, attached to a photo)
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeVideo.html b/data/core.telegram.org/constructor/documentAttributeVideo.html new file mode 100644 index 0000000000..63a0e30596 --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeVideo.html @@ -0,0 +1,172 @@ + + + + + documentAttributeVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeVideo

+ +

Defines a video

+

+ +
+
documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
round_messageflags.0?trueWhether this is a round video
supports_streamingflags.1?trueWhether the video supports streaming
durationintDuration in seconds
wintVideo width
hintVideo height
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentEmpty.html b/data/core.telegram.org/constructor/documentEmpty.html new file mode 100644 index 0000000000..873257a1e7 --- /dev/null +++ b/data/core.telegram.org/constructor/documentEmpty.html @@ -0,0 +1,147 @@ + + + + + documentEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

documentEmpty

+ +

Empty constructor, document doesn't exist.

+

+ +
+
documentEmpty#36f8c871 id:long = Document;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID or 0
+

Type

+

Document

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/draftMessage.html b/data/core.telegram.org/constructor/draftMessage.html new file mode 100644 index 0000000000..052dfef445 --- /dev/null +++ b/data/core.telegram.org/constructor/draftMessage.html @@ -0,0 +1,177 @@ + + + + + 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 new file mode 100644 index 0000000000..8f6fb7c5e8 --- /dev/null +++ b/data/core.telegram.org/constructor/draftMessageEmpty.html @@ -0,0 +1,152 @@ + + + + + draftMessageEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

draftMessageEmpty

+ +

Empty draft

+

+ +
+
draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
dateflags.0?intWhen was the draft last updated
+

Type

+

DraftMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/emojiKeyword.html b/data/core.telegram.org/constructor/emojiKeyword.html new file mode 100644 index 0000000000..7e34a40c58 --- /dev/null +++ b/data/core.telegram.org/constructor/emojiKeyword.html @@ -0,0 +1,152 @@ + + + + + emojiKeyword + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiKeyword

+ +

Emoji keyword

+

+ +
+
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis associated to keyword
+

Type

+

EmojiKeyword

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/emojiKeywordDeleted.html b/data/core.telegram.org/constructor/emojiKeywordDeleted.html new file mode 100644 index 0000000000..10c70c0e2b --- /dev/null +++ b/data/core.telegram.org/constructor/emojiKeywordDeleted.html @@ -0,0 +1,152 @@ + + + + + emojiKeywordDeleted + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiKeywordDeleted

+ +

Deleted emoji keyword

+

+ +
+
emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis that were associated to keyword
+

Type

+

EmojiKeyword

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/emojiKeywordsDifference.html b/data/core.telegram.org/constructor/emojiKeywordsDifference.html new file mode 100644 index 0000000000..338760d0aa --- /dev/null +++ b/data/core.telegram.org/constructor/emojiKeywordsDifference.html @@ -0,0 +1,162 @@ + + + + + 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 new file mode 100644 index 0000000000..982cc08851 --- /dev/null +++ b/data/core.telegram.org/constructor/emojiLanguage.html @@ -0,0 +1,147 @@ + + + + + emojiLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiLanguage

+ +

Emoji language

+

+ +
+
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Type

+

EmojiLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/emojiURL.html b/data/core.telegram.org/constructor/emojiURL.html new file mode 100644 index 0000000000..b87df8a416 --- /dev/null +++ b/data/core.telegram.org/constructor/emojiURL.html @@ -0,0 +1,147 @@ + + + + + emojiURL + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiURL

+ +

An HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

+

+ +
+
emojiURL#a575739d url:string = EmojiURL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+

Type

+

EmojiURL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedChatDiscarded.html b/data/core.telegram.org/constructor/encryptedChatDiscarded.html new file mode 100644 index 0000000000..dc5d6bee34 --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedChatDiscarded.html @@ -0,0 +1,157 @@ + + + + + encryptedChatDiscarded + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatDiscarded

+ +

Discarded or deleted chat.

+

+ +
+
encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
history_deletedflags.0?trueWhether both users of this secret chat should also remove all of its messages
idintChat ID
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedChatEmpty.html b/data/core.telegram.org/constructor/encryptedChatEmpty.html new file mode 100644 index 0000000000..a00b3384eb --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedChatEmpty.html @@ -0,0 +1,147 @@ + + + + + encryptedChatEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatEmpty

+ +

Empty constructor.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idintChat ID
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedChatRequested.html b/data/core.telegram.org/constructor/encryptedChatRequested.html new file mode 100644 index 0000000000..e744d93430 --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedChatRequested.html @@ -0,0 +1,185 @@ + + + + + encryptedChatRequested + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatRequested

+ +

Request to create an encrypted chat.

+

+ +
+
encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
idintChat ID
access_hashlongCheck sum depending on user ID
dateintChat creation date
admin_idlongChat creator ID
participant_idlongID of second chat participant
g_abytesA = g ^ a mod p, see Wikipedia
+

Type

+

EncryptedChat

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedChatWaiting.html b/data/core.telegram.org/constructor/encryptedChatWaiting.html new file mode 100644 index 0000000000..66940da991 --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedChatWaiting.html @@ -0,0 +1,167 @@ + + + + + encryptedChatWaiting + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatWaiting

+ +

Chat waiting for approval of second participant.

+

+ +
+
encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintChat ID
access_hashlongChecking sum depending on user ID
dateintDate of chat creation
admin_idlongChat creator ID
participant_idlongID of second chat participant
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedFileEmpty.html b/data/core.telegram.org/constructor/encryptedFileEmpty.html new file mode 100644 index 0000000000..2ac4199e2a --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedFileEmpty.html @@ -0,0 +1,132 @@ + + + + + encryptedFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedFileEmpty

+ +

Empty constructor, unexisitng file.

+

+ +
+
encryptedFileEmpty#c21f497e = EncryptedFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

EncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedMessage.html b/data/core.telegram.org/constructor/encryptedMessage.html new file mode 100644 index 0000000000..0cddfd4daf --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedMessage.html @@ -0,0 +1,170 @@ + + + + + encryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedMessage

+ +

Encrypted message.

+

+ +
+
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
fileEncryptedFileAttached encrypted file
+

Type

+

EncryptedMessage

+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedMessageService.html b/data/core.telegram.org/constructor/encryptedMessageService.html new file mode 100644 index 0000000000..d994207a2d --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedMessageService.html @@ -0,0 +1,165 @@ + + + + + encryptedMessageService + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedMessageService

+ +

Encrypted service message

+

+ +
+
encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
+

Type

+

EncryptedMessage

+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/error.html b/data/core.telegram.org/constructor/error.html new file mode 100644 index 0000000000..50690654a5 --- /dev/null +++ b/data/core.telegram.org/constructor/error.html @@ -0,0 +1,152 @@ + + + + + error + + + + + + + + + + + + + +
+ +
+
+
+ +

error

+ +

Error.

+

+ +
+
error#c4b9f9bb code:int text:string = Error;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
codeintError code
textstringMessage
+

Type

+

Error

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/exportedMessageLink.html b/data/core.telegram.org/constructor/exportedMessageLink.html new file mode 100644 index 0000000000..7f76b44b8f --- /dev/null +++ b/data/core.telegram.org/constructor/exportedMessageLink.html @@ -0,0 +1,152 @@ + + + + + exportedMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

exportedMessageLink

+ +

Link to a message in a supergroup/channel

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
linkstringURL
htmlstringEmbed code
+

Type

+

ExportedMessageLink

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/fileHash.html b/data/core.telegram.org/constructor/fileHash.html new file mode 100644 index 0000000000..4edb3ffc04 --- /dev/null +++ b/data/core.telegram.org/constructor/fileHash.html @@ -0,0 +1,171 @@ + + + + + FileHash + + + + + + + + + + + + + +
+ +
+
+
+ +

FileHash

+ +

SHA256 Hash of an uploaded file, to be checked for validity after download

+

+ +
+
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset from where to start computing SHA-256 hash
limitintLength
hashbytesSHA-256 Hash of file chunk, to be checked for validity after download
+

Type

+

FileHash

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/fileLocation.html b/data/core.telegram.org/constructor/fileLocation.html new file mode 100644 index 0000000000..e59f25ac3c --- /dev/null +++ b/data/core.telegram.org/constructor/fileLocation.html @@ -0,0 +1,182 @@ + + + + + fileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

fileLocation

+ +

File location.

+

+ +
+
Constructor schema is available as of layer 86. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintNumber of the data center holding the file
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
+

Type

+

FileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/fileLocationUnavailable.html b/data/core.telegram.org/constructor/fileLocationUnavailable.html new file mode 100644 index 0000000000..171eb081e5 --- /dev/null +++ b/data/core.telegram.org/constructor/fileLocationUnavailable.html @@ -0,0 +1,179 @@ + + + + + fileLocationUnavailable + + + + + + + + + + + + + +
+ +
+
+
+ +

fileLocationUnavailable

+ +

File is currently unavailable.

+

+ +
+
Constructor schema is available as of layer 98. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
+

Type

+

FileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/folder.html b/data/core.telegram.org/constructor/folder.html new file mode 100644 index 0000000000..9dae755722 --- /dev/null +++ b/data/core.telegram.org/constructor/folder.html @@ -0,0 +1,177 @@ + + + + + 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/game.html b/data/core.telegram.org/constructor/game.html new file mode 100644 index 0000000000..7d75f1217a --- /dev/null +++ b/data/core.telegram.org/constructor/game.html @@ -0,0 +1,182 @@ + + + + + game + + + + + + + + + + + + + +
+ +
+
+
+ +

game

+ +

Indicates an already sent game

+

+ +
+
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idlongID of the game
access_hashlongAccess hash of the game
short_namestringShort name for the game
titlestringTitle of the game
descriptionstringGame description
photoPhotoGame preview
documentflags.0?DocumentOptional attached document
+

Type

+

Game

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/geoPoint.html b/data/core.telegram.org/constructor/geoPoint.html new file mode 100644 index 0000000000..496f5bbdb0 --- /dev/null +++ b/data/core.telegram.org/constructor/geoPoint.html @@ -0,0 +1,167 @@ + + + + + geoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

geoPoint

+ +

GeoPoint.

+

+ +
+
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
longdoubleLongtitude
latdoubleLatitude
access_hashlongAccess hash
accuracy_radiusflags.0?intThe estimated horizontal accuracy of the location, in meters; as defined by the sender.
+

Type

+

GeoPoint

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/geoPointEmpty.html b/data/core.telegram.org/constructor/geoPointEmpty.html new file mode 100644 index 0000000000..281c782f30 --- /dev/null +++ b/data/core.telegram.org/constructor/geoPointEmpty.html @@ -0,0 +1,132 @@ + + + + + geoPointEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

geoPointEmpty

+ +

Empty constructor.

+

+ +
+
geoPointEmpty#1117dd5f = GeoPoint;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

GeoPoint

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/globalPrivacySettings.html b/data/core.telegram.org/constructor/globalPrivacySettings.html new file mode 100644 index 0000000000..6017aa062a --- /dev/null +++ b/data/core.telegram.org/constructor/globalPrivacySettings.html @@ -0,0 +1,152 @@ + + + + + globalPrivacySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

globalPrivacySettings

+ +

Global privacy settings

+

+ +
+
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
archive_and_mute_new_noncontact_peersflags.0?BoolWhether to archive and mute new chats from non-contacts
+

Type

+

GlobalPrivacySettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/groupCallDiscarded.html b/data/core.telegram.org/constructor/groupCallDiscarded.html new file mode 100644 index 0000000000..757f4b716e --- /dev/null +++ b/data/core.telegram.org/constructor/groupCallDiscarded.html @@ -0,0 +1,157 @@ + + + + + groupCallDiscarded + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCallDiscarded

+ +

An ended group call

+

+ +
+
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongGroup call ID
access_hashlongGroup call access hash
durationintGroup call duration
+

Type

+

GroupCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/groupCallParticipant.html b/data/core.telegram.org/constructor/groupCallParticipant.html new file mode 100644 index 0000000000..de9007327d --- /dev/null +++ b/data/core.telegram.org/constructor/groupCallParticipant.html @@ -0,0 +1,247 @@ + + + + + groupCallParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCallParticipant

+ +

Info about a group call participant

+

+ +
+
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
mutedflags.0?trueWhether the participant is muted
leftflags.1?trueWhether the participant has left
can_self_unmuteflags.2?trueWhether the participant can unmute themselves
just_joinedflags.4?trueWhether the participant has just joined
versionedflags.5?trueIf set, and updateGroupCallParticipants.version < locally stored call.version, info about this participant should be ignored. If (...), and updateGroupCallParticipants.version > call.version+1, the participant list should be refetched using phone.getGroupParticipants.
minflags.8?trueIf not set, the volume and muted_by_you fields can be safely used to overwrite locally cached information; otherwise, volume will contain valid information only if volume_by_admin is set both in the cache and in the received constructor.
muted_by_youflags.9?trueWhether this participant was muted by the current user
volume_by_adminflags.10?trueWhether our volume can only changed by an admin
selfflags.12?trueWhether this participant is the current user
video_joinedflags.15?trueWhether this participant is currently broadcasting video
peerPeerPeer information
dateintWhen did this participant join the group call
active_dateflags.3?intWhen was this participant last active in the group call
sourceintSource ID
volumeflags.7?intVolume, if not set the volume is set to 100%.
aboutflags.11?stringInfo about this participant
raise_hand_ratingflags.13?longSpecifies the UI visualization order of peers with raised hands: peers with a higher rating should be showed first in the list.
videoflags.6?GroupCallParticipantVideoInfo about the video stream the participant is currently broadcasting
presentationflags.14?GroupCallParticipantVideoInfo about the screen sharing stream the participant is currently broadcasting
+

Type

+

GroupCallParticipant

+

Related pages

+

updateGroupCallParticipants

+

The participant list of a certain group call has changed

+

phone.getGroupParticipants

+

Get group call participants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/groupCallParticipantVideo.html b/data/core.telegram.org/constructor/groupCallParticipantVideo.html new file mode 100644 index 0000000000..7adea98c53 --- /dev/null +++ b/data/core.telegram.org/constructor/groupCallParticipantVideo.html @@ -0,0 +1,167 @@ + + + + + groupCallParticipantVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCallParticipantVideo

+ +

Info about a video stream

+

+ +
+
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pausedflags.0?trueWhether the stream is currently paused
endpointstringEndpoint
source_groupsVector<GroupCallParticipantVideoSourceGroup>Source groups
audio_sourceflags.1?intAudio source ID
+

Type

+

GroupCallParticipantVideo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html b/data/core.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html new file mode 100644 index 0000000000..5015af0769 --- /dev/null +++ b/data/core.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html @@ -0,0 +1,152 @@ + + + + + groupCallParticipantVideoSourceGroup + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCallParticipantVideoSourceGroup

+ +

Describes a group of video synchronization source identifiers

+

+ +
+
groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
semanticsstringSDP semantics
sourcesVector<int>Source IDs
+

Type

+

GroupCallParticipantVideoSourceGroup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.countriesList b/data/core.telegram.org/constructor/help.countriesList new file mode 100644 index 0000000000..0ea61c46eb --- /dev/null +++ b/data/core.telegram.org/constructor/help.countriesList @@ -0,0 +1,155 @@ + + + + + help.countriesList + + + + + + + + + + + + + +
+ +
+
+
+ +

help.countriesList

+ +

Name, ISO code, localized name and phone codes/patterns of all available countries

+

+ +
+
help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countriesVector<help.Country>Name, ISO code, localized name and phone codes/patterns of all available countries
hashintHash for pagination, for more info click here
+

Type

+

help.CountriesList

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.countriesListNotModified b/data/core.telegram.org/constructor/help.countriesListNotModified new file mode 100644 index 0000000000..033eb4c430 --- /dev/null +++ b/data/core.telegram.org/constructor/help.countriesListNotModified @@ -0,0 +1,132 @@ + + + + + help.countriesListNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

help.countriesListNotModified

+ +

The country list has not changed

+

+ +
+
help.countriesListNotModified#93cc1f32 = help.CountriesList;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.CountriesList

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.country b/data/core.telegram.org/constructor/help.country new file mode 100644 index 0000000000..48f232d08f --- /dev/null +++ b/data/core.telegram.org/constructor/help.country @@ -0,0 +1,172 @@ + + + + + help.country + + + + + + + + + + + + + +
+ +
+
+
+ +

help.country

+ +

Name, ISO code, localized name and phone codes/patterns of a specific country

+

+ +
+
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
hiddenflags.0?trueWhether this country should not be shown in the list
iso2stringISO code of country
default_namestringName of the country in the country's language
nameflags.1?stringName of the country in the user's language, if different from the original name
country_codesVector<help.CountryCode>Phone codes/patterns
+

Type

+

help.Country

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.countryCode b/data/core.telegram.org/constructor/help.countryCode new file mode 100644 index 0000000000..2626e3dcf4 --- /dev/null +++ b/data/core.telegram.org/constructor/help.countryCode @@ -0,0 +1,162 @@ + + + + + help.countryCode + + + + + + + + + + + + + +
+ +
+
+
+ +

help.countryCode

+ +

Country code and phone number pattern of a specific country

+

+ +
+
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
country_codestringISO country code
prefixesflags.0?Vector<string>Possible phone prefixes
patternsflags.1?Vector<string>Phone patterns: for example, XXX XXX XXX
+

Type

+

help.CountryCode

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.deepLinkInfo b/data/core.telegram.org/constructor/help.deepLinkInfo new file mode 100644 index 0000000000..cbdcdf38e0 --- /dev/null +++ b/data/core.telegram.org/constructor/help.deepLinkInfo @@ -0,0 +1,165 @@ + + + + + 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 new file mode 100644 index 0000000000..36f84eca8d --- /dev/null +++ b/data/core.telegram.org/constructor/help.deepLinkInfoEmpty @@ -0,0 +1,132 @@ + + + + + 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.noAppUpdate b/data/core.telegram.org/constructor/help.noAppUpdate new file mode 100644 index 0000000000..94ec14d918 --- /dev/null +++ b/data/core.telegram.org/constructor/help.noAppUpdate @@ -0,0 +1,132 @@ + + + + + help.noAppUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.noAppUpdate

+ +

No updates are available for the application.

+

+ +
+
help.noAppUpdate#c45a6536 = help.AppUpdate;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.AppUpdate

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.passportConfig b/data/core.telegram.org/constructor/help.passportConfig new file mode 100644 index 0000000000..fd58c3692f --- /dev/null +++ b/data/core.telegram.org/constructor/help.passportConfig @@ -0,0 +1,156 @@ + + + + + help.passportConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.passportConfig

+ +

Telegram passport configuration

+

+ +
+
help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
countries_langsDataJSONLocalization
+

Type

+

help.PassportConfig

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.passportConfigNotModified b/data/core.telegram.org/constructor/help.passportConfigNotModified new file mode 100644 index 0000000000..30ded66bc7 --- /dev/null +++ b/data/core.telegram.org/constructor/help.passportConfigNotModified @@ -0,0 +1,132 @@ + + + + + help.passportConfigNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

help.passportConfigNotModified

+ +

Password configuration not modified

+

+ +
+
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.PassportConfig

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.promoData b/data/core.telegram.org/constructor/help.promoData new file mode 100644 index 0000000000..d78dcd4277 --- /dev/null +++ b/data/core.telegram.org/constructor/help.promoData @@ -0,0 +1,182 @@ + + + + + help.promoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.promoData

+ +

MTProxy/Public Service Announcement information

+

+ +
+
help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
proxyflags.0?trueMTProxy-related channel
expiresintExpiry of PSA/MTProxy info
peerPeerMTProxy/PSA peer
chatsVector<Chat>Chat info
usersVector<User>User info
psa_typeflags.1?stringPSA type
psa_messageflags.2?stringPSA message
+

Type

+

help.PromoData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.promoDataEmpty b/data/core.telegram.org/constructor/help.promoDataEmpty new file mode 100644 index 0000000000..ccfdddebfd --- /dev/null +++ b/data/core.telegram.org/constructor/help.promoDataEmpty @@ -0,0 +1,147 @@ + + + + + help.promoDataEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.promoDataEmpty

+ +

No PSA/MTProxy info is available

+

+ +
+
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintRe-fetch PSA/MTProxy info after the specified number of seconds
+

Type

+

help.PromoData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.recentMeUrls b/data/core.telegram.org/constructor/help.recentMeUrls new file mode 100644 index 0000000000..d3941a8020 --- /dev/null +++ b/data/core.telegram.org/constructor/help.recentMeUrls @@ -0,0 +1,157 @@ + + + + + help.recentMeUrls + + + + + + + + + + + + + +
+ +
+
+
+ +

help.recentMeUrls

+ +

Recent t.me URLs

+

+ +
+
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlsVector<RecentMeUrl>URLs
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

help.RecentMeUrls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.support b/data/core.telegram.org/constructor/help.support new file mode 100644 index 0000000000..9fd3a27f7d --- /dev/null +++ b/data/core.telegram.org/constructor/help.support @@ -0,0 +1,152 @@ + + + + + help.support + + + + + + + + + + + + + +
+ +
+
+
+ +

help.support

+ +

Info on support user.

+

+ +
+
help.support#17c6b5f6 phone_number:string user:User = help.Support;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
userUserUser
+

Type

+

help.Support

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.supportName b/data/core.telegram.org/constructor/help.supportName new file mode 100644 index 0000000000..1678b3093b --- /dev/null +++ b/data/core.telegram.org/constructor/help.supportName @@ -0,0 +1,147 @@ + + + + + help.supportName + + + + + + + + + + + + + +
+ +
+
+
+ +

help.supportName

+ +

Localized name for telegram support

+

+ +
+
help.supportName#8c05f1c9 name:string = help.SupportName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
namestringLocalized name
+

Type

+

help.SupportName

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.termsOfService b/data/core.telegram.org/constructor/help.termsOfService new file mode 100644 index 0000000000..a541b36b04 --- /dev/null +++ b/data/core.telegram.org/constructor/help.termsOfService @@ -0,0 +1,175 @@ + + + + + help.termsOfService + + + + + + + + + + + + + +
+ +
+
+
+ +

help.termsOfService

+ +

Info about the latest telegram Terms Of Service

+

+ +
+
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?trueWhether a prompt must be showed to the user, in order to accept the new terms.
idDataJSONID of the new terms
textstringText of the new terms
entitiesVector<MessageEntity>Message entities for styled text
min_age_confirmflags.1?intMinimum age required to sign up to telegram, the user must confirm that they is older than the minimum age.
+

Type

+

help.TermsOfService

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.termsOfServiceUpdate b/data/core.telegram.org/constructor/help.termsOfServiceUpdate new file mode 100644 index 0000000000..f8a6a726cf --- /dev/null +++ b/data/core.telegram.org/constructor/help.termsOfServiceUpdate @@ -0,0 +1,157 @@ + + + + + help.termsOfServiceUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.termsOfServiceUpdate

+ +

Info about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"

+

+ +
+
help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
terms_of_servicehelp.TermsOfServiceNew terms of service
+

Type

+

help.TermsOfServiceUpdate

+

Related pages

+

help.getTermsOfServiceUpdate

+

Look for updates of telegram's terms of service

+

account.deleteAccount

+

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty b/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty new file mode 100644 index 0000000000..9e7c7a5816 --- /dev/null +++ b/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty @@ -0,0 +1,150 @@ + + + + + help.termsOfServiceUpdateEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.termsOfServiceUpdateEmpty

+ +

No changes were made to telegram's terms of service

+

+ +
+
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
+

Type

+

help.TermsOfServiceUpdate

+

Related pages

+

help.getTermsOfServiceUpdate

+

Look for updates of telegram's terms of service

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.userInfo b/data/core.telegram.org/constructor/help.userInfo new file mode 100644 index 0000000000..59adcc9e18 --- /dev/null +++ b/data/core.telegram.org/constructor/help.userInfo @@ -0,0 +1,165 @@ + + + + + help.userInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.userInfo

+ +

Internal use

+

+ +
+
help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagestringInfo
entitiesVector<MessageEntity>Message entities for styled text
authorstringAuthor
dateintDate
+

Type

+

help.UserInfo

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.userInfoEmpty b/data/core.telegram.org/constructor/help.userInfoEmpty new file mode 100644 index 0000000000..785d3211d1 --- /dev/null +++ b/data/core.telegram.org/constructor/help.userInfoEmpty @@ -0,0 +1,132 @@ + + + + + help.userInfoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.userInfoEmpty

+ +

Internal use

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.UserInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/highScore.html b/data/core.telegram.org/constructor/highScore.html new file mode 100644 index 0000000000..f7d137486c --- /dev/null +++ b/data/core.telegram.org/constructor/highScore.html @@ -0,0 +1,157 @@ + + + + + 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/inlineBotSwitchPM.html b/data/core.telegram.org/constructor/inlineBotSwitchPM.html new file mode 100644 index 0000000000..6d3591f322 --- /dev/null +++ b/data/core.telegram.org/constructor/inlineBotSwitchPM.html @@ -0,0 +1,152 @@ + + + + + inlineBotSwitchPM + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineBotSwitchPM

+ +

The bot requested the user to message him in private

+

+ +
+
inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstringText for the button that switches the user to a private chat with the bot and sends the bot a start message with the parameter start_parameter (can be empty)
start_paramstringThe parameter for the /start parameter
+

Type

+

InlineBotSwitchPM

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html new file mode 100644 index 0000000000..5b9493c1d7 --- /dev/null +++ b/data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html @@ -0,0 +1,135 @@ + + + + + inlineQueryPeerTypeBroadcast + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeBroadcast

+ +

The inline query was sent in a channel

+

+ +
+
inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeChat.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeChat.html new file mode 100644 index 0000000000..a2965a58d3 --- /dev/null +++ b/data/core.telegram.org/constructor/inlineQueryPeerTypeChat.html @@ -0,0 +1,135 @@ + + + + + inlineQueryPeerTypeChat + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeChat

+ +

The inline query was sent in a chat

+

+ +
+
inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html new file mode 100644 index 0000000000..34576da4ac --- /dev/null +++ b/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html @@ -0,0 +1,135 @@ + + + + + inlineQueryPeerTypeMegagroup + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeMegagroup

+ +

The inline query was sent in a supergroup

+

+ +
+
inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypePM.html b/data/core.telegram.org/constructor/inlineQueryPeerTypePM.html new file mode 100644 index 0000000000..fde1ebb46c --- /dev/null +++ b/data/core.telegram.org/constructor/inlineQueryPeerTypePM.html @@ -0,0 +1,132 @@ + + + + + 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/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html new file mode 100644 index 0000000000..22b1e8a59c --- /dev/null +++ b/data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html @@ -0,0 +1,132 @@ + + + + + inlineQueryPeerTypeSameBotPM + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeSameBotPM

+ +

The inline query was sent in a private chat with the bot itself

+

+ +
+
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputAppEvent.html b/data/core.telegram.org/constructor/inputAppEvent.html new file mode 100644 index 0000000000..dbff673a46 --- /dev/null +++ b/data/core.telegram.org/constructor/inputAppEvent.html @@ -0,0 +1,162 @@ + + + + + inputAppEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

inputAppEvent

+ +

Event that occured in the application.

+

+ +
+
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
timedoubleClient's exact timestamp for the event
typestringType of event
peerlongArbitrary numeric value for more convenient selection of certain event types, or events referring to a certain object
dataJSONValueDetails of the event
+

Type

+

InputAppEvent

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageGame.html b/data/core.telegram.org/constructor/inputBotInlineMessageGame.html new file mode 100644 index 0000000000..4d56e62a47 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageGame.html @@ -0,0 +1,152 @@ + + + + + inputBotInlineMessageGame + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageGame

+ +

A game

+

+ +
+
inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageID.html b/data/core.telegram.org/constructor/inputBotInlineMessageID.html new file mode 100644 index 0000000000..19b00417b6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageID.html @@ -0,0 +1,157 @@ + + + + + inputBotInlineMessageID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageID

+ +

Represents a sent inline message from the perspective of a bot (legacy constructor)

+

+ +
+
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintDC ID to use when working with this inline message
idlongID of message, contains both the (32-bit, legacy) owner ID and the message ID, used only for Bot API backwards compatibility with 32-bit user ID.
access_hashlongAccess hash of message
+

Type

+

InputBotInlineMessageID

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageID64.html b/data/core.telegram.org/constructor/inputBotInlineMessageID64.html new file mode 100644 index 0000000000..e00f17ecde --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageID64.html @@ -0,0 +1,162 @@ + + + + + inputBotInlineMessageID64 + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageID64

+ +

Represents a sent inline message from the perspective of a bot

+

+ +
+
inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintDC ID to use when working with this inline message
owner_idlongID of the owner of this message
idintID of message
access_hashlongAccess hash of message
+

Type

+

InputBotInlineMessageID

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html new file mode 100644 index 0000000000..e486db81c4 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html @@ -0,0 +1,165 @@ + + + + + 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 new file mode 100644 index 0000000000..97e3df4376 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html @@ -0,0 +1,172 @@ + + + + + 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 new file mode 100644 index 0000000000..b65b63cb30 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html @@ -0,0 +1,175 @@ + + + + + inputBotInlineMessageMediaGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageMediaGeo

+ +

Geolocation

+

+ +
+
inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodflags.1?intValidity period
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
reply_markupflags.2?ReplyMarkupReply markup for bot/inline keyboards
+

Type

+

InputBotInlineMessage

+

Related pages

+

Live geolocation

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html new file mode 100644 index 0000000000..da702cb351 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html @@ -0,0 +1,187 @@ + + + + + inputBotInlineMessageMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageMediaInvoice

+ +

An invoice

+

+ +
+
inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentInvoice photo
invoiceInvoiceThe invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerstringPayments provider token, obtained via Botfather
provider_dataDataJSONA JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html new file mode 100644 index 0000000000..a9df186da6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html @@ -0,0 +1,182 @@ + + + + + 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 new file mode 100644 index 0000000000..7519809734 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineMessageText.html @@ -0,0 +1,170 @@ + + + + + inputBotInlineMessageText + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageText

+ +

Simple text message

+

+ +
+
inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringMessage
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineResult.html b/data/core.telegram.org/constructor/inputBotInlineResult.html new file mode 100644 index 0000000000..d054d480a7 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineResult.html @@ -0,0 +1,189 @@ + + + + + inputBotInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResult

+ +

An inline bot result

+

+ +
+
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringID of result
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of result
thumbflags.4?InputWebDocumentThumbnail for result
contentflags.5?InputWebDocumentResult contents
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineResultDocument.html b/data/core.telegram.org/constructor/inputBotInlineResultDocument.html new file mode 100644 index 0000000000..7201913625 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineResultDocument.html @@ -0,0 +1,179 @@ + + + + + inputBotInlineResultDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResultDocument

+ +

Document (media of any type except for photos)

+

+ +
+
inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
documentInputDocumentDocument to send
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineResultGame.html b/data/core.telegram.org/constructor/inputBotInlineResultGame.html new file mode 100644 index 0000000000..ce75d7eb22 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineResultGame.html @@ -0,0 +1,157 @@ + + + + + inputBotInlineResultGame + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResultGame

+ +

Game

+

+ +
+
inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringResult ID
short_namestringGame short name
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html b/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html new file mode 100644 index 0000000000..cb0d8308c0 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html @@ -0,0 +1,164 @@ + + + + + inputBotInlineResultPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResultPhoto

+ +

Photo

+

+ +
+
inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringResult ID
typestringResult type (see bot API docs)
photoInputPhotoPhoto to send
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChannel.html b/data/core.telegram.org/constructor/inputChannel.html new file mode 100644 index 0000000000..446f12351e --- /dev/null +++ b/data/core.telegram.org/constructor/inputChannel.html @@ -0,0 +1,155 @@ + + + + + inputChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChannel

+ +

Represents a channel

+

+ +
+
inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
access_hashlongAccess hash taken from the channel constructor
+

Type

+

InputChannel

+

Related pages

+

channel

+

Channel/supergroup info

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChannelEmpty.html b/data/core.telegram.org/constructor/inputChannelEmpty.html new file mode 100644 index 0000000000..cbda28bc2a --- /dev/null +++ b/data/core.telegram.org/constructor/inputChannelEmpty.html @@ -0,0 +1,132 @@ + + + + + inputChannelEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChannelEmpty

+ +

Represents the absence of a channel

+

+ +
+
inputChannelEmpty#ee8c1e86 = InputChannel;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputChannel

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChannelFromMessage.html b/data/core.telegram.org/constructor/inputChannelFromMessage.html new file mode 100644 index 0000000000..c35d28fc4d --- /dev/null +++ b/data/core.telegram.org/constructor/inputChannelFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputChannelFromMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChannelFromMessage

+ +

Defines a min channel that was seen in a certain message of a certain chat.

+

+ +
+
inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the channel was seen
msg_idintThe message ID in the chat where the channel was seen
channel_idlongThe channel ID
+

Type

+

InputChannel

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChatPhoto.html b/data/core.telegram.org/constructor/inputChatPhoto.html new file mode 100644 index 0000000000..6b4d04dc66 --- /dev/null +++ b/data/core.telegram.org/constructor/inputChatPhoto.html @@ -0,0 +1,147 @@ + + + + + inputChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatPhoto

+ +

Existing photo to be set as a chat profile photo.

+

+ +
+
inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPhotoExisting photo
+

Type

+

InputChatPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChatPhotoEmpty.html b/data/core.telegram.org/constructor/inputChatPhotoEmpty.html new file mode 100644 index 0000000000..0bbacd38ac --- /dev/null +++ b/data/core.telegram.org/constructor/inputChatPhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + inputChatPhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatPhotoEmpty

+ +

Empty constructor, remove group photo.

+

+ +
+
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputChatPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChatUploadedPhoto.html b/data/core.telegram.org/constructor/inputChatUploadedPhoto.html new file mode 100644 index 0000000000..9c2878c525 --- /dev/null +++ b/data/core.telegram.org/constructor/inputChatUploadedPhoto.html @@ -0,0 +1,165 @@ + + + + + inputChatUploadedPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatUploadedPhoto

+ +

New photo to be set as group profile photo.

+

+ +
+
inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts using the method upload.saveFilePart
videoflags.1?InputFileSquare video for animated profile picture
video_start_tsflags.2?doubleTimestamp that should be shown as static preview to the user (seconds)
+

Type

+

InputChatPhoto

+

Related pages

+

upload.saveFilePart

+

Saves a part of file for futher sending to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html b/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html new file mode 100644 index 0000000000..6ee3bb2418 --- /dev/null +++ b/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html @@ -0,0 +1,132 @@ + + + + + inputCheckPasswordEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputCheckPasswordEmpty

+ +

There is no password

+

+ +
+
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputCheckPasswordSRP

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputCheckPasswordSRP.html b/data/core.telegram.org/constructor/inputCheckPasswordSRP.html new file mode 100644 index 0000000000..c10f94221e --- /dev/null +++ b/data/core.telegram.org/constructor/inputCheckPasswordSRP.html @@ -0,0 +1,160 @@ + + + + + inputCheckPasswordSRP + + + + + + + + + + + + + +
+ +
+
+
+ +

inputCheckPasswordSRP

+ +

Constructor for checking the validity of a 2FA SRP password (see SRP)

+

+ +
+
inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
srp_idlongSRP ID
AbytesA parameter (see SRP)
M1bytesM1 parameter (see SRP)
+

Type

+

InputCheckPasswordSRP

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputClientProxy.html b/data/core.telegram.org/constructor/inputClientProxy.html new file mode 100644 index 0000000000..622a381c94 --- /dev/null +++ b/data/core.telegram.org/constructor/inputClientProxy.html @@ -0,0 +1,154 @@ + + + + + inputClientProxy + + + + + + + + + + + + + +
+ +
+
+
+ +

inputClientProxy

+ +

Info about an MTProxy used to connect.

+

+ +
+
inputClientProxy#75588b3f address:string port:int = InputClientProxy;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
addressstringProxy address
portintProxy port
+

Type

+

InputClientProxy

+

Related pages

+

MTProto transports

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputDialogPeer.html b/data/core.telegram.org/constructor/inputDialogPeer.html new file mode 100644 index 0000000000..f2f30e9651 --- /dev/null +++ b/data/core.telegram.org/constructor/inputDialogPeer.html @@ -0,0 +1,147 @@ + + + + + inputDialogPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDialogPeer

+ +

A peer

+

+ +
+
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
+

Type

+

InputDialogPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputDialogPeerFolder.html b/data/core.telegram.org/constructor/inputDialogPeerFolder.html new file mode 100644 index 0000000000..ac4abe8a2e --- /dev/null +++ b/data/core.telegram.org/constructor/inputDialogPeerFolder.html @@ -0,0 +1,150 @@ + + + + + inputDialogPeerFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDialogPeerFolder

+ +

All peers in a peer folder

+

+ +
+
inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Type

+

InputDialogPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputDocument.html b/data/core.telegram.org/constructor/inputDocument.html new file mode 100644 index 0000000000..8e1427d141 --- /dev/null +++ b/data/core.telegram.org/constructor/inputDocument.html @@ -0,0 +1,162 @@ + + + + + inputDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocument

+ +

Defines a video for subsequent interaction.

+

+ +
+
inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
+

Type

+

InputDocument

+

Related pages

+

document

+

Document

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputDocumentEmpty.html b/data/core.telegram.org/constructor/inputDocumentEmpty.html new file mode 100644 index 0000000000..fd5b82388f --- /dev/null +++ b/data/core.telegram.org/constructor/inputDocumentEmpty.html @@ -0,0 +1,132 @@ + + + + + inputDocumentEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocumentEmpty

+ +

Empty constructor.

+

+ +
+
inputDocumentEmpty#72f0eaae = InputDocument;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputDocument

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputDocumentFileLocation.html b/data/core.telegram.org/constructor/inputDocumentFileLocation.html new file mode 100644 index 0000000000..8646345423 --- /dev/null +++ b/data/core.telegram.org/constructor/inputDocumentFileLocation.html @@ -0,0 +1,167 @@ + + + + + inputDocumentFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocumentFileLocation

+ +

Document location (video, voice, audio, basically every type except photo)

+

+ +
+
inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
thumb_sizestringThumbnail size to download the thumbnail
+

Type

+

InputFileLocation

+

Related pages

+

document

+

Document

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputEncryptedChat.html b/data/core.telegram.org/constructor/inputEncryptedChat.html new file mode 100644 index 0000000000..5aa25b5c19 --- /dev/null +++ b/data/core.telegram.org/constructor/inputEncryptedChat.html @@ -0,0 +1,159 @@ + + + + + inputEncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedChat

+ +

Creates an encrypted chat.

+

+ +
+
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idintChat ID
access_hashlongChecking sum from constructor encryptedChat, encryptedChatWaiting or encryptedChatRequested
+

Type

+

InputEncryptedChat

+

Related pages

+

encryptedChat

+

Encrypted chat

+

encryptedChatWaiting

+

Chat waiting for approval of second participant.

+

encryptedChatRequested

+

Request to create an encrypted chat.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputEncryptedFile.html b/data/core.telegram.org/constructor/inputEncryptedFile.html new file mode 100644 index 0000000000..da625b6136 --- /dev/null +++ b/data/core.telegram.org/constructor/inputEncryptedFile.html @@ -0,0 +1,155 @@ + + + + + inputEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFile

+ +

Sets forwarded encrypted file for attachment.

+

+ +
+
inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongFile ID, value of id parameter from encryptedFile
access_hashlongChecking sum, value of access_hash parameter from encryptedFile
+

Type

+

InputEncryptedFile

+

Related pages

+

encryptedFile

+

Encrypted file.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html b/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html new file mode 100644 index 0000000000..99734c28a4 --- /dev/null +++ b/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html @@ -0,0 +1,160 @@ + + + + + inputEncryptedFileBigUploaded + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileBigUploaded

+ +

Assigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.

+

+ +
+
inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of saved parts
key_fingerprintint32-bit imprint of the key used to encrypt the file
+

Type

+

InputEncryptedFile

+

Related pages

+

upload.saveBigFilePart

+

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html b/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html new file mode 100644 index 0000000000..d4ff3e220e --- /dev/null +++ b/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html @@ -0,0 +1,132 @@ + + + + + inputEncryptedFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileEmpty

+ +

Empty constructor.

+

+ +
+
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputEncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputEncryptedFileLocation.html b/data/core.telegram.org/constructor/inputEncryptedFileLocation.html new file mode 100644 index 0000000000..9cbf818169 --- /dev/null +++ b/data/core.telegram.org/constructor/inputEncryptedFileLocation.html @@ -0,0 +1,155 @@ + + + + + inputEncryptedFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileLocation

+ +

Location of encrypted secret chat file.

+

+ +
+
inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongFile ID, id parameter value from encryptedFile
access_hashlongChecksum, access_hash parameter value from encryptedFile
+

Type

+

InputFileLocation

+

Related pages

+

encryptedFile

+

Encrypted file.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html b/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html new file mode 100644 index 0000000000..9b74ed857d --- /dev/null +++ b/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html @@ -0,0 +1,162 @@ + + + + + inputEncryptedFileUploaded + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileUploaded

+ +

Sets new encrypted file saved by parts using upload.saveFilePart method.

+

+ +
+
inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongRandom file ID created by clien
partsintNumber of saved parts
md5_checksumstringIn case md5-HASH of the (already encrypted) file was transmitted, file content will be checked prior to use
key_fingerprintint32-bit fingerprint of the key used to encrypt a file
+

Type

+

InputEncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputFile.html b/data/core.telegram.org/constructor/inputFile.html new file mode 100644 index 0000000000..1e85ee5228 --- /dev/null +++ b/data/core.telegram.org/constructor/inputFile.html @@ -0,0 +1,165 @@ + + + + + inputFile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputFile

+ +

Defines a file saved in parts using the method upload.saveFilePart.

+

+ +
+
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongRandom file identifier created by the client
partsintNumber of parts saved
namestringFull name of the file
md5_checksumstringIn case the file's md5-hash was passed, contents of the file will be checked prior to use
+

Type

+

InputFile

+

Related pages

+

upload.saveFilePart

+

Saves a part of file for futher sending to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputFileBig.html b/data/core.telegram.org/constructor/inputFileBig.html new file mode 100644 index 0000000000..c173b0a37d --- /dev/null +++ b/data/core.telegram.org/constructor/inputFileBig.html @@ -0,0 +1,160 @@ + + + + + inputFileBig + + + + + + + + + + + + + +
+ +
+
+
+ +

inputFileBig

+ +

Assigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.

+

+ +
+
inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of parts saved
namestringFull file name
+

Type

+

InputFile

+

Related pages

+

upload.saveBigFilePart

+

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputFileLocation.html b/data/core.telegram.org/constructor/inputFileLocation.html new file mode 100644 index 0000000000..80d6f2e22e --- /dev/null +++ b/data/core.telegram.org/constructor/inputFileLocation.html @@ -0,0 +1,165 @@ + + + + + inputFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputFileLocation

+ +

DEPRECATED location of a photo

+

+ +
+
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
volume_idlongServer volume
local_idintFile identifier
secretlongCheck sum to access the file
file_referencebytesFile reference
+

Type

+

InputFileLocation

+

Related pages

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputFolderPeer.html b/data/core.telegram.org/constructor/inputFolderPeer.html new file mode 100644 index 0000000000..0e6afeeef7 --- /dev/null +++ b/data/core.telegram.org/constructor/inputFolderPeer.html @@ -0,0 +1,155 @@ + + + + + inputFolderPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

inputFolderPeer

+ +

Peer in a folder

+

+ +
+
inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
folder_idintPeer folder ID, for more info click here
+

Type

+

InputFolderPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputGameID.html b/data/core.telegram.org/constructor/inputGameID.html new file mode 100644 index 0000000000..d651626822 --- /dev/null +++ b/data/core.telegram.org/constructor/inputGameID.html @@ -0,0 +1,155 @@ + + + + + inputGameID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGameID

+ +

Indicates an already sent game

+

+ +
+
inputGameID#32c3e77 id:long access_hash:long = InputGame;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlonggame ID from Game constructor
access_hashlongaccess hash from Game constructor
+

Type

+

InputGame

+

Related pages

+

Game

+

Indicates an already sent game

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputGameShortName.html b/data/core.telegram.org/constructor/inputGameShortName.html new file mode 100644 index 0000000000..300b20232b --- /dev/null +++ b/data/core.telegram.org/constructor/inputGameShortName.html @@ -0,0 +1,152 @@ + + + + + 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 new file mode 100644 index 0000000000..5f8ae96eaa --- /dev/null +++ b/data/core.telegram.org/constructor/inputGeoPoint.html @@ -0,0 +1,162 @@ + + + + + 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/inputGroupCall.html b/data/core.telegram.org/constructor/inputGroupCall.html new file mode 100644 index 0000000000..30b035aa84 --- /dev/null +++ b/data/core.telegram.org/constructor/inputGroupCall.html @@ -0,0 +1,152 @@ + + + + + inputGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGroupCall

+ +

Points to a specific group call

+

+ +
+
inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongGroup call ID
access_hashlongGroup call access hash
+

Type

+

InputGroupCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputGroupCallStream.html b/data/core.telegram.org/constructor/inputGroupCallStream.html new file mode 100644 index 0000000000..f94ce73d66 --- /dev/null +++ b/data/core.telegram.org/constructor/inputGroupCallStream.html @@ -0,0 +1,172 @@ + + + + + inputGroupCallStream + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGroupCallStream

+ +

Chunk of a livestream

+

+ +
+
inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallLivestream info
time_mslongTimestamp in milliseconds
scaleintSpecifies the duration of the video segment to fetch in milliseconds, by bitshifting 1000 to the right scale times: duration_ms := 1000 >> scale
video_channelflags.0?intSelected video channel
video_qualityflags.0?intSelected video quality (0 = lowest, 1 = medium, 2 = best)
+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html b/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html new file mode 100644 index 0000000000..2de7853f5c --- /dev/null +++ b/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html @@ -0,0 +1,176 @@ + + + + + inputKeyboardButtonUrlAuth + + + + + + + + + + + + + +
+ +
+
+
+ +

inputKeyboardButtonUrlAuth

+ +

Button to request a user to authorize via URL using Seamless Telegram Login.

+

+ +
+
inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueSet this flag to request the permission for your bot to send messages to the user.
textstringButton text
fwd_textflags.1?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.
NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
botInputUserUsername of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
+

Type

+

KeyboardButton

+

Related pages

+

Telegram Login Widget

+

messages.acceptUrlAuth

+

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaContact.html b/data/core.telegram.org/constructor/inputMediaContact.html new file mode 100644 index 0000000000..0cfb9daa93 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaContact.html @@ -0,0 +1,162 @@ + + + + + inputMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaContact

+ +

Phonebook contact

+

+ +
+
inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringContact vcard
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaDice.html b/data/core.telegram.org/constructor/inputMediaDice.html new file mode 100644 index 0000000000..d4970073bd --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaDice.html @@ -0,0 +1,150 @@ + + + + + inputMediaDice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaDice

+ +

Send a dice-based animated sticker

+

+ +
+
inputMediaDice#e66fbf7b emoticon:string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
+

Type

+

InputMedia

+

Related pages

+

Dice

+

Telegram supports sending animated dice emojis.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaDocument.html b/data/core.telegram.org/constructor/inputMediaDocument.html new file mode 100644 index 0000000000..72afc685b3 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaDocument.html @@ -0,0 +1,162 @@ + + + + + inputMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaDocument

+ +

Forwarded document

+

+ +
+
inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idInputDocumentThe document to be forwarded.
ttl_secondsflags.0?intTime to live of self-destructing document
queryflags.1?stringText query or emoji that was used by the user to find this sticker or GIF: used to improve search result relevance.
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaDocumentExternal.html b/data/core.telegram.org/constructor/inputMediaDocumentExternal.html new file mode 100644 index 0000000000..fa2d260996 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaDocumentExternal.html @@ -0,0 +1,157 @@ + + + + + inputMediaDocumentExternal + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaDocumentExternal

+ +

Document that will be downloaded by the telegram servers

+

+ +
+
inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the document
ttl_secondsflags.0?intSelf-destruct time to live of document
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaEmpty.html b/data/core.telegram.org/constructor/inputMediaEmpty.html new file mode 100644 index 0000000000..9134ab2239 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaEmpty.html @@ -0,0 +1,132 @@ + + + + + inputMediaEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaEmpty

+ +

Empty media content of a message.

+

+ +
+
inputMediaEmpty#9664f57f = InputMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaGame.html b/data/core.telegram.org/constructor/inputMediaGame.html new file mode 100644 index 0000000000..f48c578646 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaGame.html @@ -0,0 +1,147 @@ + + + + + inputMediaGame + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaGame

+ +

A game

+

+ +
+
inputMediaGame#d33f43f3 id:InputGame = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputGameThe game to forward
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaGeoLive.html b/data/core.telegram.org/constructor/inputMediaGeoLive.html new file mode 100644 index 0000000000..4b7c529d09 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaGeoLive.html @@ -0,0 +1,175 @@ + + + + + inputMediaGeoLive + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaGeoLive

+ +

Live geolocation

+

+ +
+
inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
stoppedflags.0?trueWhether sending of the geolocation was stopped
geo_pointInputGeoPointCurrent geolocation
headingflags.2?intFor live locations, a direction in which the location moves, in degrees; 1-360.
periodflags.1?intValidity period of the current location
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
+

Type

+

InputMedia

+

Related pages

+

Live geolocation

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaGeoPoint.html b/data/core.telegram.org/constructor/inputMediaGeoPoint.html new file mode 100644 index 0000000000..5a5dc83319 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaGeoPoint.html @@ -0,0 +1,147 @@ + + + + + inputMediaGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaGeoPoint

+ +

Map.

+

+ +
+
inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointInputGeoPointGeoPoint
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaInvoice.html b/data/core.telegram.org/constructor/inputMediaInvoice.html new file mode 100644 index 0000000000..453dc2c840 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaInvoice.html @@ -0,0 +1,189 @@ + + + + + inputMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaInvoice

+ +

Generated invoice of a bot payment

+

+ +
+
inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
invoiceInvoiceThe actual invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerstringPayments provider token, obtained via Botfather
provider_dataDataJSONJSON-encoded data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
start_paramflags.1?stringStart parameter
+

Type

+

InputMedia

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaPhoto.html b/data/core.telegram.org/constructor/inputMediaPhoto.html new file mode 100644 index 0000000000..112d09c05b --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaPhoto.html @@ -0,0 +1,157 @@ + + + + + inputMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaPhoto

+ +

Forwarded photo

+

+ +
+
inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idInputPhotoPhoto to be forwarded
ttl_secondsflags.0?intTime to live in seconds of self-destructing photo
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaPoll.html b/data/core.telegram.org/constructor/inputMediaPoll.html new file mode 100644 index 0000000000..f974f133c5 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaPoll.html @@ -0,0 +1,170 @@ + + + + + inputMediaPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaPoll

+ +

A poll

+

+ +
+
inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pollPollThe poll to send
correct_answersflags.0?Vector<bytes>Correct answer IDs (for quiz polls)
solutionflags.1?stringExplanation of quiz solution
solution_entitiesflags.1?Vector<MessageEntity>Message entities for styled text
+

Type

+

InputMedia

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaUploadedDocument.html b/data/core.telegram.org/constructor/inputMediaUploadedDocument.html new file mode 100644 index 0000000000..8f8034f307 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaUploadedDocument.html @@ -0,0 +1,190 @@ + + + + + inputMediaUploadedDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaUploadedDocument

+ +

New document

+

+ +
+
inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
nosound_videoflags.3?trueWhether the specified document is a video file with no audio tracks (a GIF animation (even as MPEG4), for example)
force_fileflags.4?trueForce the media file to be uploaded as document
fileInputFileThe uploaded file
thumbflags.2?InputFileThumbnail of the document, uploaded as for the file
mime_typestringMIME type of document
attributesVector<DocumentAttribute>Attributes that specify the type of the document (video, audio, voice, sticker, etc.)
stickersflags.0?Vector<InputDocument>Attached stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing document
+

Type

+

InputMedia

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html b/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html new file mode 100644 index 0000000000..809c3dffe9 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html @@ -0,0 +1,165 @@ + + + + + inputMediaUploadedPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaUploadedPhoto

+ +

Photo

+

+ +
+
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileThe uploaded file
stickersflags.0?Vector<InputDocument>Attached mask stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing photo
+

Type

+

InputMedia

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html b/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html new file mode 100644 index 0000000000..6f562d9add --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html @@ -0,0 +1,176 @@ + + + + + inputMediaUploadedThumbDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaUploadedThumbDocument

+ +

New document with a thumbnail.

+

+ +
+
Constructor schema is available as of layer 22. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
fileInputFileDocument, saved in parts by using the methods upload.saveFilePart or upload.saveBigFilePart
thumbInputFileThumbnail file, saved in parts by using upload.saveFilePart
file_namestringFile name with extension
mime_typestringFile MIME-type
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaVenue.html b/data/core.telegram.org/constructor/inputMediaVenue.html new file mode 100644 index 0000000000..b56966fc83 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaVenue.html @@ -0,0 +1,172 @@ + + + + + inputMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaVenue

+ +

Can be used to send a venue geolocation.

+

+ +
+
inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringPhysical address of the venue
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessageCallbackQuery.html b/data/core.telegram.org/constructor/inputMessageCallbackQuery.html new file mode 100644 index 0000000000..6afc34fe1e --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessageCallbackQuery.html @@ -0,0 +1,152 @@ + + + + + inputMessageCallbackQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageCallbackQuery

+ +

Used by bots for fetching information about the message that originated a callback query

+

+ +
+
inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintMessage ID
query_idlongCallback query ID
+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessageEntityMentionName.html b/data/core.telegram.org/constructor/inputMessageEntityMentionName.html new file mode 100644 index 0000000000..7b8f9b9fcd --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessageEntityMentionName.html @@ -0,0 +1,162 @@ + + + + + inputMessageEntityMentionName + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageEntityMentionName

+ +

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

+

+ +
+
inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idInputUserIdentifier of the user that was mentioned
+

Type

+

MessageEntity

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

messageEntityMentionName

+

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessageID.html b/data/core.telegram.org/constructor/inputMessageID.html new file mode 100644 index 0000000000..e963113d09 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessageID.html @@ -0,0 +1,147 @@ + + + + + inputMessageID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageID

+ +

Message by ID

+

+ +
+
inputMessageID#a676a322 id:int = InputMessage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idintMessage ID
+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagePinned.html b/data/core.telegram.org/constructor/inputMessagePinned.html new file mode 100644 index 0000000000..8f1e3668e0 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagePinned.html @@ -0,0 +1,132 @@ + + + + + inputMessagePinned + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagePinned

+ +

Pinned message

+

+ +
+
inputMessagePinned#86872538 = InputMessage;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessageReplyTo.html b/data/core.telegram.org/constructor/inputMessageReplyTo.html new file mode 100644 index 0000000000..e6c8d722f8 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessageReplyTo.html @@ -0,0 +1,147 @@ + + + + + inputMessageReplyTo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageReplyTo

+ +

Message to which the specified message replies to

+

+ +
+
inputMessageReplyTo#bad88395 id:int = InputMessage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idintID of the message that replies to the message we need
+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html b/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html new file mode 100644 index 0000000000..8d8250b104 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterChatPhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterChatPhotos

+ +

Return only chat photo changes

+

+ +
+
inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterContacts.html b/data/core.telegram.org/constructor/inputMessagesFilterContacts.html new file mode 100644 index 0000000000..7ad7f7e001 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterContacts.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterContacts

+ +

Return only messages containing contacts

+

+ +
+
inputMessagesFilterContacts#e062db83 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterDocument.html b/data/core.telegram.org/constructor/inputMessagesFilterDocument.html new file mode 100644 index 0000000000..cce6c52f71 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterDocument.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterDocument

+ +

Filter for messages containing documents.

+

+ +
+
inputMessagesFilterDocument#9eddf188 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html b/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html new file mode 100644 index 0000000000..8859a0230e --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterEmpty

+ +

Filter is absent.

+

+ +
+
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterGif.html b/data/core.telegram.org/constructor/inputMessagesFilterGif.html new file mode 100644 index 0000000000..8013c90838 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterGif.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterGif + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterGif

+ +

Return only messages containing gifs

+

+ +
+
inputMessagesFilterGif#ffc86587 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterMusic.html b/data/core.telegram.org/constructor/inputMessagesFilterMusic.html new file mode 100644 index 0000000000..5ede2afb2b --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterMusic.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterMusic + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterMusic

+ +

Return only messages containing audio files

+

+ +
+
inputMessagesFilterMusic#3751b49e = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html b/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html new file mode 100644 index 0000000000..44315d5366 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html @@ -0,0 +1,135 @@ + + + + + inputMessagesFilterMyMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterMyMentions

+ +

Return only messages where the current user was mentioned.

+

+ +
+
inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html b/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html new file mode 100644 index 0000000000..7e52897222 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html @@ -0,0 +1,152 @@ + + + + + inputMessagesFilterPhoneCalls + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterPhoneCalls

+ +

Return only phone calls

+

+ +
+
inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
missedflags.0?trueReturn only missed phone calls
+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html new file mode 100644 index 0000000000..1f5baef1e7 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterPhotoVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterPhotoVideo

+ +

Filter for messages containing photos or videos.

+

+ +
+
inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html b/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html new file mode 100644 index 0000000000..2ee576bd78 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..04eb79e38f --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterPinned.html @@ -0,0 +1,132 @@ + + + + + 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/inputMessagesFilterRoundVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html new file mode 100644 index 0000000000..1f2ea2876a --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterRoundVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterRoundVideo

+ +

Return only round videos

+

+ +
+
inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html b/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html new file mode 100644 index 0000000000..26c674d727 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterRoundVoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterRoundVoice

+ +

Return only round videos and voice notes

+

+ +
+
inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterUrl.html b/data/core.telegram.org/constructor/inputMessagesFilterUrl.html new file mode 100644 index 0000000000..7df7ab51c8 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterUrl.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterUrl

+ +

Return only messages containing URLs

+

+ +
+
inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterVideo.html new file mode 100644 index 0000000000..2507e24c6d --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterVideo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterVideo

+ +

Filter for messages containing videos.

+

+ +
+
inputMessagesFilterVideo#9fc00e65 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterVoice.html b/data/core.telegram.org/constructor/inputMessagesFilterVoice.html new file mode 100644 index 0000000000..1416315e4d --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterVoice.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterVoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterVoice

+ +

Return only messages containing voice notes

+

+ +
+
inputMessagesFilterVoice#50f5c392 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputNotifyChats.html b/data/core.telegram.org/constructor/inputNotifyChats.html new file mode 100644 index 0000000000..8cd45038b6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputNotifyChats.html @@ -0,0 +1,132 @@ + + + + + inputNotifyChats + + + + + + + + + + + + + +
+ +
+
+
+ +

inputNotifyChats

+ +

Notifications generated by all groups.

+

+ +
+
inputNotifyChats#4a95e84e = InputNotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputNotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputNotifyPeer.html b/data/core.telegram.org/constructor/inputNotifyPeer.html new file mode 100644 index 0000000000..9c0f21ab11 --- /dev/null +++ b/data/core.telegram.org/constructor/inputNotifyPeer.html @@ -0,0 +1,147 @@ + + + + + inputNotifyPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

inputNotifyPeer

+ +

Notifications generated by a certain user or group.

+

+ +
+
inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerUser or group
+

Type

+

InputNotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputNotifyUsers.html b/data/core.telegram.org/constructor/inputNotifyUsers.html new file mode 100644 index 0000000000..05ff385b4b --- /dev/null +++ b/data/core.telegram.org/constructor/inputNotifyUsers.html @@ -0,0 +1,132 @@ + + + + + inputNotifyUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

inputNotifyUsers

+ +

Notifications generated by all users.

+

+ +
+
inputNotifyUsers#193b4417 = InputNotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputNotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPaymentCredentials.html b/data/core.telegram.org/constructor/inputPaymentCredentials.html new file mode 100644 index 0000000000..aaf1b05c15 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPaymentCredentials.html @@ -0,0 +1,157 @@ + + + + + inputPaymentCredentials + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPaymentCredentials

+ +

Payment credentials

+

+ +
+
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
saveflags.0?trueSave payment credential for future use
dataDataJSONPayment credentials
+

Type

+

InputPaymentCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html b/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html new file mode 100644 index 0000000000..6a8dffa157 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html @@ -0,0 +1,147 @@ + + + + + inputPaymentCredentialsApplePay + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPaymentCredentialsApplePay

+ +

Apple pay payment credentials

+

+ +
+
inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
payment_dataDataJSONPayment data
+

Type

+

InputPaymentCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsGooglePay.html b/data/core.telegram.org/constructor/inputPaymentCredentialsGooglePay.html new file mode 100644 index 0000000000..5092d70baa --- /dev/null +++ b/data/core.telegram.org/constructor/inputPaymentCredentialsGooglePay.html @@ -0,0 +1,147 @@ + + + + + inputPaymentCredentialsGooglePay + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPaymentCredentialsGooglePay

+ +

Google Pay payment credentials

+

+ +
+
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
payment_tokenDataJSONPayment token
+

Type

+

InputPaymentCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html b/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html new file mode 100644 index 0000000000..68fabf3079 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html @@ -0,0 +1,152 @@ + + + + + inputPaymentCredentialsSaved + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPaymentCredentialsSaved

+ +

Saved payment credentials

+

+ +
+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringCredential ID
tmp_passwordbytesTemporary password
+

Type

+

InputPaymentCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerChannel.html b/data/core.telegram.org/constructor/inputPeerChannel.html new file mode 100644 index 0000000000..50751f05af --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerChannel.html @@ -0,0 +1,155 @@ + + + + + inputPeerChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerChannel

+ +

Defines a channel for further interaction.

+

+ +
+
inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel identifier
access_hashlongaccess_hash value from the channel constructor
+

Type

+

InputPeer

+

Related pages

+

channel

+

Channel/supergroup info

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerChannelFromMessage.html b/data/core.telegram.org/constructor/inputPeerChannelFromMessage.html new file mode 100644 index 0000000000..1e3520bee6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerChannelFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputPeerChannelFromMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerChannelFromMessage

+ +

Defines a min channel that was seen in a certain message of a certain chat.

+

+ +
+
inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the channel's message was seen
msg_idintThe message ID
channel_idlongThe identifier of the channel that was seen
+

Type

+

InputPeer

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerChat.html b/data/core.telegram.org/constructor/inputPeerChat.html new file mode 100644 index 0000000000..1816841acb --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerChat.html @@ -0,0 +1,147 @@ + + + + + inputPeerChat + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerChat

+ +

Defines a chat for further interaction.

+

+ +
+
inputPeerChat#35a95cb9 chat_id:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat idientifier
+

Type

+

InputPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerEmpty.html b/data/core.telegram.org/constructor/inputPeerEmpty.html new file mode 100644 index 0000000000..befbf1c746 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerEmpty.html @@ -0,0 +1,132 @@ + + + + + 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/inputPeerPhotoFileLocation.html b/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html new file mode 100644 index 0000000000..5b30662baa --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html @@ -0,0 +1,162 @@ + + + + + inputPeerPhotoFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerPhotoFileLocation

+ +

Location of profile photo of channel/group/supergroup/user

+

+ +
+
inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
bigflags.0?trueWhether to download the high-quality version of the picture
peerInputPeerThe peer whose profile picture should be downloaded
photo_idlongPhoto ID
+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerSelf.html b/data/core.telegram.org/constructor/inputPeerSelf.html new file mode 100644 index 0000000000..45a02fe522 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerSelf.html @@ -0,0 +1,132 @@ + + + + + inputPeerSelf + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerSelf

+ +

Defines the current user.

+

+ +
+
inputPeerSelf#7da07ec9 = InputPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerUser.html b/data/core.telegram.org/constructor/inputPeerUser.html new file mode 100644 index 0000000000..acabf3ee89 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerUser.html @@ -0,0 +1,155 @@ + + + + + inputPeerUser + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerUser

+ +

Defines a user for further interaction.

+

+ +
+
inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
access_hashlongaccess_hash value from the user constructor
+

Type

+

InputPeer

+

Related pages

+

user

+

Indicates info about a certain user

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerUserFromMessage.html b/data/core.telegram.org/constructor/inputPeerUserFromMessage.html new file mode 100644 index 0000000000..e0beebbbc9 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerUserFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputPeerUserFromMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerUserFromMessage

+ +

Defines a min user that was seen in a certain message of a certain chat.

+

+ +
+
inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idlongThe identifier of the user that was seen
+

Type

+

InputPeer

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPhoneCall.html b/data/core.telegram.org/constructor/inputPhoneCall.html new file mode 100644 index 0000000000..89bcff0bdb --- /dev/null +++ b/data/core.telegram.org/constructor/inputPhoneCall.html @@ -0,0 +1,152 @@ + + + + + inputPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhoneCall

+ +

Phone call

+

+ +
+
inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongCall ID
access_hashlongAccess hash
+

Type

+

InputPhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPhoneContact.html b/data/core.telegram.org/constructor/inputPhoneContact.html new file mode 100644 index 0000000000..ba51c8bf7d --- /dev/null +++ b/data/core.telegram.org/constructor/inputPhoneContact.html @@ -0,0 +1,166 @@ + + + + + inputPhoneContact + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhoneContact

+ +

Phone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.

+

+ +
+
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
client_idlongUser identifier on the client
phonestringPhone number
first_namestringContact's first name
last_namestringContact's last name
+

Type

+

InputContact

+

Related pages

+

contacts.importContacts

+

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

+

Use contacts.addContact to add Telegram contacts without actually using their phone number.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPhoto.html b/data/core.telegram.org/constructor/inputPhoto.html new file mode 100644 index 0000000000..addf5a5bf6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPhoto.html @@ -0,0 +1,162 @@ + + + + + inputPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhoto

+ +

Defines a photo for further interaction.

+

+ +
+
inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongPhoto identifier
access_hashlongaccess_hash value from the photo constructor
file_referencebytesFile reference
+

Type

+

InputPhoto

+

Related pages

+

photo

+

Photo

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPhotoEmpty.html b/data/core.telegram.org/constructor/inputPhotoEmpty.html new file mode 100644 index 0000000000..79effed578 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + inputPhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhotoEmpty

+ +

Empty constructor.

+

+ +
+
inputPhotoEmpty#1cd7bf0d = InputPhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPhotoFileLocation.html b/data/core.telegram.org/constructor/inputPhotoFileLocation.html new file mode 100644 index 0000000000..625e163c82 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPhotoFileLocation.html @@ -0,0 +1,171 @@ + + + + + inputPhotoFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhotoFileLocation

+ +

Use this object to download a photo with upload.getFile method

+

+ +
+
inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongPhoto ID, obtained from the photo object
access_hashlongPhoto's access hash, obtained from the photo object
file_referencebytesFile reference
thumb_sizestringThe PhotoSize to download: must be set to the type field of the desired PhotoSize object of the photo
+

Type

+

InputFileLocation

+

Related pages

+

photo

+

Photo

+

File references

+

How to handle file references.

+

PhotoSize

+

Location of a certain size of a picture

+

upload.getFile

+

Returns content of a whole file or its part.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html b/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html new file mode 100644 index 0000000000..461753c0e1 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html @@ -0,0 +1,172 @@ + + + + + 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 new file mode 100644 index 0000000000..4a43c77464 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..bf8280fd43 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..26ee4c83a1 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..27039b54a8 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..4c89cb42fb --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..a11b083a1d --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..46c17a25ed --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyProfilePhoto

+ +

Whether people will be able to see the user's profile picture

+

+ +
+
inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html b/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html new file mode 100644 index 0000000000..b5cc1c6b2e --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyStatusTimestamp + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyStatusTimestamp

+ +

Whether we can see the exact last online timestamp of the user

+

+ +
+
inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html new file mode 100644 index 0000000000..85164c819c --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyValueAllowAll + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueAllowAll

+ +

Allow all users

+

+ +
+
inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html new file mode 100644 index 0000000000..9a899eeb73 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueAllowChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueAllowChatParticipants

+ +

Allow only participants of certain chats

+

+ +
+
inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<long>Allowed chat IDs
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html new file mode 100644 index 0000000000..572c06af8d --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueAllowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueAllowUsers

+ +

Allow only certain users

+

+ +
+
inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>Allowed users
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html new file mode 100644 index 0000000000..1bf29d6635 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyValueDisallowAll + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowAll

+ +

Disallow all

+

+ +
+
inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html new file mode 100644 index 0000000000..322a376251 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueDisallowChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowChatParticipants

+ +

Disallow only participants of certain chats

+

+ +
+
inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<long>Disallowed chat IDs
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowContacts.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowContacts.html new file mode 100644 index 0000000000..5028061cb6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueDisallowContacts.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyValueDisallowContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowContacts

+ +

Disallow only contacts

+

+ +
+
inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html new file mode 100644 index 0000000000..57404c0f39 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueDisallowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowUsers

+ +

Disallow only certain users

+

+ +
+
inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>Users to disallow
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html b/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html new file mode 100644 index 0000000000..8529533cbc --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonChildAbuse + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonChildAbuse

+ +

Report for child abuse

+

+ +
+
inputReportReasonChildAbuse#adf44ee3 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonCopyright.html b/data/core.telegram.org/constructor/inputReportReasonCopyright.html new file mode 100644 index 0000000000..2383e4ed2b --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonCopyright.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonCopyright + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonCopyright

+ +

Report for copyrighted content

+

+ +
+
inputReportReasonCopyright#9b89f93a = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonFake.html b/data/core.telegram.org/constructor/inputReportReasonFake.html new file mode 100644 index 0000000000..3ddec4d04a --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonFake.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonFake + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonFake

+ +

Report for impersonation

+

+ +
+
inputReportReasonFake#f5ddd6e7 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonOther.html b/data/core.telegram.org/constructor/inputReportReasonOther.html new file mode 100644 index 0000000000..208a6ae511 --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonOther.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonOther + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonOther

+ +

Other

+

+ +
+
inputReportReasonOther#c1e4a2b1 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonPornography.html b/data/core.telegram.org/constructor/inputReportReasonPornography.html new file mode 100644 index 0000000000..daa10d7d5c --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonPornography.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonPornography + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonPornography

+ +

Report for pornography

+

+ +
+
inputReportReasonPornography#2e59d922 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonSpam.html b/data/core.telegram.org/constructor/inputReportReasonSpam.html new file mode 100644 index 0000000000..73dfed9198 --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonSpam.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonSpam

+ +

Report for spam

+

+ +
+
inputReportReasonSpam#58dbcab8 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonViolence.html b/data/core.telegram.org/constructor/inputReportReasonViolence.html new file mode 100644 index 0000000000..44a933a223 --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonViolence.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonViolence + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonViolence

+ +

Report for violence

+

+ +
+
inputReportReasonViolence#1e22c78d = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputSecureFile.html b/data/core.telegram.org/constructor/inputSecureFile.html new file mode 100644 index 0000000000..aaefa7288d --- /dev/null +++ b/data/core.telegram.org/constructor/inputSecureFile.html @@ -0,0 +1,155 @@ + + + + + inputSecureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureFile

+ +

Preuploaded passport file, for more info see the passport docs »

+

+ +
+
inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongSecure file ID
access_hashlongSecure file access hash
+

Type

+

InputSecureFile

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputSecureFileLocation.html b/data/core.telegram.org/constructor/inputSecureFileLocation.html new file mode 100644 index 0000000000..6c8a7f47e4 --- /dev/null +++ b/data/core.telegram.org/constructor/inputSecureFileLocation.html @@ -0,0 +1,156 @@ + + + + + inputSecureFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureFileLocation

+ +

Location of encrypted telegram passport file.

+

+ +
+
inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongFile ID, id parameter value from secureFile
access_hashlongChecksum, access_hash parameter value from secureFile
+

Type

+

InputFileLocation

+

Related pages

+

secureFile

+

Secure passport file, for more info see the passport docs »

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputSecureFileUploaded.html b/data/core.telegram.org/constructor/inputSecureFileUploaded.html new file mode 100644 index 0000000000..2ecd0ec67a --- /dev/null +++ b/data/core.telegram.org/constructor/inputSecureFileUploaded.html @@ -0,0 +1,169 @@ + + + + + inputSecureFileUploaded + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureFileUploaded

+ +

Uploaded secure file, for more info see the passport docs »

+

+ +
+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongSecure file ID
partsintSecure file part count
md5_checksumstringMD5 hash of encrypted uploaded file, to be checked server-side
file_hashbytesFile hash
secretbytesSecret
+

Type

+

InputSecureFile

+

Related pages

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputSecureValue.html b/data/core.telegram.org/constructor/inputSecureValue.html new file mode 100644 index 0000000000..e2625ec09d --- /dev/null +++ b/data/core.telegram.org/constructor/inputSecureValue.html @@ -0,0 +1,190 @@ + + + + + inputSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureValue

+ +

Secure value, for more info see the passport docs »

+

+ +
+
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
+

Type

+

InputSecureValue

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputSingleMedia.html b/data/core.telegram.org/constructor/inputSingleMedia.html new file mode 100644 index 0000000000..51f91b5804 --- /dev/null +++ b/data/core.telegram.org/constructor/inputSingleMedia.html @@ -0,0 +1,174 @@ + + + + + inputSingleMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSingleMedia

+ +

A single media in an album or grouped media sent with messages.sendMultiMedia.

+

+ +
+
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
mediaInputMediaThe media
random_idlongUnique client media ID required to prevent message resending
messagestringA caption for the media
entitiesflags.0?Vector<MessageEntity>Message entities for styled text
+

Type

+

InputSingleMedia

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

messages.sendMultiMedia

+

Send an album or grouped media

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetAnimatedEmoji.html b/data/core.telegram.org/constructor/inputStickerSetAnimatedEmoji.html new file mode 100644 index 0000000000..ee67a51064 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetAnimatedEmoji.html @@ -0,0 +1,132 @@ + + + + + inputStickerSetAnimatedEmoji + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetAnimatedEmoji

+ +

Animated emojis stickerset

+

+ +
+
inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html b/data/core.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html new file mode 100644 index 0000000000..ac97df05f0 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html @@ -0,0 +1,132 @@ + + + + + inputStickerSetAnimatedEmojiAnimations + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetAnimatedEmojiAnimations

+ +

Animated emoji reaction stickerset (contains animations to play when a user clicks on a given animated emoji)

+

+ +
+
inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetDice.html b/data/core.telegram.org/constructor/inputStickerSetDice.html new file mode 100644 index 0000000000..6f0b7b58ed --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetDice.html @@ -0,0 +1,150 @@ + + + + + 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/inputStickerSetEmpty.html b/data/core.telegram.org/constructor/inputStickerSetEmpty.html new file mode 100644 index 0000000000..dcadb50f38 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetEmpty.html @@ -0,0 +1,132 @@ + + + + + inputStickerSetEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetEmpty

+ +

Empty constructor

+

+ +
+
inputStickerSetEmpty#ffb62b95 = InputStickerSet;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetID.html b/data/core.telegram.org/constructor/inputStickerSetID.html new file mode 100644 index 0000000000..021e80cfb8 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetID.html @@ -0,0 +1,152 @@ + + + + + inputStickerSetID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetID

+ +

Stickerset by ID

+

+ +
+
inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetItem.html b/data/core.telegram.org/constructor/inputStickerSetItem.html new file mode 100644 index 0000000000..1cc21a714b --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetItem.html @@ -0,0 +1,162 @@ + + + + + inputStickerSetItem + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetItem

+ +

Sticker in a stickerset

+

+ +
+
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
documentInputDocumentThe sticker
emojistringAssociated emoji
mask_coordsflags.0?MaskCoordsCoordinates for mask sticker
+

Type

+

InputStickerSetItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetShortName.html b/data/core.telegram.org/constructor/inputStickerSetShortName.html new file mode 100644 index 0000000000..f4a7361f55 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetShortName.html @@ -0,0 +1,147 @@ + + + + + inputStickerSetShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetShortName

+ +

Stickerset by short name, from tg://addstickers?set=short_name

+

+ +
+
inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
short_namestringFrom tg://addstickers?set=short_name
+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetThumb.html b/data/core.telegram.org/constructor/inputStickerSetThumb.html new file mode 100644 index 0000000000..47c63b6c53 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetThumb.html @@ -0,0 +1,155 @@ + + + + + inputStickerSetThumb + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetThumb

+ +

Location of stickerset thumbnail (see files)

+

+ +
+
inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetSticker set
thumb_versionintThumbnail version
+

Type

+

InputFileLocation

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickeredMediaDocument.html b/data/core.telegram.org/constructor/inputStickeredMediaDocument.html new file mode 100644 index 0000000000..186dc647b3 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickeredMediaDocument.html @@ -0,0 +1,147 @@ + + + + + inputStickeredMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickeredMediaDocument

+ +

A document with stickers attached

+

+ +
+
inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputDocumentThe document
+

Type

+

InputStickeredMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html b/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html new file mode 100644 index 0000000000..85e684cd61 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html @@ -0,0 +1,147 @@ + + + + + inputStickeredMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickeredMediaPhoto

+ +

A photo with stickers attached

+

+ +
+
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPhotoThe photo
+

Type

+

InputStickeredMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputTakeoutFileLocation.html b/data/core.telegram.org/constructor/inputTakeoutFileLocation.html new file mode 100644 index 0000000000..d5b309c2e7 --- /dev/null +++ b/data/core.telegram.org/constructor/inputTakeoutFileLocation.html @@ -0,0 +1,132 @@ + + + + + inputTakeoutFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputTakeoutFileLocation

+ +

Empty constructor for takeout

+

+ +
+
inputTakeoutFileLocation#29be5899 = InputFileLocation;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputTheme.html b/data/core.telegram.org/constructor/inputTheme.html new file mode 100644 index 0000000000..2b385c80c6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputTheme.html @@ -0,0 +1,152 @@ + + + + + inputTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

inputTheme

+ +

Theme

+

+ +
+
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
+

Type

+

InputTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputThemeSettings.html b/data/core.telegram.org/constructor/inputThemeSettings.html new file mode 100644 index 0000000000..afd0437507 --- /dev/null +++ b/data/core.telegram.org/constructor/inputThemeSettings.html @@ -0,0 +1,182 @@ + + + + + inputThemeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

inputThemeSettings

+ +

Theme settings

+

+ +
+
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
message_colors_animatedflags.2?trueIf set, the freeform gradient fill needs to be animated on every sent message
base_themeBaseThemeDefault theme on which this theme is based
accent_colorintAccent color, ARGB format
outbox_accent_colorflags.3?intAccent color of outgoing messages in ARGB format
message_colorsflags.0?Vector<int>The fill to be used as a background for outgoing messages, in RGB24 format.
If just one or two equal colors are provided, describes a solid fill of a background.
If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
If three or four colors are provided, describes a freeform gradient fill of a background.
wallpaperflags.1?InputWallPaperWallpaper
wallpaper_settingsflags.1?WallPaperSettingsWallpaper settings
+

Type

+

InputThemeSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputThemeSlug.html b/data/core.telegram.org/constructor/inputThemeSlug.html new file mode 100644 index 0000000000..13acc9f9c7 --- /dev/null +++ b/data/core.telegram.org/constructor/inputThemeSlug.html @@ -0,0 +1,147 @@ + + + + + inputThemeSlug + + + + + + + + + + + + + +
+ +
+
+
+ +

inputThemeSlug

+ +

Theme by theme ID

+

+ +
+
inputThemeSlug#f5890df1 slug:string = InputTheme;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
slugstringUnique theme ID
+

Type

+

InputTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputUser.html b/data/core.telegram.org/constructor/inputUser.html new file mode 100644 index 0000000000..19c4056092 --- /dev/null +++ b/data/core.telegram.org/constructor/inputUser.html @@ -0,0 +1,155 @@ + + + + + inputUser + + + + + + + + + + + + + +
+ +
+
+
+ +

inputUser

+ +

Defines a user for further interaction.

+

+ +
+
inputUser#f21158c6 user_id:long access_hash:long = InputUser;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
access_hashlongaccess_hash value from the user constructor
+

Type

+

InputUser

+

Related pages

+

user

+

Indicates info about a certain user

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputUserEmpty.html b/data/core.telegram.org/constructor/inputUserEmpty.html new file mode 100644 index 0000000000..44b8adcaf6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputUserEmpty.html @@ -0,0 +1,132 @@ + + + + + inputUserEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputUserEmpty

+ +

Empty constructor, does not define a user.

+

+ +
+
inputUserEmpty#b98886cf = InputUser;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputUser

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputUserFromMessage.html b/data/core.telegram.org/constructor/inputUserFromMessage.html new file mode 100644 index 0000000000..4eec2ed10d --- /dev/null +++ b/data/core.telegram.org/constructor/inputUserFromMessage.html @@ -0,0 +1,160 @@ + + + + + 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 new file mode 100644 index 0000000000..21d44f392d --- /dev/null +++ b/data/core.telegram.org/constructor/inputUserSelf.html @@ -0,0 +1,132 @@ + + + + + inputUserSelf + + + + + + + + + + + + + +
+ +
+
+
+ +

inputUserSelf

+ +

Defines the current user.

+

+ +
+
inputUserSelf#f7c1b13f = InputUser;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputUser

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputWallPaper.html b/data/core.telegram.org/constructor/inputWallPaper.html new file mode 100644 index 0000000000..4432bf6581 --- /dev/null +++ b/data/core.telegram.org/constructor/inputWallPaper.html @@ -0,0 +1,152 @@ + + + + + inputWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWallPaper

+ +

Wallpaper

+

+ +
+
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongWallpaper ID
access_hashlongAccess hash
+

Type

+

InputWallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputWallPaperNoFile.html b/data/core.telegram.org/constructor/inputWallPaperNoFile.html new file mode 100644 index 0000000000..8a56c3a709 --- /dev/null +++ b/data/core.telegram.org/constructor/inputWallPaperNoFile.html @@ -0,0 +1,150 @@ + + + + + inputWallPaperNoFile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWallPaperNoFile

+ +

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.

+

+ +
+
inputWallPaperNoFile#967a462e id:long = InputWallPaper;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongWallpaper ID
+

Type

+

InputWallPaper

+

Related pages

+

account.saveWallPaper

+

Install/uninstall wallpaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputWallPaperSlug.html b/data/core.telegram.org/constructor/inputWallPaperSlug.html new file mode 100644 index 0000000000..6ca41fab1c --- /dev/null +++ b/data/core.telegram.org/constructor/inputWallPaperSlug.html @@ -0,0 +1,147 @@ + + + + + inputWallPaperSlug + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWallPaperSlug

+ +

Wallpaper by slug (a unique ID)

+

+ +
+
inputWallPaperSlug#72091c80 slug:string = InputWallPaper;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
slugstringUnique wallpaper ID
+

Type

+

InputWallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputWebDocument.html b/data/core.telegram.org/constructor/inputWebDocument.html new file mode 100644 index 0000000000..4cd5d55682 --- /dev/null +++ b/data/core.telegram.org/constructor/inputWebDocument.html @@ -0,0 +1,165 @@ + + + + + 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 new file mode 100644 index 0000000000..e7f9359db6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html @@ -0,0 +1,172 @@ + + + + + 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/invoice.html b/data/core.telegram.org/constructor/invoice.html new file mode 100644 index 0000000000..8e10e9d9c2 --- /dev/null +++ b/data/core.telegram.org/constructor/invoice.html @@ -0,0 +1,209 @@ + + + + + invoice + + + + + + + + + + + + + +
+ +
+
+
+ +

invoice

+ +

Invoice

+

+ +
+
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
testflags.0?trueTest invoice
name_requestedflags.1?trueSet this flag if you require the user's full name to complete the order
phone_requestedflags.2?trueSet this flag if you require the user's phone number to complete the order
email_requestedflags.3?trueSet this flag if you require the user's email address to complete the order
shipping_address_requestedflags.4?trueSet this flag if you require the user's shipping address to complete the order
flexibleflags.5?trueSet this flag if the final price depends on the shipping method
phone_to_providerflags.6?trueSet this flag if user's phone number should be sent to provider
email_to_providerflags.7?trueSet this flag if user's email address should be sent to provider
currencystringThree-letter ISO 4217 currency code
pricesVector<LabeledPrice>Price breakdown, a list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountflags.8?longThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
suggested_tip_amountsflags.8?Vector<long>A vector of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
+

Type

+

Invoice

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonArray.html b/data/core.telegram.org/constructor/jsonArray.html new file mode 100644 index 0000000000..70f79d96eb --- /dev/null +++ b/data/core.telegram.org/constructor/jsonArray.html @@ -0,0 +1,147 @@ + + + + + jsonArray + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonArray

+ +

JSON array

+

+ +
+
jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valueVector<JSONValue>JSON values
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonBool.html b/data/core.telegram.org/constructor/jsonBool.html new file mode 100644 index 0000000000..7d834c2670 --- /dev/null +++ b/data/core.telegram.org/constructor/jsonBool.html @@ -0,0 +1,147 @@ + + + + + jsonBool + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonBool

+ +

JSON boolean value

+

+ +
+
jsonBool#c7345e6a value:Bool = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valueBoolValue
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonNull.html b/data/core.telegram.org/constructor/jsonNull.html new file mode 100644 index 0000000000..89d234ae35 --- /dev/null +++ b/data/core.telegram.org/constructor/jsonNull.html @@ -0,0 +1,132 @@ + + + + + jsonNull + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonNull

+ +

null JSON value

+

+ +
+
jsonNull#3f6d7b68 = JSONValue;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonNumber.html b/data/core.telegram.org/constructor/jsonNumber.html new file mode 100644 index 0000000000..eb7f4e3815 --- /dev/null +++ b/data/core.telegram.org/constructor/jsonNumber.html @@ -0,0 +1,147 @@ + + + + + jsonNumber + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonNumber

+ +

JSON numeric value

+

+ +
+
jsonNumber#2be0dfa4 value:double = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valuedoubleValue
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonObject.html b/data/core.telegram.org/constructor/jsonObject.html new file mode 100644 index 0000000000..a8fb071e23 --- /dev/null +++ b/data/core.telegram.org/constructor/jsonObject.html @@ -0,0 +1,147 @@ + + + + + jsonObject + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonObject

+ +

JSON object value

+

+ +
+
jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valueVector<JSONObjectValue>Values
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonObjectValue.html b/data/core.telegram.org/constructor/jsonObjectValue.html new file mode 100644 index 0000000000..a25a310f02 --- /dev/null +++ b/data/core.telegram.org/constructor/jsonObjectValue.html @@ -0,0 +1,152 @@ + + + + + jsonObjectValue + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonObjectValue

+ +

JSON key: value pair

+

+ +
+
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keystringKey
valueJSONValueValue
+

Type

+

JSONObjectValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonString.html b/data/core.telegram.org/constructor/jsonString.html new file mode 100644 index 0000000000..7bef87ac42 --- /dev/null +++ b/data/core.telegram.org/constructor/jsonString.html @@ -0,0 +1,147 @@ + + + + + jsonString + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonString

+ +

JSON string

+

+ +
+
jsonString#b71e767a value:string = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valuestringValue
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButton.html b/data/core.telegram.org/constructor/keyboardButton.html new file mode 100644 index 0000000000..f4601525ca --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButton.html @@ -0,0 +1,147 @@ + + + + + keyboardButton + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButton

+ +

Bot keyboard button

+

+ +
+
keyboardButton#a2fa4880 text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonBuy.html b/data/core.telegram.org/constructor/keyboardButtonBuy.html new file mode 100644 index 0000000000..223cf96d05 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonBuy.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonBuy + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonBuy

+ +

Button to buy a product

+

+ +
+
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonCallback.html b/data/core.telegram.org/constructor/keyboardButtonCallback.html new file mode 100644 index 0000000000..5b5263399f --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonCallback.html @@ -0,0 +1,167 @@ + + + + + keyboardButtonCallback + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonCallback

+ +

Callback button

+

+ +
+
keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
requires_passwordflags.0?trueWhether the user should verify his identity by entering his 2FA SRP parameters to the messages.getBotCallbackAnswer method. NOTE: telegram and the bot WILL NOT have access to the plaintext password, thanks to SRP. This button is mainly used by the official @botfather bot, for verifying the user's identity before transferring ownership of a bot to another user.
textstringButton text
databytesCallback data
+

Type

+

KeyboardButton

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

messages.getBotCallbackAnswer

+

Press an inline callback button and get a callback answer from the bot

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonGame.html b/data/core.telegram.org/constructor/keyboardButtonGame.html new file mode 100644 index 0000000000..f12baa8348 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonGame.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonGame + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonGame

+ +

Button to start a game

+

+ +
+
keyboardButtonGame#50f41ccf text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html b/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html new file mode 100644 index 0000000000..b9d0c6f693 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonRequestGeoLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRequestGeoLocation

+ +

Button to request a user's geolocation

+

+ +
+
keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html b/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html new file mode 100644 index 0000000000..2d93039361 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonRequestPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRequestPhone

+ +

Button to request a user's phone number

+

+ +
+
keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html b/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html new file mode 100644 index 0000000000..98cf901d7b --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html @@ -0,0 +1,157 @@ + + + + + keyboardButtonRequestPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRequestPoll

+ +

A button that allows the user to create and send a poll when pressed; available only in private

+

+ +
+
keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
quizflags.0?BoolIf set, only quiz polls can be sent
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonRow.html b/data/core.telegram.org/constructor/keyboardButtonRow.html new file mode 100644 index 0000000000..96aacbfdf3 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonRow.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonRow + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRow

+ +

Inline keyboard row

+

+ +
+
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
buttonsVector<KeyboardButton>Bot or inline keyboard buttons
+

Type

+

KeyboardButtonRow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html b/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html new file mode 100644 index 0000000000..106c395e5a --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html @@ -0,0 +1,162 @@ + + + + + keyboardButtonSwitchInline + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonSwitchInline

+ +

Button to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.

+

+ +
+
keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
same_peerflags.0?trueIf set, pressing the button will insert the bot‘s username and the specified inline query in the current chat's input field.
textstringButton label
querystringThe inline query to use
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonUrl.html b/data/core.telegram.org/constructor/keyboardButtonUrl.html new file mode 100644 index 0000000000..9defc29723 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonUrl.html @@ -0,0 +1,152 @@ + + + + + keyboardButtonUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonUrl

+ +

URL button

+

+ +
+
keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton label
urlstringURL
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html b/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html new file mode 100644 index 0000000000..c5f12d448b --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html @@ -0,0 +1,179 @@ + + + + + keyboardButtonUrlAuth + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonUrlAuth

+ +

Button to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.

+

+ +
+
keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
textstringButton label
fwd_textflags.0?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: Services must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
button_idintID of the button to pass to messages.requestUrlAuth
+

Type

+

KeyboardButton

+

Related pages

+

Telegram Login Widget

+

messages.requestUrlAuth

+

Get more info about a Seamless Telegram Login authorization request, for more info click here »

+

urlAuthResultRequest

+

Details about the authorization request, for more info click here »

+

messages.acceptUrlAuth

+

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

+

urlAuthResultAccepted

+

Details about an accepted authorization request, for more info click here »

+

urlAuthResultDefault

+

Details about an accepted authorization request, for more info click here »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/labeledPrice.html b/data/core.telegram.org/constructor/labeledPrice.html new file mode 100644 index 0000000000..336c0b3c2d --- /dev/null +++ b/data/core.telegram.org/constructor/labeledPrice.html @@ -0,0 +1,154 @@ + + + + + labeledPrice + + + + + + + + + + + + + +
+ +
+
+
+ +

labeledPrice

+ +

This object represents a portion of the price for goods or services.

+

+ +
+
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
labelstringPortion label
amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Type

+

LabeledPrice

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/langPackDifference.html b/data/core.telegram.org/constructor/langPackDifference.html new file mode 100644 index 0000000000..5b6120a163 --- /dev/null +++ b/data/core.telegram.org/constructor/langPackDifference.html @@ -0,0 +1,162 @@ + + + + + langPackDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackDifference

+ +

Changes to the app's localization pack

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious version number
versionintNew version number
stringsVector<LangPackString>Localized strings
+

Type

+

LangPackDifference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/langPackLanguage.html b/data/core.telegram.org/constructor/langPackLanguage.html new file mode 100644 index 0000000000..9d4795691a --- /dev/null +++ b/data/core.telegram.org/constructor/langPackLanguage.html @@ -0,0 +1,202 @@ + + + + + langPackLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackLanguage

+ +

Identifies a localization pack

+

+ +
+
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
officialflags.0?trueWhether the language pack is official
rtlflags.2?trueIs this a localization pack for an RTL language
betaflags.3?trueIs this a beta localization pack?
namestringLanguage name
native_namestringLanguage name in the language itself
lang_codestringLanguage code (pack identifier)
base_lang_codeflags.1?stringIdentifier of a base language pack; may be empty. If a string is missed in the language pack, then it should be fetched from base language pack. Unsupported in custom language packs
plural_codestringA language code to be used to apply plural forms. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
strings_countintTotal number of non-deleted strings from the language pack
translated_countintTotal number of translated strings from the language pack
translations_urlstringLink to language translation interface; empty for custom local language packs
+

Type

+

LangPackLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/langPackStringDeleted.html b/data/core.telegram.org/constructor/langPackStringDeleted.html new file mode 100644 index 0000000000..028ad5eae0 --- /dev/null +++ b/data/core.telegram.org/constructor/langPackStringDeleted.html @@ -0,0 +1,147 @@ + + + + + langPackStringDeleted + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackStringDeleted

+ +

Deleted localization string

+

+ +
+
langPackStringDeleted#2979eeb2 key:string = LangPackString;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
keystringLocalization key
+

Type

+

LangPackString

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/langPackStringPluralized.html b/data/core.telegram.org/constructor/langPackStringPluralized.html new file mode 100644 index 0000000000..6012cb2751 --- /dev/null +++ b/data/core.telegram.org/constructor/langPackStringPluralized.html @@ -0,0 +1,182 @@ + + + + + langPackStringPluralized + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackStringPluralized

+ +

A language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info

+

+ +
+
langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
keystringLocalization key
zero_valueflags.0?stringValue for zero objects
one_valueflags.1?stringValue for one object
two_valueflags.2?stringValue for two objects
few_valueflags.3?stringValue for a few objects
many_valueflags.4?stringValue for many objects
other_valuestringDefault value
+

Type

+

LangPackString

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/maskCoords.html b/data/core.telegram.org/constructor/maskCoords.html new file mode 100644 index 0000000000..e81910719a --- /dev/null +++ b/data/core.telegram.org/constructor/maskCoords.html @@ -0,0 +1,169 @@ + + + + + maskCoords + + + + + + + + + + + + + +
+ +
+
+
+ +

maskCoords

+ +

Position on a photo where a mask should be placed

+

The n position indicates where the mask should be placed:

+
    +
  • 0 => Relative to the forehead
  • +
  • 1 => Relative to the eyes
  • +
  • 2 => Relative to the mouth
  • +
  • 3 => Relative to the chin
  • +
+

+ +
+
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
nintPart of the face, relative to which the mask should be placed
xdoubleShift by X-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
ydoubleShift by Y-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
zoomdoubleMask scaling coefficient. (For example, 2.0 means a doubled size)
+

Type

+

MaskCoords

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/message.html b/data/core.telegram.org/constructor/message.html new file mode 100644 index 0000000000..16de546363 --- /dev/null +++ b/data/core.telegram.org/constructor/message.html @@ -0,0 +1,302 @@ + + + + + message + + + + + + + + + + + + + +
+ +
+
+
+ +

message

+ +

A message

+

+ +
+
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueIs this an outgoing message
mentionedflags.4?trueWhether we were mentioned in this message
media_unreadflags.5?trueWhether there are unread media attachments in this message
silentflags.13?trueWhether this is a silent message (no notification triggered)
postflags.14?trueWhether this is a channel post
from_scheduledflags.18?trueWhether this is a scheduled message
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
edit_hideflags.21?trueWhether the message should be shown as not modified to the user, even if an edit date is present
pinnedflags.24?trueWhether this message is pinned
idintID of the message
from_idflags.8?PeerID of the sender of the message
peer_idPeerPeer ID, the chat where this message was sent
fwd_fromflags.2?MessageFwdHeaderInfo about forwarded messages
via_bot_idflags.11?longID of the inline bot that generated the message
reply_toflags.3?MessageReplyHeaderReply information
dateintDate of the message
messagestringThe message
mediaflags.9?MessageMediaMedia attachment
reply_markupflags.6?ReplyMarkupReply markup (bot/inline keyboards)
entitiesflags.7?Vector<MessageEntity>Message entities for styled text
viewsflags.10?intView count for channel posts
forwardsflags.10?intForward counter
repliesflags.23?MessageRepliesInfo about post comments (for channels) or message replies (for groups)
edit_dateflags.15?intLast edit date of this message
post_authorflags.16?stringName of the author of this message for channel posts (with signatures enabled)
grouped_idflags.17?longMultiple media messages sent using messages.sendMultiMedia with the same grouped ID indicate an album or media group
restriction_reasonflags.22?Vector<RestrictionReason>Contains the reason why access to this message must be restricted.
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Message

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

Scheduled messages

+

Telegram allows scheduling messages

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Styled text with message entities

+

How to create styled text with message entities

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

messages.sendMultiMedia

+

Send an album or grouped media

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionBotAllowed.html b/data/core.telegram.org/constructor/messageActionBotAllowed.html new file mode 100644 index 0000000000..fa06938c18 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionBotAllowed.html @@ -0,0 +1,149 @@ + + + + + messageActionBotAllowed + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionBotAllowed

+ +

The domain name of the website on which the user has logged in. More about Telegram Login »

+

+ +
+
messageActionBotAllowed#abe9affe domain:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
domainstringThe domain name of the website on which the user has logged in.
+

Type

+

MessageAction

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChannelCreate.html b/data/core.telegram.org/constructor/messageActionChannelCreate.html new file mode 100644 index 0000000000..027debd35c --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChannelCreate.html @@ -0,0 +1,147 @@ + + + + + messageActionChannelCreate + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChannelCreate

+ +

The channel was created

+

+ +
+
messageActionChannelCreate#95d2ac92 title:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
titlestringOriginal channel/supergroup title
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html b/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html new file mode 100644 index 0000000000..d636a24ab6 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html @@ -0,0 +1,155 @@ + + + + + messageActionChannelMigrateFrom + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChannelMigrateFrom

+ +

Indicates the channel was migrated from the specified chat

+

+ +
+
messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
titlestringThe old chat tite
chat_idlongThe old chat ID
+

Type

+

MessageAction

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatAddUser.html b/data/core.telegram.org/constructor/messageActionChatAddUser.html new file mode 100644 index 0000000000..659e185341 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatAddUser.html @@ -0,0 +1,147 @@ + + + + + messageActionChatAddUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatAddUser

+ +

New member in the group

+

+ +
+
messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<long>Users that were invited to the chat
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatCreate.html b/data/core.telegram.org/constructor/messageActionChatCreate.html new file mode 100644 index 0000000000..c4c19cf60d --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatCreate.html @@ -0,0 +1,152 @@ + + + + + messageActionChatCreate + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatCreate

+ +

Group created

+

+ +
+
messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
titlestringGroup name
usersVector<long>List of group members
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatDeletePhoto.html b/data/core.telegram.org/constructor/messageActionChatDeletePhoto.html new file mode 100644 index 0000000000..847af5b07c --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatDeletePhoto.html @@ -0,0 +1,132 @@ + + + + + messageActionChatDeletePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatDeletePhoto

+ +

Group profile photo removed.

+

+ +
+
messageActionChatDeletePhoto#95e3fbef = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatDeleteUser.html b/data/core.telegram.org/constructor/messageActionChatDeleteUser.html new file mode 100644 index 0000000000..7ea47c2b29 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatDeleteUser.html @@ -0,0 +1,147 @@ + + + + + messageActionChatDeleteUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatDeleteUser

+ +

User left the group.

+

+ +
+
messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongLeaving user ID
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatEditPhoto.html b/data/core.telegram.org/constructor/messageActionChatEditPhoto.html new file mode 100644 index 0000000000..43c505f3d8 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatEditPhoto.html @@ -0,0 +1,147 @@ + + + + + messageActionChatEditPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatEditPhoto

+ +

Group profile changed

+

+ +
+
messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
photoPhotoNew group pofile photo
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatEditTitle.html b/data/core.telegram.org/constructor/messageActionChatEditTitle.html new file mode 100644 index 0000000000..5dd19c081d --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatEditTitle.html @@ -0,0 +1,147 @@ + + + + + messageActionChatEditTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatEditTitle

+ +

Group name changed.

+

+ +
+
messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
titlestringNew group name
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html b/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html new file mode 100644 index 0000000000..a5365fcde3 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html @@ -0,0 +1,147 @@ + + + + + messageActionChatJoinedByLink + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatJoinedByLink

+ +

A user joined the chat via an invite link

+

+ +
+
messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
inviter_idlongID of the user that created the invite link
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatMigrateTo.html b/data/core.telegram.org/constructor/messageActionChatMigrateTo.html new file mode 100644 index 0000000000..323bec7d1a --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatMigrateTo.html @@ -0,0 +1,150 @@ + + + + + messageActionChatMigrateTo + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatMigrateTo

+ +

Indicates the chat was migrated to the specified supergroup

+

+ +
+
messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongThe supergroup it was migrated to
+

Type

+

MessageAction

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionContactSignUp.html b/data/core.telegram.org/constructor/messageActionContactSignUp.html new file mode 100644 index 0000000000..0086008c26 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionContactSignUp.html @@ -0,0 +1,132 @@ + + + + + messageActionContactSignUp + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionContactSignUp

+ +

A contact just signed up to telegram

+

+ +
+
messageActionContactSignUp#f3f25f76 = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionCustomAction.html b/data/core.telegram.org/constructor/messageActionCustomAction.html new file mode 100644 index 0000000000..0035330426 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionCustomAction.html @@ -0,0 +1,147 @@ + + + + + messageActionCustomAction + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionCustomAction

+ +

Custom action (most likely not supported by the current layer, an upgrade might be needed)

+

+ +
+
messageActionCustomAction#fae69f56 message:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messagestringAction message
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionEmpty.html b/data/core.telegram.org/constructor/messageActionEmpty.html new file mode 100644 index 0000000000..a886e79552 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionEmpty.html @@ -0,0 +1,132 @@ + + + + + messageActionEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionEmpty

+ +

Empty constructor.

+

+ +
+
messageActionEmpty#b6aef7b0 = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionGameScore.html b/data/core.telegram.org/constructor/messageActionGameScore.html new file mode 100644 index 0000000000..1a4ae26249 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionGameScore.html @@ -0,0 +1,152 @@ + + + + + messageActionGameScore + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionGameScore

+ +

Someone scored in a game

+

+ +
+
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
game_idlongGame ID
scoreintScore
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionGeoProximityReached.html b/data/core.telegram.org/constructor/messageActionGeoProximityReached.html new file mode 100644 index 0000000000..5452d3a384 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionGeoProximityReached.html @@ -0,0 +1,160 @@ + + + + + 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 new file mode 100644 index 0000000000..793f748714 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionGroupCall.html @@ -0,0 +1,157 @@ + + + + + messageActionGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionGroupCall

+ +

The group call has ended

+

+ +
+
messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallGroup call
durationflags.0?intGroup call duration
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionGroupCallScheduled.html b/data/core.telegram.org/constructor/messageActionGroupCallScheduled.html new file mode 100644 index 0000000000..a089ad27f7 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionGroupCallScheduled.html @@ -0,0 +1,152 @@ + + + + + messageActionGroupCallScheduled + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionGroupCallScheduled

+ +

A group call was scheduled

+

+ +
+
messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
schedule_dateintWhen is this group call scheduled to start
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionHistoryClear.html b/data/core.telegram.org/constructor/messageActionHistoryClear.html new file mode 100644 index 0000000000..5244cb2c65 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionHistoryClear.html @@ -0,0 +1,132 @@ + + + + + messageActionHistoryClear + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionHistoryClear

+ +

Chat history was cleared

+

+ +
+
messageActionHistoryClear#9fbab604 = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionInviteToGroupCall.html b/data/core.telegram.org/constructor/messageActionInviteToGroupCall.html new file mode 100644 index 0000000000..84c058c54f --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionInviteToGroupCall.html @@ -0,0 +1,152 @@ + + + + + messageActionInviteToGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionInviteToGroupCall

+ +

A set of users was invited to the group call

+

+ +
+
messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
usersVector<long>The invited users
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionPaymentSent.html b/data/core.telegram.org/constructor/messageActionPaymentSent.html new file mode 100644 index 0000000000..2fb384462f --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionPaymentSent.html @@ -0,0 +1,154 @@ + + + + + messageActionPaymentSent + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionPaymentSent

+ +

A payment was sent

+

+ +
+
messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Type

+

MessageAction

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionPaymentSentMe.html b/data/core.telegram.org/constructor/messageActionPaymentSentMe.html new file mode 100644 index 0000000000..ad0a6554e0 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionPaymentSentMe.html @@ -0,0 +1,179 @@ + + + + + messageActionPaymentSentMe + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionPaymentSentMe

+ +

A user just sent a payment to me (a bot)

+

+ +
+
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
chargePaymentChargeProvider payment identifier
+

Type

+

MessageAction

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionPhoneCall.html b/data/core.telegram.org/constructor/messageActionPhoneCall.html new file mode 100644 index 0000000000..a810e4e061 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionPhoneCall.html @@ -0,0 +1,167 @@ + + + + + messageActionPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionPhoneCall

+ +

A phone call

+

+ +
+
messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.2?trueIs this a video call?
call_idlongCall ID
reasonflags.0?PhoneCallDiscardReasonIf the call has ended, the reason why it ended
durationflags.1?intDuration of the call in seconds
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionPinMessage.html b/data/core.telegram.org/constructor/messageActionPinMessage.html new file mode 100644 index 0000000000..ad5c92c963 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionPinMessage.html @@ -0,0 +1,132 @@ + + + + + messageActionPinMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionPinMessage

+ +

A message was pinned

+

+ +
+
messageActionPinMessage#94bd38ed = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionScreenshotTaken.html b/data/core.telegram.org/constructor/messageActionScreenshotTaken.html new file mode 100644 index 0000000000..39b5d092e0 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionScreenshotTaken.html @@ -0,0 +1,132 @@ + + + + + messageActionScreenshotTaken + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionScreenshotTaken

+ +

A screenshot of the chat was taken

+

+ +
+
messageActionScreenshotTaken#4792929b = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionSecureValuesSent.html b/data/core.telegram.org/constructor/messageActionSecureValuesSent.html new file mode 100644 index 0000000000..8720707f39 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionSecureValuesSent.html @@ -0,0 +1,149 @@ + + + + + messageActionSecureValuesSent + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSecureValuesSent

+ +

Request for secure telegram passport values was sent

+

+ +
+
messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typesVector<SecureValueType>Secure value types
+

Type

+

MessageAction

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html b/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html new file mode 100644 index 0000000000..e243bdbd9e --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html @@ -0,0 +1,154 @@ + + + + + messageActionSecureValuesSentMe + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSecureValuesSentMe

+ +

Secure telegram passport values were received

+

+ +
+
messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
valuesVector<SecureValue>Vector with information about documents and other Telegram Passport elements that were shared with the bot
credentialsSecureCredentialsEncryptedEncrypted credentials required to decrypt the data
+

Type

+

MessageAction

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionSetChatTheme.html b/data/core.telegram.org/constructor/messageActionSetChatTheme.html new file mode 100644 index 0000000000..6dcc4af289 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionSetChatTheme.html @@ -0,0 +1,147 @@ + + + + + messageActionSetChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSetChatTheme

+ +

The chat theme was changed

+

+ +
+
messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringThe emoji that identifies a chat theme
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionSetMessagesTTL.html b/data/core.telegram.org/constructor/messageActionSetMessagesTTL.html new file mode 100644 index 0000000000..c3331eea07 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionSetMessagesTTL.html @@ -0,0 +1,147 @@ + + + + + messageActionSetMessagesTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSetMessagesTTL

+ +

The Time-To-Live of messages in this chat was changed.

+

+ +
+
messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
periodintNew Time-To-Live
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEmpty.html b/data/core.telegram.org/constructor/messageEmpty.html new file mode 100644 index 0000000000..9785a0e652 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEmpty.html @@ -0,0 +1,157 @@ + + + + + messageEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEmpty

+ +

Empty constructor, non-existent message.

+

+ +
+
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintMessage identifier
peer_idflags.0?PeerPeer ID, the chat where this message was sent
+

Type

+

Message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityBankCard.html b/data/core.telegram.org/constructor/messageEntityBankCard.html new file mode 100644 index 0000000000..d1dc75a1f5 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityBankCard.html @@ -0,0 +1,152 @@ + + + + + messageEntityBankCard + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBankCard

+ +

Indicates a credit card number

+

+ +
+
messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityBlockquote.html b/data/core.telegram.org/constructor/messageEntityBlockquote.html new file mode 100644 index 0000000000..818551c8ff --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityBlockquote.html @@ -0,0 +1,152 @@ + + + + + messageEntityBlockquote + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBlockquote

+ +

Message entity representing a block quote.

+

+ +
+
messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityBold.html b/data/core.telegram.org/constructor/messageEntityBold.html new file mode 100644 index 0000000000..e140938aa8 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityBold.html @@ -0,0 +1,152 @@ + + + + + messageEntityBold + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBold

+ +

Message entity representing bold text.

+

+ +
+
messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityBotCommand.html b/data/core.telegram.org/constructor/messageEntityBotCommand.html new file mode 100644 index 0000000000..594b2c97b6 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityBotCommand.html @@ -0,0 +1,152 @@ + + + + + messageEntityBotCommand + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBotCommand

+ +

Message entity representing a bot /command

+

+ +
+
messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityCashtag.html b/data/core.telegram.org/constructor/messageEntityCashtag.html new file mode 100644 index 0000000000..723fe1a2a9 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityCashtag.html @@ -0,0 +1,152 @@ + + + + + messageEntityCashtag + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityCashtag

+ +

Message entity representing a $cashtag.

+

+ +
+
messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityCode.html b/data/core.telegram.org/constructor/messageEntityCode.html new file mode 100644 index 0000000000..dbb8132c6d --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityCode.html @@ -0,0 +1,152 @@ + + + + + messageEntityCode + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityCode

+ +

Message entity representing a codeblock.

+

+ +
+
messageEntityCode#28a20571 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityEmail.html b/data/core.telegram.org/constructor/messageEntityEmail.html new file mode 100644 index 0000000000..99324ce92b --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityEmail.html @@ -0,0 +1,152 @@ + + + + + messageEntityEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityEmail

+ +

Message entity representing an email@example.com.

+

+ +
+
messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityHashtag.html b/data/core.telegram.org/constructor/messageEntityHashtag.html new file mode 100644 index 0000000000..f216b8463a --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityHashtag.html @@ -0,0 +1,152 @@ + + + + + messageEntityHashtag + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityHashtag

+ +

#hashtag message entity

+

+ +
+
messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityItalic.html b/data/core.telegram.org/constructor/messageEntityItalic.html new file mode 100644 index 0000000000..598c5f0a32 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityItalic.html @@ -0,0 +1,152 @@ + + + + + messageEntityItalic + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityItalic

+ +

Message entity representing italic text.

+

+ +
+
messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityMention.html b/data/core.telegram.org/constructor/messageEntityMention.html new file mode 100644 index 0000000000..4584daf19d --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityMention.html @@ -0,0 +1,155 @@ + + + + + messageEntityMention + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityMention

+ +

Message entity mentioning the current user

+

+ +
+
messageEntityMention#fa04579d offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityMentionName.html b/data/core.telegram.org/constructor/messageEntityMentionName.html new file mode 100644 index 0000000000..efcaa4849f --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityMentionName.html @@ -0,0 +1,162 @@ + + + + + messageEntityMentionName + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityMentionName

+ +

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

+

+ +
+
messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idlongIdentifier of the user that was mentioned
+

Type

+

MessageEntity

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

inputMessageEntityMentionName

+

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityPhone.html b/data/core.telegram.org/constructor/messageEntityPhone.html new file mode 100644 index 0000000000..794f1b0197 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityPhone.html @@ -0,0 +1,152 @@ + + + + + messageEntityPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityPhone

+ +

Message entity representing a phone number.

+

+ +
+
messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityPre.html b/data/core.telegram.org/constructor/messageEntityPre.html new file mode 100644 index 0000000000..14e32ff352 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityPre.html @@ -0,0 +1,157 @@ + + + + + messageEntityPre + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityPre

+ +

Message entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.

+

+ +
+
messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
languagestringProgramming language of the code
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityTextUrl.html b/data/core.telegram.org/constructor/messageEntityTextUrl.html new file mode 100644 index 0000000000..00a81ee79b --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityTextUrl.html @@ -0,0 +1,160 @@ + + + + + messageEntityTextUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityTextUrl

+ +

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

+

+ +
+
messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
urlstringThe actual URL
+

Type

+

MessageEntity

+

Related pages

+

messageEntityUrl

+

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityUnderline.html b/data/core.telegram.org/constructor/messageEntityUnderline.html new file mode 100644 index 0000000000..a74348e32e --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityUnderline.html @@ -0,0 +1,152 @@ + + + + + messageEntityUnderline + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUnderline

+ +

Message entity representing underlined text.

+

+ +
+
messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityUnknown.html b/data/core.telegram.org/constructor/messageEntityUnknown.html new file mode 100644 index 0000000000..bb67ce7f8c --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityUnknown.html @@ -0,0 +1,152 @@ + + + + + messageEntityUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUnknown

+ +

Unknown message entity

+

+ +
+
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityUrl.html b/data/core.telegram.org/constructor/messageEntityUrl.html new file mode 100644 index 0000000000..87ec3fe3e0 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityUrl.html @@ -0,0 +1,155 @@ + + + + + messageEntityUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUrl

+ +

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

+

+ +
+
messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+

Related pages

+

messageEntityTextUrl

+

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageFwdHeader.html b/data/core.telegram.org/constructor/messageFwdHeader.html new file mode 100644 index 0000000000..bbfc984d74 --- /dev/null +++ b/data/core.telegram.org/constructor/messageFwdHeader.html @@ -0,0 +1,195 @@ + + + + + messageFwdHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

messageFwdHeader

+ +

Info about a forwarded message

+

+ +
+
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
importedflags.7?trueWhether this message was imported from a foreign chat service, click here for more info »
from_idflags.0?PeerThe ID of the user that originally sent the message
from_nameflags.5?stringThe name of the user that originally sent the message
dateintWhen was the message originally sent
channel_postflags.2?intID of the channel message that was forwarded
post_authorflags.3?stringFor channels and if signatures are enabled, author of the channel message
saved_from_peerflags.4?PeerOnly for messages forwarded to the current user (inputPeerSelf), full info about the user/channel that originally sent the message
saved_from_msg_idflags.4?intOnly for messages forwarded to the current user (inputPeerSelf), ID of the message that was forwarded from the original user/channel
psa_typeflags.6?stringPSA type
+

Type

+

MessageFwdHeader

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageInteractionCounters.html b/data/core.telegram.org/constructor/messageInteractionCounters.html new file mode 100644 index 0000000000..4c189ab684 --- /dev/null +++ b/data/core.telegram.org/constructor/messageInteractionCounters.html @@ -0,0 +1,157 @@ + + + + + messageInteractionCounters + + + + + + + + + + + + + +
+ +
+
+
+ +

messageInteractionCounters

+ +

Message interaction counters

+

+ +
+
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idintMessage ID
viewsintViews
forwardsintNumber of times this message was forwarded
+

Type

+

MessageInteractionCounters

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaAudio.html b/data/core.telegram.org/constructor/messageMediaAudio.html new file mode 100644 index 0000000000..4b99bc798d --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaAudio.html @@ -0,0 +1,147 @@ + + + + + messageMediaAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaAudio

+ +

Attached audio file.

+

+ +
+
Constructor schema is available as of layer 46. Switch »

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
audioAudioAudi file
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaContact.html b/data/core.telegram.org/constructor/messageMediaContact.html new file mode 100644 index 0000000000..4fd06b089e --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaContact.html @@ -0,0 +1,167 @@ + + + + + messageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaContact

+ +

Attached contact.

+

+ +
+
messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringVCARD of contact
user_idlongUser identifier or 0, if the user with the given phone number is not registered
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaDice.html b/data/core.telegram.org/constructor/messageMediaDice.html new file mode 100644 index 0000000000..5a50eab126 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaDice.html @@ -0,0 +1,155 @@ + + + + + messageMediaDice + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaDice

+ +

Dice-based animated sticker

+

+ +
+
messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
valueintDice value
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
+

Type

+

MessageMedia

+

Related pages

+

Dice

+

Telegram supports sending animated dice emojis.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaDocument.html b/data/core.telegram.org/constructor/messageMediaDocument.html new file mode 100644 index 0000000000..bd23851587 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaDocument.html @@ -0,0 +1,157 @@ + + + + + messageMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaDocument

+ +

Document (video, audio, voice, sticker, any media type except photo)

+

+ +
+
messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
documentflags.0?DocumentAttached document
ttl_secondsflags.2?intTime to live of self-destructing document
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaEmpty.html b/data/core.telegram.org/constructor/messageMediaEmpty.html new file mode 100644 index 0000000000..a4d518f5b4 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaEmpty.html @@ -0,0 +1,132 @@ + + + + + messageMediaEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaEmpty

+ +

Empty constructor.

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaGame.html b/data/core.telegram.org/constructor/messageMediaGame.html new file mode 100644 index 0000000000..e439d34c75 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaGame.html @@ -0,0 +1,147 @@ + + + + + messageMediaGame + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaGame

+ +

Telegram game

+

+ +
+
messageMediaGame#fdb19008 game:Game = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
gameGameGame
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaGeo.html b/data/core.telegram.org/constructor/messageMediaGeo.html new file mode 100644 index 0000000000..3bcf17c634 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaGeo.html @@ -0,0 +1,147 @@ + + + + + messageMediaGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaGeo

+ +

Attached map.

+

+ +
+
messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
geoGeoPointGeoPoint
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaGeoLive.html b/data/core.telegram.org/constructor/messageMediaGeoLive.html new file mode 100644 index 0000000000..fa4967169f --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaGeoLive.html @@ -0,0 +1,170 @@ + + + + + messageMediaGeoLive + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaGeoLive

+ +

Indicates a live geolocation

+

+ +
+
messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodintValidity period of provided geolocation
proximity_notification_radiusflags.1?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000).
+

Type

+

MessageMedia

+

Related pages

+

Live geolocation

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaInvoice.html b/data/core.telegram.org/constructor/messageMediaInvoice.html new file mode 100644 index 0000000000..e06d694510 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaInvoice.html @@ -0,0 +1,198 @@ + + + + + messageMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaInvoice

+ +

Invoice

+

+ +
+
messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueWhether the shipping address was requested
testflags.3?trueWhether this is an example invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
receipt_msg_idflags.2?intMessage ID of receipt: if set, clients should change the text of the first keyboardButtonBuy button always attached to the message to a localized version of the word Receipt
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
start_paramstringUnique bot deep-linking parameter that can be used to generate this invoice
+

Type

+

MessageMedia

+

Related pages

+

keyboardButtonBuy

+

Button to buy a product

+

message

+

A message

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaPhoto.html b/data/core.telegram.org/constructor/messageMediaPhoto.html new file mode 100644 index 0000000000..71475f35d0 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaPhoto.html @@ -0,0 +1,157 @@ + + + + + messageMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaPhoto

+ +

Attached photo.

+

+ +
+
messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
photoflags.0?PhotoPhoto
ttl_secondsflags.2?intTime to live in seconds of self-destructing photo
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaPoll.html b/data/core.telegram.org/constructor/messageMediaPoll.html new file mode 100644 index 0000000000..d68156fd1b --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaPoll.html @@ -0,0 +1,152 @@ + + + + + messageMediaPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaPoll

+ +

Poll

+

+ +
+
messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
pollPollThe poll
resultsPollResultsThe results of the poll
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaUnsupported.html b/data/core.telegram.org/constructor/messageMediaUnsupported.html new file mode 100644 index 0000000000..0a7a4728fc --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaUnsupported.html @@ -0,0 +1,132 @@ + + + + + messageMediaUnsupported + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaUnsupported

+ +

Current version of the client does not support this media type.

+

+ +
+
messageMediaUnsupported#9f84f49e = MessageMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaVenue.html b/data/core.telegram.org/constructor/messageMediaVenue.html new file mode 100644 index 0000000000..5bcb778635 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaVenue.html @@ -0,0 +1,172 @@ + + + + + messageMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaVenue

+ +

Venue

+

+ +
+
messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaVideo.html b/data/core.telegram.org/constructor/messageMediaVideo.html new file mode 100644 index 0000000000..c2832334c5 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaVideo.html @@ -0,0 +1,147 @@ + + + + + messageMediaVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaVideo

+ +

Attached video.

+

+ +
+
Constructor schema is available as of layer 28. Switch »

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
videoVideoVideo
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaWebPage.html b/data/core.telegram.org/constructor/messageMediaWebPage.html new file mode 100644 index 0000000000..0de3ffed8f --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaWebPage.html @@ -0,0 +1,147 @@ + + + + + messageMediaWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaWebPage

+ +

Preview of webpage

+

+ +
+
messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
webpageWebPageWebpage preview
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageRange.html b/data/core.telegram.org/constructor/messageRange.html new file mode 100644 index 0000000000..3b73eaecdb --- /dev/null +++ b/data/core.telegram.org/constructor/messageRange.html @@ -0,0 +1,152 @@ + + + + + messageRange + + + + + + + + + + + + + +
+ +
+
+
+ +

messageRange

+ +

Indicates a range of chat messages

+

+ +
+
messageRange#ae30253 min_id:int max_id:int = MessageRange;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
min_idintStart of range (message ID)
max_idintEnd of range (message ID)
+

Type

+

MessageRange

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageReplies.html b/data/core.telegram.org/constructor/messageReplies.html new file mode 100644 index 0000000000..e180f705fa --- /dev/null +++ b/data/core.telegram.org/constructor/messageReplies.html @@ -0,0 +1,189 @@ + + + + + messageReplies + + + + + + + + + + + + + +
+ +
+
+
+ +

messageReplies

+ +

Info about the comment section of a channel post, or a simple message thread

+

+ +
+
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
commentsflags.0?trueWhether this constructor contains information about the comment section of a channel post, or a simple message thread
repliesintContains the total number of replies in this thread or comment section.
replies_ptsintPTS of the message that started this thread.
recent_repliersflags.1?Vector<Peer>For channel post comments, contains information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.
channel_idflags.0?longFor channel post comments, contains the ID of the associated discussion supergroup
max_idflags.2?intID of the latest message in this thread or comment section.
read_max_idflags.3?intContains the ID of the latest read message in this thread or comment section.
+

Type

+

MessageReplies

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageReplyHeader.html b/data/core.telegram.org/constructor/messageReplyHeader.html new file mode 100644 index 0000000000..e662887c71 --- /dev/null +++ b/data/core.telegram.org/constructor/messageReplyHeader.html @@ -0,0 +1,165 @@ + + + + + messageReplyHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

messageReplyHeader

+ +

Message replies and thread information

+

+ +
+
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
reply_to_msg_idintID of message to which this message is replying
reply_to_peer_idflags.0?PeerFor replies sent in channel discussion threads of which the current user is not a member, the discussion group ID
reply_to_top_idflags.1?intID of the message that started this message thread
+

Type

+

MessageReplyHeader

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageService.html b/data/core.telegram.org/constructor/messageService.html new file mode 100644 index 0000000000..f226f554e6 --- /dev/null +++ b/data/core.telegram.org/constructor/messageService.html @@ -0,0 +1,212 @@ + + + + + messageService + + + + + + + + + + + + + +
+ +
+
+
+ +

messageService

+ +

Indicates a service message

+

+ +
+
messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether the message contains unread media
silentflags.13?trueWhether the message is silent
postflags.14?trueWhether it's a channel post
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
idintMessage ID
from_idflags.8?PeerID of the sender of this message
peer_idPeerSender of service message
reply_toflags.3?MessageReplyHeaderReply (thread) information
dateintMessage date
actionMessageActionEvent connected with the service message
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageUserVote.html b/data/core.telegram.org/constructor/messageUserVote.html new file mode 100644 index 0000000000..03592d4f54 --- /dev/null +++ b/data/core.telegram.org/constructor/messageUserVote.html @@ -0,0 +1,157 @@ + + + + + messageUserVote + + + + + + + + + + + + + +
+ +
+
+
+ +

messageUserVote

+ +

How a user voted in a poll

+

+ +
+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
optionbytesThe option chosen by the user
dateintWhen did the user cast the vote
+

Type

+

MessageUserVote

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageUserVoteInputOption.html b/data/core.telegram.org/constructor/messageUserVoteInputOption.html new file mode 100644 index 0000000000..c1c8117b11 --- /dev/null +++ b/data/core.telegram.org/constructor/messageUserVoteInputOption.html @@ -0,0 +1,155 @@ + + + + + messageUserVoteInputOption + + + + + + + + + + + + + +
+ +
+
+
+ +

messageUserVoteInputOption

+ +

How a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)

+

+ +
+
messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongThe user that voted for the queried option
dateintWhen did the user cast the vote
+

Type

+

MessageUserVote

+

Related pages

+

messages.getPollVotes

+

Get poll results for non-anonymous polls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageViews.html b/data/core.telegram.org/constructor/messageViews.html new file mode 100644 index 0000000000..8c03b860d4 --- /dev/null +++ b/data/core.telegram.org/constructor/messageViews.html @@ -0,0 +1,165 @@ + + + + + messageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messageViews

+ +

View, forward counter + info about replies of a specific message

+

+ +
+
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
viewsflags.0?intViewcount of message
forwardsflags.1?intForward count of message
repliesflags.2?MessageRepliesReply and thread information of message
+

Type

+

MessageViews

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.affectedFoundMessages b/data/core.telegram.org/constructor/messages.affectedFoundMessages new file mode 100644 index 0000000000..f955fe1dfe --- /dev/null +++ b/data/core.telegram.org/constructor/messages.affectedFoundMessages @@ -0,0 +1,165 @@ + + + + + messages.affectedFoundMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.affectedFoundMessages

+ +

Messages found and affected by changes

+

+ +
+
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
offsetintIf bigger than zero, the request must be repeated to remove more messages
messagesVector<int>Affected message IDs
+

Type

+

messages.AffectedFoundMessages

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.affectedHistory b/data/core.telegram.org/constructor/messages.affectedHistory new file mode 100644 index 0000000000..d8b960021b --- /dev/null +++ b/data/core.telegram.org/constructor/messages.affectedHistory @@ -0,0 +1,157 @@ + + + + + messages.affectedHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.affectedHistory

+ +

Affected part of communication history with the user or in a chat.

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintNumber of events occured in a text box
pts_countintNumber of affected events
offsetintIf a parameter contains positive value, it is necessary to repeat the method call using the given value; during the proceeding of all the history the value itself shall gradually decrease
+

Type

+

messages.AffectedHistory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.affectedMessages b/data/core.telegram.org/constructor/messages.affectedMessages new file mode 100644 index 0000000000..557b694732 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.affectedMessages @@ -0,0 +1,155 @@ + + + + + messages.affectedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.affectedMessages

+ +

Events affected by operation

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

messages.AffectedMessages

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.allStickers b/data/core.telegram.org/constructor/messages.allStickers new file mode 100644 index 0000000000..1d5a2403bc --- /dev/null +++ b/data/core.telegram.org/constructor/messages.allStickers @@ -0,0 +1,155 @@ + + + + + messages.allStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.allStickers

+ +

Info about all installed stickers

+

+ +
+
messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
setsVector<StickerSet>All stickersets
+

Type

+

messages.AllStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.allStickersNotModified b/data/core.telegram.org/constructor/messages.allStickersNotModified new file mode 100644 index 0000000000..180d8a43b8 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.allStickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.allStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.allStickersNotModified

+ +

Info about all installed stickers hasn't changed

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.AllStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.archivedStickers b/data/core.telegram.org/constructor/messages.archivedStickers new file mode 100644 index 0000000000..8d1f505279 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.archivedStickers @@ -0,0 +1,152 @@ + + + + + messages.archivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.archivedStickers

+ +

Archived stickersets

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of archived stickers
setsVector<StickerSetCovered>Archived stickersets
+

Type

+

messages.ArchivedStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.botCallbackAnswer b/data/core.telegram.org/constructor/messages.botCallbackAnswer new file mode 100644 index 0000000000..d89ee5a8a4 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.botCallbackAnswer @@ -0,0 +1,177 @@ + + + + + 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.botResults b/data/core.telegram.org/constructor/messages.botResults new file mode 100644 index 0000000000..14ce77f8c6 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.botResults @@ -0,0 +1,182 @@ + + + + + messages.botResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.botResults

+ +

Result of a query to an inline bot

+

+ +
+
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueWhether the result is a picture gallery
query_idlongQuery ID
next_offsetflags.1?stringThe next offset to use when navigating through results
switch_pmflags.2?InlineBotSwitchPMWhether the bot requested the user to message him in private
resultsVector<BotInlineResult>The results
cache_timeintCaching validity of the results
usersVector<User>Users mentioned in the results
+

Type

+

messages.BotResults

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.channelMessages b/data/core.telegram.org/constructor/messages.channelMessages new file mode 100644 index 0000000000..1059577aac --- /dev/null +++ b/data/core.telegram.org/constructor/messages.channelMessages @@ -0,0 +1,185 @@ + + + + + messages.channelMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.channelMessages

+ +

Channel messages

+

+ +
+
messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, returned results may be inexact
ptsintEvent count after generation
countintTotal number of results were found server-side (may not be all included here)
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>Found messages
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

messages.Messages

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.chatAdminsWithInvites b/data/core.telegram.org/constructor/messages.chatAdminsWithInvites new file mode 100644 index 0000000000..eb2e6e7853 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.chatAdminsWithInvites @@ -0,0 +1,152 @@ + + + + + messages.chatAdminsWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatAdminsWithInvites

+ +

Info about chat invites generated by admins.

+

+ +
+
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
adminsVector<ChatAdminWithInvites>Info about chat invites generated by admins.
usersVector<User>Mentioned users
+

Type

+

messages.ChatAdminsWithInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.chatFull b/data/core.telegram.org/constructor/messages.chatFull new file mode 100644 index 0000000000..7f2160eb7a --- /dev/null +++ b/data/core.telegram.org/constructor/messages.chatFull @@ -0,0 +1,157 @@ + + + + + messages.chatFull + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatFull

+ +

Extended info on chat and auxiliary data.

+

+ +
+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
full_chatChatFullExtended info on a chat
chatsVector<Chat>List containing basic info on chat
usersVector<User>List of users mentioned above
+

Type

+

messages.ChatFull

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.chatInviteImporters b/data/core.telegram.org/constructor/messages.chatInviteImporters new file mode 100644 index 0000000000..222ee4d54b --- /dev/null +++ b/data/core.telegram.org/constructor/messages.chatInviteImporters @@ -0,0 +1,157 @@ + + + + + messages.chatInviteImporters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatInviteImporters

+ +

Info about the users that joined the chat using a specific chat invite

+

+ +
+
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of users that joined
importersVector<ChatInviteImporter>The users that joined
usersVector<User>The users that joined
+

Type

+

messages.ChatInviteImporters

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.chats b/data/core.telegram.org/constructor/messages.chats new file mode 100644 index 0000000000..cab0da8262 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.chats @@ -0,0 +1,147 @@ + + + + + messages.chats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chats

+ +

List of chats with auxiliary data.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<Chat>List of chats
+

Type

+

messages.Chats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.chatsSlice b/data/core.telegram.org/constructor/messages.chatsSlice new file mode 100644 index 0000000000..22e0895dec --- /dev/null +++ b/data/core.telegram.org/constructor/messages.chatsSlice @@ -0,0 +1,155 @@ + + + + + messages.chatsSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatsSlice

+ +

Partial list of chats, more would have to be fetched with pagination

+

+ +
+
messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of results that were found server-side (not all are included in chats)
chatsVector<Chat>Chats
+

Type

+

messages.Chats

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.checkedHistoryImportPeer b/data/core.telegram.org/constructor/messages.checkedHistoryImportPeer new file mode 100644 index 0000000000..43ef5a8c32 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.checkedHistoryImportPeer @@ -0,0 +1,150 @@ + + + + + messages.checkedHistoryImportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkedHistoryImportPeer

+ +

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

+

+ +
+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
confirm_textstringA confirmation text to be shown to the user, upon importing chat history ».
+

Type

+

messages.CheckedHistoryImportPeer

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.dhConfig b/data/core.telegram.org/constructor/messages.dhConfig new file mode 100644 index 0000000000..afb3f3c3f0 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.dhConfig @@ -0,0 +1,162 @@ + + + + + messages.dhConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.dhConfig

+ +

New set of configuring parameters.

+

+ +
+
messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
gintNew value prime, see Wikipedia
pbytesNew value primitive root, see Wikipedia
versionintVestion of set of parameters
randombytesRandom sequence of bytes of assigned length
+

Type

+

messages.DhConfig

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.dhConfigNotModified b/data/core.telegram.org/constructor/messages.dhConfigNotModified new file mode 100644 index 0000000000..b364445f51 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.dhConfigNotModified @@ -0,0 +1,147 @@ + + + + + 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.dialogs b/data/core.telegram.org/constructor/messages.dialogs new file mode 100644 index 0000000000..467e147cc1 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.dialogs @@ -0,0 +1,162 @@ + + + + + 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/core.telegram.org/constructor/messages.dialogsNotModified b/data/core.telegram.org/constructor/messages.dialogsNotModified new file mode 100644 index 0000000000..b48535f510 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.dialogsNotModified @@ -0,0 +1,147 @@ + + + + + messages.dialogsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.dialogsNotModified

+ +

Dialogs haven't changed

+

+ +
+
messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of dialogs found server-side by the query
+

Type

+

messages.Dialogs

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.dialogsSlice b/data/core.telegram.org/constructor/messages.dialogsSlice new file mode 100644 index 0000000000..d1fd165555 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.dialogsSlice @@ -0,0 +1,167 @@ + + + + + messages.dialogsSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.dialogsSlice

+ +

Incomplete list of dialogs with messages and auxiliary data.

+

+ +
+
messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of dialogs
dialogsVector<Dialog>List of dialogs
messagesVector<Message>List of last messages from dialogs
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
+

Type

+

messages.Dialogs

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.discussionMessage b/data/core.telegram.org/constructor/messages.discussionMessage new file mode 100644 index 0000000000..be23222222 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.discussionMessage @@ -0,0 +1,185 @@ + + + + + messages.discussionMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.discussionMessage

+ +

Information about a message thread

+

+ +
+
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
messagesVector<Message>Discussion messages
max_idflags.0?intMessage ID of latest reply in this thread
read_inbox_max_idflags.1?intMessage ID of latest read incoming message in this thread
read_outbox_max_idflags.2?intMessage ID of latest read outgoing message in this thread
unread_countintNumber of unread messages
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
+

Type

+

messages.DiscussionMessage

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.exportedChatInvite b/data/core.telegram.org/constructor/messages.exportedChatInvite new file mode 100644 index 0000000000..8d965aabd0 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.exportedChatInvite @@ -0,0 +1,152 @@ + + + + + messages.exportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInvite

+ +

Info about a chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteInfo about the chat invite
usersVector<User>Mentioned users
+

Type

+

messages.ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.exportedChatInviteReplaced b/data/core.telegram.org/constructor/messages.exportedChatInviteReplaced new file mode 100644 index 0000000000..a6af29aa86 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.exportedChatInviteReplaced @@ -0,0 +1,157 @@ + + + + + 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.exportedChatInvites b/data/core.telegram.org/constructor/messages.exportedChatInvites new file mode 100644 index 0000000000..5fbcb7dc5e --- /dev/null +++ b/data/core.telegram.org/constructor/messages.exportedChatInvites @@ -0,0 +1,157 @@ + + + + + messages.exportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInvites

+ +

Info about chat invites exported by a certain admin.

+

+ +
+
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of invites exported by the admin
invitesVector<ExportedChatInvite>Exported invites
usersVector<User>Info about the admin
+

Type

+

messages.ExportedChatInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.favedStickers b/data/core.telegram.org/constructor/messages.favedStickers new file mode 100644 index 0000000000..ec70df2b2f --- /dev/null +++ b/data/core.telegram.org/constructor/messages.favedStickers @@ -0,0 +1,160 @@ + + + + + messages.favedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.favedStickers

+ +

Favorited stickers

+

+ +
+
messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Favorited stickers
+

Type

+

messages.FavedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.favedStickersNotModified b/data/core.telegram.org/constructor/messages.favedStickersNotModified new file mode 100644 index 0000000000..58f4bbfd2f --- /dev/null +++ b/data/core.telegram.org/constructor/messages.favedStickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.favedStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.favedStickersNotModified

+ +

No new favorited stickers were found

+

+ +
+
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.FavedStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.featuredStickers b/data/core.telegram.org/constructor/messages.featuredStickers new file mode 100644 index 0000000000..256f1725d7 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.featuredStickers @@ -0,0 +1,165 @@ + + + + + messages.featuredStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.featuredStickers

+ +

Featured stickersets

+

+ +
+
messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
countintTotal number of featured stickers
setsVector<StickerSetCovered>Featured stickersets
unreadVector<long>IDs of new featured stickersets
+

Type

+

messages.FeaturedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.featuredStickersNotModified b/data/core.telegram.org/constructor/messages.featuredStickersNotModified new file mode 100644 index 0000000000..d56e5b5a76 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.featuredStickersNotModified @@ -0,0 +1,147 @@ + + + + + messages.featuredStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.featuredStickersNotModified

+ +

Featured stickers haven't changed

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of featured stickers
+

Type

+

messages.FeaturedStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.foundStickerSets b/data/core.telegram.org/constructor/messages.foundStickerSets new file mode 100644 index 0000000000..01d19baa25 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.foundStickerSets @@ -0,0 +1,155 @@ + + + + + messages.foundStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.foundStickerSets

+ +

Found stickersets

+

+ +
+
messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
setsVector<StickerSetCovered>Found stickersets
+

Type

+

messages.FoundStickerSets

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified b/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified new file mode 100644 index 0000000000..168fc83b54 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified @@ -0,0 +1,132 @@ + + + + + messages.foundStickerSetsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.foundStickerSetsNotModified

+ +

No further results were found

+

+ +
+
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.FoundStickerSets

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.highScores b/data/core.telegram.org/constructor/messages.highScores new file mode 100644 index 0000000000..a6da22ce25 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.highScores @@ -0,0 +1,152 @@ + + + + + messages.highScores + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.highScores

+ +

Highscores in a game

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scoresVector<HighScore>Highscores
usersVector<User>Users, associated to the highscores
+

Type

+

messages.HighScores

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.historyImport b/data/core.telegram.org/constructor/messages.historyImport new file mode 100644 index 0000000000..10daabdd9d --- /dev/null +++ b/data/core.telegram.org/constructor/messages.historyImport @@ -0,0 +1,150 @@ + + + + + messages.historyImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.historyImport

+ +

ID of a specific chat import session, click here for more info ».

+

+ +
+
messages.historyImport#1662af0b id:long = messages.HistoryImport;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongHistory import ID
+

Type

+

messages.HistoryImport

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.historyImportParsed b/data/core.telegram.org/constructor/messages.historyImportParsed new file mode 100644 index 0000000000..2c49dcc24e --- /dev/null +++ b/data/core.telegram.org/constructor/messages.historyImportParsed @@ -0,0 +1,166 @@ + + + + + messages.historyImportParsed + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.historyImportParsed

+ +

Contains information about a chat export file generated by a foreign chat app, click here for more info.
+If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

+

+ +
+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pmflags.0?trueThe chat export file was generated from a private chat.
groupflags.1?trueThe chat export file was generated from a group chat.
titleflags.2?stringTitle of the chat.
+

Type

+

messages.HistoryImportParsed

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.inactiveChats b/data/core.telegram.org/constructor/messages.inactiveChats new file mode 100644 index 0000000000..a2d77f9780 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.inactiveChats @@ -0,0 +1,157 @@ + + + + + messages.inactiveChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.inactiveChats

+ +

Inactive chat list

+

+ +
+
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
datesVector<int>When was the chat last active
chatsVector<Chat>Chat list
usersVector<User>Users mentioned in the chat list
+

Type

+

messages.InactiveChats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.messageEditData b/data/core.telegram.org/constructor/messages.messageEditData new file mode 100644 index 0000000000..b36d5f264c --- /dev/null +++ b/data/core.telegram.org/constructor/messages.messageEditData @@ -0,0 +1,152 @@ + + + + + messages.messageEditData + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messageEditData

+ +

Message edit data for media

+

+ +
+
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
captionflags.0?trueMedia caption, if the specified media's caption can be edited
+

Type

+

messages.MessageEditData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.messageViews b/data/core.telegram.org/constructor/messages.messageViews new file mode 100644 index 0000000000..4f44796a53 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.messageViews @@ -0,0 +1,157 @@ + + + + + messages.messageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messageViews

+ +

View, forward counter + info about replies

+

+ +
+
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
viewsVector<MessageViews>View, forward counter + info about replies
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
+

Type

+

messages.MessageViews

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.messages b/data/core.telegram.org/constructor/messages.messages new file mode 100644 index 0000000000..9aec4d0344 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.messages @@ -0,0 +1,157 @@ + + + + + messages.messages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messages

+ +

Full list of messages with auxilary data.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
+

Type

+

messages.Messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.messagesNotModified b/data/core.telegram.org/constructor/messages.messagesNotModified new file mode 100644 index 0000000000..df24944e7f --- /dev/null +++ b/data/core.telegram.org/constructor/messages.messagesNotModified @@ -0,0 +1,147 @@ + + + + + messages.messagesNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messagesNotModified

+ +

No new messages matching the query were found

+

+ +
+
messages.messagesNotModified#74535f21 count:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of results found server-side by the given query
+

Type

+

messages.Messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.messagesSlice b/data/core.telegram.org/constructor/messages.messagesSlice new file mode 100644 index 0000000000..03e3f7b7bd --- /dev/null +++ b/data/core.telegram.org/constructor/messages.messagesSlice @@ -0,0 +1,185 @@ + + + + + messages.messagesSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messagesSlice

+ +

Incomplete list of messages and auxiliary data.

+

+ +
+
messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, indicates that the results may be inexact
countintTotal number of messages in the list
next_rateflags.0?intRate to use in the offset_rate parameter in the next call to messages.searchGlobal
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in messages
usersVector<User>List of users mentioned in messages and chats
+

Type

+

messages.Messages

+

Related pages

+

messages.searchGlobal

+

Search for messages and peers globally

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.peerDialogs b/data/core.telegram.org/constructor/messages.peerDialogs new file mode 100644 index 0000000000..328434af49 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.peerDialogs @@ -0,0 +1,170 @@ + + + + + messages.peerDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.peerDialogs

+ +

Dialog info of multiple peers

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dialogsVector<Dialog>Dialog info
messagesVector<Message>Messages mentioned in dialog info
chatsVector<Chat>Chats
usersVector<User>Users
stateupdates.StateCurrent update state of dialog
+

Type

+

messages.PeerDialogs

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.recentStickers b/data/core.telegram.org/constructor/messages.recentStickers new file mode 100644 index 0000000000..f1320e84a0 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.recentStickers @@ -0,0 +1,165 @@ + + + + + messages.recentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.recentStickers

+ +

Recently used stickers

+

+ +
+
messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Recent stickers
datesVector<int>When was each sticker last used
+

Type

+

messages.RecentStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.recentStickersNotModified b/data/core.telegram.org/constructor/messages.recentStickersNotModified new file mode 100644 index 0000000000..9b6c0caf08 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.recentStickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.recentStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.recentStickersNotModified

+ +

No new recent sticker was found

+

+ +
+
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.RecentStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.savedGifs b/data/core.telegram.org/constructor/messages.savedGifs new file mode 100644 index 0000000000..355dc2ba0d --- /dev/null +++ b/data/core.telegram.org/constructor/messages.savedGifs @@ -0,0 +1,155 @@ + + + + + messages.savedGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.savedGifs

+ +

Saved gifs

+

+ +
+
messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
gifsVector<Document>List of saved gifs
+

Type

+

messages.SavedGifs

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.savedGifsNotModified b/data/core.telegram.org/constructor/messages.savedGifsNotModified new file mode 100644 index 0000000000..24e390a658 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.savedGifsNotModified @@ -0,0 +1,132 @@ + + + + + messages.savedGifsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.savedGifsNotModified

+ +

No new saved gifs were found

+

+ +
+
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.SavedGifs

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.searchCounter b/data/core.telegram.org/constructor/messages.searchCounter new file mode 100644 index 0000000000..43cd3b55aa --- /dev/null +++ b/data/core.telegram.org/constructor/messages.searchCounter @@ -0,0 +1,165 @@ + + + + + messages.searchCounter + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchCounter

+ +

Indicates how many results would be found by a messages.search call with the same parameters

+

+ +
+
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, the results may be inexact
filterMessagesFilterProvided message filter
countintNumber of results that were found server-side
+

Type

+

messages.SearchCounter

+

Related pages

+

messages.search

+

Gets back found messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.sentEncryptedFile b/data/core.telegram.org/constructor/messages.sentEncryptedFile new file mode 100644 index 0000000000..5cd6e151c7 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.sentEncryptedFile @@ -0,0 +1,152 @@ + + + + + messages.sentEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sentEncryptedFile

+ +

Message with a file enclosure sent to a protected chat

+

+ +
+
messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dateintSending date
fileEncryptedFileAttached file
+

Type

+

messages.SentEncryptedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.sentEncryptedMessage b/data/core.telegram.org/constructor/messages.sentEncryptedMessage new file mode 100644 index 0000000000..f88f8392e0 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.sentEncryptedMessage @@ -0,0 +1,147 @@ + + + + + messages.sentEncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sentEncryptedMessage

+ +

Message without file attachemts sent to an encrypted file.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dateintDate of sending
+

Type

+

messages.SentEncryptedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.sentMessageLink b/data/core.telegram.org/constructor/messages.sentMessageLink new file mode 100644 index 0000000000..f56f6d1e61 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.sentMessageLink @@ -0,0 +1,167 @@ + + + + + messages.sentMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sentMessageLink

+ +

Info on successfully sent message and on changes links.

+

+ +
+
Constructor schema is available as of layer 24. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintMessage ID
dateintDate of sending
ptsintNew value of pts parameter of a current state
seqintNew value of seq parameter of a current state
linksVector<contacts.Link>List of changes links
+

Type

+

messages.SentMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.sponsoredMessages b/data/core.telegram.org/constructor/messages.sponsoredMessages new file mode 100644 index 0000000000..16b95514f2 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.sponsoredMessages @@ -0,0 +1,157 @@ + + + + + messages.sponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sponsoredMessages

+ +

A set of sponsored messages associated to a channel

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<SponsoredMessage>Sponsored messages
chatsVector<Chat>Chats mentioned in the sponsored messages
usersVector<User>Users mentioned in the sponsored messages
+

Type

+

messages.SponsoredMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.statedMessageLink b/data/core.telegram.org/constructor/messages.statedMessageLink new file mode 100644 index 0000000000..562a59257c --- /dev/null +++ b/data/core.telegram.org/constructor/messages.statedMessageLink @@ -0,0 +1,172 @@ + + + + + messages.statedMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.statedMessageLink

+ +

Message with auxiliary data, state data and the list of changed links.

+

+ +
+
Constructor schema is available as of layer 24. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageMessage
chatsVector<Chat>List of chats mentioned in message
usersVector<User>List of users mentioned in message and chats
linksVector<contacts.Link>List of changed links
ptsintNumber of events occurred in text box
seqintNumber of sent updates
+

Type

+

messages.StatedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.statedMessagesLinks b/data/core.telegram.org/constructor/messages.statedMessagesLinks new file mode 100644 index 0000000000..13eeddd424 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.statedMessagesLinks @@ -0,0 +1,172 @@ + + + + + messages.statedMessagesLinks + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.statedMessagesLinks

+ +

Message with auxiliary data, state data and the list of changed links.

+

+ +
+
Constructor schema is available as of layer 24. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of cats mentioned in messages
usersVector<User>List of users mentioned in messages and cahts
linksVector<contacts.Link>List of changed links
ptsintNumber of event occurred in a text box
seqintNumber of sent updates
+

Type

+

messages.StatedMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.stickerSet b/data/core.telegram.org/constructor/messages.stickerSet new file mode 100644 index 0000000000..46e45cdbee --- /dev/null +++ b/data/core.telegram.org/constructor/messages.stickerSet @@ -0,0 +1,157 @@ + + + + + messages.stickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickerSet

+ +

Stickerset and stickers inside it

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
setStickerSetThe stickerset
packsVector<StickerPack>Emoji info for stickers
documentsVector<Document>Stickers in stickerset
+

Type

+

messages.StickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive b/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive new file mode 100644 index 0000000000..00859a4765 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive @@ -0,0 +1,147 @@ + + + + + messages.stickerSetInstallResultArchive + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickerSetInstallResultArchive

+ +

The stickerset was installed, but since there are too many stickersets some were archived

+

+ +
+
messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
setsVector<StickerSetCovered>Archived stickersets
+

Type

+

messages.StickerSetInstallResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess b/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess new file mode 100644 index 0000000000..3e5fb096b1 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess @@ -0,0 +1,132 @@ + + + + + messages.stickerSetInstallResultSuccess + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickerSetInstallResultSuccess

+ +

The stickerset was installed successfully

+

+ +
+
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.StickerSetInstallResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.stickers b/data/core.telegram.org/constructor/messages.stickers new file mode 100644 index 0000000000..9eb9b02d0b --- /dev/null +++ b/data/core.telegram.org/constructor/messages.stickers @@ -0,0 +1,155 @@ + + + + + messages.stickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickers

+ +

Found stickers

+

+ +
+
messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
stickersVector<Document>Stickers
+

Type

+

messages.Stickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.stickersNotModified b/data/core.telegram.org/constructor/messages.stickersNotModified new file mode 100644 index 0000000000..dc640e7b7a --- /dev/null +++ b/data/core.telegram.org/constructor/messages.stickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.stickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickersNotModified

+ +

No new stickers were found for the given query

+

+ +
+
messages.stickersNotModified#f1749a22 = messages.Stickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.Stickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.votesList b/data/core.telegram.org/constructor/messages.votesList new file mode 100644 index 0000000000..33c76927cc --- /dev/null +++ b/data/core.telegram.org/constructor/messages.votesList @@ -0,0 +1,170 @@ + + + + + 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 new file mode 100644 index 0000000000..c1dd455bc7 --- /dev/null +++ b/data/core.telegram.org/constructor/nearestDc.html @@ -0,0 +1,157 @@ + + + + + nearestDc + + + + + + + + + + + + + +
+ +
+
+
+ +

nearestDc

+ +

Nearest data centre, according to geo-ip.

+

+ +
+
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countrystringCountry code determined by geo-ip
this_dcintNumber of current data centre
nearest_dcintNumber of nearest data centre
+

Type

+

NearestDc

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/notifyBroadcasts.html b/data/core.telegram.org/constructor/notifyBroadcasts.html new file mode 100644 index 0000000000..a2e26db1d9 --- /dev/null +++ b/data/core.telegram.org/constructor/notifyBroadcasts.html @@ -0,0 +1,132 @@ + + + + + notifyBroadcasts + + + + + + + + + + + + + +
+ +
+
+
+ +

notifyBroadcasts

+ +

Channel notification settings

+

+ +
+
notifyBroadcasts#d612e8ef = NotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

NotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/notifyChats.html b/data/core.telegram.org/constructor/notifyChats.html new file mode 100644 index 0000000000..c2edc13500 --- /dev/null +++ b/data/core.telegram.org/constructor/notifyChats.html @@ -0,0 +1,132 @@ + + + + + notifyChats + + + + + + + + + + + + + +
+ +
+
+
+ +

notifyChats

+ +

Notifications generated by all groups.

+

+ +
+
notifyChats#c007cec3 = NotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

NotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/notifyPeer.html b/data/core.telegram.org/constructor/notifyPeer.html new file mode 100644 index 0000000000..9beb73c9d5 --- /dev/null +++ b/data/core.telegram.org/constructor/notifyPeer.html @@ -0,0 +1,147 @@ + + + + + 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/notifyUsers.html b/data/core.telegram.org/constructor/notifyUsers.html new file mode 100644 index 0000000000..a72465c25a --- /dev/null +++ b/data/core.telegram.org/constructor/notifyUsers.html @@ -0,0 +1,132 @@ + + + + + notifyUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

notifyUsers

+ +

Notifications generated by all users.

+

+ +
+
notifyUsers#b4c83b4c = NotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

NotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/null.html b/data/core.telegram.org/constructor/null.html new file mode 100644 index 0000000000..3c3bb87d9d --- /dev/null +++ b/data/core.telegram.org/constructor/null.html @@ -0,0 +1,132 @@ + + + + + null + + + + + + + + + + + + + +
+ +
+
+
+ +

null

+ +

Corresponds to an arbitrary empty object.

+

+ +
+
null#56730bcc = Null;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Null

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/page.html b/data/core.telegram.org/constructor/page.html new file mode 100644 index 0000000000..619d560c57 --- /dev/null +++ b/data/core.telegram.org/constructor/page.html @@ -0,0 +1,190 @@ + + + + + page + + + + + + + + + + + + + +
+ +
+
+
+ +

page

+ +

Instant view page

+

+ +
+
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
partflags.0?trueIndicates that not full page preview is available to the client and it will need to fetch full Instant View from the server using messages.getWebPagePreview.
rtlflags.1?trueWhether the page contains RTL text
v2flags.2?trueWhether this is an IV v2 page
urlstringOriginal page HTTP URL
blocksVector<PageBlock>Page elements (like with HTML elements, only as TL constructors)
photosVector<Photo>Photos in page
documentsVector<Document>Media in page
viewsflags.3?intViewcount
+

Type

+

Page

+

Related pages

+

messages.getWebPagePreview

+

Get preview of webpage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockAnchor.html b/data/core.telegram.org/constructor/pageBlockAnchor.html new file mode 100644 index 0000000000..c48e66b036 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockAnchor.html @@ -0,0 +1,147 @@ + + + + + pageBlockAnchor + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockAnchor

+ +

Link to section within the page itself (like <a href="#target">anchor</a>)

+

+ +
+
pageBlockAnchor#ce0d37b0 name:string = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
namestringName of target section
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockAudio.html b/data/core.telegram.org/constructor/pageBlockAudio.html new file mode 100644 index 0000000000..e3698915a7 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockAudio.html @@ -0,0 +1,155 @@ + + + + + pageBlockAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockAudio

+ +

Audio

+

+ +
+
pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
audio_idlongAudio ID (to be fetched from the container page constructor
captionPageCaptionAudio caption
+

Type

+

PageBlock

+

Related pages

+

page

+

Instant view page

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockAuthorDate.html b/data/core.telegram.org/constructor/pageBlockAuthorDate.html new file mode 100644 index 0000000000..0f24d2fbda --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockAuthorDate.html @@ -0,0 +1,152 @@ + + + + + pageBlockAuthorDate + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockAuthorDate

+ +

Author and date of creation of article

+

+ +
+
pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
authorRichTextAuthor name
published_dateintDate of pubblication
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockBlockquote.html b/data/core.telegram.org/constructor/pageBlockBlockquote.html new file mode 100644 index 0000000000..1d207c8fce --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockBlockquote.html @@ -0,0 +1,152 @@ + + + + + pageBlockBlockquote + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockBlockquote

+ +

Quote (equivalent to the HTML <blockquote>)

+

+ +
+
pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextQuote contents
captionRichTextCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockChannel.html b/data/core.telegram.org/constructor/pageBlockChannel.html new file mode 100644 index 0000000000..e8690b2830 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockChannel.html @@ -0,0 +1,147 @@ + + + + + pageBlockChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockChannel

+ +

Reference to a telegram channel

+

+ +
+
pageBlockChannel#ef1751b5 channel:Chat = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelChatThe channel/supergroup/chat
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockCollage.html b/data/core.telegram.org/constructor/pageBlockCollage.html new file mode 100644 index 0000000000..f6a8fd5db7 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockCollage.html @@ -0,0 +1,152 @@ + + + + + pageBlockCollage + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockCollage

+ +

Collage of media

+

+ +
+
pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageBlock>Media elements
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockCover.html b/data/core.telegram.org/constructor/pageBlockCover.html new file mode 100644 index 0000000000..714bf0551b --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockCover.html @@ -0,0 +1,147 @@ + + + + + pageBlockCover + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockCover

+ +

A page cover

+

+ +
+
pageBlockCover#39f23300 cover:PageBlock = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
coverPageBlockCover
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockDetails.html b/data/core.telegram.org/constructor/pageBlockDetails.html new file mode 100644 index 0000000000..e9e599be5a --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockDetails.html @@ -0,0 +1,162 @@ + + + + + pageBlockDetails + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockDetails

+ +

A collapsible details block

+

+ +
+
pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
openflags.0?trueWhether the block is open by default
blocksVector<PageBlock>Block contents
titleRichTextAlways visible heading for the block
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockDivider.html b/data/core.telegram.org/constructor/pageBlockDivider.html new file mode 100644 index 0000000000..c760735f55 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockDivider.html @@ -0,0 +1,132 @@ + + + + + pageBlockDivider + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockDivider

+ +

An empty block separating a page

+

+ +
+
pageBlockDivider#db20b188 = PageBlock;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockEmbed.html b/data/core.telegram.org/constructor/pageBlockEmbed.html new file mode 100644 index 0000000000..2cb9358f7c --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockEmbed.html @@ -0,0 +1,187 @@ + + + + + pageBlockEmbed + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockEmbed

+ +

An embedded webpage

+

+ +
+
pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
full_widthflags.0?trueWhether the block should be full width
allow_scrollingflags.3?trueWhether scrolling should be allowed
urlflags.1?stringWeb page URL, if available
htmlflags.2?stringHTML-markup of the embedded page
poster_photo_idflags.4?longPoster photo, if available
wflags.5?intBlock width, if known
hflags.5?intBlock height, if known
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockEmbedPost.html b/data/core.telegram.org/constructor/pageBlockEmbedPost.html new file mode 100644 index 0000000000..41dfac8c00 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockEmbedPost.html @@ -0,0 +1,177 @@ + + + + + pageBlockEmbedPost + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockEmbedPost

+ +

An embedded post

+

+ +
+
pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringWeb page URL
webpage_idlongID of generated webpage preview
author_photo_idlongID of the author's photo
authorstringAuthor name
dateintCreation date
blocksVector<PageBlock>Post contents
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockFooter.html b/data/core.telegram.org/constructor/pageBlockFooter.html new file mode 100644 index 0000000000..b168e0bb1f --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockFooter.html @@ -0,0 +1,147 @@ + + + + + pageBlockFooter + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockFooter

+ +

Page footer

+

+ +
+
pageBlockFooter#48870999 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextContents
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockHeader.html b/data/core.telegram.org/constructor/pageBlockHeader.html new file mode 100644 index 0000000000..a16dac3083 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockHeader.html @@ -0,0 +1,147 @@ + + + + + pageBlockHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockHeader

+ +

Page header

+

+ +
+
pageBlockHeader#bfd064ec text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextContents
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockKicker.html b/data/core.telegram.org/constructor/pageBlockKicker.html new file mode 100644 index 0000000000..4414562bac --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockKicker.html @@ -0,0 +1,147 @@ + + + + + pageBlockKicker + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockKicker

+ +

Kicker

+

+ +
+
pageBlockKicker#1e148390 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextContents
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockList.html b/data/core.telegram.org/constructor/pageBlockList.html new file mode 100644 index 0000000000..925921bc8c --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockList.html @@ -0,0 +1,147 @@ + + + + + pageBlockList + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockList

+ +

Unordered list of IV blocks

+

+ +
+
pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageListItem>List of blocks in an IV page
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockMap.html b/data/core.telegram.org/constructor/pageBlockMap.html new file mode 100644 index 0000000000..e2af18353b --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockMap.html @@ -0,0 +1,167 @@ + + + + + pageBlockMap + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockMap

+ +

A map

+

+ +
+
pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geoGeoPointLocation of the map center
zoomintMap zoom level; 13-20
wintMap width in pixels before applying scale; 16-102
hintMap height in pixels before applying scale; 16-1024
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockOrderedList.html b/data/core.telegram.org/constructor/pageBlockOrderedList.html new file mode 100644 index 0000000000..5528e7602a --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockOrderedList.html @@ -0,0 +1,147 @@ + + + + + pageBlockOrderedList + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockOrderedList

+ +

Ordered list of IV blocks

+

+ +
+
pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageListOrderedItem>List items
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockParagraph.html b/data/core.telegram.org/constructor/pageBlockParagraph.html new file mode 100644 index 0000000000..f971022717 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockParagraph.html @@ -0,0 +1,147 @@ + + + + + pageBlockParagraph + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockParagraph

+ +

A paragraph

+

+ +
+
pageBlockParagraph#467a0766 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockPhoto.html b/data/core.telegram.org/constructor/pageBlockPhoto.html new file mode 100644 index 0000000000..f8ed8806e0 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockPhoto.html @@ -0,0 +1,167 @@ + + + + + pageBlockPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockPhoto

+ +

A photo

+

+ +
+
pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
photo_idlongPhoto ID
captionPageCaptionCaption
urlflags.0?stringHTTP URL of page the photo leads to when clicked
webpage_idflags.0?longID of preview of the page the photo leads to when clicked
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockPreformatted.html b/data/core.telegram.org/constructor/pageBlockPreformatted.html new file mode 100644 index 0000000000..6efc006058 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockPreformatted.html @@ -0,0 +1,152 @@ + + + + + pageBlockPreformatted + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockPreformatted

+ +

Preformatted (<pre> text)

+

+ +
+
pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
languagestringProgramming language of preformatted text
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockPullquote.html b/data/core.telegram.org/constructor/pageBlockPullquote.html new file mode 100644 index 0000000000..ff8b351133 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockPullquote.html @@ -0,0 +1,152 @@ + + + + + pageBlockPullquote + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockPullquote

+ +

Pullquote

+

+ +
+
pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
captionRichTextCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockRelatedArticles.html b/data/core.telegram.org/constructor/pageBlockRelatedArticles.html new file mode 100644 index 0000000000..64f79422f3 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockRelatedArticles.html @@ -0,0 +1,152 @@ + + + + + pageBlockRelatedArticles + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockRelatedArticles

+ +

Related articles

+

+ +
+
pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
titleRichTextTitle
articlesVector<PageRelatedArticle>Related articles
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockSlideshow.html b/data/core.telegram.org/constructor/pageBlockSlideshow.html new file mode 100644 index 0000000000..dbf984b58b --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockSlideshow.html @@ -0,0 +1,152 @@ + + + + + pageBlockSlideshow + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockSlideshow

+ +

Slideshow

+

+ +
+
pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageBlock>Slideshow items
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockSubheader.html b/data/core.telegram.org/constructor/pageBlockSubheader.html new file mode 100644 index 0000000000..67ffc78d55 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockSubheader.html @@ -0,0 +1,147 @@ + + + + + pageBlockSubheader + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockSubheader

+ +

Subheader

+

+ +
+
pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextSubheader
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockSubtitle.html b/data/core.telegram.org/constructor/pageBlockSubtitle.html new file mode 100644 index 0000000000..56ecef710c --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockSubtitle.html @@ -0,0 +1,147 @@ + + + + + pageBlockSubtitle + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockSubtitle

+ +

Subtitle

+

+ +
+
pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockTitle.html b/data/core.telegram.org/constructor/pageBlockTitle.html new file mode 100644 index 0000000000..bf3d2ff4ef --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockTitle.html @@ -0,0 +1,147 @@ + + + + + pageBlockTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockTitle

+ +

Title

+

+ +
+
pageBlockTitle#70abc3fd text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextTitle
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockUnsupported.html b/data/core.telegram.org/constructor/pageBlockUnsupported.html new file mode 100644 index 0000000000..a2fc55c003 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockUnsupported.html @@ -0,0 +1,132 @@ + + + + + pageBlockUnsupported + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockUnsupported

+ +

Unsupported IV element

+

+ +
+
pageBlockUnsupported#13567e8a = PageBlock;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockVideo.html b/data/core.telegram.org/constructor/pageBlockVideo.html new file mode 100644 index 0000000000..662ddf3ab6 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockVideo.html @@ -0,0 +1,167 @@ + + + + + pageBlockVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockVideo

+ +

Video

+

+ +
+
pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
autoplayflags.0?trueWhether the video is set to autoplay
loopflags.1?trueWhether the video is set to loop
video_idlongVideo ID
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageCaption.html b/data/core.telegram.org/constructor/pageCaption.html new file mode 100644 index 0000000000..9604f73951 --- /dev/null +++ b/data/core.telegram.org/constructor/pageCaption.html @@ -0,0 +1,152 @@ + + + + + pageCaption + + + + + + + + + + + + + +
+ +
+
+
+ +

pageCaption

+ +

Page caption

+

+ +
+
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextCaption
creditRichTextCredits
+

Type

+

PageCaption

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageListItemBlocks.html b/data/core.telegram.org/constructor/pageListItemBlocks.html new file mode 100644 index 0000000000..93be908282 --- /dev/null +++ b/data/core.telegram.org/constructor/pageListItemBlocks.html @@ -0,0 +1,147 @@ + + + + + pageListItemBlocks + + + + + + + + + + + + + +
+ +
+
+
+ +

pageListItemBlocks

+ +

List item

+

+ +
+
pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
blocksVector<PageBlock>Blocks
+

Type

+

PageListItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageListItemText.html b/data/core.telegram.org/constructor/pageListItemText.html new file mode 100644 index 0000000000..b04f4f3b02 --- /dev/null +++ b/data/core.telegram.org/constructor/pageListItemText.html @@ -0,0 +1,147 @@ + + + + + pageListItemText + + + + + + + + + + + + + +
+ +
+
+
+ +

pageListItemText

+ +

List item

+

+ +
+
pageListItemText#b92fb6cd text:RichText = PageListItem;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

PageListItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageListOrderedItemBlocks.html b/data/core.telegram.org/constructor/pageListOrderedItemBlocks.html new file mode 100644 index 0000000000..f4ffdb10f5 --- /dev/null +++ b/data/core.telegram.org/constructor/pageListOrderedItemBlocks.html @@ -0,0 +1,152 @@ + + + + + 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/core.telegram.org/constructor/pageListOrderedItemText.html b/data/core.telegram.org/constructor/pageListOrderedItemText.html new file mode 100644 index 0000000000..12982f75d7 --- /dev/null +++ b/data/core.telegram.org/constructor/pageListOrderedItemText.html @@ -0,0 +1,152 @@ + + + + + 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 new file mode 100644 index 0000000000..2a0691b04c --- /dev/null +++ b/data/core.telegram.org/constructor/pageRelatedArticle.html @@ -0,0 +1,182 @@ + + + + + pageRelatedArticle + + + + + + + + + + + + + +
+ +
+
+
+ +

pageRelatedArticle

+ +

Related article

+

+ +
+
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of article
webpage_idlongWebpage ID of generated IV preview
titleflags.0?stringTitle
descriptionflags.1?stringDescription
photo_idflags.2?longID of preview photo
authorflags.3?stringAuthor name
published_dateflags.4?intDate of pubblication
+

Type

+

PageRelatedArticle

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageTableCell.html b/data/core.telegram.org/constructor/pageTableCell.html new file mode 100644 index 0000000000..dd1952dc1e --- /dev/null +++ b/data/core.telegram.org/constructor/pageTableCell.html @@ -0,0 +1,187 @@ + + + + + pageTableCell + + + + + + + + + + + + + +
+ +
+
+
+ +

pageTableCell

+ +

Table cell

+

+ +
+
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
headerflags.0?trueIs this element part of the column header
align_centerflags.3?trueHorizontally centered block
align_rightflags.4?trueRight-aligned block
valign_middleflags.5?trueVertically centered block
valign_bottomflags.6?trueBlock vertically-alligned to the bottom
textflags.7?RichTextContent
colspanflags.1?intFor how many columns should this cell extend
rowspanflags.2?intFor how many rows should this cell extend
+

Type

+

PageTableCell

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageTableRow.html b/data/core.telegram.org/constructor/pageTableRow.html new file mode 100644 index 0000000000..41fe78d3f3 --- /dev/null +++ b/data/core.telegram.org/constructor/pageTableRow.html @@ -0,0 +1,147 @@ + + + + + pageTableRow + + + + + + + + + + + + + +
+ +
+
+
+ +

pageTableRow

+ +

Table row

+

+ +
+
pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
cellsVector<PageTableCell>Table cells
+

Type

+

PageTableRow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html b/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html new file mode 100644 index 0000000000..c0c099b198 --- /dev/null +++ b/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html @@ -0,0 +1,165 @@ + + + + + passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow + + + + + + + + + + + + + +
+ +
+
+
+ +

passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow

+ +

This key derivation algorithm defines that SRP 2FA login must be used

+

+ +
+
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
salt1bytesOne of two salts used by the derivation function (see SRP 2FA login)
salt2bytesOne of two salts used by the derivation function (see SRP 2FA login)
gintBase (see SRP 2FA login)
pbytes2048-bit modulus (see SRP 2FA login)
+

Type

+

PasswordKdfAlgo

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html b/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html new file mode 100644 index 0000000000..13e8c3ab09 --- /dev/null +++ b/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..2479c9f5c4 --- /dev/null +++ b/data/core.telegram.org/constructor/paymentCharge.html @@ -0,0 +1,152 @@ + + + + + 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 new file mode 100644 index 0000000000..2e8b57c64b --- /dev/null +++ b/data/core.telegram.org/constructor/paymentRequestedInfo.html @@ -0,0 +1,167 @@ + + + + + paymentRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

paymentRequestedInfo

+ +

Order info provided by the user

+

+ +
+
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
nameflags.0?stringUser's full name
phoneflags.1?stringUser's phone number
emailflags.2?stringUser's email address
shipping_addressflags.3?PostAddressUser's shipping address
+

Type

+

PaymentRequestedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html b/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html new file mode 100644 index 0000000000..2ed138c16c --- /dev/null +++ b/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html @@ -0,0 +1,152 @@ + + + + + paymentSavedCredentialsCard + + + + + + + + + + + + + +
+ +
+
+
+ +

paymentSavedCredentialsCard

+ +

Saved credit card

+

+ +
+
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringCard ID
titlestringTitle
+

Type

+

PaymentSavedCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo b/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo new file mode 100644 index 0000000000..4a81460ed0 --- /dev/null +++ b/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo @@ -0,0 +1,145 @@ + + + + + payments.ValidatedRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.ValidatedRequestedInfo

+ +

Validated user-provided info

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idflags.0?stringID
shipping_optionsflags.1?Vector<ShippingOption>Shipping options
+

Type

+

payments.ValidatedRequestedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.bankCardData b/data/core.telegram.org/constructor/payments.bankCardData new file mode 100644 index 0000000000..eb3fe8753d --- /dev/null +++ b/data/core.telegram.org/constructor/payments.bankCardData @@ -0,0 +1,152 @@ + + + + + payments.bankCardData + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.bankCardData

+ +

Credit card info, provided by the card's bank(s)

+

+ +
+
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
titlestringCredit card title
open_urlsVector<BankCardOpenUrl>Info URL(s) provided by the card's bank(s)
+

Type

+

payments.BankCardData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.paymentForm b/data/core.telegram.org/constructor/payments.paymentForm new file mode 100644 index 0000000000..920813f6f6 --- /dev/null +++ b/data/core.telegram.org/constructor/payments.paymentForm @@ -0,0 +1,210 @@ + + + + + payments.paymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentForm

+ +

Payment form

+

+ +
+
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_save_credentialsflags.2?trueWhether the user can choose to save credentials.
password_missingflags.3?trueIndicates that the user can save payment credentials, but only after setting up a 2FA password (currently the account doesn't have a 2FA password)
form_idlongForm ID
bot_idlongBot ID
invoiceInvoiceInvoice
provider_idlongPayment provider ID.
urlstringPayment form URL
native_providerflags.4?stringPayment provider name.
One of the following:
- stripe
native_paramsflags.4?DataJSONContains information about the payment provider, if available, to support it natively without the need for opening the URL.
A JSON object that can contain the following fields:

- apple_pay_merchant_id: Apple Pay merchant ID
- google_pay_public_key: Google Pay public key
- need_country: True, if the user country must be provided,
- need_zip: True, if the user ZIP/postal code must be provided,
- need_cardholder_name: True, if the cardholder name must be provided
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
saved_credentialsflags.1?PaymentSavedCredentialsContains information about saved card credentials
usersVector<User>Users
+

Type

+

payments.PaymentForm

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.paymentReceipt b/data/core.telegram.org/constructor/payments.paymentReceipt new file mode 100644 index 0000000000..a8a7696e9b --- /dev/null +++ b/data/core.telegram.org/constructor/payments.paymentReceipt @@ -0,0 +1,219 @@ + + + + + payments.paymentReceipt + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentReceipt

+ +

Receipt

+

+ +
+
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
dateintDate of generation
bot_idlongBot ID
provider_idlongProvider ID
titlestringTitle
descriptionstringDescription
photoflags.2?WebDocumentPhoto
invoiceInvoiceInvoice
infoflags.0?PaymentRequestedInfoInfo
shippingflags.1?ShippingOptionSelected shipping option
tip_amountflags.3?longTipped amount
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
credentials_titlestringPayment credential name
usersVector<User>Users
+

Type

+

payments.PaymentReceipt

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.paymentResult b/data/core.telegram.org/constructor/payments.paymentResult new file mode 100644 index 0000000000..5306a7d5c5 --- /dev/null +++ b/data/core.telegram.org/constructor/payments.paymentResult @@ -0,0 +1,147 @@ + + + + + payments.paymentResult + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentResult

+ +

Payment result

+

+ +
+
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
updatesUpdatesInfo about the payment
+

Type

+

payments.PaymentResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.paymentVerificationNeeded b/data/core.telegram.org/constructor/payments.paymentVerificationNeeded new file mode 100644 index 0000000000..836c7e1c85 --- /dev/null +++ b/data/core.telegram.org/constructor/payments.paymentVerificationNeeded @@ -0,0 +1,147 @@ + + + + + payments.paymentVerificationNeeded + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentVerificationNeeded

+ +

Payment was not successful, additional verification is needed

+

+ +
+
payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL for additional payment credentials verification
+

Type

+

payments.PaymentResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.savedInfo b/data/core.telegram.org/constructor/payments.savedInfo new file mode 100644 index 0000000000..2cedcbe780 --- /dev/null +++ b/data/core.telegram.org/constructor/payments.savedInfo @@ -0,0 +1,157 @@ + + + + + payments.savedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.savedInfo

+ +

Saved server-side order information

+

+ +
+
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_saved_credentialsflags.1?trueWhether the user has some saved payment credentials
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
+

Type

+

payments.SavedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerBlocked.html b/data/core.telegram.org/constructor/peerBlocked.html new file mode 100644 index 0000000000..1b3bf106a5 --- /dev/null +++ b/data/core.telegram.org/constructor/peerBlocked.html @@ -0,0 +1,152 @@ + + + + + peerBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

peerBlocked

+ +

Information about a blocked peer

+

+ +
+
peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peer_idPeerPeer ID
dateintWhen was the peer blocked
+

Type

+

PeerBlocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerChannel.html b/data/core.telegram.org/constructor/peerChannel.html new file mode 100644 index 0000000000..514c9c0dec --- /dev/null +++ b/data/core.telegram.org/constructor/peerChannel.html @@ -0,0 +1,147 @@ + + + + + peerChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

peerChannel

+ +

Channel/supergroup

+

+ +
+
peerChannel#a2a5371e channel_id:long = Peer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
+

Type

+

Peer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerChat.html b/data/core.telegram.org/constructor/peerChat.html new file mode 100644 index 0000000000..2abfcb727a --- /dev/null +++ b/data/core.telegram.org/constructor/peerChat.html @@ -0,0 +1,147 @@ + + + + + peerChat + + + + + + + + + + + + + +
+ +
+
+
+ +

peerChat

+ +

Group.

+

+ +
+
peerChat#36c6019a chat_id:long = Peer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup identifier
+

Type

+

Peer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerLocated.html b/data/core.telegram.org/constructor/peerLocated.html new file mode 100644 index 0000000000..ead8d9e2e3 --- /dev/null +++ b/data/core.telegram.org/constructor/peerLocated.html @@ -0,0 +1,157 @@ + + + + + peerLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

peerLocated

+ +

Peer geolocated nearby

+

+ +
+
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
expiresintValidity period of current data
distanceintDistance from the peer in meters
+

Type

+

PeerLocated

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerNotifySettings.html b/data/core.telegram.org/constructor/peerNotifySettings.html new file mode 100644 index 0000000000..1a8febde59 --- /dev/null +++ b/data/core.telegram.org/constructor/peerNotifySettings.html @@ -0,0 +1,182 @@ + + + + + peerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

peerNotifySettings

+ +

Notification settings.

+

+ +
+
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolDisplay text in notifications
silentflags.1?BoolMute peer?
mute_untilflags.2?intMute all notifications until this date
soundflags.3?stringAudio file name for notifications
+

Type

+

PeerNotifySettings

+

Event flags (events_mask)

+ + + + + + + + + + + + + +
0x00000001Profile photo update notification
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerSelfLocated.html b/data/core.telegram.org/constructor/peerSelfLocated.html new file mode 100644 index 0000000000..c67b1f8860 --- /dev/null +++ b/data/core.telegram.org/constructor/peerSelfLocated.html @@ -0,0 +1,147 @@ + + + + + peerSelfLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

peerSelfLocated

+ +

Current peer

+

+ +
+
peerSelfLocated#f8ec284b expires:int = PeerLocated;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintExpiry of geolocation info for current peer
+

Type

+

PeerLocated

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerSettings.html b/data/core.telegram.org/constructor/peerSettings.html new file mode 100644 index 0000000000..adbec89557 --- /dev/null +++ b/data/core.telegram.org/constructor/peerSettings.html @@ -0,0 +1,197 @@ + + + + + peerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

peerSettings

+ +

Peer settings

+

+ +
+
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
report_spamflags.0?trueWhether we can still report the user for spam
add_contactflags.1?trueWhether we can add the user as contact
block_contactflags.2?trueWhether we can block the user
share_contactflags.3?trueWhether we can share the user's contact
need_contacts_exceptionflags.4?trueWhether a special exception for contacts is needed
report_geoflags.5?trueWhether we can report a geogroup is irrelevant for this location
autoarchivedflags.7?trueWhether this peer was automatically archived according to privacy settings
invite_membersflags.8?trueWhether we can invite members to a group or channel
geo_distanceflags.6?intDistance in meters between us and this peer
+

Type

+

PeerSettings

+

Related pages

+

globalPrivacySettings

+

Global privacy settings

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phone.exportedGroupCallInvite b/data/core.telegram.org/constructor/phone.exportedGroupCallInvite new file mode 100644 index 0000000000..34667582aa --- /dev/null +++ b/data/core.telegram.org/constructor/phone.exportedGroupCallInvite @@ -0,0 +1,147 @@ + + + + + phone.exportedGroupCallInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.exportedGroupCallInvite

+ +

An invite to a group call or livestream

+

+ +
+
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
linkstringInvite link
+

Type

+

phone.ExportedGroupCallInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phone.groupCall b/data/core.telegram.org/constructor/phone.groupCall new file mode 100644 index 0000000000..4cfc527411 --- /dev/null +++ b/data/core.telegram.org/constructor/phone.groupCall @@ -0,0 +1,170 @@ + + + + + phone.groupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.groupCall

+ +

Contains info about a group call, and partial info about its participants.

+

+ +
+
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callGroupCallInfo about the group call
participantsVector<GroupCallParticipant>A partial list of participants.
participants_next_offsetstringNext offset to use when fetching the remaining participants using phone.getGroupParticipants
chatsVector<Chat>Chats mentioned in the participants vector
usersVector<User>Users mentioned in the participants vector
+

Type

+

phone.GroupCall

+

Related pages

+

phone.getGroupParticipants

+

Get group call participants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phone.groupParticipants b/data/core.telegram.org/constructor/phone.groupParticipants new file mode 100644 index 0000000000..639e22c978 --- /dev/null +++ b/data/core.telegram.org/constructor/phone.groupParticipants @@ -0,0 +1,175 @@ + + + + + phone.groupParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.groupParticipants

+ +

Info about the participants of a group call or livestream

+

+ +
+
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of participants
participantsVector<GroupCallParticipant>List of participants
next_offsetstringIf not empty, the specified list of participants is partial, and more participants can be fetched specifying this parameter as offset in phone.getGroupParticipants.
chatsVector<Chat>Mentioned chats
usersVector<User>Mentioned users
versionintVersion info
+

Type

+

phone.GroupParticipants

+

Related pages

+

phone.getGroupParticipants

+

Get group call participants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phone.joinAsPeers b/data/core.telegram.org/constructor/phone.joinAsPeers new file mode 100644 index 0000000000..9da076f9c0 --- /dev/null +++ b/data/core.telegram.org/constructor/phone.joinAsPeers @@ -0,0 +1,157 @@ + + + + + phone.joinAsPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.joinAsPeers

+ +

A list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+

+ +
+
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peersVector<Peer>Peers
chatsVector<Chat>Chats mentioned in the peers vector
usersVector<User>Users mentioned in the peers vector
+

Type

+

phone.JoinAsPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phone.phoneCall b/data/core.telegram.org/constructor/phone.phoneCall new file mode 100644 index 0000000000..fc55a16006 --- /dev/null +++ b/data/core.telegram.org/constructor/phone.phoneCall @@ -0,0 +1,152 @@ + + + + + phone.phoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.phoneCall

+ +

A VoIP phone call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_callPhoneCallThe VoIP phone call
usersVector<User>VoIP phone call participants
+

Type

+

phone.PhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCall.html b/data/core.telegram.org/constructor/phoneCall.html new file mode 100644 index 0000000000..dcba9dafe1 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCall.html @@ -0,0 +1,209 @@ + + + + + phoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCall

+ +

Phone call

+

+ +
+
phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
p2p_allowedflags.5?trueWhether P2P connection to the other peer is allowed
videoflags.6?trueWhether this is a video call
idlongCall ID
access_hashlongAccess hash
dateintDate of creation of the call
admin_idlongUser ID of the creator of the call
participant_idlongUser ID of the other participant in the call
g_a_or_bbytesParameter for key exchange
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
connectionsVector<PhoneConnection>List of endpoints the user can connect to to exchange call data
start_dateintWhen was the call actually started
+

Type

+

PhoneCall

+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallAccepted.html b/data/core.telegram.org/constructor/phoneCallAccepted.html new file mode 100644 index 0000000000..86e8ad2759 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallAccepted.html @@ -0,0 +1,189 @@ + + + + + phoneCallAccepted + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallAccepted

+ +

An accepted phone call

+

+ +
+
phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueWhether this is a video call
idlongID of accepted phone call
access_hashlongAccess hash of phone call
dateintWhen was the call accepted
admin_idlongID of the call creator
participant_idlongID of the other user in the call
g_bbytesB parameter for secure E2E phone call key exchange
protocolPhoneCallProtocolProtocol to use for phone call
+

Type

+

PhoneCall

+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html new file mode 100644 index 0000000000..123c8f66b9 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonBusy + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonBusy

+ +

The phone call was discared because the user is busy in another call

+

+ +
+
phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html new file mode 100644 index 0000000000..d736931a9a --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonDisconnect + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonDisconnect

+ +

The phone call was disconnected

+

+ +
+
phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html new file mode 100644 index 0000000000..a79d8d0bdd --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonHangup + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonHangup

+ +

The phone call was ended normally

+

+ +
+
phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html new file mode 100644 index 0000000000..9283cfeec6 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonMissed + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonMissed

+ +

The phone call was missed

+

+ +
+
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallDiscarded.html b/data/core.telegram.org/constructor/phoneCallDiscarded.html new file mode 100644 index 0000000000..b3a32314fc --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallDiscarded.html @@ -0,0 +1,182 @@ + + + + + phoneCallDiscarded + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscarded

+ +

Indicates a discarded phone call

+

+ +
+
phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
need_ratingflags.2?trueWhether the server required the user to rate the call
need_debugflags.3?trueWhether the server required the client to send the libtgvoip call debug data
videoflags.6?trueWhether the call was a video call
idlongCall ID
reasonflags.0?PhoneCallDiscardReasonWhy was the phone call discarded
durationflags.1?intDuration of the phone call in seconds
+

Type

+

PhoneCall

+

Related pages

+

phone.setCallRating

+

Rate a call

+

phone.saveCallDebug

+

Send phone call debug data to server

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallEmpty.html b/data/core.telegram.org/constructor/phoneCallEmpty.html new file mode 100644 index 0000000000..9dc5d77a93 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallEmpty.html @@ -0,0 +1,147 @@ + + + + + phoneCallEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallEmpty

+ +

Empty constructor

+

+ +
+
phoneCallEmpty#5366c915 id:long = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongCall ID
+

Type

+

PhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallProtocol.html b/data/core.telegram.org/constructor/phoneCallProtocol.html new file mode 100644 index 0000000000..65e1a9db31 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallProtocol.html @@ -0,0 +1,179 @@ + + + + + phoneCallProtocol + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallProtocol

+ +

Protocol info for libtgvoip

+

+ +
+
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
udp_p2pflags.0?trueWhether to allow P2P connection to the other participant
udp_reflectorflags.1?trueWhether to allow connection to the other participants through the reflector servers
min_layerintMinimum layer for remote libtgvoip
max_layerintMaximum layer for remote libtgvoip
library_versionsVector<string>When using phone.requestCall and phone.acceptCall, specify all library versions supported by the client.
The server will merge and choose the best library version supported by both peers, returning only the best value in the result of the callee's phone.acceptCall and in the phoneCallAccepted update received by the caller.
+

Type

+

PhoneCallProtocol

+

Related pages

+

phone.requestCall

+

Start a telegram phone call

+

phone.acceptCall

+

Accept incoming call

+

phoneCallAccepted

+

An accepted phone call

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallRequested.html b/data/core.telegram.org/constructor/phoneCallRequested.html new file mode 100644 index 0000000000..34eb4e4dd2 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallRequested.html @@ -0,0 +1,189 @@ + + + + + phoneCallRequested + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallRequested

+ +

Requested phone call

+

+ +
+
phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueWhether this is a video call
idlongPhone call ID
access_hashlongAccess hash
dateintWhen was the phone call created
admin_idlongID of the creator of the phone call
participant_idlongID of the other participant of the phone call
g_a_hashbytesParameter for key exchange
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
+

Type

+

PhoneCall

+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallWaiting.html b/data/core.telegram.org/constructor/phoneCallWaiting.html new file mode 100644 index 0000000000..e0ea1c39ef --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallWaiting.html @@ -0,0 +1,187 @@ + + + + + phoneCallWaiting + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallWaiting

+ +

Incoming phone call

+

+ +
+
phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueIs this a video call
idlongCall ID
access_hashlongAccess hash
dateintDate
admin_idlongAdmin ID
participant_idlongParticipant ID
protocolPhoneCallProtocolPhone call protocol info
receive_dateflags.0?intWhen was the phone call received
+

Type

+

PhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneConnection.html b/data/core.telegram.org/constructor/phoneConnection.html new file mode 100644 index 0000000000..3d716a6502 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneConnection.html @@ -0,0 +1,167 @@ + + + + + phoneConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneConnection

+ +

Identifies an endpoint that can be used to connect to the other user in a phone call

+

+ +
+
phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongEndpoint ID
ipstringIP address of endpoint
ipv6stringIPv6 address of endpoint
portintPort ID
peer_tagbytesOur peer tag
+

Type

+

PhoneConnection

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneConnectionWebrtc.html b/data/core.telegram.org/constructor/phoneConnectionWebrtc.html new file mode 100644 index 0000000000..4a9891e060 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneConnectionWebrtc.html @@ -0,0 +1,187 @@ + + + + + phoneConnectionWebrtc + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneConnectionWebrtc

+ +

WebRTC connection parameters

+

+ +
+
phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
turnflags.0?trueWhether this is a TURN endpoint
stunflags.1?trueWhether this is a STUN endpoint
idlongEndpoint ID
ipstringIP address
ipv6stringIPv6 address
portintPort
usernamestringUsername
passwordstringPassword
+

Type

+

PhoneConnection

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photo.html b/data/core.telegram.org/constructor/photo.html new file mode 100644 index 0000000000..9d1e2ee6fd --- /dev/null +++ b/data/core.telegram.org/constructor/photo.html @@ -0,0 +1,192 @@ + + + + + photo + + + + + + + + + + + + + +
+ +
+
+
+ +

photo

+ +

Photo

+

+ +
+
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_stickersflags.0?trueWhether the photo has mask stickers attached to it
idlongID
access_hashlongAccess hash
file_referencebytesfile reference
dateintDate of upload
sizesVector<PhotoSize>Available sizes for download
video_sizesflags.1?Vector<VideoSize>For animated profiles, the MPEG4 videos
dc_idintDC ID to use for download
+

Type

+

Photo

+

Related pages

+

File references

+

How to handle file references.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photoCachedSize.html b/data/core.telegram.org/constructor/photoCachedSize.html new file mode 100644 index 0000000000..15adf1e61a --- /dev/null +++ b/data/core.telegram.org/constructor/photoCachedSize.html @@ -0,0 +1,167 @@ + + + + + photoCachedSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoCachedSize

+ +

Description of an image and its content.

+

+ +
+
photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
bytesbytesBinary data, file content
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See here.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photoPathSize.html b/data/core.telegram.org/constructor/photoPathSize.html new file mode 100644 index 0000000000..51ffd63c8a --- /dev/null +++ b/data/core.telegram.org/constructor/photoPathSize.html @@ -0,0 +1,155 @@ + + + + + photoPathSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoPathSize

+ +

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.

+

+ +
+
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringAlways j
bytesbytesCompressed SVG path payload, see here for decompression instructions
+

Type

+

PhotoSize

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photoSize.html b/data/core.telegram.org/constructor/photoSize.html new file mode 100644 index 0000000000..6b9a13a466 --- /dev/null +++ b/data/core.telegram.org/constructor/photoSize.html @@ -0,0 +1,167 @@ + + + + + photoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoSize

+ +

Image description.

+

+ +
+
photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
sizeintFile size
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See here.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photoSizeEmpty.html b/data/core.telegram.org/constructor/photoSizeEmpty.html new file mode 100644 index 0000000000..f32028a6ae --- /dev/null +++ b/data/core.telegram.org/constructor/photoSizeEmpty.html @@ -0,0 +1,150 @@ + + + + + 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 new file mode 100644 index 0000000000..04f09890b3 --- /dev/null +++ b/data/core.telegram.org/constructor/photoSizeProgressive.html @@ -0,0 +1,167 @@ + + + + + photoSizeProgressive + + + + + + + + + + + + + +
+ +
+
+
+ +

photoSizeProgressive

+ +

Progressively encoded photosize

+

+ +
+
photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringPhotosize type
wintPhoto width
hintPhoto height
sizesVector<int>Sizes of progressive JPEG file prefixes, which can be used to preliminarily show the image.
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See here.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photoStrippedSize.html b/data/core.telegram.org/constructor/photoStrippedSize.html new file mode 100644 index 0000000000..6fb252ccfb --- /dev/null +++ b/data/core.telegram.org/constructor/photoStrippedSize.html @@ -0,0 +1,159 @@ + + + + + photoStrippedSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoStrippedSize

+ +

A low-resolution compressed JPG payload

+

+ +
+
photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type
bytesbytesThumbnail data, see here for more info on decompression »
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See the photoSize constructor.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

photoSize

+

Image description.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photos.photo b/data/core.telegram.org/constructor/photos.photo new file mode 100644 index 0000000000..cdd463d8b2 --- /dev/null +++ b/data/core.telegram.org/constructor/photos.photo @@ -0,0 +1,152 @@ + + + + + photos.photo + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.photo

+ +

Photo with auxiliary data.

+

+ +
+
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
photoPhotoPhoto
usersVector<User>Users
+

Type

+

photos.Photo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photos.photos b/data/core.telegram.org/constructor/photos.photos new file mode 100644 index 0000000000..8e11ec97d4 --- /dev/null +++ b/data/core.telegram.org/constructor/photos.photos @@ -0,0 +1,152 @@ + + + + + photos.photos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.photos

+ +

Full list of photos with auxiliary data.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
+

Type

+

photos.Photos

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photos.photosSlice b/data/core.telegram.org/constructor/photos.photosSlice new file mode 100644 index 0000000000..5ea78e2a0c --- /dev/null +++ b/data/core.telegram.org/constructor/photos.photosSlice @@ -0,0 +1,157 @@ + + + + + photos.photosSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.photosSlice

+ +

Incomplete list of photos with auxiliary data.

+

+ +
+
photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of photos
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
+

Type

+

photos.Photos

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/poll.html b/data/core.telegram.org/constructor/poll.html new file mode 100644 index 0000000000..55d47dbc5d --- /dev/null +++ b/data/core.telegram.org/constructor/poll.html @@ -0,0 +1,195 @@ + + + + + poll + + + + + + + + + + + + + +
+ +
+
+
+ +

poll

+ +

Poll

+

+ +
+
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID of the poll
flags#Flags, see TL conditional fields
closedflags.0?trueWhether the poll is closed and doesn't accept any more answers
public_votersflags.1?trueWhether cast votes are publicly visible to all users (non-anonymous poll)
multiple_choiceflags.2?trueWhether multiple options can be chosen as answer
quizflags.3?trueWhether this is a quiz (with wrong and correct answers, results shown in the return type)
questionstringThe question of the poll
answersVector<PollAnswer>The possible answers, vote using messages.sendVote.
close_periodflags.4?intAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateflags.5?intPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period.
+

Type

+

Poll

+

Related pages

+

messages.sendVote

+

Vote in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pollAnswer.html b/data/core.telegram.org/constructor/pollAnswer.html new file mode 100644 index 0000000000..92870d7ac6 --- /dev/null +++ b/data/core.telegram.org/constructor/pollAnswer.html @@ -0,0 +1,155 @@ + + + + + pollAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

pollAnswer

+ +

A possible answer of a poll

+

+ +
+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstringTextual representation of the answer
optionbytesThe param that has to be passed to messages.sendVote.
+

Type

+

PollAnswer

+

Related pages

+

messages.sendVote

+

Vote in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pollAnswerVoters.html b/data/core.telegram.org/constructor/pollAnswerVoters.html new file mode 100644 index 0000000000..494b0a6316 --- /dev/null +++ b/data/core.telegram.org/constructor/pollAnswerVoters.html @@ -0,0 +1,170 @@ + + + + + pollAnswerVoters + + + + + + + + + + + + + +
+ +
+
+
+ +

pollAnswerVoters

+ +

A poll answer, and how users voted on it

+

+ +
+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
chosenflags.0?trueWhether we have chosen this answer
correctflags.1?trueFor quizes, whether the option we have chosen is correct
optionbytesThe param that has to be passed to messages.sendVote.
votersintHow many users voted for this option
+

Type

+

PollAnswerVoters

+

Related pages

+

messages.sendVote

+

Vote in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pollResults.html b/data/core.telegram.org/constructor/pollResults.html new file mode 100644 index 0000000000..f21c0eb9c6 --- /dev/null +++ b/data/core.telegram.org/constructor/pollResults.html @@ -0,0 +1,184 @@ + + + + + pollResults + + + + + + + + + + + + + +
+ +
+
+
+ +

pollResults

+ +

Results of poll

+

+ +
+
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
minflags.0?trueSimilar to min objects, used for poll constructors that are the same for all users so they don't have option chosen by the current user (you can use messages.getPollResults to get the full poll results).
resultsflags.1?Vector<PollAnswerVoters>Poll results
total_votersflags.2?intTotal number of people that voted in the poll
recent_votersflags.3?Vector<long>IDs of the last users that recently voted in the poll
solutionflags.4?stringExplanation of quiz solution
solution_entitiesflags.4?Vector<MessageEntity>Message entities for styled text in quiz solution
+

Type

+

PollResults

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

messages.getPollResults

+

Get poll results

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/popularContact.html b/data/core.telegram.org/constructor/popularContact.html new file mode 100644 index 0000000000..f3cb71e9a6 --- /dev/null +++ b/data/core.telegram.org/constructor/popularContact.html @@ -0,0 +1,152 @@ + + + + + popularContact + + + + + + + + + + + + + +
+ +
+
+
+ +

popularContact

+ +

Popular contact

+

+ +
+
popularContact#5ce14175 client_id:long importers:int = PopularContact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
client_idlongContact identifier
importersintHow many people imported this contact
+

Type

+

PopularContact

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/postAddress.html b/data/core.telegram.org/constructor/postAddress.html new file mode 100644 index 0000000000..a278e6fd1e --- /dev/null +++ b/data/core.telegram.org/constructor/postAddress.html @@ -0,0 +1,172 @@ + + + + + postAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

postAddress

+ +

Shipping address

+

+ +
+
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
street_line1stringFirst line for the address
street_line2stringSecond line for the address
citystringCity
statestringState, if applicable (empty otherwise)
country_iso2stringISO 3166-1 alpha-2 country code
post_codestringAddress post code
+

Type

+

PostAddress

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html b/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html new file mode 100644 index 0000000000..90dde99417 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html @@ -0,0 +1,132 @@ + + + + + privacyKeyAddedByPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyAddedByPhone

+ +

Whether people can add you to their contact list by your phone number

+

+ +
+
privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyKeyChatInvite.html b/data/core.telegram.org/constructor/privacyKeyChatInvite.html new file mode 100644 index 0000000000..acdb7d4a55 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyKeyChatInvite.html @@ -0,0 +1,132 @@ + + + + + privacyKeyChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyChatInvite

+ +

Whether the user can be invited to chats

+

+ +
+
privacyKeyChatInvite#500e6dfa = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyKeyForwards.html b/data/core.telegram.org/constructor/privacyKeyForwards.html new file mode 100644 index 0000000000..27ac48e238 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyKeyForwards.html @@ -0,0 +1,132 @@ + + + + + privacyKeyForwards + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyForwards

+ +

Whether messages forwarded from the user will be anonymously forwarded

+

+ +
+
privacyKeyForwards#69ec56a3 = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyKeyPhoneCall.html b/data/core.telegram.org/constructor/privacyKeyPhoneCall.html new file mode 100644 index 0000000000..0fb27a24e1 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyKeyPhoneCall.html @@ -0,0 +1,132 @@ + + + + + privacyKeyPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyPhoneCall

+ +

Whether the user accepts phone calls

+

+ +
+
privacyKeyPhoneCall#3d662b7b = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html b/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html new file mode 100644 index 0000000000..96dcfcf675 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html @@ -0,0 +1,132 @@ + + + + + privacyKeyPhoneP2P + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyPhoneP2P

+ +

Whether P2P connections in phone calls are allowed

+

+ +
+
privacyKeyPhoneP2P#39491cc8 = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html b/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html new file mode 100644 index 0000000000..44ae3b03f2 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html @@ -0,0 +1,132 @@ + + + + + privacyKeyStatusTimestamp + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyStatusTimestamp

+ +

Whether we can see the last online timestamp

+

+ +
+
privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyValueAllowAll.html b/data/core.telegram.org/constructor/privacyValueAllowAll.html new file mode 100644 index 0000000000..334775c79a --- /dev/null +++ b/data/core.telegram.org/constructor/privacyValueAllowAll.html @@ -0,0 +1,132 @@ + + + + + privacyValueAllowAll + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueAllowAll

+ +

Allow all users

+

+ +
+
privacyValueAllowAll#65427b82 = PrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html b/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html new file mode 100644 index 0000000000..9e1fb6d291 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html @@ -0,0 +1,147 @@ + + + + + privacyValueAllowChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueAllowChatParticipants

+ +

Allow all participants of certain chats

+

+ +
+
privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<long>Allowed chats
+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyValueAllowContacts.html b/data/core.telegram.org/constructor/privacyValueAllowContacts.html new file mode 100644 index 0000000000..b93c047dfc --- /dev/null +++ b/data/core.telegram.org/constructor/privacyValueAllowContacts.html @@ -0,0 +1,132 @@ + + + + + privacyValueAllowContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueAllowContacts

+ +

Allow all contacts

+

+ +
+
privacyValueAllowContacts#fffe1bac = PrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyValueDisallowChatParticipants.html b/data/core.telegram.org/constructor/privacyValueDisallowChatParticipants.html new file mode 100644 index 0000000000..6edaebacd4 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyValueDisallowChatParticipants.html @@ -0,0 +1,147 @@ + + + + + privacyValueDisallowChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueDisallowChatParticipants

+ +

Disallow only participants of certain chats

+

+ +
+
privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<long>Disallowed chats
+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyValueDisallowContacts.html b/data/core.telegram.org/constructor/privacyValueDisallowContacts.html new file mode 100644 index 0000000000..40cb335dcd --- /dev/null +++ b/data/core.telegram.org/constructor/privacyValueDisallowContacts.html @@ -0,0 +1,132 @@ + + + + + privacyValueDisallowContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueDisallowContacts

+ +

Disallow only contacts

+

+ +
+
privacyValueDisallowContacts#f888fa1a = PrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyValueDisallowUsers.html b/data/core.telegram.org/constructor/privacyValueDisallowUsers.html new file mode 100644 index 0000000000..e0f2dc77a6 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyValueDisallowUsers.html @@ -0,0 +1,147 @@ + + + + + privacyValueDisallowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueDisallowUsers

+ +

Disallow only certain users

+

+ +
+
privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<long>Disallowed users
+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/receivedNotifyMessage.html b/data/core.telegram.org/constructor/receivedNotifyMessage.html new file mode 100644 index 0000000000..369fba0239 --- /dev/null +++ b/data/core.telegram.org/constructor/receivedNotifyMessage.html @@ -0,0 +1,152 @@ + + + + + receivedNotifyMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

receivedNotifyMessage

+ +

Message ID, for which PUSH-notifications were cancelled.

+

+ +
+
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintMessage ID, for which PUSH-notifications were canceled
flagsintReserved for future use
+

Type

+

ReceivedNotifyMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/recentMeUrlChat.html b/data/core.telegram.org/constructor/recentMeUrlChat.html new file mode 100644 index 0000000000..366ba650bc --- /dev/null +++ b/data/core.telegram.org/constructor/recentMeUrlChat.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlChat + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlChat

+ +

Recent t.me link to a chat

+

+ +
+
recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringt.me URL
chat_idlongChat ID
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/recentMeUrlChatInvite.html b/data/core.telegram.org/constructor/recentMeUrlChatInvite.html new file mode 100644 index 0000000000..f01570470f --- /dev/null +++ b/data/core.telegram.org/constructor/recentMeUrlChatInvite.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlChatInvite

+ +

Recent t.me invite link to a chat

+

+ +
+
recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringt.me URL
chat_inviteChatInviteChat invitation
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/recentMeUrlStickerSet.html b/data/core.telegram.org/constructor/recentMeUrlStickerSet.html new file mode 100644 index 0000000000..11c7deb858 --- /dev/null +++ b/data/core.telegram.org/constructor/recentMeUrlStickerSet.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlStickerSet

+ +

Recent t.me stickerset installation URL

+

+ +
+
recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringt.me URL
setStickerSetCoveredStickerset
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/recentMeUrlUnknown.html b/data/core.telegram.org/constructor/recentMeUrlUnknown.html new file mode 100644 index 0000000000..48665c4550 --- /dev/null +++ b/data/core.telegram.org/constructor/recentMeUrlUnknown.html @@ -0,0 +1,147 @@ + + + + + recentMeUrlUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlUnknown

+ +

Unknown t.me url

+

+ +
+
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/recentMeUrlUser.html b/data/core.telegram.org/constructor/recentMeUrlUser.html new file mode 100644 index 0000000000..b035f11485 --- /dev/null +++ b/data/core.telegram.org/constructor/recentMeUrlUser.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlUser + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlUser

+ +

Recent t.me link to a user

+

+ +
+
recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL
user_idlongUser ID
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/replyInlineMarkup.html b/data/core.telegram.org/constructor/replyInlineMarkup.html new file mode 100644 index 0000000000..358df9d4e8 --- /dev/null +++ b/data/core.telegram.org/constructor/replyInlineMarkup.html @@ -0,0 +1,147 @@ + + + + + replyInlineMarkup + + + + + + + + + + + + + +
+ +
+
+
+ +

replyInlineMarkup

+ +

Bot or inline keyboard

+

+ +
+
replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
rowsVector<KeyboardButtonRow>Bot or inline keyboard rows
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/replyKeyboardForceReply.html b/data/core.telegram.org/constructor/replyKeyboardForceReply.html new file mode 100644 index 0000000000..39a8734fae --- /dev/null +++ b/data/core.telegram.org/constructor/replyKeyboardForceReply.html @@ -0,0 +1,162 @@ + + + + + replyKeyboardForceReply + + + + + + + + + + + + + +
+ +
+
+
+ +

replyKeyboardForceReply

+ +

Force the user to send a reply

+

+ +
+
replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
single_useflags.1?trueRequests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again.
selectiveflags.2?trueUse this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
Example: A user requests to change the bot‘s language, bot replies to the request with a keyboard to select the new language. Other users in the group don’t see the keyboard.
placeholderflags.3?stringThe placeholder to be shown in the input field when the keyboard is active; 1-64 characters.
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/replyKeyboardHide.html b/data/core.telegram.org/constructor/replyKeyboardHide.html new file mode 100644 index 0000000000..1e81784d4a --- /dev/null +++ b/data/core.telegram.org/constructor/replyKeyboardHide.html @@ -0,0 +1,152 @@ + + + + + replyKeyboardHide + + + + + + + + + + + + + +
+ +
+
+
+ +

replyKeyboardHide

+ +

Hide sent bot keyboard

+

+ +
+
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
selectiveflags.2?trueUse this flag if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/restrictionReason.html b/data/core.telegram.org/constructor/restrictionReason.html new file mode 100644 index 0000000000..101fe987d6 --- /dev/null +++ b/data/core.telegram.org/constructor/restrictionReason.html @@ -0,0 +1,158 @@ + + + + + restrictionReason + + + + + + + + + + + + + +
+ +
+
+
+ +

restrictionReason

+ +

Restriction reason.

+

Contains the reason why access to a certain object must be restricted. Clients are supposed to deny access to the channel if the platform field is equal to all or to the current platform (ios, android, wp, etc.). Platforms can be concatenated (ios-android, ios-wp), unknown platforms are to be ignored. The text is the error message that should be shown to the user.

+

+ +
+
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
platformstringPlatform identifier (ios, android, wp, all, etc.), can be concatenated with a dash as separator (android-ios, ios-wp, etc)
reasonstringRestriction reason (porno, terms, etc.)
textstringError message to be shown to the user
+

Type

+

RestrictionReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/savedPhoneContact.html b/data/core.telegram.org/constructor/savedPhoneContact.html new file mode 100644 index 0000000000..e450c1f02b --- /dev/null +++ b/data/core.telegram.org/constructor/savedPhoneContact.html @@ -0,0 +1,162 @@ + + + + + savedPhoneContact + + + + + + + + + + + + + +
+ +
+
+
+ +

savedPhoneContact

+ +

Saved contact

+

+ +
+
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phonestringPhone number
first_namestringFirst name
last_namestringLast name
dateintDate added
+

Type

+

SavedContact

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureCredentialsEncrypted.html b/data/core.telegram.org/constructor/secureCredentialsEncrypted.html new file mode 100644 index 0000000000..8aac7afa96 --- /dev/null +++ b/data/core.telegram.org/constructor/secureCredentialsEncrypted.html @@ -0,0 +1,159 @@ + + + + + secureCredentialsEncrypted + + + + + + + + + + + + + +
+ +
+
+
+ +

secureCredentialsEncrypted

+ +

Encrypted credentials required to decrypt telegram passport data.

+

+ +
+
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
databytesEncrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication, as described in decrypting data »
hashbytesData hash for data authentication as described in decrypting data »
secretbytesSecret, encrypted with the bot's public RSA key, required for data decryption as described in decrypting data »
+

Type

+

SecureCredentialsEncrypted

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureData.html b/data/core.telegram.org/constructor/secureData.html new file mode 100644 index 0000000000..5f46624a3e --- /dev/null +++ b/data/core.telegram.org/constructor/secureData.html @@ -0,0 +1,160 @@ + + + + + secureData + + + + + + + + + + + + + +
+ +
+
+
+ +

secureData

+ +

Secure passport data, for more info see the passport docs »

+

+ +
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
databytesData
data_hashbytesData hash
secretbytesSecret
+

Type

+

SecureData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureFile.html b/data/core.telegram.org/constructor/secureFile.html new file mode 100644 index 0000000000..e8f04136c0 --- /dev/null +++ b/data/core.telegram.org/constructor/secureFile.html @@ -0,0 +1,180 @@ + + + + + secureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

secureFile

+ +

Secure passport file, for more info see the passport docs »

+

+ +
+
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
sizeintFile size
dc_idintDC ID
dateintDate of upload
file_hashbytesFile hash
secretbytesSecret
+

Type

+

SecureFile

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureFileEmpty.html b/data/core.telegram.org/constructor/secureFileEmpty.html new file mode 100644 index 0000000000..e038aa90f8 --- /dev/null +++ b/data/core.telegram.org/constructor/secureFileEmpty.html @@ -0,0 +1,132 @@ + + + + + secureFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

secureFileEmpty

+ +

Empty constructor

+

+ +
+
secureFileEmpty#64199744 = SecureFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html new file mode 100644 index 0000000000..e261f3b770 --- /dev/null +++ b/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html @@ -0,0 +1,147 @@ + + + + + securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoPBKDF2HMACSHA512iter100000

+ +

PBKDF2 with SHA512 and 100000 iterations KDF algo

+

+ +
+
securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
saltbytesSalt
+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html new file mode 100644 index 0000000000..cc27b9b16d --- /dev/null +++ b/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html @@ -0,0 +1,147 @@ + + + + + securePasswordKdfAlgoSHA512 + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoSHA512

+ +

SHA512 KDF algo

+

+ +
+
securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
saltbytesSalt
+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html new file mode 100644 index 0000000000..efedcb8096 --- /dev/null +++ b/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html @@ -0,0 +1,132 @@ + + + + + securePasswordKdfAlgoUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoUnknown

+ +

Unknown KDF algo (most likely the client has to be updated)

+

+ +
+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/securePlainEmail.html b/data/core.telegram.org/constructor/securePlainEmail.html new file mode 100644 index 0000000000..3ffdc4669c --- /dev/null +++ b/data/core.telegram.org/constructor/securePlainEmail.html @@ -0,0 +1,150 @@ + + + + + securePlainEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

securePlainEmail

+ +

Email address to use in telegram passport: it must be verified, first ».

+

+ +
+
securePlainEmail#21ec5a5f email:string = SecurePlainData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emailstringEmail address
+

Type

+

SecurePlainData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/securePlainPhone.html b/data/core.telegram.org/constructor/securePlainPhone.html new file mode 100644 index 0000000000..68faa5d2ad --- /dev/null +++ b/data/core.telegram.org/constructor/securePlainPhone.html @@ -0,0 +1,150 @@ + + + + + securePlainPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

securePlainPhone

+ +

Phone number to use in telegram passport: it must be verified, first ».

+

+ +
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phonestringPhone number
+

Type

+

SecurePlainData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureRequiredType.html b/data/core.telegram.org/constructor/secureRequiredType.html new file mode 100644 index 0000000000..0ec1da6d0e --- /dev/null +++ b/data/core.telegram.org/constructor/secureRequiredType.html @@ -0,0 +1,167 @@ + + + + + secureRequiredType + + + + + + + + + + + + + +
+ +
+
+
+ +

secureRequiredType

+ +

Required type

+

+ +
+
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
native_namesflags.0?trueNative names
selfie_requiredflags.1?trueIs a selfie required
translation_requiredflags.2?trueIs a translation required
typeSecureValueTypeSecure value type
+

Type

+

SecureRequiredType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureRequiredTypeOneOf.html b/data/core.telegram.org/constructor/secureRequiredTypeOneOf.html new file mode 100644 index 0000000000..964273ab07 --- /dev/null +++ b/data/core.telegram.org/constructor/secureRequiredTypeOneOf.html @@ -0,0 +1,147 @@ + + + + + secureRequiredTypeOneOf + + + + + + + + + + + + + +
+ +
+
+
+ +

secureRequiredTypeOneOf

+ +

One of

+

+ +
+
secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typesVector<SecureRequiredType>Secure required value types
+

Type

+

SecureRequiredType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureSecretSettings.html b/data/core.telegram.org/constructor/secureSecretSettings.html new file mode 100644 index 0000000000..256ecbbcd3 --- /dev/null +++ b/data/core.telegram.org/constructor/secureSecretSettings.html @@ -0,0 +1,157 @@ + + + + + secureSecretSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

secureSecretSettings

+ +

Secure settings

+

+ +
+
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
secure_algoSecurePasswordKdfAlgoSecure KDF algo
secure_secretbytesSecure secret
secure_secret_idlongSecret ID
+

Type

+

SecureSecretSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValue.html b/data/core.telegram.org/constructor/secureValue.html new file mode 100644 index 0000000000..9f4304ca11 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValue.html @@ -0,0 +1,194 @@ + + + + + secureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValue

+ +

Secure value

+

+ +
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
+

Type

+

SecureValue

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueError.html b/data/core.telegram.org/constructor/secureValueError.html new file mode 100644 index 0000000000..98db7a6786 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueError.html @@ -0,0 +1,157 @@ + + + + + secureValueError + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueError

+ +

Secure value error

+

+ +
+
secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeType of element which has the issue
hashbytesHash
textstringError message
+

Type

+

SecureValueError

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorData.html b/data/core.telegram.org/constructor/secureValueErrorData.html new file mode 100644 index 0000000000..841de58f46 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorData.html @@ -0,0 +1,175 @@ + + + + + secureValueErrorData + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorData

+ +

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

+

+ +
+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeThe section of the user's Telegram Passport which has the error, one of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeAddress
data_hashbytesData hash
fieldstringName of the data field which has the error
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePersonalDetails

+

Personal details

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+

secureValueTypeAddress

+

Address

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorFile.html b/data/core.telegram.org/constructor/secureValueErrorFile.html new file mode 100644 index 0000000000..d50de5bf36 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorFile.html @@ -0,0 +1,168 @@ + + + + + secureValueErrorFile + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorFile

+ +

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

+

+ +
+
secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypeUtilityBill

+

Utility bill

+

secureValueTypeBankStatement

+

Bank statement

+

secureValueTypeRentalAgreement

+

Rental agreement

+

secureValueTypePassportRegistration

+

Internal registration passport

+

secureValueTypeTemporaryRegistration

+

Temporary registration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorFiles.html b/data/core.telegram.org/constructor/secureValueErrorFiles.html new file mode 100644 index 0000000000..4b44f96a63 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorFiles.html @@ -0,0 +1,168 @@ + + + + + secureValueErrorFiles + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorFiles

+ +

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

+

+ +
+
secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>File hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypeUtilityBill

+

Utility bill

+

secureValueTypeBankStatement

+

Bank statement

+

secureValueTypeRentalAgreement

+

Rental agreement

+

secureValueTypePassportRegistration

+

Internal registration passport

+

secureValueTypeTemporaryRegistration

+

Temporary registration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorFrontSide.html b/data/core.telegram.org/constructor/secureValueErrorFrontSide.html new file mode 100644 index 0000000000..9fc313585b --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorFrontSide.html @@ -0,0 +1,166 @@ + + + + + secureValueErrorFrontSide + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorFrontSide

+ +

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

+

+ +
+
secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorReverseSide.html b/data/core.telegram.org/constructor/secureValueErrorReverseSide.html new file mode 100644 index 0000000000..91bb222d72 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorReverseSide.html @@ -0,0 +1,162 @@ + + + + + secureValueErrorReverseSide + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorReverseSide

+ +

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

+

+ +
+
secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeDriverLicense, secureValueTypeIdentityCard
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorSelfie.html b/data/core.telegram.org/constructor/secureValueErrorSelfie.html new file mode 100644 index 0000000000..0a05a21b7f --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorSelfie.html @@ -0,0 +1,166 @@ + + + + + secureValueErrorSelfie + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorSelfie

+ +

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

+

+ +
+
secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html b/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html new file mode 100644 index 0000000000..19f9424f76 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html @@ -0,0 +1,178 @@ + + + + + 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 new file mode 100644 index 0000000000..505f9f2db6 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html @@ -0,0 +1,178 @@ + + + + + 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/secureValueHash.html b/data/core.telegram.org/constructor/secureValueHash.html new file mode 100644 index 0000000000..287f52e1ec --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueHash.html @@ -0,0 +1,152 @@ + + + + + secureValueHash + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueHash

+ +

Secure value hash

+

+ +
+
secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeSecure value type
hashbytesHash
+

Type

+

SecureValueHash

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeAddress.html b/data/core.telegram.org/constructor/secureValueTypeAddress.html new file mode 100644 index 0000000000..d83a0b1593 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeAddress.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeAddress

+ +

Address

+

+ +
+
secureValueTypeAddress#cbe31e26 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeBankStatement.html b/data/core.telegram.org/constructor/secureValueTypeBankStatement.html new file mode 100644 index 0000000000..e0f1d7f738 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeBankStatement.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeBankStatement + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeBankStatement

+ +

Bank statement

+

+ +
+
secureValueTypeBankStatement#89137c0d = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html b/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html new file mode 100644 index 0000000000..247d4461ec --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeDriverLicense + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeDriverLicense

+ +

Driver's license

+

+ +
+
secureValueTypeDriverLicense#6e425c4 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeEmail.html b/data/core.telegram.org/constructor/secureValueTypeEmail.html new file mode 100644 index 0000000000..fa245300e0 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeEmail.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeEmail

+ +

Email

+

+ +
+
secureValueTypeEmail#8e3ca7ee = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html b/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html new file mode 100644 index 0000000000..7e03c3b718 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeIdentityCard + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeIdentityCard

+ +

Identity card

+

+ +
+
secureValueTypeIdentityCard#a0d0744b = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html b/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html new file mode 100644 index 0000000000..36058bd81f --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html @@ -0,0 +1,134 @@ + + + + + secureValueTypeInternalPassport + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeInternalPassport

+ +

Internal passport

+

+ +
+
secureValueTypeInternalPassport#99a48f23 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypePassport.html b/data/core.telegram.org/constructor/secureValueTypePassport.html new file mode 100644 index 0000000000..17fa521cab --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypePassport.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePassport + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePassport

+ +

Passport

+

+ +
+
secureValueTypePassport#3dac6a00 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html b/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html new file mode 100644 index 0000000000..32b8dada30 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html @@ -0,0 +1,134 @@ + + + + + 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 new file mode 100644 index 0000000000..6d091d2b8c --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypePersonalDetails.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePersonalDetails + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePersonalDetails

+ +

Personal details

+

+ +
+
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypePhone.html b/data/core.telegram.org/constructor/secureValueTypePhone.html new file mode 100644 index 0000000000..4c31fad60b --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypePhone.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePhone + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePhone

+ +

Phone

+

+ +
+
secureValueTypePhone#b320aadb = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html b/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html new file mode 100644 index 0000000000..2e375b1061 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeRentalAgreement + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeRentalAgreement

+ +

Rental agreement

+

+ +
+
secureValueTypeRentalAgreement#8b883488 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html b/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html new file mode 100644 index 0000000000..7312f9e65f --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeTemporaryRegistration + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeTemporaryRegistration

+ +

Temporary registration

+

+ +
+
secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html b/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html new file mode 100644 index 0000000000..bbbb3ea296 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeUtilityBill + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeUtilityBill

+ +

Utility bill

+

+ +
+
secureValueTypeUtilityBill#fc36954e = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageCancelAction.html b/data/core.telegram.org/constructor/sendMessageCancelAction.html new file mode 100644 index 0000000000..0a02c7e36b --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageCancelAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageCancelAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageCancelAction

+ +

Invalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.

+

+ +
+
sendMessageCancelAction#fd5ec8f5 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageChooseContactAction.html b/data/core.telegram.org/constructor/sendMessageChooseContactAction.html new file mode 100644 index 0000000000..43986989ce --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageChooseContactAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageChooseContactAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageChooseContactAction

+ +

User is selecting a contact to share.

+

+ +
+
sendMessageChooseContactAction#628cbc6f = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageChooseStickerAction.html b/data/core.telegram.org/constructor/sendMessageChooseStickerAction.html new file mode 100644 index 0000000000..097f269723 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageChooseStickerAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageChooseStickerAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageChooseStickerAction

+ +

User is choosing a sticker

+

+ +
+
sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageEmojiInteraction.html b/data/core.telegram.org/constructor/sendMessageEmojiInteraction.html new file mode 100644 index 0000000000..4e0c69aba9 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageEmojiInteraction.html @@ -0,0 +1,160 @@ + + + + + sendMessageEmojiInteraction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageEmojiInteraction

+ +

User has clicked on an animated emoji triggering a reaction, click here for more info ».

+

+ +
+
sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji
msg_idintMessage ID of the animated emoji that was clicked
interactionDataJSONA JSON object with interaction info, click here for more info »
+

Type

+

SendMessageAction

+

Related pages

+

Animated Emojis

+

Graphical telegram clients should transform emojis into their respective animated version.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageEmojiInteractionSeen.html b/data/core.telegram.org/constructor/sendMessageEmojiInteractionSeen.html new file mode 100644 index 0000000000..75c5141b80 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageEmojiInteractionSeen.html @@ -0,0 +1,150 @@ + + + + + sendMessageEmojiInteractionSeen + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageEmojiInteractionSeen

+ +

User is watching an animated emoji reaction triggered by another user, click here for more info ».

+

+ +
+
sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji
+

Type

+

SendMessageAction

+

Related pages

+

Animated Emojis

+

Graphical telegram clients should transform emojis into their respective animated version.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageGamePlayAction.html b/data/core.telegram.org/constructor/sendMessageGamePlayAction.html new file mode 100644 index 0000000000..1528d72a25 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageGamePlayAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageGamePlayAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageGamePlayAction

+ +

User is playing a game

+

+ +
+
sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html b/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html new file mode 100644 index 0000000000..452f169866 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageGeoLocationAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageGeoLocationAction

+ +

User is selecting a location to share.

+

+ +
+
sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageHistoryImportAction.html b/data/core.telegram.org/constructor/sendMessageHistoryImportAction.html new file mode 100644 index 0000000000..8dbec2bee6 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageHistoryImportAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageHistoryImportAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageHistoryImportAction

+ +

Chat history is being imported

+

+ +
+
sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html b/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html new file mode 100644 index 0000000000..7203f42405 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageRecordAudioAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageRecordAudioAction

+ +

User is recording a voice message.

+

+ +
+
sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html b/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html new file mode 100644 index 0000000000..68b47b4573 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageRecordRoundAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageRecordRoundAction

+ +

User is recording a round video to share

+

+ +
+
sendMessageRecordRoundAction#88f27fbc = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html b/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html new file mode 100644 index 0000000000..8b3dcd0cdc --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageRecordVideoAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageRecordVideoAction

+ +

User is recording a video.

+

+ +
+
sendMessageRecordVideoAction#a187d66f = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageTypingAction.html b/data/core.telegram.org/constructor/sendMessageTypingAction.html new file mode 100644 index 0000000000..c6aa231f99 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageTypingAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageTypingAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageTypingAction

+ +

User is typing.

+

+ +
+
sendMessageTypingAction#16bf744e = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html b/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html new file mode 100644 index 0000000000..2c16728bae --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadAudioAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadAudioAction

+ +

User is uploading a voice message.

+

+ +
+
sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html b/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html new file mode 100644 index 0000000000..e94884cbeb --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadDocumentAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadDocumentAction

+ +

User is uploading a file.

+

+ +
+
sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html b/data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html new file mode 100644 index 0000000000..715bc6acb5 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html @@ -0,0 +1,147 @@ + + + + + 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/sendMessageUploadRoundAction.html b/data/core.telegram.org/constructor/sendMessageUploadRoundAction.html new file mode 100644 index 0000000000..646a82f427 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageUploadRoundAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadRoundAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadRoundAction

+ +

User is uploading a round video

+

+ +
+
sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html b/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html new file mode 100644 index 0000000000..a27269a0f4 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadVideoAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadVideoAction

+ +

User is uploading a video.

+

+ +
+
sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/shippingOption.html b/data/core.telegram.org/constructor/shippingOption.html new file mode 100644 index 0000000000..1883b6a596 --- /dev/null +++ b/data/core.telegram.org/constructor/shippingOption.html @@ -0,0 +1,157 @@ + + + + + shippingOption + + + + + + + + + + + + + +
+ +
+
+
+ +

shippingOption

+ +

Shipping option

+

+ +
+
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringOption ID
titlestringTitle
pricesVector<LabeledPrice>List of price portions
+

Type

+

ShippingOption

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/speakingInGroupCallAction.html b/data/core.telegram.org/constructor/speakingInGroupCallAction.html new file mode 100644 index 0000000000..a9bb9ca4c0 --- /dev/null +++ b/data/core.telegram.org/constructor/speakingInGroupCallAction.html @@ -0,0 +1,132 @@ + + + + + speakingInGroupCallAction + + + + + + + + + + + + + +
+ +
+
+
+ +

speakingInGroupCallAction

+ +

User is currently speaking in the group call

+

+ +
+
speakingInGroupCallAction#d92c2285 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sponsoredMessage.html b/data/core.telegram.org/constructor/sponsoredMessage.html new file mode 100644 index 0000000000..ec0c80c006 --- /dev/null +++ b/data/core.telegram.org/constructor/sponsoredMessage.html @@ -0,0 +1,178 @@ + + + + + sponsoredMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

sponsoredMessage

+ +

A sponsored message.

+

+ +
+
sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
random_idbytesMessage ID
from_idPeerID of the sender of the message
start_paramflags.0?stringParameter for the bot start message if the sponsored chat is a chat with a bot.
messagestringSponsored message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
+

Type

+

SponsoredMessage

+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+

Styled text with message entities

+

How to create styled text with message entities

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stats.broadcastStats b/data/core.telegram.org/constructor/stats.broadcastStats new file mode 100644 index 0000000000..39abf285e6 --- /dev/null +++ b/data/core.telegram.org/constructor/stats.broadcastStats @@ -0,0 +1,220 @@ + + + + + stats.broadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.broadcastStats

+ +

Channel statistics.

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
followersStatsAbsValueAndPrevFollower count change for period in consideration
views_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
shares_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date)
enabled_notificationsStatsPercentValuePercentage of subscribers with enabled notifications
growth_graphStatsGraphChannel growth graph (absolute subscriber count)
followers_graphStatsGraphFollowers growth graph (relative subscriber count)
mute_graphStatsGraphMuted users graph (relative)
top_hours_graphStatsGraphViews per hour graph (absolute)
interactions_graphStatsGraphInteractions graph (absolute)
iv_interactions_graphStatsGraphIV interactions graph (absolute)
views_by_source_graphStatsGraphViews by source graph (absolute)
new_followers_by_source_graphStatsGraphNew followers by source graph (absolute)
languages_graphStatsGraphSubscriber language graph (piechart)
recent_message_interactionsVector<MessageInteractionCounters>Recent message interactions
+

Type

+

stats.BroadcastStats

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stats.megagroupStats b/data/core.telegram.org/constructor/stats.megagroupStats new file mode 100644 index 0000000000..dcc826e2cc --- /dev/null +++ b/data/core.telegram.org/constructor/stats.megagroupStats @@ -0,0 +1,230 @@ + + + + + stats.megagroupStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.megagroupStats

+ +

Supergroup statistics

+

+ +
+
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
membersStatsAbsValueAndPrevMember count change for period in consideration
messagesStatsAbsValueAndPrevMessage number change for period in consideration
viewersStatsAbsValueAndPrevNumber of users that viewed messages, for range in consideration
postersStatsAbsValueAndPrevNumber of users that posted messages, for range in consideration
growth_graphStatsGraphSupergroup growth graph (absolute subscriber count)
members_graphStatsGraphMembers growth (relative subscriber count)
new_members_by_source_graphStatsGraphNew members by source graph
languages_graphStatsGraphSubscriber language graph (piechart)
messages_graphStatsGraphMessage activity graph (stacked bar graph, message type)
actions_graphStatsGraphGroup activity graph (deleted, modified messages, blocked users)
top_hours_graphStatsGraphActivity per hour graph (absolute)
weekdays_graphStatsGraphActivity per day of week graph (absolute)
top_postersVector<StatsGroupTopPoster>Info about most active group members
top_adminsVector<StatsGroupTopAdmin>Info about most active group admins
top_invitersVector<StatsGroupTopInviter>Info about most active group inviters
usersVector<User>Info about users mentioned in statistics
+

Type

+

stats.MegagroupStats

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stats.messageStats b/data/core.telegram.org/constructor/stats.messageStats new file mode 100644 index 0000000000..045190b0ff --- /dev/null +++ b/data/core.telegram.org/constructor/stats.messageStats @@ -0,0 +1,147 @@ + + + + + stats.messageStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.messageStats

+ +

Message statistics

+

+ +
+
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
views_graphStatsGraphMessage view graph
+

Type

+

stats.MessageStats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsAbsValueAndPrev.html b/data/core.telegram.org/constructor/statsAbsValueAndPrev.html new file mode 100644 index 0000000000..f0dfb13108 --- /dev/null +++ b/data/core.telegram.org/constructor/statsAbsValueAndPrev.html @@ -0,0 +1,152 @@ + + + + + statsAbsValueAndPrev + + + + + + + + + + + + + +
+ +
+
+
+ +

statsAbsValueAndPrev

+ +

Statistics value couple; initial and final value for period of time currently in consideration

+

+ +
+
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
currentdoubleCurrent value
previousdoublePrevious value
+

Type

+

StatsAbsValueAndPrev

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsDateRangeDays.html b/data/core.telegram.org/constructor/statsDateRangeDays.html new file mode 100644 index 0000000000..b5a605ab1c --- /dev/null +++ b/data/core.telegram.org/constructor/statsDateRangeDays.html @@ -0,0 +1,155 @@ + + + + + statsDateRangeDays + + + + + + + + + + + + + +
+ +
+
+
+ +

statsDateRangeDays

+ +

Channel statistics date range

+

+ +
+
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
min_dateintInitial date
max_dateintFinal date
+

Type

+

StatsDateRangeDays

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsGraph.html b/data/core.telegram.org/constructor/statsGraph.html new file mode 100644 index 0000000000..59cd41cf93 --- /dev/null +++ b/data/core.telegram.org/constructor/statsGraph.html @@ -0,0 +1,160 @@ + + + + + statsGraph + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGraph

+ +

Channel statistics graph

+

+ +
+
statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
jsonDataJSONStatistics data
zoom_tokenflags.0?stringZoom token
+

Type

+

StatsGraph

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsGraphAsync.html b/data/core.telegram.org/constructor/statsGraphAsync.html new file mode 100644 index 0000000000..af13962104 --- /dev/null +++ b/data/core.telegram.org/constructor/statsGraphAsync.html @@ -0,0 +1,152 @@ + + + + + statsGraphAsync + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGraphAsync

+ +

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
tokenstringToken to use for fetching the async graph
+

Type

+

StatsGraph

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

stats.loadAsyncGraph

+

Load channel statistics graph asynchronously

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsGraphError.html b/data/core.telegram.org/constructor/statsGraphError.html new file mode 100644 index 0000000000..1dc902e539 --- /dev/null +++ b/data/core.telegram.org/constructor/statsGraphError.html @@ -0,0 +1,150 @@ + + + + + statsGraphError + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGraphError

+ +

An error occurred while generating the statistics graph

+

+ +
+
statsGraphError#bedc9822 error:string = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
errorstringThe error
+

Type

+

StatsGraph

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsGroupTopAdmin.html b/data/core.telegram.org/constructor/statsGroupTopAdmin.html new file mode 100644 index 0000000000..479ff8cd4c --- /dev/null +++ b/data/core.telegram.org/constructor/statsGroupTopAdmin.html @@ -0,0 +1,165 @@ + + + + + statsGroupTopAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGroupTopAdmin

+ +

Information about an active admin in a supergroup

+

+ +
+
statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
deletedintNumber of deleted messages for statistics period in consideration
kickedintNumber of kicked users for statistics period in consideration
bannedintNumber of banned users for statistics period in consideration
+

Type

+

StatsGroupTopAdmin

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsGroupTopPoster.html b/data/core.telegram.org/constructor/statsGroupTopPoster.html new file mode 100644 index 0000000000..6af90fbd92 --- /dev/null +++ b/data/core.telegram.org/constructor/statsGroupTopPoster.html @@ -0,0 +1,160 @@ + + + + + statsGroupTopPoster + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGroupTopPoster

+ +

Information about an active user in a supergroup

+

+ +
+
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
messagesintNumber of messages for statistics period in consideration
avg_charsintAverage number of characters per message
+

Type

+

StatsGroupTopPoster

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsPercentValue.html b/data/core.telegram.org/constructor/statsPercentValue.html new file mode 100644 index 0000000000..2cb40ffd2b --- /dev/null +++ b/data/core.telegram.org/constructor/statsPercentValue.html @@ -0,0 +1,156 @@ + + + + + statsPercentValue + + + + + + + + + + + + + +
+ +
+
+
+ +

statsPercentValue

+ +

Channel statistics percentage.
+Compute the percentage simply by doing part * total / 100

+

+ +
+
statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
partdoublePartial value
totaldoubleTotal value
+

Type

+

StatsPercentValue

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsURL.html b/data/core.telegram.org/constructor/statsURL.html new file mode 100644 index 0000000000..896601ca9f --- /dev/null +++ b/data/core.telegram.org/constructor/statsURL.html @@ -0,0 +1,147 @@ + + + + + statsURL + + + + + + + + + + + + + +
+ +
+
+
+ +

statsURL

+ +

URL with chat statistics

+

+ +
+
statsURL#47a971e0 url:string = StatsURL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringChat statistics
+

Type

+

StatsURL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stickerPack.html b/data/core.telegram.org/constructor/stickerPack.html new file mode 100644 index 0000000000..9b6858a67d --- /dev/null +++ b/data/core.telegram.org/constructor/stickerPack.html @@ -0,0 +1,156 @@ + + + + + stickerPack + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerPack

+ +

A stickerpack is a group of stickers associated to the same emoji.
+It is not a sticker pack the way it is usually intended, you may be looking for a StickerSet.

+

+ +
+
stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji
documentsVector<long>Stickers
+

Type

+

StickerPack

+

Related pages

+

StickerSet

+

Represents a stickerset (stickerpack)

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stickerSet.html b/data/core.telegram.org/constructor/stickerSet.html new file mode 100644 index 0000000000..df7e9e3c08 --- /dev/null +++ b/data/core.telegram.org/constructor/stickerSet.html @@ -0,0 +1,217 @@ + + + + + stickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSet

+ +

Represents a stickerset (stickerpack)

+

+ +
+
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
archivedflags.1?trueWhether this stickerset was archived (due to too many saved stickers in the current account)
officialflags.2?trueIs this stickerset official
masksflags.3?trueIs this a mask stickerset
animatedflags.5?trueIs this an animated stickerpack
installed_dateflags.0?intWhen was this stickerset installed
idlongID of the stickerset
access_hashlongAccess hash of stickerset
titlestringTitle of stickerset
short_namestringShort name of stickerset to use in tg://addstickers?set=short_name
thumbsflags.4?Vector<PhotoSize>Stickerset thumbnail
thumb_dc_idflags.4?intDC ID of thumbnail
thumb_versionflags.4?intThumbnail version
countintNumber of stickers in pack
hashintHash
+

Type

+

StickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stickerSetCovered.html b/data/core.telegram.org/constructor/stickerSetCovered.html new file mode 100644 index 0000000000..c89e76f518 --- /dev/null +++ b/data/core.telegram.org/constructor/stickerSetCovered.html @@ -0,0 +1,152 @@ + + + + + stickerSetCovered + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSetCovered

+ +

Stickerset, with a specific sticker as preview

+

+ +
+
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
setStickerSetStickerset
coverDocumentPreview
+

Type

+

StickerSetCovered

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stickerSetMultiCovered.html b/data/core.telegram.org/constructor/stickerSetMultiCovered.html new file mode 100644 index 0000000000..a422f91723 --- /dev/null +++ b/data/core.telegram.org/constructor/stickerSetMultiCovered.html @@ -0,0 +1,152 @@ + + + + + stickerSetMultiCovered + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSetMultiCovered

+ +

Stickerset, with a specific stickers as preview

+

+ +
+
stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
setStickerSetStickerset
coversVector<Document>Preview stickers
+

Type

+

StickerSetCovered

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stickers.suggestedShortName b/data/core.telegram.org/constructor/stickers.suggestedShortName new file mode 100644 index 0000000000..536386d55e --- /dev/null +++ b/data/core.telegram.org/constructor/stickers.suggestedShortName @@ -0,0 +1,147 @@ + + + + + stickers.suggestedShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.suggestedShortName

+ +

A suggested short name for a stickerpack

+

+ +
+
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
short_namestringSuggested short name
+

Type

+

stickers.SuggestedShortName

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.fileGif b/data/core.telegram.org/constructor/storage.fileGif new file mode 100644 index 0000000000..276e955acf --- /dev/null +++ b/data/core.telegram.org/constructor/storage.fileGif @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..fa1545b29c --- /dev/null +++ b/data/core.telegram.org/constructor/storage.fileJpeg @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..b6c2a8a2c9 --- /dev/null +++ b/data/core.telegram.org/constructor/storage.fileMov @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..e3b2e9ab90 --- /dev/null +++ b/data/core.telegram.org/constructor/storage.fileMp3 @@ -0,0 +1,132 @@ + + + + + storage.fileMp3 + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileMp3

+ +

Mp3 audio. MIME type: audio/mpeg.

+

+ +
+
storage.fileMp3#528a0677 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.fileMp4 b/data/core.telegram.org/constructor/storage.fileMp4 new file mode 100644 index 0000000000..f318e4e8dc --- /dev/null +++ b/data/core.telegram.org/constructor/storage.fileMp4 @@ -0,0 +1,132 @@ + + + + + storage.fileMp4 + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileMp4

+ +

MPEG-4 video. MIME type: video/mp4.

+

+ +
+
storage.fileMp4#b3cea0e4 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.filePartial b/data/core.telegram.org/constructor/storage.filePartial new file mode 100644 index 0000000000..871ba727db --- /dev/null +++ b/data/core.telegram.org/constructor/storage.filePartial @@ -0,0 +1,132 @@ + + + + + storage.filePartial + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.filePartial

+ +

Part of a bigger file.

+

+ +
+
storage.filePartial#40bc6f52 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.filePdf b/data/core.telegram.org/constructor/storage.filePdf new file mode 100644 index 0000000000..4683010343 --- /dev/null +++ b/data/core.telegram.org/constructor/storage.filePdf @@ -0,0 +1,132 @@ + + + + + storage.filePdf + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.filePdf

+ +

PDF document image. MIME type: application/pdf.

+

+ +
+
storage.filePdf#ae1e508d = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.filePng b/data/core.telegram.org/constructor/storage.filePng new file mode 100644 index 0000000000..0dc8cecafb --- /dev/null +++ b/data/core.telegram.org/constructor/storage.filePng @@ -0,0 +1,132 @@ + + + + + storage.filePng + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.filePng

+ +

PNG image. MIME type: image/png.

+

+ +
+
storage.filePng#a4f63c0 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.fileUnknown b/data/core.telegram.org/constructor/storage.fileUnknown new file mode 100644 index 0000000000..64ec949ae3 --- /dev/null +++ b/data/core.telegram.org/constructor/storage.fileUnknown @@ -0,0 +1,132 @@ + + + + + storage.fileUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileUnknown

+ +

Unknown type.

+

+ +
+
storage.fileUnknown#aa963b05 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.fileWebp b/data/core.telegram.org/constructor/storage.fileWebp new file mode 100644 index 0000000000..faca63bb5c --- /dev/null +++ b/data/core.telegram.org/constructor/storage.fileWebp @@ -0,0 +1,132 @@ + + + + + storage.fileWebp + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileWebp

+ +

WEBP image. MIME type: image/webp.

+

+ +
+
storage.fileWebp#1081464c = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textAnchor.html b/data/core.telegram.org/constructor/textAnchor.html new file mode 100644 index 0000000000..08b2472a50 --- /dev/null +++ b/data/core.telegram.org/constructor/textAnchor.html @@ -0,0 +1,152 @@ + + + + + textAnchor + + + + + + + + + + + + + +
+ +
+
+
+ +

textAnchor

+ +

Text linking to another section of the page

+

+ +
+
textAnchor#35553762 text:RichText name:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
namestringSection name
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textBold.html b/data/core.telegram.org/constructor/textBold.html new file mode 100644 index 0000000000..1295f8fe80 --- /dev/null +++ b/data/core.telegram.org/constructor/textBold.html @@ -0,0 +1,147 @@ + + + + + textBold + + + + + + + + + + + + + +
+ +
+
+
+ +

textBold

+ +

Bold text

+

+ +
+
textBold#6724abc4 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textConcat.html b/data/core.telegram.org/constructor/textConcat.html new file mode 100644 index 0000000000..3f8c30fd65 --- /dev/null +++ b/data/core.telegram.org/constructor/textConcat.html @@ -0,0 +1,147 @@ + + + + + textConcat + + + + + + + + + + + + + +
+ +
+
+
+ +

textConcat

+ +

Concatenation of rich texts

+

+ +
+
textConcat#7e6260d7 texts:Vector<RichText> = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textsVector<RichText>Concatenated rich texts
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textEmail.html b/data/core.telegram.org/constructor/textEmail.html new file mode 100644 index 0000000000..a93efc09fa --- /dev/null +++ b/data/core.telegram.org/constructor/textEmail.html @@ -0,0 +1,152 @@ + + + + + textEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

textEmail

+ +

Rich text email link

+

+ +
+
textEmail#de5a0dd6 text:RichText email:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextLink text
emailstringEmail address
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textEmpty.html b/data/core.telegram.org/constructor/textEmpty.html new file mode 100644 index 0000000000..3969e47115 --- /dev/null +++ b/data/core.telegram.org/constructor/textEmpty.html @@ -0,0 +1,132 @@ + + + + + textEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

textEmpty

+ +

Empty rich text element

+

+ +
+
textEmpty#dc3d824f = RichText;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textFixed.html b/data/core.telegram.org/constructor/textFixed.html new file mode 100644 index 0000000000..10ad7c895b --- /dev/null +++ b/data/core.telegram.org/constructor/textFixed.html @@ -0,0 +1,147 @@ + + + + + textFixed + + + + + + + + + + + + + +
+ +
+
+
+ +

textFixed

+ +

fixed-width rich text

+

+ +
+
textFixed#6c3f19b9 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textImage.html b/data/core.telegram.org/constructor/textImage.html new file mode 100644 index 0000000000..d9745acea3 --- /dev/null +++ b/data/core.telegram.org/constructor/textImage.html @@ -0,0 +1,157 @@ + + + + + textImage + + + + + + + + + + + + + +
+ +
+
+
+ +

textImage

+ +

Inline image

+

+ +
+
textImage#81ccf4f document_id:long w:int h:int = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
document_idlongDocument ID
wintWidth
hintHeight
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textItalic.html b/data/core.telegram.org/constructor/textItalic.html new file mode 100644 index 0000000000..3ca45eaf6a --- /dev/null +++ b/data/core.telegram.org/constructor/textItalic.html @@ -0,0 +1,147 @@ + + + + + textItalic + + + + + + + + + + + + + +
+ +
+
+
+ +

textItalic

+ +

Italic text

+

+ +
+
textItalic#d912a59c text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textMarked.html b/data/core.telegram.org/constructor/textMarked.html new file mode 100644 index 0000000000..ffd36bf700 --- /dev/null +++ b/data/core.telegram.org/constructor/textMarked.html @@ -0,0 +1,147 @@ + + + + + textMarked + + + + + + + + + + + + + +
+ +
+
+
+ +

textMarked

+ +

Highlighted text

+

+ +
+
textMarked#34b8621 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textPhone.html b/data/core.telegram.org/constructor/textPhone.html new file mode 100644 index 0000000000..05127fbc64 --- /dev/null +++ b/data/core.telegram.org/constructor/textPhone.html @@ -0,0 +1,152 @@ + + + + + textPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

textPhone

+ +

Rich text linked to a phone number

+

+ +
+
textPhone#1ccb966a text:RichText phone:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
phonestringPhone number
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textPlain.html b/data/core.telegram.org/constructor/textPlain.html new file mode 100644 index 0000000000..de391188b4 --- /dev/null +++ b/data/core.telegram.org/constructor/textPlain.html @@ -0,0 +1,147 @@ + + + + + textPlain + + + + + + + + + + + + + +
+ +
+
+
+ +

textPlain

+ +

Plain text

+

+ +
+
textPlain#744694e0 text:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textStrike.html b/data/core.telegram.org/constructor/textStrike.html new file mode 100644 index 0000000000..e866d3cf63 --- /dev/null +++ b/data/core.telegram.org/constructor/textStrike.html @@ -0,0 +1,147 @@ + + + + + textStrike + + + + + + + + + + + + + +
+ +
+
+
+ +

textStrike

+ +

Strikethrough text

+

+ +
+
textStrike#9bf8bb95 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textSubscript.html b/data/core.telegram.org/constructor/textSubscript.html new file mode 100644 index 0000000000..9b2deb6e77 --- /dev/null +++ b/data/core.telegram.org/constructor/textSubscript.html @@ -0,0 +1,147 @@ + + + + + textSubscript + + + + + + + + + + + + + +
+ +
+
+
+ +

textSubscript

+ +

Subscript text

+

+ +
+
textSubscript#ed6a8504 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textSuperscript.html b/data/core.telegram.org/constructor/textSuperscript.html new file mode 100644 index 0000000000..2efa9771a5 --- /dev/null +++ b/data/core.telegram.org/constructor/textSuperscript.html @@ -0,0 +1,147 @@ + + + + + textSuperscript + + + + + + + + + + + + + +
+ +
+
+
+ +

textSuperscript

+ +

Superscript text

+

+ +
+
textSuperscript#c7fb5e01 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textUnderline.html b/data/core.telegram.org/constructor/textUnderline.html new file mode 100644 index 0000000000..3ad40497c0 --- /dev/null +++ b/data/core.telegram.org/constructor/textUnderline.html @@ -0,0 +1,147 @@ + + + + + textUnderline + + + + + + + + + + + + + +
+ +
+
+
+ +

textUnderline

+ +

Underlined text

+

+ +
+
textUnderline#c12622c4 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textUrl.html b/data/core.telegram.org/constructor/textUrl.html new file mode 100644 index 0000000000..8531b73455 --- /dev/null +++ b/data/core.telegram.org/constructor/textUrl.html @@ -0,0 +1,157 @@ + + + + + textUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

textUrl

+ +

Link

+

+ +
+
textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText of link
urlstringWebpage HTTP URL
webpage_idlongIf a preview was already generated for the page, the page ID
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/themeSettings.html b/data/core.telegram.org/constructor/themeSettings.html new file mode 100644 index 0000000000..c19f416a6b --- /dev/null +++ b/data/core.telegram.org/constructor/themeSettings.html @@ -0,0 +1,177 @@ + + + + + themeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

themeSettings

+ +

Theme settings

+

+ +
+
themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
message_colors_animatedflags.2?trueIf set, the freeform gradient fill needs to be animated on every sent message.
base_themeBaseThemeBase theme
accent_colorintAccent color, ARGB format
outbox_accent_colorflags.3?intAccent color of outgoing messages in ARGB format
message_colorsflags.0?Vector<int>The fill to be used as a background for outgoing messages, in RGB24 format.
If just one or two equal colors are provided, describes a solid fill of a background.
If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
If three or four colors are provided, describes a freeform gradient fill of a background.
wallpaperflags.1?WallPaperWallpaper
+

Type

+

ThemeSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeer.html b/data/core.telegram.org/constructor/topPeer.html new file mode 100644 index 0000000000..b43cdb82b5 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeer.html @@ -0,0 +1,155 @@ + + + + + topPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeer

+ +

Top peer

+

+ +
+
topPeer#edcdc05b peer:Peer rating:double = TopPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
ratingdoubleRating as computed in top peer rating »
+

Type

+

TopPeer

+

Related pages

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html b/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html new file mode 100644 index 0000000000..a80f92f18d --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryBotsInline + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryBotsInline

+ +

Most used inline bots

+

+ +
+
topPeerCategoryBotsInline#148677e2 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html b/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html new file mode 100644 index 0000000000..70cf994243 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryBotsPM + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryBotsPM

+ +

Most used bots

+

+ +
+
topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryChannels.html b/data/core.telegram.org/constructor/topPeerCategoryChannels.html new file mode 100644 index 0000000000..697e9e4ced --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryChannels.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryChannels

+ +

Most frequently visited channels

+

+ +
+
topPeerCategoryChannels#161d9628 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html b/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html new file mode 100644 index 0000000000..426095f2a6 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryCorrespondents + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryCorrespondents

+ +

Users we've chatted most frequently with

+

+ +
+
topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html b/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html new file mode 100644 index 0000000000..c678f8aa12 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryForwardChats + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryForwardChats

+ +

Chats to which the users often forwards messages to

+

+ +
+
topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html b/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html new file mode 100644 index 0000000000..fcb286ba72 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryForwardUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryForwardUsers

+ +

Users to which the users often forwards messages to

+

+ +
+
topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryGroups.html b/data/core.telegram.org/constructor/topPeerCategoryGroups.html new file mode 100644 index 0000000000..537448ece5 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryGroups.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryGroups + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryGroups

+ +

Often-opened groups and supergroups

+

+ +
+
topPeerCategoryGroups#bd17a14a = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryPeers.html b/data/core.telegram.org/constructor/topPeerCategoryPeers.html new file mode 100644 index 0000000000..e1cbdf1a44 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryPeers.html @@ -0,0 +1,157 @@ + + + + + topPeerCategoryPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryPeers

+ +

Top peer category

+

+ +
+
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
categoryTopPeerCategoryTop peer category of peers
countintCount of peers
peersVector<TopPeer>Peers
+

Type

+

TopPeerCategoryPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html b/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html new file mode 100644 index 0000000000..81ef90445d --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryPhoneCalls + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryPhoneCalls

+ +

Most frequently called users

+

+ +
+
topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/true.html b/data/core.telegram.org/constructor/true.html new file mode 100644 index 0000000000..a609bce6e3 --- /dev/null +++ b/data/core.telegram.org/constructor/true.html @@ -0,0 +1,134 @@ + + + + + true + + + + + + + + + + + + + +
+ +
+
+
+ +

true

+ +

See predefined identifiers.

+

+ +
+
true#3fedd339 = True;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

True

+

Related pages

+

TL-formal

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotCallbackQuery.html b/data/core.telegram.org/constructor/updateBotCallbackQuery.html new file mode 100644 index 0000000000..5be1adf264 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotCallbackQuery.html @@ -0,0 +1,182 @@ + + + + + updateBotCallbackQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotCallbackQuery

+ +

A callback button was pressed, and the button data was sent to the bot that created the button

+

+ +
+
updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongID of the user that pressed the button
peerPeerChat where the inline keyboard was sent
msg_idintMessage ID
chat_instancelongGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataflags.0?bytesCallback data
game_short_nameflags.1?stringShort name of a Game to be returned, serves as the unique identifier for the game
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotCommands.html b/data/core.telegram.org/constructor/updateBotCommands.html new file mode 100644 index 0000000000..30148f73f1 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotCommands.html @@ -0,0 +1,159 @@ + + + + + updateBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotCommands

+ +

The command set of a certain bot in a certain chat has changed.

+

+ +
+
updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe affected chat
bot_idlongID of the bot that changed its command set
commandsVector<BotCommand>New bot commands
+

Type

+

Update

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotInlineQuery.html b/data/core.telegram.org/constructor/updateBotInlineQuery.html new file mode 100644 index 0000000000..f71006b5a3 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotInlineQuery.html @@ -0,0 +1,177 @@ + + + + + updateBotInlineQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotInlineQuery

+ +

An incoming inline query

+

+ +
+
updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongUser that sent the query
querystringText of query
geoflags.0?GeoPointAttached geolocation
peer_typeflags.1?InlineQueryPeerTypeType of the chat from which the inline query was sent.
offsetstringOffset to navigate through results
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotInlineSend.html b/data/core.telegram.org/constructor/updateBotInlineSend.html new file mode 100644 index 0000000000..ec465d9961 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotInlineSend.html @@ -0,0 +1,172 @@ + + + + + updateBotInlineSend + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotInlineSend

+ +

The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.

+

+ +
+
updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_idlongThe user that chose the result
querystringThe query that was used to obtain the result
geoflags.0?GeoPointOptional. Sender location, only for bots that require user location
idstringThe unique identifier for the result that was chosen
msg_idflags.1?InputBotInlineMessageIDIdentifier of the sent inline message. Available only if there is an inline keyboard attached to the message. Will be also received in callback queries and can be used to edit the message.
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html b/data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html new file mode 100644 index 0000000000..b8ffc0c733 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html @@ -0,0 +1,184 @@ + + + + + updateBotPrecheckoutQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotPrecheckoutQuery

+ +

This object contains information about an incoming pre-checkout query.

+

+ +
+
updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Type

+

Update

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotShippingQuery.html b/data/core.telegram.org/constructor/updateBotShippingQuery.html new file mode 100644 index 0000000000..7e0efdf187 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotShippingQuery.html @@ -0,0 +1,162 @@ + + + + + updateBotShippingQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotShippingQuery

+ +

This object contains information about an incoming shipping query.

+

+ +
+
updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
shipping_addressPostAddressUser specified shipping address
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotStopped.html b/data/core.telegram.org/constructor/updateBotStopped.html new file mode 100644 index 0000000000..a54e6754ec --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotStopped.html @@ -0,0 +1,165 @@ + + + + + updateBotStopped + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotStopped

+ +

A bot was stopped or re-started.

+

+ +
+
updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongThe bot ID
dateintWhen did this action occur
stoppedBoolWhether the bot was stopped or started
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotWebhookJSON.html b/data/core.telegram.org/constructor/updateBotWebhookJSON.html new file mode 100644 index 0000000000..ea38f033de --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotWebhookJSON.html @@ -0,0 +1,147 @@ + + + + + updateBotWebhookJSON + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotWebhookJSON

+ +

A new incoming event; for bots only

+

+ +
+
updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dataDataJSONThe event
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html b/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html new file mode 100644 index 0000000000..eaeed8e555 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html @@ -0,0 +1,157 @@ + + + + + updateBotWebhookJSONQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotWebhookJSONQuery

+ +

A new incoming query; for bots only

+

+ +
+
updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
query_idlongQuery identifier
dataDataJSONQuery data
timeoutintQuery timeout
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannel.html b/data/core.telegram.org/constructor/updateChannel.html new file mode 100644 index 0000000000..f322d0d6ce --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannel.html @@ -0,0 +1,147 @@ + + + + + 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/updateChannelAvailableMessages.html b/data/core.telegram.org/constructor/updateChannelAvailableMessages.html new file mode 100644 index 0000000000..6707dabf0d --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelAvailableMessages.html @@ -0,0 +1,155 @@ + + + + + updateChannelAvailableMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelAvailableMessages

+ +

The history of a channel/supergroup was hidden.

+

+ +
+
updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
available_min_idintIdentifier of a maximum unavailable message in a channel due to hidden history.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelMessageViews.html b/data/core.telegram.org/constructor/updateChannelMessageViews.html new file mode 100644 index 0000000000..bd31194007 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelMessageViews.html @@ -0,0 +1,157 @@ + + + + + updateChannelMessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelMessageViews

+ +

The view counter of a message in a channel has changed

+

+ +
+
updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
idintID of the message
viewsintNew view counter
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelParticipant.html b/data/core.telegram.org/constructor/updateChannelParticipant.html new file mode 100644 index 0000000000..7e0a5630df --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelParticipant.html @@ -0,0 +1,192 @@ + + + + + updateChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelParticipant

+ +

A participant has left, joined, was banned or admined in a channel or supergroup.

+

+ +
+
updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
dateintDate of the event
actor_idlongUser that triggered the change (inviter, admin that kicked the user, or the even the user_id itself)
user_idlongUser that was affected by the change
prev_participantflags.0?ChannelParticipantPrevious participant status
new_participantflags.1?ChannelParticipantNew participant status
inviteflags.2?ExportedChatInviteChat invite used to join the channel/supergroup
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelReadMessagesContents.html b/data/core.telegram.org/constructor/updateChannelReadMessagesContents.html new file mode 100644 index 0000000000..c1640cd6df --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelReadMessagesContents.html @@ -0,0 +1,155 @@ + + + + + updateChannelReadMessagesContents + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelReadMessagesContents

+ +

The specified channel/supergroup messages were read

+

+ +
+
updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
messagesVector<int>IDs of messages that were read
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelTooLong.html b/data/core.telegram.org/constructor/updateChannelTooLong.html new file mode 100644 index 0000000000..7e001417d8 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelTooLong.html @@ -0,0 +1,161 @@ + + + + + updateChannelTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelTooLong

+ +

There are new updates in the specified channel, the client must fetch them.
+If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.

+

+ +
+
updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongThe channel
ptsflags.0?intThe PTS.
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelUserTyping.html b/data/core.telegram.org/constructor/updateChannelUserTyping.html new file mode 100644 index 0000000000..822be5c625 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelUserTyping.html @@ -0,0 +1,172 @@ + + + + + updateChannelUserTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelUserTyping

+ +

A user is typing in a supergroup, channel or message thread

+

+ +
+
updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
top_msg_idflags.0?intThread ID
from_idPeerThe peer that is typing
actionSendMessageActionWhether the user is typing, sending a media or doing something else
+

Type

+

Update

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelWebPage.html b/data/core.telegram.org/constructor/updateChannelWebPage.html new file mode 100644 index 0000000000..ac21f0f9da --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelWebPage.html @@ -0,0 +1,167 @@ + + + + + updateChannelWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelWebPage

+ +

A webpage preview of a link in a channel/supergroup message was generated

+

+ +
+
updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
webpageWebPageGenerated webpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChat.html b/data/core.telegram.org/constructor/updateChat.html new file mode 100644 index 0000000000..6157de529f --- /dev/null +++ b/data/core.telegram.org/constructor/updateChat.html @@ -0,0 +1,147 @@ + + + + + updateChat + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChat

+ +

A new chat is available

+

+ +
+
updateChat#f89a6a4e chat_id:long = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChatDefaultBannedRights.html b/data/core.telegram.org/constructor/updateChatDefaultBannedRights.html new file mode 100644 index 0000000000..fb84016788 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChatDefaultBannedRights.html @@ -0,0 +1,160 @@ + + + + + updateChatDefaultBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatDefaultBannedRights

+ +

Default banned rights in a normal chat were updated

+

+ +
+
updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe chat
default_banned_rightsChatBannedRightsNew default banned rights
versionintVersion
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChatParticipant.html b/data/core.telegram.org/constructor/updateChatParticipant.html new file mode 100644 index 0000000000..b9f36be21d --- /dev/null +++ b/data/core.telegram.org/constructor/updateChatParticipant.html @@ -0,0 +1,192 @@ + + + + + updateChatParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipant

+ +

A user has joined or left a specific chat

+

+ +
+
updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
chat_idlongChat ID
dateintWhen did this event occur
actor_idlongUser that triggered the change (inviter, admin that kicked the user, or the even the user_id itself)
user_idlongUser that was affected by the change
prev_participantflags.0?ChatParticipantPrevious participant info (empty if this participant just joined)
new_participantflags.1?ChatParticipantNew participant info (empty if this participant just left)
inviteflags.2?ExportedChatInviteThe invite that was used to join the group
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChatParticipantAdd.html b/data/core.telegram.org/constructor/updateChatParticipantAdd.html new file mode 100644 index 0000000000..4da2034a61 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChatParticipantAdd.html @@ -0,0 +1,167 @@ + + + + + updateChatParticipantAdd + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipantAdd

+ +

New group member.

+

+ +
+
updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup ID
user_idlongID of the new member
inviter_idlongID of the user, who added member to the group
dateintWhen was the participant added
versionintChat version number
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChatParticipantAdmin.html b/data/core.telegram.org/constructor/updateChatParticipantAdmin.html new file mode 100644 index 0000000000..62c10ebbc4 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChatParticipantAdmin.html @@ -0,0 +1,165 @@ + + + + + updateChatParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipantAdmin

+ +

Admin permissions of a user in a legacy group were changed

+

+ +
+
updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
user_idlongID of the (de)admined user
is_adminBoolWhether the user was rendered admin
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChatParticipantDelete.html b/data/core.telegram.org/constructor/updateChatParticipantDelete.html new file mode 100644 index 0000000000..0fd95c5d0c --- /dev/null +++ b/data/core.telegram.org/constructor/updateChatParticipantDelete.html @@ -0,0 +1,157 @@ + + + + + updateChatParticipantDelete + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipantDelete

+ +

A member has left the group.

+

+ +
+
updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup ID
user_idlongID of the user
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChatParticipants.html b/data/core.telegram.org/constructor/updateChatParticipants.html new file mode 100644 index 0000000000..834f29d27d --- /dev/null +++ b/data/core.telegram.org/constructor/updateChatParticipants.html @@ -0,0 +1,147 @@ + + + + + updateChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipants

+ +

Composition of chat participants changed.

+

+ +
+
updateChatParticipants#7761198 participants:ChatParticipants = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantsChatParticipantsUpdated chat participants
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChatUserTyping.html b/data/core.telegram.org/constructor/updateChatUserTyping.html new file mode 100644 index 0000000000..8d6aa09372 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChatUserTyping.html @@ -0,0 +1,160 @@ + + + + + updateChatUserTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatUserTyping

+ +

The user is preparing a message in a group; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

+

+ +
+
updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup id
from_idPeerPeer that started typing (can be the chat itself, in case of anonymous admins).
actionSendMessageActionType of action
Parameter added in Layer 17.
+

Type

+

Update

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateConfig.html b/data/core.telegram.org/constructor/updateConfig.html new file mode 100644 index 0000000000..421388b500 --- /dev/null +++ b/data/core.telegram.org/constructor/updateConfig.html @@ -0,0 +1,135 @@ + + + + + updateConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

updateConfig

+ +

The server-side configuration has changed; the client should re-fetch the config using help.getConfig

+

+ +
+
updateConfig#a229dd06 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

help.getConfig

+

Returns current configuration, including data center configuration.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateContactsReset.html b/data/core.telegram.org/constructor/updateContactsReset.html new file mode 100644 index 0000000000..017f656e84 --- /dev/null +++ b/data/core.telegram.org/constructor/updateContactsReset.html @@ -0,0 +1,132 @@ + + + + + updateContactsReset + + + + + + + + + + + + + +
+ +
+
+
+ +

updateContactsReset

+ +

All contacts were deleted

+

+ +
+
updateContactsReset#7084a7be = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDcOptions.html b/data/core.telegram.org/constructor/updateDcOptions.html new file mode 100644 index 0000000000..f8c04ce363 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDcOptions.html @@ -0,0 +1,147 @@ + + + + + updateDcOptions + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDcOptions

+ +

Changes in the data center configuration options.

+

+ +
+
updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dc_optionsVector<DcOption>New connection options
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDeleteChannelMessages.html b/data/core.telegram.org/constructor/updateDeleteChannelMessages.html new file mode 100644 index 0000000000..ba1ca84fb3 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDeleteChannelMessages.html @@ -0,0 +1,167 @@ + + + + + updateDeleteChannelMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDeleteChannelMessages

+ +

Some messages in a supergroup/channel were deleted

+

+ +
+
updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
messagesVector<int>IDs of messages that were deleted
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDeleteMessages.html b/data/core.telegram.org/constructor/updateDeleteMessages.html new file mode 100644 index 0000000000..778c70d0b2 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDeleteMessages.html @@ -0,0 +1,160 @@ + + + + + updateDeleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDeleteMessages

+ +

Messages were deleted.

+

+ +
+
updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<int>List of identifiers of deleted messages
ptsintNew quality of actions in a message box
pts_countintNumber of generated events
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html b/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html new file mode 100644 index 0000000000..f44b5cb077 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html @@ -0,0 +1,155 @@ + + + + + updateDeleteScheduledMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDeleteScheduledMessages

+ +

Some scheduled messages were deleted from the schedule queue of a chat

+

+ +
+
updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
messagesVector<int>Deleted scheduled messages
+

Type

+

Update

+

Related pages

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDialogFilter.html b/data/core.telegram.org/constructor/updateDialogFilter.html new file mode 100644 index 0000000000..eece7615f2 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDialogFilter.html @@ -0,0 +1,160 @@ + + + + + updateDialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilter

+ +

A new folder was added

+

+ +
+
updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDialogFilterOrder.html b/data/core.telegram.org/constructor/updateDialogFilterOrder.html new file mode 100644 index 0000000000..0cec4f5e97 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDialogFilterOrder.html @@ -0,0 +1,150 @@ + + + + + updateDialogFilterOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilterOrder

+ +

New folder order

+

+ +
+
updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
orderVector<int>Ordered folder IDs
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDialogFilters.html b/data/core.telegram.org/constructor/updateDialogFilters.html new file mode 100644 index 0000000000..73f9eaa1cd --- /dev/null +++ b/data/core.telegram.org/constructor/updateDialogFilters.html @@ -0,0 +1,135 @@ + + + + + updateDialogFilters + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilters

+ +

Clients should update folder info

+

+ +
+
updateDialogFilters#3504914f = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDialogPinned.html b/data/core.telegram.org/constructor/updateDialogPinned.html new file mode 100644 index 0000000000..9953aab326 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDialogPinned.html @@ -0,0 +1,165 @@ + + + + + updateDialogPinned + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogPinned

+ +

A dialog was pinned/unpinned

+

+ +
+
updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the dialog was pinned
folder_idflags.1?intPeer folder ID, for more info click here
peerDialogPeerThe dialog
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDialogUnreadMark.html b/data/core.telegram.org/constructor/updateDialogUnreadMark.html new file mode 100644 index 0000000000..b535f9f65b --- /dev/null +++ b/data/core.telegram.org/constructor/updateDialogUnreadMark.html @@ -0,0 +1,157 @@ + + + + + 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 new file mode 100644 index 0000000000..29d14ce52b --- /dev/null +++ b/data/core.telegram.org/constructor/updateDraftMessage.html @@ -0,0 +1,155 @@ + + + + + updateDraftMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDraftMessage

+ +

Notifies a change of a message draft.

+

+ +
+
updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe peer to which the draft is associated
draftDraftMessageThe draft
+

Type

+

Update

+

Related pages

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateEditChannelMessage.html b/data/core.telegram.org/constructor/updateEditChannelMessage.html new file mode 100644 index 0000000000..ee2dbbcb70 --- /dev/null +++ b/data/core.telegram.org/constructor/updateEditChannelMessage.html @@ -0,0 +1,162 @@ + + + + + updateEditChannelMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEditChannelMessage

+ +

A message was edited in a channel/supergroup

+

+ +
+
updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe new message
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateEditMessage.html b/data/core.telegram.org/constructor/updateEditMessage.html new file mode 100644 index 0000000000..c768e06310 --- /dev/null +++ b/data/core.telegram.org/constructor/updateEditMessage.html @@ -0,0 +1,160 @@ + + + + + updateEditMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEditMessage

+ +

A message was edited

+

+ +
+
updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe new edited message
ptsintPTS
pts_countintPTS count
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateEncryptedChatTyping.html b/data/core.telegram.org/constructor/updateEncryptedChatTyping.html new file mode 100644 index 0000000000..e40625d470 --- /dev/null +++ b/data/core.telegram.org/constructor/updateEncryptedChatTyping.html @@ -0,0 +1,147 @@ + + + + + updateEncryptedChatTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEncryptedChatTyping

+ +

Interlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.

+

+ +
+
updateEncryptedChatTyping#1710f156 chat_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idintChat ID
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html b/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html new file mode 100644 index 0000000000..d5cdc87540 --- /dev/null +++ b/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html @@ -0,0 +1,157 @@ + + + + + updateEncryptedMessagesRead + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEncryptedMessagesRead

+ +

Communication history in an encrypted chat was marked as read.

+

+ +
+
updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idintChat ID
max_dateintMaximum value of data for read messages
dateintTime when messages were read
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateEncryption.html b/data/core.telegram.org/constructor/updateEncryption.html new file mode 100644 index 0000000000..87fd5efd86 --- /dev/null +++ b/data/core.telegram.org/constructor/updateEncryption.html @@ -0,0 +1,152 @@ + + + + + updateEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEncryption

+ +

Change of state in an encrypted chat.

+

+ +
+
updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chatEncryptedChatEncrypted chat
dateintDate of change
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateFavedStickers.html b/data/core.telegram.org/constructor/updateFavedStickers.html new file mode 100644 index 0000000000..da0a4ad57c --- /dev/null +++ b/data/core.telegram.org/constructor/updateFavedStickers.html @@ -0,0 +1,135 @@ + + + + + updateFavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateFavedStickers

+ +

The list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list

+

+ +
+
updateFavedStickers#e511996d = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

messages.getFavedStickers

+

Get faved stickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateFolderPeers.html b/data/core.telegram.org/constructor/updateFolderPeers.html new file mode 100644 index 0000000000..8e2734d4f9 --- /dev/null +++ b/data/core.telegram.org/constructor/updateFolderPeers.html @@ -0,0 +1,162 @@ + + + + + updateFolderPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateFolderPeers

+ +

The peer list of a peer folder was updated

+

+ +
+
updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
folder_peersVector<FolderPeer>New peer list
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateGeoLiveViewed.html b/data/core.telegram.org/constructor/updateGeoLiveViewed.html new file mode 100644 index 0000000000..4019a83f92 --- /dev/null +++ b/data/core.telegram.org/constructor/updateGeoLiveViewed.html @@ -0,0 +1,152 @@ + + + + + updateGeoLiveViewed + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGeoLiveViewed

+ +

Live geoposition message was viewed

+

+ +
+
updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe user that viewed the live geoposition
msg_idintMessage ID of geoposition message
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateGroupCall.html b/data/core.telegram.org/constructor/updateGroupCall.html new file mode 100644 index 0000000000..490a4d0037 --- /dev/null +++ b/data/core.telegram.org/constructor/updateGroupCall.html @@ -0,0 +1,155 @@ + + + + + updateGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGroupCall

+ +

A new groupcall was started

+

+ +
+
updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongThe channel/supergroup where this group call or livestream takes place
callGroupCallInfo about the group call or livestream
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateGroupCallConnection.html b/data/core.telegram.org/constructor/updateGroupCallConnection.html new file mode 100644 index 0000000000..7682a21b61 --- /dev/null +++ b/data/core.telegram.org/constructor/updateGroupCallConnection.html @@ -0,0 +1,157 @@ + + + + + updateGroupCallConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGroupCallConnection

+ +

New WebRTC parameters

+

+ +
+
updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
presentationflags.0?trueAre these parameters related to the screen capture session currently in progress?
paramsDataJSONWebRTC parameters
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateGroupCallParticipants.html b/data/core.telegram.org/constructor/updateGroupCallParticipants.html new file mode 100644 index 0000000000..16b868f25c --- /dev/null +++ b/data/core.telegram.org/constructor/updateGroupCallParticipants.html @@ -0,0 +1,157 @@ + + + + + updateGroupCallParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGroupCallParticipants

+ +

The participant list of a certain group call has changed

+

+ +
+
updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
participantsVector<GroupCallParticipant>New participant list
versionintVersion
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html b/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html new file mode 100644 index 0000000000..b2e486a809 --- /dev/null +++ b/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html @@ -0,0 +1,177 @@ + + + + + updateInlineBotCallbackQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateInlineBotCallbackQuery

+ +

This notification is received by bots when a button is pressed

+

+ +
+
updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongID of the user that pressed the button
msg_idInputBotInlineMessageIDID of the inline message with the button
chat_instancelongGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataflags.0?bytesData associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
game_short_nameflags.1?stringShort name of a Game to be returned, serves as the unique identifier for the game
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateLangPack.html b/data/core.telegram.org/constructor/updateLangPack.html new file mode 100644 index 0000000000..cd5b069397 --- /dev/null +++ b/data/core.telegram.org/constructor/updateLangPack.html @@ -0,0 +1,147 @@ + + + + + updateLangPack + + + + + + + + + + + + + +
+ +
+
+
+ +

updateLangPack

+ +

Language pack updated

+

+ +
+
updateLangPack#56022f4d difference:LangPackDifference = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
differenceLangPackDifferenceChanged strings
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateLangPackTooLong.html b/data/core.telegram.org/constructor/updateLangPackTooLong.html new file mode 100644 index 0000000000..72fbf1b373 --- /dev/null +++ b/data/core.telegram.org/constructor/updateLangPackTooLong.html @@ -0,0 +1,150 @@ + + + + + updateLangPackTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updateLangPackTooLong

+ +

A language pack has changed, the client should manually fetch the changed strings using langpack.getDifference

+

+ +
+
updateLangPackTooLong#46560264 lang_code:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Type

+

Update

+

Related pages

+

langpack.getDifference

+

Get new strings in languagepack

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateLoginToken.html b/data/core.telegram.org/constructor/updateLoginToken.html new file mode 100644 index 0000000000..88cfe05c8f --- /dev/null +++ b/data/core.telegram.org/constructor/updateLoginToken.html @@ -0,0 +1,132 @@ + + + + + updateLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

updateLoginToken

+ +

A login token (for login via QR code) was accepted.

+

+ +
+
updateLoginToken#564fe691 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateMessageID.html b/data/core.telegram.org/constructor/updateMessageID.html new file mode 100644 index 0000000000..b087c5f3e9 --- /dev/null +++ b/data/core.telegram.org/constructor/updateMessageID.html @@ -0,0 +1,155 @@ + + + + + updateMessageID + + + + + + + + + + + + + +
+ +
+
+
+ +

updateMessageID

+ +

Sent message with random_id client identifier was assigned an identifier.

+

+ +
+
updateMessageID#4e90bfd6 id:int random_id:long = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintid identifier of a respective Message
random_idlongPreviuosly transferred client random_id identifier
+

Type

+

Update

+

Related pages

+

Message

+

Object describing a message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateMessagePoll.html b/data/core.telegram.org/constructor/updateMessagePoll.html new file mode 100644 index 0000000000..3fe5ffacbd --- /dev/null +++ b/data/core.telegram.org/constructor/updateMessagePoll.html @@ -0,0 +1,162 @@ + + + + + updateMessagePoll + + + + + + + + + + + + + +
+ +
+
+
+ +

updateMessagePoll

+ +

The results of a poll have changed

+

+ +
+
updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
poll_idlongPoll ID
pollflags.0?PollIf the server knows the client hasn't cached this poll yet, the poll itself
resultsPollResultsNew poll results
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateMessagePollVote.html b/data/core.telegram.org/constructor/updateMessagePollVote.html new file mode 100644 index 0000000000..80cc68ae52 --- /dev/null +++ b/data/core.telegram.org/constructor/updateMessagePollVote.html @@ -0,0 +1,165 @@ + + + + + updateMessagePollVote + + + + + + + + + + + + + +
+ +
+
+
+ +

updateMessagePollVote

+ +

A specific user has voted in a poll

+

+ +
+
updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
poll_idlongPoll ID
user_idlongUser ID
optionsVector<bytes>Chosen option(s)
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateNewChannelMessage.html b/data/core.telegram.org/constructor/updateNewChannelMessage.html new file mode 100644 index 0000000000..7cd11f83d0 --- /dev/null +++ b/data/core.telegram.org/constructor/updateNewChannelMessage.html @@ -0,0 +1,162 @@ + + + + + updateNewChannelMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewChannelMessage

+ +

A new message was sent in a channel/supergroup

+

+ +
+
updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageNew message
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateNewEncryptedMessage.html b/data/core.telegram.org/constructor/updateNewEncryptedMessage.html new file mode 100644 index 0000000000..ba19543609 --- /dev/null +++ b/data/core.telegram.org/constructor/updateNewEncryptedMessage.html @@ -0,0 +1,155 @@ + + + + + updateNewEncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewEncryptedMessage

+ +

New encrypted message.

+

+ +
+
updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageEncryptedMessageMessage
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateNewMessage.html b/data/core.telegram.org/constructor/updateNewMessage.html new file mode 100644 index 0000000000..7521944f26 --- /dev/null +++ b/data/core.telegram.org/constructor/updateNewMessage.html @@ -0,0 +1,157 @@ + + + + + updateNewMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewMessage

+ +

New message in a private chat or in a legacy group.

+

+ +
+
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageMessage
ptsintNew quantity of actions in a message box
pts_countintNumber of generated events
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateNewScheduledMessage.html b/data/core.telegram.org/constructor/updateNewScheduledMessage.html new file mode 100644 index 0000000000..2930466baf --- /dev/null +++ b/data/core.telegram.org/constructor/updateNewScheduledMessage.html @@ -0,0 +1,150 @@ + + + + + updateNewScheduledMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewScheduledMessage

+ +

A message was added to the schedule queue of a chat

+

+ +
+
updateNewScheduledMessage#39a51dfb message:Message = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageMessage
+

Type

+

Update

+

Related pages

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateNewStickerSet.html b/data/core.telegram.org/constructor/updateNewStickerSet.html new file mode 100644 index 0000000000..d43e415fcb --- /dev/null +++ b/data/core.telegram.org/constructor/updateNewStickerSet.html @@ -0,0 +1,147 @@ + + + + + updateNewStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewStickerSet

+ +

A new stickerset was installed

+

+ +
+
updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickersetmessages.StickerSetThe installed stickerset
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateNotifySettings.html b/data/core.telegram.org/constructor/updateNotifySettings.html new file mode 100644 index 0000000000..ed81c06c47 --- /dev/null +++ b/data/core.telegram.org/constructor/updateNotifySettings.html @@ -0,0 +1,152 @@ + + + + + updateNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNotifySettings

+ +

Changes in notification settings.

+

+ +
+
updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerNotifyPeerNofication source
notify_settingsPeerNotifySettingsNew notification settings
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePeerBlocked.html b/data/core.telegram.org/constructor/updatePeerBlocked.html new file mode 100644 index 0000000000..386902435c --- /dev/null +++ b/data/core.telegram.org/constructor/updatePeerBlocked.html @@ -0,0 +1,152 @@ + + + + + updatePeerBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerBlocked

+ +

A peer was blocked

+

+ +
+
updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peer_idPeerThe blocked peer
blockedBoolWhether the peer was blocked or unblocked
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePeerHistoryTTL.html b/data/core.telegram.org/constructor/updatePeerHistoryTTL.html new file mode 100644 index 0000000000..54cb12f894 --- /dev/null +++ b/data/core.telegram.org/constructor/updatePeerHistoryTTL.html @@ -0,0 +1,157 @@ + + + + + updatePeerHistoryTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerHistoryTTL

+ +

The Time-To-Live for messages sent by the current user in a specific chat has changed

+

+ +
+
updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerPeerThe chat
ttl_periodflags.0?intThe new Time-To-Live
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePeerLocated.html b/data/core.telegram.org/constructor/updatePeerLocated.html new file mode 100644 index 0000000000..29defe6111 --- /dev/null +++ b/data/core.telegram.org/constructor/updatePeerLocated.html @@ -0,0 +1,147 @@ + + + + + updatePeerLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerLocated

+ +

List of peers near you was updated

+

+ +
+
updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peersVector<PeerLocated>Geolocated peer list update
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePeerSettings.html b/data/core.telegram.org/constructor/updatePeerSettings.html new file mode 100644 index 0000000000..2cb8beb1be --- /dev/null +++ b/data/core.telegram.org/constructor/updatePeerSettings.html @@ -0,0 +1,152 @@ + + + + + updatePeerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerSettings

+ +

Settings of a certain peer have changed

+

+ +
+
updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe peer
settingsPeerSettingsAssociated peer settings
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePhoneCall.html b/data/core.telegram.org/constructor/updatePhoneCall.html new file mode 100644 index 0000000000..46fc1ca7b1 --- /dev/null +++ b/data/core.telegram.org/constructor/updatePhoneCall.html @@ -0,0 +1,147 @@ + + + + + updatePhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePhoneCall

+ +

An incoming phone call

+

+ +
+
updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phone_callPhoneCallPhone call
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html b/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html new file mode 100644 index 0000000000..55ce7cf3ad --- /dev/null +++ b/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html @@ -0,0 +1,152 @@ + + + + + updatePhoneCallSignalingData + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePhoneCallSignalingData

+ +

Incoming phone call signaling payload

+

+ +
+
updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_call_idlongPhone call ID
databytesSignaling payload
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePinnedChannelMessages.html b/data/core.telegram.org/constructor/updatePinnedChannelMessages.html new file mode 100644 index 0000000000..16773d610c --- /dev/null +++ b/data/core.telegram.org/constructor/updatePinnedChannelMessages.html @@ -0,0 +1,177 @@ + + + + + updatePinnedChannelMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePinnedChannelMessages

+ +

Messages were pinned/unpinned in a channel/supergroup

+

+ +
+
updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
channel_idlongChannel ID
messagesVector<int>Messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePinnedDialogs.html b/data/core.telegram.org/constructor/updatePinnedDialogs.html new file mode 100644 index 0000000000..db5888e8fa --- /dev/null +++ b/data/core.telegram.org/constructor/updatePinnedDialogs.html @@ -0,0 +1,160 @@ + + + + + updatePinnedDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePinnedDialogs

+ +

Pinned dialogs were updated

+

+ +
+
updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.1?intPeer folder ID, for more info click here
orderflags.0?Vector<DialogPeer>New order of pinned dialogs
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePinnedMessages.html b/data/core.telegram.org/constructor/updatePinnedMessages.html new file mode 100644 index 0000000000..199fbaff94 --- /dev/null +++ b/data/core.telegram.org/constructor/updatePinnedMessages.html @@ -0,0 +1,175 @@ + + + + + updatePinnedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePinnedMessages

+ +

Some messages were pinned in a chat

+

+ +
+
updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
peerPeerPeer
messagesVector<int>Message IDs
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePrivacy.html b/data/core.telegram.org/constructor/updatePrivacy.html new file mode 100644 index 0000000000..4631dd9a46 --- /dev/null +++ b/data/core.telegram.org/constructor/updatePrivacy.html @@ -0,0 +1,152 @@ + + + + + updatePrivacy + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePrivacy

+ +

Privacy rules were changed

+

+ +
+
updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keyPrivacyKeyPeers to which the privacy rules apply
rulesVector<PrivacyRule>New privacy rules
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePtsChanged.html b/data/core.telegram.org/constructor/updatePtsChanged.html new file mode 100644 index 0000000000..41d7f504f1 --- /dev/null +++ b/data/core.telegram.org/constructor/updatePtsChanged.html @@ -0,0 +1,135 @@ + + + + + updatePtsChanged + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePtsChanged

+ +

Common message box sequence PTS has changed, state has to be refetched using updates.getState

+

+ +
+
updatePtsChanged#3354678f = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html b/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html new file mode 100644 index 0000000000..c0c57517cb --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html @@ -0,0 +1,162 @@ + + + + + updateReadChannelDiscussionOutbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelDiscussionOutbox

+ +

Outgoing comments in a discussion thread were marked as read

+

+ +
+
updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongSupergroup ID
top_msg_idintID of the group message that started the thread
read_max_idintMessage ID of latest read outgoing message for this thread
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadChannelInbox.html b/data/core.telegram.org/constructor/updateReadChannelInbox.html new file mode 100644 index 0000000000..7d80dff5a1 --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadChannelInbox.html @@ -0,0 +1,179 @@ + + + + + updateReadChannelInbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelInbox

+ +

Incoming messages in a channel/supergroup were read

+

+ +
+
updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
channel_idlongChannel/supergroup ID
max_idintPosition up to which all incoming messages are read.
still_unread_countintCount of messages weren't read yet
ptsintEvent count after generation
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadChannelOutbox.html b/data/core.telegram.org/constructor/updateReadChannelOutbox.html new file mode 100644 index 0000000000..82976bfc8b --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadChannelOutbox.html @@ -0,0 +1,155 @@ + + + + + updateReadChannelOutbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelOutbox

+ +

Outgoing messages in a channel/supergroup were read

+

+ +
+
updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
max_idintPosition up to which all outgoing messages are read.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadFeaturedStickers.html b/data/core.telegram.org/constructor/updateReadFeaturedStickers.html new file mode 100644 index 0000000000..aeb162deee --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadFeaturedStickers.html @@ -0,0 +1,132 @@ + + + + + updateReadFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadFeaturedStickers

+ +

Some featured stickers were marked as read

+

+ +
+
updateReadFeaturedStickers#571d2742 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadHistoryInbox.html b/data/core.telegram.org/constructor/updateReadHistoryInbox.html new file mode 100644 index 0000000000..bdfa1383f5 --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadHistoryInbox.html @@ -0,0 +1,182 @@ + + + + + updateReadHistoryInbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadHistoryInbox

+ +

Incoming messages were read

+

+ +
+
updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
peerPeerPeer
max_idintMaximum ID of messages read
still_unread_countintNumber of messages that are still unread
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadHistoryOutbox.html b/data/core.telegram.org/constructor/updateReadHistoryOutbox.html new file mode 100644 index 0000000000..b67c225240 --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadHistoryOutbox.html @@ -0,0 +1,165 @@ + + + + + updateReadHistoryOutbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadHistoryOutbox

+ +

Outgoing messages were read

+

+ +
+
updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
max_idintMaximum ID of read outgoing messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadMessagesContents.html b/data/core.telegram.org/constructor/updateReadMessagesContents.html new file mode 100644 index 0000000000..7db4c08653 --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadMessagesContents.html @@ -0,0 +1,160 @@ + + + + + updateReadMessagesContents + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadMessagesContents

+ +

Contents of messages in the common message box were read

+

+ +
+
updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<int>IDs of read messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateRecentStickers.html b/data/core.telegram.org/constructor/updateRecentStickers.html new file mode 100644 index 0000000000..10d375b9b5 --- /dev/null +++ b/data/core.telegram.org/constructor/updateRecentStickers.html @@ -0,0 +1,132 @@ + + + + + updateRecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateRecentStickers

+ +

The recent sticker list was updated

+

+ +
+
updateRecentStickers#9a422c20 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateSavedGifs.html b/data/core.telegram.org/constructor/updateSavedGifs.html new file mode 100644 index 0000000000..d1ab17d29c --- /dev/null +++ b/data/core.telegram.org/constructor/updateSavedGifs.html @@ -0,0 +1,132 @@ + + + + + updateSavedGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

updateSavedGifs

+ +

The saved gif list has changed, the client should refetch it using messages.getSavedGifs

+

+ +
+
updateSavedGifs#9375341e = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateServiceNotification.html b/data/core.telegram.org/constructor/updateServiceNotification.html new file mode 100644 index 0000000000..e724518904 --- /dev/null +++ b/data/core.telegram.org/constructor/updateServiceNotification.html @@ -0,0 +1,183 @@ + + + + + updateServiceNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

updateServiceNotification

+ +

A service message for the user.

+

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

+

+ +
+
updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?true(boolTrue) if the message must be displayed in a popup.
inbox_dateflags.1?intWhen was the notification received
The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
typestringString, identical in format and contents to the type field in API errors. Describes type of service message. It is acceptable to ignore repeated messages of the same type within a short period of time (15 minutes).
messagestringMessage text
mediaMessageMediaMedia content (optional)
entitiesVector<MessageEntity>Message entities for styled text
+

Type

+

Update

+

Related pages

+

Error handling

+

How to handle API return errors correctly.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateShort.html b/data/core.telegram.org/constructor/updateShort.html new file mode 100644 index 0000000000..a12ae23837 --- /dev/null +++ b/data/core.telegram.org/constructor/updateShort.html @@ -0,0 +1,152 @@ + + + + + updateShort + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShort

+ +

Shortened constructor containing info on one update not requiring auxiliary data

+

+ +
+
updateShort#78d4dec1 update:Update date:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
updateUpdateUpdate
dateintDate of event
+

Type

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateShortMessage.html b/data/core.telegram.org/constructor/updateShortMessage.html new file mode 100644 index 0000000000..8221fbc669 --- /dev/null +++ b/data/core.telegram.org/constructor/updateShortMessage.html @@ -0,0 +1,229 @@ + + + + + updateShortMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShortMessage

+ +

Info about a message sent to (received from) another user

+

+ +
+
updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether there are some unread mentions in this message
silentflags.13?trueIf true, the message is a silent message, no notifications should be triggered
idintThe message ID
user_idlongThe ID of the sender (if outgoing will be the ID of the destination) of the message
messagestringThe message
ptsintPTS
pts_countintPTS count
dateintdate
fwd_fromflags.2?MessageFwdHeaderInfo about a forwarded message
via_bot_idflags.11?longInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply and thread information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Updates

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateShortSentMessage.html b/data/core.telegram.org/constructor/updateShortSentMessage.html new file mode 100644 index 0000000000..a3a338533f --- /dev/null +++ b/data/core.telegram.org/constructor/updateShortSentMessage.html @@ -0,0 +1,192 @@ + + + + + updateShortSentMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShortSentMessage

+ +

Shortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).

+

+ +
+
updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
idintID of the sent message
ptsintPTS
pts_countintPTS count
dateintdate
mediaflags.9?MessageMediaAttached media
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Updates

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateStickerSets.html b/data/core.telegram.org/constructor/updateStickerSets.html new file mode 100644 index 0000000000..3e7e2547b4 --- /dev/null +++ b/data/core.telegram.org/constructor/updateStickerSets.html @@ -0,0 +1,132 @@ + + + + + updateStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

updateStickerSets

+ +

Installed stickersets have changed, the client should refetch them using messages.getAllStickers

+

+ +
+
updateStickerSets#43ae3dec = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateStickerSetsOrder.html b/data/core.telegram.org/constructor/updateStickerSetsOrder.html new file mode 100644 index 0000000000..776a9c9fe7 --- /dev/null +++ b/data/core.telegram.org/constructor/updateStickerSetsOrder.html @@ -0,0 +1,157 @@ + + + + + updateStickerSetsOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

updateStickerSetsOrder

+ +

The order of stickersets was changed

+

+ +
+
updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether the updated stickers are mask stickers
orderVector<long>New sticker order by sticker ID
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateTheme.html b/data/core.telegram.org/constructor/updateTheme.html new file mode 100644 index 0000000000..c987d45e7d --- /dev/null +++ b/data/core.telegram.org/constructor/updateTheme.html @@ -0,0 +1,147 @@ + + + + + updateTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

updateTheme

+ +

A cloud theme was updated

+

+ +
+
updateTheme#8216fba3 theme:Theme = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
themeThemeTheme
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateUserBlocked.html b/data/core.telegram.org/constructor/updateUserBlocked.html new file mode 100644 index 0000000000..0890b946fd --- /dev/null +++ b/data/core.telegram.org/constructor/updateUserBlocked.html @@ -0,0 +1,159 @@ + + + + + updateUserBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserBlocked

+ +

User was added to the blacklist (method contacts.block) or removed from the blacklist (method contacts.unblock).

+

+ +
+
Constructor schema is available as of layer 119. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idintUser id
blockedBool(boolTrue) if the the user is blocked
+

Type

+

Update

+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

contacts.block

+

Adds the user to the blacklist.

+

contacts.unblock

+

Deletes the user from the blacklist.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateUserName.html b/data/core.telegram.org/constructor/updateUserName.html new file mode 100644 index 0000000000..067c54060a --- /dev/null +++ b/data/core.telegram.org/constructor/updateUserName.html @@ -0,0 +1,167 @@ + + + + + updateUserName + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserName

+ +

Changes the user's first name, last name and username.

+

+ +
+
updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
first_namestringNew first name. Corresponds to the new value of real_first_name field of the userFull constructor.
last_namestringNew last name. Corresponds to the new value of real_last_name field of the userFull constructor.
usernamestringNew username.
Parameter added in Layer 18.
+

Type

+

Update

+

Related pages

+

userFull

+

Extended user info

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateUserPhone.html b/data/core.telegram.org/constructor/updateUserPhone.html new file mode 100644 index 0000000000..77c322cd7d --- /dev/null +++ b/data/core.telegram.org/constructor/updateUserPhone.html @@ -0,0 +1,152 @@ + + + + + updateUserPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserPhone

+ +

A user's phone number was changed

+

+ +
+
updateUserPhone#5492a13 user_id:long phone:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
phonestringNew phone number
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateUserPhoto.html b/data/core.telegram.org/constructor/updateUserPhoto.html new file mode 100644 index 0000000000..7780786a47 --- /dev/null +++ b/data/core.telegram.org/constructor/updateUserPhoto.html @@ -0,0 +1,165 @@ + + + + + updateUserPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserPhoto

+ +

Change of contact's profile photo.

+

+ +
+
updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
dateintDate of photo update.
photoUserProfilePhotoNew profile photo
previousBool(boolTrue), if one of the previously used photos is set a profile photo.
+

Type

+

Update

+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateUserStatus.html b/data/core.telegram.org/constructor/updateUserStatus.html new file mode 100644 index 0000000000..0cc8b39514 --- /dev/null +++ b/data/core.telegram.org/constructor/updateUserStatus.html @@ -0,0 +1,152 @@ + + + + + updateUserStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserStatus

+ +

Contact status update.

+

+ +
+
updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
statusUserStatusNew status
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateUserTyping.html b/data/core.telegram.org/constructor/updateUserTyping.html new file mode 100644 index 0000000000..4abd9a1760 --- /dev/null +++ b/data/core.telegram.org/constructor/updateUserTyping.html @@ -0,0 +1,155 @@ + + + + + updateUserTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserTyping

+ +

The user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

+

+ +
+
updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser id
actionSendMessageActionAction type
Param added in Layer 17.
+

Type

+

Update

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateWebPage.html b/data/core.telegram.org/constructor/updateWebPage.html new file mode 100644 index 0000000000..516f3dfcf9 --- /dev/null +++ b/data/core.telegram.org/constructor/updateWebPage.html @@ -0,0 +1,160 @@ + + + + + updateWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateWebPage

+ +

An instant view webpage preview was generated

+

+ +
+
updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
webpageWebPageWebpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.channelDifference b/data/core.telegram.org/constructor/updates.channelDifference new file mode 100644 index 0000000000..5cfe96f6c3 --- /dev/null +++ b/data/core.telegram.org/constructor/updates.channelDifference @@ -0,0 +1,185 @@ + + + + + updates.channelDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.channelDifference

+ +

The new updates

+

+ +
+
updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates to be fetched using getDifference, starting from the provided pts
ptsintThe PTS from which to start getting updates the next time
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
new_messagesVector<Message>New messages
other_updatesVector<Update>Other updates
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

updates.ChannelDifference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.channelDifferenceEmpty b/data/core.telegram.org/constructor/updates.channelDifferenceEmpty new file mode 100644 index 0000000000..4d921e9a5c --- /dev/null +++ b/data/core.telegram.org/constructor/updates.channelDifferenceEmpty @@ -0,0 +1,165 @@ + + + + + updates.channelDifferenceEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.channelDifferenceEmpty

+ +

There are no new updates

+

+ +
+
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
ptsintThe latest PTS
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
+

Type

+

updates.ChannelDifference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.channelDifferenceTooLong b/data/core.telegram.org/constructor/updates.channelDifferenceTooLong new file mode 100644 index 0000000000..82b6ea7081 --- /dev/null +++ b/data/core.telegram.org/constructor/updates.channelDifferenceTooLong @@ -0,0 +1,190 @@ + + + + + updates.channelDifferenceTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.channelDifferenceTooLong

+ +

The provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

+
    +
  1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
  2. +
  3. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
  4. +
  5. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
  6. +
  7. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
  8. +
+

+ +
+
updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
dialogDialogDialog containing the latest PTS that can be used to reset the channel state
messagesVector<Message>The latest messages
chatsVector<Chat>Chats from messages
usersVector<User>Users from messages
+

Type

+

updates.ChannelDifference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

messages.getHistory

+

Gets back the conversation history with one interlocutor / within a chat

+

messages.getMessages

+

Returns the list of messages by their IDs.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.difference b/data/core.telegram.org/constructor/updates.difference new file mode 100644 index 0000000000..fe42f002ed --- /dev/null +++ b/data/core.telegram.org/constructor/updates.difference @@ -0,0 +1,172 @@ + + + + + updates.difference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.difference

+ +

Full list of occurred events.

+

+ +
+
updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
new_messagesVector<Message>List of new messages
new_encrypted_messagesVector<EncryptedMessage>List of new encrypted secret chat messages
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
stateupdates.StateCurrent state
+

Type

+

updates.Difference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.differenceEmpty b/data/core.telegram.org/constructor/updates.differenceEmpty new file mode 100644 index 0000000000..9035d2548b --- /dev/null +++ b/data/core.telegram.org/constructor/updates.differenceEmpty @@ -0,0 +1,152 @@ + + + + + updates.differenceEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceEmpty

+ +

No events.

+

+ +
+
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dateintCurrent date
seqintNumber of sent updates
+

Type

+

updates.Difference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.differenceSlice b/data/core.telegram.org/constructor/updates.differenceSlice new file mode 100644 index 0000000000..836ba3aa41 --- /dev/null +++ b/data/core.telegram.org/constructor/updates.differenceSlice @@ -0,0 +1,175 @@ + + + + + updates.differenceSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceSlice

+ +

Incomplete list of occurred events.

+

+ +
+
updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
new_messagesVector<Message>List of new messgaes
new_encrypted_messagesVector<EncryptedMessage>New messages from the encrypted event sequence
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
intermediate_stateupdates.StateIntermediary state
+

Type

+

updates.Difference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.differenceTooLong b/data/core.telegram.org/constructor/updates.differenceTooLong new file mode 100644 index 0000000000..3217397acc --- /dev/null +++ b/data/core.telegram.org/constructor/updates.differenceTooLong @@ -0,0 +1,150 @@ + + + + + updates.differenceTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceTooLong

+ +

The difference is too long, and the specified state must be used to refetch updates.

+

+ +
+
updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
ptsintThe new state to use.
+

Type

+

updates.Difference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.html b/data/core.telegram.org/constructor/updates.html new file mode 100644 index 0000000000..19eaddce47 --- /dev/null +++ b/data/core.telegram.org/constructor/updates.html @@ -0,0 +1,167 @@ + + + + + Updates + + + + + + + + + + + + + +
+ +
+
+
+ +

Updates

+ +

Full constructor of updates

+

+ +
+
updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seqintTotal number of sent updates
+

Type

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.state b/data/core.telegram.org/constructor/updates.state new file mode 100644 index 0000000000..0cb5396b9d --- /dev/null +++ b/data/core.telegram.org/constructor/updates.state @@ -0,0 +1,172 @@ + + + + + updates.state + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.state

+ +

Updates state.

+

+ +
+
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintNumber of events occured in a text box
qtsintPosition in a sequence of updates in secret chats. For further detailes refer to article secret chats
Parameter was added in eigth layer.
dateintDate of condition
seqintNumber of sent updates
unread_countintNumber of unread messages
+

Type

+

updates.State

+

Related pages

+

End-to-End Encryption, Secret Chats

+

New feature for end-to-end-encrypted messaging.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatesCombined.html b/data/core.telegram.org/constructor/updatesCombined.html new file mode 100644 index 0000000000..5492a443a0 --- /dev/null +++ b/data/core.telegram.org/constructor/updatesCombined.html @@ -0,0 +1,172 @@ + + + + + updatesCombined + + + + + + + + + + + + + +
+ +
+
+
+ +

updatesCombined

+ +

Constructor for a group of updates.

+

+ +
+
updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seq_startintValue seq for the earliest update in a group
seqintValue seq for the latest update in a group
+

Type

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatesTooLong.html b/data/core.telegram.org/constructor/updatesTooLong.html new file mode 100644 index 0000000000..1c23cb9265 --- /dev/null +++ b/data/core.telegram.org/constructor/updatesTooLong.html @@ -0,0 +1,135 @@ + + + + + updatesTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updatesTooLong

+ +

Too many updates, it is necessary to execute updates.getDifference.

+

+ +
+
updatesTooLong#e317af7e = Updates;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Updates

+

Related pages

+

updates.getDifference

+

Get new updates.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/upload.cdnFile b/data/core.telegram.org/constructor/upload.cdnFile new file mode 100644 index 0000000000..b50c25186c --- /dev/null +++ b/data/core.telegram.org/constructor/upload.cdnFile @@ -0,0 +1,149 @@ + + + + + upload.cdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.cdnFile

+ +

Represent a chunk of a CDN file.

+

+ +
+
upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
bytesbytesThe data
+

Type

+

upload.CdnFile

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded b/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded new file mode 100644 index 0000000000..369787176d --- /dev/null +++ b/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded @@ -0,0 +1,149 @@ + + + + + upload.cdnFileReuploadNeeded + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.cdnFileReuploadNeeded

+ +

The file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.

+

+ +
+
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
request_tokenbytesRequest token (see CDN)
+

Type

+

upload.CdnFile

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/upload.file b/data/core.telegram.org/constructor/upload.file new file mode 100644 index 0000000000..aff8630cd4 --- /dev/null +++ b/data/core.telegram.org/constructor/upload.file @@ -0,0 +1,157 @@ + + + + + upload.file + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.file

+ +

File content.

+

+ +
+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestorage.FileTypeFile type
mtimeintModification type
bytesbytesBinary data, file content
+

Type

+

upload.File

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/upload.fileCdnRedirect b/data/core.telegram.org/constructor/upload.fileCdnRedirect new file mode 100644 index 0000000000..cf7db284bd --- /dev/null +++ b/data/core.telegram.org/constructor/upload.fileCdnRedirect @@ -0,0 +1,169 @@ + + + + + upload.fileCdnRedirect + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.fileCdnRedirect

+ +

The file must be downloaded from a CDN DC.

+

+ +
+
upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintCDN DC ID
file_tokenbytesFile token (see CDN files)
encryption_keybytesEncryption key (see CDN files)
encryption_ivbytesEncryption IV (see CDN files)
file_hashesVector<FileHash>File hashes (see CDN files)
+

Type

+

upload.File

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/upload.webFile b/data/core.telegram.org/constructor/upload.webFile new file mode 100644 index 0000000000..0e2ae5132c --- /dev/null +++ b/data/core.telegram.org/constructor/upload.webFile @@ -0,0 +1,170 @@ + + + + + upload.webFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.webFile

+ +

Represents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers

+

+ +
+
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
sizeintFile size
mime_typestringMime type
file_typestorage.FileTypeFile type
mtimeintModified time
bytesbytesData
+

Type

+

upload.WebFile

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/urlAuthResultAccepted.html b/data/core.telegram.org/constructor/urlAuthResultAccepted.html new file mode 100644 index 0000000000..3f41ade644 --- /dev/null +++ b/data/core.telegram.org/constructor/urlAuthResultAccepted.html @@ -0,0 +1,150 @@ + + + + + urlAuthResultAccepted + + + + + + + + + + + + + +
+ +
+
+
+ +

urlAuthResultAccepted

+ +

Details about an accepted authorization request, for more info click here »

+

+ +
+
urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringThe URL name of the website on which the user has logged in.
+

Type

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/urlAuthResultDefault.html b/data/core.telegram.org/constructor/urlAuthResultDefault.html new file mode 100644 index 0000000000..ec78328aee --- /dev/null +++ b/data/core.telegram.org/constructor/urlAuthResultDefault.html @@ -0,0 +1,135 @@ + + + + + urlAuthResultDefault + + + + + + + + + + + + + +
+ +
+
+
+ +

urlAuthResultDefault

+ +

Details about an accepted authorization request, for more info click here »

+

+ +
+
urlAuthResultDefault#a9d6db1f = UrlAuthResult;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/urlAuthResultRequest.html b/data/core.telegram.org/constructor/urlAuthResultRequest.html new file mode 100644 index 0000000000..a2bf6d57bd --- /dev/null +++ b/data/core.telegram.org/constructor/urlAuthResultRequest.html @@ -0,0 +1,165 @@ + + + + + urlAuthResultRequest + + + + + + + + + + + + + +
+ +
+
+
+ +

urlAuthResultRequest

+ +

Details about the authorization request, for more info click here »

+

+ +
+
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueWhether the bot would like to send messages to the user
botUserUsername of a bot, which will be used for user authorization. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
domainstringThe domain name of the website on which the user will log in.
+

Type

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/user.html b/data/core.telegram.org/constructor/user.html new file mode 100644 index 0000000000..b6d8f4eddb --- /dev/null +++ b/data/core.telegram.org/constructor/user.html @@ -0,0 +1,287 @@ + + + + + user + + + + + + + + + + + + + +
+ +
+
+
+ +

user

+ +

Indicates info about a certain user

+

+ +
+
user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
selfflags.10?trueWhether this user indicates the currently logged in user
contactflags.11?trueWhether this user is a contact
mutual_contactflags.12?trueWhether this user is a mutual contact
deletedflags.13?trueWhether the account of this user was deleted
botflags.14?trueIs this user a bot?
bot_chat_historyflags.15?trueCan the bot see all messages in groups?
bot_nochatsflags.16?trueCan the bot be added to groups?
verifiedflags.17?trueWhether this user is verified
restrictedflags.18?trueAccess to this user must be restricted for the reason specified in restriction_reason
minflags.20?trueSee min
bot_inline_geoflags.21?trueWhether the bot can request our geolocation in inline mode
supportflags.23?trueWhether this is an official support user
scamflags.24?trueThis may be a scam user
apply_min_photoflags.25?trueIf set, the profile picture for this user should be refetched
fakeflags.26?trueIf set, this user was reported by many users as a fake or scam user: be careful when interacting with them.
idlongID of the user
access_hashflags.0?longAccess hash of the user
first_nameflags.1?stringFirst name
last_nameflags.2?stringLast name
usernameflags.3?stringUsername
phoneflags.4?stringPhone number
photoflags.5?UserProfilePhotoProfile picture of user
statusflags.6?UserStatusOnline status of user
bot_info_versionflags.14?intVersion of the bot_info field in userFull, incremented every time it changes
restriction_reasonflags.18?Vector<RestrictionReason>Contains the reason why access to this user must be restricted.
bot_inline_placeholderflags.19?stringInline placeholder for this inline bot
lang_codeflags.22?stringLanguage code of the user
+

Type

+

User

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

userFull

+

Extended user info

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userEmpty.html b/data/core.telegram.org/constructor/userEmpty.html new file mode 100644 index 0000000000..191eeda7c8 --- /dev/null +++ b/data/core.telegram.org/constructor/userEmpty.html @@ -0,0 +1,147 @@ + + + + + userEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

userEmpty

+ +

Empty constructor, non-existent user.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongUser identifier or 0
+

Type

+

User

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userFull.html b/data/core.telegram.org/constructor/userFull.html new file mode 100644 index 0000000000..2ea79bc0e1 --- /dev/null +++ b/data/core.telegram.org/constructor/userFull.html @@ -0,0 +1,239 @@ + + + + + userFull + + + + + + + + + + + + + +
+ +
+
+
+ +

userFull

+ +

Extended user info

+

+ +
+
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
blockedflags.0?trueWhether you have blocked this user
phone_calls_availableflags.4?trueWhether this user can make VoIP calls
phone_calls_privateflags.5?trueWhether this user's privacy settings allow you to call him
can_pin_messageflags.7?trueWhether you can pin messages in the chat with this user, you can do this only for a chat with yourself
has_scheduledflags.12?trueWhether scheduled messages are available
video_calls_availableflags.13?trueWhether the user can receive video calls
userUserRemaining user info
aboutflags.1?stringBio of the user
settingsPeerSettingsPeer settings
profile_photoflags.2?PhotoProfile photo
notify_settingsPeerNotifySettingsNotification settings
bot_infoflags.3?BotInfoFor bots, info about the bot (bot commands, etc)
pinned_msg_idflags.6?intMessage ID of the last pinned message
common_chats_countintChats in common with this user
folder_idflags.11?intPeer folder ID, for more info click here
ttl_periodflags.14?intTime To Live of all messages in this chat; once a message is this many seconds old, it must be deleted.
theme_emoticonflags.15?stringEmoji associated with chat theme
+

Type

+

UserFull

+

Related pages

+

Scheduled messages

+

Telegram allows scheduling messages

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userProfilePhoto.html b/data/core.telegram.org/constructor/userProfilePhoto.html new file mode 100644 index 0000000000..d74ed77ce8 --- /dev/null +++ b/data/core.telegram.org/constructor/userProfilePhoto.html @@ -0,0 +1,172 @@ + + + + + userProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

userProfilePhoto

+ +

User profile photo.

+

+ +
+
userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether an animated profile picture is available for this user
photo_idlongIdentifier of the respective photo
Parameter added in Layer 2
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC ID where the photo is stored
+

Type

+

UserProfilePhoto

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userProfilePhotoEmpty.html b/data/core.telegram.org/constructor/userProfilePhotoEmpty.html new file mode 100644 index 0000000000..cf1ead2630 --- /dev/null +++ b/data/core.telegram.org/constructor/userProfilePhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + userProfilePhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

userProfilePhotoEmpty

+ +

Profile photo has not been set, or was hidden.

+

+ +
+
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserProfilePhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusEmpty.html b/data/core.telegram.org/constructor/userStatusEmpty.html new file mode 100644 index 0000000000..b83f28c2c0 --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusEmpty.html @@ -0,0 +1,132 @@ + + + + + userStatusEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusEmpty

+ +

User status has not been set yet.

+

+ +
+
userStatusEmpty#9d05049 = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusLastMonth.html b/data/core.telegram.org/constructor/userStatusLastMonth.html new file mode 100644 index 0000000000..04c6f0d8d8 --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusLastMonth.html @@ -0,0 +1,132 @@ + + + + + userStatusLastMonth + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusLastMonth

+ +

Online status: last seen last month

+

+ +
+
userStatusLastMonth#77ebc742 = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusLastWeek.html b/data/core.telegram.org/constructor/userStatusLastWeek.html new file mode 100644 index 0000000000..69d55d347c --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusLastWeek.html @@ -0,0 +1,132 @@ + + + + + userStatusLastWeek + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusLastWeek

+ +

Online status: last seen last week

+

+ +
+
userStatusLastWeek#7bf09fc = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusOffline.html b/data/core.telegram.org/constructor/userStatusOffline.html new file mode 100644 index 0000000000..ad3d0401f7 --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusOffline.html @@ -0,0 +1,147 @@ + + + + + userStatusOffline + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusOffline

+ +

The user's offline status.

+

+ +
+
userStatusOffline#8c703f was_online:int = UserStatus;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
was_onlineintTime the user was last seen online
+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusOnline.html b/data/core.telegram.org/constructor/userStatusOnline.html new file mode 100644 index 0000000000..4b7f165d9c --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusOnline.html @@ -0,0 +1,147 @@ + + + + + userStatusOnline + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusOnline

+ +

Online status of the user.

+

+ +
+
userStatusOnline#edb93949 expires:int = UserStatus;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintTime to expiration of the current online status
+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusRecently.html b/data/core.telegram.org/constructor/userStatusRecently.html new file mode 100644 index 0000000000..9910e5a4f7 --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusRecently.html @@ -0,0 +1,132 @@ + + + + + userStatusRecently + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusRecently

+ +

Online status: last seen recently

+

+ +
+
userStatusRecently#e26f42f1 = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/vector.html b/data/core.telegram.org/constructor/vector.html new file mode 100644 index 0000000000..4b7754b27b --- /dev/null +++ b/data/core.telegram.org/constructor/vector.html @@ -0,0 +1,134 @@ + + + + + vector + + + + + + + + + + + + + +
+ +
+
+
+ +

vector

+ +

A universal vector constructor.

+

+ +
+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Vector t

+

Params additional

+

For serialization write the constructor id 0x1cb5c415:int, then the number of vector elements - #:int, then, one after another, the # of the elements of the type t, that was implicitly passed to the constructor.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/videoSize.html b/data/core.telegram.org/constructor/videoSize.html new file mode 100644 index 0000000000..03edb72674 --- /dev/null +++ b/data/core.telegram.org/constructor/videoSize.html @@ -0,0 +1,175 @@ + + + + + videoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

videoSize

+ +

Animated profile picture in MPEG4 format

+

+ +
+
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typestringu for animated profile pictures, and v for trimmed and downscaled video previews
wintVideo width
hintVideo height
sizeintFile size
video_start_tsflags.0?doubleTimestamp that should be shown as static preview to the user (seconds)
+

Type

+

VideoSize

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/wallPaper.html b/data/core.telegram.org/constructor/wallPaper.html new file mode 100644 index 0000000000..309380f275 --- /dev/null +++ b/data/core.telegram.org/constructor/wallPaper.html @@ -0,0 +1,192 @@ + + + + + wallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaper

+ +

Wallpaper settings.

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongIdentifier
flags#Flags, see TL conditional fields
creatorflags.0?trueCreator of the wallpaper
defaultflags.1?trueWhether this is the default wallpaper
patternflags.3?truePattern
darkflags.4?trueDark mode
access_hashlongAccess hash
slugstringUnique wallpaper ID
documentDocumentThe actual wallpaper
settingsflags.2?WallPaperSettingsWallpaper settings
+

Type

+

WallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/wallPaperNoFile.html b/data/core.telegram.org/constructor/wallPaperNoFile.html new file mode 100644 index 0000000000..dd043811ee --- /dev/null +++ b/data/core.telegram.org/constructor/wallPaperNoFile.html @@ -0,0 +1,171 @@ + + + + + wallPaperNoFile + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaperNoFile

+ +

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.
+Also used for some default wallpapers which contain only colours.

+

+ +
+
wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongWallpaper ID
flags#Flags, see TL conditional fields
defaultflags.1?trueWhether this is the default wallpaper
darkflags.4?trueDark mode
settingsflags.2?WallPaperSettingsWallpaper settings
+

Type

+

WallPaper

+

Related pages

+

account.saveWallPaper

+

Install/uninstall wallpaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/wallPaperSettings.html b/data/core.telegram.org/constructor/wallPaperSettings.html new file mode 100644 index 0000000000..175e5095ba --- /dev/null +++ b/data/core.telegram.org/constructor/wallPaperSettings.html @@ -0,0 +1,187 @@ + + + + + wallPaperSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaperSettings

+ +

Wallpaper settings

+

+ +
+
wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
blurflags.1?trueIf set, the wallpaper must be downscaled to fit in 450x450 square and then box-blurred with radius 12
motionflags.2?trueIf set, the background needs to be slightly moved when device is rotated
background_colorflags.0?intIf set, a PNG pattern is to be combined with the color chosen by the user: the main color of the background in RGB24 format
second_background_colorflags.4?intIf set, a PNG pattern is to be combined with the first and second background colors (RGB24 format) in a top-bottom gradient
third_background_colorflags.5?intIf set, a PNG pattern is to be combined with the first, second and third background colors (RGB24 format) in a freeform gradient
fourth_background_colorflags.6?intIf set, a PNG pattern is to be combined with the first, second, third and fourth background colors (RGB24 format) in a freeform gradient
intensityflags.3?intIntensity of the pattern when it is shown above the main background color, 0-100
rotationflags.4?intClockwise rotation angle of the gradient, in degrees; 0-359. Should be always divisible by 45
+

Type

+

WallPaperSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/wallPaperSolid.html b/data/core.telegram.org/constructor/wallPaperSolid.html new file mode 100644 index 0000000000..435ebb5bc5 --- /dev/null +++ b/data/core.telegram.org/constructor/wallPaperSolid.html @@ -0,0 +1,162 @@ + + + + + wallPaperSolid + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaperSolid

+ +

One-color background wallpaper (no image).

+

+ +
+
Constructor schema is available as of layer 93. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintIdentifier
titlestringName
bg_colorintBackground color (RGB)
colorintBasic background color (RGB)
+

Type

+

WallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webAuthorization.html b/data/core.telegram.org/constructor/webAuthorization.html new file mode 100644 index 0000000000..f90b8e5141 --- /dev/null +++ b/data/core.telegram.org/constructor/webAuthorization.html @@ -0,0 +1,189 @@ + + + + + webAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

webAuthorization

+ +

Represents a bot logged in using the Telegram login widget

+

+ +
+
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongAuthorization hash
bot_idlongBot ID
domainstringThe domain name of the website on which the user has logged in.
browserstringBrowser user-agent
platformstringPlatform
date_createdintWhen was the web session created
date_activeintWhen was the web session last active
ipstringIP address
regionstringRegion, determined from IP address
+

Type

+

WebAuthorization

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webDocument.html b/data/core.telegram.org/constructor/webDocument.html new file mode 100644 index 0000000000..6f07616c6b --- /dev/null +++ b/data/core.telegram.org/constructor/webDocument.html @@ -0,0 +1,167 @@ + + + + + webDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

webDocument

+ +

Remote document

+

+ +
+
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringDocument URL
access_hashlongAccess hash
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
+

Type

+

WebDocument

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webDocumentNoProxy.html b/data/core.telegram.org/constructor/webDocumentNoProxy.html new file mode 100644 index 0000000000..81ebe54d51 --- /dev/null +++ b/data/core.telegram.org/constructor/webDocumentNoProxy.html @@ -0,0 +1,165 @@ + + + + + webDocumentNoProxy + + + + + + + + + + + + + +
+ +
+
+
+ +

webDocumentNoProxy

+ +

Remote document that can be downloaded without proxying through telegram

+

+ +
+
webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringDocument URL
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
+

Type

+

WebDocument

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webPage.html b/data/core.telegram.org/constructor/webPage.html new file mode 100644 index 0000000000..2278dac240 --- /dev/null +++ b/data/core.telegram.org/constructor/webPage.html @@ -0,0 +1,240 @@ + + + + + webPage + + + + + + + + + + + + + +
+ +
+
+
+ +

webPage

+ +

Webpage preview

+

+ +
+
webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idlongPreview ID
urlstringURL of previewed webpage
display_urlstringWebpage URL to be displayed to the user
hashintHash for pagination, for more info click here
typeflags.0?stringType of the web page. Can be: article, photo, audio, video, document, profile, app, or something else
site_nameflags.1?stringShort name of the site (e.g., Google Docs, App Store)
titleflags.2?stringTitle of the content
descriptionflags.3?stringContent description
photoflags.4?PhotoImage representing the content
embed_urlflags.5?stringURL to show in the embedded preview
embed_typeflags.5?stringMIME type of the embedded preview, (e.g., text/html or video/mp4)
embed_widthflags.6?intWidth of the embedded preview
embed_heightflags.6?intHeight of the embedded preview
durationflags.7?intDuration of the content, in seconds
authorflags.8?stringAuthor of the content
documentflags.9?DocumentPreview of the content as a media file
cached_pageflags.10?PagePage contents in instant view format
attributesflags.12?Vector<WebPageAttribute>Webpage attributes
+

Type

+

WebPage

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webPageAttributeTheme.html b/data/core.telegram.org/constructor/webPageAttributeTheme.html new file mode 100644 index 0000000000..7d464abca6 --- /dev/null +++ b/data/core.telegram.org/constructor/webPageAttributeTheme.html @@ -0,0 +1,157 @@ + + + + + webPageAttributeTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

webPageAttributeTheme

+ +

Page theme

+

+ +
+
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
documentsflags.0?Vector<Document>Theme files
settingsflags.1?ThemeSettingsTheme settings
+

Type

+

WebPageAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webPageEmpty.html b/data/core.telegram.org/constructor/webPageEmpty.html new file mode 100644 index 0000000000..0f77f8fbb5 --- /dev/null +++ b/data/core.telegram.org/constructor/webPageEmpty.html @@ -0,0 +1,147 @@ + + + + + webPageEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

webPageEmpty

+ +

No preview is available for the webpage

+

+ +
+
webPageEmpty#eb1477e8 id:long = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongPreview ID
+

Type

+

WebPage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webPageNotModified.html b/data/core.telegram.org/constructor/webPageNotModified.html new file mode 100644 index 0000000000..1ea6beaf22 --- /dev/null +++ b/data/core.telegram.org/constructor/webPageNotModified.html @@ -0,0 +1,152 @@ + + + + + webPageNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

webPageNotModified

+ +

The preview of the webpage hasn't changed

+

+ +
+
webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
cached_page_viewsflags.0?intPage view count
+

Type

+

WebPage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webPagePending.html b/data/core.telegram.org/constructor/webPagePending.html new file mode 100644 index 0000000000..f116f7ff33 --- /dev/null +++ b/data/core.telegram.org/constructor/webPagePending.html @@ -0,0 +1,152 @@ + + + + + webPagePending + + + + + + + + + + + + + +
+ +
+
+
+ +

webPagePending

+ +

A preview of the webpage is currently being generated

+

+ +
+
webPagePending#c586da1c id:long date:int = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID of preview
dateintWhen was the processing started
+

Type

+

WebPage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/contest300K.html b/data/core.telegram.org/contest300K.html new file mode 100644 index 0000000000..86ddea9c34 --- /dev/null +++ b/data/core.telegram.org/contest300K.html @@ -0,0 +1,237 @@ + + + + + Telegram Cracking Contest Description + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram Cracking Contest Description

+ +

« Back to Contest Announcement

+
+

The current round of the contest is over. Go to results »

+
+

In this contest you assume the role of a malicious entity in control of Telegram's servers. Your goal is to extract sensitive data (a secret email and password) from a conversation between two peers — Paul and Nick. They are represented by two virtual users that communicate via Secret Chats in Telegram.

+

Paul and Nick are both using clients that perform all the checks from Telegram Security Guidelines and compare their key visualizations over an independent channel as soon as a new Secret Chat is established. If any of these checks fails, they stop accepting messages in that Secret Chat. You control the entire process by sending commands to the Telegram user @CryptoContest, used as an interface for this contest. This enables contestants to try CPA, KPA, MITM and other kinds of active attacks and data tampering.

+

Protocol

+

The protocol used by Paul and Nick to establish Secret Сhats and exchange messages is identical to the one used for Secret Chats in Telegram. Since we assume that the attacker is already in full control of the Telegram servers, basic MTProto encryption is bypassed altogether. In order to further simplify the task for contestants, we have removed irrelevant parameters, such as user_id and random_id.

+

The following TL scheme is used to establish Secret Chats in this contest:

+
contest.dhConfig#01e00a51 g:int p:64*[int] random:64*[int] = contest.DhConfig;
+contest.requestEncryption#3a73a74c g_a:64*[int] = contest.Message;
+contest.acceptEncryption#068e4342 g_b:64*[int] fingerprint:int = contest.Message;
+contest.encryptedMessage#11a6d4b1 id:long message:string = contest.Message;
+---functions---
+contest.getDhConfig#369ee1a6 = contest.DhConfig;
+

For exchange of encrypted messages (see documentation), the up-to-date layer 17 scheme with sequence numbers is used, but with plain text message support only.

+

Each plaintext message is first created as a layer 17 decryptedMessage, then embedded in a decryptedMessageLayer and encrypted as explained in the Secret Chat documentation. For the purpose of this contest, it is the result of this encryption (ciphertext) that is exchanged between the parties.

+

Notice that sending messages in an actual Telegram Secret Chat involves further embedding of that ciphertext into an API call and an additional layer of MTProto encryption for client-server interaction. This step is omitted here, since we assume the attacker to be in control of the Telegram servers, not just of the communication lines between the clients and Telegram servers.

+

Interface

+

To access the interface, find the Telegram user @CryptoContest using the Global Search by username in any of the Telegram apps. This is a special bot we created for this contest. You can control communication between Paul and Nick by sending particularly formed text messages to this bot and processing automatically generated answers to these messages (you may find the unofficial Linux CLI convenient for mass automated queries).

+

You can create as many parallel Secret Chats between Paul and Nick as you like using the bot — each of them will have a separate session_id. All data is represented in hexadecimal format, with the exception of the session_id.

+

Commands

+

Below, A stands for the creator of the Secret Chat, B stands for the second party, S — the Telegram Server.

+

Each Secret Chat session in this contest is divided in two phases:

+ +
1. Creating a Secret Chat
+

In order to create a new Secret Chat, six messages need to be exchanged:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SourceDestinationMessage
AScontest.getDhConfig
SAcontest.DhConfig
ABcontest.requestEncryption
BScontest.getDhConfig
SBcontest.DhConfig
BAcontest.acceptEncryption
+

To create a Secret Chat in this contest:

+
    +
  • Send the START command to the user @CryptoContest in Telegram. You'll get the getDhConfig query, sent by A to the Server, and the answer that the server would normally send to A. You shall also receive the new session_id as the first 32-bit integer. All further messages related to this particular session (Secret Chat instance) must be prefixed with this session_id in decimal form.
  • +
  • After that, use the PASS command to pass the server's answer to A or ANSWER bytes to send a different answer instead. Bytes is represented by a string of an even number of hexadecimal digits. You'll receive the requestEncryption query as the result.
  • +
  • After that, use the PASS command to pass this query to B or ANSWER bytes to arbitrarily change it. You‘ll receive B’s getDhConfig to the server as the result.
  • +
  • As before, you can use either PASS or ANSWER bytes. You'll receive acceptEncryption as the result.
  • +
  • As before, you can use either PASS or ANSWER bytes. You'll receive “Ok” as the result.
  • +
+

You will receive an error text as the result after any of these steps in case the participating clients perceive that something went wrong. This can happen if a security check is failed, or in the case that the first 128 bits of the SHA-1 of the newly created encryption key don‘t match on both parties’ clients when this stage is completed (this corresponds to Paul and Nick comparing the key visualizations for the Secret Chat in their Telegram apps).

+

If you obtain such an error, the session is failed and can no longer be used. You'll have to start new session. Note that the time to complete this phase is limited. Each step should not take longer than one hour, otherwise the Secret Chat will get cancelled.

+

Example:

+
START
+15 a6e19e36 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b202d33053c2340fd84dd024e8012277e9c6442ad7cd09fe85955c13196e2d32861ad0d8f8139ce5870f1c3563fbff77428632897352abd91cd0a6497a0f64a33d87cd8b53470cf1bc6a052bba7d0121623e9611c0de83ffeb63b7d15831a70187093373cb20df5613bdfab12a54bbc6fff94598d95a8dcdb1374631b021e77c350261bca9ffc16c59b19d3041bee011a20b06fc9806d633b6b9cdd79cbb8b02fe8ef9dde29b6d31d80b030c69d67d6fc4a7edb33ffab532d085796cf3e7635fd42ee72ea24840082186fd40c3c45cf0acef886533d4de7468f88942a662d302928470aa8704529180a6aec2f877398efb91893cc9b549e5123d7269adfe7b6ee
+15 PASS
+15 4ca7733a1a7823b420111d8e86e3fe9a7cff9fc611ce339d6999fc3053973ef6c8276af841b53547fdebdcb057cbad16aff6178be3fb8747889937dec082c984227c974a19232b85ad85ef457521fcf17d5f697a17b7e62952306f0ed086deb1ebcff0c8a32787789fe7afaa4035c2d0e07c10db46c0df6930a1729d3607fb035154e90c02036318862c5a9537e87a55bc656e3fc53db08f41a07f834e4917ebaaace1214409ffb44c5a806a9cb4def209bfb8ab2e59f1cb6257e422f37dfab288170bdc5666e6a63d1b0447a7b935ad3bdac8d53f64278d433b45925c84dc60214473363d57a30e31324d9b3cc42fb56d375aac2d9d1af16331ad3a92b43a9d64e47813
+15 PASS
+15 a6e19e36 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b1ccd9c752428f0bca9ac9060bb85b8f90acb9374cd8d5a03110635f591a18f131cb7cc204407efec0687a8b77ba6c4e6732c35174e79e36aaa7fa6ab685257710e074065961ce1b16d21fed8a83cd95efcc4be7111cd33b5704fe759dfab21fc3e8aaa86d44609dc0b073354f8160c653f4fbde3ae7c28c87c3667e0797fac24b32e5c1a870cd898b2a9c517709bb0b8e4ee875ff857868eb56548e6dc993f198fd78c8a77cf997ed42a15f99a9b6265c7cf9bedc7580a11514047b881f717b233f3570ec21856bd2b9791e4c43b125e9260ac3fd48b9a10de5f9d5080e53d92d194adb796766684d905cca35e691fab0c76d6b5f49242f81eb92fcc8adc5a64
+15 ANSWER 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b1ccd9c752428f0bca9ac9060bb85b8f90acb9374cd8d5a03110635f591a18f131cb7cc204407efec0687a8b77ba6c4e6732c35174e79e36aaa7fa6ab685257710e074065961ce1b16d21fed8a83cd95efcc4be7111cd33b5704fe759dfab21fc3e8aaa86d44609dc0b073354f8160c653f4fbde3ae7c28c87c3667e0797fac24b32e5c1a870cd898b2a9c517709bb0b8e4ee875ff857868eb56548e6dc993f198fd78c8a77cf997ed42a15f99a9b6265c7cf9bedc7580a11514047b881f717b233f3570ec21856bd2b9791e4c43b125e9260ac3fd48b9a10de5f9d5080e53d92d194adb796766684d905cca35e691fab0c76d6b5f49242f81eb92fcc8ad00000
+15 42438e06bbb424bba5fd95122ec2f206c9b502f1f6d4e4fdbf74ed2c946ad60abaefd6fbd6a08e3ef418709d15bc557ef5e486a51d1e304f6c1e943faad948fde4e6273c0cad0df07068ad028fb01dc0fd7221aeed6ed5dc510dbe4824939036b0f3a45e740b40cef86a32f0b73b20234efc41d573f3e14efc08b3f65e9f7be52d5b930de52d41c7aadc4e0e85dfcf3bb1dd2e9cdf94fc236082879aea27207415cb846a5d5969e619040416a7f0f708f56a5b340a8fd0be1a26bfdc3de365a950532d363b427d6d905af7534af574ae8afd3f47658de5da3fa02dd818a31523122ff53dd31ffd7aa22e53cbf2da7772a1589e9a242f28f9cb1130f54553fcb355b3398fc877b80b3ef2cc3d
+15 PASS
+15 Ok
+
2. Sending Text Messages
+

Once the Secret Chat has been established, you can use the following queries to make Paul and Nick exchange text messages inside the Secret Chat:

+
    +
  • ASK [A|B] — asks A or B to send a random plaintext message to the other party. It is guaranteed that at least one of the first ten generated messages will contain the secret email and password that are the goal of this contest. It is also guaranteed that apart from that, all messages will contain only dictionary English words, spaces, line breaks and punctuation marks. The result to this query is the ciphertext corresponding to the randomly generated plaintext.
  • +
  • TXT [A|B] bytes — asks A or B to encrypt bytes as the (plaintext) contents of a text message and send it to the other party. Note that bytes can be any byte sequence, not necessarily a valid UTF-8 sequence. The result to this query is the ciphertext corresponding to the given plaintext.
  • +
  • MSG [A|B] bytes — send a specified (ciphertext) message (for example, obtained as an answer to an ASK or TXT query) to A or B. You will receive ‘Ok’ if this message was decrypted successfully and accepted by the client, or ‘Fail’ otherwise.
  • +
+

Example:

+
15 ASK A
+15 b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b5
+15 MSG B b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b0
+15 Fail
+15 MSG B b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b5
+15 Ok
+15 TXT B abac
+15 b1d4a61101771d42f62323e6fe680000c877b80b3ef2cc3df751e68b935b083a6f5c15ba8d95b94388fc34453a1e7b9b20222402b7698be5dd8a6ff69a5141b01ca2488b0dada8f2b0e47980218f48912168ddd2cebd3b61b1edf2f557c7ec44768595ce1cb42a01f7c14dd4e6e6e7601cb17ab0b6d5a274
+
+

Objectives

+

We are offering a $300,000 reward to the first person to break Telegram's encryption protocol in this contest.

+

Your goal is to extract a secret email address from one of the random messages that are exchanged between Nick and Paul when you use the ASK command. It is guaranteed that at least one of the first ten generated messages within a session will contain the secret address. It is also guaranteed that apart from that, all messages will contain only dictionary English words, spaces, line breaks and punctuation marks.

+

Once you have the address, you will need to send an email to it. That email must contain:
- The entire text of the message that contained the secret email.
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $300,000 prize.

+

Decrypting messages

+

To prove that the competition was fair, we will add a command that returns the keys used for a particular session by its session_id at the end of the contest. This will be done as soon as a winner is announced, or on February 4, 2015 in case no winner is announced to that date.

+

Bonus objective

+

We are also offering an independent $100,000 reward to the first person to make the bot accept a ciphertext message (i.e. the first person to send a message using MSG [A|B] bytes and receive the result ‘OK’), provided that that ciphertext deciphers to a plaintext that was never encrypted by the bot itself within this session.

+

Should you succeed at this, kindly send an email to security@telegram.org and include the following:
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $100,000 prize.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/import-stickers.html b/data/core.telegram.org/import-stickers.html new file mode 100644 index 0000000000..c784348887 --- /dev/null +++ b/data/core.telegram.org/import-stickers.html @@ -0,0 +1,159 @@ + + + + + Importing Stickers to Telegram + + + + + + + + + + + + + +
+ +
+
+
+
+

Importing Stickers to Telegram

+ +

The easiest way to create stickers on Telegram is to simply upload them using the @stickers bot. This bot can help you upload new stickers, create sticker packs and get usage stats for your stickers and packs.

+

Telegram also offers a platform for developers of apps that help users make their own stickers. For example, apps that allow people to upload pictures of themselves and turn them into stickers.

+

Who is this for?

+

USE this:

+
    +
  • To help people make their own unique custom stickers.
  • +
  • To help people migrate their unique custom stickers they created from another platform.
  • +
+

DON'T use this:

+ +

In short, if a set of stickers is already available on Telegram – there's no need to import it!

+

Sticker Importing Apps

+

As of version 7.8, Telegram apps support a simple API for importing stickers.

+
+ +
+ +
+

WARNING: Each time a user imports stickers, a new sticker pack is created on Telegram. Do not use the importing feature to share stickers you made with other users. If you want to share your stickers, simply upload them using @stickers and share the link of your pack. For example, here's a link to install some Duck Stickers.

+
+

Importing SDKs

+

We have created libraries and sample apps for iOS and Android which you can use to implement importing stickers to Telegram from your app.

+

Sticker Formats

+

Telegram apps support two sticker types. Regardless of the type, each sticker must be associated with at least one emoji that expresses the emotion corresponding to the sticker.

+

Animated Stickers

+

Must be in TGS format, created using the Bodymovin-TG plugin for Adobe After Effects.

+
+

Note: Animated .WEBP is NOT currently supported, only static .WEBP is supported for static stickers. Animated stickers must be in .TGS format. You can also import .WEBM video stickers.

+
+

Max. size: 64 KB
Dimensions: 512x512 px
FPS: 30-60 FPS
Max. duration: 3 seconds

+
+

For full technical details on Telegram animated stickers, see this page.

+
+

Video Stickers

+

Must be in WEBM format with VP9 and alpha channel encoding (transparency is a temporary requirement).

+

Max. size: 256 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.
FPS: 30
Max. duration: 3 seconds

+

Static Stickers

+

Must be in PNG or WEBP format with a transparent layer. All static stickers should use white stroke and shadow, exactly like in this example: StickerExample.psd

+

Max. size: 512 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.acceptAuthorization b/data/core.telegram.org/method/account.acceptAuthorization new file mode 100644 index 0000000000..41d171d863 --- /dev/null +++ b/data/core.telegram.org/method/account.acceptAuthorization @@ -0,0 +1,170 @@ + + + + + account.acceptAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

account.acceptAuthorization

+ +

Sends a Telegram Passport authorization form, effectively sharing data with the service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
bot_idlongBot ID
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
value_hashesVector<SecureValueHash>Types of values sent and their hashes
credentialsSecureCredentialsEncryptedEncrypted values
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.cancelPasswordEmail b/data/core.telegram.org/method/account.cancelPasswordEmail new file mode 100644 index 0000000000..8a425c4876 --- /dev/null +++ b/data/core.telegram.org/method/account.cancelPasswordEmail @@ -0,0 +1,138 @@ + + + + + account.cancelPasswordEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.cancelPasswordEmail

+ +

Cancel the code that was sent to verify an email to use as 2FA recovery method.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.cancelPasswordEmail#c1cbd5b6 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.changePhone b/data/core.telegram.org/method/account.changePhone new file mode 100644 index 0000000000..2535f5a017 --- /dev/null +++ b/data/core.telegram.org/method/account.changePhone @@ -0,0 +1,190 @@ + + + + + account.changePhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.changePhone

+ +

Change the phone number of the current account

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringNew phone number
phone_code_hashstringPhone code hash received when calling account.sendChangePhoneCode
phone_codestringPhone code received when calling account.sendChangePhoneCode
+

Result

+

User

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
+

Related pages

+

account.sendChangePhoneCode

+

Verify a new phone number to associate to the current account

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.checkUsername b/data/core.telegram.org/method/account.checkUsername new file mode 100644 index 0000000000..fd10526b44 --- /dev/null +++ b/data/core.telegram.org/method/account.checkUsername @@ -0,0 +1,167 @@ + + + + + account.checkUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

account.checkUsername

+ +

Validates a username and checks availability.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.checkUsername#2714d86c username:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usernamestringusername
Accepted characters: A-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
+

Result

+

Return Bool result on whether the passed username can be used.

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USERNAME_INVALIDUnacceptable username.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.confirmPasswordEmail b/data/core.telegram.org/method/account.confirmPasswordEmail new file mode 100644 index 0000000000..e4402828e6 --- /dev/null +++ b/data/core.telegram.org/method/account.confirmPasswordEmail @@ -0,0 +1,175 @@ + + + + + account.confirmPasswordEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.confirmPasswordEmail

+ +

Verify an email to use as 2FA recovery method.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.confirmPasswordEmail#8fdf1920 code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
codestringThe phone code that was received after setting a recovery email
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_INVALIDCode invalid.
400EMAIL_HASH_EXPIREDEmail hash expired.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.confirmPhone b/data/core.telegram.org/method/account.confirmPhone new file mode 100644 index 0000000000..a0c2ab7eec --- /dev/null +++ b/data/core.telegram.org/method/account.confirmPhone @@ -0,0 +1,180 @@ + + + + + account.confirmPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.confirmPhone

+ +

Confirm a phone number to cancel account deletion, for more info click here »

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_code_hashstringPhone code hash, for more info click here »
phone_codestringSMS code, for more info click here »
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_HASH_INVALIDCode hash invalid.
400PHONE_CODE_EMPTYphone_code is missing.
+

Related pages

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.createTheme b/data/core.telegram.org/method/account.createTheme new file mode 100644 index 0000000000..80dbc9c1da --- /dev/null +++ b/data/core.telegram.org/method/account.createTheme @@ -0,0 +1,186 @@ + + + + + account.createTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.createTheme

+ +

Create a theme

+

+ +
+
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+---functions---
+account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
slugstringUnique theme ID
titlestringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
+

Result

+

Theme

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_MIME_INVALIDThe theme's MIME type is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.declinePasswordReset b/data/core.telegram.org/method/account.declinePasswordReset new file mode 100644 index 0000000000..da4fd72fc5 --- /dev/null +++ b/data/core.telegram.org/method/account.declinePasswordReset @@ -0,0 +1,155 @@ + + + + + account.declinePasswordReset + + + + + + + + + + + + + +
+ +
+
+
+ +

account.declinePasswordReset

+ +

Abort a pending 2FA password reset, see here for more info »

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.declinePasswordReset#4c9409f6 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400RESET_REQUEST_MISSINGNo password reset is in progress.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.deleteAccount b/data/core.telegram.org/method/account.deleteAccount new file mode 100644 index 0000000000..24f85058e8 --- /dev/null +++ b/data/core.telegram.org/method/account.deleteAccount @@ -0,0 +1,170 @@ + + + + + account.deleteAccount + + + + + + + + + + + + + +
+ +
+
+
+ +

account.deleteAccount

+ +

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.deleteAccount#418d4e0b reason:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
reasonstringWhy is the account being deleted, can be empty
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
4202FA_CONFIRM_WAIT_XSince this account is active and protected by a 2FA password, we will delete it in 1 week for security purposes. You can cancel this process at any time, you'll be able to reset your account in X seconds.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.deleteSecureValue b/data/core.telegram.org/method/account.deleteSecureValue new file mode 100644 index 0000000000..e00c9bf5ba --- /dev/null +++ b/data/core.telegram.org/method/account.deleteSecureValue @@ -0,0 +1,153 @@ + + + + + account.deleteSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

account.deleteSecureValue

+ +

Delete stored Telegram Passport documents, for more info see the passport docs »

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typesVector<SecureValueType>Document types to delete
+

Result

+

Bool

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.finishTakeoutSession b/data/core.telegram.org/method/account.finishTakeoutSession new file mode 100644 index 0000000000..cfed1c0658 --- /dev/null +++ b/data/core.telegram.org/method/account.finishTakeoutSession @@ -0,0 +1,172 @@ + + + + + account.finishTakeoutSession + + + + + + + + + + + + + +
+ +
+
+
+ +

account.finishTakeoutSession

+ +

Finish account takeout session

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.0?trueData exported successfully
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getAccountTTL b/data/core.telegram.org/method/account.getAccountTTL new file mode 100644 index 0000000000..b45b7c26b5 --- /dev/null +++ b/data/core.telegram.org/method/account.getAccountTTL @@ -0,0 +1,134 @@ + + + + + account.getAccountTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAccountTTL

+ +

Get days to live of account

+

+ +
+
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+---functions---
+account.getAccountTTL#8fc711d = AccountDaysTTL;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

AccountDaysTTL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getAllSecureValues b/data/core.telegram.org/method/account.getAllSecureValues new file mode 100644 index 0000000000..62d4965fd1 --- /dev/null +++ b/data/core.telegram.org/method/account.getAllSecureValues @@ -0,0 +1,136 @@ + + + + + account.getAllSecureValues + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAllSecureValues

+ +

Get all saved Telegram Passport documents, for more info see the passport docs »

+

+ +
+
---functions---
+account.getAllSecureValues#b288bc7d = Vector<SecureValue>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<SecureValue>

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getAuthorizationForm b/data/core.telegram.org/method/account.getAuthorizationForm new file mode 100644 index 0000000000..70e50136ea --- /dev/null +++ b/data/core.telegram.org/method/account.getAuthorizationForm @@ -0,0 +1,176 @@ + + + + + account.getAuthorizationForm + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAuthorizationForm

+ +

Returns a Telegram Passport authorization form for sharing data with a service

+

+ +
+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+---functions---
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
bot_idlongUser identifier of the service's bot
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
+

Result

+

account.AuthorizationForm

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PUBLIC_KEY_REQUIREDA public key is required.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getAuthorizations b/data/core.telegram.org/method/account.getAuthorizations new file mode 100644 index 0000000000..68575508d2 --- /dev/null +++ b/data/core.telegram.org/method/account.getAuthorizations @@ -0,0 +1,134 @@ + + + + + account.getAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAuthorizations

+ +

Get logged-in sessions

+

+ +
+
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
+---functions---
+account.getAuthorizations#e320c158 = account.Authorizations;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.Authorizations

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getAutoDownloadSettings b/data/core.telegram.org/method/account.getAutoDownloadSettings new file mode 100644 index 0000000000..c39115640f --- /dev/null +++ b/data/core.telegram.org/method/account.getAutoDownloadSettings @@ -0,0 +1,134 @@ + + + + + account.getAutoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAutoDownloadSettings

+ +

Get media autodownload settings

+

+ +
+
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
+---functions---
+account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.AutoDownloadSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getChatThemes b/data/core.telegram.org/method/account.getChatThemes new file mode 100644 index 0000000000..a5d227a10c --- /dev/null +++ b/data/core.telegram.org/method/account.getChatThemes @@ -0,0 +1,153 @@ + + + + + account.getChatThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getChatThemes

+ +

Get all available chat themes

+

+ +
+
account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
+account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
+---functions---
+account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
+

Result

+

account.ChatThemes

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getContactSignUpNotification b/data/core.telegram.org/method/account.getContactSignUpNotification new file mode 100644 index 0000000000..b97b7bfed7 --- /dev/null +++ b/data/core.telegram.org/method/account.getContactSignUpNotification @@ -0,0 +1,135 @@ + + + + + account.getContactSignUpNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getContactSignUpNotification

+ +

Whether the user will receive notifications when contacts sign up

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.getContactSignUpNotification#9f07c728 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getContentSettings b/data/core.telegram.org/method/account.getContentSettings new file mode 100644 index 0000000000..ada398bd14 --- /dev/null +++ b/data/core.telegram.org/method/account.getContentSettings @@ -0,0 +1,134 @@ + + + + + account.getContentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getContentSettings

+ +

Get sensitive content settings

+

+ +
+
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
+---functions---
+account.getContentSettings#8b9b4dae = account.ContentSettings;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.ContentSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getGlobalPrivacySettings b/data/core.telegram.org/method/account.getGlobalPrivacySettings new file mode 100644 index 0000000000..1079a5c0d9 --- /dev/null +++ b/data/core.telegram.org/method/account.getGlobalPrivacySettings @@ -0,0 +1,134 @@ + + + + + account.getGlobalPrivacySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getGlobalPrivacySettings

+ +

Get global privacy settings

+

+ +
+
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
+---functions---
+account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

GlobalPrivacySettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getMultiWallPapers b/data/core.telegram.org/method/account.getMultiWallPapers new file mode 100644 index 0000000000..4f62e29a73 --- /dev/null +++ b/data/core.telegram.org/method/account.getMultiWallPapers @@ -0,0 +1,148 @@ + + + + + account.getMultiWallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getMultiWallPapers

+ +

Get info about multiple wallpapers

+

+ +
+
---functions---
+account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
wallpapersVector<InputWallPaper>Wallpapers to fetch info about
+

Result

+

Vector<WallPaper>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getNotifyExceptions b/data/core.telegram.org/method/account.getNotifyExceptions new file mode 100644 index 0000000000..adaf232fe5 --- /dev/null +++ b/data/core.telegram.org/method/account.getNotifyExceptions @@ -0,0 +1,165 @@ + + + + + account.getNotifyExceptions + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getNotifyExceptions

+ +

Returns list of chats with non-default notification settings

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
compare_soundflags.1?trueIf true, chats with non-default sound will also be returned
peerflags.0?InputNotifyPeerIf specified, only chats of the specified category will be returned
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getNotifySettings b/data/core.telegram.org/method/account.getNotifySettings new file mode 100644 index 0000000000..a2b9a21f7f --- /dev/null +++ b/data/core.telegram.org/method/account.getNotifySettings @@ -0,0 +1,166 @@ + + + + + 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.getPasswordSettings b/data/core.telegram.org/method/account.getPasswordSettings new file mode 100644 index 0000000000..715b84df6b --- /dev/null +++ b/data/core.telegram.org/method/account.getPasswordSettings @@ -0,0 +1,170 @@ + + + + + account.getPasswordSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getPasswordSettings

+ +

Get private info associated to the password info (recovery email, telegram passport info & so on)

+

+ +
+
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+---functions---
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPThe password (see SRP)
+

Result

+

account.PasswordSettings

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getPrivacy b/data/core.telegram.org/method/account.getPrivacy new file mode 100644 index 0000000000..1f6a41188c --- /dev/null +++ b/data/core.telegram.org/method/account.getPrivacy @@ -0,0 +1,166 @@ + + + + + account.getPrivacy + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getPrivacy

+ +

Get privacy settings of current account

+

+ +
+
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+---functions---
+account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
keyInputPrivacyKeyPeer category whose privacy settings should be fetched
+

Result

+

account.PrivacyRules

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getSecureValue b/data/core.telegram.org/method/account.getSecureValue new file mode 100644 index 0000000000..0ef660d197 --- /dev/null +++ b/data/core.telegram.org/method/account.getSecureValue @@ -0,0 +1,151 @@ + + + + + account.getSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getSecureValue

+ +

Get saved Telegram Passport document, for more info see the passport docs »

+

+ +
+
---functions---
+account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typesVector<SecureValueType>Requested value types
+

Result

+

Vector<SecureValue>

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getTheme b/data/core.telegram.org/method/account.getTheme new file mode 100644 index 0000000000..3dc7e0300c --- /dev/null +++ b/data/core.telegram.org/method/account.getTheme @@ -0,0 +1,181 @@ + + + + + account.getTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getTheme

+ +

Get theme information

+

+ +
+
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+---functions---
+account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme
document_idlongDocument ID
+

Result

+

Theme

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_FORMAT_INVALIDInvalid theme format provided.
400THEME_INVALIDInvalid theme provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getThemes b/data/core.telegram.org/method/account.getThemes new file mode 100644 index 0000000000..eb2a65d98a --- /dev/null +++ b/data/core.telegram.org/method/account.getThemes @@ -0,0 +1,158 @@ + + + + + account.getThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getThemes

+ +

Get installed themes

+

+ +
+
account.themesNotModified#f41eb622 = account.Themes;
+account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
+---functions---
+account.getThemes#7206e458 format:string hash:long = account.Themes;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
formatstringTheme format, a string that identifies the theming engines supported by the client
hashlongHash for pagination, for more info click here
+

Result

+

account.Themes

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getTmpPassword b/data/core.telegram.org/method/account.getTmpPassword new file mode 100644 index 0000000000..cbf1e9907b --- /dev/null +++ b/data/core.telegram.org/method/account.getTmpPassword @@ -0,0 +1,176 @@ + + + + + account.getTmpPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getTmpPassword

+ +

Get temporary payment password

+

+ +
+
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+---functions---
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPSRP password parameters
periodintTime during which the temporary password will be valid, in seconds; should be between 60 and 86400
+

Result

+

account.TmpPassword

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400TMP_PASSWORD_DISABLEDThe temporary password is disabled.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getWallPaper b/data/core.telegram.org/method/account.getWallPaper new file mode 100644 index 0000000000..d604d7a4ae --- /dev/null +++ b/data/core.telegram.org/method/account.getWallPaper @@ -0,0 +1,167 @@ + + + + + account.getWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getWallPaper

+ +

Get info about a certain wallpaper

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
+---functions---
+account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
wallpaperInputWallPaperThe wallpaper to get info about
+

Result

+

WallPaper

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getWallPapers b/data/core.telegram.org/method/account.getWallPapers new file mode 100644 index 0000000000..15839451c4 --- /dev/null +++ b/data/core.telegram.org/method/account.getWallPapers @@ -0,0 +1,153 @@ + + + + + account.getWallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getWallPapers

+ +

Returns a list of available wallpapers.

+

+ +
+
account.wallPapersNotModified#1c199183 = account.WallPapers;
+account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+---functions---
+account.getWallPapers#7967d36 hash:long = account.WallPapers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

Vector<WallPaper>

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getWebAuthorizations b/data/core.telegram.org/method/account.getWebAuthorizations new file mode 100644 index 0000000000..ad5f1dd0b2 --- /dev/null +++ b/data/core.telegram.org/method/account.getWebAuthorizations @@ -0,0 +1,136 @@ + + + + + account.getWebAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getWebAuthorizations

+ +

Get web login widget authorizations

+

+ +
+
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
+---functions---
+account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.WebAuthorizations

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.initTakeoutSession b/data/core.telegram.org/method/account.initTakeoutSession new file mode 100644 index 0000000000..4fe3de2e8e --- /dev/null +++ b/data/core.telegram.org/method/account.initTakeoutSession @@ -0,0 +1,204 @@ + + + + + account.initTakeoutSession + + + + + + + + + + + + + +
+ +
+
+
+ +

account.initTakeoutSession

+ +

Initialize account takeout session

+

+ +
+
account.takeout#4dba4501 id:long = account.Takeout;
+---functions---
+account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to export contacts
message_usersflags.1?trueWhether to export messages in private chats
message_chatsflags.2?trueWhether to export messages in legacy groups
message_megagroupsflags.3?trueWhether to export messages in supergroups
message_channelsflags.4?trueWhether to export messages in channels
filesflags.5?trueWhether to export files
file_max_sizeflags.5?intMaximum size of files to export
+

Result

+

account.Takeout

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
420TAKEOUT_INIT_DELAY_XWait X seconds before initing takeout.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.installTheme b/data/core.telegram.org/method/account.installTheme new file mode 100644 index 0000000000..cf52d5a670 --- /dev/null +++ b/data/core.telegram.org/method/account.installTheme @@ -0,0 +1,165 @@ + + + + + account.installTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.installTheme

+ +

Install a theme

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to install the dark version
formatflags.1?stringTheme format, a string that identifies the theming engines supported by the client
themeflags.1?InputThemeTheme to install
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.installWallPaper b/data/core.telegram.org/method/account.installWallPaper new file mode 100644 index 0000000000..74f3f1f1e0 --- /dev/null +++ b/data/core.telegram.org/method/account.installWallPaper @@ -0,0 +1,172 @@ + + + + + account.installWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.installWallPaper

+ +

Install wallpaper

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
wallpaperInputWallPaperWallpaper to install
settingsWallPaperSettingsWallpaper settings
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.registerDevice b/data/core.telegram.org/method/account.registerDevice new file mode 100644 index 0000000000..6697495956 --- /dev/null +++ b/data/core.telegram.org/method/account.registerDevice @@ -0,0 +1,217 @@ + + + + + account.registerDevice + + + + + + + + + + + + + +
+ +
+
+
+ +

account.registerDevice

+ +

Register device to receive PUSH notifications

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_mutedflags.0?trueAvoid receiving (silent and invisible background) notifications. Useful to save battery.
token_typeintDevice token type.
Possible values:
1 - APNS (device token for apple push)
2 - FCM (firebase token for google firebase)
3 - MPNS (channel URI for microsoft push)
4 - Simple push (endpoint for firefox's simple push API)
5 - Ubuntu phone (token for ubuntu push)
6 - Blackberry (token for blackberry push)
7 - Unused
8 - WNS (windows push)
9 - APNS VoIP (token for apple push VoIP)
10 - Web push (web push, see below)
11 - MPNS VoIP (token for microsoft push VoIP)
12 - Tizen (token for tizen push)

For 10 web push, the token must be a JSON-encoded object containing the keys described in PUSH updates
tokenstringDevice token
app_sandboxBoolIf (boolTrue) is transmitted, a sandbox-certificate will be used during transmission.
secretbytesFor FCM and APNS VoIP, optional encryption key used to encrypt push notifications
other_uidsVector<long>List of user identifiers of other users currently using the client
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
400WEBPUSH_AUTH_INVALIDThe specified web push authentication secret is invalid.
400WEBPUSH_KEY_INVALIDThe specified web push elliptic curve Diffie-Hellman public key is invalid.
400WEBPUSH_TOKEN_INVALIDThe specified web push token is invalid.
+

Related pages

+

Handling PUSH-notifications

+

How to subscribe to and handle PUSH notifications

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.reportPeer b/data/core.telegram.org/method/account.reportPeer new file mode 100644 index 0000000000..054b3723e4 --- /dev/null +++ b/data/core.telegram.org/method/account.reportPeer @@ -0,0 +1,182 @@ + + + + + account.reportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

account.reportPeer

+ +

Report a peer for violation of telegram's Terms of Service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer to report
reasonReportReasonThe reason why this peer is being reported
messagestringComment for report moderation
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.reportProfilePhoto b/data/core.telegram.org/method/account.reportProfilePhoto new file mode 100644 index 0000000000..900673fd06 --- /dev/null +++ b/data/core.telegram.org/method/account.reportProfilePhoto @@ -0,0 +1,165 @@ + + + + + account.reportProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

account.reportProfilePhoto

+ +

Report a profile photo of a dialog

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
photo_idInputPhotoDialog photo ID
reasonReportReasonReport reason
messagestringComment for report moderation
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.resendPasswordEmail b/data/core.telegram.org/method/account.resendPasswordEmail new file mode 100644 index 0000000000..7cf2a8b50e --- /dev/null +++ b/data/core.telegram.org/method/account.resendPasswordEmail @@ -0,0 +1,138 @@ + + + + + account.resendPasswordEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resendPasswordEmail

+ +

Resend the code to verify an email to use as 2FA recovery method.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resendPasswordEmail#7a7f2a15 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.resetAuthorization b/data/core.telegram.org/method/account.resetAuthorization new file mode 100644 index 0000000000..e603b1f203 --- /dev/null +++ b/data/core.telegram.org/method/account.resetAuthorization @@ -0,0 +1,175 @@ + + + + + account.resetAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetAuthorization

+ +

Log out an active authorized session by its hash

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetAuthorization#df77f3bc hash:long = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongSession hash
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
400HASH_INVALIDThe provided hash is invalid.
+

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.resetNotifySettings b/data/core.telegram.org/method/account.resetNotifySettings new file mode 100644 index 0000000000..92adca9942 --- /dev/null +++ b/data/core.telegram.org/method/account.resetNotifySettings @@ -0,0 +1,135 @@ + + + + + account.resetNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetNotifySettings

+ +

Resets all notification settings from users and groups.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetNotifySettings#db7e1747 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.resetPassword b/data/core.telegram.org/method/account.resetPassword new file mode 100644 index 0000000000..61198b6eb9 --- /dev/null +++ b/data/core.telegram.org/method/account.resetPassword @@ -0,0 +1,139 @@ + + + + + account.resetPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPassword

+ +

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+---functions---
+account.resetPassword#9308ce1b = account.ResetPasswordResult;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.ResetPasswordResult

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.resetWallPapers b/data/core.telegram.org/method/account.resetWallPapers new file mode 100644 index 0000000000..84dd2f2685 --- /dev/null +++ b/data/core.telegram.org/method/account.resetWallPapers @@ -0,0 +1,135 @@ + + + + + account.resetWallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetWallPapers

+ +

Delete installed wallpapers

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetWallPapers#bb3b9804 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.resetWebAuthorization b/data/core.telegram.org/method/account.resetWebAuthorization new file mode 100644 index 0000000000..ccdd83281b --- /dev/null +++ b/data/core.telegram.org/method/account.resetWebAuthorization @@ -0,0 +1,171 @@ + + + + + account.resetWebAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetWebAuthorization

+ +

Log out an active web telegram login session

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetWebAuthorization#2d01b9ef hash:long = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongSession hash
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
+

Related pages

+

webAuthorization

+

Represents a bot logged in using the Telegram login widget

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.resetWebAuthorizations b/data/core.telegram.org/method/account.resetWebAuthorizations new file mode 100644 index 0000000000..149c5e8d00 --- /dev/null +++ b/data/core.telegram.org/method/account.resetWebAuthorizations @@ -0,0 +1,137 @@ + + + + + account.resetWebAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetWebAuthorizations

+ +

Reset all active web telegram login sessions

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetWebAuthorizations#682d2594 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.saveAutoDownloadSettings b/data/core.telegram.org/method/account.saveAutoDownloadSettings new file mode 100644 index 0000000000..903b872174 --- /dev/null +++ b/data/core.telegram.org/method/account.saveAutoDownloadSettings @@ -0,0 +1,165 @@ + + + + + account.saveAutoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.saveAutoDownloadSettings

+ +

Change media autodownload settings

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
lowflags.0?trueWhether to save settings in the low data usage preset
highflags.1?trueWhether to save settings in the high data usage preset
settingsAutoDownloadSettingsMedia autodownload settings
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.saveSecureValue b/data/core.telegram.org/method/account.saveSecureValue new file mode 100644 index 0000000000..24aa048e70 --- /dev/null +++ b/data/core.telegram.org/method/account.saveSecureValue @@ -0,0 +1,174 @@ + + + + + account.saveSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

account.saveSecureValue

+ +

Securely save Telegram Passport document, for more info see the passport docs »

+

+ +
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+---functions---
+account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
valueInputSecureValueSecure value, for more info see the passport docs »
secure_secret_idlongPassport secret hash, for more info see the passport docs »
+

Result

+

SecureValue

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_REQUIREDA 2FA password must be configured to use Telegram Passport.
+

Related pages

+

Telegram Passport Encryption Details

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.saveTheme b/data/core.telegram.org/method/account.saveTheme new file mode 100644 index 0000000000..9dcbb739b5 --- /dev/null +++ b/data/core.telegram.org/method/account.saveTheme @@ -0,0 +1,155 @@ + + + + + account.saveTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.saveTheme

+ +

Save a theme

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
themeInputThemeTheme to save
unsaveBoolUnsave
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.saveWallPaper b/data/core.telegram.org/method/account.saveWallPaper new file mode 100644 index 0000000000..dd980842fd --- /dev/null +++ b/data/core.telegram.org/method/account.saveWallPaper @@ -0,0 +1,177 @@ + + + + + account.saveWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.saveWallPaper

+ +

Install/uninstall wallpaper

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
wallpaperInputWallPaperWallpaper to save
unsaveBoolUninstall wallpaper?
settingsWallPaperSettingsWallpaper settings
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.sendChangePhoneCode b/data/core.telegram.org/method/account.sendChangePhoneCode new file mode 100644 index 0000000000..1985b88e2b --- /dev/null +++ b/data/core.telegram.org/method/account.sendChangePhoneCode @@ -0,0 +1,186 @@ + + + + + account.sendChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendChangePhoneCode

+ +

Verify a new phone number to associate to the current account

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringNew phone number
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_CHANGE_PHONE_FORBIDDENYou can't change phone number right after logging in, please wait at least 24 hours.
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.sendConfirmPhoneCode b/data/core.telegram.org/method/account.sendConfirmPhoneCode new file mode 100644 index 0000000000..5f0a68690e --- /dev/null +++ b/data/core.telegram.org/method/account.sendConfirmPhoneCode @@ -0,0 +1,174 @@ + + + + + account.sendConfirmPhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendConfirmPhoneCode

+ +

Send confirmation code to cancel account deletion, for more info click here »

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashstringThe hash from the service notification, for more info click here »
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
+

Related pages

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.sendVerifyEmailCode b/data/core.telegram.org/method/account.sendVerifyEmailCode new file mode 100644 index 0000000000..0d1b49e604 --- /dev/null +++ b/data/core.telegram.org/method/account.sendVerifyEmailCode @@ -0,0 +1,168 @@ + + + + + account.sendVerifyEmailCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendVerifyEmailCode

+ +

Send the verification email code for telegram passport.

+

+ +
+
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
+---functions---
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emailstringThe email where to send the code
+

Result

+

account.SentEmailCode

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400EMAIL_INVALIDThe specified email is invalid.
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.sendVerifyPhoneCode b/data/core.telegram.org/method/account.sendVerifyPhoneCode new file mode 100644 index 0000000000..aba57481a3 --- /dev/null +++ b/data/core.telegram.org/method/account.sendVerifyPhoneCode @@ -0,0 +1,173 @@ + + + + + account.sendVerifyPhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendVerifyPhoneCode

+ +

Send the verification phone code for telegram passport.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringThe phone number to verify
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDThe phone number is invalid.
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.setAccountTTL b/data/core.telegram.org/method/account.setAccountTTL new file mode 100644 index 0000000000..28e965e9bb --- /dev/null +++ b/data/core.telegram.org/method/account.setAccountTTL @@ -0,0 +1,167 @@ + + + + + account.setAccountTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setAccountTTL

+ +

Set account self-destruction period

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
ttlAccountDaysTTLTime to live in days
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TTL_DAYS_INVALIDThe provided TTL is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.setContactSignUpNotification b/data/core.telegram.org/method/account.setContactSignUpNotification new file mode 100644 index 0000000000..25408513ca --- /dev/null +++ b/data/core.telegram.org/method/account.setContactSignUpNotification @@ -0,0 +1,150 @@ + + + + + account.setContactSignUpNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setContactSignUpNotification

+ +

Toggle contact sign up notifications

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
silentBoolWhether to disable contact sign up notifications
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.setContentSettings b/data/core.telegram.org/method/account.setContentSettings new file mode 100644 index 0000000000..f043bdcdaf --- /dev/null +++ b/data/core.telegram.org/method/account.setContentSettings @@ -0,0 +1,172 @@ + + + + + account.setContentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setContentSettings

+ +

Set sensitive content settings (for viewing or hiding NSFW content)

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueEnable NSFW content
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403SENSITIVE_CHANGE_FORBIDDENYou can't change your sensitive content settings.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.setGlobalPrivacySettings b/data/core.telegram.org/method/account.setGlobalPrivacySettings new file mode 100644 index 0000000000..76950fec3c --- /dev/null +++ b/data/core.telegram.org/method/account.setGlobalPrivacySettings @@ -0,0 +1,166 @@ + + + + + account.setGlobalPrivacySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setGlobalPrivacySettings

+ +

Set global privacy settings

+

+ +
+
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
+---functions---
+account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
settingsGlobalPrivacySettingsGlobal privacy settings
+

Result

+

GlobalPrivacySettings

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTOARCHIVE_NOT_AVAILABLEThe autoarchive setting is not available at this time: please check the value of the autoarchive_setting_available field in client config » before calling this method.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.setPrivacy b/data/core.telegram.org/method/account.setPrivacy new file mode 100644 index 0000000000..951971b764 --- /dev/null +++ b/data/core.telegram.org/method/account.setPrivacy @@ -0,0 +1,181 @@ + + + + + account.setPrivacy + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setPrivacy

+ +

Change privacy settings of current account

+

+ +
+
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+---functions---
+account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keyInputPrivacyKeyPeers to which the privacy rules apply
rulesVector<InputPrivacyRule>New privacy rules
+

Result

+

account.PrivacyRules

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
400PRIVACY_TOO_LONGToo many privacy rules were specified, the current limit is 1000.
400PRIVACY_VALUE_INVALIDThe specified privacy rule combination is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.unregisterDevice b/data/core.telegram.org/method/account.unregisterDevice new file mode 100644 index 0000000000..893d7e9322 --- /dev/null +++ b/data/core.telegram.org/method/account.unregisterDevice @@ -0,0 +1,180 @@ + + + + + account.unregisterDevice + + + + + + + + + + + + + +
+ +
+
+
+ +

account.unregisterDevice

+ +

Deletes a device by its token, stops sending PUSH-notifications to it.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
token_typeintDevice token type.
Possible values:
1 - APNS (device token for apple push)
2 - FCM (firebase token for google firebase)
3 - MPNS (channel URI for microsoft push)
4 - Simple push (endpoint for firefox's simple push API)
5 - Ubuntu phone (token for ubuntu push)
6 - Blackberry (token for blackberry push)
7 - Unused
8 - WNS (windows push)
9 - APNS VoIP (token for apple push VoIP)
10 - Web push (web push, see below)
11 - MPNS VoIP (token for microsoft push VoIP)
12 - Tizen (token for tizen push)

For 10 web push, the token must be a JSON-encoded object containing the keys described in PUSH updates
tokenstringDevice token
other_uidsVector<long>List of user identifiers of other users currently using the client
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
+

Related pages

+

Handling PUSH-notifications

+

How to subscribe to and handle PUSH notifications

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateDeviceLocked b/data/core.telegram.org/method/account.updateDeviceLocked new file mode 100644 index 0000000000..1e2cb58dbf --- /dev/null +++ b/data/core.telegram.org/method/account.updateDeviceLocked @@ -0,0 +1,153 @@ + + + + + account.updateDeviceLocked + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateDeviceLocked

+ +

When client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updateDeviceLocked#38df3532 period:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
periodintInactivity period after which to start hiding message texts in PUSH notifications.
+

Result

+

Bool

+

Related pages

+

Handling PUSH-notifications

+

How to subscribe to and handle PUSH notifications

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateNotifySettings b/data/core.telegram.org/method/account.updateNotifySettings new file mode 100644 index 0000000000..39c1fd9be7 --- /dev/null +++ b/data/core.telegram.org/method/account.updateNotifySettings @@ -0,0 +1,192 @@ + + + + + account.updateNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateNotifySettings

+ +

Edits notification settings from a given user/group, from all users/all groups.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputNotifyPeerNotification source
settingsInputPeerNotifySettingsNotification settings
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400SETTINGS_INVALIDInvalid settings were provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updatePasswordSettings b/data/core.telegram.org/method/account.updatePasswordSettings new file mode 100644 index 0000000000..f01f1f0f37 --- /dev/null +++ b/data/core.telegram.org/method/account.updatePasswordSettings @@ -0,0 +1,207 @@ + + + + + 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 new file mode 100644 index 0000000000..21c5879fd4 --- /dev/null +++ b/data/core.telegram.org/method/account.updateProfile @@ -0,0 +1,187 @@ + + + + + account.updateProfile + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateProfile

+ +

Updates user profile.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
first_nameflags.0?stringNew user first name
last_nameflags.1?stringNew user last name
aboutflags.2?stringNew bio
+

Result

+

Returns User object containing the updated current user profile.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ABOUT_TOO_LONGAbout string too long.
400FIRSTNAME_INVALIDThe first name is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateStatus b/data/core.telegram.org/method/account.updateStatus new file mode 100644 index 0000000000..ac302243e0 --- /dev/null +++ b/data/core.telegram.org/method/account.updateStatus @@ -0,0 +1,155 @@ + + + + + account.updateStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateStatus

+ +

Updates online user status.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updateStatus#6628562c offline:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
offlineBoolIf (boolTrue) is transmitted, user status will change to (userStatusOffline).
+

Result

+

Bool

+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

userStatusOffline

+

The user's offline status.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateTheme b/data/core.telegram.org/method/account.updateTheme new file mode 100644 index 0000000000..65a1ec22dc --- /dev/null +++ b/data/core.telegram.org/method/account.updateTheme @@ -0,0 +1,196 @@ + + + + + account.updateTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateTheme

+ +

Update theme

+

+ +
+
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+---functions---
+account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme to update
slugflags.0?stringUnique theme ID
titleflags.1?stringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
+

Result

+

Theme

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_INVALIDInvalid theme provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateUsername b/data/core.telegram.org/method/account.updateUsername new file mode 100644 index 0000000000..b9437b2210 --- /dev/null +++ b/data/core.telegram.org/method/account.updateUsername @@ -0,0 +1,182 @@ + + + + + account.updateUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateUsername

+ +

Changes username for the current user.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.updateUsername#3e0bdd7c username:string = User;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usernamestringusername or empty string if username is to be removed
Accepted characters: a-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
+

Result

+

Returns updated information on the user in a User type object.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400USERNAME_INVALIDUnacceptable username.
400USERNAME_NOT_MODIFIEDUsername is not different from the current username.
400USERNAME_OCCUPIEDUsername is taken.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.uploadTheme b/data/core.telegram.org/method/account.uploadTheme new file mode 100644 index 0000000000..5b19e84a68 --- /dev/null +++ b/data/core.telegram.org/method/account.uploadTheme @@ -0,0 +1,190 @@ + + + + + account.uploadTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.uploadTheme

+ +

Upload theme

+

+ +
+
documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+---functions---
+account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileTheme file uploaded as described in files »
thumbflags.0?InputFileThumbnail
file_namestringFile name
mime_typestringMIME type, must be application/x-tgtheme-{format}, where format depends on the client
+

Result

+

Document

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_FILE_INVALIDInvalid theme file provided.
+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.uploadWallPaper b/data/core.telegram.org/method/account.uploadWallPaper new file mode 100644 index 0000000000..a300f42079 --- /dev/null +++ b/data/core.telegram.org/method/account.uploadWallPaper @@ -0,0 +1,182 @@ + + + + + account.uploadWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.uploadWallPaper

+ +

Create and upload a new wallpaper

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
+---functions---
+account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
fileInputFileThe JPG/PNG wallpaper
mime_typestringMIME type of uploaded wallpaper
settingsWallPaperSettingsWallpaper settings
+

Result

+

WallPaper

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_FILE_INVALIDThe specified wallpaper file is invalid.
400WALLPAPER_MIME_INVALIDThe specified wallpaper MIME type is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.verifyEmail b/data/core.telegram.org/method/account.verifyEmail new file mode 100644 index 0000000000..d261b1fb3c --- /dev/null +++ b/data/core.telegram.org/method/account.verifyEmail @@ -0,0 +1,179 @@ + + + + + account.verifyEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.verifyEmail

+ +

Verify an email address for telegram passport.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.verifyEmail#ecba39db email:string code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emailstringThe email to verify
codestringThe verification code that was received
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMAIL_INVALIDThe specified email is invalid.
400EMAIL_VERIFY_EXPIREDThe verification email has expired.
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.verifyPhone b/data/core.telegram.org/method/account.verifyPhone new file mode 100644 index 0000000000..e2c406a197 --- /dev/null +++ b/data/core.telegram.org/method/account.verifyPhone @@ -0,0 +1,191 @@ + + + + + account.verifyPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.verifyPhone

+ +

Verify a phone number for telegram passport.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash received from the call to account.sendVerifyPhoneCode
phone_codestringCode received after the call to account.sendVerifyPhoneCode
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_NUMBER_INVALIDThe phone number is invalid.
+

Related pages

+

account.sendVerifyPhoneCode

+

Send the verification phone code for telegram passport.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.acceptLoginToken b/data/core.telegram.org/method/auth.acceptLoginToken new file mode 100644 index 0000000000..caa21a9e6b --- /dev/null +++ b/data/core.telegram.org/method/auth.acceptLoginToken @@ -0,0 +1,171 @@ + + + + + auth.acceptLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.acceptLoginToken

+ +

Accept QR code login token, logging in the app that generated it.

+

Returns info about the new session.

+

For more info, see login via QR code.

+

+ +
+
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+---functions---
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
tokenbytesLogin token embedded in QR code, for more info, see login via QR code.
+

Result

+

Authorization

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.bindTempAuthKey b/data/core.telegram.org/method/auth.bindTempAuthKey new file mode 100644 index 0000000000..031bd715ed --- /dev/null +++ b/data/core.telegram.org/method/auth.bindTempAuthKey @@ -0,0 +1,252 @@ + + + + + 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/core.telegram.org/method/auth.cancelCode b/data/core.telegram.org/method/auth.cancelCode new file mode 100644 index 0000000000..3d60859149 --- /dev/null +++ b/data/core.telegram.org/method/auth.cancelCode @@ -0,0 +1,180 @@ + + + + + auth.cancelCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.cancelCode

+ +

Cancel the login verification code

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash from auth.sendCode
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_NUMBER_INVALIDThe phone number is invalid.
+

Related pages

+

auth.sendCode

+

Send the verification code for login

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.checkPassword b/data/core.telegram.org/method/auth.checkPassword new file mode 100644 index 0000000000..f989454809 --- /dev/null +++ b/data/core.telegram.org/method/auth.checkPassword @@ -0,0 +1,180 @@ + + + + + auth.checkPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.checkPassword

+ +

Try logging to an account protected by a 2FA password.

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPThe account's password (see SRP)
+

Result

+

auth.Authorization

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password isn't valid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.checkPhone b/data/core.telegram.org/method/auth.checkPhone new file mode 100644 index 0000000000..331e76c0da --- /dev/null +++ b/data/core.telegram.org/method/auth.checkPhone @@ -0,0 +1,176 @@ + + + + + auth.checkPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.checkPhone

+ +

Returns information on whether the passed phone number was registered.

+

+ +
+
 Method schema is available as of layer 78. Switch »

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in the international format
+

Result

+

The method returns an auth.CheckedPhone type object with information on whether an account with such a phone number has already been registered, as well as whether invitations were sent to this number (using the auth.sendInvites method).

+

Query example

+
(auth.checkPhone "79123413132")
+=
+(auth.checkedPhone
+  phone_registered:(boolFalse)
+  phone_invited:(boolFalse)
+)
+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram
400PHONE_NUMBER_INVALIDInvalid phone number
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.checkRecoveryPassword b/data/core.telegram.org/method/auth.checkRecoveryPassword new file mode 100644 index 0000000000..b63f6bf3f7 --- /dev/null +++ b/data/core.telegram.org/method/auth.checkRecoveryPassword @@ -0,0 +1,174 @@ + + + + + auth.checkRecoveryPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.checkRecoveryPassword

+ +

Check if the 2FA recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.checkRecoveryPassword#d36bf79 code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
codestringCode received via email
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_RECOVERY_EXPIREDThe recovery code has expired.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

auth.requestPasswordRecovery

+

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

+

auth.recoverPassword

+

Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.dropTempAuthKeys b/data/core.telegram.org/method/auth.dropTempAuthKeys new file mode 100644 index 0000000000..00f577e8ed --- /dev/null +++ b/data/core.telegram.org/method/auth.dropTempAuthKeys @@ -0,0 +1,151 @@ + + + + + auth.dropTempAuthKeys + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.dropTempAuthKeys

+ +

Delete all temporary authorization keys except for the ones specified

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
except_auth_keysVector<long>The auth keys that shouldn't be dropped.
+

Result

+

Bool

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.exportAuthorization b/data/core.telegram.org/method/auth.exportAuthorization new file mode 100644 index 0000000000..b0c1f3826c --- /dev/null +++ b/data/core.telegram.org/method/auth.exportAuthorization @@ -0,0 +1,167 @@ + + + + + auth.exportAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.exportAuthorization

+ +

Returns data for copying authorization to another data-centre.

+

+ +
+
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
+---functions---
+auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintNumber of a target data-centre
+

Result

+

auth.ExportedAuthorization

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400DC_ID_INVALIDThe provided DC ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.exportLoginToken b/data/core.telegram.org/method/auth.exportLoginToken new file mode 100644 index 0000000000..54a1acf57f --- /dev/null +++ b/data/core.telegram.org/method/auth.exportLoginToken @@ -0,0 +1,183 @@ + + + + + auth.exportLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.exportLoginToken

+ +

Generate a login token, for login via QR code.
+The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.

+

For more info, see login via QR code.

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+---functions---
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
except_idsVector<long>List of already logged-in user IDs, to prevent logging in twice with the same user
+

Result

+

auth.LoginToken

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400API_ID_INVALIDAPI ID invalid.
+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.importAuthorization b/data/core.telegram.org/method/auth.importAuthorization new file mode 100644 index 0000000000..23da4b4419 --- /dev/null +++ b/data/core.telegram.org/method/auth.importAuthorization @@ -0,0 +1,178 @@ + + + + + auth.importAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.importAuthorization

+ +

Logs in a user using a key transmitted from his native data-centre.

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongUser ID
bytesbytesAuthorization key
+

Result

+

auth.Authorization

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.importBotAuthorization b/data/core.telegram.org/method/auth.importBotAuthorization new file mode 100644 index 0000000000..7e42ede178 --- /dev/null +++ b/data/core.telegram.org/method/auth.importBotAuthorization @@ -0,0 +1,205 @@ + + + + + auth.importBotAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.importBotAuthorization

+ +

Login as a bot

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flagsintReserved for future use
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
bot_auth_tokenstringBot token (see bots)
+

Result

+

Returns an auth.Authorization object with information on the new authorization.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ACCESS_TOKEN_EXPIREDBot token expired.
400ACCESS_TOKEN_INVALIDThe provided token is not valid.
400API_ID_INVALIDThe api_id/api_hash combination is invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
401AUTH_KEY_INVALIDAuth key invalid.
+

Bots can use this method

+

Related pages

+

Bots: An introduction for developers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.importLoginToken b/data/core.telegram.org/method/auth.importLoginToken new file mode 100644 index 0000000000..cc69f72695 --- /dev/null +++ b/data/core.telegram.org/method/auth.importLoginToken @@ -0,0 +1,187 @@ + + + + + auth.importLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.importLoginToken

+ +

Login using a redirected login token, generated in case of DC mismatch during QR code login.

+

For more info, see login via QR code.

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+---functions---
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
tokenbytesLogin token
+

Result

+

auth.LoginToken

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_TOKEN_ALREADY_ACCEPTEDThe specified auth token was already accepted.
400AUTH_TOKEN_EXPIREDThe authorization token has expired.
400AUTH_TOKEN_INVALIDThe specified auth token is invalid.
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.logOut b/data/core.telegram.org/method/auth.logOut new file mode 100644 index 0000000000..a76fb07834 --- /dev/null +++ b/data/core.telegram.org/method/auth.logOut @@ -0,0 +1,140 @@ + + + + + auth.logOut + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.logOut

+ +

Logs out the user.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.logOut#5717da40 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Query example

+
(auth.logOut )
+=
+(boolTrue)
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.recoverPassword b/data/core.telegram.org/method/auth.recoverPassword new file mode 100644 index 0000000000..d8d1fdfa78 --- /dev/null +++ b/data/core.telegram.org/method/auth.recoverPassword @@ -0,0 +1,187 @@ + + + + + auth.recoverPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.recoverPassword

+ +

Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
codestringCode received via email
new_settingsflags.0?account.PasswordInputSettingsNew password
+

Result

+

auth.Authorization

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_EMPTYThe provided code is empty.
400NEW_SETTINGS_INVALIDThe new settings are invalid.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

auth.requestPasswordRecovery

+

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.requestPasswordRecovery b/data/core.telegram.org/method/auth.requestPasswordRecovery new file mode 100644 index 0000000000..d7d23e9d16 --- /dev/null +++ b/data/core.telegram.org/method/auth.requestPasswordRecovery @@ -0,0 +1,159 @@ + + + + + auth.requestPasswordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.requestPasswordRecovery

+ +

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+---functions---
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

auth.PasswordRecovery

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_EMPTYThe provided password is empty.
400PASSWORD_RECOVERY_NANo email was set, can't recover password via email.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.resendCode b/data/core.telegram.org/method/auth.resendCode new file mode 100644 index 0000000000..852b07fb87 --- /dev/null +++ b/data/core.telegram.org/method/auth.resendCode @@ -0,0 +1,191 @@ + + + + + auth.resendCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.resendCode

+ +

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringThe phone number
phone_code_hashstringThe phone code hash obtained from auth.sendCode
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_CODE_HASH_EMPTYphone_code_hash is missing.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
406SEND_CODE_UNAVAILABLEReturned when all available options for this type of number were already used (e.g. flash-call, then SMS, then this error might be returned to trigger a second resend).
+

Related pages

+

auth.sendCode

+

Send the verification code for login

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.resetAuthorizations b/data/core.telegram.org/method/auth.resetAuthorizations new file mode 100644 index 0000000000..d09fa29b02 --- /dev/null +++ b/data/core.telegram.org/method/auth.resetAuthorizations @@ -0,0 +1,156 @@ + + + + + auth.resetAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.resetAuthorizations

+ +

Terminates all user's authorized sessions except for the current one.

+

After calling this method it is necessary to reregister the current device using the method account.registerDevice

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.resetAuthorizations#9fab0d1a = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
+

Related pages

+

account.registerDevice

+

Register device to receive PUSH notifications

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.sendCall b/data/core.telegram.org/method/auth.sendCall new file mode 100644 index 0000000000..894cdd52e2 --- /dev/null +++ b/data/core.telegram.org/method/auth.sendCall @@ -0,0 +1,175 @@ + + + + + auth.sendCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendCall

+ +

Makes a voice call to the passed phone number. A robot will repeat the confirmation code from a previously sent SMS message.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
+

Result

+

Bool

+

Query example

+
(auth.sendCall "79991234567" "2dc02d2cda9e615c84")
+=
+(boolTrue)
+
+03c51564 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 64e1a61b
+=
+997275b5
+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.sendCode b/data/core.telegram.org/method/auth.sendCode new file mode 100644 index 0000000000..6a54617ae7 --- /dev/null +++ b/data/core.telegram.org/method/auth.sendCode @@ -0,0 +1,236 @@ + + + + + auth.sendCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendCode

+ +

Send the verification code for login

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in international format
api_idintApplication identifier (see App configuration)
api_hashstringApplication secret hash (see App configuration)
settingsCodeSettingsSettings for the code type to send
+

Result

+

The method returns an auth.SentCode object with information on the message sent.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400API_ID_INVALIDAPI ID invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
303NETWORK_MIGRATE_XRepeat the query to data-center X.
303PHONE_MIGRATE_XRepeat the query to data-center X.
400PHONE_NUMBER_APP_SIGNUP_FORBIDDENYou can't sign up using this app.
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram.
400PHONE_NUMBER_FLOODYou asked for the code too many times.
400PHONE_NUMBER_INVALIDInvalid phone number.
406PHONE_PASSWORD_FLOODYou have tried logging in too many times.
400PHONE_PASSWORD_PROTECTEDThis phone is password protected.
400SMS_CODE_CREATE_FAILEDAn error occurred while creating the SMS code.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.sendInvites b/data/core.telegram.org/method/auth.sendInvites new file mode 100644 index 0000000000..36ea47ee07 --- /dev/null +++ b/data/core.telegram.org/method/auth.sendInvites @@ -0,0 +1,157 @@ + + + + + auth.sendInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendInvites

+ +

Saves information that the current user sent SMS-messages with invitations to its unregistered contacts.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numbersVector<string>List of phone numbers of message recipients in the international format
messagestringMessage text
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.sendSms b/data/core.telegram.org/method/auth.sendSms new file mode 100644 index 0000000000..ac37879793 --- /dev/null +++ b/data/core.telegram.org/method/auth.sendSms @@ -0,0 +1,167 @@ + + + + + auth.sendSms + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendSms

+ +

Forces sending an SMS message to the specified phone number. Use this method if auth.sentAppCode was returned as a response to auth.sendCode, but the user can't reach the device with Telegram.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in international format
phone_code_hashstringSMS-message ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.signIn b/data/core.telegram.org/method/auth.signIn new file mode 100644 index 0000000000..1177c62e46 --- /dev/null +++ b/data/core.telegram.org/method/auth.signIn @@ -0,0 +1,219 @@ + + + + + auth.signIn + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.signIn

+ +

Signs in a user with a validated phone number.

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID, obtained from auth.sendCode
phone_codestringValid numerical code from the SMS-message
+

Result

+

Returns an auth.Authorization object with information on the new authorization.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code from the SMS is empty.
400PHONE_CODE_EXPIREDSMS expired.
400PHONE_CODE_INVALIDInvalid SMS code was sent.
400PHONE_NUMBER_INVALIDInvalid phone number.
400PHONE_NUMBER_UNOCCUPIEDThe code is valid but no user with the given number is registered.
+

Query example

+
(auth.signIn "79991234567" "2dc02d2cda9e615c84" "44444")
+=
+(auth.authorization
+  expires:1403938438
+  user:(userSelf
+    id:603177
+    first_name:"John"
+    last_name:"Doe"
+    phone:"79991234567"
+    photo:(userProfilePhotoEmpty)
+    status:(userStatusEmpty)
+    inactive:(boolTrue)
+  )
+)
+
+bcd51581 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 34343405 00003434 45ca2b3b
+=
+f6b673a4 53ae6686 720535ec 00093429 686f4a04 0000006e 656f4403 3939370b 33323139 37363534 4f11bae1 09d05049 997275b5 d8487410
+

Related pages

+

auth.sendCode

+

Send the verification code for login

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.signUp b/data/core.telegram.org/method/auth.signUp new file mode 100644 index 0000000000..3eadfe342f --- /dev/null +++ b/data/core.telegram.org/method/auth.signUp @@ -0,0 +1,236 @@ + + + + + auth.signUp + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.signUp

+ +

Registers a validated phone number in the system.

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
first_namestringNew user first name
last_namestringNew user last name
+

Result

+

Returns an auth.Authorization object with information about the new authorization.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FIRSTNAME_INVALIDInvalid first name.
400LASTNAME_INVALIDInvalid last name.
400PHONE_CODE_EMPTYphone_code from a SMS is empty.
400PHONE_CODE_EXPIREDSMS expired.
400PHONE_CODE_INVALIDInvalid SMS code was sent.
400PHONE_NUMBER_FLOODYou asked for the code too many times.
400PHONE_NUMBER_INVALIDInvalid phone number.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
+

Query example

+
(auth.signUp "79991234567" "2dc02d2cda9e615c84" "44444" "John" "Doe")
+=
+(auth.authorization
+  expires:1403938438
+  user:(userSelf
+    id:603177
+    first_name:"John"
+    last_name:"Doe"
+    phone:"79991234567"
+    photo:(userProfilePhotoEmpty)
+    status:(userStatusEmpty)
+    inactive:(boolTrue)
+  )
+)
+
+1b067634 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 34343405 00003434 686f4a04 0000006e 656f4403 c18027ca
+=
+f6b673a4 53ae6686 720535ec 00093429 686f4a04 0000006e 656f4403 3939370b 33323139 37363534 4f11bae1 09d05049 997275b5 d8487410
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/bots.answerWebhookJSONQuery b/data/core.telegram.org/method/bots.answerWebhookJSONQuery new file mode 100644 index 0000000000..5873dc7be8 --- /dev/null +++ b/data/core.telegram.org/method/bots.answerWebhookJSONQuery @@ -0,0 +1,178 @@ + + + + + bots.answerWebhookJSONQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.answerWebhookJSONQuery

+ +

Answers a custom query; for bots only

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
query_idlongIdentifier of a custom query
dataDataJSONJSON-serialized answer to the query
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400QUERY_ID_INVALIDThe query ID is invalid.
400USER_BOT_INVALIDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/bots.getBotCommands b/data/core.telegram.org/method/bots.getBotCommands new file mode 100644 index 0000000000..0a19b0ad91 --- /dev/null +++ b/data/core.telegram.org/method/bots.getBotCommands @@ -0,0 +1,154 @@ + + + + + bots.getBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.getBotCommands

+ +

Obtain a list of bot commands for the specified bot scope and language code

+

+ +
+
---functions---
+bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
+

Result

+

Vector<BotCommand>

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/bots.resetBotCommands b/data/core.telegram.org/method/bots.resetBotCommands new file mode 100644 index 0000000000..19bc8f9ecf --- /dev/null +++ b/data/core.telegram.org/method/bots.resetBotCommands @@ -0,0 +1,156 @@ + + + + + bots.resetBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.resetBotCommands

+ +

Clear bot commands for the specified bot scope and language code

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
+

Result

+

Bool

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/bots.sendCustomRequest b/data/core.telegram.org/method/bots.sendCustomRequest new file mode 100644 index 0000000000..656689fed9 --- /dev/null +++ b/data/core.telegram.org/method/bots.sendCustomRequest @@ -0,0 +1,177 @@ + + + + + bots.sendCustomRequest + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.sendCustomRequest

+ +

Sends a custom request; for bots only

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;
+---functions---
+bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
custom_methodstringThe method name
paramsDataJSONJSON-serialized method parameters
+

Result

+

DataJSON

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400USER_BOT_INVALIDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/bots.setBotCommands b/data/core.telegram.org/method/bots.setBotCommands new file mode 100644 index 0000000000..d346a75b97 --- /dev/null +++ b/data/core.telegram.org/method/bots.setBotCommands @@ -0,0 +1,188 @@ + + + + + bots.setBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.setBotCommands

+ +

Set bot command list

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
commandsVector<BotCommand>Bot commands
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_COMMAND_DESCRIPTION_INVALIDThe specified command description is invalid.
400BOT_COMMAND_INVALIDThe specified command is invalid.
400LANG_CODE_INVALIDThe specified language code is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.checkUsername b/data/core.telegram.org/method/channels.checkUsername new file mode 100644 index 0000000000..2a39082600 --- /dev/null +++ b/data/core.telegram.org/method/channels.checkUsername @@ -0,0 +1,190 @@ + + + + + channels.checkUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.checkUsername

+ +

Check if a username is free and can be assigned to a channel/supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe channel/supergroup that will assigned the specified username
usernamestringThe username to check
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400USERNAME_INVALIDThe provided username is not valid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.convertToGigagroup b/data/core.telegram.org/method/channels.convertToGigagroup new file mode 100644 index 0000000000..36f33f87a3 --- /dev/null +++ b/data/core.telegram.org/method/channels.convertToGigagroup @@ -0,0 +1,177 @@ + + + + + channels.convertToGigagroup + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.convertToGigagroup

+ +

Convert a supergroup to a gigagroup, when requested by channel suggestions.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup to convert
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PARTICIPANTS_TOO_FEWNot enough participants.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.createChannel b/data/core.telegram.org/method/channels.createChannel new file mode 100644 index 0000000000..99c8798677 --- /dev/null +++ b/data/core.telegram.org/method/channels.createChannel @@ -0,0 +1,232 @@ + + + + + channels.createChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.createChannel

+ +

Create a supergroup/channel.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.0?trueWhether to create a channel
megagroupflags.1?trueWhether to create a supergroup
for_importflags.3?trueWhether the supergroup is being created to import messages from a foreign chat service using messages.initHistoryImport
titlestringChannel title
aboutstringChannel description
geo_pointflags.2?InputGeoPointGeogroup location
addressflags.2?stringGeogroup address
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHThe user has reached the limit of public geogroups.
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_TITLE_EMPTYNo chat title provided.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

messages.initHistoryImport

+

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.deleteChannel b/data/core.telegram.org/method/channels.deleteChannel new file mode 100644 index 0000000000..ede33d8017 --- /dev/null +++ b/data/core.telegram.org/method/channels.deleteChannel @@ -0,0 +1,200 @@ + + + + + channels.deleteChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteChannel

+ +

Delete a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup to delete
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHANNEL_TOO_LARGEChannel is too large to be deleted; this error is issued when trying to delete channels with more than 1000 members (subject to change).
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.deleteHistory b/data/core.telegram.org/method/channels.deleteHistory new file mode 100644 index 0000000000..370317535f --- /dev/null +++ b/data/core.telegram.org/method/channels.deleteHistory @@ -0,0 +1,180 @@ + + + + + channels.deleteHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteHistory

+ +

Delete the history of a supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup whose history must be deleted
max_idintID of message up to which the history must be deleted
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.deleteMessages b/data/core.telegram.org/method/channels.deleteMessages new file mode 100644 index 0000000000..5777636044 --- /dev/null +++ b/data/core.telegram.org/method/channels.deleteMessages @@ -0,0 +1,190 @@ + + + + + channels.deleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteMessages

+ +

Delete messages in a channel/supergroup

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<int>IDs of messages to delete
+

Result

+

messages.AffectedMessages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403MESSAGE_DELETE_FORBIDDENYou can't delete one of the messages you tried to delete, most likely because it is a service message.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.deleteUserHistory b/data/core.telegram.org/method/channels.deleteUserHistory new file mode 100644 index 0000000000..fdb085b96d --- /dev/null +++ b/data/core.telegram.org/method/channels.deleteUserHistory @@ -0,0 +1,199 @@ + + + + + channels.deleteUserHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteUserHistory

+ +

Delete all messages sent by a certain user in a supergroup

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+---functions---
+channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup
user_idInputUserUser whose messages should be deleted
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.editAdmin b/data/core.telegram.org/method/channels.editAdmin new file mode 100644 index 0000000000..590ba0aff6 --- /dev/null +++ b/data/core.telegram.org/method/channels.editAdmin @@ -0,0 +1,301 @@ + + + + + channels.editAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editAdmin

+ +

Modify the admin rights of a user in a supergroup/channel.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup/channel.
user_idInputUserThe ID of the user whose admin rights should be modified
admin_rightsChatAdminRightsThe admin rights
rankstringIndicates the role (rank) of the admin in the group: just an arbitrary string
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ADMINS_TOO_MUCHThere are too many admins.
400ADMIN_RANK_EMOJI_NOT_ALLOWEDAn admin rank cannot contain emojis.
400ADMIN_RANK_INVALIDThe specified admin rank is invalid.
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_CHANNELS_NABots can't edit admin privileges.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHAT_ADMIN_INVITE_REQUIREDYou do not have the rights to do this.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
406FRESH_CHANGE_ADMINS_FORBIDDENYou were just elected admin, you can't add or modify other admins yet.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
403RIGHT_FORBIDDENYour admin rights do not allow you to do this.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BLOCKEDUser blocked.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.editBanned b/data/core.telegram.org/method/channels.editBanned new file mode 100644 index 0000000000..251020cb2e --- /dev/null +++ b/data/core.telegram.org/method/channels.editBanned @@ -0,0 +1,241 @@ + + + + + channels.editBanned + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editBanned

+ +

Ban/unban/kick a user in a supergroup/channel.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup/channel.
participantInputPeerParticipant to ban
banned_rightsChatBannedRightsThe banned rights
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_ADD_INVALIDInternal error.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400USER_ADMIN_INVALIDYou're not an admin.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.editCreator b/data/core.telegram.org/method/channels.editCreator new file mode 100644 index 0000000000..9db0cc561e --- /dev/null +++ b/data/core.telegram.org/method/channels.editCreator @@ -0,0 +1,225 @@ + + + + + channels.editCreator + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editCreator

+ +

Transfer channel ownership

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
user_idInputUserNew channel owner
passwordInputCheckPasswordSRP2FA password of account
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400PASSWORD_MISSINGYou must enable 2FA in order to transfer ownership of a channel.
400PASSWORD_TOO_FRESH_XThe password was modified less than 24 hours ago, try again in X seconds.
400SESSION_TOO_FRESH_XThis session was created less than 24 hours ago, try again in X seconds.
400SRP_ID_INVALIDInvalid SRP ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.editLocation b/data/core.telegram.org/method/channels.editLocation new file mode 100644 index 0000000000..d0eda63cf8 --- /dev/null +++ b/data/core.telegram.org/method/channels.editLocation @@ -0,0 +1,180 @@ + + + + + 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 new file mode 100644 index 0000000000..1db5822bae --- /dev/null +++ b/data/core.telegram.org/method/channels.editPhoto @@ -0,0 +1,221 @@ + + + + + channels.editPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editPhoto

+ +

Change the photo of a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup whose photo should be edited
photoInputChatPhotoNew photo
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FILE_REFERENCE_INVALIDThe specified file reference is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALIDPhoto invalid.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.editTitle b/data/core.telegram.org/method/channels.editTitle new file mode 100644 index 0000000000..271627a770 --- /dev/null +++ b/data/core.telegram.org/method/channels.editTitle @@ -0,0 +1,206 @@ + + + + + channels.editTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editTitle

+ +

Edit the name of a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editTitle#566decd0 channel:InputChannel title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
titlestringNew name
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.exportMessageLink b/data/core.telegram.org/method/channels.exportMessageLink new file mode 100644 index 0000000000..3907f2c777 --- /dev/null +++ b/data/core.telegram.org/method/channels.exportMessageLink @@ -0,0 +1,204 @@ + + + + + channels.exportMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.exportMessageLink

+ +

Get link and embed info of a message in a channel/supergroup

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+---functions---
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
groupedflags.0?trueWhether to include other grouped media (for albums)
threadflags.1?trueWhether to also include a thread ID, if available, inside of the link
channelInputChannelChannel
idintMessage ID
+

Result

+

ExportedMessageLink

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getAdminLog b/data/core.telegram.org/method/channels.getAdminLog new file mode 100644 index 0000000000..59c02d2c89 --- /dev/null +++ b/data/core.telegram.org/method/channels.getAdminLog @@ -0,0 +1,226 @@ + + + + + channels.getAdminLog + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getAdminLog

+ +

Get the admin log of a channel/supergroup

+

+ +
+
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+---functions---
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channelInputChannelChannel
qstringSearch query, can be empty
events_filterflags.0?ChannelAdminLogEventsFilterEvent filter
adminsflags.1?Vector<InputUser>Only show events from these admins
max_idlongMaximum ID of message to return (see pagination)
min_idlongMinimum ID of message to return (see pagination)
limitintMaximum number of results to return, see pagination
+

Result

+

channels.AdminLogResults

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getAdminedPublicChannels b/data/core.telegram.org/method/channels.getAdminedPublicChannels new file mode 100644 index 0000000000..c94d428392 --- /dev/null +++ b/data/core.telegram.org/method/channels.getAdminedPublicChannels @@ -0,0 +1,191 @@ + + + + + channels.getAdminedPublicChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getAdminedPublicChannels

+ +

Get channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
by_locationflags.0?trueGet geogroups
check_limitflags.1?trueIf set and the user has reached the limit of owned public channels/supergroups/geogroups, instead of returning the channel list one of the specified errors will be returned.
Useful to check if a new public channel can indeed be created, even before asking the user to enter a channel username to use in channels.checkUsername/channels.updateUsername.
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHReturned if both the check_limit and the by_location flags are set and the user has reached the limit of public geogroups.
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHReturned if the check_limit flag is set and the user has reached the limit of public channels/supergroups.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

channels.checkUsername

+

Check if a username is free and can be assigned to a channel/supergroup

+

channels.updateUsername

+

Change the username of a supergroup/channel

+

config

+

Current configuration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getChannels b/data/core.telegram.org/method/channels.getChannels new file mode 100644 index 0000000000..0cb0b547ad --- /dev/null +++ b/data/core.telegram.org/method/channels.getChannels @@ -0,0 +1,181 @@ + + + + + channels.getChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getChannels

+ +

Get info about channels/supergroups

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputChannel>IDs of channels/supergroups to get info about
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getFullChannel b/data/core.telegram.org/method/channels.getFullChannel new file mode 100644 index 0000000000..58234bcb20 --- /dev/null +++ b/data/core.telegram.org/method/channels.getFullChannel @@ -0,0 +1,187 @@ + + + + + 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/core.telegram.org/method/channels.getGroupsForDiscussion b/data/core.telegram.org/method/channels.getGroupsForDiscussion new file mode 100644 index 0000000000..6b6534045b --- /dev/null +++ b/data/core.telegram.org/method/channels.getGroupsForDiscussion @@ -0,0 +1,144 @@ + + + + + channels.getGroupsForDiscussion + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getGroupsForDiscussion

+ +

Get all groups that can be used as discussion groups.

+

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
+To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

messages.Chats

+

Related pages

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

channels.togglePreHistoryHidden

+

Hide/unhide message history for new channel/supergroup users

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getInactiveChannels b/data/core.telegram.org/method/channels.getInactiveChannels new file mode 100644 index 0000000000..d600060a77 --- /dev/null +++ b/data/core.telegram.org/method/channels.getInactiveChannels @@ -0,0 +1,134 @@ + + + + + channels.getInactiveChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getInactiveChannels

+ +

Get inactive channels and supergroups

+

+ +
+
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
+---functions---
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

messages.InactiveChats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getLeftChannels b/data/core.telegram.org/method/channels.getLeftChannels new file mode 100644 index 0000000000..42d9b61911 --- /dev/null +++ b/data/core.telegram.org/method/channels.getLeftChannels @@ -0,0 +1,172 @@ + + + + + channels.getLeftChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getLeftChannels

+ +

Get a list of channels/supergroups we left

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset for pagination
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getMessages b/data/core.telegram.org/method/channels.getMessages new file mode 100644 index 0000000000..74c1e497d2 --- /dev/null +++ b/data/core.telegram.org/method/channels.getMessages @@ -0,0 +1,193 @@ + + + + + channels.getMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getMessages

+ +

Get channel/supergroup messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<InputMessage>IDs of messages to get
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getParticipant b/data/core.telegram.org/method/channels.getParticipant new file mode 100644 index 0000000000..979a90ca5a --- /dev/null +++ b/data/core.telegram.org/method/channels.getParticipant @@ -0,0 +1,205 @@ + + + + + channels.getParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getParticipant

+ +

Get info about a channel/supergroup participant

+

+ +
+
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+---functions---
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
participantInputPeerParticipant to get info about
+

Result

+

channels.ChannelParticipant

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getParticipants b/data/core.telegram.org/method/channels.getParticipants new file mode 100644 index 0000000000..b766c94a55 --- /dev/null +++ b/data/core.telegram.org/method/channels.getParticipants @@ -0,0 +1,203 @@ + + + + + channels.getParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getParticipants

+ +

Get the participants of a supergroup/channel

+

+ +
+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
+---functions---
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
filterChannelParticipantsFilterWhich participant types to fetch
offsetintOffset
limitintLimit
hashlongHash
+

Result

+

channels.ChannelParticipants

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
+

Bots can use this method

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getSponsoredMessages b/data/core.telegram.org/method/channels.getSponsoredMessages new file mode 100644 index 0000000000..ddb1b37570 --- /dev/null +++ b/data/core.telegram.org/method/channels.getSponsoredMessages @@ -0,0 +1,154 @@ + + + + + channels.getSponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getSponsoredMessages

+ +

Get a list of sponsored messages

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+---functions---
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelPeer
+

Result

+

messages.SponsoredMessages

+
+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.inviteToChannel b/data/core.telegram.org/method/channels.inviteToChannel new file mode 100644 index 0000000000..fa94c15e1c --- /dev/null +++ b/data/core.telegram.org/method/channels.inviteToChannel @@ -0,0 +1,262 @@ + + + + + channels.inviteToChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.inviteToChannel

+ +

Invite users to a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
usersVector<InputUser>Users to invite
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_INVALIDInvalid chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_BLOCKEDUser blocked.
400USER_BOTBots can only be admins in channels.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_KICKEDThis user was kicked from this supergroup/channel.
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.joinChannel b/data/core.telegram.org/method/channels.joinChannel new file mode 100644 index 0000000000..57b6eba6b8 --- /dev/null +++ b/data/core.telegram.org/method/channels.joinChannel @@ -0,0 +1,227 @@ + + + + + channels.joinChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.joinChannel

+ +

Join a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.joinChannel#24b524c5 channel:InputChannel = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup to join
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_INVALIDInvalid chat.
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.leaveChannel b/data/core.telegram.org/method/channels.leaveChannel new file mode 100644 index 0000000000..ab0ac43e4f --- /dev/null +++ b/data/core.telegram.org/method/channels.leaveChannel @@ -0,0 +1,201 @@ + + + + + channels.leaveChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.leaveChannel

+ +

Leave a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.leaveChannel#f836aa95 channel:InputChannel = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup to leave
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.readHistory b/data/core.telegram.org/method/channels.readHistory new file mode 100644 index 0000000000..14f36f5ae6 --- /dev/null +++ b/data/core.telegram.org/method/channels.readHistory @@ -0,0 +1,185 @@ + + + + + channels.readHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.readHistory

+ +

Mark channel/supergroup history as read

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
max_idintID of message up to which messages should be marked as read
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.readMessageContents b/data/core.telegram.org/method/channels.readMessageContents new file mode 100644 index 0000000000..64281416ce --- /dev/null +++ b/data/core.telegram.org/method/channels.readMessageContents @@ -0,0 +1,185 @@ + + + + + channels.readMessageContents + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.readMessageContents

+ +

Mark channel/supergroup message contents as read

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<int>IDs of messages whose contents should be marked as read
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.setDiscussionGroup b/data/core.telegram.org/method/channels.setDiscussionGroup new file mode 100644 index 0000000000..edb1b119dd --- /dev/null +++ b/data/core.telegram.org/method/channels.setDiscussionGroup @@ -0,0 +1,200 @@ + + + + + channels.setDiscussionGroup + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.setDiscussionGroup

+ +

Associate a group to a channel as discussion group for that channel

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
broadcastInputChannelChannel
groupInputChannelDiscussion group to associate to the channel
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_ID_INVALIDBroadcast ID invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400LINK_NOT_MODIFIEDDiscussion link not modified.
400MEGAGROUP_ID_INVALIDInvalid supergroup ID.
400MEGAGROUP_PREHISTORY_HIDDENGroup with hidden history for new members can't be set as discussion groups.
+

Related pages

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.setStickers b/data/core.telegram.org/method/channels.setStickers new file mode 100644 index 0000000000..23ed15033d --- /dev/null +++ b/data/core.telegram.org/method/channels.setStickers @@ -0,0 +1,183 @@ + + + + + channels.setStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.setStickers

+ +

Associate a stickerset to the supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup
stickersetInputStickerSetThe stickerset to associate
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400PARTICIPANTS_TOO_FEWNot enough participants.
406STICKERSET_OWNER_ANONYMOUSProvided stickerset can't be installed as group stickerset to prevent admin deanonymisation.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.togglePreHistoryHidden b/data/core.telegram.org/method/channels.togglePreHistoryHidden new file mode 100644 index 0000000000..44a1f39a01 --- /dev/null +++ b/data/core.telegram.org/method/channels.togglePreHistoryHidden @@ -0,0 +1,202 @@ + + + + + channels.togglePreHistoryHidden + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.togglePreHistoryHidden

+ +

Hide/unhide message history for new channel/supergroup users

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
enabledBoolHide/unhide
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_LINK_EXISTSThe chat is public, you can't hide the history to new users.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.toggleSignatures b/data/core.telegram.org/method/channels.toggleSignatures new file mode 100644 index 0000000000..0c453ffa44 --- /dev/null +++ b/data/core.telegram.org/method/channels.toggleSignatures @@ -0,0 +1,187 @@ + + + + + channels.toggleSignatures + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.toggleSignatures

+ +

Enable/disable message signatures in channels

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
enabledBoolValue
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.toggleSlowMode b/data/core.telegram.org/method/channels.toggleSlowMode new file mode 100644 index 0000000000..d95ec4e4a2 --- /dev/null +++ b/data/core.telegram.org/method/channels.toggleSlowMode @@ -0,0 +1,190 @@ + + + + + channels.toggleSlowMode + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.toggleSlowMode

+ +

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup
secondsintUsers will only be able to send one message every seconds seconds, 0 to disable the limitation
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400SECONDS_INVALIDInvalid duration provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.updateUsername b/data/core.telegram.org/method/channels.updateUsername new file mode 100644 index 0000000000..8a65dcc129 --- /dev/null +++ b/data/core.telegram.org/method/channels.updateUsername @@ -0,0 +1,212 @@ + + + + + channels.updateUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.updateUsername

+ +

Change the username of a supergroup/channel

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
usernamestringNew username
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400USERNAME_INVALIDThe provided username is not valid.
400USERNAME_NOT_MODIFIEDThe username was not modified.
400USERNAME_OCCUPIEDThe provided username is already occupied.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.acceptContact b/data/core.telegram.org/method/contacts.acceptContact new file mode 100644 index 0000000000..77bb6fcbd9 --- /dev/null +++ b/data/core.telegram.org/method/contacts.acceptContact @@ -0,0 +1,190 @@ + + + + + contacts.acceptContact + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.acceptContact

+ +

If the peer settings of a new user allow us to add him as contact, add that user as contact

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.acceptContact#f831a20f id:InputUser = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputUserThe user to add as contact
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONTACT_ADD_MISSINGContact to add is missing.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400CONTACT_REQ_MISSINGMissing contact request.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

peerSettings

+

Peer settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.addContact b/data/core.telegram.org/method/contacts.addContact new file mode 100644 index 0000000000..1cf71a56b4 --- /dev/null +++ b/data/core.telegram.org/method/contacts.addContact @@ -0,0 +1,217 @@ + + + + + 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.block b/data/core.telegram.org/method/contacts.block new file mode 100644 index 0000000000..e64d02ebaa --- /dev/null +++ b/data/core.telegram.org/method/contacts.block @@ -0,0 +1,182 @@ + + + + + contacts.block + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.block

+ +

Adds the user to the blacklist.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.block#68cc1411 id:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPeerUser ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.blockFromReplies b/data/core.telegram.org/method/contacts.blockFromReplies new file mode 100644 index 0000000000..bdc3625380 --- /dev/null +++ b/data/core.telegram.org/method/contacts.blockFromReplies @@ -0,0 +1,178 @@ + + + + + contacts.blockFromReplies + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.blockFromReplies

+ +

Stop getting notifications about thread replies of a certain user in @replies

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
delete_messageflags.0?trueWhether to delete the specified message as well
delete_historyflags.1?trueWhether to delete all @replies messages from this user as well
report_spamflags.2?trueWhether to also report this user for spam
msg_idintID of the message in the @replies chat
+

Result

+

Updates

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.deleteByPhones b/data/core.telegram.org/method/contacts.deleteByPhones new file mode 100644 index 0000000000..fdd9a3949f --- /dev/null +++ b/data/core.telegram.org/method/contacts.deleteByPhones @@ -0,0 +1,150 @@ + + + + + contacts.deleteByPhones + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.deleteByPhones

+ +

Delete contacts by phone number

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phonesVector<string>Phone numbers
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.deleteContacts b/data/core.telegram.org/method/contacts.deleteContacts new file mode 100644 index 0000000000..34a358f690 --- /dev/null +++ b/data/core.telegram.org/method/contacts.deleteContacts @@ -0,0 +1,155 @@ + + + + + contacts.deleteContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.deleteContacts

+ +

Deletes several contacts from the list.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputUser>User ID list
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getBlocked b/data/core.telegram.org/method/contacts.getBlocked new file mode 100644 index 0000000000..c7b1e35554 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getBlocked @@ -0,0 +1,155 @@ + + + + + contacts.getBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getBlocked

+ +

Returns the list of blocked users.

+

+ +
+
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+---functions---
+contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintThe number of list elements to be skipped
limitintThe number of list elements to be returned
+

Result

+

contacts.Blocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getContactIDs b/data/core.telegram.org/method/contacts.getContactIDs new file mode 100644 index 0000000000..0b2d62f294 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getContactIDs @@ -0,0 +1,151 @@ + + + + + contacts.getContactIDs + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getContactIDs

+ +

Get contact by telegram IDs

+

+ +
+
---functions---
+contacts.getContactIDs#7adc669d hash:long = Vector<int>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

Vector<int>

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getContacts b/data/core.telegram.org/method/contacts.getContacts new file mode 100644 index 0000000000..72e31ea6d7 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getContacts @@ -0,0 +1,155 @@ + + + + + contacts.getContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getContacts

+ +

Returns the current user's contact list.

+

+ +
+
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
+contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
+---functions---
+contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongIf there already is a full contact list on the client, a hash of a the list of contact IDs in ascending order may be passed in this parameter. If the contact set was not changed, (contacts.contactsNotModified) will be returned.
+

Result

+

contacts.Contacts

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

contacts.contactsNotModified

+

Contact list on the server is the same as the list on the client.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getLocated b/data/core.telegram.org/method/contacts.getLocated new file mode 100644 index 0000000000..a8252e9443 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getLocated @@ -0,0 +1,197 @@ + + + + + contacts.getLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getLocated

+ +

Get contacts near you

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
backgroundflags.1?trueWhile the geolocation of the current user is public, clients should update it in the background every half-an-hour or so, while setting this flag.
Do this only if the new location is more than 1 KM away from the previous one, or if the previous location is unknown.
geo_pointInputGeoPointGeolocation
self_expiresflags.0?intIf set, the geolocation of the current user will be public for the specified number of seconds; pass 0x7fffffff to disable expiry, 0 to make the current geolocation private; if the flag isn't set, no changes will be applied.
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400GEO_POINT_INVALIDInvalid geoposition provided.
406USERPIC_PRIVACY_REQUIREDYou need to disable privacy settings for your profile picture in order to make your geolocation public.
406USERPIC_UPLOAD_REQUIREDYou must have a profile picture to publish your geolocation.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getSaved b/data/core.telegram.org/method/contacts.getSaved new file mode 100644 index 0000000000..e74fada5e9 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getSaved @@ -0,0 +1,150 @@ + + + + + contacts.getSaved + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getSaved

+ +

Get all contacts

+

+ +
+
---functions---
+contacts.getSaved#82f1e39f = Vector<SavedContact>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<SavedContact>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getStatuses b/data/core.telegram.org/method/contacts.getStatuses new file mode 100644 index 0000000000..5ad7897b45 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getStatuses @@ -0,0 +1,133 @@ + + + + + contacts.getStatuses + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getStatuses

+ +

Returns the list of contact statuses.

+

+ +
+
---functions---
+contacts.getStatuses#c4a353ee = Vector<ContactStatus>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<ContactStatus>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getTopPeers b/data/core.telegram.org/method/contacts.getTopPeers new file mode 100644 index 0000000000..e19f2658ab --- /dev/null +++ b/data/core.telegram.org/method/contacts.getTopPeers @@ -0,0 +1,226 @@ + + + + + contacts.getTopPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getTopPeers

+ +

Get most used peers

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+---functions---
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
correspondentsflags.0?trueUsers we've chatted most frequently with
bots_pmflags.1?trueMost used bots
bots_inlineflags.2?trueMost used inline bots
phone_callsflags.3?trueMost frequently called users
forward_usersflags.4?trueUsers to which the users often forwards messages to
forward_chatsflags.5?trueChats to which the users often forwards messages to
groupsflags.10?trueOften-opened groups and supergroups
channelsflags.15?trueMost frequently visited channels
offsetintOffset for pagination
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

contacts.TopPeers

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TYPES_EMPTYNo top peer type was provided.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.importContacts b/data/core.telegram.org/method/contacts.importContacts new file mode 100644 index 0000000000..279b11ca35 --- /dev/null +++ b/data/core.telegram.org/method/contacts.importContacts @@ -0,0 +1,154 @@ + + + + + contacts.importContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.importContacts

+ +

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

+

Use contacts.addContact to add Telegram contacts without actually using their phone number.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+---functions---
+contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
contactsVector<InputContact>List of contacts to import
+

Result

+

contacts.ImportedContacts

+

Related pages

+

contacts.addContact

+

Add an existing telegram user as contact.

+

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.resetSaved b/data/core.telegram.org/method/contacts.resetSaved new file mode 100644 index 0000000000..4fd122e042 --- /dev/null +++ b/data/core.telegram.org/method/contacts.resetSaved @@ -0,0 +1,135 @@ + + + + + contacts.resetSaved + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.resetSaved

+ +

Delete saved contacts

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.resetSaved#879537f1 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.resetTopPeerRating b/data/core.telegram.org/method/contacts.resetTopPeerRating new file mode 100644 index 0000000000..dfb2f27f3c --- /dev/null +++ b/data/core.telegram.org/method/contacts.resetTopPeerRating @@ -0,0 +1,175 @@ + + + + + contacts.resetTopPeerRating + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.resetTopPeerRating

+ +

Reset rating of top peer

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
categoryTopPeerCategoryTop peer category
peerInputPeerPeer whose rating should be reset
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.resolveUsername b/data/core.telegram.org/method/contacts.resolveUsername new file mode 100644 index 0000000000..305d565063 --- /dev/null +++ b/data/core.telegram.org/method/contacts.resolveUsername @@ -0,0 +1,182 @@ + + + + + contacts.resolveUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.resolveUsername

+ +

Resolve a @username to get peer info

+

+ +
+
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
+---functions---
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usernamestring@username to resolve
+

Result

+

contacts.ResolvedPeer

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CONNECTION_LAYER_INVALIDLayer invalid.
400USERNAME_INVALIDThe provided username is not valid.
400USERNAME_NOT_OCCUPIEDThe provided username is not occupied.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.search b/data/core.telegram.org/method/contacts.search new file mode 100644 index 0000000000..6c662e25ac --- /dev/null +++ b/data/core.telegram.org/method/contacts.search @@ -0,0 +1,178 @@ + + + + + contacts.search + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.search

+ +

Returns users found by username substring.

+

+ +
+
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
+---functions---
+contacts.search#11f812d8 q:string limit:int = contacts.Found;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
qstringTarget substring
limitintMaximum number of users to be returned
+

Result

+

contacts.Found

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400QUERY_TOO_SHORTThe query string is too short.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Notes

+

This method will exclude the current user's contacts from the search results. It is assumed that searches among the user's contacts can be handled locally by the client.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.toggleTopPeers b/data/core.telegram.org/method/contacts.toggleTopPeers new file mode 100644 index 0000000000..069a25190b --- /dev/null +++ b/data/core.telegram.org/method/contacts.toggleTopPeers @@ -0,0 +1,153 @@ + + + + + contacts.toggleTopPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.toggleTopPeers

+ +

Enable/disable top peers

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
enabledBoolEnable/disable
+

Result

+

Bool

+

Related pages

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.unblock b/data/core.telegram.org/method/contacts.unblock new file mode 100644 index 0000000000..deb5563e5c --- /dev/null +++ b/data/core.telegram.org/method/contacts.unblock @@ -0,0 +1,182 @@ + + + + + contacts.unblock + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.unblock

+ +

Deletes the user from the blacklist.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.unblock#bea65d50 id:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPeerUser ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/folders.deleteFolder b/data/core.telegram.org/method/folders.deleteFolder new file mode 100644 index 0000000000..2e32fc7ff7 --- /dev/null +++ b/data/core.telegram.org/method/folders.deleteFolder @@ -0,0 +1,175 @@ + + + + + folders.deleteFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

folders.deleteFolder

+ +

Delete a peer folder

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+folders.deleteFolder#1c295881 folder_id:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_EMPTYAn empty folder ID was specified.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/folders.editPeerFolders b/data/core.telegram.org/method/folders.editPeerFolders new file mode 100644 index 0000000000..db9e006d61 --- /dev/null +++ b/data/core.telegram.org/method/folders.editPeerFolders @@ -0,0 +1,175 @@ + + + + + folders.editPeerFolders + + + + + + + + + + + + + +
+ +
+
+
+ +

folders.editPeerFolders

+ +

Edit peers in peer folder

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_peersVector<InputFolderPeer>New peer list
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.acceptTermsOfService b/data/core.telegram.org/method/help.acceptTermsOfService new file mode 100644 index 0000000000..d68ffeee0f --- /dev/null +++ b/data/core.telegram.org/method/help.acceptTermsOfService @@ -0,0 +1,150 @@ + + + + + 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 new file mode 100644 index 0000000000..156c2561d8 --- /dev/null +++ b/data/core.telegram.org/method/help.dismissSuggestion @@ -0,0 +1,160 @@ + + + + + help.dismissSuggestion + + + + + + + + + + + + + +
+ +
+
+
+ +

help.dismissSuggestion

+ +

Dismiss a suggestion, see here for more info ».

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerIn the case of pending suggestions in channels, the channel ID.
suggestionstringSuggestion, see here for more info ».
+

Result

+

Bool

+

Related pages

+

channelFull

+

Full info about a channel/supergroup

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.editUserInfo b/data/core.telegram.org/method/help.editUserInfo new file mode 100644 index 0000000000..32428aed38 --- /dev/null +++ b/data/core.telegram.org/method/help.editUserInfo @@ -0,0 +1,180 @@ + + + + + help.editUserInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.editUserInfo

+ +

Internal use

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+---functions---
+help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser
messagestringMessage
entitiesVector<MessageEntity>Message entities for styled text
+

Result

+

help.UserInfo

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USER_INVALIDInvalid user provided.
+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getAppChangelog b/data/core.telegram.org/method/help.getAppChangelog new file mode 100644 index 0000000000..609fb03651 --- /dev/null +++ b/data/core.telegram.org/method/help.getAppChangelog @@ -0,0 +1,162 @@ + + + + + help.getAppChangelog + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getAppChangelog

+ +

Get changelog of current app.
+Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+help.getAppChangelog#9010ef6f prev_app_version:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
prev_app_versionstringPrevious app version
+

Result

+

Updates

+

Related pages

+

Updates

+

Full constructor of updates

+

updateServiceNotification

+

A service message for the user.

+

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getAppConfig b/data/core.telegram.org/method/help.getAppConfig new file mode 100644 index 0000000000..ad032c6809 --- /dev/null +++ b/data/core.telegram.org/method/help.getAppConfig @@ -0,0 +1,142 @@ + + + + + help.getAppConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getAppConfig

+ +

Get app-specific configuration, see client configuration for more info on the result.

+

+ +
+
jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+---functions---
+help.getAppConfig#98914110 = JSONValue;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

JSONValue, see client configuration for more info on the result

+

Related pages

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getAppUpdate b/data/core.telegram.org/method/help.getAppUpdate new file mode 100644 index 0000000000..27088b0ef5 --- /dev/null +++ b/data/core.telegram.org/method/help.getAppUpdate @@ -0,0 +1,150 @@ + + + + + help.getAppUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getAppUpdate

+ +

Returns information on update availability for the current application.

+

+ +
+
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
+help.noAppUpdate#c45a6536 = help.AppUpdate;
+---functions---
+help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
sourcestringSource
+

Result

+

help.AppUpdate

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getCdnConfig b/data/core.telegram.org/method/help.getCdnConfig new file mode 100644 index 0000000000..b3b1d7abf6 --- /dev/null +++ b/data/core.telegram.org/method/help.getCdnConfig @@ -0,0 +1,154 @@ + + + + + help.getCdnConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getCdnConfig

+ +

Get configuration for CDN file downloads.

+

+ +
+
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
+---functions---
+help.getCdnConfig#52029342 = CdnConfig;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

CdnConfig

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
+

Bots can use this method

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getConfig b/data/core.telegram.org/method/help.getConfig new file mode 100644 index 0000000000..33d4326faa --- /dev/null +++ b/data/core.telegram.org/method/help.getConfig @@ -0,0 +1,192 @@ + + + + + help.getConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getConfig

+ +

Returns current configuration, including data center configuration.

+

+ +
+
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+---functions---
+help.getConfig#c4f9186b = Config;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Config

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400CONNECTION_APP_VERSION_EMPTYApp version is empty.
400CONNECTION_LAYER_INVALIDLayer invalid.
400CONNECTION_NOT_INITEDConnection not initialized.
400DATA_INVALIDEncrypted data invalid.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USERNAME_INVALIDThe provided username is not valid.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getCountriesList b/data/core.telegram.org/method/help.getCountriesList new file mode 100644 index 0000000000..88f7b8386c --- /dev/null +++ b/data/core.telegram.org/method/help.getCountriesList @@ -0,0 +1,158 @@ + + + + + help.getCountriesList + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getCountriesList

+ +

Get name, ISO code, localized name and phone codes/patterns of all available countries

+

+ +
+
help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+---functions---
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code of the current user
hashintHash for pagination, for more info click here
+

Result

+

help.CountriesList

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getDeepLinkInfo b/data/core.telegram.org/method/help.getDeepLinkInfo new file mode 100644 index 0000000000..8396b041bb --- /dev/null +++ b/data/core.telegram.org/method/help.getDeepLinkInfo @@ -0,0 +1,150 @@ + + + + + help.getDeepLinkInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getDeepLinkInfo

+ +

Get info about a t.me link

+

+ +
+
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
+help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
+---functions---
+help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
pathstringPath in t.me/path
+

Result

+

help.DeepLinkInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getInviteText b/data/core.telegram.org/method/help.getInviteText new file mode 100644 index 0000000000..014bbc704d --- /dev/null +++ b/data/core.telegram.org/method/help.getInviteText @@ -0,0 +1,134 @@ + + + + + help.getInviteText + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getInviteText

+ +

Returns localized text of a text message with an invitation.

+

+ +
+
help.inviteText#18cb9f78 message:string = help.InviteText;
+---functions---
+help.getInviteText#4d392343 = help.InviteText;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.InviteText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getNearestDc b/data/core.telegram.org/method/help.getNearestDc new file mode 100644 index 0000000000..367abfb21d --- /dev/null +++ b/data/core.telegram.org/method/help.getNearestDc @@ -0,0 +1,134 @@ + + + + + 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.getPassportConfig b/data/core.telegram.org/method/help.getPassportConfig new file mode 100644 index 0000000000..46b7e21f94 --- /dev/null +++ b/data/core.telegram.org/method/help.getPassportConfig @@ -0,0 +1,154 @@ + + + + + help.getPassportConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getPassportConfig

+ +

Get passport configuration

+

+ +
+
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
+help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
+---functions---
+help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
+

Result

+

help.PassportConfig

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getPromoData b/data/core.telegram.org/method/help.getPromoData new file mode 100644 index 0000000000..f34cdff29a --- /dev/null +++ b/data/core.telegram.org/method/help.getPromoData @@ -0,0 +1,135 @@ + + + + + help.getPromoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getPromoData

+ +

Get MTProxy/Public Service Announcement information

+

+ +
+
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
+help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
+---functions---
+help.getPromoData#c0977421 = help.PromoData;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.PromoData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getProxyData b/data/core.telegram.org/method/help.getProxyData new file mode 100644 index 0000000000..d46672dd13 --- /dev/null +++ b/data/core.telegram.org/method/help.getProxyData @@ -0,0 +1,132 @@ + + + + + help.getProxyData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getProxyData

+ +

Get promotion info of the currently-used MTProxy

+

+ +
+
 Method schema is available as of layer 113. Switch »

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.ProxyData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getRecentMeUrls b/data/core.telegram.org/method/help.getRecentMeUrls new file mode 100644 index 0000000000..f60cdd6eee --- /dev/null +++ b/data/core.telegram.org/method/help.getRecentMeUrls @@ -0,0 +1,149 @@ + + + + + help.getRecentMeUrls + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getRecentMeUrls

+ +

Get recently used t.me links

+

+ +
+
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
+---functions---
+help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
refererstringReferer
+

Result

+

help.RecentMeUrls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getSupport b/data/core.telegram.org/method/help.getSupport new file mode 100644 index 0000000000..e6ec831633 --- /dev/null +++ b/data/core.telegram.org/method/help.getSupport @@ -0,0 +1,134 @@ + + + + + help.getSupport + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getSupport

+ +

Returns the support user for the 'ask a question' feature.

+

+ +
+
help.support#17c6b5f6 phone_number:string user:User = help.Support;
+---functions---
+help.getSupport#9cdf08cd = help.Support;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.Support

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getSupportName b/data/core.telegram.org/method/help.getSupportName new file mode 100644 index 0000000000..ab4d39e208 --- /dev/null +++ b/data/core.telegram.org/method/help.getSupportName @@ -0,0 +1,151 @@ + + + + + help.getSupportName + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getSupportName

+ +

Get localized name of the telegram support user

+

+ +
+
help.supportName#8c05f1c9 name:string = help.SupportName;
+---functions---
+help.getSupportName#d360e72c = help.SupportName;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.SupportName

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403USER_INVALIDInvalid user provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getTermsOfServiceUpdate b/data/core.telegram.org/method/help.getTermsOfServiceUpdate new file mode 100644 index 0000000000..957dbf33c3 --- /dev/null +++ b/data/core.telegram.org/method/help.getTermsOfServiceUpdate @@ -0,0 +1,135 @@ + + + + + help.getTermsOfServiceUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getTermsOfServiceUpdate

+ +

Look for updates of telegram's terms of service

+

+ +
+
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+---functions---
+help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.TermsOfServiceUpdate

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getUserInfo b/data/core.telegram.org/method/help.getUserInfo new file mode 100644 index 0000000000..d8eaf8f75f --- /dev/null +++ b/data/core.telegram.org/method/help.getUserInfo @@ -0,0 +1,167 @@ + + + + + help.getUserInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getUserInfo

+ +

Internal use

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+---functions---
+help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
+

Result

+

help.UserInfo

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403USER_INVALIDInvalid user provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.hidePromoData b/data/core.telegram.org/method/help.hidePromoData new file mode 100644 index 0000000000..c9a15dcf42 --- /dev/null +++ b/data/core.telegram.org/method/help.hidePromoData @@ -0,0 +1,150 @@ + + + + + help.hidePromoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.hidePromoData

+ +

Hide MTProxy/Public Service Announcement information

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer to hide
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.saveAppLog b/data/core.telegram.org/method/help.saveAppLog new file mode 100644 index 0000000000..1623540eed --- /dev/null +++ b/data/core.telegram.org/method/help.saveAppLog @@ -0,0 +1,150 @@ + + + + + help.saveAppLog + + + + + + + + + + + + + +
+ +
+
+
+ +

help.saveAppLog

+ +

Saves logs of application on the server.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
eventsVector<InputAppEvent>List of input events
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.setBotUpdatesStatus b/data/core.telegram.org/method/help.setBotUpdatesStatus new file mode 100644 index 0000000000..067814c280 --- /dev/null +++ b/data/core.telegram.org/method/help.setBotUpdatesStatus @@ -0,0 +1,156 @@ + + + + + help.setBotUpdatesStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

help.setBotUpdatesStatus

+ +

Informs the server about the number of pending bot updates if they haven't been processed for a long time; for bots only

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
pending_updates_countintNumber of pending updates
messagestringError message, if present
+

Result

+

Bool

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/initConnection.html b/data/core.telegram.org/method/initConnection.html new file mode 100644 index 0000000000..93c0d3cc51 --- /dev/null +++ b/data/core.telegram.org/method/initConnection.html @@ -0,0 +1,216 @@ + + + + + initConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

initConnection

+ +

Initialize connection

+

+ +
+
---functions---
+initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
api_idintApplication identifier (see. App configuration)
device_modelstringDevice model
system_versionstringOperation system version
app_versionstringApplication version
system_lang_codestringCode for the language used on the device's OS, ISO 639-1 standard
lang_packstringLanguage pack to use
lang_codestringCode for the language used on the client, ISO 639-1 standard
proxyflags.0?InputClientProxyInfo about an MTProto proxy
paramsflags.1?JSONValueAdditional initConnection parameters.
For now, only the tz_offset field is supported, for specifying timezone offset in seconds.
query!XThe query itself
+

Result

+

X

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CONNECTION_LAYER_INVALIDLayer invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/invokeAfterMsg.html b/data/core.telegram.org/method/invokeAfterMsg.html new file mode 100644 index 0000000000..028d4b4940 --- /dev/null +++ b/data/core.telegram.org/method/invokeAfterMsg.html @@ -0,0 +1,154 @@ + + + + + invokeAfterMsg + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeAfterMsg

+ +

Invokes a query after successfull completion of one of the previous queries.

+

+ +
+
---functions---
+invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idlongMessage identifier on which a current query depends
query!XThe query itself
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/invokeAfterMsgs.html b/data/core.telegram.org/method/invokeAfterMsgs.html new file mode 100644 index 0000000000..a0e9cda487 --- /dev/null +++ b/data/core.telegram.org/method/invokeAfterMsgs.html @@ -0,0 +1,154 @@ + + + + + invokeAfterMsgs + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeAfterMsgs

+ +

Invokes a query after a successfull completion of previous queries

+

+ +
+
---functions---
+invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idsVector<long>List of messages on which a current query depends
query!XThe query itself
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/invokeWithLayer.html b/data/core.telegram.org/method/invokeWithLayer.html new file mode 100644 index 0000000000..a5e3c1da29 --- /dev/null +++ b/data/core.telegram.org/method/invokeWithLayer.html @@ -0,0 +1,204 @@ + + + + + invokeWithLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithLayer

+ +

Invoke the specified query using the specified API layer

+

+ +
+
---functions---
+invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
layerintThe layer to use
query!XThe query
+

Result

+

X

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400CONNECTION_NOT_INITEDConnection not initialized.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400INVITE_HASH_EXPIREDThe invite link has expired.
+

Bots can use this method

+

Related pages

+

Calling API Methods

+

Additional options for calling methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/invokeWithMessagesRange.html b/data/core.telegram.org/method/invokeWithMessagesRange.html new file mode 100644 index 0000000000..85494a609f --- /dev/null +++ b/data/core.telegram.org/method/invokeWithMessagesRange.html @@ -0,0 +1,154 @@ + + + + + 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/invokeWithTakeout.html b/data/core.telegram.org/method/invokeWithTakeout.html new file mode 100644 index 0000000000..d35a60cfc2 --- /dev/null +++ b/data/core.telegram.org/method/invokeWithTakeout.html @@ -0,0 +1,154 @@ + + + + + invokeWithTakeout + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithTakeout

+ +

Invoke a method within a takeout session

+

+ +
+
---functions---
+invokeWithTakeout#aca9fd2e {X:Type} takeout_id:long query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
takeout_idlongTakeout session ID
query!XQuery
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/invokeWithoutUpdates.html b/data/core.telegram.org/method/invokeWithoutUpdates.html new file mode 100644 index 0000000000..b6682f675f --- /dev/null +++ b/data/core.telegram.org/method/invokeWithoutUpdates.html @@ -0,0 +1,154 @@ + + + + + invokeWithoutUpdates + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithoutUpdates

+ +

Invoke a request without subscribing the used connection for updates (this is enabled by default for file queries).

+

+ +
+
---functions---
+invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
query!XThe query
+

Result

+

X

+

Bots can use this method

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/langpack.getDifference b/data/core.telegram.org/method/langpack.getDifference new file mode 100644 index 0000000000..342c0e136f --- /dev/null +++ b/data/core.telegram.org/method/langpack.getDifference @@ -0,0 +1,176 @@ + + + + + langpack.getDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getDifference

+ +

Get new strings in languagepack

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+---functions---
+langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack
lang_codestringLanguage code
from_versionintPrevious localization pack version
+

Result

+

LangPackDifference

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/langpack.getLangPack b/data/core.telegram.org/method/langpack.getLangPack new file mode 100644 index 0000000000..2ca79ec8fd --- /dev/null +++ b/data/core.telegram.org/method/langpack.getLangPack @@ -0,0 +1,171 @@ + + + + + langpack.getLangPack + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLangPack

+ +

Get localization pack strings

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+---functions---
+langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
+

Result

+

LangPackDifference

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/langpack.getLanguage b/data/core.telegram.org/method/langpack.getLanguage new file mode 100644 index 0000000000..6baac5a624 --- /dev/null +++ b/data/core.telegram.org/method/langpack.getLanguage @@ -0,0 +1,154 @@ + + + + + langpack.getLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLanguage

+ +

Get information about a language in a localization pack

+

+ +
+
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
+---functions---
+langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
+

Result

+

LangPackLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/langpack.getLanguages b/data/core.telegram.org/method/langpack.getLanguages new file mode 100644 index 0000000000..063a19ea19 --- /dev/null +++ b/data/core.telegram.org/method/langpack.getLanguages @@ -0,0 +1,165 @@ + + + + + langpack.getLanguages + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLanguages

+ +

Get information about all languages in a localization pack

+

+ +
+
---functions---
+langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack
+

Result

+

Vector<LangPackLanguage>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/langpack.getStrings b/data/core.telegram.org/method/langpack.getStrings new file mode 100644 index 0000000000..21553c29e9 --- /dev/null +++ b/data/core.telegram.org/method/langpack.getStrings @@ -0,0 +1,175 @@ + + + + + langpack.getStrings + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getStrings

+ +

Get strings from a language pack

+

+ +
+
---functions---
+langpack.getStrings#efea3803 lang_pack:string lang_code:string keys:Vector<string> = Vector<LangPackString>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
keysVector<string>Strings to get
+

Result

+

Vector<LangPackString>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.acceptEncryption b/data/core.telegram.org/method/messages.acceptEncryption new file mode 100644 index 0000000000..47732802b0 --- /dev/null +++ b/data/core.telegram.org/method/messages.acceptEncryption @@ -0,0 +1,190 @@ + + + + + messages.acceptEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.acceptEncryption

+ +

Confirms creation of a secret chat

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+---functions---
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
g_bbytesB = g ^ b mod p, see Wikipedia
key_fingerprintlong64-bit fingerprint of the received key
+

Result

+

EncryptedChat

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400ENCRYPTION_ALREADY_ACCEPTEDSecret chat already accepted.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.addChatUser b/data/core.telegram.org/method/messages.addChatUser new file mode 100644 index 0000000000..dec1244912 --- /dev/null +++ b/data/core.telegram.org/method/messages.addChatUser @@ -0,0 +1,237 @@ + + + + + messages.addChatUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.addChatUser

+ +

Adds a user to a chat and sends a service message on it.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
user_idInputUserUser ID to be added
fwd_limitintNumber of last messages to be forwarded
+

Result

+

messages.StatedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_IS_BLOCKEDYou were blocked by this user.
403USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
400YOU_BLOCKED_USERYou blocked this user.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.checkChatInvite b/data/core.telegram.org/method/messages.checkChatInvite new file mode 100644 index 0000000000..3faca74996 --- /dev/null +++ b/data/core.telegram.org/method/messages.checkChatInvite @@ -0,0 +1,178 @@ + + + + + messages.checkChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkChatInvite

+ +

Check the validity of a chat invite link and get basic info about it

+

+ +
+
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
+chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
+---functions---
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashstringInvite hash in t.me/joinchat/hash
+

Result

+

ChatInvite

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.checkHistoryImport b/data/core.telegram.org/method/messages.checkHistoryImport new file mode 100644 index 0000000000..9abec2cbc3 --- /dev/null +++ b/data/core.telegram.org/method/messages.checkHistoryImport @@ -0,0 +1,152 @@ + + + + + messages.checkHistoryImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkHistoryImport

+ +

Obtains information about a chat export file, generated by a foreign chat app, click here for more info about imported chats ».

+

+ +
+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+---functions---
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
import_headstringBeginning of the message file; up to 100 lines.
+

Result

+

messages.HistoryImportParsed

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.checkHistoryImportPeer b/data/core.telegram.org/method/messages.checkHistoryImportPeer new file mode 100644 index 0000000000..a7d5c85a01 --- /dev/null +++ b/data/core.telegram.org/method/messages.checkHistoryImportPeer @@ -0,0 +1,172 @@ + + + + + messages.checkHistoryImportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkHistoryImportPeer

+ +

Check whether chat history exported from another chat app can be imported into a specific Telegram chat, click here for more info ».

+

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.

+

+ +
+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+---functions---
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where we want to import history ».
+

Result

+

messages.CheckedHistoryImportPeer

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

messages.CheckedHistoryImportPeer

+

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.clearAllDrafts b/data/core.telegram.org/method/messages.clearAllDrafts new file mode 100644 index 0000000000..ee8ead09eb --- /dev/null +++ b/data/core.telegram.org/method/messages.clearAllDrafts @@ -0,0 +1,138 @@ + + + + + messages.clearAllDrafts + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.clearAllDrafts

+ +

Clear all drafts.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.clearAllDrafts#7e58ee9c = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.clearRecentStickers b/data/core.telegram.org/method/messages.clearRecentStickers new file mode 100644 index 0000000000..6245cb4a49 --- /dev/null +++ b/data/core.telegram.org/method/messages.clearRecentStickers @@ -0,0 +1,155 @@ + + + + + messages.clearRecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.clearRecentStickers

+ +

Clear recent stickers

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueSet this flag to clear the list of stickers recently attached to photo or video files
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.createChat b/data/core.telegram.org/method/messages.createChat new file mode 100644 index 0000000000..459f7e05c8 --- /dev/null +++ b/data/core.telegram.org/method/messages.createChat @@ -0,0 +1,197 @@ + + + + + messages.createChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.createChat

+ +

Creates a new chat.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>List of user IDs to be invited
titlestringChat name
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_INVALIDInvalid chat.
400CHAT_TITLE_EMPTYNo chat title provided.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USERS_TOO_FEWNot enough users (to create a chat, for example).
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteChat b/data/core.telegram.org/method/messages.deleteChat new file mode 100644 index 0000000000..953e7e4f9f --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteChat @@ -0,0 +1,170 @@ + + + + + messages.deleteChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteChat

+ +

Delete a chat

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.deleteChat#5bd0ee50 chat_id:long = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteChatUser b/data/core.telegram.org/method/messages.deleteChatUser new file mode 100644 index 0000000000..14c4da06ba --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteChatUser @@ -0,0 +1,208 @@ + + + + + messages.deleteChatUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteChatUser

+ +

Deletes a user from a chat and sends a service message on it.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revoke_historyflags.0?trueRemove the entire chat history of the specified user in this chat.
chat_idlongChat ID
user_idInputUserUser ID to be deleted
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteExportedChatInvite b/data/core.telegram.org/method/messages.deleteExportedChatInvite new file mode 100644 index 0000000000..65a67e647d --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteExportedChatInvite @@ -0,0 +1,155 @@ + + + + + messages.deleteExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteExportedChatInvite

+ +

Delete a chat invite

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
linkstringInvite link
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteHistory b/data/core.telegram.org/method/messages.deleteHistory new file mode 100644 index 0000000000..68124f65bb --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteHistory @@ -0,0 +1,206 @@ + + + + + messages.deleteHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteHistory

+ +

Deletes communication history.

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+---functions---
+messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
just_clearflags.0?trueJust clear history for the current user, without actually removing messages for every chat user
revokeflags.1?trueWhether to delete the message history for all chat participants
peerInputPeerUser or chat, communication history of which will be deleted
max_idintMaximum ID of message to delete
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteMessages b/data/core.telegram.org/method/messages.deleteMessages new file mode 100644 index 0000000000..ffeef81e5b --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteMessages @@ -0,0 +1,177 @@ + + + + + messages.deleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteMessages

+ +

Deletes messages by their identifiers.

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokeflags.0?trueWhether to delete messages for all participants of the chat
idVector<int>Message ID list
+

Result

+

The method returns the list of successfully deleted messages in Vector<int>.

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403MESSAGE_DELETE_FORBIDDENYou can't delete one of the messages you tried to delete, most likely because it is a service message.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deletePhoneCallHistory b/data/core.telegram.org/method/messages.deletePhoneCallHistory new file mode 100644 index 0000000000..e47d303edb --- /dev/null +++ b/data/core.telegram.org/method/messages.deletePhoneCallHistory @@ -0,0 +1,154 @@ + + + + + messages.deletePhoneCallHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deletePhoneCallHistory

+ +

Delete the entire phone call history.

+

+ +
+
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
+---functions---
+messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokeflags.0?trueWhether to remove phone call history for participants as well
+

Result

+

messages.AffectedFoundMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites b/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites new file mode 100644 index 0000000000..3103db9471 --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites @@ -0,0 +1,155 @@ + + + + + messages.deleteRevokedExportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteRevokedExportedChatInvites

+ +

Delete all revoked chat invites

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
admin_idInputUserID of the admin that originally generated the revoked chat invites
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteScheduledMessages b/data/core.telegram.org/method/messages.deleteScheduledMessages new file mode 100644 index 0000000000..e3c959730f --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteScheduledMessages @@ -0,0 +1,160 @@ + + + + + messages.deleteScheduledMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteScheduledMessages

+ +

Delete scheduled messages

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.discardEncryption b/data/core.telegram.org/method/messages.discardEncryption new file mode 100644 index 0000000000..9e5b37e730 --- /dev/null +++ b/data/core.telegram.org/method/messages.discardEncryption @@ -0,0 +1,187 @@ + + + + + messages.discardEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.discardEncryption

+ +

Cancels a request for creation and/or delete info on secret chat.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
delete_historyflags.0?trueWhether to delete the entire chat history for the other user as well
chat_idintSecret chat ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_EMPTYThe provided chat ID is empty.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editChatAbout b/data/core.telegram.org/method/messages.editChatAbout new file mode 100644 index 0000000000..206db20474 --- /dev/null +++ b/data/core.telegram.org/method/messages.editChatAbout @@ -0,0 +1,216 @@ + + + + + messages.editChatAbout + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatAbout

+ +

Edit the description of a group/supergroup/channel.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe group/supergroup/channel.
aboutstringThe new description
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ABOUT_NOT_MODIFIEDAbout text has not changed.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editChatAdmin b/data/core.telegram.org/method/messages.editChatAdmin new file mode 100644 index 0000000000..ee2e67f68a --- /dev/null +++ b/data/core.telegram.org/method/messages.editChatAdmin @@ -0,0 +1,195 @@ + + + + + messages.editChatAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatAdmin

+ +

Make a user admin in a legacy group.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongThe ID of the group
user_idInputUserThe user to make admin
is_adminBoolWhether to make him admin
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editChatDefaultBannedRights b/data/core.telegram.org/method/messages.editChatDefaultBannedRights new file mode 100644 index 0000000000..caf4ce2cba --- /dev/null +++ b/data/core.telegram.org/method/messages.editChatDefaultBannedRights @@ -0,0 +1,206 @@ + + + + + messages.editChatDefaultBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatDefaultBannedRights

+ +

Edit the default banned rights of a channel/supergroup/group.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer
banned_rightsChatBannedRightsThe new global rights
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BANNED_RIGHTS_INVALIDYou provided some invalid flags in the banned rights.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
400UNTIL_DATE_INVALIDInvalid until date provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editChatPhoto b/data/core.telegram.org/method/messages.editChatPhoto new file mode 100644 index 0000000000..e5fb3af727 --- /dev/null +++ b/data/core.telegram.org/method/messages.editChatPhoto @@ -0,0 +1,203 @@ + + + + + messages.editChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatPhoto

+ +

Changes chat photo and sends a service message on it

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
photoInputChatPhotoPhoto to be set
+

Result

+

Returns a messages.StatedMessage object containing a service message sent during an action.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALIDPhoto invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editChatTitle b/data/core.telegram.org/method/messages.editChatTitle new file mode 100644 index 0000000000..1cd755c064 --- /dev/null +++ b/data/core.telegram.org/method/messages.editChatTitle @@ -0,0 +1,193 @@ + + + + + messages.editChatTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatTitle

+ +

Chanages chat name and sends a service message on it.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatTitle#73783ffd chat_id:long title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
titlestringNew chat name, different from the old one
+

Result

+

Returns a messages.StatedMessage object containing a service message sent during an action.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editExportedChatInvite b/data/core.telegram.org/method/messages.editExportedChatInvite new file mode 100644 index 0000000000..7b7792f6d0 --- /dev/null +++ b/data/core.telegram.org/method/messages.editExportedChatInvite @@ -0,0 +1,193 @@ + + + + + messages.editExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editExportedChatInvite

+ +

Edit an exported chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+---functions---
+messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.2?trueWhether to revoke the chat invite
peerInputPeerChat
linkstringInvite link
expire_dateflags.0?intNew expiration date
usage_limitflags.1?intMaximum number of users that can join using this link
+

Result

+

messages.ExportedChatInvite

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editInlineBotMessage b/data/core.telegram.org/method/messages.editInlineBotMessage new file mode 100644 index 0000000000..a7d7203284 --- /dev/null +++ b/data/core.telegram.org/method/messages.editInlineBotMessage @@ -0,0 +1,206 @@ + + + + + messages.editInlineBotMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editInlineBotMessage

+ +

Edit an inline bot message

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable webpage preview
idInputBotInlineMessageIDSent inline message ID
messageflags.11?stringMessage
mediaflags.14?InputMediaMedia
reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_NOT_MODIFIEDThe message text has not changed.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editMessage b/data/core.telegram.org/method/messages.editMessage new file mode 100644 index 0000000000..136fbdb7ab --- /dev/null +++ b/data/core.telegram.org/method/messages.editMessage @@ -0,0 +1,338 @@ + + + + + messages.editMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editMessage

+ +

Edit message

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable webpage preview
peerInputPeerWhere was the message sent
idintID of the message to edit
messageflags.11?stringNew message
mediaflags.14?InputMediaNew attached media
reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.15?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400ENTITIES_TOO_LONGYou provided too many styled message entities.
403INLINE_BOT_REQUIREDOnly the inline bot can edit message.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_GROUPED_INVALIDYou tried to send media of different types in an album.
400MEDIA_NEW_INVALIDThe new media is invalid.
400MEDIA_PREV_INVALIDPrevious media invalid.
403MESSAGE_AUTHOR_REQUIREDMessage author required.
400MESSAGE_EDIT_TIME_EXPIREDYou can't edit this message anymore, too much time has passed since its creation.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_NOT_MODIFIEDThe message text has not changed.
400MESSAGE_TOO_LONGThe provided message is too long.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.exportChatInvite b/data/core.telegram.org/method/messages.exportChatInvite new file mode 100644 index 0000000000..3ed5b23341 --- /dev/null +++ b/data/core.telegram.org/method/messages.exportChatInvite @@ -0,0 +1,217 @@ + + + + + messages.exportChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportChatInvite

+ +

Export an invite link for a chat

+

+ +
+
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
+---functions---
+messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
legacy_revoke_permanentflags.2?trueLegacy flag, reproducing legacy behavior of this method: if set, revokes all previous links before creating a new one. Kept for bot API BC, should not be used by modern clients.
peerInputPeerChat
expire_dateflags.0?intExpiration date
usage_limitflags.1?intMaximum number of users that can join using this link
+

Result

+

ExportedChatInvite

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400EXPIRE_DATE_INVALIDThe specified expiration date is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USAGE_LIMIT_INVALIDThe specified usage limit is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.faveSticker b/data/core.telegram.org/method/messages.faveSticker new file mode 100644 index 0000000000..6e27b088c1 --- /dev/null +++ b/data/core.telegram.org/method/messages.faveSticker @@ -0,0 +1,172 @@ + + + + + messages.faveSticker + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.faveSticker

+ +

Mark a sticker as favorite

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputDocumentSticker to mark as favorite
unfaveBoolUnfavorite
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.forwardMessage b/data/core.telegram.org/method/messages.forwardMessage new file mode 100644 index 0000000000..fd72ffa74f --- /dev/null +++ b/data/core.telegram.org/method/messages.forwardMessage @@ -0,0 +1,177 @@ + + + + + messages.forwardMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.forwardMessage

+ +

Forwards single messages.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerUser or chat where a message will be forwarded
idintForwarded message ID
random_idlongUnique client message ID required to prevent message resending
+

Result

+

messages.StatedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid
400MESSAGE_ID_INVALIDThe provided message id is invalid
400PEER_ID_INVALIDThe provided peer id is invalid
400YOU_BLOCKED_USERYou blocked this user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.forwardMessages b/data/core.telegram.org/method/messages.forwardMessages new file mode 100644 index 0000000000..35fe91fc45 --- /dev/null +++ b/data/core.telegram.org/method/messages.forwardMessages @@ -0,0 +1,363 @@ + + + + + messages.forwardMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.forwardMessages

+ +

Forwards messages by their IDs.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send messages silently (no notification will be triggered on the destination clients)
backgroundflags.6?trueWhether to send the message in background
with_my_scoreflags.8?trueWhen forwarding games, whether to include your score in the game
drop_authorflags.11?trueWhether to forward messages without quoting the original author
drop_media_captionsflags.12?trueWhether to strip captions from media
from_peerInputPeerSource of messages
idVector<int>IDs of messages
random_idVector<long>Random ID to prevent resending of messages
to_peerInputPeerDestination peer
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400GROUPED_MEDIA_INVALIDInvalid grouped media.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
420P0NY_FLOODWAIT 
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_INVALIDA provided random ID is invalid.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
400SLOWMODE_MULTI_MSGS_DISABLEDSlowmode is enabled, you cannot forward multiple messages to this group.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getAdminsWithInvites b/data/core.telegram.org/method/messages.getAdminsWithInvites new file mode 100644 index 0000000000..26e37e4b8c --- /dev/null +++ b/data/core.telegram.org/method/messages.getAdminsWithInvites @@ -0,0 +1,149 @@ + + + + + messages.getAdminsWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAdminsWithInvites

+ +

Get info about chat invites generated by admins.

+

+ +
+
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
+---functions---
+messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
+

Result

+

messages.ChatAdminsWithInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getAllChats b/data/core.telegram.org/method/messages.getAllChats new file mode 100644 index 0000000000..c7d25cad86 --- /dev/null +++ b/data/core.telegram.org/method/messages.getAllChats @@ -0,0 +1,150 @@ + + + + + messages.getAllChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAllChats

+ +

Get all chats, channels and supergroups

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
except_idsVector<long>Except these chats/channels/supergroups
+

Result

+

messages.Chats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getAllDrafts b/data/core.telegram.org/method/messages.getAllDrafts new file mode 100644 index 0000000000..0b41aefe85 --- /dev/null +++ b/data/core.telegram.org/method/messages.getAllDrafts @@ -0,0 +1,143 @@ + + + + + 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 new file mode 100644 index 0000000000..a84ad9cb14 --- /dev/null +++ b/data/core.telegram.org/method/messages.getAllStickers @@ -0,0 +1,153 @@ + + + + + messages.getAllStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAllStickers

+ +

Get all installed stickers

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+---functions---
+messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.AllStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getArchivedStickers b/data/core.telegram.org/method/messages.getArchivedStickers new file mode 100644 index 0000000000..81acf27c79 --- /dev/null +++ b/data/core.telegram.org/method/messages.getArchivedStickers @@ -0,0 +1,167 @@ + + + + + messages.getArchivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getArchivedStickers

+ +

Get all archived stickers

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
+---functions---
+messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueGet mask stickers
offset_idlongOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
+

Result

+

messages.ArchivedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getAttachedStickers b/data/core.telegram.org/method/messages.getAttachedStickers new file mode 100644 index 0000000000..f5bde49924 --- /dev/null +++ b/data/core.telegram.org/method/messages.getAttachedStickers @@ -0,0 +1,148 @@ + + + + + messages.getAttachedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAttachedStickers

+ +

Get stickers attached to a photo or video

+

+ +
+
---functions---
+messages.getAttachedStickers#cc5b67cc media:InputStickeredMedia = Vector<StickerSetCovered>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
mediaInputStickeredMediaStickered media
+

Result

+

Vector<StickerSetCovered>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getBotCallbackAnswer b/data/core.telegram.org/method/messages.getBotCallbackAnswer new file mode 100644 index 0000000000..47db722c11 --- /dev/null +++ b/data/core.telegram.org/method/messages.getBotCallbackAnswer @@ -0,0 +1,226 @@ + + + + + messages.getBotCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getBotCallbackAnswer

+ +

Press an inline callback button and get a callback answer from the bot

+

+ +
+
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+---functions---
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
gameflags.1?trueWhether this is a "play game" button
peerInputPeerWhere was the inline keyboard sent
msg_idintID of the Message with the inline keyboard
dataflags.0?bytesCallback data
passwordflags.2?InputCheckPasswordSRPFor buttons requiring you to verify your identity with your 2FA password, the SRP payload generated using SRP.
+

Result

+

messages.BotCallbackAnswer

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400DATA_INVALIDEncrypted data invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-503TimeoutTimeout while fetching data.
+

Related pages

+

keyboardButtonCallback

+

Callback button

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getChatInviteImporters b/data/core.telegram.org/method/messages.getChatInviteImporters new file mode 100644 index 0000000000..7ee6e1e7b3 --- /dev/null +++ b/data/core.telegram.org/method/messages.getChatInviteImporters @@ -0,0 +1,172 @@ + + + + + messages.getChatInviteImporters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getChatInviteImporters

+ +

Get info about the users that joined the chat using a specific chat invite

+

+ +
+
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+---functions---
+messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
linkstringInvite link
offset_dateintOffsets for pagination, for more info click here
offset_userInputUserUser ID for pagination
limitintMaximum number of results to return, see pagination
+

Result

+

messages.ChatInviteImporters

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getChats b/data/core.telegram.org/method/messages.getChats new file mode 100644 index 0000000000..a37b1501e6 --- /dev/null +++ b/data/core.telegram.org/method/messages.getChats @@ -0,0 +1,173 @@ + + + + + messages.getChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getChats

+ +

Returns chat basic info on their IDs.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+messages.getChats#49e9528f id:Vector<long> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<long>List of chat IDs
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getCommonChats b/data/core.telegram.org/method/messages.getCommonChats new file mode 100644 index 0000000000..3cdef9f345 --- /dev/null +++ b/data/core.telegram.org/method/messages.getCommonChats @@ -0,0 +1,185 @@ + + + + + messages.getCommonChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getCommonChats

+ +

Get chats in common with a user

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
max_idlongMaximum ID of chat to return (see pagination)
limitintMaximum number of results to return, see pagination
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getDhConfig b/data/core.telegram.org/method/messages.getDhConfig new file mode 100644 index 0000000000..b9adc1ca90 --- /dev/null +++ b/data/core.telegram.org/method/messages.getDhConfig @@ -0,0 +1,175 @@ + + + + + messages.getDhConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDhConfig

+ +

Returns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.

+

+ +
+
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
+messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
+---functions---
+messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
versionintValue of the version parameter from messages.dhConfig, avialable at the client
random_lengthintLength of the required random sequence
+

Result

+

messages.DhConfig

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400RANDOM_LENGTH_INVALIDRandom length invalid.
+

Related pages

+

messages.dhConfig

+

New set of configuring parameters.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getDialogFilters b/data/core.telegram.org/method/messages.getDialogFilters new file mode 100644 index 0000000000..cd4956007c --- /dev/null +++ b/data/core.telegram.org/method/messages.getDialogFilters @@ -0,0 +1,136 @@ + + + + + messages.getDialogFilters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDialogFilters

+ +

Get folders

+

+ +
+
---functions---
+messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<DialogFilter>

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getDialogUnreadMarks b/data/core.telegram.org/method/messages.getDialogUnreadMarks new file mode 100644 index 0000000000..7cf19f4084 --- /dev/null +++ b/data/core.telegram.org/method/messages.getDialogUnreadMarks @@ -0,0 +1,133 @@ + + + + + messages.getDialogUnreadMarks + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDialogUnreadMarks

+ +

Get dialogs manually marked as unread

+

+ +
+
---functions---
+messages.getDialogUnreadMarks#22e24e22 = Vector<DialogPeer>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<DialogPeer>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getDialogs b/data/core.telegram.org/method/messages.getDialogs new file mode 100644 index 0000000000..7207b94946 --- /dev/null +++ b/data/core.telegram.org/method/messages.getDialogs @@ -0,0 +1,213 @@ + + + + + messages.getDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDialogs

+ +

Returns the current user dialog list.

+

+ +
+
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
+---functions---
+messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_pinnedflags.0?trueExclude pinned dialogs
folder_idflags.1?intPeer folder ID, for more info click here
offset_dateintOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
offset_peerInputPeerOffset peer for pagination
limitintNumber of list elements to be returned
hashlongHash for pagination, for more info click here
+

Result

+

messages.Dialogs

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
400OFFSET_PEER_ID_INVALIDThe provided offset peer is invalid.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getDiscussionMessage b/data/core.telegram.org/method/messages.getDiscussionMessage new file mode 100644 index 0000000000..cf281a5b58 --- /dev/null +++ b/data/core.telegram.org/method/messages.getDiscussionMessage @@ -0,0 +1,183 @@ + + + + + messages.getDiscussionMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDiscussionMessage

+ +

Get discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group

+

+ +
+
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
+---functions---
+messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChannel ID
msg_idintMessage ID
+

Result

+

messages.DiscussionMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getDocumentByHash b/data/core.telegram.org/method/messages.getDocumentByHash new file mode 100644 index 0000000000..e74833bb5d --- /dev/null +++ b/data/core.telegram.org/method/messages.getDocumentByHash @@ -0,0 +1,178 @@ + + + + + messages.getDocumentByHash + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDocumentByHash

+ +

Get a document by its SHA256 hash, mainly used for gifs

+

+ +
+
documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+---functions---
+messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
sha256bytesSHA256 of file
sizeintSize of the file in bytes
mime_typestringMime type
+

Result

+

Document

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400SHA256_HASH_INVALIDThe provided SHA256 hash is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getEmojiKeywords b/data/core.telegram.org/method/messages.getEmojiKeywords new file mode 100644 index 0000000000..6eb0c1c9c3 --- /dev/null +++ b/data/core.telegram.org/method/messages.getEmojiKeywords @@ -0,0 +1,149 @@ + + + + + messages.getEmojiKeywords + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiKeywords

+ +

Get localized emoji keywords

+

+ +
+
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+---functions---
+messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Result

+

EmojiKeywordsDifference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getEmojiKeywordsDifference b/data/core.telegram.org/method/messages.getEmojiKeywordsDifference new file mode 100644 index 0000000000..d2a6bd18dd --- /dev/null +++ b/data/core.telegram.org/method/messages.getEmojiKeywordsDifference @@ -0,0 +1,154 @@ + + + + + messages.getEmojiKeywordsDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiKeywordsDifference

+ +

Get changed emoji keywords

+

+ +
+
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+---functions---
+messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious emoji keyword localization version
+

Result

+

EmojiKeywordsDifference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getEmojiURL b/data/core.telegram.org/method/messages.getEmojiURL new file mode 100644 index 0000000000..f89cca4caf --- /dev/null +++ b/data/core.telegram.org/method/messages.getEmojiURL @@ -0,0 +1,149 @@ + + + + + messages.getEmojiURL + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiURL

+ +

Returns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

+

+ +
+
emojiURL#a575739d url:string = EmojiURL;
+---functions---
+messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code for which the emoji replacements will be suggested
+

Result

+

EmojiURL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getExportedChatInvite b/data/core.telegram.org/method/messages.getExportedChatInvite new file mode 100644 index 0000000000..26aa13353f --- /dev/null +++ b/data/core.telegram.org/method/messages.getExportedChatInvite @@ -0,0 +1,155 @@ + + + + + messages.getExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getExportedChatInvite

+ +

Get info about a chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+---functions---
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
linkstringInvite link
+

Result

+

messages.ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getFavedStickers b/data/core.telegram.org/method/messages.getFavedStickers new file mode 100644 index 0000000000..43d2f3b65a --- /dev/null +++ b/data/core.telegram.org/method/messages.getFavedStickers @@ -0,0 +1,153 @@ + + + + + messages.getFavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getFavedStickers

+ +

Get faved stickers

+

+ +
+
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+---functions---
+messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.FavedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getFeaturedStickers b/data/core.telegram.org/method/messages.getFeaturedStickers new file mode 100644 index 0000000000..f9d1ae7496 --- /dev/null +++ b/data/core.telegram.org/method/messages.getFeaturedStickers @@ -0,0 +1,153 @@ + + + + + messages.getFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getFeaturedStickers

+ +

Get featured stickers

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+---functions---
+messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.FeaturedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getFullChat b/data/core.telegram.org/method/messages.getFullChat new file mode 100644 index 0000000000..d6a8545748 --- /dev/null +++ b/data/core.telegram.org/method/messages.getFullChat @@ -0,0 +1,172 @@ + + + + + messages.getFullChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getFullChat

+ +

Returns full chat info according to its ID.

+

+ +
+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
+---functions---
+messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
+

Result

+

messages.ChatFull

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getGameHighScores b/data/core.telegram.org/method/messages.getGameHighScores new file mode 100644 index 0000000000..6ba307d512 --- /dev/null +++ b/data/core.telegram.org/method/messages.getGameHighScores @@ -0,0 +1,187 @@ + + + + + messages.getGameHighScores + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getGameHighScores

+ +

Get highscores of a game

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+---functions---
+messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerWhere was the game sent
idintID of message with game media attachment
user_idInputUserGet high scores made by a certain user
+

Result

+

messages.HighScores

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getInlineBotResults b/data/core.telegram.org/method/messages.getInlineBotResults new file mode 100644 index 0000000000..160d8caa5c --- /dev/null +++ b/data/core.telegram.org/method/messages.getInlineBotResults @@ -0,0 +1,226 @@ + + + + + messages.getInlineBotResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getInlineBotResults

+ +

Query an inline bot

+

+ +
+
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
+---functions---
+messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
botInputUserThe bot to query
peerInputPeerThe currently opened chat
geo_pointflags.0?InputGeoPointThe geolocation, if requested
querystringThe query
offsetstringThe offset within the results, will be passed directly as-is to the bot.
+

Result

+

messages.BotResults

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_INLINE_DISABLEDThis bot can't be used in inline mode.
400BOT_INVALIDThis is not a valid bot.
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
-503TimeoutTimeout while fetching data.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getInlineGameHighScores b/data/core.telegram.org/method/messages.getInlineGameHighScores new file mode 100644 index 0000000000..a8fb43a61e --- /dev/null +++ b/data/core.telegram.org/method/messages.getInlineGameHighScores @@ -0,0 +1,177 @@ + + + + + messages.getInlineGameHighScores + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getInlineGameHighScores

+ +

Get highscores of a game sent using an inline bot

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+---functions---
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputBotInlineMessageIDID of inline message
user_idInputUserGet high scores of a certain user
+

Result

+

messages.HighScores

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getMaskStickers b/data/core.telegram.org/method/messages.getMaskStickers new file mode 100644 index 0000000000..59a25592ce --- /dev/null +++ b/data/core.telegram.org/method/messages.getMaskStickers @@ -0,0 +1,153 @@ + + + + + messages.getMaskStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMaskStickers

+ +

Get installed mask stickers

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+---functions---
+messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.AllStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getMessageEditData b/data/core.telegram.org/method/messages.getMessageEditData new file mode 100644 index 0000000000..a740752192 --- /dev/null +++ b/data/core.telegram.org/method/messages.getMessageEditData @@ -0,0 +1,186 @@ + + + + + messages.getMessageEditData + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessageEditData

+ +

Find out if a media message's caption can be edited

+

+ +
+
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
+---functions---
+messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where the media was sent
idintID of message
+

Result

+

messages.MessageEditData

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403MESSAGE_AUTHOR_REQUIREDMessage author required.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getMessageReactionsList b/data/core.telegram.org/method/messages.getMessageReactionsList new file mode 100644 index 0000000000..ef469a7f4c --- /dev/null +++ b/data/core.telegram.org/method/messages.getMessageReactionsList @@ -0,0 +1,178 @@ + + + + + messages.getMessageReactionsList + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessageReactionsList

+ +

Get full message reaction list

+

+ +
+
 Method schema is available as of layer 136. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerPeer
idintMessage ID
reactionflags.0?stringGet only reactions of this type (UTF8 emoji)
offsetflags.1?stringOffset (typically taken from the next_offset field of the returned MessageReactionsList)
limitintMaximum number of results to return, see pagination
+

Result

+

MessageReactionsList

+

Bots can use this method

+

Related pages

+

MessageReactionsList

+

List of message reactions

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getMessageReadParticipants b/data/core.telegram.org/method/messages.getMessageReadParticipants new file mode 100644 index 0000000000..2b44d3f516 --- /dev/null +++ b/data/core.telegram.org/method/messages.getMessageReadParticipants @@ -0,0 +1,173 @@ + + + + + messages.getMessageReadParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessageReadParticipants

+ +

Get which users read a specific message: only available for groups and supergroups with less than chat_read_mark_size_threshold members, read receipts will be stored for chat_read_mark_expire_period seconds after the message was sent, see client configuration for more info ».

+

+ +
+
---functions---
+messages.getMessageReadParticipants#2c6f97b7 peer:InputPeer msg_id:int = Vector<long>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerDialog
msg_idintMessage ID
+

Result

+

Vector<long>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_TOO_BIGThis method is not available for groups with more than chat_read_mark_size_threshold members, see client configuration ».
+

Related pages

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getMessages b/data/core.telegram.org/method/messages.getMessages new file mode 100644 index 0000000000..59ee1f69d4 --- /dev/null +++ b/data/core.telegram.org/method/messages.getMessages @@ -0,0 +1,153 @@ + + + + + messages.getMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessages

+ +

Returns the list of messages by their IDs.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputMessage>Message ID list
+

Result

+

messages.Messages

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getMessagesReactions b/data/core.telegram.org/method/messages.getMessagesReactions new file mode 100644 index 0000000000..2f5c3d4892 --- /dev/null +++ b/data/core.telegram.org/method/messages.getMessagesReactions @@ -0,0 +1,153 @@ + + + + + messages.getMessagesReactions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessagesReactions

+ +

Get message reactions

+

+ +
+
 Method schema is available as of layer 136. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>Message IDs
+

Result

+

Updates

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getMessagesViews b/data/core.telegram.org/method/messages.getMessagesViews new file mode 100644 index 0000000000..a2ab25b93d --- /dev/null +++ b/data/core.telegram.org/method/messages.getMessagesViews @@ -0,0 +1,199 @@ + + + + + messages.getMessagesViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessagesViews

+ +

Get and increase the view counter of a message sent or forwarded from a channel

+

+ +
+
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
+---functions---
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where the message was found
idVector<int>ID of message
incrementBoolWhether to mark the message as viewed and increment the view counter
+

Result

+

Vector<int>

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getOldFeaturedStickers b/data/core.telegram.org/method/messages.getOldFeaturedStickers new file mode 100644 index 0000000000..1df560d371 --- /dev/null +++ b/data/core.telegram.org/method/messages.getOldFeaturedStickers @@ -0,0 +1,163 @@ + + + + + messages.getOldFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getOldFeaturedStickers

+ +

Method for fetching previously featured stickers

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+---functions---
+messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

messages.FeaturedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getOnlines b/data/core.telegram.org/method/messages.getOnlines new file mode 100644 index 0000000000..8ab9c93408 --- /dev/null +++ b/data/core.telegram.org/method/messages.getOnlines @@ -0,0 +1,171 @@ + + + + + messages.getOnlines + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getOnlines

+ +

Get count of online users in a chat

+

+ +
+
chatOnlines#f041e250 onlines:int = ChatOnlines;
+---functions---
+messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat
+

Result

+

ChatOnlines

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getPeerDialogs b/data/core.telegram.org/method/messages.getPeerDialogs new file mode 100644 index 0000000000..35bc3b3a15 --- /dev/null +++ b/data/core.telegram.org/method/messages.getPeerDialogs @@ -0,0 +1,181 @@ + + + + + messages.getPeerDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getPeerDialogs

+ +

Get dialog info of specified peers

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+---functions---
+messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peersVector<InputDialogPeer>Peers
+

Result

+

messages.PeerDialogs

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getPeerSettings b/data/core.telegram.org/method/messages.getPeerSettings new file mode 100644 index 0000000000..91606c866b --- /dev/null +++ b/data/core.telegram.org/method/messages.getPeerSettings @@ -0,0 +1,171 @@ + + + + + messages.getPeerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getPeerSettings

+ +

Get peer settings

+

+ +
+
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
+---functions---
+messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer
+

Result

+

PeerSettings

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getPinnedDialogs b/data/core.telegram.org/method/messages.getPinnedDialogs new file mode 100644 index 0000000000..64f6c1867a --- /dev/null +++ b/data/core.telegram.org/method/messages.getPinnedDialogs @@ -0,0 +1,169 @@ + + + + + messages.getPinnedDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getPinnedDialogs

+ +

Get pinned dialogs

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+---functions---
+messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Result

+

messages.PeerDialogs

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getPollResults b/data/core.telegram.org/method/messages.getPollResults new file mode 100644 index 0000000000..df8aae8cbf --- /dev/null +++ b/data/core.telegram.org/method/messages.getPollResults @@ -0,0 +1,177 @@ + + + + + messages.getPollResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getPollResults

+ +

Get poll results

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where the poll was found
msg_idintMessage ID of poll message
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getPollVotes b/data/core.telegram.org/method/messages.getPollVotes new file mode 100644 index 0000000000..0d08473f1c --- /dev/null +++ b/data/core.telegram.org/method/messages.getPollVotes @@ -0,0 +1,204 @@ + + + + + messages.getPollVotes + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getPollVotes

+ +

Get poll results for non-anonymous polls

+

+ +
+
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
+---functions---
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerChat where the poll was sent
idintMessage ID
optionflags.0?bytesGet only results for the specified poll option
offsetflags.1?stringOffset for results, taken from the next_offset field of messages.votesList, initially an empty string.
Note: if no more results are available, the method call will return an empty next_offset; thus, avoid providing the next_offset returned in messages.votesList if it is empty, to avoid an infinite loop.
limitintNumber of results to return
+

Result

+

messages.VotesList

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
403BROADCAST_FORBIDDENParticipants of polls in channels should stay anonymous.
400MSG_ID_INVALIDInvalid message ID provided.
403POLL_VOTE_REQUIREDCast a vote in the poll before calling this method.
+

Related pages

+

messages.votesList

+

How users voted in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getRecentLocations b/data/core.telegram.org/method/messages.getRecentLocations new file mode 100644 index 0000000000..2150b8166e --- /dev/null +++ b/data/core.telegram.org/method/messages.getRecentLocations @@ -0,0 +1,165 @@ + + + + + messages.getRecentLocations + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getRecentLocations

+ +

Get live location history of a certain user

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerUser
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

messages.Messages

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getRecentStickers b/data/core.telegram.org/method/messages.getRecentStickers new file mode 100644 index 0000000000..4ce9d8ed7c --- /dev/null +++ b/data/core.telegram.org/method/messages.getRecentStickers @@ -0,0 +1,163 @@ + + + + + messages.getRecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getRecentStickers

+ +

Get recent stickers

+

+ +
+
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
+messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
+---functions---
+messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueGet stickers recently attached to photo or video files
hashlongHash for pagination, for more info click here
+

Result

+

messages.RecentStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getReplies b/data/core.telegram.org/method/messages.getReplies new file mode 100644 index 0000000000..a6af9cba26 --- /dev/null +++ b/data/core.telegram.org/method/messages.getReplies @@ -0,0 +1,217 @@ + + + + + messages.getReplies + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getReplies

+ +

Get messages in a reply thread

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
msg_idintMessage ID
offset_idintOffsets for pagination, for more info click here
offset_dateintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintIf a positive value was transferred, the method will return only messages with ID smaller than max_id
min_idintIf a positive value was transferred, the method will return only messages with ID bigger than min_id
hashlongHash for pagination, for more info click here
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getSavedGifs b/data/core.telegram.org/method/messages.getSavedGifs new file mode 100644 index 0000000000..9751dc5010 --- /dev/null +++ b/data/core.telegram.org/method/messages.getSavedGifs @@ -0,0 +1,153 @@ + + + + + messages.getSavedGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getSavedGifs

+ +

Get saved GIFs

+

+ +
+
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
+messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
+---functions---
+messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.SavedGifs

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getScheduledHistory b/data/core.telegram.org/method/messages.getScheduledHistory new file mode 100644 index 0000000000..fc05c81d9c --- /dev/null +++ b/data/core.telegram.org/method/messages.getScheduledHistory @@ -0,0 +1,182 @@ + + + + + messages.getScheduledHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getScheduledHistory

+ +

Get scheduled messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
hashlongHash for pagination, for more info click here
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getSearchCounters b/data/core.telegram.org/method/messages.getSearchCounters new file mode 100644 index 0000000000..da24b43d74 --- /dev/null +++ b/data/core.telegram.org/method/messages.getSearchCounters @@ -0,0 +1,173 @@ + + + + + messages.getSearchCounters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getSearchCounters

+ +

Get the number of results that would be found by a messages.search call with the same parameters

+

+ +
+
---functions---
+messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where to search
filtersVector<MessagesFilter>Search filters
+

Result

+

Vector<messages.SearchCounter>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

messages.search

+

Gets back found messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getSplitRanges b/data/core.telegram.org/method/messages.getSplitRanges new file mode 100644 index 0000000000..1e89a6af54 --- /dev/null +++ b/data/core.telegram.org/method/messages.getSplitRanges @@ -0,0 +1,133 @@ + + + + + messages.getSplitRanges + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getSplitRanges

+ +

Get message ranges for saving the user's chat history

+

+ +
+
---functions---
+messages.getSplitRanges#1cff7e08 = Vector<MessageRange>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<MessageRange>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getStickerSet b/data/core.telegram.org/method/messages.getStickerSet new file mode 100644 index 0000000000..fd7c9375f1 --- /dev/null +++ b/data/core.telegram.org/method/messages.getStickerSet @@ -0,0 +1,172 @@ + + + + + messages.getStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getStickerSet

+ +

Get info about a stickerset

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+---functions---
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetStickerset
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMOTICON_STICKERPACK_MISSING 
400STICKERSET_INVALIDThe provided sticker set is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getStickers b/data/core.telegram.org/method/messages.getStickers new file mode 100644 index 0000000000..f6ad0f6907 --- /dev/null +++ b/data/core.telegram.org/method/messages.getStickers @@ -0,0 +1,175 @@ + + + + + messages.getStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getStickers

+ +

Get stickers by emoji

+

+ +
+
messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
+---functions---
+messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringThe emoji
hashlongHash for pagination, for more info click here
+

Result

+

messages.Stickers

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400EMOTICON_EMPTYThe emoji is empty.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getSuggestedDialogFilters b/data/core.telegram.org/method/messages.getSuggestedDialogFilters new file mode 100644 index 0000000000..9eac88e7ff --- /dev/null +++ b/data/core.telegram.org/method/messages.getSuggestedDialogFilters @@ -0,0 +1,136 @@ + + + + + messages.getSuggestedDialogFilters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getSuggestedDialogFilters

+ +

Get suggested folders

+

+ +
+
---functions---
+messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<DialogFilterSuggested>

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getUnreadMentions b/data/core.telegram.org/method/messages.getUnreadMentions new file mode 100644 index 0000000000..f5edcf0b9b --- /dev/null +++ b/data/core.telegram.org/method/messages.getUnreadMentions @@ -0,0 +1,212 @@ + + + + + messages.getUnreadMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getUnreadMentions

+ +

Get unread messages where we were mentioned

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where to look for mentions
offset_idintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintMaximum message ID to return, see pagination
min_idintMinimum message ID to return, see pagination
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getWebPage b/data/core.telegram.org/method/messages.getWebPage new file mode 100644 index 0000000000..5162dd1cc9 --- /dev/null +++ b/data/core.telegram.org/method/messages.getWebPage @@ -0,0 +1,177 @@ + + + + + messages.getWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getWebPage

+ +

Get instant view page

+

+ +
+
webPageEmpty#eb1477e8 id:long = WebPage;
+webPagePending#c586da1c id:long date:int = WebPage;
+webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
+---functions---
+messages.getWebPage#32ca8f91 url:string hash:int = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL of IV page to fetch
hashintHash for pagination, for more info click here
+

Result

+

WebPage

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WC_CONVERT_URL_INVALIDWC convert URL invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getWebPagePreview b/data/core.telegram.org/method/messages.getWebPagePreview new file mode 100644 index 0000000000..1bff9722fb --- /dev/null +++ b/data/core.telegram.org/method/messages.getWebPagePreview @@ -0,0 +1,191 @@ + + + + + messages.getWebPagePreview + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getWebPagePreview

+ +

Get preview of webpage

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+---functions---
+messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringMessage from which to extract the preview
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
+

Result

+

MessageMedia

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty.
+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.hidePeerSettingsBar b/data/core.telegram.org/method/messages.hidePeerSettingsBar new file mode 100644 index 0000000000..0423a4ffe1 --- /dev/null +++ b/data/core.telegram.org/method/messages.hidePeerSettingsBar @@ -0,0 +1,153 @@ + + + + + messages.hidePeerSettingsBar + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.hidePeerSettingsBar

+ +

Should be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
+

Result

+

Bool

+

Related pages

+

peerSettings

+

Peer settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.importChatInvite b/data/core.telegram.org/method/messages.importChatInvite new file mode 100644 index 0000000000..af4e306be1 --- /dev/null +++ b/data/core.telegram.org/method/messages.importChatInvite @@ -0,0 +1,227 @@ + + + + + messages.importChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.importChatInvite

+ +

Import a chat invite and join a private chat/supergroup/channel

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.importChatInvite#6c50051c hash:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashstringhash from t.me/joinchat/hash
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_INVALIDInvalid chat.
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.initHistoryImport b/data/core.telegram.org/method/messages.initHistoryImport new file mode 100644 index 0000000000..247e72e358 --- /dev/null +++ b/data/core.telegram.org/method/messages.initHistoryImport @@ -0,0 +1,191 @@ + + + + + messages.initHistoryImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.initHistoryImport

+ +

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

+

+ +
+
messages.historyImport#1662af0b id:long = messages.HistoryImport;
+---functions---
+messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe Telegram chat where the history should be imported.
fileInputFileFile with messages to import.
media_countintNumber of media files associated with the chat that will be uploaded using messages.uploadImportedMedia.
+

Result

+

messages.HistoryImport

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400IMPORT_FILE_INVALIDThe specified chat export file is invalid.
400IMPORT_FORMAT_UNRECOGNIZEDThe specified chat export file was exported from an unsupported chat app.
406PREVIOUS_CHAT_IMPORT_ACTIVE_WAIT_5MINImport for this chat is already in progress, wait 5 minutes before starting a new one.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

messages.uploadImportedMedia

+

Upload a media file associated with an imported chat, click here for more info ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.installStickerSet b/data/core.telegram.org/method/messages.installStickerSet new file mode 100644 index 0000000000..514e6bb84f --- /dev/null +++ b/data/core.telegram.org/method/messages.installStickerSet @@ -0,0 +1,172 @@ + + + + + messages.installStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.installStickerSet

+ +

Install a stickerset

+

+ +
+
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
+messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
+---functions---
+messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetStickerset to install
archivedBoolWhether to archive stickerset
+

Result

+

messages.StickerSetInstallResult

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.markDialogUnread b/data/core.telegram.org/method/messages.markDialogUnread new file mode 100644 index 0000000000..7eaba0110b --- /dev/null +++ b/data/core.telegram.org/method/messages.markDialogUnread @@ -0,0 +1,160 @@ + + + + + messages.markDialogUnread + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.markDialogUnread

+ +

Manually mark dialog as unread

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueMark as unread/read
peerInputDialogPeerDialog
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.migrateChat b/data/core.telegram.org/method/messages.migrateChat new file mode 100644 index 0000000000..df381825c6 --- /dev/null +++ b/data/core.telegram.org/method/messages.migrateChat @@ -0,0 +1,190 @@ + + + + + messages.migrateChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.migrateChat

+ +

Turn a legacy group into a supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.migrateChat#a2875319 chat_id:long = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongLegacy group to migrate
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
403CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.readDiscussion b/data/core.telegram.org/method/messages.readDiscussion new file mode 100644 index 0000000000..48f929fe42 --- /dev/null +++ b/data/core.telegram.org/method/messages.readDiscussion @@ -0,0 +1,180 @@ + + + + + messages.readDiscussion + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readDiscussion

+ +

Mark a thread as read

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerGroup ID
msg_idintID of message that started the thread
read_max_idintID up to which thread messages were read
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.readEncryptedHistory b/data/core.telegram.org/method/messages.readEncryptedHistory new file mode 100644 index 0000000000..72e640a26f --- /dev/null +++ b/data/core.telegram.org/method/messages.readEncryptedHistory @@ -0,0 +1,172 @@ + + + + + messages.readEncryptedHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readEncryptedHistory

+ +

Marks message history within a secret chat as read.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
max_dateintMaximum date value for received messages in history
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_WAIT_FAILEDA waiting call returned an error.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.readFeaturedStickers b/data/core.telegram.org/method/messages.readFeaturedStickers new file mode 100644 index 0000000000..ad338d9a7e --- /dev/null +++ b/data/core.telegram.org/method/messages.readFeaturedStickers @@ -0,0 +1,150 @@ + + + + + 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.readHistory b/data/core.telegram.org/method/messages.readHistory new file mode 100644 index 0000000000..06802b10b5 --- /dev/null +++ b/data/core.telegram.org/method/messages.readHistory @@ -0,0 +1,186 @@ + + + + + messages.readHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readHistory

+ +

Marks message history as read.

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerTarget user or group
max_idintIf a positive value is passed, only messages with identifiers less or equal than the given one will be read
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.readMentions b/data/core.telegram.org/method/messages.readMentions new file mode 100644 index 0000000000..68df81baa7 --- /dev/null +++ b/data/core.telegram.org/method/messages.readMentions @@ -0,0 +1,181 @@ + + + + + messages.readMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readMentions

+ +

Mark mentions as read

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+---functions---
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerDialog
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.readMessageContents b/data/core.telegram.org/method/messages.readMessageContents new file mode 100644 index 0000000000..e3951d5ec9 --- /dev/null +++ b/data/core.telegram.org/method/messages.readMessageContents @@ -0,0 +1,149 @@ + + + + + messages.readMessageContents + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readMessageContents

+ +

Notifies the sender about the recipient having listened a voice message or watched a video.

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<int>Message ID list
+

Result

+

Returns a list of listened\watched messages as Vector<int>.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.receivedMessages b/data/core.telegram.org/method/messages.receivedMessages new file mode 100644 index 0000000000..84e5989c75 --- /dev/null +++ b/data/core.telegram.org/method/messages.receivedMessages @@ -0,0 +1,148 @@ + + + + + messages.receivedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.receivedMessages

+ +

Confirms receipt of messages by a client, cancels PUSH-notification sending.

+

+ +
+
---functions---
+messages.receivedMessages#5a954c0 max_id:int = Vector<ReceivedNotifyMessage>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
max_idintMaximum message ID available in a client.
+

Result

+

The method returns the list of message IDs, for which PUSH-notifications were cancelled.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.receivedQueue b/data/core.telegram.org/method/messages.receivedQueue new file mode 100644 index 0000000000..39debae4f5 --- /dev/null +++ b/data/core.telegram.org/method/messages.receivedQueue @@ -0,0 +1,170 @@ + + + + + messages.receivedQueue + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.receivedQueue

+ +

Confirms receipt of messages in a secret chat by client, cancels push notifications.

+

+ +
+
---functions---
+messages.receivedQueue#55a5bb66 max_qts:int = Vector<long>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
max_qtsintMaximum qts value available at the client
+

Result

+

Method returns a list of random_ids of messages for which push notifications were cancelled in Vector<long>.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MAX_QTS_INVALIDThe specified max_qts is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.reorderPinnedDialogs b/data/core.telegram.org/method/messages.reorderPinnedDialogs new file mode 100644 index 0000000000..0bb8c438db --- /dev/null +++ b/data/core.telegram.org/method/messages.reorderPinnedDialogs @@ -0,0 +1,185 @@ + + + + + messages.reorderPinnedDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reorderPinnedDialogs

+ +

Reorder pinned dialogs

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueIf set, dialogs pinned server-side but not present in the order field will be unpinned.
folder_idintPeer folder ID, for more info click here
orderVector<InputDialogPeer>New dialog order
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.reorderStickerSets b/data/core.telegram.org/method/messages.reorderStickerSets new file mode 100644 index 0000000000..58d00ac522 --- /dev/null +++ b/data/core.telegram.org/method/messages.reorderStickerSets @@ -0,0 +1,160 @@ + + + + + messages.reorderStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reorderStickerSets

+ +

Reorder installed stickersets

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueReorder mask stickersets
orderVector<long>New stickerset order by stickerset IDs
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.report b/data/core.telegram.org/method/messages.report new file mode 100644 index 0000000000..b703f80c9c --- /dev/null +++ b/data/core.telegram.org/method/messages.report @@ -0,0 +1,187 @@ + + + + + messages.report + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.report

+ +

Report a message in a chat for violation of telegram's Terms of Service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>IDs of messages to report
reasonReportReasonWhy are these messages being reported
messagestringComment for report moderation
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.reportEncryptedSpam b/data/core.telegram.org/method/messages.reportEncryptedSpam new file mode 100644 index 0000000000..e9f3d6606a --- /dev/null +++ b/data/core.telegram.org/method/messages.reportEncryptedSpam @@ -0,0 +1,167 @@ + + + + + messages.reportEncryptedSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reportEncryptedSpam

+ +

Report a secret chat for spam

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatThe secret chat to report
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.reportSpam b/data/core.telegram.org/method/messages.reportSpam new file mode 100644 index 0000000000..851db85844 --- /dev/null +++ b/data/core.telegram.org/method/messages.reportSpam @@ -0,0 +1,180 @@ + + + + + messages.reportSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reportSpam

+ +

Report a new incoming chat for spam, if the peer settings of the chat allow us to do that

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reportSpam#cf1592db peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer to report
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

peerSettings

+

Peer settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.requestEncryption b/data/core.telegram.org/method/messages.requestEncryption new file mode 100644 index 0000000000..aa9cc13fa8 --- /dev/null +++ b/data/core.telegram.org/method/messages.requestEncryption @@ -0,0 +1,185 @@ + + + + + messages.requestEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.requestEncryption

+ +

Sends a request to start a secret chat to the user.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+---functions---
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
random_idintUnique client request ID required to prevent resending. This also doubles as the chat ID.
g_abytesA = g ^ a mod p, see Wikipedia
+

Result

+

EncryptedChat

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400DH_G_A_INVALIDg_a invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.requestUrlAuth b/data/core.telegram.org/method/messages.requestUrlAuth new file mode 100644 index 0000000000..66f2c025aa --- /dev/null +++ b/data/core.telegram.org/method/messages.requestUrlAuth @@ -0,0 +1,174 @@ + + + + + messages.requestUrlAuth + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.requestUrlAuth

+ +

Get more info about a Seamless Telegram Login authorization request, for more info click here »

+

+ +
+
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
+urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
+urlAuthResultDefault#a9d6db1f = UrlAuthResult;
+---functions---
+messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerflags.1?InputPeerPeer where the message is located
msg_idflags.1?intThe message
button_idflags.1?intThe ID of the button with the authorization request
urlflags.2?stringURL used for link URL authorization, click here for more info »
+

Result

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.saveDraft b/data/core.telegram.org/method/messages.saveDraft new file mode 100644 index 0000000000..960d382ff7 --- /dev/null +++ b/data/core.telegram.org/method/messages.saveDraft @@ -0,0 +1,202 @@ + + + + + messages.saveDraft + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.saveDraft

+ +

Save a message draft associated to a chat.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable generation of the webpage preview
reply_to_msg_idflags.0?intMessage ID the message should reply to
peerInputPeerDestination of the message that should be sent
messagestringThe draft
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.saveGif b/data/core.telegram.org/method/messages.saveGif new file mode 100644 index 0000000000..45ed9f61ec --- /dev/null +++ b/data/core.telegram.org/method/messages.saveGif @@ -0,0 +1,172 @@ + + + + + messages.saveGif + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.saveGif

+ +

Add GIF to saved gifs list

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputDocumentGIF to save
unsaveBoolWhether to remove GIF from saved gifs list
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400GIF_ID_INVALIDThe provided GIF ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.saveRecentSticker b/data/core.telegram.org/method/messages.saveRecentSticker new file mode 100644 index 0000000000..af8b20cae8 --- /dev/null +++ b/data/core.telegram.org/method/messages.saveRecentSticker @@ -0,0 +1,182 @@ + + + + + messages.saveRecentSticker + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.saveRecentSticker

+ +

Add/remove sticker from recent stickers list

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueWhether to add/remove stickers recently attached to photo or video files
idInputDocumentSticker
unsaveBoolWhether to save or unsave the sticker
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.search b/data/core.telegram.org/method/messages.search new file mode 100644 index 0000000000..42836278a1 --- /dev/null +++ b/data/core.telegram.org/method/messages.search @@ -0,0 +1,291 @@ + + + + + messages.search + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.search

+ +

Gets back found messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerUser or chat, histories with which are searched, or (inputPeerEmpty) constructor for global search
qstringText search request
from_idflags.0?InputPeerOnly return messages sent by the specified user ID
top_msg_idflags.1?intThread ID
filterMessagesFilterFilter to return only specified message types
min_dateintIf a positive value was transferred, only messages with a sending date bigger than the transferred one will be returned
max_dateintIf a positive value was transferred, only messages with a sending date smaller than the transferred one will be returned
offset_idintOnly return messages starting from the specified message ID
add_offsetintAdditional offset
limitintNumber of results to return
max_idintMaximum message ID to return
min_idintMinimum message ID to return
hashlongHash
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400FROM_PEER_INVALIDThe specified from_id is invalid.
400INPUT_FILTER_INVALIDThe specified filter is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PEER_ID_NOT_SUPPORTEDThe provided peer ID is not supported.
400SEARCH_QUERY_EMPTYThe search query is empty.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

inputPeerEmpty

+

An empty constructor, no user or chat is defined.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.searchGifs b/data/core.telegram.org/method/messages.searchGifs new file mode 100644 index 0000000000..161693bb23 --- /dev/null +++ b/data/core.telegram.org/method/messages.searchGifs @@ -0,0 +1,177 @@ + + + + + messages.searchGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchGifs

+ +

Search for GIFs

+

+ +
+
 Method schema is available as of layer 114. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
qstringText query
offsetintOffset for pagination »
+

Result

+

messages.FoundGifs

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.searchGlobal b/data/core.telegram.org/method/messages.searchGlobal new file mode 100644 index 0000000000..e966ef85b3 --- /dev/null +++ b/data/core.telegram.org/method/messages.searchGlobal @@ -0,0 +1,226 @@ + + + + + messages.searchGlobal + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchGlobal

+ +

Search for messages and peers globally

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
qstringQuery
filterMessagesFilterGlobal search filter
min_dateintIf a positive value was specified, the method will return only messages with date bigger than min_date
max_dateintIf a positive value was transferred, the method will return only messages with date smaller than max_date
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintOffsets for pagination, for more info click here
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

messages.messagesSlice

+

Incomplete list of messages and auxiliary data.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.searchStickerSets b/data/core.telegram.org/method/messages.searchStickerSets new file mode 100644 index 0000000000..2fadab6b4a --- /dev/null +++ b/data/core.telegram.org/method/messages.searchStickerSets @@ -0,0 +1,168 @@ + + + + + messages.searchStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchStickerSets

+ +

Search for stickersets

+

+ +
+
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
+messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
+---functions---
+messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_featuredflags.0?trueExclude featured stickersets from results
qstringQuery string
hashlongHash for pagination, for more info click here
+

Result

+

messages.FoundStickerSets

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendBroadcast b/data/core.telegram.org/method/messages.sendBroadcast new file mode 100644 index 0000000000..5244109ad0 --- /dev/null +++ b/data/core.telegram.org/method/messages.sendBroadcast @@ -0,0 +1,145 @@ + + + + + messages.sendBroadcast + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendBroadcast

+ +

Sends multiple messages to contacts.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
contactsVector<InputUser>List of user ID to whom a message will be sent
messagestringMessage text
mediaInputMediaMessage media-contents
+

Result

+

messages.StatedMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendEncrypted b/data/core.telegram.org/method/messages.sendEncrypted new file mode 100644 index 0000000000..b8ff1a69dc --- /dev/null +++ b/data/core.telegram.org/method/messages.sendEncrypted @@ -0,0 +1,210 @@ + + + + + messages.sendEncrypted + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendEncrypted

+ +

Sends a text message to a secret chat.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+---functions---
+messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueSend encrypted message without a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID, necessary to avoid message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key that was created during chat initialization
+

Result

+

messages.SentEncryptedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_IS_BLOCKEDYou were blocked by this user.
+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendEncryptedFile b/data/core.telegram.org/method/messages.sendEncryptedFile new file mode 100644 index 0000000000..c5d252bc7d --- /dev/null +++ b/data/core.telegram.org/method/messages.sendEncryptedFile @@ -0,0 +1,215 @@ + + + + + messages.sendEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendEncryptedFile

+ +

Sends a message with a file attachment to a secret chat

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+---functions---
+messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueWhether to send the file without triggering a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID necessary to prevent message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
fileInputEncryptedFileFile attachment for the secret chat
+

Result

+

messages.SentEncryptedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400DATA_TOO_LONGData too long.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400FILE_EMTPYAn empty file was provided.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MSG_WAIT_FAILEDA waiting call returned an error.
+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendEncryptedService b/data/core.telegram.org/method/messages.sendEncryptedService new file mode 100644 index 0000000000..bc40808518 --- /dev/null +++ b/data/core.telegram.org/method/messages.sendEncryptedService @@ -0,0 +1,205 @@ + + + + + messages.sendEncryptedService + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendEncryptedService

+ +

Sends a service message to a secret chat.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+---functions---
+messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID required to prevent message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
+

Result

+

messages.SentEncryptedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_DELETEDYou can't send this secret message because the other participant deleted their account.
403USER_IS_BLOCKEDYou were blocked by this user.
+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendInlineBotResult b/data/core.telegram.org/method/messages.sendInlineBotResult new file mode 100644 index 0000000000..ddd4e5d7f4 --- /dev/null +++ b/data/core.telegram.org/method/messages.sendInlineBotResult @@ -0,0 +1,344 @@ + + + + + messages.sendInlineBotResult + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendInlineBotResult

+ +

Send a result obtained using messages.getInlineBotResults.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the message silently (no notification will be triggered on the other client)
backgroundflags.6?trueWhether to send the message in background
clear_draftflags.7?trueWhether to clear the draft
hide_viaflags.11?trueWhether to hide the via @botname in the resulting message (only for bot usernames encountered in the config)
peerInputPeerDestination
reply_to_msg_idflags.0?intID of the message this message should reply to
random_idlongRandom ID to avoid resending the same query
query_idlongQuery ID from messages.getInlineBotResults
idstringResult ID from messages.getInlineBotResults
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_INLINE_FORBIDDENYou can't send inline messages in this group.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INLINE_RESULT_EXPIREDThe inline query expired.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400QUERY_ID_EMPTYThe query ID is empty.
400RESULT_ID_EMPTYResult ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
+

Related pages

+

Message drafts

+

How to handle message drafts

+

config

+

Current configuration

+

messages.getInlineBotResults

+

Query an inline bot

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendMedia b/data/core.telegram.org/method/messages.sendMedia new file mode 100644 index 0000000000..ca4043c09c --- /dev/null +++ b/data/core.telegram.org/method/messages.sendMedia @@ -0,0 +1,518 @@ + + + + + messages.sendMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendMedia

+ +

Send a media

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueSend message silently (no notification should be triggered)
backgroundflags.6?trueSend message in background
clear_draftflags.7?trueClear the draft
peerInputPeerDestination
reply_to_msg_idflags.0?intMessage ID to which this message should reply to
mediaInputMediaAttached media
messagestringCaption
random_idlongRandom ID to avoid resending the same message
reply_markupflags.2?ReplyMarkupReply markup for bot keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_PAYMENTS_DISABLEDPlease enable bot payments in botfather before calling this method.
400BOT_POLLS_DISABLED 
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CURRENCY_TOTAL_AMOUNT_INVALIDThe total amount of all prices is invalid.
400EMOTICON_INVALIDThe specified emoji is invalid.
400EXTERNAL_URL_INVALIDExternal URL invalid.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_LENGTH_INVALIDThe length of a file part is invalid.
400FILE_REFERENCE_EMPTYAn empty file reference was specified.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference.
400GAME_BOT_INVALIDBots can't send another bot's game.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PAYMENT_PROVIDER_INVALIDThe specified payment provider is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400POLL_ANSWERS_INVALIDInvalid poll answers were provided.
400POLL_ANSWER_INVALIDOne of the poll answers is not acceptable.
400POLL_OPTION_DUPLICATEDuplicate poll options provided.
400POLL_OPTION_INVALIDInvalid poll option provided.
400POLL_QUESTION_INVALIDOne of the poll questions is not acceptable.
400QUIZ_CORRECT_ANSWERS_EMPTYNo correct quiz answer was specified.
400QUIZ_CORRECT_ANSWERS_TOO_MUCHYou specified too many correct answers in a quiz, quizes can only have one right answer!
400QUIZ_CORRECT_ANSWER_INVALIDAn invalid value was provided to the correct_answers field.
400QUIZ_MULTIPLE_INVALIDQuizes can't have the multiple_choice flag set!
400REPLY_MARKUP_BUY_EMPTYReply markup for buy button empty.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400TTL_MEDIA_INVALIDInvalid media Time To Live was provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400VIDEO_CONTENT_TYPE_INVALIDThe video's content type is invalid.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendMessage b/data/core.telegram.org/method/messages.sendMessage new file mode 100644 index 0000000000..04af62058d --- /dev/null +++ b/data/core.telegram.org/method/messages.sendMessage @@ -0,0 +1,398 @@ + + + + + messages.sendMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendMessage

+ +

Sends a message to a chat

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueSet this flag to disable generation of the webpage preview
silentflags.5?trueSend this message silently (no notifications for the receivers)
backgroundflags.6?trueSend this message as background message
clear_draftflags.7?trueClear the draft field
peerInputPeerThe destination where the message will be sent
reply_to_msg_idflags.0?intThe message ID to which this message will reply to
messagestringThe message
random_idlongUnique client message ID required to prevent message resending
reply_markupflags.2?ReplyMarkupReply markup for sending bot buttons
entitiesflags.3?Vector<MessageEntity>Message entities for sending styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400BOT_DOMAIN_INVALIDBot domain invalid.
400BOT_INVALIDThis is not a valid bot.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400ENTITIES_TOO_LONGYou provided too many styled message entities.
400ENTITY_MENTION_USER_INVALIDYou mentioned an invalid user.
400FROM_MESSAGE_BOT_DISABLEDBots can't use fromMessage min constructors.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400MSG_ID_INVALIDProvided reply_to_msg_id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400POLL_OPTION_INVALIDInvalid poll option provided.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400REPLY_MARKUP_TOO_LONGThe specified reply_markup is too long.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_STATUS_PRIVATECan't schedule until user is online, if the user's last seen timestamp is hidden by their privacy settings.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendMultiMedia b/data/core.telegram.org/method/messages.sendMultiMedia new file mode 100644 index 0000000000..cfa150bdf1 --- /dev/null +++ b/data/core.telegram.org/method/messages.sendMultiMedia @@ -0,0 +1,263 @@ + + + + + messages.sendMultiMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendMultiMedia

+ +

Send an album or grouped media

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the album silently (no notification triggered)
backgroundflags.6?trueSend in background?
clear_draftflags.7?trueWhether to clear drafts
peerInputPeerThe destination chat
reply_to_msg_idflags.0?intThe message to reply to
multi_mediaVector<InputSingleMedia>The medias to send
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MULTI_MEDIA_TOO_LONGToo many media files for album.
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_EMPTYRandom ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: wait X seconds before sending another message to this chat.
+

Bots can use this method

+

Related pages

+

Message drafts

+

How to handle message drafts

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendReaction b/data/core.telegram.org/method/messages.sendReaction new file mode 100644 index 0000000000..b02e1db557 --- /dev/null +++ b/data/core.telegram.org/method/messages.sendReaction @@ -0,0 +1,185 @@ + + + + + messages.sendReaction + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendReaction

+ +

Send reaction to message

+

+ +
+
 Method schema is available as of layer 136. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerPeer
msg_idintMessage ID to react to
reactionflags.0?stringReaction (a UTF8 emoji)
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400REACTION_EMPTYEmpty reaction provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendScheduledMessages b/data/core.telegram.org/method/messages.sendScheduledMessages new file mode 100644 index 0000000000..92715f213b --- /dev/null +++ b/data/core.telegram.org/method/messages.sendScheduledMessages @@ -0,0 +1,182 @@ + + + + + messages.sendScheduledMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendScheduledMessages

+ +

Send scheduled messages right away

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendScreenshotNotification b/data/core.telegram.org/method/messages.sendScreenshotNotification new file mode 100644 index 0000000000..c5424b40a3 --- /dev/null +++ b/data/core.telegram.org/method/messages.sendScreenshotNotification @@ -0,0 +1,187 @@ + + + + + messages.sendScreenshotNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendScreenshotNotification

+ +

Notify the other user in a private chat that a screenshot of the chat was taken

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerOther user
reply_to_msg_idintID of message that was screenshotted, can be 0
random_idlongRandom ID to avoid message resending
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
400YOU_BLOCKED_USERYou blocked this user.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendVote b/data/core.telegram.org/method/messages.sendVote new file mode 100644 index 0000000000..927ebfc9fc --- /dev/null +++ b/data/core.telegram.org/method/messages.sendVote @@ -0,0 +1,220 @@ + + + + + messages.sendVote + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendVote

+ +

Vote in a poll

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the poll was sent
msg_idintThe message ID of the poll
optionsVector<bytes>The options that were chosen
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_POLL_CLOSEDPoll closed.
400OPTIONS_TOO_MUCHToo many options provided.
400OPTION_INVALIDInvalid option selected.
400PEER_ID_INVALIDThe provided peer id is invalid.
400REVOTE_NOT_ALLOWEDYou cannot change your vote.
+

Related pages

+

poll

+

Poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setBotCallbackAnswer b/data/core.telegram.org/method/messages.setBotCallbackAnswer new file mode 100644 index 0000000000..befb3bb4a6 --- /dev/null +++ b/data/core.telegram.org/method/messages.setBotCallbackAnswer @@ -0,0 +1,203 @@ + + + + + messages.setBotCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setBotCallbackAnswer

+ +

Set the callback answer to a user button press (bots only)

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
alertflags.1?trueWhether to show the message as a popup instead of a toast notification
query_idlongQuery ID
messageflags.0?stringPopup to show
urlflags.2?stringURL to open
cache_timeintCache validity
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_TOO_LONGThe provided message is too long.
400QUERY_ID_INVALIDThe query ID is invalid.
400URL_INVALIDInvalid URL provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setBotPrecheckoutResults b/data/core.telegram.org/method/messages.setBotPrecheckoutResults new file mode 100644 index 0000000000..408b373dc0 --- /dev/null +++ b/data/core.telegram.org/method/messages.setBotPrecheckoutResults @@ -0,0 +1,188 @@ + + + + + messages.setBotPrecheckoutResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setBotPrecheckoutResults

+ +

Once the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
+Use this method to respond to such pre-checkout queries.
+Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.1?trueSet this flag if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order, otherwise do not set it, and set the error field, instead
query_idlongUnique identifier for the query to be answered
errorflags.0?stringRequired if the success isn't set. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400ERROR_TEXT_EMPTYThe provided error message is empty.
+

Bots can use this method

+

Related pages

+

updateBotPrecheckoutQuery

+

This object contains information about an incoming pre-checkout query.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setBotShippingResults b/data/core.telegram.org/method/messages.setBotShippingResults new file mode 100644 index 0000000000..6b60e9d524 --- /dev/null +++ b/data/core.telegram.org/method/messages.setBotShippingResults @@ -0,0 +1,186 @@ + + + + + messages.setBotShippingResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setBotShippingResults

+ +

If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongUnique identifier for the query to be answered
errorflags.0?stringError message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
shipping_optionsflags.1?Vector<ShippingOption>A vector of available shipping options.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400QUERY_ID_INVALIDThe query ID is invalid.
+

Bots can use this method

+

Related pages

+

updateBotShippingQuery

+

This object contains information about an incoming shipping query.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setChatTheme b/data/core.telegram.org/method/messages.setChatTheme new file mode 100644 index 0000000000..f581091ac8 --- /dev/null +++ b/data/core.telegram.org/method/messages.setChatTheme @@ -0,0 +1,185 @@ + + + + + messages.setChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setChatTheme

+ +

Change the chat theme of a certain chat

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPrivate chat where to change theme
emoticonstringEmoji, identifying a specific chat theme; a list of chat themes can be fetched using account.getChatThemes
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMOJI_INVALIDThe specified theme emoji is valid.
400EMOJI_NOT_MODIFIEDThe theme wasn't changed.
+

Related pages

+

account.getChatThemes

+

Get all available chat themes

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setEncryptedTyping b/data/core.telegram.org/method/messages.setEncryptedTyping new file mode 100644 index 0000000000..f1aa28dd9d --- /dev/null +++ b/data/core.telegram.org/method/messages.setEncryptedTyping @@ -0,0 +1,177 @@ + + + + + messages.setEncryptedTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setEncryptedTyping

+ +

Send typing event by the current user to a secret chat.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
typingBoolTyping.
Possible values:
(boolTrue), if the user started typing and more than 5 seconds have passed since the last request
(boolFalse), if the user stopped typing
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

boolFalse

+

Constructor may be interpreted as a booleanfalse value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setGameScore b/data/core.telegram.org/method/messages.setGameScore new file mode 100644 index 0000000000..7c7540ddc6 --- /dev/null +++ b/data/core.telegram.org/method/messages.setGameScore @@ -0,0 +1,218 @@ + + + + + messages.setGameScore + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setGameScore

+ +

Use this method to set the score of the specified user in a game sent as a normal message (bots only).

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
peerInputPeerUnique identifier of target chat
idintIdentifier of the sent message
user_idInputUserUser identifier
scoreintNew score
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_SCORE_NOT_MODIFIEDThe score wasn't modified.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setHistoryTTL b/data/core.telegram.org/method/messages.setHistoryTTL new file mode 100644 index 0000000000..0edfce6a9e --- /dev/null +++ b/data/core.telegram.org/method/messages.setHistoryTTL @@ -0,0 +1,182 @@ + + + + + messages.setHistoryTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setHistoryTTL

+ +

Set maximum Time-To-Live of all messages in the specified chat

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
periodintAutomatically delete all messages sent in the chat after this many seconds
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400TTL_PERIOD_INVALIDThe specified TTL period is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setInlineBotResults b/data/core.telegram.org/method/messages.setInlineBotResults new file mode 100644 index 0000000000..7de8b5d0c2 --- /dev/null +++ b/data/core.telegram.org/method/messages.setInlineBotResults @@ -0,0 +1,358 @@ + + + + + messages.setInlineBotResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setInlineBotResults

+ +

Answer an inline query, for bots only

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueSet this flag if the results are composed of media files
privateflags.1?trueSet this flag if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
query_idlongUnique identifier for the answered query
resultsVector<InputBotInlineResult>Vector of results for the inline query
cache_timeintThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
next_offsetflags.2?stringPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don‘t support pagination. Offset length can’t exceed 64 bytes.
switch_pmflags.3?InlineBotSwitchPMIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with a certain parameter.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ARTICLE_TITLE_EMPTYThe title of the article is empty.
400AUDIO_CONTENT_URL_EMPTYThe remote URL specified in the content field is empty.
400AUDIO_TITLE_EMPTYAn empty audio title was provided.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400DOCUMENT_INVALIDThe specified document is invalid.
400FILE_CONTENT_TYPE_INVALIDFile content-type is invalid.
400FILE_TITLE_EMPTYAn empty file title was specified.
400GIF_CONTENT_TYPE_INVALIDGIF content-type invalid.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400NEXT_OFFSET_INVALIDThe specified offset is longer than 64 bytes.
400PHOTO_CONTENT_TYPE_INVALIDPhoto mime-type invalid.
400PHOTO_CONTENT_URL_EMPTYPhoto URL invalid.
400PHOTO_INVALIDPhoto invalid.
400PHOTO_THUMB_URL_EMPTYPhoto thumbnail URL is empty.
400QUERY_ID_INVALIDThe query ID is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400RESULTS_TOO_MUCHToo many results were provided.
400RESULT_ID_DUPLICATEYou provided a duplicate result ID.
400RESULT_TYPE_INVALIDResult type invalid.
400SEND_MESSAGE_MEDIA_INVALIDInvalid media provided.
400SEND_MESSAGE_TYPE_INVALIDThe message type is invalid.
400START_PARAM_INVALIDStart parameter invalid.
400STICKER_DOCUMENT_INVALIDThe specified sticker document is invalid.
403USER_BOT_INVALIDThis method can only be called by a bot.
400VIDEO_TITLE_EMPTYThe specified video title is empty.
400WEBDOCUMENT_INVALIDInvalid webdocument URL provided.
400WEBDOCUMENT_MIME_INVALIDInvalid webdocument mime type provided.
400WEBDOCUMENT_SIZE_TOO_BIGWebdocument is too big!
400WEBDOCUMENT_URL_INVALIDThe specified webdocument URL is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setInlineGameScore b/data/core.telegram.org/method/messages.setInlineGameScore new file mode 100644 index 0000000000..e2c2cd24e2 --- /dev/null +++ b/data/core.telegram.org/method/messages.setInlineGameScore @@ -0,0 +1,198 @@ + + + + + messages.setInlineGameScore + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setInlineGameScore

+ +

Use this method to set the score of the specified user in a game sent as an inline message (bots only).

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
idInputBotInlineMessageIDID of the inline message
user_idInputUserUser identifier
scoreintNew score
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setTyping b/data/core.telegram.org/method/messages.setTyping new file mode 100644 index 0000000000..f7f748b7f0 --- /dev/null +++ b/data/core.telegram.org/method/messages.setTyping @@ -0,0 +1,240 @@ + + + + + messages.setTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setTyping

+ +

Sends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerTarget user or group
top_msg_idflags.0?intThread ID
actionSendMessageActionType of action
Parameter added in Layer 17.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
+

Bots can use this method

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+

SendMessageAction

+

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.startBot b/data/core.telegram.org/method/messages.startBot new file mode 100644 index 0000000000..649ccfb07b --- /dev/null +++ b/data/core.telegram.org/method/messages.startBot @@ -0,0 +1,224 @@ + + + + + messages.startBot + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.startBot

+ +

Start a conversation with a bot using a deep linking parameter

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
botInputUserThe bot
peerInputPeerThe chat where to start the bot, can be the bot's private chat or a group
random_idlongRandom ID to avoid resending the same message
start_paramstringDeep linking parameter
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_INVALIDThis is not a valid bot.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400START_PARAM_EMPTYThe start parameter is empty.
400START_PARAM_INVALIDStart parameter invalid.
400START_PARAM_TOO_LONGStart parameter is too long.
+

Related pages

+

Bots: An introduction for developers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.toggleDialogPin b/data/core.telegram.org/method/messages.toggleDialogPin new file mode 100644 index 0000000000..9afa039ef5 --- /dev/null +++ b/data/core.telegram.org/method/messages.toggleDialogPin @@ -0,0 +1,187 @@ + + + + + messages.toggleDialogPin + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.toggleDialogPin

+ +

Pin/unpin a dialog

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether to pin or unpin the dialog
peerInputDialogPeerThe dialog to pin
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.toggleStickerSets b/data/core.telegram.org/method/messages.toggleStickerSets new file mode 100644 index 0000000000..b5ab641ee3 --- /dev/null +++ b/data/core.telegram.org/method/messages.toggleStickerSets @@ -0,0 +1,170 @@ + + + + + messages.toggleStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.toggleStickerSets

+ +

Apply changes to multiple stickersets

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
uninstallflags.0?trueUninstall the specified stickersets
archiveflags.1?trueArchive the specified stickersets
unarchiveflags.2?trueUnarchive the specified stickersets
stickersetsVector<InputStickerSet>Stickersets to act upon
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.uninstallStickerSet b/data/core.telegram.org/method/messages.uninstallStickerSet new file mode 100644 index 0000000000..915b78790f --- /dev/null +++ b/data/core.telegram.org/method/messages.uninstallStickerSet @@ -0,0 +1,167 @@ + + + + + messages.uninstallStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uninstallStickerSet

+ +

Uninstall a stickerset

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetThe stickerset to uninstall
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.unpinAllMessages b/data/core.telegram.org/method/messages.unpinAllMessages new file mode 100644 index 0000000000..2846da9dc4 --- /dev/null +++ b/data/core.telegram.org/method/messages.unpinAllMessages @@ -0,0 +1,153 @@ + + + + + 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/messages.updateDialogFilter b/data/core.telegram.org/method/messages.updateDialogFilter new file mode 100644 index 0000000000..61f26cef9c --- /dev/null +++ b/data/core.telegram.org/method/messages.updateDialogFilter @@ -0,0 +1,190 @@ + + + + + messages.updateDialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.updateDialogFilter

+ +

Update folder

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FILTER_ID_INVALIDThe specified filter ID is invalid.
400FILTER_INCLUDE_EMPTYThe include_peers vector of the filter is empty.
400FILTER_TITLE_EMPTYThe title field of the filter is empty.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.updateDialogFiltersOrder b/data/core.telegram.org/method/messages.updateDialogFiltersOrder new file mode 100644 index 0000000000..53bb20c5f9 --- /dev/null +++ b/data/core.telegram.org/method/messages.updateDialogFiltersOrder @@ -0,0 +1,153 @@ + + + + + messages.updateDialogFiltersOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.updateDialogFiltersOrder

+ +

Reorder folders

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
orderVector<int>New folder order
+

Result

+

Bool

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.updatePinnedMessage b/data/core.telegram.org/method/messages.updatePinnedMessage new file mode 100644 index 0000000000..cc90271f29 --- /dev/null +++ b/data/core.telegram.org/method/messages.updatePinnedMessage @@ -0,0 +1,233 @@ + + + + + messages.updatePinnedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.updatePinnedMessage

+ +

Pin a message

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?truePin the message silently, without triggering a notification
unpinflags.1?trueWhether the message should unpinned or pinned
pm_onesideflags.2?trueWhether the message should only be pinned on the local side of a one-to-one chat
peerInputPeerThe peer where to pin the message
idintThe message to pin or unpin
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_ONESIDE_NOT_AVAILBots can't pin messages in PM just for themselves.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PIN_RESTRICTEDYou can't pin messages.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.uploadEncryptedFile b/data/core.telegram.org/method/messages.uploadEncryptedFile new file mode 100644 index 0000000000..7e41e40df9 --- /dev/null +++ b/data/core.telegram.org/method/messages.uploadEncryptedFile @@ -0,0 +1,155 @@ + + + + + messages.uploadEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uploadEncryptedFile

+ +

Upload encrypted file and associate it to a secret chat

+

+ +
+
encryptedFileEmpty#c21f497e = EncryptedFile;
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+---functions---
+messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatThe secret chat to associate the file to
fileInputEncryptedFileThe file
+

Result

+

EncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.uploadImportedMedia b/data/core.telegram.org/method/messages.uploadImportedMedia new file mode 100644 index 0000000000..4281220576 --- /dev/null +++ b/data/core.telegram.org/method/messages.uploadImportedMedia @@ -0,0 +1,181 @@ + + + + + messages.uploadImportedMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uploadImportedMedia

+ +

Upload a media file associated with an imported chat, click here for more info ».

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+---functions---
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe Telegram chat where the media will be imported
import_idlongIdentifier of a history import session, returned by messages.initHistoryImport
file_namestringFile name
mediaInputMediaMedia metadata
+

Result

+

MessageMedia

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

messages.initHistoryImport

+

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.uploadMedia b/data/core.telegram.org/method/messages.uploadMedia new file mode 100644 index 0000000000..52cce5e019 --- /dev/null +++ b/data/core.telegram.org/method/messages.uploadMedia @@ -0,0 +1,264 @@ + + + + + messages.uploadMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uploadMedia

+ +

Upload a file and associate it to a chat (without actually sending it to the chat)

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+---functions---
+messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat, can be an inputPeerEmpty for bots
mediaInputMediaFile uploaded in chunks as described in files »
+

Result

+

MessageMedia

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
+

Bots can use this method

+

Related pages

+

inputPeerEmpty

+

An empty constructor, no user or chat is defined.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/payments.clearSavedInfo b/data/core.telegram.org/method/payments.clearSavedInfo new file mode 100644 index 0000000000..efb91efb38 --- /dev/null +++ b/data/core.telegram.org/method/payments.clearSavedInfo @@ -0,0 +1,160 @@ + + + + + payments.clearSavedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.clearSavedInfo

+ +

Clear saved payment information

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
credentialsflags.0?trueRemove saved payment credentials
infoflags.1?trueClear the last order settings saved by the user
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/payments.getBankCardData b/data/core.telegram.org/method/payments.getBankCardData new file mode 100644 index 0000000000..258081dcb9 --- /dev/null +++ b/data/core.telegram.org/method/payments.getBankCardData @@ -0,0 +1,166 @@ + + + + + payments.getBankCardData + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getBankCardData

+ +

Get info about a credit card

+

+ +
+
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
+---functions---
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
numberstringCredit card number
+

Result

+

payments.BankCardData

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400BANK_CARD_NUMBER_INVALIDThe specified card number is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/payments.getPaymentForm b/data/core.telegram.org/method/payments.getPaymentForm new file mode 100644 index 0000000000..6eea9d4136 --- /dev/null +++ b/data/core.telegram.org/method/payments.getPaymentForm @@ -0,0 +1,181 @@ + + + + + payments.getPaymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getPaymentForm

+ +

Get a payment form

+

+ +
+
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+---functions---
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of payment form
theme_paramsflags.0?DataJSONA JSON object with the following keys, containing color theme information (integers, RGB24) to pass to the payment provider, to apply in eventual verification pages:
bg_color - Background color
text_color - Text color
hint_color - Hint text color
link_color - Link color
button_color - Button color
button_text_color - Button text color
+

Result

+

payments.PaymentForm

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/payments.getPaymentReceipt b/data/core.telegram.org/method/payments.getPaymentReceipt new file mode 100644 index 0000000000..254a4bea07 --- /dev/null +++ b/data/core.telegram.org/method/payments.getPaymentReceipt @@ -0,0 +1,171 @@ + + + + + payments.getPaymentReceipt + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getPaymentReceipt

+ +

Get payment receipt

+

+ +
+
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+---functions---
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer where the payment receipt was sent
msg_idintMessage ID of receipt
+

Result

+

payments.PaymentReceipt

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/payments.getSavedInfo b/data/core.telegram.org/method/payments.getSavedInfo new file mode 100644 index 0000000000..53a1cbbcc1 --- /dev/null +++ b/data/core.telegram.org/method/payments.getSavedInfo @@ -0,0 +1,134 @@ + + + + + payments.getSavedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getSavedInfo

+ +

Get saved payment information

+

+ +
+
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
+---functions---
+payments.getSavedInfo#227d824b = payments.SavedInfo;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

payments.SavedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/payments.sendPaymentForm b/data/core.telegram.org/method/payments.sendPaymentForm new file mode 100644 index 0000000000..775d51218b --- /dev/null +++ b/data/core.telegram.org/method/payments.sendPaymentForm @@ -0,0 +1,206 @@ + + + + + payments.sendPaymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.sendPaymentForm

+ +

Send compiled payment form

+

+ +
+
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
+payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
+---functions---
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
form_idlongForm ID
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of form
requested_info_idflags.0?stringID of saved and validated order info
shipping_option_idflags.1?stringChosen shipping option ID
credentialsInputPaymentCredentialsPayment credentials
tip_amountflags.2?longTip, in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Result

+

payments.PaymentResult

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+

Related pages

+

payments.ValidatedRequestedInfo

+

Validated user-provided info

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/payments.validateRequestedInfo b/data/core.telegram.org/method/payments.validateRequestedInfo new file mode 100644 index 0000000000..18b405ddbf --- /dev/null +++ b/data/core.telegram.org/method/payments.validateRequestedInfo @@ -0,0 +1,186 @@ + + + + + payments.validateRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.validateRequestedInfo

+ +

Submit requested order information for validation

+

+ +
+
payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
+---functions---
+payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
saveflags.0?trueSave order information to re-use it for future orders
peerInputPeerPeer where the payment form was sent
msg_idintMessage ID of payment form
infoPaymentRequestedInfoRequested order information
+

Result

+

payments.ValidatedRequestedInfo

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.acceptCall b/data/core.telegram.org/method/phone.acceptCall new file mode 100644 index 0000000000..396248bac2 --- /dev/null +++ b/data/core.telegram.org/method/phone.acceptCall @@ -0,0 +1,193 @@ + + + + + phone.acceptCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.acceptCall

+ +

Accept incoming call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+---functions---
+phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe call to accept
g_bbytesParameter for E2E encryption key exchange »
protocolPhoneCallProtocolPhone call settings
+

Result

+

phone.PhoneCall

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_ACCEPTEDThe call was already accepted.
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
400CALL_PROTOCOL_FLAGS_INVALIDCall protocol flags invalid.
+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.checkGroupCall b/data/core.telegram.org/method/phone.checkGroupCall new file mode 100644 index 0000000000..a576b95a20 --- /dev/null +++ b/data/core.telegram.org/method/phone.checkGroupCall @@ -0,0 +1,154 @@ + + + + + phone.checkGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.checkGroupCall

+ +

Check whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs

+

+ +
+
---functions---
+phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
sourcesVector<int>Source IDs
+

Result

+

Vector<int>

+

Returns an intersection of the source IDs specified in sources, and the source IDs currently being forwarded by the SFU.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.confirmCall b/data/core.telegram.org/method/phone.confirmCall new file mode 100644 index 0000000000..26f29bbc5d --- /dev/null +++ b/data/core.telegram.org/method/phone.confirmCall @@ -0,0 +1,188 @@ + + + + + phone.confirmCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.confirmCall

+ +

Complete phone call E2E encryption key exchange »

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+---functions---
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe phone call
g_abytesParameter for E2E encryption key exchange »
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolPhone call settings
+

Result

+

phone.PhoneCall

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.createGroupCall b/data/core.telegram.org/method/phone.createGroupCall new file mode 100644 index 0000000000..494106b9ca --- /dev/null +++ b/data/core.telegram.org/method/phone.createGroupCall @@ -0,0 +1,200 @@ + + + + + phone.createGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.createGroupCall

+ +

Create a group call or livestream

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.createGroupCall#48cdc6d8 flags:# rtmp_stream:flags.2?true peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerAssociate the group call or livestream to the provided group/supergroup/channel
random_idintUnique client message ID required to prevent creation of duplicate group calls
titleflags.0?stringCall title
schedule_dateflags.1?intFor scheduled group call or livestreams, the absolute date when the group call will start
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.discardCall b/data/core.telegram.org/method/phone.discardCall new file mode 100644 index 0000000000..a91a3e61c4 --- /dev/null +++ b/data/core.telegram.org/method/phone.discardCall @@ -0,0 +1,202 @@ + + + + + phone.discardCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.discardCall

+ +

Refuse or end running call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.0?trueWhether this is a video call
peerInputPhoneCallThe phone call
durationintCall duration
reasonPhoneCallDiscardReasonWhy was the call discarded
connection_idlongPreferred libtgvoip relay ID
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_ACCEPTEDThe call was already accepted.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.discardGroupCall b/data/core.telegram.org/method/phone.discardGroupCall new file mode 100644 index 0000000000..fa87075be8 --- /dev/null +++ b/data/core.telegram.org/method/phone.discardGroupCall @@ -0,0 +1,155 @@ + + + + + phone.discardGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.discardGroupCall

+ +

Terminate a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call to terminate
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.editGroupCallMember b/data/core.telegram.org/method/phone.editGroupCallMember new file mode 100644 index 0000000000..168774e042 --- /dev/null +++ b/data/core.telegram.org/method/phone.editGroupCallMember @@ -0,0 +1,167 @@ + + + + + phone.editGroupCallMember + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.editGroupCallMember

+ +

Edit information about a given group call participant

+

+ +
+
 Method schema is available as of layer 123. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + +
flags#Flags, see TL conditional fields
mutedflags.0?trueWhether to mute or unmute the user
callInputGroupCallGroup call
user_idInputUserThe user in question
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.editGroupCallParticipant b/data/core.telegram.org/method/phone.editGroupCallParticipant new file mode 100644 index 0000000000..0b2b587fec --- /dev/null +++ b/data/core.telegram.org/method/phone.editGroupCallParticipant @@ -0,0 +1,225 @@ + + + + + phone.editGroupCallParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.editGroupCallParticipant

+ +

Edit information about a given group call participant

+

Note: flags.N?Bool parameters can have three possible values:

+
    +
  • If the TL flag is not set, the previous value will not be changed.
  • +
  • If the TL flag is set and contains a boolTrue, the previous value will be overwritten to true.
  • +
  • If the TL flag is set and contains a boolFalse, the previous value will be overwritten to false.
  • +
+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallThe group call
participantInputPeerThe group call participant (can also be the user itself)
mutedflags.0?BoolWhether to mute or unmute the specified participant
volumeflags.1?intNew volume
raise_handflags.2?BoolRaise or lower hand
video_stoppedflags.3?BoolStart or stop the video stream
video_pausedflags.4?BoolPause or resume the video stream
presentation_pausedflags.5?BoolPause or resume the screen sharing stream
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USER_VOLUME_INVALIDThe specified user volume is invalid.
+

Related pages

+

Bool

+

Boolean type.

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

boolFalse

+

Constructor may be interpreted as a booleanfalse value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.editGroupCallTitle b/data/core.telegram.org/method/phone.editGroupCallTitle new file mode 100644 index 0000000000..16bf81792b --- /dev/null +++ b/data/core.telegram.org/method/phone.editGroupCallTitle @@ -0,0 +1,160 @@ + + + + + phone.editGroupCallTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.editGroupCallTitle

+ +

Edit the title of a group call or livestream

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
titlestringNew title
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.exportGroupCallInvite b/data/core.telegram.org/method/phone.exportGroupCallInvite new file mode 100644 index 0000000000..985569dbde --- /dev/null +++ b/data/core.telegram.org/method/phone.exportGroupCallInvite @@ -0,0 +1,159 @@ + + + + + phone.exportGroupCallInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.exportGroupCallInvite

+ +

Get an invite link for a group call or livestream

+

+ +
+
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
+---functions---
+phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_self_unmuteflags.0?trueFor livestreams, if set, users that join using this link will be able to speak without explicitly requesting permission by (for example by raising their hand).
callInputGroupCallThe group call
+

Result

+

phone.ExportedGroupCallInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.getCallConfig b/data/core.telegram.org/method/phone.getCallConfig new file mode 100644 index 0000000000..0e158854b2 --- /dev/null +++ b/data/core.telegram.org/method/phone.getCallConfig @@ -0,0 +1,134 @@ + + + + + phone.getCallConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getCallConfig

+ +

Get phone call configuration to be passed to libtgvoip's shared config

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;
+---functions---
+phone.getCallConfig#55451fa9 = DataJSON;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

DataJSON

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.getGroupCall b/data/core.telegram.org/method/phone.getGroupCall new file mode 100644 index 0000000000..f18ff9900e --- /dev/null +++ b/data/core.telegram.org/method/phone.getGroupCall @@ -0,0 +1,157 @@ + + + + + phone.getGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getGroupCall

+ +

Get info about a group call

+

+ +
+
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
+---functions---
+phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
limitintMaximum number of results to return, see pagination
+

Result

+

phone.GroupCall

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.getGroupCallJoinAs b/data/core.telegram.org/method/phone.getGroupCallJoinAs new file mode 100644 index 0000000000..dea38cc8da --- /dev/null +++ b/data/core.telegram.org/method/phone.getGroupCallJoinAs @@ -0,0 +1,149 @@ + + + + + phone.getGroupCallJoinAs + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getGroupCallJoinAs

+ +

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+

+ +
+
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+---functions---
+phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog whose group call or livestream we're trying to join
+

Result

+

phone.JoinAsPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.getGroupParticipants b/data/core.telegram.org/method/phone.getGroupParticipants new file mode 100644 index 0000000000..9e91d3c267 --- /dev/null +++ b/data/core.telegram.org/method/phone.getGroupParticipants @@ -0,0 +1,174 @@ + + + + + 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 new file mode 100644 index 0000000000..2e2a2a9911 --- /dev/null +++ b/data/core.telegram.org/method/phone.inviteToGroupCall @@ -0,0 +1,177 @@ + + + + + phone.inviteToGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.inviteToGroupCall

+ +

Invite a set of users to a group call.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
usersVector<InputUser>The users to invite.
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403GROUPCALL_FORBIDDENThe group call has already ended.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.joinGroupCall b/data/core.telegram.org/method/phone.joinGroupCall new file mode 100644 index 0000000000..237de0c3d2 --- /dev/null +++ b/data/core.telegram.org/method/phone.joinGroupCall @@ -0,0 +1,202 @@ + + + + + phone.joinGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.joinGroupCall

+ +

Join a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
mutedflags.0?trueIf set, the user will be muted by default upon joining.
video_stoppedflags.2?trueIf set, the user's video will be disabled by default upon joining.
callInputGroupCallThe group call
join_asInputPeerJoin the group call, presenting yourself as the specified user/channel
invite_hashflags.1?stringThe invitation hash from the invite link: https://t.me/username?voicechat=hash
paramsDataJSONWebRTC parameters
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400GROUPCALL_SSRC_DUPLICATE_MUCHThe app needs to retry joining the group call with a new SSRC value.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.joinGroupCallPresentation b/data/core.telegram.org/method/phone.joinGroupCallPresentation new file mode 100644 index 0000000000..dd564458dc --- /dev/null +++ b/data/core.telegram.org/method/phone.joinGroupCallPresentation @@ -0,0 +1,180 @@ + + + + + phone.joinGroupCallPresentation + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.joinGroupCallPresentation

+ +

Start screen sharing in a call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
paramsDataJSONWebRTC parameters
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403PARTICIPANT_JOIN_MISSINGTrying to enable a presentation, when the user hasn't joined the Video Chat with phone.joinGroupCall.
+

Related pages

+

phone.joinGroupCall

+

Join a group call

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.leaveGroupCall b/data/core.telegram.org/method/phone.leaveGroupCall new file mode 100644 index 0000000000..30af727e59 --- /dev/null +++ b/data/core.telegram.org/method/phone.leaveGroupCall @@ -0,0 +1,160 @@ + + + + + phone.leaveGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.leaveGroupCall

+ +

Leave a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
sourceintYour source ID
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.leaveGroupCallPresentation b/data/core.telegram.org/method/phone.leaveGroupCallPresentation new file mode 100644 index 0000000000..68d2b3a42e --- /dev/null +++ b/data/core.telegram.org/method/phone.leaveGroupCallPresentation @@ -0,0 +1,155 @@ + + + + + phone.leaveGroupCallPresentation + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.leaveGroupCallPresentation

+ +

Stop screen sharing in a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.receivedCall b/data/core.telegram.org/method/phone.receivedCall new file mode 100644 index 0000000000..db38b7ee97 --- /dev/null +++ b/data/core.telegram.org/method/phone.receivedCall @@ -0,0 +1,172 @@ + + + + + phone.receivedCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.receivedCall

+ +

Optional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe phone call we're currently in
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.requestCall b/data/core.telegram.org/method/phone.requestCall new file mode 100644 index 0000000000..7d8637b743 --- /dev/null +++ b/data/core.telegram.org/method/phone.requestCall @@ -0,0 +1,213 @@ + + + + + phone.requestCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.requestCall

+ +

Start a telegram phone call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+---functions---
+phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.0?trueWhether to start a video call
user_idInputUserDestination of the phone call
random_idintRandom ID to avoid resending the same object
g_a_hashbytesParameter for E2E encryption key exchange »
protocolPhoneCallProtocolPhone call settings
+

Result

+

phone.PhoneCall

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_PROTOCOL_FLAGS_INVALIDCall protocol flags invalid.
400PARTICIPANT_VERSION_OUTDATEDThe other participant does not use an up to date telegram client with support for calls.
400USER_ID_INVALIDThe provided user ID is invalid.
403USER_IS_BLOCKEDYou were blocked by this user.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.saveCallDebug b/data/core.telegram.org/method/phone.saveCallDebug new file mode 100644 index 0000000000..43ee57b329 --- /dev/null +++ b/data/core.telegram.org/method/phone.saveCallDebug @@ -0,0 +1,177 @@ + + + + + phone.saveCallDebug + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.saveCallDebug

+ +

Send phone call debug data to server

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallPhone call
debugDataJSONDebug statistics obtained from libtgvoip
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
400DATA_JSON_INVALIDThe provided JSON data is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.saveDefaultGroupCallJoinAs b/data/core.telegram.org/method/phone.saveDefaultGroupCallJoinAs new file mode 100644 index 0000000000..3882972a27 --- /dev/null +++ b/data/core.telegram.org/method/phone.saveDefaultGroupCallJoinAs @@ -0,0 +1,155 @@ + + + + + phone.saveDefaultGroupCallJoinAs + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.saveDefaultGroupCallJoinAs

+ +

Set the default peer that will be used to join a group call in a specific dialog.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
join_asInputPeerThe default peer that will be used to join group calls in this dialog, presenting yourself as a specific user/channel.
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.sendSignalingData b/data/core.telegram.org/method/phone.sendSignalingData new file mode 100644 index 0000000000..80a694ced8 --- /dev/null +++ b/data/core.telegram.org/method/phone.sendSignalingData @@ -0,0 +1,155 @@ + + + + + phone.sendSignalingData + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.sendSignalingData

+ +

Send VoIP signaling data

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallPhone call
databytesSignaling payload
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.setCallRating b/data/core.telegram.org/method/phone.setCallRating new file mode 100644 index 0000000000..f8e8a4a273 --- /dev/null +++ b/data/core.telegram.org/method/phone.setCallRating @@ -0,0 +1,192 @@ + + + + + phone.setCallRating + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.setCallRating

+ +

Rate a call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_initiativeflags.0?trueWhether the user decided on their own initiative to rate the call
peerInputPhoneCallThe call to rate
ratingintRating in 1-5 stars
commentstringAn additional comment
+

Result

+

Updates with info about the rating message sent to the official VoIP bot

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.startScheduledGroupCall b/data/core.telegram.org/method/phone.startScheduledGroupCall new file mode 100644 index 0000000000..b39b2f43b0 --- /dev/null +++ b/data/core.telegram.org/method/phone.startScheduledGroupCall @@ -0,0 +1,155 @@ + + + + + phone.startScheduledGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.startScheduledGroupCall

+ +

Start a scheduled group call.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe scheduled group call
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.toggleGroupCallRecord b/data/core.telegram.org/method/phone.toggleGroupCallRecord new file mode 100644 index 0000000000..3cfbb43261 --- /dev/null +++ b/data/core.telegram.org/method/phone.toggleGroupCallRecord @@ -0,0 +1,180 @@ + + + + + phone.toggleGroupCallRecord + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.toggleGroupCallRecord

+ +

Start or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
startflags.0?trueWhether to start or stop recording
videoflags.2?trueWhether to also record video streams
callInputGroupCallThe group call or livestream
titleflags.1?stringRecording title
video_portraitflags.2?BoolIf video stream recording is enabled, whether to record in portrait or landscape mode
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.toggleGroupCallStartSubscription b/data/core.telegram.org/method/phone.toggleGroupCallStartSubscription new file mode 100644 index 0000000000..15d6aff834 --- /dev/null +++ b/data/core.telegram.org/method/phone.toggleGroupCallStartSubscription @@ -0,0 +1,160 @@ + + + + + phone.toggleGroupCallStartSubscription + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.toggleGroupCallStartSubscription

+ +

Subscribe or unsubscribe to a scheduled group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallScheduled group call
subscribedBoolEnable or disable subscription
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/photos.deletePhotos b/data/core.telegram.org/method/photos.deletePhotos new file mode 100644 index 0000000000..03ca8188b5 --- /dev/null +++ b/data/core.telegram.org/method/photos.deletePhotos @@ -0,0 +1,148 @@ + + + + + photos.deletePhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.deletePhotos

+ +

Deletes profile photos.

+

+ +
+
---functions---
+photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputPhoto>Input photos to delete
+

Result

+

Method returns a list of successfully deleted photos in Vector<long>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/photos.getUserPhotos b/data/core.telegram.org/method/photos.getUserPhotos new file mode 100644 index 0000000000..210930d62c --- /dev/null +++ b/data/core.telegram.org/method/photos.getUserPhotos @@ -0,0 +1,193 @@ + + + + + photos.getUserPhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.getUserPhotos

+ +

Returns the list of user photos.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+---functions---
+photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
offsetintNumber of list elements to be skipped
max_idlongIf a positive value was transferred, the method will return only photos with IDs less than the set one
limitintNumber of list elements to be returned
+

Result

+

photos.Photos

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MAX_ID_INVALIDThe provided max ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/photos.updateProfilePhoto b/data/core.telegram.org/method/photos.updateProfilePhoto new file mode 100644 index 0000000000..5c51006165 --- /dev/null +++ b/data/core.telegram.org/method/photos.updateProfilePhoto @@ -0,0 +1,196 @@ + + + + + photos.updateProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.updateProfilePhoto

+ +

Installs a previously uploaded photo as a profile photo.

+

+ +
+
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+---functions---
+photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPhotoInput photo
+

Result

+

UserProfilePhoto

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ALBUM_PHOTOS_TOO_MANYToo many.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400LOCATION_INVALIDThe provided location is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_ID_INVALIDPhoto ID invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/photos.uploadProfilePhoto b/data/core.telegram.org/method/photos.uploadProfilePhoto new file mode 100644 index 0000000000..a0481513af --- /dev/null +++ b/data/core.telegram.org/method/photos.uploadProfilePhoto @@ -0,0 +1,221 @@ + + + + + photos.uploadProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.uploadProfilePhoto

+ +

Updates current user profile photo.

+

+ +
+
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+---functions---
+photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts by means of upload.saveFilePart method
videoflags.1?InputFileAnimated profile picture video
video_start_tsflags.2?doubleFloating point UNIX timestamp in seconds, indicating the frame of the video that should be used as static preview.
+

Result

+

photos.Photo

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ALBUM_PHOTOS_TOO_MANYToo many .
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400PHOTO_CROP_FILE_MISSINGPhoto crop file missing.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_FILE_MISSINGProfile photo file missing.
400VIDEO_FILE_INVALIDThe specified video file is invalid.
+

Related pages

+

upload.saveFilePart

+

Saves a part of file for futher sending to one of the methods.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stats.getBroadcastStats b/data/core.telegram.org/method/stats.getBroadcastStats new file mode 100644 index 0000000000..069ce9bb0f --- /dev/null +++ b/data/core.telegram.org/method/stats.getBroadcastStats @@ -0,0 +1,194 @@ + + + + + stats.getBroadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getBroadcastStats

+ +

Get channel statistics

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+---functions---
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelThe channel
+

Result

+

stats.BroadcastStats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_REQUIREDThis method can only be called on a channel, please use stats.getMegagroupStats for supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stats.getMegagroupStats b/data/core.telegram.org/method/stats.getMegagroupStats new file mode 100644 index 0000000000..ddc3e8eefd --- /dev/null +++ b/data/core.telegram.org/method/stats.getMegagroupStats @@ -0,0 +1,191 @@ + + + + + stats.getMegagroupStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getMegagroupStats

+ +

Get supergroup statistics

+

+ +
+
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
+---functions---
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelSupergroup ID
+

Result

+

stats.MegagroupStats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEGAGROUP_REQUIREDYou can only use this method on a supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stats.getMessagePublicForwards b/data/core.telegram.org/method/stats.getMessagePublicForwards new file mode 100644 index 0000000000..9fcd2812f4 --- /dev/null +++ b/data/core.telegram.org/method/stats.getMessagePublicForwards @@ -0,0 +1,212 @@ + + + + + stats.getMessagePublicForwards + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getMessagePublicForwards

+ +

Obtains a list of messages, indicating to which other public channels was a channel message forwarded.
+Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSource channel
msg_idintSource message ID
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+

Related pages

+

messages.messagesSlice

+

Incomplete list of messages and auxiliary data.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

message

+

A message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stats.getMessageStats b/data/core.telegram.org/method/stats.getMessageStats new file mode 100644 index 0000000000..3c0ffc4335 --- /dev/null +++ b/data/core.telegram.org/method/stats.getMessageStats @@ -0,0 +1,189 @@ + + + + + stats.getMessageStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getMessageStats

+ +

Get message statistics

+

+ +
+
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
+---functions---
+stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelChannel ID
msg_idintMessage ID
+

Result

+

stats.MessageStats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stats.loadAsyncGraph b/data/core.telegram.org/method/stats.loadAsyncGraph new file mode 100644 index 0000000000..e73034a5ea --- /dev/null +++ b/data/core.telegram.org/method/stats.loadAsyncGraph @@ -0,0 +1,193 @@ + + + + + stats.loadAsyncGraph + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.loadAsyncGraph

+ +

Load channel statistics graph asynchronously

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+---functions---
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
tokenstringGraph token from statsGraphAsync constructor
xflags.0?longZoom value, if required
+

Result

+

StatsGraph

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400GRAPH_EXPIRED_RELOADThis graph has expired, please obtain a new graph token.
400GRAPH_INVALID_RELOADInvalid graph token provided, please reload the stats and provide the updated token.
400GRAPH_OUTDATED_RELOADThe graph is outdated, please get a new async token using stats.getBroadcastStats.
+

Related pages

+

statsGraphAsync

+

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stickers.addStickerToSet b/data/core.telegram.org/method/stickers.addStickerToSet new file mode 100644 index 0000000000..2225d38b19 --- /dev/null +++ b/data/core.telegram.org/method/stickers.addStickerToSet @@ -0,0 +1,187 @@ + + + + + stickers.addStickerToSet + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.addStickerToSet

+ +

Add a sticker to a stickerset, bots only. The sticker set must have been created by the bot.

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+---functions---
+stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetThe stickerset
stickerInputStickerSetItemThe sticker
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKERSET_INVALIDThe provided sticker set is invalid.
400STICKER_PNG_NOPNGOne of the specified stickers is not a valid PNG file.
400STICKER_TGS_NOTGSInvalid TGS sticker provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stickers.changeStickerPosition b/data/core.telegram.org/method/stickers.changeStickerPosition new file mode 100644 index 0000000000..1b97809f09 --- /dev/null +++ b/data/core.telegram.org/method/stickers.changeStickerPosition @@ -0,0 +1,177 @@ + + + + + stickers.changeStickerPosition + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.changeStickerPosition

+ +

Changes the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+---functions---
+stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickerInputDocumentThe sticker
positionintThe new position of the sticker, zero-based
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKER_INVALIDThe provided sticker is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stickers.checkShortName b/data/core.telegram.org/method/stickers.checkShortName new file mode 100644 index 0000000000..d4fe11206b --- /dev/null +++ b/data/core.telegram.org/method/stickers.checkShortName @@ -0,0 +1,172 @@ + + + + + stickers.checkShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.checkShortName

+ +

Check whether the given short name is available

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+stickers.checkShortName#284b3639 short_name:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
short_namestringShort name
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400SHORT_NAME_INVALIDThe specified short name is invalid.
400SHORT_NAME_OCCUPIEDThe specified short name is already in use.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stickers.createStickerSet b/data/core.telegram.org/method/stickers.createStickerSet new file mode 100644 index 0000000000..49dedfb447 --- /dev/null +++ b/data/core.telegram.org/method/stickers.createStickerSet @@ -0,0 +1,282 @@ + + + + + stickers.createStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.createStickerSet

+ +

Create a stickerset, bots only.

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+---functions---
+stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether this is a mask stickerset
animatedflags.1?trueWhether this is an animated stickerset
user_idInputUserStickerset owner
titlestringStickerset name, 1-64 chars
short_namestringSticker set name. Can contain only English letters, digits and underscores. Must end with "by" ( is case insensitive); 1-64 characters
thumbflags.2?InputDocumentThumbnail
stickersVector<InputStickerSetItem>Stickers
softwareflags.3?stringUsed when importing stickers using the sticker import SDKs, specifies the name of the software that created the stickers
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400PACK_SHORT_NAME_INVALIDShort pack name invalid.
400PACK_SHORT_NAME_OCCUPIEDA stickerpack with this name already exists.
400PACK_TITLE_INVALIDThe stickerpack title is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400SHORTNAME_OCCUPY_FAILEDAn internal error occurred.
400STICKERS_EMPTYNo sticker provided.
400STICKER_EMOJI_INVALIDSticker emoji invalid.
400STICKER_FILE_INVALIDSticker file invalid.
400STICKER_PNG_DIMENSIONSSticker png dimensions invalid.
400STICKER_PNG_NOPNGOne of the specified stickers is not a valid PNG file.
400STICKER_TGS_NODOCIncorrect document type for sticker.
400STICKER_TGS_NOTGSInvalid TGS sticker provided.
400STICKER_THUMB_PNG_NOPNGIncorrect stickerset thumb file provided, PNG / WEBP expected.
400STICKER_THUMB_TGS_NOTGSIncorrect stickerset TGS thumb file provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stickers.removeStickerFromSet b/data/core.telegram.org/method/stickers.removeStickerFromSet new file mode 100644 index 0000000000..9b0859defc --- /dev/null +++ b/data/core.telegram.org/method/stickers.removeStickerFromSet @@ -0,0 +1,172 @@ + + + + + stickers.removeStickerFromSet + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.removeStickerFromSet

+ +

Remove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+---functions---
+stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickerInputDocumentThe sticker to remove
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKER_INVALIDThe provided sticker is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stickers.setStickerSetThumb b/data/core.telegram.org/method/stickers.setStickerSetThumb new file mode 100644 index 0000000000..ef8e968631 --- /dev/null +++ b/data/core.telegram.org/method/stickers.setStickerSetThumb @@ -0,0 +1,182 @@ + + + + + stickers.setStickerSetThumb + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.setStickerSetThumb

+ +

Set stickerset thumbnail

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+---functions---
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetStickerset
thumbInputDocumentThumbnail
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
400STICKER_THUMB_PNG_NOPNGIncorrect stickerset thumb file provided, PNG / WEBP expected.
400STICKER_THUMB_TGS_NOTGSIncorrect stickerset TGS thumb file provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stickers.suggestShortName b/data/core.telegram.org/method/stickers.suggestShortName new file mode 100644 index 0000000000..8fed309902 --- /dev/null +++ b/data/core.telegram.org/method/stickers.suggestShortName @@ -0,0 +1,166 @@ + + + + + stickers.suggestShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.suggestShortName

+ +

Suggests a short name for a given stickerpack name

+

+ +
+
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
+---functions---
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
titlestringSticker pack name
+

Result

+

stickers.SuggestedShortName

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TITLE_INVALIDThe specified stickerpack title is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/updates.getChannelDifference b/data/core.telegram.org/method/updates.getChannelDifference new file mode 100644 index 0000000000..c9d897c76a --- /dev/null +++ b/data/core.telegram.org/method/updates.getChannelDifference @@ -0,0 +1,247 @@ + + + + + updates.getChannelDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.getChannelDifference

+ +

Returns the difference between the current state of updates of a certain channel and transmitted.

+

+ +
+
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
+updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+---functions---
+updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueSet to true to skip some possibly unneeded updates and reduce server-side load
channelInputChannelThe channel
filterChannelMessagesFilterMesssage filter
ptsintPersistent timestamp (see updates)
limitintHow many updates to fetch, max 100000
Ordinary (non-bot) users are supposed to pass 10-100
+

Result

+

updates.ChannelDifference

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FROM_MESSAGE_BOT_DISABLEDBots can't use fromMessage min constructors.
400MSG_ID_INVALIDInvalid message ID provided.
400PERSISTENT_TIMESTAMP_EMPTYPersistent timestamp empty.
400PERSISTENT_TIMESTAMP_INVALIDPersistent timestamp invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400RANGES_INVALIDInvalid range provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
+

Bots can use this method

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/updates.getDifference b/data/core.telegram.org/method/updates.getDifference new file mode 100644 index 0000000000..3eacfb81e1 --- /dev/null +++ b/data/core.telegram.org/method/updates.getDifference @@ -0,0 +1,225 @@ + + + + + updates.getDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.getDifference

+ +

Get new updates.

+

+ +
+
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
+updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
+updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
+updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
+---functions---
+updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
ptsintPTS, see updates.
pts_total_limitflags.0?intFor fast updating: if provided and pts + pts_total_limit < remote pts, updates.differenceTooLong will be returned.
Simply tells the server to not return the difference if it is bigger than pts_total_limit
If the remote pts is too big (> ~4000000), this field will default to 1000000
dateintdate, see updates.
qtsintQTS, see updates.
+

Result

+

updates.Difference

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400DATE_EMPTYDate empty.
400MSG_ID_INVALIDInvalid message ID provided.
400PERSISTENT_TIMESTAMP_EMPTYPersistent timestamp empty.
400PERSISTENT_TIMESTAMP_INVALIDPersistent timestamp invalid.
+

Bots can use this method

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

updates.differenceTooLong

+

The difference is too long, and the specified state must be used to refetch updates.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/updates.getState b/data/core.telegram.org/method/updates.getState new file mode 100644 index 0000000000..a0ea6efa33 --- /dev/null +++ b/data/core.telegram.org/method/updates.getState @@ -0,0 +1,135 @@ + + + + + updates.getState + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.getState

+ +

Returns a current state of updates.

+

+ +
+
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
+---functions---
+updates.getState#edd4882a = updates.State;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

updates.State

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.getCdnFile b/data/core.telegram.org/method/upload.getCdnFile new file mode 100644 index 0000000000..cdae467550 --- /dev/null +++ b/data/core.telegram.org/method/upload.getCdnFile @@ -0,0 +1,162 @@ + + + + + upload.getCdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getCdnFile

+ +

Download a CDN file.

+

+ +
+
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+---functions---
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_tokenbytesFile token
offsetintOffset of chunk to download
limitintLength of chunk to download
+

Result

+

upload.CdnFile

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.getCdnFileHashes b/data/core.telegram.org/method/upload.getCdnFileHashes new file mode 100644 index 0000000000..123454e5dc --- /dev/null +++ b/data/core.telegram.org/method/upload.getCdnFileHashes @@ -0,0 +1,178 @@ + + + + + upload.getCdnFileHashes + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getCdnFileHashes

+ +

Get SHA256 hashes for verifying downloaded CDN files

+

+ +
+
---functions---
+upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_tokenbytesFile
offsetintOffset from which to start getting hashes
+

Result

+

Vector<FileHash>

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
400RSA_DECRYPT_FAILEDInternal RSA decryption failed.
+

Bots can use this method

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.getFile b/data/core.telegram.org/method/upload.getFile new file mode 100644 index 0000000000..6ffa2293fd --- /dev/null +++ b/data/core.telegram.org/method/upload.getFile @@ -0,0 +1,252 @@ + + + + + upload.getFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getFile

+ +

Returns content of a whole file or its part.

+

+ +
+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+---functions---
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
preciseflags.0?trueDisable some checks on limit and offset values, useful for example to stream videos by keyframes
cdn_supportedflags.1?trueWhether the current client supports CDN downloads
locationInputFileLocationFile location
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
+

Result

+

upload.File

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
406FILEREF_UPGRADE_NEEDEDThe client has to be updated in order to support file references.
400FILE_ID_INVALIDThe provided file id is invalid.
400FILE_REFERENCE_*The file reference expired, it must be refreshed.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference.
400LIMIT_INVALIDThe provided limit is invalid.
400LOCATION_INVALIDThe provided location is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400OFFSET_INVALIDThe provided offset is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+

Related pages

+

Encrypted CDNs for Speed and Security

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.getFileHashes b/data/core.telegram.org/method/upload.getFileHashes new file mode 100644 index 0000000000..161326a0cc --- /dev/null +++ b/data/core.telegram.org/method/upload.getFileHashes @@ -0,0 +1,171 @@ + + + + + upload.getFileHashes + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getFileHashes

+ +

Get SHA256 hashes for verifying downloaded files

+

+ +
+
---functions---
+upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
locationInputFileLocationFile
offsetintOffset from which to get file hashes
+

Result

+

Vector<FileHash>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.getWebFile b/data/core.telegram.org/method/upload.getWebFile new file mode 100644 index 0000000000..8b7d09fef5 --- /dev/null +++ b/data/core.telegram.org/method/upload.getWebFile @@ -0,0 +1,176 @@ + + + + + upload.getWebfile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getWebfile

+ +

Returns content of an HTTP file or a part, by proxying the request through telegram.

+

+ +
+
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
+---functions---
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
locationInputWebFileLocationThe file to download
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
+

Result

+

upload.WebFile

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.reuploadCdnFile b/data/core.telegram.org/method/upload.reuploadCdnFile new file mode 100644 index 0000000000..7460bf1287 --- /dev/null +++ b/data/core.telegram.org/method/upload.reuploadCdnFile @@ -0,0 +1,173 @@ + + + + + upload.reuploadCdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.reuploadCdnFile

+ +

Request a reupload of a certain file to a CDN DC.

+

+ +
+
---functions---
+upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_tokenbytesFile token
request_tokenbytesRequest token
+

Result

+

Vector<FileHash>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400RSA_DECRYPT_FAILEDInternal RSA decryption failed.
+

Bots can use this method

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.saveBigFilePart b/data/core.telegram.org/method/upload.saveBigFilePart new file mode 100644 index 0000000000..1a3bf68b2b --- /dev/null +++ b/data/core.telegram.org/method/upload.saveBigFilePart @@ -0,0 +1,208 @@ + + + + + upload.saveBigFilePart + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.saveBigFilePart

+ +

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_idlongRandom file id, created by the client
file_partintPart sequence number
file_total_partsintTotal number of parts
bytesbytesBinary data, part contents
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_EMPTYThe provided file part is empty.
400FILE_PART_INVALIDThe file part number is invalid.
400FILE_PART_SIZE_CHANGEDProvided file part size has changed.
400FILE_PART_SIZE_INVALIDThe provided file part size is invalid.
400FILE_PART_TOO_BIGThe uploaded file part is too big.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.saveFilePart b/data/core.telegram.org/method/upload.saveFilePart new file mode 100644 index 0000000000..f70f3ead83 --- /dev/null +++ b/data/core.telegram.org/method/upload.saveFilePart @@ -0,0 +1,183 @@ + + + + + upload.saveFilePart + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.saveFilePart

+ +

Saves a part of file for futher sending to one of the methods.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_idlongRandom file identifier created by the client
file_partintNumerical order of a part
bytesbytesBinary data, contend of a part
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FILE_PART_EMPTYThe provided file part is empty.
400FILE_PART_INVALIDThe file part number is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/users.getFullUser b/data/core.telegram.org/method/users.getFullUser new file mode 100644 index 0000000000..2c49abe91b --- /dev/null +++ b/data/core.telegram.org/method/users.getFullUser @@ -0,0 +1,177 @@ + + + + + users.getFullUser + + + + + + + + + + + + + +
+ +
+
+
+ +

users.getFullUser

+ +

Returns extended user info by ID.

+

+ +
+
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
+---functions---
+users.getFullUser#ca30a5b1 id:InputUser = UserFull;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputUserUser ID
+

Result

+

Returns a UserFull object containing user info.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/users.getUsers b/data/core.telegram.org/method/users.getUsers new file mode 100644 index 0000000000..4729571195 --- /dev/null +++ b/data/core.telegram.org/method/users.getUsers @@ -0,0 +1,191 @@ + + + + + users.getUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

users.getUsers

+ +

Returns basic user info according to their identifiers.

+

+ +
+
---functions---
+users.getUsers#d91a548 id:Vector<InputUser> = Vector<User>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputUser>List of user identifiers
+

Result

+

Vector<User>

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONNECTION_NOT_INITEDConnection not initialized.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/users.setSecureValueErrors b/data/core.telegram.org/method/users.setSecureValueErrors new file mode 100644 index 0000000000..c592e08479 --- /dev/null +++ b/data/core.telegram.org/method/users.setSecureValueErrors @@ -0,0 +1,176 @@ + + + + + users.setSecureValueErrors + + + + + + + + + + + + + +
+ +
+
+
+ +

users.setSecureValueErrors

+ +

Notify the user that the sent passport data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).

+

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputUserThe user
errorsVector<SecureValueError>Errors
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/methods.html b/data/core.telegram.org/methods.html new file mode 100644 index 0000000000..1b0c6e7f5a --- /dev/null +++ b/data/core.telegram.org/methods.html @@ -0,0 +1,2306 @@ + + + + + Methods + + + + + + + + + + + + + +
+ +
+
+
+ +

Methods

+ +

Accepting the Terms of Service

+ + + + + + + + + + + + + + + + + +
NameDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
help.acceptTermsOfServiceAccept the new terms of service
+

Dealing with spam and ToS violations

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.reportPeerReport a peer for violation of telegram's Terms of Service
account.reportProfilePhotoReport a profile photo of a dialog
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
messages.reportReport a message in a chat for violation of telegram's Terms of Service
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportEncryptedSpamReport a secret chat for spam
+

Fetching configuration

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.getAppChangelogGet changelog of current app.
Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.
help.getAppConfigGet app-specific configuration, see client configuration for more info on the result.
help.getAppUpdateReturns information on update availability for the current application.
help.getConfigReturns current configuration, including data center configuration.
help.getInviteTextReturns localized text of a text message with an invitation.
help.getNearestDcReturns info on data centre nearest to the user.
help.getSupportReturns the support user for the 'ask a question' feature.
help.getSupportNameGet localized name of the telegram support user
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
help.dismissSuggestionDismiss a suggestion, see here for more info ».
+

Login via QR code

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
auth.exportLoginTokenGenerate a login token, for login via QR code.
The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.

For more info, see login via QR code.
auth.acceptLoginTokenAccept QR code login token, logging in the app that generated it.

Returns info about the new session.

For more info, see login via QR code.
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
+

Miscellaneous

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.saveAppLogSaves logs of application on the server.
initConnectionInitialize connection
invokeAfterMsgInvokes a query after successfull completion of one of the previous queries.
invokeAfterMsgsInvokes a query after a successfull completion of previous queries
invokeWithLayerInvoke the specified query using the specified API layer
invokeWithoutUpdatesInvoke a request without subscribing the used connection for updates (this is enabled by default for file queries).
+

Registration/Authorization

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
auth.bindTempAuthKeyBinds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

For more information, see Perfect Forward Secrecy.
auth.cancelCodeCancel the login verification code
auth.checkPasswordTry logging to an account protected by a 2FA password.
account.resetPasswordInitiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »
auth.checkRecoveryPasswordCheck if the 2FA recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.logOutLogs out the user.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
auth.resetAuthorizationsTerminates all user's authorized sessions except for the current one.

After calling this method it is necessary to reregister the current device using the method account.registerDevice
auth.sendCodeSend the verification code for login
auth.signInSigns in a user with a validated phone number.
auth.signUpRegisters a validated phone number in the system.
+

Working with GDPR export

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.initTakeoutSessionInitialize account takeout session
account.finishTakeoutSessionFinish account takeout session
messages.getSplitRangesGet message ranges for saving the user's chat history
channels.getLeftChannelsGet a list of channels/supergroups we left
invokeWithMessagesRangeInvoke with the given message range
invokeWithTakeoutInvoke a method within a takeout session
+

Working with GIFs (actually MPEG4 GIFs)

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getSavedGifsGet saved GIFs
messages.saveGifAdd GIF to saved gifs list
messages.searchGifsSearch for GIFs
+

Working with Public Service Announcement and MTProxy channels

+ + + + + + + + + + + + + + + + + +
NameDescription
help.hidePromoDataHide MTProxy/Public Service Announcement information
help.getPromoDataGet MTProxy/Public Service Announcement information
+

Working with TSF (internal use only)

+ + + + + + + + + + + + + + + + + +
NameDescription
help.editUserInfoInternal use
help.getUserInfoInternal use
+

Working with 2FA login

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getPasswordObtain configuration for two-factor authorization with password
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
account.updatePasswordSettingsSet a new 2FA password
account.declinePasswordResetAbort a pending 2FA password reset, see here for more info »
+

Working with Seamless Telegram Login

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
account.getWebAuthorizationsGet web login widget authorizations
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
+

Working with VoIP calls

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
phone.acceptCallAccept incoming call
phone.confirmCallComplete phone call E2E encryption key exchange »
phone.discardCallRefuse or end running call
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.requestCallStart a telegram phone call
phone.saveCallDebugSend phone call debug data to server
phone.sendSignalingDataSend VoIP signaling data
phone.setCallRatingRate a call
messages.deletePhoneCallHistoryDelete the entire phone call history.
+

Working with channels/supergroups/geogroups

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
channels.createChannelCreate a supergroup/channel.
channels.getInactiveChannelsGet inactive channels and supergroups
channels.deleteChannelDelete a channel/supergroup
channels.deleteHistoryDelete the history of a supergroup
channels.deleteMessagesDelete messages in a channel/supergroup
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editBannedBan/unban/kick a user in a supergroup/channel.
channels.editCreatorTransfer channel ownership
channels.editLocationEdit location of geogroup
channels.editPhotoChange the photo of a channel/supergroup
channels.editTitleEdit the name of a channel/supergroup
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
channels.getAdminLogGet the admin log of a channel/supergroup
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
channels.getChannelsGet info about channels/supergroups
channels.getFullChannelGet full info about a channel
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups.

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.
channels.getMessagesGet channel/supergroup messages
channels.getParticipantGet info about a channel/supergroup participant
channels.getParticipantsGet the participants of a supergroup/channel
channels.inviteToChannelInvite users to a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.readHistoryMark channel/supergroup history as read
channels.readMessageContentsMark channel/supergroup message contents as read
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
channels.setStickersAssociate a stickerset to the supergroup
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
channels.toggleSignaturesEnable/disable message signatures in channels
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
+

Working with chats/supergroups/channels

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getMessageReadParticipantsGet which users read a specific message: only available for groups and supergroups with less than chat_read_mark_size_threshold members, read receipts will be stored for chat_read_mark_expire_period seconds after the message was sent, see client configuration for more info ».
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
messages.createChatCreates a new chat.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.editChatAboutEdit the description of a group/supergroup/channel.
messages.editChatAdminMake a user admin in a legacy group.
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.editChatTitleChanages chat name and sends a service message on it.
messages.exportChatInviteExport an invite link for a chat
messages.getAllChatsGet all chats, channels and supergroups
messages.getChatsReturns chat basic info on their IDs.
messages.getAdminsWithInvitesGet info about chat invites generated by admins.
messages.deleteExportedChatInviteDelete a chat invite
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteChatDelete a chat
messages.getCommonChatsGet chats in common with a user
messages.getFullChatReturns full chat info according to its ID.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
messages.migrateChatTurn a legacy group into a supergroup
channels.convertToGigagroupConvert a supergroup to a gigagroup, when requested by channel suggestions.
+

Working with deep links

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getDeepLinkInfoGet info about a t.me link
help.getRecentMeUrlsGet recently used t.me links
+

Working with files

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.getCdnConfigGet configuration for CDN file downloads.
upload.getCdnFileDownload a CDN file.
upload.getCdnFileHashesGet SHA256 hashes for verifying downloaded CDN files
upload.reuploadCdnFileRequest a reupload of a certain file to a CDN DC.
upload.getFileReturns content of a whole file or its part.
upload.getFileHashesGet SHA256 hashes for verifying downloaded files
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
+

Working with instant view pages

+ + + + + + + + + + + + + + + + + +
NameDescription
messages.getWebPageGet instant view page
messages.getWebPagePreviewGet preview of webpage
+

Working with secret chats

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.acceptEncryptionConfirms creation of a secret chat
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
messages.receivedQueueConfirms receipt of messages in a secret chat by client, cancels push notifications.
+

Working with telegram passport

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
account.verifyPhoneVerify a phone number for telegram passport.
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
account.getAuthorizationsGet logged-in sessions
account.deleteSecureValueDelete stored Telegram Passport documents, for more info see the passport docs »
account.getAllSecureValuesGet all saved Telegram Passport documents, for more info see the passport docs »
account.getSecureValueGet saved Telegram Passport document, for more info see the passport docs »
account.saveSecureValueSecurely save Telegram Passport document, for more info see the passport docs »
help.getPassportConfigGet passport configuration
users.setSecureValueErrorsNotify the user that the sent passport data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.
+

Working with updates

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
updates.getDifferenceGet new updates.
updates.getStateReturns a current state of updates.
+

Working with bot inline queries and callback buttons

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getInlineBotResultsQuery an inline bot
messages.setInlineBotResultsAnswer an inline query, for bots only
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
messages.editInlineBotMessageEdit an inline bot message
+

Working with bots

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
bots.getBotCommandsObtain a list of bot commands for the specified bot scope and language code
bots.setBotCommandsSet bot command list
+

Working with bots (internal bot API use)

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
bots.sendCustomRequestSends a custom request; for bots only
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
+

Working with cloud themes

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.updateThemeUpdate theme
account.uploadThemeUpload theme
account.getThemesGet installed themes
account.createThemeCreate a theme
account.installThemeInstall a theme
account.saveThemeSave a theme
account.getThemeGet theme information
account.getChatThemesGet all available chat themes
messages.setChatThemeChange the chat theme of a certain chat
+

Working with contacts and top peers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
contacts.addContactAdd an existing telegram user as contact.

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.
contacts.blockAdds the user to the blacklist.
contacts.deleteByPhonesDelete contacts by phone number
contacts.deleteContactsDeletes several contacts from the list.
contacts.getBlockedReturns the list of blocked users.
contacts.getContactIDsGet contact by telegram IDs
contacts.getContactsReturns the current user's contact list.
contacts.getLocatedGet contacts near you
contacts.getSavedGet all contacts
contacts.getStatusesReturns the list of contact statuses.
contacts.getTopPeersGet most used peers
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

Use contacts.addContact to add Telegram contacts without actually using their phone number.
contacts.resetSavedDelete saved contacts
contacts.resetTopPeerRatingReset rating of top peer
contacts.searchReturns users found by username substring.
contacts.toggleTopPeersEnable/disable top peers
contacts.unblockDeletes the user from the blacklist.
+

Working with credit cards

+ + + + + + + + + + + + + +
NameDescription
payments.getBankCardDataGet info about a credit card
+

Working with dialogs

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getDialogsReturns the current user dialog list.
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
messages.getDialogUnreadMarksGet dialogs manually marked as unread
messages.markDialogUnreadManually mark dialog as unread
messages.getPeerSettingsGet peer settings
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
messages.getOnlinesGet count of online users in a chat
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
+

Working with drafts

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.clearAllDraftsClear all drafts.
messages.getAllDraftsSave get all message drafts.
messages.saveDraftSave a message draft associated to a chat.
+

Working with emoji keywords

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getEmojiKeywordsGet localized emoji keywords
messages.getEmojiKeywordsDifferenceGet changed emoji keywords
messages.getEmojiKeywordsLanguagesGet info about an emoji keyword localization
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+

Working with folders

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.updateDialogFiltersOrderReorder folders
messages.getDialogFiltersGet folders
messages.getSuggestedDialogFiltersGet suggested folders
messages.updateDialogFilterUpdate folder
folders.deleteFolderDelete a peer folder
folders.editPeerFoldersEdit peers in peer folder
+

Working with games

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
+

Working with group calls & live streaming

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
phone.getGroupCallJoinAsGet a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
phone.editGroupCallParticipantEdit information about a given group call participant

Note: flags.N?Bool parameters can have three possible values:

- If the TL flag is not set, the previous value will not be changed.
- If the TL flag is set and contains a boolTrue, the previous value will be overwritten to true.
- If the TL flag is set and contains a boolFalse, the previous value will be overwritten to false.
phone.toggleGroupCallRecordStart or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).
phone.editGroupCallTitleEdit the title of a group call or livestream
phone.getGroupParticipantsGet group call participants
phone.checkGroupCallCheck whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs
phone.createGroupCallCreate a group call or livestream
phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
phone.leaveGroupCallLeave a group call
phone.toggleGroupCallSettingsChange group call settings
phone.inviteToGroupCallInvite a set of users to a group call.
phone.getGroupCallGet info about a group call
phone.joinGroupCallJoin a group call
phone.leaveGroupCallPresentationStop screen sharing in a group call
phone.discardGroupCallTerminate a group call
phone.joinGroupCallPresentationStart screen sharing in a call
phone.startScheduledGroupCallStart a scheduled group call.
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
+

Working with imported chats

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.uploadImportedMediaUpload a media file associated with an imported chat, click here for more info ».
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat, click here for more info ».

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
messages.checkHistoryImportObtains information about a chat export file, generated by a foreign chat app, click here for more info about imported chats ».
messages.initHistoryImportImport chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».
+

Working with localization packs

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
langpack.getDifferenceGet new strings in languagepack
langpack.getLangPackGet localization pack strings
langpack.getLanguageGet information about a language in a localization pack
langpack.getLanguagesGet information about all languages in a localization pack
langpack.getStringsGet strings from a language pack
+

Working with media autodownload settings

+ + + + + + + + + + + + + + + + + +
NameDescription
account.getAutoDownloadSettingsGet media autodownload settings
account.saveAutoDownloadSettingsChange media autodownload settings
+

Working with message threads

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getRepliesGet messages in a reply thread
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
messages.readDiscussionMark a thread as read
+

Working with message reactions

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getMessagesReactionsGet message reactions
messages.sendReactionSend reaction to message
messages.getMessageReactionsListGet full message reaction list
+

Working with messages

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.deleteHistoryDeletes communication history.
messages.deleteMessagesDeletes messages by their identifiers.
messages.editMessageEdit message
messages.forwardMessagesForwards messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.getMessageEditDataFind out if a media message's caption can be edited
messages.getMessagesReturns the list of messages by their IDs.
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
messages.getRecentLocationsGet live location history of a certain user
messages.getSearchCountersGet the number of results that would be found by a messages.search call with the same parameters
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.readHistoryMarks message history as read.
messages.readMentionsMark mentions as read
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
messages.receivedMessagesConfirms receipt of messages by a client, cancels PUSH-notification sending.
messages.searchGets back found messages
messages.searchGlobalSearch for messages and peers globally
messages.sendMediaSend a media
messages.sendMessageSends a message to a chat
messages.sendMultiMediaSend an album or grouped media
messages.updatePinnedMessagePin a message
messages.unpinAllMessagesUnpin all pinned messages
+

Working with notification settings

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.getNotifyExceptionsReturns list of chats with non-default notification settings
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
+

Working with other users

+ + + + + + + + + + + + + + + + + +
NameDescription
users.getFullUserReturns extended user info by ID.
users.getUsersReturns basic user info according to their identifiers.
+

Working with payments

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
payments.getSavedInfoGet saved payment information
payments.clearSavedInfoClear saved payment information
payments.getPaymentFormGet a payment form
payments.validateRequestedInfoSubmit requested order information for validation
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
account.getTmpPasswordGet temporary payment password
payments.sendPaymentFormSend compiled payment form
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
Use this method to respond to such pre-checkout queries.
Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
payments.getPaymentReceiptGet payment receipt
+

Working with polls

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getPollResultsGet poll results
messages.getPollVotesGet poll results for non-anonymous polls
messages.sendVoteVote in a poll
+

Working with scheduled messages

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.sendScheduledMessagesSend scheduled messages right away
messages.getScheduledHistoryGet scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
messages.getScheduledMessagesGet scheduled messages
+

Working with sensitive content (NSFW)

+ + + + + + + + + + + + + + + + + +
NameDescription
account.getContentSettingsGet sensitive content settings
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
+

Working with sponsored messages

+ + + + + + + + + + + + + + + + + +
NameDescription
channels.getSponsoredMessagesGet a list of sponsored messages
channels.viewSponsoredMessageMark a specific sponsored message as read
+

Working with sponsored proxies

+ + + + + + + + + + + + + +
NameDescription
help.getProxyDataGet promotion info of the currently-used MTProxy
+

Working with statistics

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
stats.loadAsyncGraphLoad channel statistics graph asynchronously
stats.getBroadcastStatsGet channel statistics
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.
stats.getMegagroupStatsGet supergroup statistics
stats.getMessageStatsGet message statistics
+

Working with stickers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getOldFeaturedStickersMethod for fetching previously featured stickers
messages.toggleStickerSetsApply changes to multiple stickersets
stickers.suggestShortNameSuggests a short name for a given stickerpack name
stickers.checkShortNameCheck whether the given short name is available
stickers.setStickerSetThumbSet stickerset thumbnail
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
messages.clearRecentStickersClear recent stickers
messages.faveStickerMark a sticker as favorite
messages.getAllStickersGet all installed stickers
messages.getArchivedStickersGet all archived stickers
messages.getAttachedStickersGet stickers attached to a photo or video
messages.getFavedStickersGet faved stickers
messages.getFeaturedStickersGet featured stickers
messages.getMaskStickersGet installed mask stickers
messages.getRecentStickersGet recent stickers
messages.getStickerSetGet info about a stickerset
messages.getStickersGet stickers by emoji
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.installStickerSetInstall a stickerset
messages.readFeaturedStickersMark new featured stickers as read
messages.reorderStickerSetsReorder installed stickersets
messages.searchStickerSetsSearch for stickersets
messages.uninstallStickerSetUninstall a stickerset
+

Working with the user's account

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.changePhoneChange the phone number of the current account
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.getAccountTTLGet days to live of account
account.getPrivacyGet privacy settings of current account
account.resetAuthorizationLog out an active authorized session by its hash
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.setAccountTTLSet account self-destruction period
account.setPrivacyChange privacy settings of current account
account.setGlobalPrivacySettingsSet global privacy settings
account.getGlobalPrivacySettingsGet global privacy settings
account.updateProfileUpdates user profile.
account.updateStatusUpdates online user status.
+

Working with user profile pictures

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
photos.deletePhotosDeletes profile photos.
photos.getUserPhotosReturns the list of user photos.
photos.updateProfilePhotoInstalls a previously uploaded photo as a profile photo.
photos.uploadProfilePhotoUpdates current user profile photo.
+

Working with usernames

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
account.updateUsernameChanges username for the current user.
account.checkUsernameValidates a username and checks availability.
contacts.resolveUsernameResolve a @username to get peer info
+

Working with wallpapers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.getMultiWallPapersGet info about multiple wallpapers
account.getWallPaperGet info about a certain wallpaper
account.getWallPapersReturns a list of available wallpapers.
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveWallPaperInstall/uninstall wallpaper
account.uploadWallPaperCreate and upload a new wallpaper
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto.html b/data/core.telegram.org/mtproto.html new file mode 100644 index 0000000000..fc52d378d4 --- /dev/null +++ b/data/core.telegram.org/mtproto.html @@ -0,0 +1,260 @@ + + + + + MTProto Mobile Protocol + + + + + + + + + + + + + +
+ +
+
+
+
+

MTProto Mobile Protocol

+ +
+ +
+

Please feel free to check out our FAQ for the Technically Inclined. +Client developers are required to comply with the Security Guidelines.

+
+

Related articles

+

+
+

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

+ +

General Description

+

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

+

The protocol is subdivided into three virtually independent components:

+
    +
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • +
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • +
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as HTTP, HTTPS, WS (plain websockets), WSS (websockets over HTTPS), TCP, UDP).
  • +
+ +
+

As of version 4.6, major Telegram clients are using MTProto 2.0, described in this article. +MTProto v1.0 (described here for reference) is deprecated and is currently being phased out.

+
+

Brief Component Summary

+

High-Level Component (RPC Query Language/API)

+

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific websocket/http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

+

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

+

There are several types of messages:

+
    +
  • RPC calls (client to server): calls to API methods
  • +
  • RPC responses (server to client): results of RPC calls
  • +
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • +
  • Message status query
  • +
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • +
+

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

+

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

+

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

+

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is how the OpenSSL library does it.

+

Authorization and Encryption

+

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 middle bits of the SHA256 of the message body (including session, message ID, etc.), including the padding bytes, prepended by 32 bytes taken from the authorization key. Multipart messages are encrypted as a single message.

+
+

For a technical specification, see Mobile Protocol: Detailed Description

+
+

The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

+

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

+
    +
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • +
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • +
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to that data.
  • +
+

Time Synchronization

+

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

+

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

+

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

+

MTProto transport

+

Before being sent using the selected transport protocol, the payload has to be wrapped in a secondary protocol header, defined by the appropriate MTProto transport protocol.

+ +

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header. +Additionally, the following transport features can be used:

+ +

Example implementations for these protocols can be seen in tdlib and MadelineProto.

+

Transport

+

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. +Multiple transport protocols are defined:

+ +

(We shall examine only the first five types.)

+

Recap

+

To recap, using the ISO/OSI stack as comparison:

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/mtproto/TL-abstract-types.html b/data/core.telegram.org/mtproto/TL-abstract-types.html new file mode 100644 index 0000000000..4612ecdf00 --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-abstract-types.html @@ -0,0 +1,202 @@ + + + + + Binary serialization and abstract TL types + + + + + + + + + + + + + +
+ +
+
+
+ +

Binary serialization and abstract TL types

+ +

TL Language defines abstract data types in the spirit of a general theory of types (more accurately, Martin-Löf’s theories of dependent intuitionistic types) without specifying the values of these types should be represented in memory, when saved to disk, or transmitted over a network. In contrast, the article on binary serialization discusses the problem of effective serialization of values of abstract types. To this end, the concept of a concrete or serialized type has been defined as the sets of serializations of all possible values of the corresponding abstract type. In this case, the serializations take values in the set A of words in the alphabet A*, which consists of 2^32 characters -- 32-bit integers.

+

In order to use a TL schema (e.g. “program”) in the TL language to describe the serialization of values of abstract types, we should explain how the concrete type [T] (subset [T] of A^) is associated with the abstract type T (defined in TL), and how the values of the abstract type T correspond to the values of the concrete type [T] (i.e. the elements of [T]*).

+

Serialization is the process of constructing an element of [T] based on a value of the abstract type T. The reverse process is deserialization.

+

Values of the abstract type T may be represented in a different way. Typically, some sort of trees or graphs are used in memory or, if desired, a set of nodes may be used, each of which contains a certain tag (“node type”) and several pointers to other nodes and/or values of built-in primitive types such as int. However, for general discussions it is useful to write the values of abstract type T as a string, more specifically, an S-expression. Recall that an S-expression is either an atom (the value of a primitive type, for example, an integer or a string constant in quotation marks; or an identifier that corresponds to a built-in or defined function) or a space-delimited list of S-expressions ending in parentheses. In our case, we use S-expressions, the first element of which is a combinator identifier, while the remaining elements (the number of which depends on the combinator’s arity) are S-expressions representing elements of the chosen combinator’s fields (or parameters). Moreover, the type of the arguments’ S-expressions and the type of the S-expressions of the result (e.g. the associated expression) must match.

+

For example, for the schema

+
pair x:int y:int = Pair;
+pnil = PairList;
+pcons hd:Pair tl:PairList = PairList;
+

the following are examples of the abstract type PairList, written as S-expressions:

+
(pnil)
+(pcons (pair 2 3) (pcons (pair 9 4) (pnil)))
+

We usually write E : T (read "E of type T”) when we want to say that E is a value of type T. We assume there is a built-in type Type whose values are types. Thus, writing T : Type means that T is a type.

+

For example, we can write:

+
PairList : Type;
+(pcons (pair 2 3) (pcons (pair 9 4) (pnil))) : PairList;
+

Converting an abstract value to a serialized value, generally speaking, is straightforward (and, if desired, can be defined by induction):

+
    +
  • +

    It is the serialization of values n of the primitive type int (as a single-symbol word in the alphabet A)

    +
  • +
  • +

    The serialization of a string constant (a value of the primitive type string) is a sequence of the 32-bit numbers defined in Binary serialization.

    +
  • +
  • +

    The serialization of the S-expression (C E1 ... Er) : T, where C is a combinator with arity r with argument types T1, ..., Tr and result type T (e.g. C : T1->T2->...->Tr->T) is the concatenation of the combinator number C (a 32-bit number that unambiguously identifies the combinator, usually equal to the CRC-32 of the string of its TL description) and the serializations of the values E1 of type T1, E2 of type T2, ..., Er of type Tr.

    +
  • +
+

If we use [T] to denote the concrete type corresponding to the abstract T, and [E] to denote an element of [T] corresponding to the value E of type T, then the last rule may be written as:

+
    +
  • [T] is the combination, for each constructor of type C T1->T2->...->Tr->T (i.e. that returns a value of type T), of direct products {C} x [T1] x [T2] x ... x [Tr], where {C} is a single-element set consisting of the combinator number C. Because {C}<>{C'} when C<>C’, this defines a mutually single-valued mapping of the values of the abstract type T (written using S-expressions) to the set [T].
  • +
+

Values of the built-in clothed types Int and String and serialized as if they were defined using int x:int = Int; and string s:string = String;, i.e. the serialization of integer constant or a string is preceded by number of the int or string combinator (constructor). In S-expressions, this may be written as (int 5) or (string "Test").

+

However, what has been described above does not account for certain subtleties, such as the existence of naked types, or the difference between functions (active combinators whose application may be reduced, e.g. calculated) and constructors (passive combinators for which there are not and cannot be reduction rules). Furthermore, we have not explained how to handle polymorphic types and optional combinator parameters. We will attempt to explain this now.

+

Constants, surface values, and functional values

+

By dividing combinators into constructors and functions, we can introduce the following classes of expressions (values) of the abstract type T:

+
    +
  • +

    Constant expressions: for the types int and string, these are all integer/string constants; for T, these are all expressions like (C E1 ... Er) : T, where the combinator C : T1->T2->...->Tr->T is a constructor, and Ei : Ti is constant expressions of types Ti. In other words, a constant expression is an S-expression consisting of only constructors and constant of primitive types.

    +
  • +
  • +

    Surface expressions are expressions that outwardly contain a functional combinator whose arguments, however, are constant expressions of the appropriate types. In other words, the functional combinator is resolved only at the outer level. (This is not entirely true; see the full explanation below).

    +
  • +
  • +

    Functional expressions: These are expressions that may contain any combinators or constants at all levels.

    +
  • +
+

In practice, we most frequently need constant values (for storage and passing any data structures, in particular, responses to RPC queries) and surface expressions (for example, as RPC queries: then the functional combinator of the outer level is the name of the RPC function that we want to call, while its parameters are the arguments, which are constant values, for invoking the function). In some cases, arbitrary functional expressions are helpful (for example, it we want to remotely transmit the result of one RPC query to a different RPC query).

+

We will use c(T) to denote a subtype of the abstract type T, whose values are constant expressions of type T. Clearly, c(T) possesses approximately the same constructors as T itself (with the types of all arguments Ti replaced by c(Ti), but it does not have functional combinators.

+

Analogously, we will use f(T) to denote a subtype of T, whose values are surface expressions of type T. Clearly, the combinators of f(T) are essentially functional combinators of type T, but c() applies to the types of these combinators’ arguments: The combinator A : T1->...->Tr->T turns into A' : c(T1)->...->c(Tr)->f(T). (See the clarification of this rule below.)

+

Thus, we have defined two “functionals” c : Type -> Type and f : Type -> Type, such that forall T : Type, c(T) :- T and forall T : Type, f(T) :- T (writing T :- T' means that T is contained in T', or that T is a subtype of T').

+

We will assume that c and f are idempotent.

+

Naked types

+

From the perspective of abstract type theory, naked types (in contrast to built-in primitive types like int and string are unnecessary. However, they are extremely useful in practice.

+

Therefore, TL introduces the (partially defined) idempotent unary operator %, which turns a standard functional (e.g. an expression of type ...->Type or simply Type) into a different standard functional of the same type. If T is a type, then from an abstract theoretical point of view, %T is equivalent to c(T). In other words, the values of %T are the constant values of T. If T is a k-arity standard expression, then T : S1 -> ... -> Sk -> Type, where each Si=Type or #, then by definition %T is a k-arity standard expression with the same arity, which is defined by the equation (%T) a1 ... ak = % (T a1 ... ak).

+

When a constant value of type %T is serialized, it is first serialized as a value of type T (assuming that T is not already a naked type itself). Then the first character of the serialization is discarded (e.g. the name of the enclosing combinator). Therefore, %T is a only a valid type expression if there is not more than one constructor for %T. The expression %T, where T : S1 -> ... -> Sk -> Type, is valid, if for any choice of parameters a1 : S1, ... , ak : Sk, the type T a1 ... ak does not have more than one constructor. Using % in other instances is incorrect.

+

If for every value of the parameters a1 : S1, ..., ak : Sk, there is exactly one constructor C for T a1 ... ak, then TL allows writing C a1 ... ak instead of %T a1 ... ak or %(T a1 .. ak). In other words, in certain situations the identifier C is a synonym for %T. This is only allowed in the context of a type (when specifying the type of a combinator’s field or result).

+

Moreover, it is assumed that %Int = int and %String = string.

+

! modifier

+

In TL, the idempotent operator ! can modify any type, actually making surface values be allowed when its constant values are serialized. However, if T is a standard function like S1->..->Sr->Type, then !T is defined using the equation (!T) a1 ... ar = !(T a1 ... ar), for any a1:S1, ..., ar:Sr.

+

The ! operator is only allowed in a definition of the types of fields of functional combinators. It is usually used as a type prefix, for example:

+
set_timeout {X:Type} timeout:int f:!X = X;
+

In this case, the set_timeout “wrapper” is defined. It takes two explicit parameters: the integer timeout and a surface expression of type X. X : Type is itself an implicit parameter (it is not explicitly stated, rather it is inferred from the values of the other parameters and their types). A similar kind of wrapper may be helpful for modifying the action of RPC queries (which are surface expressions of various types). For example, suppose we have the function

+
factorial n:int = int;
+

then we can wrap the RPC query (factorial 100) as follows: (set_timeout 200 (factorial 100)). This expression is still a surface value of type int, which means it can be passed as an RPC query.

+

A consecutive pair of two computations is another example:

+
pair {X Y : Type} x:X y:Y = Pair X Y;  // constructor
+seq_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for sequential computation
+par_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for parallel computation
+

Now the RPC query (seq_pair (factorial 2) (factorial 3)) : Pair int int first calculates factorial 2, then factorial 3, and returns the pair (pair 2 6). In this case, the sequence of operations isn’t important, because they do not have side effects. It would have been just as well to use (par_pair (factorial 2) (factorial 3)). However, this is not always the case.

+

We can also define an analogy to a “comma” operation:

+
comma {X Y : Type} x:!X y:!Y = Y;
+

For example, this operation could first calculate x, then forget the result, calculate y, and return y.

+

Note that the semantics of the seq_pair, par_pair and comma wrappers are indeed defined where they are implemented (like the semantics of all other functional combinators), not by their TL declaration.

+

In principle, polymorphic wrappers like set_timeout can also be applied, for example, to “annotate” a RPC response’s constant values. For example, the server might return a response to a query together with the time it was calculated. However, a value of type !X must be constant, because that is what is expected as the enclosing expression’s value. In other words, set_timeout 239 E is a constant/surface value of type X if and only if E is such itself.

+

$ modifier

+

The idempotent modifier $ permits the use of arbitrary functional values of an appropriate type in contexts where only constants or surface values are usually allowed. It recursively transforms all combinators for all of the types involved, canceling the action of % and affixing $ to the parameter types and result of all combinators ($ is also added to the front of the transformed combinators). Moreover, built-in types are also transformed (in the final stage): $int = Int and $string = String.

+

This may be useful to create an RPC query that performs a “deep computation” of the expression passed to it:

+
compute {X:Type} expr:$X = X;
+

For example, now we can transmit the following as an RPC query:

+
(compute ($factorial ($factorial (int 3)))) : int
+

(Note that the three has become clothed; the combinator $factorial has type $int -> $int).

+

This is very powerful tool. It does not have to be implemented in very simple versions of TL. $ is not encountered in currently used TL schemas.

+

More on modifiers

+

In fact, at least in terms of its application to serialization, the TL language by default implies the c() modifier around all combinators’ parameter types and results, while ! and $ cancel it (more accurately, ! only cancels, and in some sense $ reverses the meaning). This is why there is no explicit c() modifier in TL and why it is assumed that all functions only accept constant values and return constant results, unless otherwise specified.

+

You may think that some functional combinators may have a type such as partial_factorial n:int = $int; and that the RPC query (partial_factorial 3) might then unexpectedly return ($product (int 3) ($product (int 2) ($product (int 1) (int 1)))) : $int ...

+

It is probably more correct to think about the ! modifier as follows. All types initially include only constant values (and only constructors). The ! modifier makes a new type (it’s twin) out of each type. This new type has no inherent constructors. Functional combinators differ from constructors in that ! is implicitly added in front of their result’s type. After this, the (local or remote) process of calculating the expression can be represented using the polymorphic function eval : !X -> X.

+

Optional combinator parameters and their values

+

See Optional combinator parameters and their values.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-combinators.html b/data/core.telegram.org/mtproto/TL-combinators.html new file mode 100644 index 0000000000..d064ead04c --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-combinators.html @@ -0,0 +1,251 @@ + + + + + Formal description of TL combinators + + + + + + + + + + + + + +
+ +
+
+
+ +

Formal description of TL combinators

+ +

Formal declaration of TL combinators

+

Main article: Formal description of TL. See also TL Language.

+

Combinators in TL are declared as follows:

+
+

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
+full-combinator-id ::= lc-ident-full | _
+combinator-id ::= lc-ident-ns | _
+opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
+args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
+args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
+args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
+args ::= [ ! ] type-term
+multiplicity ::= nat-term
+var-ident-opt ::= var-ident | _
+conditional-arg-def ::= var-ident [ . nat-const ] ?
+result-type ::= boxed-type-ident { subexpr }
+result-type ::= boxed-type-ident < subexpr { , subexpr } >

+
+

We shall clarify what all this means.

+
    +
  • +

    A combinator identifier is either an identifier starting with a lowercase Latin letter (lc-ident), or a namespace identifier (also lc-ident) followed by a period and another lc-ident. Therefore, cons and lists.get are valid combinator identifiers.

    +
  • +
  • +

    A combinator has a name, also known as a number (not to be confused with the designation) -- a 32-bit number that unambiguously determines it. It is either calculated automatically (see below) or it is explicitly assigned in the declaration. To do this, a hash mark (#) and exactly 8 hexadecimal digits -- the combinator’s name -- are added to the identifier of the combinator being defined.

    +
  • +
  • +

    A combinator’s declaration begins with its identifier, to which its name (separated by a hash mark) may have been added.

    +
  • +
  • +

    After the combinator identifier comes the main part of the declaration, which consists of declarations of fields (or variables), including an indication of their types.

    +
  • +
  • +

    First come declarations of optional fields (of which there may be several or none at all). Then there are the declarations of the required fields (there may not be any of these either).

    +
  • +
  • +

    Any identifier that begins with an uppercase or lowercase letter and which does not contain references to a namespace can be a field (variable) identifier. Using uc-ident for identifiers of variable types and lc-indent for other variables is good practice.

    +
  • +
  • +

    Next a combinator declaration contains the equals sign (=) and the result type (it may be composite or appearing for the first time). The result type may be polymorphic and/or dependent; any fields of the defined constructor’s fields of type Type or # may be returned (as subexpressions).

    +
  • +
  • +

    A combinator declaration is terminated with a semicolon.

    +
  • +
+

In what follows, a constructor’s fields, variables, and arguments mean the same thing.

+

Optional field declarations

+
    +
  • +

    These have the form { field_1 ... field_k : type-expr }, where field_i is a variable (field) identifier that is unique within the scope of the combinator declaration, and type-expr is a type shared by all of the fields.

    +
  • +
  • +

    If k>1, this entry is functionally equivalent to { field_1 : type-expr } ... { field_k : type-expr }.

    +
  • +
  • +

    All optional fields must be explicitly named (using _ instead of field_i is not allowed).

    +
  • +
  • +

    Moreover, at present the names of all optional fields must share the combinator’s result type (possibly more than once) and themselves be of type # (i,e., nat) or Type. Therefore, if the exact result type is known, it is possible to determine the values of all of the combinator’s implicit parameters (possibly obtaining a contradiction of the form 2=3 in doing so, which means that the combinator is not allowed in the context).

    +
  • +
+

Required field declarations

+
    +
  • +

    These may have the form ( field_1 ... field_k : type-expr ), similar to an optional field declaration, but with parentheses. This entry is equivalent to ( field_1 : type-expr ) ... ( field_k : type-expr ), where the fields are defined one at a time.

    +
  • +
  • +

    The underscore sign (_) can be used as names of one or more fields (field_i), indicating that the field is anonymous (the exact name is unimportant).

    +
  • +
  • +

    One field may be declared without outer parentheses, like this: field_id : type-expr. Here, however, if type-expr is a complex type, parentheses may be necessary around type-expr (this is reflected in BNF).

    +
  • +
  • +

    Furthermore, one anonymous field may be declared using a type-expr entry, functionally equivalent to _ : type-expr.

    +
  • +
  • +

    Required field declarations follow one after another, separated by spaces (by any number of whitespace symbols, to be more precise).

    +
  • +
  • +

    The declared field’s type (type-expr) may use the declared combinator’s previously defined variables (fields) as subexpressions (i.e. parameter values). For example:

    +

    nil {X:Type} = List X; +cons {X:Type} hd:X tl:(list X) = List X; +typed_list (X:Type) (l : list X) = TypedList;

    +
  • +
+

Repetitions

+
    +
  • +

    These may only exist among required parameters. They have the form [ field-id : ] [ multiplicity * ] [ args ], where args has the same format as the combinator’s declaration of (several) required fields, except that all of the enclosing combinator’s previously declared fields may be used in the argument types.

    +
  • +
  • +

    The name of a field of an enclosing combinator that receives a repetition as a value may be specified (field-id), or bypassed, which is equivalent to using the underscore sign as a field-id.

    +
  • +
  • +

    The multiplicity field is an expression of the type # (nat), which can be a real constant, the name of a preceding field of type #, or an expression in the form ( c + v ), where c is a real constant and v is the name of a field of type #. The sense of the multiplicity field is to provide the length of the (repetition) vector, each element of which consists of values of the types enumerated in args.

    +
  • +
  • +

    The multiplicity field may be bypassed. In this case, the last preceding parameter of type # from the enclosing combinator is used (it must be).

    +
  • +
  • +

    Functionally, the repetition field-id : multiplicity * [ args ] is equivalent to the declaration of the single field ( field-id : %Tuple %AuxType multiplicity ), where aux_type is an auxiliary type with a new name defined as aux_type *args* = AuxType. If any of the enclosing type’s fields are used within args, they are added to the auxiliary constructor aux_type and to its AuxType result type as the first (optional) parameters.

    +
  • +
  • +

    If args consists of one anonymous field of type some-type, then some-type can be used directly instead of %AuxType.

    +
  • +
  • +

    If during implementation the repetitions are rewritten as indicated above, it is logical to use instead of aux_type and AuxType, some identifiers that contain the name of the outer combinator being defined and the repetition’s index number inside its definition.

    +
  • +
+

Example:

+
matrix {m n : #} a : m* [ n* [ double ] ] = Matrix m n;
+

is functionally equivalent to

+
aux_type {n : #} (_ : %Tuple double n) = AuxType n;
+matrix {m : #} {n : #} (a : %Tuple %(AuxType n) m) = Matrix m n;
+

Moreover, the built-in types Tuple and Vector could be defined as:

+
tnil {X : Type} = Tuple X 0;
+tcons {X : Type} {n : #} hd:X tl:%(Tuple X n) = Tuple X (S n);
+vector {X : Type} (n : #) (v : %(Tuple X n)) = Vector X;
+

Actually, the following equivalent entry is considered the definition of Vector (i.e. it is specifically this entry that is used to compute the name of the vector constructor and its partial applications):

+
vector {t : Type} # [ t ] = Vector t;
+

If we expand it using Tuple, we obtain the previous definition exactly.

+

Conditional fields

+

The construction

+
+

args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
+conditional-arg-def ::= var-ident [ . nat-const ] ?

+
+

permits assigning fields which are only present if the value of a preceding mandatory or optional field of type # is not null (or if its chosen bit is not zero if the special binary bit-selection operator . is applied). +Example:

+
+

user {fields:#} id:int first_name:(fields.0?string) last_name:(fields.1?string) friends:(fields.2?%(Vector int)) = User fields;
+get_users req_fields:# ids:%(Vector int) = Vector %(User req_fields)

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-dependent.html b/data/core.telegram.org/mtproto/TL-dependent.html new file mode 100644 index 0000000000..987e34555b --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-dependent.html @@ -0,0 +1,236 @@ + + + + + TL-dependent + + + + + + + + + + + + + +
+ +
+
+
+ +

TL-dependent

+ +

Main article: TL Language.

+

In certain cases, types may depend not only on other types (polymorphism), but also on the parameters of another type (dependent types). The TL language provides very limited support for this functionality: dependence is only allowed on a natural parameter whose type is designated using # (alias nat, but this is private -- TL doesn’t currently support this synonym). Values of type # are serialized as 32-bit signed numbers from 0 to 2^31-1.

+

Example: integer tuples (vectors)

+

Suppose we want to use induction to define the types “one integer”, “two integers”, and “three integers”. We could try to define them as follows:

+
empty = Empty;
+single x:int = Single;
+pair x:int y:int = Pair;
+triple x:int y:int z:int = Triple;
+quadruple x:int y:int z:int t:int = Quadruple;
+...
+

or as:

+
empty = Empty;
+single x:int empty = Single;
+pair x:int y:single = Pair;
+triple x:int yz:pair = Triple;
+quadruple x:int yzt:triple = Quadruple;
+

or as:

+
tnil = Tuple0;
+tcons0 hd:int tl:Tuple0 = Tuple1;
+tcons1 hd:int tl:Tuple1 = Tuple2;
+tcons2 hd:int tl:Tuple2 = Tuple3;
+...
+tcons_n hd:int tl:Tuple_n = Tuple_(n+1)
+

The first two variations lead to the same serialization. For example, (2 3 9):%triple and (2 (3 9)):%triple serialize as three 32-bit numbers: 2 3 9. The last variation better emphasizes the inductive version of the definition, but it uses boxed types. This is good from a theoretical perspective, but it leads to “superfluous” constructor names in serialization.

+

Therefore, we will write %Type-Ident to indicate the bare type that corresponds to the boxed type Type-Ident with a single constructor. If this constructor is named constructor, then according to the definition %Type-Ident = %constructor. Now we can write our definition like this:

+
tnil = Tuple0;
+tcons_n hd:int tl:%Tuple_n = Tuple_(n+1)
+

If we now abstract n out of the name of the type name and make it like a parameter for a polymorphic (dependent, to be more exact) type, then something like the following can be written in a suitable functional language:

+
NewType Tuple (n : #) :=
+| tnil = Tuple 0
+| tcons n:# hd:int tl:%(Tuple n) = Tuple (S n)
+EndType;
+

In the TL language, it looks like this:

+
tnil = Tuple 0;
+tcons {n:#} hd:int tl:%(Tuple n) = Tuple (S n);
+

The function S : # -> # and the constant O : # (it is 0) are the function for the next natural number (S n = n + 1) and the constant null. Therefore, the type # (alias nat) behaves as if it were defined in TL using the constructors

+
O = nat;
+S nat = nat;
+

or, using syntax more typical of other functional languages,

+
NewType nat :=
+| O
+| S nat
+EndType;
+

Types of all defined combinators:

+
O : #
+S : # -> #
+Tuple : # -> Type
+tnil : Tuple 0
+tcons : forall n : #, int -> Tuple n -> Tuple (S n)
+

or

+
Tuple : forall n : #, Type;
+tcons : forall n : #, forall hd : int, forall tl : Tuple n, Tuple (S n)
+

Note that in this case the constructor tnil does not depend on the parameter n, while tcons does.

+

In an analogous manner, it is possible to define a complete binary tree of height h with strings in the leaf nodes:

+
tleaf value:string = BinTree 0;
+tnode {h:#} left:(BinTree h) right:(BinTree h) = BinTree (S h);
+

Or a random tree whose leaf nodes are all a distance of h from the root and whose nodes are all labeled with integers:

+
hleaf value:int = Tree 0;
+hnode {n:#} left:(Tree n) next:(Tree (S n)) = Tree (S n)
+hnil {n:#} = Tree (S n)
+

Another version:

+
hleaf' value:int = Tree' 0;
+hnode' {n:#} children:(list (Tree' n)) = Tree' (S n)
+

Polymorphic dependent types

+

Let us try to define a type Tuple X n whose values are n-tuples of type X values. In this way, Tuple will be simultaneously polymorphic and dependent:

+
Tuple : Type -> # -> Type;
+

In the familiar syntax of functional languages:

+
NewType Tuple {X : Type} {n : #} :=
+| vnil : Tuple X 0
+| vcons {n:#} hd:X tl:%(Tuple X n) : Tuple X (S n)
+EndType
+

or, in TL syntax,

+
vnil {X:Type} = Tuple X 0;
+vcons {X:Type} {n:#} tl:(%Tuple X n) = Tuple X S n
+

In the end we obtain terms for the following types:

+
vnil : forall X : Type, Tuple X 0
+vcons : forall X : Type, forall n : #, X -> Tuple X n -> Tuple X (S n)
+

or

+
vnil : forall X : Type, Tuple X 0
+vcons : forall X : Type, forall n : #, forall hd : X, forall tl : Tuple X n, Tuple X (S n)
+

Dependent sums

+

The Tuple we just defined differs from the built-in Vector type. Specifically, the Vector type formally depends on a single argument (a type), but our Tuple depends on two (a type and a number):

+
Tuple : Type -> # -> Type;
+Vector : Type -> Type;
+

The built-in Vector could be defined in terms of our Tuple using “summing across all n : #":

+
vector {X:Type} n:# v:(%Tuple X n) = Vector X;
+

Nevertheless, our Tuple has its advantages. For example, we can define data types such as:

+
matrix_10x10 a:(%Tuple (%Tuple double 10) 10) = Matrix_10x10;
+

In any event, remember that during calculation of the matrix_10x10 combinator’s number, all parentheses must be removed and the CRC32 of the string matrix_10x10 a:%Tuple %Tuple double 10 10 = Matrix_10x10 must be computed.

+

Moreover, we can define arbitrarily-sized matrices:

+
matrix {X:Type} m:# n:# a:(%Tuple (%Tuple X m) n) = Matrix X;
+

In this case using vector would result in storing the length of a row (m) in each row, e.g. n times.

+

Note that the serializations of values of type %Tuple X n and vector X (also known as %vector X and %Vector X) nearly match when n > 0: in both cases we obtain a single 32-bit number (equal to n-1 or n depending on the version) followed by the serializations of n objects of type X. (This is slightly untrue: values of type %Tuple X n can only be serialized if n is a constant or value known from one of the preceding fields of the enclosing entry; but then this n won’t be serialized explicitly anywhere).

+

Special syntax for repetitions

+

In view of the importance of the construction presented above, it is built into the TL language in the following manner. A substructure in the form of [ array-field-name ":" ] [ nat-ident "" ] "[" field-descr ... "]” may be used in the declaration of any combinator, where nat-ident* is the name of any previously encountered field of type # (if it is not explicitly indicated, the most recent is used). In abstract, this substructure is equivalent to:

+
aux_type *field-descr* ... = AuxType;
+*current_constructor* ... [ *array-field-name* ":" ] (%Tuple aux_type *nat-ident*)
+

For example, 10x10 matrices, vectors, and arbitrary matrices may be defined in the following way:

+
matrix {X:Type} m:# n:# a:n*[ m*[ X ] ] = Matrix X;
+matrix_10x10 a:10*[ 10*[ double ]] = Matrix_10x10;
+vector {X:Type} # [ X ] = Vector X;
+

We have already encountered the last version as a “definition” of the “built-in type” Vector.

+

Of course, several fields, as complex as desired, may be within the repeating part. Furthermore, besides using n as a repeat counter, one may use expressions of the form (n+const) and (const+n), where const is a small nonnegative constant, which are shorthand for S (S ( ... (S n) ... )):

+
repeat_np1 n:# a:(S n)*[ key:string value:string ] = Dictionary;
+

To calculate the CRC32 these expressions are converted to expressions of the form (const+X) without internal spaces. Additionally, the * in this case is not set off by spaces on the left and right.

+

Serialization of dependent types

+

Serialization of dependent types and polymorphic types is not a fundamental challenge: we have combinators with non-zero arity with Type values. For example, the type Tuple double 10 : Type serializes to 'Tuple' '%double' 10. Note that at present in practice there is virtually no need to serialize types, whether dependent or not.

+

Optional combinator parameters in TL

+

Optional combinator parameters in TL must possess the following properties:

+
    +
  • +

    Optional parameters must be precisely ythe combinator’s first several arguments;

    +
  • +
  • +

    The value of any optional parameter must be entirely determined by the combinator’s result type.

    +
  • +
+

For example, in cons {X:Type} hd:X tl:(list X) = list X the parameter X may be made optional, because it is located at the very beginning of the argument list and is unambiguously determined by the list X result type. Similarly, in tcons {X:Type} {n:#} hd:X tl:(%Tuple X n) = Tuple X (S n) the values of X and n are completely determined based on the Tuple X (S n) result type, therefore they made be made optional parameters.

+

It usually makes sense to move all of a constructor’s arguments satisfying the second condition to the beginning of the list, arrange them in the order they appear in the result type’s parameters, and make them optional. Given such an approach, the full version of a constructor is rarely needed -- only when we want to transmit the value of the polymorphic or dependent type as a value of type Object. In all other cases, the type of the expected value from the context is already known, which means that all optional parameters can be recovered during decomposition.

+

See also Optional combinator parameters and their values.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-formal.html b/data/core.telegram.org/mtproto/TL-formal.html new file mode 100644 index 0000000000..0bd0d20bfd --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-formal.html @@ -0,0 +1,319 @@ + + + + + TL-formal + + + + + + + + + + + + + +
+ +
+
+
+ +

TL-formal

+ +

See also TL Language. +For the syntax of declaring combinators, see in article Formal declaration of TL combinators. +For the syntax of patterns, see in article Formal declaration of TL patterns.

+

Tokens

+

Comments are the same as in C/C++. They are removed by a lexical parser (for example, being replaced by a single space). Whitespace separates tokens. Except for string constants, tokens cannot contain spaces.

+

Character classes:

+
+

lc-letter ::= a | b | ... | z
+uc-letter ::= A | B | ... | Z
+digit ::= 0 | 1 | ... | 9
+hex-digit ::= digit | a | b | c | d | e | f
+underscore ::= _
+letter ::= lc-letter | uc-letter
+ident-char ::= letter | digit | underscore

+
+

Simple identifiers and keywords:

+
+

lc-ident ::= lc-letter { ident-char }
+uc-ident ::= uc-letter { ident-char }
+namespace-ident ::= lc-ident
+lc-ident-ns ::= [ namespace-ident . ] lc-ident
+uc-ident-ns ::= [ namespace-ident . ] uc-ident
+lc-ident-full ::= lc-ident-ns [ # hex-digit *8 ]

+
+

Tokens:

+
+

underscore ::= _
+colon ::= :
+semicolon ::= ;
+open-par ::= (
+close-par ::= )
+open-bracket ::= [
+close-bracket ::= ]
+open-brace ::= {
+close-brace ::= }
+triple-minus ::= ---
+nat-const ::= digit { digit }
+lc-ident-full
+lc-ident
+uc-ident-ns
+equals ::= =
+hash ::= #
+question-mark ::= ?
+percent ::= %
+plus ::= +
+langle ::= <
+rangle ::= >
+comma ::= ,
+dot ::= .
+asterisk ::= *
+excl-mark ::= !
+Final-kw ::= Final
+New-kw ::= New
+Empty-kw ::= Empty

+
+

Final is a reserved keyword, e.g. a special token. Words like Type are not keywords, rather they are identifiers with preset values.

+

Tokens consisting of one or more constant symbols shall be hereafter denoted using terms in quotation marks (for example, --- replaces triple-minus).

+

Syntax

+

General syntax of a TL program

+

Syntactically, a TL program consists of a stream of tokens (separated by spaces, which are ignored at this stage). General program structure:

+
+

TL-program ::= constr-declarations { --- functions --- fun-declarations | --- types --- constr-declarations }

+
+

Here the constructor- and function declarations are nearly identical in their syntax (they are both combinators):

+
+

constr-declarations ::= { declaration }
+fun-declarations ::= { declaration }

+
+

There are various declarations:

+
+

declaration ::= combinator-decl | partial-app-decl | final-decl

+
+

Before explaining how declarations of combinators, partial applications, and type finalization are given, we will introduce additional syntactical categories:

+

Syntactical categories and constructions

+

The concept of an expression (expr) is important. There are type expressions (type-expr) and numeric expressions (nat-expr). However, they are defined the same way. Their correctness as type- or numeric expressions is checked when the type of the analyzed expression is checked.

+
+

type-expr ::= expr
+nat-expr ::= expr
+expr ::= { subexpr }
+subexpr ::= term | nat-const + subexpr | subexpr + nat-const
+term ::= ( expr ) | type-ident | var-ident | nat-const | % term | type-ident < expr { , expr } >
+type-ident ::= boxed-type-ident | lc-ident-ns | #
+boxed-type-ident ::= uc-ident-ns
+var-ident ::= lc-ident | uc-ident
+type-term ::= term
+nat-term ::= term

+
+

Note that writing E = E_1 E_2 ... E_n in the expression for expr means applying the function E_1 to the argument E_2, applying the result to E_3, etc. Specifically, E_1 E_2 E_3 = (E_1 E_2) E_3. A solitary # is included in type-ident, because it is actually the identifier for a built-in type (# alias nat).

+

The expression E<E_1,...,E_n> is syntactic sugar for (E (E_1) ... (E_n)), i.e. both expressions are transformed into the same internal representation.

+

Combinator declarations

+
+

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
+full-combinator-id ::= lc-ident-full | _
+combinator-id ::= lc-ident-ns | _
+opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
+args ::= var-ident-opt : [ conditional-def ] [ ! ] type-term
+args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
+args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
+args ::= [ ! ] type-term
+multiplicity ::= nat-term
+var-ident-opt ::= var-ident | _
+conditional-def ::= var-ident [ . nat-const ] ?
+result-type ::= boxed-type-ident { subexpr }
+result-type ::= boxed-type-ident < subexpr { , subexpr } >

+
+

See Formal declaration of TL combinators for a description of what exactly this means. Here we will only note that when declaring the type of a combinator’s next argument, only the names of previously arranged (more to the left) arguments of the same combinator may be used as variables, but when declaring the result type you can use all of its parameters (of type Type and #).

+

Note that the names of combinators declared in this way may be used in TL itself only as the corresponding bare types. The only combinators that appear in declarations are built-in: O : # and S : # -> #.

+

There are also “pseudo-declarations” that are allowed only to declare built-in types (such as int ? = Int;):

+
+

builtin-combinator-decl ::= full-combinator-id ? = boxed-type-ident ;

+
+

Partial applications (patterns)

+
+

partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
+partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
+partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

+
+

See Formal declaration of TL patterns.

+

Type finalization

+
+

final-decl ::= New boxed-type-ident ; | Final boxed-type-ident ; | Empty boxed-type-ident ;

+
+

This type of declaration means that there must not be any constructor for the indicated type: before the declaration for New and after the declaration for Final. The keyword Empty enables both effects.

+

Predefined identifiers

+

Nearly all predefined identifiers may be given using the following schema (usually located in common.tl):

+
+

/////
+//
+// Common Types
+//
+/////

+

// Built-in types
+int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;

+

// Boolean emulation
+boolFalse = Bool;
+boolTrue = Bool;

+

// Boolean for diagonal queries
+boolStat statTrue:int statFalse:int statUnknown:int = BoolStat;

+

// Vector
+vector {t:Type} # [t] = Vector t;
+tuple {t:Type} {n:#} [t] = Tuple t n;
+vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;

+

/////
+//
+// Result- (Maybe-) types
+//
+/////

+

resultFalse {t:Type} = Maybe t;
+resultTrue {t:Type} result:t = Maybe t;

+

pair {X:Type} {Y:Type} a:X b:Y = Pair X Y;
+map {X:Type} {Y:Type} key:X value:Y = Map X Y;

+

Empty False;
+true = True;

+

unit = Unit;

+
+
    +
  • +

    Predefined identifier Type: This type signifies the type of all types. It is usually used to specify the types of optional parameters in the constructors of polymorphic types. If strongly desired, it can be used in its own right, but this is very rarely needed in practice.

    +
  • +
  • +

    Identifier #: This type is used to specify a special type of nonnegative integers in the range from 0 to 2^31-1; its main purpose is the same as that of Type. There are two built-in constructors: O : # and S : # -> # (“null” and “next number”, respectively), which work as if # was defined using the schema

    +
  • +
+
+

O = #;
+S # = #;

+
+
    +
  • +

    Identifier Tuple: Type -> # -> Type denotes a set of the specified number of values of the indicated type. In other words, Tuple X n means “a set of n values of type X".

    +
  • +
  • +

    The typeBool, with two constructors boolTrue and boolFalse, is used to transmit Boolean values.

    +
  • +
  • +

    The constructor-less type False may be used instead of undeclared or invalid types in the construction of a TL schema, because any attempt to (de)serialize a value of type False will produce an error. Usage Example:

    +
  • +
+
+

user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string reserved3:flags.3?False reserved4:flags.4?False = User flags;
+user_present {flags:#} info:%(User flags) = UserInfo flags;
+user_absent {flags:#} = UserInfo flags;
+getUser flags:# id:int = !UserInfo flags;

+
+

In the future, bits 3 and 4 in the flags field may be used to transmit new fields after changing the names and types of the reserved3 and reserved4 fields. This will change the user constructor’s number, but this isn’t too important, since the User flags type is only used as a bare type. Transmitting bits 3 or 4 in the flags field in a getUser query before these fields have actually been defined will lead to an error in the (de)serialization of the request.

+
    +
  • The type True with a single null constructor true plays a role similar to the void type in C/C++. It is especially useful as a bare type %True, alias true, because its serialization has zero length. For example, the first_name:flags.1?string constructor used above is in fact shorthand for (the as-yet unsupported) alternative-type general constructor first_name:(flags.1?string:true).
  • +
+

When directly used in a conditional field it may simply indicate the presence (absence) of a certain parameter with void type. +If the conditional field exists, the associated parameter will not be populated; the conditional field simply exists and the existance value can be used to perform certain operations, example:

+
user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string bot:flags.3?true reserved4:flags.4?False = User flags;
+

If bit 3 of the flags parameter isn't set, the user is a normal user. +If bit 3 of the flags parameter is set, this indicates that the specified user is a bot: however, during deserialization, the bot parameter must not be assigned any value, since true is actually a void type.

+
    +
  • The typeUnit with a single null constructor Unit is similar to the previous type.
  • +
+

ANTLR definition

+

An ANLTR definition of TL grammar can be found here ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-optargs.html b/data/core.telegram.org/mtproto/TL-optargs.html new file mode 100644 index 0000000000..5c71a8e2bf --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-optargs.html @@ -0,0 +1,151 @@ + + + + + Optional combinator parameters and their values + + + + + + + + + + + + + +
+ +
+
+
+ +

Optional combinator parameters and their values

+ +

TL Language makes it possible to declare a combinator’s first few parameters optional. Subsequently, they are almost never required to be explicitly stated. This is directly related to another important property of TL: polymorphism.

+

All optional parameters are typically required to be part of the result type (at least once).

+

A (sub)expression may be serialized/deserialized in one of two ways:

+
    +
  • +

    The result type is known (for example, we’re parsing the response to a previously sent RPC query and therefore know the value of some type is expected). In this case, the result type may be used to determine the values of the combinator’s implicit parameters.

    +
  • +
  • +

    The result type is not known. It is determined as a result of (de)serialization (for example, we are serializing an RPC query). In this case, it is necessary to explicitly specify (and serialize) all of the combinator’s optional parameters by using the full version of the combinator.

    +
  • +
+

We will assume that the functional combinator only differs from the constructor in that before its result type the ! modifier is implicitly added, and the (remote or local) computation of a functional expression may be presented as the execution of some polymorphic function eval : !X -> X.

+

Moreover, the unknown result type is obviously usually (but not always) bound to the serialization of an expression whose type has been modified by !.

+

We can formulate the following rules. Let there be some constructor

+
C {a1:T1} ... {am:Tm} b1:U1 ... bn:Un = T;
+

Some of its arguments or its result may be marked with the ! modifier (We consider a functional combinator to be a constructor whose result type has been modified by an implicit !).

+

The following conditions must hold:

+
    +
  • +

    Each type T1, ..., Tm, U1, ..., Un, and T may depend on parameters of type Type or #, which have been declared to the left of the use of the given type.

    +
  • +
  • +

    The types of implicit parameters T1, ..., Tm may not be modified by !.

    +
  • +
  • +

    Only implicit parameters of type Type or # are allowed. In other words, Ti is either a Type or a #. (Unlike the previous rule, this rule may be relaxed in the future.)

    +
  • +
  • +

    Each implicit parameter a1, ..., am must be used at least once -- either within one of the Ui types that have a !, or in the result type T, if it does not have an explicit or implicit !.

    +
  • +
  • +

    If an implicit parameter ai is not used in the result type, or if the result type has a !, then its first (leftmost) usage must be within a type Uj that is modified by !.

    +
  • +
+

The idea is this: we assume that during (de)serialization of a value of a type modified by ! that we do not know this type in advance and we will find out what it is only based on the result of the (de)serialization; Conversely, we assume that during (de)serialization of a value of a type that is not modified by ! that we know this type in advance. In this case, complying with the rules stated above lets us always compute the values of all implicit parameters -- either from the (previously known) result type or from the type of one of the bj:!Uj parameters (which was obtained during the serialization process).

+

In fact, ! denotes the direction in which type information is flowing. By default, the result type is the source of information about types (and their parameters), while argument types are the recipients of that information. The use of ! reverses the direction of information flow, making the result type the recipient and the argument type the source of type information.

+

See also Binary serialization and abstract TL types and Polymorphism in TL.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-patterns.html b/data/core.telegram.org/mtproto/TL-patterns.html new file mode 100644 index 0000000000..bf3f26f51a --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-patterns.html @@ -0,0 +1,129 @@ + + + + + TL-patterns + + + + + + + + + + + + + +
+ +
+
+
+ +

TL-patterns

+ +
+

partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
+partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
+partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

+
+

According to the original design, templates must be used to replace concrete values in the first few or all of the optional arguments of a constructor or polymorphic type. For example, if Tuple int 10 is used frequently, you can declare a template for it, which will cause the appropriate constructors to be generated automatically. When using such a constructor there may be nowhere to pass an int type or the tuple size 10. Similarly, it was originally planned to declared templates for Vector int, Vector string, etc. in order to generate constructors for each vector type being used type. These constructors would make it possible during deserialization to determine what kind of array is being transmitted.

+

Templates are not used now. Instead, the same universal constructors (for example, vector {t:Type} [t] = Vector t) are used with the values of the optional parameters being inferred from the type of the result (if we already know from the schema that in this location there must be a Vector int during deserialization, we understand that we will see the universal vector constructor in which t is equal to int).

+

This approach is better in that it is not necessary to define Vector SomeType templates in advance for all possible types in order to generate their own constructors for each of these cases. Nevertheless, there is a drawback. If someone wants to transmit the serialization of a value of the clothed type Vector int as a serialization of a value of type Object, a problem arises during serialization: after seeing the universal vector constructor and then reading the vector length, we cannot determine what type of values should be expected next.

+

In theory, this problem can be solved by using the full form of the constructor (@vector) corresponding to vector (it is automatically defined and is different in that all of the optional parameters become required), or by defining

+
+

object X:Type X = TypedObject

+
+

and passing the object type explicitly. Type serialization is required in both cases.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-polymorph.html b/data/core.telegram.org/mtproto/TL-polymorph.html new file mode 100644 index 0000000000..c2a4b9cde8 --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-polymorph.html @@ -0,0 +1,170 @@ + + + + + Polymorphism in TL + + + + + + + + + + + + + +
+ +
+
+
+ +

Polymorphism in TL

+ +

It should be noted that in the TL schema of the overwhelming majority of API calls the use of polymorphic types is restricted to the Vector type. Nevertheless, having a view of the big picture is still helpful.

+

Ordinary inductive types

+

For example, let us consider the IntList, which is defined as follows:

+
int_cons hd:int tl:IntList = IntList;
+int_nil = IntList;
+

The “int_cons” and “int_nil” constructors as well as the “IntList” type itself are expressions of the following types (writing A : X means that A is an expression of type X):

+
IntList : Type;
+int_cons : int -> IntList -> IntList;
+int_nil : IntList;
+

The keyword Type is used to denote the type of all types. Note that Type is not Object (Object is the type of all terms). +Here is alternative syntax that could be used in some other functional programming language (but not in TL):

+
NewType IntList :=
+| int_cons hd:int tl:IntList
+| int_nil
+EndType
+

Polymorphic type

+

TL supports the following version (curly brackets indicate optional fields, see below):

+
cons {X:Type} hd:X tl:(List X) = List X;
+nil {X:Type} = List X
+

Here is an alternative formulation in other functional languages with dependent types:

+
NewType List {X:Type} :=
+| cons {X:Type} hd:X tl:(List X)
+| nil {X:Type}
+EndType
+

In any event, these variations are equivalent to one another from the point of view of the formal theory of types and lead to the definition of the following terms:

+
List : Type -> Type;
+cons : forall (X:Type), X -> List X -> List X;
+nil : forall (X:Type), X -> List X;
+

In each case, remember that writing “A -> B” is shorthand for “forall (x : A), B” for any variable x not entering into A and B. For example, the “cons” type could be written as follows:

+
cons : forall (X:Type), forall (hd : X), forall (tl : List X), List X
+

or more compactly:

+
cons : forall (X : Type) (hd : X) (tl : List X), List X
+

See Calculus of constructions. Examples of functional languages with dependent types, which support similar constructions are Coq and Agda.

+

In this case, the entry after a universal quantifier proves to be more content-related than that after an arrow, because the name of a variable bound by the quantifier is used to transmit the name of the corresponding field in the constructor, even if this variable is not used anywhere as it pertains to the expression under the quantifier. Structurally, all of these entries of the “cons” type are equivalent.

+

Serialization of types (values of type Type)

+

As we can see, to serialize a value of type List X, which has been obtained by applying the combinator “cons X:Type hd:X tl:(List X) = List X”, we need to:

+
    +
  1. serialize the name of the “cons” combinator into a 32-bit number;
  2. +
  3. serialize X (as a type, i.e. as a value of type Type) if X is a required parameter;
  4. +
  5. serialize the head of the list (hd) as a value of type X;
  6. +
  7. serialize the tail of the list as a value of the polymorphic type List X.
  8. +
+

In the first step, the natural question is which string exactly will be used to calculate the CRC32. It is proposed to take "cons X:Type hd:X tl:List X = List X” without the terminating semicolon and without any parentheses (closed type expressions are unambiguously reconstructed based on their construction’s prefix).

+

In the last step, we recursively resolve the very same problem of serializing a value of type List X; we will consider it resolved based on the assumption of induction in the construction of the value being serialized. We will similarly consider the third step understandable (induction in the construction of the value being serialized).

+

We still need to describe how to transmit (serialize) types, e.g. values of type Type. Types in TL schemas currently appear only as constructors’ optional parameters and are therefore never serialized explicitly. Rather, their values are inferred from the previously known type of the value being serialized.

+

For completeness we will describe how it would be possible to serialize types (values of type Type). However, keep in mind that for now this information is not useful. See Type serialization.

+

Optional arguments in polymorphic constructors

+

It was stated above that any subset of (the first few) parameters of any constructor can be identified as optional (by enclosing their declarations in curly brackets), but this is not actually entirely accurate. First, these optional parameters can only be of type Type or # (natural numbers). Second, optional parameters must share the return value’s type, otherwise their value cannot be determined.

+

Note that @'''constr-id''' means the constructor’s “full form” (in which all optional parameters become required), while '''constr-id'’ denotes its abbreviated form (without the optional arguments). If there are no optional arguments, then these two forms are the same. Constructors’ full forms are never used at present.

+

Bare polymorphic types

+

There is a small problem: if we want to serialize the value of the bare type ‘%pair string int’ or ‘%pair string Y’ (which in TL is usually denoted simply as “pair”, though the form “%Pair” is preferable), we cannot simultaneously use both the full constructor @pair and the partial pair, because the constructor’s name will not be serialized. Therefore, we must differentiate the bare types %@pair (type X, type Y, value x:X, and value y:Y are serialized) and %pair (only x:X and y:Y are serialized; types X and Y are known from the context). In practice, we nearly almost always need the bare type %pair, and this is precisely what “pair” means in the type’s context in TL. Therefore,

+
record name:string map:(List (pair int string)) = Record;
+

will be serialized approximately like we want it to be (the serialization of list elements will consist of the serialization of int and the serialization of string, without any additional headers, types, or combinator names). +Incidentally, when calculating the “record” combinator’s name 'record' in the example given above, the CRC32 of record name:string map:List pair int string = Record will be computed.

+

Also note that a more precise description of this type would be

+
record name:string map:(List %(Pair int string)) = Record
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-tl.html b/data/core.telegram.org/mtproto/TL-tl.html new file mode 100644 index 0000000000..1af3157e11 --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-tl.html @@ -0,0 +1,308 @@ + + + + + TL schema for serialization of TL schemas + + + + + + + + + + + + + +
+ +
+
+
+ +

TL schema for serialization of TL schemas

+ +

If necessary, a TL schema can be serialized in binary form. Here, this serialization format is defined by a TL schema (usually stored in the file tl.tl). This can be useful, for example, to make it possible to write a parser one time for converting a TL schema from text form (stored in the file something.tl) to binary form (stored in the file something.tlo). All other programs (for example, auto-generators of TL-(de)serializers for various programming languages) only need to know how to read .tlo files, which only requires generating an automatic deserializer according to the schema presented below.

+

First, a fragment of the file common.tl with certain required built-in types:

+
/////
+//
+// Common Types (source file common.tl, only necessary definitions included)
+//
+/////
+
+// Built-in types
+int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+
+// Boolean emulation
+boolFalse = Bool;
+boolTrue = Bool;
+
+// Vector
+vector {t:Type} # [t] = Vector t;
+tuple {t:Type} {n:#} [t] = Tuple t n;
+vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;
+
+Empty False;
+true = True;
+

Next, properly, comes tl.tl itself. Note that the declaration for a fairly complex data type required only twenty lines in TL. This demonstrates the expressiveness and compactness of the TL language.

+
/////
+//
+// Serialized binary TL-schema in TL format, source file tl.tl
+//
+/////
+tls.schema_v2 version:int date:int types_num:# types:types_num*[tls.Type] 
+
+    constructor_num:# constructors:constructor_num*[tls.Combinator] 
+    functions_num:# functions:functions_num*[tls.Combinator] = tls.Schema;
+tls.type name:int id:string constructors_num:int flags:int arity:int params_type:long = tls.Type;
+
+tls.combinator name:int id:string type_name:int left:tls.CombinatorLeft right:tls.CombinatorRight = tls.Combinator;
+tls.combinatorLeftBuiltin = tls.CombinatorLeft;
+tls.combinatorLeft args_num:# args:args_num*[tls.Arg] = tls.CombinatorLeft;
+tls.combinatorRight value:tls.TypeExpr = tls.CombinatorRight;
+
+tls.arg id:string flags:# var_num:flags.1?int exist_var_num:flags.2?int exist_var_bit:flags.2?int type:tls.TypeExpr = tls.Arg;
+
+tls.exprType _:tls.TypeExpr = tls.Expr;
+
+tls.exprNat _:tls.NatExpr = tls.Expr;
+tls.natConst value:int = tls.NatExpr;
+
+tls.natVar dif:int var_num:int = tls.NatExpr;
+tls.typeVar var_num:int flags:int = tls.TypeExpr;
+
+tls.array multiplicity:tls.NatExpr args_num:# args:args_num*[tls.Arg] = tls.TypeExpr;
+tls.typeExpr name:int flags:int children_num:# children:children_num*[tls.Expr] = tls.TypeExpr;
+

Remarks

+

Schema serialization (version 2) always begins with the index number of the tls.schema_v2 constructor for tls.Schema. +Because the CRC32 of the string

+
tls.schema_v2 version:int date:int types_num:# types:types_num*[ tls.Type ] constructor_num:# constructors:constructor_num*[ tls.Combinator ] functions_num:# functions:functions_num*[ tls.Combinator ] = tls.Schema
+

is 0x3a2f9be2, this constant is in fact the magic number for tlo files in the current version’s format. +If the format is extended in the future (for example, if TL’s additional features are supported), then a tls.schema_v3 constructor with a different number will appear.

+

Example

+

If one adds declarations for the used built-in types (like int ? = Int;) from the file common.tl before tl.tl and serialize the resulting schema, the following binary data is obtained (tl.tlo):

+
+

0000: 3a2f9be2 00000000 51fec698 00000015 12eb4386 70659eff 00002301 00000000
+0020: 00000000 00000000 00000000 00000000 12eb4386 250be282 6f6f4204 0000006c
+0040: 00000002 02000010 00000000 00000000 00000000 12eb4386 2210c154 756f4406
+0060: 00656c62 00000001 02000000 00000000 00000000 00000000 12eb4386 00000000
+0080: 6c614605 00006573 00000000 00000401 00000000 00000000 00000000 12eb4386
+00a0: a8509bda 746e4903 00000001 02000001 00000000 00000000 00000000 12eb4386
+00c0: 22076cba 6e6f4c04 00000067 00000001 02000001 00000000 00000000 00000000
+00e0: 12eb4386 b5286e24 72745306 00676e69 00000001 02000001 00000000 00000000
+0100: 00000000 12eb4386 3fedd339 75725404 00000065 00000001 02000000 00000000
+0120: 00000000 00000000 12eb4386 9770768a 70755405 0000656c 00000001 02000000
+0140: 00000002 00000002 00000000 12eb4386 2cecf817 70795404 00000065 00000000
+0160: 00000000 00000000 00000000 00000000 12eb4386 1cb5c415 63655606 00726f74
+0180: 00000001 02000008 00000001 00000000 00000000 12eb4386 10133f47 6365560b
+01a0: 54726f74 6c61746f 00000001 02000000 00000001 00000000 00000000 12eb4386
+01c0: 29dfe61b 736c7407 6772412e 00000001 02000000 00000000 00000000 00000000
+01e0: 12eb4386 5c0a1ed5 736c740e 6d6f432e 616e6962 00726f74 00000001 02000000
+0200: 00000000 00000000 00000000 12eb4386 8133d9ba 736c7412 6d6f432e 616e6962
+0220: 4c726f74 00746665 00000002 02000010 00000000 00000000 00000000 12eb4386
+0240: 2c064372 736c7413 6d6f432e 616e6962 52726f74 74686769 00000001 02000000
+0260: 00000000 00000000 00000000 12eb4386 307d41a0 736c7408 7078452e 00000072
+0280: 00000002 02000010 00000000 00000000 00000000 12eb4386 c2635441 736c740b
+02a0: 74614e2e 72707845 00000002 02000010 00000000 00000000 00000000 12eb4386
+02c0: 3a2f9be2 736c740a 6863532e 00616d65 00000001 02000000 00000000 00000000
+02e0: 00000000 12eb4386 12eb4386 736c7408 7079542e 00000065 00000001 02000000
+0300: 00000000 00000000 00000000 12eb4386 193fd378 736c740c 7079542e 70784565
+0320: 00000072 00000003 02000010 00000000 00000000 00000000 00000018 5c0a1ed5
+0340: bc799737 6f6f6209 6c61466c 00006573 250be282 4c12c6d9 00000000 2c064372
+0360: c1863d08 250be282 00000000 00000000 5c0a1ed5 997275b5 6f6f6208 7572546c
+0380: 00000065 250be282 4c12c6d9 00000000 2c064372 c1863d08 250be282 00000000
+03a0: 00000000 5c0a1ed5 2210c154 756f6406 00656c62 2210c154 cd211f63 2c064372
+03c0: c1863d08 2210c154 00000000 00000000 5c0a1ed5 a8509bda 746e6903 a8509bda
+03e0: cd211f63 2c064372 c1863d08 a8509bda 00000000 00000000 5c0a1ed5 22076cba
+0400: 6e6f6c04 00000067 22076cba cd211f63 2c064372 c1863d08 22076cba 00000000
+0420: 00000000 5c0a1ed5 b5286e24 72747306 00676e69 b5286e24 cd211f63 2c064372
+0440: c1863d08 b5286e24 00000000 00000000 5c0a1ed5 3fedd339 75727404 00000065
+0460: 3fedd339 4c12c6d9 00000000 2c064372 c1863d08 3fedd339 00000000 00000000
+0480: 5c0a1ed5 9770768a 70757405 0000656c 9770768a 4c12c6d9 00000003 29dfe61b
+04a0: 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000 29dfe61b
+04c0: 00006e01 00020005 00000001 c1863d08 70659eff 00000000 00000000 29dfe61b
+04e0: 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
+0500: 00000000 00000000 0142ceae 00000000 00000000 2c064372 c1863d08 9770768a
+0520: 00000000 00000002 ecc9da78 0142ceae 00000000 00000000 dcb49bd8 4e8a14f0
+0540: 00000000 00000001 5c0a1ed5 1cb5c415 63657606 00726f74 1cb5c415 4c12c6d9
+0560: 00000003 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000
+0580: 00000000 29dfe61b 00000000 00000004 00000001 c1863d08 70659eff 00000000
+05a0: 00000000 29dfe61b 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001
+05c0: 00000001 29dfe61b 00000000 00000000 0142ceae 00000000 00000000 2c064372
+05e0: c1863d08 1cb5c415 00000000 00000001 ecc9da78 0142ceae 00000000 00000000
+0600: 5c0a1ed5 10133f47 6365760b 54726f74 6c61746f 10133f47 4c12c6d9 00000003
+0620: 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000
+0640: 29dfe61b 746f740b 635f6c61 746e756f 00000000 c1863d08 a8509bda 00000001
+0660: 00000000 29dfe61b 63657606 00726f74 00000000 c1863d08 1cb5c415 00000001
+0680: 00000001 ecc9da78 0142ceae 00000000 00000000 2c064372 c1863d08 10133f47
+06a0: 00000000 00000001 ecc9da78 0142ceae 00000000 00000000 5c0a1ed5 29dfe61b
+06c0: 736c7407 6772612e 29dfe61b 4c12c6d9 00000006 29dfe61b 00646902 00000000
+06e0: c1863d08 b5286e24 00000001 00000000 29dfe61b 616c6605 00007367 00000004
+0700: 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b 72617607 6d756e5f
+0720: 00000002 00000000 00000001 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0740: 6978650d 765f7473 6e5f7261 00006d75 00000002 00000000 00000002 c1863d08
+0760: a8509bda 00000001 00000000 29dfe61b 6978650d 765f7473 625f7261 00007469
+0780: 00000002 00000000 00000002 c1863d08 a8509bda 00000001 00000000 29dfe61b
+07a0: 70797404 00000065 00000000 c1863d08 193fd378 00000000 00000000 2c064372
+07c0: c1863d08 29dfe61b 00000000 00000000 5c0a1ed5 5c0a1ed5 736c740e 6d6f632e
+07e0: 616e6962 00726f74 5c0a1ed5 4c12c6d9 00000005 29dfe61b 6d616e04 00000065
+0800: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 00646902 00000000
+0820: c1863d08 b5286e24 00000001 00000000 29dfe61b 70797409 616e5f65 0000656d
+0840: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 66656c04 00000074
+0860: 00000000 c1863d08 8133d9ba 00000000 00000000 29dfe61b 67697205 00007468
+0880: 00000000 c1863d08 2c064372 00000000 00000000 2c064372 c1863d08 5c0a1ed5
+08a0: 00000000 00000000 5c0a1ed5 cd211f63 736c7419 6d6f632e 616e6962 4c726f74
+08c0: 42746665 746c6975 00006e69 8133d9ba 4c12c6d9 00000000 2c064372 c1863d08
+08e0: 8133d9ba 00000000 00000000 5c0a1ed5 4c12c6d9 736c7412 6d6f632e 616e6962
+0900: 4c726f74 00746665 8133d9ba 4c12c6d9 00000002 29dfe61b 67726108 756e5f73
+0920: 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b
+0940: 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000 00000001
+0960: 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000 2c064372
+0980: c1863d08 8133d9ba 00000000 00000000 5c0a1ed5 2c064372 736c7413 6d6f632e
+09a0: 616e6962 52726f74 74686769 2c064372 4c12c6d9 00000001 29dfe61b 6c617605
+09c0: 00006575 00000000 c1863d08 193fd378 00000000 00000000 2c064372 c1863d08
+09e0: 2c064372 00000000 00000000 5c0a1ed5 ecc9da78 736c740c 7078652e 70795472
+0a00: 00000065 307d41a0 4c12c6d9 00000001 29dfe61b 00000000 00000000 c1863d08
+0a20: 193fd378 00000000 00000000 2c064372 c1863d08 307d41a0 00000000 00000000
+0a40: 5c0a1ed5 dcb49bd8 736c740b 7078652e 74614e72 307d41a0 4c12c6d9 00000001
+0a60: 29dfe61b 00000000 00000000 c1863d08 c2635441 00000000 00000000 2c064372
+0a80: c1863d08 307d41a0 00000000 00000000 5c0a1ed5 8ce940b1 736c740c 74616e2e
+0aa0: 736e6f43 00000074 c2635441 4c12c6d9 00000001 29dfe61b 6c617605 00006575
+0ac0: 00000000 c1863d08 a8509bda 00000001 00000000 2c064372 c1863d08 c2635441
+0ae0: 00000000 00000000 5c0a1ed5 4e8a14f0 736c740a 74616e2e 00726156 c2635441
+0b00: 4c12c6d9 00000002 29dfe61b 66696403 00000000 c1863d08 a8509bda 00000001
+0b20: 00000000 29dfe61b 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001
+0b40: 00000000 2c064372 c1863d08 c2635441 00000000 00000000 5c0a1ed5 3a2f9be2
+0b60: 736c740d 6863732e 5f616d65 00003276 3a2f9be2 4c12c6d9 00000008 29dfe61b
+0b80: 72657607 6e6f6973 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0ba0: 74616404 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0bc0: 70797409 6e5f7365 00006d75 00000004 00000000 c1863d08 70659eff 00000000
+0be0: 00000000 29dfe61b 70797405 00007365 00000000 d9fb20de 4e8a14f0 00000000
+0c00: 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 12eb4386 00000000
+0c20: 00000000 29dfe61b 6e6f630f 75727473 726f7463 6d756e5f 00000004 00000001
+0c40: c1863d08 70659eff 00000000 00000000 29dfe61b 6e6f630c 75727473 726f7463
+0c60: 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
+0c80: 00000000 00000000 c1863d08 5c0a1ed5 00000000 00000000 29dfe61b 6e75660d
+0ca0: 6f697463 6e5f736e 00006d75 00000004 00000002 c1863d08 70659eff 00000000
+0cc0: 00000000 29dfe61b 6e756609 6f697463 0000736e 00000000 d9fb20de 4e8a14f0
+0ce0: 00000000 00000002 00000001 29dfe61b 00000000 00000000 c1863d08 5c0a1ed5
+0d00: 00000000 00000000 2c064372 c1863d08 3a2f9be2 00000000 00000000 5c0a1ed5
+0d20: 12eb4386 736c7408 7079742e 00000065 12eb4386 4c12c6d9 00000006 29dfe61b
+0d40: 6d616e04 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0d60: 00646902 00000000 c1863d08 b5286e24 00000001 00000000 29dfe61b 6e6f6310
+0d80: 75727473 726f7463 756e5f73 0000006d 00000000 c1863d08 a8509bda 00000001
+0da0: 00000000 29dfe61b 616c6605 00007367 00000000 c1863d08 a8509bda 00000001
+0dc0: 00000000 29dfe61b 69726105 00007974 00000000 c1863d08 a8509bda 00000001
+0de0: 00000000 29dfe61b 7261700b 5f736d61 65707974 00000000 c1863d08 22076cba
+0e00: 00000001 00000000 2c064372 c1863d08 12eb4386 00000000 00000000 5c0a1ed5
+0e20: 0142ceae 736c740b 7079742e 72615665 193fd378 4c12c6d9 00000002 29dfe61b
+0e40: 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0e60: 616c6605 00007367 00000000 c1863d08 a8509bda 00000001 00000000 2c064372
+0e80: c1863d08 193fd378 00000000 00000000 5c0a1ed5 d9fb20de 736c7409 7272612e
+0ea0: 00007961 193fd378 4c12c6d9 00000003 29dfe61b 6c756d0c 6c706974 74696369
+0ec0: 00000079 00000000 c1863d08 c2635441 00000000 00000000 29dfe61b 67726108
+0ee0: 756e5f73 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000
+0f00: 29dfe61b 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000
+0f20: 00000001 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000
+0f40: 2c064372 c1863d08 193fd378 00000000 00000000 5c0a1ed5 c1863d08 736c740c
+0f60: 7079742e 70784565 00000072 193fd378 4c12c6d9 00000004 29dfe61b 6d616e04
+0f80: 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 616c6605
+0fa0: 00007367 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 6968630c
+0fc0: 6572646c 756e5f6e 0000006d 00000004 00000000 c1863d08 70659eff 00000000
+0fe0: 00000000 29dfe61b 69686308 6572646c 0000006e 00000000 d9fb20de 4e8a14f0
+1000: 00000000 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 307d41a0
+1020: 00000000 00000000 2c064372 c1863d08 193fd378 00000000 00000000 00000000

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-types.html b/data/core.telegram.org/mtproto/TL-types.html new file mode 100644 index 0000000000..37ec9451ae --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-types.html @@ -0,0 +1,124 @@ + + + + + Type serialization + + + + + + + + + + + + + +
+ +
+
+
+ +

Type serialization

+ +

See Polymorphism in TL and TL Language.

+

It remains to describe how types, e.g. values of type Type, are transmitted (serialized). In general, there is nothing unexpected going on here: we have type constructors of various arities (for example, List is an arity-1 constructor, but IntList is a 0-arity constructor); and if we know that a 32-bit “name” is assigned to each type constructor, there are no further questions -- values of type Type are serialized exactly like values of any other recursive type with a defined set of constructors of differing arity.

+

How can a 32-bit “name” be assigned to a type (a type constructor, to be more exact) such as List or IntList? +It is proposed to use the sum of the names of all of its constructors, plus the CRC32 of the string with the designation of the type's name and all of its parameters such as “IntList = Type” or “List X:Type = Type”. This way, the List constructor’s “name” is the sum of the CRC32s of the three strings "List X:Type = Type", "cons X:Type hd:X tl:List X = List X", and "nil X:Type = List X". +For “bare” types (which, formally speaking, are subtypes of the corresponding “boxed” type), the situation is somewhat more complicated; the logical negation of the corresponding constructor’s name is used. For built-in bareand boxed types (for example, int and Int), a pseudo-declaration is used (for example, int ? = Int").

+
    +
  • This description is somewhat outdated and may be updated in the future. Specifically, how to treat the ! modifier has not been explained.*
  • +
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL.html b/data/core.telegram.org/mtproto/TL.html new file mode 100644 index 0000000000..fdf733ae29 --- /dev/null +++ b/data/core.telegram.org/mtproto/TL.html @@ -0,0 +1,210 @@ + + + + + TL Language + + + + + + + + + + + + + +
+ +
+
+
+ +

TL Language

+ +

TL (Type Language) serves to describe the used system of types, constructors, and existing functions. In fact, the combinator description format presented in Binary Data Serialization is used.

+

See also:

+ +

Advanced topics:

+ +

Overview

+

A TL program usually consists of two sections separated by keyword ---functions---. The first section consists of declarations of built-in types and aggregate types (i.e. their constructors). The second section consists of the declared functions, i.e. functional combinators.

+

Actually, both the first and second sections consist of combinator declarations, each of which ends with a semicolon. However, the first section contains only constructors, while the second section only involves functions. Each combinator is declared using a “combinator declaration” in the format explained above. However, the combinator number and field names may be explicitly assigned.

+

If additional type declarations are required after functions have been declared, the keyword (section divider) ---types--- is used. Furthermore, a functional combinator may be declared in the type section if its result type begins with an exclamation point (in fact, when the function section is interpreted, this exclamation point is added automatically).

+

To explicitly define 32-bit names of combinators, a hash mark (#) is added immediately after the combinator’s name, followed by 8 hexadecimal digits.

+

Namespaces

+

Composite constructions like <namespace_identifier>.<constructor_identifier> and <namespace_identifier>.<Type_identifier> can be used as constructor- or type identifiers. The portion of the identifier to the left of the period is called the namespace. Moreover, the rule about a first uppercase letter in type identifiers and lowercase letter in constructor identifiers applies to the part of the construction after the period. For example, auth.Message would be a type, while auth.std_message would be a constructor.

+

Namespaces do not require a special declaration.

+

Comments

+

Comments are the same as in C++.

+

Example

+
// built-in types
+int#a8509bda ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+null = Null;
+
+vector {t:Type} # [ t ] = Vector t;
+coupleInt {alpha:Type} int alpha = CoupleInt<alpha>;
+coupleStr {gamma:Type} string gamma = CoupleStr gamma;  
+/* The name of the type variable is irrelevant: "gamma" could be replaced with "alpha"; 
+   However, the combinator number will depend on the specific choice. */
+
+intHash {alpha:Type} vector<coupleInt<alpha>> = IntHash<alpha>;
+strHash {alpha:Type} (vector (coupleStr alpha)) = StrHash alpha;
+intSortedHash {alpha:Type} intHash<alpha> = IntSortedHash<alpha>;
+strSortedHash {alpha:Type} (strHash alpha) = StrSortedHash alpha;
+
+// custom types
+pair x:Object y:Object = Pair;
+triple x:Object y:Object z:Object = Triple;
+
+user#d23c81a3 id:int first_name:string last_name:string = User;
+no_user#c67599d1 id:int = User;
+group id:int title:string last_name:string = Group;
+no_group = Group;
+
+---functions---
+
+// Maybe some built-in arithmetic functions; inverse quotes make "identifiers" out of arbitrary non-alphanumeric strings
+`+` Int Int = Int;
+`-` Int Int = Int;
+`+` Double Double = Double;
+// ...
+
+// API functions (aka RPC functions)
+getUser#b0f732d5 int = User;
+getUsers#2d84d5f5 (Vector int) = Vector User;
+

In this case, the user constructor has been explicitly assigned a number (0xd23c81a3); In fact, this was not necessary, since this value is the CRC32 of the string "user id:int first_name:string last_name:string = User", which would have been used by default.

+

Special constructors are not required for Vector int, Vector User, Vector Object, etc. -- the same universal constructor can be used everywhere:

+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;
+

Note that when the getUsers (Vector int) = Vector User; constructor number is calculated, the CRC32 of the string "getUsers Vector int = Vector User” is computed (from which all parentheses have been removed).

+

Notation T0<T1,T2,...,Tn> is syntactic sugar for (T0 (T1) (T2) ... (Tn)). For example, Vector<User> and (Vector User) are entirely interchangeable.

+

Example of an RPC query

+

Suppose we want to call getUsers([2,3,4]). This query will be serialized into a sequence of 32-bit integers as follows:

+
0x2d84d5f5 0x1cb5c415 0x3 0x2 0x3 0x4
+

Please note that TL serialization yields sequences of 32-bit integers. When it has to be embedded into a byte stream, for example a network packet, each 32-bit integer is represented by four bytes in little-endian order. In this way the above query corresponds to the following byte stream:

+
F5 D5 84 2D 15 C4 B5 1C 03 00 00 00 02 00 00 00 03 00 00 00 04 00 00 00
+

The response might look something like this:

+
0x1cb5c415 0x3 0xd23c81a3 0x2 0x74655005 0x00007265 0x72615006 0x72656b 0xc67599d1 0x3 0xd23c81a3 0x4 0x686f4a04 0x6e 0x656f4403
+

This roughly corresponds to

+
[{"id":2,"first_name":"Peter", "last_name":"Parker"},{},{"id":4,"first_name":"John","last_name":"Doe"}]
+

Note that in both cases the same universal constructor vector#1cb5c415 is used: in the request to serialize the value of type Vector int, and in the serialization of the value of type Vector User in the response. There is no ambiguity because in both cases the type of the value being (de)serialized is known before its (de)serialization begins. For example, after receiving the query, the server sees that the first part is 0x2d84d5f5, which corresponds to the combinator getUsers#2d84d5f5 (Vector int) = Vector User. Thus, it is understood that what follows will be a value of type Vector int. After receiving the response to this query, the client knows that it must receive a value of type Vector User and it deserializes the response accordingly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/auth_key.html b/data/core.telegram.org/mtproto/auth_key.html new file mode 100644 index 0000000000..4b54a1fdaa --- /dev/null +++ b/data/core.telegram.org/mtproto/auth_key.html @@ -0,0 +1,262 @@ + + + + + Creating an Authorization Key + + + + + + + + + + + + + +
+ +
+
+
+ +

Creating an Authorization Key

+ +

The query format is described using Binary Data Serialization and the TL Language. All large numbers are transmitted as strings containing the required sequence of bytes in big endian order. Hash functions, such as SHA1, return strings (of 20 bytes) which can also be interpreted as big endian numbers. Small numbers (int, long, int128, int256) are normally little endian; however, if they are part of SHA1, the bytes are not rearranged. This way, if long x is the 64 lower-order bits of SHA1 of string s, then the final 8 bytes of 20-byte string SHA1(s) are taken and interpreted as a 64-bit integer.

+

Prior to sending off unencrypted messages (required in this instance to generate an authorization key), the client must undergo (p,q) authorization as follows.

+

DH exchange initiation

+
    +
  1. +

    Client sends query to server

    +

    req_pq_multi#be7e8ef1 nonce:int128 = ResPQ;

    +
  2. +
+

The value of nonce is selected randomly by the client (random number) and identifies the client within this communication. Following this step, it is known to all.

+
    +
  1. +

    Server sends response of the form

    +

    resPQ#05162463 nonce:int128 server_nonce:int128 pq:string server_public_key_fingerprints:Vector long = ResPQ;

    +
  2. +
+

Here, string pq is a representation of a natural number (in binary big endian format). This number is the product of two different odd prime numbers. Normally, pq is less than or equal to 2^63-1. The value of server_nonce is selected randomly by the server; following this step, it is known to all.

+

server_public_key_fingerprints is a list of public RSA key fingerprints (64 lower-order bits of SHA1 (server_public_key); the public key is represented as a bare type rsa_public_key n:string e:string = RSAPublicKey, where, as usual, n and е are numbers in big endian format serialized as strings of bytes, following which SHA1 is computed) received by the server.

+

All subsequent messages contain the pair (nonce, server_nonce) both in the plain-text, and the encrypted portions which makes it possible to identify a “temporary session” — one run of the key generation protocol described on this page that uses the same (nonce, server_nonce) pair. An intruder could not create a parallel session with the server with the same parameters and reuse parts of server- or client-encrypted messages for its own purposes in such a parallel session, because a different server_nonce would be selected by the server for any new “temporary session”.

+

Proof of work

+
    +
  1. Client decomposes pq into prime factors such that p < q.
  2. +
+

This starts a round of Diffie-Hellman key exchanges.

+

Presenting proof of work; Server authentication

+
    +
  1. +

    Client sends query to server

    +

    req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:string q:string public_key_fingerprint:long encrypted_data:string = Server_DH_Params

    +
  2. +
+

Here, encrypted_data is obtained as follows:

+
    +
  • +

    new_nonce := another (good) random number generated by the client; after this query, it is known to both client and server;

    +
  • +
  • +

    data := a serialization of

    +
    p_q_inner_data_dc#a9f55f95 pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 dc:int = P_Q_inner_data;
    +

    or of

    +
    p_q_inner_data_temp_dc#56fddf88 pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 dc:int expires_in:int = P_Q_inner_data;
    +
  • +
  • +

    encrypted_data := RSA_PAD (data, server_public_key), where RSA_PAD is a version of RSA with a variant of OAEP+ padding explained below in 4.1).

    +
  • +
+

Someone might intercept the query and replace it with their own, independently decomposing pq into factors instead of the client. The only field that it makes sense to modify is new_nonce which would be the one an intruder would have to re-generate (because an intruder cannot decrypt the encrypted data sent by the client). Since all subsequent messages are encrypted using new_nonce or contain new_nonce_hash, they will not be processed by the client (an intruder would not be able to make it look as though they had been generated by the server because they would not contain new_nonce). Therefore, this intercept will only result in the intruder’s completing the authorization key generation protocol in place of the client and creating a new key (that has nothing to do with the client); however, the same effect could be achieved simply by creating a new key in one's own name.

+

An alternative form of inner data (p_q_inner_data_temp_dc) is used to create temporary keys, that are only stored in the server RAM and are discarded after at most expires_in seconds. The server is free to discard its copy earlier. In all other respects the temporary key generation protocol is the same. After a temporary key is created, the client usually binds it to its principal authorisation key by means of the auth.bindTempAuthKey method, and uses it for all client-server communication until it expires; then a new temporary key is generated. Thus Perfect Forward Secrecy (PFS) in client-server communication is achieved. Read more about PFS »

+

4.1) RSA_PAD(data, server_public_key) mentioned above is implemented as follows:

+
    +
  • data_with_padding := data + random_padding_bytes; -- where random_padding_bytes are chosen so that the resulting length of data_with_padding is precisely 192 bytes, and data is the TL-serialized data to be encrypted as before. One has to check that data is not longer than 144 bytes.
  • +
  • data_pad_reversed := BYTE_REVERSE(data_with_padding); -- is obtained from data_with_padding by reversing the byte order.
  • +
  • a random 32-byte temp_key is generated.
  • +
  • data_with_hash := data_pad_reversed + SHA256(temp_key + data_with_padding); -- after this assignment, data_with_hash is exactly 224 bytes long.
  • +
  • aes_encrypted := AES256_IGE(data_with_hash, temp_key, 0); -- AES256-IGE encryption with zero IV.
  • +
  • temp_key_xor := temp_key XOR SHA256(aes_encrypted); -- adjusted key, 32 bytes
  • +
  • key_aes_encrypted := temp_key_xor + aes_encrypted; -- exactly 256 bytes (2048 bits) long
  • +
  • The value of key_aes_encrypted is compared with the RSA-modulus of server_pubkey as a big-endian 2048-bit (256-byte) unsigned integer. If key_aes_encrypted turns out to be greater than or equal to the RSA modulus, the previous steps starting from the generation of new random temp_key are repeated. Otherwise the final step is performed:
  • +
  • encrypted_data := RSA(key_aes_encrypted, server_pubkey); -- 256-byte big-endian integer is elevated to the requisite power from the RSA public key modulo the RSA modulus, and the result is stored as a big-endian integer consisting of exactly 256 bytes (with leading zero bytes if required).
  • +
+
    +
  1. +

    Server responds with:

    +

    server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:string = Server_DH_Params;

    +
  2. +
+
+

If the query is incorrect, the server returns a -404 error and the handshake must be restarted (any subsequent request also returns -404, even if it is correct).

+
+

Here, encrypted_answer is obtained as follows:

+
    +
  • +

    new_nonce_hash := 128 lower-order bits of SHA1 (new_nonce);

    +
  • +
  • +

    answer := serialization

    +
      server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:string g_a:string server_time:int = Server_DH_inner_data;
    +
  • +
  • +

    answer_with_hash := SHA1(answer) + answer + (0-15 random bytes); such that the length be divisible by 16;

    +
  • +
  • +

    tmp_aes_key := SHA1(new_nonce + server_nonce) + substr (SHA1(server_nonce + new_nonce), 0, 12);

    +
  • +
  • +

    tmp_aes_iv := substr (SHA1(server_nonce + new_nonce), 12, 8) + SHA1(new_nonce + new_nonce) + substr (new_nonce, 0, 4);

    +
  • +
  • +

    encrypted_answer := AES256_ige_encrypt (answer_with_hash, tmp_aes_key, tmp_aes_iv); here, tmp_aes_key is a 256-bit key, and tmp_aes_iv is a 256-bit initialization vector. The same as in all the other instances that use AES encryption, the encrypted data is padded with random bytes to a length divisible by 16 immediately prior to encryption.

    +
  • +
+

Following this step, new_nonce is still known to client and server only. The client is certain that it is the server that responded and that the response was generated specifically in response to client query req_DH_params, since the response data are encrypted using new_nonce.

+

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

+

If the verification takes too long time (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations later in the background.

+

Another optimization is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. Server changes these values rarely, thus one usually has to put the current value of server's dh_prime into such a table. For example, current value of dh_prime equals (in big-endian byte order)

+
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
+
    +
  1. +

    Client computes random 2048-bit number b (using a sufficient amount of entropy) and sends the server a message

    +

    set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:string = Set_client_DH_params_answer;

    +
  2. +
+

Here, encrypted_data is obtained thus:

+
    +
  • +

    g_b := pow(g, b) mod dh_prime;

    +
  • +
  • +

    data := serialization

    +
      client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:string = Client_DH_Inner_Data
    +
  • +
  • +

    data_with_hash := SHA1(data) + data + (0-15 random bytes); such that length be divisible by 16;

    +
  • +
  • +

    encrypted_data := AES256_ige_encrypt (data_with_hash, tmp_aes_key, tmp_aes_iv);

    +
  • +
+

The retry_id field is equal to zero at the time of the first attempt; otherwise, it is equal to auth_key_aux_hash from the previous failed attempt (see Item 9).

+
    +
  1. +

    Thereafter, auth_key equals pow(g, {ab}) mod dh_prime; on the server, it is computed as pow(g_b, a) mod dh_prime, and on the client as (g_a)^b mod dh_prime.

    +
  2. +
  3. +

    auth_key_hash is computed := 64 lower-order bits of SHA1 (auth_key). The server checks whether there already is another key with the same auth_key_hash and responds in one of the following ways.

    +
  4. +
+

DH key exchange complete

+
    +
  1. +

    Server responds in one of three ways:

    +

    dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer; +dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer; +dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;

    +
  2. +
+
    +
  • new_nonce_hash1, new_nonce_hash2, and new_nonce_hash3 are obtained as the 128 lower-order bits of SHA1 of the byte string derived from the new_nonce string by adding a single byte with the value of 1, 2, or 3, and followed by another 8 bytes with auth_key_aux_hash. Different values are required to prevent an intruder from changing server response dh_gen_ok into dh_gen_retry.
  • +
  • auth_key_aux_hash is the 64 higher-order bits of SHA1(auth_key). It must not be confused with auth_key_hash.
  • +
+

In the other case, the client goes to Item 6) generating a new b. +In the first case, the client and the server have negotiated auth_key, following which they forget all other temporary data, and the client creates another encrypted session using auth_key. At the same time, server_salt is initially set to substr(new_nonce, 0, 8) XOR substr(server_nonce, 0, 8). If required, the client stores the difference between server_time received in 5) and its local time, to be able always to have a good approximation of server time which is required to generate correct message identifiers.

+

IMPORTANT: Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

+

Error Handling (Lost Queries and Responses)

+

If the client fails to receive any response to its query from the server within a certain time interval, it may simply re-send the query. If the server has already sent a response to this query (exactly the same request and not just similar: all the parameters during the repeat request must take on the same values) but it did not get to the client, the server will simply re-send the same response. The server remembers the response for up to 10 minutes after having received the query in 1). If the server has already forgotten the response or the requisite temporary data, the client will have to start from the beginning.

+

The server may consider that if the client has already sent in the next query using the data from the previous server response to the specific client, the response is known to have been received by the client and may be forgotten by the server.

+

Usage Example

+

An example of a complete list of queries required to generate an authorization key is shown on a separate page.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/description.html b/data/core.telegram.org/mtproto/description.html new file mode 100644 index 0000000000..7c5054cdcf --- /dev/null +++ b/data/core.telegram.org/mtproto/description.html @@ -0,0 +1,238 @@ + + + + + Mobile Protocol: Detailed Description + + + + + + + + + + + + + +
+ +
+
+
+ +

Mobile Protocol: Detailed Description

+ +
+ +
+

As of version 4.6, major Telegram clients are using MTProto 2.0. +MTProto v.1.0 is deprecated and is currently being phased out.

+
+

This article describes the basic layer of the MTProto protocol version 2.0 (Cloud chats, server-client encryption). The principal differences from version 1.0 (described here for reference) are as follows:

+
    +
  • SHA-256 is used instead of SHA-1;
  • +
  • Padding bytes are involved in the computation of msg_key;
  • +
  • msg_key depends not only on the message to be encrypted, but on a portion of auth_key as well;
  • +
  • 12..1024 padding bytes are used instead of 0..15 padding bytes in v.1.0.
  • +
+

See also: MTProto 2.0: Secret Chats, end-to-end encryption

+

Protocol description

+

Before a message (or a multipart message) is transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message that consists of a 64-bit key identifier auth_key_id (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key msg_key.

+

The authorization key auth_key combined with the message key msg_key define an actual 256-bit key aes_key and a 256-bit initialization vector aes_iv, which are used to encrypt the message using AES-256 encryption in infinite garble extension (IGE) mode. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). In MTProto 2.0, the message key is defined as the 128 middle bits of the SHA-256 of the message body (including session, message ID, padding, etc.) prepended by 32 bytes taken from the authorization key. In the older MTProto 1.0, the message key was computed as the lower 128 bits of SHA-1 of the message body, excluding the padding bytes.

+

Multipart messages are encrypted as a single message.

+ +
+

Got questions about this setup? — Check out the Advanced FAQ!

+
+
Note 1
+

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

+
    +
  • server salt (64-Bit)
  • +
  • session id
  • +
  • message sequence number
  • +
  • message length
  • +
  • time
  • +
+
Note 2
+

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

+

Terminology

+

Authorization Key (auth_key)

+

A 2048-bit key shared by the client device and the server, created upon user registration directly on the client device by exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

+

Server Key

+

A 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

+

Key Identifier (auth_key_id)

+

The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key in a Diffie-Hellman exchange. For MTProto 2.0, SHA1 is still used here, because auth_key_id should identify the authorization key used independently of the protocol version.

+

Session

+

A (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

+

Server Salt

+

A (random) 64-bit number changed every 30 minutes (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 1800 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

+

Message Identifier (msg_id)

+

A (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

+

Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created.

+

Content-related Message

+

A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

+

Message Sequence Number (msg_seqno)

+

A 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

+

Message Key (msg_key)

+

In MTProto 2.0, the middle 128 bits of the SHA-256 hash of the message to be encrypted (including the internal header and the padding bytes for MTProto 2.0), prepended by a 32-byte fragment of the authorization key.

+

In MTProto 1.0, message key was defined differently, as the lower 128 bits of the SHA-1 hash of the message to be encrypted, with padding bytes excluded from the computation of the hash. Authorization key was not involved in this computation.

+

Internal (cryptographic) Header

+

A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

+

External (cryptographic) Header

+

A header (24 bytes) added before an encrypted message or a container. Consists of the key identifier auth_key_id (64 bits) and the message key msg_key (128 bits).

+

Payload

+

External header + encrypted message or container.

+

Defining AES Key and Initialization Vector

+

The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header that is added later) with AES-256 in infinite garble extension (IGE) mode.

+

For MTProto 2.0, the algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows.

+
    +
  • msg_key_large = SHA256 (substr (auth_key, 88+x, 32) + plaintext + random_padding);
  • +
  • msg_key = substr (msg_key_large, 8, 16);
  • +
  • sha256_a = SHA256 (msg_key + substr (auth_key, x, 36));
  • +
  • sha256_b = SHA256 (substr (auth_key, 40+x, 36) + msg_key);
  • +
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • +
  • aes_iv = substr (sha256_b, 0, 8) + substr (sha256_a, 8, 16) + substr (sha256_b, 24, 8);
  • +
+

where x = 0 for messages from client to server and x = 8 for those from server to client.

+

For the obsolete MTProto 1.0, msg_key, aes_key, and aes_iv were computed differently (see this document for reference).

+

The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

+

In MTProto 1.0, when AES was used to encrypt a block of data of a length not divisible by 16 bytes, the data was padded with 0 to 15 random padding bytes random_padding to a length divisible by 16 bytes prior to encryption. In MTProto 2.0, this padding is taken into account when computing msg_key. Note that MTProto 2.0 requires from 12 to 1024 bytes of padding, still subject to the condition that the resulting message length be divisible by 16 bytes.

+

Using MTProto 2.0 instead of MTProto 1.0

+

A client may either use only MTProto 2.0 or only MTProto 1.0 in the same TCP connection. The server detects the protocol used by the first message received from the client, and then uses the same encryption for its messages, and expects the client to use the same encryption henceforth. We recommend using MTProto 2.0; MTProto 1.0 is deprecated and supported for backward compatibility only.

+

Important Checks

+

When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 middle bits of the SHA-256 of the decrypted data with a 32-byte fragment of auth_key prepended to it, and that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with msg_id lower than all or equal to any of the stored values, the message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is forgotten.

+

On top of this, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications of invalid client time. See Mobile Protocol: Service Messages.

+

Storing an Authorization Key on a Client Device

+

It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This can be accomplished by prepending the value of cryptographic hash function, such as SHA-256, of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by checking the SHA-256 value. From the user’s standpoint, this is practically the same as using an application or a website password.

+

Unencrypted Messages

+

Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

+

Only a very limited number of messages of special types can be transmitted as plain text.

+

Schematic Presentation of Messages

+

Encrypted Message

+ + + + +
auth_key_id
int64
msg_key
int128
encrypted_data
bytes
+

Encrypted Message: encrypted_data

+

Contains the cypher text for the following data:

+ + + + + + + + +
salt
int64
session_id
int64
message_id
int64
seq_no
int32
message_data_length
int32
message_data
bytes
padding12..1024
bytes
+

Unencrypted Message

+ + + + + +
auth_key_id = 0
int64
message_id
int64
message_data_length
int32
message_data
bytes
+

MTProto 2.0 uses 12..1024 padding bytes, instead of the 0..15 used in MTProto 1.0

+

Creating an Authorization Key

+

An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

+

See Creating an Authorization Key.

+

During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/mtproto/description_v1.html b/data/core.telegram.org/mtproto/description_v1.html new file mode 100644 index 0000000000..73c7fb0de0 --- /dev/null +++ b/data/core.telegram.org/mtproto/description_v1.html @@ -0,0 +1,205 @@ + + + + + Mobile Protocol: Detailed Description (v.1.0, DEPRECATED) + + + + + + + + + + + + + +
+ +
+
+
+ +

Mobile Protocol: Detailed Description (v.1.0, DEPRECATED)

+ +
+

This document describes MTProto v.1.0, its status is DEPRECATED. +For information on encryption used in up-to-date Telegram clients, kindly see this document.

+
+

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key.

+

A user key together with the message key define an actual 256-bit key and a 256-bit initialization vector, which is what encrypts the message using AES-256 encryption with infinite garble extension (IGE). Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.) Multipart messages are encrypted as a single message.

+ +

Terminology

+

Authorization Key

+

a 2048-bit key shared by the client device and the server, created upon user registration directly on the client device be exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

+

Server Key

+

a 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

+

Key Identifier

+

The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key based on a Diffie-Hellman exchange.

+

Session

+

a (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

+

Server Salt

+

a (random) 64-bit number periodically (say, every 24 hours) changed (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 300 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

+

Message Identifier (msg_id)

+

a (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

+

Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created. At some point in the nearest future the server will start ignoring messages, in which the lower 32 bits of msg_id contain too many zeroes.

+

Content-related Message

+

A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

+

Message Sequence Number (msg_seqno)

+

a 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

+

Message Key

+

The lower-order 128 bits of the SHA1 hash of the part of the message to be encrypted (including the internal header and excluding the alignment bytes).

+

Internal (cryptographic) Header

+

A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

+

External (cryptographic) Header

+

A header (24 bytes) added before an encrypted message or a container. Consists of a key identifier (64 bits) and a message key (128 bits).

+

Payload

+

External header + encrypted message or container.

+

Defining AES Key and Initialization Vector

+

The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header which is added later) with AES-256 in infinite garble extension (IGE) mode.

+

The algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows:

+
    +
  • msg_key = substr (SHA1 (plaintext), 4, 16);
  • +
  • sha1_a = SHA1 (msg_key + substr (auth_key, x, 32));
  • +
  • sha1_b = SHA1 (substr (auth_key, 32+x, 16) + msg_key + substr (auth_key, 48+x, 16));
  • +
  • sha1_с = SHA1 (substr (auth_key, 64+x, 32) + msg_key);
  • +
  • sha1_d = SHA1 (msg_key + substr (auth_key, 96+x, 32));
  • +
  • aes_key = substr (sha1_a, 0, 8) + substr (sha1_b, 8, 12) + substr (sha1_c, 4, 12);
  • +
  • aes_iv = substr (sha1_a, 8, 12) + substr (sha1_b, 0, 8) + substr (sha1_c, 16, 4) + substr (sha1_d, 0, 8);
  • +
+

where x = 0 for messages from client to server and x = 8 for those from server to client.

+

The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

+

When AES is used to encrypt a block of data of a length not divisible by 16 bytes, the data is padded with random bytes to the smallest length divisible by 16 bytes immediately prior to being encrypted.

+

Important Tests

+

When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 lower-order bits of the SHA1 hash of the previously encrypted portion, and that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with msg_id lower than all or equal to any of the stored values, the message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is forgotten.

+

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications of invalid client time. See Mobile Protocol: Service Messages.

+

Storing an Authorization Key on a Client Device

+

It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This is accomplished by adding the SHA1 of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by being compared with SHA1. From the user’s standpoint, this is practically the same as using an application or a website password.

+

Unencrypted Messages

+

Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

+

Only a very limited number of messages of special types can be transmitted as plain text.

+

Schematic Presentation of Messages

+

Encrypted Message

+ + + + +
auth_key_id
int64
msg_key
int128
encrypted_data
bytes
+

Encrypted Message: encrypted_data

+

Contains the cypher text for the following data:

+ + + + + + + + +
salt
int64
session_id
int64
message_id
int64
seq_no
int32
message_data_length
int32
message_data
bytes
padding 0..15
bytes
+

Unencrypted Message

+ + + + + +
auth_key_id = 0
int64
message_id
int64
message_data_length
int32
message_data
bytes
+

Creating an Authorization Key

+

An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

+

See Creating an Authorization Key.

+

During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/mtproto-transports.html b/data/core.telegram.org/mtproto/mtproto-transports.html new file mode 100644 index 0000000000..838d121472 --- /dev/null +++ b/data/core.telegram.org/mtproto/mtproto-transports.html @@ -0,0 +1,280 @@ + + + + + MTProto transports + + + + + + + + + + + + + +
+ +
+
+
+ +

MTProto transports

+ +
+ +

Here's a list of MTProto transport protocols (see the ISO/OSI recap for a full explanation):

+ +

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header.
Additionally, the following transport features can be used:

+ +

Example implementations for these protocols can be seen in tdlib and MadelineProto.

+

Abridged

+

The lightest protocol available.

+
    +
  • Overhead: Very small
  • +
  • Minimum envelope length: 1 byte
  • +
  • Maximum envelope length: 4 bytes
  • +
+

Payload structure:

+
+-+----...----+
+|l|  payload  |
++-+----...----+
+OR
+
++-+---+----...----+
+|h|len|  payload  +
++-+---+----...----+
+

Before sending anything into the underlying socket (see transports), the client must first send 0xef as the first byte (the server will not send 0xef as the first byte in the first reply).
Then, payloads are wrapped in the following envelope:

+
    +
  • Length: payload length, divided by four, and encoded as a single byte, only if the resulting packet length is a value between 0x01..0x7e.
  • +
  • Payload: the MTProto payload
  • +
+

If the packet length divided by four is bigger than or equal to 127 (>= 0x7f), the following envelope must be used, instead:

+
    +
  • Header: A single byte of value 0x7f
  • +
  • Length: payload length, divided by four, and encoded as 3 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
+

Intermediate

+

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used.

+
    +
  • Overhead: small
  • +
  • Minimum envelope length: 4 bytes
  • +
  • Maximum envelope length: 4 bytes
  • +
+

Payload structure:

+
+----+----...----+
++len.+  payload  +
++----+----...----+
+

Before sending anything into the underlying socket (see transports), the client must first send 0xeeeeeeee as the first int (four bytes, the server will not send 0xeeeeeeee as the first int in the first reply).
Then, payloads are wrapped in the following envelope:

+
    +
  • Length: payload length encoded as 4 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
+

Padded intermediate

+

Padded version of the intermediate protocol, to use with obfuscation enabled to bypass ISP blocks.

+
    +
  • Overhead: small-medium
  • +
  • Minimum envelope length: random
  • +
  • Maximum envelope length: random
  • +
+

Before sending anything into the underlying socket (see transports), the client must first send 0xdddddddd as the first int (four bytes, the server will not send 0xdddddddd as the first int in the first reply).
Then, payloads are wrapped in the following envelope:

+
+----+----...----+----...----+
+|tlen|  payload  |  padding  |
++----+----...----+----...----+
+

Envelope description:

+
    +
  • Total length: payload+padding length encoded as 4 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
  • Padding: A random padding string of length 0-15
  • +
+

Full

+

The basic MTProto transport protocol

+
    +
  • Overhead: medium
  • +
  • Minimum envelope length: 12 bytes (length+seqno+crc)
  • +
  • Maximum envelope length: 12 bytes (length+seqno+crc)
  • +
+

Payload structure:

+
+----+----+----...----+----+
+|len.|seq.|  payload  |crc.|
++----+----+----...----+----+
+

Envelope description:

+
    +
  • Length: length+seqno+payload+crc length encoded as 4 length bytes (little endian, the length of the length field must be included, too)
  • +
  • Seqno: the TCP sequence number for this TCP connection (different from the MTProto sequence number): the first packet sent is numbered 0, the next one 1, etc.
  • +
  • payload: MTProto payload
  • +
  • crc: 4 CRC32 bytes computed using length, sequence number, and payload together.
  • +
+

Transport features

+

Additionally, the following transport features can be used:

+

Quick ack

+

These MTProto transport protocols have support for quick acknowledgment.
In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet.
They are the 32 higher-order bits of SHA256 of the encrypted portion of the packet prepended by 32 bytes from the authorization key (the same hash as computed for verifying the message key), with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

+

Transport errors

+

In the event of a transport error (missing auth key, transport flood, etc.), the server may send a packet with a signed little-endian number of 4 bytes, whose absolute value contains the error code (the error itself is actually negative).

+

For example, error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

+

Error 404 (auth key not found) is returned when the specified auth key ID cannot be found by the DC.

+

Error 429 (transport flood) is returned when too many transport connections are established to the same IP in a too short lapse of time, or if any of the container/service message limits are reached.

+

Transport obfuscation

+

Transport obfuscation is required to use the websocket transports.

+

Transport obfuscation to prevent ISP blocks is implemented using the following protocol, situated under the MTProto transport in the ISO/OSI stack, see the recap; this means that the payload is first wrapped in the MTProto transport envelope (all transports are supported), and then obfuscated:

+

Prior to establishing the connection (and eventually sending the protocol header of a specific MTProto transport), a 64-byte (512-bit) random initialization payload is generated.
During the generation process, special care must be taken in order to avoid a situation where that the first int (first four bytes) of the random string are equal to one of the known protocol identifiers (see above).
In particular, the first four bytes must not be equal to 0xdddddddd (padded intermediate), 0xeeeeeeee (intermediate), POST, GET, HEAD, or any of the HTTP methods that are accepted by the MTProto servers.
The first byte must also not be equal to 0xef (abridged).
Bytes 4-8 must also not be equal to 0x00000000, since that would indicate use of the full transport with the initial TCP sequence number (0).

+

The protocol identifier, if present, must be inserted in the initialization payload at byte offset 56: if its length is less than 4, it must be padded using the protocol identifier itself, to make its length 4 (0xef => 0xefefefef): the standalone protocol identifier must be not be sent aftwerwards.

+

This protocol is also (but not exclusively) used when connecting to MTProxies: only in this case, the DC ID in a specially encoded form must also be inserted in the initialization payload at offset 60.
The encoding simply consist of the DC ID in two-byte signed little-endian form; 10000 has to be added to the DC ID to connect to the test servers; it has to be made negative if the DC we're connecting to is a media (not CDN) DC.

+

Next, a secondary initialization payload is generated by reversing the primary initialization payload.

+

Two keys are extracted from both initialization payloads, using bytes at offsets 8-40: the key extracted from the primary payload is used as encryption key, the key extracted from the secondary payload is used as decryption key.

+

Two IVs are extracted from both initialization payloads, using bytes at offsets 40-56: the IV extracted from the primary payload is used as encryption IV, the IV extracted from the secondary payload is used as decryption IV.

+

Only if using MTProxy, the secret is used to provide connection with the MTProxy server.
The secret is a 16-byte string, usually distributed in its hexadecimal form along with the MTProxy host and port.

+

Often, a 17-byte version of the secret can be found: this simply indicates that the client should use a specific MTProto transport (based on the first byte, usually it's 0xdd, to indicate that the padded intermediate protocol should be used 0xdddddddd; however, clients should default to the padded intermediate transport whenever an additional byte in the secret is encountered).

+

The extracted encryption and decryption keys must be concatenated with the secret (the first byte of which should be ignored if it's the 17-byte version), and the SHA256 hash of such string should be used as encryption/decryption key.

+

The obtained encryption and decryption key/IV pairs must then be used with AES-256-CTR to encrypt and decrypt all outgoing and incoming payloads.

+

The first thing that must be encrypted using the encryption key is the initialization payload itself.
Then bytes 56-64 of the encrypted initialization payload are substituted in the original initialization payload: this is the part that contains the constant MTProto transport protocol identifier and the DC ID (only for MTProxies).

+

The final initialization payload must then be sent in the socket as first 64 bytes after the TCP handshake.

+

Example pseudocode for the generation of an MTProxy connection payload (media DC 4) using the obfuscated padded intermediate transport.
Warning: do not use the specified proxy secret in any MTProxy exposed on the internet.

+
protocol := 0xdddddddd
+dc := 0xfcff
+
+while 1:
+    init := (56 random bytes) + protocol + dc + (2 random bytes)
+
+    if init[0] == 0xef:
+      continue
+
+    first_int := substr(init, 0, 4)
+    if first_int == 0x44414548 || first_int == 0x54534f50 || first_int == 0x20544547 || first_int == 0x4954504f || first_int == 0x02010316 || first_int == 0xdddddddd || first_int == 0xeeeeeeee:
+      continue
+
+    second_int := substr(init, 4, 4)
+    if second_int == 0x00000000:
+      continue
+
+    break
+
+initRev := strrev(init)
+
+encryptKey := substr(init, 8, 32)
+encryptIV := substr(init, 40, 16)
+
+decryptKey := substr(initRev, 8, 32)
+decryptIV := substr(initRev, 40, 16)
+
+secret := substr(0xdd99999999999999999999999999999999, 1, 16)
+
+encryptKey = SHA256(encryptKey + secret)
+decryptKey = SHA256(decryptKey + secret)
+
+encryptedInit := CTR(encryptKey, encryptIV, init)
+
+finalInit := substr(init, 0, 56) + substr(encryptedInit, 56, 8)
+
+write(finalInit)
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/mtproto/samples-auth_key.html b/data/core.telegram.org/mtproto/samples-auth_key.html new file mode 100644 index 0000000000..e327ea0f77 --- /dev/null +++ b/data/core.telegram.org/mtproto/samples-auth_key.html @@ -0,0 +1,748 @@ + + + + + samples-auth_key + + + + + + + + + + + + + +
+ +
+
+
+ +

samples-auth_key

+ +

In the examples below, the transport headers are omitted:

+
+

For example, for an abridged version of the transport the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01-0x7e = data length divided by 4; or 0x7f followed by 3 bytes (little endian) divided by 4) followed by the data themselves. In this case, server responses have the same form (although the server does not send 0xefas the first byte).

+
+

Detailed documentation on creating authorization keys is available here ».

+

1. Request for (p,q) Authorization

+
req_pq#60469778 nonce:int128 = ResPQ
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac42770964aExact unixtime * 2^32
message_length16, 420Message body length
%(req_pq)20, 460469778req_pq constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCRandom number
+

The header is 20 bytes long, the message body is 20 bytes long, and the entire message is 40 bytes in length.

+
0000 | 00 00 00 00 00 00 00 00 4A 96 70 27 C4 7A E5 51
+0010 | 14 00 00 00 78 97 46 60 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC
+

2. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 C8 83 1E C9 7A E5 51
+0010 | 40 00 00 00 63 24 16 05 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 08 17 ED 48 94 1A 08 F9
+0040 | 81 00 00 00 15 C4 B5 1C 01 00 00 00 21 6B E8 6C
+0050 | 02 2B B4 C3
+
Response decomposition using the following formula:
+
resPQ#05162463 nonce:int128 server_nonce:int128 pq:string server_public_key_fingerprints:Vector long = ResPQ 
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57AC91E83C801Server message ID
message_length16, 464Message body length
%(resPQ)20, 405162463resPQ constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Server-generated random number
pq56, 1217ED48941A08F981Single-byte prefix denoting length, an 8-byte string, and three bytes of padding
%(Vector long)68, 41cb5c415Vector long constructor number from TL schema
count72, 41Number of elements in key fingerprint list
fingerprints[]76, 8c3b42b026ce86b2164 lower-order bits of SHA1 (server_public_key)
+

The server_public_key public key has been selected whose fingerprint corresponds to the only one received from the server: c3b42b026ce86b21.

+

3. Pq = 17ED48941A08F981 decomposed into 2 prime cofactors:

+
p = 494C553B
+q = 53911073
+

4. encrypted_data Generation

+
p_q_inner_data#83c95aec pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 = P_Q_inner_data
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(p_q_inner_data)0, 483c95aecp_q_inner_data constructor number from TL schema
pq4, 1217ED48941A08F981Single-byte prefix denoting length, 8-byte string, and three bytes of padding
p16, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q24, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
nonce32, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce48, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce64, 32311C85DB234AA2640AFC4A76A735CF5B 1F0FD68BD17FA181E1229AD867CC024DClient-generated random number
+

The serialization of P_Q_inner_data produces some string data. This is followed by encrypted_data:

+
SHA1 (data) = DB761C27718A2305044F71F2AD951629D78B2449
+RSA (data_with_hash, server_public_key) = 7BB0100A523161904D9C69FA04BC60DECFC5DD74B99995C768EB60D8716E2109BAF2D4601DAB6B09610DC11067BB89021E09471FCFA52DBD0F23204AD8CA8B012BF40A112F44695AB6C266955386114EF5211E6372227ADBD34995D3E0E5FF02EC63A43F9926878962F7C570E6A6E78BF8366AF917A5272675C46064BE62E3E202EFA8B1ADFB1C32A898C2987BE27B5F31D57C9BB963ABCB734B16F652CEDB4293CBB7C878A3A3FFAC9DBEA9DF7C67BC9E9508E111C78FC46E057F5C65ADE381D91FEE430A6B576A99BDF8551FDB1BE2B57069B1A45730618F27427E8A04720B4971EF4A9215983D68F2830C3EAA6E40385562F970D38A05C9F1246DC33438E6
+

The length of the final string was 256 bytes.

+
Request to Start Diffie-Hellman Key Exchange
+
req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:string q:string public_key_fingerprint:long encrypted_data:string = Server_DH_Params
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac917717a27Exact unixtime * 2^32
message_length16, 4320Message body length
%(req_DH_params)20, 4d712e4bereq_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
p56, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q64, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
public_key_fingerprint72, 8c3b42b026ce86b21Fingerprint of public key used
encrypted_data80, 260See aboveSee “Generation of encrypted_data"
+
0000 | 00 00 00 00 00 00 00 00 27 7A 71 17 C9 7A E5 51
+0010 | 40 01 00 00 BE E4 12 D7 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 04 49 4C 55 3B 00 00 00
+0040 | 04 53 91 10 73 00 00 00 21 6B E8 6C 02 2B B4 C3
+0050 | FE 00 01 00 7B B0 10 0A 52 31 61 90 4D 9C 69 FA
+0060 | 04 BC 60 DE CF C5 DD 74 B9 99 95 C7 68 EB 60 D8
+0070 | 71 6E 21 09 BA F2 D4 60 1D AB 6B 09 61 0D C1 10
+0080 | 67 BB 89 02 1E 09 47 1F CF A5 2D BD 0F 23 20 4A
+0090 | D8 CA 8B 01 2B F4 0A 11 2F 44 69 5A B6 C2 66 95
+00A0 | 53 86 11 4E F5 21 1E 63 72 22 7A DB D3 49 95 D3
+00B0 | E0 E5 FF 02 EC 63 A4 3F 99 26 87 89 62 F7 C5 70
+00C0 | E6 A6 E7 8B F8 36 6A F9 17 A5 27 26 75 C4 60 64
+00D0 | BE 62 E3 E2 02 EF A8 B1 AD FB 1C 32 A8 98 C2 98
+00E0 | 7B E2 7B 5F 31 D5 7C 9B B9 63 AB CB 73 4B 16 F6
+00F0 | 52 CE DB 42 93 CB B7 C8 78 A3 A3 FF AC 9D BE A9
+0100 | DF 7C 67 BC 9E 95 08 E1 11 C7 8F C4 6E 05 7F 5C
+0110 | 65 AD E3 81 D9 1F EE 43 0A 6B 57 6A 99 BD F8 55
+0120 | 1F DB 1B E2 B5 70 69 B1 A4 57 30 61 8F 27 42 7E
+0130 | 8A 04 72 0B 49 71 EF 4A 92 15 98 3D 68 F2 83 0C
+0140 | 3E AA 6E 40 38 55 62 F9 70 D3 8A 05 C9 F1 24 6D
+0150 | C3 34 38 E6
+

5. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 54 43 36 CB 7A E5 51
+0010 | 78 02 00 00 5C 07 E8 D0 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 FE 50 02 00 28 A9 2F E2
+0040 | 01 73 B3 47 A8 BB 32 4B 5F AB 26 67 C9 A8 BB CE
+0050 | 64 68 D5 B5 09 A4 CB DD C1 86 24 0A C9 12 CF 70
+0060 | 06 AF 89 26 DE 60 6A 2E 74 C0 49 3C AA 57 74 1E
+0070 | 6C 82 45 1F 54 D3 E0 68 F5 CC C4 9B 44 44 12 4B
+0080 | 96 66 FF B4 05 AA B5 64 A3 D0 1E 67 F6 E9 12 86
+0090 | 7C 8D 20 D9 88 27 07 DC 33 0B 17 B4 E0 DD 57 CB
+00A0 | 53 BF AA FA 9E F5 BE 76 AE 6C 1B 9B 6C 51 E2 D6
+00B0 | 50 2A 47 C8 83 09 5C 46 C8 1E 3B E2 5F 62 42 7B
+00C0 | 58 54 88 BB 3B F2 39 21 3B F4 8E B8 FE 34 C9 A0
+00D0 | 26 CC 84 13 93 40 43 97 4D B0 35 56 63 30 38 39
+00E0 | 2C EC B5 1F 94 82 4E 14 0B 98 63 77 30 A4 BE 79
+00F0 | A8 F9 DA FA 39 BA E8 1E 10 95 84 9E A4 C8 34 67
+0100 | C9 2A 3A 17 D9 97 81 7C 8A 7A C6 1C 3F F4 14 DA
+0110 | 37 B7 D6 6E 94 9C 0A EC 85 8F 04 82 24 21 0F CC
+0120 | 61 F1 1C 3A 91 0B 43 1C CB D1 04 CC CC 8D C6 D2
+0130 | 9D 4A 5D 13 3B E6 39 A4 C3 2B BF F1 53 E6 3A CA
+0140 | 3A C5 2F 2E 47 09 B8 AE 01 84 4B 14 2C 1E E8 9D
+0150 | 07 5D 64 F6 9A 39 9F EB 04 E6 56 FE 36 75 A6 F8
+0160 | F4 12 07 8F 3D 0B 58 DA 15 31 1C 1A 9F 8E 53 B3
+0170 | CD 6B B5 57 2C 29 49 04 B7 26 D0 BE 33 7E 2E 21
+0180 | 97 7D A2 6D D6 E3 32 70 25 1C 2C A2 9D FC C7 02
+0190 | 27 F0 75 5F 84 CF DA 9A C4 B8 DD 5F 84 F1 D1 EB
+01A0 | 36 BA 45 CD DC 70 44 4D 8C 21 3E 4B D8 F6 3B 8A
+01B0 | B9 5A 2D 0B 41 80 DC 91 28 3D C0 63 AC FB 92 D6
+01C0 | A4 E4 07 CD E7 C8 C6 96 89 F7 7A 00 74 41 D4 A6
+01D0 | A8 38 4B 66 65 02 D9 B7 7F C6 8B 5B 43 CC 60 7E
+01E0 | 60 A1 46 22 3E 11 0F CB 43 BC 3C 94 2E F9 81 93
+01F0 | 0C DC 4A 1D 31 0C 0B 64 D5 E5 5D 30 8D 86 32 51
+0200 | AB 90 50 2C 3E 46 CC 59 9E 88 6A 92 7C DA 96 3B
+0210 | 9E B1 6C E6 26 03 B6 85 29 EE 98 F9 F5 20 64 19
+0220 | E0 3F B4 58 EC 4B D9 45 4A A8 F6 BA 77 75 73 CC
+0230 | 54 B3 28 89 5B 1D F2 5E AD 9F B4 CD 51 98 EE 02
+0240 | 2B 2B 81 F3 88 D2 81 D5 E5 BC 58 01 07 CA 01 A5
+0250 | 06 65 C3 2B 55 27 15 F3 35 FD 76 26 4F AD 00 DD
+0260 | D5 AE 45 B9 48 32 AC 79 CE 7C 51 1D 19 4B C4 2B
+0270 | 70 EF A8 50 BB 15 C2 01 2C 52 15 CA BF E9 7C E6
+0280 | 6B 8D 87 34 D0 EE 75 9A 63 8A F0 13
+
Response decomposition using the following formula:
+
server_DH_params_fail#79cb045d nonce:int128 server_nonce:int128 new_nonce_hash:int128 = Server_DH_Params;
+server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:string = Server_DH_Params;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57ACB36435401Exact unixtime * 2^32
message_length16, 4632Message body length
%(server_DH_params_ok)20, 4d0e8075cserver_DH_params_ok constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_answer56, 596See belowSee “Decomposition of encrypted_answer"
+
Conversion of encrypted_answer into answer:
+
encrypted_answer = 28A92FE20173B347A8BB324B5FAB2667C9A8BBCE6468D5B509A4CBDDC186240AC912CF7006AF8926DE606A2E74C0493CAA57741E6C82451F54D3E068F5CCC49B4444124B9666FFB405AAB564A3D01E67F6E912867C8D20D9882707DC330B17B4E0DD57CB53BFAAFA9EF5BE76AE6C1B9B6C51E2D6502A47C883095C46C81E3BE25F62427B585488BB3BF239213BF48EB8FE34C9A026CC8413934043974DB03556633038392CECB51F94824E140B98637730A4BE79A8F9DAFA39BAE81E1095849EA4C83467C92A3A17D997817C8A7AC61C3FF414DA37B7D66E949C0AEC858F048224210FCC61F11C3A910B431CCBD104CCCC8DC6D29D4A5D133BE639A4C32BBFF153E63ACA3AC52F2E4709B8AE01844B142C1EE89D075D64F69A399FEB04E656FE3675A6F8F412078F3D0B58DA15311C1A9F8E53B3CD6BB5572C294904B726D0BE337E2E21977DA26DD6E33270251C2CA29DFCC70227F0755F84CFDA9AC4B8DD5F84F1D1EB36BA45CDDC70444D8C213E4BD8F63B8AB95A2D0B4180DC91283DC063ACFB92D6A4E407CDE7C8C69689F77A007441D4A6A8384B666502D9B77FC68B5B43CC607E60A146223E110FCB43BC3C942EF981930CDC4A1D310C0B64D5E55D308D863251AB90502C3E46CC599E886A927CDA963B9EB16CE62603B68529EE98F9F5206419E03FB458EC4BD9454AA8F6BA777573CC54B328895B1DF25EAD9FB4CD5198EE022B2B81F388D281D5E5BC580107CA01A50665C32B552715F335FD76264FAD00DDD5AE45B94832AC79CE7C511D194BC42B70EFA850BB15C2012C5215CABFE97CE66B8D8734D0EE759A638AF013
+tmp_aes_key = F011280887C7BB01DF0FC4E17830E0B91FBB8BE4B2267CB985AE25F33B527253
+tmp_aes_iv = 3212D579EE35452ED23E0D0C92841AA7D31B2E9BDEF2151E80D15860311C85DB
+answer = BA0D89B53E0549828CCA27E966B301A48FECE2FCA5CF4D33F4A11EA877BA4AA57390733002000000FE000100C71CAEB9C6B1C9048E6C522F70F13F73980D40238E3E21C14934D037563D930F48198A0AA7C14058229493D22530F4DBFA336F6E0AC925139543AED44CCE7C3720FD51F69458705AC68CD4FE6B6B13ABDC9746512969328454F18FAF8C595F642477FE96BB2A941D5BCD1D4AC8CC49880708FA9B378E3C4F3A9060BEE67CF9A4A4A695811051907E162753B56B0F6B410DBA74D8A84B2A14B3144E0EF1284754FD17ED950D5965B4B9DD46582DB1178D169C6BC465B0D6FF9CA3928FEF5B9AE4E418FC15E83EBEA0F87FA9FF5EED70050DED2849F47BF959D956850CE929851F0D8115F635B105EE2E4E15D04B2454BF6F4FADF034B10403119CD8E3B92FCC5BFE000100262AABA621CC4DF587DC94CF8252258C0B9337DFB47545A49CDD5C9B8EAE7236C6CADC40B24E88590F1CC2CC762EBF1CF11DCC0B393CAAD6CEE4EE5848001C73ACBB1D127E4CB93072AA3D1C8151B6FB6AA6124B7CD782EAF981BDCFCE9D7A00E423BD9D194E8AF78EF6501F415522E44522281C79D906DDB79C72E9C63D83FB2A940FF779DFB5F2FD786FB4AD71C9F08CF48758E534E9815F634F1E3A80A5E1C2AF210C5AB762755AD4B2126DFA61A77FA9DA967D65DFD0AFB5CDF26C4D4E1A88B180F4E0D0B45BA1484F95CB2712B50BF3F5968D9D55C99C0FB9FB67BFF56D7D4481B634514FBA3488C4CDA2FC0659990E8E868B28632875A9AA703BCDCE8FCB7AE551
+
Server_DH_inner_data decomposition using the following formula:
+
server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:string g_a:string server_time:int = Server_DH_inner_data;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(server_DH_inner_data)0, 4b5890dbaserver_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
g36, 42Value received from server in Step 2
dh_prime40, 260C71CAEB9C6B1C9048E6C522F70F13F73 980D40238E3E21C14934D037563D930F 48198A0AA7C14058229493D22530F4DB FA336F6E0AC925139543AED44CCE7C37 20FD51F69458705AC68CD4FE6B6B13AB DC9746512969328454F18FAF8C595F64 2477FE96BB2A941D5BCD1D4AC8CC4988 0708FA9B378E3C4F3A9060BEE67CF9A4 A4A695811051907E162753B56B0F6B41 0DBA74D8A84B2A14B3144E0EF1284754 FD17ED950D5965B4B9DD46582DB1178D 169C6BC465B0D6FF9CA3928FEF5B9AE4 E418FC15E83EBEA0F87FA9FF5EED7005 0DED2849F47BF959D956850CE929851F 0D8115F635B105EE2E4E15D04B2454BF 6F4FADF034B10403119CD8E3B92FCC5B
g_a300, 260262AABA621CC4DF587DC94CF8252258C 0B9337DFB47545A49CDD5C9B8EAE7236 C6CADC40B24E88590F1CC2CC762EBF1C F11DCC0B393CAAD6CEE4EE5848001C73 ACBB1D127E4CB93072AA3D1C8151B6FB 6AA6124B7CD782EAF981BDCFCE9D7A00 E423BD9D194E8AF78EF6501F415522E4 4522281C79D906DDB79C72E9C63D83FB 2A940FF779DFB5F2FD786FB4AD71C9F0 8CF48758E534E9815F634F1E3A80A5E1 C2AF210C5AB762755AD4B2126DFA61A7 7FA9DA967D65DFD0AFB5CDF26C4D4E1A 88B180F4E0D0B45BA1484F95CB2712B5 0BF3F5968D9D55C99C0FB9FB67BFF56D 7D4481B634514FBA3488C4CDA2FC0659 990E8E868B28632875A9AA703BCDCE8F
server_time560, 41373993675Server time
+

6. Random number b is computed:

+
b = 6F620AFA575C9233EB4C014110A7BCAF49464F798A18A0981FEA1E05E8DA67D9681E0FD6DF0EDF0272AE3492451A84502F2EFC0DA18741A5FB80BD82296919A70FAA6D07CBBBCA2037EA7D3E327B61D585ED3373EE0553A91CBD29B01FA9A89D479CA53D57BDE3A76FBD922A923A0A38B922C1D0701F53FF52D7EA9217080163A64901E766EB6A0F20BC391B64B9D1DD2CD13A7D0C946A3A7DF8CEC9E2236446F646C42CFE2B60A2A8D776E56C8D7519B08B88ED0970E10D12A8C9E355D765F2B7BBB7B4CA9360083435523CB0D57D2B106FD14F94B4EEE79D8AC131CA56AD389C84FE279716F8124A543337FB9EA3D988EC5FA63D90A4BA3970E7A39E5C0DE5
+
Generation of encrypted_data
+
client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:string = Client_DH_Inner_Data
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(client_DH_inner_data)0, 46643b654client_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
retry_id36, 80First attempt
g_b44, 26073700E7BFC7AEEC828EB8E0DCC04D09A 0DD56A1B4B35F72F0B55FCE7DB7EBB72 D7C33C5D4AA59E1C74D09B01AE536B31 8CFED436AFDB15FE9EB4C70D7F0CB14E 46DBBDE9053A64304361EB358A9BB32E 9D5C2843FE87248B89C3F066A7D5876D 61657ACC52B0D81CD683B2A0FA93E8AD AB20377877F3BC3369BBF57B10F5B589 E65A9C27490F30A0C70FFCFD3453F5B3 79C1B9727A573CFFDCA8D23C721B135B 92E529B1CDD2F7ABD4F34DAC4BE1EEAF 60993DDE8ED45890E4F47C26F2C0B2E0 37BB502739C8824F2A99E2B1E7E41658 3417CC79A8807A4BDAC6A5E9805D4F61 86C37D66F6988C9F9C752896F3D34D25 529263FAF2670A09B2A59CE35264511Fg^b mod dh_prime
+

The serialization of Client_DH_Inner_Data produces some string data. This is followed by encrypted_data:

+
data_with_hash := SHA1(data) + data + (0-15 random bytes); such that the length be divisible by 16;
+AES256_ige_encrypt (data_with_hash, tmp_aes_key, tmp_aes_iv) = 928A4957D0463B525C1CC48AABAA030A256BE5C746792C84CA4C5A0DF60AC799048D98A38A8480EDCF082214DFC79DCB9EE34E206513E2B3BC1504CFE6C9ADA46BF9A03CA74F192EAF8C278454ADABC795A566615462D31817382984039505F71CB33A41E2527A4B1AC05107872FED8E3ABCEE1518AE965B0ED3AED7F67479155BDA8E4C286B64CDF123EC748CF289B1DB02D1907B562DF462D8582BA6F0A3022DC2D3504D69D1BA48B677E3A830BFAFD67584C8AA24E1344A8904E305F9587C92EF964F0083F50F61EAB4A393EAA33C9270294AEDC7732891D4EA1599F52311D74469D2112F4EDF3F342E93C8E87E812DC3989BAECFE6740A46077524C75093F5A5405736DE8937BB6E42C9A0DCF22CA53227D462BCCC2CFE94B6FE86AB7FBFA395021F66661AF7C0024CA2986CA03F3476905407D1EA9C010B763258DB1AA2CC7826D91334EFC1FDC665B67FE45ED0
+

The length of the final string was 336 bytes.

+
Request
+
set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:string = Set_client_DH_params_answer;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57acd2aa32c6dExact unixtime * 2^32
message_length16, 4376Message body length
%(set_client_DH_params)20, 4f5045f1fset_client_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_data56, 340See aboveSee “Generation of encrypted_data"
+
0000 | 00 00 00 00 00 00 00 00 6D 2C A3 2A CD 7A E5 51
+0010 | 78 01 00 00 1F 5F 04 F5 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 FE 50 01 00 92 8A 49 57
+0040 | D0 46 3B 52 5C 1C C4 8A AB AA 03 0A 25 6B E5 C7
+0050 | 46 79 2C 84 CA 4C 5A 0D F6 0A C7 99 04 8D 98 A3
+0060 | 8A 84 80 ED CF 08 22 14 DF C7 9D CB 9E E3 4E 20
+0070 | 65 13 E2 B3 BC 15 04 CF E6 C9 AD A4 6B F9 A0 3C
+0080 | A7 4F 19 2E AF 8C 27 84 54 AD AB C7 95 A5 66 61
+0090 | 54 62 D3 18 17 38 29 84 03 95 05 F7 1C B3 3A 41
+00A0 | E2 52 7A 4B 1A C0 51 07 87 2F ED 8E 3A BC EE 15
+00B0 | 18 AE 96 5B 0E D3 AE D7 F6 74 79 15 5B DA 8E 4C
+00C0 | 28 6B 64 CD F1 23 EC 74 8C F2 89 B1 DB 02 D1 90
+00D0 | 7B 56 2D F4 62 D8 58 2B A6 F0 A3 02 2D C2 D3 50
+00E0 | 4D 69 D1 BA 48 B6 77 E3 A8 30 BF AF D6 75 84 C8
+00F0 | AA 24 E1 34 4A 89 04 E3 05 F9 58 7C 92 EF 96 4F
+0100 | 00 83 F5 0F 61 EA B4 A3 93 EA A3 3C 92 70 29 4A
+0110 | ED C7 73 28 91 D4 EA 15 99 F5 23 11 D7 44 69 D2
+0120 | 11 2F 4E DF 3F 34 2E 93 C8 E8 7E 81 2D C3 98 9B
+0130 | AE CF E6 74 0A 46 07 75 24 C7 50 93 F5 A5 40 57
+0140 | 36 DE 89 37 BB 6E 42 C9 A0 DC F2 2C A5 32 27 D4
+0150 | 62 BC CC 2C FE 94 B6 FE 86 AB 7F BF A3 95 02 1F
+0160 | 66 66 1A F7 C0 02 4C A2 98 6C A0 3F 34 76 90 54
+0170 | 07 D1 EA 9C 01 0B 76 32 58 DB 1A A2 CC 78 26 D9
+0180 | 13 34 EF C1 FD C6 65 B6 7F E4 5E D0
+

7. Computing auth_key using formula g^{ab} mod dh_prime:

+
auth_key = AB96E207C631300986F30EF97DF55E179E63C112675F0CE502EE76D74BBEE6CBD1E95772818881E9F2FF54BD52C258787474F6A7BEA61EABE49D1D01D55F64FC07BC31685716EC8FB46FEACF9502E42CFD6B9F45A08E90AA5C2B5933AC767CBE1CD50D8E64F89727CA4A1A5D32C0DB80A9FCDBDDD4F8D5A1E774198F1A4299F927C484FEEC395F29647E43C3243986F93609E23538C21871DF50E00070B3B6A8FA9BC15628E8B43FF977409A61CEEC5A21CF7DFB5A4CC28F5257BC30CD8F2FB92FBF21E28924065F50E0BBD5E11A420300E2C136B80E9826C6C5609B5371B7850AA628323B6422F3A94F6DFDE4C3DC1EA60F7E11EE63122B3F39CBD1A8430157
+

8. The server verifies that auth_key_hash is unique.

+

The key is unique.

+

9. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 30 AA C5 CE 7A E5 51
+0010 | 34 00 00 00 34 F7 CB 3B 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 CC EB C0 21 72 66 E1 ED
+0040 | EC 7F B0 A0 EE D6 C2 20
+

Set_client_DH_params_answer decomposition using the following formula:

+
dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
+dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
+dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(dh_gen_ok)0, 43bcbf734dh_gen_ok constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce_hash136, 16CCEBC0217266E1EDEC7FB0A0EED6C220
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/security_guidelines.html b/data/core.telegram.org/mtproto/security_guidelines.html new file mode 100644 index 0000000000..180cb6991a --- /dev/null +++ b/data/core.telegram.org/mtproto/security_guidelines.html @@ -0,0 +1,177 @@ + + + + + Security Guidelines for Client Developers + + + + + + + + + + + + + +
+ +
+
+
+ +

Security Guidelines for Client Developers

+ +
+ +

See also:

+

+ +

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply.

+
+

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. +MTProto v.1.0 is deprecated and is currently being phased out.

+
+

Diffie-Hellman key exchange

+

We use DH key exchange in two cases:

+ +

In both cases, there are some verifications to be done whenever DH is used:

+

Validation of DH parameters

+

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

+

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

+

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

+
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
+

g_a and g_b validation

+

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

+

Checking SHA1 hash values during key generation

+

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

+
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
+

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

+

Checking nonce, server_nonce and new_nonce fields

+

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

+

Using secure pseudorandom number generator to create DH secret parameters a and b

+

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

+

MTProto Encrypted Messages

+

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

+

Checking SHA256 hash value of msg_key

+

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA256 of the plaintext obtained as the result of decryption (including the final 12...1024 padding bytes), prepended with 32 bytes taken from the auth_key, as explained in MTProto 2.0 Description.

+

If an error is encountered before this check could be performed, the client must perform the msg_key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

+

Checking message length

+

The client must check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference (i.e. the length of the random padding) lies in the range from 12 to 1024 bytes.

+

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

+

Checking session_id

+

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

+

Checking msg_id

+

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

+

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

+

Behavior in case of mismatch

+

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

+

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

+

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

+
+

The previous version of security recommendations relevant for MTProto 1.0 clients is available here.

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/mtproto/security_guidelines_v1.html b/data/core.telegram.org/mtproto/security_guidelines_v1.html new file mode 100644 index 0000000000..bbf0d1a3b5 --- /dev/null +++ b/data/core.telegram.org/mtproto/security_guidelines_v1.html @@ -0,0 +1,175 @@ + + + + + Security Guidelines for Client Developers (v.1.0, DEPRECATED) + + + + + + + + + + + + + +
+ +
+
+
+ +

Security Guidelines for Client Developers (v.1.0, DEPRECATED)

+ +
+ +
+

This document describes security recommendations for clients using MTProto 1.0, its status is DEPRECATED. +For up-to-date security recommendations, kindly see this document.

+
+

See also:

+

+ +

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply with these.

+

Diffie--Hellman key exchange

+

We use DH key exchange in two cases:

+ +

In both cases, there are some verifications to be done whenever DH is used:

+

Validation of DH parameters

+

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

+

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

+

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

+
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
+

g_a and g_b validation

+

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

+

Checking SHA1 hash values

+

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

+
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
+

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

+

Checking nonce, server_nonce and new_nonce fields

+

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

+

Using secure pseudorandom number generator to create DH secret parameters a and b

+

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

+

MTProto Encrypted Messages

+

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

+

Checking SHA1 hash value of msg_key

+

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA1 of the plaintext obtained as the result of decryption (without the final padding bytes).

+

If an error is encountered before this check could be performed, the client must perform the msg-key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

+

Checking message length

+

The client is to check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference is not more than 15 bytes. Apart from this, knowing the total length is important for the previous verification.

+

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

+

Checking session_id

+

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

+

Checking msg_id

+

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

+

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

+

Behavior in case of mismatch

+

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

+

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

+

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/mtproto/serialize.html b/data/core.telegram.org/mtproto/serialize.html new file mode 100644 index 0000000000..e014d3aa7c --- /dev/null +++ b/data/core.telegram.org/mtproto/serialize.html @@ -0,0 +1,240 @@ + + + + + Binary Data Serialization + + + + + + + + + + + + + +
+ +
+
+
+ +

Binary Data Serialization

+ +

MTProto operation requires that elementary and composite data types as well as queries to which such data types are passed as arguments or by which they are returned, be transmitted in binary format (i. e. serialized) . +The TL language is used to describe the data types to be serialized.

+

General Definitions

+

For our purposes, we can identify a type with the set of its (serialized) values understood as strings (finite sequences) of 32-bit numbers (transmitted in little endian order).

+

Therefore:

+
    +
  • Alphabet (A), in this case, is a set of 32-bit numbers (normally, signed, i. e. between -2^31 and 2^31 - 1).
  • +
  • Value, in this case, is the same as a string in Alphabet A, i. e. a finite (possibly, empty) sequence of 32-bit numbers. The set of all such sequences is designated as A*.
  • +
  • Type, for our purposes, is the same as the set of legal values of a type, i. e. some set T which is a subset of A* and is a prefix code (i. e. no element of T may be a prefix for any other element). Therefore, any sequence from A* can contain no more than one prefix that is a member of T.
  • +
  • Value of Type T is any sequence (value) which is a member of T as a subset of A*.
  • +
  • Compatible Types are the types T and T’ not intersecting as subsets of A*, such that the union of T and T' is a prefix code.
  • +
  • Coordinated System of Types is a finite or infinite set of types T_1, ..., T_n, ..., such that any two types from this set are compatible.
  • +
  • Data Type is the same as type in the sense of the definition above.
  • +
  • Functional Type is a type describing a function; it is not a type in the sense of the definition above. Initially, we ignore the existence of functional types and describe only the data types; however, in reality, functional types will later be implemented in some extension of this system using the so-called temporary combinators.
  • +
+

Combinators, Constructors, Composite Data Types

+
    +
  • +

    Combinator is a function that takes arguments of certain types and returns a value of some other type. We normally look at combinators whose argument and result types are data types (rather than functional types).

    +
  • +
  • +

    Arity (of combinator) is a non-negative integer, the number of combinator arguments.

    +
  • +
  • +

    Combinator identifier is an identifier beginning with a lowercase Roman letter that uniquely identifies a combinator.

    +
  • +
  • +

    Combinator number or combinator name is a 32-bit number (i.e., an element of A) that uniquely identifies a combinator. Most often, it is CRC32 of the string containing the combinator description without the final semicolon, and with one space between contiguous lexemes. This always falls in the range from 0x01000000 to 0xffffff00. The highest 256 values are reserved for the so-called temporal-logic combinators used to transmit functions. We frequently denote as combinator the combinator name with single quotes: ‘combinator’.

    +
  • +
  • +

    Combinator description is a string of format combinator_name type_arg_1 ... type_arg_N = type_res; where N stands for the arity of the combinator, type_arg_i is the type of the i-th argument (or rather, a string with the combinator name), and type_res is the combinator value type.

    +
  • +
  • +

    Constructor is a combinator that cannot be computed (reduced). This is used to represent composite data types. For example, combinator ‘int_tree’ with description int_tree IntTree int IntTree = IntTree, alongside combinator empty_tree = IntTree, may be used to define a composite data type called “IntTree” that takes on values in the form of binary trees with integers as nodes.

    +
  • +
  • +

    Function (functional combinator) is a combinator which may be computed (reduced) on condition that the requisite number of arguments of requisite types are provided. The result of the computation is an expression consisting of constructors and base type values only.

    +
  • +
  • +

    Normal form is an expression consisting only of constructors and base type values; that which is normally the result of computing a function.

    +
  • +
  • +

    Type identifier is an identifier that normally starts with a capital letter in Roman script and uniquely identifies the type.

    +
  • +
  • +

    Type number or type name is a 32-bit number that uniquely identifies a type; it normally is the sum of the CRC32 values of the descriptions of the type constructors.

    +
  • +
  • +

    Description of (composite) Type T is a collection of the descriptions of all constructors that take on Type T values. This is normally written as text with each string containing the description of a single constructor. Here is a description of Type ‘IntTree’, for example:

    +

    int_tree IntTree int IntTree = IntTree; +empty_tree = IntTree;

    +
  • +
  • +

    Polymorphic type is a type whose description contains parameters (type variables) in lieu of actual types; approximately, what would be a template in C++. Here is a description of Type List alpha where List is a polymorphic type of arity 1 (i. e., dependent on a single argument), and alpha is a type variable which appears as the constructor’s optional parameter (in curly braces):

    +

    cons {alpha:Type} alpha (List alpha) = List alpha; +nil {alpha:Type} = List alpha;

    +
  • +
  • +

    Value of (composite) Type T is any sequence from A* in the format constr_num arg1 ... argN, where constr_num is the index number of some Constructor C which takes on values of Type T, and arg_i is a value of Type T_i which is the type of the i-th argument to Constructor C. For example, let Combinator int_tree have the index number 17, whereas Combinator empty_tree has the index number 239. Then, the value of Type IntTree is, for example, 17 17 239 1 239 2 239 which is more conveniently written as 'int_tree' 'int_tree' 'empty_tree' 1 'empty_tree' 2 ‘empty_tree’. From the standpoint of a high-level language, this is int_tree (int_tree (empty_tree) 1 (empty_tree)) 2 (empty_tree): IntTree.

    +
  • +
  • +

    Schema is a collection of all the (composite) data type descriptions. This is used to define some agreed-to system of types.

    +
  • +
+

Boxed and Bare Types

+
    +
  • Boxed type is a type any value of which starts with the constructor number. Since every constructor has a uniquely determined value type, the first number in any boxed type value uniquely defines its type. This guarantees that the various boxed types in totality make up a coordinated system of types. A boxed type identifier is always capitalized.
  • +
  • Bare type is a type whose values do not contain a constructor number, which is implied instead. A bare type identifier always coincides with the name of the implied constructor (and therefore, begins with a lowercase letter) which may be padded at the front by the percentage sign (%). In addition, if X is a boxed type with no more than a single constructor, then %X refers to the corresponding bare type. The values of a bare type are identical with the set of number sequences obtained by dropping the first number (i. e., the external constructor index number) from the set of values of the corresponding boxed type (which is the result type of the selected constructor), starting with the selected constructor index number. For example, 3 4 is a value of the int_couple bare type, defined using int_couple int int = IntCouple. The corresponding boxed type is IntCouple; if 404 is the constructor index number for int_couple, then 404 3 4 is the value for the IntCouple boxed type which corresponds to the value of the bare type int_couple (also known as %int_couple and %IntCouple; the latter form is conceptually preferable but longer).
  • +
+

Conceptually, only boxed types should be used everywhere. However, for speed and compactness, bare types have to be used (for instance, an array of 10,000 bare int values is 40,000 bytes long, whereas boxed Int values take up twice as much space; therefore, when transmitting a large array of integer identifiers, say, it is more efficient to use the Vector int type rather than Vector Int). In addition, all base types (int, long, double, string) are bare.

+

If a boxed type is polymorphic of type arity r, this is also true of any derived bare type. In other words, if one were to define intCouple {alpha:Type} int alpha = IntCouple alpha, then, thereafter, intCouple as an identifier would also be a polymorphic type of arity 1 in combinator (and consequently, in constructor and type) descriptions. The notations intCouple X, %(IntCouple X), and %IntCouple X are equivalent.

+

Base Types

+

Base types exist both as bare (int, long, double, string) and as boxed (Int, Long, Double, String) versions. Their constructor identifiers coincide with the names of the relevant bare types. Their pseudodescriptions have the following appearance:

+
int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+

Consequently, the int constructor index number, for example, is the CRC32 of the string "int ? = Int".

+

The values of bare type int are exactly all the single-element sequences, i. e. numbers between -2^31 and 2^31-1 represent themselves in this case. Values of type long are two-element sequences that are 64-bit signed numbers (little endian again). Values of type double, again, are two-element sequences containing 64-bit real numbers in a standard double format. And finally, the values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit numbers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

Object Pseudotype

+

The Object pseudotype is a “type” which can take on values that belong to any boxed type in the schema. This helps quickly define such types as list of random items without using polymorphic types. It is best not to abuse this capability since it results in the use of dynamic typing. Nonetheless, it is hard to imagine the data structures that we know from PHP and JSON without using the Object pseudotype.

+

It is recommended to use TypedObject instead whenever possible:

+
object X:Type value:X = TypedObject;
+

Built-In Composite Types: Vectors and Associative Arrays

+

The Vector t polymorphic pseudotype is a “type” whose value is a sequence of values of any type t, either boxed or bare.

+
vector {t:Type} # [ t ] = Vector t;
+

Serialization always uses the same constructor “vector” (const 0x1cb5c415 = crc32("vector t:Type # [ t ] = Vector t”) that is not dependent on the specific value of the variable of type t. The value of the Vector t type is the index number of the relevant constructor number followed by N, the number of elements in the vector, and then by N values of type t. The value of the optional parameter t is not involved in the serialization since it is derived from the result type (always known prior to deserialization).

+

Polymorphic pseudotypes IntHash t and StrHash t are associative arrays mapping integer and string keys to values of type t. They are, in fact, vectors containing bare 2-tuples (int, t) or (string, t):

+
coupleInt {t:Type} int t = CoupleInt t;
+intHash {t:Type} (vector %(CoupleInt t)) = IntHash t;
+coupleStr {t:Type} string t = CoupleStr t;
+strHash {t:Type} (vector %(CoupleStr t)) = StrHash t;
+

The percentage sign, in this case, means that a bare type that corresponds to the boxed type in parentheses is taken; the boxed type in question must have no more than a single constructor, whatever the values of the parameters.

+

The keys may be sorted or be in some other order (as in PHP arrays). For associative arrays with sorted keys, the IntSortedHash or StrSortedHash alias is used:

+
intSortedHash {t:Type} (intHash t) = IntSortedHash t;
+strSortedHash {t:Type} (strHash t) = StrSortedHash t;
+

Polymorphic Type Constructors

+

The constructor of a polymorphic type does not depend on the specific types to which the polymorphic type is applied. When it is computed, optional parameters (normally containing type variables and placed in curly braces) cease to be optional (the curly braces are removed), and, in addition to that, all parenthesis are also removed. Therefore,

+
vector {t:Type} # [ t ] = Vector t;
+

corresponds to the constructor number crc32("vector t:Type # [ t ] = Vector t") = 0x1cb5c415. During (de)serialization, the specific values of the optional variable t are derived from the result type (i. e. the object being serialized or deserialized) that is always known, and are never serialized explicitly.

+

Previously, it had to be known which specific variable types each polymorphic type will apply to. To accomplish this, the type system used strings of the form

+
polymorphic_type_name type_1 ... type_N;
+

For example,

+
Vector int;
+Vector string;
+Vector Object;
+

Now they are ignored.

+

See also polymorphism in TL.

+

In this case, the Object pseudotype permits using Vector Object to store lists of anything (the values of any boxed types). Since bare types are efficient when short, in practice it is unlikely that cases more complex than the ones cited above will be required.

+

Field Names

+

Let us say that we need to represent users as triplets containing one integer (user ID) and two strings (first and last names). The requisite data structure is the triplet int, string, string which may be declared as follows:

+
user int string string = User;
+

On the other hand, a group may be described by a similar triplet consisting of a group ID, its name, and description:

+
group int string string = Group;
+

For the difference between User and Group to be clear, it is convenient to assign names to some or all of the fields:

+
user id:int first_name:string last_name:string = User;
+group id:int title:string description:string = Group;
+

If the User type needs to be extended at a later time by having records with some additional field added to it, it could be accomplished as follows:

+
userv2 id:int unread_messages:int first_name:string last_name:string in_groups:vector int = User;
+

Aside from other things, this approach helps define correct mappings between fields that belong to different constructors of the same type, convert between them as well as convert type values into an associative array with string keys (field names, if defined, are natural choices for such keys).

+

TL Language

+

See TL Language

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/service_messages.html b/data/core.telegram.org/mtproto/service_messages.html new file mode 100644 index 0000000000..25e631fce7 --- /dev/null +++ b/data/core.telegram.org/mtproto/service_messages.html @@ -0,0 +1,195 @@ + + + + + Service Messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Service Messages

+ +

Response to an RPC query

+

A response to an RPC query is normally wrapped as follows:

+
rpc_result#f35c6d01 req_msg_id:long result:Object = RpcResult;
+

Here req_msg_id is the identifier of the message sent by the other party and containing an RPC query. This way, the recipient knows that the result is a response to the specific RPC query in question. +At the same time, this response serves as acknowledgment of the other party’s receipt of the req_msg_id message.

+

Note that the response to an RPC query must also be acknowledged. Most frequently, this coincides with the transmission of the next message (which may have a container attached to it carrying a service message with the acknowledgment).

+

RPC Error

+

The result field returned in response to any RPC query may also contain an error message in the following format:

+
rpc_error#2144ca19 error_code:int error_message:string = RpcError;
+

Cancellation of an RPC Query

+

In certain situations, the client does not want to receive a response to an already transmitted RPC query, for example because the response turns out to be long and the client has decided to do without it because of insufficient link capacity. Simply interrupting the TCP connection will not have any effect because the server would re-send the missing response at the first opportunity. Therefore, the client needs a way to cancel receipt of the RPC response message, actually acknowledging its receipt prior to it being in fact received, which will settle the server down and prevent it from re-sending the response. However, the client does not know the RPC response’s msg_id prior to receiving the response; the only thing it knows is the req_msg_id. i. e. the msg_id of the relevant RPC query. Therefore, a special query is used:

+
rpc_drop_answer#58e4a740 req_msg_id:long = RpcDropAnswer;
+

The response to this query returns as one of the following messages wrapped in rpc_result and requiring an acknowledgment:

+
rpc_answer_unknown#5e2ad36e = RpcDropAnswer;
+rpc_answer_dropped_running#cd78e586 = RpcDropAnswer;
+rpc_answer_dropped#a43ad8b7 msg_id:long seq_no:int bytes:int = RpcDropAnswer;
+

The first version of the response is used if the server remembers nothing of the incoming req_msg_id (if it has already been responded to, for example). The second version is used if the response was canceled while the RPC query was being processed (where the RPC query itself was still fully processed); in this case, the same rpc_answer_dropped_running is also returned in response to the original query, and both of these responses require an acknowledgment from the client. The final version means that the RPC response was removed from the server’s outgoing queue, and its msg_id, seq_no, and length in bytes are transmitted to the client.

+

Note that rpc_answer_dropped_running and rpc_answer_dropped serve as acknowledgments of the server’s receipt of the original query (the same one, the response to which we wish to forget). In addition, same as for any RPC queries, any response to rpc_drop_answer is an acknowledgment for rpc_drop_answer itself.

+

As an alternative to using rpc_drop_answer, a new session may be created after the connection is reset and the old session is removed through destroy_session.

+

Messages associated with querying, changing, and receiving the status of other messages

+

See Mobile Protocol: Service Messages about Messages

+

Request for several future salts

+

The client may at any time request from the server several (between 1 and 64) future server salts together with their validity periods. Having stored them in persistent memory, the client may use them to send messages in the future even if it changes sessions (a server salt is attached to the authorization key rather than being session-specific).

+
get_future_salts#b921bd04 num:int = FutureSalts;
+future_salt#0949d9dc valid_since:int valid_until:int salt:long = FutureSalt;
+future_salts#ae500895 req_msg_id:long now:int salts:vector<future_salt> = FutureSalts;
+

The client must check to see that the response’s req_msg_id in fact coincides with msg_id of the query for get_future_salts. The server returns a maximum of num future server salts (may return fewer). The response serves as the acknowledgment of the query and does not require an acknowledgment itself.

+

Ping Messages (PING/PONG)

+
ping#7abe77ec ping_id:long = Pong;
+

A response is usually returned to the same connection:

+
pong#347773c5 msg_id:long ping_id:long = Pong;
+

These messages do not require acknowledgments. A pong is transmitted only in response to a ping while a ping can be initiated by either side.

+

Deferred Connection Closure + PING

+
ping_delay_disconnect#f3427b8c ping_id:long disconnect_delay:int = Pong;
+

Works like ping. In addition, after this is received, the server starts a timer which will close the current connection disconnect_delay seconds later unless it receives a new message of the same type which automatically resets all previous timers. If the client sends these pings once every 60 seconds, for example, it may set disconnect_delay equal to 75 seconds.

+

Request to Destroy Session

+

Used by the client to notify the server that it may forget the data from a different session belonging to the same user (i. e. with the same auth_key_id). The result of this being applied to the current session is undefined.

+
destroy_session#e7512126 session_id:long = DestroySessionRes;
+destroy_session_ok#e22045fc session_id:long = DestroySessionRes;
+destroy_session_none#62d350c9 session_id:long = DestroySessionRes;
+

New Session Creation Notification

+

The server notifies the client that a new session (from the server’s standpoint) had to be created to handle a client message. If, after this, the server receives a message with an even smaller msg_id within the same session, a similar notification will be generated for this msg_id as well. No such notifications are generated for high msg_id values.

+
new_session_created#9ec20908 first_msg_id:long unique_id:long server_salt:long = NewSession
+

The unique_id parameter is generated by the server every time a session is (re-)created.

+

This notification must be acknowledged by the client. It is necessary, for instance, for the client to understand that there is, in fact, a “gap” in the stream of long poll notifications received from the server (the user may have failed to receive notifications during some period of time).

+

Notice that the server may unilaterally destroy (close) any existing client sessions with all pending messages and notifications, without sending any notifications. This happens, for example, if the session is inactive for a long time, and the server runs out of memory. If the client at some point decides to send new messages to the server using the old session, already forgotten by the server, such a "new session created" notification will be generated. The client is expected to handle such situations gracefully.

+

Containers

+

Containers are messages containing several other messages. Used for the ability to transmit several RPC queries and/or service messages at the same time, using HTTP or even TCP or UDP protocol. A container may only be accepted or rejected by the other party as a whole.

+

Simple Container

+

A simple container carries several messages as follows:

+
msg_container#73f1f8dc messages:vector message = MessageContainer;
+

Here message refers to any message together with its length and msg_id:

+
message msg_id:long seqno:int bytes:int body:Object = Message;
+

bytes is the number of bytes in the body serialization. +All messages in a container must have msg_id lower than that of the container itself. A container does not require an acknowledgment and may not carry other simple containers. When messages are re-sent, they may be combined into a container in a different manner or sent individually.

+

MTProto container payloads have a limit of 2^15 bytes or 1020 messages, whichever limit is reached first.
+Clients should group acknowledgments, state requests and message resend requests into three separate msgs_ack, msgs_state_req, msg_resend_req service messages with at most 8192 IDs each; these three messages (+http_wait) will not be included in the 1020 message limit.

+

Empty containers are also allowed. They are used by the server, for example, to respond to an HTTP request when the timeout specified in http_wait expires, and there are no messages to transmit.

+

Example implementation.

+

Message Copies

+

In some situations, an old message with a msg_id that is no longer valid needs to be re-sent. Then, it is wrapped in a copy container:

+
msg_copy#e06046b2 orig_message:Message = MessageCopy;
+

Once received, the message is processed as if the wrapper were not there. However, if it is known for certain that the message orig_message.msg_id was received, then the new message is not processed (while at the same time, it and orig_message.msg_id are acknowledged). The value of orig_message.msg_id must be lower than the container’s msg_id.

+

This is not used at this time, because an old message can be wrapped in a simple container with the same result.

+

Packed Object

+

Used to replace any other object (or rather, a serialization thereof) with its archived (gzipped) representation:

+
gzip_packed#3072cfa1 packed_data:string = Object;
+

At the present time, it is supported in the body of an RPC response (i.e., as result in rpc_result) and generated by the server for a limited number of high-level queries. In addition, it may be used to transmit non-service messages (i. e. RPC queries) from client to server.

+

HTTP Wait/Long Poll

+

The following special service query not requiring an acknowledgement (which must be transmitted only through an HTTP connection) is used to enable the server to send messages in the future to the client using HTTP protocol:

+
http_wait#9299359f max_delay:int wait_after:int max_wait:int = HttpWait;
+

When such a message (or a container carrying such a message) is received, the server either waits max_delay milliseconds, whereupon it forwards all the messages that it is holding on to the client if there is at least one message queued in session (if needed, by placing them into a container to which acknowledgments may also be added); or else waits no more than max_wait milliseconds until such a message is available. If a message never appears, an empty container is transmitted.

+

The max_delay parameter denotes the maximum number of milliseconds that has elapsed between the first message for this session and the transmission of an HTTP response. The wait_after parameter works as follows: after the receipt of the latest message for a particular session, the server waits another wait_after milliseconds in case there are more messages. If there are no additional messages, the result is transmitted (a container with all the messages). If more messages appear, the wait_after timer is reset.

+

At the same time, the max_delay parameter has higher priority than wait_after, and max_wait has higher priority than max_delay.

+

This message does not require a response or an acknowledgement. If the container transmitted over HTTP carries several such messages, the behavior is undefined (in fact, the latest parameter will be used).

+

If no http_wait is present in container, default values max_delay=0 (milliseconds), wait_after=0 (milliseconds), and max_wait=25000 (milliseconds) are used.

+

If the client’s ping of the server takes a long time, it may make sense to set max_delay to a value that is comparable in magnitude to ping time.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/service_messages_about_messages.html b/data/core.telegram.org/mtproto/service_messages_about_messages.html new file mode 100644 index 0000000000..3a8f6d4ba1 --- /dev/null +++ b/data/core.telegram.org/mtproto/service_messages_about_messages.html @@ -0,0 +1,185 @@ + + + + + Service Messages about Messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Service Messages about Messages

+ +

Acknowledgment of Receipt

+

Receipt of virtually all messages (with the exception of some purely service ones as well as the plain-text messages used in the protocol for creating an authorization key) must be acknowledged. +This requires the use of the following service message (not requiring an acknowledgment):

+
msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
+

A server usually acknowledges the receipt of a message from a client (normally, an RPC query) using an RPC response. If a response is a long time coming, a server may first send a receipt acknowledgment, and somewhat later, the RPC response itself.

+

A client normally acknowledges the receipt of a message from a server (usually, an RPC response) by adding an acknowledgment to the next RPC query if it is not transmitted too late (if it is generated, say, 60-120 seconds following the receipt of a message from the server). However, if for a long period of time there is no reason to send messages to the server or if there is a large number of unacknowledged messages from the server (say, over 16), the client transmits a stand-alone acknowledgment.

+

Max 8192 IDs are allowed per constructor.

+

Notice of Ignored Error Message

+

In certain cases, a server may notify a client that its incoming message was ignored for whatever reason. Note that such a notification cannot be generated unless a message is correctly decoded by the server.

+
bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
+bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
+

Here, error_code can also take on the following values:

+
    +
  • 16: msg_id too low (most likely, client time is wrong; it would be worthwhile to synchronize it using msg_id notifications and re-send the original message with the “correct” msg_id or wrap it in a container with a new msg_id if the original message had waited too long on the client to be transmitted)
  • +
  • 17: msg_id too high (similar to the previous case, the client time has to be synchronized, and the message re-sent with the correct msg_id)
  • +
  • 18: incorrect two lower order msg_id bits (the server expects client message msg_id to be divisible by 4)
  • +
  • 19: container msg_id is the same as msg_id of a previously received message (this must never happen)
  • +
  • 20: message too old, and it cannot be verified whether the server has received a message with this msg_id or not
  • +
  • 32: msg_seqno too low (the server has already received a message with a lower msg_id but with either a higher or an equal and odd seqno)
  • +
  • 33: msg_seqno too high (similarly, there is a message with a higher msg_id but with either a lower or an equal and odd seqno)
  • +
  • 34: an even msg_seqno expected (irrelevant message), but odd received
  • +
  • 35: odd msg_seqno expected (relevant message), but even received
  • +
  • 48: incorrect server salt (in this case, the bad_server_salt response is received with the correct salt, and the message is to be re-sent with it)
  • +
  • 64: invalid container.
  • +
+

The intention is that error_code values are grouped (error_code >> 4): for example, the codes 0x40 - 0x4f correspond to errors in container decomposition.

+

Notifications of an ignored message do not require acknowledgment (i.e., are irrelevant).

+

Important: if server_salt has changed on the server or if client time is incorrect, any query will result in a notification in the above format. The client must check that it has, in fact, recently sent a message with the specified msg_id, and if that is the case, update its time correction value (the difference between the client’s and the server’s clocks) and the server salt based on msg_id and the server_salt notification, so as to use these to (re)send future messages. In the meantime, the original message (the one that caused the error message to be returned) must also be re-sent with a better msg_id and/or server_salt.

+

In addition, the client can update the server_salt value used to send messages to the server, based on the values of RPC responses or containers carrying an RPC response, provided that this RPC response is actually a match for the query sent recently. (If there is doubt, it is best not to update since there is risk of a replay attack).

+

Request for Message Status Information

+

If either party has not received information on the status of its outgoing messages for a while, it may explicitly request it from the other party:

+
msgs_state_req#da69fb52 msg_ids:Vector long = MsgsStateReq;
+

Max 8192 IDs are allowed per constructor.

+

The response to the query contains the following information:

+

Informational Message regarding Status of Messages

+
msgs_state_info#04deb57d req_msg_id:long info:string = MsgsStateInfo;
+

Here, info is a string that contains exactly one byte of message status for each message from the incoming msg_ids list:

+
    +
  • 1 = nothing is known about the message (msg_id too low, the other party may have forgotten it)
  • +
  • 2 = message not received (msg_id falls within the range of stored identifiers; however, the other party has certainly not received a message like that)
  • +
  • 3 = message not received (msg_id too high; however, the other party has certainly not received it yet)
  • +
  • 4 = message received (note that this response is also at the same time a receipt acknowledgment)
  • +
  • +8 = message already acknowledged
  • +
  • +16 = message not requiring acknowledgment
  • +
  • +32 = RPC query contained in message being processed or processing already complete
  • +
  • +64 = content-related response to message already generated
  • +
  • +128 = other party knows for a fact that message is already received
  • +
+

This response does not require an acknowledgment. It is an acknowledgment of the relevant msgs_state_req, in and of itself.

+

Note that if it turns out suddenly that the other party is missing a message that appears to have been sent to it, the message must not be re-sent on its own with the same msg_id. Instead, it can be either wrapped in a container, or the status of the message can be checked using msgs_state_req and if the message wasn't received, then it must be re-sent with a new msg_id.

+

Voluntary Communication of Status of Messages

+

Either party may voluntarily inform the other party of the status of the messages transmitted by the other party.

+
msgs_all_info#8cc0d131 msg_ids:Vector long info:string = MsgsAllInfo
+

All message codes known to this party are enumerated, with the exception of those for which the +128 and the +16 flags are set. However, if the +32 flag is set but not +64, then the message status will still be communicated.

+

This message does not require an acknowledgment.

+

Extended Voluntary Communication of Status of One Message

+

Normally used by the server to respond to the receipt of a duplicate msg_id, especially if a response to the message has already been generated and the response is large. If the response is small, the server may re-send the answer itself instead. This message can also be used as a notification instead of resending a large message.

+
msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+

The second version is used to notify of messages that were created on the server not in response to an RPC query (such as notifications of new messages) and were transmitted to the client some time ago, but not acknowledged.

+

Currently, status is always zero. This may change in future.

+

This message does not require an acknowledgment.

+

Explicit Request to Re-Send Messages

+
msg_resend_req#7d861a08 msg_ids:Vector long = MsgResendReq;
+

The remote party immediately responds by re-sending the requested messages, normally using the same connection that was used to transmit the query. If at least one message with requested msg_id does not exist or has already been forgotten, or has been sent by the requesting party (known from parity), MsgsStateInfo is returned for all messages requested as if the MsgResendReq query had been a MsgsStateReq query as well.
+Max 8192 IDs are allowed per constructor.

+

Explicit Request to Re-Send Answers

+
msg_resend_ans_req#8610baeb msg_ids:Vector long = MsgResendReq;
+

The remote party immediately responds by re-sending answers to the requested messages, normally using the same connection that was used to transmit the query. MsgsStateInfo is returned for all messages requested as if the MsgResendReq query had been a MsgsStateReq query as well.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto_v1.html b/data/core.telegram.org/mtproto_v1.html new file mode 100644 index 0000000000..e3cdb7c384 --- /dev/null +++ b/data/core.telegram.org/mtproto_v1.html @@ -0,0 +1,229 @@ + + + + + MTProto Mobile Protocol v.1.0 (DEPRECATED) + + + + + + + + + + + + + +
+ +
+
+
+
+

MTProto Mobile Protocol v.1.0 (DEPRECATED)

+ +
+

This document describes MTProto v1.0, its status is DEPRECATED.
For information on encryption used in up-to-date Telegram clients, kindly see this document.

+
+

Related articles

+

+
+

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

+ +

General Description

+

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

+

The protocol is subdivided into three virtually independent components:

+
    +
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • +
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • +
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as, http, https, tcp, udp).
  • +
+ + +
+

Got questions about this setup? — Check out the Advanced FAQ!

+
+
Note 1
+

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

+
    +
  • server salt (64-Bit)
  • +
  • session id
  • +
  • message sequence number
  • +
  • message length
  • +
  • time
  • +
+
Note 2
+

See additional comments on our use of IGE, SHA-1 and message authentication.

+
Note 3
+

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

+

Brief Component Summary

+

High-Level Component (RPC Query Language/API)

+

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

+

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

+

There are several types of messages:

+
    +
  • RPC calls (client to server): calls to API methods
  • +
  • RPC responses (server to client): results of RPC calls
  • +
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • +
  • Message status query
  • +
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • +
+

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

+

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

+

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

+

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is what the OpenSSL library does.

+

Authorization and Encryption

+

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.). Multipart messages are encrypted as a single message.

+

For a technical specification, see Mobile Protocol: Detailed Description
The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

+

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

+
    +
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • +
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • +
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to those data.
  • +
+

Time Synchronization

+

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

+

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

+

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

+

Transport

+

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. There are three types of transport:

+
    +
  • HTTP
  • +
  • TCP
  • +
  • UDP
  • +
+

We shall examine the first two types.

+

HTTP Transport

+

Implemented over HTTP/1.1 (with keepalive) running over the traditional TCP Port 80. HTTPS is not used; the above encryption method is used instead.

+

An HTTP connection is attached to a session (or rather, to session + key identifier) specified in the most recent user query received; normally, the session is the same in all queries, but crafty HTTP proxies may corrupt that. A server may not return a message into an HTTP connection unless it belongs to the same session, and unless it is the server’s turn (an HTTP request had been received from the client to which a response has not been sent yet).

+

The overall arrangement is as follows. The client opens one or more keepalive HTTP connections to the server. If one or more messages need to be sent, they are made into a payload which is followed by a POST request to the URL/api to which the payload is transmitted as data. In addition, Content-Length, Keepalive, and Host are valid HTTP headers.

+

Having received the query, the server may either wait a little while (if the query requires a response following a short timeout) or immediately return a dummy response (only acknowledging the receipt of the container). In any case, the response may contain any number of messages. The server may at the same time send out any other messages it might be holding for the session.

+

In addition, there exists a special long poll RPC query (valid for HTTP connections only) which transmits maximum timeout T. If the server has messages for the session, they are returned immediately; otherwise, a wait state is entered until such time as the server has a message for the client or T seconds have elapsed. If no events occur in the span of T seconds, a dummy response is returned (special message).

+

If a server needs to send a message to a client, it checks for an HTTP connection that belongs to the required session and is in the “answering an HTTP request” state (including long poll) whereupon the message is added to the response container for the connection and sent to the user. In a typical case, there is some additional wait time (50 milliseconds) against the eventuality that the server will soon have more messages for the session.

+

If no suitable HTTP connection is available, the messages are placed in the current session’s send queue. However, they find their way there anyway until receipt is explicitly or indirectly confirmed by the client. For the HTTP protocol, sending the next query into the same HTTP connection is regarded as an implicit acknowledgment (not any more, the HTTP protocol also requires that explicit acknowledgments be sent); in other cases, the client must return an explicit acknowledgment within a reasonable time (it can be added to a container for the following request).

+

Important: if the acknowledgment fails to arrive on time, the message can be resent (possibly, in a different container). The parties must autonomously be ready for this and must store the identifiers of the most recent messages received (and ignore such duplicates rather than repeat actions). In order not to have the identifiers stored forever, there exist special garbage collection messages that take advantage of message identifier monotonicity.

+

If the send queue overflows or if messages stay in the queue for over 10 minutes, the server forgets them (or sends them to swap, no genius required). This may happen even faster, if the server is running out of buffer space (for example, because of serious network issues resulting in a large number of connections becoming severed).

+

TCP Transport

+

This is very similar to the HTTP transport. May also be implemented over Port 80 (to penetrate all firewalls) and even use the same server IP addresses. In this situation, the server understands whether HTTP or TCP protocol must be used for the connection, based on the first four incoming bytes (for HTTP, it is POST).

+

When a TCP connection is created, it is assigned to the session (and the authorization key) transmitted in the first user message, and subsequently used exclusively for this session (multiplexing arrangements are not allowed).

+

If a payload (packet) needs to be transmitted from server to client or from client to server, it is encapsulated as follows: 4 length bytes are added at the front (to include the length, the sequence number, and CRC32; always divisible by 4) and 4 bytes with the packet sequence number within this TCP connection (the first packet sent is numbered 0, the next one 1, etc.), and 4 CRC32 bytes at the end (length, sequence number, and payload together).

+

There is an abridged version of the same protocol: if the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01..0x7e = data length divided by 4; or 0x7f followed by 3 length bytes (little endian) divided by 4) followed by the data themselves (sequence number and CRC32 not added). In this case, server responses look the same (the server does not send 0xefas the first byte).

+

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used: if the client sends 0xeeeeeeee as the first int (four bytes), then packet length is encoded always by four bytes as in the original version, but the sequence number and CRC32 are omitted, thus decreasing total packet size by 8 bytes.

+

The full, the intermediate and the abridged versions of the protocol have support for quick acknowledgment. In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet. They are the 32 higher-order SHA1 bits of the encrypted portion of the packet with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

+

There are no implicit acknowledgments for the TCP transport: all messages must be acknowledged explicitly. Most frequently, acknowledgments are placed in a container with the next query or response if it is transmitted in short order. For example, this is almost always the case for client messages containing RPC queries: the acknowledgment normally arrives with the RPC response.

+

In the event of an error, the server may send a packet whose payload consists of 4 bytes as the error code. For example, Error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/passport.html b/data/core.telegram.org/passport.html new file mode 100644 index 0000000000..2a175b5ae2 --- /dev/null +++ b/data/core.telegram.org/passport.html @@ -0,0 +1,690 @@ + + + + + Telegram Passport Manual + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram Passport Manual

+ +
+ +

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn't have access to the users' personal information thanks to end-to-end encryption.

+

Overview

+

From the perspective of a service that requires real-world ID, the process looks like this:

+
    +
  • A user presses "Log in with Telegram" on your website or in your app.
  • +
  • You request the data you need.
  • +
  • The user accepts your privacy policy and agrees to share their data.
  • +
  • The user's Telegram app downloads and decrypts the data you requested from the end-to-end encrypted storage on Telegram.
  • +
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • +
  • The user's app encrypts the data with your public key and sends it to you.
  • +
  • You decrypt the data, check it for errors and re-request any missing or invalid information.
  • +
  • You sign the user up for your service. Tada!
  • +
+

Check out this example to see Telegram Passport in action.

+
+

To learn more about Telegram Passport from the perspective of a user, please see this blog post and the technical MTProto documentation. +See this page if you're interested in encryption algorithms used on Telegram's side.

+
+

Recent changes

+

August 25, 2018

+

Telegram Passport 1.1 (blog post)

+
    +
  • Added support for requesting several documents of one type. See the new objects PassportScope, PassportScopeElement, PassportScopeElementOneOfSeveral and PassportScopeElementOne.
  • +
  • Added support for middle names.
  • +
  • Added support for requesting certified English translations for documents (see Fields; new field translation also added to the SecureValue object). Note: Please only request translations after you have received a valid document that requires one.
  • +
  • Added support for requesting names in the language of the user's country of residence (if other than English). New fields first_name_native, last_name_native and middle_name_native added to the PersonalDetails object.
  • +
  • Replaced the payload parameter with the new parameter nonce, which serves the same function, to make the purpose more obvious (see Request Parameters and the Credentials object).
  • +
  • Updated the example page to support the new functionality.
  • +
+

Setting Up Telegram Passport

+

To integrate Telegram Passport into your login or verification flow, you need a working Telegram bot (see this page for information on how to get one).

+

To request data from Telegram Passport users, your bot will need to generate a pair of encryption keys.

+

Generating a private key

+

First, use a console to generate a private key:

+
openssl genrsa 2048 > private.key
+

WARNING: Keep your private key SECRET!

+

Generating your public key

+

Then use the console to print the corresponding public key:

+
openssl rsa -in private.key -pubout
+

Use the /setpublickey command with @BotFather to connect this public key with your bot.

+

Privacy Policy

+

Add a link to your Privacy Policy by using the /setprivacypolicy command. Users will see this link when offered to authorize you to access their data.

+

Requesting Information

+

SDK

+

To request information stored in a Telegram Passport, use one of these SDKs:

+ +

Request Parameters

+

Use the following parameters to request information with the SDK:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParametersTypeRequired
bot_idIntegerYes
scopePassportScopeYes
public_keyStringYes
nonceStringYes
+

PassportScope

+

This object represents the data to be requested.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dataArray of PassportScopeElementList of requested elements, each type may be used only once in the entire array of PassportScopeElement objects
vIntegerScope version, must be 1
+

PassportScopeElement

+

This object represents a requested element, should be one of:

+ +

PassportScopeElementOneOfSeveral

+

This object represents several elements one of which must be provided.

+ + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
one_ofArray of PassportScopeElementOneList of elements one of which must be provided; must contain either several of “passport”, “driver_license”, “identity_card”, “internal_passport” or several of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
translationBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
+

PassportScopeElementOne

+

This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringElement type. One of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration", "phone_number", "email"
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "passport", "driver_license", "identity_card" and "internal_passport"
translationBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration". Note: We suggest to only request translations after you have received a valid document that requires one.
native_namesBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "personal_details"
+

You can also use the special type "id_document" as an alias for one of "passport", "driver_license", "identity_card" and the special type "address_document" as an alias for one of "utility_bill", "bank_statement", "rental_agreement". +So {"type":"id_document",selfie:true} is equal to {"one_of":["passport","driver_license","identity_card"],selfie:true}.

+

Fields

+

Your bot can request personal details, one or several types of identity document, residential address, one or several types of proof of address document, a phone number, or an email address. You can also request optional selfies with the document and certified English translations of the document. +This is just a list of data types that can be requested, and the encrypted objects that will contain such data.

+
+

Note: We suggest to only request English translations after you have received a valid document that requires one.

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameKeyTypeDescription
personal_detailsdataPersonalDetailsPersonal Details
passportdataIdDocumentDataPassport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
internal_passportdataIdDocumentDataInternal Passport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
driver_licensedataIdDocumentDataDriver License
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
identity_carddataIdDocumentDataIdentity Card
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
addressdataResidentialAddressAddress
utility_billfilesArray of PassportFileUtility Bill
translationOptional. Array of PassportFile
bank_statementfilesArray of PassportFileBank Statement
translationOptional. Array of PassportFile
rental_agreementfilesArray of PassportFileRental Agreement
translationOptional. Array of PassportFile
passport_registrationfilesArray of PassportFileRegistration Page in the Internal Passport
translationOptional. Array of PassportFile
temporary_registrationfilesArray of PassportFileTemporary Registration
translationOptional. Array of PassportFile
phone_numberStringPhone number
emailStringEmail
+

PersonalDetails

+

This object represents personal details.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
first_nameStringFirst Name
last_nameStringLast Name
middle_nameStringOptional. Middle Name
birth_dateStringDate of birth in DD.MM.YYYY format
genderStringGender, male or female
country_codeStringCitizenship (ISO 3166-1 alpha-2 country code)
residence_country_codeStringCountry of residence (ISO 3166-1 alpha-2 country code)
first_name_nativeStringFirst Name in the language of the user's country of residence
last_name_nativeStringLast Name in the language of the user's country of residence
middle_name_nativeStringOptional. Middle Name in the language of the user's country of residence
+

ResidentialAddress

+

This object represents a residential address.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
street_line1StringFirst line for the address
street_line2StringOptional. Second line for the address
cityStringCity
stateStringOptional. State
country_codeStringISO 3166-1 alpha-2 country code
post_codeStringAddress post code
+

IdDocumentData

+

This object represents the data of an identity document.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
document_noStringDocument number
expiry_dateStringOptional. Date of expiry, in DD.MM.YYYY format
+

PassportFile

+

This object represents a PassportFile related to a document. The file is up to 10MB in size and in the .jpg format.

+

Receiving information

+

When the user confirms your request by pressing the 'Authorize' button, the Bot API sends an Update with the field passport_data to the bot that contains encrypted Telegram Passport data.

+
+

Note that all base64-encoded fields should be decoded before use.

+
+

Decrypting data

+

To decrypt the received data, first, decrypt the credentials contained in EncryptedCredentials.

+
    +
  1. +

    Decrypt the credentials secret ( secret field in EncryptedCredentials) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)

    +
  2. +
  3. +

    Use this secret and the credentials hash ( hash field in EncryptedCredentials) to calculate credentials_key and credentials_iv as described below:

    +
     credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    + credentials_key = slice( credentials_secret_hash, 0, 32 )
    + credentials_iv = slice( credentials_secret_hash, 32, 16 )
    +
  4. +
  5. +

    Decrypt the credentials data ( data field in EncryptedCredentials) by AES256-CBC using these credentials_key and credentials_iv. IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )

    +
  6. +
  7. +

    Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.

    +
  8. +
+
+

Note that all hashes represent as raw binary data, not hexits

+
+

Credentials

+

Credentials is a JSON-serialized object.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
secure_dataSecureDataCredentials for encrypted data
nonceStringBot-specified nonce
+

IMPORTANT: Make sure that the nonce is the same as was passed in the request.

+

SecureData

+

This object represents the credentials required to decrypt encrypted data. All fields are optional and depend on fields that were requested.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
personal_detailsSecureValueOptional. Credentials for encrypted personal details
passportSecureValueOptional. Credentials for encrypted passport
internal_passportSecureValueOptional. Credentials for encrypted internal passport
driver_licenseSecureValueOptional. Credentials for encrypted driver license
identity_cardSecureValueOptional. Credentials for encrypted ID card
addressSecureValueOptional. Credentials for encrypted residential address
utility_billSecureValueOptional. Credentials for encrypted utility bill
bank_statementSecureValueOptional. Credentials for encrypted bank statement
rental_agreementSecureValueOptional. Credentials for encrypted rental agreement
passport_registrationSecureValueOptional. Credentials for encrypted registration from internal passport
temporary_registrationSecureValueOptional. Credentials for encrypted temporary registration
+

SecureValue

+

This object represents the credentials required to decrypt encrypted values. All fields are optional and depend on the type of fields that were requested.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dataDataCredentialsOptional. Credentials for encrypted Telegram Passport data. Available for "personal_details", "passport", "driver_license", "identity_card", "internal_passport" and "address" types.
front_sideFileCredentialsOptional. Credentials for an encrypted document's front side. Available for "passport", "driver_license", "identity_card" and "internal_passport".
reverse_sideFileCredentialsOptional. Credentials for an encrypted document's reverse side. Available for "driver_license" and "identity_card".
selfieFileCredentialsOptional. Credentials for an encrypted selfie of the user with a document. Available for "passport", "driver_license", "identity_card" and "internal_passport".
translationArray of FileCredentialsOptional. Credentials for an encrypted translation of the document. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration".
filesArray of FileCredentialsOptional. Credentials for encrypted files. Available for "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types.
+

DataCredentials

+

These credentials can be used to decrypt encrypted data from the data field in EncryptedPassportElement.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
data_hashStringChecksum of encrypted data
secretStringSecret of encrypted data
+
    +
  1. +

    To decrypt data, use the corresponding secret and data_hash from DataCredentials as described below:

    +
     data_secret_hash = SHA512( data_secret + data_hash )
    + data_key = slice( data_secret_hash, 0, 32 )
    + data_iv = slice( data_secret_hash, 32, 16 )
    +
  2. +
  3. +

    Use AES256-CBC with this data_key and data_iv to decrypt the data (the data field in EncryptedPassportElement). IMPORTANT: At this step, make sure that data_hash from the credentials is equal to SHA256( data ).

    +
  4. +
  5. +

    The data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of the padding (including this byte). Remove padding to get the data.

    +
  6. +
  7. +

    The data is a JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on type.

    +
  8. +
+

FileCredentials

+

These credentials can be used to decrypt encrypted files from the front_side, reverse_side, selfie, files and translation fields in EncryptedPassportElement.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_hashStringChecksum of encrypted file
secretStringSecret of encrypted file
+
    +
  1. +

    To decrypt the file, use the corresponding secret and file_hash from FileCredentials as described below:

    +
     file_secret_hash = SHA512( file_secret + file_hash )
    + file_key = slice( file_secret_hash, 0, 32 )
    + file_iv = slice( file_secret_hash, 32, 16 )
    +
  2. +
  3. +

    Download the encrypted file using the getFile method.

    +
  4. +
  5. +

    Use AES256-CBC with this file_key and file_iv to decrypt the content of the file. IMPORTANT: At this step, make sure that file_hash from the credentials is equal to SHA256( file_content ).

    +
  6. +
  7. +

    The content of the file is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of the padding (including that byte). Remove padding to get the file content.

    +
  8. +
+

Fixing errors

+

If the data you received contains errors, the bot can use the setPassportDataErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/passport/encryption.html b/data/core.telegram.org/passport/encryption.html new file mode 100644 index 0000000000..86a46fec6c --- /dev/null +++ b/data/core.telegram.org/passport/encryption.html @@ -0,0 +1,606 @@ + + + + + Telegram Passport Encryption Details + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram Passport Encryption Details

+ +
+ +

Telegram Passport data is stored encrypted End-to-End which means that the Telegram server does not have access to the data and only functions as a storage for encrypted data it can't decipher. Encryption and decryption are handled exclusively by the Telegram clients, which are open source.

+

Overview

+

To encrypt each particular element of Telegram Passport, the client generates a random secret. The secret is a 32-byte number with the modulo 255 sum of bytes equal to 239. This secret is in turn encrypted with the passport_secret that is generated when the user creates their Telegram Passport. passport_secret is encrypted with the user's password and is stored encrypted in the Telegram Cloud.

+

Passport Secret

+

The passport secret is one of the secret parameters used to encrypt the data uploaded by the user to the Telegram Cloud.

+

When first setting up Telegram Passport it must be created, encrypted and uploaded as described in Passport Secret Encryption.

+

When using Telegram Passport normally, it must be downloaded and decrypted for use as described in Passport Secret Decryption.

+

The passport secret must also be downloaded, re-encrypted and re-uploaded as described in Passport Secret Encryption if a new, more secure encryption algorithm is defined in a newer version of Telegram or the 2FA password is updated.

+

Passport Secret Encryption

+

First of all, server-side passport parameters are fetched, schema:

+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+
+securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+
+---functions---
+
+account.getPassword#548a30f5 = account.Password;
+

When Telegram Passport is first used, the client generates a passport_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239), using a part of server-generated random secure_random from account.password as an additional source of entropy for OpenSSL (when re-encrypting the passport_secret with a more secure algorithm or after a 2FA password change, the previous passport_secret is used, instead). +Then passport_secret is then encrypted using the user's password and hashed using the schema and parameters specified in the new_algo field of account.password.

+

The server should always return a securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 constructor in the new_algo field. +If securePasswordKdfAlgoUnknown is returned, the remotely stored secret is encrypted using a new algorithm, not supported by the current client: the user should update their app.

+

The other constructors may be used only when decrypting old passport parameters generated by a legacy client; in this case, the passport secret should be re-encrypted and updated using new_algo.

+ +

Subsequently, the client receives the encrypted passport_secret from the server and decrypts it after the user enters their password ».

+

In case the password is changed or a more secure algorithm is introduced in an update of the API, the client re-encrypts the passport_secret using the new password. +If the password is disabled, all Telegram Passport data is lost.

+

Passport Secret Decryption

+

Schema:

+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
+
+account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
+---functions---
+
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
+

The client requests the user's 2FA password and generates the SRP paramaters to be passed to account.getPasswordSettings.

+

If the password is correct, an account.passwordSettings constructor with secureSecretSettings is returned.

+

encrypted_passport_secret, passport_secret_fingerprint parameters are extracted from the secureSecretSettings constructor:

+
encrypted_passport_secret = secureSecretSettings.secure_secret
+passport_secret_fingerprint = secureSecretSettings.secure_id
+

The combined passport_secret_salt is extracted from the SecurePasswordKdfAlgo.

+
passport_secret_salt = SecurePasswordKdfAlgo.salt
+

Similar to passport secret encryption, the following process is used to decrypt and verify the encrypted_passport_secret:

+
    +
  • +

    The user's 2FA plaintext password is hashed using the specified algorithm.

    + +
  • +
  • +

    The secret_key and iv parameters are extracted from the generated password_hash

    +
    secret_key = slice( password_hash, 0, 32 )
    +iv = slice( password_hash, 32, 16 )
    +
  • +
  • +

    The encrypted_passport_secret is decrypted using AES256-CBC with the key secret_key and iv:

    +
    passport_secret = AES256_CBC_DEC(encrypted_passport_secret, secret_key, iv)
    +
  • +
  • +

    The passport_secret is verified by generating and checking the fingerprint:

    +
    my_passport_secret_fingerprint = long( slice( SHA256( passport_secret ), 0, 8 ) )
    +

    The client must verify that passport_secret_fingerprint is indeed equal to my_passport_secret_fingerprint.

    +
  • +
+

The passport_secret can now be used to decrypt encrypted passport data stored on telegram servers:

+

Data and File Encryption

+

Encryption

+

To encrypt Telegram Passport data, the client generates a data_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). The the data is encrypted according to the following scheme:

+ +

Packing

+
SecureData
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
    +
  • data is an encrypted and padded (see Encryption) JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on the chosen type. +Data must be in JSON format and not TL, as it has to be passed directly to the service using E2E encryption, without the bot API middleman to convert TL objects.
  • +
  • data_hash is the data_hash
  • +
  • secret is the encrypted_data_secret
  • +
+

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
+
InputSecureFile
+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+---functions---
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+

Files (JPG format, max. 10MB) are encrypted and padded (see Encryption), and then uploaded chunk by chunk as described in files », except that instead of generating an inputFile, an inputSecureFile should be generated, instead.

+
    +
  • As for secret chat files, the md5_checksum is to be set to the MD5 hash of the encrypted file, for a server-side integrity check.
  • +
  • The file_hash field should be set to the data_hash of the data.
  • +
  • The secret field is the encrypted_data_secret.
  • +
+
SecurePlainData
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+---functions---
+
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;
+account.verifyEmail#ecba39db email:string code:string = Bool;
+
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
+

The email/phone is passed in plaintext using the respective SecurePlainData constructor. +To verify a phone number or email and use it in Telegram Passport, use the appropriate methods:

+ +

The flow is similar to the one used for logging in:

+
    +
  • Send email/phone code using the appropriate account.sendVerify*Code method
  • +
  • Pass the received code to the appropriate account.verify* method
  • +
  • Only for phone code verification, you can also resend/cancel the phone code using auth.resendCode/auth.cancelCode, as for logging in.
  • +
+

For more info, see the authorization docs.

+

When to use each constructor.

+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;
+
+securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
+inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
+

The schema for the inputSecureValue constructor defines the constructor to use for each field.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
+

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
+

Fetching and deleting stored passport data

+
---functions---
+
+account.getAllSecureValues#b288bc7d = Vector<SecureValue>;
+account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
+

The above methods can be used to fetch or remove encrypted Telegram Passport files stored in the Telegram Cloud by document type.

+

Passport Credentials

+

When a service requests data, it passes a nonce to the client. The nonce is a cryptographically secure unique identifier which allows the service to identify a request when receiving data as well as confirm the integrity of the data. The Telegram server doesn't have access to this nonce.

+

Once the user authorizes the Telegram Passport data transfer, the client forms the credentials (Credentials JSON object). Credentials contain the data_hash and data_secret from each element of Telegram Passport to which the user has allowed access. In addition to this, the credentials will always contain the nonce that the client received from the service at the initiation of the request.

+

Credentials are then passed to the service through the Bot API in encrypted form. To encrypt the credentials, the client generates a credentials_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). Then the credentials are encrypted according to the following scheme:

+
    +
  • +

    Credentials are padded to a length which is divisible by 16 bytes. To achieve this, 32 to 255 bytes are added at the beginning, where the first byte always holds the number of added bytes and the rest are random.

    +
  • +
  • +

    A hash of the padded credentials credentials_hash is calculated:

    +
    credentials_hash = SHA256( credentials )
    +
  • +
  • +

    The encryption key credentials_key is calculated:

    +
    credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    +credentials_key = slice( credentials_secret_hash, 0, 32 )
    +iv = slice( credentials_secret_hash, 32, 16 )
    +
  • +
  • +

    Credentials are encrypted using AES256-CBC with the key credentials_key and iv.

    +
    encrypted_credentials = AES256-CBC-ENC(credentials, credentials_key, iv)
    +
  • +
  • +

    credentials_secret is encrypted with the public RSA-key of the service with OPENSSL_PKCS1_OAEP_PADDING.

    +
    encrypted_credentials_secret = RSA-ENC(credentials_secret, key, OPENSSL_PKCS1_OAEP_PADDING)
    +
  • +
  • +

    The encrypted credentials are passed to the service via the MTProto API together with the encrypred credentials_secret and credentials_hash. Along with the credentials, the service receives from the Telegram Cloud the data it requested in encrypted form. See Submitting the Passport Form and PassportData:

    +
    secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
    +
  • +
  • +

    data is the encrypted_credentials

    +
  • +
  • +

    hash is the credentials_hash

    +
  • +
  • +

    secret is the encrypted_credentials_secret

    +
  • +
+

Then the service decrypts the data as described here.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/passport/example.html b/data/core.telegram.org/passport/example.html new file mode 100644 index 0000000000..68d5d0c84e --- /dev/null +++ b/data/core.telegram.org/passport/example.html @@ -0,0 +1,585 @@ + + + + + Example + + + + + + + + + + + + + + + +
+ +
+
+
+
+

Example

+ +

If you'd like to test Telegram Passport, use this page to request data. If you'd like to check out a real-life implementation, please see this blog post for examples of services that have integrated Telegram Passport.

+

Request Telegram Passport Data

+

+

+
+
+
+ + +
+
+
+
+ +
+ +
+ +
+
+ +
+
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ + +
+
+
+
+ +
+ +
+ +
+ +
+
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ + +
+
+
+
+ +
+ +
+ +
+
+ +
+
+ +
+
+ + +
+
+
+ +

+
+
+

Note that the passport demo bot will only store data for 1 hour and then discard it. After logging in here, you can use the logout button on this page to reset your session.

+
+ +
+ +
+
+ +
+ + + + + + + + + diff --git a/data/core.telegram.org/passport/sdk-android.html b/data/core.telegram.org/passport/sdk-android.html new file mode 100644 index 0000000000..5060a7f97e --- /dev/null +++ b/data/core.telegram.org/passport/sdk-android.html @@ -0,0 +1,180 @@ + + + + + Android SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

Android SDK

+ +
+ +

The Android SDK helps you easily integrate Telegram Passport requests into your Android-based apps. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Installing from Maven

+

Telegram Passport SDK is available from the Maven repository. +Add this line to the dependencies section in your build.gradle:

+
compile 'org.telegram:passport:1.1'
+

and sync your project.

+

Adding as a module

+

Download the library, unzip it and copy the library project to the root of your project directory (the one with settings.gradle and gradle.properties). Then, make the following changes to your Gradle scripts.

+

In settings.gradle, add ':telegrampassport' to includes:

+
include ':app', ':telegrampassport'
+

In the build.gradle file for your app, add this line to the dependencies section:

+
compile ':telegrampassport'
+

and sync your project.

+

Usage

+

Adding the button

+

The SDK provides the "Log in with Telegram" button which we recommend using for a consistent user experience across different apps. You can either add it from your Java code:

+
TelegramLoginButton telegramButton;
+// ...
+telegramButton=new TelegramLoginButton(this);
+// Optionally you can change the roundness of the button corners
+// to better fit your design.
+telegramButton.setCornerRoundness(1f);
+viewGroupOfSomeSort.addView(telegramButton, ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT);
+

Or from XML:

+
 <org.telegram.passport.TelegramLoginButton
+             android:layout_width="wrap_content"
+             android:layout_height="wrap_content"
+             app:cornerRoundness="0.5"/>
+

Requesting authorization

+

The button doesn't do anything by itself; you need to set an OnClickListener on it to start the authorization flow (replace the comments with actual parameters):

+
private static final int TG_PASSPORT_RESULT=352; // this can be any integer less than 0xFFFF
+// ...
+telegramButton.setOnClickListener(new View.OnClickListener(){
+@Override
+public void onClick(View view){
+    TelegramPassport.AuthRequest req=new TelegramPassport.AuthRequest();
+    req.botID=/* your bot ID here */;
+    req.publicKey=/* your bot public key here */;
+    req.nonce=/* a unique nonce to pass to the bot server */;
+    // Request either a passport or an ID card with selfie, a driver license, personal details with
+    // name as it appears in the documents, address with any address document, and a phone number.
+    // You could also pass a raw JSON object here if that's what works better for you
+    // (for example, if you already get it from your server in the correct format).
+    req.scope=new PassportScope(
+        new PassportScopeElementOneOfSeveral(PassportScope.PASSPORT, PassportScope.IDENTITY_CARD).withSelfie(),
+        new PassportScopeElementOne(PassportScope.PERSONAL_DETAILS).withNativeNames(),
+        PassportScope.DRIVER_LICENSE,
+        PassportScope.ADDRESS,
+        PassportScope.ADDRESS_DOCUMENT,
+        PassportScope.PHONE_NUMBER
+    );
+    TelegramPassport.request(MyActivity.this, req, TG_PASSPORT_RESULT);
+}});
+

If you need more control over the process, the TelegramPassport class contains several more methods:

+
    +
  • getAuthIntent(AuthParams) returns an Intent for you to use in startActivityForResult if you need to do that in some special way. Be sure to check that an app is present that can handle this intent before starting it by using PackageManager or intent.resolveActivity.
  • +
  • showAppInstallAlert(Activity) shows an alert that the user needs to install Telegram in order to continue. This is intended to be used together with the previous method for the cases when the app isn't installed.
  • +
+

Handling the result

+

The result is delivered via the onActivityResult method in your activity with the request code you passed to TelegramPassport.request. Currently, the only meaningful parameter is resultCode, which is RESULT_OK if the authorization was successful and RESULT_CANCELED otherwise.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/passport/sdk-ios-mac.html b/data/core.telegram.org/passport/sdk-ios-mac.html new file mode 100644 index 0000000000..057cfb4e6d --- /dev/null +++ b/data/core.telegram.org/passport/sdk-ios-mac.html @@ -0,0 +1,246 @@ + + + + + iOS & macOS SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

iOS & macOS SDK

+ +
+ +

TGPassportKit helps you easily integrate Telegram Passport requests into your iOS & macOS apps. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Installing using Cocoapods

+

To install TGPassportKit via Cocoapods add the following to your Podfile:

+
target 'MyApp' do
+  pod 'TGPassportKit' 
+end
+

then run pod install in your project root directory.

+

Installing using Carthage

+

Add the following line to your Cartfile:

+
github "telegrammessenger/TGPassportKit"
+

then run carthage update, and you will get the latest version of TGPassportKit in your Carthage folder.

+

Project Setup

+

Configure Your Info.plist

+

Configure your Info.plist by right-clicking it in Project Navigator, choosing Open As > Source Code and adding this snippet: +Replace {bot_id} with your value

+
<key>CFBundleURLTypes</key>
+<array>
+  <dict>
+  <key>CFBundleURLSchemes</key>
+  <array>
+    <string>tgbot{bot_id}</string>
+  </array>
+  </dict>
+</array>
+<key>LSApplicationQueriesSchemes</key>
+<array>
+  <string>tg</string>
+</array>
+

Connect AppDelegate methods

+

Add this code to your UIApplicationDelegate implementation

+
#import <TGPassportKit/TGPAppDelegate.h>
+
+- (BOOL)application:(UIApplication *)application
+            openURL:(NSURL *)url
+            options:(NSDictionary<UIApplicationOpenURLOptionsKey, id> *)options {
+    BOOL handledByPassportKit = [[TGPAppDelegate sharedDelegate] application:application
+                                                                     openURL:url
+                                                                     options:options];
+
+    return YES;
+}
+

If you support iOS 9 and below, also add this method:

+
- (BOOL)application:(UIApplication *)application 
+            openURL:(NSURL *)url 
+  sourceApplication:(nullable NSString *)sourceApplication 
+         annotation:(id)annotation {
+    BOOL handledByPassportKit = [[TGPAppDelegate sharedDelegate] application:application
+                                                                     openURL:url
+                                                           sourceApplication:sourceApplication
+                                                                  annotation:annotation];
+
+    return YES;
+}
+

Usage

+

Add Telegram Passport Button

+

To add the Telegram Passport button, add the following code to your view controller: +Replace {bot_id}, {bot_public_key} and {request_nonce} with your values

+
#import <TGPassportKit/TGPButton.h>
+
+@interface ViewController <TGPButtonDelegate>
+
+@end
+
+@implementation ViewController
+
+- (void)viewDidLoad {
+  [super viewDidLoad];
+
+  TGPButton *button = [[TGPButton alloc] init];
+  button.botConfig = [[TGPBotConfig alloc] initWithBotId:{bot_id} 
+                                               publicKey:@"{bot_public_key}"];
+  button.scope = [[TGPScope alloc] initWithJSONString:@"{\"data\":[\"id_document\",\"address_document\",\"phone_number\"],\"v\":1}"];
+// You can also construct a scope using provided data type classes like this: 
+// button.scope = [[TGPScope alloc] initWithTypes:@[[[TGPPersonalDetails alloc] init], [[TGPIdentityDocument alloc] initWithType:TGPIdentityDocumentTypePassport selfie:true translation:true]]];
+  button.nonce = @"{request_nonce}";
+  button.delegate = self;
+  [self.view addSubview:button];
+}
+
+- (void)passportButton:(TGPButton *)passportButton 
+ didCompleteWithResult:(TGPRequestResult)result 
+                 error:(NSError *)error {
+    switch (result) {
+        case TGPRequestResultSucceed:
+            NSLog(@"Succeed");
+            break;
+
+        case TGPRequestResultCancelled:
+            NSLog(@"Cancelled");
+            break;
+
+        default:
+            NSLog(@"Failed");
+            break;
+    }
+}
+
+@end
+

...or Implement Your Own Behavior

+

If you want to design a custom UI and behavior, you can invoke a Passport request like this: +Replace {bot_id}, {bot_public_key} and {request_nonce} with your values

+
#import <TGPassportKit/TGPRequest.h>
+
+- (void)performPassportRequest 
+{
+    TGPBotConfig *botConfig = [[TGPBotConfig alloc] initWithBotId:{bot_id} 
+                                                        publicKey:@"{bot_public_key}"];
+    TGPRequest *request = [[TGPRequest alloc] initWithBotConfig:botConfig];
+    [request performWithScope:[[TGPScope alloc] initWithJSONString:@"{\"data\":[\"id_document\",\"phone_number\"],\"v\":1}"] 
+                      payload:@"{request_nonce}" 
+            completionHandler:^(TGPRequestResult result, NSError * _Nullable error) {
+        switch (result) {
+            case TGPRequestResultSucceed:
+                NSLog(@"Succeed");
+                break;
+
+            case TGPRequestResultCancelled:
+                NSLog(@"Cancelled");
+                break;
+
+            default:
+                NSLog(@"Failed");
+                break;
+        }
+    }];
+}
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/passport/sdk-javascript.html b/data/core.telegram.org/passport/sdk-javascript.html new file mode 100644 index 0000000000..504328eb0c --- /dev/null +++ b/data/core.telegram.org/passport/sdk-javascript.html @@ -0,0 +1,258 @@ + + + + + Javascript SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

Javascript SDK

+ +
+ +

The Javascript SDK helps you easily integrate Telegram Passport requests into your website. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Download and include the Javascript SDK in the head section of your page:

+
<script src="telegram-passport.js"></script>
+

Usage

+

Simply call Telegram.Passport.createAuthButton to create the default Telegram Passport button:

+
<div id="telegram_passport_auth"></div>
+<script>
+  Telegram.Passport.createAuthButton('telegram_passport_auth', {
+    bot_id:       123456, // place id of your bot here
+    scope:        {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
+    public_key:   '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
+    nonce:        'ab2df83746a87d2f3bd6...', // place nonce here
+    callback_url: 'https://example.com/callback/' // place callback url here
+  });
+</script>
+
+

Note that if you use a Content-Security-Policy (CSP) header with the frame-src/child-src directive you should allow tg: source to prevent errors in some browsers (e.g. Firefox)

+
+

createAuthButton

+ + + + + + + + + + + + + + + + + + + + + + + +
ParametersTypeRequired
elementString or DOMNodeYes
auth_paramsAuthParameters or FunctionYes
optionsAuthButtonOptionsOptional
+

AuthParameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
bot_idIntegerUnique identifier for the bot
scopePassportScopeA JSON-serialized object describing the data you want to request
public_keyStringPublic key of your bot
nonceStringBot-specified nonce
callback_urlStringOptional. URL to which the user will be redirected.
+

AuthButtonOptions

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringOptional. Text on the button. Defaults to "Log In With Telegram".
radiusIntegerOptional. Radius of the button and tooltip in px. Defaults to 23.
tooltip_textStringOptional. Text on the tooltip. Defaults to "Please install Telegram to use this option.".
tooltip_positionStringOptional. Tooltip position. One of "top", "bottom", "left", "right". Defaults to "bottom".
tooltip_forceBooleanOptional. Always show a tooltip. Defaults to false.
+

You can also create your custom button. Do not forget about the tooltip. You should add an onclick listener to the button which calls the Telegram.Passport.auth(auth_params, tooltip_toggle); method:

+
<button id="telegram_passport_auth">Log In With Telegram</button>
+<script>
+  var auth_button = document.getElementById('telegram_passport_auth');
+  var auth_params = {
+    bot_id:        XXXXXX, // place id of your bot here
+    scope:         {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
+    public_key:    '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
+    nonce:         'ab2df83746a87d2f3bd6...', // place nonce here
+    callback_url:  'https://example.com/callback/' // place callback url here
+  };
+  auth_button.addEventListener('click', function() {
+    Telegram.Passport.auth(auth_params, function(show) {
+      if (show) {
+        // some code to show tooltip
+      } else {
+        // some code to hide tooltip
+      }
+    });
+  }, false);
+</script>
+

Receiving information

+

When the user confirms your request by pressing the 'Authorize' button, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=success and the Bot API will send the bot an Update with the field passport_data which contains encrypted Telegram Passport data.

+

If the user cancels your request, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=cancel.

+

If an error occurs during the request, the user will be redirected to the URL specified in the callback_url with the parameter tg_passport=error. The parameter error will contain one of the following values: BOT_INVALID, PUBLIC_KEY_REQUIRED, PUBLIC_KEY_INVALID, SCOPE_EMPTY, NONCE_EMPTY.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/reproducible-builds.html b/data/core.telegram.org/reproducible-builds.html new file mode 100644 index 0000000000..d0f23db600 --- /dev/null +++ b/data/core.telegram.org/reproducible-builds.html @@ -0,0 +1,488 @@ + + + + + Reproducible Builds for iOS and Android + + + + + + + + + + + + + +
+ +
+
+
+
+

Reproducible Builds for iOS and Android

+ +

This page contains instructions for verifying that Telegram's open source code is exactly the same as the code that is used to build the apps that are available in the App Store, Google Play and directly on the Telegram website.

+

Warning: Telegram supports reproducible builds as of version 5.13. Bear in mind that, at this stage, the verification process should be considered experimental. We will be updating our apps and these instructions to make this process as straightforward as possible.

+ +
+

Please read the relevant notes and troubleshooting section carefully.

+
+
+
+ Dude in a jacket inspecting the hologram of a mechanical dog to verify it's built according to the blueprints provided. +
+ +

Reproducible Builds for Android

+

Step 1. Install Docker

+

Docker can be obtained here. Once the installation is complete, log into your Docker account > Preferences > Advanced and configure the amount of resources Docker may use:

+
+ +

Docker Performance

+
+ +

We recommend using the maximum amount allowed by your system's hardware, in order to speed up the build time.

+

Step 2. Confirm which version you have installed on your Android device

+

You can find the version/build number at the bottom of the Settings page. Note that Telegram supports reproducible builds starting with version 5.13.

+
+ +

App Version

+
+ +

The commit tag to checkout source code for the example above will be release-5.13.0_1821.

+
+

Please make sure that you're using the correct version and build number of the version you want to check (and not the one from this example 😈).

+
+

The part after the version number will help you know in which folder to look for the correct APK when you've finished building the app (Step 4):

+
    +
  • “Direct” after version number means that the APK will be inside the “afat/standalone” folder.
  • +
  • “Universal” after version number means that the APK will be inside the “afat/release” folder.
  • +
  • If you have Android Version 6.0 or greater, your APK folder will have the “_SDK23” suffix.
  • +
  • “arm64-v8a” - folder name will start with “arm64”.
  • +
  • “armeabi-v7” - folder name will start with “armv7”.
  • +
  • “x86” - folder name will start with “x86”.
  • +
  • “x86_64” - folder name will start with “x64”.
  • +
+
+ +

APK Folders

+
+ + +

Step 3. Obtain the source code

+

Open Terminal, run the commands:
git clone https://github.com/DrKLO/Telegram.git $HOME/telegram-android
cd $HOME/telegram-android
git checkout release-{VERSION AND BUILD NUMBER FROM STEP 2}

+

For our example, the command would be:
git checkout release-5.13.0_1821

+
+ +
+ +

Step 4. Build the app

+

Open Terminal, run the commands:
cd $HOME/telegram-android
docker build -t telegram-build .

+
+ +
+ +

docker run --rm -v "$PWD":/home/source telegram-build

+
+ +
+ +

These commands will produce 9 different APKs for different target SDK versions and CPU ABIs.

+

These APKs can be found in:
$HOME/telegram-android/TMessagesProj/build/outputs/apk/

+

Use the folder name from Step 2 to find the correct folder that holds the same APK as installed on your device. For example, for non-universal Android 9.0 arm64-v8a, the path to your APK will be:
$HOME/telegram-android/TMessagesProj/build/outputs/apk/arm64_SDK23/release/app.apk
Copy this APK to the root source directory by running this command in Terminal:
cp $HOME/telegram-android/TMessagesProj/build/outputs/apk/arm64_SDK23/release/app.apk $HOME/telegram-android/telegram_built.apk

+
+ +
+ +

Step 5. The Telegram APK installed on your device

+

You will need adb for this step.

+
+ +

ADB

+
+ +
+

If you downloaded your APK directly from Telegram's website, use the package name org.telegram.messenger.web in this step. To verify the Google Play APK, use org.telegram.messenger.

+
+

Connect your device to the computer, open Terminal, run the commands:
adb shell pm path org.telegram.messenger

+
+ +
+ +

The output will look something like this:
package:/data/app/org.telegram.messenger-_zOSURFEx2GpHM8UDF_PVg==/base.apk
By using this information, pull the APK from your device to $HOME/telegram-android using command:
adb pull /data/app/org.telegram.messenger-_zOSURFEx2GpHM8UDF_PVg==/base.apk $HOME/telegram-android/telegram_store.apk

+

Step 6. Compare the APKs

+

Open Terminal, run the commands:
cd $HOME/telegram-android
python apkdiff.py telegram_store.apk telegram_built.apk
If the APKs are the same, you will see
APKs are the same!

+
+ +
+Tada! + +Otherwise, something went wrong. +
+ +
+ +

If your APKs don't match, please make sure that you chose the correct code version and the right SDK.

+

Check out the Troubleshooting section first in case you run into trouble.

+
+

Reproducible Builds for iOS

+

The verification process for iOS builds is, unfortunately, a lot more complex than for Android. The two main issues with Apple's current policies and infrastructure are as follows:

+
    +
  1. Apple insists on using FairPlay encryption to “protect” even free apps from “app pirates” which makes obtaining the executable code of apps impossible without a jailbroken device. To solve this issue, Apple would simply need to allow submitting unencryptable binaries to the App Store. This would not affect security since the code would still be signed – and would enable anyone to check the integrity of apps supporting reproducible builds without endangering the integrity and security of their devices.

    +
  2. +
  3. Building your own reproducible binaries is difficult because macOS doesn't support containers like Docker. If Apple followed in the footsteps of Linux (and even Microsoft!) and added container support, it would eliminate the need for steps 1-3 in the guide below.

    +
  4. +
+
+

As things stand now, you'll need a jailbroken device, at least 1,5 hours and approximately 90GB of free space to properly set up a virtual machine for the verification process.

+
+

To provide a stable and easily reproducible environment, Telegram iOS builds are compiled on a virtual machine. Parallels is used to verify the builds.

+

Step 1. Install the Parallels virtual machine

+

Parallels can be obtained here, it features a fully-functional trial version.

+

Step 2. Install the latest version of macOS Big Sur

+

To download an image that can be installed on the virtual machine, open the App Store, search for “Catalina” and click “View”.

+
+ +

Search for macOS Catalina on App Store > View

+
+ +
+ +

macOS Catalina > Get +

+
+ +

This will open a system pop-up offering to download the OS:

+
+ +
+Choose “Download” and wait for the download to finish. + +> If you were not using the latest version of the OS, your system may start updating instead. Please finish updating to download macOS Catalina. + +When done, open Parallels and choose macOS Catalina: + +
+ +

Select 'Install Windows or another OS' > Continue

+
+ +
+ +

Select a file... > Applications (All files) > Install macOS Сatalina

+
+ +

Before starting the installation, configure the virtual machine:

+
+ +

Checkbox 'Customize settings before installation'

+
+ +

Change the name of the virtual machine to macos11_Xcode12_5_1

+
+ +

Name VM as macos10_15_Xcode12_2

+
+ +

Hardware > Processors: 2-4
Memory > 4GB may suffice but 8GB is recommended

+
+ +

At least 2 CPUs + 4 (8 recommended) GB Memory.

+
+ +

You will get something like this:

+
+ +

Click Continue

+
+ +

Parallels may request access to your microphone and camera, this is not required – just press Close.

+
+ +

Install macOS > Continue

+
+ +

Your Apple ID is also not required, you can choose Set Up Later.

+
+ +

Skip Apple ID with 'Set Up Later'

+
+ +

Use “telegram” for both the account name and password.

+
+

Do not ever use the password “telegram” for anything else, it's cursed.

+
+
+ +

Create a computer account with 'telegram' set both as account name and password

+
+ +

Now install Parallels tools from the menu bar:

+
+ + +

Install Parallels Tools using menu bar > Parallels icon > Actions > Install (Reinstall) Parallels Tools...

+
+ +

After the system restarts, log in.
Open Terminal and run:
sudo visudo
Enter the password “telegram”

+
+ +
+ +

Find this line at the end of the file:
%admin ALL=(ALL) ALL
Press “i” on your keyboard, add “NOPASSWD:”
%admin ALL=(ALL) NOPASSWD: ALL
Press Escape.
Type in “:wq”
Press Enter

+
+ +

Press i to edit the highlighted string.

+ +

Enter :wq > press Enter.

+
+ +

In the terminal, run:
sudo systemsetup -setcomputersleep Never

+
+ +

sudo systemsetup -setcomputersleep Never > press Enter.

+
+ +

Step 3. Install SSH keys on the virtual machine

+

In the virtual machine, open System Settings > Sharing and enable Remote Login.

+
+ +
+ +

In the virtual machine, open Terminal and run:
mkdir -p .ssh; nano .ssh/authorized_keys

+
+ +
+ +

In your main OS, open Terminal and run:
if [ ! -e ~/.ssh/id_rsa.pub ]; then ssh-keygen -t rsa -b 4096; fi && cat ~/.ssh/id_rsa.pub | pbcopy

+
+ +
+ +

If you see the line “Enter file in which to save the key (/Users/…/.ssh/id_rsa):”, press Enter
In the virtual machine, press CMD+V
Then Ctrl+O, Ctrl+X

+
+ +
+ +

Step 4. Install Xcode version 12.5.1

+

In the virtual machine, open Safari and go to https://developer.apple.com
Sign in to your Account:

+
+ +

developer.apple.com > Account > sign in with your Apple ID

+
+ +

Go to Downloads > More
Enter Xcode in the search field and find the version 12.5.1

+
+ +

Downloads > More > Xcode 12.5.1

+
+ +

Once the installation is complete, open the file Xcode 12.5.1.xip. The system will unarchive the app into the same folder. Move it to the Applications folder using Finder.

+
+ +

Unarchive Xcode > drag the app to Applications folder

+
+ +
+ +
+ +

On the virtual machine, run this command from the terminal:
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

+
+ +
+ +

Shut down the virtual machine.

+
+ +

Shut down the virtual machine

+
+ +

Step 4.1

+

Download the certificates at https://github.com/TelegramMessenger/Telegram-iOS/tree/master/build-system/fake-codesigning/certs/distribution and install them into the virtual machine.

+

Launch Keychain Access and double-click the installed certificate. Under “Trust”, change “When using this certificate” to “Always Trust”.

+

Step 5. Obtaining the source code

+

git clone --recursive https://github.com/TelegramMessenger/telegram-ios.git $HOME/telegram-ios
cd $HOME/telegram-ios
git checkout release-${VERSION_NUMBER}

+

E.g., git checkout release-7.3. Please note that you need to check out the whole git history as the build version depends on the number of commits in the repository.

+
+ +
+ +

Step 6. Downloading Bazel 3.7.0 to $HOME/bazel/bazel

+

mkdir -p $HOME/bazel && cd $HOME/bazel
curl -O -L https://github.com/bazelbuild/bazel/releases/download/3.7.0/bazel-3.7.0-darwin-x86_64
mv bazel-3.7.0-darwin-x86_64 bazel

+

Check that you have downloaded the correct version:
chmod +x bazel
./bazel --version

+

Step 7. Building the app

+

Open Terminal, run the commands:
cd $HOME/telegram-ios +BAZEL="$HOME/bazel/bazel" sh buildbox/build-telegram.sh verify

+
+ +
+ +

If the environment has been set up correctly, this will start the building process. Note that this step can easily take 30-40 minutes. The average build time on a MacBook Pro (i9 6 core) is 35 minutes.

+
+ + +
+ +

Once the process is complete the resulting IPA file can be found in build/artifacts/Telegram.ipa
All the following steps will be made via Terminal on your main system.

+

Step 8. Downloading a decrypted version of the app from the App Store

+

This step requires a jailbroken device equipped with tools for decrypting apps. We‘d love to make this process more simple but that’s what you get for using Apple tech.

+

Step 9. Comparing the AppStore build and the version built in the virtual machine

+

Install the necessary tools:
if ! type brew > /dev/null; + then /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"; fi && brew install python3

+
+ +
+ +

Run
python3 tools/ipadiff.py build/artifacts/Telegram.ipa PATH-TO-THE-IPA-FILE-FROM-STEP-9

+
    +
  1. cd telegram-ios > Enter
  2. +
  3. python3 tools/ipadiff.py build/artifacts/Telegram.ipa /path/ > Enter
  4. +
+
+ +
+ +

In case of a successful comparison, you will get a text along these lines:

+
IPAs are equal, except for the files that can't currently be checked:
+    Excluded files that couldn't be checked due to being encrypted:
+        PlugIns/SiriIntents.appex/SiriIntents
+        PlugIns/Widget.appex/Widget
+        PlugIns/NotificationContent.appex/NotificationContent
+        PlugIns/NotificationService.appex/NotificationService
+        PlugIns/Share.appex/Share
+    IPAs contain Watch directory with a Watch app which can't be checked currently.
+    IPAs contain .car (Asset Catalog) files that are compiled by the App Store and can't currently be checked:
+
+        Frameworks/TelegramUI.framework/Assets.car
+        Assets.car
+    IPAs contain .nib (compiled Interface Builder) files that are compiled by the App Store and can't currently be checked:
+        Base.lproj/LaunchScreen.nib
+
+ +
+ +

In case of any mismatches, you'll get a detailed report.

+
+ +
+ +

iOS: Notes

+
    +
  1. You will get a warning if the archive created in Step 7 contains encrypted files. If all these files are in the PlugIns subfolder, they represent various system extensions (e.g. external sharing, Siri, 3D touch). Decrypting such files using existing ways of receiving app archives via Jailbreak is non-trivial (but we're working on resolving this issue). If you do manage to decrypt them, e.g. on iOS 8, they will be matched.

    +
  2. +
  3. You will be notified if the archive includes an Apple Watch app. The watch app will soon no longer be included in the archive.

    +
  4. +
  5. Files with the .car extension are app resource archives (images, sounds) which were compiled and processed specifically for the target device. The App Store processes them in non-trivial ways, we're planning on getting rid of them in future versions.

    +
  6. +
  7. The LaunchScreen.nib file is an empty file containing a description of the interface which is displayed by the system before the app is launched. It is processed by the App Store in a non-trivial way but doesn't contain any code and therefore may be ignored.

    +
  8. +
+
+

Troubleshooting

+

If you encounter any issues with obtaining the code, building and comparing the apps, please contact us at @botsupport and include the hashtag #reproducibleBuilds with your message describing the problem.

+

Troubleshooting: Android

+
    +
  1. Make sure that you checkout the correct version of the code.

    +
  2. +
  3. Make sure that you build the app using the right SDK.

    +
  4. +
  5. If the gradle version used in the Dockerfile is not available anymore and building of the Docker image fails, wait for a Dockerfile update or update manually to lastest available version.

    +
  6. +
+

+

We will update this section with information on overcoming other common issues.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/schema.html b/data/core.telegram.org/schema.html new file mode 100644 index 0000000000..83765d3d76 --- /dev/null +++ b/data/core.telegram.org/schema.html @@ -0,0 +1,1800 @@ + + + + + Schema + + + + + + + + + + + + + +
+ +
+
+
+ +

Schema

+ +

Below you will find the current TL-schema. More details on TL »

+

See also the detailed schema in JSON »

+

See also TL-Schema for end-to-end encrypted messages »

+
+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+true#3fedd339 = True;
+
+vector#1cb5c415 {t:Type} # [ t ] = Vector t;
+
+error#c4b9f9bb code:int text:string = Error;
+
+null#56730bcc = Null;
+
+inputPeerEmpty#7f3b18ea = InputPeer;
+inputPeerSelf#7da07ec9 = InputPeer;
+inputPeerChat#35a95cb9 chat_id:long = InputPeer;
+inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
+inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
+inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;
+inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;
+
+inputUserEmpty#b98886cf = InputUser;
+inputUserSelf#f7c1b13f = InputUser;
+inputUser#f21158c6 user_id:long access_hash:long = InputUser;
+inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;
+
+inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;
+
+inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
+inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;
+
+inputMediaEmpty#9664f57f = InputMedia;
+inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;
+inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;
+inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;
+inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;
+inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;
+inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaGame#d33f43f3 id:InputGame = InputMedia;
+inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
+inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+inputMediaDice#e66fbf7b emoticon:string = InputMedia;
+
+inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;
+inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
+inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;
+
+inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
+
+inputPhotoEmpty#1cd7bf0d = InputPhoto;
+inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;
+
+inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
+inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
+inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
+inputTakeoutFileLocation#29be5899 = InputFileLocation;
+inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
+inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
+inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
+inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;
+
+peerUser#59511722 user_id:long = Peer;
+peerChat#36c6019a chat_id:long = Peer;
+peerChannel#a2a5371e channel_id:long = Peer;
+
+storage.fileUnknown#aa963b05 = storage.FileType;
+storage.filePartial#40bc6f52 = storage.FileType;
+storage.fileJpeg#7efe0e = storage.FileType;
+storage.fileGif#cae1aadf = storage.FileType;
+storage.filePng#a4f63c0 = storage.FileType;
+storage.filePdf#ae1e508d = storage.FileType;
+storage.fileMp3#528a0677 = storage.FileType;
+storage.fileMov#4b09ebbc = storage.FileType;
+storage.fileMp4#b3cea0e4 = storage.FileType;
+storage.fileWebp#1081464c = storage.FileType;
+
+userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+
+userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;
+userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
+
+userStatusEmpty#9d05049 = UserStatus;
+userStatusOnline#edb93949 expires:int = UserStatus;
+userStatusOffline#8c703f was_online:int = UserStatus;
+userStatusRecently#e26f42f1 = UserStatus;
+userStatusLastWeek#7bf09fc = UserStatus;
+userStatusLastMonth#77ebc742 = UserStatus;
+
+chatEmpty#29562865 id:long = Chat;
+chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;
+chatForbidden#6592a1a7 id:long title:string = Chat;
+channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;
+channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;
+
+chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
+channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
+
+chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;
+chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;
+chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;
+
+chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;
+chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;
+
+chatPhotoEmpty#37c1011c = ChatPhoto;
+chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
+
+messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
+
+messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+
+messageActionEmpty#b6aef7b0 = MessageAction;
+messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;
+messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;
+messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;
+messageActionChatDeletePhoto#95e3fbef = MessageAction;
+messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;
+messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;
+messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;
+messageActionChannelCreate#95d2ac92 title:string = MessageAction;
+messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;
+messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;
+messageActionPinMessage#94bd38ed = MessageAction;
+messageActionHistoryClear#9fbab604 = MessageAction;
+messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
+messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
+messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
+messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;
+messageActionScreenshotTaken#4792929b = MessageAction;
+messageActionCustomAction#fae69f56 message:string = MessageAction;
+messageActionBotAllowed#abe9affe domain:string = MessageAction;
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;
+messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;
+messageActionContactSignUp#f3f25f76 = MessageAction;
+messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
+messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
+messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;
+messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;
+messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;
+messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;
+
+dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
+dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;
+
+photoEmpty#2331b22d id:long = Photo;
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
+
+photoSizeEmpty#e17e23c type:string = PhotoSize;
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
+photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
+photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
+photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
+
+geoPointEmpty#1117dd5f = GeoPoint;
+geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
+
+auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+
+auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+
+auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
+
+inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;
+inputNotifyUsers#193b4417 = InputNotifyPeer;
+inputNotifyChats#4a95e84e = InputNotifyPeer;
+inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;
+
+inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;
+
+peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
+
+peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
+
+wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
+
+inputReportReasonSpam#58dbcab8 = ReportReason;
+inputReportReasonViolence#1e22c78d = ReportReason;
+inputReportReasonPornography#2e59d922 = ReportReason;
+inputReportReasonChildAbuse#adf44ee3 = ReportReason;
+inputReportReasonOther#c1e4a2b1 = ReportReason;
+inputReportReasonCopyright#9b89f93a = ReportReason;
+inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;
+inputReportReasonFake#f5ddd6e7 = ReportReason;
+
+userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
+
+contact#145ade0b user_id:long mutual:Bool = Contact;
+
+importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;
+
+contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;
+
+contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
+contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
+
+contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+
+contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+
+messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
+
+messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+
+messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+
+messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
+
+messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+
+inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
+inputMessagesFilterPhotos#9609a51c = MessagesFilter;
+inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
+inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
+inputMessagesFilterDocument#9eddf188 = MessagesFilter;
+inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
+inputMessagesFilterGif#ffc86587 = MessagesFilter;
+inputMessagesFilterVoice#50f5c392 = MessagesFilter;
+inputMessagesFilterMusic#3751b49e = MessagesFilter;
+inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
+inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
+inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
+inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
+inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
+inputMessagesFilterGeo#e7026d0d = MessagesFilter;
+inputMessagesFilterContacts#e062db83 = MessagesFilter;
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+updateMessageID#4e90bfd6 id:int random_id:long = Update;
+updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;
+updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
+updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;
+updateChatParticipants#7761198 participants:ChatParticipants = Update;
+updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;
+updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;
+updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;
+updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;
+updateEncryptedChatTyping#1710f156 chat_id:int = Update;
+updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;
+updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;
+updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;
+updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;
+updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;
+updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
+updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
+updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;
+updateUserPhone#5492a13 user_id:long phone:string = Update;
+updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;
+updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;
+updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;
+updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;
+updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;
+updateChannel#635b4c09 channel_id:long = Update;
+updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
+updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;
+updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;
+updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;
+updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;
+updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;
+updateStickerSets#43ae3dec = Update;
+updateSavedGifs#9375341e = Update;
+updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
+updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
+updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;
+updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;
+updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;
+updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;
+updateReadFeaturedStickers#571d2742 = Update;
+updateRecentStickers#9a422c20 = Update;
+updateConfig#a229dd06 = Update;
+updatePtsChanged#3354678f = Update;
+updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;
+updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;
+updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;
+updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;
+updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;
+updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
+updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
+updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;
+updateLangPackTooLong#46560264 lang_code:string = Update;
+updateLangPack#56022f4d difference:LangPackDifference = Update;
+updateFavedStickers#e511996d = Update;
+updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;
+updateContactsReset#7084a7be = Update;
+updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;
+updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;
+updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
+updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;
+updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;
+updateNewScheduledMessage#39a51dfb message:Message = Update;
+updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
+updateTheme#8216fba3 theme:Theme = Update;
+updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
+updateLoginToken#564fe691 = Update;
+updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
+updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
+updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
+updateDialogFilters#3504914f = Update;
+updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;
+updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;
+updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;
+updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;
+updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;
+updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;
+updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
+updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+updateChat#f89a6a4e chat_id:long = Update;
+updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
+updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;
+updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
+updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;
+updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;
+updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;
+
+updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
+
+updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
+updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
+updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
+updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
+
+updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+
+photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+
+photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+
+upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+
+config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+
+nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+
+help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
+help.noAppUpdate#c45a6536 = help.AppUpdate;
+
+help.inviteText#18cb9f78 message:string = help.InviteText;
+
+encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+
+inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;
+
+encryptedFileEmpty#c21f497e = EncryptedFile;
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
+inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
+inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
+inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;
+
+encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;
+
+messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
+messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
+
+messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+
+inputDocumentEmpty#72f0eaae = InputDocument;
+inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;
+
+documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+
+help.support#17c6b5f6 phone_number:string user:User = help.Support;
+
+notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;
+notifyUsers#b4c83b4c = NotifyPeer;
+notifyChats#c007cec3 = NotifyPeer;
+notifyBroadcasts#d612e8ef = NotifyPeer;
+
+sendMessageTypingAction#16bf744e = SendMessageAction;
+sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
+sendMessageRecordVideoAction#a187d66f = SendMessageAction;
+sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
+sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
+sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
+sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
+sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
+sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
+sendMessageChooseContactAction#628cbc6f = SendMessageAction;
+sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
+sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
+sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
+speakingInGroupCallAction#d92c2285 = SendMessageAction;
+sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
+sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
+
+contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
+
+inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
+inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
+inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
+inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
+inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
+inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
+inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
+inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;
+
+privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;
+privacyKeyChatInvite#500e6dfa = PrivacyKey;
+privacyKeyPhoneCall#3d662b7b = PrivacyKey;
+privacyKeyPhoneP2P#39491cc8 = PrivacyKey;
+privacyKeyForwards#69ec56a3 = PrivacyKey;
+privacyKeyProfilePhoto#96151fed = PrivacyKey;
+privacyKeyPhoneNumber#d19ae46d = PrivacyKey;
+privacyKeyAddedByPhone#42ffd42b = PrivacyKey;
+
+inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;
+inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
+inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;
+inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
+inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;
+inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;
+
+privacyValueAllowContacts#fffe1bac = PrivacyRule;
+privacyValueAllowAll#65427b82 = PrivacyRule;
+privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;
+privacyValueDisallowContacts#f888fa1a = PrivacyRule;
+privacyValueDisallowAll#8b73e763 = PrivacyRule;
+privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;
+privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
+privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;
+
+account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+
+accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
+documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
+documentAttributeHasStickers#9801d2f7 = DocumentAttribute;
+
+messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
+
+stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
+
+messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+
+messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+
+webPageEmpty#eb1477e8 id:long = WebPage;
+webPagePending#c586da1c id:long date:int = WebPage;
+webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
+
+authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+
+account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
+
+account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+
+account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
+account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;
+
+auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+
+receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;
+
+chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
+
+chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
+chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
+
+inputStickerSetEmpty#ffb62b95 = InputStickerSet;
+inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
+inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
+inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
+inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
+
+stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+botCommand#c27ac8c7 command:string description:string = BotCommand;
+
+botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;
+
+keyboardButton#a2fa4880 text:string = KeyboardButton;
+keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
+keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
+keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
+keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
+keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
+keyboardButtonGame#50f41ccf text:string = KeyboardButton;
+keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
+inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
+keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
+
+keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
+
+replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
+replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
+replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
+
+messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
+messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
+messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
+messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
+messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
+messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
+messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
+messageEntityCode#28a20571 offset:int length:int = MessageEntity;
+messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
+messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
+messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
+inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
+messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
+messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
+messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
+messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
+messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
+messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;
+
+inputChannelEmpty#ee8c1e86 = InputChannel;
+inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;
+inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;
+
+contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
+
+messageRange#ae30253 min_id:int max_id:int = MessageRange;
+
+updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
+updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+
+channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;
+channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;
+
+channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
+channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;
+channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
+channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
+channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
+channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;
+
+channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;
+channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;
+channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;
+channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;
+channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;
+channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;
+channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;
+channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;
+
+channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
+
+channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+
+help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;
+
+messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
+messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
+
+inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+
+inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;
+
+botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+
+botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
+botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;
+
+messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
+
+exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+
+messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
+
+auth.codeTypeSms#72a3158c = auth.CodeType;
+auth.codeTypeCall#741cd3e3 = auth.CodeType;
+auth.codeTypeFlashCall#226ccefb = auth.CodeType;
+
+auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;
+auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;
+auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;
+auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;
+
+messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+
+messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
+
+inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
+inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;
+
+inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;
+
+messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+
+topPeer#edcdc05b peer:Peer rating:double = TopPeer;
+
+topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
+topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
+topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
+topPeerCategoryGroups#bd17a14a = TopPeerCategory;
+topPeerCategoryChannels#161d9628 = TopPeerCategory;
+topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
+topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
+topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;
+
+topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;
+
+contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+
+draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;
+draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;
+
+messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+
+messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
+messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
+
+messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
+
+messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
+messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
+
+stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;
+stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;
+
+maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;
+
+inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;
+inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;
+
+game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;
+
+inputGameID#32c3e77 id:long access_hash:long = InputGame;
+inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;
+
+highScore#73a379eb pos:int user_id:long score:int = HighScore;
+
+messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+
+textEmpty#dc3d824f = RichText;
+textPlain#744694e0 text:string = RichText;
+textBold#6724abc4 text:RichText = RichText;
+textItalic#d912a59c text:RichText = RichText;
+textUnderline#c12622c4 text:RichText = RichText;
+textStrike#9bf8bb95 text:RichText = RichText;
+textFixed#6c3f19b9 text:RichText = RichText;
+textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;
+textEmail#de5a0dd6 text:RichText email:string = RichText;
+textConcat#7e6260d7 texts:Vector<RichText> = RichText;
+textSubscript#ed6a8504 text:RichText = RichText;
+textSuperscript#c7fb5e01 text:RichText = RichText;
+textMarked#34b8621 text:RichText = RichText;
+textPhone#1ccb966a text:RichText phone:string = RichText;
+textImage#81ccf4f document_id:long w:int h:int = RichText;
+textAnchor#35553762 text:RichText name:string = RichText;
+
+pageBlockUnsupported#13567e8a = PageBlock;
+pageBlockTitle#70abc3fd text:RichText = PageBlock;
+pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;
+pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;
+pageBlockHeader#bfd064ec text:RichText = PageBlock;
+pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;
+pageBlockParagraph#467a0766 text:RichText = PageBlock;
+pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;
+pageBlockFooter#48870999 text:RichText = PageBlock;
+pageBlockDivider#db20b188 = PageBlock;
+pageBlockAnchor#ce0d37b0 name:string = PageBlock;
+pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;
+pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;
+pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;
+pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;
+pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;
+pageBlockCover#39f23300 cover:PageBlock = PageBlock;
+pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;
+pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockChannel#ef1751b5 channel:Chat = PageBlock;
+pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;
+pageBlockKicker#1e148390 text:RichText = PageBlock;
+pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;
+pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;
+pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;
+pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;
+pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;
+
+phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;
+phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;
+phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;
+phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;
+
+dataJSON#7d748d04 data:string = DataJSON;
+
+labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
+
+invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
+
+paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;
+
+postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;
+
+paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
+
+paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
+
+webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+
+inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;
+
+inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
+inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
+
+upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+
+payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
+
+payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
+payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
+
+payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+
+payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
+
+inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
+
+account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+
+shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;
+
+inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;
+
+inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;
+
+phoneCallEmpty#5366c915 id:long = PhoneCall;
+phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
+phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;
+phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;
+
+phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;
+phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;
+
+phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;
+
+phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+
+upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+
+cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
+
+cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
+
+langPackString#cad181f6 key:string value:string = LangPackString;
+langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;
+langPackStringDeleted#2979eeb2 key:string = LangPackString;
+
+langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+
+langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
+
+channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
+channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
+channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
+channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;
+channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantVolume#3e7f6847 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;
+
+channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;
+
+channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+
+channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;
+
+popularContact#5ce14175 client_id:long importers:int = PopularContact;
+
+messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+
+recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;
+recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;
+recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;
+recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;
+recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;
+
+help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
+
+inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;
+
+webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;
+
+account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
+
+inputMessageID#a676a322 id:int = InputMessage;
+inputMessageReplyTo#bad88395 id:int = InputMessage;
+inputMessagePinned#86872538 = InputMessage;
+inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;
+
+inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
+inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
+
+dialogPeer#e56dbf05 peer:Peer = DialogPeer;
+dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
+
+messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
+messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
+
+fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
+
+inputClientProxy#75588b3f address:string port:int = InputClientProxy;
+
+help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+
+inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+secureFileEmpty#64199744 = SecureFile;
+secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;
+
+secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
+securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;
+
+secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
+
+secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;
+
+secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+
+secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
+
+help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
+help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
+
+savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;
+
+account.takeout#4dba4501 id:long = account.Takeout;
+
+passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
+passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;
+
+securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
+
+inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
+inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;
+
+secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;
+secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;
+
+help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
+help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
+
+inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;
+
+jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
+
+jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+
+pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;
+
+pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;
+
+pageCaption#6f747657 text:RichText credit:RichText = PageCaption;
+
+pageListItemText#b92fb6cd text:RichText = PageListItem;
+pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;
+
+pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
+pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;
+
+pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;
+
+page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;
+
+help.supportName#8c05f1c9 name:string = help.SupportName;
+
+help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+
+pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+chatOnlines#f041e250 onlines:int = ChatOnlines;
+
+statsURL#47a971e0 url:string = StatsURL;
+
+chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;
+
+chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;
+
+inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
+inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
+inputWallPaperNoFile#967a462e id:long = InputWallPaper;
+
+account.wallPapersNotModified#1c199183 = account.WallPapers;
+account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+
+codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;
+
+wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;
+
+autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;
+
+account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
+
+emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;
+emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;
+
+emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+
+emojiURL#a575739d url:string = EmojiURL;
+
+emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;
+
+folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;
+
+inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;
+
+folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;
+
+messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;
+
+urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
+urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
+urlAuthResultDefault#a9d6db1f = UrlAuthResult;
+
+channelLocationEmpty#bfb5ad8b = ChannelLocation;
+channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;
+
+peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;
+peerSelfLocated#f8ec284b expires:int = PeerLocated;
+
+restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;
+
+inputTheme#3c5693e9 id:long access_hash:long = InputTheme;
+inputThemeSlug#f5890df1 slug:string = InputTheme;
+
+theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+
+account.themesNotModified#f41eb622 = account.Themes;
+account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
+
+auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+
+account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
+
+messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
+
+baseThemeClassic#c3a12462 = BaseTheme;
+baseThemeDay#fbd81688 = BaseTheme;
+baseThemeNight#b7b31ea8 = BaseTheme;
+baseThemeTinted#6d5f77ee = BaseTheme;
+baseThemeArctic#5b11125a = BaseTheme;
+
+inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;
+
+themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;
+
+webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;
+
+messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
+
+messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
+
+bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;
+
+payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
+
+dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;
+
+dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;
+
+statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;
+
+statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;
+
+statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;
+
+statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+
+messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;
+
+stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+
+help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
+help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
+
+videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
+
+statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;
+
+statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;
+
+statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;
+
+stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
+
+globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
+
+help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
+
+help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
+
+help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+
+messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;
+
+messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
+
+messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
+
+messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
+
+messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
+
+peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;
+
+stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
+
+groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
+groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true rtmp_stream:flags.12?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;
+
+inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;
+
+groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;
+
+phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
+
+phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
+
+inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
+inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
+inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
+inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
+inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;
+
+messages.historyImport#1662af0b id:long = messages.HistoryImport;
+
+messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+
+messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
+
+chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;
+
+messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
+
+messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+
+messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+
+chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;
+
+messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
+
+messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+
+phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+
+phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
+
+groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;
+
+groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;
+
+stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
+
+botCommandScopeDefault#2f6cb2ab = BotCommandScope;
+botCommandScopeUsers#3c4f04d8 = BotCommandScope;
+botCommandScopeChats#6fe1a881 = BotCommandScope;
+botCommandScopeChatAdmins#b9aa606a = BotCommandScope;
+botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;
+botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;
+botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;
+
+account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+
+chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;
+
+account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
+account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
+
+sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;
+
+messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+
+---functions---
+
+invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
+invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;
+initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;
+invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;
+invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;
+invokeWithMessagesRange#365275f2 {X:Type} range:MessageRange query:!X = X;
+invokeWithTakeout#aca9fd2e {X:Type} takeout_id:long query:!X = X;
+
+auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;
+auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;
+auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
+auth.logOut#5717da40 = Bool;
+auth.resetAuthorizations#9fab0d1a = Bool;
+auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;
+auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
+auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
+auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;
+auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
+auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
+auth.checkRecoveryPassword#d36bf79 code:string = Bool;
+
+account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;
+account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;
+account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;
+account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;
+account.resetNotifySettings#db7e1747 = Bool;
+account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;
+account.updateStatus#6628562c offline:Bool = Bool;
+account.getWallPapers#7967d36 hash:long = account.WallPapers;
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;
+account.checkUsername#2714d86c username:string = Bool;
+account.updateUsername#3e0bdd7c username:string = User;
+account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;
+account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;
+account.deleteAccount#418d4e0b reason:string = Bool;
+account.getAccountTTL#8fc711d = AccountDaysTTL;
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;
+account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;
+account.updateDeviceLocked#38df3532 period:int = Bool;
+account.getAuthorizations#e320c158 = account.Authorizations;
+account.resetAuthorization#df77f3bc hash:long = Bool;
+account.getPassword#548a30f5 = account.Password;
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
+account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
+account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;
+account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;
+account.resetWebAuthorization#2d01b9ef hash:long = Bool;
+account.resetWebAuthorizations#682d2594 = Bool;
+account.getAllSecureValues#b288bc7d = Vector<SecureValue>;
+account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;
+account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;
+account.verifyEmail#ecba39db email:string code:string = Bool;
+account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;
+account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;
+account.confirmPasswordEmail#8fdf1920 code:string = Bool;
+account.resendPasswordEmail#7a7f2a15 = Bool;
+account.cancelPasswordEmail#c1cbd5b6 = Bool;
+account.getContactSignUpNotification#9f07c728 = Bool;
+account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;
+account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;
+account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;
+account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;
+account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
+account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
+account.resetWallPapers#bb3b9804 = Bool;
+account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;
+account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;
+account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;
+account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
+account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
+account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
+account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;
+account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;
+account.getThemes#7206e458 format:string hash:long = account.Themes;
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
+account.getContentSettings#8b9b4dae = account.ContentSettings;
+account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;
+account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
+account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;
+account.resetPassword#9308ce1b = account.ResetPasswordResult;
+account.declinePasswordReset#4c9409f6 = Bool;
+account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;
+
+users.getUsers#d91a548 id:Vector<InputUser> = Vector<User>;
+users.getFullUser#ca30a5b1 id:InputUser = UserFull;
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
+
+contacts.getContactIDs#7adc669d hash:long = Vector<int>;
+contacts.getStatuses#c4a353ee = Vector<ContactStatus>;
+contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;
+contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;
+contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;
+contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;
+contacts.block#68cc1411 id:InputPeer = Bool;
+contacts.unblock#bea65d50 id:InputPeer = Bool;
+contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;
+contacts.search#11f812d8 q:string limit:int = contacts.Found;
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;
+contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;
+contacts.resetSaved#879537f1 = Bool;
+contacts.getSaved#82f1e39f = Vector<SavedContact>;
+contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;
+contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;
+contacts.acceptContact#f831a20f id:InputUser = Updates;
+contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
+
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
+messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;
+messages.getHistory#4423e6c5 peer:InputPeer offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;
+messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;
+messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;
+messages.receivedMessages#5a954c0 max_id:int = Vector<ReceivedNotifyMessage>;
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;
+messages.reportSpam#cf1592db peer:InputPeer = Bool;
+messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
+messages.getChats#49e9528f id:Vector<long> = messages.Chats;
+messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;
+messages.editChatTitle#73783ffd chat_id:long title:string = Updates;
+messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
+messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;
+messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;
+messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;
+messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;
+messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;
+messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;
+messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
+messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.receivedQueue#55a5bb66 max_qts:int = Vector<long>;
+messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;
+messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;
+messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;
+messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;
+messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;
+messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;
+messages.importChatInvite#6c50051c hash:string = Updates;
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;
+messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;
+messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;
+messages.migrateChat#a2875319 chat_id:long = Updates;
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
+messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;
+messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
+messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;
+messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;
+messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
+messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
+messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
+messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;
+messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
+messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
+messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;
+messages.getAllDrafts#6a3f8d65 = Updates;
+messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;
+messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;
+messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;
+messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;
+messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;
+messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;
+messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;
+messages.getAttachedStickers#cc5b67cc media:InputStickeredMedia = Vector<StickerSetCovered>;
+messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
+messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;
+messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;
+messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;
+messages.getWebPage#32ca8f91 url:string hash:int = WebPage;
+messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;
+messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
+messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
+messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
+messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;
+messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;
+messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;
+messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
+messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;
+messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;
+messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;
+messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;
+messages.getSplitRanges#1cff7e08 = Vector<MessageRange>;
+messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;
+messages.getDialogUnreadMarks#22e24e22 = Vector<DialogPeer>;
+messages.clearAllDrafts#7e58ee9c = Bool;
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
+messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;
+messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;
+messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;
+messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;
+messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;
+messages.getEmojiKeywordsLanguages#4e9963b2 lang_codes:Vector<string> = Vector<EmojiLanguage>;
+messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;
+messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;
+messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
+messages.acceptUrlAuth#b12c7125 flags:# write_allowed:flags.0?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
+messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
+messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
+messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;
+messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;
+messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;
+messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;
+messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
+messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
+messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;
+messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;
+messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
+messages.deleteChat#5bd0ee50 chat_id:long = Bool;
+messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;
+messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;
+messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
+messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
+messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
+messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;
+messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;
+messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;
+messages.getMessageReadParticipants#2c6f97b7 peer:InputPeer msg_id:int = Vector<long>;
+
+updates.getState#edd4882a = updates.State;
+updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;
+updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;
+
+photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
+photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;
+photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;
+photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
+upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
+upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
+upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;
+
+help.getConfig#c4f9186b = Config;
+help.getNearestDc#1fb33026 = NearestDc;
+help.getAppUpdate#522d5a7d source:string = help.AppUpdate;
+help.getInviteText#4d392343 = help.InviteText;
+help.getSupport#9cdf08cd = help.Support;
+help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
+help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;
+help.getCdnConfig#52029342 = CdnConfig;
+help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;
+help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
+help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;
+help.getAppConfig#98914110 = JSONValue;
+help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;
+help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;
+help.getSupportName#d360e72c = help.SupportName;
+help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;
+help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;
+help.getPromoData#c0977421 = help.PromoData;
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;
+
+channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;
+channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;
+channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;
+channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;
+channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;
+channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;
+channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;
+channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;
+channels.editTitle#566decd0 channel:InputChannel title:string = Updates;
+channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
+channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
+channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
+channels.joinChannel#24b524c5 channel:InputChannel = Updates;
+channels.leaveChannel#f836aa95 channel:InputChannel = Updates;
+channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;
+channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;
+channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;
+channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;
+channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;
+channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;
+channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;
+channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;
+channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
+channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;
+channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;
+channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;
+channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;
+channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;
+
+bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;
+bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
+bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;
+
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;
+payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
+payments.getSavedInfo#227d824b = payments.SavedInfo;
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;
+
+stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
+stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
+stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
+stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;
+stickers.checkShortName#284b3639 short_name:string = Bool;
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;
+
+phone.getCallConfig#55451fa9 = DataJSON;
+phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
+phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;
+phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
+phone.createGroupCall#48cdc6d8 flags:# rtmp_stream:flags.2?true peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
+phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
+phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
+phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
+phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
+phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;
+phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;
+phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;
+phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;
+phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;
+phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;
+phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;
+phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;
+phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
+phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;
+
+langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;
+langpack.getStrings#efea3803 lang_pack:string lang_code:string keys:Vector<string> = Vector<LangPackString>;
+langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;
+langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;
+langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;
+
+folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
+folders.deleteFolder#1c295881 folder_id:int = Updates;
+
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;
+stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
+stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;
+
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/schema/end-to-end-json.html b/data/core.telegram.org/schema/end-to-end-json.html new file mode 100644 index 0000000000..6c3b4f2cbe --- /dev/null +++ b/data/core.telegram.org/schema/end-to-end-json.html @@ -0,0 +1 @@ +{"constructors":[{"id":"528568095","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":8},{"id":"541931640","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":17},{"id":"917541342","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"}],"type":"DecryptedMessage","layer":45},{"id":"-1848883596","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"},{"name":"grouped_id","type":"flags.17?long"}],"type":"DecryptedMessage","layer":73},{"id":"-1438109059","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":8},{"id":"1930838368","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":17},{"id":"144661578","predicate":"decryptedMessageMediaEmpty","params":[],"type":"DecryptedMessageMedia","layer":8},{"id":"846826124","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-235238024","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1290694387","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1380598109","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"-1760785394","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"893913689","predicate":"decryptedMessageMediaGeoPoint","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1485441687","predicate":"decryptedMessageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"user_id","type":"int"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-1586283796","predicate":"decryptedMessageActionSetMessageTTL","params":[{"name":"ttl_seconds","type":"int"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1332395189","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"2063502050","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"attributes","type":"Vector"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1619031439","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1474341323","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"206520510","predicate":"decryptedMessageActionReadMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1700872964","predicate":"decryptedMessageActionDeleteMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1967000459","predicate":"decryptedMessageActionScreenshotMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1729750108","predicate":"decryptedMessageActionFlushHistory","params":[],"type":"DecryptedMessageAction","layer":8},{"id":"467867529","predicate":"decryptedMessageLayer","params":[{"name":"random_bytes","type":"bytes"},{"name":"layer","type":"int"},{"name":"in_seq_no","type":"int"},{"name":"out_seq_no","type":"int"},{"name":"message","type":"DecryptedMessage"}],"type":"DecryptedMessageLayer","layer":17},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1845219337","predicate":"sendMessageUploadVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-424899985","predicate":"sendMessageUploadAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1727382502","predicate":"sendMessageUploadPhotoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1884362354","predicate":"sendMessageUploadDocumentAction","params":[],"type":"SendMessageAction","layer":17},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1360072880","predicate":"decryptedMessageActionResend","params":[{"name":"start_seq_no","type":"int"},{"name":"end_seq_no","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-217806717","predicate":"decryptedMessageActionNotifyLayer","params":[{"name":"layer","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-860719551","predicate":"decryptedMessageActionTyping","params":[{"name":"action","type":"SendMessageAction"}],"type":"DecryptedMessageAction","layer":17},{"id":"-204906213","predicate":"decryptedMessageActionRequestKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"DecryptedMessageAction","layer":20},{"id":"1877046107","predicate":"decryptedMessageActionAcceptKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-586814357","predicate":"decryptedMessageActionAbortKey","params":[{"name":"exchange_id","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-332526693","predicate":"decryptedMessageActionCommitKey","params":[{"name":"exchange_id","type":"long"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-1473258141","predicate":"decryptedMessageActionNoop","params":[],"type":"DecryptedMessageAction","layer":20},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute","layer":23},{"id":"-83208409","predicate":"documentAttributeSticker","params":[],"type":"DocumentAttribute","layer":23},{"id":"978674434","predicate":"documentAttributeSticker","params":[{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"}],"type":"DocumentAttribute","layer":45},{"id":"1494273227","predicate":"documentAttributeVideo","params":[{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":66},{"id":"85215461","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"-556656416","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"},{"name":"title","type":"string"},{"name":"performer","type":"string"}],"type":"DocumentAttribute","layer":45},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute","layer":46},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute","layer":23},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize","layer":23},{"id":"2009052699","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize","layer":23},{"id":"-374917894","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize","layer":23},{"id":"2086234950","predicate":"fileLocationUnavailable","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"1406570614","predicate":"fileLocation","params":[{"name":"dc_id","type":"int"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"-90853155","predicate":"decryptedMessageMediaExternalDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumb","type":"PhotoSize"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"DecryptedMessageMedia","layer":23},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity","layer":45},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity","layer":45},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet","layer":45},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet","layer":45},{"id":"-1978796689","predicate":"decryptedMessageMediaVenue","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-452652584","predicate":"decryptedMessageMediaWebPage","params":[{"name":"url","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction","layer":66},{"id":"-1150187996","predicate":"sendMessageUploadRoundAction","params":[],"type":"SendMessageAction","layer":66}],"methods":[]} \ No newline at end of file diff --git a/data/core.telegram.org/schema/end-to-end.html b/data/core.telegram.org/schema/end-to-end.html new file mode 100644 index 0000000000..05edef7f0d --- /dev/null +++ b/data/core.telegram.org/schema/end-to-end.html @@ -0,0 +1,225 @@ + + + + + Current end-to-end TL-schema + + + + + + + + + + + + + +
+ +
+
+
+ +

Current end-to-end TL-schema

+ +
+

Below you will find the current end-to-end TL-schema. More details on TL »

+
+

See also:
+End-to-end encryption in MTProto, Secret Chats
+Detailed schema in JSON

+
+ +
+
===8===
+decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;
+decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;
+decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
+decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;
+decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;
+
+===17===
+decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
+decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;
+sendMessageTypingAction#16bf744e = SendMessageAction;
+sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
+sendMessageRecordVideoAction#a187d66f = SendMessageAction;
+sendMessageUploadVideoAction#92042ff7 = SendMessageAction;
+sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
+sendMessageUploadAudioAction#e6ac8a6f = SendMessageAction;
+sendMessageUploadPhotoAction#990a3c1a = SendMessageAction;
+sendMessageUploadDocumentAction#8faee98e = SendMessageAction;
+sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
+sendMessageChooseContactAction#628cbc6f = SendMessageAction;
+decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;
+decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;
+decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;
+
+===20===
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
+decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;
+
+===23===
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#fb0a5727 = DocumentAttribute;
+documentAttributeVideo#5910cccb duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#51448e5 duration:int = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
+photoSizeEmpty#e17e23c type:string = PhotoSize;
+photoSize#77bfb61b type:string location:FileLocation w:int h:int size:int = PhotoSize;
+photoCachedSize#e9a734fa type:string location:FileLocation w:int h:int bytes:bytes = PhotoSize;
+fileLocationUnavailable#7c596b46 volume_id:long local_id:int secret:long = FileLocation;
+fileLocation#53d69076 dc_id:int volume_id:long local_id:int secret:long = FileLocation;
+decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;
+
+===45===
+decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
+decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
+decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
+decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
+documentAttributeSticker#3a556302 alt:string stickerset:InputStickerSet = DocumentAttribute;
+documentAttributeAudio#ded218e0 duration:int title:string performer:string = DocumentAttribute;
+messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
+messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
+messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
+messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
+messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
+messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
+messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
+messageEntityCode#28a20571 offset:int length:int = MessageEntity;
+messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
+messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
+inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
+inputStickerSetEmpty#ffb62b95 = InputStickerSet;
+decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;
+decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;
+
+===46===
+documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
+
+===66===
+documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true duration:int w:int h:int = DocumentAttribute;
+sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
+sendMessageUploadRoundAction#bb718624 = SendMessageAction;
+
+===73===
+decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;
+
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/schema/json.html b/data/core.telegram.org/schema/json.html new file mode 100644 index 0000000000..5cdec104ab --- /dev/null +++ b/data/core.telegram.org/schema/json.html @@ -0,0 +1 @@ +{"constructors":[{"id":"-1132882121","predicate":"boolFalse","params":[],"type":"Bool"},{"id":"-1720552011","predicate":"boolTrue","params":[],"type":"Bool"},{"id":"1072550713","predicate":"true","params":[],"type":"True"},{"id":"481674261","predicate":"vector","params":[],"type":"Vector t"},{"id":"-994444869","predicate":"error","params":[{"name":"code","type":"int"},{"name":"text","type":"string"}],"type":"Error"},{"id":"1450380236","predicate":"null","params":[],"type":"Null"},{"id":"2134579434","predicate":"inputPeerEmpty","params":[],"type":"InputPeer"},{"id":"2107670217","predicate":"inputPeerSelf","params":[],"type":"InputPeer"},{"id":"900291769","predicate":"inputPeerChat","params":[{"name":"chat_id","type":"long"}],"type":"InputPeer"},{"id":"-1182234929","predicate":"inputUserEmpty","params":[],"type":"InputUser"},{"id":"-138301121","predicate":"inputUserSelf","params":[],"type":"InputUser"},{"id":"-208488460","predicate":"inputPhoneContact","params":[{"name":"client_id","type":"long"},{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"InputContact"},{"id":"-181407105","predicate":"inputFile","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"},{"name":"md5_checksum","type":"string"}],"type":"InputFile"},{"id":"-1771768449","predicate":"inputMediaEmpty","params":[],"type":"InputMedia"},{"id":"505969924","predicate":"inputMediaUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"-1279654347","predicate":"inputMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputPhoto"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-104578748","predicate":"inputMediaGeoPoint","params":[{"name":"geo_point","type":"InputGeoPoint"}],"type":"InputMedia"},{"id":"-122978821","predicate":"inputMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"}],"type":"InputMedia"},{"id":"480546647","predicate":"inputChatPhotoEmpty","params":[],"type":"InputChatPhoto"},{"id":"-968723890","predicate":"inputChatUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"InputChatPhoto"},{"id":"-1991004873","predicate":"inputChatPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputChatPhoto"},{"id":"-457104426","predicate":"inputGeoPointEmpty","params":[],"type":"InputGeoPoint"},{"id":"1210199983","predicate":"inputGeoPoint","params":[{"name":"flags","type":"#"},{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"InputGeoPoint"},{"id":"483901197","predicate":"inputPhotoEmpty","params":[],"type":"InputPhoto"},{"id":"1001634122","predicate":"inputPhoto","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputPhoto"},{"id":"-539317279","predicate":"inputFileLocation","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputFileLocation"},{"id":"1498486562","predicate":"peerUser","params":[{"name":"user_id","type":"long"}],"type":"Peer"},{"id":"918946202","predicate":"peerChat","params":[{"name":"chat_id","type":"long"}],"type":"Peer"},{"id":"-1432995067","predicate":"storage.fileUnknown","params":[],"type":"storage.FileType"},{"id":"1086091090","predicate":"storage.filePartial","params":[],"type":"storage.FileType"},{"id":"8322574","predicate":"storage.fileJpeg","params":[],"type":"storage.FileType"},{"id":"-891180321","predicate":"storage.fileGif","params":[],"type":"storage.FileType"},{"id":"172975040","predicate":"storage.filePng","params":[],"type":"storage.FileType"},{"id":"-1373745011","predicate":"storage.filePdf","params":[],"type":"storage.FileType"},{"id":"1384777335","predicate":"storage.fileMp3","params":[],"type":"storage.FileType"},{"id":"1258941372","predicate":"storage.fileMov","params":[],"type":"storage.FileType"},{"id":"-1278304028","predicate":"storage.fileMp4","params":[],"type":"storage.FileType"},{"id":"276907596","predicate":"storage.fileWebp","params":[],"type":"storage.FileType"},{"id":"-742634630","predicate":"userEmpty","params":[{"name":"id","type":"long"}],"type":"User"},{"id":"1326562017","predicate":"userProfilePhotoEmpty","params":[],"type":"UserProfilePhoto"},{"id":"-2100168954","predicate":"userProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"UserProfilePhoto"},{"id":"164646985","predicate":"userStatusEmpty","params":[],"type":"UserStatus"},{"id":"-306628279","predicate":"userStatusOnline","params":[{"name":"expires","type":"int"}],"type":"UserStatus"},{"id":"9203775","predicate":"userStatusOffline","params":[{"name":"was_online","type":"int"}],"type":"UserStatus"},{"id":"693512293","predicate":"chatEmpty","params":[{"name":"id","type":"long"}],"type":"Chat"},{"id":"1103884886","predicate":"chat","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"kicked","type":"flags.1?true"},{"name":"left","type":"flags.2?true"},{"name":"deactivated","type":"flags.5?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"noforwards","type":"flags.25?true"},{"name":"id","type":"long"},{"name":"title","type":"string"},{"name":"photo","type":"ChatPhoto"},{"name":"participants_count","type":"int"},{"name":"date","type":"int"},{"name":"version","type":"int"},{"name":"migrated_to","type":"flags.6?InputChannel"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"}],"type":"Chat"},{"id":"1704108455","predicate":"chatForbidden","params":[{"name":"id","type":"long"},{"name":"title","type":"string"}],"type":"Chat"},{"id":"1304281241","predicate":"chatFull","params":[{"name":"flags","type":"#"},{"name":"can_set_username","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants","type":"ChatParticipants"},{"name":"chat_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.13?ExportedChatInvite"},{"name":"bot_info","type":"flags.3?Vector"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"call","type":"flags.12?InputGroupCall"},{"name":"ttl_period","type":"flags.14?int"},{"name":"groupcall_default_join_as","type":"flags.15?Peer"},{"name":"theme_emoticon","type":"flags.16?string"}],"type":"ChatFull"},{"id":"-1070776313","predicate":"chatParticipant","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-2023500831","predicate":"chatParticipantsForbidden","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"self_participant","type":"flags.0?ChatParticipant"}],"type":"ChatParticipants"},{"id":"1018991608","predicate":"chatParticipants","params":[{"name":"chat_id","type":"long"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"ChatParticipants"},{"id":"935395612","predicate":"chatPhotoEmpty","params":[],"type":"ChatPhoto"},{"id":"476978193","predicate":"chatPhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"ChatPhoto"},{"id":"-1868117372","predicate":"messageEmpty","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"peer_id","type":"flags.0?Peer"}],"type":"Message"},{"id":"-2049520670","predicate":"message","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"from_scheduled","type":"flags.18?true"},{"name":"legacy","type":"flags.19?true"},{"name":"edit_hide","type":"flags.21?true"},{"name":"pinned","type":"flags.24?true"},{"name":"noforwards","type":"flags.26?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"reply_markup","type":"flags.6?ReplyMarkup"},{"name":"entities","type":"flags.7?Vector"},{"name":"views","type":"flags.10?int"},{"name":"forwards","type":"flags.10?int"},{"name":"replies","type":"flags.23?MessageReplies"},{"name":"edit_date","type":"flags.15?int"},{"name":"post_author","type":"flags.16?string"},{"name":"grouped_id","type":"flags.17?long"},{"name":"restriction_reason","type":"flags.22?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"721967202","predicate":"messageService","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"legacy","type":"flags.19?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"action","type":"MessageAction"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"1038967584","predicate":"messageMediaEmpty","params":[],"type":"MessageMedia"},{"id":"1766936791","predicate":"messageMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"photo","type":"flags.0?Photo"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1457575028","predicate":"messageMediaGeo","params":[{"name":"geo","type":"GeoPoint"}],"type":"MessageMedia"},{"id":"1882335561","predicate":"messageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"user_id","type":"long"}],"type":"MessageMedia"},{"id":"-1618676578","predicate":"messageMediaUnsupported","params":[],"type":"MessageMedia"},{"id":"-1230047312","predicate":"messageActionEmpty","params":[],"type":"MessageAction"},{"id":"-1119368275","predicate":"messageActionChatCreate","params":[{"name":"title","type":"string"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1247687078","predicate":"messageActionChatEditTitle","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"2144015272","predicate":"messageActionChatEditPhoto","params":[{"name":"photo","type":"Photo"}],"type":"MessageAction"},{"id":"-1780220945","predicate":"messageActionChatDeletePhoto","params":[],"type":"MessageAction"},{"id":"365886720","predicate":"messageActionChatAddUser","params":[{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1539362612","predicate":"messageActionChatDeleteUser","params":[{"name":"user_id","type":"long"}],"type":"MessageAction"},{"id":"739712882","predicate":"dialog","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"unread_mark","type":"flags.3?true"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"unread_mentions_count","type":"int"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"pts","type":"flags.0?int"},{"name":"draft","type":"flags.1?DraftMessage"},{"name":"folder_id","type":"flags.4?int"}],"type":"Dialog"},{"id":"590459437","predicate":"photoEmpty","params":[{"name":"id","type":"long"}],"type":"Photo"},{"id":"-82216347","predicate":"photo","params":[{"name":"flags","type":"#"},{"name":"has_stickers","type":"flags.0?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"sizes","type":"Vector"},{"name":"video_sizes","type":"flags.1?Vector"},{"name":"dc_id","type":"int"}],"type":"Photo"},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize"},{"id":"1976012384","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize"},{"id":"35527382","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"286776671","predicate":"geoPointEmpty","params":[],"type":"GeoPoint"},{"id":"-1297942941","predicate":"geoPoint","params":[{"name":"flags","type":"#"},{"name":"long","type":"double"},{"name":"lat","type":"double"},{"name":"access_hash","type":"long"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"GeoPoint"},{"id":"1577067778","predicate":"auth.sentCode","params":[{"name":"flags","type":"#"},{"name":"type","type":"auth.SentCodeType"},{"name":"phone_code_hash","type":"string"},{"name":"next_type","type":"flags.1?auth.CodeType"},{"name":"timeout","type":"flags.2?int"}],"type":"auth.SentCode"},{"id":"-855308010","predicate":"auth.authorization","params":[{"name":"flags","type":"#"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"user","type":"User"}],"type":"auth.Authorization"},{"id":"-1271602504","predicate":"auth.exportedAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.ExportedAuthorization"},{"id":"-1195615476","predicate":"inputNotifyPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputNotifyPeer"},{"id":"423314455","predicate":"inputNotifyUsers","params":[],"type":"InputNotifyPeer"},{"id":"1251338318","predicate":"inputNotifyChats","params":[],"type":"InputNotifyPeer"},{"id":"-1673717362","predicate":"inputPeerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"InputPeerNotifySettings"},{"id":"-1353671392","predicate":"peerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"PeerNotifySettings"},{"id":"1933519201","predicate":"peerSettings","params":[{"name":"flags","type":"#"},{"name":"report_spam","type":"flags.0?true"},{"name":"add_contact","type":"flags.1?true"},{"name":"block_contact","type":"flags.2?true"},{"name":"share_contact","type":"flags.3?true"},{"name":"need_contacts_exception","type":"flags.4?true"},{"name":"report_geo","type":"flags.5?true"},{"name":"autoarchived","type":"flags.7?true"},{"name":"invite_members","type":"flags.8?true"},{"name":"geo_distance","type":"flags.6?int"}],"type":"PeerSettings"},{"id":"-1539849235","predicate":"wallPaper","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"pattern","type":"flags.3?true"},{"name":"dark","type":"flags.4?true"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"document","type":"Document"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"1490799288","predicate":"inputReportReasonSpam","params":[],"type":"ReportReason"},{"id":"505595789","predicate":"inputReportReasonViolence","params":[],"type":"ReportReason"},{"id":"777640226","predicate":"inputReportReasonPornography","params":[],"type":"ReportReason"},{"id":"-1376497949","predicate":"inputReportReasonChildAbuse","params":[],"type":"ReportReason"},{"id":"-1041980751","predicate":"inputReportReasonOther","params":[],"type":"ReportReason"},{"id":"-694681851","predicate":"userFull","params":[{"name":"flags","type":"#"},{"name":"blocked","type":"flags.0?true"},{"name":"phone_calls_available","type":"flags.4?true"},{"name":"phone_calls_private","type":"flags.5?true"},{"name":"can_pin_message","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.12?true"},{"name":"video_calls_available","type":"flags.13?true"},{"name":"user","type":"User"},{"name":"about","type":"flags.1?string"},{"name":"settings","type":"PeerSettings"},{"name":"profile_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"bot_info","type":"flags.3?BotInfo"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"common_chats_count","type":"int"},{"name":"folder_id","type":"flags.11?int"},{"name":"ttl_period","type":"flags.14?int"},{"name":"theme_emoticon","type":"flags.15?string"}],"type":"UserFull"},{"id":"341499403","predicate":"contact","params":[{"name":"user_id","type":"long"},{"name":"mutual","type":"Bool"}],"type":"Contact"},{"id":"-1052885936","predicate":"importedContact","params":[{"name":"user_id","type":"long"},{"name":"client_id","type":"long"}],"type":"ImportedContact"},{"id":"383348795","predicate":"contactStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"ContactStatus"},{"id":"-1219778094","predicate":"contacts.contactsNotModified","params":[],"type":"contacts.Contacts"},{"id":"-353862078","predicate":"contacts.contacts","params":[{"name":"contacts","type":"Vector"},{"name":"saved_count","type":"int"},{"name":"users","type":"Vector"}],"type":"contacts.Contacts"},{"id":"2010127419","predicate":"contacts.importedContacts","params":[{"name":"imported","type":"Vector"},{"name":"popular_invites","type":"Vector"},{"name":"retry_contacts","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"182326673","predicate":"contacts.blocked","params":[{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"-513392236","predicate":"contacts.blockedSlice","params":[{"name":"count","type":"int"},{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"364538944","predicate":"messages.dialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"1910543603","predicate":"messages.dialogsSlice","params":[{"name":"count","type":"int"},{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"-1938715001","predicate":"messages.messages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"978610270","predicate":"messages.messagesSlice","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"count","type":"int"},{"name":"next_rate","type":"flags.0?int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"1694474197","predicate":"messages.chats","params":[{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-438840932","predicate":"messages.chatFull","params":[{"name":"full_chat","type":"ChatFull"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatFull"},{"id":"-1269012015","predicate":"messages.affectedHistory","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"}],"type":"messages.AffectedHistory"},{"id":"1474492012","predicate":"inputMessagesFilterEmpty","params":[],"type":"MessagesFilter"},{"id":"-1777752804","predicate":"inputMessagesFilterPhotos","params":[],"type":"MessagesFilter"},{"id":"-1614803355","predicate":"inputMessagesFilterVideo","params":[],"type":"MessagesFilter"},{"id":"1458172132","predicate":"inputMessagesFilterPhotoVideo","params":[],"type":"MessagesFilter"},{"id":"-1629621880","predicate":"inputMessagesFilterDocument","params":[],"type":"MessagesFilter"},{"id":"2129714567","predicate":"inputMessagesFilterUrl","params":[],"type":"MessagesFilter"},{"id":"-3644025","predicate":"inputMessagesFilterGif","params":[],"type":"MessagesFilter"},{"id":"522914557","predicate":"updateNewMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1318109142","predicate":"updateMessageID","params":[{"name":"id","type":"int"},{"name":"random_id","type":"long"}],"type":"Update"},{"id":"-1576161051","predicate":"updateDeleteMessages","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1071741569","predicate":"updateUserTyping","params":[{"name":"user_id","type":"long"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-2092401936","predicate":"updateChatUserTyping","params":[{"name":"chat_id","type":"long"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"125178264","predicate":"updateChatParticipants","params":[{"name":"participants","type":"ChatParticipants"}],"type":"Update"},{"id":"-440534818","predicate":"updateUserStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"Update"},{"id":"-1007549728","predicate":"updateUserName","params":[{"name":"user_id","type":"long"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"username","type":"string"}],"type":"Update"},{"id":"-232290676","predicate":"updateUserPhoto","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"photo","type":"UserProfilePhoto"},{"name":"previous","type":"Bool"}],"type":"Update"},{"id":"-1519637954","predicate":"updates.state","params":[{"name":"pts","type":"int"},{"name":"qts","type":"int"},{"name":"date","type":"int"},{"name":"seq","type":"int"},{"name":"unread_count","type":"int"}],"type":"updates.State"},{"id":"1567990072","predicate":"updates.differenceEmpty","params":[{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"updates.Difference"},{"id":"16030880","predicate":"updates.difference","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-1459938943","predicate":"updates.differenceSlice","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"intermediate_state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-484987010","predicate":"updatesTooLong","params":[],"type":"Updates"},{"id":"826001400","predicate":"updateShortMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"user_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"1299050149","predicate":"updateShortChatMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"from_id","type":"long"},{"name":"chat_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"2027216577","predicate":"updateShort","params":[{"name":"update","type":"Update"},{"name":"date","type":"int"}],"type":"Updates"},{"id":"1918567619","predicate":"updatesCombined","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq_start","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"1957577280","predicate":"updates","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"-1916114267","predicate":"photos.photos","params":[{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"352657236","predicate":"photos.photosSlice","params":[{"name":"count","type":"int"},{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"539045032","predicate":"photos.photo","params":[{"name":"photo","type":"Photo"},{"name":"users","type":"Vector"}],"type":"photos.Photo"},{"id":"157948117","predicate":"upload.file","params":[{"name":"type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.File"},{"id":"414687501","predicate":"dcOption","params":[{"name":"flags","type":"#"},{"name":"ipv6","type":"flags.0?true"},{"name":"media_only","type":"flags.1?true"},{"name":"tcpo_only","type":"flags.2?true"},{"name":"cdn","type":"flags.3?true"},{"name":"static","type":"flags.4?true"},{"name":"id","type":"int"},{"name":"ip_address","type":"string"},{"name":"port","type":"int"},{"name":"secret","type":"flags.10?bytes"}],"type":"DcOption"},{"id":"856375399","predicate":"config","params":[{"name":"flags","type":"#"},{"name":"phonecalls_enabled","type":"flags.1?true"},{"name":"default_p2p_contacts","type":"flags.3?true"},{"name":"preload_featured_stickers","type":"flags.4?true"},{"name":"ignore_phone_entities","type":"flags.5?true"},{"name":"revoke_pm_inbox","type":"flags.6?true"},{"name":"blocked_mode","type":"flags.8?true"},{"name":"pfs_enabled","type":"flags.13?true"},{"name":"date","type":"int"},{"name":"expires","type":"int"},{"name":"test_mode","type":"Bool"},{"name":"this_dc","type":"int"},{"name":"dc_options","type":"Vector"},{"name":"dc_txt_domain_name","type":"string"},{"name":"chat_size_max","type":"int"},{"name":"megagroup_size_max","type":"int"},{"name":"forwarded_count_max","type":"int"},{"name":"online_update_period_ms","type":"int"},{"name":"offline_blur_timeout_ms","type":"int"},{"name":"offline_idle_timeout_ms","type":"int"},{"name":"online_cloud_timeout_ms","type":"int"},{"name":"notify_cloud_delay_ms","type":"int"},{"name":"notify_default_delay_ms","type":"int"},{"name":"push_chat_period_ms","type":"int"},{"name":"push_chat_limit","type":"int"},{"name":"saved_gifs_limit","type":"int"},{"name":"edit_time_limit","type":"int"},{"name":"revoke_time_limit","type":"int"},{"name":"revoke_pm_time_limit","type":"int"},{"name":"rating_e_decay","type":"int"},{"name":"stickers_recent_limit","type":"int"},{"name":"stickers_faved_limit","type":"int"},{"name":"channels_read_media_period","type":"int"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"pinned_dialogs_count_max","type":"int"},{"name":"pinned_infolder_count_max","type":"int"},{"name":"call_receive_timeout_ms","type":"int"},{"name":"call_ring_timeout_ms","type":"int"},{"name":"call_connect_timeout_ms","type":"int"},{"name":"call_packet_timeout_ms","type":"int"},{"name":"me_url_prefix","type":"string"},{"name":"autoupdate_url_prefix","type":"flags.7?string"},{"name":"gif_search_username","type":"flags.9?string"},{"name":"venue_search_username","type":"flags.10?string"},{"name":"img_search_username","type":"flags.11?string"},{"name":"static_maps_provider","type":"flags.12?string"},{"name":"caption_length_max","type":"int"},{"name":"message_length_max","type":"int"},{"name":"webfile_dc_id","type":"int"},{"name":"suggested_lang_code","type":"flags.2?string"},{"name":"lang_pack_version","type":"flags.2?int"},{"name":"base_lang_pack_version","type":"flags.2?int"}],"type":"Config"},{"id":"-1910892683","predicate":"nearestDc","params":[{"name":"country","type":"string"},{"name":"this_dc","type":"int"},{"name":"nearest_dc","type":"int"}],"type":"NearestDc"},{"id":"-860107216","predicate":"help.appUpdate","params":[{"name":"flags","type":"#"},{"name":"can_not_skip","type":"flags.0?true"},{"name":"id","type":"int"},{"name":"version","type":"string"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"document","type":"flags.1?Document"},{"name":"url","type":"flags.2?string"},{"name":"sticker","type":"flags.3?Document"}],"type":"help.AppUpdate"},{"id":"-1000708810","predicate":"help.noAppUpdate","params":[],"type":"help.AppUpdate"},{"id":"415997816","predicate":"help.inviteText","params":[{"name":"message","type":"string"}],"type":"help.InviteText"},{"id":"314359194","predicate":"updateNewEncryptedMessage","params":[{"name":"message","type":"EncryptedMessage"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"386986326","predicate":"updateEncryptedChatTyping","params":[{"name":"chat_id","type":"int"}],"type":"Update"},{"id":"-1264392051","predicate":"updateEncryption","params":[{"name":"chat","type":"EncryptedChat"},{"name":"date","type":"int"}],"type":"Update"},{"id":"956179895","predicate":"updateEncryptedMessagesRead","params":[{"name":"chat_id","type":"int"},{"name":"max_date","type":"int"},{"name":"date","type":"int"}],"type":"Update"},{"id":"-1417756512","predicate":"encryptedChatEmpty","params":[{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"1722964307","predicate":"encryptedChatWaiting","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"}],"type":"EncryptedChat"},{"id":"1223809356","predicate":"encryptedChatRequested","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1643173063","predicate":"encryptedChat","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"505183301","predicate":"encryptedChatDiscarded","params":[{"name":"flags","type":"#"},{"name":"history_deleted","type":"flags.0?true"},{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"-247351839","predicate":"inputEncryptedChat","params":[{"name":"chat_id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedChat"},{"id":"-1038136962","predicate":"encryptedFileEmpty","params":[],"type":"EncryptedFile"},{"id":"1248893260","predicate":"encryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"EncryptedFile"},{"id":"406307684","predicate":"inputEncryptedFileEmpty","params":[],"type":"InputEncryptedFile"},{"id":"1690108678","predicate":"inputEncryptedFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1511503333","predicate":"inputEncryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedFile"},{"id":"-182231723","predicate":"inputEncryptedFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"-317144808","predicate":"encryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"},{"name":"file","type":"EncryptedFile"}],"type":"EncryptedMessage"},{"id":"594758406","predicate":"encryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"}],"type":"EncryptedMessage"},{"id":"-1058912715","predicate":"messages.dhConfigNotModified","params":[{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"740433629","predicate":"messages.dhConfig","params":[{"name":"g","type":"int"},{"name":"p","type":"bytes"},{"name":"version","type":"int"},{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"1443858741","predicate":"messages.sentEncryptedMessage","params":[{"name":"date","type":"int"}],"type":"messages.SentEncryptedMessage"},{"id":"-1802240206","predicate":"messages.sentEncryptedFile","params":[{"name":"date","type":"int"},{"name":"file","type":"EncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"-95482955","predicate":"inputFileBig","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"}],"type":"InputFile"},{"id":"767652808","predicate":"inputEncryptedFileBigUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1037718609","predicate":"updateChatParticipantAdd","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-483443337","predicate":"updateChatParticipantDelete","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-1906403213","predicate":"updateDcOptions","params":[{"name":"dc_options","type":"Vector"}],"type":"Update"},{"id":"1530447553","predicate":"inputMediaUploadedDocument","params":[{"name":"flags","type":"#"},{"name":"nosound_video","type":"flags.3?true"},{"name":"force_file","type":"flags.4?true"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.2?InputFile"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"860303448","predicate":"inputMediaDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputDocument"},{"name":"ttl_seconds","type":"flags.0?int"},{"name":"query","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-1666158377","predicate":"messageMediaDocument","params":[{"name":"flags","type":"#"},{"name":"document","type":"flags.0?Document"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1928391342","predicate":"inputDocumentEmpty","params":[],"type":"InputDocument"},{"id":"448771445","predicate":"inputDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputDocument"},{"id":"-1160743548","predicate":"inputDocumentFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"922273905","predicate":"documentEmpty","params":[{"name":"id","type":"long"}],"type":"Document"},{"id":"512177195","predicate":"document","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumbs","type":"flags.0?Vector"},{"name":"video_thumbs","type":"flags.1?Vector"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"Document"},{"id":"398898678","predicate":"help.support","params":[{"name":"phone_number","type":"string"},{"name":"user","type":"User"}],"type":"help.Support"},{"id":"-1613493288","predicate":"notifyPeer","params":[{"name":"peer","type":"Peer"}],"type":"NotifyPeer"},{"id":"-1261946036","predicate":"notifyUsers","params":[],"type":"NotifyPeer"},{"id":"-1073230141","predicate":"notifyChats","params":[],"type":"NotifyPeer"},{"id":"-1094555409","predicate":"updateNotifySettings","params":[{"name":"peer","type":"NotifyPeer"},{"name":"notify_settings","type":"PeerNotifySettings"}],"type":"Update"},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction"},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction"},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction"},{"id":"-378127636","predicate":"sendMessageUploadVideoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction"},{"id":"-212740181","predicate":"sendMessageUploadAudioAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-774682074","predicate":"sendMessageUploadPhotoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-1441998364","predicate":"sendMessageUploadDocumentAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction"},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction"},{"id":"-1290580579","predicate":"contacts.found","params":[{"name":"my_results","type":"Vector"},{"name":"results","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Found"},{"id":"-337352679","predicate":"updateServiceNotification","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"inbox_date","type":"flags.1?int"},{"name":"type","type":"string"},{"name":"message","type":"string"},{"name":"media","type":"MessageMedia"},{"name":"entities","type":"Vector"}],"type":"Update"},{"id":"-496024847","predicate":"userStatusRecently","params":[],"type":"UserStatus"},{"id":"129960444","predicate":"userStatusLastWeek","params":[],"type":"UserStatus"},{"id":"2011940674","predicate":"userStatusLastMonth","params":[],"type":"UserStatus"},{"id":"-298113238","predicate":"updatePrivacy","params":[{"name":"key","type":"PrivacyKey"},{"name":"rules","type":"Vector"}],"type":"Update"},{"id":"1335282456","predicate":"inputPrivacyKeyStatusTimestamp","params":[],"type":"InputPrivacyKey"},{"id":"-1137792208","predicate":"privacyKeyStatusTimestamp","params":[],"type":"PrivacyKey"},{"id":"218751099","predicate":"inputPrivacyValueAllowContacts","params":[],"type":"InputPrivacyRule"},{"id":"407582158","predicate":"inputPrivacyValueAllowAll","params":[],"type":"InputPrivacyRule"},{"id":"320652927","predicate":"inputPrivacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"195371015","predicate":"inputPrivacyValueDisallowContacts","params":[],"type":"InputPrivacyRule"},{"id":"-697604407","predicate":"inputPrivacyValueDisallowAll","params":[],"type":"InputPrivacyRule"},{"id":"-1877932953","predicate":"inputPrivacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-123988","predicate":"privacyValueAllowContacts","params":[],"type":"PrivacyRule"},{"id":"1698855810","predicate":"privacyValueAllowAll","params":[],"type":"PrivacyRule"},{"id":"-1198497870","predicate":"privacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"-125240806","predicate":"privacyValueDisallowContacts","params":[],"type":"PrivacyRule"},{"id":"-1955338397","predicate":"privacyValueDisallowAll","params":[],"type":"PrivacyRule"},{"id":"-463335103","predicate":"privacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"1352683077","predicate":"account.privacyRules","params":[{"name":"rules","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"-1194283041","predicate":"accountDaysTTL","params":[{"name":"days","type":"int"}],"type":"AccountDaysTTL"},{"id":"88680979","predicate":"updateUserPhone","params":[{"name":"user_id","type":"long"},{"name":"phone","type":"string"}],"type":"Update"},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute"},{"id":"1662637586","predicate":"documentAttributeSticker","params":[{"name":"flags","type":"#"},{"name":"mask","type":"flags.1?true"},{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"DocumentAttribute"},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"round_message","type":"flags.0?true"},{"name":"supports_streaming","type":"flags.1?true"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"voice","type":"flags.10?true"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute"},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute"},{"id":"-244016606","predicate":"messages.stickersNotModified","params":[],"type":"messages.Stickers"},{"id":"816245886","predicate":"messages.stickers","params":[{"name":"hash","type":"long"},{"name":"stickers","type":"Vector"}],"type":"messages.Stickers"},{"id":"313694676","predicate":"stickerPack","params":[{"name":"emoticon","type":"string"},{"name":"documents","type":"Vector"}],"type":"StickerPack"},{"id":"-395967805","predicate":"messages.allStickersNotModified","params":[],"type":"messages.AllStickers"},{"id":"-843329861","predicate":"messages.allStickers","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.AllStickers"},{"id":"-1667805217","predicate":"updateReadHistoryInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"791617983","predicate":"updateReadHistoryOutbox","params":[{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-2066640507","predicate":"messages.affectedMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"messages.AffectedMessages"},{"id":"2139689491","predicate":"updateWebPage","params":[{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-350980120","predicate":"webPageEmpty","params":[{"name":"id","type":"long"}],"type":"WebPage"},{"id":"-981018084","predicate":"webPagePending","params":[{"name":"id","type":"long"},{"name":"date","type":"int"}],"type":"WebPage"},{"id":"-392411726","predicate":"webPage","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"url","type":"string"},{"name":"display_url","type":"string"},{"name":"hash","type":"int"},{"name":"type","type":"flags.0?string"},{"name":"site_name","type":"flags.1?string"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"photo","type":"flags.4?Photo"},{"name":"embed_url","type":"flags.5?string"},{"name":"embed_type","type":"flags.5?string"},{"name":"embed_width","type":"flags.6?int"},{"name":"embed_height","type":"flags.6?int"},{"name":"duration","type":"flags.7?int"},{"name":"author","type":"flags.8?string"},{"name":"document","type":"flags.9?Document"},{"name":"cached_page","type":"flags.10?Page"},{"name":"attributes","type":"flags.12?Vector"}],"type":"WebPage"},{"id":"-1557277184","predicate":"messageMediaWebPage","params":[{"name":"webpage","type":"WebPage"}],"type":"MessageMedia"},{"id":"-1392388579","predicate":"authorization","params":[{"name":"flags","type":"#"},{"name":"current","type":"flags.0?true"},{"name":"official_app","type":"flags.1?true"},{"name":"password_pending","type":"flags.2?true"},{"name":"encrypted_requests_disabled","type":"flags.3?true"},{"name":"call_requests_disabled","type":"flags.4?true"},{"name":"hash","type":"long"},{"name":"device_model","type":"string"},{"name":"platform","type":"string"},{"name":"system_version","type":"string"},{"name":"api_id","type":"int"},{"name":"app_name","type":"string"},{"name":"app_version","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"country","type":"string"},{"name":"region","type":"string"}],"type":"Authorization"},{"id":"307276766","predicate":"account.authorizations","params":[{"name":"authorizations","type":"Vector"}],"type":"account.Authorizations"},{"id":"408623183","predicate":"account.password","params":[{"name":"flags","type":"#"},{"name":"has_recovery","type":"flags.0?true"},{"name":"has_secure_values","type":"flags.1?true"},{"name":"has_password","type":"flags.2?true"},{"name":"current_algo","type":"flags.2?PasswordKdfAlgo"},{"name":"srp_B","type":"flags.2?bytes"},{"name":"srp_id","type":"flags.2?long"},{"name":"hint","type":"flags.3?string"},{"name":"email_unconfirmed_pattern","type":"flags.4?string"},{"name":"new_algo","type":"PasswordKdfAlgo"},{"name":"new_secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_random","type":"bytes"},{"name":"pending_reset_date","type":"flags.5?int"}],"type":"account.Password"},{"id":"-1705233435","predicate":"account.passwordSettings","params":[{"name":"flags","type":"#"},{"name":"email","type":"flags.0?string"},{"name":"secure_settings","type":"flags.1?SecureSecretSettings"}],"type":"account.PasswordSettings"},{"id":"-1036572727","predicate":"account.passwordInputSettings","params":[{"name":"flags","type":"#"},{"name":"new_algo","type":"flags.0?PasswordKdfAlgo"},{"name":"new_password_hash","type":"flags.0?bytes"},{"name":"hint","type":"flags.0?string"},{"name":"email","type":"flags.1?string"},{"name":"new_secure_settings","type":"flags.2?SecureSecretSettings"}],"type":"account.PasswordInputSettings"},{"id":"326715557","predicate":"auth.passwordRecovery","params":[{"name":"email_pattern","type":"string"}],"type":"auth.PasswordRecovery"},{"id":"-1052959727","predicate":"inputMediaVenue","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"InputMedia"},{"id":"784356159","predicate":"messageMediaVenue","params":[{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"MessageMedia"},{"id":"-1551583367","predicate":"receivedNotifyMessage","params":[{"name":"id","type":"int"},{"name":"flags","type":"int"}],"type":"ReceivedNotifyMessage"},{"id":"-1316944408","predicate":"chatInviteExported","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.0?true"},{"name":"permanent","type":"flags.5?true"},{"name":"link","type":"string"},{"name":"admin_id","type":"long"},{"name":"date","type":"int"},{"name":"start_date","type":"flags.4?int"},{"name":"expire_date","type":"flags.1?int"},{"name":"usage_limit","type":"flags.2?int"},{"name":"usage","type":"flags.3?int"}],"type":"ExportedChatInvite"},{"id":"1516793212","predicate":"chatInviteAlready","params":[{"name":"chat","type":"Chat"}],"type":"ChatInvite"},{"id":"-540871282","predicate":"chatInvite","params":[{"name":"flags","type":"#"},{"name":"channel","type":"flags.0?true"},{"name":"broadcast","type":"flags.1?true"},{"name":"public","type":"flags.2?true"},{"name":"megagroup","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"photo","type":"Photo"},{"name":"participants_count","type":"int"},{"name":"participants","type":"flags.4?Vector"}],"type":"ChatInvite"},{"id":"51520707","predicate":"messageActionChatJoinedByLink","params":[{"name":"inviter_id","type":"long"}],"type":"MessageAction"},{"id":"1757493555","predicate":"updateReadMessagesContents","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet"},{"id":"-1645763991","predicate":"inputStickerSetID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputStickerSet"},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet"},{"id":"-673242758","predicate":"stickerSet","params":[{"name":"flags","type":"#"},{"name":"archived","type":"flags.1?true"},{"name":"official","type":"flags.2?true"},{"name":"masks","type":"flags.3?true"},{"name":"animated","type":"flags.5?true"},{"name":"videos","type":"flags.6?true"},{"name":"installed_date","type":"flags.0?int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumbs","type":"flags.4?Vector"},{"name":"thumb_dc_id","type":"flags.4?int"},{"name":"thumb_version","type":"flags.4?int"},{"name":"count","type":"int"},{"name":"hash","type":"int"}],"type":"StickerSet"},{"id":"-1240849242","predicate":"messages.stickerSet","params":[{"name":"set","type":"StickerSet"},{"name":"packs","type":"Vector"},{"name":"documents","type":"Vector"}],"type":"messages.StickerSet"},{"id":"1073147056","predicate":"user","params":[{"name":"flags","type":"#"},{"name":"self","type":"flags.10?true"},{"name":"contact","type":"flags.11?true"},{"name":"mutual_contact","type":"flags.12?true"},{"name":"deleted","type":"flags.13?true"},{"name":"bot","type":"flags.14?true"},{"name":"bot_chat_history","type":"flags.15?true"},{"name":"bot_nochats","type":"flags.16?true"},{"name":"verified","type":"flags.17?true"},{"name":"restricted","type":"flags.18?true"},{"name":"min","type":"flags.20?true"},{"name":"bot_inline_geo","type":"flags.21?true"},{"name":"support","type":"flags.23?true"},{"name":"scam","type":"flags.24?true"},{"name":"apply_min_photo","type":"flags.25?true"},{"name":"fake","type":"flags.26?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.0?long"},{"name":"first_name","type":"flags.1?string"},{"name":"last_name","type":"flags.2?string"},{"name":"username","type":"flags.3?string"},{"name":"phone","type":"flags.4?string"},{"name":"photo","type":"flags.5?UserProfilePhoto"},{"name":"status","type":"flags.6?UserStatus"},{"name":"bot_info_version","type":"flags.14?int"},{"name":"restriction_reason","type":"flags.18?Vector"},{"name":"bot_inline_placeholder","type":"flags.19?string"},{"name":"lang_code","type":"flags.22?string"}],"type":"User"},{"id":"-1032140601","predicate":"botCommand","params":[{"name":"command","type":"string"},{"name":"description","type":"string"}],"type":"BotCommand"},{"id":"460632885","predicate":"botInfo","params":[{"name":"user_id","type":"long"},{"name":"description","type":"string"},{"name":"commands","type":"Vector"}],"type":"BotInfo"},{"id":"-1560655744","predicate":"keyboardButton","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"2002815875","predicate":"keyboardButtonRow","params":[{"name":"buttons","type":"Vector"}],"type":"KeyboardButtonRow"},{"id":"-1606526075","predicate":"replyKeyboardHide","params":[{"name":"flags","type":"#"},{"name":"selective","type":"flags.2?true"}],"type":"ReplyMarkup"},{"id":"-2035021048","predicate":"replyKeyboardForceReply","params":[{"name":"flags","type":"#"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-2049074735","predicate":"replyKeyboardMarkup","params":[{"name":"flags","type":"#"},{"name":"resize","type":"flags.0?true"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"rows","type":"Vector"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-571955892","predicate":"inputPeerUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-233744186","predicate":"inputUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputUser"},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity"},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity"},{"id":"-1877614335","predicate":"updateShortSentMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"-292807034","predicate":"inputChannelEmpty","params":[],"type":"InputChannel"},{"id":"-212145112","predicate":"inputChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputChannel"},{"id":"-1566230754","predicate":"peerChannel","params":[{"name":"channel_id","type":"long"}],"type":"Peer"},{"id":"666680316","predicate":"inputPeerChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-2107528095","predicate":"channel","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"left","type":"flags.2?true"},{"name":"broadcast","type":"flags.5?true"},{"name":"verified","type":"flags.7?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"restricted","type":"flags.9?true"},{"name":"signatures","type":"flags.11?true"},{"name":"min","type":"flags.12?true"},{"name":"scam","type":"flags.19?true"},{"name":"has_link","type":"flags.20?true"},{"name":"has_geo","type":"flags.21?true"},{"name":"slowmode_enabled","type":"flags.22?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"fake","type":"flags.25?true"},{"name":"gigagroup","type":"flags.26?true"},{"name":"noforwards","type":"flags.27?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.13?long"},{"name":"title","type":"string"},{"name":"username","type":"flags.6?string"},{"name":"photo","type":"ChatPhoto"},{"name":"date","type":"int"},{"name":"restriction_reason","type":"flags.9?Vector"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"banned_rights","type":"flags.15?ChatBannedRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"},{"name":"participants_count","type":"flags.17?int"}],"type":"Chat"},{"id":"399807445","predicate":"channelForbidden","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.5?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"until_date","type":"flags.16?int"}],"type":"Chat"},{"id":"2131196633","predicate":"contacts.resolvedPeer","params":[{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ResolvedPeer"},{"id":"-374179305","predicate":"channelFull","params":[{"name":"flags","type":"#"},{"name":"can_view_participants","type":"flags.3?true"},{"name":"can_set_username","type":"flags.6?true"},{"name":"can_set_stickers","type":"flags.7?true"},{"name":"hidden_prehistory","type":"flags.10?true"},{"name":"can_set_location","type":"flags.16?true"},{"name":"has_scheduled","type":"flags.19?true"},{"name":"can_view_stats","type":"flags.20?true"},{"name":"blocked","type":"flags.22?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants_count","type":"flags.0?int"},{"name":"admins_count","type":"flags.1?int"},{"name":"kicked_count","type":"flags.2?int"},{"name":"banned_count","type":"flags.2?int"},{"name":"online_count","type":"flags.13?int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"chat_photo","type":"Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.23?ExportedChatInvite"},{"name":"bot_info","type":"Vector"},{"name":"migrated_from_chat_id","type":"flags.4?long"},{"name":"migrated_from_max_id","type":"flags.4?int"},{"name":"pinned_msg_id","type":"flags.5?int"},{"name":"stickerset","type":"flags.8?StickerSet"},{"name":"available_min_id","type":"flags.9?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"linked_chat_id","type":"flags.14?long"},{"name":"location","type":"flags.15?ChannelLocation"},{"name":"slowmode_seconds","type":"flags.17?int"},{"name":"slowmode_next_send_date","type":"flags.18?int"},{"name":"stats_dc","type":"flags.12?int"},{"name":"pts","type":"int"},{"name":"call","type":"flags.21?InputGroupCall"},{"name":"ttl_period","type":"flags.24?int"},{"name":"pending_suggestions","type":"flags.25?Vector"},{"name":"groupcall_default_join_as","type":"flags.26?Peer"},{"name":"theme_emoticon","type":"flags.27?string"}],"type":"ChatFull"},{"id":"182649427","predicate":"messageRange","params":[{"name":"min_id","type":"int"},{"name":"max_id","type":"int"}],"type":"MessageRange"},{"id":"1682413576","predicate":"messages.channelMessages","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"pts","type":"int"},{"name":"count","type":"int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"-1781355374","predicate":"messageActionChannelCreate","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"277713951","predicate":"updateChannelTooLong","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"pts","type":"flags.0?int"}],"type":"Update"},{"id":"1666927625","predicate":"updateChannel","params":[{"name":"channel_id","type":"long"}],"type":"Update"},{"id":"1656358105","predicate":"updateNewChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1842450928","predicate":"updateReadChannelInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"}],"type":"Update"},{"id":"-1020437742","predicate":"updateDeleteChannelMessages","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-232346616","predicate":"updateChannelMessageViews","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"views","type":"int"}],"type":"Update"},{"id":"1041346555","predicate":"updates.channelDifferenceEmpty","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"}],"type":"updates.ChannelDifference"},{"id":"-1531132162","predicate":"updates.channelDifferenceTooLong","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"timeout","type":"flags.1?int"},{"name":"dialog","type":"Dialog"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"543450958","predicate":"updates.channelDifference","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"},{"name":"new_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"-1798033689","predicate":"channelMessagesFilterEmpty","params":[],"type":"ChannelMessagesFilter"},{"id":"-847783593","predicate":"channelMessagesFilter","params":[{"name":"flags","type":"#"},{"name":"exclude_new_messages","type":"flags.1?true"},{"name":"ranges","type":"Vector"}],"type":"ChannelMessagesFilter"},{"id":"-1072953408","predicate":"channelParticipant","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"682146919","predicate":"channelParticipantSelf","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"803602899","predicate":"channelParticipantCreator","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.0?string"}],"type":"ChannelParticipant"},{"id":"-566281095","predicate":"channelParticipantsRecent","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1268741783","predicate":"channelParticipantsAdmins","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1548400251","predicate":"channelParticipantsKicked","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-1699676497","predicate":"channels.channelParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipants"},{"id":"-541588713","predicate":"channels.channelParticipant","params":[{"name":"participant","type":"ChannelParticipant"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipant"},{"id":"-462696732","predicate":"chatParticipantCreator","params":[{"name":"user_id","type":"long"}],"type":"ChatParticipant"},{"id":"-1600962725","predicate":"chatParticipantAdmin","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-674602590","predicate":"updateChatParticipantAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"is_admin","type":"Bool"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-519864430","predicate":"messageActionChatMigrateTo","params":[{"name":"channel_id","type":"long"}],"type":"MessageAction"},{"id":"-365344535","predicate":"messageActionChannelMigrateFrom","params":[{"name":"title","type":"string"},{"name":"chat_id","type":"long"}],"type":"MessageAction"},{"id":"-1328445861","predicate":"channelParticipantsBots","params":[],"type":"ChannelParticipantsFilter"},{"id":"2013922064","predicate":"help.termsOfService","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"id","type":"DataJSON"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"min_age_confirm","type":"flags.1?int"}],"type":"help.TermsOfService"},{"id":"1753886890","predicate":"updateNewStickerSet","params":[{"name":"stickerset","type":"messages.StickerSet"}],"type":"Update"},{"id":"196268545","predicate":"updateStickerSetsOrder","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Update"},{"id":"1135492588","predicate":"updateStickerSets","params":[],"type":"Update"},{"id":"-402498398","predicate":"messages.savedGifsNotModified","params":[],"type":"messages.SavedGifs"},{"id":"-2069878259","predicate":"messages.savedGifs","params":[{"name":"hash","type":"long"},{"name":"gifs","type":"Vector"}],"type":"messages.SavedGifs"},{"id":"-1821035490","predicate":"updateSavedGifs","params":[],"type":"Update"},{"id":"864077702","predicate":"inputBotInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1036876423","predicate":"inputBotInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-2000710887","predicate":"inputBotInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?InputWebDocument"},{"name":"content","type":"flags.5?InputWebDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1984755728","predicate":"botInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1937807902","predicate":"botInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"295067450","predicate":"botInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?WebDocument"},{"name":"content","type":"flags.5?WebDocument"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1803769784","predicate":"messages.botResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"query_id","type":"long"},{"name":"next_offset","type":"flags.1?string"},{"name":"switch_pm","type":"flags.2?InlineBotSwitchPM"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"users","type":"Vector"}],"type":"messages.BotResults"},{"id":"1232025500","predicate":"updateBotInlineQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"peer_type","type":"flags.1?InlineQueryPeerType"},{"name":"offset","type":"string"}],"type":"Update"},{"id":"317794823","predicate":"updateBotInlineSend","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"id","type":"string"},{"name":"msg_id","type":"flags.1?InputBotInlineMessageID"}],"type":"Update"},{"id":"1358283666","predicate":"inputMessagesFilterVoice","params":[],"type":"MessagesFilter"},{"id":"928101534","predicate":"inputMessagesFilterMusic","params":[],"type":"MessagesFilter"},{"id":"-1107622874","predicate":"inputPrivacyKeyChatInvite","params":[],"type":"InputPrivacyKey"},{"id":"1343122938","predicate":"privacyKeyChatInvite","params":[],"type":"PrivacyKey"},{"id":"1571494644","predicate":"exportedMessageLink","params":[{"name":"link","type":"string"},{"name":"html","type":"string"}],"type":"ExportedMessageLink"},{"id":"1601666510","predicate":"messageFwdHeader","params":[{"name":"flags","type":"#"},{"name":"imported","type":"flags.7?true"},{"name":"from_id","type":"flags.0?Peer"},{"name":"from_name","type":"flags.5?string"},{"name":"date","type":"int"},{"name":"channel_post","type":"flags.2?int"},{"name":"post_author","type":"flags.3?string"},{"name":"saved_from_peer","type":"flags.4?Peer"},{"name":"saved_from_msg_id","type":"flags.4?int"},{"name":"psa_type","type":"flags.6?string"}],"type":"MessageFwdHeader"},{"id":"457133559","predicate":"updateEditChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1799538451","predicate":"messageActionPinMessage","params":[],"type":"MessageAction"},{"id":"1923290508","predicate":"auth.codeTypeSms","params":[],"type":"auth.CodeType"},{"id":"1948046307","predicate":"auth.codeTypeCall","params":[],"type":"auth.CodeType"},{"id":"577556219","predicate":"auth.codeTypeFlashCall","params":[],"type":"auth.CodeType"},{"id":"1035688326","predicate":"auth.sentCodeTypeApp","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1073693790","predicate":"auth.sentCodeTypeSms","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"1398007207","predicate":"auth.sentCodeTypeCall","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1425815847","predicate":"auth.sentCodeTypeFlashCall","params":[{"name":"pattern","type":"string"}],"type":"auth.SentCodeType"},{"id":"629866245","predicate":"keyboardButtonUrl","params":[{"name":"text","type":"string"},{"name":"url","type":"string"}],"type":"KeyboardButton"},{"id":"901503851","predicate":"keyboardButtonCallback","params":[{"name":"flags","type":"#"},{"name":"requires_password","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"data","type":"bytes"}],"type":"KeyboardButton"},{"id":"-1318425559","predicate":"keyboardButtonRequestPhone","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-59151553","predicate":"keyboardButtonRequestGeoLocation","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"90744648","predicate":"keyboardButtonSwitchInline","params":[{"name":"flags","type":"#"},{"name":"same_peer","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"query","type":"string"}],"type":"KeyboardButton"},{"id":"1218642516","predicate":"replyInlineMarkup","params":[{"name":"rows","type":"Vector"}],"type":"ReplyMarkup"},{"id":"911761060","predicate":"messages.botCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"has_url","type":"flags.3?true"},{"name":"native_ui","type":"flags.4?true"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"messages.BotCallbackAnswer"},{"id":"-1177566067","predicate":"updateBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"649453030","predicate":"messages.messageEditData","params":[{"name":"flags","type":"#"},{"name":"caption","type":"flags.0?true"}],"type":"messages.MessageEditData"},{"id":"-469536605","predicate":"updateEditMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1768777083","predicate":"inputBotInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1098628881","predicate":"inputBotInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-1494368259","predicate":"inputBotInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"85477117","predicate":"botInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1970903652","predicate":"botInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"416402882","predicate":"botInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1462213465","predicate":"inputBotInlineResultPhoto","params":[{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"InputPhoto"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"-459324","predicate":"inputBotInlineResultDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"document","type":"InputDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"400266251","predicate":"botInlineMediaResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"flags.0?Photo"},{"name":"document","type":"flags.1?Document"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1995686519","predicate":"inputBotInlineMessageID","params":[{"name":"dc_id","type":"int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"},{"id":"1763610706","predicate":"updateInlineBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"msg_id","type":"InputBotInlineMessageID"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"1008755359","predicate":"inlineBotSwitchPM","params":[{"name":"text","type":"string"},{"name":"start_param","type":"string"}],"type":"InlineBotSwitchPM"},{"id":"863093588","predicate":"messages.peerDialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"messages.PeerDialogs"},{"id":"-305282981","predicate":"topPeer","params":[{"name":"peer","type":"Peer"},{"name":"rating","type":"double"}],"type":"TopPeer"},{"id":"-1419371685","predicate":"topPeerCategoryBotsPM","params":[],"type":"TopPeerCategory"},{"id":"344356834","predicate":"topPeerCategoryBotsInline","params":[],"type":"TopPeerCategory"},{"id":"104314861","predicate":"topPeerCategoryCorrespondents","params":[],"type":"TopPeerCategory"},{"id":"-1122524854","predicate":"topPeerCategoryGroups","params":[],"type":"TopPeerCategory"},{"id":"371037736","predicate":"topPeerCategoryChannels","params":[],"type":"TopPeerCategory"},{"id":"-75283823","predicate":"topPeerCategoryPeers","params":[{"name":"category","type":"TopPeerCategory"},{"name":"count","type":"int"},{"name":"peers","type":"Vector"}],"type":"TopPeerCategoryPeers"},{"id":"-567906571","predicate":"contacts.topPeersNotModified","params":[],"type":"contacts.TopPeers"},{"id":"1891070632","predicate":"contacts.topPeers","params":[{"name":"categories","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.TopPeers"},{"id":"-595914432","predicate":"messageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"long"}],"type":"MessageEntity"},{"id":"546203849","predicate":"inputMessageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"MessageEntity"},{"id":"975236280","predicate":"inputMessagesFilterChatPhotos","params":[],"type":"MessagesFilter"},{"id":"-1218471511","predicate":"updateReadChannelOutbox","params":[{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"}],"type":"Update"},{"id":"-299124375","predicate":"updateDraftMessage","params":[{"name":"peer","type":"Peer"},{"name":"draft","type":"DraftMessage"}],"type":"Update"},{"id":"453805082","predicate":"draftMessageEmpty","params":[{"name":"flags","type":"#"},{"name":"date","type":"flags.0?int"}],"type":"DraftMessage"},{"id":"-40996577","predicate":"draftMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"},{"name":"date","type":"int"}],"type":"DraftMessage"},{"id":"-1615153660","predicate":"messageActionHistoryClear","params":[],"type":"MessageAction"},{"id":"-958657434","predicate":"messages.featuredStickersNotModified","params":[{"name":"count","type":"int"}],"type":"messages.FeaturedStickers"},{"id":"-2067782896","predicate":"messages.featuredStickers","params":[{"name":"hash","type":"long"},{"name":"count","type":"int"},{"name":"sets","type":"Vector"},{"name":"unread","type":"Vector"}],"type":"messages.FeaturedStickers"},{"id":"1461528386","predicate":"updateReadFeaturedStickers","params":[],"type":"Update"},{"id":"186120336","predicate":"messages.recentStickersNotModified","params":[],"type":"messages.RecentStickers"},{"id":"-1999405994","predicate":"messages.recentStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"},{"name":"dates","type":"Vector"}],"type":"messages.RecentStickers"},{"id":"-1706939360","predicate":"updateRecentStickers","params":[],"type":"Update"},{"id":"1338747336","predicate":"messages.archivedStickers","params":[{"name":"count","type":"int"},{"name":"sets","type":"Vector"}],"type":"messages.ArchivedStickers"},{"id":"946083368","predicate":"messages.stickerSetInstallResultSuccess","params":[],"type":"messages.StickerSetInstallResult"},{"id":"904138920","predicate":"messages.stickerSetInstallResultArchive","params":[{"name":"sets","type":"Vector"}],"type":"messages.StickerSetInstallResult"},{"id":"1678812626","predicate":"stickerSetCovered","params":[{"name":"set","type":"StickerSet"},{"name":"cover","type":"Document"}],"type":"StickerSetCovered"},{"id":"-1574314746","predicate":"updateConfig","params":[],"type":"Update"},{"id":"861169551","predicate":"updatePtsChanged","params":[],"type":"Update"},{"id":"-440664550","predicate":"inputMediaPhotoExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-78455655","predicate":"inputMediaDocumentExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"872932635","predicate":"stickerSetMultiCovered","params":[{"name":"set","type":"StickerSet"},{"name":"covers","type":"Vector"}],"type":"StickerSetCovered"},{"id":"-1361650766","predicate":"maskCoords","params":[{"name":"n","type":"int"},{"name":"x","type":"double"},{"name":"y","type":"double"},{"name":"zoom","type":"double"}],"type":"MaskCoords"},{"id":"-1744710921","predicate":"documentAttributeHasStickers","params":[],"type":"DocumentAttribute"},{"id":"1251549527","predicate":"inputStickeredMediaPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputStickeredMedia"},{"id":"70813275","predicate":"inputStickeredMediaDocument","params":[{"name":"id","type":"InputDocument"}],"type":"InputStickeredMedia"},{"id":"-1107729093","predicate":"game","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"short_name","type":"string"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"Photo"},{"name":"document","type":"flags.0?Document"}],"type":"Game"},{"id":"1336154098","predicate":"inputBotInlineResultGame","params":[{"name":"id","type":"string"},{"name":"short_name","type":"string"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1262639204","predicate":"inputBotInlineMessageGame","params":[{"name":"flags","type":"#"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-38694904","predicate":"messageMediaGame","params":[{"name":"game","type":"Game"}],"type":"MessageMedia"},{"id":"-750828557","predicate":"inputMediaGame","params":[{"name":"id","type":"InputGame"}],"type":"InputMedia"},{"id":"53231223","predicate":"inputGameID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGame"},{"id":"-1020139510","predicate":"inputGameShortName","params":[{"name":"bot_id","type":"InputUser"},{"name":"short_name","type":"string"}],"type":"InputGame"},{"id":"1358175439","predicate":"keyboardButtonGame","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-1834538890","predicate":"messageActionGameScore","params":[{"name":"game_id","type":"long"},{"name":"score","type":"int"}],"type":"MessageAction"},{"id":"1940093419","predicate":"highScore","params":[{"name":"pos","type":"int"},{"name":"user_id","type":"long"},{"name":"score","type":"int"}],"type":"HighScore"},{"id":"-1707344487","predicate":"messages.highScores","params":[{"name":"scores","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.HighScores"},{"id":"1258196845","predicate":"updates.differenceTooLong","params":[{"name":"pts","type":"int"}],"type":"updates.Difference"},{"id":"791390623","predicate":"updateChannelWebPage","params":[{"name":"channel_id","type":"long"},{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1663561404","predicate":"messages.chatsSlice","params":[{"name":"count","type":"int"},{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-599948721","predicate":"textEmpty","params":[],"type":"RichText"},{"id":"1950782688","predicate":"textPlain","params":[{"name":"text","type":"string"}],"type":"RichText"},{"id":"1730456516","predicate":"textBold","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-653089380","predicate":"textItalic","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1054465340","predicate":"textUnderline","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1678197867","predicate":"textStrike","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1816074681","predicate":"textFixed","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1009288385","predicate":"textUrl","params":[{"name":"text","type":"RichText"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"}],"type":"RichText"},{"id":"-564523562","predicate":"textEmail","params":[{"name":"text","type":"RichText"},{"name":"email","type":"string"}],"type":"RichText"},{"id":"2120376535","predicate":"textConcat","params":[{"name":"texts","type":"Vector"}],"type":"RichText"},{"id":"324435594","predicate":"pageBlockUnsupported","params":[],"type":"PageBlock"},{"id":"1890305021","predicate":"pageBlockTitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1879401953","predicate":"pageBlockSubtitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1162877472","predicate":"pageBlockAuthorDate","params":[{"name":"author","type":"RichText"},{"name":"published_date","type":"int"}],"type":"PageBlock"},{"id":"-1076861716","predicate":"pageBlockHeader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-248793375","predicate":"pageBlockSubheader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"1182402406","predicate":"pageBlockParagraph","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1066346178","predicate":"pageBlockPreformatted","params":[{"name":"text","type":"RichText"},{"name":"language","type":"string"}],"type":"PageBlock"},{"id":"1216809369","predicate":"pageBlockFooter","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-618614392","predicate":"pageBlockDivider","params":[],"type":"PageBlock"},{"id":"-837994576","predicate":"pageBlockAnchor","params":[{"name":"name","type":"string"}],"type":"PageBlock"},{"id":"-454524911","predicate":"pageBlockList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"641563686","predicate":"pageBlockBlockquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"1329878739","predicate":"pageBlockPullquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"391759200","predicate":"pageBlockPhoto","params":[{"name":"flags","type":"#"},{"name":"photo_id","type":"long"},{"name":"caption","type":"PageCaption"},{"name":"url","type":"flags.0?string"},{"name":"webpage_id","type":"flags.0?long"}],"type":"PageBlock"},{"id":"2089805750","predicate":"pageBlockVideo","params":[{"name":"flags","type":"#"},{"name":"autoplay","type":"flags.0?true"},{"name":"loop","type":"flags.1?true"},{"name":"video_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"972174080","predicate":"pageBlockCover","params":[{"name":"cover","type":"PageBlock"}],"type":"PageBlock"},{"id":"-1468953147","predicate":"pageBlockEmbed","params":[{"name":"flags","type":"#"},{"name":"full_width","type":"flags.0?true"},{"name":"allow_scrolling","type":"flags.3?true"},{"name":"url","type":"flags.1?string"},{"name":"html","type":"flags.2?string"},{"name":"poster_photo_id","type":"flags.4?long"},{"name":"w","type":"flags.5?int"},{"name":"h","type":"flags.5?int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-229005301","predicate":"pageBlockEmbedPost","params":[{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"author_photo_id","type":"long"},{"name":"author","type":"string"},{"name":"date","type":"int"},{"name":"blocks","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1705048653","predicate":"pageBlockCollage","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"52401552","predicate":"pageBlockSlideshow","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1930545681","predicate":"webPageNotModified","params":[{"name":"flags","type":"#"},{"name":"cached_page_views","type":"flags.0?int"}],"type":"WebPage"},{"id":"-88417185","predicate":"inputPrivacyKeyPhoneCall","params":[],"type":"InputPrivacyKey"},{"id":"1030105979","predicate":"privacyKeyPhoneCall","params":[],"type":"PrivacyKey"},{"id":"-580219064","predicate":"sendMessageGamePlayAction","params":[],"type":"SendMessageAction"},{"id":"-2048646399","predicate":"phoneCallDiscardReasonMissed","params":[],"type":"PhoneCallDiscardReason"},{"id":"-527056480","predicate":"phoneCallDiscardReasonDisconnect","params":[],"type":"PhoneCallDiscardReason"},{"id":"1471006352","predicate":"phoneCallDiscardReasonHangup","params":[],"type":"PhoneCallDiscardReason"},{"id":"-84416311","predicate":"phoneCallDiscardReasonBusy","params":[],"type":"PhoneCallDiscardReason"},{"id":"1852826908","predicate":"updateDialogPinned","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-99664734","predicate":"updatePinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.1?int"},{"name":"order","type":"flags.0?Vector"}],"type":"Update"},{"id":"2104790276","predicate":"dataJSON","params":[{"name":"data","type":"string"}],"type":"DataJSON"},{"id":"-2095595325","predicate":"updateBotWebhookJSON","params":[{"name":"data","type":"DataJSON"}],"type":"Update"},{"id":"-1684914010","predicate":"updateBotWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"},{"name":"timeout","type":"int"}],"type":"Update"},{"id":"-886477832","predicate":"labeledPrice","params":[{"name":"label","type":"string"},{"name":"amount","type":"long"}],"type":"LabeledPrice"},{"id":"215516896","predicate":"invoice","params":[{"name":"flags","type":"#"},{"name":"test","type":"flags.0?true"},{"name":"name_requested","type":"flags.1?true"},{"name":"phone_requested","type":"flags.2?true"},{"name":"email_requested","type":"flags.3?true"},{"name":"shipping_address_requested","type":"flags.4?true"},{"name":"flexible","type":"flags.5?true"},{"name":"phone_to_provider","type":"flags.6?true"},{"name":"email_to_provider","type":"flags.7?true"},{"name":"currency","type":"string"},{"name":"prices","type":"Vector"},{"name":"max_tip_amount","type":"flags.8?long"},{"name":"suggested_tip_amounts","type":"flags.8?Vector"}],"type":"Invoice"},{"id":"-646342540","predicate":"inputMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"start_param","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-368917890","predicate":"paymentCharge","params":[{"name":"id","type":"string"},{"name":"provider_charge_id","type":"string"}],"type":"PaymentCharge"},{"id":"-1892568281","predicate":"messageActionPaymentSentMe","params":[{"name":"flags","type":"#"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"charge","type":"PaymentCharge"}],"type":"MessageAction"},{"id":"-2074799289","predicate":"messageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"receipt_msg_id","type":"flags.2?int"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"start_param","type":"string"}],"type":"MessageMedia"},{"id":"512535275","predicate":"postAddress","params":[{"name":"street_line1","type":"string"},{"name":"street_line2","type":"string"},{"name":"city","type":"string"},{"name":"state","type":"string"},{"name":"country_iso2","type":"string"},{"name":"post_code","type":"string"}],"type":"PostAddress"},{"id":"-1868808300","predicate":"paymentRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"name","type":"flags.0?string"},{"name":"phone","type":"flags.1?string"},{"name":"email","type":"flags.2?string"},{"name":"shipping_address","type":"flags.3?PostAddress"}],"type":"PaymentRequestedInfo"},{"id":"-1344716869","predicate":"keyboardButtonBuy","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1080663248","predicate":"messageActionPaymentSent","params":[{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"MessageAction"},{"id":"-842892769","predicate":"paymentSavedCredentialsCard","params":[{"name":"id","type":"string"},{"name":"title","type":"string"}],"type":"PaymentSavedCredentials"},{"id":"475467473","predicate":"webDocument","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"-1678949555","predicate":"inputWebDocument","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"InputWebDocument"},{"id":"-1036396922","predicate":"inputWebFileLocation","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"}],"type":"InputWebFileLocation"},{"id":"568808380","predicate":"upload.webFile","params":[{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"file_type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.WebFile"},{"id":"378828315","predicate":"payments.paymentForm","params":[{"name":"flags","type":"#"},{"name":"can_save_credentials","type":"flags.2?true"},{"name":"password_missing","type":"flags.3?true"},{"name":"form_id","type":"long"},{"name":"bot_id","type":"long"},{"name":"invoice","type":"Invoice"},{"name":"provider_id","type":"long"},{"name":"url","type":"string"},{"name":"native_provider","type":"flags.4?string"},{"name":"native_params","type":"flags.4?DataJSON"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"},{"name":"saved_credentials","type":"flags.1?PaymentSavedCredentials"},{"name":"users","type":"Vector"}],"type":"payments.PaymentForm"},{"id":"-784000893","predicate":"payments.validatedRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"id","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"payments.ValidatedRequestedInfo"},{"id":"1314881805","predicate":"payments.paymentResult","params":[{"name":"updates","type":"Updates"}],"type":"payments.PaymentResult"},{"id":"1891958275","predicate":"payments.paymentReceipt","params":[{"name":"flags","type":"#"},{"name":"date","type":"int"},{"name":"bot_id","type":"long"},{"name":"provider_id","type":"long"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.2?WebDocument"},{"name":"invoice","type":"Invoice"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping","type":"flags.1?ShippingOption"},{"name":"tip_amount","type":"flags.3?long"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"credentials_title","type":"string"},{"name":"users","type":"Vector"}],"type":"payments.PaymentReceipt"},{"id":"-74456004","predicate":"payments.savedInfo","params":[{"name":"flags","type":"#"},{"name":"has_saved_credentials","type":"flags.1?true"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"}],"type":"payments.SavedInfo"},{"id":"-1056001329","predicate":"inputPaymentCredentialsSaved","params":[{"name":"id","type":"string"},{"name":"tmp_password","type":"bytes"}],"type":"InputPaymentCredentials"},{"id":"873977640","predicate":"inputPaymentCredentials","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-614138572","predicate":"account.tmpPassword","params":[{"name":"tmp_password","type":"bytes"},{"name":"valid_until","type":"int"}],"type":"account.TmpPassword"},{"id":"-1239335713","predicate":"shippingOption","params":[{"name":"id","type":"string"},{"name":"title","type":"string"},{"name":"prices","type":"Vector"}],"type":"ShippingOption"},{"id":"-1246823043","predicate":"updateBotShippingQuery","params":[{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"shipping_address","type":"PostAddress"}],"type":"Update"},{"id":"-1934976362","predicate":"updateBotPrecheckoutQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"Update"},{"id":"-6249322","predicate":"inputStickerSetItem","params":[{"name":"flags","type":"#"},{"name":"document","type":"InputDocument"},{"name":"emoji","type":"string"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"InputStickerSetItem"},{"id":"-1425052898","predicate":"updatePhoneCall","params":[{"name":"phone_call","type":"PhoneCall"}],"type":"Update"},{"id":"506920429","predicate":"inputPhoneCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPhoneCall"},{"id":"1399245077","predicate":"phoneCallEmpty","params":[{"name":"id","type":"long"}],"type":"PhoneCall"},{"id":"-987599081","predicate":"phoneCallWaiting","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"receive_date","type":"flags.0?int"}],"type":"PhoneCall"},{"id":"347139340","predicate":"phoneCallRequested","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"912311057","predicate":"phoneCallAccepted","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"-1770029977","predicate":"phoneCall","params":[{"name":"flags","type":"#"},{"name":"p2p_allowed","type":"flags.5?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"connections","type":"Vector"},{"name":"start_date","type":"int"}],"type":"PhoneCall"},{"id":"1355435489","predicate":"phoneCallDiscarded","params":[{"name":"flags","type":"#"},{"name":"need_rating","type":"flags.2?true"},{"name":"need_debug","type":"flags.3?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"PhoneCall"},{"id":"-1655957568","predicate":"phoneConnection","params":[{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"peer_tag","type":"bytes"}],"type":"PhoneConnection"},{"id":"-58224696","predicate":"phoneCallProtocol","params":[{"name":"flags","type":"#"},{"name":"udp_p2p","type":"flags.0?true"},{"name":"udp_reflector","type":"flags.1?true"},{"name":"min_layer","type":"int"},{"name":"max_layer","type":"int"},{"name":"library_versions","type":"Vector"}],"type":"PhoneCallProtocol"},{"id":"-326966976","predicate":"phone.phoneCall","params":[{"name":"phone_call","type":"PhoneCall"},{"name":"users","type":"Vector"}],"type":"phone.PhoneCall"},{"id":"-2134272152","predicate":"inputMessagesFilterPhoneCalls","params":[{"name":"flags","type":"#"},{"name":"missed","type":"flags.0?true"}],"type":"MessagesFilter"},{"id":"-2132731265","predicate":"messageActionPhoneCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.2?true"},{"name":"call_id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"MessageAction"},{"id":"2054952868","predicate":"inputMessagesFilterRoundVoice","params":[],"type":"MessagesFilter"},{"id":"-1253451181","predicate":"inputMessagesFilterRoundVideo","params":[],"type":"MessagesFilter"},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction"},{"id":"608050278","predicate":"sendMessageUploadRoundAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-242427324","predicate":"upload.fileCdnRedirect","params":[{"name":"dc_id","type":"int"},{"name":"file_token","type":"bytes"},{"name":"encryption_key","type":"bytes"},{"name":"encryption_iv","type":"bytes"},{"name":"file_hashes","type":"Vector"}],"type":"upload.File"},{"id":"-290921362","predicate":"upload.cdnFileReuploadNeeded","params":[{"name":"request_token","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-1449145777","predicate":"upload.cdnFile","params":[{"name":"bytes","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-914167110","predicate":"cdnPublicKey","params":[{"name":"dc_id","type":"int"},{"name":"public_key","type":"string"}],"type":"CdnPublicKey"},{"id":"1462101002","predicate":"cdnConfig","params":[{"name":"public_keys","type":"Vector"}],"type":"CdnConfig"},{"id":"-283684427","predicate":"pageBlockChannel","params":[{"name":"channel","type":"Chat"}],"type":"PageBlock"},{"id":"-892239370","predicate":"langPackString","params":[{"name":"key","type":"string"},{"name":"value","type":"string"}],"type":"LangPackString"},{"id":"1816636575","predicate":"langPackStringPluralized","params":[{"name":"flags","type":"#"},{"name":"key","type":"string"},{"name":"zero_value","type":"flags.0?string"},{"name":"one_value","type":"flags.1?string"},{"name":"two_value","type":"flags.2?string"},{"name":"few_value","type":"flags.3?string"},{"name":"many_value","type":"flags.4?string"},{"name":"other_value","type":"string"}],"type":"LangPackString"},{"id":"695856818","predicate":"langPackStringDeleted","params":[{"name":"key","type":"string"}],"type":"LangPackString"},{"id":"-209337866","predicate":"langPackDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"strings","type":"Vector"}],"type":"LangPackDifference"},{"id":"-288727837","predicate":"langPackLanguage","params":[{"name":"flags","type":"#"},{"name":"official","type":"flags.0?true"},{"name":"rtl","type":"flags.2?true"},{"name":"beta","type":"flags.3?true"},{"name":"name","type":"string"},{"name":"native_name","type":"string"},{"name":"lang_code","type":"string"},{"name":"base_lang_code","type":"flags.1?string"},{"name":"plural_code","type":"string"},{"name":"strings_count","type":"int"},{"name":"translated_count","type":"int"},{"name":"translations_url","type":"string"}],"type":"LangPackLanguage"},{"id":"1180041828","predicate":"updateLangPackTooLong","params":[{"name":"lang_code","type":"string"}],"type":"Update"},{"id":"1442983757","predicate":"updateLangPack","params":[{"name":"difference","type":"LangPackDifference"}],"type":"Update"},{"id":"885242707","predicate":"channelParticipantAdmin","params":[{"name":"flags","type":"#"},{"name":"can_edit","type":"flags.0?true"},{"name":"self","type":"flags.1?true"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"flags.1?long"},{"name":"promoted_by","type":"long"},{"name":"date","type":"int"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.2?string"}],"type":"ChannelParticipant"},{"id":"1844969806","predicate":"channelParticipantBanned","params":[{"name":"flags","type":"#"},{"name":"left","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"kicked_by","type":"long"},{"name":"date","type":"int"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"ChannelParticipant"},{"id":"338142689","predicate":"channelParticipantsBanned","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"106343499","predicate":"channelParticipantsSearch","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-421545947","predicate":"channelAdminLogEventActionChangeTitle","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1427671598","predicate":"channelAdminLogEventActionChangeAbout","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1783299128","predicate":"channelAdminLogEventActionChangeUsername","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1129042607","predicate":"channelAdminLogEventActionChangePhoto","params":[{"name":"prev_photo","type":"Photo"},{"name":"new_photo","type":"Photo"}],"type":"ChannelAdminLogEventAction"},{"id":"460916654","predicate":"channelAdminLogEventActionToggleInvites","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"648939889","predicate":"channelAdminLogEventActionToggleSignatures","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-370660328","predicate":"channelAdminLogEventActionUpdatePinned","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1889215493","predicate":"channelAdminLogEventActionEditMessage","params":[{"name":"prev_message","type":"Message"},{"name":"new_message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1121994683","predicate":"channelAdminLogEventActionDeleteMessage","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"405815507","predicate":"channelAdminLogEventActionParticipantJoin","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-124291086","predicate":"channelAdminLogEventActionParticipantLeave","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-484690728","predicate":"channelAdminLogEventActionParticipantInvite","params":[{"name":"participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-422036098","predicate":"channelAdminLogEventActionParticipantToggleBan","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-714643696","predicate":"channelAdminLogEventActionParticipantToggleAdmin","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"531458253","predicate":"channelAdminLogEvent","params":[{"name":"id","type":"long"},{"name":"date","type":"int"},{"name":"user_id","type":"long"},{"name":"action","type":"ChannelAdminLogEventAction"}],"type":"ChannelAdminLogEvent"},{"id":"-309659827","predicate":"channels.adminLogResults","params":[{"name":"events","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.AdminLogResults"},{"id":"-368018716","predicate":"channelAdminLogEventsFilter","params":[{"name":"flags","type":"#"},{"name":"join","type":"flags.0?true"},{"name":"leave","type":"flags.1?true"},{"name":"invite","type":"flags.2?true"},{"name":"ban","type":"flags.3?true"},{"name":"unban","type":"flags.4?true"},{"name":"kick","type":"flags.5?true"},{"name":"unkick","type":"flags.6?true"},{"name":"promote","type":"flags.7?true"},{"name":"demote","type":"flags.8?true"},{"name":"info","type":"flags.9?true"},{"name":"settings","type":"flags.10?true"},{"name":"pinned","type":"flags.11?true"},{"name":"edit","type":"flags.12?true"},{"name":"delete","type":"flags.13?true"},{"name":"group_call","type":"flags.14?true"},{"name":"invites","type":"flags.15?true"},{"name":"send","type":"flags.16?true"}],"type":"ChannelAdminLogEventsFilter"},{"id":"511092620","predicate":"topPeerCategoryPhoneCalls","params":[],"type":"TopPeerCategory"},{"id":"-2143067670","predicate":"pageBlockAudio","params":[{"name":"audio_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1558266229","predicate":"popularContact","params":[{"name":"client_id","type":"long"},{"name":"importers","type":"int"}],"type":"PopularContact"},{"id":"1200788123","predicate":"messageActionScreenshotTaken","params":[],"type":"MessageAction"},{"id":"-1634752813","predicate":"messages.favedStickersNotModified","params":[],"type":"messages.FavedStickers"},{"id":"750063767","predicate":"messages.favedStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"}],"type":"messages.FavedStickers"},{"id":"-451831443","predicate":"updateFavedStickers","params":[],"type":"Update"},{"id":"1153291573","predicate":"updateChannelReadMessagesContents","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-1040652646","predicate":"inputMessagesFilterMyMentions","params":[],"type":"MessagesFilter"},{"id":"1887741886","predicate":"updateContactsReset","params":[],"type":"Update"},{"id":"-1312568665","predicate":"channelAdminLogEventActionChangeStickerSet","params":[{"name":"prev_stickerset","type":"InputStickerSet"},{"name":"new_stickerset","type":"InputStickerSet"}],"type":"ChannelAdminLogEventAction"},{"id":"-85549226","predicate":"messageActionCustomAction","params":[{"name":"message","type":"string"}],"type":"MessageAction"},{"id":"178373535","predicate":"inputPaymentCredentialsApplePay","params":[{"name":"payment_data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-419271411","predicate":"inputMessagesFilterGeo","params":[],"type":"MessagesFilter"},{"id":"-530392189","predicate":"inputMessagesFilterContacts","params":[],"type":"MessagesFilter"},{"id":"-1304443240","predicate":"updateChannelAvailableMessages","params":[{"name":"channel_id","type":"long"},{"name":"available_min_id","type":"int"}],"type":"Update"},{"id":"1599903217","predicate":"channelAdminLogEventActionTogglePreHistoryHidden","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1759532989","predicate":"inputMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"stopped","type":"flags.0?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.2?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"}],"type":"InputMedia"},{"id":"-1186937242","predicate":"messageMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"int"},{"name":"proximity_notification_radius","type":"flags.1?int"}],"type":"MessageMedia"},{"id":"1189204285","predicate":"recentMeUrlUnknown","params":[{"name":"url","type":"string"}],"type":"RecentMeUrl"},{"id":"-1188296222","predicate":"recentMeUrlUser","params":[{"name":"url","type":"string"},{"name":"user_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-1294306862","predicate":"recentMeUrlChat","params":[{"name":"url","type":"string"},{"name":"chat_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-347535331","predicate":"recentMeUrlChatInvite","params":[{"name":"url","type":"string"},{"name":"chat_invite","type":"ChatInvite"}],"type":"RecentMeUrl"},{"id":"-1140172836","predicate":"recentMeUrlStickerSet","params":[{"name":"url","type":"string"},{"name":"set","type":"StickerSetCovered"}],"type":"RecentMeUrl"},{"id":"235081943","predicate":"help.recentMeUrls","params":[{"name":"urls","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"help.RecentMeUrls"},{"id":"-266911767","predicate":"channels.channelParticipantsNotModified","params":[],"type":"channels.ChannelParticipants"},{"id":"1951620897","predicate":"messages.messagesNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Messages"},{"id":"482797855","predicate":"inputSingleMedia","params":[{"name":"flags","type":"#"},{"name":"media","type":"InputMedia"},{"name":"random_id","type":"long"},{"name":"message","type":"string"},{"name":"entities","type":"flags.0?Vector"}],"type":"InputSingleMedia"},{"id":"-1493633966","predicate":"webAuthorization","params":[{"name":"hash","type":"long"},{"name":"bot_id","type":"long"},{"name":"domain","type":"string"},{"name":"browser","type":"string"},{"name":"platform","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"region","type":"string"}],"type":"WebAuthorization"},{"id":"-313079300","predicate":"account.webAuthorizations","params":[{"name":"authorizations","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.WebAuthorizations"},{"id":"-1502174430","predicate":"inputMessageID","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-1160215659","predicate":"inputMessageReplyTo","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-2037963464","predicate":"inputMessagePinned","params":[],"type":"InputMessage"},{"id":"-1687559349","predicate":"messageEntityPhone","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1280209983","predicate":"messageEntityCashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1410748418","predicate":"messageActionBotAllowed","params":[{"name":"domain","type":"string"}],"type":"MessageAction"},{"id":"-55902537","predicate":"inputDialogPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputDialogPeer"},{"id":"-445792507","predicate":"dialogPeer","params":[{"name":"peer","type":"Peer"}],"type":"DialogPeer"},{"id":"223655517","predicate":"messages.foundStickerSetsNotModified","params":[],"type":"messages.FoundStickerSets"},{"id":"-1963942446","predicate":"messages.foundStickerSets","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.FoundStickerSets"},{"id":"1648543603","predicate":"fileHash","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"bytes"}],"type":"FileHash"},{"id":"-104284986","predicate":"webDocumentNoProxy","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"1968737087","predicate":"inputClientProxy","params":[{"name":"address","type":"string"},{"name":"port","type":"int"}],"type":"InputClientProxy"},{"id":"-483352705","predicate":"help.termsOfServiceUpdateEmpty","params":[{"name":"expires","type":"int"}],"type":"help.TermsOfServiceUpdate"},{"id":"686618977","predicate":"help.termsOfServiceUpdate","params":[{"name":"expires","type":"int"},{"name":"terms_of_service","type":"help.TermsOfService"}],"type":"help.TermsOfServiceUpdate"},{"id":"859091184","predicate":"inputSecureFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"InputSecureFile"},{"id":"1399317950","predicate":"inputSecureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputSecureFile"},{"id":"-876089816","predicate":"inputSecureFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"1679398724","predicate":"secureFileEmpty","params":[],"type":"SecureFile"},{"id":"-534283678","predicate":"secureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"date","type":"int"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureFile"},{"id":"-1964327229","predicate":"secureData","params":[{"name":"data","type":"bytes"},{"name":"data_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureData"},{"id":"2103482845","predicate":"securePlainPhone","params":[{"name":"phone","type":"string"}],"type":"SecurePlainData"},{"id":"569137759","predicate":"securePlainEmail","params":[{"name":"email","type":"string"}],"type":"SecurePlainData"},{"id":"-1658158621","predicate":"secureValueTypePersonalDetails","params":[],"type":"SecureValueType"},{"id":"1034709504","predicate":"secureValueTypePassport","params":[],"type":"SecureValueType"},{"id":"115615172","predicate":"secureValueTypeDriverLicense","params":[],"type":"SecureValueType"},{"id":"-1596951477","predicate":"secureValueTypeIdentityCard","params":[],"type":"SecureValueType"},{"id":"-1717268701","predicate":"secureValueTypeInternalPassport","params":[],"type":"SecureValueType"},{"id":"-874308058","predicate":"secureValueTypeAddress","params":[],"type":"SecureValueType"},{"id":"-63531698","predicate":"secureValueTypeUtilityBill","params":[],"type":"SecureValueType"},{"id":"-1995211763","predicate":"secureValueTypeBankStatement","params":[],"type":"SecureValueType"},{"id":"-1954007928","predicate":"secureValueTypeRentalAgreement","params":[],"type":"SecureValueType"},{"id":"-1713143702","predicate":"secureValueTypePassportRegistration","params":[],"type":"SecureValueType"},{"id":"-368907213","predicate":"secureValueTypeTemporaryRegistration","params":[],"type":"SecureValueType"},{"id":"-1289704741","predicate":"secureValueTypePhone","params":[],"type":"SecureValueType"},{"id":"-1908627474","predicate":"secureValueTypeEmail","params":[],"type":"SecureValueType"},{"id":"411017418","predicate":"secureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?SecureFile"},{"name":"reverse_side","type":"flags.2?SecureFile"},{"name":"selfie","type":"flags.3?SecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"},{"name":"hash","type":"bytes"}],"type":"SecureValue"},{"id":"-618540889","predicate":"inputSecureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?InputSecureFile"},{"name":"reverse_side","type":"flags.2?InputSecureFile"},{"name":"selfie","type":"flags.3?InputSecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"}],"type":"InputSecureValue"},{"id":"-316748368","predicate":"secureValueHash","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"}],"type":"SecureValueHash"},{"id":"-391902247","predicate":"secureValueErrorData","params":[{"name":"type","type":"SecureValueType"},{"name":"data_hash","type":"bytes"},{"name":"field","type":"string"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"12467706","predicate":"secureValueErrorFrontSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2037765467","predicate":"secureValueErrorReverseSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-449327402","predicate":"secureValueErrorSelfie","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"2054162547","predicate":"secureValueErrorFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"1717706985","predicate":"secureValueErrorFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"871426631","predicate":"secureCredentialsEncrypted","params":[{"name":"data","type":"bytes"},{"name":"hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureCredentialsEncrypted"},{"id":"-1389486888","predicate":"account.authorizationForm","params":[{"name":"flags","type":"#"},{"name":"required_types","type":"Vector"},{"name":"values","type":"Vector"},{"name":"errors","type":"Vector"},{"name":"users","type":"Vector"},{"name":"privacy_policy_url","type":"flags.0?string"}],"type":"account.AuthorizationForm"},{"id":"-2128640689","predicate":"account.sentEmailCode","params":[{"name":"email_pattern","type":"string"},{"name":"length","type":"int"}],"type":"account.SentEmailCode"},{"id":"455635795","predicate":"messageActionSecureValuesSentMe","params":[{"name":"values","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"MessageAction"},{"id":"-648257196","predicate":"messageActionSecureValuesSent","params":[{"name":"types","type":"Vector"}],"type":"MessageAction"},{"id":"1722786150","predicate":"help.deepLinkInfoEmpty","params":[],"type":"help.DeepLinkInfo"},{"id":"1783556146","predicate":"help.deepLinkInfo","params":[{"name":"flags","type":"#"},{"name":"update_app","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"help.DeepLinkInfo"},{"id":"289586518","predicate":"savedPhoneContact","params":[{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"date","type":"int"}],"type":"SavedContact"},{"id":"1304052993","predicate":"account.takeout","params":[{"name":"id","type":"long"}],"type":"account.Takeout"},{"id":"700340377","predicate":"inputTakeoutFileLocation","params":[],"type":"InputFileLocation"},{"id":"-513517117","predicate":"updateDialogUnreadMark","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-253500010","predicate":"messages.dialogsNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Dialogs"},{"id":"-1625153079","predicate":"inputWebFileGeoPointLocation","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"access_hash","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"zoom","type":"int"},{"name":"scale","type":"int"}],"type":"InputWebFileLocation"},{"id":"-1255369827","predicate":"contacts.topPeersDisabled","params":[],"type":"contacts.TopPeers"},{"id":"-1685456582","predicate":"inputReportReasonCopyright","params":[],"type":"ReportReason"},{"id":"-732254058","predicate":"passwordKdfAlgoUnknown","params":[],"type":"PasswordKdfAlgo"},{"id":"4883767","predicate":"securePasswordKdfAlgoUnknown","params":[],"type":"SecurePasswordKdfAlgo"},{"id":"-1141711456","predicate":"securePasswordKdfAlgoPBKDF2HMACSHA512iter100000","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"-2042159726","predicate":"securePasswordKdfAlgoSHA512","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"354925740","predicate":"secureSecretSettings","params":[{"name":"secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_secret","type":"bytes"},{"name":"secure_secret_id","type":"long"}],"type":"SecureSecretSettings"},{"id":"982592842","predicate":"passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow","params":[{"name":"salt1","type":"bytes"},{"name":"salt2","type":"bytes"},{"name":"g","type":"int"},{"name":"p","type":"bytes"}],"type":"PasswordKdfAlgo"},{"id":"-1736378792","predicate":"inputCheckPasswordEmpty","params":[],"type":"InputCheckPasswordSRP"},{"id":"-763367294","predicate":"inputCheckPasswordSRP","params":[{"name":"srp_id","type":"long"},{"name":"A","type":"bytes"},{"name":"M1","type":"bytes"}],"type":"InputCheckPasswordSRP"},{"id":"-2036501105","predicate":"secureValueError","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-1592506512","predicate":"secureValueErrorTranslationFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"878931416","predicate":"secureValueErrorTranslationFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2103600678","predicate":"secureRequiredType","params":[{"name":"flags","type":"#"},{"name":"native_names","type":"flags.0?true"},{"name":"selfie_required","type":"flags.1?true"},{"name":"translation_required","type":"flags.2?true"},{"name":"type","type":"SecureValueType"}],"type":"SecureRequiredType"},{"id":"41187252","predicate":"secureRequiredTypeOneOf","params":[{"name":"types","type":"Vector"}],"type":"SecureRequiredType"},{"id":"-1078332329","predicate":"help.passportConfigNotModified","params":[],"type":"help.PassportConfig"},{"id":"-1600596305","predicate":"help.passportConfig","params":[{"name":"hash","type":"int"},{"name":"countries_langs","type":"DataJSON"}],"type":"help.PassportConfig"},{"id":"488313413","predicate":"inputAppEvent","params":[{"name":"time","type":"double"},{"name":"type","type":"string"},{"name":"peer","type":"long"},{"name":"data","type":"JSONValue"}],"type":"InputAppEvent"},{"id":"-1059185703","predicate":"jsonObjectValue","params":[{"name":"key","type":"string"},{"name":"value","type":"JSONValue"}],"type":"JSONObjectValue"},{"id":"1064139624","predicate":"jsonNull","params":[],"type":"JSONValue"},{"id":"-952869270","predicate":"jsonBool","params":[{"name":"value","type":"Bool"}],"type":"JSONValue"},{"id":"736157604","predicate":"jsonNumber","params":[{"name":"value","type":"double"}],"type":"JSONValue"},{"id":"-1222740358","predicate":"jsonString","params":[{"name":"value","type":"string"}],"type":"JSONValue"},{"id":"-146520221","predicate":"jsonArray","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1715350371","predicate":"jsonObject","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1311015810","predicate":"inputNotifyBroadcasts","params":[],"type":"InputNotifyPeer"},{"id":"-703403793","predicate":"notifyBroadcasts","params":[],"type":"NotifyPeer"},{"id":"-311786236","predicate":"textSubscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-939827711","predicate":"textSuperscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"55281185","predicate":"textMarked","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"483104362","predicate":"textPhone","params":[{"name":"text","type":"RichText"},{"name":"phone","type":"string"}],"type":"RichText"},{"id":"136105807","predicate":"textImage","params":[{"name":"document_id","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"RichText"},{"id":"504660880","predicate":"pageBlockKicker","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"878078826","predicate":"pageTableCell","params":[{"name":"flags","type":"#"},{"name":"header","type":"flags.0?true"},{"name":"align_center","type":"flags.3?true"},{"name":"align_right","type":"flags.4?true"},{"name":"valign_middle","type":"flags.5?true"},{"name":"valign_bottom","type":"flags.6?true"},{"name":"text","type":"flags.7?RichText"},{"name":"colspan","type":"flags.1?int"},{"name":"rowspan","type":"flags.2?int"}],"type":"PageTableCell"},{"id":"-524237339","predicate":"pageTableRow","params":[{"name":"cells","type":"Vector"}],"type":"PageTableRow"},{"id":"-1085412734","predicate":"pageBlockTable","params":[{"name":"flags","type":"#"},{"name":"bordered","type":"flags.0?true"},{"name":"striped","type":"flags.1?true"},{"name":"title","type":"RichText"},{"name":"rows","type":"Vector"}],"type":"PageBlock"},{"id":"1869903447","predicate":"pageCaption","params":[{"name":"text","type":"RichText"},{"name":"credit","type":"RichText"}],"type":"PageCaption"},{"id":"-1188055347","predicate":"pageListItemText","params":[{"name":"text","type":"RichText"}],"type":"PageListItem"},{"id":"635466748","predicate":"pageListItemBlocks","params":[{"name":"blocks","type":"Vector"}],"type":"PageListItem"},{"id":"1577484359","predicate":"pageListOrderedItemText","params":[{"name":"num","type":"string"},{"name":"text","type":"RichText"}],"type":"PageListOrderedItem"},{"id":"-1730311882","predicate":"pageListOrderedItemBlocks","params":[{"name":"num","type":"string"},{"name":"blocks","type":"Vector"}],"type":"PageListOrderedItem"},{"id":"-1702174239","predicate":"pageBlockOrderedList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"1987480557","predicate":"pageBlockDetails","params":[{"name":"flags","type":"#"},{"name":"open","type":"flags.0?true"},{"name":"blocks","type":"Vector"},{"name":"title","type":"RichText"}],"type":"PageBlock"},{"id":"-1282352120","predicate":"pageRelatedArticle","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"title","type":"flags.0?string"},{"name":"description","type":"flags.1?string"},{"name":"photo_id","type":"flags.2?long"},{"name":"author","type":"flags.3?string"},{"name":"published_date","type":"flags.4?int"}],"type":"PageRelatedArticle"},{"id":"370236054","predicate":"pageBlockRelatedArticles","params":[{"name":"title","type":"RichText"},{"name":"articles","type":"Vector"}],"type":"PageBlock"},{"id":"-1538310410","predicate":"pageBlockMap","params":[{"name":"geo","type":"GeoPoint"},{"name":"zoom","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-1738178803","predicate":"page","params":[{"name":"flags","type":"#"},{"name":"part","type":"flags.0?true"},{"name":"rtl","type":"flags.1?true"},{"name":"v2","type":"flags.2?true"},{"name":"url","type":"string"},{"name":"blocks","type":"Vector"},{"name":"photos","type":"Vector"},{"name":"documents","type":"Vector"},{"name":"views","type":"flags.3?int"}],"type":"Page"},{"id":"-610373422","predicate":"inputPrivacyKeyPhoneP2P","params":[],"type":"InputPrivacyKey"},{"id":"961092808","predicate":"privacyKeyPhoneP2P","params":[],"type":"PrivacyKey"},{"id":"894777186","predicate":"textAnchor","params":[{"name":"text","type":"RichText"},{"name":"name","type":"string"}],"type":"RichText"},{"id":"-1945767479","predicate":"help.supportName","params":[{"name":"name","type":"string"}],"type":"help.SupportName"},{"id":"-206688531","predicate":"help.userInfoEmpty","params":[],"type":"help.UserInfo"},{"id":"32192344","predicate":"help.userInfo","params":[{"name":"message","type":"string"},{"name":"entities","type":"Vector"},{"name":"author","type":"string"},{"name":"date","type":"int"}],"type":"help.UserInfo"},{"id":"-202219658","predicate":"messageActionContactSignUp","params":[],"type":"MessageAction"},{"id":"-1398708869","predicate":"updateMessagePoll","params":[{"name":"flags","type":"#"},{"name":"poll_id","type":"long"},{"name":"poll","type":"flags.0?Poll"},{"name":"results","type":"PollResults"}],"type":"Update"},{"id":"1823064809","predicate":"pollAnswer","params":[{"name":"text","type":"string"},{"name":"option","type":"bytes"}],"type":"PollAnswer"},{"id":"-2032041631","predicate":"poll","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"closed","type":"flags.0?true"},{"name":"public_voters","type":"flags.1?true"},{"name":"multiple_choice","type":"flags.2?true"},{"name":"quiz","type":"flags.3?true"},{"name":"question","type":"string"},{"name":"answers","type":"Vector"},{"name":"close_period","type":"flags.4?int"},{"name":"close_date","type":"flags.5?int"}],"type":"Poll"},{"id":"997055186","predicate":"pollAnswerVoters","params":[{"name":"flags","type":"#"},{"name":"chosen","type":"flags.0?true"},{"name":"correct","type":"flags.1?true"},{"name":"option","type":"bytes"},{"name":"voters","type":"int"}],"type":"PollAnswerVoters"},{"id":"-591909213","predicate":"pollResults","params":[{"name":"flags","type":"#"},{"name":"min","type":"flags.0?true"},{"name":"results","type":"flags.1?Vector"},{"name":"total_voters","type":"flags.2?int"},{"name":"recent_voters","type":"flags.3?Vector"},{"name":"solution","type":"flags.4?string"},{"name":"solution_entities","type":"flags.4?Vector"}],"type":"PollResults"},{"id":"261416433","predicate":"inputMediaPoll","params":[{"name":"flags","type":"#"},{"name":"poll","type":"Poll"},{"name":"correct_answers","type":"flags.0?Vector"},{"name":"solution","type":"flags.1?string"},{"name":"solution_entities","type":"flags.1?Vector"}],"type":"InputMedia"},{"id":"1272375192","predicate":"messageMediaPoll","params":[{"name":"poll","type":"Poll"},{"name":"results","type":"PollResults"}],"type":"MessageMedia"},{"id":"-264117680","predicate":"chatOnlines","params":[{"name":"onlines","type":"int"}],"type":"ChatOnlines"},{"id":"1202287072","predicate":"statsURL","params":[{"name":"url","type":"string"}],"type":"StatsURL"},{"id":"-525288402","predicate":"photoStrippedSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"1605510357","predicate":"chatAdminRights","params":[{"name":"flags","type":"#"},{"name":"change_info","type":"flags.0?true"},{"name":"post_messages","type":"flags.1?true"},{"name":"edit_messages","type":"flags.2?true"},{"name":"delete_messages","type":"flags.3?true"},{"name":"ban_users","type":"flags.4?true"},{"name":"invite_users","type":"flags.5?true"},{"name":"pin_messages","type":"flags.7?true"},{"name":"add_admins","type":"flags.9?true"},{"name":"anonymous","type":"flags.10?true"},{"name":"manage_call","type":"flags.11?true"},{"name":"other","type":"flags.12?true"}],"type":"ChatAdminRights"},{"id":"-1626209256","predicate":"chatBannedRights","params":[{"name":"flags","type":"#"},{"name":"view_messages","type":"flags.0?true"},{"name":"send_messages","type":"flags.1?true"},{"name":"send_media","type":"flags.2?true"},{"name":"send_stickers","type":"flags.3?true"},{"name":"send_gifs","type":"flags.4?true"},{"name":"send_games","type":"flags.5?true"},{"name":"send_inline","type":"flags.6?true"},{"name":"embed_links","type":"flags.7?true"},{"name":"send_polls","type":"flags.8?true"},{"name":"change_info","type":"flags.10?true"},{"name":"invite_users","type":"flags.15?true"},{"name":"pin_messages","type":"flags.17?true"},{"name":"until_date","type":"int"}],"type":"ChatBannedRights"},{"id":"1421875280","predicate":"updateChatDefaultBannedRights","params":[{"name":"peer","type":"Peer"},{"name":"default_banned_rights","type":"ChatBannedRights"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-433014407","predicate":"inputWallPaper","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputWallPaper"},{"id":"1913199744","predicate":"inputWallPaperSlug","params":[{"name":"slug","type":"string"}],"type":"InputWallPaper"},{"id":"-1150621555","predicate":"channelParticipantsContacts","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"771095562","predicate":"channelAdminLogEventActionDefaultBannedRights","params":[{"name":"prev_banned_rights","type":"ChatBannedRights"},{"name":"new_banned_rights","type":"ChatBannedRights"}],"type":"ChannelAdminLogEventAction"},{"id":"-1895328189","predicate":"channelAdminLogEventActionStopPoll","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"471437699","predicate":"account.wallPapersNotModified","params":[],"type":"account.WallPapers"},{"id":"-842824308","predicate":"account.wallPapers","params":[{"name":"hash","type":"long"},{"name":"wallpapers","type":"Vector"}],"type":"account.WallPapers"},{"id":"-557924733","predicate":"codeSettings","params":[{"name":"flags","type":"#"},{"name":"allow_flashcall","type":"flags.0?true"},{"name":"current_number","type":"flags.1?true"},{"name":"allow_app_hash","type":"flags.4?true"}],"type":"CodeSettings"},{"id":"499236004","predicate":"wallPaperSettings","params":[{"name":"flags","type":"#"},{"name":"blur","type":"flags.1?true"},{"name":"motion","type":"flags.2?true"},{"name":"background_color","type":"flags.0?int"},{"name":"second_background_color","type":"flags.4?int"},{"name":"third_background_color","type":"flags.5?int"},{"name":"fourth_background_color","type":"flags.6?int"},{"name":"intensity","type":"flags.3?int"},{"name":"rotation","type":"flags.4?int"}],"type":"WallPaperSettings"},{"id":"-532532493","predicate":"autoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"disabled","type":"flags.0?true"},{"name":"video_preload_large","type":"flags.1?true"},{"name":"audio_preload_next","type":"flags.2?true"},{"name":"phonecalls_less_data","type":"flags.3?true"},{"name":"photo_size_max","type":"int"},{"name":"video_size_max","type":"int"},{"name":"file_size_max","type":"int"},{"name":"video_upload_maxbitrate","type":"int"}],"type":"AutoDownloadSettings"},{"id":"1674235686","predicate":"account.autoDownloadSettings","params":[{"name":"low","type":"AutoDownloadSettings"},{"name":"medium","type":"AutoDownloadSettings"},{"name":"high","type":"AutoDownloadSettings"}],"type":"account.AutoDownloadSettings"},{"id":"-709641735","predicate":"emojiKeyword","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"594408994","predicate":"emojiKeywordDeleted","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"1556570557","predicate":"emojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"keywords","type":"Vector"}],"type":"EmojiKeywordsDifference"},{"id":"-1519029347","predicate":"emojiURL","params":[{"name":"url","type":"string"}],"type":"EmojiURL"},{"id":"-1275374751","predicate":"emojiLanguage","params":[{"name":"lang_code","type":"string"}],"type":"EmojiLanguage"},{"id":"-1529000952","predicate":"inputPrivacyKeyForwards","params":[],"type":"InputPrivacyKey"},{"id":"1777096355","predicate":"privacyKeyForwards","params":[],"type":"PrivacyKey"},{"id":"1461304012","predicate":"inputPrivacyKeyProfilePhoto","params":[],"type":"InputPrivacyKey"},{"id":"-1777000467","predicate":"privacyKeyProfilePhoto","params":[],"type":"PrivacyKey"},{"id":"1075322878","predicate":"inputPhotoFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"-667654413","predicate":"inputPhotoLegacyFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"InputFileLocation"},{"id":"925204121","predicate":"inputPeerPhotoFileLocation","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"long"}],"type":"InputFileLocation"},{"id":"-1652231205","predicate":"inputStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb_version","type":"int"}],"type":"InputFileLocation"},{"id":"-11252123","predicate":"folder","params":[{"name":"flags","type":"#"},{"name":"autofill_new_broadcasts","type":"flags.0?true"},{"name":"autofill_public_groups","type":"flags.1?true"},{"name":"autofill_new_correspondents","type":"flags.2?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"photo","type":"flags.3?ChatPhoto"}],"type":"Folder"},{"id":"1908216652","predicate":"dialogFolder","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"folder","type":"Folder"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"unread_muted_peers_count","type":"int"},{"name":"unread_unmuted_peers_count","type":"int"},{"name":"unread_muted_messages_count","type":"int"},{"name":"unread_unmuted_messages_count","type":"int"}],"type":"Dialog"},{"id":"1684014375","predicate":"inputDialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"InputDialogPeer"},{"id":"1363483106","predicate":"dialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"DialogPeer"},{"id":"-70073706","predicate":"inputFolderPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"folder_id","type":"int"}],"type":"InputFolderPeer"},{"id":"-373643672","predicate":"folderPeer","params":[{"name":"peer","type":"Peer"},{"name":"folder_id","type":"int"}],"type":"FolderPeer"},{"id":"422972864","predicate":"updateFolderPeers","params":[{"name":"folder_peers","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"497305826","predicate":"inputUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputUser"},{"id":"1536380829","predicate":"inputChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputChannel"},{"id":"-1468331492","predicate":"inputPeerUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputPeer"},{"id":"-1121318848","predicate":"inputPeerChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputPeer"},{"id":"55761658","predicate":"inputPrivacyKeyPhoneNumber","params":[],"type":"InputPrivacyKey"},{"id":"-778378131","predicate":"privacyKeyPhoneNumber","params":[],"type":"PrivacyKey"},{"id":"-1472172887","predicate":"topPeerCategoryForwardUsers","params":[],"type":"TopPeerCategory"},{"id":"-68239120","predicate":"topPeerCategoryForwardChats","params":[],"type":"TopPeerCategory"},{"id":"84703944","predicate":"channelAdminLogEventActionChangeLinkedChat","params":[{"name":"prev_value","type":"long"},{"name":"new_value","type":"long"}],"type":"ChannelAdminLogEventAction"},{"id":"-398136321","predicate":"messages.searchCounter","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"filter","type":"MessagesFilter"},{"name":"count","type":"int"}],"type":"messages.SearchCounter"},{"id":"280464681","predicate":"keyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.0?string"},{"name":"url","type":"string"},{"name":"button_id","type":"int"}],"type":"KeyboardButton"},{"id":"-802258988","predicate":"inputKeyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.1?string"},{"name":"url","type":"string"},{"name":"bot","type":"InputUser"}],"type":"KeyboardButton"},{"id":"-1831650802","predicate":"urlAuthResultRequest","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"bot","type":"User"},{"name":"domain","type":"string"}],"type":"UrlAuthResult"},{"id":"-1886646706","predicate":"urlAuthResultAccepted","params":[{"name":"url","type":"string"}],"type":"UrlAuthResult"},{"id":"-1445536993","predicate":"urlAuthResultDefault","params":[],"type":"UrlAuthResult"},{"id":"-2079962673","predicate":"inputPrivacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-380694650","predicate":"inputPrivacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"1796427406","predicate":"privacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"1103656293","predicate":"privacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"-1672577397","predicate":"messageEntityUnderline","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1090087980","predicate":"messageEntityStrike","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"34469328","predicate":"messageEntityBlockquote","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1786671974","predicate":"updatePeerSettings","params":[{"name":"peer","type":"Peer"},{"name":"settings","type":"PeerSettings"}],"type":"Update"},{"id":"-1078612597","predicate":"channelLocationEmpty","params":[],"type":"ChannelLocation"},{"id":"547062491","predicate":"channelLocation","params":[{"name":"geo_point","type":"GeoPoint"},{"name":"address","type":"string"}],"type":"ChannelLocation"},{"id":"-901375139","predicate":"peerLocated","params":[{"name":"peer","type":"Peer"},{"name":"expires","type":"int"},{"name":"distance","type":"int"}],"type":"PeerLocated"},{"id":"-1263546448","predicate":"updatePeerLocated","params":[{"name":"peers","type":"Vector"}],"type":"Update"},{"id":"241923758","predicate":"channelAdminLogEventActionChangeLocation","params":[{"name":"prev_value","type":"ChannelLocation"},{"name":"new_value","type":"ChannelLocation"}],"type":"ChannelAdminLogEventAction"},{"id":"-606798099","predicate":"inputReportReasonGeoIrrelevant","params":[],"type":"ReportReason"},{"id":"1401984889","predicate":"channelAdminLogEventActionToggleSlowMode","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"1148485274","predicate":"auth.authorizationSignUpRequired","params":[{"name":"flags","type":"#"},{"name":"terms_of_service","type":"flags.0?help.TermsOfService"}],"type":"auth.Authorization"},{"id":"-666824391","predicate":"payments.paymentVerificationNeeded","params":[{"name":"url","type":"string"}],"type":"payments.PaymentResult"},{"id":"42402760","predicate":"inputStickerSetAnimatedEmoji","params":[],"type":"InputStickerSet"},{"id":"967122427","predicate":"updateNewScheduledMessage","params":[{"name":"message","type":"Message"}],"type":"Update"},{"id":"-1870238482","predicate":"updateDeleteScheduledMessages","params":[{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-797791052","predicate":"restrictionReason","params":[{"name":"platform","type":"string"},{"name":"reason","type":"string"},{"name":"text","type":"string"}],"type":"RestrictionReason"},{"id":"1012306921","predicate":"inputTheme","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputTheme"},{"id":"-175567375","predicate":"inputThemeSlug","params":[{"name":"slug","type":"string"}],"type":"InputTheme"},{"id":"-402474788","predicate":"theme","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"for_chat","type":"flags.5?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?Document"},{"name":"settings","type":"flags.3?ThemeSettings"},{"name":"installs_count","type":"flags.4?int"}],"type":"Theme"},{"id":"-199313886","predicate":"account.themesNotModified","params":[],"type":"account.Themes"},{"id":"-1707242387","predicate":"account.themes","params":[{"name":"hash","type":"long"},{"name":"themes","type":"Vector"}],"type":"account.Themes"},{"id":"-2112423005","predicate":"updateTheme","params":[{"name":"theme","type":"Theme"}],"type":"Update"},{"id":"-786326563","predicate":"inputPrivacyKeyAddedByPhone","params":[],"type":"InputPrivacyKey"},{"id":"1124062251","predicate":"privacyKeyAddedByPhone","params":[],"type":"PrivacyKey"},{"id":"-2027964103","predicate":"updateGeoLiveViewed","params":[{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"}],"type":"Update"},{"id":"1448076945","predicate":"updateLoginToken","params":[],"type":"Update"},{"id":"1654593920","predicate":"auth.loginToken","params":[{"name":"expires","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"110008598","predicate":"auth.loginTokenMigrateTo","params":[{"name":"dc_id","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"957176926","predicate":"auth.loginTokenSuccess","params":[{"name":"authorization","type":"auth.Authorization"}],"type":"auth.LoginToken"},{"id":"1474462241","predicate":"account.contentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"},{"name":"sensitive_can_change","type":"flags.1?true"}],"type":"account.ContentSettings"},{"id":"-1456996667","predicate":"messages.inactiveChats","params":[{"name":"dates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.InactiveChats"},{"id":"-1012849566","predicate":"baseThemeClassic","params":[],"type":"BaseTheme"},{"id":"-69724536","predicate":"baseThemeDay","params":[],"type":"BaseTheme"},{"id":"-1212997976","predicate":"baseThemeNight","params":[],"type":"BaseTheme"},{"id":"1834973166","predicate":"baseThemeTinted","params":[],"type":"BaseTheme"},{"id":"1527845466","predicate":"baseThemeArctic","params":[],"type":"BaseTheme"},{"id":"-1770371538","predicate":"inputWallPaperNoFile","params":[{"name":"id","type":"long"}],"type":"InputWallPaper"},{"id":"-528465642","predicate":"wallPaperNoFile","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"default","type":"flags.1?true"},{"name":"dark","type":"flags.4?true"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"-1881255857","predicate":"inputThemeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?InputWallPaper"},{"name":"wallpaper_settings","type":"flags.1?WallPaperSettings"}],"type":"InputThemeSettings"},{"id":"-94849324","predicate":"themeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?WallPaper"}],"type":"ThemeSettings"},{"id":"1421174295","predicate":"webPageAttributeTheme","params":[{"name":"flags","type":"#"},{"name":"documents","type":"flags.0?Vector"},{"name":"settings","type":"flags.1?ThemeSettings"}],"type":"WebPageAttribute"},{"id":"274961865","predicate":"updateMessagePollVote","params":[{"name":"poll_id","type":"long"},{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"886196148","predicate":"messageUserVote","params":[{"name":"user_id","type":"long"},{"name":"option","type":"bytes"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"1017491692","predicate":"messageUserVoteInputOption","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"-1973033641","predicate":"messageUserVoteMultiple","params":[{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"136574537","predicate":"messages.votesList","params":[{"name":"flags","type":"#"},{"name":"count","type":"int"},{"name":"votes","type":"Vector"},{"name":"users","type":"Vector"},{"name":"next_offset","type":"flags.0?string"}],"type":"messages.VotesList"},{"id":"-1144565411","predicate":"keyboardButtonRequestPoll","params":[{"name":"flags","type":"#"},{"name":"quiz","type":"flags.0?Bool"},{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1981704948","predicate":"messageEntityBankCard","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-177732982","predicate":"bankCardOpenUrl","params":[{"name":"url","type":"string"},{"name":"name","type":"string"}],"type":"BankCardOpenUrl"},{"id":"1042605427","predicate":"payments.bankCardData","params":[{"name":"title","type":"string"},{"name":"open_urls","type":"Vector"}],"type":"payments.BankCardData"},{"id":"-118740917","predicate":"peerSelfLocated","params":[{"name":"expires","type":"int"}],"type":"PeerLocated"},{"id":"1949890536","predicate":"dialogFilter","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"non_contacts","type":"flags.1?true"},{"name":"groups","type":"flags.2?true"},{"name":"broadcasts","type":"flags.3?true"},{"name":"bots","type":"flags.4?true"},{"name":"exclude_muted","type":"flags.11?true"},{"name":"exclude_read","type":"flags.12?true"},{"name":"exclude_archived","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"emoticon","type":"flags.25?string"},{"name":"pinned_peers","type":"Vector"},{"name":"include_peers","type":"Vector"},{"name":"exclude_peers","type":"Vector"}],"type":"DialogFilter"},{"id":"2004110666","predicate":"dialogFilterSuggested","params":[{"name":"filter","type":"DialogFilter"},{"name":"description","type":"string"}],"type":"DialogFilterSuggested"},{"id":"654302845","predicate":"updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Update"},{"id":"-1512627963","predicate":"updateDialogFilterOrder","params":[{"name":"order","type":"Vector"}],"type":"Update"},{"id":"889491791","predicate":"updateDialogFilters","params":[],"type":"Update"},{"id":"-1237848657","predicate":"statsDateRangeDays","params":[{"name":"min_date","type":"int"},{"name":"max_date","type":"int"}],"type":"StatsDateRangeDays"},{"id":"-884757282","predicate":"statsAbsValueAndPrev","params":[{"name":"current","type":"double"},{"name":"previous","type":"double"}],"type":"StatsAbsValueAndPrev"},{"id":"-875679776","predicate":"statsPercentValue","params":[{"name":"part","type":"double"},{"name":"total","type":"double"}],"type":"StatsPercentValue"},{"id":"1244130093","predicate":"statsGraphAsync","params":[{"name":"token","type":"string"}],"type":"StatsGraph"},{"id":"-1092839390","predicate":"statsGraphError","params":[{"name":"error","type":"string"}],"type":"StatsGraph"},{"id":"-1901828938","predicate":"statsGraph","params":[{"name":"flags","type":"#"},{"name":"json","type":"DataJSON"},{"name":"zoom_token","type":"flags.0?string"}],"type":"StatsGraph"},{"id":"-1387279939","predicate":"messageInteractionCounters","params":[{"name":"msg_id","type":"int"},{"name":"views","type":"int"},{"name":"forwards","type":"int"}],"type":"MessageInteractionCounters"},{"id":"-1107852396","predicate":"stats.broadcastStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"followers","type":"StatsAbsValueAndPrev"},{"name":"views_per_post","type":"StatsAbsValueAndPrev"},{"name":"shares_per_post","type":"StatsAbsValueAndPrev"},{"name":"enabled_notifications","type":"StatsPercentValue"},{"name":"growth_graph","type":"StatsGraph"},{"name":"followers_graph","type":"StatsGraph"},{"name":"mute_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"interactions_graph","type":"StatsGraph"},{"name":"iv_interactions_graph","type":"StatsGraph"},{"name":"views_by_source_graph","type":"StatsGraph"},{"name":"new_followers_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"recent_message_interactions","type":"Vector"}],"type":"stats.BroadcastStats"},{"id":"-428884101","predicate":"inputMediaDice","params":[{"name":"emoticon","type":"string"}],"type":"InputMedia"},{"id":"1065280907","predicate":"messageMediaDice","params":[{"name":"value","type":"int"},{"name":"emoticon","type":"string"}],"type":"MessageMedia"},{"id":"-427863538","predicate":"inputStickerSetDice","params":[{"name":"emoticon","type":"string"}],"type":"InputStickerSet"},{"id":"-1728664459","predicate":"help.promoDataEmpty","params":[{"name":"expires","type":"int"}],"type":"help.PromoData"},{"id":"-1942390465","predicate":"help.promoData","params":[{"name":"flags","type":"#"},{"name":"proxy","type":"flags.0?true"},{"name":"expires","type":"int"},{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"psa_type","type":"flags.1?string"},{"name":"psa_message","type":"flags.2?string"}],"type":"help.PromoData"},{"id":"-567037804","predicate":"videoSize","params":[{"name":"flags","type":"#"},{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"video_start_ts","type":"flags.0?double"}],"type":"VideoSize"},{"id":"643940105","predicate":"updatePhoneCallSignalingData","params":[{"name":"phone_call_id","type":"long"},{"name":"data","type":"bytes"}],"type":"Update"},{"id":"1634294960","predicate":"chatInvitePeek","params":[{"name":"chat","type":"Chat"},{"name":"expires","type":"int"}],"type":"ChatInvite"},{"id":"-1660637285","predicate":"statsGroupTopPoster","params":[{"name":"user_id","type":"long"},{"name":"messages","type":"int"},{"name":"avg_chars","type":"int"}],"type":"StatsGroupTopPoster"},{"id":"-682079097","predicate":"statsGroupTopAdmin","params":[{"name":"user_id","type":"long"},{"name":"deleted","type":"int"},{"name":"kicked","type":"int"},{"name":"banned","type":"int"}],"type":"StatsGroupTopAdmin"},{"id":"1398765469","predicate":"statsGroupTopInviter","params":[{"name":"user_id","type":"long"},{"name":"invitations","type":"int"}],"type":"StatsGroupTopInviter"},{"id":"-276825834","predicate":"stats.megagroupStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"members","type":"StatsAbsValueAndPrev"},{"name":"messages","type":"StatsAbsValueAndPrev"},{"name":"viewers","type":"StatsAbsValueAndPrev"},{"name":"posters","type":"StatsAbsValueAndPrev"},{"name":"growth_graph","type":"StatsGraph"},{"name":"members_graph","type":"StatsGraph"},{"name":"new_members_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"messages_graph","type":"StatsGraph"},{"name":"actions_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"weekdays_graph","type":"StatsGraph"},{"name":"top_posters","type":"Vector"},{"name":"top_admins","type":"Vector"},{"name":"top_inviters","type":"Vector"},{"name":"users","type":"Vector"}],"type":"stats.MegagroupStats"},{"id":"-1096616924","predicate":"globalPrivacySettings","params":[{"name":"flags","type":"#"},{"name":"archive_and_mute_new_noncontact_peers","type":"flags.0?Bool"}],"type":"GlobalPrivacySettings"},{"id":"1667228533","predicate":"phoneConnectionWebrtc","params":[{"name":"flags","type":"#"},{"name":"turn","type":"flags.0?true"},{"name":"stun","type":"flags.1?true"},{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"username","type":"string"},{"name":"password","type":"string"}],"type":"PhoneConnection"},{"id":"1107543535","predicate":"help.countryCode","params":[{"name":"flags","type":"#"},{"name":"country_code","type":"string"},{"name":"prefixes","type":"flags.0?Vector"},{"name":"patterns","type":"flags.1?Vector"}],"type":"help.CountryCode"},{"id":"-1014526429","predicate":"help.country","params":[{"name":"flags","type":"#"},{"name":"hidden","type":"flags.0?true"},{"name":"iso2","type":"string"},{"name":"default_name","type":"string"},{"name":"name","type":"flags.1?string"},{"name":"country_codes","type":"Vector"}],"type":"help.Country"},{"id":"-1815339214","predicate":"help.countriesListNotModified","params":[],"type":"help.CountriesList"},{"id":"-2016381538","predicate":"help.countriesList","params":[{"name":"countries","type":"Vector"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"1163625789","predicate":"messageViews","params":[{"name":"flags","type":"#"},{"name":"views","type":"flags.0?int"},{"name":"forwards","type":"flags.1?int"},{"name":"replies","type":"flags.2?MessageReplies"}],"type":"MessageViews"},{"id":"-761649164","predicate":"updateChannelMessageForwards","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"forwards","type":"int"}],"type":"Update"},{"id":"-96535659","predicate":"photoSizeProgressive","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"sizes","type":"Vector"}],"type":"PhotoSize"},{"id":"-1228606141","predicate":"messages.messageViews","params":[{"name":"views","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.MessageViews"},{"id":"-693004986","predicate":"updateReadChannelDiscussionInbox","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"},{"name":"broadcast_id","type":"flags.0?long"},{"name":"broadcast_post","type":"flags.0?int"}],"type":"Update"},{"id":"1767677564","predicate":"updateReadChannelDiscussionOutbox","params":[{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Update"},{"id":"-1506535550","predicate":"messages.discussionMessage","params":[{"name":"flags","type":"#"},{"name":"messages","type":"Vector"},{"name":"max_id","type":"flags.0?int"},{"name":"read_inbox_max_id","type":"flags.1?int"},{"name":"read_outbox_max_id","type":"flags.2?int"},{"name":"unread_count","type":"int"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.DiscussionMessage"},{"id":"-1495959709","predicate":"messageReplyHeader","params":[{"name":"flags","type":"#"},{"name":"reply_to_msg_id","type":"int"},{"name":"reply_to_peer_id","type":"flags.0?Peer"},{"name":"reply_to_top_id","type":"flags.1?int"}],"type":"MessageReplyHeader"},{"id":"-2083123262","predicate":"messageReplies","params":[{"name":"flags","type":"#"},{"name":"comments","type":"flags.0?true"},{"name":"replies","type":"int"},{"name":"replies_pts","type":"int"},{"name":"recent_repliers","type":"flags.1?Vector"},{"name":"channel_id","type":"flags.0?long"},{"name":"max_id","type":"flags.2?int"},{"name":"read_max_id","type":"flags.3?int"}],"type":"MessageReplies"},{"id":"610945826","predicate":"updatePeerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"blocked","type":"Bool"}],"type":"Update"},{"id":"-386039788","predicate":"peerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"date","type":"int"}],"type":"PeerBlocked"},{"id":"-1937192669","predicate":"updateChannelUserTyping","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-1392895362","predicate":"inputMessageCallbackQuery","params":[{"name":"id","type":"int"},{"name":"query_id","type":"long"}],"type":"InputMessage"},{"id":"453242886","predicate":"channelParticipantLeft","params":[{"name":"peer","type":"Peer"}],"type":"ChannelParticipant"},{"id":"-531931925","predicate":"channelParticipantsMentions","params":[{"name":"flags","type":"#"},{"name":"q","type":"flags.0?string"},{"name":"top_msg_id","type":"flags.1?int"}],"type":"ChannelParticipantsFilter"},{"id":"-309990731","predicate":"updatePinnedMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1538885128","predicate":"updatePinnedChannelMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"464520273","predicate":"inputMessagesFilterPinned","params":[],"type":"MessagesFilter"},{"id":"-1986399595","predicate":"stats.messageStats","params":[{"name":"views_graph","type":"StatsGraph"}],"type":"stats.MessageStats"},{"id":"-1730095465","predicate":"messageActionGeoProximityReached","params":[{"name":"from_id","type":"Peer"},{"name":"to_id","type":"Peer"},{"name":"distance","type":"int"}],"type":"MessageAction"},{"id":"-668906175","predicate":"photoPathSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"-651419003","predicate":"speakingInGroupCallAction","params":[],"type":"SendMessageAction"},{"id":"2004925620","predicate":"groupCallDiscarded","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"duration","type":"int"}],"type":"GroupCall"},{"id":"-711498484","predicate":"groupCall","params":[{"name":"flags","type":"#"},{"name":"join_muted","type":"flags.1?true"},{"name":"can_change_join_muted","type":"flags.2?true"},{"name":"join_date_asc","type":"flags.6?true"},{"name":"schedule_start_subscribed","type":"flags.8?true"},{"name":"can_start_video","type":"flags.9?true"},{"name":"record_video_active","type":"flags.11?true"},{"name":"rtmp_stream","type":"flags.12?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"participants_count","type":"int"},{"name":"title","type":"flags.3?string"},{"name":"stream_dc_id","type":"flags.4?int"},{"name":"record_start_date","type":"flags.5?int"},{"name":"schedule_date","type":"flags.7?int"},{"name":"unmuted_video_count","type":"flags.10?int"},{"name":"unmuted_video_limit","type":"int"},{"name":"version","type":"int"}],"type":"GroupCall"},{"id":"-659913713","predicate":"inputGroupCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGroupCall"},{"id":"2047704898","predicate":"messageActionGroupCall","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"duration","type":"flags.0?int"}],"type":"MessageAction"},{"id":"1345295095","predicate":"messageActionInviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-341428482","predicate":"groupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"left","type":"flags.1?true"},{"name":"can_self_unmute","type":"flags.2?true"},{"name":"just_joined","type":"flags.4?true"},{"name":"versioned","type":"flags.5?true"},{"name":"min","type":"flags.8?true"},{"name":"muted_by_you","type":"flags.9?true"},{"name":"volume_by_admin","type":"flags.10?true"},{"name":"self","type":"flags.12?true"},{"name":"video_joined","type":"flags.15?true"},{"name":"peer","type":"Peer"},{"name":"date","type":"int"},{"name":"active_date","type":"flags.3?int"},{"name":"source","type":"int"},{"name":"volume","type":"flags.7?int"},{"name":"about","type":"flags.11?string"},{"name":"raise_hand_rating","type":"flags.13?long"},{"name":"video","type":"flags.6?GroupCallParticipantVideo"},{"name":"presentation","type":"flags.14?GroupCallParticipantVideo"}],"type":"GroupCallParticipant"},{"id":"-124097970","predicate":"updateChat","params":[{"name":"chat_id","type":"long"}],"type":"Update"},{"id":"-219423922","predicate":"updateGroupCallParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"Update"},{"id":"347227392","predicate":"updateGroupCall","params":[{"name":"chat_id","type":"long"},{"name":"call","type":"GroupCall"}],"type":"Update"},{"id":"-1636664659","predicate":"phone.groupCall","params":[{"name":"call","type":"GroupCall"},{"name":"participants","type":"Vector"},{"name":"participants_next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.GroupCall"},{"id":"-193506890","predicate":"phone.groupParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"version","type":"int"}],"type":"phone.GroupParticipants"},{"id":"813821341","predicate":"inlineQueryPeerTypeSameBotPM","params":[],"type":"InlineQueryPeerType"},{"id":"-2093215828","predicate":"inlineQueryPeerTypePM","params":[],"type":"InlineQueryPeerType"},{"id":"-681130742","predicate":"inlineQueryPeerTypeChat","params":[],"type":"InlineQueryPeerType"},{"id":"1589952067","predicate":"inlineQueryPeerTypeMegagroup","params":[],"type":"InlineQueryPeerType"},{"id":"1664413338","predicate":"inlineQueryPeerTypeBroadcast","params":[],"type":"InlineQueryPeerType"},{"id":"589338437","predicate":"channelAdminLogEventActionStartGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-610299584","predicate":"channelAdminLogEventActionDiscardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-115071790","predicate":"channelAdminLogEventActionParticipantMute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-431740480","predicate":"channelAdminLogEventActionParticipantUnmute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1456906823","predicate":"channelAdminLogEventActionToggleGroupCallSetting","params":[{"name":"join_muted","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1966921727","predicate":"inputPaymentCredentialsGooglePay","params":[{"name":"payment_token","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"375566091","predicate":"messages.historyImport","params":[{"name":"id","type":"long"}],"type":"messages.HistoryImport"},{"id":"-606432698","predicate":"sendMessageHistoryImportAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"1578088377","predicate":"messages.historyImportParsed","params":[{"name":"flags","type":"#"},{"name":"pm","type":"flags.0?true"},{"name":"group","type":"flags.1?true"},{"name":"title","type":"flags.2?string"}],"type":"messages.HistoryImportParsed"},{"id":"-170010905","predicate":"inputReportReasonFake","params":[],"type":"ReportReason"},{"id":"-275956116","predicate":"messages.affectedFoundMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"},{"name":"messages","type":"Vector"}],"type":"messages.AffectedFoundMessages"},{"id":"-1441072131","predicate":"messageActionSetMessagesTTL","params":[{"name":"period","type":"int"}],"type":"MessageAction"},{"id":"-1147422299","predicate":"updatePeerHistoryTTL","params":[{"name":"flags","type":"#"},{"name":"peer","type":"Peer"},{"name":"ttl_period","type":"flags.0?int"}],"type":"Update"},{"id":"-796432838","predicate":"updateChatParticipant","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChatParticipant"},{"name":"new_participant","type":"flags.1?ChatParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1738720581","predicate":"updateChannelParticipant","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChannelParticipant"},{"name":"new_participant","type":"flags.1?ChannelParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-997782967","predicate":"updateBotStopped","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"stopped","type":"Bool"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"190633460","predicate":"chatInviteImporter","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatInviteImporter"},{"id":"-1111085620","predicate":"messages.exportedChatInvites","params":[{"name":"count","type":"int"},{"name":"invites","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvites"},{"id":"410107472","predicate":"messages.exportedChatInvite","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"572915951","predicate":"messages.exportedChatInviteReplaced","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"-2118733814","predicate":"messages.chatInviteImporters","params":[{"name":"count","type":"int"},{"name":"importers","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatInviteImporters"},{"id":"-219353309","predicate":"chatAdminWithInvites","params":[{"name":"admin_id","type":"long"},{"name":"invites_count","type":"int"},{"name":"revoked_invites_count","type":"int"}],"type":"ChatAdminWithInvites"},{"id":"-1231326505","predicate":"messages.chatAdminsWithInvites","params":[{"name":"admins","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatAdminsWithInvites"},{"id":"1557846647","predicate":"channelAdminLogEventActionParticipantJoinByInvite","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1515256996","predicate":"channelAdminLogEventActionExportedInviteDelete","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1091179342","predicate":"channelAdminLogEventActionExportedInviteRevoke","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"-384910503","predicate":"channelAdminLogEventActionExportedInviteEdit","params":[{"name":"prev_invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1048537159","predicate":"channelAdminLogEventActionParticipantVolume","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1855199800","predicate":"channelAdminLogEventActionChangeHistoryTTL","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"-1571952873","predicate":"messages.checkedHistoryImportPeer","params":[{"name":"confirm_text","type":"string"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"93890858","predicate":"inputGroupCallStream","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"time_ms","type":"long"},{"name":"scale","type":"int"},{"name":"video_channel","type":"flags.0?int"},{"name":"video_quality","type":"flags.0?int"}],"type":"InputFileLocation"},{"id":"-1343921601","predicate":"phone.joinAsPeers","params":[{"name":"peers","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.JoinAsPeers"},{"id":"541839704","predicate":"phone.exportedGroupCallInvite","params":[{"name":"link","type":"string"}],"type":"phone.ExportedGroupCallInvite"},{"id":"-672693723","predicate":"inputBotInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"894081801","predicate":"botInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1281329567","predicate":"messageActionGroupCallScheduled","params":[{"name":"call","type":"InputGroupCall"},{"name":"schedule_date","type":"int"}],"type":"MessageAction"},{"id":"-592373577","predicate":"groupCallParticipantVideoSourceGroup","params":[{"name":"semantics","type":"string"},{"name":"sources","type":"Vector"}],"type":"GroupCallParticipantVideoSourceGroup"},{"id":"1735736008","predicate":"groupCallParticipantVideo","params":[{"name":"flags","type":"#"},{"name":"paused","type":"flags.0?true"},{"name":"endpoint","type":"string"},{"name":"source_groups","type":"Vector"},{"name":"audio_source","type":"flags.1?int"}],"type":"GroupCallParticipantVideo"},{"id":"192428418","predicate":"updateGroupCallConnection","params":[{"name":"flags","type":"#"},{"name":"presentation","type":"flags.0?true"},{"name":"params","type":"DataJSON"}],"type":"Update"},{"id":"-2046910401","predicate":"stickers.suggestedShortName","params":[{"name":"short_name","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"795652779","predicate":"botCommandScopeDefault","params":[],"type":"BotCommandScope"},{"id":"1011811544","predicate":"botCommandScopeUsers","params":[],"type":"BotCommandScope"},{"id":"1877059713","predicate":"botCommandScopeChats","params":[],"type":"BotCommandScope"},{"id":"-1180016534","predicate":"botCommandScopeChatAdmins","params":[],"type":"BotCommandScope"},{"id":"-610432643","predicate":"botCommandScopePeer","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"1071145937","predicate":"botCommandScopePeerAdmins","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"169026035","predicate":"botCommandScopePeerUser","params":[{"name":"peer","type":"InputPeer"},{"name":"user_id","type":"InputUser"}],"type":"BotCommandScope"},{"id":"-478701471","predicate":"account.resetPasswordFailedWait","params":[{"name":"retry_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-370148227","predicate":"account.resetPasswordRequestedWait","params":[{"name":"until_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-383330754","predicate":"account.resetPasswordOk","params":[],"type":"account.ResetPasswordResult"},{"id":"1299263278","predicate":"updateBotCommands","params":[{"name":"peer","type":"Peer"},{"name":"bot_id","type":"long"},{"name":"commands","type":"Vector"}],"type":"Update"},{"id":"-318022605","predicate":"chatTheme","params":[{"name":"emoticon","type":"string"},{"name":"theme","type":"Theme"},{"name":"dark_theme","type":"Theme"}],"type":"ChatTheme"},{"id":"-535699004","predicate":"account.chatThemesNotModified","params":[],"type":"account.ChatThemes"},{"id":"-28524867","predicate":"account.chatThemes","params":[{"name":"hash","type":"int"},{"name":"themes","type":"Vector"}],"type":"account.ChatThemes"},{"id":"-1434950843","predicate":"messageActionSetChatTheme","params":[{"name":"emoticon","type":"string"}],"type":"MessageAction"},{"id":"-1336228175","predicate":"sendMessageChooseStickerAction","params":[],"type":"SendMessageAction"},{"id":"708589599","predicate":"sponsoredMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"bytes"},{"name":"from_id","type":"Peer"},{"name":"start_param","type":"flags.0?string"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"SponsoredMessage"},{"id":"1705297877","predicate":"messages.sponsoredMessages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.SponsoredMessages"},{"id":"215889721","predicate":"inputStickerSetAnimatedEmojiAnimations","params":[],"type":"InputStickerSet"},{"id":"630664139","predicate":"sendMessageEmojiInteraction","params":[{"name":"emoticon","type":"string"},{"name":"msg_id","type":"int"},{"name":"interaction","type":"DataJSON"}],"type":"SendMessageAction"},{"id":"-1234857938","predicate":"sendMessageEmojiInteractionSeen","params":[{"name":"emoticon","type":"string"}],"type":"SendMessageAction"},{"id":"-1227287081","predicate":"inputBotInlineMessageID64","params":[{"name":"dc_id","type":"int"},{"name":"owner_id","type":"long"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"}],"methods":[{"id":"-878758099","method":"invokeAfterMsg","params":[{"name":"msg_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"1036301552","method":"invokeAfterMsgs","params":[{"name":"msg_ids","type":"Vector"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1502141361","method":"auth.sendCode","params":[{"name":"phone_number","type":"string"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"-2131827673","method":"auth.signUp","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"auth.Authorization"},{"id":"-1126886015","method":"auth.signIn","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"auth.Authorization"},{"id":"1461180992","method":"auth.logOut","params":[],"type":"Bool"},{"id":"-1616179942","method":"auth.resetAuthorizations","params":[],"type":"Bool"},{"id":"-440401971","method":"auth.exportAuthorization","params":[{"name":"dc_id","type":"int"}],"type":"auth.ExportedAuthorization"},{"id":"-1518699091","method":"auth.importAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.Authorization"},{"id":"-841733627","method":"auth.bindTempAuthKey","params":[{"name":"perm_auth_key_id","type":"long"},{"name":"nonce","type":"long"},{"name":"expires_at","type":"int"},{"name":"encrypted_message","type":"bytes"}],"type":"Bool"},{"id":"-326762118","method":"account.registerDevice","params":[{"name":"flags","type":"#"},{"name":"no_muted","type":"flags.0?true"},{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"app_sandbox","type":"Bool"},{"name":"secret","type":"bytes"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"1779249670","method":"account.unregisterDevice","params":[{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"-2067899501","method":"account.updateNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"},{"name":"settings","type":"InputPeerNotifySettings"}],"type":"Bool"},{"id":"313765169","method":"account.getNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"}],"type":"PeerNotifySettings"},{"id":"-612493497","method":"account.resetNotifySettings","params":[],"type":"Bool"},{"id":"2018596725","method":"account.updateProfile","params":[{"name":"flags","type":"#"},{"name":"first_name","type":"flags.0?string"},{"name":"last_name","type":"flags.1?string"},{"name":"about","type":"flags.2?string"}],"type":"User"},{"id":"1713919532","method":"account.updateStatus","params":[{"name":"offline","type":"Bool"}],"type":"Bool"},{"id":"127302966","method":"account.getWallPapers","params":[{"name":"hash","type":"long"}],"type":"account.WallPapers"},{"id":"-977650298","method":"account.reportPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"227648840","method":"users.getUsers","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-902781519","method":"users.getFullUser","params":[{"name":"id","type":"InputUser"}],"type":"UserFull"},{"id":"2061264541","method":"contacts.getContactIDs","params":[{"name":"hash","type":"long"}],"type":"Vector"},{"id":"-995929106","method":"contacts.getStatuses","params":[],"type":"Vector"},{"id":"1574346258","method":"contacts.getContacts","params":[{"name":"hash","type":"long"}],"type":"contacts.Contacts"},{"id":"746589157","method":"contacts.importContacts","params":[{"name":"contacts","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"157945344","method":"contacts.deleteContacts","params":[{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"269745566","method":"contacts.deleteByPhones","params":[{"name":"phones","type":"Vector"}],"type":"Bool"},{"id":"1758204945","method":"contacts.block","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-1096393392","method":"contacts.unblock","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-176409329","method":"contacts.getBlocked","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"contacts.Blocked"},{"id":"1673946374","method":"messages.getMessages","params":[{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1594569905","method":"messages.getDialogs","params":[{"name":"flags","type":"#"},{"name":"exclude_pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"offset_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Dialogs"},{"id":"1143203525","method":"messages.getHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1593989278","method":"messages.search","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"q","type":"string"},{"name":"from_id","type":"flags.0?InputPeer"},{"name":"top_msg_id","type":"flags.1?int"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"238054714","method":"messages.readHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"}],"type":"messages.AffectedMessages"},{"id":"469850889","method":"messages.deleteHistory","params":[{"name":"flags","type":"#"},{"name":"just_clear","type":"flags.0?true"},{"name":"revoke","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"}],"type":"messages.AffectedHistory"},{"id":"-443640366","method":"messages.deleteMessages","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"94983360","method":"messages.receivedMessages","params":[{"name":"max_id","type":"int"}],"type":"Vector"},{"id":"1486110434","method":"messages.setTyping","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"action","type":"SendMessageAction"}],"type":"Bool"},{"id":"1376532592","method":"messages.sendMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"881978281","method":"messages.sendMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"media","type":"InputMedia"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-637606386","method":"messages.forwardMessages","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"with_my_score","type":"flags.8?true"},{"name":"drop_author","type":"flags.11?true"},{"name":"drop_media_captions","type":"flags.12?true"},{"name":"from_peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"random_id","type":"Vector"},{"name":"to_peer","type":"InputPeer"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-820669733","method":"messages.reportSpam","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"913498268","method":"messages.getPeerSettings","params":[{"name":"peer","type":"InputPeer"}],"type":"PeerSettings"},{"id":"-1991005362","method":"messages.report","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"1240027791","method":"messages.getChats","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"-1364194508","method":"messages.getFullChat","params":[{"name":"chat_id","type":"long"}],"type":"messages.ChatFull"},{"id":"1937260541","method":"messages.editChatTitle","params":[{"name":"chat_id","type":"long"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"903730804","method":"messages.editChatPhoto","params":[{"name":"chat_id","type":"long"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"-230206493","method":"messages.addChatUser","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"fwd_limit","type":"int"}],"type":"Updates"},{"id":"-1575461717","method":"messages.deleteChatUser","params":[{"name":"flags","type":"#"},{"name":"revoke_history","type":"flags.0?true"},{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"}],"type":"Updates"},{"id":"164303470","method":"messages.createChat","params":[{"name":"users","type":"Vector"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-304838614","method":"updates.getState","params":[],"type":"updates.State"},{"id":"630429265","method":"updates.getDifference","params":[{"name":"flags","type":"#"},{"name":"pts","type":"int"},{"name":"pts_total_limit","type":"flags.0?int"},{"name":"date","type":"int"},{"name":"qts","type":"int"}],"type":"updates.Difference"},{"id":"1926525996","method":"photos.updateProfilePhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"photos.Photo"},{"id":"-1980559511","method":"photos.uploadProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"photos.Photo"},{"id":"-2016444625","method":"photos.deletePhotos","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-1291540959","method":"upload.saveFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1319462148","method":"upload.getFile","params":[{"name":"flags","type":"#"},{"name":"precise","type":"flags.0?true"},{"name":"cdn_supported","type":"flags.1?true"},{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.File"},{"id":"-990308245","method":"help.getConfig","params":[],"type":"Config"},{"id":"531836966","method":"help.getNearestDc","params":[],"type":"NearestDc"},{"id":"1378703997","method":"help.getAppUpdate","params":[{"name":"source","type":"string"}],"type":"help.AppUpdate"},{"id":"1295590211","method":"help.getInviteText","params":[],"type":"help.InviteText"},{"id":"-1848823128","method":"photos.getUserPhotos","params":[{"name":"user_id","type":"InputUser"},{"name":"offset","type":"int"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"photos.Photos"},{"id":"651135312","method":"messages.getDhConfig","params":[{"name":"version","type":"int"},{"name":"random_length","type":"int"}],"type":"messages.DhConfig"},{"id":"-162681021","method":"messages.requestEncryption","params":[{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1035731989","method":"messages.acceptEncryption","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"-208425312","method":"messages.discardEncryption","params":[{"name":"flags","type":"#"},{"name":"delete_history","type":"flags.0?true"},{"name":"chat_id","type":"int"}],"type":"Bool"},{"id":"2031374829","method":"messages.setEncryptedTyping","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"typing","type":"Bool"}],"type":"Bool"},{"id":"2135648522","method":"messages.readEncryptedHistory","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"max_date","type":"int"}],"type":"Bool"},{"id":"1157265941","method":"messages.sendEncrypted","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1431914525","method":"messages.sendEncryptedFile","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"},{"name":"file","type":"InputEncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"852769188","method":"messages.sendEncryptedService","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1436924774","method":"messages.receivedQueue","params":[{"name":"max_qts","type":"int"}],"type":"Vector"},{"id":"1259113487","method":"messages.reportEncryptedSpam","params":[{"name":"peer","type":"InputEncryptedChat"}],"type":"Bool"},{"id":"-562337987","method":"upload.saveBigFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"file_total_parts","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1043505495","method":"initConnection","params":[{"name":"flags","type":"#"},{"name":"api_id","type":"int"},{"name":"device_model","type":"string"},{"name":"system_version","type":"string"},{"name":"app_version","type":"string"},{"name":"system_lang_code","type":"string"},{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"proxy","type":"flags.0?InputClientProxy"},{"name":"params","type":"flags.1?JSONValue"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1663104819","method":"help.getSupport","params":[],"type":"help.Support"},{"id":"916930423","method":"messages.readMessageContents","params":[{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"655677548","method":"account.checkUsername","params":[{"name":"username","type":"string"}],"type":"Bool"},{"id":"1040964988","method":"account.updateUsername","params":[{"name":"username","type":"string"}],"type":"User"},{"id":"301470424","method":"contacts.search","params":[{"name":"q","type":"string"},{"name":"limit","type":"int"}],"type":"contacts.Found"},{"id":"-623130288","method":"account.getPrivacy","params":[{"name":"key","type":"InputPrivacyKey"}],"type":"account.PrivacyRules"},{"id":"-906486552","method":"account.setPrivacy","params":[{"name":"key","type":"InputPrivacyKey"},{"name":"rules","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"1099779595","method":"account.deleteAccount","params":[{"name":"reason","type":"string"}],"type":"Bool"},{"id":"150761757","method":"account.getAccountTTL","params":[],"type":"AccountDaysTTL"},{"id":"608323678","method":"account.setAccountTTL","params":[{"name":"ttl","type":"AccountDaysTTL"}],"type":"Bool"},{"id":"-627372787","method":"invokeWithLayer","params":[{"name":"layer","type":"int"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-113456221","method":"contacts.resolveUsername","params":[{"name":"username","type":"string"}],"type":"contacts.ResolvedPeer"},{"id":"-2108208411","method":"account.sendChangePhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1891839707","method":"account.changePhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"User"},{"id":"-710552671","method":"messages.getStickers","params":[{"name":"emoticon","type":"string"},{"name":"hash","type":"long"}],"type":"messages.Stickers"},{"id":"-1197432408","method":"messages.getAllStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"954152242","method":"account.updateDeviceLocked","params":[{"name":"period","type":"int"}],"type":"Bool"},{"id":"1738800940","method":"auth.importBotAuthorization","params":[{"name":"flags","type":"int"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"bot_auth_token","type":"string"}],"type":"auth.Authorization"},{"id":"-1956073268","method":"messages.getWebPagePreview","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"MessageMedia"},{"id":"-484392616","method":"account.getAuthorizations","params":[],"type":"account.Authorizations"},{"id":"-545786948","method":"account.resetAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1418342645","method":"account.getPassword","params":[],"type":"account.Password"},{"id":"-1663767815","method":"account.getPasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"account.PasswordSettings"},{"id":"-1516564433","method":"account.updatePasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"new_settings","type":"account.PasswordInputSettings"}],"type":"Bool"},{"id":"-779399914","method":"auth.checkPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"auth.Authorization"},{"id":"-661144474","method":"auth.requestPasswordRecovery","params":[],"type":"auth.PasswordRecovery"},{"id":"923364464","method":"auth.recoverPassword","params":[{"name":"flags","type":"#"},{"name":"code","type":"string"},{"name":"new_settings","type":"flags.0?account.PasswordInputSettings"}],"type":"auth.Authorization"},{"id":"-1080796745","method":"invokeWithoutUpdates","params":[{"name":"query","type":"!X"}],"type":"X"},{"id":"347716823","method":"messages.exportChatInvite","params":[{"name":"flags","type":"#"},{"name":"legacy_revoke_permanent","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"}],"type":"ExportedChatInvite"},{"id":"1051570619","method":"messages.checkChatInvite","params":[{"name":"hash","type":"string"}],"type":"ChatInvite"},{"id":"1817183516","method":"messages.importChatInvite","params":[{"name":"hash","type":"string"}],"type":"Updates"},{"id":"639215886","method":"messages.getStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"}],"type":"messages.StickerSet"},{"id":"-946871200","method":"messages.installStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"archived","type":"Bool"}],"type":"messages.StickerSetInstallResult"},{"id":"-110209570","method":"messages.uninstallStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"-421563528","method":"messages.startBot","params":[{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"long"},{"name":"start_param","type":"string"}],"type":"Updates"},{"id":"-1877938321","method":"help.getAppChangelog","params":[{"name":"prev_app_version","type":"string"}],"type":"Updates"},{"id":"1468322785","method":"messages.getMessagesViews","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"increment","type":"Bool"}],"type":"messages.MessageViews"},{"id":"-871347913","method":"channels.readHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"-2067661490","method":"channels.deleteMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"-787622117","method":"channels.deleteUserHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"}],"type":"messages.AffectedHistory"},{"id":"-32999408","method":"channels.reportSpam","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1383294429","method":"channels.getMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"2010044880","method":"channels.getParticipants","params":[{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelParticipantsFilter"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"channels.ChannelParticipants"},{"id":"-1599378234","method":"channels.getParticipant","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"}],"type":"channels.ChannelParticipant"},{"id":"176122811","method":"channels.getChannels","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"141781513","method":"channels.getFullChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.ChatFull"},{"id":"1029681423","method":"channels.createChannel","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.0?true"},{"name":"megagroup","type":"flags.1?true"},{"name":"for_import","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"about","type":"string"},{"name":"geo_point","type":"flags.2?InputGeoPoint"},{"name":"address","type":"flags.2?string"}],"type":"Updates"},{"id":"-751007486","method":"channels.editAdmin","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"string"}],"type":"Updates"},{"id":"1450044624","method":"channels.editTitle","params":[{"name":"channel","type":"InputChannel"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-248621111","method":"channels.editPhoto","params":[{"name":"channel","type":"InputChannel"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"283557164","method":"channels.checkUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"890549214","method":"channels.updateUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"615851205","method":"channels.joinChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"-130635115","method":"channels.leaveChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"429865580","method":"channels.inviteToChannel","params":[{"name":"channel","type":"InputChannel"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"-1072619549","method":"channels.deleteChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"51854712","method":"updates.getChannelDifference","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelMessagesFilter"},{"name":"pts","type":"int"},{"name":"limit","type":"int"}],"type":"updates.ChannelDifference"},{"id":"-1470377534","method":"messages.editChatAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"is_admin","type":"Bool"}],"type":"Bool"},{"id":"-1568189671","method":"messages.migrateChat","params":[{"name":"chat_id","type":"long"}],"type":"Updates"},{"id":"1271290010","method":"messages.searchGlobal","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"q","type":"string"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"2016638777","method":"messages.reorderStickerSets","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"864953444","method":"messages.getDocumentByHash","params":[{"name":"sha256","type":"bytes"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"1559270965","method":"messages.getSavedGifs","params":[{"name":"hash","type":"long"}],"type":"messages.SavedGifs"},{"id":"846868683","method":"messages.saveGif","params":[{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"1364105629","method":"messages.getInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"geo_point","type":"flags.0?InputGeoPoint"},{"name":"query","type":"string"},{"name":"offset","type":"string"}],"type":"messages.BotResults"},{"id":"-346119674","method":"messages.setInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"private","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"next_offset","type":"flags.2?string"},{"name":"switch_pm","type":"flags.3?InlineBotSwitchPM"}],"type":"Bool"},{"id":"570955184","method":"messages.sendInlineBotResult","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"hide_via","type":"flags.11?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"random_id","type":"long"},{"name":"query_id","type":"long"},{"name":"id","type":"string"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-432034325","method":"channels.exportMessageLink","params":[{"name":"flags","type":"#"},{"name":"grouped","type":"flags.0?true"},{"name":"thread","type":"flags.1?true"},{"name":"channel","type":"InputChannel"},{"name":"id","type":"int"}],"type":"ExportedMessageLink"},{"id":"527021574","method":"channels.toggleSignatures","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"1056025023","method":"auth.resendCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"auth.SentCode"},{"id":"520357240","method":"auth.cancelCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"Bool"},{"id":"-39416522","method":"messages.getMessageEditData","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"messages.MessageEditData"},{"id":"1224152952","method":"messages.editMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.15?int"}],"type":"Updates"},{"id":"-2091549254","method":"messages.editInlineBotMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"-1824339449","method":"messages.getBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"game","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"data","type":"flags.0?bytes"},{"name":"password","type":"flags.2?InputCheckPasswordSRP"}],"type":"messages.BotCallbackAnswer"},{"id":"-712043766","method":"messages.setBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"Bool"},{"id":"-1758168906","method":"contacts.getTopPeers","params":[{"name":"flags","type":"#"},{"name":"correspondents","type":"flags.0?true"},{"name":"bots_pm","type":"flags.1?true"},{"name":"bots_inline","type":"flags.2?true"},{"name":"phone_calls","type":"flags.3?true"},{"name":"forward_users","type":"flags.4?true"},{"name":"forward_chats","type":"flags.5?true"},{"name":"groups","type":"flags.10?true"},{"name":"channels","type":"flags.15?true"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"contacts.TopPeers"},{"id":"451113900","method":"contacts.resetTopPeerRating","params":[{"name":"category","type":"TopPeerCategory"},{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-462373635","method":"messages.getPeerDialogs","params":[{"name":"peers","type":"Vector"}],"type":"messages.PeerDialogs"},{"id":"-1137057461","method":"messages.saveDraft","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"peer","type":"InputPeer"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"1782549861","method":"messages.getAllDrafts","params":[],"type":"Updates"},{"id":"1685588756","method":"messages.getFeaturedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"1527873830","method":"messages.readFeaturedStickers","params":[{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1649852357","method":"messages.getRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"hash","type":"long"}],"type":"messages.RecentStickers"},{"id":"958863608","method":"messages.saveRecentSticker","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"-1986437075","method":"messages.clearRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"}],"type":"Bool"},{"id":"1475442322","method":"messages.getArchivedStickers","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"offset_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.ArchivedStickers"},{"id":"457157256","method":"account.sendConfirmPhoneCode","params":[{"name":"hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1596029123","method":"account.confirmPhone","params":[{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"-122669393","method":"channels.getAdminedPublicChannels","params":[{"name":"flags","type":"#"},{"name":"by_location","type":"flags.0?true"},{"name":"check_limit","type":"flags.1?true"}],"type":"messages.Chats"},{"id":"1678738104","method":"messages.getMaskStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"-866424884","method":"messages.getAttachedStickers","params":[{"name":"media","type":"InputStickeredMedia"}],"type":"Vector"},{"id":"-1907842680","method":"auth.dropTempAuthKeys","params":[{"name":"except_auth_keys","type":"Vector"}],"type":"Bool"},{"id":"-1896289088","method":"messages.setGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Updates"},{"id":"363700068","method":"messages.setInlineGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Bool"},{"id":"-400399203","method":"messages.getGameHighScores","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"258170395","method":"messages.getInlineGameHighScores","params":[{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"-468934396","method":"messages.getCommonChats","params":[{"name":"user_id","type":"InputUser"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.Chats"},{"id":"-2023787330","method":"messages.getAllChats","params":[{"name":"except_ids","type":"Vector"}],"type":"messages.Chats"},{"id":"-333262899","method":"help.setBotUpdatesStatus","params":[{"name":"pending_updates_count","type":"int"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"852135825","method":"messages.getWebPage","params":[{"name":"url","type":"string"},{"name":"hash","type":"int"}],"type":"WebPage"},{"id":"-1489903017","method":"messages.toggleDialogPin","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"991616823","method":"messages.reorderPinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"folder_id","type":"int"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-692498958","method":"messages.getPinnedDialogs","params":[{"name":"folder_id","type":"int"}],"type":"messages.PeerDialogs"},{"id":"-1440257555","method":"bots.sendCustomRequest","params":[{"name":"custom_method","type":"string"},{"name":"params","type":"DataJSON"}],"type":"DataJSON"},{"id":"-434028723","method":"bots.answerWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"}],"type":"Bool"},{"id":"619086221","method":"upload.getWebFile","params":[{"name":"location","type":"InputWebFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.WebFile"},{"id":"-1976353651","method":"payments.getPaymentForm","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"theme_params","type":"flags.0?DataJSON"}],"type":"payments.PaymentForm"},{"id":"611897804","method":"payments.getPaymentReceipt","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"payments.PaymentReceipt"},{"id":"-619695760","method":"payments.validateRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"info","type":"PaymentRequestedInfo"}],"type":"payments.ValidatedRequestedInfo"},{"id":"818134173","method":"payments.sendPaymentForm","params":[{"name":"flags","type":"#"},{"name":"form_id","type":"long"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"requested_info_id","type":"flags.0?string"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"credentials","type":"InputPaymentCredentials"},{"name":"tip_amount","type":"flags.2?long"}],"type":"payments.PaymentResult"},{"id":"1151208273","method":"account.getTmpPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"period","type":"int"}],"type":"account.TmpPassword"},{"id":"578650699","method":"payments.getSavedInfo","params":[],"type":"payments.SavedInfo"},{"id":"-667062079","method":"payments.clearSavedInfo","params":[{"name":"flags","type":"#"},{"name":"credentials","type":"flags.0?true"},{"name":"info","type":"flags.1?true"}],"type":"Bool"},{"id":"-436833542","method":"messages.setBotShippingResults","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"Bool"},{"id":"163765653","method":"messages.setBotPrecheckoutResults","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"}],"type":"Bool"},{"id":"-1876841625","method":"stickers.createStickerSet","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"animated","type":"flags.1?true"},{"name":"videos","type":"flags.4?true"},{"name":"user_id","type":"InputUser"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumb","type":"flags.2?InputDocument"},{"name":"stickers","type":"Vector"},{"name":"software","type":"flags.3?string"}],"type":"messages.StickerSet"},{"id":"-143257775","method":"stickers.removeStickerFromSet","params":[{"name":"sticker","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"-4795190","method":"stickers.changeStickerPosition","params":[{"name":"sticker","type":"InputDocument"},{"name":"position","type":"int"}],"type":"messages.StickerSet"},{"id":"-2041315650","method":"stickers.addStickerToSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"sticker","type":"InputStickerSetItem"}],"type":"messages.StickerSet"},{"id":"1369162417","method":"messages.uploadMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"1430593449","method":"phone.getCallConfig","params":[],"type":"DataJSON"},{"id":"1124046573","method":"phone.requestCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"1003664544","method":"phone.acceptCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"788404002","method":"phone.confirmCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_a","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"399855457","method":"phone.receivedCall","params":[{"name":"peer","type":"InputPhoneCall"}],"type":"Bool"},{"id":"-1295269440","method":"phone.discardCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"duration","type":"int"},{"name":"reason","type":"PhoneCallDiscardReason"},{"name":"connection_id","type":"long"}],"type":"Updates"},{"id":"1508562471","method":"phone.setCallRating","params":[{"name":"flags","type":"#"},{"name":"user_initiative","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"rating","type":"int"},{"name":"comment","type":"string"}],"type":"Updates"},{"id":"662363518","method":"phone.saveCallDebug","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"debug","type":"DataJSON"}],"type":"Bool"},{"id":"536919235","method":"upload.getCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.CdnFile"},{"id":"-1691921240","method":"upload.reuploadCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"request_token","type":"bytes"}],"type":"Vector"},{"id":"1375900482","method":"help.getCdnConfig","params":[],"type":"CdnConfig"},{"id":"-219008246","method":"langpack.getLangPack","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackDifference"},{"id":"-269862909","method":"langpack.getStrings","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"keys","type":"Vector"}],"type":"Vector"},{"id":"-845657435","method":"langpack.getDifference","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"LangPackDifference"},{"id":"1120311183","method":"langpack.getLanguages","params":[{"name":"lang_pack","type":"string"}],"type":"Vector"},{"id":"-1763259007","method":"channels.editBanned","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"870184064","method":"channels.getAdminLog","params":[{"name":"flags","type":"#"},{"name":"channel","type":"InputChannel"},{"name":"q","type":"string"},{"name":"events_filter","type":"flags.0?ChannelAdminLogEventsFilter"},{"name":"admins","type":"flags.1?Vector"},{"name":"max_id","type":"long"},{"name":"min_id","type":"long"},{"name":"limit","type":"int"}],"type":"channels.AdminLogResults"},{"id":"1302676017","method":"upload.getCdnFileHashes","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"-914493408","method":"messages.sendScreenshotNotification","params":[{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"int"},{"name":"random_id","type":"long"}],"type":"Updates"},{"id":"-359881479","method":"channels.setStickers","params":[{"name":"channel","type":"InputChannel"},{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"82946729","method":"messages.getFavedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FavedStickers"},{"id":"-1174420133","method":"messages.faveSticker","params":[{"name":"id","type":"InputDocument"},{"name":"unfave","type":"Bool"}],"type":"Bool"},{"id":"-357180360","method":"channels.readMessageContents","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-2020263951","method":"contacts.resetSaved","params":[],"type":"Bool"},{"id":"1180140658","method":"messages.getUnreadMentions","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"}],"type":"messages.Messages"},{"id":"-1355375294","method":"channels.deleteHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"1036054804","method":"help.getRecentMeUrls","params":[{"name":"referer","type":"string"}],"type":"help.RecentMeUrls"},{"id":"-356796084","method":"channels.togglePreHistoryHidden","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"251759059","method":"messages.readMentions","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1881817312","method":"messages.getRecentLocations","params":[{"name":"peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-872345397","method":"messages.sendMultiMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"multi_media","type":"Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"1347929239","method":"messages.uploadEncryptedFile","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"file","type":"InputEncryptedFile"}],"type":"EncryptedFile"},{"id":"405695855","method":"account.getWebAuthorizations","params":[],"type":"account.WebAuthorizations"},{"id":"755087855","method":"account.resetWebAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1747789204","method":"account.resetWebAuthorizations","params":[],"type":"Bool"},{"id":"896555914","method":"messages.searchStickerSets","params":[{"name":"flags","type":"#"},{"name":"exclude_featured","type":"flags.0?true"},{"name":"q","type":"string"},{"name":"hash","type":"long"}],"type":"messages.FoundStickerSets"},{"id":"-956147407","method":"upload.getFileHashes","params":[{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"749019089","method":"help.getTermsOfServiceUpdate","params":[],"type":"help.TermsOfServiceUpdate"},{"id":"-294455398","method":"help.acceptTermsOfService","params":[{"name":"id","type":"DataJSON"}],"type":"Bool"},{"id":"-1299661699","method":"account.getAllSecureValues","params":[],"type":"Vector"},{"id":"1936088002","method":"account.getSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Vector"},{"id":"-1986010339","method":"account.saveSecureValue","params":[{"name":"value","type":"InputSecureValue"},{"name":"secure_secret_id","type":"long"}],"type":"SecureValue"},{"id":"-1199522741","method":"account.deleteSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Bool"},{"id":"-1865902923","method":"users.setSecureValueErrors","params":[{"name":"id","type":"InputUser"},{"name":"errors","type":"Vector"}],"type":"Bool"},{"id":"-1456907910","method":"account.getAuthorizationForm","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"}],"type":"account.AuthorizationForm"},{"id":"-202552205","method":"account.acceptAuthorization","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"},{"name":"value_hashes","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"Bool"},{"id":"-1516022023","method":"account.sendVerifyPhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1305716726","method":"account.verifyPhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"1880182943","method":"account.sendVerifyEmailCode","params":[{"name":"email","type":"string"}],"type":"account.SentEmailCode"},{"id":"-323339813","method":"account.verifyEmail","params":[{"name":"email","type":"string"},{"name":"code","type":"string"}],"type":"Bool"},{"id":"1072547679","method":"help.getDeepLinkInfo","params":[{"name":"path","type":"string"}],"type":"help.DeepLinkInfo"},{"id":"-2098076769","method":"contacts.getSaved","params":[],"type":"Vector"},{"id":"-2092831552","method":"channels.getLeftChannels","params":[{"name":"offset","type":"int"}],"type":"messages.Chats"},{"id":"-262453244","method":"account.initTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"message_users","type":"flags.1?true"},{"name":"message_chats","type":"flags.2?true"},{"name":"message_megagroups","type":"flags.3?true"},{"name":"message_channels","type":"flags.4?true"},{"name":"files","type":"flags.5?true"},{"name":"file_max_size","type":"flags.5?int"}],"type":"account.Takeout"},{"id":"489050862","method":"account.finishTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.0?true"}],"type":"Bool"},{"id":"486505992","method":"messages.getSplitRanges","params":[],"type":"Vector"},{"id":"911373810","method":"invokeWithMessagesRange","params":[{"name":"range","type":"MessageRange"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1398145746","method":"invokeWithTakeout","params":[{"name":"takeout_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1031349873","method":"messages.markDialogUnread","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"585256482","method":"messages.getDialogUnreadMarks","params":[],"type":"Vector"},{"id":"-2062238246","method":"contacts.toggleTopPeers","params":[{"name":"enabled","type":"Bool"}],"type":"Bool"},{"id":"2119757468","method":"messages.clearAllDrafts","params":[],"type":"Bool"},{"id":"-1735311088","method":"help.getAppConfig","params":[],"type":"JSONValue"},{"id":"1862465352","method":"help.saveAppLog","params":[{"name":"events","type":"Vector"}],"type":"Bool"},{"id":"-966677240","method":"help.getPassportConfig","params":[{"name":"hash","type":"int"}],"type":"help.PassportConfig"},{"id":"1784243458","method":"langpack.getLanguage","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackLanguage"},{"id":"-760547348","method":"messages.updatePinnedMessage","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"unpin","type":"flags.1?true"},{"name":"pm_oneside","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"Updates"},{"id":"-1881204448","method":"account.confirmPasswordEmail","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"2055154197","method":"account.resendPasswordEmail","params":[],"type":"Bool"},{"id":"-1043606090","method":"account.cancelPasswordEmail","params":[],"type":"Bool"},{"id":"-748624084","method":"help.getSupportName","params":[],"type":"help.SupportName"},{"id":"59377875","method":"help.getUserInfo","params":[{"name":"user_id","type":"InputUser"}],"type":"help.UserInfo"},{"id":"1723407216","method":"help.editUserInfo","params":[{"name":"user_id","type":"InputUser"},{"name":"message","type":"string"},{"name":"entities","type":"Vector"}],"type":"help.UserInfo"},{"id":"-1626880216","method":"account.getContactSignUpNotification","params":[],"type":"Bool"},{"id":"-806076575","method":"account.setContactSignUpNotification","params":[{"name":"silent","type":"Bool"}],"type":"Bool"},{"id":"1398240377","method":"account.getNotifyExceptions","params":[{"name":"flags","type":"#"},{"name":"compare_sound","type":"flags.1?true"},{"name":"peer","type":"flags.0?InputNotifyPeer"}],"type":"Updates"},{"id":"283795844","method":"messages.sendVote","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"options","type":"Vector"}],"type":"Updates"},{"id":"1941660731","method":"messages.getPollResults","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1848369232","method":"messages.getOnlines","params":[{"name":"peer","type":"InputPeer"}],"type":"ChatOnlines"},{"id":"-554301545","method":"messages.editChatAbout","params":[{"name":"peer","type":"InputPeer"},{"name":"about","type":"string"}],"type":"Bool"},{"id":"-1517917375","method":"messages.editChatDefaultBannedRights","params":[{"name":"peer","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"-57811990","method":"account.getWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"}],"type":"WallPaper"},{"id":"-578472351","method":"account.uploadWallPaper","params":[{"name":"file","type":"InputFile"},{"name":"mime_type","type":"string"},{"name":"settings","type":"WallPaperSettings"}],"type":"WallPaper"},{"id":"1817860919","method":"account.saveWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"unsave","type":"Bool"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-18000023","method":"account.installWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-1153722364","method":"account.resetWallPapers","params":[],"type":"Bool"},{"id":"1457130303","method":"account.getAutoDownloadSettings","params":[],"type":"account.AutoDownloadSettings"},{"id":"1995661875","method":"account.saveAutoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"low","type":"flags.0?true"},{"name":"high","type":"flags.1?true"},{"name":"settings","type":"AutoDownloadSettings"}],"type":"Bool"},{"id":"899735650","method":"messages.getEmojiKeywords","params":[{"name":"lang_code","type":"string"}],"type":"EmojiKeywordsDifference"},{"id":"352892591","method":"messages.getEmojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"EmojiKeywordsDifference"},{"id":"1318675378","method":"messages.getEmojiKeywordsLanguages","params":[{"name":"lang_codes","type":"Vector"}],"type":"Vector"},{"id":"-709817306","method":"messages.getEmojiURL","params":[{"name":"lang_code","type":"string"}],"type":"EmojiURL"},{"id":"1749536939","method":"folders.editPeerFolders","params":[{"name":"folder_peers","type":"Vector"}],"type":"Updates"},{"id":"472471681","method":"folders.deleteFolder","params":[{"name":"folder_id","type":"int"}],"type":"Updates"},{"id":"1932455680","method":"messages.getSearchCounters","params":[{"name":"peer","type":"InputPeer"},{"name":"filters","type":"Vector"}],"type":"Vector"},{"id":"-170208392","method":"channels.getGroupsForDiscussion","params":[],"type":"messages.Chats"},{"id":"1079520178","method":"channels.setDiscussionGroup","params":[{"name":"broadcast","type":"InputChannel"},{"name":"group","type":"InputChannel"}],"type":"Bool"},{"id":"428848198","method":"messages.requestUrlAuth","params":[{"name":"flags","type":"#"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"-1322487515","method":"messages.acceptUrlAuth","params":[{"name":"flags","type":"#"},{"name":"write_allowed","type":"flags.0?true"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"1336717624","method":"messages.hidePeerSettingsBar","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-386636848","method":"contacts.addContact","params":[{"name":"flags","type":"#"},{"name":"add_phone_privacy_exception","type":"flags.0?true"},{"name":"id","type":"InputUser"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"phone","type":"string"}],"type":"Updates"},{"id":"-130964977","method":"contacts.acceptContact","params":[{"name":"id","type":"InputUser"}],"type":"Updates"},{"id":"-1892102881","method":"channels.editCreator","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"password","type":"InputCheckPasswordSRP"}],"type":"Updates"},{"id":"-750207932","method":"contacts.getLocated","params":[{"name":"flags","type":"#"},{"name":"background","type":"flags.1?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"self_expires","type":"flags.0?int"}],"type":"Updates"},{"id":"1491484525","method":"channels.editLocation","params":[{"name":"channel","type":"InputChannel"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"address","type":"string"}],"type":"Bool"},{"id":"-304832784","method":"channels.toggleSlowMode","params":[{"name":"channel","type":"InputChannel"},{"name":"seconds","type":"int"}],"type":"Updates"},{"id":"-183077365","method":"messages.getScheduledHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1111817116","method":"messages.getScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1120369398","method":"messages.sendScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"1504586518","method":"messages.deleteScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"473805619","method":"account.uploadTheme","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.0?InputFile"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"-2077048289","method":"account.createTheme","params":[{"name":"flags","type":"#"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?InputThemeSettings"}],"type":"Theme"},{"id":"1555261397","method":"account.updateTheme","params":[{"name":"flags","type":"#"},{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"slug","type":"flags.0?string"},{"name":"title","type":"flags.1?string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?InputThemeSettings"}],"type":"Theme"},{"id":"-229175188","method":"account.saveTheme","params":[{"name":"theme","type":"InputTheme"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"2061776695","method":"account.installTheme","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"format","type":"flags.1?string"},{"name":"theme","type":"flags.1?InputTheme"}],"type":"Bool"},{"id":"-1919060949","method":"account.getTheme","params":[{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"document_id","type":"long"}],"type":"Theme"},{"id":"1913054296","method":"account.getThemes","params":[{"name":"format","type":"string"},{"name":"hash","type":"long"}],"type":"account.Themes"},{"id":"-1210022402","method":"auth.exportLoginToken","params":[{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"except_ids","type":"Vector"}],"type":"auth.LoginToken"},{"id":"-1783866140","method":"auth.importLoginToken","params":[{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"-392909491","method":"auth.acceptLoginToken","params":[{"name":"token","type":"bytes"}],"type":"Authorization"},{"id":"-1250643605","method":"account.setContentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"}],"type":"Bool"},{"id":"-1952756306","method":"account.getContentSettings","params":[],"type":"account.ContentSettings"},{"id":"300429806","method":"channels.getInactiveChannels","params":[],"type":"messages.InactiveChats"},{"id":"1705865692","method":"account.getMultiWallPapers","params":[{"name":"wallpapers","type":"Vector"}],"type":"Vector"},{"id":"-1200736242","method":"messages.getPollVotes","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"option","type":"flags.0?bytes"},{"name":"offset","type":"flags.1?string"},{"name":"limit","type":"int"}],"type":"messages.VotesList"},{"id":"-1257951254","method":"messages.toggleStickerSets","params":[{"name":"flags","type":"#"},{"name":"uninstall","type":"flags.0?true"},{"name":"archive","type":"flags.1?true"},{"name":"unarchive","type":"flags.2?true"},{"name":"stickersets","type":"Vector"}],"type":"Bool"},{"id":"779736953","method":"payments.getBankCardData","params":[{"name":"number","type":"string"}],"type":"payments.BankCardData"},{"id":"-241247891","method":"messages.getDialogFilters","params":[],"type":"Vector"},{"id":"-1566780372","method":"messages.getSuggestedDialogFilters","params":[],"type":"Vector"},{"id":"450142282","method":"messages.updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Bool"},{"id":"-983318044","method":"messages.updateDialogFiltersOrder","params":[{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-1421720550","method":"stats.getBroadcastStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.BroadcastStats"},{"id":"1646092192","method":"stats.loadAsyncGraph","params":[{"name":"flags","type":"#"},{"name":"token","type":"string"},{"name":"x","type":"flags.0?long"}],"type":"StatsGraph"},{"id":"-1707717072","method":"stickers.setStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"85399130","method":"bots.setBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"},{"name":"commands","type":"Vector"}],"type":"Bool"},{"id":"2127598753","method":"messages.getOldFeaturedStickers","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"-1063816159","method":"help.getPromoData","params":[],"type":"help.PromoData"},{"id":"505748629","method":"help.hidePromoData","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-8744061","method":"phone.sendSignalingData","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"data","type":"bytes"}],"type":"Bool"},{"id":"-589330937","method":"stats.getMegagroupStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.MegagroupStats"},{"id":"-349483786","method":"account.getGlobalPrivacySettings","params":[],"type":"GlobalPrivacySettings"},{"id":"517647042","method":"account.setGlobalPrivacySettings","params":[{"name":"settings","type":"GlobalPrivacySettings"}],"type":"GlobalPrivacySettings"},{"id":"-183649631","method":"help.dismissSuggestion","params":[{"name":"peer","type":"InputPeer"},{"name":"suggestion","type":"string"}],"type":"Bool"},{"id":"1935116200","method":"help.getCountriesList","params":[{"name":"lang_code","type":"string"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"584962828","method":"messages.getReplies","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"1147761405","method":"messages.getDiscussionMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"messages.DiscussionMessage"},{"id":"-147740172","method":"messages.readDiscussion","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Bool"},{"id":"698914348","method":"contacts.blockFromReplies","params":[{"name":"flags","type":"#"},{"name":"delete_message","type":"flags.0?true"},{"name":"delete_history","type":"flags.1?true"},{"name":"report_spam","type":"flags.2?true"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1445996571","method":"stats.getMessagePublicForwards","params":[{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"-1226791947","method":"stats.getMessageStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"}],"type":"stats.MessageStats"},{"id":"-265962357","method":"messages.unpinAllMessages","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1221445336","method":"phone.createGroupCall","params":[{"name":"flags","type":"#"},{"name":"rtmp_stream","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"schedule_date","type":"flags.1?int"}],"type":"Updates"},{"id":"-1322057861","method":"phone.joinGroupCall","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"video_stopped","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_as","type":"InputPeer"},{"name":"invite_hash","type":"flags.1?string"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"1342404601","method":"phone.leaveGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"source","type":"int"}],"type":"Updates"},{"id":"2067345760","method":"phone.inviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"2054648117","method":"phone.discardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1958458429","method":"phone.toggleGroupCallSettings","params":[{"name":"flags","type":"#"},{"name":"reset_invite_hash","type":"flags.1?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_muted","type":"flags.0?Bool"}],"type":"Updates"},{"id":"68699611","method":"phone.getGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"limit","type":"int"}],"type":"phone.GroupCall"},{"id":"-984033109","method":"phone.getGroupParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"ids","type":"Vector"},{"name":"sources","type":"Vector"},{"name":"offset","type":"string"},{"name":"limit","type":"int"}],"type":"phone.GroupParticipants"},{"id":"-1248003721","method":"phone.checkGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"sources","type":"Vector"}],"type":"Vector"},{"id":"1540419152","method":"messages.deleteChat","params":[{"name":"chat_id","type":"long"}],"type":"Bool"},{"id":"-104078327","method":"messages.deletePhoneCallHistory","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"}],"type":"messages.AffectedFoundMessages"},{"id":"1140726259","method":"messages.checkHistoryImport","params":[{"name":"import_head","type":"string"}],"type":"messages.HistoryImportParsed"},{"id":"873008187","method":"messages.initHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"file","type":"InputFile"},{"name":"media_count","type":"int"}],"type":"messages.HistoryImport"},{"id":"713433234","method":"messages.uploadImportedMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"},{"name":"file_name","type":"string"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"-1271008444","method":"messages.startHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"}],"type":"Bool"},{"id":"-1565154314","method":"messages.getExportedChatInvites","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.3?true"},{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"},{"name":"offset_date","type":"flags.2?int"},{"name":"offset_link","type":"flags.2?string"},{"name":"limit","type":"int"}],"type":"messages.ExportedChatInvites"},{"id":"1937010524","method":"messages.getExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"messages.ExportedChatInvite"},{"id":"48562110","method":"messages.editExportedChatInvite","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"}],"type":"messages.ExportedChatInvite"},{"id":"1452833749","method":"messages.deleteRevokedExportedChatInvites","params":[{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"}],"type":"Bool"},{"id":"-731601877","method":"messages.deleteExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"Bool"},{"id":"958457583","method":"messages.getAdminsWithInvites","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.ChatAdminsWithInvites"},{"id":"654013065","method":"messages.getChatInviteImporters","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"},{"name":"offset_date","type":"int"},{"name":"offset_user","type":"InputUser"},{"name":"limit","type":"int"}],"type":"messages.ChatInviteImporters"},{"id":"-1207017500","method":"messages.setHistoryTTL","params":[{"name":"peer","type":"InputPeer"},{"name":"period","type":"int"}],"type":"Updates"},{"id":"-91437323","method":"account.reportProfilePhoto","params":[{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"InputPhoto"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"187239529","method":"channels.convertToGigagroup","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"1573261059","method":"messages.checkHistoryImportPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"-248985848","method":"phone.toggleGroupCallRecord","params":[{"name":"flags","type":"#"},{"name":"start","type":"flags.0?true"},{"name":"video","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"title","type":"flags.1?string"},{"name":"video_portrait","type":"flags.2?Bool"}],"type":"Updates"},{"id":"-1524155713","method":"phone.editGroupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"participant","type":"InputPeer"},{"name":"muted","type":"flags.0?Bool"},{"name":"volume","type":"flags.1?int"},{"name":"raise_hand","type":"flags.2?Bool"},{"name":"video_stopped","type":"flags.3?Bool"},{"name":"video_paused","type":"flags.4?Bool"},{"name":"presentation_paused","type":"flags.5?Bool"}],"type":"Updates"},{"id":"480685066","method":"phone.editGroupCallTitle","params":[{"name":"call","type":"InputGroupCall"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-277077702","method":"phone.getGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"}],"type":"phone.JoinAsPeers"},{"id":"-425040769","method":"phone.exportGroupCallInvite","params":[{"name":"flags","type":"#"},{"name":"can_self_unmute","type":"flags.0?true"},{"name":"call","type":"InputGroupCall"}],"type":"phone.ExportedGroupCallInvite"},{"id":"563885286","method":"phone.toggleGroupCallStartSubscription","params":[{"name":"call","type":"InputGroupCall"},{"name":"subscribed","type":"Bool"}],"type":"Updates"},{"id":"1451287362","method":"phone.startScheduledGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1465786252","method":"phone.saveDefaultGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"},{"name":"join_as","type":"InputPeer"}],"type":"Bool"},{"id":"-873829436","method":"phone.joinGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"475058500","method":"phone.leaveGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"676017721","method":"stickers.checkShortName","params":[{"name":"short_name","type":"string"}],"type":"Bool"},{"id":"1303364867","method":"stickers.suggestShortName","params":[{"name":"title","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"1032708345","method":"bots.resetBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Bool"},{"id":"-481554986","method":"bots.getBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Vector"},{"id":"-1828139493","method":"account.resetPassword","params":[],"type":"account.ResetPasswordResult"},{"id":"1284770294","method":"account.declinePasswordReset","params":[],"type":"Bool"},{"id":"221691769","method":"auth.checkRecoveryPassword","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"-690545285","method":"account.getChatThemes","params":[{"name":"hash","type":"int"}],"type":"account.ChatThemes"},{"id":"-432283329","method":"messages.setChatTheme","params":[{"name":"peer","type":"InputPeer"},{"name":"emoticon","type":"string"}],"type":"Updates"},{"id":"-1095836780","method":"channels.viewSponsoredMessage","params":[{"name":"channel","type":"InputChannel"},{"name":"random_id","type":"bytes"}],"type":"Bool"},{"id":"-333377601","method":"channels.getSponsoredMessages","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.SponsoredMessages"},{"id":"745510839","method":"messages.getMessageReadParticipants","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Vector"}]} \ No newline at end of file diff --git a/data/core.telegram.org/schema/mtproto.html b/data/core.telegram.org/schema/mtproto.html new file mode 100644 index 0000000000..74d5a9b3d4 --- /dev/null +++ b/data/core.telegram.org/schema/mtproto.html @@ -0,0 +1,204 @@ + + + + + Current MTProto TL-schema + + + + + + + + + + + + + +
+ +
+
+
+ +

Current MTProto TL-schema

+ +

Below you will find the current MTProto TL-schema. More details on TL »

+

See also the detailed schema in JSON »

+


+
int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+
+vector {t:Type} # [ t ] = Vector t;
+
+int128 4*[ int ] = Int128;
+int256 8*[ int ] = Int256;
+
+resPQ#05162463 nonce:int128 server_nonce:int128 pq:bytes server_public_key_fingerprints:Vector<long> = ResPQ;
+
+p_q_inner_data_dc#a9f55f95 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int = P_Q_inner_data;
+p_q_inner_data_temp_dc#56fddf88 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int expires_in:int = P_Q_inner_data;
+
+server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:bytes = Server_DH_Params;
+
+server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:bytes g_a:bytes server_time:int = Server_DH_inner_data;
+
+client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:bytes = Client_DH_Inner_Data;
+
+dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
+dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
+dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
+
+bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
+
+rpc_result#f35c6d01 req_msg_id:long result:Object = RpcResult;
+rpc_error#2144ca19 error_code:int error_message:string = RpcError;
+
+rpc_answer_unknown#5e2ad36e = RpcDropAnswer;
+rpc_answer_dropped_running#cd78e586 = RpcDropAnswer;
+rpc_answer_dropped#a43ad8b7 msg_id:long seq_no:int bytes:int = RpcDropAnswer;
+
+future_salt#0949d9dc valid_since:int valid_until:int salt:long = FutureSalt;
+future_salts#ae500895 req_msg_id:long now:int salts:vector<future_salt> = FutureSalts;
+
+pong#347773c5 msg_id:long ping_id:long = Pong;
+
+destroy_session_ok#e22045fc session_id:long = DestroySessionRes;
+destroy_session_none#62d350c9 session_id:long = DestroySessionRes;
+
+new_session_created#9ec20908 first_msg_id:long unique_id:long server_salt:long = NewSession;
+
+msg_container#73f1f8dc messages:vector<%Message> = MessageContainer;
+message msg_id:long seqno:int bytes:int body:Object = Message;
+msg_copy#e06046b2 orig_message:Message = MessageCopy;
+
+gzip_packed#3072cfa1 packed_data:bytes = Object;
+
+msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
+
+bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
+bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
+
+msg_resend_req#7d861a08 msg_ids:Vector<long> = MsgResendReq;
+msgs_state_req#da69fb52 msg_ids:Vector<long> = MsgsStateReq;
+msgs_state_info#04deb57d req_msg_id:long info:bytes = MsgsStateInfo;
+msgs_all_info#8cc0d131 msg_ids:Vector<long> info:bytes = MsgsAllInfo;
+msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+
+destroy_auth_key_ok#f660e1d4 = DestroyAuthKeyRes;
+destroy_auth_key_none#0a9f2259 = DestroyAuthKeyRes;
+destroy_auth_key_fail#ea109b13 = DestroyAuthKeyRes;
+
+---functions---
+
+req_pq_multi#be7e8ef1 nonce:int128 = ResPQ;
+
+req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:bytes q:bytes public_key_fingerprint:long encrypted_data:bytes = Server_DH_Params;
+
+set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:bytes = Set_client_DH_params_answer;
+
+rpc_drop_answer#58e4a740 req_msg_id:long = RpcDropAnswer;
+get_future_salts#b921bd04 num:int = FutureSalts;
+ping#7abe77ec ping_id:long = Pong;
+ping_delay_disconnect#f3427b8c ping_id:long disconnect_delay:int = Pong;
+destroy_session#e7512126 session_id:long = DestroySessionRes;
+
+http_wait#9299359f max_delay:int wait_after:int max_wait:int = HttpWait;
+
+destroy_auth_key#d1435160 = DestroyAuthKeyRes;
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/stickers.html b/data/core.telegram.org/stickers.html new file mode 100644 index 0000000000..b1683a7d5b --- /dev/null +++ b/data/core.telegram.org/stickers.html @@ -0,0 +1,249 @@ + + + + + Telegram Stickers + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram Stickers

+ +

All users can create, send and share custom artwork using Telegram's open Sticker Platform. Stickers take many forms – from basic images to stunning vector animations.

+

To start building your own custom sets, click below:

+ +

Animated Stickers

+

Telegram stickers can move with smooth 60 FPS animations to bring your characters to life in high-resolution.

+
+

Animated stickers use Telegram's unique .TGS format – click here for Video Stickers made in .WEBM format.

+
+

Creating Animated Stickers

+

To create vector animated stickers you will need the following:

+
    +
  1. Any vector graphics editor that allows exporting vector objects to Adobe After Effects to turn them into animations.
  2. +
  3. Adobe After Effects.
  4. +
  5. The Bodymovin-TG plugin, a fork of Bodymovin for Adobe After Effects that can be used to export animations to .TGS, the Telegram animated sticker format.
  6. +
+
+

The Lottie-based .TGS format allows for incredibly detailed stickers that are less than 30 KB in size – six times smaller than the average photo.

+
+

Animated Sticker Requirements

+
    +
  • Sticker/canvas size must be 512х512 pixels.
  • +
  • Sticker objects must not leave the canvas.
  • +
  • Animation length must not exceed 3 seconds.
  • +
  • All animations must be looped.
  • +
  • Sticker size must not exceed 64 KB after rendering in Bodymovin.
  • +
  • All animations must run at 60 Frames Per Second.
  • +
  • You must not use the following Adobe After Effects functionality when animating your stickers: Auto-bezier keys, Expressions, Masks, Layer Effects, Images, Solids, Texts, 3D Layers, Merge Paths, Star Shapes, Gradient Strokes, Repeaters, Time Stretching, Time Remapping, Auto-Oriented Layers.
  • +
+

Uploading Animated Stickers

+

When your stickers are ready, send the /newanimated command to the @Stickers bot – then send it the .TGS files.

+

Your set will need an icon. Icons for animated sticker sets must be 100x100 pixels, with a looped animation not exceeding 3 seconds.

+
+

Video Stickers

+

Video Stickers are built with .WEBM – an open-source format that is compatible with many graphics editors to create high-detail images. Requires Telegram 8.5 or higher.

+ + +

Creating Video Stickers

+

To create Video Stickers, you only need editing software that lets you export your project as a .WEBM video file (alpha channel no longer required).

+

Video Sticker Requirements

+
+

See this Encoding .WEBM with VP9 Guide for details

+
+
    +
  • One side of the sticker must be exactly 512 pixels in size – the other side can be 512 pixels or less.
  • +
  • Video duration must not exceed 3 seconds.
  • +
  • Frame rate can be up to 30 FPS.
  • +
  • Video must have a transparent layer (this is no longer required).
  • +
  • Video should be looped for optimal user experience.
  • +
  • Video size should not exceed 256 KB.
  • +
  • Video must be in .WEBM format encoded with the VP9 codec.
  • +
  • Video must have no audio stream.
  • +
+

Uploading Video Stickers

+

Once your stickers are ready, send the /newvideo command to the @Stickers bot – then send it the .WEBM files.

+

Your set will need a .WEBM icon. Icons for video sticker sets must be 100x100 pixels, with a looped animation not exceeding 3 seconds.

+
+

Static Stickers

+

Turn your favorite drawings and memes into packs of images that are easily accessible on any device – no more digging through your gallery.

+

Creating Static Stickers

+

To create static stickers for the Telegram platform, you only need an image editor that lets you export in .PNG or .WEBP format.

+

Static Sticker Requirements

+
    +
  • One side of the sticker must be exactly 512 pixels in size – the other side can be 512 pixels or less.
  • +
  • The image file must be in either .PNG or .WEBP format.
  • +
+
+

Tip: a transparent background, white stroke and black shadow effect will make your sticker stand out.

+
+

Uploading Static Stickers

+

Once your stickers are ready, start a chat with the @Stickers bot and send the command /newpack. Your sticker set can also have a custom icon – a 100x100 pixel image in .PNG or .WEBP format.

+
+

For more info about using the @Stickers bot, click here.

+
+
+

Using the @Stickers Bot

+

Publishing and editing sticker packs is simple and automated, thanks to the @Stickers bot. It can also show you detailed stats for stickers and packs.

+

Publishing a Sticker Pack

+

Once you open the bot, press the Start button or send /start. The bot will reply, describing its different commands. It will walk you through step by step, but here's a quick guide:

+
    +
  • Open the bot menu in the message bar and select the /newpack command to start uploading static stickers. For animated stickers use /newanimated, or /newvideo for video stickers.
  • +
  • Give your sticker pack a name – this name will appear as the title for your pack in the sticker panel.
  • +
  • Send your first sticker file – an image file, .TGS file, or .WEBM file. Using one of the Desktop or Web apps is strongly recommended.
  • +
  • Choose an emoji that corresponds to your sticker – this lets users quickly find it with sticker suggestions.
  • +
  • Continue uploading all your sticker files.
  • +
  • When you're done uploading, send the /publish command.
  • +
  • Set an icon for your pack – static sticker packs can /skip this step, but it is required for animated or video stickers.
  • +
  • Choose a short name for your sticker pack – it will be used to create a shareable link for the pack like t.me/addstickers/HotCherry. Congratulations! Your stickers are ready for the world.
  • +
+
+

After your pack is finished, you can send /start again to see the full list of commands, or use the bot menu to create another pack, edit an existing pack, or see statistics.

+
+

Editing a Sticker Pack

+

Once you've created one or more packs, you can add, edit or replace stickers in your existing sets.

+
    +
  • Use /addsticker if you have more artwork you'd like to add to a set. Choose one of your packs from the list – the upload process is exactly the same as before.
  • +
  • Use /editsticker to change the emoji you assigned to a sticker – select the pack and sticker, or simply send the intended sticker from your panel.
  • +
  • Use /replacesticker if you want to swap out an older sticker for an updated version.
  • +
  • Use /ordersticker to change the order of stickers in your pack. Choose the pack and one of the stickers, then choose another sticker to appear before it (to the left) in the panel.
  • +
  • Use /delsticker to remove a sticker from the pack – you can always use /addsticker to add it again if you change your mind.
  • +
  • Use /seticon to set an icon for your pack or to change the icon. Static sticker packs without a custom icon will use the first sticker as its icon.
  • +
+
+

Edits to your sticker packs may take up to an hour to update for all users.

+
+

Sticker Stats

+

There are a number of commands that let you see statistics for your stickers – here's what they all do:

+
    +
  • /packstats shows how many times your pack was used, installed and removed – both recently and overall.
  • +
  • /stats shows how many times an individual sticker has been sent.
  • +
  • /top shows the most popular stickers from all your packs.
  • +
  • /packtop shows your most popular sticker packs and their individual stats.
  • +
  • /topbypack shows the top stickers from a specific sticker pack.
  • +
  • /packusagetop shows your most popular packs by recent usage.
  • +
+
+

You can filter the results of /top, /packtop, /topbypack and /packusagetop. For example /top 20 would show your top 20 stickers, and /topbypack -5 would show the 5 least popular stickers from a pack.

+
+

Importing Stickers From Other Apps

+

Developers can build apps to automate importing stickers using Telegram’s API. With these tools, users can instantly bring their favorite stickers to Telegram.

+

For Developers

+

As of version 7.8, Telegram apps support a simple API for importing stickers. Developers can use this to build apps or add tools to apps that let users instantly transfer stickers to Telegram – or create custom stickers from photos or videos.

+
+

Click here for more information about developing apps for importing stickers.

+
+

For Users

+

Users can find apps that allow them to import stickers or quickly generate their own. They can also easily publish custom stickers with the @Stickers bot using .PNG, .WEBP or .WEBM files for stickers from other apps.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/stickers/webm-vp9-encoding.html b/data/core.telegram.org/stickers/webm-vp9-encoding.html new file mode 100644 index 0000000000..adb9aa235c --- /dev/null +++ b/data/core.telegram.org/stickers/webm-vp9-encoding.html @@ -0,0 +1,159 @@ + + + + + Encoding Video Stickers with .WEBM and VP9 + + + + + + + + + + + + + +
+ +
+
+
+
+

Encoding Video Stickers with .WEBM and VP9

+ +

The Video Sticker format allows anyone to easily create high-detail animations that users can send and share instantly in Telegram.

+

Video Sticker Requirements

+
    +
  • Video must be in .WEBM format, up to 30 FPS.
  • +
  • Video must be encoded with the VP9 codec.
  • +
  • Video must have no audio stream.
  • +
  • One side must be 512 pixels in size – the other side can be 512 pixels or less.
  • +
  • Duration must not exceed 3 seconds.
  • +
  • Video must have a transparent layer (this is no longer required).
  • +
  • Video should be looped for optimal user experience.
  • +
  • Video size should not exceed 256 KB after encoding.
  • +
+

Encoding Video Files

+

You can design your animation in your preferred app – but depending on the app’s export settings, you may need an encoding program to create the final file.

+
+

Programs like Handbrake or ffmpeg natively support .WEBM encoding with VP9.

+
+

Encoding with Adobe Media Encoder

+

Adobe’s Media Encoder requires a plug-in to support .WEBM encoding. Here is a modified version of a plug-in by fnord software that you can install to render your video stickers with Media Encoder.

+ +

After the plug-in is installed, .WEBM will appear in the list of formats in the Queue tab.

+
+

On macOS, you may need to go to Settings > Security & Privacy to approve installation.

+
+

Render Settings

+

If it’s your first time working with encoding software, here are some tips that might help:

+
    +
  • Make sure to check that VP9 is selected in the codec settings – some apps may default to VP8.
  • +
  • Make sure to remove any audio streams (uncheck ‘Export Audio’ in Adobe programs).
  • +
  • Make sure the frame rate is a constant 30 FPS.
  • +
  • Use Constant Quality and a lower (or lowest) quality setting – size dramatically decreases without affecting fidelity.
  • +
  • In Media Encoder, make sure your Renderer is set to ‘Software Only’.
  • +
  • If your file fails to render, try importing it as a PNG Sequence.
  • +
+
+

After Effects projects integrate directly with Media Encoder via File > Export > Add to Media Encoder Queue.

+
+

Uploading Video Stickers

+

The @Stickers bot lets you quickly publish and manage your sticker packs. Start a chat with it on Telegram and it will walk you through the process. For step-by-step instructions and more information, see this guide.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/tdlib.html b/data/core.telegram.org/tdlib.html new file mode 100644 index 0000000000..a48649c3b4 --- /dev/null +++ b/data/core.telegram.org/tdlib.html @@ -0,0 +1,147 @@ + + + + + Telegram Database Library + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram Database Library

+ +
+ +
+ +

TDLib (Telegram Database Library) is a cross-platform, fully functional Telegram client. We designed it to help third-party developers create their own custom apps using the Telegram platform.

+
+

Read about TDLib on the Telegram blog »

+
+

TDLib Advantages

+
    +
  • Cross-platform. TDLib can be used on Android, iOS, Windows, macOS, Linux, WebAssembly, FreeBSD, Windows Phone, watchOS, tvOS, Tizen, Cygwin. It should also work on other *nix systems with or without minimal effort.
  • +
  • Multilanguage. TDLib can be easily used with any programming language that is able to execute C functions. Additionally it already has native bindings to Java (using JNI) and C# (using C++/CLI).
  • +
  • Easy to use. TDLib takes care of all network implementation details, encryption and local data storage.
  • +
  • High-performance. In the Telegram Bot API, each TDLib instance handles more than 24,000 active bots simultaneously.
  • +
  • Well-documented. All TDLib API methods and public interfaces are fully documented.
  • +
  • Consistent. TDLib guarantees that all updates will be delivered in the right order.
  • +
  • Reliable. TDLib remains stable on slow and unreliable Internet connections.
  • +
  • Secure: All local data is encrypted using a user-provided encryption key.
  • +
  • Fully-asynchronous. Requests to TDLib don't block each other or anything else, responses will be sent when they are available.
  • +
+
+

Getting started with TDLib »

+
+

Resources

+

TDLib is fully open source, all code is available on GitHub.

+

See also:

+ +
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/tdlib/getting-started.html b/data/core.telegram.org/tdlib/getting-started.html new file mode 100644 index 0000000000..d5ee3a802d --- /dev/null +++ b/data/core.telegram.org/tdlib/getting-started.html @@ -0,0 +1,198 @@ + + + + + Getting started with TDLib + + + + + + + + + + + + + +
+ +
+
+
+ +

Getting started with TDLib

+ +
+ +

TDLib is a fully functional Telegram client which takes care of all networking, local storage and data consistency details. In this tutorial we describe the main concepts understanding of which is required for efficient TDLib usage.

+

TDLib interface

+

In this text, Client means an interface for interaction with a TDLib instance and Application means the program that uses TDLib to interact with Telegram.

+

The main TDLib API is fully-asyncronous. An Application can send a request to TDLib through ClientManager.send method and receive a response asynchronously through the ClientManager.receive method when it becomes available. The exact naming of these methods and the way in which requests are matched with responses is different for different TDLib interfaces, but the concept as a whole remains the same. For example, in TDLib JSON interface these methods are called td_send and td_receive, and their @extra field must be used to match requests with the corresponding responses.

+

In a high-level interface used by an Application the matching of responses with corresponding requests is often automated and transformed by some wrapper into a call to a continuation, a callback, a Promise or a Future to simplify the handling of responses.

+

Aside from responses to requests, an Application receives a lot of important data through incoming updates. Updates are used to pass new data from TDLib to the Application and often control the behavior of the Application, leaving no chance to implement something wrong. The correct handling of updates is crucial for creating an Application that is efficient and works correctly.

+
+

You can find a list of all available TDLib API methods in our web-documentation. You can also find the descriptions of all available TDLib methods and classes in the TDLIB API scheme.

+

TDLib can be used from any programming language. You can find a lot of examples of TDLib-based frameworks in various programming languages in our examples section.

+
+

TDLib glossary

+

This section describes the basic notions required for understanding the TDLib API. If you have used the TDLib-based Telegram Bot API most of them should be already familiar to you.

+

Telegram is a messenger, so the main object is a message. Each message belongs to some chat and has a unique identifier within that chat. Messages inside a chat must be sorted by that identifier. Telegram supports many different kinds of messages, so a message can have many different kinds of message content. Currently there are more than 45 different kinds of message content, for example messageText for text messages, messagePhoto for photos, or messageScreenshotTaken for notifications about screenshots taken by the other party.

+

A Telegram user is called user. Each user has a unique identifier and a first name, and can also have an optional last name, username and profile photo among other useful fields. Bot is a special type of user which can be controlled through the Telegram Bot API.

+

Each chat has members, i.e. users that immediately receive all messages sent to the chat. Currently there are 6 possible chat member statuses which describe different rights and restrictions a user can have in a chat, ranging from the owner of the chat who has more rights in the chat than any other user, to a user banned in the chat who is banned in the chat and can't return to it by self or even view chat messages, even if the chat is public.

+

As noted earlier, each message belongs to a chat. Currently there are 4 different types of chats on Telegram:

+
    +
  • Private chats are ordinary one-to-one chats with another user (or with oneself in the case of the special “Saved messages” chat).
  • +
  • Basic groups are basic groups with 0-200 members. Every basic group member has their own copy of the message history, so new basic group members may not see older messages (unless another user forwards their own copy to them).
  • +
  • Supergroups are groups with up to 200000 members who share a common message history, so new supergroup members can see all the previously sent messages (unless this is explicitly forbidden by the chat creator). There are special kinds of supergroups, called broadcast groups and channels, which can have an unlimited number of members and where only the chat creator and some chat administrators can write. All other chat members can only read messages in channel and broadcast group chats.
  • +
  • Secret chats are end-to-end encrypted one-to-one chats with another user, available only on the device which was used to initiate and accept the chat.
  • +
+

Each chat has a unique identifier, a title and an optional chat photo. Chats comprise sorted lists shown to the user, position in which is determined, roughly speaking, by the time of latest activity. The correct order of chats in chat lists is maintained by TDLib, so the Application only needs to listen to updates that change the chat.positions field and sort all chats by the pair (position.order, chat.id) in a given position.list.

+

Messages, chat photos and many other objects can have a file inside of them. Each file has an identifier and may be available locally on a local storage or remotely on a cloud server. A file can be usually downloaded to the local storage or uploaded to Telegram cloud servers.

+

Messages with media content like photos or videos can have a short accompanying text called caption. The texts of text messages and media captions can contain fragments, which must be formatted in some unusual way. These fragments are called text entities and the combination of a text and its entities are referred together as a formatted text.

+

TDLib sends a lot of important data to the Application through updates. For example, if there is a user unknown to the Application, or some data about a user has changed, then TDLib immediately sends an updateUser to the Application.

+
+

You can find list of all currently available updates here »

+
+

User authorization

+

Authorization is an example of a behavior, which is controlled by TDLib through updates. Whenever an action is required to proceed with user authorization, the Application receives an updateAuthorizationState with the description of the current AuthorizationState. The Application only needs to handle this update appropriately to correctly implement user authorization.

+

The first authorization state received by the Application is always of the type authorizationStateWaitTdlibParameters. When it is received, the Application must provide parameters for TDLib initialization by calling the setTdlibParameters method. In this method the Application will need to specify, among other parameters:

+
    +
  • api_id — Application identifier for accessing the Telegram API, which can be obtained at https://my.telegram.org.
  • +
  • api_hash — Hash of the Application identifier for accessing the Telegram API, which can be obtained at https://my.telegram.org.
  • +
  • database_directory — The path to the directory on the local disk where the TDLib database is to be stored; must point to a writable directory.
  • +
  • use_message_database — If set to true, the library will maintain a local cache of chats and messages.
  • +
  • use_secret_chats — If set to true, support for secret chats will be enabled.
  • +
  • system_language_code — IETF language tag of the user's operating system language, like “en-GB”.
  • +
  • device_model — Model of the device the Application is being run on, like “iPhone Z”.
  • +
+

After call to setTdlibParameters in case of success Application will receive updateAuthorizationState with new state and just needs to handle that update, nothing should be done explicitly. If setTdlibParameters fails, then authorization state is not changed and the Application must try to handle the current authorization state again.

+

The second received authorization state is always authorizationStateWaitEncryptionKey. When it is received, the database encryption key must be provided through a call to checkDatabaseEncryptionKey. For most mobile apps, you can provide an empty database encryption key here (more info). If user isn't authorized yet, then some of authorizationStateWaitPhoneNumber, authorizationStateWaitCode, authorizationStateWaitRegistration and authorizationStateWaitPassword authorization states may be received. After completing these authorization steps, the Application will receive authorizationStateReady, meaning that authorization was successful and ordinary requests can be sent now.

+
+

You can find complete examples of user authorization in our Java and C# examples.

+
+

Sending a message

+

To send any kind of message, the Application needs to call the method sendMessage providing a chat identifier and the content of the message to be sent. For example, the Application can send a text message using inputMessageText class as input message content, a photo using inputMessagePhoto, or a location using inputMessageLocation. The Application can use inputFileLocal as InputFile in these objects to send a local file from the local storage.

+
+

You can find examples of sending a text message in our Java and C# examples.

+
+

Handling updates

+

All updates and responses to requests must be handled in the order they are received. Here is a list of the most important updates and how they must be handled:

+
    +
  • updateAuthorizationState — The handling of this update is essential for correct user authorization.
  • +
  • updateNewChat — This update is received whenever a new chat is discovered. This update is guaranteed to come before the chat identifier is returned to the Application. So, whenever an Application receives a chat_id, it never needs to use a getChat request to receive the chat object. Instead it must maintain a cache of chats received through this update and take all the necessary data about chats from this cache.
  • +
  • updateUser — This update is received whenever a new user has been discovered or some data about a known user has changed. This update is guaranteed to come before the user identifier is returned to the Application. So, whenever an Application receives a user_id, it never needs to use the getUser request to receive the user object. Instead it must maintain a cache of users received through this update and take all the necessary data about users from this cache.
  • +
  • updateBasicGroup — This update is received whenever a new basic group has been discovered or some data about a known basic group has changed. This update is guaranteed to come before the basic group identifier is returned to the Application. So, whenever an Application receives a basic_group_id, it never needs to use the getBasicGroup request to receive the basicGroup object. Instead it must maintain a cache of basic groups received through this update and take all the necessary data about basic groups from this cache.
  • +
  • updateSupergroup — This update is received whenever a new supergroup has been discovered or some data about a known supergroup has changed. This update is guaranteed to come before the supergroup identifier is returned to the Application. So, whenever an Application receives a supergroup_id, it never needs to use the getSupergroup request to receive the supergroup object. Instead it must maintain a cache of supergroups received through this update and take all the necessary data about supergroups from this cache.
  • +
  • updateSecretChat — This update is received whenever a new secret chat has been discovered or some data about a known secret chat has changed. This update is guaranteed to come before the secret chat identifier is returned to the Application. So, whenever an Application receives a secret_chat_id, it never needs to use the getSecretChat request to receive the secret chat object. Instead it must maintain a cache of secret chats received through this update and take all the necessary data about secret chats from this cache.
  • +
  • updateNewMessage — This update is received whenever a new message is added to a chat.
  • +
  • updateMessageSendSucceeded — This update is received whenever a message is successfully sent.
  • +
  • updateMessageContent — This update is received whenever the content of a message changes.
  • +
  • updateFile — This update is received whenever information about a file is updated. The handling of this update is essential to follow the progress of files being downloaded or uploaded.
  • +
  • updateChatTitle, updateChatPhoto, updateChatPermissions, updateChatLastMessage, updateChatPosition, updateChatReadInbox, updateChatReadOutbox, updateChatActionBar, updateChatDraftMessage, updateChatMessageSender, updateChatMessageTtl, updateChatNotificationSettings, updateChatPendingJoinRequests, updateChatReplyMarkup, updateChatTheme, updateChatUnreadMentionCount, updateChatVideoChat, updateChatDefaultDisableNotification, updateChatHasProtectedContent, updateChatHasScheduledMessages, updateChatIsBlocked, updateChatIsMarkedAsUnread — These updates are received whenever some information about a chat changes, the chats cache must be updated accordingly
  • +
+
+

For a full list of currently available updates see the documentation for the Update class.

+

You can find an example of correct handling of some updates in our Java example.

+
+

Getting the lists of chats

+

Currently there are 3 different types of chat lists:
- Main chat list.
- Archive chat list.
- A folder chat list.

+

The positions of chats in chat lists are managed by TDLib, so the Application only needs to listen to updates that change the chat.positions field, maintain the list of all chats, sorted by the pair (position.order, chat.id) in descending order, and call loadChats only if more chats are needed. For optimal performance, the number of loaded chats is chosen by TDLib and can be smaller than the specified limit. If the Application needs more chats, it must send another loadChats request.

+
+

You can find an example of retrieving the Main chat list in our Java example.

+
+

Getting chat messages

+

The Application can use the method getChatHistory to get messages in a chat. The messages will be returned in the reverse chronological order (i.e., in descending order of message_id). The Application can pass from_message_id == 0 to get messages from the last message. To get more messages than can be returned in one response, the Application needs to pass the identifier of the last message it has received as from_message_id to next request. For optimal performance, the number of the returned messages is chosen by TDLib and can be smaller than the specified limit. If the Application needs more messages, it needs to adjust the from_message_id parameter and repeat the request.

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/tdlib/notification-api.html b/data/core.telegram.org/tdlib/notification-api.html new file mode 100644 index 0000000000..f2baabbdb3 --- /dev/null +++ b/data/core.telegram.org/tdlib/notification-api.html @@ -0,0 +1,210 @@ + + + + + Notification API + + + + + + + + + + + + + +
+ +
+
+
+
+

Notification API

+ +

This article describes the TDLib Notification API introduced in TDLib 1.4.0.

+

Notification API overview

+

TDLib takes care of everything that is related to handling notifications (as usually, except for how exactly the notifications will be shown to the user). TDLib controls when notifications are shown to the user, when they are edited and removed, guarantees consistency of notifications with the database state and persistence of active notifications between client restarts.

+

All notifications shown to the user are combined into notification groups. For example, notifications about ordinary messages from the one chat belong to one notification group. This grouping is done automatically by TDLib based on message content and the user's notification settings. Currently, there are 4 different notification group types:

+
    +
  • Messages notification groups contain notifications with ordinary unread messages from a chat.
  • +
  • Mentions notification groups contain notifications with unread mentions of the current user, replies to their messages, and notifications about pinned messages in a chat.
  • +
  • SecretChat notification groups contain a single notification about creating a new secret chat.
  • +
  • Calls notification groups contain notifications about received calls in a chat.
  • +
+

TDLib ensures that the number of notification groups shown to the user any given moment is limited by the value of the notification_group_count_max option and that the number of active notifications, shown to the user in a notification group at any given time, is limited by the value of the notification_group_size_max option. Whenever the number of notification groups with active notifications exceeds notification_group_count_max, TDLib sends an update hiding all notifications from the oldest group. If subsequently all notifications are hidden in some other group, that first group can be silently brought back by an update from TDLib. Similarly, whenever the number of active notifications in a group exceeds notification_group_size_max, TDLib sends an update hiding the oldest notifications in the group. If subsequently some newer notifications are removed from the group, older notifications can be silently brought back by an update from TDLib.

+

To enable the TDLib Notificaition API you need to set option notification_group_count_max to a positive value, to disable the Notification API you can change the option value back to 0 or set the option value to empty.

+

Every notification group has a unique ID, which is a persistent small integer number, assigned consequently from 1. The client should not assume that the group‘s type and other fields are fixed, because TDLib may reuse the notification group ID whenever it’s known that the group will never be used again in the future. Every notification belongs to a notification group and has a globally unique ID, which is a persistent small integer number, assigned consequently from 1. Notification IDs are never reused and can be used together with their notification group ID to uniquely identify a notification. Within a notification group, notifications must be shown in the order defined by their IDs. If notification grouping isn't available in your operating system, the existence of notification groups can be safely ignored and notifications can be handled separately just by their unique ID.

+

Currently, there are 4 different kinds of notifications:

+
    +
  • NewMessage notifications contain the full information about a new incoming message received from the server. They may be located in Messages and Mentions notification groups.
  • +
  • NewPushMessage notifications contain information about a new incoming message received in a push notification. They contain only partial data about the message and will be replaced by NewMessage notifications as soon as the client downloads the necessary data. They may be located in Messages and Mentions notification groups.
  • +
  • NewSecretChat notifications inform about creating a new secret chat. Only one will be located in each SecretChat notification group. The group may be reused as soon as the notification is removed.
  • +
  • NewCall notifications contain information about a new incoming call. They are located in a Calls notification group. The group may be reused as soon as the notifications are removed.
  • +
+

Messages from new push message notifications will not be shown in the chat message list, but their message identifiers are known and they can be replied to and used in ViewMessages calls anyway.

+

Handling Notification API updates

+

Notification API introduced 4 new updates from TDLib, namely updateActiveNotifications, updateNotificationGroup, updateNotification and updateHavePendingNotifications.

+

If Notification API is enabled, the client receives an updateActiveNotifications update on startup, containing all notifications that are to be shown to the user. The client needs to synchronize the list of notifications that is shown to the user with the list received in updateActiveNotifications and save information about all active notifications in memory, because subsequent updates will contain only changes to the list of active notifications.

+

Whenever a notification is added to a group or is removed from a group, TDLib sends an updateNotificationGroup update to the client. Aside from the list of added notifications and list of identifiers of removed notifications, the update contains full information about the new type of the notification group, the identifier of the chat to which all notifications in the group now belong, the identifier of the chat the notification settings of which must be used to show the notification, a flag determining whether the notification must be shown with or without sound and the new total count of unread notifications in the group. Be aware that the total count of unread notifications in a group can be higher than the number of active notifications. Also note that some old notifications can be added through updateNotificationGroup when newer notifications are removed, so the client must ensure the correct notification order based on notification identifiers. Whenever possible, updateNotificationGroup updates for a group are combined into a single update, so the client can apply the changes together. TDLib also controls the delay before notifications are shown to the user in order to give them a chance to read the messages from a different device before the notification is shown, therefore the updates should be processed on the client side immediately without any additional delays.

+

Whenever an active notification is changed, TDLib sends an updateNotification update to the client. The update contains new content of the notification. The client should be ready to handle the change of notification type, for example, from NewPushMessage to NewMessage.

+

Whenever there are some received but delayed notifications or there can be some yet unreceived notifications because of unavailable network connection to the Telegram servers, TDLib informs the client about that via updateHavePendingNotifications update. Client is supposed to keep the application running in order to receive all delayed notifications. If there is no possibility to keep the application running, the client can close the TDLib instance in order to immediately receive all delayed notification updates.

+

TDLib tries to ensure that whenever a notification about a pinned message is sent, the pinned message is already available locally in the memory, so the client can use a new request getMessageLocally to get the pinned message. Also, updateNotification will be sent whenever pinned message is changed, despite that the notification itself wasn't changed.

+

Customizing the Notification API

+

The client controls the maximum number of active notification groups by using the option notification_group_count_max. This option's value defaults to 0, i.e. there are no active notification groups and the Notification API is effectively disabled. Any integer value between 0 and 25 can be used as the value of the option. Values above 25 are not allowed because most operating systems will not show so many notification groups anyway.

+

The client also controls the maximum number of active notifications in a group by using the option notification_group_size_max. This option's value defaults to 10 and can be set to any integer value between 1 and 25. Values above 25 are not allowed, because most operating systems will not show so many notifications in a group anyway.

+

The user may choose to show pinned messages or mentions among ordinary messages in the Messages notification group instead of the Mentions notification group and choose to not apply notification settings from the sender's private chat to them. This can be done on a per chat basis or for the whole chats notification scope via the new options disable_pinned_message_notifications and disable_mention_notifications which were added to chatNotificationSettings and scopeNotificationSettings classes.

+

Handling push notifications

+

In order to support multiple accounts in one app, the method registerDevice now returns a globally unique identifier of the push notification subscription. This identifier can be used to match a push notification with the corresponding account and process the notification only by the account for which the notification was sent.

+

Whenever a push notification is received, the client needs to call the synchronous method getPushReceiverId with the payload of the push notification. The method will return a globally unique identifier of the push notification subscription (aka push receiver ID), which can be used to find the TDLib instance which needs to be launched and used to process the push notification. If the method returns 0 as a push receiver ID, then the push notification should be processed by all clients (this usually happens when there is only one client).

+

To process a notification, the method processPushNotification needs to be called in the TDLib instance (or instances) found by push receiver ID. This method can be called before authorization and its execution will be automatically postponed until TDLib initialization. The method returns the result only after all updates caused by the push notification have been sent and the TDLib instance can be safely closed. If the method returns an error with the code 406, then the push notification is known to be unsupported and connection to the server is required to fetch new data. If any other error is returned, an error occurred while processing the push notification, i.e. the notification payload has failed to decrypt or parse. In that case, connection to the server isn't required, but there can be new notifications there. After a successful response from processPushNotification the TDLib instance can be immediately closed in order to reduce battery usage. Alternatively, the client can wait for an updateHavePendingNotifications update telling that there are no more delayed or unreceived notifications.

+

Android and iOS clients can opt-in to receive end-to-end encrypted push notifications via a Firebase Cloud Messaging or Apple Push Notification service VoIP notifications while subscribing to push notifications through registerDevice method. In case of Firebase Cloud Messaging, if end-to-end encrypted push notifications are disabled, push notifications are sent without content, so there no notifications of the type NewPushMessage will be created, the client will always need to connect to Telegram servers to download new messages whenever a push notification is received.

+

Examples of push notification payloads, which are accepted by TDLib:

+
{
+  "date": 1234567890,
+  "data": {
+    "custom": {
+      "msg_id": "1234567",
+      "from_id": "12345678",
+      "mtpeer": {
+        "ah": "-1234567",
+        "ph": {
+          "volume_id": "987654321",
+          "local_id": "98765",
+          "secret": "998877665544332211",
+          "file_reference": "ABCDEFGHIJKLMNOPQRSTUVWXYZ",
+          "dc_id": 6,
+          "_": "fileLocation"
+        }
+      }
+    },
+    "badge": "239",
+    "loc_key": "MESSAGE_TEXT",
+    "loc_args": [
+      "First name Last name",
+      "qwerty"
+    ],
+    "line1": "First name Last name",
+    "line2": "qwerty",
+    "random_id": 728931540,
+    "text": "First name Last name: qwerty",
+    "system": "Windows 10.0.20573.1"
+  }
+}
+{
+  "google.sent_time": 1234567890123,
+  "p": "jdTXkJnEMUTK6R82AB-55bLA3U_RB-2K-CLDz7mWp7ckjMIfnCoHEcm710SkN"
+}
+{
+  "date": 1234567890,
+  "loc_key": "CHAT_MESSAGE_TEXT",
+  "loc_args": [
+    "First name Last name",
+    "Chat title",
+    "qwerty"
+  ],
+  "custom": {
+    "msg_id": "1234567",
+    "channel_id": "56781234",
+    "chat_from_id": "12345678",
+    "mention": "1"
+  },
+  "badge": "239"
+}
+

Users removing active notifications

+

There are two methods for removing notifications from the list of active notifications when they are hidden by the user. If the user removes a single notification, it can be removed by calling the method removeNotification. If the user dismisses the whole notification group, this can be achieved using the method removeNotificationGroup. Removed notifications will never return to the list of active notifications, but can be still counted in the total count of unread notifications of the group.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/tdlib/options.html b/data/core.telegram.org/tdlib/options.html new file mode 100644 index 0000000000..925f0a5425 --- /dev/null +++ b/data/core.telegram.org/tdlib/options.html @@ -0,0 +1,501 @@ + + + + + TDLib options + + + + + + + + + + + + + +
+ +
+
+
+ +

TDLib options

+ +

TDLib has many options that affect the behavior of the library. Each option has a name and a value. Value may be of one of the following types:

+ + + + + + + + + + + + + + + + + + + + + + + +
Type of valueDefault valueValue range
Integer064-bit integer
BooleanfalseTrue or false
StringAny Unicode string
+

List of options supported by TDLib

+

Options not mentioned in this list may be safely ignored.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeWritableDescription
always_parse_markdownBooleanYesIf true, text entities will be automatically parsed in all inputMessageText objects
archive_and_mute_new_chats_from_unknown_usersBooleanYesIf true, new chats from non-contacts will be automatically archived and muted. The option can be set only if the option “can_archive_and_mute_new_chats_from_unknown_users” is true. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
disable_animated_emojiBooleanYesIf true, animated emoji will be disabled and shown as plain emoji
disable_contact_registered_notificationsBooleanYesIf true, notifications about the user's contacts who have joined Telegram will be disabled. User will still receive the corresponding message in the private chat. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
disable_persistent_network_statisticsBooleanYesIf true, persistent network statistics will be disabled, which significantly reduces disk usage
disable_sent_scheduled_message_notificationsBooleanYesIf true, notifications about outgoing scheduled messages that were sent will be disabled
disable_time_adjustment_protectionBooleanYesIf true, protection from external time adjustment will be disabled, which significantly reduces disk usage
disable_top_chatsBooleanYesIf true, support for top chats and statistics collection is disabled
ignore_background_updatesBooleanYesIf true, allows to skip all updates received while the TDLib instance was not running. The option does nothing if the database or secret chats are used
ignore_default_disable_notificationBooleanYesIf true, the disable_notification value specified in the request will be always used instead of the default value
ignore_inline_thumbnailsBooleanYesIf true, prevents file thumbnails sent by the server along with messages from being saved on the disk
ignore_platform_restrictionsBooleanYesIf true, chat and message restrictions specific to the currently used operating system will be ignored
ignore_sensitive_content_restrictionsBooleanYesIf true, sensitive content will be shown on all user devices. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
is_location_visibleBooleanYesIf true, other users will be allowed to see the current user's location. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
language_pack_database_pathStringYesPath to a database for storing language pack strings, so that this database can be shared between different accounts. By default, language pack strings are stored only in memory. Changes of value of this option will be applied only after TDLib restart, so it should be set before call to setTdlibParameters.
language_pack_idStringYesIdentifier of the currently used language pack from the current localization target
localization_targetStringYesName for the current localization target (currently supported: “android”, “android_x”, “ios”, “macos” and “tdesktop”)
message_unload_delayIntegerYesThe maximum time messages are stored in memory before they are unloaded, 60-86400; in seconds. Defaults to 60 for users and 1800 for bots
notification_group_count_maxIntegerYesMaximum number of notification groups to be shown simultaneously, 0-25
notification_group_size_maxIntegerYesMaximum number of simultaneously shown notifications in a group, 1-25. Defaults to 10
onlineBooleanYesOnline status of the current user
prefer_ipv6BooleanYesIf true, IPv6 addresses will be preferred over IPv4 addresses
use_pfsBooleanYesIf true, Perfect Forward Secrecy will be enabled for interaction with the Telegram servers for cloud chats
use_quick_ackBooleanYesIf true, quick acknowledgement will be enabled for outgoing messages
use_storage_optimizerBooleanYesIf true, the background storage optimizer will be enabled
utc_time_offsetIntegerYesA UTC time offset used for splitting messages by days. The option is reset automatically on each TDLib instance launch, so it needs to be set manually only if the time offset is changed during execution.
animation_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for animations search
authentication_tokenStringNoAn authentication token to be used on subsequent authorizations and received when logging out
authorization_dateIntegerNoPoint in time (Unix timestamp) when authorization was received
basic_group_size_maxIntegerNoMaximum number of members in a basic group
call_connect_timeout_msIntegerNoMaximum time to wait for call connection creation to be passed to libtgvoip
call_packet_timeout_msIntegerNoMaximum time to wait for call packet delivery to be passed to libtgvoip
can_archive_and_mute_new_chats_from_unknown_usersBooleanNoIf true, the option “archive_and_mute_new_chats_from_unknown_users” can be changed
can_ignore_sensitive_content_restrictionsBooleanNoIf true, the option “ignore_sensitive_content_restrictions” can be changed
channel_bot_user_idIntegerNoIdentifier of the bot which is shown as the sender of messages sent on behalf of channels when viewed from an outdated client
enabled_proxy_idIntegerNoIdentifier of the enabled proxy
expect_blockingBooleanNoIf true, access to Telegram is likely blocked for the user
favorite_stickers_limitIntegerNoMaximum number of favorite stickers
forwarded_message_count_maxIntegerNoMaximum number of forwarded messages per one request
group_anonymous_bot_user_idIntegerNoIdentifier of the bot which is shown as the sender of anonymous messages in groups when viewed from an outdated client
message_caption_length_maxIntegerNoMaximum length of a message caption
message_text_length_maxIntegerNoMaximum length of a message text
my_idIntegerNoIdentifier of the current user
pinned_archived_chat_count_maxIntegerNoMaximum number of pinned cloud chats in the Archive chat list. The same amount of secret chats can be pinned locally
pinned_chat_count_maxIntegerNoMaximum number of pinned cloud chats in the Main chat list. The same amount of secret chats can be pinned locally
photo_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for photos search
replies_bot_chat_idIntegerNoIdentifier of the @replies bot
suggested_language_pack_idStringNoIdentifier of the language pack, suggested for the user by the server
suggested_video_note_audio_bitrateIntegerNoSuggested bit rate for audio encoding in video notes, in kbit/s
suggested_video_note_lengthIntegerNoSuggested width and height of the video in video notes
suggested_video_note_video_bitrateIntegerNoSuggested bit rate for video encoding in video notes, in kbit/s
supergroup_size_maxIntegerNoMaximum number of members in a supergroup
t_me_urlStringNoCurrent value of t.me URL, i.e. https://t.me/
telegram_service_notifications_chat_idIntegerNoIdentifier of the Telegram Service Notifications chat
test_modeBooleanNoIf true, the test environment is being used instead of the production environment
unix_timeIntegerNoAn estimation of the current Unix timestamp. The option will not be updated automatically unless the difference between the previous estimation and the locally available monotonic clocks changes significantly
venue_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for venues search
versionStringNoTDLib version. This options is guaranteed to come before all other updates since TDLib 1.4.0
+

Additionally any option beginning with 'x' or 'X' is writeable and can be safely used by the application to persistently store some small amount of data.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/techfaq.html b/data/core.telegram.org/techfaq.html new file mode 100644 index 0000000000..a9aceb9a38 --- /dev/null +++ b/data/core.telegram.org/techfaq.html @@ -0,0 +1,333 @@ + + + + + FAQ for the Technically Inclined + + + + + + + + + + + + + +
+ +
+
+
+
+

FAQ for the Technically Inclined

+ +
+

This FAQ about MTProto is intended for advanced users. You may also want to check out our Basic FAQ.
Please note, that client developers are required to comply with the Security Guidelines.

+
+

+

General questions

+

Q: Why did you go for a custom protocol?

+

In order to achieve reliability on weak mobile connections as well as speed when dealing with large files (such as photos, large videos and files up to 2 GB each), MTProto uses an original approach. This document is intended to clarify certain details of our setup, as well as address some important points that might be overlooked at first glance.

+

Q: Where can I read more about the protocol?

+

Detailed protocol documentation is available here. Please note that MTProto supports two layers: client-server encryption that is used in Telegram cloud chats and end-to-end encryption that is used in Telegram Secret Chats. See below for more information.

+

If you have any comments, feel free to reach out to security@telegram.org

+

Q: How does server-client encryption work in MTProto?

+

Server-client encryption is used in Telegram Cloud Chats. Here's a brief overview of the setup:

+ + +
Note 1
+

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

+
    +
  • server salt (64-Bit)
  • +
  • session id
  • +
  • message sequence number
  • +
  • message length
  • +
  • time
  • +
+
Note 2
+

See additional comments on our use of IGE and message authentication.

+
Note 3
+

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above.

+

Q: How does end-to-end encryption work in MTProto?

+

End-to-end encryption is used in Telegram Secret Chats, as well as voice and video calls. You can read more about it here: Secret Chats, End-to-End encryption. Here's a brief overview of the setup:

+
+ +
+ +

Please see these articles for details:

+ +

Q: Why are you not using X? (insert solution)

+

While other ways of achieving the same cryptographic goals, undoubtedly, exist, we feel that the present solution is both robust and also sucсeeds at our secondary task of beating unencrypted messengers in terms of delivery time and stability.

+

Q: Why are you mostly relying on classical crypto algorithms?

+

We prefer to use well-known algorithms, created in the days when bandwidth and processing power were both a much rarer commodity. This has valuable side-effects for modern-day mobile development and sending large files, provided one takes care of the known drawbacks.

+

The weakspots of such algorithms are also well-known, and have been exploited for decades. We use these algorithms in such a combination that, to the best of our knowledge, prevents any known attacks.

+

Q: I'm a security expert and I have comments about your setup.

+

Any comments on Telegram's security are welcome at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $100 to $100,000 or more, depending on the severity of the issue.

+

Please note that we can not offer bounties for issues that are disclosed to the public before they are addressed.

+

Encryption

+

Q: How are MTProto messages authenticated?

+

All Telegram apps ensure that msg_key is equal to SHA-256 of a fragment of the auth_key concatenated with the decrypted message (including 12…1024 bytes of random padding). It is important that the plaintext always contains message length, server salt, session_id and other data not known to the attacker.

+

It is crucial that AES decryption keys depend both on msg_key, and on auth_key, known only to the parties involved in the exchange.

+

Q: Are you doing Encrypt-then-MAC, MAC-then-Encrypt or MAC-and-Encrypt?

+

We do none of the above, strictly speaking. For message authentication, we compute SHA-256(auth_key_fragment + AES_decrypt(…,encrypted_message)) upon message receipt and compare this value to the msg_key received with the encrypted message.

+
+

See also: Why not Encrypt-then-MAC?

+
+

Q: Why don't you go for a standard encrypt-then-MAC approach?

+

Using encrypt-then-MAC, e.g. involving GCM (Galois Counter Mode), would enable the receiving party to detect unauthorized or modified ciphertexts, thus eliminating the need to decrypt them in case of tampering.

+

In MTProto, the clients and the server authenticate messages by ensuring that SHA-256(auth_key_fragment + plaintext + padding) = msg_key and that the plaintext always contains message length, server salt, session_id and other data not known to a potential attacker before accepting any message. These security checks performed on the client before any message is accepted ensure that invalid or tampered with messages will always be safely (and silently) discarded.

+

This way we arrive at the same result. The difference is that the security check is performed before decryption in Encrypt-then-MAC and after decryption in MTProto – but in either case before a message is accepted. AES encryption / decryption on devices currently in use is comparable in speed with the additional HMAC computation required for the encrypt-then-MAC approach.

+

Q: Do you still use SHA-1?

+

The current version of the protocol is using SHA-256. MTProto 1.0 used to rely on SHA-1 (see this FAQ for details).

+

In MTProto 2.0, SHA-1 is used only where the choice of hash function is irrelevant for security, e.g.:

+ +

Q: Do you use IGE? IGE is broken!

+

Yes, we use IGE, but it is not broken in our implementation. The fact that we do not use IGE as MAC together with other properties of our system makes the known attacks on IGE irrelevant.

+

IGE, just as the ubiquitous CBC, is vulnerable to blockwise-adaptive CPA. But adaptive attacks are only a threat for as long as the same key can be used in several messages (not so in MTProto).

+

Adaptive attacks are even theoretically impossible in MTProto, because in order to be encrypted the message must be fully formed first, since the key is dependent on the message content. As for non-adaptive CPA, IGE is secure against them, as is CBC.

+

Authentication

+

Q: How is the server authenticated during DH key exchange?

+

The DH exchange is authenticated with the server's public RSA-key that is built into the client (the same RSA-key is also used for protection against MitM attacks).

+

Q: How are clients authenticated?

+

Various secrets (nonce, server_nonce, new_nonce) exchanged during key generation guarantee that the DH-key can only be obtained by the instance that initiated the exchange.

+

Notice that new_nonce is transferred explicitly only once, inside an RSA-encrypted message from the client to the server.

+

Q: How are Secret Chats authenticated?

+

Keys for end-to-end encrypted secret chats are generated by a new instance of DH key exchange, so they are known only to the parties involved and not to the server. To establish the identities of these parties and to ensure that no MitM is in place, it is recommended to compare identicons, generated from hashes of the DH secret chat keys (key visualizations).

+

Q: How are Voice Calls authenticated?

+

Keys for end-to-end encrypted calls are generated using the Diffie-Hellman key exchange. Users who are on a call can ensure that there is no MitM by comparing key visualizations.

+

To make key verification practical in the context of a voice call, Telegram uses a three-message modification of the standard DH key exchange for calls:

+
    +
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • +
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • +
  • A->B : (computes key (g_b)a, then) sends g_a := ga
  • +
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • +
+

The idea is that Alice commits to a specific value of a (and of g_a), but does not reveal g_a to Bob (or Eve) until the very last step. Bob has to choose his value of b and g_b without knowing the true value of g_a. If Eve is performing a Man-in-the-Middle attack, she cannot change a depending on the value of g_b received from Bob and she also can't tune her value of b depending on g_a. As a result, Eve only gets one shot at injecting her parameters — and she must fire this shot with her eyes closed.

+

Thanks to this modification, it becomes possible to prevent eavesdropping (MitM attacks on DH) with a probability of more than 0.9999999999 by using just over 33 bits of entropy in the visualization. These bits are presented to the users in the form of four emoticons. We have selected a pool of 333 emoji that all look quite different from one another and can be easily described in simple words in any language.

+

You can read more about key verification for Telegram calls here.

+

Q: Do you have Forward Secrecy?

+

Telegram's Secret chats support Perfect Forward Secrecy, you can read more about it here.

+

Protection against known attacks

+

Known-Plaintext Attacks

+

By definition, the known-plaintext attack (KPA) is an attack model for cryptanalysis where the attacker has samples of both the plaintext, and its encrypted version (ciphertext).

+

AES IGE that is used in MTProto is robust against KPA attacks (see this, if you wonder how one can securely use IGE). On top of that, the plaintext in MTProto always contains server_salt and session id.

+

Chosen-Plaintext Attacks

+

By definition, a chosen-plaintext attack (CPA) is an attack model for cryptanalysis which presumes that the attacker has the capability to choose arbitrary plaintexts to be encrypted and obtain the corresponding ciphertexts.

+

MTProto uses AES in IGE mode (see this, if you wonder how one can securely use IGE) that is secure against non-adaptive CPAs. IGE is known to be not secure against blockwise-adaptive CPA, but MTProto fixes this in the following manner:

+

Each plaintext message to be encrypted always contains the following to be checked upon decryption:

+
    +
  • server salt (64-Bit)
  • +
  • message sequence number
  • +
  • time
  • +
+

On top of this, in order to replace the plaintext, you would also need to use the right AES key and iv, both dependent on the auth_key. This makes MTProto robust against a CPA.

+

Chosen-Ciphertext Attacks

+

By definition, a chosen-ciphertext attack (CCA) is an attack model for cryptanalysis in which the cryptanalyst gathers information, at least in part, by choosing a ciphertext and obtaining its decryption under an unknown key. In the attack, an adversary has a chance to enter one or more known ciphertexts into the system and obtain the resulting plaintexts. From these pieces of information the adversary can attempt to recover the hidden secret key used for decryption.

+

Each time a message is decrypted in MTProto, a check is performed to see whether msg_key is equal to the SHA-256 of a fragment of the auth_key concatenated with the decrypted message (including 12…1024 bytes of random padding). The plaintext (decrypted data) also always contains message length, server salt and sequence number. This negates known CCAs.

+

What about IND-CCA?

+

MTProto 2.0 satisfies the conditions for indistinguishability under chosen ciphertext attack (IND-CCA).

+
+

Read more about IND-CCA in MTProto 1.0

+
+

Replay attacks

+

Replay attacks are denied because each plaintext to be encrypted contains the server salt and the unique message id and sequence number.

+

This means that each message can only be sent once.

+

Man-in-the-middle attacks

+

Telegram has two modes of communication — ordinary chats using client-server encryption and Secret Chats using end-to-end encryption.

+

Client-Server communication is protected from MiTM-attacks during DH key generation by means of a server RSA public key embedded into client software. After that, if both clients trust the server software, the Secret Chats between them are protected by the server from MiTM attacks.

+

The interface offers a way of comparing Secret Chat keys for users who do not trust the server. Visualizations of the key are presented in the form of identicons (example here). By comparing key visualizations users can make sure no MITM attack had taken place.

+

Hash collisions for Diffie-Hellman Keys

+

Currently, the fingerprint uses 128-bits of SHA-1 concatenated with 160 bits from the SHA-256 of the key, yielding a total of 288 fingerprint bits, thus negating the possibility of hash-collision attacks.

+
+

Read more about fingerprints in earlier versions of Telegram

+
+

Length extension attacks

+

By definition, length extension attacks are a type of attack when certain types of hashes are misused as message authentication codes, allowing for inclusion of extra information.

+

A message in MTProto consists of an msg_key, equal to the SHA-256 of a fragment of the auth_key concatenated with the plaintext (including 12…1024 bytes of random padding and some additional parameters), followed by the ciphertext. The attacker cannot append extra bytes to the end and recompute the SHA-256, since the SHA-256 is computed from the plaintext, not the ciphertext, and the attacker has no way to obtain the ciphertext corresponding to the extra plaintext bytes she may want to add.

+

Apart from that, changing the msg_key would also change the AES decryption key for the message in a way unpredictable for the attacker, so even the original prefix would decrypt to garbage — which would be immediately detected since the app performs a security check to ensure that the SHA-256 of the plaintext (combined with a fragment of the auth_key) matches the msg_key received.

+

Encrypted CDNs

+

As of Telegram 4.2, we support encrypted CDNs for caching media from public channels with over 100.000 members. The CDN caching nodes are located in regions with significant Telegram traffic where we wouldn't want to place Telegram servers for various reasons.

+
+

For technical details of the implementation, encryption and verification of data, see the CDN manual.

+
+

See this document for a Persian version of this FAQ.
بخش فارسی

+

Q: Why did you decide to use CDNs?

+

We use our own distributed servers to speed up downloads in regions where freedom of speech is guaranteed — and even there we don't take this for granted. But when Telegram becomes immensely popular in other areas, we can only rely on CDNs which we treat rather like ISPs from the technical standpoint in that they only get encrypted data they can't decipher.

+

Thanks to this technology, the download speed for public photos and videos can become significantly higher in regions like Turkey, Indonesia, South America, India, Iran or Iraq without the slightest compromise in security.

+

Q: Can the CDN decipher the files?

+

No. Each file that is to be sent to the CDN is encrypted with a unique key using AES-256-CTR encryption. The CDN can't access the data it stores because these keys are only accessible to the main MTProto server and to the authorized client.

+

Q: Can the CDN substitute the data with their own version?

+

No. Data downloaded from CDN caching nodes is always verified by the receiving Telegram app by way of a hash: attackers won’t be able to replace any files with their own versions.

+

Q: Can the CDN delete any files?

+

No. CDN nodes only cache encrypted copies of files, originals are stored on the Telegram servers. The user is notified about receiving the file by the Telegram server. If the CDN caching node doesn't give the file to the user, the user will receive the file from the Telegram server directly.

+

Q: Can CDNs be used for censorship?

+

No. All original files are stored on the Telegram servers. The CDNs only get encrypted data — and they can't decipher it. They can't substitute any data. And in case of any problems with the CDN, the file will be simply delivered to the users directly from the Telegram servers. Users will always get their data, nobody can stop this.

+

Q: Can I verify this?

+

Yes. Anyone can verify our CDN implementation by checking the source code of Telegram apps and inspecting traffic.

+

Q: Does this affect private data?

+

No. The CDN caching nodes are not a part of the Telegram cloud. CDN caching nodes are used only for caching popular public media from massive channels. Private data never goes there.

+

Q: Is this connected with government requests to move private data to their territory?

+

No. We haven't entered in any agreements with any government regarding the CDNs and the CDNs are not part of any deal. The only purpose of CDNs is to securely improve connectivity in high demand regions where Telegram can't place its servers.

+

Q: Does this give some countries any influence over Telegram?

+

No. We have taken special precautions to make sure that no country gains any leverage over Telegram by way of the CDN caching nodes:

+
    +
  • The CDNs do not belong to Telegram – all the risks are on a third-party company that supplies us with CDN nodes around the world.
  • +
  • We did not invest anything in these CDNs and will only be paying for traffic that is used to pass cached items from our main clusters and to the end users.
  • +
+

As the result, if any country decides to mess with the CDN in their region, they gain nothing except for reducing connectivity for their own citizens – and Telegram loses nothing of value.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/themes.html b/data/core.telegram.org/themes.html new file mode 100644 index 0000000000..bf98edc07e --- /dev/null +++ b/data/core.telegram.org/themes.html @@ -0,0 +1,143 @@ + + + + + Creating Custom Cloud Themes + + + + + + + + + + + + + +
+ +
+
+
+
+

Creating Custom Cloud Themes

+ +

Official Telegram apps support custom cloud themes as of version 5.11. Everyone is welcome to create and share their themes.

+

Creating a theme

+

You can use the Online Theme Editor (use a VPN if it is blocked in your country) to create new Telegram themes from scratch or edit existing ones. Simply log in with your Telegram account and pick a platform to start editing the relevant theme file – or import an existing theme.

+
    +
  • Set a name for your theme using the name attribute
  • +
  • Set colors for elements using hex codes or the color picker
  • +
  • Press ‘Save and apply theme’ to push changes to all users of your theme
  • +
+

Checking your theme in-app

+

Once you have saved a theme for the first time, Telegram will send you a message with its sharing link. Open the link in the app to switch to your theme.

+

You can always switch to your theme in Settings > Chat Settings. On iOS and MacOS native app – Settings > Appearance.

+

Publishing your theme

+

Each theme has a t.me/addtheme link which people can use to switch to your theme. You can choose a beautiful short link (e.g., https://t.me/addtheme/desert) by changing the shortname attribute. If you add support for multiple platforms, the same link can be used for setting your theme on all of them.

+

Updating your theme

+

Your theme gets updated automatically for all its users whenever you save and apply changes.

+

Including a chat background

+

Your themes can include a custom wallpaper. To do this, simply go to Settings > Chat Settings > Chat Background. On iOS and MacOS native app – Settings > Appearance > Chat Background.

+

Open any background and tap the sharing button in the top right corner, then copy its t.me/bg/... link. In the theme file, set this link as the value of the wallpaper attribute.

+

For Telegram Desktop, if you want to make the background tiled, add ?mode=tiled at the end of the link. For example:

+
wallpaper: t.me/bg/-jI7lnO3DFABAAAA1vXcFaZP_Vo?mode=tiled
+

Creating themes in-app

+

If you prefer a more WYSIWYG approach, try creating themes using the in-app tools for customizing appearance. Telegram for Android and Telegram Desktop have advanced in-app theme editors. Telegram for iOS and MacOS allow choosing a custom accent color from the color wheel and a background, then saving the result as a custom theme.

+

Once you have saved a new theme in any of the apps, it also becomes accessible in the online editor.

+

Read more

+ +
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/AccountDaysTTL.html b/data/core.telegram.org/type/AccountDaysTTL.html new file mode 100644 index 0000000000..de81618068 --- /dev/null +++ b/data/core.telegram.org/type/AccountDaysTTL.html @@ -0,0 +1,162 @@ + + + + + AccountDaysTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

AccountDaysTTL

+ +

Time-to-live of current account

+

+ +
+
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+
+---functions---
+
+account.getAccountTTL#8fc711d = AccountDaysTTL;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
accountDaysTTLTime to live in days of the current account
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAccountTTLGet days to live of account
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Audio.html b/data/core.telegram.org/type/Audio.html new file mode 100644 index 0000000000..fcca48232a --- /dev/null +++ b/data/core.telegram.org/type/Audio.html @@ -0,0 +1,128 @@ + + + + + Audio + + + + + + + + + + + + + +
+ +
+
+
+ +

Audio

+ +

Audio file.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Authorization.html b/data/core.telegram.org/type/Authorization.html new file mode 100644 index 0000000000..4cc237363b --- /dev/null +++ b/data/core.telegram.org/type/Authorization.html @@ -0,0 +1,162 @@ + + + + + Authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

Authorization

+ +

Represents a logged-in session

+

+ +
+
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+
+---functions---
+
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
authorizationLogged-in session
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
auth.acceptLoginTokenLogin via QR code
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/AutoDownloadSettings.html b/data/core.telegram.org/type/AutoDownloadSettings.html new file mode 100644 index 0000000000..2df1842091 --- /dev/null +++ b/data/core.telegram.org/type/AutoDownloadSettings.html @@ -0,0 +1,143 @@ + + + + + AutoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

AutoDownloadSettings

+ +

Media autodownload settings

+

+ +
+
autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
autoDownloadSettingsAutodownload settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/BankCardOpenUrl.html b/data/core.telegram.org/type/BankCardOpenUrl.html new file mode 100644 index 0000000000..054636976f --- /dev/null +++ b/data/core.telegram.org/type/BankCardOpenUrl.html @@ -0,0 +1,143 @@ + + + + + BankCardOpenUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

BankCardOpenUrl

+ +

Credit card info URL provided by the bank

+

+ +
+
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
bankCardOpenUrlCredit card info URL provided by the bank
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/BaseTheme.html b/data/core.telegram.org/type/BaseTheme.html new file mode 100644 index 0000000000..e548570717 --- /dev/null +++ b/data/core.telegram.org/type/BaseTheme.html @@ -0,0 +1,163 @@ + + + + + BaseTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

BaseTheme

+ +

Basic theme settings

+

+ +
+
baseThemeClassic#c3a12462 = BaseTheme;
+baseThemeDay#fbd81688 = BaseTheme;
+baseThemeNight#b7b31ea8 = BaseTheme;
+baseThemeTinted#6d5f77ee = BaseTheme;
+baseThemeArctic#5b11125a = BaseTheme;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
baseThemeClassicClassic theme
baseThemeDayDay theme
baseThemeNightNight theme
baseThemeTintedTinted theme
baseThemeArcticArctic theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Bool.html b/data/core.telegram.org/type/Bool.html new file mode 100644 index 0000000000..0f2612e8b6 --- /dev/null +++ b/data/core.telegram.org/type/Bool.html @@ -0,0 +1,718 @@ + + + + + Bool + + + + + + + + + + + + + +
+ +
+
+
+ +

Bool

+ +

Boolean type.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+---functions---
+
+auth.logOut#5717da40 = Bool;
+auth.resetAuthorizations#9fab0d1a = Bool;
+auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
+auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;
+auth.checkRecoveryPassword#d36bf79 code:string = Bool;
+
+account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;
+account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;
+account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;
+account.resetNotifySettings#db7e1747 = Bool;
+account.updateStatus#6628562c offline:Bool = Bool;
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;
+account.checkUsername#2714d86c username:string = Bool;
+account.deleteAccount#418d4e0b reason:string = Bool;
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;
+account.updateDeviceLocked#38df3532 period:int = Bool;
+account.resetAuthorization#df77f3bc hash:long = Bool;
+account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;
+account.resetWebAuthorization#2d01b9ef hash:long = Bool;
+account.resetWebAuthorizations#682d2594 = Bool;
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
+account.verifyEmail#ecba39db email:string code:string = Bool;
+account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;
+account.confirmPasswordEmail#8fdf1920 code:string = Bool;
+account.resendPasswordEmail#7a7f2a15 = Bool;
+account.cancelPasswordEmail#c1cbd5b6 = Bool;
+account.getContactSignUpNotification#9f07c728 = Bool;
+account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;
+account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
+account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
+account.resetWallPapers#bb3b9804 = Bool;
+account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;
+account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
+account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;
+account.declinePasswordReset#4c9409f6 = Bool;
+
+contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;
+contacts.block#68cc1411 id:InputPeer = Bool;
+contacts.unblock#bea65d50 id:InputPeer = Bool;
+contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;
+contacts.resetSaved#879537f1 = Bool;
+contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;
+
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+messages.reportSpam#cf1592db peer:InputPeer = Bool;
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;
+messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;
+messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;
+messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;
+messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;
+messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;
+messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
+messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
+messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
+messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;
+messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;
+messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;
+messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
+messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;
+messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
+messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;
+messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;
+messages.clearAllDrafts#7e58ee9c = Bool;
+messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;
+messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;
+messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;
+messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
+messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
+messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;
+messages.deleteChat#5bd0ee50 chat_id:long = Bool;
+messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
+
+channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;
+channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;
+channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
+channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
+channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;
+channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;
+channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;
+channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
+
+help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
+help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
+
+bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
+
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
+
+phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
+phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;
+
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
+
+stickers.checkShortName#284b3639 short_name:string = Bool;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
boolFalseConstructor may be interpreted as a booleanfalse value.
boolTrueThe constructor can be interpreted as a booleantrue value.
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
auth.logOutLogs out the user.
auth.resetAuthorizationsTerminates all user's authorized sessions except for the current one.

After calling this method it is necessary to reregister the current device using the method account.registerDevice
auth.bindTempAuthKeyBinds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

For more information, see Perfect Forward Secrecy.
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
account.updateStatusUpdates online user status.
account.reportPeerReport a peer for violation of telegram's Terms of Service
contacts.deleteByPhonesDelete contacts by phone number
contacts.blockAdds the user to the blacklist.
contacts.unblockDeletes the user from the blacklist.
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportReport a message in a chat for violation of telegram's Terms of Service
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.reportEncryptedSpamReport a secret chat for spam
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
account.checkUsernameValidates a username and checks availability.
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.setAccountTTLSet account self-destruction period
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.resetAuthorizationLog out an active authorized session by it hash
account.updatePasswordSettingsSet a new 2FA password
messages.uninstallStickerSetUninstall a stickerset
channels.readHistoryMark channel/supergroup history as read
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
messages.editChatAdminMake a user admin in a legacy group.
messages.reorderStickerSetsReorder installed stickersets
messages.saveGifAdd GIF to saved gifs list
messages.setInlineBotResultsAnswer an inline query, for bots only
auth.cancelCodeCancel the login verification code
messages.editInlineBotMessageEdit an inline bot message
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
contacts.resetTopPeerRatingReset rating of top peer
messages.saveDraftSave a message draft associated to a chat.
messages.readFeaturedStickersMark new featured stickers as read
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.clearRecentStickersClear recent stickers
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
payments.clearSavedInfoClear saved payment information
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
Use this method to respond to such pre-checkout queries.
Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.saveCallDebugSend phone call debug data to server
channels.setStickersAssociate a stickerset to the supergroup
messages.faveStickerMark a sticker as favorite
channels.readMessageContentsMark channel/supergroup message contents as read
contacts.resetSavedDelete saved contacts
channels.deleteHistoryDelete the history of a supergroup
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
help.acceptTermsOfServiceAccept the new terms of service
account.deleteSecureValueDelete stored telegram passport value
users.setSecureValueErrorsSet secure passport value errors for a user
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.verifyPhoneVerify a phone number for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.finishTakeoutSessionFinish account takeout session
messages.markDialogUnreadManually mark dialog as unread
contacts.toggleTopPeersEnable/disable top peers
messages.clearAllDraftsClear all drafts.
help.saveAppLogSaves logs of application on the server.
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
messages.editChatAboutEdit the description of a group/supergroup/channel.
account.saveWallPaperInstall/uninstall wallpaper
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveAutoDownloadSettingsChange media autodownload settings
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
channels.editLocationEdit location of geogroup
account.saveThemeSave a theme
account.installThemeInstall a theme
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
messages.toggleStickerSetsApply changes to multiple stickersets
messages.updateDialogFilterUpdate folder
messages.updateDialogFiltersOrderReorder folders
bots.setBotCommandsSet bot command list
help.hidePromoDataHide MTProxy/Public Service Announcement information
phone.sendSignalingDataSend VoIP signaling data
help.dismissSuggestionDismiss a suggestion
messages.readDiscussionMark a channel discussion as read
messages.deleteChatDelete a chat
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteExportedChatInviteDelete a chat invite
account.reportProfilePhotoReport a profile photo of a dialog
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
stickers.checkShortNameCheck whether the given short name is available
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
account.declinePasswordResetAbort a pending 2FA password reset
auth.checkRecoveryPasswordCheck if the recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
channels.viewSponsoredMessageMark a specific sponsored message as read
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/BotCommand.html b/data/core.telegram.org/type/BotCommand.html new file mode 100644 index 0000000000..7c27fc5d35 --- /dev/null +++ b/data/core.telegram.org/type/BotCommand.html @@ -0,0 +1,143 @@ + + + + + BotCommand + + + + + + + + + + + + + +
+ +
+
+
+ +

BotCommand

+ +

Describes a bot command that can be used in a chat

+

+ +
+
botCommand#c27ac8c7 command:string description:string = BotCommand;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
botCommandDescribes a bot command that can be used in a chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/BotCommandScope.html b/data/core.telegram.org/type/BotCommandScope.html new file mode 100644 index 0000000000..a263d67cb5 --- /dev/null +++ b/data/core.telegram.org/type/BotCommandScope.html @@ -0,0 +1,176 @@ + + + + + BotCommandScope + + + + + + + + + + + + + +
+ +
+
+
+ +

BotCommandScope

+ +

Represents a scope where the bot commands, specified using bots.setBotCommands will be valid.

+

+ +
+
botCommandScopeDefault#2f6cb2ab = BotCommandScope;
+botCommandScopeUsers#3c4f04d8 = BotCommandScope;
+botCommandScopeChats#6fe1a881 = BotCommandScope;
+botCommandScopeChatAdmins#b9aa606a = BotCommandScope;
+botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;
+botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;
+botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
botCommandScopeDefaultThe commands will be valid in all chats
botCommandScopeUsersThe specified bot commands will only be valid in all private chats with users.
botCommandScopeChatsThe specified bot commands will be valid in all groups and supergroups
botCommandScopeChatAdminsThe specified bot commands will be valid only for chat administrators, in all groups and supergroups.
botCommandScopePeerThe specified bot commands will be valid only in a specific dialog
botCommandScopePeerAdminsThe specified bot commands will be valid for all admins of the specified group or supergroup.
botCommandScopePeerUserThe specified bot commands will be valid only for a specific user in the specified chat
+

Related pages

+

bots.setBotCommands

+

Set bot command list

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/BotInfo.html b/data/core.telegram.org/type/BotInfo.html new file mode 100644 index 0000000000..d988f6935f --- /dev/null +++ b/data/core.telegram.org/type/BotInfo.html @@ -0,0 +1,143 @@ + + + + + BotInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

BotInfo

+ +

Info about bots (available bot commands, etc)

+

+ +
+
botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
botInfoInfo about bots (available bot commands, etc)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/BotInlineMessage.html b/data/core.telegram.org/type/BotInlineMessage.html new file mode 100644 index 0000000000..316feda9a8 --- /dev/null +++ b/data/core.telegram.org/type/BotInlineMessage.html @@ -0,0 +1,168 @@ + + + + + BotInlineMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

BotInlineMessage

+ +

Inline message

+

+ +
+
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
botInlineMessageMediaAutoSend whatever media is attached to the botInlineMediaResult
botInlineMessageTextSend a simple text message
botInlineMessageMediaGeoSend a geolocation
botInlineMessageMediaVenueSend a venue
botInlineMessageMediaContactSend a contact
botInlineMessageMediaInvoiceSend an invoice
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/BotInlineResult.html b/data/core.telegram.org/type/BotInlineResult.html new file mode 100644 index 0000000000..e9e7f7738d --- /dev/null +++ b/data/core.telegram.org/type/BotInlineResult.html @@ -0,0 +1,148 @@ + + + + + BotInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

BotInlineResult

+ +

Results of an inline query

+

+ +
+
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
+botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
botInlineResultGeneric result
botInlineMediaResultMedia result
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/CdnConfig.html b/data/core.telegram.org/type/CdnConfig.html new file mode 100644 index 0000000000..416fe83f25 --- /dev/null +++ b/data/core.telegram.org/type/CdnConfig.html @@ -0,0 +1,164 @@ + + + + + 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 new file mode 100644 index 0000000000..6ccb82085f --- /dev/null +++ b/data/core.telegram.org/type/CdnPublicKey.html @@ -0,0 +1,145 @@ + + + + + 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/ChannelAdminLogEventsFilter.html b/data/core.telegram.org/type/ChannelAdminLogEventsFilter.html new file mode 100644 index 0000000000..64712a8d68 --- /dev/null +++ b/data/core.telegram.org/type/ChannelAdminLogEventsFilter.html @@ -0,0 +1,143 @@ + + + + + ChannelAdminLogEventsFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelAdminLogEventsFilter

+ +

Filter for fetching events in the channel admin log

+

+ +
+
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channelAdminLogEventsFilterFilter only certain admin log events
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChannelLocation.html b/data/core.telegram.org/type/ChannelLocation.html new file mode 100644 index 0000000000..5dd2122123 --- /dev/null +++ b/data/core.telegram.org/type/ChannelLocation.html @@ -0,0 +1,148 @@ + + + + + ChannelLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelLocation

+ +

Geographical location of supergroup (geogroups)

+

+ +
+
channelLocationEmpty#bfb5ad8b = ChannelLocation;
+channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
channelLocationEmptyNo location (normal supergroup)
channelLocationGeographical location of supergroup (geogroups)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChannelMessagesFilter.html b/data/core.telegram.org/type/ChannelMessagesFilter.html new file mode 100644 index 0000000000..2c4371a0d2 --- /dev/null +++ b/data/core.telegram.org/type/ChannelMessagesFilter.html @@ -0,0 +1,148 @@ + + + + + ChannelMessagesFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelMessagesFilter

+ +

Filter for fetching only certain types of channel messages

+

+ +
+
channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;
+channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
channelMessagesFilterEmptyNo filter
channelMessagesFilterFilter for getting only certain types of channel messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChannelParticipant.html b/data/core.telegram.org/type/ChannelParticipant.html new file mode 100644 index 0000000000..d2274b1ba4 --- /dev/null +++ b/data/core.telegram.org/type/ChannelParticipant.html @@ -0,0 +1,168 @@ + + + + + ChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelParticipant

+ +

Channel participant

+

+ +
+
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
+channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;
+channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
+channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
+channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
+channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
channelParticipantChannel/supergroup participant
channelParticipantSelfMyself
channelParticipantCreatorChannel/supergroup creator
channelParticipantAdminAdmin
channelParticipantBannedBanned/kicked user
channelParticipantLeftA participant that left the channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChannelParticipantsFilter.html b/data/core.telegram.org/type/ChannelParticipantsFilter.html new file mode 100644 index 0000000000..6d2090cd0c --- /dev/null +++ b/data/core.telegram.org/type/ChannelParticipantsFilter.html @@ -0,0 +1,178 @@ + + + + + ChannelParticipantsFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelParticipantsFilter

+ +

Filter for fetching channel participants

+

+ +
+
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;
+channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;
+channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;
+channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;
+channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;
+channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;
+channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;
+channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
channelParticipantsRecentFetch only recent participants
channelParticipantsAdminsFetch only admin participants
channelParticipantsKickedFetch only kicked participants
channelParticipantsBotsFetch only bot participants
channelParticipantsBannedFetch only banned participants
channelParticipantsSearchQuery participants by name
channelParticipantsContactsFetch only participants that are also contacts
channelParticipantsMentionsThis filter is used when looking for members to mention.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Chat.html b/data/core.telegram.org/type/Chat.html new file mode 100644 index 0000000000..593dcf12d5 --- /dev/null +++ b/data/core.telegram.org/type/Chat.html @@ -0,0 +1,163 @@ + + + + + Chat + + + + + + + + + + + + + +
+ +
+
+
+ +

Chat

+ +

Object defines a group.

+

+ +
+
chatEmpty#29562865 id:long = Chat;
+chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;
+chatForbidden#6592a1a7 id:long title:string = Chat;
+channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;
+channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
chatEmptyEmpty constructor, group doesn't exist
chatInfo about a group
chatForbiddenA group to which the user has no access. E.g., because the user was kicked from the group.
channelChannel/supergroup info
channelForbiddenIndicates a channel/supergroup we can't access because we were banned, or for some other reason.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatAdminRights.html b/data/core.telegram.org/type/ChatAdminRights.html new file mode 100644 index 0000000000..2e585e999d --- /dev/null +++ b/data/core.telegram.org/type/ChatAdminRights.html @@ -0,0 +1,146 @@ + + + + + ChatAdminRights + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatAdminRights

+ +

Represents the rights of an admin in a channel/supergroup.

+

+ +
+
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatAdminRightsRepresents the rights of an admin in a channel/supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatAdminWithInvites.html b/data/core.telegram.org/type/ChatAdminWithInvites.html new file mode 100644 index 0000000000..de71b94b23 --- /dev/null +++ b/data/core.telegram.org/type/ChatAdminWithInvites.html @@ -0,0 +1,143 @@ + + + + + ChatAdminWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatAdminWithInvites

+ +

Info about chat invites generated by admins.

+

+ +
+
chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatAdminWithInvitesInfo about chat invites generated by admins.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatBannedRights.html b/data/core.telegram.org/type/ChatBannedRights.html new file mode 100644 index 0000000000..ea21b3656a --- /dev/null +++ b/data/core.telegram.org/type/ChatBannedRights.html @@ -0,0 +1,146 @@ + + + + + ChatBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatBannedRights

+ +

Represents the rights of a normal user in a supergroup/channel/chat.

+

+ +
+
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatBannedRightsRepresents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatFull.html b/data/core.telegram.org/type/ChatFull.html new file mode 100644 index 0000000000..10ce7a0af0 --- /dev/null +++ b/data/core.telegram.org/type/ChatFull.html @@ -0,0 +1,148 @@ + + + + + ChatFull + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatFull

+ +

Object containing detailed group info

+

+ +
+
chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
+channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
chatFullDetailed chat info
channelFullFull info about a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatInvite.html b/data/core.telegram.org/type/ChatInvite.html new file mode 100644 index 0000000000..b018613b36 --- /dev/null +++ b/data/core.telegram.org/type/ChatInvite.html @@ -0,0 +1,172 @@ + + + + + ChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatInvite

+ +

Chat invite

+

+ +
+
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
+chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
+
+---functions---
+
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
chatInviteAlreadyThe user has already joined this chat
chatInviteChat invite info
chatInvitePeekA chat invitation that also allows peeking into the group to read messages without joining it.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatInviteImporter.html b/data/core.telegram.org/type/ChatInviteImporter.html new file mode 100644 index 0000000000..dcbcf76d68 --- /dev/null +++ b/data/core.telegram.org/type/ChatInviteImporter.html @@ -0,0 +1,143 @@ + + + + + ChatInviteImporter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatInviteImporter

+ +

When and which user joined the chat using a chat invite

+

+ +
+
chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatInviteImporterWhen and which user joined the chat using a chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatOnlines.html b/data/core.telegram.org/type/ChatOnlines.html new file mode 100644 index 0000000000..9280a09df5 --- /dev/null +++ b/data/core.telegram.org/type/ChatOnlines.html @@ -0,0 +1,162 @@ + + + + + ChatOnlines + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatOnlines

+ +

Number of online users in a chat

+

+ +
+
chatOnlines#f041e250 onlines:int = ChatOnlines;
+
+---functions---
+
+messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatOnlinesNumber of online users in a chat
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getOnlinesGet count of online users in a chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatParticipant.html b/data/core.telegram.org/type/ChatParticipant.html new file mode 100644 index 0000000000..46c022bc0e --- /dev/null +++ b/data/core.telegram.org/type/ChatParticipant.html @@ -0,0 +1,153 @@ + + + + + ChatParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatParticipant

+ +

Details of a group member.

+

+ +
+
chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;
+chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;
+chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
chatParticipantGroup member.
chatParticipantCreatorRepresents the creator of the group
chatParticipantAdminChat admin
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatParticipants.html b/data/core.telegram.org/type/ChatParticipants.html new file mode 100644 index 0000000000..2ae72c16fa --- /dev/null +++ b/data/core.telegram.org/type/ChatParticipants.html @@ -0,0 +1,148 @@ + + + + + ChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatParticipants

+ +

Object contains info on group members.

+

+ +
+
chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;
+chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
chatParticipantsForbiddenInfo on members is unavailable
chatParticipantsGroup members.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatPhoto.html b/data/core.telegram.org/type/ChatPhoto.html new file mode 100644 index 0000000000..0c4a5e067e --- /dev/null +++ b/data/core.telegram.org/type/ChatPhoto.html @@ -0,0 +1,148 @@ + + + + + ChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatPhoto

+ +

Object defines a group profile photo.

+

+ +
+
chatPhotoEmpty#37c1011c = ChatPhoto;
+chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
chatPhotoEmptyGroup photo is not set.
chatPhotoGroup profile photo.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatTheme.html b/data/core.telegram.org/type/ChatTheme.html new file mode 100644 index 0000000000..1ca3407fce --- /dev/null +++ b/data/core.telegram.org/type/ChatTheme.html @@ -0,0 +1,143 @@ + + + + + ChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatTheme

+ +

A chat theme

+

+ +
+
chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatThemeA chat theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/CodeSettings.html b/data/core.telegram.org/type/CodeSettings.html new file mode 100644 index 0000000000..2a4d520361 --- /dev/null +++ b/data/core.telegram.org/type/CodeSettings.html @@ -0,0 +1,143 @@ + + + + + CodeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

CodeSettings

+ +

Settings for the code type to send

+

+ +
+
codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
codeSettingsSettings used by telegram servers for sending the confirm code.

Example implementations: telegram for android, tdlib.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Config.html b/data/core.telegram.org/type/Config.html new file mode 100644 index 0000000000..d609658f4d --- /dev/null +++ b/data/core.telegram.org/type/Config.html @@ -0,0 +1,162 @@ + + + + + Config + + + + + + + + + + + + + +
+ +
+
+
+ +

Config

+ +

Object contains info on API configuring parameters.

+

+ +
+
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+
+---functions---
+
+help.getConfig#c4f9186b = Config;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
configCurrent configuration
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getConfigReturns current configuration, icluding data center configuration.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Contact.html b/data/core.telegram.org/type/Contact.html new file mode 100644 index 0000000000..1908495f25 --- /dev/null +++ b/data/core.telegram.org/type/Contact.html @@ -0,0 +1,143 @@ + + + + + Contact + + + + + + + + + + + + + +
+ +
+
+
+ +

Contact

+ +

A contact of the current user.

+

+ +
+
contact#145ade0b user_id:long mutual:Bool = Contact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contactA contact of the current user that is registered in the system.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ContactStatus.html b/data/core.telegram.org/type/ContactStatus.html new file mode 100644 index 0000000000..5479d46446 --- /dev/null +++ b/data/core.telegram.org/type/ContactStatus.html @@ -0,0 +1,143 @@ + + + + + ContactStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

ContactStatus

+ +

Contact status: online / offline.

+

+ +
+
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contactStatusContact status: online / offline.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DataJSON.html b/data/core.telegram.org/type/DataJSON.html new file mode 100644 index 0000000000..1b536eb2f9 --- /dev/null +++ b/data/core.telegram.org/type/DataJSON.html @@ -0,0 +1,168 @@ + + + + + DataJSON + + + + + + + + + + + + + +
+ +
+
+
+ +

DataJSON

+ +

Represent a JSON-encoded object

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;
+
+---functions---
+
+bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;
+
+phone.getCallConfig#55451fa9 = DataJSON;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
dataJSONRepresents a json-encoded object
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
bots.sendCustomRequestSends a custom request; for bots only
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DcOption.html b/data/core.telegram.org/type/DcOption.html new file mode 100644 index 0000000000..dc9fa76764 --- /dev/null +++ b/data/core.telegram.org/type/DcOption.html @@ -0,0 +1,143 @@ + + + + + DcOption + + + + + + + + + + + + + +
+ +
+
+
+ +

DcOption

+ +

Information for connection to data centre.

+

+ +
+
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
dcOptionData centre
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DecryptedDataBlock.html b/data/core.telegram.org/type/DecryptedDataBlock.html new file mode 100644 index 0000000000..1ce54fed4a --- /dev/null +++ b/data/core.telegram.org/type/DecryptedDataBlock.html @@ -0,0 +1,128 @@ + + + + + DecryptedDataBlock + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedDataBlock

+ +

VoIP decrypted data block

+

+ +
+
Type schema is not available in the selected layer.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DecryptedMessage.html b/data/core.telegram.org/type/DecryptedMessage.html new file mode 100644 index 0000000000..44487a5b19 --- /dev/null +++ b/data/core.telegram.org/type/DecryptedMessage.html @@ -0,0 +1,140 @@ + + + + + DecryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedMessage

+ +

Object describes the contents of an encrypted message.

+

+ +
+
===8===
+decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+
+===17===
+decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
+
+===45===
+decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
+
+===73===
+decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DecryptedMessageAction.html b/data/core.telegram.org/type/DecryptedMessageAction.html new file mode 100644 index 0000000000..273e9ae356 --- /dev/null +++ b/data/core.telegram.org/type/DecryptedMessageAction.html @@ -0,0 +1,145 @@ + + + + + DecryptedMessageAction + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedMessageAction

+ +

Object describes the action to which a service message is linked.

+

+ +
+
===8===
+decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;
+decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;
+
+===17===
+decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;
+decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;
+decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;
+
+===20===
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
+decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DecryptedMessageLayer.html b/data/core.telegram.org/type/DecryptedMessageLayer.html new file mode 100644 index 0000000000..bb15e1cfc6 --- /dev/null +++ b/data/core.telegram.org/type/DecryptedMessageLayer.html @@ -0,0 +1,129 @@ + + + + + DecryptedMessageLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedMessageLayer

+ +

Object describes encrypted message content in relation to the required layer.

+

+ +
+
===17===
+decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DecryptedMessageMedia.html b/data/core.telegram.org/type/DecryptedMessageMedia.html new file mode 100644 index 0000000000..4f281691e6 --- /dev/null +++ b/data/core.telegram.org/type/DecryptedMessageMedia.html @@ -0,0 +1,149 @@ + + + + + DecryptedMessageMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedMessageMedia

+ +

Object describes media contents of an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;
+decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;
+decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
+decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===17===
+decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===23===
+decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
+decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
+decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
+decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;
+decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Dialog.html b/data/core.telegram.org/type/Dialog.html new file mode 100644 index 0000000000..0343ee4052 --- /dev/null +++ b/data/core.telegram.org/type/Dialog.html @@ -0,0 +1,148 @@ + + + + + Dialog + + + + + + + + + + + + + +
+ +
+
+
+ +

Dialog

+ +

Chat info.

+

+ +
+
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
+dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
dialogChat
dialogFolderDialog in folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DialogFilter.html b/data/core.telegram.org/type/DialogFilter.html new file mode 100644 index 0000000000..e3b54f7bef --- /dev/null +++ b/data/core.telegram.org/type/DialogFilter.html @@ -0,0 +1,143 @@ + + + + + DialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

DialogFilter

+ +

Dialog filter (folders)

+

+ +
+
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
dialogFilterDialog filter (folder)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DialogFilterSuggested.html b/data/core.telegram.org/type/DialogFilterSuggested.html new file mode 100644 index 0000000000..f9f20477ee --- /dev/null +++ b/data/core.telegram.org/type/DialogFilterSuggested.html @@ -0,0 +1,143 @@ + + + + + DialogFilterSuggested + + + + + + + + + + + + + +
+ +
+
+
+ +

DialogFilterSuggested

+ +

Suggested dialog filters (folders)

+

+ +
+
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
dialogFilterSuggestedSuggested folders
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DisabledFeature.html b/data/core.telegram.org/type/DisabledFeature.html new file mode 100644 index 0000000000..5cff87c98c --- /dev/null +++ b/data/core.telegram.org/type/DisabledFeature.html @@ -0,0 +1,128 @@ + + + + + DisabledFeature + + + + + + + + + + + + + +
+ +
+
+
+ +

DisabledFeature

+ +

A disabled feature

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Document.html b/data/core.telegram.org/type/Document.html new file mode 100644 index 0000000000..5a922e2dfa --- /dev/null +++ b/data/core.telegram.org/type/Document.html @@ -0,0 +1,173 @@ + + + + + Document + + + + + + + + + + + + + +
+ +
+
+
+ +

Document

+ +

A document.

+

+ +
+
documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+
+---functions---
+
+messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
+
+account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
documentEmptyEmpty constructor, document doesn't exist.
documentDocument
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
account.uploadThemeUpload theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DocumentAttribute.html b/data/core.telegram.org/type/DocumentAttribute.html new file mode 100644 index 0000000000..3c8f4eb2bc --- /dev/null +++ b/data/core.telegram.org/type/DocumentAttribute.html @@ -0,0 +1,173 @@ + + + + + DocumentAttribute + + + + + + + + + + + + + +
+ +
+
+
+ +

DocumentAttribute

+ +

Various possible attributes of a document (used to define if it's a sticker, a GIF, a video, a mask sticker, an image, an audio, and so on)

+

+ +
+
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
+documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
+documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
documentAttributeImageSizeDefines the width and height of an image uploaded as document
documentAttributeAnimatedDefines an animated GIF
documentAttributeStickerDefines a sticker
documentAttributeVideoDefines a video
documentAttributeAudioRepresents an audio file
documentAttributeFilenameA simple document with a file name
documentAttributeHasStickersWhether the current document has stickers attached
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DraftMessage.html b/data/core.telegram.org/type/DraftMessage.html new file mode 100644 index 0000000000..98790757d8 --- /dev/null +++ b/data/core.telegram.org/type/DraftMessage.html @@ -0,0 +1,151 @@ + + + + + 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/EmojiKeyword.html b/data/core.telegram.org/type/EmojiKeyword.html new file mode 100644 index 0000000000..b9a0b64f8a --- /dev/null +++ b/data/core.telegram.org/type/EmojiKeyword.html @@ -0,0 +1,148 @@ + + + + + EmojiKeyword + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiKeyword

+ +

Emoji keyword

+

+ +
+
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;
+emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
emojiKeywordEmoji keyword
emojiKeywordDeletedDeleted emoji keyword
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EmojiKeywordsDifference.html b/data/core.telegram.org/type/EmojiKeywordsDifference.html new file mode 100644 index 0000000000..f883b296d7 --- /dev/null +++ b/data/core.telegram.org/type/EmojiKeywordsDifference.html @@ -0,0 +1,167 @@ + + + + + EmojiKeywordsDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiKeywordsDifference

+ +

New emoji keywords

+

+ +
+
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+
+---functions---
+
+messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;
+messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
emojiKeywordsDifferenceChanges to emoji keywords
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getEmojiKeywordsGet localized emoji keywords
messages.getEmojiKeywordsDifferenceGet changed emoji keywords
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EmojiLanguage.html b/data/core.telegram.org/type/EmojiLanguage.html new file mode 100644 index 0000000000..d71fa5aba2 --- /dev/null +++ b/data/core.telegram.org/type/EmojiLanguage.html @@ -0,0 +1,143 @@ + + + + + EmojiLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiLanguage

+ +

Emoji language

+

+ +
+
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
emojiLanguageEmoji language
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EmojiURL.html b/data/core.telegram.org/type/EmojiURL.html new file mode 100644 index 0000000000..83d6f66f1a --- /dev/null +++ b/data/core.telegram.org/type/EmojiURL.html @@ -0,0 +1,162 @@ + + + + + EmojiURL + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiURL

+ +

Emoji URL

+

+ +
+
emojiURL#a575739d url:string = EmojiURL;
+
+---functions---
+
+messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
emojiURLAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EncryptedChat.html b/data/core.telegram.org/type/EncryptedChat.html new file mode 100644 index 0000000000..b7d67a122f --- /dev/null +++ b/data/core.telegram.org/type/EncryptedChat.html @@ -0,0 +1,187 @@ + + + + + EncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedChat

+ +

Object contains info on an encrypted chat.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+
+---functions---
+
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedChatEmptyEmpty constructor.
encryptedChatWaitingChat waiting for approval of second participant.
encryptedChatRequestedRequest to create an encrypted chat.
encryptedChatEncrypted chat
encryptedChatDiscardedDiscarded or deleted chat.
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.acceptEncryptionConfirms creation of a secret chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EncryptedFile.html b/data/core.telegram.org/type/EncryptedFile.html new file mode 100644 index 0000000000..461b6767b2 --- /dev/null +++ b/data/core.telegram.org/type/EncryptedFile.html @@ -0,0 +1,167 @@ + + + + + EncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedFile

+ +

Seta an encrypted file.

+

+ +
+
encryptedFileEmpty#c21f497e = EncryptedFile;
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+---functions---
+
+messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedFileEmptyEmpty constructor, unexisitng file.
encryptedFileEncrypted file.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EncryptedMessage.html b/data/core.telegram.org/type/EncryptedMessage.html new file mode 100644 index 0000000000..0096c27c9a --- /dev/null +++ b/data/core.telegram.org/type/EncryptedMessage.html @@ -0,0 +1,148 @@ + + + + + EncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedMessage

+ +

Object contains encrypted message.

+

+ +
+
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedMessageEncrypted message.
encryptedMessageServiceEncrypted service message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Error.html b/data/core.telegram.org/type/Error.html new file mode 100644 index 0000000000..0bdedb2b31 --- /dev/null +++ b/data/core.telegram.org/type/Error.html @@ -0,0 +1,143 @@ + + + + + Error + + + + + + + + + + + + + +
+ +
+
+
+ +

Error

+ +

An object containing a query error.

+

+ +
+
error#c4b9f9bb code:int text:string = Error;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
errorError.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ExportedChatInvite.html b/data/core.telegram.org/type/ExportedChatInvite.html new file mode 100644 index 0000000000..aed3752f1b --- /dev/null +++ b/data/core.telegram.org/type/ExportedChatInvite.html @@ -0,0 +1,162 @@ + + + + + ExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

ExportedChatInvite

+ +

Exported chat invite

+

+ +
+
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
+
+---functions---
+
+messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatInviteExportedExported chat invite
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.exportChatInviteExport an invite link for a chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ExportedMessageLink.html b/data/core.telegram.org/type/ExportedMessageLink.html new file mode 100644 index 0000000000..cd7f496ad9 --- /dev/null +++ b/data/core.telegram.org/type/ExportedMessageLink.html @@ -0,0 +1,162 @@ + + + + + ExportedMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

ExportedMessageLink

+ +

HTTP link and embed info of channel message

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+
+---functions---
+
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
exportedMessageLinkLink to a message in a supergroup/channel
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/FileHash.html b/data/core.telegram.org/type/FileHash.html new file mode 100644 index 0000000000..528661d09d --- /dev/null +++ b/data/core.telegram.org/type/FileHash.html @@ -0,0 +1,143 @@ + + + + + FileHash + + + + + + + + + + + + + +
+ +
+
+
+ +

FileHash

+ +

Hash of an uploaded file, to be checked for validity after download

+

+ +
+
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
fileHashSHA256 Hash of an uploaded file, to be checked for validity after download
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/FileLocation.html b/data/core.telegram.org/type/FileLocation.html new file mode 100644 index 0000000000..7f3f05d54a --- /dev/null +++ b/data/core.telegram.org/type/FileLocation.html @@ -0,0 +1,128 @@ + + + + + FileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

FileLocation

+ +

Indicates the location of a photo, will be deprecated soon

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Folder.html b/data/core.telegram.org/type/Folder.html new file mode 100644 index 0000000000..39366f9a02 --- /dev/null +++ b/data/core.telegram.org/type/Folder.html @@ -0,0 +1,143 @@ + + + + + Folder + + + + + + + + + + + + + +
+ +
+
+
+ +

Folder

+ +

A folder

+

+ +
+
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
folderFolder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/FolderPeer.html b/data/core.telegram.org/type/FolderPeer.html new file mode 100644 index 0000000000..b04a296dcf --- /dev/null +++ b/data/core.telegram.org/type/FolderPeer.html @@ -0,0 +1,143 @@ + + + + + FolderPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

FolderPeer

+ +

Peer associated to folder

+

+ +
+
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
folderPeerPeer in a folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Game.html b/data/core.telegram.org/type/Game.html new file mode 100644 index 0000000000..dcba7cddad --- /dev/null +++ b/data/core.telegram.org/type/Game.html @@ -0,0 +1,143 @@ + + + + + Game + + + + + + + + + + + + + +
+ +
+
+
+ +

Game

+ +

Indicates an already sent game

+

+ +
+
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
gameIndicates an already sent game
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GeoPoint.html b/data/core.telegram.org/type/GeoPoint.html new file mode 100644 index 0000000000..3011f0e13c --- /dev/null +++ b/data/core.telegram.org/type/GeoPoint.html @@ -0,0 +1,148 @@ + + + + + GeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

GeoPoint

+ +

Object defines a GeoPoint.

+

+ +
+
geoPointEmpty#1117dd5f = GeoPoint;
+geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
geoPointEmptyEmpty constructor.
geoPointGeoPoint.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GlobalPrivacySettings.html b/data/core.telegram.org/type/GlobalPrivacySettings.html new file mode 100644 index 0000000000..dd3915ea7e --- /dev/null +++ b/data/core.telegram.org/type/GlobalPrivacySettings.html @@ -0,0 +1,167 @@ + + + + + GlobalPrivacySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

GlobalPrivacySettings

+ +

Global privacy settings

+

+ +
+
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
+
+---functions---
+
+account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
+account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
globalPrivacySettingsGlobal privacy settings
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
account.getGlobalPrivacySettingsSet global privacy settings
account.setGlobalPrivacySettingsSet global privacy settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GroupCall.html b/data/core.telegram.org/type/GroupCall.html new file mode 100644 index 0000000000..13f1d9cf8b --- /dev/null +++ b/data/core.telegram.org/type/GroupCall.html @@ -0,0 +1,148 @@ + + + + + GroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCall

+ +

A group call

+

+ +
+
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
+groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true rtmp_stream:flags.12?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
groupCallDiscardedAn ended group call
groupCallInfo about a group call or livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GroupCallParticipant.html b/data/core.telegram.org/type/GroupCallParticipant.html new file mode 100644 index 0000000000..b8d2891a5c --- /dev/null +++ b/data/core.telegram.org/type/GroupCallParticipant.html @@ -0,0 +1,143 @@ + + + + + GroupCallParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCallParticipant

+ +

Info about a group call participant

+

+ +
+
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
groupCallParticipantInfo about a group call participant
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GroupCallParticipantVideo.html b/data/core.telegram.org/type/GroupCallParticipantVideo.html new file mode 100644 index 0000000000..d39d5ab6df --- /dev/null +++ b/data/core.telegram.org/type/GroupCallParticipantVideo.html @@ -0,0 +1,143 @@ + + + + + GroupCallParticipantVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCallParticipantVideo

+ +

Info about a video stream

+

+ +
+
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
groupCallParticipantVideoInfo about a video stream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GroupCallParticipantVideoSourceGroup.html b/data/core.telegram.org/type/GroupCallParticipantVideoSourceGroup.html new file mode 100644 index 0000000000..f170653f12 --- /dev/null +++ b/data/core.telegram.org/type/GroupCallParticipantVideoSourceGroup.html @@ -0,0 +1,143 @@ + + + + + GroupCallParticipantVideoSourceGroup + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCallParticipantVideoSourceGroup

+ +

Describes a group of video synchronization source identifiers

+

+ +
+
groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
groupCallParticipantVideoSourceGroupDescribes a group of video synchronization source identifiers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/HighScore.html b/data/core.telegram.org/type/HighScore.html new file mode 100644 index 0000000000..400288806c --- /dev/null +++ b/data/core.telegram.org/type/HighScore.html @@ -0,0 +1,143 @@ + + + + + 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/ImportedContact.html b/data/core.telegram.org/type/ImportedContact.html new file mode 100644 index 0000000000..9b2c4ab572 --- /dev/null +++ b/data/core.telegram.org/type/ImportedContact.html @@ -0,0 +1,143 @@ + + + + + ImportedContact + + + + + + + + + + + + + +
+ +
+
+
+ +

ImportedContact

+ +

Object contains info on a successfully imported contact.

+

+ +
+
importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
importedContactSuccessfully imported contact.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InlineQueryPeerType.html b/data/core.telegram.org/type/InlineQueryPeerType.html new file mode 100644 index 0000000000..8c730017db --- /dev/null +++ b/data/core.telegram.org/type/InlineQueryPeerType.html @@ -0,0 +1,163 @@ + + + + + InlineQueryPeerType + + + + + + + + + + + + + +
+ +
+
+
+ +

InlineQueryPeerType

+ +

Type of the chat from which the inline query was sent.

+

+ +
+
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
+inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
+inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
+inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
+inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inlineQueryPeerTypeSameBotPMThe inline query was sent in a private chat with the bot itself
inlineQueryPeerTypePMThe inline query was sent in a private chat
inlineQueryPeerTypeChatThe inline query was sent in a chat
inlineQueryPeerTypeMegagroupThe inline query was sent in a supergroup
inlineQueryPeerTypeBroadcastThe inline query was sent in a channel
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputAppEvent.html b/data/core.telegram.org/type/InputAppEvent.html new file mode 100644 index 0000000000..fac7f5bf18 --- /dev/null +++ b/data/core.telegram.org/type/InputAppEvent.html @@ -0,0 +1,143 @@ + + + + + InputAppEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

InputAppEvent

+ +

Object contains info about an event that occured in the application.

+

+ +
+
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputAppEventEvent that occured in the application.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputBotInlineMessage.html b/data/core.telegram.org/type/InputBotInlineMessage.html new file mode 100644 index 0000000000..a345efb14a --- /dev/null +++ b/data/core.telegram.org/type/InputBotInlineMessage.html @@ -0,0 +1,173 @@ + + + + + InputBotInlineMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

InputBotInlineMessage

+ +

Represents a sent inline message from the perspective of a bot

+

+ +
+
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputBotInlineMessageMediaAutoA media
inputBotInlineMessageTextSimple text message
inputBotInlineMessageMediaGeoGeolocation
inputBotInlineMessageMediaVenueVenue
inputBotInlineMessageMediaContactA contact
inputBotInlineMessageGameA game
inputBotInlineMessageMediaInvoiceAn invoice
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputBotInlineMessageID.html b/data/core.telegram.org/type/InputBotInlineMessageID.html new file mode 100644 index 0000000000..e9fd77229c --- /dev/null +++ b/data/core.telegram.org/type/InputBotInlineMessageID.html @@ -0,0 +1,148 @@ + + + + + InputBotInlineMessageID + + + + + + + + + + + + + +
+ +
+
+
+ +

InputBotInlineMessageID

+ +

Represents a sent inline message from the perspective of a bot

+

+ +
+
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
+inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputBotInlineMessageIDRepresents a sent inline message from the perspective of a bot
inputBotInlineMessageID64Represents a sent inline message from the perspective of a bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputBotInlineResult.html b/data/core.telegram.org/type/InputBotInlineResult.html new file mode 100644 index 0000000000..afc4b9f91f --- /dev/null +++ b/data/core.telegram.org/type/InputBotInlineResult.html @@ -0,0 +1,158 @@ + + + + + InputBotInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

InputBotInlineResult

+ +

Inline bot result

+

+ +
+
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputBotInlineResultAn inline bot result
inputBotInlineResultPhotoPhoto
inputBotInlineResultDocumentDocument (media of any type except for photos)
inputBotInlineResultGameGame
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputChannel.html b/data/core.telegram.org/type/InputChannel.html new file mode 100644 index 0000000000..707ea775f6 --- /dev/null +++ b/data/core.telegram.org/type/InputChannel.html @@ -0,0 +1,153 @@ + + + + + InputChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

InputChannel

+ +

Represents a channel

+

+ +
+
inputChannelEmpty#ee8c1e86 = InputChannel;
+inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;
+inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputChannelEmptyRepresents the absence of a channel
inputChannelRepresents a channel
inputChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputChatPhoto.html b/data/core.telegram.org/type/InputChatPhoto.html new file mode 100644 index 0000000000..00b9754a47 --- /dev/null +++ b/data/core.telegram.org/type/InputChatPhoto.html @@ -0,0 +1,153 @@ + + + + + InputChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

InputChatPhoto

+ +

Defines a new group profile photo.

+

+ +
+
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;
+inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
+inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputChatPhotoEmptyEmpty constructor, remove group photo.
inputChatUploadedPhotoNew photo to be set as group profile photo.
inputChatPhotoExisting photo to be set as a chat profile photo.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputCheckPasswordSRP.html b/data/core.telegram.org/type/InputCheckPasswordSRP.html new file mode 100644 index 0000000000..7efd169546 --- /dev/null +++ b/data/core.telegram.org/type/InputCheckPasswordSRP.html @@ -0,0 +1,151 @@ + + + + + InputCheckPasswordSRP + + + + + + + + + + + + + +
+ +
+
+
+ +

InputCheckPasswordSRP

+ +

Constructors for checking the validity of a 2FA SRP password

+

+ +
+
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
+inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputCheckPasswordEmptyThere is no password
inputCheckPasswordSRPConstructor for checking the validity of a 2FA SRP password (see SRP)
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputClientProxy.html b/data/core.telegram.org/type/InputClientProxy.html new file mode 100644 index 0000000000..2e7b988df4 --- /dev/null +++ b/data/core.telegram.org/type/InputClientProxy.html @@ -0,0 +1,145 @@ + + + + + InputClientProxy + + + + + + + + + + + + + +
+ +
+
+
+ +

InputClientProxy

+ +

Info about an MTProxy used to connect.

+

+ +
+
inputClientProxy#75588b3f address:string port:int = InputClientProxy;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputClientProxyInfo about an MTProxy used to connect.
+

Related pages

+

MTProto transports

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputContact.html b/data/core.telegram.org/type/InputContact.html new file mode 100644 index 0000000000..8992628ec8 --- /dev/null +++ b/data/core.telegram.org/type/InputContact.html @@ -0,0 +1,143 @@ + + + + + InputContact + + + + + + + + + + + + + +
+ +
+
+
+ +

InputContact

+ +

Object defines a contact from the user's phonebook.

+

+ +
+
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputPhoneContactPhone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputDialogPeer.html b/data/core.telegram.org/type/InputDialogPeer.html new file mode 100644 index 0000000000..f1be186d1c --- /dev/null +++ b/data/core.telegram.org/type/InputDialogPeer.html @@ -0,0 +1,148 @@ + + + + + InputDialogPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputDialogPeer

+ +

Peer, or all peers in a certain folder

+

+ +
+
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
+inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputDialogPeerA peer
inputDialogPeerFolderAll peers in a folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputDocument.html b/data/core.telegram.org/type/InputDocument.html new file mode 100644 index 0000000000..dbbcccb487 --- /dev/null +++ b/data/core.telegram.org/type/InputDocument.html @@ -0,0 +1,148 @@ + + + + + InputDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

InputDocument

+ +

Defines a document for subsequent interaction.

+

+ +
+
inputDocumentEmpty#72f0eaae = InputDocument;
+inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputDocumentEmptyEmpty constructor.
inputDocumentDefines a video for subsequent interaction.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputEncryptedChat.html b/data/core.telegram.org/type/InputEncryptedChat.html new file mode 100644 index 0000000000..f8a4ee9fd3 --- /dev/null +++ b/data/core.telegram.org/type/InputEncryptedChat.html @@ -0,0 +1,143 @@ + + + + + InputEncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

InputEncryptedChat

+ +

Object sets an encrypted chat ID.

+

+ +
+
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputEncryptedChatCreates an encrypted chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputEncryptedFile.html b/data/core.telegram.org/type/InputEncryptedFile.html new file mode 100644 index 0000000000..92b7416df6 --- /dev/null +++ b/data/core.telegram.org/type/InputEncryptedFile.html @@ -0,0 +1,158 @@ + + + + + InputEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

InputEncryptedFile

+ +

Object sets encrypted file for attachment

+

+ +
+
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
+inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
+inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
+inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputEncryptedFileEmptyEmpty constructor.
inputEncryptedFileUploadedSets new encrypted file saved by parts using upload.saveFilePart method.
inputEncryptedFileSets forwarded encrypted file for attachment.
inputEncryptedFileBigUploadedAssigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputFile.html b/data/core.telegram.org/type/InputFile.html new file mode 100644 index 0000000000..3b71dbb92a --- /dev/null +++ b/data/core.telegram.org/type/InputFile.html @@ -0,0 +1,148 @@ + + + + + InputFile + + + + + + + + + + + + + +
+ +
+
+
+ +

InputFile

+ +

Defines a file uploaded by the client.

+

+ +
+
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
+inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputFileDefines a file saved in parts using the method upload.saveFilePart.
inputFileBigAssigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputFileLocation.html b/data/core.telegram.org/type/InputFileLocation.html new file mode 100644 index 0000000000..5628c999b6 --- /dev/null +++ b/data/core.telegram.org/type/InputFileLocation.html @@ -0,0 +1,188 @@ + + + + + InputFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

InputFileLocation

+ +

Defines the location of a file for download.

+

+ +
+
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
+inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
+inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
+inputTakeoutFileLocation#29be5899 = InputFileLocation;
+inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
+inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
+inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
+inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputFileLocationDEPRECATED location of a photo
inputEncryptedFileLocationLocation of encrypted secret chat file.
inputDocumentFileLocationDocument location (video, voice, audio, basically every type except photo)
inputSecureFileLocationLocation of encrypted telegram passport file.
inputTakeoutFileLocationEmpty constructor for takeout
inputPhotoFileLocationUse this object to download a photo with upload.getFile method
inputPhotoLegacyFileLocationLegacy file location
inputPeerPhotoFileLocationLocation of profile photo of channel/group/supergroup/user
inputStickerSetThumbLocation of stickerset thumbnail (see files)
inputGroupCallStreamChunk of a livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputFolderPeer.html b/data/core.telegram.org/type/InputFolderPeer.html new file mode 100644 index 0000000000..01c2acd2b5 --- /dev/null +++ b/data/core.telegram.org/type/InputFolderPeer.html @@ -0,0 +1,143 @@ + + + + + InputFolderPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputFolderPeer

+ +

Peer in a folder

+

+ +
+
inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputFolderPeerPeer in a folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputGame.html b/data/core.telegram.org/type/InputGame.html new file mode 100644 index 0000000000..0793c16933 --- /dev/null +++ b/data/core.telegram.org/type/InputGame.html @@ -0,0 +1,148 @@ + + + + + InputGame + + + + + + + + + + + + + +
+ +
+
+
+ +

InputGame

+ +

A game to send

+

+ +
+
inputGameID#32c3e77 id:long access_hash:long = InputGame;
+inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputGameIDIndicates an already sent game
inputGameShortNameGame by short name
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputGeoPoint.html b/data/core.telegram.org/type/InputGeoPoint.html new file mode 100644 index 0000000000..7cd476bd42 --- /dev/null +++ b/data/core.telegram.org/type/InputGeoPoint.html @@ -0,0 +1,148 @@ + + + + + InputGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

InputGeoPoint

+ +

Defines a GeoPoint.

+

+ +
+
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputGeoPointEmptyEmpty GeoPoint constructor.
inputGeoPointDefines a GeoPoint by its coordinates.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputGroupCall.html b/data/core.telegram.org/type/InputGroupCall.html new file mode 100644 index 0000000000..c1dc72f9a4 --- /dev/null +++ b/data/core.telegram.org/type/InputGroupCall.html @@ -0,0 +1,143 @@ + + + + + InputGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

InputGroupCall

+ +

Indicates a group call

+

+ +
+
inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputGroupCallPoints to a specific group call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputMedia.html b/data/core.telegram.org/type/InputMedia.html new file mode 100644 index 0000000000..048a3c1d2b --- /dev/null +++ b/data/core.telegram.org/type/InputMedia.html @@ -0,0 +1,213 @@ + + + + + InputMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

InputMedia

+ +

Defines media content of a message.

+

+ +
+
inputMediaEmpty#9664f57f = InputMedia;
+inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;
+inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;
+inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;
+inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;
+inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;
+inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaGame#d33f43f3 id:InputGame = InputMedia;
+inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
+inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+inputMediaDice#e66fbf7b emoticon:string = InputMedia;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputMediaEmptyEmpty media content of a message.
inputMediaUploadedPhotoPhoto
inputMediaPhotoForwarded photo
inputMediaGeoPointMap.
inputMediaContactPhonebook contact
inputMediaUploadedDocumentNew document
inputMediaDocumentForwarded document
inputMediaVenueCan be used to send a venue geolocation.
inputMediaPhotoExternalNew photo that will be uploaded by the server using the specified URL
inputMediaDocumentExternalDocument that will be downloaded by the telegram servers
inputMediaGameA game
inputMediaInvoiceGenerated invoice of a bot payment
inputMediaGeoLiveLive geographical location
inputMediaPollA poll
inputMediaDiceSend a dice in the chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputMessage.html b/data/core.telegram.org/type/InputMessage.html new file mode 100644 index 0000000000..07b7c6ef55 --- /dev/null +++ b/data/core.telegram.org/type/InputMessage.html @@ -0,0 +1,158 @@ + + + + + InputMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

InputMessage

+ +

A message

+

+ +
+
inputMessageID#a676a322 id:int = InputMessage;
+inputMessageReplyTo#bad88395 id:int = InputMessage;
+inputMessagePinned#86872538 = InputMessage;
+inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputMessageIDMessage by ID
inputMessageReplyToMessage to which the specified message replies to
inputMessagePinnedPinned message
inputMessageCallbackQueryUsed by bots for fetching information about the message that originated a callback query
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputNotifyPeer.html b/data/core.telegram.org/type/InputNotifyPeer.html new file mode 100644 index 0000000000..29b7da1285 --- /dev/null +++ b/data/core.telegram.org/type/InputNotifyPeer.html @@ -0,0 +1,158 @@ + + + + + InputNotifyPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputNotifyPeer

+ +

Object defines the set of users and/or groups that generate notifications.

+

+ +
+
inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;
+inputNotifyUsers#193b4417 = InputNotifyPeer;
+inputNotifyChats#4a95e84e = InputNotifyPeer;
+inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputNotifyPeerNotifications generated by a certain user or group.
inputNotifyUsersNotifications generated by all users.
inputNotifyChatsNotifications generated by all groups.
inputNotifyBroadcastsAll channels
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPaymentCredentials.html b/data/core.telegram.org/type/InputPaymentCredentials.html new file mode 100644 index 0000000000..a1022825e7 --- /dev/null +++ b/data/core.telegram.org/type/InputPaymentCredentials.html @@ -0,0 +1,158 @@ + + + + + InputPaymentCredentials + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPaymentCredentials

+ +

Payment credentials

+

+ +
+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPaymentCredentialsSavedSaved payment credentials
inputPaymentCredentialsPayment credentials
inputPaymentCredentialsApplePayApple pay payment credentials
inputPaymentCredentialsGooglePayGoogle Pay payment credentials
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPeer.html b/data/core.telegram.org/type/InputPeer.html new file mode 100644 index 0000000000..4ab7b227c0 --- /dev/null +++ b/data/core.telegram.org/type/InputPeer.html @@ -0,0 +1,173 @@ + + + + + InputPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPeer

+ +

Peer

+

+ +
+
inputPeerEmpty#7f3b18ea = InputPeer;
+inputPeerSelf#7da07ec9 = InputPeer;
+inputPeerChat#35a95cb9 chat_id:long = InputPeer;
+inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
+inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
+inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;
+inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPeerEmptyAn empty constructor, no user or chat is defined.
inputPeerSelfDefines the current user.
inputPeerChatDefines a chat for further interaction.
inputPeerUserDefines a user for further interaction.
inputPeerChannelDefines a channel for further interaction.
inputPeerUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
inputPeerChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPeerNotifySettings.html b/data/core.telegram.org/type/InputPeerNotifySettings.html new file mode 100644 index 0000000000..8d9d1ca7d9 --- /dev/null +++ b/data/core.telegram.org/type/InputPeerNotifySettings.html @@ -0,0 +1,143 @@ + + + + + InputPeerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPeerNotifySettings

+ +

Notifications settings.

+

+ +
+
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputPeerNotifySettingsNotification settings.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPhoneCall.html b/data/core.telegram.org/type/InputPhoneCall.html new file mode 100644 index 0000000000..d94189a022 --- /dev/null +++ b/data/core.telegram.org/type/InputPhoneCall.html @@ -0,0 +1,143 @@ + + + + + InputPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPhoneCall

+ +

Phone call

+

+ +
+
inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputPhoneCallPhone call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPhoto.html b/data/core.telegram.org/type/InputPhoto.html new file mode 100644 index 0000000000..a8c395e2c9 --- /dev/null +++ b/data/core.telegram.org/type/InputPhoto.html @@ -0,0 +1,148 @@ + + + + + InputPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPhoto

+ +

Defines a photo for further interaction.

+

+ +
+
inputPhotoEmpty#1cd7bf0d = InputPhoto;
+inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPhotoEmptyEmpty constructor.
inputPhotoDefines a photo for further interaction.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPrivacyKey.html b/data/core.telegram.org/type/InputPrivacyKey.html new file mode 100644 index 0000000000..ea4b22031f --- /dev/null +++ b/data/core.telegram.org/type/InputPrivacyKey.html @@ -0,0 +1,178 @@ + + + + + InputPrivacyKey + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPrivacyKey

+ +

Privacy key

+

+ +
+
inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
+inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
+inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
+inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
+inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
+inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
+inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
+inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPrivacyKeyStatusTimestampWhether we can see the exact last online timestamp of the user
inputPrivacyKeyChatInviteWhether the user can be invited to chats
inputPrivacyKeyPhoneCallWhether the user will accept phone calls
inputPrivacyKeyPhoneP2PWhether the user allows P2P communication during VoIP calls
inputPrivacyKeyForwardsWhether messages forwarded from this user will be anonymous
inputPrivacyKeyProfilePhotoWhether people will be able to see the user's profile picture
inputPrivacyKeyPhoneNumberWhether people will be able to see the user's phone number
inputPrivacyKeyAddedByPhoneWhether people can add you to their contact list by your phone number
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPrivacyRule.html b/data/core.telegram.org/type/InputPrivacyRule.html new file mode 100644 index 0000000000..f69fefd909 --- /dev/null +++ b/data/core.telegram.org/type/InputPrivacyRule.html @@ -0,0 +1,178 @@ + + + + + InputPrivacyRule + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPrivacyRule

+ +

Privacy rule

+

+ +
+
inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;
+inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
+inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;
+inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
+inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;
+inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPrivacyValueAllowContactsAllow only contacts
inputPrivacyValueAllowAllAllow all users
inputPrivacyValueAllowUsersAllow only certain users
inputPrivacyValueDisallowContactsDisallow only contacts
inputPrivacyValueDisallowAllDisallow all
inputPrivacyValueDisallowUsersDisallow only certain users
inputPrivacyValueAllowChatParticipantsAllow only participants of certain chats
inputPrivacyValueDisallowChatParticipantsDisallow only participants of certain chats
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputSecureFile.html b/data/core.telegram.org/type/InputSecureFile.html new file mode 100644 index 0000000000..3d03f4afc7 --- /dev/null +++ b/data/core.telegram.org/type/InputSecureFile.html @@ -0,0 +1,151 @@ + + + + + InputSecureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

InputSecureFile

+ +

Secure passport file, for more info see the passport docs »

+

+ +
+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputSecureFileUploadedUploaded secure file, for more info see the passport docs »
inputSecureFilePreuploaded passport file, for more info see the passport docs »
+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputSecureValue.html b/data/core.telegram.org/type/InputSecureValue.html new file mode 100644 index 0000000000..6de27de5d0 --- /dev/null +++ b/data/core.telegram.org/type/InputSecureValue.html @@ -0,0 +1,145 @@ + + + + + InputSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

InputSecureValue

+ +

Secure value, for more info see the passport docs »

+

+ +
+
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputSecureValueSecure value, for more info see the passport docs »
+

Related pages

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputSingleMedia.html b/data/core.telegram.org/type/InputSingleMedia.html new file mode 100644 index 0000000000..e414427aa0 --- /dev/null +++ b/data/core.telegram.org/type/InputSingleMedia.html @@ -0,0 +1,148 @@ + + + + + InputSingleMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

InputSingleMedia

+ +

A single media in an album or grouped media sent with messages.sendMultiMedia.

+

+ +
+
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputSingleMediaA single media in an album or grouped media sent with messages.sendMultiMedia.
+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

messages.sendMultiMedia

+

Send an album or grouped media

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputStickerSet.html b/data/core.telegram.org/type/InputStickerSet.html new file mode 100644 index 0000000000..4683b32505 --- /dev/null +++ b/data/core.telegram.org/type/InputStickerSet.html @@ -0,0 +1,168 @@ + + + + + InputStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

InputStickerSet

+ +

Represents a stickerset

+

+ +
+
inputStickerSetEmpty#ffb62b95 = InputStickerSet;
+inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
+inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
+inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
+inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputStickerSetEmptyEmpty constructor
inputStickerSetIDStickerset by ID
inputStickerSetShortNameStickerset by short name, from tg://addstickers?set=short_name
inputStickerSetAnimatedEmojiAnimated emojis stickerset
inputStickerSetDiceSend a dice
inputStickerSetAnimatedEmojiAnimationsAnimated emoji reaction stickerset (contains animations to play when a user clicks on a given animated emoji)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputStickerSetItem.html b/data/core.telegram.org/type/InputStickerSetItem.html new file mode 100644 index 0000000000..67da6bdecb --- /dev/null +++ b/data/core.telegram.org/type/InputStickerSetItem.html @@ -0,0 +1,143 @@ + + + + + InputStickerSetItem + + + + + + + + + + + + + +
+ +
+
+
+ +

InputStickerSetItem

+ +

Sticker

+

+ +
+
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputStickerSetItemSticker in a stickerset
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputStickeredMedia.html b/data/core.telegram.org/type/InputStickeredMedia.html new file mode 100644 index 0000000000..0eecf98e65 --- /dev/null +++ b/data/core.telegram.org/type/InputStickeredMedia.html @@ -0,0 +1,148 @@ + + + + + InputStickeredMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

InputStickeredMedia

+ +

Represents a media with attached stickers

+

+ +
+
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;
+inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputStickeredMediaPhotoA photo with stickers attached
inputStickeredMediaDocumentA document with stickers attached
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputTheme.html b/data/core.telegram.org/type/InputTheme.html new file mode 100644 index 0000000000..039413483d --- /dev/null +++ b/data/core.telegram.org/type/InputTheme.html @@ -0,0 +1,148 @@ + + + + + InputTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

InputTheme

+ +

Cloud theme

+

+ +
+
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;
+inputThemeSlug#f5890df1 slug:string = InputTheme;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputThemeTheme
inputThemeSlugTheme by theme ID
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputThemeSettings.html b/data/core.telegram.org/type/InputThemeSettings.html new file mode 100644 index 0000000000..f605e410c0 --- /dev/null +++ b/data/core.telegram.org/type/InputThemeSettings.html @@ -0,0 +1,143 @@ + + + + + InputThemeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

InputThemeSettings

+ +

Theme settings

+

+ +
+
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputThemeSettingsTheme settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputUser.html b/data/core.telegram.org/type/InputUser.html new file mode 100644 index 0000000000..ed465499f3 --- /dev/null +++ b/data/core.telegram.org/type/InputUser.html @@ -0,0 +1,158 @@ + + + + + InputUser + + + + + + + + + + + + + +
+ +
+
+
+ +

InputUser

+ +

Defines a user for subsequent interaction.

+

+ +
+
inputUserEmpty#b98886cf = InputUser;
+inputUserSelf#f7c1b13f = InputUser;
+inputUser#f21158c6 user_id:long access_hash:long = InputUser;
+inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputUserEmptyEmpty constructor, does not define a user.
inputUserSelfDefines the current user.
inputUserDefines a user for further interaction.
inputUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputWallPaper.html b/data/core.telegram.org/type/InputWallPaper.html new file mode 100644 index 0000000000..050f43dac4 --- /dev/null +++ b/data/core.telegram.org/type/InputWallPaper.html @@ -0,0 +1,153 @@ + + + + + InputWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

InputWallPaper

+ +

Wallpaper

+

+ +
+
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
+inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
+inputWallPaperNoFile#967a462e id:long = InputWallPaper;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputWallPaperWallpaper
inputWallPaperSlugWallpaper by slug (a unique ID)
inputWallPaperNoFileWallpaper with no file
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputWebDocument.html b/data/core.telegram.org/type/InputWebDocument.html new file mode 100644 index 0000000000..574c186612 --- /dev/null +++ b/data/core.telegram.org/type/InputWebDocument.html @@ -0,0 +1,143 @@ + + + + + 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/InputWebFileLocation.html b/data/core.telegram.org/type/InputWebFileLocation.html new file mode 100644 index 0000000000..29e25fee26 --- /dev/null +++ b/data/core.telegram.org/type/InputWebFileLocation.html @@ -0,0 +1,148 @@ + + + + + InputWebFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

InputWebFileLocation

+ +

Location of remote file

+

+ +
+
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
+inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputWebFileLocationLocation of a remote HTTP(s) file
inputWebFileGeoPointLocationGeolocation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Invoice.html b/data/core.telegram.org/type/Invoice.html new file mode 100644 index 0000000000..bdf5a48dbc --- /dev/null +++ b/data/core.telegram.org/type/Invoice.html @@ -0,0 +1,143 @@ + + + + + Invoice + + + + + + + + + + + + + +
+ +
+
+
+ +

Invoice

+ +

Invoice

+

+ +
+
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
invoiceInvoice
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/JSONObjectValue.html b/data/core.telegram.org/type/JSONObjectValue.html new file mode 100644 index 0000000000..c4dfeaee82 --- /dev/null +++ b/data/core.telegram.org/type/JSONObjectValue.html @@ -0,0 +1,143 @@ + + + + + JSONObjectValue + + + + + + + + + + + + + +
+ +
+
+
+ +

JSONObjectValue

+ +

JSON key: value pair

+

+ +
+
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
jsonObjectValueJSON key: value pair
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/JSONValue.html b/data/core.telegram.org/type/JSONValue.html new file mode 100644 index 0000000000..e0179988f3 --- /dev/null +++ b/data/core.telegram.org/type/JSONValue.html @@ -0,0 +1,187 @@ + + + + + JSONValue + + + + + + + + + + + + + +
+ +
+
+
+ +

JSONValue

+ +

JSON value

+

+ +
+
jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+
+---functions---
+
+help.getAppConfig#98914110 = JSONValue;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
jsonNullnull JSON value
jsonBoolJSON boolean value
jsonNumberJSON numeric value
jsonStringJSON string
jsonArrayJSON array
jsonObjectJSON object value
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getAppConfigGet app-specific configuration
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/KeyboardButton.html b/data/core.telegram.org/type/KeyboardButton.html new file mode 100644 index 0000000000..61ffafc3b9 --- /dev/null +++ b/data/core.telegram.org/type/KeyboardButton.html @@ -0,0 +1,193 @@ + + + + + KeyboardButton + + + + + + + + + + + + + +
+ +
+
+
+ +

KeyboardButton

+ +

Bot or inline keyboard buttons

+

+ +
+
keyboardButton#a2fa4880 text:string = KeyboardButton;
+keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
+keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
+keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
+keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
+keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
+keyboardButtonGame#50f41ccf text:string = KeyboardButton;
+keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
+inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
+keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
keyboardButtonBot keyboard button
keyboardButtonUrlURL button
keyboardButtonCallbackCallback button
keyboardButtonRequestPhoneButton to request a user's phone number
keyboardButtonRequestGeoLocationButton to request a user's geolocation
keyboardButtonSwitchInlineButton to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.
keyboardButtonGameButton to start a game
keyboardButtonBuyButton to buy a product
keyboardButtonUrlAuthButton to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.
inputKeyboardButtonUrlAuthButton to request a user to authorize via URL using Seamless Telegram Login.
keyboardButtonRequestPollA button that allows the user to create and send a poll when pressed; available only in private
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/KeyboardButtonRow.html b/data/core.telegram.org/type/KeyboardButtonRow.html new file mode 100644 index 0000000000..9888c0004d --- /dev/null +++ b/data/core.telegram.org/type/KeyboardButtonRow.html @@ -0,0 +1,143 @@ + + + + + KeyboardButtonRow + + + + + + + + + + + + + +
+ +
+
+
+ +

KeyboardButtonRow

+ +

Bot or inline keyboard rows

+

+ +
+
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
keyboardButtonRowInline keyboard row
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/LabeledPrice.html b/data/core.telegram.org/type/LabeledPrice.html new file mode 100644 index 0000000000..7eb7f86d98 --- /dev/null +++ b/data/core.telegram.org/type/LabeledPrice.html @@ -0,0 +1,143 @@ + + + + + LabeledPrice + + + + + + + + + + + + + +
+ +
+
+
+ +

LabeledPrice

+ +

Labeled pricetag

+

+ +
+
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
labeledPriceThis object represents a portion of the price for goods or services.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/LangPackDifference.html b/data/core.telegram.org/type/LangPackDifference.html new file mode 100644 index 0000000000..23fbb1494f --- /dev/null +++ b/data/core.telegram.org/type/LangPackDifference.html @@ -0,0 +1,167 @@ + + + + + LangPackDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

LangPackDifference

+ +

Language pack changes

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+
+---functions---
+
+langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;
+langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
langPackDifferenceChanges to the app's localization pack
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
langpack.getLangPackGet localization pack strings
langpack.getDifferenceGet new strings in languagepack
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/LangPackLanguage.html b/data/core.telegram.org/type/LangPackLanguage.html new file mode 100644 index 0000000000..29ef8513d7 --- /dev/null +++ b/data/core.telegram.org/type/LangPackLanguage.html @@ -0,0 +1,162 @@ + + + + + LangPackLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

LangPackLanguage

+ +

Language pack language

+

+ +
+
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
+
+---functions---
+
+langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
langPackLanguageIdentifies a localization pack
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
langpack.getLanguageGet information about a language in a localization pack
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/LangPackString.html b/data/core.telegram.org/type/LangPackString.html new file mode 100644 index 0000000000..68ef3edc31 --- /dev/null +++ b/data/core.telegram.org/type/LangPackString.html @@ -0,0 +1,153 @@ + + + + + LangPackString + + + + + + + + + + + + + +
+ +
+
+
+ +

LangPackString

+ +

Language pack string

+

+ +
+
langPackString#cad181f6 key:string value:string = LangPackString;
+langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;
+langPackStringDeleted#2979eeb2 key:string = LangPackString;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
langPackStringTranslated localization string
langPackStringPluralizedA language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
langPackStringDeletedDeleted localization string
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MaskCoords.html b/data/core.telegram.org/type/MaskCoords.html new file mode 100644 index 0000000000..fa939dec50 --- /dev/null +++ b/data/core.telegram.org/type/MaskCoords.html @@ -0,0 +1,143 @@ + + + + + MaskCoords + + + + + + + + + + + + + +
+ +
+
+
+ +

MaskCoords

+ +

Mask coordinates (if this is a mask sticker, attached to a photo)

+

+ +
+
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
maskCoordsPosition on a photo where a mask should be placed

The n position indicates where the mask should be placed:

- 0 => Relative to the forehead
- 1 => Relative to the eyes
- 2 => Relative to the mouth
- 3 => Relative to the chin
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Message.html b/data/core.telegram.org/type/Message.html new file mode 100644 index 0000000000..0f402c6052 --- /dev/null +++ b/data/core.telegram.org/type/Message.html @@ -0,0 +1,153 @@ + + + + + Message + + + + + + + + + + + + + +
+ +
+
+
+ +

Message

+ +

Object describing a message.

+

+ +
+
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageEmptyEmpty constructor, non-existent message.
messageA message
messageServiceIndicates a service message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageAction.html b/data/core.telegram.org/type/MessageAction.html new file mode 100644 index 0000000000..0df8432505 --- /dev/null +++ b/data/core.telegram.org/type/MessageAction.html @@ -0,0 +1,283 @@ + + + + + MessageAction + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageAction

+ +

Object describing actions connected to a service message.

+

+ +
+
messageActionEmpty#b6aef7b0 = MessageAction;
+messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;
+messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;
+messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;
+messageActionChatDeletePhoto#95e3fbef = MessageAction;
+messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;
+messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;
+messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;
+messageActionChannelCreate#95d2ac92 title:string = MessageAction;
+messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;
+messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;
+messageActionPinMessage#94bd38ed = MessageAction;
+messageActionHistoryClear#9fbab604 = MessageAction;
+messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
+messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
+messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
+messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;
+messageActionScreenshotTaken#4792929b = MessageAction;
+messageActionCustomAction#fae69f56 message:string = MessageAction;
+messageActionBotAllowed#abe9affe domain:string = MessageAction;
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;
+messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;
+messageActionContactSignUp#f3f25f76 = MessageAction;
+messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
+messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
+messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;
+messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;
+messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;
+messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageActionEmptyEmpty constructor.
messageActionChatCreateGroup created
messageActionChatEditTitleGroup name changed.
messageActionChatEditPhotoGroup profile changed
messageActionChatDeletePhotoGroup profile photo removed.
messageActionChatAddUserNew member in the group
messageActionChatDeleteUserUser left the group.
messageActionChatJoinedByLinkA user joined the chat via an invite link
messageActionChannelCreateThe channel was created
messageActionChatMigrateToIndicates the chat was migrated to the specified supergroup
messageActionChannelMigrateFromIndicates the channel was migrated from the specified chat
messageActionPinMessageA message was pinned
messageActionHistoryClearChat history was cleared
messageActionGameScoreSomeone scored in a game
messageActionPaymentSentMeA user just sent a payment to me (a bot)
messageActionPaymentSentA payment was sent
messageActionPhoneCallA phone call
messageActionScreenshotTakenA screenshot of the chat was taken
messageActionCustomActionCustom action (most likely not supported by the current layer, an upgrade might be needed)
messageActionBotAllowedThe domain name of the website on which the user has logged in. More about Telegram Login »
messageActionSecureValuesSentMeSecure telegram passport values were received
messageActionSecureValuesSentRequest for secure telegram passport values was sent
messageActionContactSignUpA contact just signed up to telegram
messageActionGeoProximityReachedWe are now in proximity of this user (triggered by the other user, by sending a live geolocation with the proximity_notification_radius flag)
messageActionGroupCallThe group call has ended
messageActionInviteToGroupCallA set of users was invited to the group call
messageActionSetMessagesTTLYou changed the Time-To-Live of your messages in this chat.
messageActionGroupCallScheduledA group call was scheduled
messageActionSetChatThemeThe chat theme was changed
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageEntity.html b/data/core.telegram.org/type/MessageEntity.html new file mode 100644 index 0000000000..f4f6d12e2d --- /dev/null +++ b/data/core.telegram.org/type/MessageEntity.html @@ -0,0 +1,233 @@ + + + + + MessageEntity + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageEntity

+ +

Message entities, representing styled text in a message

+

+ +
+
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
+messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
+messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
+messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
+messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
+messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
+messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
+messageEntityCode#28a20571 offset:int length:int = MessageEntity;
+messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
+messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
+messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
+inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
+messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
+messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
+messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
+messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
+messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
+messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageEntityUnknownUnknown message entity
messageEntityMentionMessage entity mentioning the current user
messageEntityHashtag#hashtag message entity
messageEntityBotCommandMessage entity representing a bot /command
messageEntityUrlMessage entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.
messageEntityEmailMessage entity representing an email@example.com.
messageEntityBoldMessage entity representing bold text.
messageEntityItalicMessage entity representing italic text.
messageEntityCodeMessage entity representing a codeblock.
messageEntityPreMessage entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.
messageEntityTextUrlMessage entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
messageEntityMentionNameMessage entity representing a user mention: for creating a mention use inputMessageEntityMentionName.
inputMessageEntityMentionNameMessage entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.
messageEntityPhoneMessage entity representing a phone number.
messageEntityCashtagMessage entity representing a $cashtag.
messageEntityUnderlineMessage entity representing underlined text.
messageEntityStrikeMessage entity representing strikethrough text.
messageEntityBlockquoteMessage entity representing a block quote.
messageEntityBankCardIndicates a credit card number
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageFwdHeader.html b/data/core.telegram.org/type/MessageFwdHeader.html new file mode 100644 index 0000000000..bbe619ecac --- /dev/null +++ b/data/core.telegram.org/type/MessageFwdHeader.html @@ -0,0 +1,143 @@ + + + + + MessageFwdHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageFwdHeader

+ +

Info about a forwarded message

+

+ +
+
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageFwdHeaderInfo about a forwarded message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageInteractionCounters.html b/data/core.telegram.org/type/MessageInteractionCounters.html new file mode 100644 index 0000000000..e5aa85ea07 --- /dev/null +++ b/data/core.telegram.org/type/MessageInteractionCounters.html @@ -0,0 +1,143 @@ + + + + + MessageInteractionCounters + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageInteractionCounters

+ +

Message interaction counters

+

+ +
+
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageInteractionCountersMessage interaction counters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageMedia.html b/data/core.telegram.org/type/MessageMedia.html new file mode 100644 index 0000000000..d69390ddf4 --- /dev/null +++ b/data/core.telegram.org/type/MessageMedia.html @@ -0,0 +1,232 @@ + + + + + MessageMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageMedia

+ +

Media

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+
+---functions---
+
+messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;
+messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageMediaEmptyEmpty constructor.
messageMediaPhotoAttached photo.
messageMediaGeoAttached map.
messageMediaContactAttached contact.
messageMediaUnsupportedCurrent version of the client does not support this media type.
messageMediaDocumentDocument (video, audio, voice, sticker, any media type except photo)
messageMediaWebPagePreview of webpage
messageMediaVenueVenue
messageMediaGameTelegram game
messageMediaInvoiceInvoice
messageMediaGeoLiveIndicates a live geolocation
messageMediaPollPoll
messageMediaDiceDice
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getWebPagePreviewGet preview of webpage
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.uploadImportedMediaUpload a media file associated with an imported chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageRange.html b/data/core.telegram.org/type/MessageRange.html new file mode 100644 index 0000000000..dda8a5fc9e --- /dev/null +++ b/data/core.telegram.org/type/MessageRange.html @@ -0,0 +1,143 @@ + + + + + MessageRange + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageRange

+ +

Indicates a range of chat messages

+

+ +
+
messageRange#ae30253 min_id:int max_id:int = MessageRange;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageRangeIndicates a range of chat messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageReactionsList.html b/data/core.telegram.org/type/MessageReactionsList.html new file mode 100644 index 0000000000..364301100e --- /dev/null +++ b/data/core.telegram.org/type/MessageReactionsList.html @@ -0,0 +1,128 @@ + + + + + MessageReactionsList + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageReactionsList

+ +

List of message reactions

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageReplies.html b/data/core.telegram.org/type/MessageReplies.html new file mode 100644 index 0000000000..0d8b600a6e --- /dev/null +++ b/data/core.telegram.org/type/MessageReplies.html @@ -0,0 +1,146 @@ + + + + + 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 new file mode 100644 index 0000000000..0b040a9e46 --- /dev/null +++ b/data/core.telegram.org/type/MessageUserVote.html @@ -0,0 +1,153 @@ + + + + + MessageUserVote + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageUserVote

+ +

How a user voted in a poll

+

+ +
+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageUserVoteUser ID
messageUserVoteInputOptionHow a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)
messageUserVoteMultipleHow a user voted in a multiple-choice poll
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageViews.html b/data/core.telegram.org/type/MessageViews.html new file mode 100644 index 0000000000..139d829d0d --- /dev/null +++ b/data/core.telegram.org/type/MessageViews.html @@ -0,0 +1,143 @@ + + + + + MessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageViews

+ +

View, forward counter + info about replies of a specific message

+

+ +
+
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageViewsView, forward counter + info about replies of a specific message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessagesFilter.html b/data/core.telegram.org/type/MessagesFilter.html new file mode 100644 index 0000000000..343aa14e3c --- /dev/null +++ b/data/core.telegram.org/type/MessagesFilter.html @@ -0,0 +1,223 @@ + + + + + MessagesFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

MessagesFilter

+ +

Object describes message filter.

+

+ +
+
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
+inputMessagesFilterPhotos#9609a51c = MessagesFilter;
+inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
+inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
+inputMessagesFilterDocument#9eddf188 = MessagesFilter;
+inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
+inputMessagesFilterGif#ffc86587 = MessagesFilter;
+inputMessagesFilterVoice#50f5c392 = MessagesFilter;
+inputMessagesFilterMusic#3751b49e = MessagesFilter;
+inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
+inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
+inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
+inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
+inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
+inputMessagesFilterGeo#e7026d0d = MessagesFilter;
+inputMessagesFilterContacts#e062db83 = MessagesFilter;
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputMessagesFilterEmptyFilter is absent.
inputMessagesFilterPhotosFilter for messages containing photos.
inputMessagesFilterVideoFilter for messages containing videos.
inputMessagesFilterPhotoVideoFilter for messages containing photos or videos.
inputMessagesFilterDocumentFilter for messages containing documents.
inputMessagesFilterUrlReturn only messages containing URLs
inputMessagesFilterGifReturn only messages containing gifs
inputMessagesFilterVoiceReturn only messages containing voice notes
inputMessagesFilterMusicReturn only messages containing audio files
inputMessagesFilterChatPhotosReturn only chat photo changes
inputMessagesFilterPhoneCallsReturn only phone calls
inputMessagesFilterRoundVoiceReturn only round videos and voice notes
inputMessagesFilterRoundVideoReturn only round videos
inputMessagesFilterMyMentionsReturn only messages where the current user was mentioned
inputMessagesFilterGeoReturn only messages containing geolocations
inputMessagesFilterContactsReturn only messages containing contacts
inputMessagesFilterPinnedFetch only pinned messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/NearestDc.html b/data/core.telegram.org/type/NearestDc.html new file mode 100644 index 0000000000..b39d7f7256 --- /dev/null +++ b/data/core.telegram.org/type/NearestDc.html @@ -0,0 +1,162 @@ + + + + + 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/NotifyPeer.html b/data/core.telegram.org/type/NotifyPeer.html new file mode 100644 index 0000000000..5f9abf093e --- /dev/null +++ b/data/core.telegram.org/type/NotifyPeer.html @@ -0,0 +1,158 @@ + + + + + NotifyPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

NotifyPeer

+ +

Object defines the set of users and/or groups that generate notifications.

+

+ +
+
notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;
+notifyUsers#b4c83b4c = NotifyPeer;
+notifyChats#c007cec3 = NotifyPeer;
+notifyBroadcasts#d612e8ef = NotifyPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
notifyPeerNotifications generated by a certain user or group.
notifyUsersNotifications generated by all users.
notifyChatsNotifications generated by all groups.
notifyBroadcastsChannel notification settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Null.html b/data/core.telegram.org/type/Null.html new file mode 100644 index 0000000000..1c82eb47c0 --- /dev/null +++ b/data/core.telegram.org/type/Null.html @@ -0,0 +1,143 @@ + + + + + Null + + + + + + + + + + + + + +
+ +
+
+
+ +

Null

+ +

Object corresponds to an arbitrary empty object.

+

+ +
+
null#56730bcc = Null;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
nullCorresponds to an arbitrary empty object.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Page.html b/data/core.telegram.org/type/Page.html new file mode 100644 index 0000000000..93e5d471a9 --- /dev/null +++ b/data/core.telegram.org/type/Page.html @@ -0,0 +1,143 @@ + + + + + Page + + + + + + + + + + + + + +
+ +
+
+
+ +

Page

+ +

Instant view page

+

+ +
+
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageInstant view page
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PageBlock.html b/data/core.telegram.org/type/PageBlock.html new file mode 100644 index 0000000000..7d5299437c --- /dev/null +++ b/data/core.telegram.org/type/PageBlock.html @@ -0,0 +1,283 @@ + + + + + PageBlock + + + + + + + + + + + + + +
+ +
+
+
+ +

PageBlock

+ +

Represents an instant view page element

+

+ +
+
pageBlockUnsupported#13567e8a = PageBlock;
+pageBlockTitle#70abc3fd text:RichText = PageBlock;
+pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;
+pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;
+pageBlockHeader#bfd064ec text:RichText = PageBlock;
+pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;
+pageBlockParagraph#467a0766 text:RichText = PageBlock;
+pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;
+pageBlockFooter#48870999 text:RichText = PageBlock;
+pageBlockDivider#db20b188 = PageBlock;
+pageBlockAnchor#ce0d37b0 name:string = PageBlock;
+pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;
+pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;
+pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;
+pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;
+pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;
+pageBlockCover#39f23300 cover:PageBlock = PageBlock;
+pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;
+pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockChannel#ef1751b5 channel:Chat = PageBlock;
+pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;
+pageBlockKicker#1e148390 text:RichText = PageBlock;
+pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;
+pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;
+pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;
+pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;
+pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
pageBlockUnsupportedUnsupported IV element
pageBlockTitleTitle
pageBlockSubtitleSubtitle
pageBlockAuthorDateAuthor and date of creation of article
pageBlockHeaderPage header
pageBlockSubheaderSubheader
pageBlockParagraphA paragraph
pageBlockPreformattedPreformatted (<pre> text)
pageBlockFooterPage footer
pageBlockDividerAn empty block separating a page
pageBlockAnchorLink to section within the page itself (like <a href="#target">anchor</a>)
pageBlockListUnordered list of IV blocks
pageBlockBlockquoteQuote (equivalent to the HTML <blockquote>)
pageBlockPullquotePullquote
pageBlockPhotoA photo
pageBlockVideoVideo
pageBlockCoverA page cover
pageBlockEmbedAn embedded webpage
pageBlockEmbedPostAn embedded post
pageBlockCollageCollage of media
pageBlockSlideshowSlideshow
pageBlockChannelReference to a telegram channel
pageBlockAudioAudio
pageBlockKickerKicker
pageBlockTableTable
pageBlockOrderedListOrdered list of IV blocks
pageBlockDetailsA collapsible details block
pageBlockRelatedArticlesRelated articles
pageBlockMapA map
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PageCaption.html b/data/core.telegram.org/type/PageCaption.html new file mode 100644 index 0000000000..a90dd9e022 --- /dev/null +++ b/data/core.telegram.org/type/PageCaption.html @@ -0,0 +1,143 @@ + + + + + PageCaption + + + + + + + + + + + + + +
+ +
+
+
+ +

PageCaption

+ +

Page caption

+

+ +
+
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageCaptionPage caption
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PageListItem.html b/data/core.telegram.org/type/PageListItem.html new file mode 100644 index 0000000000..72eaddf3ea --- /dev/null +++ b/data/core.telegram.org/type/PageListItem.html @@ -0,0 +1,148 @@ + + + + + PageListItem + + + + + + + + + + + + + +
+ +
+
+
+ +

PageListItem

+ +

Item in block list

+

+ +
+
pageListItemText#b92fb6cd text:RichText = PageListItem;
+pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
pageListItemTextList item
pageListItemBlocksList item
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PageListOrderedItem.html b/data/core.telegram.org/type/PageListOrderedItem.html new file mode 100644 index 0000000000..044a4e8232 --- /dev/null +++ b/data/core.telegram.org/type/PageListOrderedItem.html @@ -0,0 +1,148 @@ + + + + + PageListOrderedItem + + + + + + + + + + + + + +
+ +
+
+
+ +

PageListOrderedItem

+ +

Represents an instant view ordered list

+

+ +
+
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
+pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
pageListOrderedItemTextOrdered list of text items
pageListOrderedItemBlocksOrdered list of IV blocks
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PageRelatedArticle.html b/data/core.telegram.org/type/PageRelatedArticle.html new file mode 100644 index 0000000000..08c198b179 --- /dev/null +++ b/data/core.telegram.org/type/PageRelatedArticle.html @@ -0,0 +1,143 @@ + + + + + PageRelatedArticle + + + + + + + + + + + + + +
+ +
+
+
+ +

PageRelatedArticle

+ +

Related articles

+

+ +
+
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageRelatedArticleRelated article
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PageTableCell.html b/data/core.telegram.org/type/PageTableCell.html new file mode 100644 index 0000000000..0cd1136272 --- /dev/null +++ b/data/core.telegram.org/type/PageTableCell.html @@ -0,0 +1,143 @@ + + + + + PageTableCell + + + + + + + + + + + + + +
+ +
+
+
+ +

PageTableCell

+ +

Represents a table in an instant view table

+

+ +
+
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageTableCellTable cell
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PageTableRow.html b/data/core.telegram.org/type/PageTableRow.html new file mode 100644 index 0000000000..4d1c09514a --- /dev/null +++ b/data/core.telegram.org/type/PageTableRow.html @@ -0,0 +1,143 @@ + + + + + PageTableRow + + + + + + + + + + + + + +
+ +
+
+
+ +

PageTableRow

+ +

Table row

+

+ +
+
pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageTableRowTable row
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PasswordKdfAlgo.html b/data/core.telegram.org/type/PasswordKdfAlgo.html new file mode 100644 index 0000000000..e22a7ea56b --- /dev/null +++ b/data/core.telegram.org/type/PasswordKdfAlgo.html @@ -0,0 +1,151 @@ + + + + + PasswordKdfAlgo + + + + + + + + + + + + + +
+ +
+
+
+ +

PasswordKdfAlgo

+ +

Key derivation function to use when generating the password hash for SRP two-factor authorization

+

+ +
+
passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
+passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
passwordKdfAlgoUnknownUnknown KDF (most likely, the client is outdated and does not support the specified KDF algorithm)
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPowThis key derivation algorithm defines that SRP 2FA login must be used
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PaymentCharge.html b/data/core.telegram.org/type/PaymentCharge.html new file mode 100644 index 0000000000..47bb3abbd6 --- /dev/null +++ b/data/core.telegram.org/type/PaymentCharge.html @@ -0,0 +1,143 @@ + + + + + PaymentCharge + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentCharge

+ +

Charged payment

+

+ +
+
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentChargePayment identifier
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PaymentRequestedInfo.html b/data/core.telegram.org/type/PaymentRequestedInfo.html new file mode 100644 index 0000000000..884f917385 --- /dev/null +++ b/data/core.telegram.org/type/PaymentRequestedInfo.html @@ -0,0 +1,143 @@ + + + + + PaymentRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentRequestedInfo

+ +

Requested payment info

+

+ +
+
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentRequestedInfoOrder info provided by the user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PaymentSavedCredentials.html b/data/core.telegram.org/type/PaymentSavedCredentials.html new file mode 100644 index 0000000000..05f6211577 --- /dev/null +++ b/data/core.telegram.org/type/PaymentSavedCredentials.html @@ -0,0 +1,143 @@ + + + + + PaymentSavedCredentials + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentSavedCredentials

+ +

Saved payment credentials

+

+ +
+
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentSavedCredentialsCardSaved credit card
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Peer.html b/data/core.telegram.org/type/Peer.html new file mode 100644 index 0000000000..6ba68784c5 --- /dev/null +++ b/data/core.telegram.org/type/Peer.html @@ -0,0 +1,153 @@ + + + + + Peer + + + + + + + + + + + + + +
+ +
+
+
+ +

Peer

+ +

Chat partner or group.

+

+ +
+
peerUser#59511722 user_id:long = Peer;
+peerChat#36c6019a chat_id:long = Peer;
+peerChannel#a2a5371e channel_id:long = Peer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
peerUserChat partner
peerChatGroup.
peerChannelChannel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PeerBlocked.html b/data/core.telegram.org/type/PeerBlocked.html new file mode 100644 index 0000000000..0bab94d05c --- /dev/null +++ b/data/core.telegram.org/type/PeerBlocked.html @@ -0,0 +1,143 @@ + + + + + PeerBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

PeerBlocked

+ +

Info about a blocked user

+

+ +
+
peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
peerBlockedInformation about a blocked peer
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PeerLocated.html b/data/core.telegram.org/type/PeerLocated.html new file mode 100644 index 0000000000..09e62c12a8 --- /dev/null +++ b/data/core.telegram.org/type/PeerLocated.html @@ -0,0 +1,148 @@ + + + + + PeerLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

PeerLocated

+ +

Geolocated peer

+

+ +
+
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;
+peerSelfLocated#f8ec284b expires:int = PeerLocated;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
peerLocatedPeer geolocated nearby
peerSelfLocatedCurrent peer
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PeerNotifySettings.html b/data/core.telegram.org/type/PeerNotifySettings.html new file mode 100644 index 0000000000..c49c82e618 --- /dev/null +++ b/data/core.telegram.org/type/PeerNotifySettings.html @@ -0,0 +1,162 @@ + + + + + PeerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

PeerNotifySettings

+ +

Notification settings.

+

+ +
+
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
+
+---functions---
+
+account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
peerNotifySettingsNotification settings.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PeerSettings.html b/data/core.telegram.org/type/PeerSettings.html new file mode 100644 index 0000000000..a50bfde48e --- /dev/null +++ b/data/core.telegram.org/type/PeerSettings.html @@ -0,0 +1,162 @@ + + + + + PeerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

PeerSettings

+ +

Peer settings

+

+ +
+
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
+
+---functions---
+
+messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
peerSettingsPeer settings
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getPeerSettingsGet peer settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PhoneCall.html b/data/core.telegram.org/type/PhoneCall.html new file mode 100644 index 0000000000..52b4674580 --- /dev/null +++ b/data/core.telegram.org/type/PhoneCall.html @@ -0,0 +1,168 @@ + + + + + PhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCall

+ +

Phone call

+

+ +
+
phoneCallEmpty#5366c915 id:long = PhoneCall;
+phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
+phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;
+phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneCallEmptyEmpty constructor
phoneCallWaitingIncoming phone call
phoneCallRequestedRequested phone call
phoneCallAcceptedAn accepted phone call
phoneCallPhone call
phoneCallDiscardedIndicates a discarded phone call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PhoneCallDiscardReason.html b/data/core.telegram.org/type/PhoneCallDiscardReason.html new file mode 100644 index 0000000000..bdb3fea497 --- /dev/null +++ b/data/core.telegram.org/type/PhoneCallDiscardReason.html @@ -0,0 +1,158 @@ + + + + + PhoneCallDiscardReason + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCallDiscardReason

+ +

Why was the phone call discarded?

+

+ +
+
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;
+phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;
+phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;
+phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneCallDiscardReasonMissedThe phone call was missed
phoneCallDiscardReasonDisconnectThe phone call was disconnected
phoneCallDiscardReasonHangupThe phone call was ended normally
phoneCallDiscardReasonBusyThe phone call was discared because the user is busy in another call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PhoneCallProtocol.html b/data/core.telegram.org/type/PhoneCallProtocol.html new file mode 100644 index 0000000000..1930d6420d --- /dev/null +++ b/data/core.telegram.org/type/PhoneCallProtocol.html @@ -0,0 +1,143 @@ + + + + + PhoneCallProtocol + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCallProtocol

+ +

Phone call protocol

+

+ +
+
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phoneCallProtocolProtocol info for libtgvoip
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PhoneConnection.html b/data/core.telegram.org/type/PhoneConnection.html new file mode 100644 index 0000000000..812287d216 --- /dev/null +++ b/data/core.telegram.org/type/PhoneConnection.html @@ -0,0 +1,148 @@ + + + + + PhoneConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneConnection

+ +

Phone call connection

+

+ +
+
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;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneConnectionIdentifies an endpoint that can be used to connect to the other user in a phone call
phoneConnectionWebrtcWebRTC connection parameters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Photo.html b/data/core.telegram.org/type/Photo.html new file mode 100644 index 0000000000..f81614edab --- /dev/null +++ b/data/core.telegram.org/type/Photo.html @@ -0,0 +1,148 @@ + + + + + Photo + + + + + + + + + + + + + +
+ +
+
+
+ +

Photo

+ +

Object describes a photo.

+

+ +
+
photoEmpty#2331b22d id:long = Photo;
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
photoEmptyEmpty constructor, non-existent photo
photoPhoto
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PhotoSize.html b/data/core.telegram.org/type/PhotoSize.html new file mode 100644 index 0000000000..a45b1c3618 --- /dev/null +++ b/data/core.telegram.org/type/PhotoSize.html @@ -0,0 +1,168 @@ + + + + + PhotoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

PhotoSize

+ +

Location of a certain size of a picture

+

+ +
+
photoSizeEmpty#e17e23c type:string = PhotoSize;
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
+photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
+photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
+photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
photoSizeEmptyEmpty constructor. Image with this thumbnail is unavailable.
photoSizeImage description.
photoCachedSizeDescription of an image and its content.
photoStrippedSizeJust the image's content
photoSizeProgressiveProgressively encoded photosize
photoPathSizeMessages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Poll.html b/data/core.telegram.org/type/Poll.html new file mode 100644 index 0000000000..567314114c --- /dev/null +++ b/data/core.telegram.org/type/Poll.html @@ -0,0 +1,143 @@ + + + + + Poll + + + + + + + + + + + + + +
+ +
+
+
+ +

Poll

+ +

Indicates a poll message

+

+ +
+
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollPoll
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PollAnswer.html b/data/core.telegram.org/type/PollAnswer.html new file mode 100644 index 0000000000..6715b84997 --- /dev/null +++ b/data/core.telegram.org/type/PollAnswer.html @@ -0,0 +1,146 @@ + + + + + PollAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

PollAnswer

+ +

Indicates a possible answer to a poll.

+

+ +
+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollAnswerA possible answer of a poll
+

Related pages

+

Poll

+

Indicates a poll message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PollAnswerVoters.html b/data/core.telegram.org/type/PollAnswerVoters.html new file mode 100644 index 0000000000..d5f760790c --- /dev/null +++ b/data/core.telegram.org/type/PollAnswerVoters.html @@ -0,0 +1,143 @@ + + + + + PollAnswerVoters + + + + + + + + + + + + + +
+ +
+
+
+ +

PollAnswerVoters

+ +

How users voted on a certain poll answer

+

+ +
+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollAnswerVotersA poll answer, and how users voted on it
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PollResults.html b/data/core.telegram.org/type/PollResults.html new file mode 100644 index 0000000000..8894dd373c --- /dev/null +++ b/data/core.telegram.org/type/PollResults.html @@ -0,0 +1,143 @@ + + + + + PollResults + + + + + + + + + + + + + +
+ +
+
+
+ +

PollResults

+ +

Results of poll

+

+ +
+
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollResultsResults of poll
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PopularContact.html b/data/core.telegram.org/type/PopularContact.html new file mode 100644 index 0000000000..162e4f02cc --- /dev/null +++ b/data/core.telegram.org/type/PopularContact.html @@ -0,0 +1,143 @@ + + + + + PopularContact + + + + + + + + + + + + + +
+ +
+
+
+ +

PopularContact

+ +

Popular contact

+

+ +
+
popularContact#5ce14175 client_id:long importers:int = PopularContact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
popularContactPopular contact
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PostAddress.html b/data/core.telegram.org/type/PostAddress.html new file mode 100644 index 0000000000..6df885b58a --- /dev/null +++ b/data/core.telegram.org/type/PostAddress.html @@ -0,0 +1,143 @@ + + + + + PostAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

PostAddress

+ +

Shipping address

+

+ +
+
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
postAddressShipping address
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PrivacyKey.html b/data/core.telegram.org/type/PrivacyKey.html new file mode 100644 index 0000000000..806a9d1d7d --- /dev/null +++ b/data/core.telegram.org/type/PrivacyKey.html @@ -0,0 +1,178 @@ + + + + + PrivacyKey + + + + + + + + + + + + + +
+ +
+
+
+ +

PrivacyKey

+ +

Privacy key

+

+ +
+
privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;
+privacyKeyChatInvite#500e6dfa = PrivacyKey;
+privacyKeyPhoneCall#3d662b7b = PrivacyKey;
+privacyKeyPhoneP2P#39491cc8 = PrivacyKey;
+privacyKeyForwards#69ec56a3 = PrivacyKey;
+privacyKeyProfilePhoto#96151fed = PrivacyKey;
+privacyKeyPhoneNumber#d19ae46d = PrivacyKey;
+privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
privacyKeyStatusTimestampWhether we can see the last online timestamp
privacyKeyChatInviteWhether the user can be invited to chats
privacyKeyPhoneCallWhether the user accepts phone calls
privacyKeyPhoneP2PWhether P2P connections in phone calls are allowed
privacyKeyForwardsWhether messages forwarded from the user will be anonymously forwarded
privacyKeyProfilePhotoWhether the profile picture of the user is visible
privacyKeyPhoneNumberWhether the user allows us to see his phone number
privacyKeyAddedByPhoneWhether people can add you to their contact list by your phone number
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PrivacyRule.html b/data/core.telegram.org/type/PrivacyRule.html new file mode 100644 index 0000000000..e38fee3c82 --- /dev/null +++ b/data/core.telegram.org/type/PrivacyRule.html @@ -0,0 +1,178 @@ + + + + + PrivacyRule + + + + + + + + + + + + + +
+ +
+
+
+ +

PrivacyRule

+ +

Privacy rule

+

+ +
+
privacyValueAllowContacts#fffe1bac = PrivacyRule;
+privacyValueAllowAll#65427b82 = PrivacyRule;
+privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;
+privacyValueDisallowContacts#f888fa1a = PrivacyRule;
+privacyValueDisallowAll#8b73e763 = PrivacyRule;
+privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;
+privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
+privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
privacyValueAllowContactsAllow all contacts
privacyValueAllowAllAllow all users
privacyValueAllowUsersAllow only certain users
privacyValueDisallowContactsDisallow only contacts
privacyValueDisallowAllDisallow all users
privacyValueDisallowUsersDisallow only certain users
privacyValueAllowChatParticipantsAllow all participants of certain chats
privacyValueDisallowChatParticipantsDisallow only participants of certain chats
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ReceivedNotifyMessage.html b/data/core.telegram.org/type/ReceivedNotifyMessage.html new file mode 100644 index 0000000000..d281fb997e --- /dev/null +++ b/data/core.telegram.org/type/ReceivedNotifyMessage.html @@ -0,0 +1,143 @@ + + + + + ReceivedNotifyMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

ReceivedNotifyMessage

+ +

Confirmation of message receipt

+

+ +
+
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
receivedNotifyMessageMessage ID, for which PUSH-notifications were cancelled.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/RecentMeUrl.html b/data/core.telegram.org/type/RecentMeUrl.html new file mode 100644 index 0000000000..0562d74e7d --- /dev/null +++ b/data/core.telegram.org/type/RecentMeUrl.html @@ -0,0 +1,163 @@ + + + + + RecentMeUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

RecentMeUrl

+ +

Recent t.me urls

+

+ +
+
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;
+recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;
+recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;
+recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;
+recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
recentMeUrlUnknownUnknown t.me url
recentMeUrlUserRecent t.me link to a user
recentMeUrlChatRecent t.me link to a chat
recentMeUrlChatInviteRecent t.me invite link to a chat
recentMeUrlStickerSetRecent t.me stickerset installation URL
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ReplyMarkup.html b/data/core.telegram.org/type/ReplyMarkup.html new file mode 100644 index 0000000000..b15813b492 --- /dev/null +++ b/data/core.telegram.org/type/ReplyMarkup.html @@ -0,0 +1,158 @@ + + + + + ReplyMarkup + + + + + + + + + + + + + +
+ +
+
+
+ +

ReplyMarkup

+ +

Reply markup for bot and inline keyboards

+

+ +
+
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
+replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
+replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
replyKeyboardHideHide sent bot keyboard
replyKeyboardForceReplyForce the user to send a reply
replyKeyboardMarkupBot keyboard
replyInlineMarkupBot or inline keyboard
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ReportReason.html b/data/core.telegram.org/type/ReportReason.html new file mode 100644 index 0000000000..69953d3340 --- /dev/null +++ b/data/core.telegram.org/type/ReportReason.html @@ -0,0 +1,178 @@ + + + + + ReportReason + + + + + + + + + + + + + +
+ +
+
+
+ +

ReportReason

+ +

Report reason

+

+ +
+
inputReportReasonSpam#58dbcab8 = ReportReason;
+inputReportReasonViolence#1e22c78d = ReportReason;
+inputReportReasonPornography#2e59d922 = ReportReason;
+inputReportReasonChildAbuse#adf44ee3 = ReportReason;
+inputReportReasonOther#c1e4a2b1 = ReportReason;
+inputReportReasonCopyright#9b89f93a = ReportReason;
+inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;
+inputReportReasonFake#f5ddd6e7 = ReportReason;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputReportReasonSpamReport for spam
inputReportReasonViolenceReport for violence
inputReportReasonPornographyReport for pornography
inputReportReasonChildAbuseReport for child abuse
inputReportReasonOtherOther
inputReportReasonCopyrightReport for copyrighted content
inputReportReasonGeoIrrelevantReport an irrelevant geogroup
inputReportReasonFakeReport for impersonation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/RestrictionReason.html b/data/core.telegram.org/type/RestrictionReason.html new file mode 100644 index 0000000000..6abc2362be --- /dev/null +++ b/data/core.telegram.org/type/RestrictionReason.html @@ -0,0 +1,143 @@ + + + + + RestrictionReason + + + + + + + + + + + + + +
+ +
+
+
+ +

RestrictionReason

+ +

Restriction reason

+

+ +
+
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
restrictionReasonRestriction reason
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/RichText.html b/data/core.telegram.org/type/RichText.html new file mode 100644 index 0000000000..51d5fc0813 --- /dev/null +++ b/data/core.telegram.org/type/RichText.html @@ -0,0 +1,218 @@ + + + + + RichText + + + + + + + + + + + + + +
+ +
+
+
+ +

RichText

+ +

Rich text

+

+ +
+
textEmpty#dc3d824f = RichText;
+textPlain#744694e0 text:string = RichText;
+textBold#6724abc4 text:RichText = RichText;
+textItalic#d912a59c text:RichText = RichText;
+textUnderline#c12622c4 text:RichText = RichText;
+textStrike#9bf8bb95 text:RichText = RichText;
+textFixed#6c3f19b9 text:RichText = RichText;
+textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;
+textEmail#de5a0dd6 text:RichText email:string = RichText;
+textConcat#7e6260d7 texts:Vector<RichText> = RichText;
+textSubscript#ed6a8504 text:RichText = RichText;
+textSuperscript#c7fb5e01 text:RichText = RichText;
+textMarked#34b8621 text:RichText = RichText;
+textPhone#1ccb966a text:RichText phone:string = RichText;
+textImage#81ccf4f document_id:long w:int h:int = RichText;
+textAnchor#35553762 text:RichText name:string = RichText;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
textEmptyEmpty rich text element
textPlainPlain text
textBoldBold text
textItalicItalic text
textUnderlineUnderlined text
textStrikeStrikethrough text
textFixedfixed-width rich text
textUrlLink
textEmailRich text email link
textConcatConcatenation of rich texts
textSubscriptSubscript text
textSuperscriptSuperscript text
textMarkedHighlighted text
textPhoneRich text linked to a phone number
textImageInline image
textAnchorText linking to another section of the page
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SavedContact.html b/data/core.telegram.org/type/SavedContact.html new file mode 100644 index 0000000000..ddbd71d748 --- /dev/null +++ b/data/core.telegram.org/type/SavedContact.html @@ -0,0 +1,143 @@ + + + + + SavedContact + + + + + + + + + + + + + +
+ +
+
+
+ +

SavedContact

+ +

Saved contact

+

+ +
+
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
savedPhoneContactSaved contact
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureCredentialsEncrypted.html b/data/core.telegram.org/type/SecureCredentialsEncrypted.html new file mode 100644 index 0000000000..83969a99fc --- /dev/null +++ b/data/core.telegram.org/type/SecureCredentialsEncrypted.html @@ -0,0 +1,143 @@ + + + + + SecureCredentialsEncrypted + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureCredentialsEncrypted

+ +

Encrypted secure credentials

+

+ +
+
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureCredentialsEncryptedEncrypted credentials required to decrypt telegram passport data.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureData.html b/data/core.telegram.org/type/SecureData.html new file mode 100644 index 0000000000..d5b3aa24db --- /dev/null +++ b/data/core.telegram.org/type/SecureData.html @@ -0,0 +1,146 @@ + + + + + SecureData + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureData

+ +

Secure passport data, for more info see the passport docs »

+

+ +
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureDataSecure data
+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureFile.html b/data/core.telegram.org/type/SecureFile.html new file mode 100644 index 0000000000..bd82e09aee --- /dev/null +++ b/data/core.telegram.org/type/SecureFile.html @@ -0,0 +1,151 @@ + + + + + SecureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureFile

+ +

Secure passport file, for more info see the passport docs »

+

+ +
+
secureFileEmpty#64199744 = SecureFile;
+secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
secureFileEmptyEmpty constructor
secureFileSecure file
+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecurePlainData.html b/data/core.telegram.org/type/SecurePlainData.html new file mode 100644 index 0000000000..5f46a9cddf --- /dev/null +++ b/data/core.telegram.org/type/SecurePlainData.html @@ -0,0 +1,150 @@ + + + + + SecurePlainData + + + + + + + + + + + + + +
+ +
+
+
+ +

SecurePlainData

+ +

Plaintext verified passport data.

+

+ +
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
securePlainPhonePhone number to use in telegram passport: it must be verified, first ».
securePlainEmailEmail address to use in telegram passport: it must be verified, first ».
+

Related pages

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureRequiredType.html b/data/core.telegram.org/type/SecureRequiredType.html new file mode 100644 index 0000000000..3bec48883d --- /dev/null +++ b/data/core.telegram.org/type/SecureRequiredType.html @@ -0,0 +1,148 @@ + + + + + SecureRequiredType + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureRequiredType

+ +

Required secure file type

+

+ +
+
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;
+secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
secureRequiredTypeRequired type
secureRequiredTypeOneOfOne of
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureSecretSettings.html b/data/core.telegram.org/type/SecureSecretSettings.html new file mode 100644 index 0000000000..f6a2af64f6 --- /dev/null +++ b/data/core.telegram.org/type/SecureSecretSettings.html @@ -0,0 +1,145 @@ + + + + + SecureSecretSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureSecretSettings

+ +

Telegram passport settings

+

+ +
+
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureSecretSettingsSecure settings
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureValue.html b/data/core.telegram.org/type/SecureValue.html new file mode 100644 index 0000000000..ae0341370c --- /dev/null +++ b/data/core.telegram.org/type/SecureValue.html @@ -0,0 +1,162 @@ + + + + + SecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValue

+ +

Secure tgpassport value

+

+ +
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+---functions---
+
+account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureValueSecure value
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.saveSecureValueSave secure passport value
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureValueError.html b/data/core.telegram.org/type/SecureValueError.html new file mode 100644 index 0000000000..57d53fa14e --- /dev/null +++ b/data/core.telegram.org/type/SecureValueError.html @@ -0,0 +1,183 @@ + + + + + SecureValueError + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValueError

+ +

Secure value error

+

+ +
+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
secureValueErrorDataSecure value error
secureValueErrorFrontSideSecure value error front side
secureValueErrorReverseSideReverse side error
secureValueErrorSelfieSecure value error: invalid selfie
secureValueErrorFileSecure value error file
secureValueErrorFilesSecure value error files
secureValueErrorSecure value error
secureValueErrorTranslationFileTranslation missing
secureValueErrorTranslationFilesTranslation file error
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureValueHash.html b/data/core.telegram.org/type/SecureValueHash.html new file mode 100644 index 0000000000..335491da51 --- /dev/null +++ b/data/core.telegram.org/type/SecureValueHash.html @@ -0,0 +1,143 @@ + + + + + SecureValueHash + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValueHash

+ +

Secure value hash

+

+ +
+
secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureValueHashSecure value hash
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureValueType.html b/data/core.telegram.org/type/SecureValueType.html new file mode 100644 index 0000000000..f6b8803cab --- /dev/null +++ b/data/core.telegram.org/type/SecureValueType.html @@ -0,0 +1,203 @@ + + + + + SecureValueType + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValueType

+ +

Secure value type

+

+ +
+
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
secureValueTypePersonalDetailsPersonal details
secureValueTypePassportPassport
secureValueTypeDriverLicenseDriver's license
secureValueTypeIdentityCardIdentity card
secureValueTypeInternalPassportInternal passport
secureValueTypeAddressAddress
secureValueTypeUtilityBillUtility bill
secureValueTypeBankStatementBank statement
secureValueTypeRentalAgreementRental agreement
secureValueTypePassportRegistrationInternal registration passport
secureValueTypeTemporaryRegistrationTemporary registration
secureValueTypePhonePhone
secureValueTypeEmailEmail
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SendMessageAction.html b/data/core.telegram.org/type/SendMessageAction.html new file mode 100644 index 0000000000..9fae21a4fe --- /dev/null +++ b/data/core.telegram.org/type/SendMessageAction.html @@ -0,0 +1,228 @@ + + + + + SendMessageAction + + + + + + + + + + + + + +
+ +
+
+
+ +

SendMessageAction

+ +

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

+

+ +
+
sendMessageTypingAction#16bf744e = SendMessageAction;
+sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
+sendMessageRecordVideoAction#a187d66f = SendMessageAction;
+sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
+sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
+sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
+sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
+sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
+sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
+sendMessageChooseContactAction#628cbc6f = SendMessageAction;
+sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
+sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
+sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
+speakingInGroupCallAction#d92c2285 = SendMessageAction;
+sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
+sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
sendMessageTypingActionUser is typing.
sendMessageCancelActionInvalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.
sendMessageRecordVideoActionUser is recording a video.
sendMessageUploadVideoActionUser is uploading a video.
sendMessageRecordAudioActionUser is recording a voice message.
sendMessageUploadAudioActionUser is uploading a voice message.
sendMessageUploadPhotoActionUser is uploading a photo.
sendMessageUploadDocumentActionUser is uploading a file.
sendMessageGeoLocationActionUser is selecting a location to share.
sendMessageChooseContactActionUser is selecting a contact to share.
sendMessageGamePlayActionUser is playing a game
sendMessageRecordRoundActionUser is recording a round video to share
sendMessageUploadRoundActionUser is uploading a round video
speakingInGroupCallActionUser is currently speaking in the group call
sendMessageHistoryImportActionChat history is being imported
sendMessageChooseStickerActionUser is choosing a sticker
sendMessageEmojiInteractionUser has clicked on an animated emoji, triggering a reaction
sendMessageEmojiInteractionSeenUser has seen the reaction generated by another user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ShippingOption.html b/data/core.telegram.org/type/ShippingOption.html new file mode 100644 index 0000000000..bee95e197d --- /dev/null +++ b/data/core.telegram.org/type/ShippingOption.html @@ -0,0 +1,143 @@ + + + + + ShippingOption + + + + + + + + + + + + + +
+ +
+
+
+ +

ShippingOption

+ +

Shipping options

+

+ +
+
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
shippingOptionShipping option
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SponsoredMessage.html b/data/core.telegram.org/type/SponsoredMessage.html new file mode 100644 index 0000000000..9902b43556 --- /dev/null +++ b/data/core.telegram.org/type/SponsoredMessage.html @@ -0,0 +1,143 @@ + + + + + SponsoredMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

SponsoredMessage

+ +

A sponsored message

+

+ +
+
sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
sponsoredMessageA sponsored message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/StatsAbsValueAndPrev.html b/data/core.telegram.org/type/StatsAbsValueAndPrev.html new file mode 100644 index 0000000000..5af90cf3ee --- /dev/null +++ b/data/core.telegram.org/type/StatsAbsValueAndPrev.html @@ -0,0 +1,143 @@ + + + + + StatsAbsValueAndPrev + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsAbsValueAndPrev

+ +

Channel statistics value pair

+

+ +
+
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsAbsValueAndPrevStatistics value couple; initial and final value for period of time currently in consideration
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/StatsDateRangeDays.html b/data/core.telegram.org/type/StatsDateRangeDays.html new file mode 100644 index 0000000000..00204cac14 --- /dev/null +++ b/data/core.telegram.org/type/StatsDateRangeDays.html @@ -0,0 +1,143 @@ + + + + + StatsDateRangeDays + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsDateRangeDays

+ +

Channel statistics date range

+

+ +
+
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsDateRangeDaysChannel statistics date range
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/StatsGraph.html b/data/core.telegram.org/type/StatsGraph.html new file mode 100644 index 0000000000..eb0b4cc0c3 --- /dev/null +++ b/data/core.telegram.org/type/StatsGraph.html @@ -0,0 +1,172 @@ + + + + + StatsGraph + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsGraph

+ +

Channel statistics graph

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+
+---functions---
+
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
statsGraphAsyncThis graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load
statsGraphErrorAn error occurred while generating the statistics graph
statsGraphChannel statistics graph
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.loadAsyncGraphLoad channel statistics graph asynchronously
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/StatsGroupTopAdmin.html b/data/core.telegram.org/type/StatsGroupTopAdmin.html new file mode 100644 index 0000000000..27488200b1 --- /dev/null +++ b/data/core.telegram.org/type/StatsGroupTopAdmin.html @@ -0,0 +1,146 @@ + + + + + StatsGroupTopAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsGroupTopAdmin

+ +

Most active admin in a supergroup

+

+ +
+
statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsGroupTopAdminInformation about an active admin in a supergroup
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/StatsGroupTopInviter.html b/data/core.telegram.org/type/StatsGroupTopInviter.html new file mode 100644 index 0000000000..1e6ca20091 --- /dev/null +++ b/data/core.telegram.org/type/StatsGroupTopInviter.html @@ -0,0 +1,146 @@ + + + + + StatsGroupTopInviter + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsGroupTopInviter

+ +

Most active inviter in a supergroup

+

+ +
+
statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsGroupTopInviterInformation about an active supergroup inviter
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/StatsGroupTopPoster.html b/data/core.telegram.org/type/StatsGroupTopPoster.html new file mode 100644 index 0000000000..8de718255f --- /dev/null +++ b/data/core.telegram.org/type/StatsGroupTopPoster.html @@ -0,0 +1,146 @@ + + + + + StatsGroupTopPoster + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsGroupTopPoster

+ +

Most active user in a supergroup

+

+ +
+
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsGroupTopPosterInformation about an active user in a supergroup
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/StatsPercentValue.html b/data/core.telegram.org/type/StatsPercentValue.html new file mode 100644 index 0000000000..6b926097ae --- /dev/null +++ b/data/core.telegram.org/type/StatsPercentValue.html @@ -0,0 +1,143 @@ + + + + + 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 new file mode 100644 index 0000000000..f81ad87e0c --- /dev/null +++ b/data/core.telegram.org/type/StatsURL.html @@ -0,0 +1,143 @@ + + + + + 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/StickerSet.html b/data/core.telegram.org/type/StickerSet.html new file mode 100644 index 0000000000..67c5dd20d1 --- /dev/null +++ b/data/core.telegram.org/type/StickerSet.html @@ -0,0 +1,143 @@ + + + + + StickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

StickerSet

+ +

Represents a stickerset (stickerpack)

+

+ +
+
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stickerSetRepresents a stickerset (stickerpack)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/StickerSetCovered.html b/data/core.telegram.org/type/StickerSetCovered.html new file mode 100644 index 0000000000..08031c4dad --- /dev/null +++ b/data/core.telegram.org/type/StickerSetCovered.html @@ -0,0 +1,148 @@ + + + + + StickerSetCovered + + + + + + + + + + + + + +
+ +
+
+
+ +

StickerSetCovered

+ +

Stickerset, with a specific sticker as preview

+

+ +
+
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;
+stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
stickerSetCoveredStickerset, with a specific sticker as preview
stickerSetMultiCoveredStickerset, with a specific stickers as preview
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Theme.html b/data/core.telegram.org/type/Theme.html new file mode 100644 index 0000000000..a7fbcafad3 --- /dev/null +++ b/data/core.telegram.org/type/Theme.html @@ -0,0 +1,172 @@ + + + + + Theme + + + + + + + + + + + + + +
+ +
+
+
+ +

Theme

+ +

Cloud theme

+

+ +
+
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+
+---functions---
+
+account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
+account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
+account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
themeTheme
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
account.createThemeCreate a theme
account.updateThemeUpdate theme
account.getThemeGet theme information
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ThemeSettings.html b/data/core.telegram.org/type/ThemeSettings.html new file mode 100644 index 0000000000..1bc573edcb --- /dev/null +++ b/data/core.telegram.org/type/ThemeSettings.html @@ -0,0 +1,143 @@ + + + + + ThemeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

ThemeSettings

+ +

Theme settings

+

+ +
+
themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
themeSettingsTheme settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/TopPeer.html b/data/core.telegram.org/type/TopPeer.html new file mode 100644 index 0000000000..94574c28ac --- /dev/null +++ b/data/core.telegram.org/type/TopPeer.html @@ -0,0 +1,143 @@ + + + + + TopPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

TopPeer

+ +

Top peer

+

+ +
+
topPeer#edcdc05b peer:Peer rating:double = TopPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
topPeerTop peer
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/TopPeerCategory.html b/data/core.telegram.org/type/TopPeerCategory.html new file mode 100644 index 0000000000..dac2ccf4ae --- /dev/null +++ b/data/core.telegram.org/type/TopPeerCategory.html @@ -0,0 +1,178 @@ + + + + + TopPeerCategory + + + + + + + + + + + + + +
+ +
+
+
+ +

TopPeerCategory

+ +

Top peer category

+

+ +
+
topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
+topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
+topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
+topPeerCategoryGroups#bd17a14a = TopPeerCategory;
+topPeerCategoryChannels#161d9628 = TopPeerCategory;
+topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
+topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
+topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
topPeerCategoryBotsPMMost used bots
topPeerCategoryBotsInlineMost used inline bots
topPeerCategoryCorrespondentsUsers we've chatted most frequently with
topPeerCategoryGroupsOften-opened groups and supergroups
topPeerCategoryChannelsMost frequently visited channels
topPeerCategoryPhoneCallsMost frequently called users
topPeerCategoryForwardUsersUsers to which the users often forwards messages to
topPeerCategoryForwardChatsChats to which the users often forwards messages to
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/TopPeerCategoryPeers.html b/data/core.telegram.org/type/TopPeerCategoryPeers.html new file mode 100644 index 0000000000..53a033e129 --- /dev/null +++ b/data/core.telegram.org/type/TopPeerCategoryPeers.html @@ -0,0 +1,143 @@ + + + + + TopPeerCategoryPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

TopPeerCategoryPeers

+ +

Top peers by top peer category

+

+ +
+
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
topPeerCategoryPeersTop peer category
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/True.html b/data/core.telegram.org/type/True.html new file mode 100644 index 0000000000..a3b2316c7f --- /dev/null +++ b/data/core.telegram.org/type/True.html @@ -0,0 +1,145 @@ + + + + + True + + + + + + + + + + + + + +
+ +
+
+
+ +

True

+ +

See predefined identifiers.

+

+ +
+
true#3fedd339 = True;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
trueSee predefined identifiers.
+

Related pages

+

TL-formal

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Update.html b/data/core.telegram.org/type/Update.html new file mode 100644 index 0000000000..4b82d7af3a --- /dev/null +++ b/data/core.telegram.org/type/Update.html @@ -0,0 +1,603 @@ + + + + + Update + + + + + + + + + + + + + +
+ +
+
+
+ +

Update

+ +

Object contains info on events occured.

+

+ +
+
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+updateMessageID#4e90bfd6 id:int random_id:long = Update;
+updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;
+updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
+updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;
+updateChatParticipants#7761198 participants:ChatParticipants = Update;
+updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;
+updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;
+updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;
+updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;
+updateEncryptedChatTyping#1710f156 chat_id:int = Update;
+updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;
+updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;
+updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;
+updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;
+updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;
+updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
+updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
+updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;
+updateUserPhone#5492a13 user_id:long phone:string = Update;
+updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;
+updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;
+updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;
+updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;
+updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;
+updateChannel#635b4c09 channel_id:long = Update;
+updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
+updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;
+updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;
+updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;
+updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;
+updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;
+updateStickerSets#43ae3dec = Update;
+updateSavedGifs#9375341e = Update;
+updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
+updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
+updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;
+updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;
+updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;
+updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;
+updateReadFeaturedStickers#571d2742 = Update;
+updateRecentStickers#9a422c20 = Update;
+updateConfig#a229dd06 = Update;
+updatePtsChanged#3354678f = Update;
+updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;
+updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;
+updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;
+updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;
+updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;
+updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
+updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
+updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;
+updateLangPackTooLong#46560264 lang_code:string = Update;
+updateLangPack#56022f4d difference:LangPackDifference = Update;
+updateFavedStickers#e511996d = Update;
+updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;
+updateContactsReset#7084a7be = Update;
+updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;
+updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;
+updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
+updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;
+updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;
+updateNewScheduledMessage#39a51dfb message:Message = Update;
+updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
+updateTheme#8216fba3 theme:Theme = Update;
+updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
+updateLoginToken#564fe691 = Update;
+updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
+updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
+updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
+updateDialogFilters#3504914f = Update;
+updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;
+updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;
+updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;
+updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;
+updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;
+updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;
+updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
+updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+updateChat#f89a6a4e chat_id:long = Update;
+updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
+updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;
+updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
+updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;
+updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;
+updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updateNewMessageNew message.
updateMessageIDSent message with random_id client identifier was assigned an identifier.
updateDeleteMessagesMessages were deleted.
updateUserTypingThe user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.
updateChatUserTypingThe user is preparing a message in a group; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.
updateChatParticipantsComposition of chat participants changed.
updateUserStatusContact status update.
updateUserNameChanges the user's first name, last name and username.
updateUserPhotoChange of contact's profile photo.
updateNewEncryptedMessageNew encrypted message.
updateEncryptedChatTypingInterlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.
updateEncryptionChange of state in an encrypted chat.
updateEncryptedMessagesReadCommunication history in an encrypted chat was marked as read.
updateChatParticipantAddNew group member.
updateChatParticipantDeleteA member has left the group.
updateDcOptionsChanges in the data center configuration options.
updateNotifySettingsChanges in notification settings.
updateServiceNotificationA service message for the user.

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
updatePrivacyPrivacy rules were changed
updateUserPhoneA user's phone number was changed
updateReadHistoryInboxIncoming messages were read
updateReadHistoryOutboxOutgoing messages were read
updateWebPageAn (IV) webpage preview was generated
updateReadMessagesContentsContents of messages in the common message box were read
updateChannelTooLongThere are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
updateChannelA new channel is available
updateNewChannelMessageA new message was sent in a channel/supergroup
updateReadChannelInboxIncoming messages in a channel/supergroup were read
updateDeleteChannelMessagesSome messages in a supergroup/channel were deleted
updateChannelMessageViewsThe view counter of a message in a channel has changed
updateChatParticipantAdminAdmin permissions of a user in a legacy group were changed
updateNewStickerSetA new stickerset was installed
updateStickerSetsOrderThe order of stickersets was changed
updateStickerSetsInstalled stickersets have changed, the client should refetch them using messages.getAllStickers
updateSavedGifsThe saved gif list has changed, the client should refetch it using messages.getSavedGifs
updateBotInlineQueryAn incoming inline query
updateBotInlineSendThe result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
updateEditChannelMessageA message was edited in a channel/supergroup
updateBotCallbackQueryA callback button was pressed, and the button data was sent to the bot that created the button
updateEditMessageA message was edited
updateInlineBotCallbackQueryThis notification is received by bots when a button is pressed
updateReadChannelOutboxOutgoing messages in a channel/supergroup were read
updateDraftMessageNotifies a change of a message draft.
updateReadFeaturedStickersSome featured stickers were marked as read
updateRecentStickersThe recent sticker list was updated
updateConfigThe server-side configuration has changed; the client should re-fetch the config using help.getConfig
updatePtsChangedCommon message box sequence PTS has changed, state has to be refetched using updates.getState
updateChannelWebPageA webpage preview of a link in a channel/supergroup message was generated
updateDialogPinnedA dialog was pinned/unpinned
updatePinnedDialogsPinned dialogs were updated
updateBotWebhookJSONA new incoming event; for bots only
updateBotWebhookJSONQueryA new incoming query; for bots only
updateBotShippingQueryThis object contains information about an incoming shipping query.
updateBotPrecheckoutQueryThis object contains information about an incoming pre-checkout query.
updatePhoneCallAn incoming phone call
updateLangPackTooLongA language pack has changed, the client should manually fetch the changed strings using langpack.getDifference
updateLangPackLanguage pack updated
updateFavedStickersThe list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list
updateChannelReadMessagesContentsThe specified channel/supergroup messages were read
updateContactsResetAll contacts were deleted
updateChannelAvailableMessagesThe history of a channel/supergroup was hidden.
updateDialogUnreadMarkThe manual unread mark of a chat was changed
updateMessagePollThe results of a poll have changed
updateChatDefaultBannedRightsDefault banned rights in a normal chat were updated
updateFolderPeersThe dialog list of a folder was changed
updatePeerSettingsSettings of a certain peer have changed
updatePeerLocatedList of peers near you was updated
updateNewScheduledMessageNew incoming scheduled message
updateDeleteScheduledMessagesSome scheduled messages were deleted
updateThemeA new cloud theme was installed
updateGeoLiveViewedLive geoposition message was viewed
updateLoginTokenA login token (for login via QR code) was generated
updateMessagePollVoteA specific user has voted in a poll
updateDialogFilterA new folder was added
updateDialogFilterOrderNew chat folders order
updateDialogFiltersUpdate folder list
updatePhoneCallSignalingDataIncoming phone call signaling payload
updateChannelMessageForwardsThe forward counter of a message in a channel has changed
updateReadChannelDiscussionInboxIncoming messages were marked as read
updateReadChannelDiscussionOutboxOutgoing comments in a discussion thread were marked as read
updatePeerBlockedA peer was blocked
updateChannelUserTypinguser is typing in a supergroup, channel or message thread
updatePinnedMessagesSome messages were pinned in a chat
updatePinnedChannelMessagesMessages were pinned/unpinned in a channel/supergroup
updateChatA new chat is available
updateGroupCallParticipantsThe participant list of a certain group call has changed
updateGroupCallA new groupcall was started
updatePeerHistoryTTLThe Time-To-Live for messages sent by the current user in a specific chat has changed
updateChatParticipantA user has joined or left a specific chat
updateChannelParticipantA participant has left/joined a channel or supergroup.
updateBotStoppedA bot was stopped or re-started.
updateGroupCallConnectionNew WebRTC parameters
updateBotCommandsThe command set of a certain bot in a certain chat has changed.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Updates.html b/data/core.telegram.org/type/Updates.html new file mode 100644 index 0000000000..c5b774e673 --- /dev/null +++ b/data/core.telegram.org/type/Updates.html @@ -0,0 +1,508 @@ + + + + + Updates + + + + + + + + + + + + + +
+ +
+
+
+ +

Updates

+ +

Object which is perceived by the client without a call on its part when an event occurs.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+
+---functions---
+
+contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;
+contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;
+contacts.acceptContact#f831a20f id:InputUser = Updates;
+contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
+
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;
+messages.editChatTitle#73783ffd chat_id:long title:string = Updates;
+messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
+messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;
+messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;
+messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;
+messages.importChatInvite#6c50051c hash:string = Updates;
+messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;
+messages.migrateChat#a2875319 chat_id:long = Updates;
+messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
+messages.getAllDrafts#6a3f8d65 = Updates;
+messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
+messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;
+messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
+messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
+messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
+messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;
+
+help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
+
+channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;
+channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;
+channels.editTitle#566decd0 channel:InputChannel title:string = Updates;
+channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
+channels.joinChannel#24b524c5 channel:InputChannel = Updates;
+channels.leaveChannel#f836aa95 channel:InputChannel = Updates;
+channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;
+channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;
+channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;
+channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;
+channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
+channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;
+channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;
+channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;
+
+phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;
+phone.createGroupCall#48cdc6d8 flags:# rtmp_stream:flags.2?true peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
+phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
+phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
+phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
+phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;
+phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;
+phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;
+phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
+phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
+phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;
+
+account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;
+
+folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
+folders.deleteFolder#1c295881 folder_id:int = Updates;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updatesTooLongToo many updates, it is necessary to execute updates.getDifference.
updateShortMessageInfo about a message sent to (received from) another user
updateShortChatMessageShortened constructor containing info on one new incoming text message from a chat
updateShortShortened constructor containing info on one update not requiring auxiliary data
updatesCombinedConstructor for a group of updates.
updatesFull constructor of updates
updateShortSentMessageShortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
contacts.deleteContactsDeletes several contacts from the list.
messages.sendMessageSends a message to a chat
messages.sendMediaSend a media
messages.forwardMessagesForwards messages by their IDs.
messages.editChatTitleChanages chat name and sends a service message on it.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.createChatCreates a new chat.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getAppChangelogGet changelog of current app
channels.createChannelCreate a supergroup/channel.
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editTitleEdit the name of a channel/supergroup
channels.editPhotoChange the photo of a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.inviteToChannelInvite users to a channel/supergroup
channels.deleteChannelDelete a channel/supergroup
messages.migrateChatTurn a legacy group into a supergroup
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
channels.toggleSignaturesEnable/disable message signatures in channels
messages.editMessageEdit message
messages.getAllDraftsSave get all message drafts.
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
phone.discardCallRefuse or end running call
phone.setCallRatingRate a call
channels.editBannedBan/unban/kick a user in a supergroup/channel.
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
messages.sendMultiMediaSend an album of media
messages.updatePinnedMessagePin a message
account.getNotifyExceptionsReturns list of chats with non-default notification settings
messages.sendVoteVote in a poll
messages.getPollResultsGet poll results
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
folders.editPeerFoldersEdit peers in folder
folders.deleteFolderDelete a folder
contacts.addContactAdd an existing telegram user as contact
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
channels.editCreatorTransfer channel ownership
contacts.getLocatedGet contacts near you
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
messages.sendScheduledMessagesSend scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
phone.createGroupCallCreate a group call or livestream
phone.joinGroupCallJoin a group call
phone.leaveGroupCallLeave a group call
phone.inviteToGroupCallInvite a set of users to a group call.
phone.discardGroupCallTerminate a group call
phone.toggleGroupCallSettingsChange group call settings
messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
channels.convertToGigagroupConvert a supergroup to a gigagroup
phone.toggleGroupCallRecordStart or stop recording a group call
phone.editGroupCallParticipantEdit information about a given group call participant
phone.editGroupCallTitleEdit the title of a group call or livestream
phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
phone.startScheduledGroupCallStart a scheduled group call.
phone.joinGroupCallPresentationStart screen sharing in a call
phone.leaveGroupCallPresentationStop screen sharing in a group call
messages.setChatThemeChange the chat theme of a certain chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/UrlAuthResult.html b/data/core.telegram.org/type/UrlAuthResult.html new file mode 100644 index 0000000000..a0b6f055e5 --- /dev/null +++ b/data/core.telegram.org/type/UrlAuthResult.html @@ -0,0 +1,177 @@ + + + + + UrlAuthResult + + + + + + + + + + + + + +
+ +
+
+
+ +

UrlAuthResult

+ +

URL authorization result

+

+ +
+
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
+urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
+urlAuthResultDefault#a9d6db1f = UrlAuthResult;
+
+---functions---
+
+messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
+messages.acceptUrlAuth#b12c7125 flags:# write_allowed:flags.0?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
urlAuthResultRequestDetails about the authorization request, for more info click here »
urlAuthResultAcceptedDetails about an accepted authorization request, for more info click here »
urlAuthResultDefaultDetails about an accepted authorization request, for more info click here »
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/User.html b/data/core.telegram.org/type/User.html new file mode 100644 index 0000000000..20e0c4bbb0 --- /dev/null +++ b/data/core.telegram.org/type/User.html @@ -0,0 +1,177 @@ + + + + + User + + + + + + + + + + + + + +
+ +
+
+
+ +

User

+ +

Object defines a user.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+
+---functions---
+
+account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;
+account.updateUsername#3e0bdd7c username:string = User;
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
userEmptyEmpty constructor, non-existent user.
userIndicates info about a certain user
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
account.updateProfileUpdates user profile.
account.updateUsernameChanges username for the current user.
account.changePhoneChange the phone number of the current account
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/UserFull.html b/data/core.telegram.org/type/UserFull.html new file mode 100644 index 0000000000..719ddade41 --- /dev/null +++ b/data/core.telegram.org/type/UserFull.html @@ -0,0 +1,162 @@ + + + + + UserFull + + + + + + + + + + + + + +
+ +
+
+
+ +

UserFull

+ +

Object contains extended user info.

+

+ +
+
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
+
+---functions---
+
+users.getFullUser#ca30a5b1 id:InputUser = UserFull;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
userFullExtended user info
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
users.getFullUserReturns extended user info by ID.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/UserProfilePhoto.html b/data/core.telegram.org/type/UserProfilePhoto.html new file mode 100644 index 0000000000..a7ec0d4121 --- /dev/null +++ b/data/core.telegram.org/type/UserProfilePhoto.html @@ -0,0 +1,148 @@ + + + + + UserProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

UserProfilePhoto

+ +

Object contains info on the user's profile photo.

+

+ +
+
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;
+userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
userProfilePhotoEmptyProfile photo has not been set, or was hidden.
userProfilePhotoUser profile photo.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/UserStatus.html b/data/core.telegram.org/type/UserStatus.html new file mode 100644 index 0000000000..8f1327ddc3 --- /dev/null +++ b/data/core.telegram.org/type/UserStatus.html @@ -0,0 +1,168 @@ + + + + + UserStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

UserStatus

+ +

User online status

+

+ +
+
userStatusEmpty#9d05049 = UserStatus;
+userStatusOnline#edb93949 expires:int = UserStatus;
+userStatusOffline#8c703f was_online:int = UserStatus;
+userStatusRecently#e26f42f1 = UserStatus;
+userStatusLastWeek#7bf09fc = UserStatus;
+userStatusLastMonth#77ebc742 = UserStatus;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
userStatusEmptyUser status has not been set yet.
userStatusOnlineOnline status of the user.
userStatusOfflineThe user's offline status.
userStatusRecentlyOnline status: last seen recently
userStatusLastWeekOnline status: last seen last week
userStatusLastMonthOnline status: last seen last month
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Vector t.html b/data/core.telegram.org/type/Vector t.html new file mode 100644 index 0000000000..54de2ffb2d --- /dev/null +++ b/data/core.telegram.org/type/Vector t.html @@ -0,0 +1,143 @@ + + + + + Vector t + + + + + + + + + + + + + +
+ +
+
+
+ +

Vector t

+ +

Universal vector.

+

+ +
+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
vectorA universal vector constructor.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Video.html b/data/core.telegram.org/type/Video.html new file mode 100644 index 0000000000..e4aac783bc --- /dev/null +++ b/data/core.telegram.org/type/Video.html @@ -0,0 +1,128 @@ + + + + + Video + + + + + + + + + + + + + +
+ +
+
+
+ +

Video

+ +

Video.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/VideoSize.html b/data/core.telegram.org/type/VideoSize.html new file mode 100644 index 0000000000..96f57dfd75 --- /dev/null +++ b/data/core.telegram.org/type/VideoSize.html @@ -0,0 +1,143 @@ + + + + + VideoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

VideoSize

+ +

Represents an animated video thumbnail

+

+ +
+
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
videoSizeAnimated profile picture in MPEG4 format
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/WallPaper.html b/data/core.telegram.org/type/WallPaper.html new file mode 100644 index 0000000000..ca67900ae6 --- /dev/null +++ b/data/core.telegram.org/type/WallPaper.html @@ -0,0 +1,172 @@ + + + + + WallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

WallPaper

+ +

Object contains info on a wallpaper.

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
+
+---functions---
+
+account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;
+account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
wallPaperWallpaper settings.
wallPaperNoFileNo file wallpaper
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
account.getWallPaperGet info about a certain wallpaper
account.uploadWallPaperCreate and upload a new wallpaper
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/WallPaperSettings.html b/data/core.telegram.org/type/WallPaperSettings.html new file mode 100644 index 0000000000..62dc8c381f --- /dev/null +++ b/data/core.telegram.org/type/WallPaperSettings.html @@ -0,0 +1,143 @@ + + + + + WallPaperSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

WallPaperSettings

+ +

Wallpaper settings

+

+ +
+
wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
wallPaperSettingsWallpaper settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/WebAuthorization.html b/data/core.telegram.org/type/WebAuthorization.html new file mode 100644 index 0000000000..722bc888c0 --- /dev/null +++ b/data/core.telegram.org/type/WebAuthorization.html @@ -0,0 +1,143 @@ + + + + + WebAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

WebAuthorization

+ +

Web authorization

+

+ +
+
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
webAuthorizationRepresents a bot logged in using the Telegram login widget
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/WebDocument.html b/data/core.telegram.org/type/WebDocument.html new file mode 100644 index 0000000000..ab8dd84eaf --- /dev/null +++ b/data/core.telegram.org/type/WebDocument.html @@ -0,0 +1,148 @@ + + + + + WebDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

WebDocument

+ +

Remote document

+

+ +
+
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
webDocumentRemote document
webDocumentNoProxyRemote document that can be downloaded without proxying through telegram
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/WebPage.html b/data/core.telegram.org/type/WebPage.html new file mode 100644 index 0000000000..d3d5f7337f --- /dev/null +++ b/data/core.telegram.org/type/WebPage.html @@ -0,0 +1,177 @@ + + + + + WebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

WebPage

+ +

Instant View webpage preview

+

+ +
+
webPageEmpty#eb1477e8 id:long = WebPage;
+webPagePending#c586da1c id:long date:int = WebPage;
+webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
+
+---functions---
+
+messages.getWebPage#32ca8f91 url:string hash:int = WebPage;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
webPageEmptyNo preview is available for the webpage
webPagePendingA preview of the webpage is currently being generated
webPageWebpage preview
webPageNotModifiedThe preview of the webpage hasn't changed
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getWebPageGet instant view page
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/WebPageAttribute.html b/data/core.telegram.org/type/WebPageAttribute.html new file mode 100644 index 0000000000..81e361ff36 --- /dev/null +++ b/data/core.telegram.org/type/WebPageAttribute.html @@ -0,0 +1,143 @@ + + + + + WebPageAttribute + + + + + + + + + + + + + +
+ +
+
+
+ +

WebPageAttribute

+ +

Webpage attributes

+

+ +
+
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
webPageAttributeThemePage theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.AuthorizationForm b/data/core.telegram.org/type/account.AuthorizationForm new file mode 100644 index 0000000000..c91c97ca35 --- /dev/null +++ b/data/core.telegram.org/type/account.AuthorizationForm @@ -0,0 +1,162 @@ + + + + + Account.AuthorizationForm + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.AuthorizationForm

+ +

Authorization form

+

+ +
+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+---functions---
+
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.authorizationFormAuthorization form
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.Authorizations b/data/core.telegram.org/type/account.Authorizations new file mode 100644 index 0000000000..9546f70b64 --- /dev/null +++ b/data/core.telegram.org/type/account.Authorizations @@ -0,0 +1,162 @@ + + + + + Account.Authorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.Authorizations

+ +

Logged-in sessions

+

+ +
+
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
+
+---functions---
+
+account.getAuthorizations#e320c158 = account.Authorizations;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.authorizationsLogged-in sessions
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAuthorizationsGet logged-in sessions
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.AutoDownloadSettings b/data/core.telegram.org/type/account.AutoDownloadSettings new file mode 100644 index 0000000000..a71f740e6a --- /dev/null +++ b/data/core.telegram.org/type/account.AutoDownloadSettings @@ -0,0 +1,162 @@ + + + + + Account.AutoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.AutoDownloadSettings

+ +

Media autodownload settings

+

+ +
+
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
+
+---functions---
+
+account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.autoDownloadSettingsMedia autodownload settings
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAutoDownloadSettingsGet media autodownload settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.ChatThemes b/data/core.telegram.org/type/account.ChatThemes new file mode 100644 index 0000000000..61a5efdf2e --- /dev/null +++ b/data/core.telegram.org/type/account.ChatThemes @@ -0,0 +1,167 @@ + + + + + account.ChatThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ChatThemes

+ +

Available chat themes

+

+ +
+
account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
+account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
+
+---functions---
+
+account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
account.chatThemesNotModifiedThe available chat themes were not modified
account.chatThemesAvailable chat themes
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getChatThemesGet all available chat themes
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.ContentSettings b/data/core.telegram.org/type/account.ContentSettings new file mode 100644 index 0000000000..e8ffd73307 --- /dev/null +++ b/data/core.telegram.org/type/account.ContentSettings @@ -0,0 +1,162 @@ + + + + + account.ContentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ContentSettings

+ +

Sensitive content settings

+

+ +
+
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
+
+---functions---
+
+account.getContentSettings#8b9b4dae = account.ContentSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.contentSettingsSensitive content settings
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getContentSettingsGet sensitive content settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.Password b/data/core.telegram.org/type/account.Password new file mode 100644 index 0000000000..5305af021c --- /dev/null +++ b/data/core.telegram.org/type/account.Password @@ -0,0 +1,162 @@ + + + + + account.Password + + + + + + + + + + + + + +
+ +
+
+
+ +

account.Password

+ +

Configuration for two-factor authorization

+

+ +
+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+
+---functions---
+
+account.getPassword#548a30f5 = account.Password;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordConfiguration for two-factor authorization
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getPasswordObtain configuration for two-factor authorization with password
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.PasswordInputSettings b/data/core.telegram.org/type/account.PasswordInputSettings new file mode 100644 index 0000000000..94972c9aed --- /dev/null +++ b/data/core.telegram.org/type/account.PasswordInputSettings @@ -0,0 +1,146 @@ + + + + + account.PasswordInputSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.PasswordInputSettings

+ +

Constructor for setting up a new 2FA SRP password

+

+ +
+
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordInputSettingsSettings for setting up a new password
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.PasswordSettings b/data/core.telegram.org/type/account.PasswordSettings new file mode 100644 index 0000000000..576f249b87 --- /dev/null +++ b/data/core.telegram.org/type/account.PasswordSettings @@ -0,0 +1,164 @@ + + + + + account.PasswordSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.PasswordSettings

+ +

Private info associated to the password info (recovery email, telegram passport info & so on)

+

+ +
+
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
+---functions---
+
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordSettingsPrivate info associated to the password info (recovery email, telegram passport info & so on)
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.PrivacyRules b/data/core.telegram.org/type/account.PrivacyRules new file mode 100644 index 0000000000..01a30770aa --- /dev/null +++ b/data/core.telegram.org/type/account.PrivacyRules @@ -0,0 +1,167 @@ + + + + + Account.PrivacyRules + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.PrivacyRules

+ +

Privacy rules

+

+ +
+
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+
+---functions---
+
+account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;
+account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.privacyRulesPrivacy rules
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
account.getPrivacyGet privacy settings of current account
account.setPrivacyChange privacy settings of current account
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.ResetPasswordResult b/data/core.telegram.org/type/account.ResetPasswordResult new file mode 100644 index 0000000000..a5c2a6ec9c --- /dev/null +++ b/data/core.telegram.org/type/account.ResetPasswordResult @@ -0,0 +1,175 @@ + + + + + account.ResetPasswordResult + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ResetPasswordResult

+ +

Result of an account.resetPassword request.

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+
+---functions---
+
+account.resetPassword#9308ce1b = account.ResetPasswordResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
account.resetPasswordFailedWaitYou requested a password reset too many times, please wait until the specified date before retrying the reset.
account.resetPasswordRequestedWaitYou already requested a password reset, please wait until the specified date before retrying the reset.
account.resetPasswordOkThe 2FA password was reset successfully.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.resetPasswordInitiate a 2FA password reset
+

Related pages

+

account.resetPassword

+

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.SentChangePhoneCode b/data/core.telegram.org/type/account.SentChangePhoneCode new file mode 100644 index 0000000000..c0ce024e0b --- /dev/null +++ b/data/core.telegram.org/type/account.SentChangePhoneCode @@ -0,0 +1,128 @@ + + + + + Account.SentChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.SentChangePhoneCode

+ +

Sent phone code

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.SentEmailCode b/data/core.telegram.org/type/account.SentEmailCode new file mode 100644 index 0000000000..f5659893af --- /dev/null +++ b/data/core.telegram.org/type/account.SentEmailCode @@ -0,0 +1,162 @@ + + + + + account.SentEmailCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.SentEmailCode

+ +

The email code that was sent

+

+ +
+
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
+
+---functions---
+
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.sentEmailCodeThe sent email code
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.Takeout b/data/core.telegram.org/type/account.Takeout new file mode 100644 index 0000000000..2608c74cd5 --- /dev/null +++ b/data/core.telegram.org/type/account.Takeout @@ -0,0 +1,162 @@ + + + + + Account.Takeout + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.Takeout

+ +

Takeout info

+

+ +
+
account.takeout#4dba4501 id:long = account.Takeout;
+
+---functions---
+
+account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.takeoutTakout info
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.initTakeoutSessionInitialize account takeout session
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.Themes b/data/core.telegram.org/type/account.Themes new file mode 100644 index 0000000000..21b17f67c2 --- /dev/null +++ b/data/core.telegram.org/type/account.Themes @@ -0,0 +1,167 @@ + + + + + account.Themes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.Themes

+ +

Installed themes

+

+ +
+
account.themesNotModified#f41eb622 = account.Themes;
+account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
+
+---functions---
+
+account.getThemes#7206e458 format:string hash:long = account.Themes;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
account.themesNotModifiedNo new themes were installed
account.themesInstalled themes
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getThemesGet installed themes
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.TmpPassword b/data/core.telegram.org/type/account.TmpPassword new file mode 100644 index 0000000000..3a97076220 --- /dev/null +++ b/data/core.telegram.org/type/account.TmpPassword @@ -0,0 +1,162 @@ + + + + + Account.TmpPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.TmpPassword

+ +

Temporary password

+

+ +
+
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+
+---functions---
+
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.tmpPasswordTemporary payment password
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getTmpPasswordGet temporary payment password
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.WallPapers b/data/core.telegram.org/type/account.WallPapers new file mode 100644 index 0000000000..1494bd7c95 --- /dev/null +++ b/data/core.telegram.org/type/account.WallPapers @@ -0,0 +1,167 @@ + + + + + Account.WallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.WallPapers

+ +

Wallpapers

+

+ +
+
account.wallPapersNotModified#1c199183 = account.WallPapers;
+account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+
+---functions---
+
+account.getWallPapers#7967d36 hash:long = account.WallPapers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
account.wallPapersNotModifiedNo new wallpapers were found
account.wallPapersInstalled wallpapers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getWallPapersReturns a list of available wallpapers.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.WebAuthorizations b/data/core.telegram.org/type/account.WebAuthorizations new file mode 100644 index 0000000000..687072af52 --- /dev/null +++ b/data/core.telegram.org/type/account.WebAuthorizations @@ -0,0 +1,162 @@ + + + + + Account.WebAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.WebAuthorizations

+ +

Web authorizations

+

+ +
+
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
+
+---functions---
+
+account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.webAuthorizationsWeb authorizations
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getWebAuthorizationsGet web login widget authorizations
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.Authorization b/data/core.telegram.org/type/auth.Authorization new file mode 100644 index 0000000000..5fca033406 --- /dev/null +++ b/data/core.telegram.org/type/auth.Authorization @@ -0,0 +1,192 @@ + + + + + auth.Authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.Authorization

+ +

Oject contains info on user authorization.

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+
+---functions---
+
+auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;
+auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
+auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
+auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;
+auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.authorizationContains user authorization info.
auth.authorizationSignUpRequiredAn account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
auth.signUpRegisters a validated phone number in the system.
auth.signInSigns in a user with a validated phone number.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.checkPasswordTry logging to an account protected by a 2FA password.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.CheckedPhone b/data/core.telegram.org/type/auth.CheckedPhone new file mode 100644 index 0000000000..de79f5c4ec --- /dev/null +++ b/data/core.telegram.org/type/auth.CheckedPhone @@ -0,0 +1,128 @@ + + + + + Auth.CheckedPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

Auth.CheckedPhone

+ +

Checked phone

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.CodeType b/data/core.telegram.org/type/auth.CodeType new file mode 100644 index 0000000000..d652fe1f1e --- /dev/null +++ b/data/core.telegram.org/type/auth.CodeType @@ -0,0 +1,153 @@ + + + + + auth.CodeType + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.CodeType

+ +

Type of verification code that will be sent next if you call the resendCode method

+

+ +
+
auth.codeTypeSms#72a3158c = auth.CodeType;
+auth.codeTypeCall#741cd3e3 = auth.CodeType;
+auth.codeTypeFlashCall#226ccefb = auth.CodeType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.codeTypeSmsType of verification code that will be sent next if you call the resendCode method: SMS code
auth.codeTypeCallType of verification code that will be sent next if you call the resendCode method: SMS code
auth.codeTypeFlashCallType of verification code that will be sent next if you call the resendCode method: SMS code
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.ExportedAuthorization b/data/core.telegram.org/type/auth.ExportedAuthorization new file mode 100644 index 0000000000..be1bcc28cb --- /dev/null +++ b/data/core.telegram.org/type/auth.ExportedAuthorization @@ -0,0 +1,162 @@ + + + + + Auth.ExportedAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

Auth.ExportedAuthorization

+ +

Exported authorization

+

+ +
+
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
+
+---functions---
+
+auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
auth.exportedAuthorizationData for copying of authorization between data centres.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.LoginToken b/data/core.telegram.org/type/auth.LoginToken new file mode 100644 index 0000000000..d2fbae7b30 --- /dev/null +++ b/data/core.telegram.org/type/auth.LoginToken @@ -0,0 +1,177 @@ + + + + + auth.LoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.LoginToken

+ +

Login token (for QR code login)

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+
+---functions---
+
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.loginTokenLogin token (for QR code login)
auth.loginTokenMigrateToRepeat the query to the specified DC
auth.loginTokenSuccessLogin via token (QR code) succeded!
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
auth.exportLoginTokenExport login token (for login via QR code)
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.PasswordRecovery b/data/core.telegram.org/type/auth.PasswordRecovery new file mode 100644 index 0000000000..94ec06ba24 --- /dev/null +++ b/data/core.telegram.org/type/auth.PasswordRecovery @@ -0,0 +1,165 @@ + + + + + auth.PasswordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.PasswordRecovery

+ +

Recovery info of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+
+---functions---
+
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
auth.passwordRecoveryRecovery info of a 2FA password, only for accounts with a recovery email configured.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.SentCode b/data/core.telegram.org/type/auth.SentCode new file mode 100644 index 0000000000..1f1481338f --- /dev/null +++ b/data/core.telegram.org/type/auth.SentCode @@ -0,0 +1,183 @@ + + + + + auth.SentCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.SentCode

+ +

Contains info on a confirmation code message sent via SMS, phone call or Telegram.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+
+---functions---
+
+auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
+
+account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;
+account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
auth.sentCodeContains info about a sent verification code.
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
auth.sendCodeSend the verification code for login
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.SentCodeType b/data/core.telegram.org/type/auth.SentCodeType new file mode 100644 index 0000000000..f8c320c6f0 --- /dev/null +++ b/data/core.telegram.org/type/auth.SentCodeType @@ -0,0 +1,158 @@ + + + + + auth.SentCodeType + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.SentCodeType

+ +

Type of the verification code that was sent

+

+ +
+
auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;
+auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;
+auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;
+auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.sentCodeTypeAppThe code was sent through the telegram app
auth.sentCodeTypeSmsThe code was sent via SMS
auth.sentCodeTypeCallThe code will be sent via a phone call: a synthesized voice will tell the user which verification code to input.
auth.sentCodeTypeFlashCallThe code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/bytes.html b/data/core.telegram.org/type/bytes.html new file mode 100644 index 0000000000..898629893f --- /dev/null +++ b/data/core.telegram.org/type/bytes.html @@ -0,0 +1,125 @@ + + + + + bytes + + + + + + + + + + + + + +
+ +
+
+
+ +

bytes

+ +

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

+

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

+

Related pages

+

string

+

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

+

Further details on basic types»

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/channels.AdminLogResults b/data/core.telegram.org/type/channels.AdminLogResults new file mode 100644 index 0000000000..27b366ed1f --- /dev/null +++ b/data/core.telegram.org/type/channels.AdminLogResults @@ -0,0 +1,162 @@ + + + + + Channels.AdminLogResults + + + + + + + + + + + + + +
+ +
+
+
+ +

Channels.AdminLogResults

+ +

Admin log events

+

+ +
+
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+
+---functions---
+
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channels.adminLogResultsAdmin log events
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getAdminLogGet the admin log of a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/channels.ChannelParticipant b/data/core.telegram.org/type/channels.ChannelParticipant new file mode 100644 index 0000000000..d52b701832 --- /dev/null +++ b/data/core.telegram.org/type/channels.ChannelParticipant @@ -0,0 +1,162 @@ + + + + + Channels.ChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

Channels.ChannelParticipant

+ +

Channel participant

+

+ +
+
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+
+---functions---
+
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channels.channelParticipantRepresents a channel participant
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getParticipantGet info about a channel/supergroup participant
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/channels.ChannelParticipants b/data/core.telegram.org/type/channels.ChannelParticipants new file mode 100644 index 0000000000..f740392bcc --- /dev/null +++ b/data/core.telegram.org/type/channels.ChannelParticipants @@ -0,0 +1,167 @@ + + + + + Channels.ChannelParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

Channels.ChannelParticipants

+ +

Channel/supergroup participants

+

+ +
+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
+
+---functions---
+
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
channels.channelParticipantsRepresents multiple channel participants
channels.channelParticipantsNotModifiedNo new participant info could be found
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getParticipantsGet the participants of a channel
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/contacts.Blocked b/data/core.telegram.org/type/contacts.Blocked new file mode 100644 index 0000000000..9ce9e6f2e9 --- /dev/null +++ b/data/core.telegram.org/type/contacts.Blocked @@ -0,0 +1,167 @@ + + + + + contacts.Blocked + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.Blocked

+ +

Info on users from the current user's black list.

+

+ +
+
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+
+---functions---
+
+contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
contacts.blockedFull list of blocked users.
contacts.blockedSliceIncomplete list of blocked users.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.getBlockedReturns the list of blocked users.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/contacts.Contacts b/data/core.telegram.org/type/contacts.Contacts new file mode 100644 index 0000000000..11c346b49f --- /dev/null +++ b/data/core.telegram.org/type/contacts.Contacts @@ -0,0 +1,167 @@ + + + + + contacts.Contacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.Contacts

+ +

Info on the current user's contact list.

+

+ +
+
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
+contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
+
+---functions---
+
+contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
contacts.contactsNotModifiedContact list on the server is the same as the list on the client.
contacts.contactsThe current user's contact list and info on users.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.getContactsReturns the current user's contact list.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/contacts.Found b/data/core.telegram.org/type/contacts.Found new file mode 100644 index 0000000000..a68139410f --- /dev/null +++ b/data/core.telegram.org/type/contacts.Found @@ -0,0 +1,162 @@ + + + + + contacts.Found + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.Found

+ +

Object contains info on users found by name substring and auxiliary data.

+

+ +
+
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
+
+---functions---
+
+contacts.search#11f812d8 q:string limit:int = contacts.Found;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contacts.foundUsers found by name substring and auxiliary data.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.searchReturns users found by username substring.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/contacts.ImportedContacts b/data/core.telegram.org/type/contacts.ImportedContacts new file mode 100644 index 0000000000..12b11e5739 --- /dev/null +++ b/data/core.telegram.org/type/contacts.ImportedContacts @@ -0,0 +1,162 @@ + + + + + contacts.ImportedContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.ImportedContacts

+ +

Object contains info on succesfully imported contacts.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+
+---functions---
+
+contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contacts.importedContactsInfo on succesfully imported contacts.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/contacts.Link b/data/core.telegram.org/type/contacts.Link new file mode 100644 index 0000000000..48ca844de4 --- /dev/null +++ b/data/core.telegram.org/type/contacts.Link @@ -0,0 +1,128 @@ + + + + + contacts.Link + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.Link

+ +

Object describes the connection between a certain user and the current authorized user.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/contacts.ResolvedPeer b/data/core.telegram.org/type/contacts.ResolvedPeer new file mode 100644 index 0000000000..bd6365796a --- /dev/null +++ b/data/core.telegram.org/type/contacts.ResolvedPeer @@ -0,0 +1,162 @@ + + + + + Contacts.ResolvedPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

Contacts.ResolvedPeer

+ +

Peer returned after resolving a @username

+

+ +
+
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
+
+---functions---
+
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contacts.resolvedPeerResolved peer
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.resolveUsernameResolve a @username to get peer info
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/contacts.TopPeers b/data/core.telegram.org/type/contacts.TopPeers new file mode 100644 index 0000000000..cc6018dd40 --- /dev/null +++ b/data/core.telegram.org/type/contacts.TopPeers @@ -0,0 +1,172 @@ + + + + + Contacts.TopPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

Contacts.TopPeers

+ +

Top peers

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+
+---functions---
+
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
contacts.topPeersNotModifiedTop peer info hasn't changed
contacts.topPeersTop peers
contacts.topPeersDisabledTop peers disabled
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.getTopPeersGet most used peers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/double.html b/data/core.telegram.org/type/double.html new file mode 100644 index 0000000000..b1a3a9ae88 --- /dev/null +++ b/data/core.telegram.org/type/double.html @@ -0,0 +1,118 @@ + + + + + double + + + + + + + + + + + + + +
+ +
+
+
+ +

double

+ +

A basic bare type, values of which correspond two-element sequences containing 64-bit real numbers in a standard double format.

+

More on basic types»

+

Related pages

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.AppUpdate b/data/core.telegram.org/type/help.AppUpdate new file mode 100644 index 0000000000..4c9a203e8d --- /dev/null +++ b/data/core.telegram.org/type/help.AppUpdate @@ -0,0 +1,167 @@ + + + + + help.AppUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.AppUpdate

+ +

Contains info on app update availability.

+

+ +
+
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
+help.noAppUpdate#c45a6536 = help.AppUpdate;
+
+---functions---
+
+help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.appUpdateAn update is available for the application.
help.noAppUpdateNo updates are available for the application.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getAppUpdateReturns information on update availability for the current application.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.CountriesList b/data/core.telegram.org/type/help.CountriesList new file mode 100644 index 0000000000..00d0dee1cc --- /dev/null +++ b/data/core.telegram.org/type/help.CountriesList @@ -0,0 +1,167 @@ + + + + + help.CountriesList + + + + + + + + + + + + + +
+ +
+
+
+ +

help.CountriesList

+ +

Name, ISO code, localized name and phone codes/patterns of all available countries

+

+ +
+
help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+
+---functions---
+
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.countriesListNotModifiedThe country list has not changed
help.countriesListName, ISO code, localized name and phone codes/patterns of all available countries
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.Country b/data/core.telegram.org/type/help.Country new file mode 100644 index 0000000000..b88bc8e262 --- /dev/null +++ b/data/core.telegram.org/type/help.Country @@ -0,0 +1,143 @@ + + + + + help.Country + + + + + + + + + + + + + +
+ +
+
+
+ +

help.Country

+ +

Name, ISO code, localized name and phone codes/patterns of a specific country

+

+ +
+
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.countryName, ISO code, localized name and phone codes/patterns of a specific country
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.CountryCode b/data/core.telegram.org/type/help.CountryCode new file mode 100644 index 0000000000..1307f9054a --- /dev/null +++ b/data/core.telegram.org/type/help.CountryCode @@ -0,0 +1,143 @@ + + + + + help.CountryCode + + + + + + + + + + + + + +
+ +
+
+
+ +

help.CountryCode

+ +

Country code and phone number pattern of a specific country

+

+ +
+
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.countryCodeCountry code and phone number pattern of a specific country
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.DeepLinkInfo b/data/core.telegram.org/type/help.DeepLinkInfo new file mode 100644 index 0000000000..debbcaaf24 --- /dev/null +++ b/data/core.telegram.org/type/help.DeepLinkInfo @@ -0,0 +1,167 @@ + + + + + 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.InviteText b/data/core.telegram.org/type/help.InviteText new file mode 100644 index 0000000000..8c0e105fe5 --- /dev/null +++ b/data/core.telegram.org/type/help.InviteText @@ -0,0 +1,162 @@ + + + + + help.InviteText + + + + + + + + + + + + + +
+ +
+
+
+ +

help.InviteText

+ +

Object contains info on the text of a message with an invitation.

+

+ +
+
help.inviteText#18cb9f78 message:string = help.InviteText;
+
+---functions---
+
+help.getInviteText#4d392343 = help.InviteText;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.inviteTextText of a text message with an invitation to install application.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getInviteTextReturns text of a text message with an invitation.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.PassportConfig b/data/core.telegram.org/type/help.PassportConfig new file mode 100644 index 0000000000..c553d378fb --- /dev/null +++ b/data/core.telegram.org/type/help.PassportConfig @@ -0,0 +1,169 @@ + + + + + Help.PassportConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.PassportConfig

+ +

Telegram passport configuration

+

+ +
+
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
+help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
+
+---functions---
+
+help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.passportConfigNotModifiedPassword configuration not modified
help.passportConfigTelegram passport configuration
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getPassportConfigGet passport configuration
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.PromoData b/data/core.telegram.org/type/help.PromoData new file mode 100644 index 0000000000..2b20632203 --- /dev/null +++ b/data/core.telegram.org/type/help.PromoData @@ -0,0 +1,167 @@ + + + + + help.PromoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.PromoData

+ +

Info about pinned MTProxy or Public Service Announcement peers.

+

+ +
+
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
+help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
+
+---functions---
+
+help.getPromoData#c0977421 = help.PromoData;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.promoDataEmptyNo PSA/MTProxy info is available
help.promoDataMTProxy/Public Service Announcement information
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getPromoDataGet MTProxy/Public Service Announcement information
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.ProxyData b/data/core.telegram.org/type/help.ProxyData new file mode 100644 index 0000000000..aa1148fcf4 --- /dev/null +++ b/data/core.telegram.org/type/help.ProxyData @@ -0,0 +1,130 @@ + + + + + Help.ProxyData + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.ProxyData

+ +

Info about an MTProxy

+

+ +
+

+

Related pages

+

MTProto transports

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.RecentMeUrls b/data/core.telegram.org/type/help.RecentMeUrls new file mode 100644 index 0000000000..ecbddce68b --- /dev/null +++ b/data/core.telegram.org/type/help.RecentMeUrls @@ -0,0 +1,162 @@ + + + + + Help.RecentMeUrls + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.RecentMeUrls

+ +

Recent t.me URLs

+

+ +
+
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
+
+---functions---
+
+help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.recentMeUrlsRecent t.me URLs
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getRecentMeUrlsGet recently used t.me links
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.Support b/data/core.telegram.org/type/help.Support new file mode 100644 index 0000000000..9bf3bd3706 --- /dev/null +++ b/data/core.telegram.org/type/help.Support @@ -0,0 +1,162 @@ + + + + + help.Support + + + + + + + + + + + + + +
+ +
+
+
+ +

help.Support

+ +

Info about the support user, relevant to the current user.

+

+ +
+
help.support#17c6b5f6 phone_number:string user:User = help.Support;
+
+---functions---
+
+help.getSupport#9cdf08cd = help.Support;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.supportInfo on support user.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getSupportReturns the support user for the 'ask a question' feature.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.SupportName b/data/core.telegram.org/type/help.SupportName new file mode 100644 index 0000000000..9dc768c76a --- /dev/null +++ b/data/core.telegram.org/type/help.SupportName @@ -0,0 +1,162 @@ + + + + + Help.SupportName + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.SupportName

+ +

Get localized name for support user

+

+ +
+
help.supportName#8c05f1c9 name:string = help.SupportName;
+
+---functions---
+
+help.getSupportName#d360e72c = help.SupportName;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.supportNameLocalized name for telegram support
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getSupportNameGet localized name of the telegram support user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.TermsOfService b/data/core.telegram.org/type/help.TermsOfService new file mode 100644 index 0000000000..8d4d3ac168 --- /dev/null +++ b/data/core.telegram.org/type/help.TermsOfService @@ -0,0 +1,143 @@ + + + + + help.TermsOfService + + + + + + + + + + + + + +
+ +
+
+
+ +

help.TermsOfService

+ +

Contains info about the latest telegram Terms Of Service.

+

+ +
+
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.termsOfServiceInfo about the latest telegram Terms Of Service
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.TermsOfServiceUpdate b/data/core.telegram.org/type/help.TermsOfServiceUpdate new file mode 100644 index 0000000000..77e24f1d4d --- /dev/null +++ b/data/core.telegram.org/type/help.TermsOfServiceUpdate @@ -0,0 +1,167 @@ + + + + + Help.TermsOfServiceUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.TermsOfServiceUpdate

+ +

Update of Telegram's terms of service

+

+ +
+
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+
+---functions---
+
+help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.termsOfServiceUpdateEmptyNo changes were made to telegram's terms of service
help.termsOfServiceUpdateInfo about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.UserInfo b/data/core.telegram.org/type/help.UserInfo new file mode 100644 index 0000000000..3e21ed83d3 --- /dev/null +++ b/data/core.telegram.org/type/help.UserInfo @@ -0,0 +1,172 @@ + + + + + Help.UserInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.UserInfo

+ +

User info

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+
+---functions---
+
+help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;
+help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.userInfoEmptyInternal use
help.userInfoInternal use
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
help.getUserInfoInternal use
help.editUserInfoInternal use
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/int.html b/data/core.telegram.org/type/int.html new file mode 100644 index 0000000000..e80540da18 --- /dev/null +++ b/data/core.telegram.org/type/int.html @@ -0,0 +1,118 @@ + + + + + int + + + + + + + + + + + + + +
+ +
+
+
+ +

int

+ +

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

+

More on basic types »

+

Related pages

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/long.html b/data/core.telegram.org/type/long.html new file mode 100644 index 0000000000..152e73654f --- /dev/null +++ b/data/core.telegram.org/type/long.html @@ -0,0 +1,118 @@ + + + + + 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.AffectedFoundMessages b/data/core.telegram.org/type/messages.AffectedFoundMessages new file mode 100644 index 0000000000..9e8a731077 --- /dev/null +++ b/data/core.telegram.org/type/messages.AffectedFoundMessages @@ -0,0 +1,162 @@ + + + + + messages.AffectedFoundMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.AffectedFoundMessages

+ +

Messages found and affected by changes

+

+ +
+
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
+
+---functions---
+
+messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.affectedFoundMessagesMessages found and affected by changes
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.deletePhoneCallHistoryDelete the phone call history with a user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.AffectedHistory b/data/core.telegram.org/type/messages.AffectedHistory new file mode 100644 index 0000000000..e1f95a5960 --- /dev/null +++ b/data/core.telegram.org/type/messages.AffectedHistory @@ -0,0 +1,178 @@ + + + + + messages.AffectedHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.AffectedHistory

+ +

Object contains info on affected part of communication history with the user or in a chat.

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+
+---functions---
+
+messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
+
+channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.affectedHistoryAffected part of communication history with the user or in a chat.
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.deleteHistoryDeletes communication history.
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
messages.readMentionsMark mentions as read
messages.unpinAllMessagesUnpin all pinned messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.AffectedMessages b/data/core.telegram.org/type/messages.AffectedMessages new file mode 100644 index 0000000000..d5a4cd5b2c --- /dev/null +++ b/data/core.telegram.org/type/messages.AffectedMessages @@ -0,0 +1,178 @@ + + + + + Messages.AffectedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.AffectedMessages

+ +

Messages affected by changes

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+
+---functions---
+
+messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;
+messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;
+messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;
+
+channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.affectedMessagesEvents affected by operation
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.readHistoryMarks message history as read.
messages.deleteMessagesDeletes messages by their identifiers.
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
channels.deleteMessagesDelete messages in a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.AllStickers b/data/core.telegram.org/type/messages.AllStickers new file mode 100644 index 0000000000..6571f62fe4 --- /dev/null +++ b/data/core.telegram.org/type/messages.AllStickers @@ -0,0 +1,172 @@ + + + + + Messages.AllStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.AllStickers

+ +

All stickers

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+
+---functions---
+
+messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;
+messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.allStickersNotModifiedInfo about all installed stickers hasn't changed
messages.allStickersInfo about all installed stickers
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getAllStickersGet all installed stickers
messages.getMaskStickersGet installed mask stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.ArchivedStickers b/data/core.telegram.org/type/messages.ArchivedStickers new file mode 100644 index 0000000000..573b9cb6cb --- /dev/null +++ b/data/core.telegram.org/type/messages.ArchivedStickers @@ -0,0 +1,162 @@ + + + + + Messages.ArchivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.ArchivedStickers

+ +

Archived stickers

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
+
+---functions---
+
+messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.archivedStickersArchived stickersets
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getArchivedStickersGet all archived stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.BotCallbackAnswer b/data/core.telegram.org/type/messages.BotCallbackAnswer new file mode 100644 index 0000000000..bd5f776ff5 --- /dev/null +++ b/data/core.telegram.org/type/messages.BotCallbackAnswer @@ -0,0 +1,162 @@ + + + + + Messages.BotCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.BotCallbackAnswer

+ +

Callback answer of bot

+

+ +
+
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+
+---functions---
+
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.botCallbackAnswerCallback answer sent by the bot in response to a button press
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.BotResults b/data/core.telegram.org/type/messages.BotResults new file mode 100644 index 0000000000..3d8d43a6e4 --- /dev/null +++ b/data/core.telegram.org/type/messages.BotResults @@ -0,0 +1,162 @@ + + + + + messages.BotResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.BotResults

+ +

Result of a query to an inline bot

+

+ +
+
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
+
+---functions---
+
+messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.botResultsResult of a query to an inline bot
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getInlineBotResultsQuery an inline bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.ChatAdminsWithInvites b/data/core.telegram.org/type/messages.ChatAdminsWithInvites new file mode 100644 index 0000000000..71c75b9593 --- /dev/null +++ b/data/core.telegram.org/type/messages.ChatAdminsWithInvites @@ -0,0 +1,162 @@ + + + + + messages.ChatAdminsWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ChatAdminsWithInvites

+ +

Info about chat invites generated by admins.

+

+ +
+
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
+
+---functions---
+
+messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.chatAdminsWithInvitesInfo about chat invites generated by admins.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getAdminsWithInvitesGet info about chat invites generated by admins.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.ChatInviteImporters b/data/core.telegram.org/type/messages.ChatInviteImporters new file mode 100644 index 0000000000..da87a3270d --- /dev/null +++ b/data/core.telegram.org/type/messages.ChatInviteImporters @@ -0,0 +1,162 @@ + + + + + messages.ChatInviteImporters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ChatInviteImporters

+ +

List of users that imported a chat invitation link.

+

+ +
+
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+
+---functions---
+
+messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.chatInviteImportersInfo about the users that joined the chat using a specific chat invite
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.Chats b/data/core.telegram.org/type/messages.Chats new file mode 100644 index 0000000000..89288e129c --- /dev/null +++ b/data/core.telegram.org/type/messages.Chats @@ -0,0 +1,198 @@ + + + + + messages.Chats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.Chats

+ +

Object contains list of chats with auxiliary data.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+
+---functions---
+
+messages.getChats#49e9528f id:Vector<long> = messages.Chats;
+messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;
+messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;
+
+channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;
+channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;
+channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.chatsList of chats with auxiliary data.
messages.chatsSlicePartial list of chats, more would have to be fetched with pagination
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getChatsReturns chat basic info on their IDs.
channels.getChannelsGet info about channels/supergroups
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
messages.getCommonChatsGet chats in common with a user
messages.getAllChatsGet all chats, channels and supergroups
channels.getLeftChannelsGet a list of channels/supergroups we left
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.CheckedHistoryImportPeer b/data/core.telegram.org/type/messages.CheckedHistoryImportPeer new file mode 100644 index 0000000000..0996418f17 --- /dev/null +++ b/data/core.telegram.org/type/messages.CheckedHistoryImportPeer @@ -0,0 +1,165 @@ + + + + + messages.CheckedHistoryImportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.CheckedHistoryImportPeer

+ +

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

+

+ +
+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+
+---functions---
+
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.checkedHistoryImportPeerContains a confirmation text to be shown to the user, upon importing chat history.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat.

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.DhConfig b/data/core.telegram.org/type/messages.DhConfig new file mode 100644 index 0000000000..83405aa313 --- /dev/null +++ b/data/core.telegram.org/type/messages.DhConfig @@ -0,0 +1,167 @@ + + + + + Messages.DhConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.DhConfig

+ +

Contains info on cofiguring parameters for key generation by Diffie-Hellman protocol.

+

+ +
+
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
+messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
+
+---functions---
+
+messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.dhConfigNotModifiedConfiguring parameters did not change.
messages.dhConfigNew set of configuring parameters.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.Dialogs b/data/core.telegram.org/type/messages.Dialogs new file mode 100644 index 0000000000..6532ae3ba4 --- /dev/null +++ b/data/core.telegram.org/type/messages.Dialogs @@ -0,0 +1,172 @@ + + + + + messages.Dialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.Dialogs

+ +

Object contains a list of chats with messages and auxiliary data.

+

+ +
+
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
+
+---functions---
+
+messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.dialogsFull list of chats with messages and auxiliary data.
messages.dialogsSliceIncomplete list of dialogs with messages and auxiliary data.
messages.dialogsNotModifiedDialogs haven't changed
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getDialogsReturns the current user dialog list.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.DiscussionMessage b/data/core.telegram.org/type/messages.DiscussionMessage new file mode 100644 index 0000000000..bbd699a196 --- /dev/null +++ b/data/core.telegram.org/type/messages.DiscussionMessage @@ -0,0 +1,162 @@ + + + + + messages.DiscussionMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.DiscussionMessage

+ +

Info about a message thread

+

+ +
+
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
+
+---functions---
+
+messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.discussionMessageInformation about a message thread
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.ExportedChatInvite b/data/core.telegram.org/type/messages.ExportedChatInvite new file mode 100644 index 0000000000..998e30f4f6 --- /dev/null +++ b/data/core.telegram.org/type/messages.ExportedChatInvite @@ -0,0 +1,172 @@ + + + + + messages.ExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ExportedChatInvite

+ +

Contains info about a chat invite, and eventually a pointer to the newest chat invite.

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+
+---functions---
+
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
+messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.exportedChatInviteInfo about a chat invite
messages.exportedChatInviteReplacedThe specified chat invite was replaced with another one
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.ExportedChatInvites b/data/core.telegram.org/type/messages.ExportedChatInvites new file mode 100644 index 0000000000..0b10b1e633 --- /dev/null +++ b/data/core.telegram.org/type/messages.ExportedChatInvites @@ -0,0 +1,162 @@ + + + + + messages.ExportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ExportedChatInvites

+ +

Info about chat invites exported by a certain admin.

+

+ +
+
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
+
+---functions---
+
+messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.exportedChatInvitesInfo about chat invites exported by a certain admin.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.FavedStickers b/data/core.telegram.org/type/messages.FavedStickers new file mode 100644 index 0000000000..e76cb717e7 --- /dev/null +++ b/data/core.telegram.org/type/messages.FavedStickers @@ -0,0 +1,167 @@ + + + + + Messages.FavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FavedStickers

+ +

Favorited stickers

+

+ +
+
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+
+---functions---
+
+messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.favedStickersNotModifiedNo new favorited stickers were found
messages.favedStickersFavorited stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getFavedStickersGet faved stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.FeaturedStickers b/data/core.telegram.org/type/messages.FeaturedStickers new file mode 100644 index 0000000000..60b6c4c0f3 --- /dev/null +++ b/data/core.telegram.org/type/messages.FeaturedStickers @@ -0,0 +1,172 @@ + + + + + Messages.FeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FeaturedStickers

+ +

Featured stickers

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+
+---functions---
+
+messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;
+messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.featuredStickersNotModifiedFeatured stickers haven't changed
messages.featuredStickersFeatured stickersets
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getFeaturedStickersGet featured stickers
messages.getOldFeaturedStickersOld method for fetching featured sticker
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.FoundGifs b/data/core.telegram.org/type/messages.FoundGifs new file mode 100644 index 0000000000..01f4ddc619 --- /dev/null +++ b/data/core.telegram.org/type/messages.FoundGifs @@ -0,0 +1,128 @@ + + + + + Messages.FoundGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FoundGifs

+ +

Found GIFs

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.FoundStickerSets b/data/core.telegram.org/type/messages.FoundStickerSets new file mode 100644 index 0000000000..a04e8a7921 --- /dev/null +++ b/data/core.telegram.org/type/messages.FoundStickerSets @@ -0,0 +1,167 @@ + + + + + Messages.FoundStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FoundStickerSets

+ +

Found stickersets

+

+ +
+
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
+messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
+
+---functions---
+
+messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.foundStickerSetsNotModifiedNo further results were found
messages.foundStickerSetsFound stickersets
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.searchStickerSetsSearch for stickersets
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.HighScores b/data/core.telegram.org/type/messages.HighScores new file mode 100644 index 0000000000..c950349984 --- /dev/null +++ b/data/core.telegram.org/type/messages.HighScores @@ -0,0 +1,167 @@ + + + + + Messages.HighScores + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.HighScores

+ +

High scores (in games)

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+
+---functions---
+
+messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.highScoresHighscores in a game
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.HistoryImport b/data/core.telegram.org/type/messages.HistoryImport new file mode 100644 index 0000000000..c1bde8eef5 --- /dev/null +++ b/data/core.telegram.org/type/messages.HistoryImport @@ -0,0 +1,165 @@ + + + + + messages.HistoryImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.HistoryImport

+ +

Identifier of a history import session, click here for more info ».

+

+ +
+
messages.historyImport#1662af0b id:long = messages.HistoryImport;
+
+---functions---
+
+messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.historyImportID of a specific chat import session
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.initHistoryImportImport chat history from a foreign chat app into a specific Telegram chat.
Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.HistoryImportParsed b/data/core.telegram.org/type/messages.HistoryImportParsed new file mode 100644 index 0000000000..ee4a11bc8d --- /dev/null +++ b/data/core.telegram.org/type/messages.HistoryImportParsed @@ -0,0 +1,162 @@ + + + + + messages.HistoryImportParsed + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.HistoryImportParsed

+ +

Contains information about a chat export file, generated by a foreign chat app.

+

+ +
+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+
+---functions---
+
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.historyImportParsedContains information about a chat export file, generated by a foreign chat app. If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.checkHistoryImportObtains information about a chat export file, generated by a foreign chat app.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.InactiveChats b/data/core.telegram.org/type/messages.InactiveChats new file mode 100644 index 0000000000..f3944798c2 --- /dev/null +++ b/data/core.telegram.org/type/messages.InactiveChats @@ -0,0 +1,162 @@ + + + + + messages.InactiveChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.InactiveChats

+ +

Inactive chat list

+

+ +
+
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
+
+---functions---
+
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.inactiveChatsInactive chat list
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getInactiveChannelsGet inactive channels and supergroups
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.MessageEditData b/data/core.telegram.org/type/messages.MessageEditData new file mode 100644 index 0000000000..8ba8a76e4a --- /dev/null +++ b/data/core.telegram.org/type/messages.MessageEditData @@ -0,0 +1,162 @@ + + + + + Messages.MessageEditData + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.MessageEditData

+ +

Message edit data for media

+

+ +
+
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
+
+---functions---
+
+messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.messageEditDataMessage edit data for media
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getMessageEditDataFind out if a media message's caption can be edited
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.MessageViews b/data/core.telegram.org/type/messages.MessageViews new file mode 100644 index 0000000000..4dd41b1614 --- /dev/null +++ b/data/core.telegram.org/type/messages.MessageViews @@ -0,0 +1,162 @@ + + + + + messages.MessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.MessageViews

+ +

View, forward counter + info about replies

+

+ +
+
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
+
+---functions---
+
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.messageViewsView, forward counter + info about replies
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.Messages b/data/core.telegram.org/type/messages.Messages new file mode 100644 index 0000000000..e54d01214d --- /dev/null +++ b/data/core.telegram.org/type/messages.Messages @@ -0,0 +1,229 @@ + + + + + messages.Messages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.Messages

+ +

Object contains infor on list of messages with auxiliary data.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+
+---functions---
+
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
+messages.getHistory#4423e6c5 peer:InputPeer offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
+messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
+messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
+messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
+messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
+
+stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.messagesFull list of messages with auxilary data.
messages.messagesSliceIncomplete list of messages and auxiliary data.
messages.channelMessagesChannel messages
messages.messagesNotModifiedNo new messages matching the query were found
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getMessagesReturns the list of messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.searchGets back found messages
channels.getMessagesGet channel/supergroup messages
messages.searchGlobalSearch for messages and peers globally
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.getRecentLocationsGet live location history of a certain user
messages.getScheduledHistoryGet scheduled messages
messages.getScheduledMessagesGet scheduled messages
messages.getRepliesGet messages in a reply thread
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.PeerDialogs b/data/core.telegram.org/type/messages.PeerDialogs new file mode 100644 index 0000000000..b4eb333f5b --- /dev/null +++ b/data/core.telegram.org/type/messages.PeerDialogs @@ -0,0 +1,167 @@ + + + + + Messages.PeerDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.PeerDialogs

+ +

List of dialogs

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+
+---functions---
+
+messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
+messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.peerDialogsDialog info of multiple peers
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.RecentStickers b/data/core.telegram.org/type/messages.RecentStickers new file mode 100644 index 0000000000..d5a5435b1b --- /dev/null +++ b/data/core.telegram.org/type/messages.RecentStickers @@ -0,0 +1,167 @@ + + + + + Messages.RecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.RecentStickers

+ +

Recent stickers

+

+ +
+
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
+messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
+
+---functions---
+
+messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.recentStickersNotModifiedNo new recent sticker was found
messages.recentStickersRecently used stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getRecentStickersGet recent stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.SearchCounter b/data/core.telegram.org/type/messages.SearchCounter new file mode 100644 index 0000000000..61cfea4766 --- /dev/null +++ b/data/core.telegram.org/type/messages.SearchCounter @@ -0,0 +1,143 @@ + + + + + Messages.SearchCounter + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.SearchCounter

+ +

Number of results that would be returned by a search

+

+ +
+
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.searchCounterIndicates how many results would be found by a messages.search call with the same parameters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.SentEncryptedMessage b/data/core.telegram.org/type/messages.SentEncryptedMessage new file mode 100644 index 0000000000..dfd39de2f3 --- /dev/null +++ b/data/core.telegram.org/type/messages.SentEncryptedMessage @@ -0,0 +1,177 @@ + + + + + Messages.SentEncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.SentEncryptedMessage

+ +

Contains info on message sent to an encrypted chat.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+
+---functions---
+
+messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
+messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.sentEncryptedMessageMessage without file attachemts sent to an encrypted file.
messages.sentEncryptedFileMessage with a file enclosure sent to a protected chat
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.SentMessage b/data/core.telegram.org/type/messages.SentMessage new file mode 100644 index 0000000000..485855df94 --- /dev/null +++ b/data/core.telegram.org/type/messages.SentMessage @@ -0,0 +1,128 @@ + + + + + messages.SentMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.SentMessage

+ +

Info on a successfully sent message.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.SponsoredMessages b/data/core.telegram.org/type/messages.SponsoredMessages new file mode 100644 index 0000000000..f4ee16bf07 --- /dev/null +++ b/data/core.telegram.org/type/messages.SponsoredMessages @@ -0,0 +1,166 @@ + + + + + messages.SponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.SponsoredMessages

+ +

A set of sponsored messages associated with a channel

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+
+---functions---
+
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.sponsoredMessagesA set of sponsored messages associated with a channel
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getSponsoredMessagesGet a list of sponsored messages
+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.StatedMessage b/data/core.telegram.org/type/messages.StatedMessage new file mode 100644 index 0000000000..a133d679e0 --- /dev/null +++ b/data/core.telegram.org/type/messages.StatedMessage @@ -0,0 +1,128 @@ + + + + + messages.StatedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.StatedMessage

+ +

Object contains info on one message with auxiliary data and data on the current state of updates.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.StatedMessages b/data/core.telegram.org/type/messages.StatedMessages new file mode 100644 index 0000000000..1943721b20 --- /dev/null +++ b/data/core.telegram.org/type/messages.StatedMessages @@ -0,0 +1,128 @@ + + + + + messages.StatedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.StatedMessages

+ +

Object contains info on the list of messages with auxiliary data and data on current state of updates.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.StickerSet b/data/core.telegram.org/type/messages.StickerSet new file mode 100644 index 0000000000..88abddd05a --- /dev/null +++ b/data/core.telegram.org/type/messages.StickerSet @@ -0,0 +1,188 @@ + + + + + Messages.StickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.StickerSet

+ +

Stickerset

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+---functions---
+
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+
+stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
+stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
+stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
+stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.stickerSetStickerset and stickers inside it
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getStickerSetGet info about a stickerset
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.setStickerSetThumbSet stickerset thumbnail
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.StickerSetInstallResult b/data/core.telegram.org/type/messages.StickerSetInstallResult new file mode 100644 index 0000000000..027c42e510 --- /dev/null +++ b/data/core.telegram.org/type/messages.StickerSetInstallResult @@ -0,0 +1,167 @@ + + + + + Messages.StickerSetInstallResult + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.StickerSetInstallResult

+ +

Result of stickerset installation process

+

+ +
+
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
+messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
+
+---functions---
+
+messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.stickerSetInstallResultSuccessThe stickerset was installed successfully
messages.stickerSetInstallResultArchiveThe stickerset was installed, but since there are too many stickersets some were archived
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.installStickerSetInstall a stickerset
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.Stickers b/data/core.telegram.org/type/messages.Stickers new file mode 100644 index 0000000000..c0b1c1f658 --- /dev/null +++ b/data/core.telegram.org/type/messages.Stickers @@ -0,0 +1,167 @@ + + + + + Messages.Stickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.Stickers

+ +

Stickers

+

+ +
+
messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
+
+---functions---
+
+messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.stickersNotModifiedNo new stickers were found for the given query
messages.stickersFound stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getStickersGet stickers by emoji
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.VotesList b/data/core.telegram.org/type/messages.VotesList new file mode 100644 index 0000000000..ad699b77ee --- /dev/null +++ b/data/core.telegram.org/type/messages.VotesList @@ -0,0 +1,162 @@ + + + + + messages.VotesList + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.VotesList

+ +

How users voted in a poll

+

+ +
+
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
+
+---functions---
+
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.votesListHow users voted in a poll
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getPollVotesGet poll results for non-anonymous polls
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/payments.BankCardData b/data/core.telegram.org/type/payments.BankCardData new file mode 100644 index 0000000000..6268d3ffbb --- /dev/null +++ b/data/core.telegram.org/type/payments.BankCardData @@ -0,0 +1,162 @@ + + + + + payments.BankCardData + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.BankCardData

+ +

Credit card info, provided by the card's bank(s)

+

+ +
+
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
+
+---functions---
+
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.bankCardDataCredit card info, provided by the card's bank(s)
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getBankCardDataGet info about a credit card
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/payments.PaymentForm b/data/core.telegram.org/type/payments.PaymentForm new file mode 100644 index 0000000000..9306c2e712 --- /dev/null +++ b/data/core.telegram.org/type/payments.PaymentForm @@ -0,0 +1,162 @@ + + + + + Payments.PaymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.PaymentForm

+ +

Payment form

+

+ +
+
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+
+---functions---
+
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.paymentFormPayment form
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getPaymentFormGet a payment form
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/payments.PaymentReceipt b/data/core.telegram.org/type/payments.PaymentReceipt new file mode 100644 index 0000000000..9e1b997c17 --- /dev/null +++ b/data/core.telegram.org/type/payments.PaymentReceipt @@ -0,0 +1,162 @@ + + + + + Payments.PaymentReceipt + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.PaymentReceipt

+ +

Payment receipt

+

+ +
+
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+
+---functions---
+
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.paymentReceiptReceipt
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getPaymentReceiptGet payment receipt
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/payments.PaymentResult b/data/core.telegram.org/type/payments.PaymentResult new file mode 100644 index 0000000000..35a3f18083 --- /dev/null +++ b/data/core.telegram.org/type/payments.PaymentResult @@ -0,0 +1,167 @@ + + + + + Payments.PaymentResult + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.PaymentResult

+ +

Payment result

+

+ +
+
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
+payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
+
+---functions---
+
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
payments.paymentResultPayment result
payments.paymentVerificationNeededPayment was not successful, additional verification is needed
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.sendPaymentFormSend compiled payment form
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/payments.SavedInfo b/data/core.telegram.org/type/payments.SavedInfo new file mode 100644 index 0000000000..878a4c65fd --- /dev/null +++ b/data/core.telegram.org/type/payments.SavedInfo @@ -0,0 +1,162 @@ + + + + + Payments.SavedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.SavedInfo

+ +

Saved payment info

+

+ +
+
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
+
+---functions---
+
+payments.getSavedInfo#227d824b = payments.SavedInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.savedInfoSaved server-side order information
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getSavedInfoGet saved payment information
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/payments.ValidatedRequestedInfo b/data/core.telegram.org/type/payments.ValidatedRequestedInfo new file mode 100644 index 0000000000..499f1e45a1 --- /dev/null +++ b/data/core.telegram.org/type/payments.ValidatedRequestedInfo @@ -0,0 +1,162 @@ + + + + + Payments.ValidatedRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.ValidatedRequestedInfo

+ +

Validated requested info

+

+ +
+
payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
+
+---functions---
+
+payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.validatedRequestedInfoValidated user-provided info
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.validateRequestedInfoSubmit requested order information for validation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/phone.ExportedGroupCallInvite b/data/core.telegram.org/type/phone.ExportedGroupCallInvite new file mode 100644 index 0000000000..a7b6c923fd --- /dev/null +++ b/data/core.telegram.org/type/phone.ExportedGroupCallInvite @@ -0,0 +1,162 @@ + + + + + phone.ExportedGroupCallInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.ExportedGroupCallInvite

+ +

An exported group call invitation.

+

+ +
+
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
+
+---functions---
+
+phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.exportedGroupCallInviteAn invite to a group call or livestream
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/phone.GroupCall b/data/core.telegram.org/type/phone.GroupCall new file mode 100644 index 0000000000..12704f8752 --- /dev/null +++ b/data/core.telegram.org/type/phone.GroupCall @@ -0,0 +1,162 @@ + + + + + phone.GroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.GroupCall

+ +

Contains info about a group call, and partial info about its participants.

+

+ +
+
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
+
+---functions---
+
+phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.groupCallContains info about a group call, and partial info about its participants.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.getGroupCallGet info about a group call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/phone.GroupParticipants b/data/core.telegram.org/type/phone.GroupParticipants new file mode 100644 index 0000000000..d1e3205fc7 --- /dev/null +++ b/data/core.telegram.org/type/phone.GroupParticipants @@ -0,0 +1,162 @@ + + + + + phone.GroupParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.GroupParticipants

+ +

Info about the participants of a group call or livestream

+

+ +
+
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
+
+---functions---
+
+phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.groupParticipantsInfo about the participants of a group call or livestream
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.getGroupParticipantsGet group call participants
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/phone.JoinAsPeers b/data/core.telegram.org/type/phone.JoinAsPeers new file mode 100644 index 0000000000..fb077eb86c --- /dev/null +++ b/data/core.telegram.org/type/phone.JoinAsPeers @@ -0,0 +1,162 @@ + + + + + phone.JoinAsPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.JoinAsPeers

+ +

A list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+

+ +
+
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+
+---functions---
+
+phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.joinAsPeersA list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.getGroupCallJoinAsGet a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/phone.PhoneCall b/data/core.telegram.org/type/phone.PhoneCall new file mode 100644 index 0000000000..c214b95a23 --- /dev/null +++ b/data/core.telegram.org/type/phone.PhoneCall @@ -0,0 +1,172 @@ + + + + + Phone.PhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

Phone.PhoneCall

+ +

Phone call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+
+---functions---
+
+phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.phoneCallA VoIP phone call
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
phone.requestCallStart a telegram phone call
phone.acceptCallAccept incoming call
phone.confirmCallComplete phone call E2E encryption key exchange »
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/photos.Photo b/data/core.telegram.org/type/photos.Photo new file mode 100644 index 0000000000..e849b14b6a --- /dev/null +++ b/data/core.telegram.org/type/photos.Photo @@ -0,0 +1,167 @@ + + + + + photos.Photo + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.Photo

+ +

Photo with auxiliary data.

+

+ +
+
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+
+---functions---
+
+photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
+photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
photos.photoPhoto with auxiliary data.
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
photos.updateProfilePhotoInstalls a previously uploaded photo as a profile photo.
photos.uploadProfilePhotoUpdates current user profile photo.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/photos.Photos b/data/core.telegram.org/type/photos.Photos new file mode 100644 index 0000000000..9647b8ce0f --- /dev/null +++ b/data/core.telegram.org/type/photos.Photos @@ -0,0 +1,167 @@ + + + + + photos.Photos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.Photos

+ +

Object contains list of photos with auxiliary data.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+
+---functions---
+
+photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
photos.photosFull list of photos with auxiliary data.
photos.photosSliceIncomplete list of photos with auxiliary data.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
photos.getUserPhotosReturns the list of user photos.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/stats.BroadcastStats b/data/core.telegram.org/type/stats.BroadcastStats new file mode 100644 index 0000000000..0b6f833163 --- /dev/null +++ b/data/core.telegram.org/type/stats.BroadcastStats @@ -0,0 +1,162 @@ + + + + + Stats.BroadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

Stats.BroadcastStats

+ +

Channel statistics

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+
+---functions---
+
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stats.broadcastStatsChannel statistics
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.getBroadcastStatsGet channel statistics
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/stats.MegagroupStats b/data/core.telegram.org/type/stats.MegagroupStats new file mode 100644 index 0000000000..e109a88bee --- /dev/null +++ b/data/core.telegram.org/type/stats.MegagroupStats @@ -0,0 +1,162 @@ + + + + + stats.MegagroupStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.MegagroupStats

+ +

Supergroup statistics

+

+ +
+
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
+
+---functions---
+
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stats.megagroupStatsSupergroup statistics
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.getMegagroupStatsGet supergroup statistics
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/stats.MessageStats b/data/core.telegram.org/type/stats.MessageStats new file mode 100644 index 0000000000..454c91154a --- /dev/null +++ b/data/core.telegram.org/type/stats.MessageStats @@ -0,0 +1,162 @@ + + + + + stats.MessageStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.MessageStats

+ +

Message statistics

+

+ +
+
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
+
+---functions---
+
+stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stats.messageStatsMessage statistics
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.getMessageStatsGet message statistics
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/stickers.SuggestedShortName b/data/core.telegram.org/type/stickers.SuggestedShortName new file mode 100644 index 0000000000..694c2ba182 --- /dev/null +++ b/data/core.telegram.org/type/stickers.SuggestedShortName @@ -0,0 +1,162 @@ + + + + + stickers.SuggestedShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.SuggestedShortName

+ +

A suggested short name for the specified stickerpack

+

+ +
+
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
+
+---functions---
+
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stickers.suggestedShortNameA suggested short name for a stickerpack
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stickers.suggestShortNameSuggests a short name for a given stickerpack name
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/storage.FileType b/data/core.telegram.org/type/storage.FileType new file mode 100644 index 0000000000..10f85871df --- /dev/null +++ b/data/core.telegram.org/type/storage.FileType @@ -0,0 +1,188 @@ + + + + + storage.FileType + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.FileType

+ +

Object describes the file type.

+

+ +
+
storage.fileUnknown#aa963b05 = storage.FileType;
+storage.filePartial#40bc6f52 = storage.FileType;
+storage.fileJpeg#7efe0e = storage.FileType;
+storage.fileGif#cae1aadf = storage.FileType;
+storage.filePng#a4f63c0 = storage.FileType;
+storage.filePdf#ae1e508d = storage.FileType;
+storage.fileMp3#528a0677 = storage.FileType;
+storage.fileMov#4b09ebbc = storage.FileType;
+storage.fileMp4#b3cea0e4 = storage.FileType;
+storage.fileWebp#1081464c = storage.FileType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
storage.fileUnknownUnknown type.
storage.filePartialPart of a bigger file.
storage.fileJpegJPEG image. MIME type: image/jpeg.
storage.fileGifGIF image. MIME type: image/gif.
storage.filePngPNG image. MIME type: image/png.
storage.filePdfPDF document image. MIME type: application/pdf.
storage.fileMp3Mp3 audio. MIME type: audio/mpeg.
storage.fileMovQuicktime video. MIME type: video/quicktime.
storage.fileMp4MPEG-4 video. MIME type: video/mp4.
storage.fileWebpWEBP image. MIME type: image/webp.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/string.html b/data/core.telegram.org/type/string.html new file mode 100644 index 0000000000..ad86e71f6b --- /dev/null +++ b/data/core.telegram.org/type/string.html @@ -0,0 +1,126 @@ + + + + + string + + + + + + + + + + + + + +
+ +
+
+
+ +

string

+ +

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

+

Further details on basic types»

+

Related pages

+

bytes

+

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

+

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/updates.ChannelDifference b/data/core.telegram.org/type/updates.ChannelDifference new file mode 100644 index 0000000000..59315ec131 --- /dev/null +++ b/data/core.telegram.org/type/updates.ChannelDifference @@ -0,0 +1,172 @@ + + + + + updates.ChannelDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.ChannelDifference

+ +

Contains the difference (new messages) between our local channel state and the remote state

+

+ +
+
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
+updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+
+---functions---
+
+updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updates.channelDifferenceEmptyThere are no new updates
updates.channelDifferenceTooLongThe provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoother for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
updates.channelDifferenceThe new updates
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/updates.Difference b/data/core.telegram.org/type/updates.Difference new file mode 100644 index 0000000000..df743e954b --- /dev/null +++ b/data/core.telegram.org/type/updates.Difference @@ -0,0 +1,177 @@ + + + + + updates.Difference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.Difference

+ +

Occurred changes.

+

+ +
+
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
+updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
+updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
+updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
+
+---functions---
+
+updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updates.differenceEmptyNo events.
updates.differenceFull list of occurred events.
updates.differenceSliceIncomplete list of occurred events.
updates.differenceTooLongThe difference is too long, and the specified state must be used to refetch updates.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
updates.getDifferenceGet new updates.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/updates.State b/data/core.telegram.org/type/updates.State new file mode 100644 index 0000000000..ab92b162ad --- /dev/null +++ b/data/core.telegram.org/type/updates.State @@ -0,0 +1,162 @@ + + + + + updates.State + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.State

+ +

Object contains info on state for further updates.

+

+ +
+
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
+
+---functions---
+
+updates.getState#edd4882a = updates.State;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
updates.stateUpdates state.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
updates.getStateReturns a current state of updates.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/upload.CdnFile b/data/core.telegram.org/type/upload.CdnFile new file mode 100644 index 0000000000..0c1b0cbfdf --- /dev/null +++ b/data/core.telegram.org/type/upload.CdnFile @@ -0,0 +1,167 @@ + + + + + upload.CdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.CdnFile

+ +

Represents the download status of a CDN file

+

+ +
+
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+
+---functions---
+
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
upload.cdnFileReuploadNeededThe file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.
upload.cdnFileRepresent a chunk of a CDN file.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
upload.getCdnFileDownload a CDN file.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/upload.File b/data/core.telegram.org/type/upload.File new file mode 100644 index 0000000000..8a195440cf --- /dev/null +++ b/data/core.telegram.org/type/upload.File @@ -0,0 +1,167 @@ + + + + + upload.File + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.File

+ +

Contains info on file.

+

+ +
+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+---functions---
+
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
upload.fileFile content.
upload.fileCdnRedirectThe file must be downloaded from a CDN DC.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
upload.getFileReturns content of a whole file or its part.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/upload.WebFile b/data/core.telegram.org/type/upload.WebFile new file mode 100644 index 0000000000..2e1bcb3ec0 --- /dev/null +++ b/data/core.telegram.org/type/upload.WebFile @@ -0,0 +1,162 @@ + + + + + Upload.WebFile + + + + + + + + + + + + + +
+ +
+
+
+ +

Upload.WebFile

+ +

Remote file

+

+ +
+
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
+
+---functions---
+
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
upload.webFileRepresents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/video_stickers.html b/data/core.telegram.org/video_stickers.html new file mode 100644 index 0000000000..abf48687bc --- /dev/null +++ b/data/core.telegram.org/video_stickers.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+
+

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/widgets.html b/data/core.telegram.org/widgets.html new file mode 100644 index 0000000000..8099284b07 --- /dev/null +++ b/data/core.telegram.org/widgets.html @@ -0,0 +1,141 @@ + + + + + Telegram Widgets + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram Widgets

+ +

Telegram widgets offer a quick way to add a sharing button to your pages, embed posts from public channels or groups. Widgets can also help your users log in with Telegram or view Telegram Discussions on your website.

+
+
+
+ + +
+
+ + +
+
+ + +
+
+ + +
+
+
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/widgets/discussion.html b/data/core.telegram.org/widgets/discussion.html new file mode 100644 index 0000000000..01745f0f3c --- /dev/null +++ b/data/core.telegram.org/widgets/discussion.html @@ -0,0 +1,226 @@ + + + + + Discussion Widget + + + + + + + + + + + + + + + +
+ +
+
+
+ +

Discussion Widget

+ +

You can embed discussions from any public channel on your website. You only need a link to a post with comments to embed it together with all discussion.

+

If you have a website with articles and a telegram channel where you post links to these articles, you can use this widget to show discussions from that channel on your website. In this case you only need a link to the channel. Discussions will be available on your website as soon as you post a link into the channel. For this to work, you should add the <link rel="canonical" href="%page_url%"> tag to the page header where %page_url% is the canonical URL of the current page.

+

Configure widget

+

You can choose options for your widget using the form below.

+

+
+ +
+
+ +
+ +
+
+
+ +
+ +
+
+ +
+
+
+ +
+
+ +
+
+
+
+ +
+ +
+
+ + + + + + + +
+ + +
+
+ +
+ +
+ +
Make sure you have a <link rel="canonical" href="%page_url%"> tag in the page header with the canonical url of the current page.
+
+
+ +
+
+
+
+
+

+

Basic comments

+

If you're looking to simply add Telegram comments to pages on your website, without linking them with a channel, you can use our basic comments solution.

+
+ +
+ +
+
+ +
+ + + + + + + + + + diff --git a/data/core.telegram.org/widgets/login.html b/data/core.telegram.org/widgets/login.html new file mode 100644 index 0000000000..67d03f408b --- /dev/null +++ b/data/core.telegram.org/widgets/login.html @@ -0,0 +1,404 @@ + + + + + Telegram Login Widget + + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram Login Widget

+ +
+

The Telegram login widget is a simple way to authorize users on your website.
Check out this post for a general overview of the widget.

+
+

Setting up a bot

+

To use the login widget, you'll need a Telegram bot.

+

We strongly recommend that the profile picture of the bot you use for authorization corresponds with your website‘s logo, and that the bot’s name reflects that connection.

+

Users will see this message when they log into your website:

+
+ +
+ +

It is more likely that users will log in if your bot has a name and logo they expect to see.

+

Linking your domain to the bot

+

Once you have chosen a bot, send the /setdomain command to @Botfather to link your website's domain to the bot. Then configure your widget below and embed the code on your website.

+

Widget configuration

+

+
+ +
+
+
+ +
+ +
+ + +
+ Log in below to load your bots with linked domains +
+
+ +
+ +
+ + + +
+
+ +
+
+ +
+ +
+ + +
+
+ +
+ +
+ + +
+
+ +
+ +
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+
+

+

Receiving authorization data

+

After a successful authorization, the widget can return data in two ways:

+
    +
  • by redirecting the user to the URL specified in the data-auth-url attribute with the following parameters: id, first_name, last_name, username, photo_url, auth_date and hash;
  • +
  • by calling the callback function data-onauth with the JSON-object containing id, first_name, last_name, username, photo_url, auth_date and hash fields.
  • +
+

Checking authorization

+

You can verify the authentication and the integrity of the data received by comparing the received hash parameter with the hexadecimal representation of the HMAC-SHA-256 signature of the data-check-string with the SHA256 hash of the bot's token used as a secret key.

+

Data-check-string is a concatenation of all received fields, sorted in alphabetical order, in the format key=<value> with a line feed character ('\n', 0x0A) used as separator – e.g., 'auth_date=<auth_date>\nfirst_name=<first_name>\nid=<id>\nusername=<username>'.

+

The full check might look like:

+
data_check_string = ...
+secret_key = SHA256(<bot_token>)
+if (hex(HMAC_SHA256(data_check_string, secret_key)) == hash) {
+  // data is from Telegram
+}
+

To prevent the use of outdated data, you can additionally check the auth_date field, which contains a Unix timestamp when the authentication was received.

+

Sample implementation

+

You can find sample PHP code for checking authorization and receiving data about a logged in user on this page.

+
+ +
+ +
+
+ +
+ + + + + + + + + diff --git a/data/core.telegram.org/widgets/post.html b/data/core.telegram.org/widgets/post.html new file mode 100644 index 0000000000..a5a36f8a8e --- /dev/null +++ b/data/core.telegram.org/widgets/post.html @@ -0,0 +1,240 @@ + + + + + Post Widget + + + + + + + + + + + + + + + +
+ +
+
+
+ +

Post Widget

+ +

You can embed messages from public groups and channels anywhere. Here’s what an embed of a Telegram message looks like when included on a web page:

+

+ +

+
+ +

To get the HTML-code for embedding a message, just open its t.me link (e.g., t.me/durov/43) in a web browser and click < > EMBED:

+
+ +
+ +

Configure widget

+

You can choose more options using the form below.

+

+
+ +
+
+ +
+ +
+
+
+ +
+ +
+
+ +
+
+
+
+ +
+ +
+ + + +
+
+ +
+ +
+
+ + + + + + + +
+ + +
+
+ +
+ +
+ +
+
+ +
+
+
+
+
+

+
+ +
+ +
+
+ +
+ + + + + + + + + + diff --git a/data/core.telegram.org/widgets/share.html b/data/core.telegram.org/widgets/share.html new file mode 100644 index 0000000000..0f1e2ca268 --- /dev/null +++ b/data/core.telegram.org/widgets/share.html @@ -0,0 +1,250 @@ + + + + + Sharing Button + + + + + + + + + + + + + + +
+ +
+
+
+ +

Sharing Button

+ +

A Telegram Sharing Button is an easy way to let users forward content from your website or app to their friends, Channels or Saved Messages on Telegram.

+
+ TITLE +
+ +

When a user presses the button, Telegram asks them to choose a chat, group or channel where your link will be shared. You can also add some text that describes the link – the user will be able to edit it before sending the message.

+
+ TITLE +
+ +
+

Check out posts on the Telegram Blog for working examples of sharing buttons.

+
+

Adding Telegram sharing buttons to your website

+

Widget Constructor

+

Use this constructor to get embeddable code for your website.

+


+ +

+
+ +
+
+ +
+ +
+
+
+ +
+ +
+
+ +
+
+
+
+ +
+ +
+ + +
+
+ +
+ +
+ + +
+
+ +
+ +
+ +
+
+ +
+
+
+
+
+

+

Custom buttons

+

Feel free to create your own custom UI for the button. The only thing you need to make it work is to point the user to this URL on click:

+
https://t.me/share/url?url={url}&text={text}
+

where {url} is the URL the user will be sharing and {text} is an optional description that will be included with the link. Both values should be URL-encoded.

+

Here is a sample code for PHP:

+
/**
+ * @param string $url Absolute URL to share, e.g. "https://example.com/path/to/article?with=params"
+ * @param string $text Optional comment to share URL with, e.g. "Check out this article!"
+ * @return string Button HTML markup, feel free to modify to your taste
+ */
+function telegramForwardButton($url, $text = '') {
+  $share_url = 'https://t.me/share/url?url='.rawurlencode($url).'&text='.rawurlencode($text);
+  return "<a href=\"{$share_url}\">Share</a>";
+}
+

You are welcome to use the Telegram Logos in your custom button design.

+

Integrations and libraries

+ +

If you have a library, plugin or integration script for Telegram sharing buttons, please contact @BotSupport and we'll add you to this list.

+
+ +
+ +
+
+ +
+ + + + + + + + + diff --git a/data/corefork.telegram.org.html b/data/corefork.telegram.org.html new file mode 100644 index 0000000000..a082817b82 --- /dev/null +++ b/data/corefork.telegram.org.html @@ -0,0 +1,253 @@ + + + + + Telegram APIs + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram APIs

+ +

We offer two kinds of APIs for developers. The Bot API allows you to easily create programs that use Telegram messages for an interface. The Telegram API and TDLib allow you to build your own customized Telegram clients. You are welcome to use both APIs free of charge.

+

You can also add Telegram Widgets to your website.

+

Designers are welcome to create Animated Stickers or Custom Themes for Telegram.

+
+

Bot API

+
+ +
+

This API allows you to connect bots to our system. Telegram Bots are special accounts that do not require an additional phone number to set up. These accounts serve as an interface for code running somewhere on your server.

+

To use this, you don't need to know anything about how our MTProto encryption protocol works — our intermediary server will handle all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API.

+
+

Learn more about the Bot API here »

+
+

Bot developers can also make use of our Payments API to accept payments from Telegram users around the world.

+
+

TDLib – build your own Telegram

+

Even if you're looking for maximum customization, you don't have to create your app from scratch. Try our Telegram Database Library (or simply TDLib), a tool for third-party developers that makes it easy to build fast, secure and feature-rich Telegram apps.

+

TDLib takes care of all network implementation details, encryption and local data storage, so that you can dedicate more time to design, responsive interfaces and beautiful animations.

+

TDLib supports all Telegram features and makes developing Telegram apps a breeze on any platform. It can be used on Android, iOS, Windows, macOS, Linux and virtually any other system. The library is open source and compatible with virtually any programming language.

+
+

Learn more about TDLib here »

+
+
+

Telegram API

+

This API allows you to build your own customized Telegram clients. It is 100% open for all developers who wish to create Telegram applications on our platform. Feel free to study the open source code of existing Telegram applications for examples of how things work here. Don't forget to register your application in our system.

+ +

Getting started

+

Creating an application

+

How to get your application identifier and create a new Telegram app.

+

User authorization

+

How to register a user's phone to start using the API.

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

QR code login

+

QR code login flow

+

Error handling

+

How to handle API return errors correctly.

+

Handling different data centers

+

How to connect to the closest DC access point for faster interaction with the API, and things to watch out for when developing a client.

+

Handling updates

+

How to subscribe to updates and handle them properly.

+

Handling PUSH-notifications

+

How to subscribe and handle them properly.

+

Channels, supergroups and groups

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

Calling methods

+

Additional options for calling methods.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

Pagination

+

How to fetch results from large lists of objects.

+

Client configuration

+

The MTProto API has multiple client configuration parameters that can be fetched with the appropriate methods.

+

Security

+

Secret chats, end-to-end encryption

+

End-to-end-encrypted messaging.

+

Security guidelines

+

Important checks required in your client application.

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

End-to-End Encryption in Voice and Video Calls

+

End-to-end-encrypted calls.

+

Optimization

+

Client optimization

+

Ways to boost API interactions.

+

API methods

+

Available method list

+

A list of available high-level methods.

+

API TL-schema, as JSON

+

Text and JSON-presentation of types and methods used in API.

+

Available layer list

+

A list of available schema versions.

+

Other articles

+

Working with bots, using the MTProto API

+

How to work with bots using the MTProto API.

+

Commands

+

Bots offer a set of commands that can be used by users in private, or in a chat.

+

Buttons

+

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

+

Inline queries

+

Users can interact with your bot via inline queries, straight from the text input field in any chat.

+

Games

+

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

+

Search & filters

+

Telegram allows applying detailed message filters while looking for messages in chats. +This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

+

Polls

+

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

+

Admin, banned and default rights for channels, supergroups and groups

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

Channel comments and message threads

+

Telegram allows commenting on a channel post or on a generic group message, thanks to message threads.

+

Admin log

+

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

Scheduled messages

+

Telegram allows scheduling messages.

+

Live geolocations

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+

Min constructors

+

Sometimes, user and channel constructors met in group chat updates may not contain full info about the user: how to handle such constructors.

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

Telegram Passport

+

How to work with Telegram Passport directly using the MTProto API.

+

Telegram Payments

+

How to work with Telegram Payments directly using the MTProto API.

+

Styled text with message entities

+

How to create styled text with message entities

+

Working with animated emojis

+

Graphical telegram clients should transform emojis into their respective animated version.

+

Working with animated dice

+

Telegram supports sending animated dice emojis.

+

Message drafts

+

How to handle message drafts

+

Folders

+

Working with folders

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+

Handling file references

+

How to handle file references.

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+

Web events

+

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api.html b/data/corefork.telegram.org/api.html new file mode 100644 index 0000000000..a082817b82 --- /dev/null +++ b/data/corefork.telegram.org/api.html @@ -0,0 +1,253 @@ + + + + + Telegram APIs + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram APIs

+ +

We offer two kinds of APIs for developers. The Bot API allows you to easily create programs that use Telegram messages for an interface. The Telegram API and TDLib allow you to build your own customized Telegram clients. You are welcome to use both APIs free of charge.

+

You can also add Telegram Widgets to your website.

+

Designers are welcome to create Animated Stickers or Custom Themes for Telegram.

+
+

Bot API

+
+ +
+

This API allows you to connect bots to our system. Telegram Bots are special accounts that do not require an additional phone number to set up. These accounts serve as an interface for code running somewhere on your server.

+

To use this, you don't need to know anything about how our MTProto encryption protocol works — our intermediary server will handle all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API.

+
+

Learn more about the Bot API here »

+
+

Bot developers can also make use of our Payments API to accept payments from Telegram users around the world.

+
+

TDLib – build your own Telegram

+

Even if you're looking for maximum customization, you don't have to create your app from scratch. Try our Telegram Database Library (or simply TDLib), a tool for third-party developers that makes it easy to build fast, secure and feature-rich Telegram apps.

+

TDLib takes care of all network implementation details, encryption and local data storage, so that you can dedicate more time to design, responsive interfaces and beautiful animations.

+

TDLib supports all Telegram features and makes developing Telegram apps a breeze on any platform. It can be used on Android, iOS, Windows, macOS, Linux and virtually any other system. The library is open source and compatible with virtually any programming language.

+
+

Learn more about TDLib here »

+
+
+

Telegram API

+

This API allows you to build your own customized Telegram clients. It is 100% open for all developers who wish to create Telegram applications on our platform. Feel free to study the open source code of existing Telegram applications for examples of how things work here. Don't forget to register your application in our system.

+ +

Getting started

+

Creating an application

+

How to get your application identifier and create a new Telegram app.

+

User authorization

+

How to register a user's phone to start using the API.

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

QR code login

+

QR code login flow

+

Error handling

+

How to handle API return errors correctly.

+

Handling different data centers

+

How to connect to the closest DC access point for faster interaction with the API, and things to watch out for when developing a client.

+

Handling updates

+

How to subscribe to updates and handle them properly.

+

Handling PUSH-notifications

+

How to subscribe and handle them properly.

+

Channels, supergroups and groups

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

Calling methods

+

Additional options for calling methods.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

Pagination

+

How to fetch results from large lists of objects.

+

Client configuration

+

The MTProto API has multiple client configuration parameters that can be fetched with the appropriate methods.

+

Security

+

Secret chats, end-to-end encryption

+

End-to-end-encrypted messaging.

+

Security guidelines

+

Important checks required in your client application.

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

End-to-End Encryption in Voice and Video Calls

+

End-to-end-encrypted calls.

+

Optimization

+

Client optimization

+

Ways to boost API interactions.

+

API methods

+

Available method list

+

A list of available high-level methods.

+

API TL-schema, as JSON

+

Text and JSON-presentation of types and methods used in API.

+

Available layer list

+

A list of available schema versions.

+

Other articles

+

Working with bots, using the MTProto API

+

How to work with bots using the MTProto API.

+

Commands

+

Bots offer a set of commands that can be used by users in private, or in a chat.

+

Buttons

+

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

+

Inline queries

+

Users can interact with your bot via inline queries, straight from the text input field in any chat.

+

Games

+

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

+

Search & filters

+

Telegram allows applying detailed message filters while looking for messages in chats. +This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

+

Polls

+

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

+

Admin, banned and default rights for channels, supergroups and groups

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

Channel comments and message threads

+

Telegram allows commenting on a channel post or on a generic group message, thanks to message threads.

+

Admin log

+

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

Scheduled messages

+

Telegram allows scheduling messages.

+

Live geolocations

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+

Min constructors

+

Sometimes, user and channel constructors met in group chat updates may not contain full info about the user: how to handle such constructors.

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

Telegram Passport

+

How to work with Telegram Passport directly using the MTProto API.

+

Telegram Payments

+

How to work with Telegram Payments directly using the MTProto API.

+

Styled text with message entities

+

How to create styled text with message entities

+

Working with animated emojis

+

Graphical telegram clients should transform emojis into their respective animated version.

+

Working with animated dice

+

Telegram supports sending animated dice emojis.

+

Message drafts

+

How to handle message drafts

+

Folders

+

Working with folders

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+

Handling file references

+

How to handle file references.

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+

Web events

+

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/account-deletion.html b/data/corefork.telegram.org/api/account-deletion.html new file mode 100644 index 0000000000..632a361da8 --- /dev/null +++ b/data/corefork.telegram.org/api/account-deletion.html @@ -0,0 +1,129 @@ + + + + + Account deletion + + + + + + + + + + + + + +
+ +
+
+
+ +

Account deletion

+ +

If the user has successfully provided the login code, but they forgot the 2FA password, the account should be reset: this can be done using account.deleteAccount.

+

If the account's 2FA password was modified more than 7 days ago and was active in the last 7 days, account deletion will be delayed for 7 days, and a service message will be sent to the user, containing a link in one of the following formats:

+
    +
  • https://telegram.me/confirmphone?phone=XXX&hash=YYYY
  • +
  • tg://confirmphone?phone=XXX&hash=YYYY
  • +
+

When clicked, account.sendConfirmPhoneCode must be called with the specified hash, using the account with the specified phone number. +This will send a phone number verification code to the phone number associated with the account. +The phone code settings are the same as for the login code, and auth.cancelCode with auth.resendCode can be used as well, to resend or cancel the phone code as for the login code.

+

Once the SMS code is received, the account.confirmPhone method will have to be called with the SMS code and the phone hash received from the account.sendConfirmPhoneCode method.

+

This will cancel deletion of the account and will log out the user that tried to reset it. +Otherwise, if the number isn't confirmed in 7 days, the account will be deleted and the user will be free to recreate it.

+

Related articles

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/animated-emojis.html b/data/corefork.telegram.org/api/animated-emojis.html new file mode 100644 index 0000000000..f4c1402574 --- /dev/null +++ b/data/corefork.telegram.org/api/animated-emojis.html @@ -0,0 +1,187 @@ + + + + + Animated Emojis + + + + + + + + + + + + + +
+ +
+
+
+ +

Animated Emojis

+ +

Graphical telegram clients should transform emojis into their respective animated version.

+
inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+---functions---
+
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+

On startup, clients should fetch the animated emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmoji to the stickerset field.
+The returned stickerset will contain a set of animated stickers, one for each of the supported emojis.

+

Clients should substitute messages containing only one instance of one of the allowed emojis with the respective animated sticker.

+

Animated emojis should loop only once when first sent or received, or when clicked.
+For supported emojis, clients on both sides of private chats with users are supposed to show a reaction animation when any of the two users clicks on the animated emoji: click here for more info ».

+

For special dice emojis like 🎲, 🎯, or 🏀, clients are supposed to behave differently both when sending and receiving such emojis: click here for more info ».

+

Emojis with sounds

+

Certained animated emojis should play sound when clicked, as specified by server-side configuration.

+

The returned JSON object will contain the following map, with a list of file IDs to download:

+
    "emojies_sounds": {
+        "\ud83c\udf83": {
+            "id": "4956223179606458539",
+            "access_hash": "-2107001400913062971",
+            "file_reference_base64": "AF-4ApC7ukC0UWEPZN0TeSJURe7T"
+        },
+        "\u26b0": {
+            "id": "4956223179606458540",
+            "access_hash": "-1498869544183595185",
+            "file_reference_base64": "AF-4ApCLKMGt96WCvLm58kbqZHd3"
+        },
+        "\ud83e\udddf\u200d\u2642": {
+            "id": "4960929110848176331",
+            "access_hash": "3986395821757915468",
+            "file_reference_base64": "AF-4ApAedNln3IMEHH-SUQuH8L9g"
+        },
+    }
+

The file reference field should be base64-decoded before downloading the file.

+

Emoji reactions

+
inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
+
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
+
+updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
+
+---functions---
+
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+

On startup, clients should fetch the animated reaction emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmojiAnimations to the stickerset field.
+The returned stickerset will contain a set of animated emoji reactions, one or more for each of the supported emojis.
+If a set of reactions for the ❤ emoji is returned, the same reactions should also be assigned to the 🧡, 💛, 💚, 💙, 💜, 🖤, 🤍 and 🤎 emojis.

+

Clients on both sides of private chats with users should overlay one of the appropriate reaction animations over the animated sticker when any of the two users clicks on a supported animated emoji.
+The reaction animation for each separate tap should be chosen randomly from all the available reactions for a given emoji, and multiple taps should be aggregated and sent to the other user as follows:

+

At each tap, clients should store all occurred taps in a local list.
+After 1 second has elapsed with no more taps, the local list should be cleared and stored taps should be sent using messages.setTyping, passing a sendMessageEmojiInteraction constructor with the following fields:

+
    +
  • emoticon - The emoji we're reacting to
  • +
  • msg_id - Message ID of the animated emoji that was clicked
  • +
  • interaction - A JSON object with interaction info, containing the following keys:
      +
    • v - An integer indicating the object version, currently 1
    • +
    • a - An array of JSON objects, each containing the following keys:
        +
      • t - float, number of seconds that passed since the previous tap in the array, the first tap uses a value of 0.0.
      • +
      • i - integer, 1-based index of the randomly chosen animation for the tap (equivalent to the index of a specific emoji-related animation in stickerPack + 1).
      • +
      +
    • +
    +
  • +
+

1 second after the receiving user has seen the last reaction animation for a specific emoji, an acknowledgement must be sent using messages.setTyping, passing a sendMessageEmojiInteractionSeen with that emoji.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/auth.html b/data/corefork.telegram.org/api/auth.html new file mode 100644 index 0000000000..aee36a6995 --- /dev/null +++ b/data/corefork.telegram.org/api/auth.html @@ -0,0 +1,202 @@ + + + + + User Authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

User Authorization

+ +
+ +

Authorization is associated with a client’s encryption key identifier: auth_key_id. No additional parameters need to be passed into methods following authorization.

+

To log in as a bot, follow these instructions ».

+

Sending a verification code

+

Example implementations: telegram for android, tdlib.

+

To show a nicely formatted and validated phone number field, the help.countriesList constructor can be obtained using the help.getCountriesList method.
The help.countriesList config is then used as described here ».

+

Authorization requires that a text message containing an authorization code first be sent to the user’s phone.
This may be done using the auth.sendCode method.
The system will automatically choose how to send the authorization code; there are four possible ways the code can arrive:

+
    +
  • Telegram code
  • +
  • SMS code
  • +
  • Phone call: a synthesized voice will tell the user which verification code to input
  • +
  • Flash phone call: the code will be sent via a flash phone call, that will be closed immediately.
    In the last case, the phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern (see auth.sentCodeTypeFlashCall).
  • +
+

The auth.sendCode method also has parameters for enabling/disabling use of flash calls, and allows passing an SMS token that will be included in the sent SMS.
For example, the latter is required in newer versions of android, to use the android SMS receiver APIs.

+

The returned auth.SentCode object will contain multiple parameters:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
+

If the message takes too long (timeout seconds) to arrive at the phone, the auth.resendCode method may be invoked to resend a code of type next_type.
If the same happens again, you can use auth.resendCode with the next_type returned by the previous call to auth.resendCode.
To cancel the verification code use auth.cancelCode.

+

Sign in/sign up

+

When user enters verification code, the auth.signIn method must be used to validate it and possibly sign user in.

+

If the code was entered correctly, but the method returns auth.authorizationSignUpRequired, it means that account with this phone number doesn't exist yet: user needs to provide basic information, accept terms of service and then the new user registration method (auth.signUp) must be invoked.

+

2FA

+

When trying to sign in using auth.signIn, an error 400 SESSION_PASSWORD_NEEDED may be returned, if the user has two-factor authentication enabled.
In this case, instructions for SRP 2FA authentication must be followed.

+

To set up two-factor authorization on an already authorized account, follow the SRP 2FA authentication docs.

+

Test Accounts

+

Each phone number is limited to only a certain amount of logins per day (e.g. 5, but this is subject to change) after which the API will return a FLOOD error until the next day. This might not be enough for testing the implementation of User Authorization flows in client applications.

+

There are several reserved phone number prefixes for testing that your application handles redirects between DCs, sign up, sign in and 2FA flows correctly. These numbers are only available on Test DCs (their IP addresses for TCP transport are availble in API development tools panel after api_id was obtained, URI format for HTTPS/Websocket transport).

+

If you wish to emulate an application of a user associated with DC number X, it is sufficient to specify the phone number as 99966XYYYY, where YYYY are random numbers, when registering the user. A user like this would always get XXXXX as the login confirmation code (the DC number, repeated five times). Note that the value of X must be in the range of 1-3 because there are only 3 Test DCs. When the flood limit is reached for any particular test number, just choose another number (changing the YYYY random part).

+

Do not store any important or private information in the messages of such test accounts; anyone can make use of the simplified authorization mechanism – and we periodically wipe all information stored there.

+

Proceed with User Authorization flows in Production DCs only after you make sure everything works correctly on Test DCs first to avoid reaching flood limits.

+
+

To help you with working on production DCs, logins with the same phone number with which the api_id was registered have more generous flood limits.

+
+

We are authorized

+

As a result of authorization, the client key, auth_key_id, becomes associated with the user, and each subsequent API call with this key will be executed with that user’s identity. The authorization method itself returns the relevant user. It is best to immediately store the User ID locally in a binding with the key.

+

Only a small portion of the API methods are available to unauthorized users:

+ +

Other methods will result in an error: 401 UNAUTHORIZED.

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/bots.html b/data/corefork.telegram.org/api/bots.html new file mode 100644 index 0000000000..cacdbd775b --- /dev/null +++ b/data/corefork.telegram.org/api/bots.html @@ -0,0 +1,142 @@ + + + + + Bots + + + + + + + + + + + + + +
+ +
+
+
+ +

Bots

+ +
+ +

Working with bots, using the MTProto API.

+

See here for more info about bots.

+

Please note that you can also use the simplified HTTP Bot API to use bots, see here for more info ».

+

Login

+
---functions---
+
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
+

In order to login as a bot, instead of using the standard login code flow, simply provide the bot token generated by @botfather.
+You must still provide your API ID, as per user logins.

+

After successful authorization, you will be able to use most MTProto API methods, just as any normal user.
+Methods that can be called by bots will have a Bots can use this method notice.

+

Commands

+

Bots offer a set of commands that can be used by users in private, or in a chat.

+

Buttons

+

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

+

Inline queries

+

Users can interact with your bot via inline queries, straight from the text input field in any chat.

+

Games

+

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/bots/buttons.html b/data/corefork.telegram.org/api/bots/buttons.html new file mode 100644 index 0000000000..f96e195248 --- /dev/null +++ b/data/corefork.telegram.org/api/bots/buttons.html @@ -0,0 +1,242 @@ + + + + + Buttons + + + + + + + + + + + + + +
+ +
+
+
+ +

Buttons

+ +
+ +

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.
+This article describes the full button flow, using the MTProto API.

+

For a simplified description using the HTTP bot API, see here ».

+

Buttons

+
keyboardButton#a2fa4880 text:string = KeyboardButton;
+keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
+keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
+keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
+keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
+keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
+keyboardButtonGame#50f41ccf text:string = KeyboardButton;
+keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
+inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
+keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
+
+keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
+
+replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
+replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
+replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+---functions---
+
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

Bots can attach a ReplyMarkup constructor to outgoing messages, to attach an inline keyboard or a custom reply keyboard:

+ +

Pressing buttons

+
keyboardButton#a2fa4880 text:string = KeyboardButton;
+keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
+keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
+keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
+keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
+keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
+keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
+keyboardButtonGame#50f41ccf text:string = KeyboardButton;
+keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
+
+// Used by bots to send a keyboardButtonUrlAuth
+inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
+
+keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
+

Both reply and inline keyboards are composed of a vector of rows, each row containing a vector of buttons, for each column.
+Each row can have a different number of columns, and user clients should properly handle clicking buttons of every type.

+

Buttons available only in reply keyboards:

+ +

Buttons available only in inline keyboards:

+ +

Callback queries

+

keyboardButtonCallback buttons can be used to send the specified data payload back to the bot, when they are clicked.
+Additionally, a bot can verify a user's identity by requiring they verify their 2FA password with SRP.

+

Sending a callback query

+
keyboardButtonGame#50f41ccf text:string = KeyboardButton;
+keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
+
+messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+
+---functions---
+
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;
+

When the user clicks on a keyboardButtonCallback in a message sent by a bot, or generated by an inline query, messages.getBotCallbackAnswer should be called, passing the peer and ID of the message.
+The same should happen when clicking on keyboardButtonGame buttons, with the difference that the game flag must be set instead of the data parameter.

+

Make sure to properly handle bot timeouts in the form of BOT_RESPONSE_TIMEOUT RPC errors, as the bot may be offline and unable to reply.

+

The returned messages.botCallbackAnswer constructor contains:

+
    +
  • message if specified, a message that should be shown in a non-blocking toast notification
  • +
  • alert indicates whether the message should be shown as a dismissable prompt, instead of a simple toast notification
  • +
  • has_url Whether an URL is present
  • +
  • url if specified, the client should open the URL, without showing a confirmation prompt.
    This is safe and allowed, because here, bots can only return:
      +
    • URLs to themselves with added query parameters (t.me/bot?start=aaa)
    • +
    • URLs to a valid game, if the bot has manually configured games, and the clicked button was a keyboardButtonGame.
    • +
    +
  • +
  • native_ui whether to open game URLs in a WebView or in native UI.
  • +
  • cache_time specifies for how long should this answer be cached, client-side
  • +
+
SRP verification
+

If the requires_password flag is set, the SRP 2FA payload must also be generated and attached to the query, to verify the identity of the user.

+

Note that the bot will NOT be able to access your password or the SRP payload.

+

The SRP payload will be processed exclusively on the Telegram's servers, simply returning an RPC error without passing the query to the bot if the verification fails.
+This is just a way of verifying the identity of the user, mainly used by the official @botfather bot to allow securely transferring the ownership of a bot to another user.

+

Answering a callback query

+
updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+
+updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+
+---functions---
+
+messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
+

After the user invokes messages.getBotCallbackAnswer, an updateBotCallbackQuery or updateInlineBotCallbackQuery is generated and sent to the bot, depending on whether the query originated from a normal message sent by the bot, or from a message sent from an inline query.

+

Either way, bots must reply to the query as quickly as possible using messages.setBotCallbackAnswer:

+ +

If a game_short_name is present in the update, the bot should return the URL of the game with the specified name.
+The messages.setBotCallbackAnswer method must be called anyway, even if no message or url is returned, to avoid timeouts on the client.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/bots/commands.html b/data/corefork.telegram.org/api/bots/commands.html new file mode 100644 index 0000000000..4a0e8fd99d --- /dev/null +++ b/data/corefork.telegram.org/api/bots/commands.html @@ -0,0 +1,140 @@ + + + + + Commands + + + + + + + + + + + + + +
+ +
+
+
+ +

Commands

+ +
+ +

Bots offer a set of commands that can be used by users in private, or in a chat.

+

For a simplified description using the HTTP bot API, see here ».

+

Getting commands

+
botCommand#c27ac8c7 command:string description:string = BotCommand;
+
+botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;
+
+channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
+userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
+
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+

The botInfo constructors contained in the userFull, chatFull, channelFull contain a list of commands, and for groups, the ID and a description of each bot.

+

In graphical clients, when users begin a message with a /, a list of commands supported by all bots present in the current chat should be shown; the same should be done for one-to-one chats with the bot itself.

+

If the command list of a bot changes, the bot_info_version contained in the user constructor received in updates will change; this indicates that the client should refetch full bot information using users.getFullUser.

+

Setting commands

+
botCommand#c27ac8c7 command:string description:string = BotCommand;
+
+---functions---
+
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
+

The command list can be changed by the owner of the bot through @botfather, but bots can also change their own command list by invoking bots.setBotCommands.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/bots/games.html b/data/corefork.telegram.org/api/bots/games.html new file mode 100644 index 0000000000..cbda184569 --- /dev/null +++ b/data/corefork.telegram.org/api/bots/games.html @@ -0,0 +1,171 @@ + + + + + Games + + + + + + + + + + + + + +
+ +
+
+
+ +

Games

+ +
+ +

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats.

+

Sending a game

+
inputUserSelf#f7c1b13f = InputUser;
+
+inputGameID#32c3e77 id:long access_hash:long = InputGame;
+inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;
+
+inputMediaGame#d33f43f3 id:InputGame = InputMedia;
+
+game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+
+---functions---
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

Bots can directly send a game using messages.sendMedia, providing:

+
    +
  • The bot's shortname obtained from @BotFather to inputGameShortName.short_name
  • +
  • The current bot's info to inputGameShortName.bot_id
  • +
+

The sent message will contain a messageMediaGame with a game, that can then be used by users to forward the game using sendMedia with inputGameID.

+

Starting a game

+

Games are started clicking on the button, which triggers an callback query that returns the game URL, for more info see here &raquo.
+The game should then be opened in a WebView or in native UI (specified by the native_ui flag), exposing the appropriate HTML5 APIs in order to receive various JS game events directly from the code of the game, as described here ».

+

Setting highscores

+
---functions---
+
+messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
+

Games are supposed to report back to the MTProto API every time the user looses a game with a new highscore.
+Since games run in the browser, they cannot directly report data to the API using the bot token, which must be kept secret.
+Instead, they should send highscores to an intermediate server, that will then report scores using messages.setGameScore or messages.setInlineGameScore, depending on the source of the game.

+
    +
  • The edit_message flag should be set if the game message should be automatically edited to include the current scoreboard
  • +
  • The force flag should be set if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters.
  • +
+

Getting highscores

+
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
+
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
+
+highScore#73a379eb pos:int user_id:long score:int = HighScore;
+
+messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+
+---functions---
+
+messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;
+

Every time a highscore is reached, and the edit_message flag is set when reporting the score, a messageService with a messageActionGameScore is generated, indicating that the highscore of a certain game has changed, thanks to a certain user_id.
+Our own current position of the scoreboard is also reported as pos.

+

When receiving such an update, graphical clients should refetch the scoreboard using messages.getGameHighScores or messages.getInlineGameHighScores.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/bots/inline.html b/data/corefork.telegram.org/api/bots/inline.html new file mode 100644 index 0000000000..8daa00d149 --- /dev/null +++ b/data/corefork.telegram.org/api/bots/inline.html @@ -0,0 +1,215 @@ + + + + + Inline + + + + + + + + + + + + + +
+ +
+
+
+
+

Inline

+ +
+ +

Users can interact with your bot via inline queries, straight from the text input field in any chat.
+This article describes the full inline bot flow, using the MTProto API.

+

For a simplified description using the HTTP bot API, see here ».

+

Making an inline query

+
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
+
+---functions---
+
+messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;
+

When, in a graphical client, the user starts a message with an @, clients should:

+
    +
  • Use the cached top peer rating for inline bots to show a list of frequently used inline bots.
  • +
  • If the user chooses a bot from the recent bot list or:
  • +
  • Finishes typing a full username followed by a whitespace, and if the username resolves to a valid bot
  • +
  • messages.getInlineBotResults is called, with the following parameters:
      +
    • bot - The bot peer
    • +
    • peer - The chat where the user made the query
    • +
    • geo_point - The user's current geolocation, if the bot requires location-based inline results (the bot_inline_geo flag of the bot's user constructor will be set)
    • +
    • query - What the user typed after the bot's username
    • +
    • offset - If the user scrolls past the first len(results) results, and next_offset field is set, the inline query should be repeated with this offset.
    • +
    +
  • +
+

Answering to an inline query

+
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+
+inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;
+
+updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
+
+---functions---
+
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
+

Bots can answer to incoming updateBotInlineQuery updates using messages.setInlineBotResults.
+Just like its bot API counterpart, the method can be used to send a set of inline results to the user; see the constructor page for more info on the MTProto method parameters ».

+

In general, the method accepts a vector of InputBotInlineResult constructors, that when chosen, generates a message with optionally attached media, and even inline buttons.

+

Sending the inline query result

+
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+
+botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
+botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;
+
+messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
+
+---functions---
+
+messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
+

The user client should display the results obtained during querying in a list, making sure to handle eventual bot timeouts in the form of a BOT_RESPONSE_TIMEOUT RPC error, by simply not displaying anything.

+

If the user then chooses a specific BotInlineResult, the messages.sendInlineBotResult method should be invoked, passing:

+
    +
  • The query_id from messages.botResults
  • +
  • The id of the chosen result
  • +
  • The peer where to send the chosen result
  • +
+

The resulting message will have the via_bot_id field set, to indicate that the result was generated by the bot that generated the inline result.
+Graphical clients should display the bot @username in the header of the message, allowing the user to click on it, automatically starting an inline query by inserting @username in the text bar.

+

Inline feedback

+
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
+
+updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
+

If feedback collection is enabled, the bot may receive an updateBotInlineSend when the user chooses and sends an inline result.

+

Even if the probability setting is set to 100%, not all inline results may be reported due to caching (see the cache_time parameter in Answering a callback query).
+Feedback collection can also create load issues for popular bots, so adjust the probability setting to a lower value in such cases.

+

Either way, feedback collection should only be used for statistical purposes rather than functional.

+

The updateBotInlineSend will contain:

+
    +
  • id - The ID of the chosen result
  • +
  • msg_id - The ID of the sent inline message
  • +
  • user_id - The ID of the user that chose the result
  • +
  • query - The query string that was used to obtain the result
  • +
  • geo - For bots requiring location-based inline results, the user's location
  • +
+

Editing sent inline messages

+
updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+
+inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
+
+---functions---
+
+messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
+

Sent inline messages can be edited by the bot, for example in response to a button press callback query.

+

Simply pass the inputBotInlineMessageID specified in the updateInlineBotCallbackQuery to messages.editInlineBotMessage along with the new message, making sure to send the query to the datacenter specified in inputBotInlineMessageID.dc_id.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/channel.html b/data/corefork.telegram.org/api/channel.html new file mode 100644 index 0000000000..dadc7ad4f6 --- /dev/null +++ b/data/corefork.telegram.org/api/channel.html @@ -0,0 +1,154 @@ + + + + + Channels + + + + + + + + + + + + + +
+ +
+
+
+ +

Channels

+ +
+ +

Channels, chats, supergroups & gigagroups

+

Channels are a tool for broadcasting your messages to large audiences. They can have an unlimited number of subscribers, they can be public with a permanent URL and each post in a channel has its own view counter.
+Technically, they are represented by channel constructors.

+

Supergroups are a powerful tool for building communities and can support up to 200,000 members each.
+Technically, supergroups are actually channels: they are represented by channel constructors, with the megagroup flag set to true.

+

Gigagroups are something inbetween a channel and a supergroup.
+An admin, when prompted by the API using suggestions », can convert a megagroup into a gigagroup using channels.convertToGigagroup (one way only).
+After that, only admins will be able to write in the group (like when send_messages rights are disabled for all group participants by default), but the participant limit is removed and the group can become much bigger than a supergroup (e.g. >200,000 currently).
+Also, one can't invite people into gigagroups and participants of voice chats in gigagroups are muted by default.

+

Channels and supergroups can be created using the channels.createChannel method, by setting the appropriate broadcast or megagroup flags.
+Supergroups can also be assigned a geo_point to become geochats.

+

In previous versions of telegram, only normal groups (represented by chat constructors) could be created using messages.createChat: these groups have fewer features, and can only have 200 members at max.

+

Migration

+

To upgrade a legacy group to a supergroup, messages.migrateChat can be used. +The chats field of the result will have two objects:

+
    +
  • A chat constructor with a migrated_to field, indicating the address of the new supergroup
  • +
  • The new channel megagroup constructor
  • +
+

When getting full info about the migrated channel, the channelFull object will have migrated_from_chat_id and migrated_from_max_id fields indicating the original ID of the chat, and the message ID in the original chat at which the group was migrated.

+

All users of the chat will receive an updateNewMessage from the old chat with a messageService containing a messageActionChatMigrateTo constructor.

+

All new messages have to be sent to the new supergroup.

+

When working with migrated groups clients need to handle loading of the message history (as well as search results et cetera) from both the legacy group and the new supergroup. This is done by merging the two messages lists (requested with different Peer values) client side.

+

Rights

+

Channels, legacy groups and supergroups allow setting granular permissions both for admins and specific users; channels, supergroups and legacy groups also allow setting global granular permissions for users.

+

For more info on how to set and modify rights, see here ».

+

Pinned messages

+

Telegram allows pinning multiple messages on top in a chat, group, supergroup or channel.

+

See here » for more info on pinning and unpinning messages.

+

Discussion

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

For more info on how to set a discussion group in channel, see here »

+

Recent actions

+

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

+

See here » for more info.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/config.html b/data/corefork.telegram.org/api/config.html new file mode 100644 index 0000000000..7cc87667f9 --- /dev/null +++ b/data/corefork.telegram.org/api/config.html @@ -0,0 +1,422 @@ + + + + + Client configuration + + + + + + + + + + + + + +
+ +
+
+
+ +

Client configuration

+ +
+ +

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+

MTProto configuration

+
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+
+---functions---
+
+help.getConfig#c4f9186b = Config;
+help.getNearestDc#1fb33026 = NearestDc;
+

The huge config constructor contains lots of useful information, from chat and message size limitations, to privacy settings, online status refresh interval and timeout, VoIP configuration, default inline bot usernames for GIF, image and venue lookup, and lots of other global and user-specific information, check out the constructor page for more information.

+

Client configuration

+
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
+
+jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+
+---functions---
+
+help.getAppConfig#98914110 = JSONValue;
+

The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.
+While help.getConfig returns MTProto-specific configuration with information about server-side limitations and other MTProto-related information, help.getAppConfig returns configuration parameters useful for graphical Telegram clients.

+

Typical fields included in the resulting JSON object are:

+
    +
  • emojies_animated_zoom - Animated emojis and animated dice should be scaled by this factor before being shown to the user (float)
  • +
  • keep_alive_service - Whether app clients should start a keepalive service to keep the app running and fetch updates even when the app is closed (boolean)
  • +
  • background_connection - Whether app clients should start a background TCP connection for MTProto update fetching (boolean)
  • +
  • emojies_send_dice - A list of supported animated dice stickers (array of strings).
  • +
  • emojies_send_dice_success - For animated dice emojis other than the basic 🎲, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks 🎆 (object with emoji keys and object values, containing value and frame_start float values)
  • +
  • emojies_sounds - A map of soundbites to be played when the user clicks on the specified animated emoji; the file reference field should be base64-decoded before downloading the file (map of file IDs, with emoji string keys)
  • +
  • gif_search_branding - Specifies the name of the service providing GIF search through gif_search_username (string)
  • +
  • gif_search_emojies - Specifies a list of emojies that should be suggested as search term in a bar above the GIF search box (array of string emojis)
  • +
  • stickers_emoji_suggest_only_api - Specifies that the app should not display local sticker suggestions for emojis at all and just use the result of messages.getStickers (bool)
  • +
  • stickers_emoji_cache_time - Specifies the validity period of the local cache of messages.getStickers, also relevant when generating the pagination hash when invoking the method. (int)
  • +
  • qr_login_camera - Whether the Settings->Devices menu should show an option to scan a QR login code (boolean)
  • +
  • qr_login_code - Whether the login screen should show a QR code login option, possibly as default login method (string, "disabled", "primary" or "secondary")
  • +
  • dialog_filters_enabled - Whether clients should show an option for managing dialog filters AKA folders (boolean)
  • +
  • dialog_filters_tooltip - Whether clients should actively show a tooltip, inviting the user to configure dialog filters AKA folders; typically this happens when the chat list is long enough to start getting cluttered. (boolean)
  • +
  • autoarchive_setting_available - Whether clients can invoke account.setGlobalPrivacySettings with globalPrivacySettings.archive_and_mute_new_noncontact_peers = boolTrue, to automatically archive and mute new incoming chats from non-contacts. (boolean)
  • +
  • pending_suggestions - Contains a list of suggestions that should be actively shown as a tooltip to the user. (Array of strings, possible values shown in the suggestions section ».
  • +
  • url_auth_domains - A list of domains that support automatic login with manual user confirmation, click here for more info on URL authorization ». (array of strings)
  • +
  • autologin_domains - A list of Telegram domains that support automatic login with no user confirmation, click here for more info on URL authorization ». (array of strings)
  • +
  • autologin_token - Autologin token, click here for more info on URL authorization ». (string)
  • +
  • round_video_encoding - Contains a set of recommended codec parameters for round videos.
  • +
  • chat_read_mark_size_threshold - Per-user read receipts, fetchable using messages.getMessageReadParticipants will be available in groups with less than chat_read_mark_size_threshold participants. (int)
  • +
  • chat_read_mark_expire_period - To protect user privacy, read receipts are only stored for chat_read_mark_expire_period seconds after the message was sent. (int)
  • +
+

Example value:

+
{
+    "test": 1,
+    "emojies_animated_zoom": 0.625,
+    "emojies_send_dice": [
+        "\ud83c\udfb2",
+        "\ud83c\udfaf",
+        "\ud83c\udfc0",
+        "\u26bd",
+        "\u26bd\ufe0f",
+        "\ud83c\udfb0",
+        "\ud83c\udfb3"
+    ],
+    "emojies_send_dice_success": {
+        "\ud83c\udfaf": {
+            "value": 6,
+            "frame_start": 62
+        },
+        "\ud83c\udfc0": {
+            "value": 5,
+            "frame_start": 110
+        },
+        "\u26bd": {
+            "value": 5,
+            "frame_start": 110
+        },
+        "\u26bd\ufe0f": {
+            "value": 5,
+            "frame_start": 110
+        },
+        "\ud83c\udfb0": {
+            "value": 64,
+            "frame_start": 110
+        },
+        "\ud83c\udfb3": {
+            "value": 6,
+            "frame_start": 110
+        }
+    },
+    "emojies_sounds": {
+        "\ud83c\udf83": {
+            "id": "4956223179606458539",
+            "access_hash": "-2107001400913062971",
+            "file_reference_base64": "AGFhvoKbftK5O9K9RpgN1ZtgSzWy"
+        },
+        "\u26b0": {
+            "id": "4956223179606458540",
+            "access_hash": "-1498869544183595185",
+            "file_reference_base64": "AGFhvoJIm8Uz0qSMIdm3AsKlK7wJ"
+        },
+        "\ud83e\udddf\u200d\u2642": {
+            "id": "4960929110848176331",
+            "access_hash": "3986395821757915468",
+            "file_reference_base64": "AGFhvoLtXSSIclmvfg6ePz3KsHQF"
+        },
+        "\ud83e\udddf": {
+            "id": "4960929110848176332",
+            "access_hash": "-8929417974289765626",
+            "file_reference_base64": "AGFhvoImaz5Umt4GvMUD5nocIu0W"
+        },
+        "\ud83e\udddf\u200d\u2640": {
+            "id": "4960929110848176333",
+            "access_hash": "9161696144162881753",
+            "file_reference_base64": "AGFhvoIm1QZsb48xlpRfh4Mq7EMG"
+        },
+        "\ud83c\udf51": {
+            "id": "4963180910661861548",
+            "access_hash": "-7431729439735063448",
+            "file_reference_base64": "AGFhvoKLrwl_WKr5LR0Jjs7o3RyT"
+        },
+        "\ud83c\udf8a": {
+            "id": "5094064004578410732",
+            "access_hash": "8518192996098758509",
+            "file_reference_base64": "AGFhvoKMNffRV2J3vKED0O6d8e42"
+        },
+        "\ud83c\udf84": {
+            "id": "5094064004578410733",
+            "access_hash": "-4142643820629256996",
+            "file_reference_base64": "AGFhvoJ1ulPBbXEURlTZWwJFx6xZ"
+        },
+        "\ud83e\uddbe": {
+            "id": "5094064004578410734",
+            "access_hash": "-8934384022571962340",
+            "file_reference_base64": "AGFhvoL4zdMRmYv9z3L8KPaX4JQL"
+        }
+    },
+    "gif_search_branding": "tenor",
+    "gif_search_emojies": [
+        "\ud83d\udc4d",
+        "\ud83d\ude18",
+        "\ud83d\ude0d",
+        "\ud83d\ude21",
+        "\ud83e\udd73",
+        "\ud83d\ude02",
+        "\ud83d\ude2e",
+        "\ud83d\ude44",
+        "\ud83d\ude0e",
+        "\ud83d\udc4e"
+    ],
+    "stickers_emoji_suggest_only_api": false,
+    "stickers_emoji_cache_time": 86400,
+    "qr_login_camera": false,
+    "qr_login_code": "disabled",
+    "dialog_filters_enabled": true,
+    "dialog_filters_tooltip": false,
+    "autoarchive_setting_available": false,
+    "pending_suggestions": [
+        "AUTOARCHIVE_POPULAR",
+        "VALIDATE_PASSWORD",
+        "VALIDATE_PHONE_NUMBER",
+        "NEWCOMER_TICKS"
+    ],
+    "autologin_token": "string",
+    "autologin_domains": [
+        "instantview.telegram.org",
+        "translations.telegram.org",
+        "contest.dev",
+        "contest.com",
+        "bugs.telegram.org",
+        "suggestions.telegram.org",
+        "themes.telegram.org"
+    ],
+    "url_auth_domains": [
+        "somedomain.telegram.org"
+    ],
+    "round_video_encoding": {
+        "diameter": 384,
+        "video_bitrate": 1000,
+        "audio_bitrate": 64,
+        "max_size": 12582912
+    },
+    "chat_read_mark_size_threshold": 50,
+    "chat_read_mark_expire_period": 604800
+}
+

Suggestions

+

The API can return a set of useful suggestions for users of graphical clients.

+

Basic suggestions

+
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
+
+jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+
+---functions---
+
+help.getAppConfig#98914110 = JSONValue;
+

The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.
+A full list of these parameters can be seen in the Client Configuration section », but we're mostly interested in the pending_suggestions and autoarchive_setting_available fields of the returned JSON object:

+ +

Channel suggestions

+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
+
+channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
+
+---functions---
+
+channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;
+

Some channel/supergroup-related suggestions can also be contained in the pending_suggestions field of the channelFull constructor, returned by channels.getFullChannel.
+Here's a list of possible suggestions:

+ +

Dismissing suggestions

+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+---functions---
+
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
+

help.dismissSuggestion can be used to dismiss a suggestion.
+Pass inputPeerEmpty to peer for basic suggestions and the channel/supergroup's peer for channel suggestions.

+

App-specific configuration

+
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
+help.noAppUpdate#c45a6536 = help.AppUpdate;
+
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
+
+help.inviteText#18cb9f78 message:string = help.InviteText;
+
+---functions---
+
+help.getAppUpdate#522d5a7d source:string = help.AppUpdate;
+help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
+
+help.getInviteText#4d392343 = help.InviteText;
+
    +
  • help.getAppUpdate - Get info about an application update, can contain the updated application binary in the attached document
  • +
  • help.getAppChangelog - Get a list of service messages with app-specific changelogs
  • +
  • help.getInviteText - Returns a localized invitation message that can be sent via SMS to contacts that haven't signed up to Telegram yet
  • +
+

Terms of service

+
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+
+help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;
+
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+
+---functions---
+
+help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
+
+auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
+
+account.deleteAccount#418d4e0b reason:string = Bool;
+

These methods can be used for managing consent to Telegram's Terms Of Service.

+

Typically, before a user signs up by invoking auth.signUp, apps should show a pop-up (if the popup flag of the help.termsOfService method is set), asking the user to accept Telegram's terms of service; in case of denial, the user is to be returned to the initial page of the login flow.

+

When signing up for the first time, the help.termsOfService is to be obtained from the auth.authorizationSignUpRequired constructor returned by the auth.signIn.

+

After signing up, or when logging in as an existing user, apps are supposed to call help.getTermsOfServiceUpdate to check for any updates to the Terms of Service; this call should be repeated after expires seconds have elapsed.
+If an update to the Terms Of Service is available, clients are supposed to show a consent popup; if accepted, clients should call help.acceptTermsOfService, providing the termsOfService id JSON object; in case of denial, clients are to delete the account using account.deleteAccount, providing Decline ToS update as deletion reason.

+

Example implementation: android (signup), android (after login)

+

Telegram support info

+
user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+
+help.support#17c6b5f6 phone_number:string user:User = help.Support;
+help.supportName#8c05f1c9 name:string = help.SupportName;
+
+---functions---
+
+help.getSupport#9cdf08cd = help.Support;
+help.getSupportName#d360e72c = help.SupportName;
+

These methods can be used for fetching info about Telegram's support user, that users can use to get support and ask questions about the app.

+ +

Country information and login phone patterns

+
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
+
+help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
+
+help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+
+---functions---
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;
+

help.getCountriesList can be used to fetch a list of localized names for all available countries and phone code patterns for logging in.

+

The phone code pattern should be used when showing the login screen, or when changing phone number: for example, a pattern value of XXX XXX XXX with country_code +39 indicates that the phone field for login should accept a spaced pattern like +39 123 456 789.
+Also, the beginning of the national part of the phone number (123 456 789) should match one of the prefixes, if any were returned.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/datacenter.html b/data/corefork.telegram.org/api/datacenter.html new file mode 100644 index 0000000000..b6e3c15dbb --- /dev/null +++ b/data/corefork.telegram.org/api/datacenter.html @@ -0,0 +1,148 @@ + + + + + Working with Different Data Centers + + + + + + + + + + + + + +
+ +
+
+
+ +

Working with Different Data Centers

+ +

The servers are divided into several data centers (hereinafter “DCs”) in different parts of the world.
A complete list of proxy access points for these DCs may be obtained using help.getConfig:

+
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+---functions---
+help.getConfig#c4f9186b = Config;
+

In this context, this_dc is the number of the current DC, dc_options is a list of all DCs available at the moment, each of which has an id, ip, and port for establishing a connection. Please note that ip and port may change frequently, based on proxy server load and the user's current location.
Typically, each DC has at least one IPv4 and one IPv6 endpoint available.

+

To optimize client communication with the API, each client must use the connection to the closest access point for its main queries (sending messages, getting contacts, etc.). Therefore, knowing how to select a DC is required before communicating with the API.

+

Registration/Authorization

+

The auth.sendCode method is the basic entry point when registering a new user or authorizing an existing user. 95% of all redirection cases to a different DC will occur when invoking this method.

+

The client does not yet know which DC it will be associated with; therefore, it establishes an encrypted connection to a random address and sends its query to that address.
Having received a phone_number from a client, we can find out whether or not it is registered in the system. If it is, then, if necessary, instead of sending a text message, we request that it establish a connection with a different DC first (PHONE_MIGRATE_X error).
If we do not yet have a user with this number, we examine its IP-address. We can use it to identify the closest DC. Again, if necessary, we redirect the user to a different DC (NETWORK_MIGRATE_X error).

+

Testing Redirects

+

There are reserved phone number prefixes to test the correctness of the application’s handling of redirects between DCs. Read more in User Authorization article.

+

File Access

+

A file saved by a user with upload.saveFilePart will be available for direct download only from the DC where the query was executed. That is why each file has a dc_id parameter:

+
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
+
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
+chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
+

To download the file, an encrypted connection to DC dc_id must be established and used to execute the upload.getFile query.
If an attempt is made to download the file over a wrong connection, the FILE_MIGRATE_X error will be returned.

+

Please note that encryption keys are not copied between DCs; therefore, the process of establishing an encrypted connection is started from the very beginning for each new DC. An issued auth_key can be associated with the current authorized user by using an authorization transfer.

+

User Migration

+

During the process of working with the API, user information is accumulated in the DC with which the user is associated. This is the reason a user cannot be associated with a different DC by means of the client. However, in the future, during prolonged communication from an unusual location, we may decide that the user’s data must be moved to a different DC. After some time, the data will be copied and the association will be updated. Once this happens, when executing any query transmitted to the old DC, the API will return the USER_MIGRATE_X error. The client will then have to establish a connection with the new DC and repeat the query.

+

Authorization Transfer

+

The following methods can be used to eliminate the need for users to enter the code from a text message every time:

+
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
+auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+---functions---
+auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
+auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;
+

auth.exportAuthorization must be executed in the current DC (the DC with which a connection has already been established), passing in dc_id as the value for the new DC. The method should return the user identifier and a long string of random data. An import operation can be performed at the new DC by sending it what was received. Queries requiring authorization can then be successfully executed in the new DC.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/dice.html b/data/corefork.telegram.org/api/dice.html new file mode 100644 index 0000000000..89db5f5186 --- /dev/null +++ b/data/corefork.telegram.org/api/dice.html @@ -0,0 +1,149 @@ + + + + + Dice + + + + + + + + + + + + + +
+ +
+
+
+ +

Dice

+ +

Telegram supports sending animated dice emojis.
+This is implemented by using the dice constructors:

+
inputMediaDice#e66fbf7b emoticon:string = InputMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+---functions---
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+
+help.getAppConfig#98914110 = JSONValue;
+

On startup, clients should fetch app configuration using help.getAppConfig.
+Then, for each dice emoji contained in the emojies_send_dice field, clients should fetch the dice emoji stickerset by calling the messages.getStickerSet method, providing the properly populated inputStickerSetDice to the stickerset field.
+The returned stickerset will contain a set of animated stickers, one for each of the dice outcomes, plus a first looping sticker that should be shown as preview to the user before actually sending the dice.

+

If a user attempts to send a single emoji from the ones specified in emojies_send_dice, the dice should be sent using messages.sendMedia, providing the dice emoji to the emoticon field.

+

Incoming dice stickers will be received as a messageMediaDice constructor, along with a randomly generated server-side value, ranging from 1 to the maximum allowed value for this type of dice.
+Clients should display the correct dice animated sticker for the specified value: since dice values start from 1, and the first animated sticker in dice stickerset is the preview, value can be used to directly index the documents sticker array from the animated stickerset.

+

The emojies_send_dice_success configuration parameter contains more info about dice emojis other than the basic 🎲:

+
    "emojies_send_dice_success": {
+        "\ud83c\udfaf": {
+            "value": 6,
+            "frame_start": 62
+        },
+        "\ud83c\udfc0": {
+            "value": 5,
+            "frame_start": 110
+        }
+    }
+

For each of the dice emojis, a maximum "winning" value is specified, along with the frame number at which to show the fireworks 🎆.
+Please note that dice animated stickers should loop only once, right after being sent/received for the first time; clicking on the dice sticker should bring up a popup, inviting the user to send a new dice of the same type.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/discussion.html b/data/corefork.telegram.org/api/discussion.html new file mode 100644 index 0000000000..70271a7f45 --- /dev/null +++ b/data/corefork.telegram.org/api/discussion.html @@ -0,0 +1,151 @@ + + + + + Discussion groups + + + + + + + + + + + + + +
+ +
+
+
+ +

Discussion groups

+ +
+ +

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
+
+messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+
+---functions---
+
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
+

A discussion group can be associated to a channel using channels.setDiscussionGroup.
+The discussion group can be accessed in the client by clicking on the discuss button of the channel, or by accessing the comment section of a specific post; the discussion group ID is also present in the linked_chat_id field of the channelFull constructor.

+

All messages sent to the channel will also be sent to the linked group (with sender peer from_id equal to the peer of the linked channel); those messages will also be automatically pinned in the group.

+

Linking a discussion group

+

To obtain a list of admined supergroups that a channel admin can possibly associate to a channel, use channels.getGroupsForDiscussion.
+Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
+Before linking a supergroup to a channel, access to the supergroup's old messages must also be enabled using channels.togglePreHistoryHidden.

+

To set a returned supergroup as a discussion group use channels.setDiscussionGroup.

+

Schema:

+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+
+---functions---
+
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
+
+channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/drafts.html b/data/corefork.telegram.org/api/drafts.html new file mode 100644 index 0000000000..8770c19a7e --- /dev/null +++ b/data/corefork.telegram.org/api/drafts.html @@ -0,0 +1,131 @@ + + + + + Message drafts + + + + + + + + + + + + + +
+ +
+
+
+ +

Message drafts

+ +
+ +

Message drafts in Telegram allow syncing the text typed into message fields between devices.

+

Drafts

+

Drafts are represented by the DraftMessage constructors. +The parameters of the peer-specific draft should be used as defaults when composing a message to be sent to a certain peer (in the case of media, the same draft should still be used as base, the message will become the caption). +If the user exits the app before sending the message, the message should be saved as a draft:

+

Saving drafts

+

Drafts can be saved using the messages.saveDraft method.

+

Downloading drafts

+

New drafts are automatically sent to all devices via updateDraftMessage updates.

+

Dialog objects fetched via the API also contain the draft associated with the dialog.

+

Clearing drafts

+

Drafts can be cleared by setting the clear_draft flag when sending messages or media using messages.sendMessage, messages.sendMedia, messages.sendMultiMedia, messages.sendInlineBotResult and similar or manually by passing empty values to messages.saveDraft.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/end-to-end.html b/data/corefork.telegram.org/api/end-to-end.html new file mode 100644 index 0000000000..27fd5216fd --- /dev/null +++ b/data/corefork.telegram.org/api/end-to-end.html @@ -0,0 +1,244 @@ + + + + + End-to-End Encryption, Secret Chats + + + + + + + + + + + + + +
+ +
+
+
+ +

End-to-End Encryption, Secret Chats

+ +
+ +
+

This article on MTProto's End-to-End encryption is meant for advanced users. +If you want to learn more about Secret Chats from a less intimidating source, kindly see our general FAQ.

+
+
+

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. +MTProto v.1.0 is deprecated and is currently being phased out.

+
+
+
Related articles
+

+
+

Secret Chats are one-on-one chats wherein messages are encrypted with a key held only by the chat’s participants. Note that the schema for these end-to-end encrypted Secret Chats is different from what is used for cloud chats:

+
+ +
+

A note on MTProto 2.0

+

This article describes the end-to-end encryption layer in the MTProto protocol version 2.0. +The principal differences from version 1.0 (described here for reference) are as follows:

+
    +
  • SHA-256 is used instead of SHA-1;
  • +
  • Padding bytes are involved in the computation of msg_key;
  • +
  • msg_key depends not only on the message to be encrypted, but on a portion of the secret chat key as well;
  • +
  • 12..1024 padding bytes are used instead of 0..15 padding bytes in v.1.0.
  • +
+

See also: MTProto 2.0: Cloud Chats, server-client encryption

+

Key Generation

+

Keys are generated using the Diffie-Hellman protocol.

+

Let us consider the following scenario: User A would like to initiate end-to-end encrypted communication with User B.

+

Sending a Request

+

User A executes messages.getDhConfig to obtain the Diffie-Hellman parameters: a prime p, and a high order element g.

+

Executing this method before each new key generation procedure is of vital importance. It makes sense to cache the values of the parameters together with the version in order to avoid having to receive all of the values every time. If the version stored on the client is still up-to-date, the server will return the constructor messages.dhConfigNotModified.

+

Client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

+

If the client needs additional entropy for the random number generator, it can pass the random_length parameter (random_length> 0) so the server generates its own random sequence random of the appropriate length. +Important: using the server’s random sequence in its raw form may be unsafe, it must be combined with a client sequence.

+

Client A computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and executes messages.requestEncryption after passing in g_a := pow(g, a) mod dh_prime.

+

User B receives the update updateEncryption for all associated authorization keys (all authorized devices) with the chat constructor encryptedChatRequested. The user must be shown basic information about User A and must be prompted to accept or reject the request.

+

Both clients are to check that g, g_a and g_b are greater than one and smaller than p-1. We recommend checking that g_a and g_b are between 2^{2048-64} and p - 2^{2048-64} as well.

+

Accepting a Request

+

After User B confirms the creation of a secret chat with A in the client interface, Client B also receives up-to-date configuration parameters for the Diffie-Hellman method. Thereafter, it generates a random 2048-bit number, b, using rules similar to those for a.

+

Having received g_a from the update with encryptedChatRequested, it can immediately generate the final shared key: key = (pow(g_a, b) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. Its fingerprint, key_fingerprint, is equal to the 64 last bits of SHA1 (key).

+

Note 1: in this particular case SHA1 is used here even for MTProto 2.0 secret chats.

+

Note 2: this fingerprint is used as a sanity check for the key exchange procedure to detect bugs when developing client software — it is not connected to the key visualization used on the clients as means of external authentication in secret chats. Key visualizations on the clients are generated using the first 128 bits of SHA1(initial key) followed by the first 160 bits of SHA256(key used when secret chat was updated to layer 46).

+

Client B executes messages.acceptEncryption after passing it g_b := pow(g, b) mod dh_prime and key_fingerprint.

+

For all of Client B’s authorized devices, except the current one, updateEncryption updates are sent with the constructor encryptedChatDiscarded. Thereafter, the only device that will be able to access the secret chat is Device B, which made the call to messages.acceptEncryption.

+

User A will be sent an updateEncryption update with the constructor encryptedChat, for the authorization key that initiated the chat.

+

With g_b from the update, Client A can also compute the shared key key = (pow(g_b, a) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. If the fingerprint for the received key is identical to the one that was passed to encryptedChat, incoming messages can be sent and processed. Otherwise, messages.discardEncryption must be executed and the user notified.

+

Perfect Forward Secrecy

+

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

+
+

The re-keying protocol is further described in this article: Perfect Forward Secrecy in Secret Chats.

+
+

Please note that your client must support Forward Secrecy in Secret Chats to be compatible with official Telegram clients.

+

Sending and Receiving Messages in a Secret Chat

+

Serialization and Encryption of Outgoing Messages

+

A TL object of type DecryptedMessage is created and contains the message in plain text. For backward compatibility, the object must be wrapped in the constructor decryptedMessageLayer with an indication of the supported layer (starting with 46).

+
+

The TL-Schema for the contents of end-to-end encrypted messages is available here »

+
+

The resulting construct is serialized as an array of bytes using generic TL rules. The resulting array is prepended by 4 bytes containing the array length not counting these 4 bytes.

+

The byte array is padded with 12 to 1024 random padding bytes to make its length divisible by 16 bytes. (In the older MTProto 1.0 encryption, only 0 to 15 padding bytes were used.)

+

Message key, msg_key, is computed as the 128 middle bits of the SHA256 of the data obtained in the previous step, prepended by 32 bytes from the shared key key. (For the older MTProto 1.0 encryption, msg_key was computed differently, as the 128 lower bits of SHA1 of the data obtained in the previous steps, excluding the padding bytes.)

+

For MTProto 2.0, the AES key aes_key and initialization vector aes_iv are computed ( key is the shared key obtained during Key Generation ) as follows:

+
    +
  • msg_key_large = SHA256 (substr (key, 88+x, 32) + plaintext + random_padding);
  • +
  • msg_key = substr (msg_key_large, 8, 16);
  • +
  • sha256_a = SHA256 (msg_key + substr (key, x, 36));
  • +
  • sha256_b = SHA256 (substr (key, 40+x, 36) + msg_key);
  • +
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • +
  • aes_iv = substr (sha256_b, 0, 8) + substr (sha256_a, 8, 16) + substr (sha256_b, 24, 8);
  • +
+

For MTProto 2.0, x=0 for messages from the originator of the secret chat, x=8 for the messages in the opposite direction.

+

For the obsolete MTProto 1.0, msg_key, aes_key, and aes_iv were computed differently (see this document for reference).

+

Data is encrypted with a 256-bit key, aes_key, and a 256-bit initialization vector, aes-iv, using AES-256 encryption with infinite garble extension (IGE). Encryption key fingerprint key_fingerprint and the message key msg_key are added at the top of the resulting byte array.

+

Encrypted data is embedded into a messages.sendEncrypted API call and passed to Telegram server for delivery to the other party of the Secret Chat.

+

Upgrading to MTProto 2.0 from MTProto 1.0

+

As soon as both parties in a secret chat are using at least Layer 73, they should only use MTProto 2.0 for all outgoing messages. Some of the first received messages may use MTProto 1.0, if a sufficiently high starting layer has not been negotiated during the creation of the secret chat. After the first message encrypted with MTProto 2.0 (or the first message with Layer 73 or higher) is received, all messages with higher sequence numbers must be encrypted with MTProto 2.0 as well.

+

As long as the current layer is lower than 73, each party should try to decrypt received messages with MTProto 1.0, and if this is not successfull (msg_key does not match), try MTProto 2.0. Once the first MTProto 2.0-encrypted message arrives (or the layer is upgraded to 73), there is no need to try MTProto 1.0 decryption for any of the further messages (unless the client is still waiting for some gaps to be closed).

+

Decrypting an Incoming Message

+

The steps above are performed in reverse order. +When an encrypted message is received, you must check that msg_key is in fact equal to the 128 middle bits of the SHA256 hash of the decrypted message, prepended by 32 bytes taken from the shared key. +If the message layer is greater than the one supported by the client, the user must be notified that the client version is out of date and prompted to update.

+

Sequence numbers

+

It is necessary to interpret all messages in their original order to protect against possible manipulations. Secret chats support a special mechanism for handling seq_no counters independently from the server.

+
+

Proper handling of these counters is further described in this article: Sequence numbers in Secret Chats.

+
+

Please note that your client must support sequence numbers in Secret Chats to be compatible with official Telegram clients.

+

Sending Encrypted Files

+

All files sent to secret chats are encrypted with one-time keys that are in no way related to the chat’s shared key. Before an encrypted file is sent, it is assumed that the encrypted file’s address will be attached to the outside of an encrypted message using the file parameter of the messages.sendEncryptedFile method and that the key for direct decryption will be sent in the body of the message (the key parameter in the constructors decryptedMessageMediaPhoto, decryptedMessageMediaVideo and decryptedMessageMediaFile.

+

Prior to a file being sent to a secret chat, 2 random 256-bit numbers are computed which will serve as the AES key and initialization vector used to encrypt the file. AES-256 encryption with infinite garble extension (IGE) is used in like manner.

+

The key fingerprint is computed as follows:

+
    +
  • digest = md5(key + iv)
  • +
  • fingerprint = substr(digest, 0, 4) XOR substr(digest, 4, 4)
  • +
+

The encrypted contents of a file are stored on the server in much the same way as those of a file in cloud chats: piece by piece using calls to upload.saveFilePart. +A subsequent call to messages.sendEncryptedFile will assign an identifier to the stored file and send the address together with the message. The recipient will receive an update with encryptedMessage, and the file parameter will contain file information.

+

Incoming and outgoing encrypted files can be forwarded to other secret chats using the constructor inputEncryptedFile to avoid saving the same content on the server twice.

+

Working with an Update Box

+

Secret chats are associated with specific devices (or rather with authorization keys), not users. A conventional message box, which uses pts to describe the client’s status, is not suitable, because it is designed for long-term message storage and message access from different devices.

+

An additional temporary message queue is introduced as a solution to this problem. When an update regarding a message from a secret chat is sent, a new value of qts is sent, which helps reconstruct the difference if there has been a long break in the connection or in case of loss of an update.

+

As the number of events increases, the value of qts increases by 1 with each new event. The initial value may not (and will not) be equal to 0.

+

The fact that events from the temporary queue have been received and stored by the client is acknowledged explicitly by a call to the messages.receivedQueue method or implicitly by a call to updates.getDifference (the value of qts passed, not the final state). All messages acknowledged as delivered by the client, as well as any messages older than 7 days, may (and will) be deleted from the server.

+

Upon de-authorization, the event queue of the corresponding device will be forcibly cleared, and the value of qts will become irrelevant.

+

Updating to new layers

+

Your client should always store the maximal layer that is known to be supported by the client on the other side of a secret chat. When the secret chat is first created, this value should be initialized to 46. This remote layer value must always be updated immediately after receiving any packet containing information of an upper layer, i.e.:

+
    +
  • any secret chat message containing layer_no in its decryptedMessageLayer with layer>=46, or
  • +
  • a decryptedMessageActionNotifyLayer service message, wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d).
  • +
+

Notifying the remote client about your local layer

+

In order to notify the remote client of your local layer, your client must send a message of the decryptedMessageActionNotifyLayer type. This notification must be wrapped in a constructor of an appropriate layer.

+

There are two cases when your client must notify the remote client about its local layer:

+
    +
  1. As soon as a new secret chat has been created, immediately after the secret key has been successfully exchanged.
  2. +
  3. Immediately after the local client has been updated to support a new secret chat layer. In this case notifications must be sent to all currently existing secret chats. Note that this is only necessary when updating to new layers that contain changes in the secret chats implementation (e.g. you don’t need to do this when your client is updated from Layer 46 to Layer 47).
  4. +
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/end-to-end/pfs.html b/data/corefork.telegram.org/api/end-to-end/pfs.html new file mode 100644 index 0000000000..8447ceee85 --- /dev/null +++ b/data/corefork.telegram.org/api/end-to-end/pfs.html @@ -0,0 +1,176 @@ + + + + + Perfect Forward Secrecy + + + + + + + + + + + + + +
+ +
+
+
+ +

Perfect Forward Secrecy

+ +
+

Telegram supports Perfect Forward Secrecy (PFS) in Secret Chats as of Layer 20. See updating to new layers.

+
+

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

+

Any client participating in a Secret Chat can initiate re-keying as soon as it perceives that the current key has been used for too long or for encrypting too many messages. Please note that you should never initiate a new instance of the re-keying protocol if an uncompleted instance exists, initiated by either party.

+

Note: third-party developers are required to maintain the same level of security. All clients with secret chat support must be able to initiate re-keying and accept relevant service messages. See Security Guidelines.

+

Re-keying protocol

+

New keys are generated by exchanging special messages, using previously established keys for encryption. The re-keying protocol between parties A and B normally consists of four steps:

+
1. decryptedMessageActionRequestKey
+

A (re-keying initiator) generates a new value of a, subject to the same limitations as for the initial Diffie-Hellman key exchange, and sends the value of pow(g,a) to B, embedded in a decryptedMessageService:

+
decryptedMessageActionRequestKey exchange_id:long g_a:string = DecryptedMessageAction;
+
    +
  • exchange_id is a random number identifying this instance of the Re-Keying Protocol for both parties
  • +
  • g_a is the value of pow(g,a) mod p
  • +
+

Note that the same Diffie--Hellman parameters (p,g) as for the initial Diffie--Hellman key exchange in this secret chat are used. They do not need to be re-transmitted explicitly.

+
2. decryptedMessageActionAcceptKey
+

Upon receipt of the above service message, B checks its content, and generates a response with same exchange_id, for a newly generated value of b:

+
decryptedMessageActionAcceptKey exchange_id:long g_b:string key_fingerprint:long = DecryptedMessageAction;
+
    +
  • exchange_id is the same as in the received decryptedMessageActionRequestKey
  • +
  • g_b is the value of pow(g,b) mod p
  • +
  • key_fingerprint is the 64-bit fingerprint of the newly generated key = pow(g_a, b) mod p, used as a sanity check of the implementation
  • +
+

At this stage, B can already compute the new key key = pow(g_a, b) mod p and its key_fingerprint (last 64 bits of its SHA-1). However, it continues using the previous key until the completion of the exchange.

+

Once side B sends decryptedMessageActionAcceptKey, it cannot abort the key exchange; it must be ready to switch to the new key immediately after a decryptedMessageActionCommitKey is received. Therefore, if side B wishes to delay the usage of new key, for example in order to fill some seq_no gaps first, it must delay the decryptedMessageActionAcceptKey answer accordingly.

+
3. decryptedMessageActionCommitKey
+

Once A receives a valid decryptedMessageActionAcceptKey, it performs all necessary checks, and "commits" the new key by means of the following service message:

+
decryptedMessageActionCommitKey exchange_id:long key_fingerprint:long = DecryptedMessageAction;
+
    +
  • exchange_id is the same as in the two previous messages
  • +
  • key_fingerprint is the value of the hash (last 64 bits of SHA-1) of the new key computed by A, for implementation sanity check
  • +
+

After that, A can (and must) encrypt all following messages with the new key.

+

If side A wishes to delay installation of the new key, for example because there are some seq_no gaps that it wants to fill first, it must delay decryptedMessageActionCommitKey answer accordingly.

+
4. Final step
+

When B receives either a decryptedMessageActionCommitKey or a message encrypted by the new key, recognized by the value of key_fingerprint prepended to the encrypted message (it may happen that the decryptedMessageActionCommitKey has been lost and will be re-requested later), it assumes that A has started using the new key for encryption, and does the same.

+

However, the previous key may be kept until there are no gaps in received messages up to the switch to the new key. Once all the gaps have been filled, the old key must be securely discarded.

+

There is one exception to this rule — the SHA-1 of the original key (generated during the establishment of Secret Chat in question) is always stored, in order to show key visualizations on the clients.

+

Aborting protocol

+

Any of the parties may abort any instance of an uncompleted re-keying protocol, unless decryptedMessageActionCommitKey or decryptedMessageActionAcceptKey has been already sent by the party in question. In order to abort re-keying, send

+
decryptedMessageActionAbortKey exchange_id:long = DecryptedMessageAction;
+

This could be done, for example, if the party is already participating in a different instance of the re-keying protocol, or if the received values of g_a, g_b and other parameters do not pass security checks. In the latter case, it might be advisable to abort the Secret Chat altogether.

+

Discarding Previous Keys

+

Once B receives decryptedMessageActionCommitKey, it can safely discard the previous key provided there are no gaps. However, A may only discard the previous key after a message encrypted with the new key has been received. If no ordinary messages are scheduled to be sent, a special no-op message should sent by B for this purpose:

+
decryptedMessageActionNoop = DecryptedMessageAction;
+

Concurrent Re-Keying

+

It may happen that both parties concurrently initiate re-keying by sending decryptedMessageActionRequestKey without knowing that the other party has already done so. If each side aborts re-keying because it is already participating in another instance of the protocol initiated by itself, the re-keying will never happen.

+

Because of this possibility, we suggest that only the instance with the smaller exchange_id is aborted, with the option to re-use its (a,g_a) for the re-keying protocol instance with the larger exchange_id (when compared as a long, i.e. signed little-endian 64-bit integer).

+

In other words, if a decryptedMessageActionRequestKey is received after A has sent its decryptedMessageActionRequestKey, but has not yet received decryptedMessageActionAcceptKey, the following is to be done:

+
    +
  • if exchange_id in the sent decryptedMessageActionRequestKey was larger than that in the decryptionActionRequestKey just received, abort the newly-suggested re-keying protocol instance without sending explicit decryptedMessageActionAbortKey (the other side will do the same according to the next rule).
  • +
  • if exchange_id in our decryptedMessageActionRequestKey was smaller, respond to the newly-received decryptedMessageActionRequestKey with a decryptedMessageActionAcceptKey, and participate only in the re-keying protocol instance initiated by the other side. It is possible to re-use at this stage the value of g_a (now called g_b) that was generated for the original decryptedMessageActionRequestKey, now abandoned, or totally new (b,g_b) can be generated.
  • +
  • in the unlikely (2^{-64}) case both exchange_id are equal, abort both instances without sending an explicit decryptedMessageActionAbortKey. The other side will do the same.
  • +
+
Key Visualization
+

Since all re-keying instances are carried over the secure channel established when the secret chat is created, it is necessary for the user to confirm that no MITM attack had taken place during the initial exchange. The key visualization on the clients uses the first 128-bits of the SHA-1 of the original key created when the Secret Chat was first established, followed by the first 160 bits of the SHA-256 of the key in use when the secret chat was updated to layer 46 (coincides with the original key if chat was created using layer 46).

+
+

Please note that the key_fingerprint parameter was introduced as a maintenance tool (with a misleading name) and is not related to key visualization on the clients.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/end-to-end/seq_no.html b/data/corefork.telegram.org/api/end-to-end/seq_no.html new file mode 100644 index 0000000000..ed84d5f923 --- /dev/null +++ b/data/corefork.telegram.org/api/end-to-end/seq_no.html @@ -0,0 +1,173 @@ + + + + + Sequence numbers in Secret Chats + + + + + + + + + + + + + +
+ +
+
+
+ +

Sequence numbers in Secret Chats

+ +

It is necessary to interpret all messages in their original order to protect against reordering, reflection, replay, omission and other manipulations (decryptedMessageActionResend messages are the only exception to this rule, see avoiding concurrent gaps). Secret chats support a special mechanism for handling seq_no counters independently from the server. Note that any service messages in secret chats must also increment the seq_no.

+

All Secret Chats messages in clients using Layer 17 or higher are wrapped in decryptedMessageLayer and have seq_no (sequence number) counters attached to them. The seq_no counters in their raw form are initialized with (out_seq_no, in_seq_no) := (0,0), and incremented strictly by 1 after any message (service or not) is sent/received and processed. They must be protected from mirroring before being sent to the remote client by transformation according to formula 2*raw_seq_no+x, where x is 0 or 1, determined by the following rule:

+ + + + + + + + + + + + + + + + + +
in_seq_noout_seq_no
secret chat initiated by sender01
secret chat initiated by recipient10
+

In this way the least significant bit of each seq_no field included in the message is different for incoming and outgoing messages. This is done to prevent a possible attacker from mirroring the messages. If any of the received in_seq_no or out_seq_no are not consistent in terms of parity (see table above), the client is required to immediately abort the secret chat.

+
+

E.g., the first message the local client sends to any secret chat will have out_seq_no of 0+x_out, the second one will have out_seq_no of 2*1+x_out, and so on, where x_out is 0 if the chat was initiated by the remote client, 1 otherwise; similarly for the received messages, but there x_in is used instead of x_out and is equal to 0 if the chat was initiated by the local client, 1 otherwise.

+
+

Raw sequence numbers will be used in the remaining part of this text, unless otherwise specified.

+

Preventing gaps

+

Your client must ensure that all outgoing secret chat messages are queued on the server in the correct order. This is achieved by correctly placing them into the invokeAfterMsgs chain. Failure to do this may result in gaps on the remote client, which may in turn lead to aborted secret chats. The local client must maintain the correct sequence of in_seq_no for the remote client. To achieve this, assign in_seq_no and out_seq_no to each message at the exact moment when the message is created, and never change them in the future.

+

Security checks

+

Checking out_seq_no

+

Your client must check that it has received each message with the sequence number out_seq_no starting from 0 to some current point C. It should then expect the next message to have the sequence number out_seq_no=C+1. If the out_seq_no in the received message does not match this, the following needs to be done:

+
    +
  • If the received out_seq_no<=C, the local client must drop the message (repeated message). The client should not check the contents of the message because the original message could have been deleted (see Deleting unacknowledged messages).
  • +
  • If the received out_seq_no>C+1, it most likely means that the server left out some messages due to a technical failure or due to the messages becoming obsolete. A temporary solution to this is to simply abort the secret chat. But since this may cause some existing older secret chats to be aborted, it is strongly recommended for the client to properly handle such seq_no gaps. Note that in_seq_no is not increased upon receipt of such a message; it is advanced only after all preceding gaps are filled.
  • +
+

Proper handling of gaps

+

In order to correctly handle incoming messages after a hole has been identified (when received out_seq_no>C+1), it is necessary to put received messages with the wrong seq_no into a "waiting queue" on the local client, and to re-request the missing messages using the special constructor decryptedMessageActionResend start_seq_no:int end_seq_no:int = DecryptedMessageAction;. The sequence numbers used in this constructor must be ready for interpretation by the remote client and therefore cannot be in their raw form: you can easily get the necessary start_seq_no by adding 2 to the out_seq_no of the last message before the hole and the end_seq_no by subtracting 2 from the out_seq_no of the received message with the wrong sequence number.

+

Each hole normally requires only one request to resend messages — if the remote client keeps sending out of sync messages, they should be put into the queue without sending a new request. Having received the missing messages, the local client must first interpret these messages in the right order by their seq_no. Once this is done, the client can proceed to interpret messages from the queue (again, in the right seq_no order).

+

Special cases:

+
    +
  • Note that having two gaps simultaneously is very rare (provided that the remote client and server are operating normally) and it is acceptable to abort the secret chat in this situation.
  • +
  • If a local client receives decryptedMessageActionResend but is unable to satisfy the request, it must abort the secret chat.
  • +
+

Avoiding concurrent gaps

+

In order to avoid getting stuck with concurrent gaps on both sides, decryptedMessageActionResend must always be interpreted immediately upon receipt in all cases, even if its out_seq_no>=C+1. Note that each decryptedMessageActionResend must only be handled once, it must not be interpreted again when we interpret messages in the queue.

+

Checking and handling in_seq_no

+

in_seq_no of all received messages must be valid. To ensure this, perform the following checks:

+
    +
  • in_seq_no must form a non-decreasing sequence of non-negative integer numbers.
  • +
  • in_seq_no must be valid at the moment of receiving the message, that is, if D is the out_seq_no of last message we sent, the received in_seq_no should not be greater than D + 1. This also allows us to insert the received message into its correct place in the secret chat. For example, imagine that the local client has sent 5 secret chat messages, and then receives a secret chat message with the text "Yes" and in_seq_no=2. In this situation the local client must place that message after the second message it sent. This makes manipulations with delayed messages impossible.
  • +
+

If in_seq_no contradicts these criteria, the local client is required to immediately abort the secret chat. This could happen only in case of malicious or buggy behaviour on either server or remote client side.

+

Deleting unacknowledged messages

+

In case the user on the local client has deleted a message before the server (or the remote client, if decryptedMessageActionResend is handled correctly) could acknowledge the message, for security reasons, you must:

+
    +
  • securely destroy the contents of the message (as in case of any other deleted Secret Chat message);
  • +
  • change the local copy of the original message to decryptedMessageActionDeleteMessages with random_id equal to its own random_id;
  • +
  • create a new outgoing message deleting the original message.
  • +
+

This must be done because your client doesn't know whether the remote client really received the message or not. In the case the message was already received, it will be deleted by the second message; otherwise it must arrive as a "self-delete" message to maintain the correct sequence of seq_no.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/end-to-end/video-calls.html b/data/corefork.telegram.org/api/end-to-end/video-calls.html new file mode 100644 index 0000000000..3561fafe1d --- /dev/null +++ b/data/corefork.telegram.org/api/end-to-end/video-calls.html @@ -0,0 +1,215 @@ + + + + + End-to-End Encrypted Voice and Video Calls + + + + + + + + + + + + + +
+ +
+
+
+ +

End-to-End Encrypted Voice and Video Calls

+ +

This article describes the end-to-end encryption used for Telegram voice and video calls.

+
Related Articles
+

+ +
+

Establishing Calls

+

Before a call is ready, some preliminary actions have to be performed. The calling party needs to contact the party to be called and check whether it is ready to accept the call. Besides that, the parties have to negotiate the protocols to be used, learn the IP addresses of each other or of the Telegram relay servers to be used (so-called reflectors), and generate a one-time encryption key for this voice call with the aid of Diffie--Hellman key exchange. All of this is accomplished in parallel with the aid of several Telegram API methods and related notifications. This document covers details related to key generation, encryption and security.

+

Key Generation

+

The Diffie-Hellman key exchange, as well as the whole protocol used to create a new voice call, is quite similar to the one used for Secret Chats. We recommend studying the linked article before proceeding.

+

However, we have introduced some important changes to facilitate the key verification process. Below is the entire exchange between the two communicating parties, the Caller (A) and the Callee (B), through the Telegram servers (S).

+
    +
  • A executes messages.getDhConfig to find out the 2048-bit Diffie-Hellman prime p and generator g. The client is expected to check whether p is a safe prime and perform all the security checks necessary for secret chats.
  • +
  • A chooses a random value of a, 1 < a < p-1, and computes g_a:=power(g,a) mod p (a 256-byte number) and g_a_hash:=SHA256(g_a) (32 bytes long).
  • +
  • A invokes (sends to server S) phone.requestCall, which has the field g_a_hash:bytes, among others. For this call, this field is to be filled with g_a_hash, not g_a itself.
  • +
  • The Server S performs privacy checks and sends an updatePhoneCall update with a phoneCallRequested constructor to all of B's active devices. This update, apart from the identity of A and other relevant parameters, contains the g_a_hash field, filled with the value obtained from A.
  • +
  • B accepts the call on one of their devices, stores the received value of g_a_hash for this instance of the voice call creation protocol, chooses a random value of b, 1 < b < p-1, computes g_b:=power(g,b) mod p, performs all the required security checks, and invokes the phone.acceptCall method, which has a g_b:bytes field (among others), to be filled with the value of g_b itself (not its hash).
  • +
  • The Server S sends an updatePhoneCall with the phoneCallDiscarded constructor to all other devices B has authorized, to prevent accepting the same call on any of the other devices. From this point on, the server S works only with that of B's devices which has invoked phone.acceptCall first.
  • +
  • The Server S sends to A an updatePhoneCall update with phoneCallAccepted constructor, containing the value of g_b received from B.
  • +
  • A performs all the usual security checks on g_b and a, computes the Diffie--Hellman key key:=power(g_b,a) mod p and its fingerprint key_fingerprint:long, equal to the lower 64 bits of SHA1(key), the same as with secret chats. Then A invokes the phone.confirmCall method, containing g_a:bytes and key_fingerprint:long.
  • +
  • The Server S sends to B an updatePhoneCall update with the phoneCall constructor, containing the value of g_a in g_a_or_b:bytes field, and key_fingerprint:long
  • +
  • At this point B receives the value of g_a. It checks that SHA256(g_a) is indeed equal to the previously received value of g_a_hash, performs all the usual Diffie-Hellman security checks, and computes the key key:=power(g_a,b) mod p and its fingerprint, equal to the lower 64 bits of SHA1(key). Then it checks that this fingerprint equals the value of key_fingerprint:long received from the other side, as an implementation sanity check.
  • +
+

At this point, the Diffie--Hellman key exchange is complete, and both parties have a 256-byte shared secret key key which is used to encrypt all further exchanges between A and B.

+

It is of paramount importance to accept each update only once for each instance of the key generation protocol, discarding any duplicates or alternative versions of already received and processed messages (updates).

+

Encryption

+
+

This document describes encryption in voice and video calls as implemented in Telegram apps with versions 7.0 and above. See this document for details on encryption used in voice calls in app versions released before August 14, 2020.

+
+

The Telegram Voice and Video Call Library uses an optimized version of MTProto 2.0 to send and receive packets, consisting of one or more end-to-end encrypted messages of various types (ice candidates list, video formats, remote video status, audio stream data, video stream data, message ack or empty).

+

This document describes only the encryption process, leaving out encoding and network-dependent parts.

+

The library starts working with:

+
    +
  • An encryption key key shared between the parties, as generated above.
  • +
  • Information whether the call is outgoing or incoming.
  • +
  • Two data transfer channels: signaling, offered by the Telegram API, and transport based on WebRTC.
  • +
+

Both data transfer channels are unreliable (messages may get lost), but signaling is slower and more reliable.

+

Encrypting Call Data

+

The body of a packet (decrypted_body) consists of several messages and their respective seq numbers concatenated together.

+
    +
  • decrypted_body = message_seq1 + message_body1 + message_seq2 + message_body2
  • +
+

Each decrypted_body is unique because no two seq numbers of the first message can be the same. If only old messages need to be re-sent, an empty message with new unique seq is added to the packet first.

+

The encryption key key is used to compute a 128-bit msg_key and then a 256-bit aes_key and a 128-bit aes_iv:

+
    +
  • msg_key_large = SHA256 (substr(key, 88+x, 32) + decrypted_body);
  • +
  • msg_key = substr (msg_key_large, 8, 16);
  • +
  • sha256_a = SHA256 (msg_key + substr (key, x, 36));
  • +
  • sha256_b = SHA256 (substr (key, 40+x, 36) + msg_key);
  • +
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • +
  • aes_iv = substr (sha256_b, 0, 4) + substr (sha256_a, 8, 8) + substr (sha256_b, 24, 4);
  • +
+

x depends on whether the call is outgoing or incoming and on the connection type:

+
    +
  • x = 0 for outgoing + transport
  • +
  • x = 8 for incoming + transport
  • +
  • x = 128 for outgoing + signaling
  • +
  • x = 136 for incoming + signaling
  • +
+

This allows apps to decide which packet types will be sent to which connections and work in these connections independently (with each having its own seq counter).

+

The resulting aes_key and aes_iv are used to encrypt decrypted_body:

+
    +
  • encrypted_body = AES_CTR (decrypted_body, aes_key, aes_iv)
  • +
+

The packet that gets sent consists of msg_key and encrypted_body:

+
    +
  • packet_bytes = msg_key + encrypted_body
  • +
+

When received, the packet gets decrypted using key and msg_key, after which msg_key is checked against the relevant SHA256 substring. If the check fails, the packet must be discarded.

+

Protecting Against Replay Attacks

+

Each of the peers maintains its own 32-bit monotonically increasing counter for outgoing messages, seq, starting with 1. This seq counter is prepended to each sent message and increased by 1 for each new message. No two seq numbers of the first message in a packet can be the same. If only old messages need to be re-sent, an empty message with a new unique seq is added to the packet first. When the seq counter reaches 2^30, the call must be aborted. Each peer stores seq values of all the messages it has received (and processed) which are larger than max_received_seq - 64, where max_received_seq is the largest seq number received so far.

+

If a packet is received, the first message of which has a seq that is smaller or equal to max_received_seq - 64 or its seq had already been received, the message is discarded. Otherwise, the seq values of all incoming messages are memorized and max_received_seq is adjusted. This guarantees that no two packets will be processed twice.

+

Key Verification

+

To verify the key, and ensure that no MITM attack is taking place, both parties concatenate the secret key key with the value g_a of the Caller ( A ), compute SHA256 and use it to generate a sequence of emoticons. More precisely, the SHA256 hash is split into four 64-bit integers; each of them is divided by the total number of emoticons used (currently 333), and the remainder is used to select specific emoticons. The specifics of the protocol guarantee that comparing four emoticons out of a set of 333 is sufficient to prevent eavesdropping (MiTM attack on DH) with a probability of 0.9999999999.

+

This is because instead of the standard Diffie-Hellman key exchange which requires only two messages between the parties:

+
    +
  • A->B : (generates a and) sends g_a := g^a
  • +
  • B->A : (generates b and true key (g_a)^b, then) sends g_b := g^b
  • +
  • A : computes key (g_b)^a
  • +
+

we use a three-message modification thereof that works well when both parties are online (which also happens to be a requirement for voice calls):

+
    +
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • +
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • +
  • A->B : (computes key (g_b)^a, then) sends g_a := g^a
  • +
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • +
+

The idea here is that A commits to a specific value of a (and of g_a) without disclosing it to B. B has to choose its value of b and g_b without knowing the true value of g_a, so that it cannot try different values of b to force the final key (g_a)^b to have any specific properties (such as fixed lower 32 bits of SHA256(key)). At this point, B commits to a specific value of g_b without knowing g_a. Then A has to send its value g_a; it cannot change it even though it knows g_b now, because the other party B would accept only a value of g_a that has a hash specified in the very first message of the exchange.

+

If some impostor is pretending to be either A or B and tries to perform a Man-in-the-Middle Attack on this Diffie--Hellman key exchange, the above still holds. Party A will generate a shared key with B -- or whoever pretends to be B -- without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a. The same is valid for the key generation between the impostor and the party B.

+

The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.

+
+

For a slightly more user-friendly explanation of the above see: How are calls authenticated?

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/end-to-end/voice-calls.html b/data/corefork.telegram.org/api/end-to-end/voice-calls.html new file mode 100644 index 0000000000..2743024d71 --- /dev/null +++ b/data/corefork.telegram.org/api/end-to-end/voice-calls.html @@ -0,0 +1,178 @@ + + + + + End-to-End Encrypted Voice Calls + + + + + + + + + + + + + +
+ +
+
+
+ +

End-to-End Encrypted Voice Calls

+ +
+

This document describes encryption in voice calls as implemented in Telegram apps with versions < 7.0. See this document for details on encryption used in voice and video calls in app versions released on August 14, 2020 and later.

+
+
Related articles
+

+ +

Establishing voice calls

+

Before a voice call is ready, some preliminary actions have to be performed. The calling party needs to contact the party to be called and check whether it is ready to accept the call. Besides that, the parties have to negotiate the protocols to be used, learn the IP addresses of each other or of the Telegram relay servers to be used (so-called reflectors), and generate a one-time encryption key for this voice call with the aid of Diffie--Hellman key exchange. All of this is accomplished in parallel with the aid of several Telegram API methods and related notifications. This document details the generation of the encryption key. Other negotiations will be eventually documented elsewhere.

+

Key Generation

+

The Diffie-Hellman key exchange, as well as the whole protocol used to create a new voice call, is quite similar to the one used for Secret Chats. We recommend studying the linked article before proceeding.

+

However, we have introduced some important changes to facilitate the key verification process. Below is the entire exchange between the two communicating parties, the Caller (A) and the Callee (B), through the Telegram servers (S).

+
    +
  • A executes messages.getDhConfig to find out the 2048-bit Diffie-Hellman prime p and generator g. The client is expected to check whether p is a safe prime and perform all the security checks necessary for secret chats.
  • +
  • A chooses a random value of a, 1 < a < p-1, and computes g_a:=power(g,a) mod p (a 256-byte number) and g_a_hash:=SHA256(g_a) (32 bytes long).
  • +
  • A invokes (sends to server S) phone.requestCall, which has the field g_a_hash:bytes, among others. For this call, this field is to be filled with g_a_hash, not g_a itself.
  • +
  • The Server S performs privacy checks and sends an updatePhoneCall update with a phoneCallRequested constructor to all of B's active devices. This update, apart from the identity of A and other relevant parameters, contains the g_a_hash field, filled with the value obtained from A.
  • +
  • B accepts the call on one of their devices, stores the received value of g_a_hash for this instance of the voice call creation protocol, chooses a random value of b, 1 < b < p-1, computes g_b:=power(g,b) mod p, performs all the required security checks, and invokes the phone.acceptCall method, which has a g_b:bytes field (among others), to be filled with the value of g_b itself (not its hash).
  • +
  • The Server S sends an updatePhoneCall with the phoneCallDiscarded constructor to all other devices B has authorized, to prevent accepting the same call on any of the other devices. From this point on, the server S works only with that of B's devices which has invoked phone.acceptCall first.
  • +
  • The Server S sends to A an updatePhoneCall update with phoneCallAccepted constructor, containing the value of g_b received from B.
  • +
  • A performs all the usual security checks on g_b and a, computes the Diffie--Hellman key key:=power(g_b,a) mod p and its fingerprint key_fingerprint:long, equal to the lower 64 bits of SHA1(key), the same as with secret chats. Then A invokes the phone.confirmCall method, containing g_a:bytes and key_fingerprint:long.
  • +
  • The Server S sends to B an updatePhoneCall update with the phoneCall constructor, containing the value of g_a in g_a_or_b:bytes field, and key_fingerprint:long
  • +
  • At this point B receives the value of g_a. It checks that SHA256(g_a) is indeed equal to the previously received value of g_a_hash, performs all the usual Diffie-Hellman security checks, and computes the key key:=power(g_a,b) mod p and its fingerprint, equal to the lower 64 bits of SHA1(key). Then it checks that this fingerprint equals the value of key_fingerprint:long received from the other side, as an implementation sanity check.
  • +
+

At this point, the Diffie--Hellman key exchange is complete, and both parties have a 256-byte shared secret key key which is used to encrypt all further exchanges between A and B.

+

It is of paramount importance to accept each update only once for each instance of the key generation protocol, discarding any duplicates or alternative versions of already received and processed messages (updates).

+

Encryption of voice data

+

Both parties A (the Caller) and B (the Callee) transform the voice information into a sequence of small chunks or packets, not more than 1 kilobyte each. This information is to be encrypted using the shared key key generated during the initial exchange, and sent to the other party, either directly (P2P) or through Telegram's relay servers (so-called reflectors). This document describes only the encryption process for each chunk, leaving out voice encoding and the network-dependent parts.

+

Encapsulation of low-level voice data

+

The low-level data chunk raw_data:string, obtained from voice encoder, is first encapsulated into one of the two constructors for the DecryptedDataBlock type, similar to DecryptedMessage used in secret chats:

+
decryptedDataBlock#dbf948c1 random_id:long random_bytes:string flags:# voice_call_id:flags.2?int128 in_seq_no:flags.4?int out_seq_no:flags.4?int recent_received_mask:flags.5?int proto:flags.3?int extra:flags.1?string raw_data:flags.0?string = DecryptedDataBlock;
+simpleDataBlock#cc0d0e76 random_id:long random_bytes:string raw_data:string = DecryptedDataBlock;
+

Here out_seq_no is the chunk's sequence number among all sent by this party (starting from one), in_seq_no -- the highest known out_seq_no from the received packets. The parameter recent_received_mask is a 32-bit mask, used to track delivery of the last 32 packets sent by the other party. The bit i is set if a packet with out_seq_no equal to in_seq_no-i has been received.

+

The higher 8 bits in flags are reserved for use by the lower-level protocol (the one which generates and interprets raw_data), and will never be used for future extensions of decryptedDataBlock.

+

The parameters voice_call_id and proto are mandatory until the other side confirms reception of at least one packet by sending a packet with a non-zero in_seq_no. After that, they become optional, and the simpleDataBlock constructor can be used if the lower level protocol wants to.

+

The parameter voice_call_id is computed from the key key and equals the lower 128 bits of its SHA-256.

+

The random_bytes string should contain at least 7 bytes of random data. The field random_id also contains 8 random bytes, which can be used as a unique packet identifier if necessary.

+

MTProto encryption

+

Once the data is encapsulated in DecryptedDataBlock, it is TL-serialized and encrypted with MTProto, using key instead of auth_key; the parameter x is to be set to 0 for messages from A to B, and to 8 for messages in the opposite direction. Encrypted data are prepended by the 128-bit msg_key (usual for MTProto); before that, either the 128-bit voice_call_id (if P2P is used) or the peer_tag (if reflectors are used) is prepended. The resulting data packet is sent by UDP either directly to the other party (if P2P is possible) or to the Telegram relay servers (reflectors).

+

Key Verification

+

To verify the key, both parties concatenate the secret key key with the value g_a of the Caller ( A ), compute SHA256 and use it to generate a sequence of emoticons. More precisely, the SHA256 hash is split into four 64-bit integers; each of them is divided by the total number of emoticons used (currently 333), and the remainder is used to select specific emoticons. The specifics of the protocol guarantee that comparing four emoticons out of a set of 333 is sufficient to prevent eavesdropping (MiTM attack on DH) with a probability of 0.9999999999.

+

This is because instead of the standard Diffie-Hellman key exchange which requires only two messages between the parties:

+
    +
  • A->B : (generates a and) sends g_a := g^a
  • +
  • B->A : (generates b and true key (g_a)^b, then) sends g_b := g^b
  • +
  • A : computes key (g_b)^a
  • +
+

we use a three-message modification thereof that works well when both parties are online (which also happens to be a requirement for voice calls):

+
    +
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • +
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • +
  • A->B : (computes key (g_b)^a, then) sends g_a := g^a
  • +
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • +
+

The idea here is that A commits to a specific value of a (and of g_a) without disclosing it to B. B has to choose its value of b and g_b without knowing the true value of g_a, so that it cannot try different values of b to force the final key (g_a)^b to have any specific properties (such as fixed lower 32 bits of SHA256(key)). At this point, B commits to a specific value of g_b without knowing g_a. Then A has to send its value g_a; it cannot change it even though it knows g_b now, because the other party B would accept only a value of g_a that has a hash specified in the very first message of the exchange.

+

If some impostor is pretending to be either A or B and tries to perform a Man-in-the-Middle Attack on this Diffie--Hellman key exchange, the above still holds. Party A will generate a shared key with B -- or whoever pretends to be B -- without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a. The same is valid for the key generation between the impostor and the party B.

+

The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.

+
+

For a slightly more user-friendly explanation of the above see: How are calls authenticated?

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/end-to-end_v1.html b/data/corefork.telegram.org/api/end-to-end_v1.html new file mode 100644 index 0000000000..6cd75973a3 --- /dev/null +++ b/data/corefork.telegram.org/api/end-to-end_v1.html @@ -0,0 +1,225 @@ + + + + + Secret chats, end-to-end encryption (v. 1.0, DEPRECATED) + + + + + + + + + + + + + +
+ +
+
+
+ +

Secret chats, end-to-end encryption (v. 1.0, DEPRECATED)

+ +
+

This document describes end-to-end encrypted Secret Chats in MTProto 1.0, its status is DEPRECATED. +For information on end-to-end encryption used in up-to-date Telegram clients, kindly see this document.

+
+
Related articles
+

+
+

Secret Chats are one-on-one chats wherein messages are encrypted with a key held only by the chat’s participants. Please note that the schema for end-to-end encrypted Secret Chats is different from what is used for cloud chats:

+
+ +
+

Key Generation

+

The Diffie-Hellman protocol is used for key generation. For more information, see Wikipedia.

+

Let us consider the following scenario: User A would like to initiate encrypted communication with User B.

+

Sending a Request

+

User A executes messages.getDhConfig to obtain the Diffie-Hellman parameters: a prime p, and a high order element g.

+

Executing this method before each new key generation procedure is of vital importance. It makes sense to cache the values of the parameters together with the version in order to avoid having to receive all of the values every time. If the version stored on the client is still up-to-date, the server will return the constructor messages.dhConfigNotModified.

+

Client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

+

If the client has an inadequate random number generator, it makes sense to pass the random_length parameter (random_length> 0) so the server generates its own random sequence random of the appropriate length. +Important: using the server’s random sequence in its raw form may be unsafe. It must be combined with a client sequence, for example, by generating a client random number of the same length (client_random) and using final_random := random XOR client_random.

+

Client A computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and executes messages.requestEncryption after passing in g_a := pow(g, a) mod dh_prime.

+

User B receives the update updateEncryption for all associated authorization keys (all authorized devices) with the chat constructor encryptedChatRequested. The user must be shown basic information about User A and must be prompted to accept or reject the request.

+

Both clients are to check that g, g_a and g_b are greater than one and smaller than p-1. We recommend checking that g_a and g_b are between 2^{2048-64} and p - 2^{2048-64} as well.

+

Accepting a Request

+

After User B confirms the creation of a secret chat with A in the client interface, Client B also receives up-to-date configuration parameters for the Diffie-Hellman method. Thereafter, it generates a random 2048-bit number, b, using rules similar to those for a.

+

Having received g_a from the update with encryptedChatRequested, it can immediately generate the final shared key: key = (pow(g_a, b) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. Its fingerprint, key_fingerprint, is equal to the 64 last bits of SHA1 (key).

+

Note: this fingerprint is used as a sanity check for the key exchange procedure to detect bugs while developing client software — it is not connected to the key visualization used on the clients as means of external authentication in secret chats. Key visualizations on the clients are generated using the first 128 bits of SHA1(initial key) followed by the first 160 bits of SHA256(key used when secret chat was updated to layer 46).

+

Client B executes messages.acceptEncryption after passing it g_b := pow(g, b) mod dh_prime and key_fingerprint.

+

For all of Client B’s authorized devices, except the current one, updateEncryption updates are sent with the constructor encryptedChatDiscarded. Thereafter, the only device that will be able to access the secret chat is Device B, which made the call to messages.acceptEncryption.

+

User A will be sent an updateEncryption update with the constructor encryptedChat, for the authorization key that initiated the chat.

+

With g_b from the update, Client A can also receive the shared key key = (pow(g_b, a) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. If the fingerprint for the received key is identical to the one that was passed to encryptedChat, incoming messages can be sent and processed. Otherwise, messages.discardEncryption must be executed and the user notified.

+

Perfect Forward Secrecy

+

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

+
+

The re-keying protocol is further described in this article: Perfect Forward Secrecy in Secret Chats.

+
+

Please note that your client must support Forward Secrecy in Secret Chats to be compatible with official Telegram clients.

+

Sending and Receiving Messages in a Secret Chat

+

Serialization and Encryption of Outgoing Messages

+

A TL object of type DecryptedMessage is created and contains the message in plain text. For backward compatibility, the object must be wrapped in the constructor decryptedMessageLayer with an indication of the supported layer (starting with 8). +The TL-Schema for end-to-end encrypted messages contents is represented here ».

+

The resulting construct is serialized as an array of bytes using generic TL rules. The resulting array is padded at the top with 4 bytes of the array length not counting these 4 bytes. +A message key, msg_key, is computed as the 128 low-order bits of the SHA1 of the data obtained in the previous step. +The byte array is padded with random data until its length is divisible by 16 bytes. +An AES key and an initialization vector are computed ( key is the shared key obtained during Key Generation; in MTProto 1.0, x = 0 ):

+
    +
  • msg_key = substr (SHA1 (plaintext), 4, 16);
  • +
  • sha1_a = SHA1 (msg_key + substr (key, x, 32));
  • +
  • sha1_b = SHA1 (substr (key, 32+x, 16) + msg_key + substr (key, 48+x, 16));
  • +
  • sha1_с = SHA1 (substr (key, 64+x, 32) + msg_key);
  • +
  • sha1_d = SHA1 (msg_key + substr (key, 96+x, 32));
  • +
  • aes_key = substr (sha1_a, 0, 8) + substr (sha1_b, 8, 12) + substr (sha1_c, 4, 12);
  • +
  • aes_iv = substr (sha1_a, 8, 12) + substr (sha1_b, 0, 8) + substr (sha1_c, 16, 4) + substr (sha1_d, 0, 8);
  • +
+

Data is encrypted with a 256-bit key, aes_key, and a 256-bit initialization vector, aes-iv, using AES-256 encryption with infinite garble extension (IGE). Encryption key fingerprint key_fingerprint and the message key msg_key are added at the top of the resulting byte array.

+

Encrypted data is embedded into a messages.sendEncrypted API call and passed to Telegram server for delivery to the other party of the Secret Chat.

+

Decrypting an Incoming Message

+

The steps above are performed in reverse order. +When an encrypted message is received, you must check that msg_key is in fact equal to the 128 low-order bits of the SHA1 hash of the decrypted message. +If the message layer is greater than the one supported by the client, the user must be notified that the client version is out of date and prompted to update.

+

Sequence numbers

+

It is necessary to interpret all messages in their original order to protect against possible manipulations. Secret chats support a special mechanism for handling seq_no counters independently from the server.

+
+

Proper handling of these counters is further described in this article: Sequence numbers in Secret Chats.

+
+

Please note that your client must support sequence numbers in Secret Chats to be compatible with official Telegram clients.

+

Sending Encrypted Files

+

All files sent to secret chats are encrypted with one-time keys that are in no way related to the chat’s shared key. Before an encrypted file is sent, it is assumed that the encrypted file’s address will be attached to the outside of an encrypted message using the file parameter of the messages.sendEncryptedFile method and that the key for direct decryption will be sent in the body of the message (the key parameter in the constructors decryptedMessageMediaPhoto, decryptedMessageMediaVideo and decryptedMessageMediaFile.

+

Prior to a file being sent to a secret chat, 2 random 256-bit numbers are computed which will serve as the AES key and initialization vector used to encrypt the file. AES-256 encryption with infinite garble extension (IGE) is used in like manner.

+

The key fingerprint is computed as follows:

+
    +
  • digest = md5(key + iv)
  • +
  • fingerprint = substr(digest, 0, 4) XOR substr(digest, 4, 4)
  • +
+

The encrypted contents of a file are stored on the server in much the same way as those of a file in cloud chats: piece by piece using calls to upload.saveFilePart. +A subsequent call to messages.sendEncryptedFile will assign an identifier to the stored file and send the address together with the message. The recipient will receive an update with encryptedMessage, and the file parameter will contain file information.

+

Incoming and outgoing encrypted files can be forwarded to other secret chats using the constructor inputEncryptedFile to avoid saving the same content on the server twice.

+

Working with an Update Box

+

Secret chats are associated with specific devices (or rather with authorization keys), not users. A conventional message box, which uses pts to describe the client’s status, is not suitable, because it is designed for long-term message storage and message access from different devices.

+

An additional temporary message queue is introduced as a solution to this problem. When an update regarding a message from a secret chat is sent, a new value of qts is sent, which helps reconstruct the difference if there has been a long break in the connection or in case of loss of an update.

+

As the number of events increases, the value of qts increases monotonically (not always by 1). The initial value may not (and will not) be equal to 0.

+

The fact that events from the temporary queue have been received and stored by the client is acknowledged explicitly by a call to the messages.receivedQueue method or implicitly by a call to updates.getDifference (the value of qts passed, not the final state). All messages acknowledged as delivered by the client, as well as any messages older than 7 days, may (and will) be deleted from the server.

+

Upon de-authorization, the event queue of the corresponding device will be forcibly cleared, and the value of qts will become irrelevant.

+

Updating to new layers

+

Your client should always store the maximal layer that is known to be supported by the client on the other side of a secret chat. When the secret chat is first created, this value should be initialized to 8, the first layer where Secret Chats became available. This remote layer value must always be updated immediately after receiving any packet containing information of an upper layer, i.e.:

+
    +
  • any secret chat message containing layer_no in its decryptedMessageLayer with layer>=17, or
  • +
  • a decryptedMessageActionNotifyLayer service message, wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d).
  • +
+

Notifying the remote client about your local layer

+

In order to notify the remote client of your local layer, your client must send a message of the decryptedMessageActionNotifyLayer type. This notification must be wrapped in a constructor of an appropriate layer. For instance, if the remote layer for the chat in question is deemed to be lower than 17, the notification must be wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d), despite the fact that the decryptedMessageActionNotifyLayer constructor is actually not present in Layer 8.

+

There are three cases when your client must notify the remote client about its local layer:

+
    +
  1. As soon as a new secret chat has been created, immediately after the secret key has been successfully exchanged.
  2. +
  3. Immediately after the remote layer value is updated to layer 17 or higher. An exception to this case is when the secret chat in question has been created less than 15 seconds ago. In this case the notification was already sent (see 1).
  4. +
  5. Immediately after the local client has been updated to support a new secret chat layer. In this case notifications must be sent to all currently existing secret chats. Note that this is only necessary when updating to new layers that contain changes in the secret chats implementation (e.g. you don’t need to do this when your client is updated from Layer 17 to Layer 18).
  6. +
+
+

Note that all pending obsolete layer messages must be sent prior to the layer update notification (more on this in Handling Sequence numbers).

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/entities.html b/data/corefork.telegram.org/api/entities.html new file mode 100644 index 0000000000..9548e5d616 --- /dev/null +++ b/data/corefork.telegram.org/api/entities.html @@ -0,0 +1,137 @@ + + + + + Styled text with message entities + + + + + + + + + + + + + +
+ +
+
+
+ +

Styled text with message entities

+ +

Telegram supports styled text using message entities.

+

A client that wants to send styled messages would simply have to integrate a Markdown/HTML parser, and generate an array of message entities by iterating through the parsed tags.

+

Special care must be taken to consider the UTF-8 length of strings when generating message entities, see example implementations: tdlib, MadelineProto.

+

Nested entities are supported.
+For example the following HTML/Markdown aliases for message entities can be used:

+ +
+```c++
+code
+```
+
+

The following entities can also be used to mention users:

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/errors.html b/data/corefork.telegram.org/api/errors.html new file mode 100644 index 0000000000..a7f8aeec7d --- /dev/null +++ b/data/corefork.telegram.org/api/errors.html @@ -0,0 +1,189 @@ + + + + + Error handling + + + + + + + + + + + + + +
+ +
+
+
+ +

Error handling

+ +

There will be errors when working with the API, and they must be correctly handled on the client.

+

An error is characterized by several parameters:

+

Error Code

+

Numerical value similar to HTTP status. Contains information on the type of error that occurred: for example, a data input error, privacy error, or server error. This is a required parameter.

+

Error Type

+

A string literal in the form of /[A-Z_0-9]+/, which summarizes the problem. For example, AUTH_KEY_UNREGISTERED. This is an optional parameter.

+
+

Error Constructors

+

There should be a way to handle errors that are returned in rpc_error constructors.

+

Below is a list of error codes and their meanings:

+

303 SEE_OTHER

+

The request must be repeated, but directed to a different data center.

+

Examples of Errors:

+
    +
  • FILE_MIGRATE_X: the file to be accessed is currently stored in a different data center.
  • +
  • PHONE_MIGRATE_X: the phone number a user is trying to use for authorization is associated with a different data center.
  • +
  • NETWORK_MIGRATE_X: the source IP address is associated with a different data center (for registration)
  • +
  • USER_MIGRATE_X: the user whose identity is being used to execute queries is associated with a different data center (for registration)
  • +
+

In all these cases, the error description’s string literal contains the number of the data center (instead of the X) to which the repeated query must be sent. +More information about redirects between data centers »

+

400 BAD_REQUEST

+

The query contains errors. In the event that a request was created using a form and contains user generated data, the user should be notified that the data must be corrected before the query is repeated.

+

Examples of Errors:

+
    +
  • FIRSTNAME_INVALID: The first name is invalid
  • +
  • LASTNAME_INVALID: The last name is invalid
  • +
  • PHONE_NUMBER_INVALID: The phone number is invalid
  • +
  • PHONE_CODE_HASH_EMPTY: phone_code_hash is missing
  • +
  • PHONE_CODE_EMPTY: phone_code is missing
  • +
  • PHONE_CODE_EXPIRED: The confirmation code has expired
  • +
  • API_ID_INVALID: The api_id/api_hash combination is invalid
  • +
  • PHONE_NUMBER_OCCUPIED: The phone number is already in use
  • +
  • PHONE_NUMBER_UNOCCUPIED: The phone number is not yet being used
  • +
  • USERS_TOO_FEW: Not enough users (to create a chat, for example)
  • +
  • USERS_TOO_MUCH: The maximum number of users has been exceeded (to create a chat, for example)
  • +
  • TYPE_CONSTRUCTOR_INVALID: The type constructor is invalid
  • +
  • FILE_PART_INVALID: The file part number is invalid
  • +
  • FILE_PARTS_INVALID: The number of file parts is invalid
  • +
  • FILE_PART_Х_MISSING: Part X (where X is a number) of the file is missing from storage
  • +
  • MD5_CHECKSUM_INVALID: The MD5 checksums do not match
  • +
  • PHOTO_INVALID_DIMENSIONS: The photo dimensions are invalid
  • +
  • FIELD_NAME_INVALID: The field with the name FIELD_NAME is invalid
  • +
  • FIELD_NAME_EMPTY: The field with the name FIELD_NAME is missing
  • +
  • MSG_WAIT_FAILED: A request that must be completed before processing the current request returned an error
  • +
  • MSG_WAIT_TIMEOUT: A request that must be completed before processing the current request didn't finish processing yet
  • +
+

401 UNAUTHORIZED

+

There was an unauthorized attempt to use functionality available only to authorized users.

+

Examples of Errors:

+
    +
  • AUTH_KEY_UNREGISTERED: The key is not registered in the system
  • +
  • AUTH_KEY_INVALID: The key is invalid
  • +
  • USER_DEACTIVATED: The user has been deleted/deactivated
  • +
  • SESSION_REVOKED: The authorization has been invalidated, because of the user terminating all sessions
  • +
  • SESSION_EXPIRED: The authorization has expired
  • +
  • AUTH_KEY_PERM_EMPTY: The method is unavailble for temporary authorization key, not bound to permanent
  • +
+

403 FORBIDDEN

+

Privacy violation. For example, an attempt to write a message to someone who has blacklisted the current user.

+

404 NOT_FOUND

+

An attempt to invoke a non-existent object, such as a method.

+

406 NOT_ACCEPTABLE

+

Similar to 400 BAD_REQUEST, but the app should not display any error messages to user in UI as a result of this response. The error message will be delivered via updateServiceNotification instead.

+

420 FLOOD

+

The maximum allowed number of attempts to invoke the given method with the given input parameters has been exceeded. For example, in an attempt to request a large number of text messages (SMS) for the same phone number.

+

Error Example:

+
    +
  • FLOOD_WAIT_X: A wait of X seconds is required (where X is a number)
  • +
+

500 INTERNAL

+

An internal server error occurred while a request was being processed; for example, there was a disruption while accessing a database or file storage.

+

If a client receives a 500 error, or you believe this error should not have occurred, please collect as much information as possible about the query and error and send it to the developers.

+

Other Error Codes

+

If a server returns an error with a code other than the ones listed above, it may be considered the same as a 500 error and treated as an internal server error.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/file_reference.html b/data/corefork.telegram.org/api/file_reference.html new file mode 100644 index 0000000000..10f025ba7b --- /dev/null +++ b/data/corefork.telegram.org/api/file_reference.html @@ -0,0 +1,125 @@ + + + + + File references + + + + + + + + + + + + + +
+ +
+
+
+ +

File references

+ +

File references are strings of bytes, that can be encountered in the file_reference fields of document and photo objects.

+

They must be cached by the client, along with the origin context where the document/photo object was found, in order to be refetched when the file reference expires.

+

Example implementation of a reference database: MadelineProto, android, telegram desktop, tdlib.

+

Another example:

+

Assume you receive a message from your friend: that message contains a messageMediaPhoto with a photo.

+

Your client has to cache not only the file_reference field of the photo, but also the context in which the file reference was seen (in this case, a message coming from a specific user).

+

The context info is in this case, an origin context of type message, containing the message ID and the peer ID of the chat/channel/user where the message was seen.

+

The context info has to be associated with the file reference: when downloading a file using upload.getFile, a FILE_REFERENCE_EXPIRED error (or another error starting with FILE_REFERENCE_) may be returned.
+If this happens, the context info must be used to refetch the object that contained the file reference: in this example, the peer info and the message ID have to be used with channels.getMessages or messages.getMessages to refetch the message, recache the file reference and use it in a new file download request.

+

More than one origin context can be associated to one file reference, for greater resilience (in the case of a message that was deleted in one chat but was also forwarded in another chat, the file reference can be refetched from the second chat, instead).

+

Origin contexts for objects returned by method calls with certain parameters can be considered, too (for example, in the case of favorited sticker sets returned by messages.getFavedStickers).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/files.html b/data/corefork.telegram.org/api/files.html new file mode 100644 index 0000000000..5cb328b3b2 --- /dev/null +++ b/data/corefork.telegram.org/api/files.html @@ -0,0 +1,568 @@ + + + + + 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/geochats.html b/data/corefork.telegram.org/api/geochats.html new file mode 100644 index 0000000000..ca5cba3792 --- /dev/null +++ b/data/corefork.telegram.org/api/geochats.html @@ -0,0 +1,115 @@ + + + + + Nope + + + + + + + + + + + + + +
+ +
+
+
+ +

Nope

+ +

Deprecated old docs. This was definitely not the droid you were looking for.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/import.html b/data/corefork.telegram.org/api/import.html new file mode 100644 index 0000000000..8ebb0f6140 --- /dev/null +++ b/data/corefork.telegram.org/api/import.html @@ -0,0 +1,173 @@ + + + + + Imported messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Imported messages

+ +
+ +

Telegram allows importing messages and media from foreign chat apps.

+
+

Note: This article is intended for MTProto API developers. If you're looking for a way to move history from other chat apps into Telegram, check out the related Telegram blog post.

+
+

1. Validate the chat export file

+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+
+---functions---
+
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;
+

The import process begins by calling messages.checkHistoryImport, passing to import_head up to 100 lines of the chat export file, starting from the beginning of the file.

+

The returned constructor contains information about the exported chat, including its title or type. +If the pm flag is set, the chat export file was generated from a private chat. +If the group flag is set, the chat export file was generated from a group chat. +If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

+

2. Choosing a destination Telegram chat

+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+
+---functions---
+
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;
+

Using messages.checkHistoryImportPeer, check whether chat history exported from another chat app can be imported into a specific Telegram peer, chosen by the user.
+Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

+

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user in a confirmation prompt.
+Upon final user confirmation, the import process is initialized.

+

3. Initialize the import

+
messages.historyImport#1662af0b id:long = messages.HistoryImport;
+
+---functions---
+
+messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;
+

Use messages.initHistoryImport to initialize the import process, passing the following parameters:

+
    +
  • peer - The Telegram chat where the history should be imported.
  • +
  • file - The chat export file.
  • +
  • media_count - The number of media files associated with the export, to be uploaded in the next step.
  • +
+

4. Uploading media

+
---functions---
+
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;
+

Use messages.uploadImportedMedia to upload media files eventually associated with the chat export.
+import_id is the id contained in the messages.historyImport constructor, returned by messages.initHistoryImport in the previous step.

+

5. Finalize the import

+
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
+
+---functions---
+
+messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
+

Finally, invoke messages.startHistoryImport to complete the history import process, importing all messages into the chat.
+As usual, import_id is the id contained in the messages.historyImport constructor, returned by messages.initHistoryImport.

+

Imported messages will show in the chat history as messages containing a fwd_from messageFwdHeader constructor with the imported flag, and should be appropriately marked in the UI as messages imported from a foreign chat app.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/invoking.html b/data/corefork.telegram.org/api/invoking.html new file mode 100644 index 0000000000..1095dbc4d0 --- /dev/null +++ b/data/corefork.telegram.org/api/invoking.html @@ -0,0 +1,154 @@ + + + + + Calling API Methods + + + + + + + + + + + + + +
+ +
+
+
+ +

Calling API Methods

+ +
+ +

Layers

+

Versioning in the API is supported by so-called TL layers.

+

The need to add a new object constructor or to add/remove a field in a constructor creates a backwards compatibility problem for previous versions of API clients. After all, simply changing a constructor in a schema also changes its number. To address this problem, each schema update is separated into a layer.

+

A layer is a collection of updated methods or constructors in a TL schema. Each layer is numbered with sequentially increasing numbers starting with 2. The first layer is the base layer -- the TL schema without any changes.

+

There is a helper method to let the API know that a client supports the Layer layer:

+
invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;
+

The helper method invokeWithLayer can be used only together with initConnection: the present layer will be saved with all other parameters of the client and any future requests will be using this saved value. See more below.

+

List of Available Layers

+

Saving Client Info

+

It is possible to save information about the current client on the server in conjunction with an authorization key. This may help eliminate client-side problems with certain releases on certain devices or with certain localizations, as well as eliminate the need for sending layer information in each request.

+

The helper method initConnection accepts client parameters. This method must be called when first calling the API after the application has restarted or in case the value of one of the parameters could have changed.

+

initConnection must also be called after each auth.bindTempAuthKey.

+

When calling this method, the current layer used by the client is also saved (the layer in which initConnection was wrapped is used). After a successful call to initConnection it is no longer necessary to wrap each API call in invokeWithLayerN.

+

Disabling updates

+
invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;
+

invokeWithoutUpdates can be used to invoke a request without subscribing the used connection for updates (this is enabled by default for file queries).

+

Sequential Requests

+

By default, the server processes parallel requests in arbitrary order. Two helper methods exist for cases when the client needs certain requests to be processed in a certain order and intends to send a new request before the previous one is completed:

+
+

invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
+invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector query:!X = X;

+
+

They may be used, for example, when a client attempts to send messages that accumulated while waiting for the Internet connection to be restored for a long time. In this case, the 32-bit number 0xcb9f372d must be added before the method number in each request, followed by a 64-bit message identifier, msg_id, which contains the previous request in the queue.

+

The second method is similar, except it takes several messages that must be successfully processed before the current one.

+

If the waiting period exceeds 0.5 seconds (this value may change in the future) and no result has appeared, the method will return the 400 MSG_WAIT_TIMEOUT error.

+

Helper Method Sequence

+

Important: if the helper methods invokeAfterMsg / invokeAfterMsgs are used together with invokeWithLayerN or other helper methods, invokeAfterMsg / invokeAfterMsgs must always be the outermost wrapper.

+

Data Compression

+

We recommend using gzip compression when calling methods to reduce the amount of network traffic.

+

The schema and constructor information are given in the protocol documentation.

+

Data Compression when Making a Request

+

Before transmitting a query, the string containing the entire body of the serialized high-level query (starting with the method number) must be compressed using gzip. If the resulting string is smaller than the original, it makes sense to transmit the gzip_packed constructor.

+

There is no point in doing the above when transmitting binary multimedia data (photos, videos) or small messages (up to 255 bytes).

+

Uncompressing Data

+

By default, the server compresses the response to any request as well as updates, in accordance with the rules stated above. If the gzip_packed constructor is received as a response in rpc_result, then the string that follows must be extracted and uncompressed. Processing then continues on the resulting new string.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/layers.html b/data/corefork.telegram.org/api/layers.html new file mode 100644 index 0000000000..8f2254a383 --- /dev/null +++ b/data/corefork.telegram.org/api/layers.html @@ -0,0 +1,2499 @@ + + + + + Layers + + + + + + + + + + + + + +
+ +
+
+
+ +

Layers

+ +
+ +

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+

Layer 133

+

Group message receipts, animated emoji reactions » and switch to 64-bit identifiers for users, groups, supergroups and channels.

+

Over 160 constructors and methods were changed, changing parameter types from int to long, including user, chat and channel: the full changelog is elided for space reasons.
You can visit the schema for an updated list of constructors.

+

Also note that the hashing algorithm for pagination was also changed to account for 64-bit IDs.

+

Changes

+ +

Layer 132

+

Chat themes and sponsored messages, save video recordings of group calls and livestreams.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+
    +
  • Added theme_emoticon parameter in chatFull
  • +
  • Added theme_emoticon parameter in userFull
  • +
  • Added theme_emoticon parameter in channelFull
  • +
  • Added for_chat parameter, changed type of installs_count from int to flags.4?int in theme
  • +
  • Added message_colors_animated, message_colors parameters, removed message_top_color, message_bottom_color parameters in inputThemeSettings
  • +
  • Added message_colors_animated, message_colors parameters, removed message_top_color, message_bottom_color parameters in themeSettings
  • +
  • Added unread_count parameter in messages.discussionMessage
  • +
  • Added flags, video_channel, video_quality parameters in inputGroupCallStream
  • +
+

Schema

+
chatFull#49a0a5d9 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int 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;\
+
+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;\
+
+channelFull#2f532f3c 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:int 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?int 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?int 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;\
+
+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;\
+
+inputThemeSettings#ff38f912 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;\
+
+themeSettings#8db4e76c flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;\
+
+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;\
+
+inputGroupCallStream#0598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;\
+
+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;\
+
+messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;\
+
+sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
+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---\
+
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;\
+
+account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;\
+
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;\
+
+channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;\
+
+ + + +

Layer 131

+

2FA password reset for logged-in accounts, add a method to check the validity of the e-mail recovery code before use.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;\
+
+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;
+groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;\
+
+account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;\
+
+updateBotCommands#cf7e0873 peer:Peer bot_id:int commands:Vector<BotCommand> = Update;\
+
+---functions---\
+
+auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;\
+
+phone.getGroupCall#041845db call:InputGroupCall limit:int = phone.GroupCall;\
+
+account.resetPassword#9308ce1b = account.ResetPasswordResult;
+account.declinePasswordReset#4c9409f6 = Bool;
+auth.checkRecoveryPassword#0d36bf79 code:string = Bool;\
+
+ + + +

Layer 130

+

Custom placeholder for bot reply keyboards.

+

Schema changes

+
Changed Constructors
+ +

Schema

+
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;\
+
+ + + +

Layer 129

+

Group call screen sharing, short name suggestions for stickerpacks, scoped bot commands, imported stickers, wallpaper and group call improvements.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
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;\
+
+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;\
+
+inputWallPaperNoFile#967a462e id:long = InputWallPaper;\
+
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;\
+
+updateMessagePollVote#37f69f0b poll_id:long user_id:int options:Vector<bytes> qts:int = Update;\
+
+groupCall#653dbaad 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 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 version:int = GroupCall;
+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;
+groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;
+groupCallParticipantVideo#78e41663 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> = GroupCallParticipantVideo;\
+
+updateGroupCallConnection#0b783982 flags:# presentation:flags.0?true params:DataJSON = Update;\
+
+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#0a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;\
+
+---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;\
+
+bots.setBotCommands#0517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;\
+
+phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;
+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.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
+phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;\
+
+stickers.checkShortName#284b3639 short_name:string = Bool;
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;\
+
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
+bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;\
+
+ + + +

Layer 128

+

Deprecate legacy profile picture locations, group call improvements.
See the file documentation article for more info on the new file constructors ».

+

Schema changes

+
Changed Methods
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed fileLocationToBeDeprecated
  • +
+

Schema

+
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;\
+
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#021e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;\
+
+inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
+inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;\
+
+videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;\
+
+photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;\
+
+---functions---\
+
+phone.editGroupCallParticipant#aec610e4 flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_muted:flags.3?Bool = Updates;\
+
+ + + +

Layer 127

+

Scheduled group calls, payments in channels, payment tips, stripped profile picture thumbnails.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
userProfilePhoto#cc656077 flags:# has_video:flags.0?true photo_id:long photo_small:FileLocation photo_big:FileLocation stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;\
+
+chatPhoto#4790ee05 flags:# has_video:flags.0?true photo_small:FileLocation photo_big:FileLocation stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;\
+
+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;\
+
+invoice#0cd886e0 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;\
+
+payments.paymentForm#8d0b2415 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:int invoice:Invoice provider_id:int 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.paymentReceipt#10b555d0 flags:# date:int bot_id:int provider_id:int 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;\
+
+groupCall#c95c6654 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 id:long access_hash:long participants_count:int params:flags.0?DataJSON title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int version:int = GroupCall;
+groupCallParticipant#b96b25ee 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 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 params:flags.6?DataJSON = GroupCallParticipant;\
+
+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;\
+
+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;\
+
+messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;\
+
+---functions---\
+
+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;
+phone.createGroupCall#48cdc6d8 flags:# peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
+phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;\
+
+ + + +

Layer 126

+

Ban channels in chats.

+

Schema changes

+
Changed Methods
+ +
Changed Constructors
+ +

Schema

+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+channelParticipantBanned#50a1dfd6 flags:# left:flags.0?true peer:Peer kicked_by:int date:int banned_rights:ChatBannedRights = ChannelParticipant;
+channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;\
+
+---functions---\
+
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;
+channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;\
+
+ + + +

Layer 125

+

Voice chats in channels.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
Deleted Methods
+
    +
  • Removed phone.editGroupCallMember
  • +
+
New Constructors
+ +
Changed Constructors
+ +

Schema

+
chatFull#8a1e2983 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int 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 = ChatFull;\
+
+updateChatUserTyping#86cadb6c chat_id:int from_id:Peer action:SendMessageAction = Update;\
+
+channelFull#548c3f93 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:int 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?int 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?int 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 = ChatFull;\
+
+updateChannelUserTyping#6b171718 flags:# channel_id:int top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;\
+
+groupCall#c0c2052e flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true id:long access_hash:long participants_count:int params:flags.0?DataJSON title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int version:int = GroupCall;
+groupCallParticipant#19adba89 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 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 = 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;\
+
+inputGroupCallStream#bba51639 call:InputGroupCall time_ms:long scale:int = InputFileLocation;\
+
+phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;\
+
+---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;\
+
+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.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
+phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;
+phone.toggleGroupCallRecord#c02a66d7 flags:# start:flags.0?true call:InputGroupCall title:flags.1?string = Updates;
+phone.editGroupCallParticipant#d975eb80 flags:# muted:flags.0?true call:InputGroupCall participant:InputPeer volume:flags.1?int raise_hand:flags.2?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;\
+
+ + + +

Layer 124

+

Expiring invite links, self-destruction settings for all messages in a chat, gigagroups, chat import improvements.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
chatFull#f06c4018 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int 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 = ChatFull;\
+
+message#bce383d2 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?int 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;\
+
+inputReportReasonOther#c1e4a2b1 = ReportReason;\
+
+userFull#139a9a77 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 = UserFull;
+updateShortMessage#faeff833 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:int message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?int reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#1157b858 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:int chat_id:int message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?int reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;\
+
+channelFull#2548c037 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:int 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?int 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?int 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> = ChatFull;\
+
+messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;\
+
+updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
+updateChatParticipant#f3b3781f flags:# chat_id:int date:int actor_id:int user_id:int prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateChannelParticipant#7fecb1ec flags:# channel_id:int date:int actor_id:int user_id:int prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateBotStopped#07f9488a user_id:int date:int stopped:Bool qts:int = Update;\
+
+chatInviteImporter#1e3e6680 user_id:int 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#dfd2330f admin_id:int invites_count:int revoked_invites_count:int = ChatAdminWithInvites;\
+
+messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;\
+
+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;\
+
+messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;\
+
+---functions---\
+
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;\
+
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
+messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;\
+
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = 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#02e4ffbe 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;\
+
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;\
+
+channels.convertToGigagroup#0b290c69 channel:InputChannel = Updates;\
+
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;\
+
+ + + +

Layer 123

+

Import messages from foreign chat apps, delete history for both users upon deletion of a secret chat, delete phone call history, group call improvements.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+
    +
  • Changed type of exported_invite from ExportedChatInvite to flags.13?ExportedChatInvite in chatFull
  • +
  • Added flags, peer_id parameters in messageEmpty
  • +
  • Added flags, history_deleted parameters in encryptedChatDiscarded
  • +
  • Added flags, revoked, permanent, admin_id, date, start_date, expire_date, usage_limit, usage parameters in chatInviteExported
  • +
  • Added fake parameter in user
  • +
  • Added fake, gigagroup parameters in channel
  • +
  • Changed type of exported_invite from ExportedChatInvite to flags.23?ExportedChatInvite in channelFull
  • +
  • Added min, muted_by_you, volume_by_admin, volume parameters in groupCallParticipant
  • +
+
Deleted Constructors
+
    +
  • Removed chatInviteEmpty
  • +
  • Removed inputPaymentCredentialsAndroidPay
  • +
+

Schema

+
chatFull#f3474af6 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int 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 = ChatFull;\
+
+messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;\
+
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;\
+
+chatInviteExported#6e24fc9d flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:int date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;\
+
+user#938458c1 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:int 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;\
+
+channel#d31a961e 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 id:int access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int version: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;
+channelFull#7a7de4f7 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:int 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?int 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?int 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 = ChatFull;\
+
+groupCallParticipant#64c62a15 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 user_id:int date:int active_date:flags.3?int source:int volume:flags.7?int = GroupCallParticipant;\
+
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;\
+
+messages.historyImport#1662af0b id:long = messages.HistoryImport;\
+
+sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;\
+
+messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;\
+
+inputReportReasonFake#f5ddd6e7 = ReportReason;\
+
+messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;\
+
+---functions---\
+
+messages.deleteChatUser#c534459a flags:# revoke_history:flags.0?true chat_id:int user_id:InputUser = Updates;
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;\
+
+phone.editGroupCallMember#a5e76cd8 flags:# muted:flags.0?true call:InputGroupCall user_id:InputUser volume:flags.1?int = Updates;\
+
+messages.deleteChat#83247d11 chat_id:int = 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;\
+
+ + + +

Layer 122

+

Group calls.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed updateChannelParticipant
  • +
+

PUSH notification changes

+
New PUSH notifications
+ +
Changed PUSH notifications
+
    +
  • Changed template from {1} posted a map to {1} posted a location in CHANNEL_MESSAGE_GEO
  • +
  • Changed template from {1} posted a {2}sticker to {1} posted a {2} sticker in CHANNEL_MESSAGE_STICKER
  • +
  • Changed template from {1} kicked {3} from the group {2} to {1} removed {3} from the group {2} in CHAT_DELETE_MEMBER
  • +
  • Changed template from {1} kicked you from the group {2} to {1} removed you from the group {2} in CHAT_DELETE_YOU
  • +
  • Changed template from {1} has joined the group {2} to {1} joined the group {2} in CHAT_JOINED
  • +
  • Changed template from {1} has left the group {2} to {1} left the group {2} in CHAT_LEFT
  • +
  • Changed template from {1} invited the group {2} to play {3}. to {1} invited the group {2} to play {3} in CHAT_MESSAGE_GAME
  • +
  • Changed template from {1} sent a map to the group {2} to {1} sent a location to the group {2} in CHAT_MESSAGE_GEO
  • +
  • Changed template from {1} started sharing their live location with {2} to {1} shared a live location with the group {2} in CHAT_MESSAGE_GEOLIVE
  • +
  • Changed template from {1} sent a {3}sticker to the group {2} to {1} sent a {3} sticker to the group {2} in CHAT_MESSAGE_STICKER
  • +
  • Changed template from {1}@{2}: {3} to {1} @ {2}: {3} in CHAT_MESSAGE_TEXT
  • +
  • Changed template from {1} edited the group's {2} photo to {1} changed the group photo for {2} in CHAT_PHOTO_EDITED
  • +
  • Changed template from {1} has returned to the group {2} to {1} returned to the group {2} in CHAT_RETURNED
  • +
  • Changed template from {1} edited the group's {2} name to {1} renamed the group {2} in CHAT_TITLE_EDITED
  • +
  • Changed template from {1} sent you a map to {1} sent you a location in MESSAGE_GEO
  • +
  • Changed template from {1} started sharing their live location to {1} sent you a live location in MESSAGE_GEOLIVE
  • +
  • Changed template from {1} sent you a {2}sticker to {1} sent you a {2} sticker in MESSAGE_STICKER
  • +
  • Changed template from {1} pinned a {2}sticker to {1} pinned a {2} sticker in PINNED_STICKER
  • +
+

Schema

+
chat#3bda1bde 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 id:int 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;
+chatFull#0dc8c181 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:int about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall = ChatFull;\
+
+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;\
+
+inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;\
+
+stickerSet#40e237a8 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 count:int hash:int = StickerSet;\
+
+channel#d31a961e 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 id:int access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int version: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;
+channelFull#ef3a6acd 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:int 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:ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?int 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?int 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 = ChatFull;\
+
+updateBotInlineQuery#3f2038db flags:# query_id:long user_id:int query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;\
+
+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;\
+
+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;
+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;\
+
+speakingInGroupCallAction#d92c2285 = SendMessageAction;\
+
+groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
+groupCall#55903081 flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true id:long access_hash:long participants_count:int params:flags.0?DataJSON version:int = GroupCall;\
+
+inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;\
+
+messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
+messageActionInviteToGroupCall#76b9f11a call:InputGroupCall users:Vector<int> = MessageAction;\
+
+groupCallParticipant#56b087c9 flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true user_id:int date:int active_date:flags.3?int source:int = GroupCallParticipant;\
+
+updateChat#1330a196 chat_id:int = Update;
+updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
+updateGroupCall#a45eb99b chat_id:int call:GroupCall = Update;\
+
+phone.groupCall#66ab0bfc call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string users:Vector<User> = phone.GroupCall;
+phone.groupParticipants#9cfeb92d count:int participants:Vector<GroupCallParticipant> next_offset:string users:Vector<User> version:int = phone.GroupParticipants;\
+
+inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
+inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
+inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
+inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
+inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;\
+
+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;\
+
+---functions---\
+
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;\
+
+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;\
+
+phone.createGroupCall#bd3dabe0 peer:InputPeer random_id:int = Updates;
+phone.joinGroupCall#5f9c8e62 flags:# muted:flags.0?true call:InputGroupCall params:DataJSON = Updates;
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
+phone.editGroupCallMember#63146ae4 flags:# muted:flags.0?true call:InputGroupCall user_id:InputUser = Updates;
+phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
+phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
+phone.toggleGroupCallSettings#74bbb43d flags:# call:InputGroupCall join_muted:flags.0?Bool = Updates;
+phone.getGroupCall#0c7cb017 call:InputGroupCall = phone.GroupCall;
+phone.getGroupParticipants#c9f1d285 call:InputGroupCall ids:Vector<int> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;
+phone.checkGroupCall#b74a7bea call:InputGroupCall source:int = Bool;\
+
+ + + +

Layer 121

+

Added SVG path previews for animated stickers.

+

Schema changes

+
New Constructors
+
    +
  • Added photoPathSize - Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.
  • +
+

Schema

+
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;\
+
+ + + +

Layer 120

+

Added message statistics, and a method to unpin all pinned messages in a chat.

+

Schema changes

+
New Methods
+ +
Changed Methods
+
    +
  • Changed type of from_id from flags.0?InputUser to flags.0?InputPeer in messages.search
  • +
+
New Constructors
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed updateChannelPinnedMessage
  • +
  • Removed updateUserPinnedMessage
  • +
  • Removed updateChatPinnedMessage
  • +
+

PUSH notification changes

+
New PUSH notifications
+ +

Schema

+
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;\
+
+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;\
+
+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;\
+
+botInlineMessageMediaGeo#051846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;\
+
+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;\
+
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;\
+
+inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;\
+
+channelParticipantLeft#c3c6796b user_id:int = ChannelParticipant;
+channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;\
+
+updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
+updatePinnedChannelMessages#8588878b flags:# pinned:flags.0?true channel_id:int messages:Vector<int> pts:int pts_count:int = Update;\
+
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;\
+
+stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;\
+
+messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;\
+
+---functions---\
+
+messages.search#0c352eec 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:int = messages.Messages;\
+
+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;\
+
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;\
+
+ + + +

Layer 119

+

Added message threads and comment sections in channel posts.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+
    +
  • Added pinned, peer_id, reply_to, forwards, replies parameters, removed to_id, reply_to_msg_id parameters, changed type of from_id from flags.8?int to flags.8?Peer in message
  • +
  • Added peer_id, reply_to parameters, removed to_id, reply_to_msg_id parameters, changed type of from_id from flags.8?int to flags.8?Peer in messageService
  • +
  • Added chats parameter, changed type of blocked from Vector<ContactBlocked> to Vector<PeerBlocked> in contacts.blocked
  • +
  • Added chats parameter, changed type of blocked from Vector<ContactBlocked> to Vector<PeerBlocked> in contacts.blockedSlice
  • +
  • Added reply_to parameter, removed reply_to_msg_id parameter in updateShortMessage
  • +
  • Added reply_to parameter, removed reply_to_msg_id parameter in updateShortChatMessage
  • +
  • Added admin_rights parameter in channelParticipantCreator
  • +
  • Removed channel_id parameter, changed type of from_id from flags.0?int to flags.0?Peer in messageFwdHeader
  • +
+
Deleted Constructors
+
    +
  • Removed contactBlocked
  • +
  • Removed updateUserBlocked
  • +
+

Schema

+
message#58ae39c9 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?int 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> = Message;
+messageService#286fa604 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 = Message;\
+
+contacts.blocked#0ade1591 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;\
+
+updateShortMessage#2296d2c8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:int message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?int reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> = Updates;
+updateShortChatMessage#402d5dbb flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:int chat_id:int message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?int reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> = Updates;\
+
+channelParticipantCreator#447dca4b flags:# user_id:int admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;\
+
+messageFwdHeader#5f777dce flags:# 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;
+messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;\
+
+updateChannelMessageForwards#6e8a84df channel_id:int id:int forwards:int = Update;\
+
+photoSizeProgressive#5aa86a51 type:string location:FileLocation w:int h:int sizes:Vector<int> = PhotoSize;\
+
+messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;\
+
+updateReadChannelDiscussionInbox#1cc7de54 flags:# channel_id:int top_msg_id:int read_max_id:int broadcast_id:flags.0?int broadcast_post:flags.0?int = Update;
+updateReadChannelDiscussionOutbox#4638a26c channel_id:int top_msg_id:int read_max_id:int = Update;\
+
+messages.discussionMessage#f5dd8f9d flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?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#4128faac flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?int max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;\
+
+updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;\
+
+peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;\
+
+updateChannelUserTyping#ff2abe9f flags:# channel_id:int top_msg_id:flags.0?int user_id:int action:SendMessageAction = Update;\
+
+---functions---\
+
+contacts.block#68cc1411 id:InputPeer = Bool;
+contacts.unblock#bea65d50 id:InputPeer = Bool;\
+
+messages.search#4e17810b flags:# peer:InputPeer q:string from_id:flags.0?InputUser 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:int = messages.Messages;
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;
+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;\
+
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;\
+
+messages.getReplies#24b581ba peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:int = 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;\
+
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;\
+
+ + + +

Layer 118

+

Added method for fetching country names and phone patterns.

+

Schema changes

+
New Methods
+
    +
  • Added help.getCountriesList - Get name, ISO code, localized name and phone codes/patterns of all available countries
  • +
+
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;\
+
+help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
+help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
+help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;\
+
+---functions---\
+
+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.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;\
+
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;\
+
+ + + +

Layer 117

+

Added WebRTC endpoint constructors.

+

Schema changes

+
New Constructors
+ +

Schema

+
phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;\
+
+ + + +

Layer 116

+

Added supergroup statistics and global privacy settings.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;\
+
+userProfilePhoto#69d3ab26 flags:# has_video:flags.0?true photo_id:long photo_small:FileLocation photo_big:FileLocation dc_id:int = UserProfilePhoto;\
+
+chatPhoto#d20b9f3c flags:# has_video:flags.0?true photo_small:FileLocation photo_big:FileLocation dc_id:int = ChatPhoto;\
+
+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;
+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 geo_distance:flags.6?int = PeerSettings;\
+
+encryptedChatRequested#62718a82 flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:int participant_id:int g_a:bytes = EncryptedChat;\
+
+videoSize#e831c556 flags:# type:string location:FileLocation w:int h:int size:int video_start_ts:flags.0?double = VideoSize;\
+
+statsGroupTopPoster#18f3d0f7 user_id:int messages:int avg_chars:int = StatsGroupTopPoster;
+statsGroupTopAdmin#6014f412 user_id:int deleted:int kicked:int banned:int = StatsGroupTopAdmin;
+statsGroupTopInviter#31962a4c user_id:int 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;\
+
+updateChannelParticipant#65d2b464 flags:# channel_id:int date:int user_id:int prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant qts:int = Update;\
+
+---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;\
+
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;\
+
+account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
+account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;\
+
+help.dismissSuggestion#077fa99f suggestion:string = Bool;\
+
+ + + +

Layer 115

+

Added a chat invitation that also allows peeking into the group to read messages without joining it.

+

Schema changes

+
New Constructors
+
    +
  • Added chatInvitePeek - A chat invitation that also allows peeking into the group to read messages without joining it.
  • +
+

Schema

+
chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;\
+
+ + + +

Layer 114

+

Added WebRTC signaling methods.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
Deleted Methods
+
    +
  • Removed messages.searchGifs
  • +
+
New Constructors
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed foundGif
  • +
  • Removed foundGifCached
  • +
  • Removed inputMediaGifExternal
  • +
  • Removed messages.foundGifs
  • +
+

Schema

+
userFull#edf17c12 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 = UserFull;\
+
+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;\
+
+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;\
+
+user#938458c1 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 id:int 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;\
+
+channelFull#f0e6672a 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:int 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:ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?int 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?int location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int = ChatFull;\
+
+phoneCallWaiting#1b8f4ad1 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:int participant_id:int protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
+phoneCallRequested#87eabb53 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:int participant_id:int g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCallAccepted#997c454a flags:# video:flags.6?true id:long access_hash:long date:int admin_id:int participant_id:int g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCall#8742ae7f flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:int participant_id:int 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;\
+
+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 = ChatAdminRights;\
+
+videoSize#435bb987 type:string location:FileLocation w:int h:int size:int = VideoSize;\
+
+updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;\
+
+---functions---\
+
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;\
+
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;\
+
+ + + +

Layer 113

+

Public Service Announcement constructors and better PUSH notifications.
Notice that all PINNED_* PUSH notifications have two variants: one for groups, and one for channels.

+

Schema changes

+
New Methods
+ +
Deleted Methods
+
    +
  • Removed help.getProxyData
  • +
+
New Constructors
+ +
Changed Constructors
+ +
Deleted Constructors
+
    +
  • Removed help.proxyDataEmpty
  • +
  • Removed help.proxyDataPromo
  • +
+

PUSH notification changes

+
New PUSH notifications
+ +
Changed PUSH notifications
+ +

Schema

+
messageFwdHeader#353a686b flags:# from_id:flags.0?int from_name:flags.5?string date:int channel_id:flags.1?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;\
+
+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;
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;\
+
+ + + +

Layer 112

+

Schema changes

+
New Methods
+ +
Changed Constructors
+ +

Schema

+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#b6abc341 hash:int count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;\
+
+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;
+pollResults#badcc1a3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<int> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;\
+
+inputMediaPoll#0f94e5f1 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;\
+
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;\
+
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;\
+
+---functions---\
+
+initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;\
+
+messages.getOldFeaturedStickers#5fe7025b offset:int limit:int hash:int = messages.FeaturedStickers;\
+
+ + + +

Layer 111

+

Folders, channel stats, bot and sticker improvements

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
channelFull#f0e6672a 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_view_stats:flags.12?true can_set_location:flags.16?true has_scheduled:flags.19?true id:int 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:ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?int 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?int location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int = ChatFull;\
+
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;\
+
+phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;
+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;\
+
+dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;
+dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;\
+
+updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
+updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
+updateDialogFilters#3504914f = Update;\
+
+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;\
+
+inputMediaDice#aeffa807 = InputMedia;\
+
+messageMediaDice#638fe46b value:int = MessageMedia;\
+
+inputStickerSetDice#79e21a53 = InputStickerSet;\
+
+---functions---\
+
+initConnection#785188b8 {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;\
+
+stickers.createStickerSet#f1036780 flags:# masks:flags.0?true animated:flags.1?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> = messages.StickerSet;\
+
+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;\
+
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;\
+
+bots.setBotCommands#805d46f6 commands:Vector<BotCommand> = Bool;\
+
+ + + +

Layer 110

+

Credit card information

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +

Schema

+
messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;\
+
+bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;\
+
+payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
+peerSelfLocated#f8ec284b expires:int = PeerLocated;\
+
+---functions---\
+
+initConnection#785188b8 {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 query:!X = X;\
+
+contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;\
+
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;\
+
+ + + +

Layer 109

+

Non-anonymous polls, improved sticker management

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+ +

Schema

+
pollResults#c87024a2 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<int> = PollResults;\
+
+inputMediaPoll#abe9ca25 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> = InputMedia;\
+
+updateMessagePollVote#42f88f2c poll_id:long user_id:int options:Vector<bytes> = Update;\
+
+messageUserVote#a28e5559 user_id:int option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#36377430 user_id:int date:int = MessageUserVote;
+messageUserVoteMultiple#0e8fe0de user_id:int options:Vector<bytes> date:int = MessageUserVote;
+messages.votesList#0823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;\
+
+keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;\
+
+---functions---\
+
+initConnection#785188b8 {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;\
+
+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;\
+
+ + + +

Layer 108

+

Login with QR-code, sensitive content settings, quizes, multiple-choice and public polls, get inactive chats, improved wallpapers and themes.

+

Schema changes

+
New Methods
+ +
Changed Methods
+ +
New Constructors
+ +
Changed Constructors
+
    +
  • Added attributes parameter, removed documents parameter in webPage
  • +
  • Added public_voters, multiple_choice, quiz parameters in poll
  • +
  • Added correct parameter in pollAnswerVoters
  • +
  • Added second_background_color, rotation parameters in wallPaperSettings
  • +
  • Added video_upload_maxbitrate parameter in autoDownloadSettings
  • +
  • Added settings parameter in theme
  • +
+
Deleted Constructors
+
    +
  • Removed themeDocumentNotModified
  • +
+

Schema

+
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;\
+
+poll#d5529d06 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> = Poll;
+pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;\
+
+wallPaperSettings#05086cf8 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?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;\
+
+inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;\
+
+theme#028f1114 flags:# creator:flags.0?true default:flags.1?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:int = Theme;\
+
+updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
+updateLoginToken#564fe691 = Update;\
+
+auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#068e9916 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;\
+
+inputWallPaperNoFile#8427bbac = InputWallPaper;\
+
+wallPaperNoFile#8af40b25 flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;\
+
+inputThemeSettings#bd507cd1 flags:# base_theme:BaseTheme accent_color:int message_top_color:flags.0?int message_bottom_color:flags.0?int wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;\
+
+themeSettings#9c14984a flags:# base_theme:BaseTheme accent_color:int message_top_color:flags.0?int message_bottom_color:flags.0?int wallpaper:flags.1?WallPaper = ThemeSettings;\
+
+webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;\
+
+---functions---\
+
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;\
+
+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;
+auth.exportLoginToken#b1b41517 api_id:int api_hash:string except_ids:Vector<int> = auth.LoginToken;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
+account.getContentSettings#8b9b4dae = account.ContentSettings;\
+
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;\
+
+account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;\
+
+ + + +

Layer 105

+

The API underwent huge changes, a full reread of the documentation is required.

+

Layer 23

+

Schema changes

+
New Methods
+ +
Deleted Methods
+
    +
  • Removed invokeWithLayer18
  • +
+
New Constructors
+ +
Changed Constructors
+ +

Schema

+
contactStatus#d3680c61 user_id:int status:UserStatus = ContactStatus;
+config#7dae33e0 date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> chat_big_size:int chat_size_max:int broadcast_size_max:int disabled_features:Vector<DisabledFeature> = Config;\
+
+inputMediaUploadedDocument#ffe76b78 file:InputFile mime_type:string attributes:Vector<DocumentAttribute> = InputMedia;
+inputMediaUploadedThumbDocument#41481486 file:InputFile thumb:InputFile mime_type:string attributes:Vector<DocumentAttribute> = InputMedia;\
+
+document#f9a39f4f id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = Document;\
+
+userStatusRecently#e26f42f1 = UserStatus;
+userStatusLastWeek#07bf09fc = UserStatus;
+userStatusLastMonth#77ebc742 = UserStatus;
+updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;\
+
+inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;\
+
+privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;\
+
+inputPrivacyValueAllowContacts#0d09e07b = InputPrivacyRule;
+inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
+inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueDisallowContacts#0ba52007 = InputPrivacyRule;
+inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
+inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;\
+
+privacyValueAllowContacts#fffe1bac = PrivacyRule;
+privacyValueAllowAll#65427b82 = PrivacyRule;
+privacyValueAllowUsers#4d5bbe0c users:Vector<int> = PrivacyRule;
+privacyValueDisallowContacts#f888fa1a = PrivacyRule;
+privacyValueDisallowAll#8b73e763 = PrivacyRule;
+privacyValueDisallowUsers#0c7f49b7 users:Vector<int> = PrivacyRule;\
+
+account.privacyRules#554abb6f rules:Vector<PrivacyRule> users:Vector<User> = account.PrivacyRules;
+accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+account.sentChangePhoneCode#a4f58c4c phone_code_hash:string send_call_timeout:int = account.SentChangePhoneCode;\
+
+updateUserPhone#12b9417b user_id:int phone:string = Update;\
+
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#fb0a5727 = DocumentAttribute;
+documentAttributeVideo#5910cccb duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#051448e5 duration:int = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;\
+
+messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#8a8ecd32 hash:string stickers:Vector<Document> = messages.Stickers;\
+
+stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;\
+
+messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#dcef3102 hash:string packs:Vector<StickerPack> documents:Vector<Document> = messages.AllStickers;\
+
+disabledFeature#ae636f24 feature:string description:string = DisabledFeature;\
+
+---functions---\
+
+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#08fc711d = AccountDaysTTL;
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;\
+
+invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;\
+
+contacts.resolveUsername#0bf0131c username:string = User;\
+
+account.sendChangePhoneCode#a407a8f4 phone_number:string = account.SentChangePhoneCode;
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;\
+
+messages.getStickers#ae22e045 emoticon:string hash:string = messages.Stickers;
+messages.getAllStickers#aa3bc868 hash:string = messages.AllStickers;\
+
+account.updateDeviceLocked#38df3532 period:int = Bool;\
+
+ +

End-to-end schema changes

+
New Constructors
+ +

End-to-end schema

+
===20===\
+
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
+decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;\
+
+===23===
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#fb0a5727 = DocumentAttribute;
+documentAttributeVideo#5910cccb duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#051448e5 duration:int = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;\
+
+photoSizeEmpty#0e17e23c type:string = PhotoSize;
+photoSize#77bfb61b type:string location:FileLocation w:int h:int size:int = PhotoSize;
+photoCachedSize#e9a734fa type:string location:FileLocation w:int h:int bytes:bytes = PhotoSize;\
+
+fileLocationUnavailable#7c596b46 volume_id:long local_id:int secret:long = FileLocation;
+fileLocation#53d69076 dc_id:int volume_id:long local_id:int secret:long = FileLocation;\
+
+decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;\
+
+ +

Layer 18

+

Added username support and a new type of updates for service messages.

+

Schema changes

+ +

Schema

+
contactFound user_id:int = ContactFound;
+
+contacts.found results:Vector<ContactFound> users:Vector<User> = contacts.Found;
+
+updateUserName user_id:int first_name:string last_name:string username:string = Update;
+
+userSelf id:int first_name:string last_name:string username:string phone:string photo:UserProfilePhoto status:UserStatus inactive:Bool = User;
+userContact id:int first_name:string last_name:string username:string access_hash:long phone:string photo:UserProfilePhoto status:UserStatus = User;
+userRequest id:int first_name:string last_name:string username:string access_hash:long phone:string photo:UserProfilePhoto status:UserStatus = User;
+userForeign id:int first_name:string last_name:string username:string access_hash:long photo:UserProfilePhoto status:UserStatus = User;
+userDeleted id:int first_name:string last_name:string username:string = User;
+
+updateServiceNotification type:string message:string media:MessageMedia popup:Bool = Update;
+
+---functions---
+
+account.checkUsername username:string = Bool;
+account.updateUsername username:string = User;
+
+contacts.search q:string limit:int = contacts.Found;
+
+invokeWithLayer18#1c900537 {X:Type} query:!X = X;
+

Layer 17

+

Added new events for recording and uploading media, selecting contacts and locations to share.

+

Read status for multimedia (messages containing messageMediaVideo or messageMediaAudio) was moved to the new method messages.readMessageContents. In case read_contents is not passed or messages.readHistory is used with an older layer, messages will be marked as read in the traditional way.

+

Schema changes

+
    +
  • Added new type SendMessageAction for user actions aside from typing (recording, uploading media, etc.). It is used in updates updateUserTyping, updateChatUserTyping, in the method messages.setTyping, and in the new encrypted service message decryptedMessageActionTyping.
  • +
  • unread and out parameters in the constructors of the Message type were joined to form the new flags parameter, containing a flag mask.
  • +
  • Added new method messages.readMessageContents, to be called once the user listened to a voice message or watched a video.
  • +
  • Added parameters for end-to-end encrypted messages in_seq_no, out_seq_no and ttl.
  • +
  • Added mime_type field to secret chat audio and video constructors.
  • +
+

Schema

+
sendMessageTypingAction = SendMessageAction;
+sendMessageCancelAction = SendMessageAction;
+sendMessageRecordVideoAction = SendMessageAction;
+sendMessageUploadVideoAction = SendMessageAction;
+sendMessageRecordAudioAction = SendMessageAction;
+sendMessageUploadAudioAction = SendMessageAction;
+sendMessageUploadPhotoAction = SendMessageAction;
+sendMessageUploadDocumentAction = SendMessageAction;
+sendMessageGeoLocationAction = SendMessageAction;
+sendMessageChooseContactAction = SendMessageAction;
+
+updateUserTyping user_id:int action:SendMessageAction = Update;
+updateChatUserTyping chat_id:int user_id:int action:SendMessageAction = Update;
+
+// Message object
+message flags:int id:int from_id:int to_id:Peer date:int message:string media:MessageMedia = Message;
+messageForwarded flags:int id:int fwd_from_id:int fwd_date:int from_id:int to_id:Peer date:int message:string media:MessageMedia = Message;
+messageService flags:int id:int from_id:int to_id:Peer date:int action:MessageAction = Message;
+
+---functions---
+
+messages.setTyping peer:InputPeer action:SendMessageAction = Bool;
+
+messages.readHistory peer:InputPeer max_id:int offset:int read_contents:Bool = messages.AffectedHistory;
+messages.readMessageContents id:Vector<int> = Vector<int>;
+
+invokeWithLayer17#50858a19 {X:Type} query:!X = X;
+

End-to-end schema

+
===17===
+
+
+// Layer
+decryptedMessageLayer random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;
+
+decryptedMessageMediaAudio duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaVideo thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+sendMessageTypingAction = SendMessageAction;
+sendMessageCancelAction = SendMessageAction;
+sendMessageRecordVideoAction = SendMessageAction;
+sendMessageUploadVideoAction = SendMessageAction;
+sendMessageRecordAudioAction = SendMessageAction;
+sendMessageUploadAudioAction = SendMessageAction;
+sendMessageUploadPhotoAction = SendMessageAction;
+sendMessageUploadDocumentAction = SendMessageAction;
+sendMessageGeoLocationAction = SendMessageAction;
+sendMessageChooseContactAction = SendMessageAction;
+
+decryptedMessageActionNotifyLayer layer:int = DecryptedMessageAction;
+decryptedMessageActionTyping action:SendMessageAction = DecryptedMessageAction;
+
+decryptedMessage random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService random_id:long action:DecryptedMessageAction = DecryptedMessage;
+

Layer 16

+

Added new sms_type = 5 in the method auth.sendCode.

+

Schema changes

+
    +
  • Added new constructor: auth.sentAppCode to determine whether a code was sent via Telegram.
  • +
  • Added new method auth.sendSms to force re-sending a code via SMS.
  • +
+

Schema

+
auth.sentAppCode phone_registered:Bool phone_code_hash:string send_call_timeout:int is_password:Bool = auth.SentCode;
+
+---functions---
+
+auth.sendSms phone_number:string phone_code_hash:string = Bool;
+
+invokeWithLayer16#cf5f0987 {X:Type} query:!X = X;
+

Layer 15

+

Modified behavior of the offset parameter in the method messages.getHistory. From now on it's possible to combine message_id offset and a numeric offset.

+

Schema

+
invokeWithLayer15#b4418b64 {X:Type} query:!X = X;
+

Layer 14

+

Schema changes

+ +

Schema

+
notifyPeer peer:Peer = NotifyPeer;
+notifyUsers = NotifyPeer;
+notifyChats = NotifyPeer;
+notifyAll = NotifyPeer;
+
+dialog peer:Peer top_message:int unread_count:int notify_settings:PeerNotifySettings = Dialog;
+
+updateUserBlocked user_id:int blocked:Bool = Update;
+updateNotifySettings peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
+
+---functions---
+
+invokeWithLayer14#2b9b08fa {X:Type} query:!X = X;
+

Layer 13

+

Schema changes

+
    +
  • Added mime_type field to all audio and video constructors.
  • +
  • Added new service message types in secret chats: messages read, messages deleted, screenshot taken, chat history cleared and API layer used by client notifications.
  • +
  • Added retry_contacts field to the contacts.importedContacts constructor: ids of contacts, that will have to be imported at a later date.
  • +
+

Schema

+
contacts.importedContacts imported:Vector<ImportedContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+
+inputMediaUploadedAudio file:InputFile duration:int mime_type:string = InputMedia;
+inputMediaUploadedVideo file:InputFile duration:int w:int h:int mime_type:string = InputMedia;
+inputMediaUploadedThumbVideo file:InputFile thumb:InputFile duration:int w:int h:int mime_type:string = InputMedia;
+
+audio id:long access_hash:long user_id:int date:int duration:int mime_type:string size:int dc_id:int = Audio;
+video id:long access_hash:long user_id:int date:int caption:string duration:int mime_type:string size:int thumb:PhotoSize dc_id:int w:int h:int = Video;
+
+---functions---
+
+invokeWithLayer13#427c8ea2 {X:Type} query:!X = X;
+

Layer 12

+

Schema changes

+
    +
  • Added method help.getSupport for obtaining support user id.
  • +
  • Added broadcast_size_max field to the constructor config, contaning maximum number of broadcast recipients.
  • +
  • Added send_call_timeout field to the constructor auth.sentCode, containing required delay before calling auth.sendCall. New field is_password in the same constructor.
  • +
+

Schema

+
auth.sentCode phone_registered:Bool phone_code_hash:string send_call_timeout:int is_password:Bool = auth.SentCode;
+
+config date:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> chat_size_max:int broadcast_size_max:int = Config;
+
+help.support phone_number:string user:User = help.Support;
+
+---functions---
+
+help.getSupport = help.Support;
+
+invokeWithLayer12#dda60d3c {X:Type} query:!X = X;
+

Layer 11

+

Schema changes

+
    +
  • The nonce parameter was removed from secret chat constructors. For purposes of backward compatibility, in all previous layers this field will contain empty bytes.
  • +
+

Schema

+
encryptedChatRequested id:int access_hash:long date:int admin_id:int participant_id:int g_a:bytes = EncryptedChat;
+encryptedChat id:int access_hash:long date:int admin_id:int participant_id:int g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+
+---functions---
+
+invokeWithLayer11#a6b88fdf {X:Type} query:!X = X;
+

Layer 10

+

Added brief constructors for editing group members. Added new attachment types for ordinary and secret chats.

+

Schema changes

+ +

Schema

+
updateChatParticipantAdd chat_id:int user_id:int inviter_id:int version:int = Update;
+updateChatParticipantDelete chat_id:int user_id:int version:int = Update;
+
+
+inputMediaUploadedAudio file:InputFile duration:int = InputMedia;
+inputMediaAudio id:InputAudio = InputMedia;
+
+inputMediaUploadedDocument file:InputFile file_name:string mime_type:string = InputMedia;
+inputMediaUploadedThumbDocument file:InputFile thumb:InputFile file_name:string mime_type:string = InputMedia;
+inputMediaDocument id:InputDocument = InputMedia;
+
+messageMediaDocument document:Document = MessageMedia;
+messageMediaAudio audio:Audio = MessageMedia;
+
+// Input Audio
+inputAudioEmpty = InputAudio;
+inputAudio id:long access_hash:long = InputAudio;
+
+// Input Document
+inputDocumentEmpty = InputDocument;
+inputDocument id:long access_hash:long = InputDocument;
+
+// Input location
+inputAudioFileLocation id:long access_hash:long = InputFileLocation;
+inputDocumentFileLocation id:long access_hash:long = InputFileLocation;
+
+
+decryptedMessageMediaDocument thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+
+// Audio object
+audioEmpty id:long = Audio;
+audio id:long access_hash:long user_id:int date:int duration:int size:int dc_id:int = Audio;
+
+// Video object
+documentEmpty id:long = Document;
+document id:long access_hash:long user_id:int date:int file_name:string mime_type:string size:int thumb:PhotoSize dc_id:int = Document;
+
+---functions---
+
+invokeWithLayer10#39620c41 {X:Type} query:!X = X;
+

Push-notifications

+

Added MESSAGE_DOC, MESSAGE_AUDIO notifications — a message with document or audio received Added CHAT_MESSAGE_DOC, CHAT_MESSAGE_AUDIO notifications — a message with document or audio received in a group

+

Layer 9

+

Increased efficiency when loading big files. Added important checks for certain methods.

+

Schema changes

+ +

Schema

+
inputFileBig id:long parts:int name:string = InputFile;
+
+inputEncryptedFileBigUploaded id:long parts:int key_fingerprint:int = InputEncryptedFile;
+
+---functions---
+
+upload.saveBigFilePart file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
+
+initConnection#69796de9 {X:Type} api_id:int device_model:string system_version:string app_version:string lang_code:string query:!X = X;
+
+invokeWithLayer9#76715a63 {X:Type} query:!X = X;
+

Layer 8

+

Added support for end-to-end encryption in secret chats. More…

+

Schema changes

+
    +
  • Added many constructors and methods for secret chats.
  • +
  • Added qts field in constructor updates.state.
  • +
  • Added 4 new constructors of Update type
  • +
+

Schema

+
updateNewEncryptedMessage message:EncryptedMessage qts:int = Update;
+updateEncryptedChatTyping chat_id:int = Update;
+updateEncryption chat:EncryptedChat date:int = Update;
+updateEncryptedMessagesRead chat_id:int max_date:int = Update;
+
+// EncryptedChat object
+encryptedChatEmpty id:int = EncryptedChat;
+encryptedChatWaiting id:int access_hash:long date:int admin_id:int participant_id:int = EncryptedChat;
+encryptedChatRequested id:int access_hash:long date:int admin_id:int participant_id:int g_a:bytes = EncryptedChat;
+encryptedChat id:int access_hash:long date:int admin_id:int participant_id:int g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded id:int = EncryptedChat;
+
+inputEncryptedChat chat_id:int access_hash:long = InputEncryptedChat;
+
+// EncryptedFile object
+encryptedFileEmpty = EncryptedFile;
+encryptedFile id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+inputEncryptedFileEmpty = InputEncryptedFile;
+inputEncryptedFileUploaded id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
+inputEncryptedFile id:long access_hash:long = InputEncryptedFile;
+
+inputEncryptedFileLocation id:long access_hash:long = InputFileLocation;
+
+// Encrypted message
+encryptedMessage random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;
+
+// Diffie-Hellman config
+messages.dhConfigNotModified random:bytes = messages.DhConfig;
+messages.dhConfig g:int p:bytes version:int random:bytes = messages.DhConfig;
+
+messages.sentEncryptedMessage date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile date:int file:EncryptedFile = messages.SentEncryptedMessage;
+
+// Updated state with qts
+updates.state pts:int qts:int date:int seq:int unread_count:int = updates.State;
+updates.difference 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 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;
+
+---functions---
+
+messages.getDhConfig version:int random_length:int = messages.DhConfig;
+messages.requestEncryption user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
+messages.acceptEncryption peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;
+messages.discardEncryption chat_id:int = Bool;
+
+messages.setEncryptedTyping peer:InputEncryptedChat typing:Bool = Bool;
+messages.readEncryptedHistory peer:InputEncryptedChat max_date:int = Bool;
+messages.sendEncrypted peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.sendEncryptedFile peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
+messages.sendEncryptedService peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.receivedQueue max_qts:int = Vector<long>;
+
+updates.getDifference pts:int date:int qts:int = updates.Difference;
+
+invokeWithLayer8#e9abd9fd {X:Type} query:!X = X;
+

Push-notifications

+
    +
  • Added notification of ENCRYPTION_REQUEST type — a contact requested secret chat creation
  • +
  • Added notification of ENCRYPTION_ACCEPT type — a contact confirmed secret chat creation
  • +
  • Added notification of ENCRYPTED_MESSAGE type — a contact sent message in a secret chat
  • +
+

End-to-end schema

+
===8===
+decryptedMessage random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+
+decryptedMessageMediaEmpty = DecryptedMessageMedia;
+decryptedMessageMediaPhoto thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaVideo thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaGeoPoint lat:double long:double = DecryptedMessageMedia;
+decryptedMessageMediaContact phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
+
+decryptedMessageActionSetMessageTTL ttl_seconds:int = DecryptedMessageAction;
+
+decryptedMessageMediaDocument thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+decryptedMessageActionReadMessages random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionDeleteMessages random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionScreenshotMessages random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionFlushHistory = DecryptedMessageAction;
+

Layer 7

+

Added wallpaper constructor wallPaperSolid.

+

Schema

+
wallPaperSolid id:int title:string bg_color:int color:int = WallPaper;
+---functions---
+invokeWithLayer7#a5be56d3 {X:Type} query:!X = X;
+

Layer 6

+

Added location identifiers from foursquare.

+

Schema

+
geoChat id:int access_hash:long title:string address:string venue:string geo:GeoPoint photo:ChatPhoto participants_count:int date:int checked_in:Bool version:int = Chat;
+---functions---
+geochats.createGeoChat title:string geo_point:InputGeoPoint address:string venue:string = geochats.StatedMessage;
+
+invokeWithLayer6#3a64d54d {X:Type} query:!X = X;
+

Layer 5

+

Added parameters for internationalization.

+

Schema changes

+ +

Schema

+
---functions---
+auth.sendCode phone_number:string sms_type:int api_id:int api_hash:string lang_code:string = auth.SentCode;
+account.registerDevice token_type:int token:string device_model:string system_version:string app_version:string app_sandbox:Bool lang_code:string = Bool;
+
+invokeWithLayer5#417a57ae {X:Type} query:!X = X;
+

Layer 4

+

Added geochats. More…

+

Schema changes

+
    +
  • Added many constructors and methods for geochats.
  • +
  • Added friends_unread_count field to constructor updates.state.
  • +
+

Schema

+
inputGeoChat chat_id:int access_hash:long = InputGeoChat;
+
+geoChat id:int access_hash:long title:string address:string geo:GeoPoint photo:ChatPhoto participants_count:int date:int left:Bool version:int = Chat;
+
+geoChatMessageEmpty chat_id:int id:int = GeoChatMessage;
+geoChatMessage chat_id:int id:int from_id:int date:int message:string media:MessageMedia = GeoChatMessage;
+geoChatMessageService chat_id:int id:int from_id:int date:int action:MessageAction = GeoChatMessage;
+
+geochats.statedMessage message:GeoChatMessage chats:Vector<Chat> users:Vector<User> seq:int = geochats.StatedMessage;
+
+geochats.located results:Vector<ChatLocated> messages:Vector<GeoChatMessage> chats:Vector<Chat> users:Vector<User> = geochats.Located;
+
+geochats.messages messages:Vector<GeoChatMessage> chats:Vector<Chat> users:Vector<User> = geochats.Messages;
+geochats.messagesSlice count:int messages:Vector<GeoChatMessage> chats:Vector<Chat> users:Vector<User> = geochats.Messages;
+
+messageActionGeoChatCreate title:string address:string = MessageAction;
+messageActionGeoChatCheckin = MessageAction;
+updateNewGeoChatMessage message:GeoChatMessage = Update;
+updates.state pts:int date:int seq:int unread_count:int friends_unread_count:int = updates.State;
+
+---functions---
+
+geochats.getLocated geo_point:InputGeoPoint radius:int limit:int = geochats.Located;
+geochats.checkin peer:InputGeoChat = geochats.StatedMessage;
+geochats.getFullChat peer:InputGeoChat = messages.ChatFull;
+geochats.editChatTitle peer:InputGeoChat title:string address:string = geochats.StatedMessage;
+geochats.editChatPhoto peer:InputGeoChat photo:InputChatPhoto = geochats.StatedMessage;
+geochats.search peer:InputGeoChat q:string filter:MessagesFilter min_date:int max_date:int offset:int max_id:int limit:int = geochats.Messages;
+geochats.getHistory peer:InputGeoChat offset:int max_id:int limit:int = geochats.Messages;
+geochats.setTyping peer:InputGeoChat typing:Bool = Bool;
+geochats.sendMessage peer:InputGeoChat message:string random_id:long = geochats.StatedMessage;
+geochats.sendMedia peer:InputGeoChat media:InputMedia random_id:long = geochats.StatedMessage;
+geochats.createGeoChat title:string geo_point:InputGeoPoint address:string = geochats.StatedMessage;
+
+invokeWithLayer4#dea0d430 {X:Type} query:!X = X;
+

Push-notifications

+
    +
  • Added notification of GEOCHAT_CHECKIN type — a user has checked-in in a geochat.
  • +
+

Layer 3

+

Support for link changes for a contact when a message is sent. Now, if user X has user Y in the contact list and if user Y writes a message to user X, number X will become available for him.

+

Schema changes

+ +

Schema

+
messages.statedMessagesLinks messages:Vector<Message> chats:Vector<Chat> users:Vector<User> links:Vector<contacts.Link> pts:int seq:int = messages.StatedMessages;
+messages.statedMessageLink message:Message chats:Vector<Chat> users:Vector<User> links:Vector<contacts.Link> pts:int seq:int = messages.StatedMessage;
+messages.sentMessageLink id:int date:int pts:int seq:int links:Vector<contacts.Link> = messages.SentMessage;
+
+---functions---
+
+messages.forwardMessage peer:InputPeer id:int random_id:long = messages.StatedMessage;
+messages.sendBroadcast contacts:Vector<InputUser> message:string media:InputMedia = messages.StatedMessages;
+
+invokeWithLayer3#b7475268 {X:Type} query:!X = X;
+

Layer 2

+

Support for notifications on changes of contact profile images. It is assumed that receiving such image changed notification a client will add a record on this event in the message history with this contact.

+

Schema changes

+ +

Schema

+
inputPeerNotifySettings mute_until:int sound:string show_previews:Bool events_mask:int = InputPeerNotifySettings;
+peerNotifySettings mute_until:int sound:string show_previews:Bool events_mask:int = PeerNotifySettings;
+updateUserPhoto user_id:int date:int photo:UserProfilePhoto previous:Bool = Update;
+userProfilePhoto photo_id:long photo_small:FileLocation photo_big:FileLocation = UserProfilePhoto;
+
+---functions---
+
+photos.getUserPhotos user_id:InputUser offset:int max_id:int limit:int = photos.Photos;
+
+invokeWithLayer2#289dd1f6 {X:Type} query:!X = X;
+

Push-notifications

+
    +
  • Added notification of CONTACT_PHOTO type — a contact has changed profile image.
  • +
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/live-location.html b/data/corefork.telegram.org/api/live-location.html new file mode 100644 index 0000000000..f72bb2e16a --- /dev/null +++ b/data/corefork.telegram.org/api/live-location.html @@ -0,0 +1,178 @@ + + + + + Live geolocation + + + + + + + + + + + + + +
+ +
+
+
+ +

Live geolocation

+ +
+ +

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+

Sending live locations

+
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
+
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
+
+inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
+
+---functions---
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
+

To send a live geolocation, use messages.sendMedia with an inputMediaGeoLive media .

+

The inputMediaGeoLive allows sending the geolocation as an inputGeoPoint with floating point latitude and longitude, with an optional accuracy_radius in meters.
+Clients can also provide a heading, a direction in degrees (1-360) that can be used to indicate the direction of the user, a validity period for the current location, and a proximity_notification_radius .

+

The sent geolocation should be updated perioducally using messages.editMessage at most every period seconds, in order to implement the "live" part of live geolocations.

+

To stop sharing the location, pass inputGeoPointEmpty as location and set the stopped flag to true in a last messages.editMessage call.

+

Receiving live locations

+
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+
+updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
+

Clients will receive a message with a messageMediaGeoLive, containing the information passed by the sender; when the geolocation message is marked as read, an updateGeoLiveViewed is generated.

+

Periodically, the geolocation will be updated with updateEditMessage/updateEditChannelMessage updates.

+

Live location previews

+
inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
+
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
+
+---functions---
+
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
+

A map preview can be generated by passing the received geoPoint to upload.getWebFile, to download an image preview of the map.

+
    +
  • geo_point is generated from the lat , long accuracy_radius parameters of the geoPoint
  • +
  • access_hash is the access hash of the geoPoint
  • +
  • w - Map width in pixels before applying scale; 16-1024
  • +
  • h - Map height in pixels before applying scale; 16-1024
  • +
  • zoom - Map zoom level; 13-20
  • +
  • scale - Map scale; 1-3
  • +
+

The image is then downloaded as specified here »

+

Proximity alert

+
messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
+
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
+

If:

+
    +
  • A user sets a proximity_notification_radius when sending a location
  • +
  • Multiple users share their location within the same chat
  • +
  • One of the other users comes within proximity_notification_radius meters of the first user, and updates their location accordingly
  • +
+

An updateNewMessage/updateNewChannelMessage is generated for all chat members, containing a messageService with action messageActionGeoProximityReached:

+
    +
  • messageActionGeoProximityReached.to_id is the peer that enabled proximity alerts
  • +
  • messageActionGeoProximityReached.from_id is the peer that is now in proximity of messageActionGeoProximityReached.to_id
  • +
  • messageActionGeoProximityReached.distance is the distance between them, in meters
  • +
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/mentions.html b/data/corefork.telegram.org/api/mentions.html new file mode 100644 index 0000000000..b89ac3f48f --- /dev/null +++ b/data/corefork.telegram.org/api/mentions.html @@ -0,0 +1,152 @@ + + + + + Mentions + + + + + + + + + + + + + +
+ +
+
+
+ +

Mentions

+ +
+ +

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+
messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
+inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;
+
+---functions---
+
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;
+

Mentions are implemented as message entities, passed to the messages.sendMessage method:

+ +

Incoming messages mentioning to the current user will have the mentioned flag set, and will contain one or more messageEntityMention and messageEntityMentionName constructors.

+

Graphical clients can show a list of mentionable users when the user starts entering an @ in the text bar; for this purpose, the channelParticipantsMentions filter can be used in channels.getParticipants.
+This filter can be enhanced by providing an additional query string q (anything the user enters after @); it will also return non-participant users, in case of channel users commenting in post comment sections.

+

Dialog mentions

+
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
+
+---functions---
+
+messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
+

Graphical clients are supposed to show a blue mention indicator next to the message counter of chats in the dialog list.
+The dialog constructor contains an unread_mentions_count field to isolate chats with unread mentions; the actual mention counter should be shown inside of the chat itself, above an @ button that can be used, by clicking multiple times, to navigate back (using messages.getUnreadMentions) through the mention history.

+

When the last unread mention is read, or when long-clicking on the @ button, all mentions for a chat should marked as read using messages.readMentions.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/min.html b/data/corefork.telegram.org/api/min.html new file mode 100644 index 0000000000..b19b2c4ab0 --- /dev/null +++ b/data/corefork.telegram.org/api/min.html @@ -0,0 +1,142 @@ + + + + + Min constructors + + + + + + + + + + + + + +
+ +
+
+
+ +

Min constructors

+ +

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set. This is done for performance and privacy reasons.

+

When receiving said constructors, the client must first check if user or chat object without min flag is already present in local cache. If it is present, then the client should just ignore constructors with min flag and use local one instead.

+

The rest of article assumes the client receives min-constructor without full object in local cache.

+

The client must store the context (similar to file references) in which the user/channel was seen. Later, when the client needs to pass the user/channel as input argument (e.g. fetch profile, mute, ban etc), the context is used to generate the input*FromMessage constructor, instead of normal inputUser, inputChannel or inputPeer.

+ +

The access_hash value, if present, is only suitable to use in inputPeerPhotoFileLocation, to directly download the profile pictures of channels and users without having to generate an inputPeer*FromMessage, simply using inputPeer* with the specified access hash.

+

Usually min constructors are encountered in messages inside of groups or channels. +When a message mentioning (sender, forwarder or forwardee, et cetera) such a user or channel is found, the constuctor must be associated with the message ID of the message and with the chat where the message was seen.

+

Example

+

Assume a message with id 34 is received from supergroup (actually channel) 123456789. +Said message was sent by from_id 102424212. +The updates container that contained the message has a user with ID 102424212 in the users field, but it has the min flag set, and the provided access_hash may be absent, or otherwise can't be used to generate a typical inputPeerUser constructor to send messages or do other actions.

+

What the client does is associate 102424212 with the channel 123456789 and message ID 34. +When and if the client will need to interact with user 102424212, it will generate one of the *FromMessage constructors mentioned above, setting:

+
    +
  • msg_id to 34
  • +
  • peer to the InputPeer associated with channel 123456789
  • +
  • user_id to 102424212
  • +
+

user_id can also be set to the IDs of users met in the fwd_header (messages forwarded from a user can be used to interact with the original sender, if they don't have privacy settings for forwards enabled). +Users mentioned via messageEntityMentionName in a message can also be used.

+

The same can be done with min channels.

+

Example implementations: Telegram for iOS, tdlib.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/obtaining_api_id.html b/data/corefork.telegram.org/api/obtaining_api_id.html new file mode 100644 index 0000000000..ed6d7eb7ab --- /dev/null +++ b/data/corefork.telegram.org/api/obtaining_api_id.html @@ -0,0 +1,140 @@ + + + + + Creating your Telegram Application + + + + + + + + + + + + + +
+ +
+
+
+ +

Creating your Telegram Application

+ +

We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge.

+
+

In order to ensure consistency and security across the Telegram ecosystem, +all third-party client apps must comply with the API Terms of Service.

+
+

Obtaining api_id

+

In order to obtain an API id and develop your own application using the Telegram API you need to do the following:

+
    +
  • Sign up for Telegram using any application.
  • +
  • Log in to your Telegram core: https://my.telegram.org.
  • +
  • Go to 'API development tools' and fill out the form.
  • +
  • You will get basic addresses as well as the api_id and api_hash parameters required for user authorization.
  • +
  • For the moment each number can only have one api_id connected to it.
  • +
+

We will be sending important developer notifications to the phone number that you use in this process, so please use an up-to-date number connected to your active Telegram account.

+

Using the api_id

+

Before using the MTProto Telegram API, please note that all API client libraries are strictly monitored to prevent abuse.

+

If you use the Telegram API for flooding, spamming, faking subscriber and view counters of channels, you will be banned forever.

+

Due to excessive abuse of the Telegram API, all accounts that sign up or log in using unofficial Telegram API clients are automatically put under observation to avoid violations of the Terms of Service.

+

If you didn't violate the Terms of Service but your account does get banned after using the API, write to recover@telegram.org explaining what you intend to do with the API, asking to unban your account.
+Please note that emails are checked by a human, so automatically generated emails will be detected and banned.

+

Using Telegram's open source code

+

Everyone is welcome to use our open source code. We have included a sample API id with the code. This API id is limited on the server side and is not suitable for apps released to end-users — using it for anything but testing purposes will result in the API_ID_PUBLISHED_FLOOD error for your users. It is necessary that you obtain your own API id before you publish your app.

+
+

Please remember to publish your code as well in order to comply with the GNU GPL licences.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/offsets.html b/data/corefork.telegram.org/api/offsets.html new file mode 100644 index 0000000000..f61d92bc36 --- /dev/null +++ b/data/corefork.telegram.org/api/offsets.html @@ -0,0 +1,170 @@ + + + + + Pagination in the API + + + + + + + + + + + + + +
+ +
+
+
+ +

Pagination in the API

+ +
+ +

Lots of Telegram API methods provide access to potentially large lists of objects, which requires pagination.

+

In order to fetch only relevant subset of results for each request there is a number of available input parameters. Here is a list in order how they are applied in API.

+

Typically, results are returned in antichronological order with descending object ID values.

+

limit parameter

+

A limit on the number of objects to be returned, typically between 1 and 100. When 0 is provided the limit will often default to an intermediate value like ~20.

+

offset-based pagination

+

For a few methods with mostly static data this parameter allows to skip offset elements from the beginning of list; negative values are ignored.

+

offset_id-based pagination

+

For most methods where results are real-time data (e.g. any chat history) offset value is not passed directly. Instead it is calculated from the passed offset_id and add_offset parameter values as offsetFromID(offset_id) + add_offset, where offsetFromID(offset_id) is a number of results from the beginning of list up to the result with ID offset_id, inclusive.

+

Sample use cases:

+
    +
  • +

    Loading 20 messages, older than message with ID MSGID:

    +

    messages.getHistory({offset_id: MSGID, add_offset: 0, limit: 20})

    +
  • +
  • +

    Loading 20 messages, newer than message with ID MSGID:

    +

    messages.getHistory({offset_id: MSGID, add_offset: -20, limit: 20})

    +
  • +
  • +

    Loading 20 messages around message with ID MSGID:

    +

    messages.getHistory({offset_id: MSGID, add_offset: -10, limit: 20})

    +
  • +
+

Additional filtering

+

There is a number of parameters, which are applied to the list after slicing with offset and limit, to reduce the result subset even more:

+
    +
  • max_id: Can be used to only return results with ID strictly smaller than max_id (e.g. message ID)
  • +
  • min_id: Can be used to only return results with ID strictly greater than min_id(e.g. message ID)
  • +
  • max_date: Can be used to only return results that are older than max_date:
  • +
  • min_date: Can be used to only return results with are newer than min_date:
  • +
  • hash: See below.
  • +
+

Hash generation

+

To further reduce the result subset, there is a mechanism to avoid fetching data if the resulting list hasn't changed from the one stored on client, similar to ETag.

+

When the client has cached results for API request, it can calculate the hash value for it by taking the result IDs (message IDs or other fields with name id) and using them to compute a 64-bit hash with the following algorithm:

+
# Here, ^ indicates a bitwise XOR
+
+hash = 0
+for id in ids:
+    hash = hash ^ (id >> 21)
+    hash = hash ^ (id << 35)
+    hash = hash ^ (id >> 4)
+    hash = hash + id
+

In some cases, the result container already has a hash field, that can be used instead.

+

When the client passes a correct value, the API will return one of *NotModified constructors, e.g. messages.messagesNotModified instead of the actual results.

+

Example methods

+
    +
  • messages.getHistory supports all result navigation parameters including message ID hashes and except filters
  • +
  • channels.getParticipants supports simple navigation using limit and offset, along with filtering and hash reducing using the user IDs of returned participants
  • +
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/optimisation.html b/data/corefork.telegram.org/api/optimisation.html new file mode 100644 index 0000000000..35d3848e85 --- /dev/null +++ b/data/corefork.telegram.org/api/optimisation.html @@ -0,0 +1,150 @@ + + + + + Client-Side Optimization + + + + + + + + + + + + + +
+ +
+
+
+ +

Client-Side Optimization

+ +

Simplified Acknowledgment of Message Delivery

+

An outgoing message may be considered sent once the server has assigned it an identifier. Normally, a client would learn of this from the result of the messages.sendMessage method. +The MTProto server provides a mechanism for “quick acknowledgments". Upon receiving such an acknowledgment, the client may be certain that the call to the send message method has at least been fully received by the server and placed in a processing queue, and can inform the user that the delivery was successful. +It is possible that the server’s actual response will never be received by the client (an interrupted connection; or the app restarts at exactly the wrong time). To correctly handle these situations, you can use a special type of notification generated by the server when updates.getDifference is called: updateMessageID. When processing this notification, the client can use the random_id identifier to associate the previously transmitted message with the one delivered to the server. +If such a notification is not issued when updates.getDifference is called for one of the previously sent messages, the message must be marked as undelivered.

+

Server Salt

+

Server salt is a 64-bit number added to every outgoing and incoming message. At present, a single salt’s lifespan is 1 hour, following which it is considered invalid and the server will return an error for all the messages that contain it. The error message will contain the correct salt, which may be immediately used for sending. Given this approach, there will always be a period of waiting before the client receives a new salt if it connects to the server less frequently than once an hour. +For improved performance, there is a special get_future_salts method, which fetches in advance a list of the salts that will be valid during the course of a specified period of time following the call (1 day, for example). A start time and an end time are specified for each salt. The salts overlap one another by half an hour. We recommend always using the record with the longest remaining lifespan.

+

Downloading Files and Uploading Data to the Server

+

We recommend that separate connections and sessions be created for these tasks. Remember that the extra sessions must be deleted when no longer needed. +It makes sense to download files over several connections (optimally to have a pool). When uploading data to a server one connection is enough to achieve the best results.

+

The file handling API is designed to perform data operations in parts. In its simplest implementation, the process of uploading files to a server looks like this: send a query, wait for a response, send the next query, etc. This approach does not optimize the use of network resources and the ping time has a huge effect. +The upload and download process is optimal when two or more queries are continuously being executed through one connection. In this arrangement, uploading to the server would look like this:

+
    +
  1. Send Query 1
  2. +
  3. Send Query 2
  4. +
  5. Wait for a response to Query 1
  6. +
  7. Send Query 3
  8. +
  9. Wait for a response to Query 2
  10. +
  11. Send Query 4
  12. +
  13. etc.
  14. +
+

This will help reduce the effect of ping latency and maximize the channel workload.

+

Sending Messages in Bulk

+

Sometimes a client needs to transmit several send message method calls to the server all at once in a single message or in several consecutive messages. However, the server may execute these requests out of order (queries are handled by different servers to improve performance, which introduces a degree of randomness to the process). +This requires that dependencies be explicitly stated when processing queries by using the function

+
invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
+

Actually, this means padding the beginning of the query with the 32-bit number 0xcb9f372d and the 64-bit message identifier of the query on which the current query is dependent.

+

Grouping Updates

+

Generating updates (notifications about various server events) and delivering them to the client form two different parts of the system (respectively, the messenger API and MTProto). By itself, MTProto cannot modify in any way the data transmitted to the client, and the server API cannot respond to client-MTProto connection events. +Imagine the situation where a client loses its connection (or is intentionally disconnected from the network) for some time. If lots of different events occur before a new connection is established (contacts come online, typing event messages are sent), then when a connection is established the client will receive lots of data containing all of the intervening events, despite the fact that most of the data is obsolete. +The grouping of messages has been introduced to optimize such situations. If new events occur and the client has not managed to “collect” the previously generated updates, then the server API can combine them into a single package.

+

A client is able to control when the MTProto server begins to consider that the connection has been lost and grouping can begin (the earlier this occurs when there is no connection, the better for the client). This functionality is implemented through a special type of Ping message, ping_delay_disconnect, which specifies a time delay following which the server will close the current connection and start grouping messages.

+

It makes sense to combine the transmission of ping_delay_disconnect with that of other recurring tasks, such as updating the user status (account.updateStatus).

+

Setting the Typing Status

+

If a contact is not online, there is no need to invoke messages.setTyping.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/passport.html b/data/corefork.telegram.org/api/passport.html new file mode 100644 index 0000000000..0aaa487f89 --- /dev/null +++ b/data/corefork.telegram.org/api/passport.html @@ -0,0 +1,674 @@ + + + + + Telegram passport + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram passport

+ +
+ +

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn‘t have access to the users’ personal information thanks to end-to-end encryption.

+

This page describes the request flow that client apps must used to send the requested data to the service.

+

Overview

+

From the perspective of a service that requires real-world ID, the process looks like this:

+
    +
  • A user presses “Log in with Telegram” on your website or in your app.
  • +
  • You request the data you need.
  • +
  • The user accepts your privacy policy and agrees to share their data.
  • +
  • The user's Telegram app downloads and decrypts the data you requested from the end-to-end encrypted storage on Telegram.
  • +
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • +
  • The user's app encrypts the data with your public key and sends it to you.
  • +
  • You decrypt the data, check it for errors and re-request any missing or invalid information.
  • +
  • You sign the user up for your service. Tada!
  • +
+

See As a bot to see how to request passport data using a bot, through the MTProto API. +Look at the Passport Manual to see how to request passport data using a bot, through the simplified bot API.

+

From the perspective of a user, the process looks something like this:

+
    +
  • Your app receives an event/intent from one of the SDKs, or from a custom source.
  • +
  • The user accepts your privacy policy and agrees to share their data.
  • +
  • The user's Telegram app downloads the data you requested from the end-to-end encrypted storage on Telegram.
  • +
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • +
  • The user's app encrypts the data with your public key and sends it to the service.
  • +
  • You sign the user up for your service. Tada!
  • +
+

See As a user to see how user client apps should send passport data to a service, through the MTProto API.

+

As a bot

+

A simplified version of this process can be used using the bot API, for more info see the Passport Manual.

+

Using the MTProto API, the process is pretty much the same, up until the actual API calls.

+
+

Note that all binary fields are in raw binary format, unlike in the bot API where they are base64-encoded

+
+

Setting Up Telegram Passport

+

As per the bot API.

+

Requesting Information

+

As per the bot API.

+

Receiving information

+

Schema:

+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
+securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;
+
+secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;
+
+secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+

When the user confirms your request by pressing the 'Authorize' button, the MTProto API sends an updateNewMessage from the user, with a messageService constructor, containing a messageActionSecureValuesSentMe constructor that contains the encrypted Telegram Passport data.

+

Decrypting data

+
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
+

To decrypt the received data, first, decrypt the credentials contained in secureCredentialsEncrypted.

+
    +
  1. +

    Decrypt the credentials secret ( secret field in secureCredentialsEncrypted) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)

    +
  2. +
  3. +

    Use this secret and the credentials hash ( hash field in secureCredentialsEncrypted) to calculate credentials_key and credentials_iv as described below:

    +
     credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    + credentials_key = slice( credentials_secret_hash, 0, 32 )
    + credentials_iv = slice( credentials_secret_hash, 32, 16 )
    +
  4. +
  5. +

    Decrypt the credentials data ( data field in secureCredentialsEncrypted) by AES256-CBC using these credentials_key and credentials_iv. IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )

    +
  6. +
  7. +

    Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.

    +
  8. +
+
+

Note that all hashes are raw binary data, not hexits

+
+

Credentials

+

The credentials are a JSON-serialized object, structured exactly as in the bot API ». +Since decryption credentials are E2E encrypted, apps have to store the decryption credentials as JSON and not TL payloads.

+

The credentials are used as described in the Passport Manual to decrypt the files attached to the secureValue. +In this case, the container for the E2E encrypted data is in TL, while the encrypted data itself is in JSON.

+
secureValue
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
+

The schema for the secureValue constructor defines the constructor that can be found in each field.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
+

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
+
SecureData
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
+

DataCredentials extracted from the credentials can then be used to decrypt encrypted data from the data field in secureData. +For more info on how to decrypt the data field, see the passport manual.

+
SecureFile
+
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile; 
+
+inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
+
+---functions---
+
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
+

Files (JPG format when decrypted, max. 10MB) are downloaded chunk by chunk as described in files », except that instead of generating an inputFileLocation, an inputFileLocation should be generated, instead.

+
    +
  • The id field is the id of the secureFile
  • +
  • The access_hash field is the access_hash of the secureFile
  • +
+

FileCredentials extracted from the credentials can then be used to decrypt downloaded encrypted data. +For more info on how to decrypt passport files, see the passport manual.

+
SecurePlainData
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+

The email/phone is passed in plaintext using the respective SecurePlainData constructor. +Emails and phone numbers sent using telegram passport are already verified as described in the passport manual.

+

Fixing errors

+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+
+inputUser#f21158c6 user_id:long access_hash:long = InputUser;
+
+
+---functions---
+
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
+

If the data you received contains errors, the bot can use the users.setSecureValueErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.

+

Descriptions of the method parameters can be found in the method's documentation page ».

+

As a user

+

Receiving requests

+

The process starts when your app receives an event from one of the SDKs, or from a custom source.

+

URI format

+

The SDKs trigger a passport authorization request by opening the following Telegram-specific URI:

+
tg://resolve?params
+

With the following query string parameters:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParametersTypeRequired
domainStringYes
bot_idIntegerYes
scopeUriPassportScopeYes
public_keyStringYes
nonceStringYes
callback_urlStringOptional
payloadStringOptional
+

Example URI, generated by the Telegram Passport Example page:

+
tg://resolve?domain=telegrampassport&bot_id=543260180&scope=%7B%22v%22%3A1%2C%22d%22%3A%5B%7B%22_%22%3A%22pd%22%2C%22n%22%3A1%7D%2C%22ad%22%2C%22pn%22%2C%22em%22%2C%7B%22_%22%3A%5B%7B%22_%22%3A%22pp%22%2C%22s%22%3A1%2C%22t%22%3A1%7D%2C%22ip%22%2C%22dl%22%2C%22ic%22%5D%7D%2C%7B%22_%22%3A%5B%22ub%22%2C%22bs%22%2C%22ra%22%2C%22pr%22%2C%22tr%22%5D%7D%5D%7D&public_key=-----BEGIN%20PUBLIC%20KEY-----%0AMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv6m1zBF8lZOCqcxf8hnj%0AkvHwuWdU8s4rBWaxKXH%2FvDDUklcCS5uhSnmjhxWca9suubaG3lW4HxlCilkeJPVf%0Ajimg5Q8ZqWrR3OoOihEpcG9iJZTOEpsEk7VtEiabgacBG3Quv9JslTrDe95Fn801%0At9d21HXwgMrHeHpWDOn31Dr%2BwoEH%2BkwySUWa6L%2FZbnGwSNP7eeDTE7Amz1RMDk3t%0A8EWGq58u0IQatPcEH09aUQlKzk6MIiALkZ9ILBKCBk6d2WCokKnsdBctovNbxwSx%0AhP1qst1r%2BYc8iPBZozsDC0ZsC5jXCkcODI3OC0tkNtYzN2XKalW5R0DjDRUDmGhT%0AzQIDAQAB%0A-----END%20PUBLIC%20KEY-----%0A&nonce=b8e892dc2e0afe63424d101b964f1256_32858210_708614a4585b84872e&callback_url=https%3A%2F%2Fcore.telegram.org%2Fpassport%2Fexample%3Fpassport_ssid%3Db8e892dc2e0afe63424d101b964f1256_32858210_db259b427f200751ce&payload=b8e892dc2e0afe63424d101b964f1256_32858210_708614a4585b84872e
+

UriPassportScope

+

This object represents the data to be requested.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dArray of UriPassportScopeElementList of requested elements, each type may be used only once in the entire array of UriPassportScopeElement objects
vIntegerScope version, must be 1
+
UriPassportScopeElement
+

This object represents a requested element, should be one of:

+ +

Passport document type identifiers are aliased with the following reduced type identifiers:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FullAlias
personal_detailspd
passportpp
driver_licensedl
identity_cardic
internal_passportip
id_documentidd
addressad
utility_billub
bank_statementbs
rental_agreementra
passport_registrationpr
temporary_registrationtr
address_documentadd
phone_numberpn
emailem
+

You can use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".

+

UriPassportScopeElementOneOfSeveral

+

This object represents several elements one of which must be provided.

+ + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
_Array of UriPassportScopeElementOneList of elements one of which must be provided; must contain either several of “pp”, “dl”, “ic”, “ip” or several of “ub”, “bs”, “ra”, “pr”, “tr”
sBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
tBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
+

UriPassportScopeElementOne

+

This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
_StringElement type. One of "pd", "pp", "dl", "ic", "ip", "ad", "ub", "bs", "ra", "pr", "tr", "pn", "em"
sBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "pp", "dl", "ic" and "ip"
tBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "pp", "dl", "ic", "ip", "ub", "bs", "ra", "pr" and "tr". Note: We suggest to only request translations after you have received a valid document that requires one.
nBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "pd"
+

You can also use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".

+

Setting up Telegram Passport

+

The next step for the client app is to request the user's 2FA passport, and configure Telegram Passport/fetch and decrypt remotely saved Telegram Passport parameters as described in the Encryption article ».

+

Fetching the passport form

+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+---functions---
+
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
+

Then, the client app passes the bot ID, scope and public key from the passport authorization request to the Telegram servers using the account.getAuthorizationForm method.

+

The response will be an account.authorizationForm constructor, with info about the required document types, the URL of the service's privacy policy, as well as info about the bot to which the form should be sent. +If the form was already submitted at least once, the constructor will also contain a list of already submitted data, along with eventual errors.

+

The user should accept the privacy policy and proceed to fill in the required data, and the client should encrypt and upload it as described in the Encryption article ».

+

Submitting the passport form

+
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;
+
+---functions---
+
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
+

Once the user finishes uploading the required documents and clicks on the submit button, the client calls account.acceptAuthorization, submitting the documents to the bot associated to the service.

+
    +
  • As before, bot_id, scope and public_key are taken from the authorization request URI.
  • +
  • value_hashes is used by the server to choose which document of which type to send to the bot: the type field should be set to the document type, and the hash field should be set to the data_hash/file_hash generated when uploading encrypting the data ».
  • +
  • credentials contains the encrypted credentials required by the service to decrypt the sent E2E encrypted secure values: it is generated as described in Passport Credentials ».
  • +
+

Finally, the client opens the callback URL (if present).

+

Handling invalid forms

+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+
+account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+---functions---
+
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
+

If any of the values of the submitted form are rejected by the service, the bot calls the appropriate method to set information about errors.

+

The user can find out about these errors directly from the service, or, if they decide to restart the process and resend the corrected data, directly from the authorization form (errors field).

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/pattern.html b/data/corefork.telegram.org/api/pattern.html new file mode 100644 index 0000000000..df161b3548 --- /dev/null +++ b/data/corefork.telegram.org/api/pattern.html @@ -0,0 +1,122 @@ + + + + + Pattern matching + + + + + + + + + + + + + +
+ +
+
+
+ +

Pattern matching

+ +

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+

For example, when requesting a login code, if the chosen verification method is a flash call, it is required that the phone number (which is the login code) matches the specified pattern.

+

Same with email verification codes.

+

In all cases, the pattern is a string of the same length as the string to verify: and matching is as simple as checking if all chars in the source string are the same as in the pattern string. +Some chars in the pattern string may be censored using an asterisk *, in this case any char in the source string is considered valid.

+

The pattern string can also be a single asterisk, in this case all patterns are considered valid.

+

If the source string is a phone number, it has to be sanitized first to include only the following chars: 0123456789.

+

Example implementation: telegram for android.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/payments.html b/data/corefork.telegram.org/api/payments.html new file mode 100644 index 0000000000..72e75765a8 --- /dev/null +++ b/data/corefork.telegram.org/api/payments.html @@ -0,0 +1,366 @@ + + + + + Payments API + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments API

+ +
+ +

You can accept payments from Telegram users via Telegram Bots.

+
+

Note: This article is intended for MTProto API developers. If you're looking for a general overview of Telegram Payments, check out the Telegram blog and the bot API payment manual.

+
+

Introducing Payments

+

Telegram bots can accept payments for goods and services from users. +For more info on how payments work, check out the Telegram Blog and the bot API payment manual.

+

This page will elaborate on the actions required to work with payments using the MTProto API.

+
+

A simplified version of the process is available only for bots using the bot API.

+
+

The first step for bots is enable payments as described here ».

+

Then, we work with payments as follows.

+

1. Create Invoice

+
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;
+
+labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
+
+invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
+
+inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
+
+---functions---
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

The user contacts the bot and requests to purchase something. +The bot forms an inputMediaInvoice with an invoice constructor with a description of the goods or service, amount to be paid, as well as requested shipping info. +The provider parameter of the inputMediaInvoice constructor is where you put the token value that you've obtained earlier via Botfather. It is possible for one merchant bot to use several different tokens for different users or different goods and services.

+

Use the messages.sendMedia method to send the invoice. +You can also attach an inline keyboard to the message using the reply_markup field: if provided, the first button must be a keyboardButtonBuy button. Otherwise, an inline keyboard will be generated automatically, with a Pay 'total price' keyboardButtonBuy as only button.

+

An invoice message with a pay button can only be sent to a private chat with the user. Groups and channels are not supported.

+

2. Order information

+

2.1 Invoice message

+
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+
+keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
+
+webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+

The user receives an updateNewMessage constructor from the bot, containing a messageMediaInvoice constructor with basic info about the product.

+

The message will also have a replyInlineMarkup keyboard attached to it. +The the first button of the keyboard will always be a keyboardButtonBuy button.

+

2.2 Getting invoice info about the product

+
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
+
+paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
+
+paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+
+---functions---
+
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;
+

If the user clicks on the keyboardButtonBuy button, the client proceeds to call payments.getPaymentForm with the message ID of the invoice preview message to get the payment form.

+

The returned form will contain fields that should be passed to the payment provider along with the full invoice. +The payment form also contains info about previously saved payment credentials and order information (name, phone number, email, shipping address & so on).

+

The full invoice contains info about the information required for the order, the price and the currency, and whether this is a test order.

+

2.3 Verifying information

+
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
+
+postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;
+
+paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
+
+payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
+
+---functions---
+
+payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;
+

If any data at all is requested by the invoice (name_requested, phone_requested, email_requested, shipping_address_requested), the user must call payments.validateRequestedInfo, providing the required data (as usual, msg_id is the ID of the invoice message). +The user can choose to save order information for future use by setting the save flag. +Data can be autofilled as described in autofill.

+

If no errors are found in the submitted info, the response of the method will contain an id flag, to be used later to complete the payment.

+

If the flexible flag of the invoice is set, calling the payments.validateRequestedInfo method will send a shipping query update to the bot, to which the bot will reply with the available shipping options for the specified address as described here ». +The return value in this case will also contain a shipping_options field with the available shipping options.

+

If any errors are found in the submmitted data, a service notification will be sent to the user, with a description of the error from the bot.

+

2.3.1 Autofill

+
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
+
+---functions---
+
+payments.getSavedInfo#227d824b = payments.SavedInfo;
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
+

The requested fields can be autofilled with the info provided in the saved_info field of the payment form, or with the info fetched manually using payments.getSavedInfo.

+

Saved order information can also be cleared using payments.clearSavedInfo.

+

2.4 Select delivery option

+
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
+
+shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;
+
+updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
+
+---functions---
+
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
+

If a shipping address was requested and the bot included the parameter flexible, when the user validates order information the Telegram API will send an updateBotShippingQuery to the bot. +The bot must respond using messages.setBotShippingResults either with a list of possible delivery options and the relevant delivery prices, or with an error (for example, if delivery to the specified address is not possible).

+

The returned shipping options or the shipping error will be returned to the user while validating order information.

+

3. Payment

+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
+
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+

3.1 Web payment

+
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+

Typically, payment takes place by opening the url in the specified payment form, which leads to a payment form on the website of the payment gateway. +Once the user finishes entering their payment credentials, a payment_form_submit web event is generated by the payment gateway, containing data and title JSON fields.

+

The title is used by the client app to represent the payment credentials (typically a censored version of credit card information). +The data is used to generate an inputPaymentCredentials constructor. +Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.

+

Telegram does not have access to your card information. Credit card details will be handled only by the payment system.

+

3.2 Native payment

+
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+

Most telegram apps support working natively with the native APIs of some payment providers, without opening the website of the payment and receiving a JS event.

+

This is done using the JSON native_params parameters field of the payments.paymentForm constructor, which contains an object, which can contain one or more of the following fields:

+
    +
  • publishable_key: Stripe API publishable key
  • +
  • apple_pay_merchant_id: Apple Pay merchant ID
  • +
  • android_pay_public_key: Android Pay public key
  • +
  • android_pay_bgcolor: Android Pay form background color
  • +
  • android_pay_inverse: Whether to use the dark theme in the Android Pay form
  • +
  • need_country: True, if the user country must be provided,
  • +
  • need_zip: True, if the user ZIP/postal code must be provided,
  • +
  • need_cardholder_name: True, if the cardholder name must be provided
  • +
+

The payment gateway to use is decided based on the value of the native_provider field.

+
3.2.1 Stripe
+
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+

If the native_provider field is set and equal to stripe, the client can make use of the native Stripe token APIs with the publishable_key from the native_params to add a payment method to Stripe, and then use the token type and id to generate a JSON object:

+
{"type":"token.type", "id":"token.id"}"
+

The generated JSON object can then be passed to the data field of the inputPaymentCredentials. +Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.

+

Telegram does not have access to your card information. Credit card details will be handled only by the payment system.

+

Example implementation: Telegram for Android.

+

3.3 Apple pay

+
inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+

On iOS devices, Apple Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsApplePay constructor.

+

Example implementation: Telegram for iOS.

+

3.4 Android pay

+
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
+

On Android devices, Google Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsGooglePay constructor.

+

Example implementation: Telegram for Android.

+

3.5 Using saved payment credentials

+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+
+paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+
+account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+
+---functions---
+
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;
+

To reuse saved payment methods, the saved_credentials field of the payment form is used. +The title of the paymentSavedCredentialsCard can be used to preview a censored version of credit card info. +The id field is provided by the payment provider directly to the Telegram servers when saving the payment method, and identifies the payment method. +Full credit card info is not saved on Telegram Servers, and cannot be fetched by the user.

+

In order to use the saved payment method, 2FA must be enabled: the user must verify their identity by entering their 2FA password, which is then used as described in the SRP docs to generate SRP parameters which must be passed to account.getTmpPassword.

+

The generated temporary password can then be used to make payments using the saved credentials using the inputPaymentCredentialsSaved constructor.

+ +

Example implementation: Telegram for Android.

+

4. Pre-Checkout

+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
+
+payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
+payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
+
+---functions---
+
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
+

After verifying order information, the final step for the client is to call payments.sendPaymentForm, with the following parameters:

+
    +
  • The msg_id is set to the ID of the invoice message
  • +
  • requested_info_id is set to the id of the verified order information, if it was requested
  • +
  • shipping_option_id is set to the selected delivery option, if shipping was requested.
  • +
  • credentials are the payment credentials generated by the payment provider, required to complete the order.
  • +
+

Payment method info can also be saved to the Telegram Servers and reused, by setting the save flag of inputPaymentCredentials when sending the form. +This is only possible on accounts with 2FA enabled.

+

The bot then replies to the received precheckout query, finally the user proceeds to checkout.

+

Please note that if the result of the method is a payments.paymentVerificationNeeded, before proceeding to checkout the payment provider requires the user to verify his identity by opening the provided url and following instructions. +Once the user finishes working with the webpage, the client can proceed to checkout.

+

Eventual errors are returned in the form of RPC errors, with the description of the error by the bot contained in service updates.

+

4.1 Receiving pre-checkout query

+
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
+
+updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
+
+---functions---
+
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
+

The user enters their payment information as described above and presses the final pay button. +At this moment the Telegram API sends an updateBotPrecheckoutQuery constructor that contains all the available information about the order to the bot. +The bot must reply using messages.setBotPrecheckoutResults within 10 seconds after receiving this update or the transaction is canceled.

+

The bot may return an error if it can‘t process the order for any reason. We highly recommend specifying a reason for failure to complete the order in human readable form (e.g. "Sorry, we’re all out of rubber ducks! Would you be interested in a steel bear instead?"). Telegram will display this reason to the user.

+

5. Checkout

+
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+
+keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
+
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+
+payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+
+---functions---
+
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;
+

In case the bot confirms the order, Telegram requests the payment provider to complete the transaction. If the payment information was entered correctly and the payment goes through, the Telegram API will modify the invoice message and send a service message as described below. Once your bot receives this message, it should proceed with delivering the goods or services purchased by the user.

+

If all is OK, the user receives a payments.paymentResult in reply to the payments.sendPaymentForm query, containing info about the updated invoice message in the form of an updateEditMessage.

+

The invoice message will be updated as follows: the attached messageMediaInvoice will now have a receipt_msg_id field. +Clients should treat invoice messages with a receipt_msg_id field as receipt messages, locally modifying the label of the keyboardButtonBuy button to a localized version of the word Receipt. +From this point, clicking on the Receipt button should trigger a call to payments.getPaymentReceipt, providing the receipt_msg_id to the msg_id field, which will return info about the transaction.

+

The payment will also generate one service message of type messageActionPaymentSent or messageActionPaymentSentMe, replying to the invoice. +For bots, the service message will be of type messageActionPaymentSentMe, for users it will be a messageActionPaymentSent.

+
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
+messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/pfs.html b/data/corefork.telegram.org/api/pfs.html new file mode 100644 index 0000000000..e6e26fd151 --- /dev/null +++ b/data/corefork.telegram.org/api/pfs.html @@ -0,0 +1,138 @@ + + + + + Perfect Forward Secrecy + + + + + + + + + + + + + +
+ +
+
+
+ +

Perfect Forward Secrecy

+ +
Related articles
+

+
+

This article is about Perfect Forward Secrecy in cloud chats, see also PFS in Secret Chats.

+
+
+

Telegram supports Perfect Forward Secrecy (PFS).

+

To make this possible, the client generates a permanent authorization key using p_q_inner_data and a temporary key using p_q_inner_data_temp. (See Creating an Authorization Key for more info.) These 2 operations may be done in parallel and even using the same connection. The client must save an expires_at unix timestamp expires_at = time + expires_in.

+

Important: in order to achieve PFS, the client must never use the permanent auth_key_id directly. Every message that is sent to MTProto, must be encrypted by a temp_auth_key_id, that was bound to the perm_auth_key_id.

+

An unbound temp_auth_key_id may only be used with the following methods:

+ +

In order to bind a temporary authorization key to the permanent key the client creates a special binding message and executes the auth.bindTempAuthKey method using temp_auth_key. Once auth.bindTempAuthKey has been executed successfully, the client may signUp / signIn using other auth.* methods and continue using the API as usual; the client must also rewrite client info using initConnection after each binding. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

+

Once the temporary key expires, the client needs to generate a new temporary key using p_q_inner_data_temp. Then it needs to re-bind that new temporary key to the initial permanent key. A new key can also be generated in advance, so that the client has a new key ready by the time the old one has expired.

+

For additional security, the client can store the temporary authorization key in RAM only and never save it in persistent storage.

+

A temporary authorization key may expire at any moment before expires_at, since such keys are also stored only in the RAM on the server-side. Be prepared to handle resulting MTProto errors correctly (non-existent auth_key_id results in a 404 error).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/pin.html b/data/corefork.telegram.org/api/pin.html new file mode 100644 index 0000000000..501034af11 --- /dev/null +++ b/data/corefork.telegram.org/api/pin.html @@ -0,0 +1,149 @@ + + + + + Pinned messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Pinned messages

+ +
+ +

Telegram allows pinning multiple messages on top of a specific chat.

+
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
+updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+
+---functions---
+
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
+
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
+

The messages.updatePinnedMessage method can be used to pin or unpin a specific message in an arbitrary chat.
+The unpin flags specifies whether to unpin or pin the message, and pm_oneside specifies whether the message should only be pinned on the local side of a one-to-one chat.

+

messages.unpinAllMessages can be used to unpin all messages in a chat.

+

When (un)pinning messages, a updatePinnedMessages or updatePinnedChannelMessages update will be emitted, containing IDs of pinned or unpinned messages.

+

Pinned messages will also have the will also have the pinned flag of message set.

+

Getting pinned messages

+
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
+chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
+channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
+
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;
+
+---functions---
+
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+

The pinned_msg_id of userFull, chatFull, channelFull contains the ID of only the latest pinned message.
+To obtain a full list, use messages.search with inputMessagesFilterPinned filter.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/poll.html b/data/corefork.telegram.org/api/poll.html new file mode 100644 index 0000000000..63d157426f --- /dev/null +++ b/data/corefork.telegram.org/api/poll.html @@ -0,0 +1,199 @@ + + + + + Poll + + + + + + + + + + + + + +
+ +
+
+
+ +

Poll

+ +
+ +

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

+

Sending a poll

+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+
+---functions---
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

To send a poll in a chat, call messages.sendMedia, providing an inputMediaPoll:

+
    +
  • +

    poll is the actual poll constructor, containing:

    +
      +
    • question - The poll title, aka the poll's title
    • +
    • answers - A vector of possible answers (2-10), each with a visible title text , and a unique option identifier (1-100 bytes)
    • +
    • closed - Whether the poll is closed
    • +
    • public_voters - Whether cast votes are publicly visible to all users (non-anonymous poll)
    • +
    • multiple_choice - Whether multiple options can be chosen as answer
    • +
    • quiz - Whether this is a quiz with correct answer IDs specified in inputMediaPoll.correct_answers
    • +
    • close_period - Amount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date .
    • +
    • close_date - Point in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period .
      +These last two parameters are exactly the same, except that one uses absolute, the other relative unixtime.
    • +
    +
  • +
  • +

    correct_answers - For quizes, option ID of the only correct answer

    +
  • +
  • +

    solution - Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds

    +
  • +
  • +

    solution_entities - Styled text message entities for the solution explanation

    +
  • +
+

In order to prematurely close the poll, preventing further votes, use messages.editMessage, setting the poll.closed flag to true.

+

Voting in polls

+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+
+---functions---
+
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
+

When receiving a message with a messageMediaPoll, users can vote in it using messages.sendVote, specifying the chosen option identifiers.

+

The method will return an updateMessagePoll, containing an updated pollResults constructor, with the chosen flag set on the options we chose, and the correct flag set on the correct answers.

+

Getting poll votes

+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+
+---functions---
+
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
+

Regularly, if new users have voted in polls available to the user, they will receive an updateMessagePoll, with updated pollResults.

+

The same constructor can also be fetched manually using messages.getPollResults.

+

Getting poll voters in non-anonymous polls

+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
+
+messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList; 
+
+updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
+
+---functions---
+
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList; 
+

messages.getPollVotes can be used to get poll results for non-anonymous polls, to see how each user voted for a poll option.
+Bots will also receive an updateMessagePollVote every time a user their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/push-updates.html b/data/corefork.telegram.org/api/push-updates.html new file mode 100644 index 0000000000..4e96c82bd4 --- /dev/null +++ b/data/corefork.telegram.org/api/push-updates.html @@ -0,0 +1,1009 @@ + + + + + Handling PUSH-notifications + + + + + + + + + + + + + +
+ +
+
+
+ +

Handling PUSH-notifications

+ +
+ +

Configuring the application

+

To be able to send APNS notifications to Apple servers or GCM notifications to Google servers, application certificates (APNS) or an application key (GCM) must be specified in the application settings.

+

Subscribing to notifications

+

To subscribe to notifications, the client must invoke the account.registerDevice query, passing in token_type and token as parameters that identify the current device. It is useful to repeat this query at least once every 24 hours or when restarting the application. Use account.unregisterDevice to unsubscribe.

+

The following modes are supported:

+
    +
  • 1 - APNS (device token for apple push)
  • +
  • 2 - FCM (firebase token for google firebase)
  • +
  • 3 - MPNS (channel URI for microsoft push)
  • +
  • 4 - Deprecated: Simple push (endpoint for firefox's simple push API)
  • +
  • 5 - Ubuntu phone (token for ubuntu push)
  • +
  • 6 - Blackberry (token for blackberry push)
  • +
  • 7 - MTProto separate session
  • +
  • 8 - WNS (windows push)
  • +
  • 9 - APNS VoIP (token for apple push VoIP)
  • +
  • 10 - Web push (web push, see below)
  • +
  • 11 - MPNS VoIP (token for microsoft push VoIP)
  • +
  • 12 - Tizen (token for tizen push)
  • +
+

For 10 web push, the token must be a JSON-encoded object with the following keys:

+
    +
  • endpoint: Absolute URL exposed by the push service where the application server can send push messages
  • +
  • keys: P-256 elliptic curve Diffie-Hellman parameters in the following object
      +
    • p256dh: Base64url-encoded P-256 elliptic curve Diffie-Hellman public key
    • +
    • auth: Base64url-encoded authentication secret
    • +
    +
  • +
+

Notification encryption

+

For FCM and APNS VoIP, an optional encryption key used to encrypt push notifications can be passed to account.registerDevice (secret). This key (auth_key) is used to encrypt the payloads using MTProto v2.

+

The FCM payload will be a JSON payload, containing a p field with the base64-encoded encrypted MTProto payload. After decryption, the result will be a JSON object, prefixed by a 32-bit little-endian integer with the length of the JSON payload. As usual, make sure to follow all security checks as described in the MTProto docs.

+

Example implementation.

+

As mentioned above, payloads can also be encrypted using P-256 Elliptic Curve Diffie-Hellman when using web push.

+

Notification structure

+

An (optionally encrypted) notification is provided as a JSON object in the following format:

+
{
+  "data": {
+    "loc_key": "CHAT_MESSAGE_CONTACT",
+    "loc_args": ["John Doe", "My magical group", "Contact Exchange"],
+    "user_id": 14124122,
+    "custom": {
+      "chat_id": 241233,
+      "msg_id": 123
+    },
+    "sound": "sound1.mp3",
+  }
+}
+

Each notification has several parameters that describe it.

+

Notification type

+

data.loc_key - A string literal in the form /[A-Z_0-9]+/, which summarizes the notification. For example, CHAT_MESSAGE_TEXT.

+

Notification text arguments

+

data.loc_args - A list or arguments which, when inserted into a template, produce a readable notification.

+

Custom parameters

+

data.custom - Parameters which are be passed into the application when a notification is opened.

+

Sound

+

data.sound - The name of an audio file to be played.

+

User id

+

data.user_id - ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

+

Processing notifications

+

In principle, data.loc_key, data.custom, and an Internet connection are sufficient to generate a notification. Obviously, if possible, when generating a visual notification you need not use all of the transmitted data and may rely on the information already stored on the client. But if a user or a chat is not cached locally, the values passed in loc_args may also be used. data.user_id is the ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

+

Service notifications

+

The following notifications can be used to update app settings.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeExtra custom argumentsDescription
DC_UPDATEdc - number of the data-center
addr - server address with port number in the format 111.112.113.114:443
In case the client gets this notification, it is necessary to add the received server address to the list of possible addresses. In case the address of the first DC was passed (dc=1), it is recommended to call it immediately using help.getConfig to update dc-configuration.
MESSAGE_DELETEDchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
messages: Comma-separated IDs of messages that were deleted
Messages were deleted, remove multiple notifications for this chat
READ_HISTORYchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
max_id: Maximum ID of read messages
Message history was read, remove multiple notifications for this chat
GEO_LIVE_PENDING Any of the live locations currently being shared should be updated
SESSION_REVOKE Logout and remove DB for specified session by data.user_id, only apply if coming from an MTProto-encrypted payload
MESSAGE_MUTED Sent rarely, every 10th message in chats or once per 15 sec in PM, to update badge or download messages
+

Possible Notifications

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeTemplate exampleArgumentsExtra custom arguments
AUTH_REGIONNew login from unrecognized device {1}, location: {2}1. Device name
2. Location
 
AUTH_UNKNOWNNew login from unrecognized device {1}1. Device name 
CHANNEL_MESSAGES{1} posted an album1. Message authorattachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_AUDIO{1} posted a voice message1. Message authorattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_CONTACT{1} posted a contact {2}1. Message author
2. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_DOC{1} posted a file1. Message authorattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_DOCS{1} posted {2} files1. Channel name
2. Number of documents that were posted
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_FWDS{1} posted {2} forwarded messages1. Message author
2. Number of forwarded messages
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_GAME{1} invited you to play {2}1. Message author
2. Game name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GAME_SCORE{1} scored {3} in game {2}1. User
2. Game name
3. Score
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GEO{1} posted a location1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GEOLIVE{1} posted a live location1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GIF{1} posted a GIF1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_NOTEXT{1} posted a message1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_PHOTO{1} posted a photo1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_PHOTOS{1} posted {2} photos1. Channel name
2. Number of photos that was sent
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_PLAYLIST{1} posted {2} music files1. Channel name
2. Number of audio files that were posted
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_POLL{1} posted a poll {2}1. Channel name
2. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_QUIZ{1} posted a quiz {2}1. Channel name
2. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_ROUND{1} posted a video message1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_STICKER{1} posted a {2} sticker1. Channel name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_TEXT{1}: {2}1. Channel name
2. Message body
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_VIDEO{1} posted a video1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_VIDEOS{1} posted {2} videos1. Channel name
2. Number of videos that were posted
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_ADD_MEMBER{1} invited {3} to the group {2}1. Message author
2. Chat name
3. New participant name
chat_id: chat identifier
CHAT_ADD_YOU{1} invited you to the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_CREATED{1} invited you to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_DELETE_MEMBER{1} removed {3} from the group {2}1. Message author
2. Chat name
3. Dropped participant name
chat_id: chat identifier
CHAT_DELETE_YOU{1} removed you from the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_JOINED{1} joined the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_LEFT{1} left the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_MESSAGES{1} sent an album to the group {2}1. User name
2. Group name
chat_from_id: Message author identifier
chat_id: chat identifier
mention: Whether the user was mentioned in the message
CHAT_MESSAGE_AUDIO{1} sent a voice message to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_CONTACT{1} shared a contact {3} in the group {2}1. User name
2. Group name
3. Contact name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_DOC{1} sent a file to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_DOCS{1} sent {3} files to the group {2}1. User name
2. Group name
3. Number of documents that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_FWDS{1} forwarded {3} messages to the group {2}1. User name
2. Group name
3. Number of messages that were forwarded
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_GAME{1} invited the group {2} to play {3}1. User name
2. Group name
3. Game name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GAME_SCORE{1} scored {4} in game {3} in the group {2}1. User name
2. Group name
3. Game name
4. Score
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GEO{1} sent a location to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GEOLIVE{1} shared a live location with the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GIF{1} sent a GIF to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_INVOICE{1} sent an invoice to the group {2} for {3}1. User name
2. Group name
3. Product name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_NOTEXT{1} sent a message to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_PHOTO{1} sent a photo to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_PHOTOS{1} sent {3} photos to the group {2}1. User name
2. Group name
3. Number of photos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_PLAYLIST{1} sent {3} music files to the group {2}1. User name
2. Group name
3. Number of audio files that were sent
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_POLL{1} sent a poll {3} to the group {2}1. User name
2. Group name
3. Poll name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_QUIZ{1} sent a quiz {3} to the group {2}1. User name
2. Group name
3. Quiz name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_ROUND{1} sent a video message to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_STICKER{1} sent a {3} sticker to the group {2}1. User name
2. Group name
3. Sticker emoji
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_TEXT{1} @ {2}: {3}1. Message author
2. Chat name
3. Message body
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_VIDEO{1} sent a video to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_VIDEOS{1} sent {3} videos to the group {2}1. User name
2. Group name
3. Number of videos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_PHOTO_EDITED{1} changed the group photo for {2}1. Message author
2. Chat name
chat_from_id: Message author identifier
chat_id: chat identifier
msg_id: ID of the message
CHAT_RETURNED{1} returned to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_TITLE_EDITED{1} renamed the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_VOICECHAT_END{1} ended a voice chat in the group {2}1. User name
2. Chat name
 
CHAT_VOICECHAT_INVITE{1} invited {3} to a voice chat in the group {2}1. User name
2. Chat name
3. Invited users
 
CHAT_VOICECHAT_INVITE_YOU{1} invited you to a voice chat in the group {2}1. User name
2. Chat name
 
CHAT_VOICECHAT_START{1} started a voice chat in the group {2}1. User name
2. Chat name
 
CONTACT_JOINED{1} joined Telegram!1. Contact namecontact_id: contact identifier
ENCRYPTED_MESSAGEYou have a new message encryption_id: secret chat identifier
random_id: message identifier
ENCRYPTION_ACCEPTYou have a new message encryption_id: secret chat identifier
ENCRYPTION_REQUESTYou have a new message encryption_id: secret chat identifier
LOCKED_MESSAGEYou have a new message  
MESSAGES{1} sent you an album1. User namefrom_id: author identifier
MESSAGE_ANNOUNCEMENT{1}1. Announcementannouncement: Announcement: roughly equivalent to a message received from the service notifications (Telegram Notifications, id 777000) user, but must be delivered via push notifications, without contacting the API.
MESSAGE_AUDIO{1} sent you a voice message1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_CONTACT{1} shared a contact {2} with you1. User name
2. Contact name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_DOC{1} sent you a file1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_DOCS{1} sent you {2} files1. User name
2. Number of documents that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_FWDS{1} forwarded you {2} messages1. User name
2. Number of messages that were forwarded
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_GAME{1} invited you to play {2}1. User name
2. Game name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GAME_SCORE{1} scored {3} in game {2}1. User name
2. Game name
3. Score
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GEO{1} sent you a location1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GEOLIVE{1} sent you a live location1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GIF{1} sent you a GIF1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_INVOICE{1} sent you an invoice for {2}1. User name
2. Product
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_NOTEXT{1} sent you a message1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PHOTO{1} sent you a photo1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PHOTOS{1} sent you {2} photos1. User name
2. Number of photos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_PHOTO_SECRET{1} sent you a self-destructing photo1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PLAYLIST{1} sent you {2} music files1. User name
2. Number of audio files that were sent
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_POLL{1} sent you a poll {2}1. User name
2. Poll name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_QUIZ{1} sent you a quiz {2}1. User name
2. Quiz name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_ROUND{1} sent you a video message1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_SCREENSHOT{1} took a screenshot1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_STICKER{1} sent you a {2} sticker1. User name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_TEXT{1}: {2}1. Message author
2. Message body
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_VIDEO{1} sent you a video1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_VIDEOS{1} sent you {2} videos1. User name
2. Number of videos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_VIDEO_SECRET{1} sent you a self-destructing video1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
PHONE_CALL_MISSEDYou missed a call from {1}1. User name 
PHONE_CALL_REQUEST{1} is calling you!1. User namecall_ah: Call access hash
call_id: Call ID
PINNED_AUDIO{1} pinned a voice message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_AUDIO{1} pinned a voice message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_CONTACT{1} pinned a contact {2}1. User name
2. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_CONTACT{1} pinned a contact {3} in the group {2}1. User name
2. Group name
3. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_DOC{1} pinned a file1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_DOC{1} pinned a file in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME{1} pinned a game1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME{1} pinned a game in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME_SCORE{1} pinned a game score1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME_SCORE{1} pinned a game score in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEO{1} pinned a map1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEO{1} pinned a map in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEOLIVE{1} pinned a live location1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEOLIVE{1} pinned a live location in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GIF{1} pinned a GIF1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GIF{1} pinned a GIF in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_INVOICE{1} pinned an invoice1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_INVOICE{1} pinned an invoice in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_NOTEXT{1} pinned a message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_NOTEXT{1} pinned a message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_PHOTO{1} pinned a photo1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_PHOTO{1} pinned a photo in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_POLL{1} pinned a poll {2}1. User name
2. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_POLL{1} pinned a poll {3} in the group {2}1. User name
2. Group name
3. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_QUIZ{1} pinned a quiz {2}1. User name
2. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_QUIZ{1} pinned a quiz {3} in the group {2}1. User name
2. Group name
3. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_ROUND{1} pinned a video message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_ROUND{1} pinned a video message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_STICKER{1} pinned a {2} sticker1. User name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_STICKER{1} pinned a {3} sticker in the group {2}1. User name
2. Group name
3. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_TEXT{1} pinned "{2}"1. User name
2. Message body
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_TEXT{1} pinned "{3}" in the group {2}1. User name
2. Group name
3. Message body
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_VIDEO{1} pinned a video1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_VIDEO{1} pinned a video in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/qr-login.html b/data/corefork.telegram.org/api/qr-login.html new file mode 100644 index 0000000000..1371a834c2 --- /dev/null +++ b/data/corefork.telegram.org/api/qr-login.html @@ -0,0 +1,154 @@ + + + + + Login via QR code + + + + + + + + + + + + + +
+ +
+
+
+ +

Login via QR code

+ +
+ +

QR code login flow.

+

Related TL schema:

+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+
+updateLoginToken#564fe691 = Update;
+
+authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+
+---functions---
+
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
+

Exporting a login token

+

First of all, auth.exportLoginToken must be called by the app that wants to log in to an existing Telegram account.
+The method will return an auth.loginToken constructor, containing a binary login token and an expiry date (usually 30 seconds).

+

The login token must be encoded using base64url, embedded in a tg://login?token=base64encodedtoken URL and shown in the form of a QR code to the user.
+After the expiration of the current QR code, the auth.exportLoginToken method must be recalled and a new QR code must be generated automatically.

+

Accepting a login token

+

In order to log in, the QR code must be scanned and accepted by an already logged-in Telegram app using auth.acceptLoginToken.
+The token must be extracted from the tg://login URI and base64url-decoded before using it in the method.

+

Possible errors returned by the method are:

+
    +
  • 400 - AUTH_TOKEN_INVALID, an invalid authorization token was provided
  • +
  • 400 - AUTH_TOKEN_EXPIRED, the provided authorization token has expired and the updated QR-code must be re-scanned
  • +
  • 400 - AUTH_TOKEN_ALREADY_ACCEPTED, the authorization token was already used
  • +
+

The method will return an authorization object, containing info about the app and session that we just authorized.

+

Confirming (importing) the login token

+

After the logged-in app calls auth.acceptLoginToken and accepts the login token, the app that is trying to login will receive an updateLoginToken update, which should trigger a second call to the auth.exportLoginToken method.

+

This second call should then return an auth.loginTokenSuccess constructor, indicating successful login, essentially allowing further authorized interaction with the API.

+

If, however, there is a DC mismatch between the two apps, auth.loginTokenMigrateTo is returned instead, to which the app that is trying to login should respond by calling auth.importLoginToken with the specified token, to the specified DC.

+

This call should then finally return a auth.loginTokenSuccess constructor.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/recent-actions.html b/data/corefork.telegram.org/api/recent-actions.html new file mode 100644 index 0000000000..f3ca80fe01 --- /dev/null +++ b/data/corefork.telegram.org/api/recent-actions.html @@ -0,0 +1,154 @@ + + + + + Admin log + + + + + + + + + + + + + +
+ +
+
+
+ +

Admin log

+ +
+ +

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

+
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
+channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
+channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
+
+channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;
+
+channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+
+channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true = ChannelAdminLogEventsFilter;
+
+---functions---
+
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;
+

channels.getAdminLog can be used to list recent admin activity.
+A channelAdminLogEventsFilter can be used to filter out actions of a certain type, and the admins field can be used to show only actions by certain admins.
+q can also be used to filter only logs matching a query string.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/rights.html b/data/corefork.telegram.org/api/rights.html new file mode 100644 index 0000000000..603681a672 --- /dev/null +++ b/data/corefork.telegram.org/api/rights.html @@ -0,0 +1,133 @@ + + + + + Admin, banned, default rights + + + + + + + + + + + + + +
+ +
+
+
+ +

Admin, banned, default rights

+ +
+ +

Channels and supergroups allow setting granular permissions both for admins and specific users. +Channels, supergroups and legacy groups also allow setting global granular permissions for users.

+

They can be modified as follows:

+

Admin rights

+

channels.editAdmin can be used to modify the admin rights of a user in a channel or supergroup. +Legacy groups do not allow setting granular admin permissions, messages.editChatAdmin has to be used, instead.

+

Permissions are defined by the chatAdminRights constructor, some admin rights can only be used for channels, others both for channels and supergroups (see the constructor page).

+

Banned rights

+

channels.editBanned can be used to modify the rights of a user in a channel or supergroup, to ban/kick a user from the group, or restrict the user from doing certain things. +Legacy groups do not allow setting granular user permissions for single users, single users can only be removed from groups using messages.deleteChatUser: however, setting global granular permissions with legacy groups is supported.

+

Permissions are defined by the chatBannedRights constructor, for more info see the constructor page.

+

Default rights

+

messages.editChatDefaultBannedRights can be used to modify the rights of all users in a channel, supergroup or legacy group, to restrict them from doing certain things.

+

Permissions are defined by the chatBannedRights constructor: all flags can be used except for view_messages, for more info see the constructor page.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/scheduled-messages.html b/data/corefork.telegram.org/api/scheduled-messages.html new file mode 100644 index 0000000000..7cb326abe1 --- /dev/null +++ b/data/corefork.telegram.org/api/scheduled-messages.html @@ -0,0 +1,156 @@ + + + + + Scheduled messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Scheduled messages

+ +

Telegram allows scheduling messages.

+
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updateNewScheduledMessage#39a51dfb message:Message = Update;
+updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
+
+---functions---
+
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

To schedule a message, simply provide a future unixtime in the schedule_date flag of messages.sendMessage or messages.sendMedia.

+

The specified message or media will be added to a server-side schedule queue for the current chat, and will be automatically sent at the specified time.
+The method call generates the following updates:

+
    +
  • Immediately, an updateNewScheduledMessage, with ID equal to the ID of the message in the schedule queue for the current chat (each PM, chat, supergroup and channel has its own schedule queue and ID sequence).
  • +
  • At schedule_date, an updateNewMessage or updateNewChannelMessage with the from_scheduled flag set, indicating to the sender that the specified scheduled message was sent.
  • +
  • At schedule_date, an updateDeleteScheduledMessages, indicating that the message was flushed from the schedule queue.
  • +
+

If the schedule_date is less than 10 seconds in the future, the message will be sent immediately, generating a normal updateNewMessage/updateNewChannelMessage .

+

Manipulating the schedule queue

+
updateNewScheduledMessage#39a51dfb message:Message = Update;
+updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
+
+---functions---
+
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
+messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
+messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
+
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
+

Clients can manually edit the schedule queue of a certain chat, providing the scheduled message ID obtained from updateNewScheduledMessage.

+ +

Modifying scheduled messages will generate an updateNewScheduledMessage with the same ID, and updated information.
+Deleting scheduled messages will generate an updateDeleteScheduledMessages.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/search.html b/data/corefork.telegram.org/api/search.html new file mode 100644 index 0000000000..017d38c3db --- /dev/null +++ b/data/corefork.telegram.org/api/search.html @@ -0,0 +1,179 @@ + + + + + Search + + + + + + + + + + + + + +
+ +
+
+
+ +

Search

+ +
+ +

Telegram allows applying detailed message filters while looking for messages in chats.

+

Search filters

+
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
+inputMessagesFilterPhotos#9609a51c = MessagesFilter;
+inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
+inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
+inputMessagesFilterDocument#9eddf188 = MessagesFilter;
+inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
+inputMessagesFilterGif#ffc86587 = MessagesFilter;
+inputMessagesFilterVoice#50f5c392 = MessagesFilter;
+inputMessagesFilterMusic#3751b49e = MessagesFilter;
+inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
+inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
+inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
+inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
+inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
+inputMessagesFilterGeo#e7026d0d = MessagesFilter;
+inputMessagesFilterContacts#e062db83 = MessagesFilter;
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;
+
+messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+
+---functions---
+
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
+

When using messages.search or messages.searchGlobal, a certain message filter may be applied.
+This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more. +Available filters:

+ +

The returned messages.Messages constructors contain parameters for pagination, the messages themselves and two offset_id_offset/count parameters that can be used to display a progress/total counter like photo 134 of 200.
+For example, when displaying the chat photo gallery, we could display a photo ${offset_id_offset} of ${count} indicator on top.

+

Search counters

+
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;
+
+---functions---
+
+messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;
+

Chat counters with filters can also be returned without fetching the actual messages, as seen in the schema above.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/sponsored-messages.html b/data/corefork.telegram.org/api/sponsored-messages.html new file mode 100644 index 0000000000..aa679e2b2c --- /dev/null +++ b/data/corefork.telegram.org/api/sponsored-messages.html @@ -0,0 +1,146 @@ + + + + + Sponsored messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Sponsored messages

+ +

Related TL schema:

+
sponsoredMessage flags:# random_id:bytes from_id:Peer channel_post:flags.2?int start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;
+messages.sponsoredMessages messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+
+---functions---
+
+channels.getSponsoredMessages channel:InputChannel = messages.SponsoredMessages;
+channels.viewSponsoredMessage channel:InputChannel random_id:bytes = Bool;
+

Getting sponsored messages

+

Each time the user opens a channel, channels.getSponsoredMessages must be called to receive sponsored messages available for this channel. The result must be cached for 5 minutes.

+
+

More about sponsored messages on Telegram

+
+

Displaying sponsored messages

+

Sponsored messages must be displayed below all other posts in the channel, after the user scrolls futher down, past the last message. The promoted channel or bot specified in the from_id field must be displayed as the author of the message. The message should also contain one of the following buttons at the bottom:

+
    +
  • View Bot — if a bot is being promoted. Tapping the button must open the chat with the bot. If start_param is specified, the app must use the deep linking mechanism to open the bot.
  • +
  • View Channel — if a channel is being promoted. Tapping the button must open the channel.
  • +
  • View Post — if a channel is being promoted and channel_post is specified. Tapping the button must open the particular channel post.
  • +
+

Counting sponsored message views

+

Once the entire text is shown on the screen (excluding the button), channels.viewSponsoredMessage must be called with the random_id of this sponsored message.

+

Testing sponsored messages

+

For the channel https://t.me/SecretAdTestChannel the system will always return a sponsored message: promoting either a channel, a particular message in a channel, or a bot with a start parameter.

+
+

Sponsored messages in third-party apps

+

Telegram continues to grow worldwide, in part thanks to third-party apps using the Telegram API. To cover the increasing costs that come with this growth, Telegram added sponsored messages – a paid privacy-friendly way to promote bots and channels.

+

If their app allows its users to access content from Telegram channels, third-party developers using the Telegam API are required to support and properly display official sponsored messages in their apps by January 1, 2022. Unfortunately, Telegram cannot financially sustain third-party apps that do not display sponsored messages and they will have to be disconnected.

+

Telegram's API usage will continue to be free of charge for all developers. The rules regarding monetization in third-party apps remain the same: developers are allowed to monetize their coding efforts through advertising of their own or other legitimate means, provided that all the methods of monetization used in their apps are prominently mentioned in their app store descriptions.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/srp.html b/data/corefork.telegram.org/api/srp.html new file mode 100644 index 0000000000..94f2217ee9 --- /dev/null +++ b/data/corefork.telegram.org/api/srp.html @@ -0,0 +1,307 @@ + + + + + Two-factor authentication + + + + + + + + + + + + + +
+ +
+
+
+ +

Two-factor authentication

+ +
+ +

Telegram uses the Secure Remote Password protocol version 6a to implement 2FA.

+

Example impementation: tdlib.

+

Checking the password with SRP

+

To login to an account protected by a 2FA password or to perform some other actions (like changing channel owner), you will need to verify the user's knowledge of the current 2FA account password.

+

To do this, first the client needs to obtain SRP parameters and the KDF algorithm to use to check the validity of the password via account.getPassword method. For now, only the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow algorithm is supported, so we'll only explain that.

+

Then, after the user provides a password, the client should generate an InputCheckPasswordSRP object using SRP and a specific KDF algorithm as shown below and pass it to appropriate method (e.g. auth.checkPassword in case of authorization).

+

This extension of the SRP protocol uses the password-based PBKDF2 with 100000 iterations using sha512 (PBKDF2HMACSHA512iter100000). +PBKDF2 is used to additionally rehash the x parameter, obtained using a method similar to the one described in RFC 2945 (H(s | H ( I | password | I) | s) instead of H(s | H ( I | ":" | password)) (see below).

+

Here, | denotes concatenation and + denotes the arithmetical operator +. +In all cases where concatenation of numbers passed to hashing functions is done, the numbers must be used in big-endian form, padded to 2048 bits; all maths is modulo p. +Instead of I, salt1 will be used (see SRP protocol). +Instead of s, salt2 will be used (see SRP protocol).

+

The main hashing function H is sha256:

+
    +
  • H(data) := sha256(data)
  • +
+

The salting hashing function SH is defined as follows:

+
    +
  • SH(data, salt) := H(salt | data | salt)
  • +
+

The primary password hashing function is defined as follows:

+
    +
  • PH1(password, salt1, salt2) := SH(SH(password, salt1), salt2)
  • +
+

The secondary password hashing function is defined as follows:

+
    +
  • PH2(password, salt1, salt2) := SH(pbkdf2(sha512, PH1(password, salt1, salt2), salt1, 100000), salt2)
  • +
+

Client-side, the following parameters are extracted from the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow object, contained in the account.password object.

+
    +
  • +

    g := algo.g

    +
  • +
  • +

    p := algo.p +The client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

    +

    If the client has an inadequate random number generator, it makes sense to use the secure_random of account.password as additional seed.

    +
  • +
  • +

    password := (user-provided password)

    +
  • +
  • +

    salt1 := algo.salt1

    +
  • +
  • +

    salt2 := algo.salt2

    +
  • +
  • +

    g_b := srp_B +srp_B and srp_id are extracted from the account.password object.

    +
  • +
+

The k parameter is generated, both on client and server:

+
    +
  • k := H(p | g)
  • +
+

The shared param u is generated: the client does this, and the server does the same with the g_a we will send him later (see below)

+
    +
  • u := H(g_a | g_b)
  • +
+

The final parameters are generated client-side only:

+
    +
  • x := PH2(password, salt1, salt2)
  • +
  • v := pow(g, x) mod p
  • +
+

The server already has v, from when we set the password.

+

A final shared param is generated, for commodity:

+
    +
  • k_v := (k * v) mod p
  • +
+

Finally, the key exchange process starts on both parties.

+

The client computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and generates:

+
    +
  • g_a := pow(g, a) mod p.
  • +
+

The server computes a 2048-bit number b using sufficient entropy and generates the g_b parameter that was sent to us (see above).

+
    +
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • +
+

Finally, the SRP session keys are generated:

+

Client side:

+
    +
  • t := (g_b - k_v) mod p (positive modulo, if the result is negative increment by p)
  • +
  • s_a := pow(t, a + u * x) mod p
  • +
  • k_a := H(s_a)
  • +
+

Server side:

+
    +
  • s_b := pow(g_a * (pow(v, u) mod p), b) mod p
  • +
  • k_b := H(s_b)
  • +
+

Since:

+
    +
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • +
  • t := (g_b - k_v) mod p
  • +
  • t := ((k_v + (pow(g, b) mod p)) - k_v) mod p
  • +
  • t := pow(g, b) mod p
  • +
  • s_a := pow(t, a + u * x) mod p
  • +
  • s_a := pow(pow(g, b) mod p, a + u * x) mod p
  • +
+

And:

+
    +
  • +

    g_a := pow(g, a) mod p

    +
  • +
  • +

    v := pow(g, x) mod p

    +
  • +
  • +

    s_b := pow(g_a * (pow(v, u) mod p), b) mod p

    +
  • +
  • +

    s_b := pow((pow(g, a) mod p) * (pow(pow(g, x) mod p, u) mod p), b) mod p

    +
  • +
  • +

    s_b := pow(pow(g, a + x * u) mod p, b) mod p

    +
  • +
  • +

    s_b := pow(pow(g, b) mod p, a + u * x) mod p

    +
  • +
  • +

    s_a := pow(pow(g, b) mod p, a + u * x) mod p

    +
  • +
+

This means:

+
    +
  • s_b === s_a
  • +
  • k_b === k_a
  • +
+

Finally, as per SRP:

+
    +
  • M1 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_a)
  • +
+

M1 is passed to inputCheckPasswordSRP, along with g_a (as A parameter) and the srp_id, extracted from the account.password object.

+

The server then computes:

+
    +
  • M2 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_b)
  • +
+

Since we said that:

+
    +
  • s_b === s_a
  • +
  • k_b === k_a
  • +
+

This means, if everything was done correctly,

+
    +
  • M1 === M2
  • +
+

If the password isn't correct, 400 PASSWORD_HASH_INVALID will be returned.

+

Setting a new 2FA password

+

To set a new 2FA password use the account.updatePasswordSettings method.
+If a password is already set, generate an InputCheckPasswordSRP object as per checking passwords with SRP, and insert it in the password field of the account.updatePasswordSettings method.
+To remove the current password, pass an empty new_password_hash in the account.PasswordInputSettings object.

+

To set a new password, use the SRP parameters and the KDF algorithm obtained using account.getPassword when generating the password field. +Then generate a new new_password_hash using the KDF algorithm specified in the new_settings, just append 32 sufficiently random bytes to the salt1, first. +Proceed as for checking passwords with SRP, just stop at the generation of the v parameter, and use it as new_password_hash:

+
    +
  • v := pow(g, x) mod p
  • +
+

As usual in big endian form, padded to 2048 bits.

+

Email verification

+

When setting up two-factor authorization, it is recommended to set up a recovery email, to allow recovery of the password through the user's email address, in case they forget it.

+

To set up a recovery email, it must first be verified. +This can be done directly when setting the new password using account.updatePasswordSettings by setting the email parameter and flag in the account.passwordInputSettings constructor. +If the email isn't verified, an EMAIL_UNCONFIRMED_X 400 error will be returned, where X is the length of the verification code that was just sent to the email. +Use account.confirmPasswordEmail to enter the received verification code and enable the recovery email. +Use account.resendPasswordEmail to resend the verification code. +Use account.cancelPasswordEmail to cancel the verification code.

+

To get the current recovery email, use account.getPasswordSettings.

+

Email recovery

+

In order to recover a forgotten 2FA password, an email must be sent to the previously specified address using the auth.requestPasswordRecovery method.
+Use auth.checkRecoveryPassword to make sure that the user provided a valid code.
+Then use auth.recoverPassword with the received code to delete the current 2FA password, to set a new one follow these instructions.

+

Password reset

+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+
+---functions---
+
+account.resetPassword#9308ce1b = account.ResetPasswordResult;
+account.declinePasswordReset#4c9409f6 = Bool;
+

If the user is already logged in and has forgotten their 2FA password, account.resetPassword can be used to initiate a password reset.
+On success, the call will initially return a account.resetPasswordRequestedWait constructor and start a 7-day server-side timer, during which the user can abort the reset process using a button sent by the Telegram service account or directly in-UI using account.declinePasswordReset.

+

When the time comes, account.resetPassword is invoked once more, returning a account.resetPasswordOk to indicate that the password was successfully reset.

+

If the user recently requested a password reset that was canceled, account.resetPasswordFailedWait will be returned by the initial account.resetPassword call, and they must wait until the specified date before requesting another reset.

+

Note that if the user already knows their 2FA password and simply wants to disable 2FA, the same process used to enable the password must also be used to disable it ».

+

Related pages

+

SRP design

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/stats.html b/data/corefork.telegram.org/api/stats.html new file mode 100644 index 0000000000..52dda65ee3 --- /dev/null +++ b/data/corefork.telegram.org/api/stats.html @@ -0,0 +1,297 @@ + + + + + Channel statistics + + + + + + + + + + + + + +
+ +
+
+
+ +

Channel statistics

+ +
+ +

Telegram offers detailed channel statistics for channels and supergroups.

+

Channel statistics

+

Schema:

+
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;
+
+statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;
+
+statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;
+
+statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+
+messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;
+
+stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+
+---functions---
+
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
+

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getBroadcastStats to get detailed channel statistics.
+The returned stats.broadcastStats contains multiple statistics:

+
    +
  • Period-related statistics: a pair of values, one at the beginning and one at the end of the period in consideration (period).
    The period typically depends on channel activity.
      +
    • Absolute follower count (followers)
    • +
    • total_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
      +Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
    • +
    • total_sharecount/postcount, for posts posted during the period in consideration (shares_per_post).
      +Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
    • +
    +
  • +
  • Percentage statistics
      +
    • Percentage of subscribers with enabled notifications (enabled_notifications)
    • +
    +
  • +
  • Graphs: graphs are described below ».
  • +
+

Supergroup statistics

+

Schema:

+
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;
+statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;
+statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;
+
+stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
+
+---functions---
+
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;
+

Administrators of supergroups of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMegagroupStats to get detailed supergroup statistics.
+The returned stats.broadcastStats contains multiple statistics, see the constructor page for more info ».

+

Message statistics

+
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
+
+---functions---
+
+stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;
+

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMessageStats to get statistics of a specific message.
+The returned stats.messageStats contains the view graph of the message.

+

Graph visualization

+

There are four available visualizations for graph types:

+ +

Graph modifiers (see various graphs for examples):

+
    +
  • y_scaled - Indicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph
  • +
  • percentage - Indicates whether value percentages should be shown in labels
  • +
  • stacked - Depending on the graph type, indicates stacking of multiple columns in the same graph
  • +
+

Graph syntax

+
statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+
+dataJSON#7d748d04 data:string = DataJSON;
+
+---functions---
+
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
+

Certain graphs are not directly sent in the stats.broadcastStats constructor to reduce server load: instead, those graphs will be sent as a statsGraphAsync constructor, and should be fetched separately using stats.loadAsyncGraph.

+

After obtaining the full statsGraph constructor, clients should parse the JSON graph object in the json field.

+

Object structure:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
KeyGraph title
columnsArray of all data column arrays in the chart. Each column array has its label at position 0, followed by values.
typesGraphs types for each of the column arrays (object, "label": "type"):
- line - line graph
- area - area graph
- step - step graph
- bar - bar graph
- x - x axis values for each of the charts at the corresponding positions, UNIX timestamps in milliseconds.
colorsColor for each type (object, "label": "colorKey#AAAAAA"; see chart colors).
namesLocalized name for each variable (object, "label": "Name")
subchartObject indicating the default zoom range for the graph, this is object's structure:
- show - Whether to use the specified zoom range (boolean)
- defaultZoom - An array with two x values, indicating the two ends of the default zoom range
y_scaledIndicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph (boolean, see various graphs for examples)
percentageIndicates whether value percentages should be shown in labels (boolean, see various graphs for examples)
stackedDepending on the graph type, indicates stacking of multiple columns in the same graph (boolean, see various graphs for examples)
+ +

The following chart restrictions apply:

+
    +
  • Up to 50 columns on one graph must be supported.
  • +
  • Chart types are always the same for every column in the graph.
  • +
  • The bar chart type and stacked option are always used together.
  • +
  • percentage is always used with the area graph. + +
  • +
+

Chart zooming

+
statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+
+dataJSON#7d748d04 data:string = DataJSON;
+
+---functions---
+
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
+

Graphs that support zooming will contain a zoom_token in the statsGraph constructor.
+Said token should be then used as token in a new stats.loadAsyncGraph call triggered when the user clicks on the label, related to a certain x axis in the graph (see graph examples).
+The x coordinate of the label should be provided to the x parameter; the method will then return (if available) a more detailed subgraph.
+If not enough data is available, a localized statsGraphError will be returned.

+

Typical zoom visualization rules:

+ +

Chart colors

+

Chart colors can be provided as a color key, followed by the primary color value in hex format:

+
red#e05356
+

The color key can be one of red, lightblue, lightgreen, golden, green, orange, blue, indigo.
+Apps can choose to use a color value specified by the currently loaded theme: for example, the android app uses statisticChartLine_* themekeys for each of the color keys, check out the assets directory for a bunch of default themes with various colors for channel statistics.

+

However, the server may also choose to return just a plain color value in hex format:

+
#e05356
+

In this case, the dark flag of the stats.getBroadcastStats method can be used to choose the palette of returned colors.

+

Graph examples

+

Line graph

+

Simple single line graph

+

Step graph

+

Step graph, always "stacked" (to indicate multiple lines)

+

Bar graph

+

Bar graph with multiple lines, always "stacked" (to indicate actual stacked bars, biggest bars first)

+

Area graph

+

Mixed bar/line graph, always "stacked" (to indicate actual stacked bars, biggest bars first)

+

Piechart

+

Piechart, typically obtained only when zooming into percentage graphs

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/terms.html b/data/corefork.telegram.org/api/terms.html new file mode 100644 index 0000000000..a049063beb --- /dev/null +++ b/data/corefork.telegram.org/api/terms.html @@ -0,0 +1,133 @@ + + + + + Telegram API Terms of Service + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram API Terms of Service

+ +
+ +

We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge. In order to ensure consistency and security across the Telegram ecosystem, all third-party client apps must comply with the following Terms of Service.

+

1. Privacy & Security

+

1.1. Telegram is a privacy-oriented platform. All client apps must, therefore, guard their users' privacy with utmost care and comply with our Security Guidelines.
1.2. Developers are welcome to add new features or improve and extend existing Telegram features provided that these modifications do not violate these Terms of Service.
1.3. As a client developer, you must make sure that all the basic features of the main Telegram apps function correctly and in an expected way both in your app and when users of your app communicate with other Telegram users. It is forbidden to force users of other Telegram clients to download your app in order to view certain messages and content sent using your app.
1.4. It is forbidden to interfere with the basic functionality of Telegram. This includes but is not limited to: making actions on behalf of the user without the user's knowledge and consent, preventing self-destructing content from disappearing, preventing last seen and online statuses from being displayed correctly, tampering with the 'read' statuses of messages (e.g. implementing a 'ghost mode'), preventing typing statuses from being sent/displayed, etc.

+

2. Transparency

+

2.1. You must obtain your own api_id for your application.
2.2. We offer our API free of charge, but your users must be aware of the fact that your app uses the Telegram API and is part of the Telegram ecosystem. This fact must be featured prominently in the app's description in the app stores and in the in-app intro if your app has it.
2.3. To avoid confusion, the title of your app must not include the word “Telegram”. An exception can be made if the word “Telegram” is preceded with the word “Unofficial” in the title.
2.4. You must not use the official Telegram logo for your app. Both the Telegram brand and its logo are registered trademarks protected by law in almost every country.

+

3. Advertising & Monetization

+

3.1. Developers are allowed to monetize their coding efforts through advertising or other legitimate means.
3.2. If you decide to monetize your app, you must clearly mention all the methods of monetization that are used in your app in all its app store descriptions.
3.3. If your app allows accessing content from Telegram channels, you must include support for official sponsored messages in Telegram channels and may not interefere with this functionality.

+

4. Breach of terms

+

4.1. If your app violates these terms, we will notify the Telegram account responsible for the app about the breach of terms.
4.2. If you do not update the app to fix the highlighted issues within 10 days, we will have to discontinue your access to Telegram API and contact the app stores about the removal of your apps that are using the Telegram API in violation of these terms.

+

We reserve the right to expand these terms and guidelines as the need arises. We will inform client developers of such changes via an in-app notification to their accounts connected to the app in question.

+
+

Back to Creating Your Telegram Application »

+
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/threads.html b/data/corefork.telegram.org/api/threads.html new file mode 100644 index 0000000000..9cfb6dc8ed --- /dev/null +++ b/data/corefork.telegram.org/api/threads.html @@ -0,0 +1,182 @@ + + + + + Threads + + + + + + + + + + + + + +
+ +
+
+
+ +

Threads

+ +
+ +

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Message threads

+

Schema:

+
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
+
+messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+---functions---
+
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+

Threads are usually automatically created when replying to any message in a group.
+For example, all replies to a message with ID 420 are associated to thread with ID 420, unique to this group; this thread ID is contained in the reply_to_top_id field of reply_to messageReplyHeader, along with an eventual reply_to_msg_id, for replies to messages within a thread.
+Replies to messages in a thread are part of the same thread, and do not spawn new threads.

+

When receiving a message from a group that is also the top of a thread (the message with ID 420), the replies optional field will contain a messageReplies constructor, containing the message ID and PTS of the latest reply in the thread, and the message ID of the latest read thread reply, along with the total number of replies in the thread.

+

Replies to a thread can also be manually fetched using messages.search, providing to top_msg_id the thread ID.

+

Channel comments

+
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
+

The same messageReplies constructor seen above will also be contained in channel posts, this time containing information about the comment section of a specific channel post.
+The comment section of a channel post is simply the message thread of the automatically forwarded channel message in the linked discussion supergroup; the ID of the linked discussion supergroup will be contained in the messageReplies.channel_id field.

+

For channel posts, the recent_repliers field will also contain information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.

+

@replies

+
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
+
+messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
+
+---functions---
+
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
+
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
+

Since a user can comment in channel posts without joining the actual discussion supergroup, there must be a way for them to receive notifications about replies in comment sections.
+For this reason, a special @replies username is provided. +Its ID for main and testing endpoints can be seen in the tdlib sources.

+

When someone replies to one of our messages in the comment section of a channel post, and the user is not subscribed to the discussion group, the client will receive two updates:

+
    +
  • An updateNewChannelMessage from the discussion group itself, structured just like any other update coming from a subscribed group, with:
      +
    • id set to the ID of the reply
    • +
    • from_id set to the peer that replied to us
    • +
    • peer_id set to the peer of the discussion group
    • +
    • reply_to.reply_to_msg_id set to the ID of our message
    • +
    • reply_to.reply_to_top_id set to the thread ID.
    • +
    +
  • +
  • An updateNewMessage
      +
    • id set to the common ID sequence for users
    • +
    • from_id set to the peer of @replies
    • +
    • peer_id set to our own peer
    • +
    • fwd_from.saved_from_msg_id set to the ID of the reply
    • +
    • fwd_from.from_id set to the the peer that replied to us
    • +
    • reply_to.reply_to_peer_id set to the peer of the discussion group
    • +
    • reply_to.reply_to_msg_id set to the ID of our message
    • +
    • reply_to.reply_to_top_id set to the thread ID
    • +
    +
  • +
+

Clients should display messages coming from @replies as a read-only supergroup, with each reply displayed as a separate message from the author of the reply, with a "View in chat" button like for channel comments.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/top-rating.html b/data/corefork.telegram.org/api/top-rating.html new file mode 100644 index 0000000000..2ac9ea8ff4 --- /dev/null +++ b/data/corefork.telegram.org/api/top-rating.html @@ -0,0 +1,145 @@ + + + + + Top peer rating + + + + + + + + + + + + + +
+ +
+
+
+ +

Top peer rating

+ +

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+

Schema:

+
topPeer#edcdc05b peer:Peer rating:double = TopPeer;
+
+topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
+topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
+topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
+topPeerCategoryGroups#bd17a14a = TopPeerCategory;
+topPeerCategoryChannels#161d9628 = TopPeerCategory;
+topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
+topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
+topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;
+
+topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;
+
+contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+
+---functions---
+
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;
+

The rate delta is computed by taking the time delta between the last time the user used a certain peer and the last time the rating for that peer was received and dividing it by the exponential decay from config.

+

Example: +Client-side, every time a user opens chat 123456789 the following operation must be done on the cached top peer info.

+
    +
  • dateOpened indicates when was the peer used
  • +
  • normalizeRate is an arbitrary time in the recent past. +When ratings are received from the server using contacts.getTopPeers and the schema described above, it is the time when they were received.
  • +
+
topPeer.rating += e^((dateOpened - normalizeRate) / config.rating_e_decay)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/updates.html b/data/corefork.telegram.org/api/updates.html new file mode 100644 index 0000000000..46c6067ad9 --- /dev/null +++ b/data/corefork.telegram.org/api/updates.html @@ -0,0 +1,226 @@ + + + + + Working with Updates + + + + + + + + + + + + + +
+ +
+
+
+ +

Working with Updates

+ +
+ +

When a client is being actively used, events will occur that affect the current user and that they must learn about as soon as possible, e.g. when a new message is received. To eliminate the need for the client itself to periodically download these events, there is an update delivery mechanism in which the server sends the user notifications over one of its available connections with the client.

+

Subscribing to Updates

+

Update events are sent to an authorized user into the last active connection (except for connections needed for downloading / uploading files).

+

So to start receiving updates the client needs to init connection and call API method, e.g. to fetch current state.

+

Event sequences

+

All events are received from the socket as a sequence of TL-serialized Updates objects, which might be optionally gzip-compressed in the same way as responses to queries.

+

Each Updates object may contain single or multiple Update objects, representing different events happening.

+

In order to apply all updates in precise order and to guarantee that no update is missed or applied twice there is seq attribute in Updates constructors, and pts (with pts_count) or qts attributes in Update constructors. The client must use those attributes values in combination with locally stored state to correctly apply incoming updates.

+

When a gap in updates sequence occurs, it must be filled via calling one of the API methods. More below »

+

Updates sequence

+

As said earlier, each payload with updates has a TL-type Updates. It can be seen from the schema below that this type has several constructors.

+
updatesTooLong#e317af7e = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+

updatesTooLong indicates that there are too many events pending to be pushed to the client, so one needs to fetch them manually.

+

Events inside updateShort constructors, normally, have lower priority and are broadcast to a large number of users, i.e. one of the chat participants started entering text in a big conversation (updateChatUserTyping).

+

The updateShortMessage, updateShortSentMessage and updateShortChatMessage constructors are redundant but help significantly reduce the transmitted message size for 90% of the updates. They should be transformed to updateShort upon receiving.

+

Two remaining constructors updates and updatesCombined are part of the Updates sequence. Both of them have seq attribute, which indicates the remote Updates state after the generation of the Updates, and seq_start indicates the remote Updates state after the first of the Updates in the packet is generated. For updates, seq_start attribute is omitted, because it is assumed that it is always equal to seq.

+

Message-related event sequences

+

Each event related to a message box (message created, message edited, message deleted, etc) is identified by a unique autoincremented pts, or qts in case of secret chat updates, certain bot updates, etc.

+

Each message box can be considered as some server-side DB table that stores messages and events associated with them. +All boxes are completely independent, and each pts sequence is tied to just one box (see below).

+

Update object may contain info about multiple events (for example, updateDeleteMessages). +That's why all single updates might have pts_count parameter indicating the number of events contained in the received update (with some exceptions, in this case, the pts_count is considered to be 0).

+

Each channel and supergroup has its message box and its event sequence as a result; private chats and legacy groups of one user have another common event sequence. +Secret chats, certain bot events and other kinds of updates have yet another common secondary event sequence.

+

To recap, the client has to take care of the integrity of the following sequences to properly handle updates:

+
    +
  • Updates sequence (seq)
      +
    • Common message box sequence (pts)
    • +
    • Secondary event sequence (qts)
    • +
    • Channel message box sequence 1 (pts)
    • +
    • Channel message box sequence 2 (pts)
    • +
    • Channel message box sequence 3 (pts)
    • +
    • and so on...
    • +
    +
  • +
+

Fetching state

+

The common update state is represented by the updates.State constructor. +When the user logs in for the first time, call to updates.getState has to be made to store the latest update state (which will not be the absolute initial state, just the latest state at the current time). +The common update state can also be fetched from updates.differenceTooLong.

+

The channel update state is represented simply by the pts of the event sequence: when first logging in, the initial channel state can be obtained from the dialog constructor when fetching dialogs, from the full channel info, or it can be received as an updateChannelTooLong update.

+

The secondary update state is represented by the qts of the secret event sequence, it is contained in the updates.State of the common update state.

+

The Updates sequence state is represented by the date and seq of the Updates sequence, it is contained in the updates.State of the common update state.

+

Update handling

+

Update handling in Telegram clients consists of receiving events, making sure there were no gaps and no events were missed based on the locally stored state of the correspondent event sequence, and then updating the locally stored state based on the parameters received.

+

When the client receives payload with serialized updates, first of all, it needs to walk through all of the nested Update objects and check if they belong to any of message box sequences (have pts or qts parameters). Those updates need to be handled separately according to corresponding local state and new pts/qts values. Details below »

+

After message box updates are handled, if there are any other updates remaining the client needs to handle them with respect to seq. Details below »

+

pts: checking and applying

+

Here, local_pts will be the local state, pts will be the remote state, pts_count will be the number of events in the update.

+

If local_pts + pts_count === pts, the update can be applied. +If local_pts + pts_count > pts, the update was already applied, and must be ignored. +If local_pts + pts_count < pts, there's an update gap that must be filled.

+

For example, let's assume the client has the following local state for the channel 123456789:

+
local_pts = 131
+

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. +Since local_pts + pts_count === pts, the total number of events since the last stored state is, in fact, equal to pts_count: this means the update can be safely accepted and the remote pts applied:

+
local_pts = 132
+

Since:

+
    +
  • pts indicates the server state after the new channel message events are generated
  • +
  • pts_count indicates the number of events in the new channel update
  • +
  • The server state before the new channel message event was generated has to be: pts_before = pts - pts_count = 131, which is, in fact, equal to our local state.
  • +
+

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. +Since local_pts + pts_count > pts (133 > 132), the update is skipped because we've already handled this update (in fact, our current local_pts was set by this same update, and it was resent twice due to network issues or other issues).

+

Now let's assume an updateDeleteChannelMessages from channel 123456789 is received with pts = 140 and pts_count=5. +Since local_pts + pts_count < pts (137 < 140), this means that updates were missed, and the gap must be recovered.

+
Secret chats & bots
+

The whole process is very similar for secret chats and certain bot updates, but there is qts instead of pts, and events are never grouped, so it's assumed that qts_count is always equal to 1.

+

seq: checking and applying

+

On top level when handling received updates and updatesCombined there are three possible cases: +If local_seq + 1 === seq_start, the updates can be applied. +If local_seq + 1 > seq_start, the updates were already applied, and must be ignored. +If local_seq + 1 < seq_start, there's an updates gap that must be filled (updates.getDifference must be used as with common and secret event sequences).

+

If the updates were applied, local Updates state must be updated with seq and date from the constructor.

+

For all the other Updates type constructors there is no need to check seq or change a local state.

+

Recovering gaps

+

To do this, updates.getDifference (common/secret state) or updates.getChannelDifference (channel state) with the respective local states must be called. +These methods should also be called on startup, to fetch new updates (preferably with some flags to reduce server load, see the method's docs). +Manually obtaining updates is also required in the following situations:

+
    +
  • Loss of sync: a gap was found in seq / pts / qts (as described above). It may be useful to wait up to 0.5 seconds in this situation and abort the sync in case a new update arrives, that fills the gap.
  • +
  • Session loss on the server: the client receives a new session created notification. This can be caused by garbage collection on the MTProto server or a server reboot.
  • +
  • Incorrect update: the client cannot deserialize the received data.
  • +
  • Incomplete update: the client is missing data about a chat/user from one of the shortened constructors, such as updateShortChatMessage, etc.
  • +
  • Long period without updates: no updates for 15 minutes or longer.
  • +
  • The server requests the client to fetch the difference using updateChannelTooLong or updatesTooLong.
  • +
+

When calling updates.getDifference if the updates.differenceSlice constructor is returned in response, the full difference was too large to be received in one request. The intermediate status, intermediate_state, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

+

To fetch the updates difference of a channel, updates.getChannelDifference is used. +If the difference is too large to be received in one request, the final flag of the result is not set (see docs). +The intermediate status, represented by the pts, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

+

For perfomance reasons and for better user experience, client can set maximum gap size to be filled: pts_total_limit parameter of updates.getDifference and limit parameter for updates.getChannelDifference can be used.

+

If the gap is too large and there are too many updates to fetch, a *TooLong constructor will be returned. In this case, the client must re-fetch the state, re-start fetching updates from that state and follow the instructions that can be found here.

+

It is recommended to use limit 10-100 for channels and 1000-10000 otherwise.

+

Example implementations

+

Implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence.

+

Example implementations: tdlib, MadelineProto.

+

An interesting and easy way this can be implemented, instead of using various locks, is by running background loops, like in MadelineProto ».

+

PUSH Notifications about Updates

+

If a client does not have an active connection at the time of an event, PUSH Notifications will also be useful.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/url-authorization.html b/data/corefork.telegram.org/api/url-authorization.html new file mode 100644 index 0000000000..365eb87458 --- /dev/null +++ b/data/corefork.telegram.org/api/url-authorization.html @@ -0,0 +1,160 @@ + + + + + Seamless Telegram Login + + + + + + + + + + + + + +
+ +
+
+
+ +

Seamless Telegram Login

+ +
+ +

Bots or Telegram websites may ask users to login to a certain website via Telegram when clicking on certain links or URL buttons in inline keyboards.

+

Bot URL authorization

+

When the user clicks on keyboardButtonUrlAuth, messages.requestUrlAuth should be called, providing the button_id of the button and the ID and peer of the container message. +The returned urlAuthResultRequest object will contain more details about the authorization request:

+
    +
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • +
  • The bot parameter will contain info about the bot which will be used for user authorization (example: DiscussBot).
  • +
  • The request_write_access will be set if the bot would like to send messages to the user.
  • +
+

The info should be shown in a prompt:

+
+ TITLE +
+

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). +The result will be a urlAuthResultAccepted with the final URL to open, which will include a query string with the requested info and a hash that must be verified upon receival by the service.

+

urlAuthResultDefault could also be returned, instead, in which case the url of the keyboardButtonUrlAuth must be opened, instead. +The same must be done if the user opens the link while refusing the authorization request.

+

Link URL authorization

+

Telegram supports automatic authorization on certain websites upon opening an HTTP URL in-app, upon clicking a link in a message or clicking on a keyboardButtonUrl.

+

Automatic authorization

+

Clients should automatically authenticate users when opening official Telegram websites, listed in the url_auth_domains key of the client configuration object ».

+

Upon clicking a link, the URL must be modified by appending the autologin_token from the client configuration object » to the query string, like so:

+

Original URL: https://somedomain.telegram.org/path?query=string#fragment=value
+Modified URL: https://somedomain.telegram.org/path?query=string&autologin_token=$autologin_token#fragment=value

+

Make sure that the used autologin_token is no more than 10000 seconds old, if it is older it must be refetched before use as described in the client configuration section ».

+

Manual authorization

+

Clients should show a confirmation prompt similar to the one used for bots, to authenticate users when opening certain Telegram websites, listed in the url_auth_domains key of the client configuration object ».

+

messages.requestUrlAuth should be called, providing only the original url. +The returned urlAuthResultRequest object will contain more details about the authorization request:

+
    +
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • +
  • The request_write_access will be set if the website would like to send messages to the user.
  • +
+

The info should be shown in a prompt.

+

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). +The result will be a urlAuthResultAccepted with the final URL to open.

+

urlAuthResultDefault could also be returned, instead, in which case the original URL must be opened, instead. +The same must be done if the user opens the link while refusing the authorization request.

+

Related articles

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/web-events.html b/data/corefork.telegram.org/api/web-events.html new file mode 100644 index 0000000000..ffe0ed4019 --- /dev/null +++ b/data/corefork.telegram.org/api/web-events.html @@ -0,0 +1,175 @@ + + + + + Web events + + + + + + + + + + + + + +
+ +
+
+
+ +

Web events

+ +
+ +

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose APIs to allow receiving data and events from the websites.

+

Event APIs

+

Games and payment gateways can generate events that are meant to be received by the Telegram apps.
Typically events are generated by using the postEvent method of the GamingCommunication library.
The postEvent function will try sending the event to the Telegram app in a number of different ways.

+

WebviewProxy

+

In mobile apps, the event receiver API should be typically exposed as a window.TelegramWebviewProxy object with a postEvent method.

+
window.TelegramWebviewProxy.postEvent(eventType, eventData)
+

window.external

+

Alternatively, a window.external.notify method can be exposed, accepting a string JSON payload with the event type and payload:

+
window.external.notify(JSON.stringify({eventType: eventType, eventData: eventData}));
+

postMessage API

+

Finally, web MTProto clients that need to open a game or process a payment in an iframe can use the postMessage API to receive events from iframes.
The GamingCommunication library by default will use '*' as targetOrigin, sending messages to parent pages regardless of the origin of the embedder.

+
window.parent.postMessage(JSON.stringify({eventType: eventType, eventData: eventData}), targetOrigin);
+

Event types

+

eventType is a simple string indicating the event type, and eventData is a payload with an object that will be parsed by the Telegram app.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
eventTypeeventDataDescription
payment_form_submitJSON object with data and title fieldstitle is the censored credit card title.
data is a service-specific JSON payload with information about the payment credentials provided by the user to the payment system.
Neither Telegram, nor bots will have access to your credit card information.
Credit card details will be handled only by the payment system.
share_scorenullWill be called by games when the user explicitly clicks on the share score button to share the game, along with his score.
Typically done by using messages.forwardMessages on the game message with the with_my_score flag.
share_gamenullWill be called by games when the user explicitly clicks on the share game button to share the game, without sharing his score.
Typically done by using messages.forwardMessages on the game message without the with_my_score flag, or by sharing the game's short URL.
game_overnullCan be called by games when the user loses a game
game_loadednullCan be called by games once the game fully loads
resize_frameJSON object with height fieldCalled by supported pages inside of IV iframe embeds, indicates the new size of the embed frame.
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html b/data/corefork.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html new file mode 100644 index 0000000000..97d4e3ec39 --- /dev/null +++ b/data/corefork.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+
+

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/bots.html b/data/corefork.telegram.org/bots.html new file mode 100644 index 0000000000..c2070b62dc --- /dev/null +++ b/data/corefork.telegram.org/bots.html @@ -0,0 +1,420 @@ + + + + + Bots: An introduction for developers + + + + + + + + + + + + + +
+ +
+
+
+
+

Bots: An introduction for developers

+ +
+ +

Bots are third-party applications that run inside Telegram. Users can interact with bots by sending them messages, commands and inline requests. You control your bots using HTTPS requests to our Bot API.

+

1. What can I do with bots?

+
+ +
+

To name just a few things, you could use bots to:

+
    +
  • +

    Get customized notifications and news. A bot can act as a smart newspaper, sending you relevant content as soon as it's published.

    +
  • +
  • +

    Integrate with other services. A bot can enrich Telegram chats with content from external services. +Gmail Bot, GIF bot, IMDB bot, Wiki bot, Music bot, Youtube bot, GitHubBot

    +
  • +
  • +

    Accept payments from Telegram users. A bot can offer paid services or work as a virtual storefront. Read more » +Demo Shop Bot, Demo Store

    +
  • +
  • +

    Create custom tools. A bot may provide you with alerts, weather forecasts, translations, formatting or other services. +Markdown bot, Sticker bot, Vote bot, Like bot

    +
  • +
  • +

    Build single- and multiplayer games. A bot can offer rich HTML5 experiences, from simple arcades and puzzles to 3D-shooters and real-time strategy games. +GameBot, Gamee

    +
  • +
  • +

    Build social services. A bot could connect people looking for conversation partners based on common interests or proximity.

    +
  • +
  • +

    Do virtually anything else. Except for dishes — bots are terrible at doing the dishes.

    +
  • +
+

2. How do bots work?

+

At the core, Telegram Bots are special accounts that do not require an additional phone number to set up. Users can interact with bots in two ways:

+
    +
  • Send messages and commands to bots by opening a chat with them or by adding them to groups.
  • +
  • Send requests directly from the input field by typing the bot's @username and a query. This allows sending content from inline bots directly into any chat, group or channel.
  • +
+

Messages, commands and requests sent by users are passed to the software running on your servers. Our intermediary server handles all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API. We call that interface our Bot API.

+
+

A detailed description of the Bot API is available on this page »

+
+

3. How do I create a bot?

+
+ +
+

There's a... bot for that. Just talk to BotFather (described below) and follow a few simple steps. Once you've created a bot and received your authentication token, head down to the Bot API manual to see what you can teach your bot to do.

+
+

You may also like to check out some code examples here »

+
+

4. How are bots different from humans?

+
    +
  • Bots have no online status and no last seen timestamps, the interface shows the label 'bot' instead.
  • +
  • Bots have limited cloud storage — older messages may be removed by the server shortly after they have been processed.
  • +
  • Bots can't initiate conversations with users. A user must either add them to a group or send them a message first. People can use t.me/<bot_username> links or username search to find your bot.
  • +
  • Bot usernames always end in 'bot' (e.g. @TriviaBot, @GitHub_bot).
  • +
  • When added to a group, bots do not receive all messages by default (see Privacy mode).
  • +
  • Bots never eat, sleep or complain (unless expressly programmed otherwise).
  • +
+
+

5. Bot perks

+

Telegram bots are unique in many ways — we offer two kinds of keyboards, additional interfaces for default commands and deep linking as well as text formatting, integrated payments and more.

+

Inline mode

+ +

Users can interact with your bot via inline queries straight from the text input field in any chat. All they need to do is start a message with your bot's username and then type a query.

+

Having received the query, your bot can return some results. As soon as the user taps one of them, it is sent to the user's currently opened chat. This way, people can request content from your bot in any of their chats, groups or channels.

+

Check out this blog to see a sample inline bot in action. You can also try the @sticker and @music bots to see for yourself.

+
+
+
+

We've also implemented an easy way for your bot to switch between inline and PM modes.

+
+

Read more about the Inline Mode »

+
+

Payment platform

+ +

You can use bots to accept payments from Telegram users around the world.

+
    +
  • Send invoices to any chat, including to groups and channels.
  • +
  • Create invoices that can be forwarded and used by multiple buyers to order things.
  • +
  • Use inline mode to help users show your goods and services to their friends and communities.
  • +
  • Allow tips from users with preset and custom amounts.
  • +
  • Accept payments from users on mobile or desktop apps.
  • +
  • Try @ShopBot to create a test invoice – or start a message with @ShopBot ... in any chat for an inline invoice.
  • +
  • Check out Demo Shop for an example of a Telegram Channel used as virtual storefront.
  • +
+
+ +
+
+

Read more about the Payments Platform »

+
+

Gaming platform

+

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. The platform allows your bot to keep track of high scores for every game played in every chat. Whenever there’s a new leader in the game, other playing members in the chat are notified that they need to step it up.

+
+ + +
+
+

Since the underlying technology is HTML5, the games can be anything from simple arcades and puzzles to multiplayer 3D-shooters and real-time strategy games. Our team has created a couple of simple demos for you to try out:

+ +

You can also check out the @gamee bot that has more than 20 games.

+
+

Read more about the Gaming Platform »

+
+

Keyboards

+

Traditional chat bots can of course be taught to understand human language. But sometimes you want some more formal input from the user — and this is where custom keyboards can become extremely useful.

+

Whenever your bot sends a message, it can pass along a special keyboard with predefined reply options (see ReplyKeyboardMarkup). Telegram apps that receive the message will display your keyboard to the user. Tapping any of the buttons will immediately send the respective command. This way you can drastically simplify user interaction with your bot.

+

We currently support text and emoji for your buttons. Here are some custom keyboard examples:

+
+
+ +
<a href="/file/811140880/1/jS-YSVkDCNQ/b397dfcefc6da0dc70" target="_blank"><img src="/file/811140880/1/jS-YSVkDCNQ/b397dfcefc6da0dc70" title="Keyboard for a calculator bot. Because you can." style="max-height: 300px; padding: 10px 5px" /></a>
+
+<a href="/file/811140733/2/KoysqJKQ_kI/a1ee46a377796c3961" target="_blank"><img src="/file/811140733/2/KoysqJKQ_kI/a1ee46a377796c3961" title="Keyboard for a trivia bot" style="max-height: 300px; padding: 10px 5px" /></a>
+
+
+

For more technical information on custom keyboards, please consult the Bot API manual (see sendMessage).

+
+

Inline keyboards and on-the-fly updating

+

There are times when you'd prefer to do things without sending any messages to the chat. For example, when your user is changing settings or flipping through search results. In such cases you can use Inline Keyboards that are integrated directly into the messages they belong to.

+

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

+
+ + + +
+
+

When callback buttons are used, your bot can update its existing messages (or just their keyboards) so that the chat remains tidy. Check out these sample bots to see inline keyboards in action: @music, @vote, @like.

+
+

Read more about inline keyboards and on-the-fly editing »

+
+

Commands

+

Commands present a more flexible way to communicate with your bot. The following syntax may be used:

+
/command
+

A command must always start with the '/' symbol and may not be longer than 32 characters. Commands can use latin letters, numbers and underscores. Here are a few examples:

+
/get_messages_stats
+/set_timer 10min Alarm!
+/get_timezone London, UK
+

Messages that start with a slash are always passed to the bot (along with replies to its messages and messages that @mention the bot by username). Telegram apps will:

+
    +
  • Suggest a list of supported commands with descriptions when the user enters a '/' (for this to work, you need to have provided a list of commands to the BotFather). Tapping on a command in the list immediately sends the command.
  • +
  • Show an additional (/) button in the input field in all chats with bots. Tapping it types a '/' and shows the list of commands.
  • +
  • Highlight /commands in messages. When the user taps a highlighted command, the command is sent at once.
  • +
+
+ +
<a href="/file/811140315/2/gf7_D2HbeyM/e3ca2de4de7918f826" target="_blank"><img src="/file/811140315/2/gf7_D2HbeyM/e3ca2de4de7918f826" title="Notice the new button in the input field, right next to the sticker button" style="width: 230px; padding: 10px 5px" /></a>
+
+
+<a href="/file/811140029/1/s5zv4fbWdhw/a04aefa0ee0557f16a" target="_blank"><img src="/file/811140029/1/s5zv4fbWdhw/a04aefa0ee0557f16a" title="Suggested commands for multiple bots" style="width: 230px; padding: 10px 5px" /></a>
+
+

If multiple bots are in a group, it is possible to add bot usernames to commands in order to avoid confusion:

+
/start@TriviaBot
+/start@ApocalypseBot
+

This is done automatically when commands are selected via the list of suggestions. Please remember that your bot needs to be able to process commands that are followed by its username.

+
Global commands
+

In order to make it easier for users to navigate the bot multiverse, we ask all developers to support a few basic commands. Telegram apps will have interface shortcuts for these commands.

+
    +
  • /start - begins interaction with the user, e.g., by sending a greeting message. This command can also be used to pass additional parameters to the bot (see Deep linking)
  • +
  • /help - returns a help message. It can be a short text about what your bot can do and a list of commands.
  • +
  • /settings - (if applicable) returns the bot's settings for this user and suggests commands to edit these settings.
  • +
+

Users will see a Start button when they first open a conversation with your bot. Help and Settings links will be available in the menu on the bot's profile page.

+
+ +
<a href="/file/811140479/2/1c2zUWhR7sA/98889b2a45f8e42a35" target="_blank"><img src="/file/811140479/2/1c2zUWhR7sA/98889b2a45f8e42a35" title="A bot's profile page, featuring 'Help' and 'Settings' buttons" style="width: 250px; padding: 10px 5px" /></a>
+
+

Formatting: bold, italic, fixed-width text and inline links

+

You can use bold, italic or fixed-width text, as well as inline links in your bots' messages. Telegram clients will render them accordingly.

+
+

Read more in the Bot API manual »

+
+

Privacy mode

+

Bots are frequently added to groups in order to augment communication between human users, e.g. by providing news, notifications from external services or additional search functionality. This is especially true for work-related groups. Now, when you share a group with a bot, you tend to ask yourself "How can I be sure that the little rascal isn't selling my chat history to my competitors?" The answer is — privacy mode.

+

A bot running in privacy mode will not receive all messages that people send to the group. Instead, it will only receive:

+
    +
  • Messages that start with a slash '/' (see Commands above)
  • +
  • Replies to the bot's own messages
  • +
  • Service messages (people added or removed from the group, etc.)
  • +
  • Messages from channels where it's a member
  • +
+

On one hand, this helps some of us sleep better at night (in our tinfoil nightcaps), on the other — it allows the bot developer to save a lot of resources, since they won't need to process tens of thousands irrelevant messages each day.

+

Privacy mode is enabled by default for all bots, except bots that were added to the group as admins (bot admins always receive all messages). It can be disabled, so that the bot receives all messages like an ordinary user (the bot will need to be re-added to the group for this change to take effect). We only recommend doing this in cases where it is absolutely necessary for your bot to work — users can always see a bot's current privacy setting in the group members list. In most cases, using the force reply option for the bot's messages should be more than enough.

+

So what messages exactly will my bot get? »

+

Deep linking

+

Telegram bots have a deep linking mechanism, that allows for passing additional parameters to the bot on startup. It could be a command that launches the bot — or an authentication token to connect the user's Telegram account to their account on some external service.

+

Each bot has a link that opens a conversation with it in Telegram — https://t.me/<bot username>. You can add the parameters start or startgroup to this link, with values up to 64 characters long. For example:

+
https://t.me/triviabot?startgroup=test
+

A-Z, a-z, 0-9, _ and - are allowed. We recommend using base64url to encode parameters with binary and other types of content.

+

Following a link with the start parameter will open a one-on-one conversation with the bot, showing a START button in the place of the input field. If the startgroup parameter is used, the user is prompted to select a group to add the bot to. As soon as a user confirms the action (presses the START button in their app or selects a group to add the bot to), your bot will receive a message from that user in this format:

+
/start PAYLOAD
+

PAYLOAD stands for the value of the start or startgroup parameter that was passed in the link.

+
Deep linking Example
+

Suppose the website example.com would like to send notifications to its users via a Telegram bot. Here's what they could do to enable notifications for a user with the ID 123.

+
    +
  1. Create a bot with a suitable username, e.g. @ExampleComBot
  2. +
  3. Set up a webhook for incoming messages
  4. +
  5. Generate a random string of a sufficient length, e.g. $memcache_key = "vCH1vGWJxfSeofSAs0K5PA"
  6. +
  7. Put the value 123 with the key $memcache_key into Memcache for 3600 seconds (one hour)
  8. +
  9. Show our user the button https://t.me/ExampleComBot?start=vCH1vGWJxfSeofSAs0K5PA
  10. +
  11. Configure the webhook processor to query Memcached with the parameter that is passed in incoming messages beginning with /start. If the key exists, record the chat_id passed to the webhook as telegram_chat_id for the user 123. Remove the key from Memcache.
  12. +
  13. Now when we want to send a notification to the user 123, check if they have the field telegram_chat_id. If yes, use the sendMessage method in the Bot API to send them a message in Telegram.
  14. +
+

Location and Number

+

Some bots need extra data from the user to work properly. For example, knowing the user's location helps provide more relevant geo-specific results. The user's phone number can be very useful for integrations with other services, like banks, etc.

+

Bots can ask a user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

+
+
+
+

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

+
+

Manual: Number and location buttons »

+
+
+

6. BotFather

+
+

Jump to top to learn everything about Telegram bots »

+
+

BotFather is the one bot to rule them all. It will help you create new bots and change settings for existing ones.

+

Creating a new bot

+

Use the /newbot command to create a new bot. The BotFather will ask you for a name and username, then generate an authentication token for your new bot.

+

The name of your bot is displayed in contact details and elsewhere.

+

The Username is a short name, to be used in mentions and t.me links. Usernames are 5-32 characters long and are case insensitive, but may only include Latin characters, numbers, and underscores. Your bot's username must end in 'bot', e.g. 'tetris_bot' or 'TetrisBot'.

+

The token is a string along the lines of 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw that is required to authorize the bot and send requests to the Bot API. Keep your token secure and store it safely, it can be used by anyone to control your bot.

+

Generating an authentication token

+

If your existing token is compromised or you lost it for some reason, use the /token command to generate a new one.

+

Botfather commands

+

The remaining commands are pretty self-explanatory:

+
    +
  • /mybots — returns a list of your bots with handy controls to edit their settings
  • +
  • /mygames — does the same for your games
  • +
+

Edit bots

+
    +
  • /setname – change your bot's name.
  • +
  • /setdescription — change the bot's description, a short text of up to 512 characters, describing your bot. Users will see this text at the beginning of the conversation with the bot, titled 'What can this bot do?'.
  • +
  • /setabouttext — change the bot's about info, an even shorter text of up to 120 characters. Users will see this text on the bot's profile page. When they share your bot with someone, this text is sent together with the link.
  • +
  • /setuserpic — change the bot's profile pictures. It's always nice to put a face to a name.
  • +
  • /setcommands — change the list of commands supported by your bot. Users will see these commands as suggestions when they type / in the chat with your bot. Each command has a name (must start with a slash ‘/’, alphanumeric plus underscores, no more than 32 characters, case-insensitive), parameters, and a text description. Users will see the list of commands whenever they type '/' in a conversation with your bot.
  • +
  • /deletebot — delete your bot and free its username.
  • +
+

Edit settings

+
    +
  • /setinline — toggle inline mode for your bot.
  • +
  • /setinlinegeo - request location data to provide location-based inline results.
  • +
  • /setjoingroups — toggle whether your bot can be added to groups or not. Any bot must be able to process private messages, but if your bot was not designed to work in groups, you can disable this.
  • +
  • /setprivacy — set which messages your bot will receive when added to a group. With privacy mode disabled, the bot will receive all messages. We recommend leaving privacy mode enabled. You will need to re-add the bot to existing groups for this change to take effect.
  • +
+

Manage games

+
    +
  • /newgame — create a new game.
  • +
  • /listgames — get a list of your games.
  • +
  • /editgame — edit a game.
  • +
  • /deletegame — delete an existing game.
  • +
+
+

Please note, that it may take a few minutes for changes to take effect.

+
+

Status alerts

+

Millions choose Telegram for its speed. To stay competitive in this environment, your bot also needs to be responsive. In order to help developers keep their bots in shape, Botfather will send status alerts if it sees something is wrong.

+

We will be checking the number of replies and the request/response conversion rate for popular bots (~300 requests per minute: but don't write this down as the value may change in the future). If we get abnormally low readings, you will receive a notification from Botfather.

+
Responding to alerts
+

By default, you will only get one alert per bot per hour. Each alert has the following buttons:

+
    +
  • Fixed. Use this if you found an issue with your bot and fixed it. If you press the fix button, we will resume sending alerts in the regular way so that you can see if your fix worked within 5-10 minutes instead of having to wait for an hour.
  • +
  • Support. Use this to open a chat with @BotSupport if you don't see any issues with your bot or if you think the problem is on our side.
  • +
  • Mute for 8h/1w. Use this if you can't fix your bot at the moment. This will disable all alerts for the bot in question for the specified period of time. We do not recommend using this option since your users may migrate to a more stable bot. You can unmute alerts in your bot's settings via Botfather.
  • +
+
Monitored issues
+

We will currently notify you about the following issues:

+

1.

+
Too few **private messages** are sent compared to previous weeks: **{value}**
+

Your bot is sending much fewer messages than it did in the previous weeks. This is useful for newsletter-style bots that send out messages without prompts from the users. The larger the value, the more significant the difference.

+

2.

+
Too few replies to incoming **private messages**. Conversion rate: **{value}**
+

Your bot is not replying to all messages that are being sent to it (the request/response conversion rate for your bot was too low for at least two of the last three 5-minute periods). To provide a good user experience, please respond to all messages that are sent to your bot. Respond to message updates by calling send... methods (e.g. sendMessage).

+

3.

+
Too few answers to **inline queries**. Conversion rate: **{value}**
+

Your bot is not replying to all inline queries that are being sent to it, calculated in the same way as above. Respond to inline_query updates by calling answerInlineQuery.

+

4.

+
Too few answers to **callback queries**. Conversion rate: **{value}**
+Too few answers to **callback game queries**. Conversion rate: **{value}**
+

Your bot is not replying to all callback queries that are being sent to it (with or without games), calculated in the same way as above. Respond to callback_query updates by calling answerCallbackQuery.

+
+

Please note that the status alerts feature is still being tested and will be improved in the future.

+
+
+

That's it for the introduction. You are now definitely ready to proceed to the BOT API MANUAL.

+

If you've got any questions, please check out our Bot FAQ »

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/bots/2-0-intro.html b/data/corefork.telegram.org/bots/2-0-intro.html new file mode 100644 index 0000000000..626344e3a0 --- /dev/null +++ b/data/corefork.telegram.org/bots/2-0-intro.html @@ -0,0 +1,230 @@ + + + + + Introducing Bot API 2.0 + + + + + + + + + + + + + +
+ +
+
+
+
+

Introducing Bot API 2.0

+ +
+ +
+

Howdy! This text assumes that you‘re familiar with Telegram’s bot platform.
If this is not the case, kindly check out our Introduction to Bots.

+
+

Today we‘re introducing the biggest change to Telegram’s Bot Platform since June 2015. These new tools will help you create fluid and intuitive interfaces for your bots. And bots are becoming a lot more capable. They can now send any type of content supported on Telegram, provide location-based services and integrate with other services deeply based on users' phone numbers.

+

If you'd like a more concise changelog, you can find one in the Bot API Manual.

+

New Inline Keyboards

+

To begin with, we're adding a new type of keyboard that is integrated directly into the message it belongs to. Inline keyboards are available for messages sent both in chat mode and inline mode.

+
+ + + +

+ + + +
+ +

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

+
+

Manual: Inline keyboards »

+
+

Callback buttons

+

When a user presses a callback button, no messages are sent to the chat. Instead, your bot simply receives the relevant query. Upon receiving the query, your bot can display some result in a notification at the top of the chat screen or in an alert.

+
+

+
+ +

Sample bot
@music – This sample music bot uses inline callback buttons to flip pages and reload random results.

+

Read on to updating messages to find out how callback buttons can get even cooler.

+

URL buttons

+

Buttons of this type have a small arrow icon to help the user understand that tapping on a URL button will open an external link. Naturally, we'll show them a confirmation alert before opening the link in the browser.

+
+
+
+ +

Switch to Inline buttons

+

Pressing a switch to inline button prompts the user to select a chat, opens it and inserts the bot's username into the input field. You can also pass a query that will be inserted along with the username – this way your users will immediately get some inline results they can share.

+
+

+
+ +

Sample bot
@sticker – This sticker search bot offers a ‘switch to inline’ button to teach users how to use it in inline mode.

+

Updating Messages

+

Since inline keyboards don‘t send additional messages to the chat, it made sense to give bots a way of manipulating their existing messages, so that they don’t have to send a new message each time they need to update something. This helps reduce clutter and build more fluid interfaces.

+
+
+ +
+
+ +

Sample bot
@music – Watch how the music bot updates its messages with search results when you press the navigation buttons.

+
+

Manual: Updating messages »

+
+

Locations and Numbers

+

Some bots need extra data from the user to work properly. For example, knowing the user‘s location helps provide more relevant geo-specific results. The user’s phone number can be very useful for integrations with other services, like banks, etc.

+

We've added an easy way for bots to ask the user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

+
+

+
+ +

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

+
+

Manual: Number and location buttons »

+
+

Inline bots can also request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

+

Sample bot
@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

+

Inline Bots 2.0

+

Speaking of inline bots, they are also getting a major upgrade today.

+

New types of content

+

Inline bots now support all types of content available in Telegram (19 in all), they are now capable of sending stickers, videos, music, locations, documents and more.

+
+

+
+ +

Sample bots
@sticker – This sticker bot will accept one or more emoji and search for relevant stickers.
@music – The music bot allows users to send mp3 tracks from a database of public domain classical music.

+
+

Manual: Types of inline content »

+
+

Switching between inline mode and private chat

+

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

+
+

+
+ +

You can now display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

+

Sample bots
@youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.

+
+

Manual: Switch to PM

+
+

Better inline UI

+

Since sending content via inline bots works differently from sending ordinary messages, we‘ve changed the interface a little. There’s hardly a more effective way of explaining that there‘s no need to hit ’Send':

+
+

+
+ +

Tapping on the cross icon once will clear the query, tapping twice will give the ‘Send’ button back to the user.

+

Group Admins

+

As a dessert, we‘re beginning to roll out tools that will allow you to create bot solutions for group admins. As the first step, we’ve added methods to remove members from groups and supergroups.

+
+

Manual: Group management »

+
+

And that's about it for now. Stay tuned for more updates and subscribe to our official @Botnews channel on Telegram.

+
+

Read the full changelog for this update »

+
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/bots/api-changelog.html b/data/corefork.telegram.org/bots/api-changelog.html new file mode 100644 index 0000000000..1a3bf096bd --- /dev/null +++ b/data/corefork.telegram.org/bots/api-changelog.html @@ -0,0 +1,670 @@ + + + + + Bot API changelog + + + + + + + + + + + + + +
+ +
+
+
+
+

Bot API changelog

+ +
+ +
+

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots »

+
+

You will find all changes to our Bot API on this page.

+

Recent changes

+
+

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

+
+

January 31, 2022

+

Bot API 5.7

+ +

December 30, 2021

+

Bot API 5.6

+ +

December 7, 2021

+

Bot API 5.5

+
    +
  • Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
  • +
  • Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
  • +
  • Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
  • +
  • Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
  • +
  • Added the field has_protected_content to the classes Chat and Message.
  • +
  • Added the field is_automatic_forward to the class Message.
  • +
+

Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.

+

Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.

+

Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.

+

November 5, 2021

+

Bot API 5.4

+ +
+
+

⚠️ WARNING! ⚠️
User identifiers will become bigger than 2^31 - 1 before the end of this year and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

June 25, 2021

+

Bot API 5.3

+

Personalized Commands

+
    +
  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • +
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • +
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • +
  • Added the parameters scope and language_code to the method getMyCommands.
  • +
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • +
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
  • +
+

Custom Placeholders

+ +

And More

+
    +
  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • +
  • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
  • +
  • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
  • +
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
  • +
+
+
+

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

April 26, 2021

+

Bot API 5.2

+
    +
  • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
  • +
  • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
  • +
  • Allowed sending invoices to group, supergroup and channel chats.
  • +
  • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
  • +
  • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
  • +
  • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
  • +
  • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
  • +
  • Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
  • +
+
+
+

⚠️ WARNING! ⚠️
After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

+
+
+
+

⚠️ WARNING! ⚠️
Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.

+
+
+
+

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

March 9, 2021

+

Bot API 5.1

+

Added two new update types

+
    +
  • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
  • +
+

Improved Invite Links

+
    +
  • Added the class ChatInviteLink, representing an invite link to a chat.
  • +
  • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
  • +
  • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
  • +
  • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
  • +
+

Voice Chat Info

+ +

And More

+
    +
  • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
  • +
  • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
  • +
  • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
  • +
  • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
  • +
+
+
+

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

November 4, 2020

+

Introducing Bot API 5.0

+

Run Your Own Bot API Server

+
    +
  • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance.
  • +
  • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
  • +
  • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
  • +
+

Transfer Bot Ownership

+
    +
  • You can now use @BotFather to transfer your existing bots to another Telegram account.
  • +
+

Webhooks

+
    +
  • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
  • +
  • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
  • +
  • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
  • +
+

Working with Groups

+
    +
  • The getChat request now returns the user's bio for private chats if available.
  • +
  • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
  • +
  • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
  • +
  • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
  • +
+

Working with Files

+
    +
  • Added the field file_name to the classes Audio and Video, containing the name of the original file.
  • +
  • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
  • +
+

Multiple Pinned Messages

+
    +
  • Added the ability to pin messages in private chats.
  • +
  • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
  • +
  • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
  • +
+

File Albums

+
    +
  • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
  • +
+

Live Locations

+ +

Anonymous Admins

+
    +
  • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
  • +
  • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
  • +
  • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
  • +
  • Added the custom title of an anonymous message sender to the class Message as author_signature.
  • +
+

And More

+ +

And Last but not Least

+
    +
  • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
  • +
+

June 4, 2020

+

Bot API 4.9

+
    +
  • Added the new field via_bot to the Message object. You can now know which bot was used to send a message.
  • +
  • Supported video thumbnails for inline GIF and MPEG4 animations.
  • +
  • Supported the new basketball animation for the random dice. Choose between different animations (dice, darts, basketball) by specifying the emoji parameter in the method sendDice.
  • +
+

April 24, 2020

+

Bot API 4.8

+
    +
  • Supported explanations for Quizzes 2.0. Add explanations by specifying the parameters explanation and explanation_parse_mode in the method sendPoll.
  • +
  • Added the fields explanation and explanation_entities to the Poll object.
  • +
  • Supported timed polls that automatically close at a certain date and time. Set up by specifying the parameter open_period or close_date in the method sendPoll.
  • +
  • Added the fields open_period and close_date to the Poll object.
  • +
  • Supported the new darts animation for the dice mini-game. Choose between the default dice animation and darts animation by specifying the parameter emoji in the method sendDice.
  • +
  • Added the field emoji to the Dice object.
  • +
+

March 30, 2020

+

Bot API 4.7

+
    +
  • Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the “proper” singular of die. But it's awkward, and we decided to help it change. One dice at a time!)
  • +
  • Added the field dice to the Message object.
  • +
  • Added the method getMyCommands for getting the current list of the bot's commands.
  • +
  • Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather.
  • +
  • Added the ability to create animated sticker sets by specifying the parameter tgs_sticker instead of png_sticker in the method createNewStickerSet.
  • +
  • Added the ability to add animated stickers to sets created by the bot by specifying the parameter tgs_sticker instead of png_sticker in the method addStickerToSet.
  • +
  • Added the field thumb to the StickerSet object.
  • +
  • Added the ability to change thumbnails of sticker sets created by the bot using the method setStickerSetThumb.
  • +
+

January 23, 2020

+

Bot API 4.6

+
    +
  • Supported Polls 2.0.
  • +
  • Added the ability to send non-anonymous, multiple answer, and quiz-style polls: added the parameters is_anonymous, type, allows_multiple_answers, correct_option_id, is_closed options to the method sendPoll.
  • +
  • Added the object KeyboardButtonPollType and the field request_poll to the object KeyboardButton.
  • +
  • Added updates about changes of user answers in non-anonymous polls, represented by the object PollAnswer and the field poll_answer in the Update object.
  • +
  • Added the fields total_voter_count, is_anonymous, type, allows_multiple_answers, correct_option_id to the Poll object.
  • +
  • Bots can now send polls to private chats.
  • +
  • Added more information about the bot in response to the getMe request: added the fields can_join_groups, can_read_all_group_messages and supports_inline_queries to the User object.
  • +
  • Added the optional field language to the MessageEntity object.
  • +
+

December 31, 2019

+

Bot API 4.5

+
    +
  • Added support for two new MessageEntity types, underline and strikethrough.
  • +
  • Added support for nested MessageEntity objects. Entities can now contain other entities. If two entities have common characters then one of them is fully contained inside the other.
  • +
  • Added support for nested entities and the new tags <u>/<ins> (for underlined text) and <s>/<strike>/<del> (for strikethrough text) in parse mode HTML.
  • +
  • Added a new parse mode, MarkdownV2, which supports nested entities and two new entities __ (for underlined text) and ~ (for strikethrough text). Parse mode Markdown remains unchanged for backward compatibility.
  • +
  • Added the field file_unique_id to the objects Animation, Audio, Document, PassportFile, PhotoSize, Sticker, Video, VideoNote, Voice, File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto. The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
  • +
  • Added the field custom_title to the ChatMember object.
  • +
  • Added the new method setChatAdministratorCustomTitle to manage the custom titles of administrators promoted by the bot.
  • +
  • Added the field slow_mode_delay to the Chat object.
  • +
+

July 29, 2019

+

Bot API 4.4

+
    +
  • Added support for animated stickers. New field is_animated in Sticker and StickerSet objects, animated stickers can now be used in sendSticker and InlineQueryResultCachedSticker.
  • +
  • Added support for default permissions in groups. New object ChatPermissions, containing actions which a member can take in a chat. New field permissions in the Chat object; new method setChatPermissions.
  • +
  • The field all_members_are_administrators has been removed from the documentation for the Chat object. The field is still returned in the object for backward compatibility, but new bots should use the permissions field instead.
  • +
  • Added support for more permissions for group and supergroup members: added the new field can_send_polls to ChatMember object, added can_change_info, can_invite_users, can_pin_messages in ChatMember object for restricted users (previously available only for administrators).
  • +
  • The method restrictChatMember now takes the new user permissions in a single argument of the type ChatPermissions. The old way of passing parameters will keep working for a while for backward compatibility.
  • +
  • Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method.
  • +
  • Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
  • +
  • File identifiers from the ChatPhoto object are now invalidated and can no longer be used whenever the photo is changed.
  • +
  • All webhook requests from the Bot API are now coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • +
  • As of the next Bot API update (version 4.5), nested MessageEntity objects will be allowed in message texts and captions. Please make sure that your code can correctly handle such entities.
  • +
+

May 31, 2019

+

Bot API 4.3

+
    +
  • Added support for Seamless Telegram Login on external websites.
  • +
  • Added the new object LoginUrl and the new field login_url to the InlineKeyboardButton object which allows to automatically authorize users before they go to a URL specified by the bot. Users will be asked to confirm authorization in their Telegram app (needs version 5.7 or higher) when they press the button:
  • +
+
+ TITLE +
+ +

Also in this update:

+
    +
  • Added the field reply_markup to the Message object, containing the inline keyboard attached to the message.
  • +
  • If a message with an inline keyboard is forwarded, the forwarded message will now have an inline keyboard if the keyboard contained only url and login_url buttons or if the message was sent via a bot and the keyboard contained only url, login_url, switch_inline_query or switch_inline_query_current_chat buttons. In the latter case, switch_inline_query_current_chat buttons are replaced with switch_inline_query buttons.
  • +
  • Bots now receive the edited_message Update even if only Message.reply_markup has changed.
  • +
  • Bots that have the can_edit_messages right in a channel can now use the method editMessageReplyMarkup for messages written by other administrators forever without the 48 hours limit.
  • +
  • Don't forget that starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • +
+

April 14, 2019

+

Bot API 4.2

+
    +
  • Added support for native polls: added the object Poll, the methods sendPoll and stopPoll and the field poll in the Message and Update objects.
  • +
  • The method deleteMessage can now be used to delete messages sent by a user to the bot in private chats within 48 hours.
  • +
  • Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage, and receive the pinned group message in Chat object.
  • +
  • Added the field is_member to the ChatMember object, which can be used to find whether a restricted user is a member of the chat.
  • +
  • Added the field forward_sender_name to the Message object, containing name of the sender who has opted to hide their account.
  • +
  • Starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • +
  • Document thumbnails now should be inscribed in a 320x320 square instead of 90x90.
  • +
+

August 27, 2018

+

Bot API 4.1

+ +

July 26, 2018

+

Bot API 4.0.

+
    +
  • Added support for Telegram Passport. See the official announcement on the blog and the manual for details.
  • +
  • Added support for editing the media content of messages: added the method editMessageMedia and new types InputMediaAnimation, InputMediaAudio, and InputMediaDocument.
  • +
  • Added the field thumb to the Audio object to contain the thumbnail of the album cover to which the music file belongs.
  • +
  • Added support for attaching custom thumbnails to uploaded files. For animations, audios, videos and video notes, which are less than 10 MB in size, thumbnails are generated automatically.
  • +
  • tg:// URLs now can be used in inline keyboard url buttons and text_link message entities.
  • +
  • Added the method sendAnimation, which can be used instead of sendDocument to send animations, specifying their duration, width and height.
  • +
  • Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set.
  • +
  • Added two new MessageEntity types: cashtag and phone_number.
  • +
  • Added support for Foursquare venues: added the new field foursquare_type to the objects Venue, InlineQueryResultVenue and InputVenueMessageContent, and the parameter foursquare_type to the sendVenue method.
  • +
  • You can now create inline mentions of users, who have pressed your bot's callback buttons.
  • +
  • You can now use the Retry-After response header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook.
  • +
  • If a webhook returns the HTTP error 410 Gone for all requests for more than 23 hours successively, it can be automatically removed.
  • +
  • Added vCard support when sharing contacts: added the field vcard to the objects Contact, InlineQueryResultContact, InputContactMessageContent and the method sendContact.
  • +
+

February 13, 2018

+

Bot API 3.6.

+
    +
  • Supported text formatting in media captions. Specify the desired parse_mode (Markdown or HTML) when you provide a caption.
  • +
  • In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot).
  • +
  • Added the new field connected_website to Message. The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
  • +
  • Added the new parameter supports_streaming to the sendVideo method and a field with the same name to the InputMediaVideo object.
  • +
+

November 17, 2017

+

Bot API 3.5.

+ +

October 11, 2017

+

Bot API 3.4.

+ +

August 23, 2017

+

Bot API 3.3.

+
    +
  • Bots can now mention users via inline mentions, without using usernames.
  • +
  • getChat now also returns pinned messages in supergroups, if present. Added the new field pinned_message to the Chat object.
  • +
  • Added the new fields author_signature and forward_signature to the Message object.
  • +
  • Added the new field is_bot to the User object.
  • +
+

July 21, 2017

+

Bot API 3.2. Teach your bot to handle stickers and sticker sets.

+ +

June 30, 2017

+

Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:

+ +

May 18, 2017

+

Introducing Bot API 3.0.

+

NEW Payment Platform

+

See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.

+ +

NEW Video Messages

+
    +
  • As of Telegram v.4.0, users can send short rounded video messages, using an interface similar to that of voice notes.
  • +
  • Added the sendVideoNote method, the new field video_note to Message, the fields record_video_note or upload_video_note to sendChatAction.
  • +
+

NEW Multilingual Bots

+
    +
  • The User object now may have a language_code field that contains the IETF language tag of the user's language.
  • +
  • Thanks to this, your bot can now offer localized responses to users that speak different languages.
  • +
+

More power to admin bots

+
    +
  • unbanChatMemeber now also works in channels!
  • +
  • New method deleteMessage that allows the bot to delete its own messages, as well as messages posted by other in groups and channels where the bot is an administrator.
  • +
+

Minor Changes

+
    +
  • Replaced the field new_chat_member in Message with new_chat_members (the old field will still be available for a while for compatibility purposes).
  • +
  • Inline keyboards with switch_inline_query and switch_inline_query_current_chat can no longer be sent to channels because they are useless there.
  • +
  • New fields gif_duration in InlineQueryResultGif and mpeg4_duration in InlineQueryResultMpeg4Gif.
  • +
+

December 4, 2016

+

Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.

+
    +
  • Use the new field max_connections in setWebhook to optimize your bot's server load
  • +
  • Use allowed_updates in setWebhook and getUpdates to selectively subscribe to updates of a certain type. Among other things, this allows you to stop getting updates about new posts in channels where your bot is an admin.
  • +
  • deleteWebhook moved out of setWebhook to get a whole separate method for itself.
  • +
+

November 21, 2016

+

Bot API 2.3

+
    +
  • Modified bot privacy mode for the sake of consistency.
  • +
  • Your bot can now get updates about posts in channels. Added new fields channel_post and edited_channel_post to Update.

    +
  • +
  • You can now update high scores to a lower value by using the new force parameter in setGameScore. Handy for punishing cheaters or fixing errors in your game's High Score table.

    +
  • +
  • Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
  • +
  • The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
  • +
  • Added the new field forward_from_message_id to Message.
  • +
  • Added the new parameter cache_time to answerCallbackQuery. Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
  • +
  • Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
  • +
+

October 3, 2016

+

Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.

+ +

Other changes

+ +
    +
  • New field all_members_are_administrators in the Chat object.
  • +
  • Certain server responses may now contain the new parameters field with expanded info on errors that occurred while processing your requests.
  • +
+

May 25, 2016

+ +

May 22, 2016

+ +

May 12, 2016

+ +

May 6, 2016

+
    +
  • Added the field emoji to the Sticker object. Your bot can now know the emoji a sticker corresponds to.
  • +
  • Added the field forward_from_chat to the Message object for messages forwarded from channels.
  • +
+

April 9, 2016

+

Introducing Bot API 2.0. Check out this page for a review of this major update.

+ +

Inline bots

+
    +
  • Added support for all content types available on Telegram. 19 types of InlineQueryResult objects are now supported.
  • +
  • Inline bots can now substitute all kinds of content with text. Added 4 types of InputMessageContent objects.
  • +
  • Your inline bot can also ask users for permission to use their location. Added the new Botfather command /setinlinegeo, added field location to the InlineQuery object, added fields location and inline_message_id to the ChosenInlineResult object.
  • +
  • Added an easy way to switch between inline mode and a private chat with the bot – useful for settings, establishing external connections and teaching users how to use your bot in inline mode. Added parameters switch_pm_text and switch_pm_parameter to the method answerInlineQuery.
  • +
+

Miscellaneous

+ +

February 20, 2016

+
    +
  • Added the disable_notification parameter to all methods that send messages or any kind.
  • +
  • Removed backward compatibility from the method sendAudio. Voice messages now must be sent using the method sendVoice. There is no more need to specify a non-empty title or performer while sending the audio by file_id.
  • +
+

January 20, 2016

+
    +
  • By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
  • +
+

January 14, 2016

+
    +
  • You can now collect feedback on which results provided by your inline bot get chosen by the users. Added the setinlinefeedback command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object.
  • +
+

January 4, 2016

+ +

November, 2015

+
    +
  • Added support for supergroups. The Type field in the Chat object can now contain 'supergroup'.
  • +
  • New optional fields added to the Message object: supergroup_chat_created, migrate_to_chat_id, migrate_from_chat_id and channel_chat_created.
  • +
+

October 8, 2015

+
    +
  • Added initial channel support for bots (no Telegram clients support this at the moment, please wait for updates):
  • +
  • The Chat field in the Message is now of the new type Chat.
  • +
  • You can now pass a channel username (in the format @channelusername) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).
  • +
+

September 18, 2015

+
    +
  • Bots can now download files and media sent by users.
  • +
  • Added getFile and File.
  • +
+

September 7, 2015

+
    +
  • You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
  • +
  • Added very basic markdown support. New field parse_mode added to sendMessage. For the moment messages with markdown will be displayed correctly only in Telegram for Android. Other official apps will catch up soon.
  • +
+

August 29, 2015

+
    +
  • Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.
  • +
  • You can now make new requests when responding to webhook updates.
  • +
+

August 15, 2015

+
    +
  • Added new type Voice and new method sendVoice for sending voice messages.
  • +
  • Earlier Audio and sendAudio should now be used for sending music files. Telegram clients will show such files in the in-app music player. If you were using sendAudio for your bot to send voice messages, please use sendVoice instead.
  • +
  • Added optional fields performer, title to the Audio object and sendAudio method.
  • +
  • Added optional field voice to the Message object.
  • +
+

July 2015

+
    +
  • The thumb field is now optional for Video, Sticker and Document objects
  • +
  • The API now supports both video and photo captions. The caption field has been removed from the Video object and added to the Message object instead.
  • +
  • caption and duration optional fields have been added to the sendVideo method.
  • +
  • Fixed typo: user_id in the Contact object is now correctly labeled as Integer, not String
  • +
+

June 24, 2015

+

The bot platform was officially launched.

+
+

Back to the Bot API Manual »

+
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/bots/api.html b/data/corefork.telegram.org/bots/api.html new file mode 100644 index 0000000000..a01ae0c040 --- /dev/null +++ b/data/corefork.telegram.org/bots/api.html @@ -0,0 +1,9288 @@ + + + + + Telegram Bot API + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram Bot API

+ +
+ +
+

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram. +To learn how to create and set up a bot, please consult our Introduction to Bots and Bot FAQ.

+
+

Recent changes

+
+

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

+
+

June 25, 2021

+

Bot API 5.3

+

Personalized Commands

+
    +
  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • +
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • +
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • +
  • Added the parameters scope and language_code to the method getMyCommands.
  • +
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • +
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
  • +
+

Custom Placeholders

+ +

And More

+
    +
  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • +
  • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
  • +
  • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
  • +
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
  • +
+
+
+

⚠️ WARNING! ⚠️ +After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

April 26, 2021

+

Bot API 5.2

+
    +
  • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
  • +
  • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
  • +
  • Allowed sending invoices to group, supergroup and channel chats.
  • +
  • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
  • +
  • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
  • +
  • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
  • +
  • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
  • +
  • Fixed an error in sendChatAction documentation to correctly mention "record_voice" and "upload_voice" instead of "record_audio" and "upload_audio" for related to voice note actions. Old action names will still work for backward compatibility.
  • +
+
+
+

⚠️ WARNING! ⚠️ +After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

+
+
+
+

⚠️ WARNING! ⚠️ +Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the "chat_member" update as a replacement.

+
+
+
+

⚠️ WARNING! ⚠️ +After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

March 9, 2021

+

Bot API 5.1

+

Added two new update types

+
    +
  • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
  • +
+

Improved Invite Links

+
    +
  • Added the class ChatInviteLink, representing an invite link to a chat.
  • +
  • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
  • +
  • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
  • +
  • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
  • +
+

Voice Chat Info

+ +

And More

+
    +
  • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
  • +
  • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
  • +
  • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
  • +
  • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
  • +
+
+
+

⚠️ WARNING! ⚠️ +After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

+
+
+

November 4, 2020

+

Introducing Bot API 5.0

+

Run Your Own Bot API Server

+
    +
  • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance (check this out to see if this will benefit your project).
  • +
  • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
  • +
  • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
  • +
+

Transfer Bot Ownership

+
    +
  • You can now use @BotFather to transfer your existing bots to another Telegram account.
  • +
+

Webhooks

+
    +
  • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
  • +
  • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
  • +
  • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
  • +
+

Working with Groups

+
    +
  • The getChat request now returns the user's bio for private chats if available.
  • +
  • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
  • +
  • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
  • +
  • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
  • +
+

Working with Files

+
    +
  • Added the field file_name to the classes Audio and Video, containing the name of the original file.
  • +
  • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
  • +
+

Multiple Pinned Messages

+
    +
  • Added the ability to pin messages in private chats.
  • +
  • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
  • +
  • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
  • +
+

File Albums

+
    +
  • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
  • +
+

Live Locations

+ +

Anonymous Admins

+
    +
  • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
  • +
  • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
  • +
  • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
  • +
  • Added the custom title of an anonymous message sender to the class Message as author_signature.
  • +
+

And More

+ +

And Last but bot Least

+
    +
  • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
  • +
+

See earlier changes »

+

Authorizing your bot

+

Each bot is given a unique authentication token when it is created. The token looks something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11, but we'll use simply <token> in this document instead. You can learn about obtaining tokens and generating new ones in this document.

+

Making requests

+

All queries to the Telegram Bot API must be served over HTTPS and need to be presented in this form: https://api.telegram.org/bot<token>/METHOD_NAME. Like this for example:

+
https://api.telegram.org/bot123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11/getMe
+

We support GET and POST HTTP methods. We support four ways of passing parameters in Bot API requests:

+
    +
  • URL query string
  • +
  • application/x-www-form-urlencoded
  • +
  • application/json (except for uploading files)
  • +
  • multipart/form-data (use to upload files)
  • +
+

The response contains a JSON object, which always has a Boolean field 'ok' and may have an optional String field 'description' with a human-readable description of the result. If 'ok' equals true, the request was successful and the result of the query can be found in the 'result' field. In case of an unsuccessful request, 'ok' equals false and the error is explained in the 'description'. An Integer 'error_code' field is also returned, but its contents are subject to change in the future. Some errors may also have an optional field 'parameters' of the type ResponseParameters, which can help to automatically handle the error.

+
    +
  • All methods in the Bot API are case-insensitive.
  • +
  • All queries must be made using UTF-8.
  • +
+

Making requests when getting updates

+

If you're using webhooks, you can perform a request to the Bot API while sending an answer to the webhook. Use either application/json or application/x-www-form-urlencoded or multipart/form-data response content type for passing parameters. Specify the method to be invoked in the method parameter of the request. It's not possible to know that such a request was successful or get its result.

+
+

Please see our FAQ for examples.

+
+

Using a Local Bot API Server

+

The Bot API server source code is available at telegram-bot-api. You can run it locally and send the requests to your own server instead of https://api.telegram.org. If you switch to a local Bot API server, your bot will be able to:

+
    +
  • Download files without a size limit.
  • +
  • Upload files up to 2000 MB.
  • +
  • Upload files using their local path and the file URI scheme.
  • +
  • Use an HTTP URL for the webhook.
  • +
  • Use any local IP address for the webhook.
  • +
  • Use any port for the webhook.
  • +
  • Set max_webhook_connections up to 100000.
  • +
  • Receive the absolute local path as a value of the file_path field without the need to download the file after a getFile request.
  • +
+

Do I need a Local Bot API Server

+

The majority of bots will be OK with the default configuration, running on our servers. But if you feel that you need one of these features, you're welcome to switch to your own at any time.

+

Getting updates

+

There are two mutually exclusive ways of receiving updates for your bot — the getUpdates method on one hand and Webhooks on the other. Incoming updates are stored on the server until the bot receives them either way, but they will not be kept longer than 24 hours.

+

Regardless of which option you choose, you will receive JSON-serialized Update objects as a result.

+

Update

+

This object represents an incoming update. +At most one of the optional parameters can be present in any given update.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
update_idIntegerThe update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using Webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.
messageMessageOptional. New incoming message of any kind — text, photo, sticker, etc.
edited_messageMessageOptional. New version of a message that is known to the bot and was edited
channel_postMessageOptional. New incoming channel post of any kind — text, photo, sticker, etc.
edited_channel_postMessageOptional. New version of a channel post that is known to the bot and was edited
inline_queryInlineQueryOptional. New incoming inline query
chosen_inline_resultChosenInlineResultOptional. The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
callback_queryCallbackQueryOptional. New incoming callback query
shipping_queryShippingQueryOptional. New incoming shipping query. Only for invoices with flexible price
pre_checkout_queryPreCheckoutQueryOptional. New incoming pre-checkout query. Contains full information about checkout
pollPollOptional. New poll state. Bots receive only updates about stopped polls and polls, which are sent by the bot
poll_answerPollAnswerOptional. A user changed their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.
my_chat_memberChatMemberUpdatedOptional. The bot's chat member status was updated in a chat. For private chats, this update is received only when the bot is blocked or unblocked by the user.
chat_memberChatMemberUpdatedOptional. A chat member's status was updated in a chat. The bot must be an administrator in the chat and must explicitly specify "chat_member" in the list of allowed_updates to receive these updates.
+

getUpdates

+

Use this method to receive incoming updates using long polling (wiki). An Array of Update objects is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
offsetIntegerOptionalIdentifier of the first update to be returned. Must be greater by one than the highest among the identifiers of previously received updates. By default, updates starting with the earliest unconfirmed update are returned. An update is considered confirmed as soon as getUpdates is called with an offset higher than its update_id. The negative offset can be specified to retrieve updates starting from -offset update from the end of the updates queue. All previous updates will forgotten.
limitIntegerOptionalLimits the number of updates to be retrieved. Values between 1-100 are accepted. Defaults to 100.
timeoutIntegerOptionalTimeout in seconds for long polling. Defaults to 0, i.e. usual short polling. Should be positive, short polling should be used for testing purposes only.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify ["message", "edited_channel_post", "callback_query"] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.

Please note that this parameter doesn't affect updates created before the call to the getUpdates, so unwanted updates may be received for a short period of time.
+
+

Notes +1. This method will not work if an outgoing webhook is set up. +2. In order to avoid getting duplicate updates, recalculate offset after each server response.

+
+

setWebhook

+

Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized Update. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns True on success.

+

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. https://www.example.com/<token>. Since nobody else knows your bot's token, you can be pretty sure it's us.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
urlStringYesHTTPS url to send updates to. Use an empty string to remove webhook integration
certificateInputFileOptionalUpload your public key certificate so that the root certificate in use can be checked. See our self-signed guide for details.
ip_addressStringOptionalThe fixed IP address which will be used to send webhook requests instead of the IP address resolved through DNS
max_connectionsIntegerOptionalMaximum allowed number of simultaneous HTTPS connections to the webhook for update delivery, 1-100. Defaults to 40. Use lower values to limit the load on your bot's server, and higher values to increase your bot's throughput.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify ["message", "edited_channel_post", "callback_query"] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.
Please note that this parameter doesn't affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time.
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
+
+

Notes +1. You will not be able to receive updates using getUpdates for as long as an outgoing webhook is set up. +2. To use a self-signed certificate, you need to upload your public key certificate using certificate parameter. Please upload as InputFile, sending a String will not work. +3. Ports currently supported for Webhooks: 443, 80, 88, 8443.

+
+
+

NEW! If you're having any trouble setting up webhooks, please check out this amazing guide to Webhooks.

+
+

deleteWebhook

+

Use this method to remove webhook integration if you decide to switch back to getUpdates. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
+

getWebhookInfo

+

Use this method to get current webhook status. Requires no parameters. On success, returns a WebhookInfo object. If the bot is using getUpdates, will return an object with the url field empty.

+

WebhookInfo

+

Contains information about the current status of a webhook.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
urlStringWebhook URL, may be empty if webhook is not set up
has_custom_certificateBooleanTrue, if a custom certificate was provided for webhook certificate checks
pending_update_countIntegerNumber of updates awaiting delivery
ip_addressStringOptional. Currently used webhook IP address
last_error_dateIntegerOptional. Unix time for the most recent error that happened when trying to deliver an update via webhook
last_error_messageStringOptional. Error message in human-readable format for the most recent error that happened when trying to deliver an update via webhook
max_connectionsIntegerOptional. Maximum allowed number of simultaneous HTTPS connections to the webhook for update delivery
allowed_updatesArray of StringOptional. A list of update types the bot is subscribed to. Defaults to all update types except chat_member
+

Available types

+

All types used in the Bot API responses are represented as JSON-objects.

+

It is safe to use 32-bit signed integers for storing all Integer fields unless otherwise noted.

+
+

Optional fields may be not returned when irrelevant.

+
+

User

+

This object represents a Telegram user or bot.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idIntegerUnique identifier for this user or bot. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
is_botBooleanTrue, if this user is a bot
first_nameStringUser's or bot's first name
last_nameStringOptional. User's or bot's last name
usernameStringOptional. User's or bot's username
language_codeStringOptional. IETF language tag of the user's language
can_join_groupsBooleanOptional. True, if the bot can be invited to groups. Returned only in getMe.
can_read_all_group_messagesBooleanOptional. True, if privacy mode is disabled for the bot. Returned only in getMe.
supports_inline_queriesBooleanOptional. True, if the bot supports inline queries. Returned only in getMe.
+

Chat

+

This object represents a chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idIntegerUnique identifier for this chat. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
typeStringType of chat, can be either "private", "group", "supergroup" or "channel"
titleStringOptional. Title, for supergroups, channels and group chats
usernameStringOptional. Username, for private chats, supergroups and channels if available
first_nameStringOptional. First name of the other party in a private chat
last_nameStringOptional. Last name of the other party in a private chat
photoChatPhotoOptional. Chat photo. Returned only in getChat.
bioStringOptional. Bio of the other party in a private chat. Returned only in getChat.
descriptionStringOptional. Description, for groups, supergroups and channel chats. Returned only in getChat.
invite_linkStringOptional. Primary invite link, for groups, supergroups and channel chats. Returned only in getChat.
pinned_messageMessageOptional. The most recent pinned message (by sending date). Returned only in getChat.
permissionsChatPermissionsOptional. Default chat member permissions, for groups and supergroups. Returned only in getChat.
slow_mode_delayIntegerOptional. For supergroups, the minimum allowed delay between consecutive messages sent by each unpriviledged user. Returned only in getChat.
message_auto_delete_timeIntegerOptional. The time after which all messages sent to the chat will be automatically deleted; in seconds. Returned only in getChat.
sticker_set_nameStringOptional. For supergroups, name of group sticker set. Returned only in getChat.
can_set_sticker_setBooleanOptional. True, if the bot can change the group sticker set. Returned only in getChat.
linked_chat_idIntegerOptional. Unique identifier for the linked chat, i.e. the discussion group identifier for a channel and vice versa; for supergroups and channel chats. This identifier may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier. Returned only in getChat.
locationChatLocationOptional. For supergroups, the location to which the supergroup is connected. Returned only in getChat.
+

Message

+

This object represents a message.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
message_idIntegerUnique message identifier inside this chat
fromUserOptional. Sender, empty for messages sent to channels
sender_chatChatOptional. Sender of the message, sent on behalf of a chat. The channel itself for channel messages. The supergroup itself for messages from anonymous group administrators. The linked channel for messages automatically forwarded to the discussion group
dateIntegerDate the message was sent in Unix time
chatChatConversation the message belongs to
forward_fromUserOptional. For forwarded messages, sender of the original message
forward_from_chatChatOptional. For messages forwarded from channels or from anonymous administrators, information about the original sender chat
forward_from_message_idIntegerOptional. For messages forwarded from channels, identifier of the original message in the channel
forward_signatureStringOptional. For messages forwarded from channels, signature of the post author if present
forward_sender_nameStringOptional. Sender's name for messages forwarded from users who disallow adding a link to their account in forwarded messages
forward_dateIntegerOptional. For forwarded messages, date the original message was sent in Unix time
reply_to_messageMessageOptional. For replies, the original message. Note that the Message object in this field will not contain further reply_to_message fields even if it itself is a reply.
via_botUserOptional. Bot through which the message was sent
edit_dateIntegerOptional. Date the message was last edited in Unix time
media_group_idStringOptional. The unique identifier of a media message group this message belongs to
author_signatureStringOptional. Signature of the post author for messages in channels, or the custom title of an anonymous group administrator
textStringOptional. For text messages, the actual UTF-8 text of the message, 0-4096 characters
entitiesArray of MessageEntityOptional. For text messages, special entities like usernames, URLs, bot commands, etc. that appear in the text
animationAnimationOptional. Message is an animation, information about the animation. For backward compatibility, when this field is set, the document field will also be set
audioAudioOptional. Message is an audio file, information about the file
documentDocumentOptional. Message is a general file, information about the file
photoArray of PhotoSizeOptional. Message is a photo, available sizes of the photo
stickerStickerOptional. Message is a sticker, information about the sticker
videoVideoOptional. Message is a video, information about the video
video_noteVideoNoteOptional. Message is a video note, information about the video message
voiceVoiceOptional. Message is a voice message, information about the file
captionStringOptional. Caption for the animation, audio, document, photo, video or voice, 0-1024 characters
caption_entitiesArray of MessageEntityOptional. For messages with a caption, special entities like usernames, URLs, bot commands, etc. that appear in the caption
contactContactOptional. Message is a shared contact, information about the contact
diceDiceOptional. Message is a dice with random value
gameGameOptional. Message is a game, information about the game. More about games »
pollPollOptional. Message is a native poll, information about the poll
venueVenueOptional. Message is a venue, information about the venue. For backward compatibility, when this field is set, the location field will also be set
locationLocationOptional. Message is a shared location, information about the location
new_chat_membersArray of UserOptional. New members that were added to the group or supergroup and information about them (the bot itself may be one of these members)
left_chat_memberUserOptional. A member was removed from the group, information about them (this member may be the bot itself)
new_chat_titleStringOptional. A chat title was changed to this value
new_chat_photoArray of PhotoSizeOptional. A chat photo was change to this value
delete_chat_photoTrueOptional. Service message: the chat photo was deleted
group_chat_createdTrueOptional. Service message: the group has been created
supergroup_chat_createdTrueOptional. Service message: the supergroup has been created. This field can't be received in a message coming through updates, because bot can't be a member of a supergroup when it is created. It can only be found in reply_to_message if someone replies to a very first message in a directly created supergroup.
channel_chat_createdTrueOptional. Service message: the channel has been created. This field can't be received in a message coming through updates, because bot can't be a member of a channel when it is created. It can only be found in reply_to_message if someone replies to a very first message in a channel.
message_auto_delete_timer_changedMessageAutoDeleteTimerChangedOptional. Service message: auto-delete timer settings changed in the chat
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
migrate_from_chat_idIntegerOptional. The supergroup has been migrated from a group with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
pinned_messageMessageOptional. Specified message was pinned. Note that the Message object in this field will not contain further reply_to_message fields even if it is itself a reply.
invoiceInvoiceOptional. Message is an invoice for a payment, information about the invoice. More about payments »
successful_paymentSuccessfulPaymentOptional. Message is a service message about a successful payment, information about the payment. More about payments »
connected_websiteStringOptional. The domain name of the website on which the user has logged in. More about Telegram Login »
passport_dataPassportDataOptional. Telegram Passport data
proximity_alert_triggeredProximityAlertTriggeredOptional. Service message. A user in the chat triggered another user's proximity alert while sharing Live Location.
voice_chat_scheduledVoiceChatScheduledOptional. Service message: voice chat scheduled
voice_chat_startedVoiceChatStartedOptional. Service message: voice chat started
voice_chat_endedVoiceChatEndedOptional. Service message: voice chat ended
voice_chat_participants_invitedVoiceChatParticipantsInvitedOptional. Service message: new participants invited to a voice chat
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message. login_url buttons are represented as ordinary url buttons.
+

MessageId

+

This object represents a unique message identifier.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
message_idIntegerUnique message identifier
+

MessageEntity

+

This object represents one special entity in a text message. For example, hashtags, usernames, URLs, etc.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the entity. Can be "mention" (@username), "hashtag" (#hashtag), "cashtag" ($USD), "bot_command" (/start@jobs_bot), "url" (https://telegram.org), "email" (do-not-reply@telegram.org), "phone_number" (+1-212-555-0123), "bold" (bold text), "italic" (italic text), "underline" (underlined text), "strikethrough" (strikethrough text), "code" (monowidth string), "pre" (monowidth block), "text_link" (for clickable text URLs), "text_mention" (for users without usernames)
offsetIntegerOffset in UTF-16 code units to the start of the entity
lengthIntegerLength of the entity in UTF-16 code units
urlStringOptional. For "text_link" only, url that will be opened after user taps on the text
userUserOptional. For "text_mention" only, the mentioned user
languageStringOptional. For "pre" only, the programming language of the entity text
+

PhotoSize

+

This object represents one size of a photo or a file / sticker thumbnail.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerPhoto width
heightIntegerPhoto height
file_sizeIntegerOptional. File size in bytes
+

Animation

+

This object represents an animation file (GIF or H.264/MPEG-4 AVC video without sound).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerVideo width as defined by sender
heightIntegerVideo height as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Animation thumbnail as defined by sender
file_nameStringOptional. Original animation filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
+

Audio

+

This object represents an audio file to be treated as music by the Telegram clients.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
durationIntegerDuration of the audio in seconds as defined by sender
performerStringOptional. Performer of the audio as defined by sender or by audio tags
titleStringOptional. Title of the audio as defined by sender or by audio tags
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
thumbPhotoSizeOptional. Thumbnail of the album cover to which the music file belongs
+

Document

+

This object represents a general file (as opposed to photos, voice messages and audio files).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
thumbPhotoSizeOptional. Document thumbnail as defined by sender
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
+

Video

+

This object represents a video file.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerVideo width as defined by sender
heightIntegerVideo height as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Video thumbnail
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. Mime type of a file as defined by sender
file_sizeIntegerOptional. File size in bytes
+

VideoNote

+

This object represents a video message (available in Telegram apps as of v.4.0).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
lengthIntegerVideo width and height (diameter of the video message) as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Video thumbnail
file_sizeIntegerOptional. File size in bytes
+

Voice

+

This object represents a voice note.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
durationIntegerDuration of the audio in seconds as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
+

Contact

+

This object represents a phone contact.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
user_idIntegerOptional. Contact's user identifier in Telegram. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
vcardStringOptional. Additional data about the contact in the form of a vCard
+

Dice

+

This object represents an animated emoji that displays a random value.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
emojiStringEmoji on which the dice throw animation is based
valueIntegerValue of the dice, 1-6 for "🎲", "🎯" and "🎳" base emoji, 1-5 for "🏀" and "⚽" base emoji, 1-64 for "🎰" base emoji
+

PollOption

+

This object contains information about one answer option in a poll.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringOption text, 1-100 characters
voter_countIntegerNumber of users that voted for this option
+

PollAnswer

+

This object represents an answer of a user in a non-anonymous poll.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
poll_idStringUnique poll identifier
userUserThe user, who changed the answer to the poll
option_idsArray of Integer0-based identifiers of answer options, chosen by the user. May be empty if the user retracted their vote.
+

Poll

+

This object contains information about a poll.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique poll identifier
questionStringPoll question, 1-300 characters
optionsArray of PollOptionList of poll options
total_voter_countIntegerTotal number of users that voted in the poll
is_closedBooleanTrue, if the poll is closed
is_anonymousBooleanTrue, if the poll is anonymous
typeStringPoll type, currently can be "regular" or "quiz"
allows_multiple_answersBooleanTrue, if the poll allows multiple answers
correct_option_idIntegerOptional. 0-based identifier of the correct answer option. Available only for polls in the quiz mode, which are closed, or was sent (not forwarded) by the bot or to the private chat with the bot.
explanationStringOptional. Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters
explanation_entitiesArray of MessageEntityOptional. Special entities like usernames, URLs, bot commands, etc. that appear in the explanation
open_periodIntegerOptional. Amount of time in seconds the poll will be active after creation
close_dateIntegerOptional. Point in time (Unix timestamp) when the poll will be automatically closed
+

Location

+

This object represents a point on the map.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
longitudeFloatLongitude as defined by sender
latitudeFloatLatitude as defined by sender
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Time relative to the message sending date, during which the location can be updated, in seconds. For active live locations only.
headingIntegerOptional. The direction in which user is moving, in degrees; 1-360. For active live locations only.
proximity_alert_radiusIntegerOptional. Maximum distance for proximity alerts about approaching another chat member, in meters. For sent live locations only.
+

Venue

+

This object represents a venue.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
locationLocationVenue location. Can't be a live location
titleStringName of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue
foursquare_typeStringOptional. Foursquare type of the venue. (For example, "arts_entertainment/default", "arts_entertainment/aquarium" or "food/icecream".)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
+

ProximityAlertTriggered

+

This object represents the content of a service message, sent whenever a user in the chat triggers a proximity alert set by another user.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
travelerUserUser that triggered the alert
watcherUserUser that set the alert
distanceIntegerThe distance between the users
+

MessageAutoDeleteTimerChanged

+

This object represents a service message about a change in auto-delete timer settings.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
message_auto_delete_timeIntegerNew auto-delete time for messages in the chat
+

VoiceChatScheduled

+

This object represents a service message about a voice chat scheduled in the chat.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
start_dateIntegerPoint in time (Unix timestamp) when the voice chat is supposed to be started by a chat administrator
+

VoiceChatStarted

+

This object represents a service message about a voice chat started in the chat. Currently holds no information.

+

VoiceChatEnded

+

This object represents a service message about a voice chat ended in the chat.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
durationIntegerVoice chat duration in seconds
+

VoiceChatParticipantsInvited

+

This object represents a service message about new members invited to a voice chat.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
usersArray of UserOptional. New members that were invited to the voice chat
+

UserProfilePhotos

+

This object represent a user's profile pictures.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
total_countIntegerTotal number of profile pictures the target user has
photosArray of Array of PhotoSizeRequested profile pictures (in up to 4 sizes each)
+

File

+

This object represents a file ready to be downloaded. The file can be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile.

+
+

Maximum file size to download is 20 MB

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
file_sizeIntegerOptional. File size in bytes, if known
file_pathStringOptional. File path. Use https://api.telegram.org/file/bot<token>/<file_path> to get the file.
+

ReplyKeyboardMarkup

+

This object represents a custom keyboard with reply options (see Introduction to bots for details and examples).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
keyboardArray of Array of KeyboardButtonArray of button rows, each represented by an Array of KeyboardButton objects
resize_keyboardBooleanOptional. Requests clients to resize the keyboard vertically for optimal fit (e.g., make the keyboard smaller if there are just two rows of buttons). Defaults to false, in which case the custom keyboard is always of the same height as the app's standard keyboard.
one_time_keyboardBooleanOptional. Requests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again. Defaults to false.
input_field_placeholderStringOptional. The placeholder to be shown in the input field when the keyboard is active; 1-64 characters
selectiveBooleanOptional. Use this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user requests to change the bot's language, bot replies to the request with a keyboard to select the new language. Other users in the group don't see the keyboard.
+

KeyboardButton

+

This object represents one button of the reply keyboard. For simple text buttons String can be used instead of this object to specify text of the button. Optional fields request_contact, request_location, and request_poll are mutually exclusive.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringText of the button. If none of the optional fields are used, it will be sent as a message when the button is pressed
request_contactBooleanOptional. If True, the user's phone number will be sent as a contact when the button is pressed. Available in private chats only
request_locationBooleanOptional. If True, the user's current location will be sent when the button is pressed. Available in private chats only
request_pollKeyboardButtonPollTypeOptional. If specified, the user will be asked to create a poll and send it to the bot when the button is pressed. Available in private chats only
+

Note: request_contact and request_location options will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message. +Note: request_poll option will only work in Telegram versions released after 23 January, 2020. Older clients will display unsupported message.

+

KeyboardButtonPollType

+

This object represents type of a poll, which is allowed to be created and sent when the corresponding button is pressed.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringOptional. If quiz is passed, the user will be allowed to create only polls in the quiz mode. If regular is passed, only regular polls will be allowed. Otherwise, the user will be allowed to create a poll of any type.
+

ReplyKeyboardRemove

+

Upon receiving a message with this object, Telegram clients will remove the current custom keyboard and display the default letter-keyboard. By default, custom keyboards are displayed until a new keyboard is sent by a bot. An exception is made for one-time keyboards that are hidden immediately after the user presses a button (see ReplyKeyboardMarkup).

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
remove_keyboardTrueRequests clients to remove the custom keyboard (user will not be able to summon this keyboard; if you want to hide the keyboard from sight but keep it accessible, use one_time_keyboard in ReplyKeyboardMarkup)
selectiveBooleanOptional. Use this parameter if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet.
+

InlineKeyboardMarkup

+

This object represents an inline keyboard that appears right next to the message it belongs to.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
inline_keyboardArray of Array of InlineKeyboardButtonArray of button rows, each represented by an Array of InlineKeyboardButton objects
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.

+

InlineKeyboardButton

+

This object represents one button of an inline keyboard. You must use exactly one of the optional fields.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringLabel text on the button
urlStringOptional. HTTP or tg:// url to be opened when button is pressed
login_urlLoginUrlOptional. An HTTP URL used to automatically authorize the user. Can be used as a replacement for the Telegram Login Widget.
callback_dataStringOptional. Data to be sent in a callback query to the bot when button is pressed, 1-64 bytes
switch_inline_queryStringOptional. If set, pressing the button will prompt the user to select one of their chats, open that chat and insert the bot's username and the specified inline query in the input field. Can be empty, in which case just the bot's username will be inserted.

Note: This offers an easy way for users to start using your bot in inline mode when they are currently in a private chat with it. Especially useful when combined with switch_pm... actions – in this case the user will be automatically returned to the chat they switched from, skipping the chat selection screen.
switch_inline_query_current_chatStringOptional. If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. Can be empty, in which case only the bot's username will be inserted.

This offers a quick way for the user to open your bot in inline mode in the same chat – good for selecting something from multiple options.
callback_gameCallbackGameOptional. Description of the game that will be launched when the user presses the button.

NOTE: This type of button must always be the first button in the first row.
payBooleanOptional. Specify True, to send a Pay button.

NOTE: This type of button must always be the first button in the first row.
+

LoginUrl

+

This object represents a parameter of the inline keyboard button used to automatically authorize a user. Serves as a great replacement for the Telegram Login Widget when the user is coming from Telegram. All the user needs to do is tap/click a button and confirm that they want to log in:

+
+ TITLE +
+

Telegram apps support these buttons as of version 5.7.

+
+

Sample bot: @discussbot

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
urlStringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
forward_textStringOptional. New text of the button in forwarded messages.
bot_usernameStringOptional. Username of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
request_write_accessBooleanOptional. Pass True to request the permission for your bot to send messages to the user.
+

CallbackQuery

+

This object represents an incoming callback query from a callback button in an inline keyboard. If the button that originated the query was attached to a message sent by the bot, the field message will be present. If the button was attached to a message sent via the bot (in inline mode), the field inline_message_id will be present. Exactly one of the fields data or game_short_name will be present.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique identifier for this query
fromUserSender
messageMessageOptional. Message with the callback button that originated the query. Note that message content and message date will not be available if the message is too old
inline_message_idStringOptional. Identifier of the message sent via the bot in inline mode, that originated the query.
chat_instanceStringGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataStringOptional. Data associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
game_short_nameStringOptional. Short name of a Game to be returned, serves as the unique identifier for the game
+
+

NOTE: After the user presses a callback button, Telegram clients will display a progress bar until you call answerCallbackQuery. It is, therefore, necessary to react by calling answerCallbackQuery even if no notification to the user is needed (e.g., without specifying any of the optional parameters).

+
+

ForceReply

+

Upon receiving a message with this object, Telegram clients will display a reply interface to the user (act as if the user has selected the bot's message and tapped 'Reply'). This can be extremely useful if you want to create user-friendly step-by-step interfaces without having to sacrifice privacy mode.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
force_replyTrueShows reply interface to the user, as if they manually selected the bot's message and tapped 'Reply'
input_field_placeholderStringOptional. The placeholder to be shown in the input field when the reply is active; 1-64 characters
selectiveBooleanOptional. Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
+
+

Example: A poll bot for groups runs in privacy mode (only receives commands, replies to its messages and mentions). There could be two ways to create a new poll:

+
    +
  • Explain the user how to send a command with parameters (e.g. /newpoll question answer1 answer2). May be appealing for hardcore users but lacks modern day polish.
  • +
  • Guide the user through a step-by-step process. 'Please send me your question', 'Cool, now let's add the first answer option', 'Great. Keep adding answer options, then send /done when you're ready'.
  • +
+

The last option is definitely more attractive. And if you use ForceReply in your bot's questions, it will receive the user's answers even if it only receives replies, commands and mentions — without any extra work for the user.

+
+

ChatPhoto

+

This object represents a chat photo.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
small_file_idStringFile identifier of small (160x160) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
small_file_unique_idStringUnique file identifier of small (160x160) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
big_file_idStringFile identifier of big (640x640) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
big_file_unique_idStringUnique file identifier of big (640x640) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
+

ChatInviteLink

+

Represents an invite link for a chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
invite_linkStringThe invite link. If the link was created by another chat administrator, then the second part of the link will be replaced with "...".
creatorUserCreator of the link
is_primaryBooleanTrue, if the link is primary
is_revokedBooleanTrue, if the link is revoked
expire_dateIntegerOptional. Point in time (Unix timestamp) when the link will expire or has been expired
member_limitIntegerOptional. Maximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
+

ChatMember

+

This object contains information about one member of a chat. Currently, the following 6 types of chat members are supported:

+ +

ChatMemberOwner

+

Represents a chat member that owns the chat and has all administrator privileges.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always "creator"
userUserInformation about the user
is_anonymousBooleanTrue, if the user's presence in the chat is hidden
custom_titleStringOptional. Custom title for this user
+

ChatMemberAdministrator

+

Represents a chat member that has some additional privileges.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always "administrator"
userUserInformation about the user
can_be_editedBooleanTrue, if the bot is allowed to edit administrator privileges of that user
is_anonymousBooleanTrue, if the user's presence in the chat is hidden
can_manage_chatBooleanTrue, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
can_delete_messagesBooleanTrue, if the administrator can delete messages of other users
can_manage_voice_chatsBooleanTrue, if the administrator can manage voice chats
can_restrict_membersBooleanTrue, if the administrator can restrict, ban or unban chat members
can_promote_membersBooleanTrue, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by the user)
can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
can_post_messagesBooleanOptional. True, if the administrator can post in the channel; channels only
can_edit_messagesBooleanOptional. True, if the administrator can edit messages of other users and can pin messages; channels only
can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages; groups and supergroups only
custom_titleStringOptional. Custom title for this user
+

ChatMemberMember

+

Represents a chat member that has no additional privileges or restrictions.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always "member"
userUserInformation about the user
+

ChatMemberRestricted

+

Represents a chat member that is under certain restrictions in the chat. Supergroups only.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always "restricted"
userUserInformation about the user
is_memberBooleanTrue, if the user is a member of the chat at the moment of the request
can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
can_pin_messagesBooleanTrue, if the user is allowed to pin messages
can_send_messagesBooleanTrue, if the user is allowed to send text messages, contacts, locations and venues
can_send_media_messagesBooleanTrue, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes
can_send_pollsBooleanTrue, if the user is allowed to send polls
can_send_other_messagesBooleanTrue, if the user is allowed to send animations, games, stickers and use inline bots
can_add_web_page_previewsBooleanTrue, if the user is allowed to add web page previews to their messages
until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is restricted forever
+

ChatMemberLeft

+

Represents a chat member that isn't currently a member of the chat, but may join it themselves.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always "left"
userUserInformation about the user
+

ChatMemberBanned

+

Represents a chat member that was banned in the chat and can't return to the chat or view chat messages.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
statusStringThe member's status in the chat, always "kicked"
userUserInformation about the user
until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is banned forever
+

ChatMemberUpdated

+

This object represents changes in the status of a chat member.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
chatChatChat the user belongs to
fromUserPerformer of the action, which resulted in the change
dateIntegerDate the change was done in Unix time
old_chat_memberChatMemberPrevious information about the chat member
new_chat_memberChatMemberNew information about the chat member
invite_linkChatInviteLinkOptional. Chat invite link, which was used by the user to join the chat; for joining by invite link events only.
+

ChatPermissions

+

Describes actions that a non-administrator user is allowed to take in a chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
can_send_messagesBooleanOptional. True, if the user is allowed to send text messages, contacts, locations and venues
can_send_media_messagesBooleanOptional. True, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes, implies can_send_messages
can_send_pollsBooleanOptional. True, if the user is allowed to send polls, implies can_send_messages
can_send_other_messagesBooleanOptional. True, if the user is allowed to send animations, games, stickers and use inline bots, implies can_send_media_messages
can_add_web_page_previewsBooleanOptional. True, if the user is allowed to add web page previews to their messages, implies can_send_media_messages
can_change_infoBooleanOptional. True, if the user is allowed to change the chat title, photo and other settings. Ignored in public supergroups
can_invite_usersBooleanOptional. True, if the user is allowed to invite new users to the chat
can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages. Ignored in public supergroups
+

ChatLocation

+

Represents a location to which a chat is connected.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
locationLocationThe location to which the supergroup is connected. Can't be a live location.
addressStringLocation address; 1-64 characters, as defined by the chat owner
+

BotCommand

+

This object represents a bot command.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
commandStringText of the command, 1-32 characters. Can contain only lowercase English letters, digits and underscores.
descriptionStringDescription of the command, 3-256 characters.
+

BotCommandScope

+

This object represents the scope to which bot commands are applied. Currently, the following 7 scopes are supported:

+ +

Determining list of commands

+

The following algorithm is used to determine the list of commands for a particular user viewing the bot menu. The first list of commands which is set is returned:

+

Commands in the chat with the bot

+
    +
  • botCommandScopeChat + language_code
  • +
  • botCommandScopeChat
  • +
  • botCommandScopeAllPrivateChats + language_code
  • +
  • botCommandScopeAllPrivateChats
  • +
  • botCommandScopeDefault + language_code
  • +
  • botCommandScopeDefault
  • +
+

Commands in group and supergroup chats

+
    +
  • botCommandScopeChatMember + language_code
  • +
  • botCommandScopeChatMember
  • +
  • botCommandScopeChatAdministrators + language_code (admins only)
  • +
  • botCommandScopeChatAdministrators (admins only)
  • +
  • botCommandScopeChat + language_code
  • +
  • botCommandScopeChat
  • +
  • botCommandScopeAllChatAdministrators + language_code (admins only)
  • +
  • botCommandScopeAllChatAdministrators (admins only)
  • +
  • botCommandScopeAllGroupChats + language_code
  • +
  • botCommandScopeAllGroupChats
  • +
  • botCommandScopeDefault + language_code
  • +
  • botCommandScopeDefault
  • +
+

BotCommandScopeDefault

+

Represents the default scope of bot commands. Default commands are used if no commands with a narrower scope are specified for the user.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be default
+

BotCommandScopeAllPrivateChats

+

Represents the scope of bot commands, covering all private chats.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be all_private_chats
+

BotCommandScopeAllGroupChats

+

Represents the scope of bot commands, covering all group and supergroup chats.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be all_group_chats
+

BotCommandScopeAllChatAdministrators

+

Represents the scope of bot commands, covering all group and supergroup chat administrators.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be all_chat_administrators
+

BotCommandScopeChat

+

Represents the scope of bot commands, covering a specific chat.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be chat
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
+

BotCommandScopeChatAdministrators

+

Represents the scope of bot commands, covering all administrators of a specific group or supergroup chat.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be chat_administrators
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
+

BotCommandScopeChatMember

+

Represents the scope of bot commands, covering a specific member of a group or supergroup chat.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringScope type, must be chat_member
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerUnique identifier of the target user
+

ResponseParameters

+

Contains information about why a request was unsuccessful.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
retry_afterIntegerOptional. In case of exceeding flood control, the number of seconds left to wait before the request can be repeated
+

InputMedia

+

This object represents the content of a media message to be sent. It should be one of

+ +

InputMediaPhoto

+

Represents a photo to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be photo
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
+

InputMediaVideo

+

Represents a video to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be video
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
widthIntegerOptional. Video width
heightIntegerOptional. Video height
durationIntegerOptional. Video duration in seconds
supports_streamingBooleanOptional. Pass True, if the uploaded video is suitable for streaming
+

InputMediaAnimation

+

Represents an animation file (GIF or H.264/MPEG-4 AVC video without sound) to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be animation
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the animation to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the animation caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
widthIntegerOptional. Animation width
heightIntegerOptional. Animation height
durationIntegerOptional. Animation duration in seconds
+

InputMediaAudio

+

Represents an audio file to be treated as music to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be audio
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the audio to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptional. Duration of the audio in seconds
performerStringOptional. Performer of the audio
titleStringOptional. Title of the audio
+

InputMediaDocument

+

Represents a general file to be sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be document
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
disable_content_type_detectionBooleanOptional. Disables automatic server-side content type detection for files uploaded using multipart/form-data. Always true, if the document is sent as part of an album.
+

InputFile

+

This object represents the contents of a file to be uploaded. Must be posted using multipart/form-data in the usual way that files are uploaded via the browser.

+

Sending files

+

There are three ways to send files (photos, stickers, audio, media, etc.):

+
    +
  1. If the file is already stored somewhere on the Telegram servers, you don't need to reupload it: each file object has a file_id field, simply pass this file_id as a parameter instead of uploading. There are no limits for files sent this way.
  2. +
  3. Provide Telegram with an HTTP URL for the file to be sent. Telegram will download and send the file. 5 MB max size for photos and 20 MB max for other types of content.
  4. +
  5. Post the file using multipart/form-data in the usual way that files are uploaded via the browser. 10 MB max size for photos, 50 MB for other files.
  6. +
+

Sending by file_id

+
    +
  • It is not possible to change the file type when resending by file_id. I.e. a video can't be sent as a photo, a photo can't be sent as a document, etc.
  • +
  • It is not possible to resend thumbnails.
  • +
  • Resending a photo by file_id will send all of its sizes.
  • +
  • file_id is unique for each individual bot and can't be transferred from one bot to another.
  • +
  • file_id uniquely identifies a file, but a file can have different valid file_ids even for the same bot.
  • +
+

Sending by URL

+
    +
  • When sending by URL the target file must have the correct MIME type (e.g., audio/mpeg for sendAudio, etc.).
  • +
  • In sendDocument, sending by URL will currently only work for GIF, PDF and ZIP files.
  • +
  • To use sendVoice, the file must have the type audio/ogg and be no more than 1MB in size. 1-20MB voice notes will be sent as files.
  • +
  • Other configurations may work but we can't guarantee that they will.
  • +
+

Inline mode objects

+

Objects and methods used in the inline mode are described in the Inline mode section.

+

Available methods

+
+

All methods in the Bot API are case-insensitive. We support GET and POST HTTP methods. Use either URL query string or application/json or application/x-www-form-urlencoded or multipart/form-data for passing parameters in Bot API requests. +On successful call, a JSON-object containing the result will be returned.

+
+

getMe

+

A simple method for testing your bot's authentication token. Requires no parameters. Returns basic information about the bot in form of a User object.

+

logOut

+

Use this method to log out from the cloud Bot API server before launching the bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive updates. After a successful call, you can immediately log in on a local server, but will not be able to log in back to the cloud Bot API server for 10 minutes. Returns True on success. Requires no parameters.

+

close

+

Use this method to close the bot instance before moving it from one local server to another. You need to delete the webhook before calling this method to ensure that the bot isn't launched again after server restart. The method will return error 429 in the first 10 minutes after the bot is launched. Returns True on success. Requires no parameters.

+

sendMessage

+

Use this method to send text messages. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
textStringYesText of the message to be sent, 1-4096 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptionalDisables link previews for links in this message
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

Formatting options

+

The Bot API supports basic formatting for messages. You can use bold, italic, underlined and strikethrough text, as well as inline links and pre-formatted code in your bots' messages. Telegram clients will render them accordingly. You can use either markdown-style or HTML-style formatting.

+

Note that Telegram clients will display an alert to the user before opening an inline link ('Open this link?' together with the full URL).

+

Message entities can be nested, providing following restrictions are met:

+
    +
  • If two entities has common characters then one of them is fully contained inside another.
  • +
  • bold, italic, underline and strikethrough entities can contain and to be contained in any other entities, except pre and code.
  • +
  • All other entities can't contain each other.
  • +
+

Links tg://user?id=<user_id> can be used to mention a user by their ID without using a username. Please note:

+
    +
  • These links will work only if they are used inside an inline link. For example, they will not work, when used in an inline keyboard button or in a message text.
  • +
  • These mentions are only guaranteed to work if the user has contacted the bot in the past, has sent a callback query to the bot via inline button or is a member in the group where he was mentioned.
  • +
+
MarkdownV2 style
+

To use this mode, pass MarkdownV2 in the parse_mode field. Use the following syntax in your message:

+
*bold \*text*
+_italic \*text_
+__underline__
+~strikethrough~
+*bold _italic bold ~italic bold strikethrough~ __underline italic bold___ bold*
+[inline URL](http://www.example.com/)
+[inline mention of a user](tg://user?id=123456789)
+`inline fixed-width code`
+```
+pre-formatted fixed-width code block
+```
+```python
+pre-formatted fixed-width code block written in the Python programming language
+```
+

Please note:

+
    +
  • Any character with code between 1 and 126 inclusively can be escaped anywhere with a preceding '\' character, in which case it is treated as an ordinary character and not a part of the markup. This implies that '\' character usually must be escaped with a preceding '\' character.
  • +
  • Inside pre and code entities, all '`' and '\' characters must be escaped with a preceding '\' character.
  • +
  • Inside (...) part of inline link definition, all ')' and '\' must be escaped with a preceding '\' character.
  • +
  • In all other places characters '_', '*', '[', ']', '(', ')', '~', '`', '>', '#', '+', '-', '=', '|', '{', '}', '.', '!' must be escaped with the preceding character '\'.
  • +
  • In case of ambiguity between italic and underline entities __ is always greadily treated from left to right as beginning or end of underline entity, so instead of ___italic underline___ use ___italic underline_\r__, where \r is a character with code 13, which will be ignored.
  • +
+
HTML style
+

To use this mode, pass HTML in the parse_mode field. The following tags are currently supported:

+
<b>bold</b>, <strong>bold</strong>
+<i>italic</i>, <em>italic</em>
+<u>underline</u>, <ins>underline</ins>
+<s>strikethrough</s>, <strike>strikethrough</strike>, <del>strikethrough</del>
+<b>bold <i>italic bold <s>italic bold strikethrough</s> <u>underline italic bold</u></i> bold</b>
+<a href="http://www.example.com/">inline URL</a>
+<a href="tg://user?id=123456789">inline mention of a user</a>
+<code>inline fixed-width code</code>
+<pre>pre-formatted fixed-width code block</pre>
+<pre><code class="language-python">pre-formatted fixed-width code block written in the Python programming language</code></pre>
+

Please note:

+
    +
  • Only the tags mentioned above are currently supported.
  • +
  • All <, > and & symbols that are not a part of a tag or an HTML entity must be replaced with the corresponding HTML entities (< with &lt;, > with &gt; and & with &amp;).
  • +
  • All numerical HTML entities are supported.
  • +
  • The API currently supports only the following named HTML entities: &lt;, &gt;, &amp; and &quot;.
  • +
  • Use nested pre and code tags, to define programming language for pre entity.
  • +
  • Programming language can't be specified for standalone code tags.
  • +
+
Markdown style
+

This is a legacy mode, retained for backward compatibility. To use this mode, pass Markdown in the parse_mode field. Use the following syntax in your message:

+
*bold text*
+_italic text_
+[inline URL](http://www.example.com/)
+[inline mention of a user](tg://user?id=123456789)
+`inline fixed-width code`
+```
+pre-formatted fixed-width code block
+```
+```python
+pre-formatted fixed-width code block written in the Python programming language
+```
+

Please note:

+
    +
  • Entities must not be nested, use parse mode MarkdownV2 instead.
  • +
  • There is no way to specify underline and strikethrough entities, use parse mode MarkdownV2 instead.
  • +
  • To escape characters '_', '*', '`', '[' outside of an entity, prepend the characters '\' before them.
  • +
  • Escaping inside entities is not allowed, so entity must be closed first and reopened again: use _snake_\__case_ for italic snake_case and *2*\**2=4* for bold 2*2=4.
  • +
+

forwardMessage

+

Use this method to forward messages of any kind. Service messages can't be forwarded. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
message_idIntegerYesMessage identifier in the chat specified in from_chat_id
+

copyMessage

+

Use this method to copy messages of any kind. Service messages and invoice messages can't be copied. The method is analogous to the method forwardMessage, but the copied message doesn't have a link to the original message. Returns the MessageId of the sent message on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
message_idIntegerYesMessage identifier in the chat specified in from_chat_id
captionStringOptionalNew caption for media, 0-1024 characters after entities parsing. If not specified, the original caption is kept
parse_modeStringOptionalMode for parsing entities in the new caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the new caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendPhoto

+

Use this method to send photos. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
photoInputFile or StringYesPhoto to send. Pass a file_id as String to send a photo that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a photo from the Internet, or upload a new photo using multipart/form-data. The photo must be at most 10 MB in size. The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20. More info on Sending Files »
captionStringOptionalPhoto caption (may also be used when resending photos by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendAudio

+

Use this method to send audio files, if you want Telegram clients to display them in the music player. Your audio must be in the .MP3 or .M4A format. On success, the sent Message is returned. Bots can currently send audio files of up to 50 MB in size, this limit may be changed in the future.

+

For sending voice messages, use the sendVoice method instead.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
audioInputFile or StringYesAudio file to send. Pass a file_id as String to send an audio file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an audio file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
captionStringOptionalAudio caption, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptionalDuration of the audio in seconds
performerStringOptionalPerformer
titleStringOptionalTrack name
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendDocument

+

Use this method to send general files. On success, the sent Message is returned. Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
documentInputFile or StringYesFile to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalDocument caption (may also be used when resending documents by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_content_type_detectionBooleanOptionalDisables automatic server-side content type detection for files uploaded using multipart/form-data
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendVideo

+

Use this method to send video files, Telegram clients support mp4 videos (other formats may be sent as Document). On success, the sent Message is returned. Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
videoInputFile or StringYesVideo to send. Pass a file_id as String to send a video that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a video from the Internet, or upload a new video using multipart/form-data. More info on Sending Files »
durationIntegerOptionalDuration of sent video in seconds
widthIntegerOptionalVideo width
heightIntegerOptionalVideo height
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalVideo caption (may also be used when resending videos by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
supports_streamingBooleanOptionalPass True, if the uploaded video is suitable for streaming
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendAnimation

+

Use this method to send animation files (GIF or H.264/MPEG-4 AVC video without sound). On success, the sent Message is returned. Bots can currently send animation files of up to 50 MB in size, this limit may be changed in the future.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
animationInputFile or StringYesAnimation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an animation from the Internet, or upload a new animation using multipart/form-data. More info on Sending Files »
durationIntegerOptionalDuration of sent animation in seconds
widthIntegerOptionalAnimation width
heightIntegerOptionalAnimation height
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalAnimation caption (may also be used when resending animation by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the animation caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendVoice

+

Use this method to send audio files, if you want Telegram clients to display the file as a playable voice message. For this to work, your audio must be in an .OGG file encoded with OPUS (other formats may be sent as Audio or Document). On success, the sent Message is returned. Bots can currently send voice messages of up to 50 MB in size, this limit may be changed in the future.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
voiceInputFile or StringYesAudio file to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
captionStringOptionalVoice message caption, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptionalDuration of the voice message in seconds
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendVideoNote

+

As of v.4.0, Telegram clients support rounded square mp4 videos of up to 1 minute long. Use this method to send video messages. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
video_noteInputFile or StringYesVideo note to send. Pass a file_id as String to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. More info on Sending Files ». Sending video notes by a URL is currently unsupported
durationIntegerOptionalDuration of sent video in seconds
lengthIntegerOptionalVideo width and height, i.e. diameter of the video message
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendMediaGroup

+

Use this method to send a group of photos, videos, documents or audios as an album. Documents and audio files can be only grouped in an album with messages of the same type. On success, an array of Messages that were sent is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
mediaArray of InputMediaAudio, InputMediaDocument, InputMediaPhoto and InputMediaVideoYesA JSON-serialized array describing messages to be sent, must include 2-10 items
disable_notificationBooleanOptionalSends messages silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the messages are a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
+

sendLocation

+

Use this method to send point on the map. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
latitudeFloat numberYesLatitude of the location
longitudeFloat numberYesLongitude of the location
horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptionalPeriod in seconds for which the location will be updated (see Live Locations, should be between 60 and 86400.
headingIntegerOptionalFor live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptionalFor live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

editMessageLiveLocation

+

Use this method to edit live location messages. A location can be edited until its live_period expires or editing is explicitly disabled by a call to stopMessageLiveLocation. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
latitudeFloat numberYesLatitude of new location
longitudeFloat numberYesLongitude of new location
horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
headingIntegerOptionalDirection in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptionalMaximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
+

stopMessageLiveLocation

+

Use this method to stop updating a live location message before live_period expires. On success, if the message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message with live location to stop
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
+

sendVenue

+

Use this method to send information about a venue. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
latitudeFloat numberYesLatitude of the venue
longitudeFloat numberYesLongitude of the venue
titleStringYesName of the venue
addressStringYesAddress of the venue
foursquare_idStringOptionalFoursquare identifier of the venue
foursquare_typeStringOptionalFoursquare type of the venue, if known. (For example, "arts_entertainment/default", "arts_entertainment/aquarium" or "food/icecream".)
google_place_idStringOptionalGoogle Places identifier of the venue
google_place_typeStringOptionalGoogle Places type of the venue. (See supported types.)
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendContact

+

Use this method to send phone contacts. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
phone_numberStringYesContact's phone number
first_nameStringYesContact's first name
last_nameStringOptionalContact's last name
vcardStringOptionalAdditional data about the contact in the form of a vCard, 0-2048 bytes
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove keyboard or to force a reply from the user.
+

sendPoll

+

Use this method to send a native poll. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
questionStringYesPoll question, 1-300 characters
optionsArray of StringYesA JSON-serialized list of answer options, 2-10 strings 1-100 characters each
is_anonymousBooleanOptionalTrue, if the poll needs to be anonymous, defaults to True
typeStringOptionalPoll type, "quiz" or "regular", defaults to "regular"
allows_multiple_answersBooleanOptionalTrue, if the poll allows multiple answers, ignored for polls in quiz mode, defaults to False
correct_option_idIntegerOptional0-based identifier of the correct answer option, required for polls in quiz mode
explanationStringOptionalText that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds after entities parsing
explanation_parse_modeStringOptionalMode for parsing entities in the explanation. See formatting options for more details.
explanation_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the poll explanation, which can be specified instead of parse_mode
open_periodIntegerOptionalAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateIntegerOptionalPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future. Can't be used together with open_period.
is_closedBooleanOptionalPass True, if the poll needs to be immediately closed. This can be useful for poll preview.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendDice

+

Use this method to send an animated emoji that will display a random value. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
emojiStringOptionalEmoji on which the dice throw animation is based. Currently, must be one of "🎲", "🎯", "🏀", "⚽", "🎳", or "🎰". Dice can have values 1-6 for "🎲", "🎯" and "🎳", values 1-5 for "🏀" and "⚽", and values 1-64 for "🎰". Defaults to "🎲"
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

sendChatAction

+

Use this method when you need to tell the user that something is happening on the bot's side. The status is set for 5 seconds or less (when a message arrives from your bot, Telegram clients clear its typing status). Returns True on success.

+
+

Example: The ImageBot needs some time to process a request and upload the image. Instead of sending a text message along the lines of "Retrieving image, please wait...", the bot may use sendChatAction with action = upload_photo. The user will see a "sending photo" status for the bot.

+
+

We only recommend using this method when a response from the bot will take a noticeable amount of time to arrive.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
actionStringYesType of action to broadcast. Choose one, depending on what the user is about to receive: typing for text messages, upload_photo for photos, record_video or upload_video for videos, record_voice or upload_voice for voice notes, upload_document for general files, find_location for location data, record_video_note or upload_video_note for video notes.
+

getUserProfilePhotos

+

Use this method to get a list of profile pictures for a user. Returns a UserProfilePhotos object.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUnique identifier of the target user
offsetIntegerOptionalSequential number of the first photo to be returned. By default, all photos are returned.
limitIntegerOptionalLimits the number of photos to be retrieved. Values between 1-100 are accepted. Defaults to 100.
+

getFile

+

Use this method to get basic info about a file and prepare it for downloading. For the moment, bots can download files of up to 20MB in size. On success, a File object is returned. The file can then be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>, where <file_path> is taken from the response. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile again.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
file_idStringYesFile identifier to get info about
+

Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type and name (if available) when the File object is received.

+

banChatMember

+

Use this method to ban a user in a group, a supergroup or a channel. In the case of supergroups and channels, the user will not be able to return to the chat on their own using invite links, etc., unless unbanned first. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
until_dateIntegerOptionalDate when the user will be unbanned, unix time. If user is banned for more than 366 days or less than 30 seconds from the current time they are considered to be banned forever. Applied for supergroups and channels only.
revoke_messagesBooleanOptionalPass True to delete all messages from the chat for the user that is being removed. If False, the user will be able to see messages in the group that were sent before the user was removed. Always True for supergroups and channels.
+

unbanChatMember

+

Use this method to unban a previously banned user in a supergroup or channel. The user will not return to the group or channel automatically, but will be able to join via link, etc. The bot must be an administrator for this to work. By default, this method guarantees that after the call the user is not a member of the chat, but will be able to join it. So if the user is a member of the chat they will also be removed from the chat. If you don't want this, use the parameter only_if_banned. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @username)
user_idIntegerYesUnique identifier of the target user
only_if_bannedBooleanOptionalDo nothing if the user is not banned
+

restrictChatMember

+

Use this method to restrict a user in a supergroup. The bot must be an administrator in the supergroup for this to work and must have the appropriate admin rights. Pass True for all permissions to lift restrictions from a user. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerYesUnique identifier of the target user
permissionsChatPermissionsYesA JSON-serialized object for new user permissions
until_dateIntegerOptionalDate when restrictions will be lifted for the user, unix time. If user is restricted for more than 366 days or less than 30 seconds from the current time, they are considered to be restricted forever
+

promoteChatMember

+

Use this method to promote or demote a user in a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Pass False for all boolean parameters to demote a user. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
is_anonymousBooleanOptionalPass True, if the administrator's presence in the chat is hidden
can_manage_chatBooleanOptionalPass True, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
can_post_messagesBooleanOptionalPass True, if the administrator can create channel posts, channels only
can_edit_messagesBooleanOptionalPass True, if the administrator can edit messages of other users and can pin messages, channels only
can_delete_messagesBooleanOptionalPass True, if the administrator can delete messages of other users
can_manage_voice_chatsBooleanOptionalPass True, if the administrator can manage voice chats
can_restrict_membersBooleanOptionalPass True, if the administrator can restrict, ban or unban chat members
can_promote_membersBooleanOptionalPass True, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by him)
can_change_infoBooleanOptionalPass True, if the administrator can change chat title, photo and other settings
can_invite_usersBooleanOptionalPass True, if the administrator can invite new users to the chat
can_pin_messagesBooleanOptionalPass True, if the administrator can pin messages, supergroups only
+

setChatAdministratorCustomTitle

+

Use this method to set a custom title for an administrator in a supergroup promoted by the bot. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerYesUnique identifier of the target user
custom_titleStringYesNew custom title for the administrator; 0-16 characters, emoji are not allowed
+

setChatPermissions

+

Use this method to set default chat permissions for all members. The bot must be an administrator in the group or a supergroup for this to work and must have the can_restrict_members admin rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
permissionsChatPermissionsYesA JSON-serialized object for new default chat permissions
+

exportChatInviteLink

+

Use this method to generate a new primary invite link for a chat; any previously generated primary link is revoked. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns the new invite link as String on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
+
+

Note: Each administrator in a chat generates their own invite links. Bots can't use invite links generated by other administrators. If you want your bot to work with invite links, it will need to generate its own link using exportChatInviteLink or by calling the getChat method. If your bot needs to generate a new primary invite link replacing its previous one, use exportChatInviteLink again.

+
+

createChatInviteLink

+

Use this method to create an additional invite link for a chat. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. The link can be revoked using the method revokeChatInviteLink. Returns the new invite link as ChatInviteLink object.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
+

editChatInviteLink

+

Use this method to edit a non-primary invite link created by the bot. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns the edited invite link as a ChatInviteLink object.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
invite_linkStringYesThe invite link to edit
expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
+

revokeChatInviteLink

+

Use this method to revoke an invite link created by the bot. If the primary link is revoked, a new link is automatically generated. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns the revoked invite link as ChatInviteLink object.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier of the target chat or username of the target channel (in the format @channelusername)
invite_linkStringYesThe invite link to revoke
+

setChatPhoto

+

Use this method to set a new profile photo for the chat. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
photoInputFileYesNew chat photo, uploaded using multipart/form-data
+

deleteChatPhoto

+

Use this method to delete a chat photo. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
+

setChatTitle

+

Use this method to change the title of a chat. Titles can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
titleStringYesNew chat title, 1-255 characters
+

setChatDescription

+

Use this method to change the description of a group, a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
descriptionStringOptionalNew chat description, 0-255 characters
+

pinChatMessage

+

Use this method to add a message to the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' admin right in a supergroup or 'can_edit_messages' admin right in a channel. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of a message to pin
disable_notificationBooleanOptionalPass True, if it is not necessary to send a notification to all chat members about the new pinned message. Notifications are always disabled in channels and private chats.
+

unpinChatMessage

+

Use this method to remove a message from the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' admin right in a supergroup or 'can_edit_messages' admin right in a channel. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalIdentifier of a message to unpin. If not specified, the most recent pinned message (by sending date) will be unpinned.
+

unpinAllChatMessages

+

Use this method to clear the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' admin right in a supergroup or 'can_edit_messages' admin right in a channel. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
+

leaveChat

+

Use this method for your bot to leave a group, supergroup or channel. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
+

getChat

+

Use this method to get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.). Returns a Chat object on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
+

getChatAdministrators

+

Use this method to get a list of administrators in a chat. On success, returns an Array of ChatMember objects that contains information about all chat administrators except other bots. If the chat is a group or a supergroup and no administrators were appointed, only the creator will be returned.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
+

getChatMemberCount

+

Use this method to get the number of members in a chat. Returns Int on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
+

getChatMember

+

Use this method to get information about a member of a chat. Returns a ChatMember object on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
+

setChatStickerSet

+

Use this method to set a new group sticker set for a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
sticker_set_nameStringYesName of the sticker set to be set as the group sticker set
+

deleteChatStickerSet

+

Use this method to delete a group sticker set from a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
+

answerCallbackQuery

+

Use this method to send answers to callback queries sent from inline keyboards. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. On success, True is returned.

+
+

Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via @Botfather and accept the terms. Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
callback_query_idStringYesUnique identifier for the query to be answered
textStringOptionalText of the notification. If not specified, nothing will be shown to the user, 0-200 characters
show_alertBooleanOptionalIf true, an alert will be shown by the client instead of a notification at the top of the chat screen. Defaults to false.
urlStringOptionalURL that will be opened by the user's client. If you have created a Game and accepted the conditions via @Botfather, specify the URL that opens your game — note that this will only work if the query comes from a callback_game button.

Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.
cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the callback query may be cached client-side. Telegram apps will support caching starting in version 3.14. Defaults to 0.
+

setMyCommands

+

Use this method to change the list of the bot's commands. See https://core.telegram.org/bots#commands for more details about bot commands. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
commandsArray of BotCommandYesA JSON-serialized list of bot commands to be set as the list of the bot's commands. At most 100 commands can be specified.
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
+

deleteMyCommands

+

Use this method to delete the list of the bot's commands for the given scope and user language. After deletion, higher level commands will be shown to affected users. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
+

getMyCommands

+

Use this method to get the current list of the bot's commands for the given scope and user language. Returns Array of BotCommand on success. If commands aren't set, an empty list is returned.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code or an empty string
+

Inline mode methods

+

Methods and objects used in the inline mode are described in the Inline mode section.

+

Updating messages

+

The following methods allow you to change an existing message in the message history instead of sending a new one with a result of an action. This is most useful for messages with inline keyboards using callback queries, but can also help reduce clutter in conversations with regular chat bots.

+

Please note, that it is currently only possible to edit messages without reply_markup or with inline keyboards.

+

editMessageText

+

Use this method to edit text and game messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
textStringYesNew text of the message, 1-4096 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptionalDisables link previews for links in this message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
+

editMessageCaption

+

Use this method to edit captions of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
captionStringOptionalNew caption of the message, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
+

editMessageMedia

+

Use this method to edit animation, audio, document, photo, or video messages. If a message is part of a message album, then it can be edited only to an audio for audio albums, only to a document for document albums and to a photo or a video otherwise. When an inline message is edited, a new file can't be uploaded; use a previously uploaded file via its file_id or specify a URL. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
mediaInputMediaYesA JSON-serialized object for a new media content of the message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
+

editMessageReplyMarkup

+

Use this method to edit only the reply markup of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
+

stopPoll

+

Use this method to stop a poll which was sent by the bot. On success, the stopped Poll is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of the original message with the poll
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new message inline keyboard.
+

deleteMessage

+

Use this method to delete a message, including service messages, with the following limitations:

+
    +
  • A message can only be deleted if it was sent less than 48 hours ago.
  • +
  • A dice message in a private chat can only be deleted if it was sent more than 24 hours ago.
  • +
  • Bots can delete outgoing messages in private chats, groups, and supergroups.
  • +
  • Bots can delete incoming messages in private chats.
  • +
  • Bots granted can_post_messages permissions can delete outgoing messages in channels.
  • +
  • If the bot is an administrator of a group, it can delete any message there.
  • +
  • If the bot has can_delete_messages permission in a supergroup or a channel, it can delete any message there. +Returns True on success.
  • +
+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of the message to delete
+

Stickers

+

The following methods and objects allow your bot to handle stickers and sticker sets.

+

Sticker

+

This object represents a sticker.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerSticker width
heightIntegerSticker height
is_animatedBooleanTrue, if the sticker is animated
thumbPhotoSizeOptional. Sticker thumbnail in the .WEBP or .JPG format
emojiStringOptional. Emoji associated with the sticker
set_nameStringOptional. Name of the sticker set to which the sticker belongs
mask_positionMaskPositionOptional. For mask stickers, the position where the mask should be placed
file_sizeIntegerOptional. File size in bytes
+

StickerSet

+

This object represents a sticker set.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
nameStringSticker set name
titleStringSticker set title
is_animatedBooleanTrue, if the sticker set contains animated stickers
contains_masksBooleanTrue, if the sticker set contains masks
stickersArray of StickerList of all set stickers
thumbPhotoSizeOptional. Sticker set thumbnail in the .WEBP or .TGS format
+

MaskPosition

+

This object describes the position on faces where a mask should be placed by default.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
pointStringThe part of the face relative to which the mask should be placed. One of "forehead", "eyes", "mouth", or "chin".
x_shiftFloat numberShift by X-axis measured in widths of the mask scaled to the face size, from left to right. For example, choosing -1.0 will place mask just to the left of the default mask position.
y_shiftFloat numberShift by Y-axis measured in heights of the mask scaled to the face size, from top to bottom. For example, 1.0 will place the mask just below the default mask position.
scaleFloat numberMask scaling coefficient. For example, 2.0 means double size.
+

sendSticker

+

Use this method to send static .WEBP or animated .TGS stickers. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
stickerInputFile or StringYesSticker to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a .WEBP file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
+

getStickerSet

+

Use this method to get a sticker set. On success, a StickerSet object is returned.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
nameStringYesName of the sticker set
+

uploadStickerFile

+

Use this method to upload a .PNG file with a sticker for later use in createNewStickerSet and addStickerToSet methods (can be used multiple times). Returns the uploaded File on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of sticker file owner
png_stickerInputFileYesPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. More info on Sending Files »
+

createNewStickerSet

+

Use this method to create a new sticker set owned by a user. The bot will be able to edit the sticker set thus created. You must use exactly one of the fields png_sticker or tgs_sticker. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of created sticker set owner
nameStringYesShort name of sticker set, to be used in t.me/addstickers/ URLs (e.g., animals). Can contain only english letters, digits and underscores. Must begin with a letter, can't contain consecutive underscores and must end in "by<bot username>". <bot_username> is case insensitive. 1-64 characters.
titleStringYesSticker set title, 1-64 characters
png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/animated_stickers#technical-requirements for technical requirements
emojisStringYesOne or more emoji corresponding to the sticker
contains_masksBooleanOptionalPass True, if a set of mask stickers should be created
mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
+

addStickerToSet

+

Use this method to add a new sticker to a set created by the bot. You must use exactly one of the fields png_sticker or tgs_sticker. Animated stickers can be added to animated sticker sets and only to them. Animated sticker sets can have up to 50 stickers. Static sticker sets can have up to 120 stickers. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of sticker set owner
nameStringYesSticker set name
png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/animated_stickers#technical-requirements for technical requirements
emojisStringYesOne or more emoji corresponding to the sticker
mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
+

setStickerPositionInSet

+

Use this method to move a sticker in a set created by the bot to a specific position. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
stickerStringYesFile identifier of the sticker
positionIntegerYesNew sticker position in the set, zero-based
+

deleteStickerFromSet

+

Use this method to delete a sticker from a set created by the bot. Returns True on success.

+ + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
stickerStringYesFile identifier of the sticker
+

setStickerSetThumb

+

Use this method to set the thumbnail of a sticker set. Animated thumbnails can be set for animated sticker sets only. Returns True on success.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
nameStringYesSticker set name
user_idIntegerYesUser identifier of the sticker set owner
thumbInputFile or StringOptionalA PNG image with the thumbnail, must be up to 128 kilobytes in size and have width and height exactly 100px, or a TGS animation with the thumbnail up to 32 kilobytes in size; see https://core.telegram.org/animated_stickers#technical-requirements for animated sticker technical requirements. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files ». Animated sticker set thumbnail can't be uploaded via HTTP URL.
+

Inline mode

+

The following methods and objects allow your bot to work in inline mode. +Please see our Introduction to Inline bots for more details.

+

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot's name.

+

InlineQuery

+

This object represents an incoming inline query. When the user sends an empty query, your bot could return some default or trending results.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique identifier for this query
fromUserSender
queryStringText of the query (up to 256 characters)
offsetStringOffset of the results to be returned, can be controlled by the bot
chat_typeStringOptional. Type of the chat, from which the inline query was sent. Can be either "sender" for a private chat with the inline query sender, "private", "group", "supergroup", or "channel". The chat type should be always known for requests sent from official clients and most third-party clients, unless the request was sent from a secret chat
locationLocationOptional. Sender location, only for bots that request user location
+

answerInlineQuery

+

Use this method to send answers to an inline query. On success, True is returned. +No more than 50 results per query are allowed.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
inline_query_idStringYesUnique identifier for the answered query
resultsArray of InlineQueryResultYesA JSON-serialized array of results for the inline query
cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
is_personalBooleanOptionalPass True, if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
next_offsetStringOptionalPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don't support pagination. Offset length can't exceed 64 bytes.
switch_pm_textStringOptionalIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with the parameter switch_pm_parameter
switch_pm_parameterStringOptionalDeep-linking parameter for the /start message sent to the bot when user presses the switch button. 1-64 characters, only A-Z, a-z, 0-9, _ and - are allowed.

Example: An inline bot that sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even before showing any. The user presses the button, switches to a private chat with the bot and, in doing so, passes a start parameter that instructs the bot to return an OAuth link. Once done, the bot can offer a switch_inline button so that the user can easily return to the chat where they wanted to use the bot's inline capabilities.
+

InlineQueryResult

+

This object represents one result of an inline query. Telegram clients currently support results of the following 20 types:

+ +

Note: All URLs passed in inline query results will be available to end users and therefore must be assumed to be public.

+

InlineQueryResultArticle

+

Represents a link to an article or web page.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be article
idStringUnique identifier for this result, 1-64 Bytes
titleStringTitle of the result
input_message_contentInputMessageContentContent of the message to be sent
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
urlStringOptional. URL of the result
hide_urlBooleanOptional. Pass True, if you don't want the URL to be shown in the message
descriptionStringOptional. Short description of the result
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

InlineQueryResultPhoto

+

Represents a link to a photo. By default, this photo will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be photo
idStringUnique identifier for this result, 1-64 bytes
photo_urlStringA valid URL of the photo. Photo must be in JPEG format. Photo size must not exceed 5MB
thumb_urlStringURL of the thumbnail for the photo
photo_widthIntegerOptional. Width of the photo
photo_heightIntegerOptional. Height of the photo
titleStringOptional. Title for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
+

InlineQueryResultGif

+

Represents a link to an animated GIF file. By default, this animated GIF file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be gif
idStringUnique identifier for this result, 1-64 bytes
gif_urlStringA valid URL for the GIF file. File size must not exceed 1MB
gif_widthIntegerOptional. Width of the GIF
gif_heightIntegerOptional. Height of the GIF
gif_durationIntegerOptional. Duration of the GIF in seconds
thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of "image/jpeg", "image/gif", or "video/mp4". Defaults to "image/jpeg"
titleStringOptional. Title for the result
captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
+

InlineQueryResultMpeg4Gif

+

Represents a link to a video animation (H.264/MPEG-4 AVC video without sound). By default, this animated MPEG-4 file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be mpeg4_gif
idStringUnique identifier for this result, 1-64 bytes
mpeg4_urlStringA valid URL for the MP4 file. File size must not exceed 1MB
mpeg4_widthIntegerOptional. Video width
mpeg4_heightIntegerOptional. Video height
mpeg4_durationIntegerOptional. Video duration in seconds
thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of "image/jpeg", "image/gif", or "video/mp4". Defaults to "image/jpeg"
titleStringOptional. Title for the result
captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
+

InlineQueryResultVideo

+

Represents a link to a page containing an embedded video player or a video file. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

+
+

If an InlineQueryResultVideo message contains an embedded video (e.g., YouTube), you must replace its content using input_message_content.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be video
idStringUnique identifier for this result, 1-64 bytes
video_urlStringA valid URL for the embedded video player or video file
mime_typeStringMime type of the content of video url, "text/html" or "video/mp4"
thumb_urlStringURL of the thumbnail (JPEG only) for the video
titleStringTitle for the result
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
video_widthIntegerOptional. Video width
video_heightIntegerOptional. Video height
video_durationIntegerOptional. Video duration in seconds
descriptionStringOptional. Short description of the result
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video. This field is required if InlineQueryResultVideo is used to send an HTML-page as a result (e.g., a YouTube video).
+

InlineQueryResultAudio

+

Represents a link to an MP3 audio file. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be audio
idStringUnique identifier for this result, 1-64 bytes
audio_urlStringA valid URL for the audio file
titleStringTitle
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
performerStringOptional. Performer
audio_durationIntegerOptional. Audio duration in seconds
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultVoice

+

Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be voice
idStringUnique identifier for this result, 1-64 bytes
voice_urlStringA valid URL for the voice recording
titleStringRecording title
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
voice_durationIntegerOptional. Recording duration in seconds
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice recording
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultDocument

+

Represents a link to a file. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. Currently, only .PDF and .ZIP files can be sent using this method.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be document
idStringUnique identifier for this result, 1-64 bytes
titleStringTitle for the result
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
document_urlStringA valid URL for the file
mime_typeStringMime type of the content of the file, either "application/pdf" or "application/zip"
descriptionStringOptional. Short description of the result
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
thumb_urlStringOptional. URL of the thumbnail (JPEG only) for the file
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultLocation

+

Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be location
idStringUnique identifier for this result, 1-64 Bytes
latitudeFloat numberLocation latitude in degrees
longitudeFloat numberLocation longitude in degrees
titleStringLocation title
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the location
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultVenue

+

Represents a venue. By default, the venue will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the venue.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be venue
idStringUnique identifier for this result, 1-64 Bytes
latitudeFloatLatitude of the venue location in degrees
longitudeFloatLongitude of the venue location in degrees
titleStringTitle of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue if known
foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, "arts_entertainment/default", "arts_entertainment/aquarium" or "food/icecream".)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the venue
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultContact

+

Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be contact
idStringUnique identifier for this result, 1-64 Bytes
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the contact
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultGame

+

Represents a Game.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be game
idStringUnique identifier for this result, 1-64 bytes
game_short_nameStringShort name of the game
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
+

Note: This will only work in Telegram versions released after October 1, 2016. Older clients will not display any inline results if a game result is among them.

+

InlineQueryResultCachedPhoto

+

Represents a link to a photo stored on the Telegram servers. By default, this photo will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be photo
idStringUnique identifier for this result, 1-64 bytes
photo_file_idStringA valid file identifier of the photo
titleStringOptional. Title for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
+

InlineQueryResultCachedGif

+

Represents a link to an animated GIF file stored on the Telegram servers. By default, this animated GIF file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with specified content instead of the animation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be gif
idStringUnique identifier for this result, 1-64 bytes
gif_file_idStringA valid file identifier for the GIF file
titleStringOptional. Title for the result
captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
+

InlineQueryResultCachedMpeg4Gif

+

Represents a link to a video animation (H.264/MPEG-4 AVC video without sound) stored on the Telegram servers. By default, this animated MPEG-4 file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be mpeg4_gif
idStringUnique identifier for this result, 1-64 bytes
mpeg4_file_idStringA valid file identifier for the MP4 file
titleStringOptional. Title for the result
captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
+

InlineQueryResultCachedSticker

+

Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be sticker
idStringUnique identifier for this result, 1-64 bytes
sticker_file_idStringA valid file identifier of the sticker
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the sticker
+

Note: This will only work in Telegram versions released after 9 April, 2016 for static stickers and after 06 July, 2019 for animated stickers. Older clients will ignore them.

+

InlineQueryResultCachedDocument

+

Represents a link to a file stored on the Telegram servers. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be document
idStringUnique identifier for this result, 1-64 bytes
titleStringTitle for the result
document_file_idStringA valid file identifier for the file
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultCachedVideo

+

Represents a link to a video file stored on the Telegram servers. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be video
idStringUnique identifier for this result, 1-64 bytes
video_file_idStringA valid file identifier for the video file
titleStringTitle for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video
+

InlineQueryResultCachedVoice

+

Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be voice
idStringUnique identifier for this result, 1-64 bytes
voice_file_idStringA valid file identifier for the voice message
titleStringVoice message title
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice message
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InlineQueryResultCachedAudio

+

Represents a link to an MP3 audio file stored on the Telegram servers. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringType of the result, must be audio
idStringUnique identifier for this result, 1-64 bytes
audio_file_idStringA valid file identifier for the audio file
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
+

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

+

InputMessageContent

+

This object represents the content of a message to be sent as a result of an inline query. Telegram clients currently support the following 5 types:

+ +

InputTextMessageContent

+

Represents the content of a text message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
message_textStringText of the message to be sent, 1-4096 characters
parse_modeStringOptional. Mode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptional. List of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptional. Disables link previews for links in the sent message
+

InputLocationMessageContent

+

Represents the content of a location message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
latitudeFloatLatitude of the location in degrees
longitudeFloatLongitude of the location in degrees
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
+

InputVenueMessageContent

+

Represents the content of a venue message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
latitudeFloatLatitude of the venue in degrees
longitudeFloatLongitude of the venue in degrees
titleStringName of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue, if known
foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, "arts_entertainment/default", "arts_entertainment/aquarium" or "food/icecream".)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
+

InputContactMessageContent

+

Represents the content of a contact message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
+

InputInvoiceMessageContent

+

Represents the content of an invoice message to be sent as the result of an inline query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
titleStringProduct name, 1-32 characters
descriptionStringProduct description, 1-255 characters
payloadStringBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
provider_tokenStringPayment provider token, obtained via Botfather
currencyStringThree-letter ISO 4217 currency code, see more on currencies
pricesArray of LabeledPricePrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountIntegerOptional. The maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies). Defaults to 0
suggested_tip_amountsArray of IntegerOptional. A JSON-serialized array of suggested amounts of tip in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
provider_dataStringOptional. A JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
photo_urlStringOptional. URL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
photo_sizeIntegerOptional. Photo size
photo_widthIntegerOptional. Photo width
photo_heightIntegerOptional. Photo height
need_nameBooleanOptional. Pass True, if you require the user's full name to complete the order
need_phone_numberBooleanOptional. Pass True, if you require the user's phone number to complete the order
need_emailBooleanOptional. Pass True, if you require the user's email address to complete the order
need_shipping_addressBooleanOptional. Pass True, if you require the user's shipping address to complete the order
send_phone_number_to_providerBooleanOptional. Pass True, if user's phone number should be sent to provider
send_email_to_providerBooleanOptional. Pass True, if user's email address should be sent to provider
is_flexibleBooleanOptional. Pass True, if the final price depends on the shipping method
+

ChosenInlineResult

+

Represents a result of an inline query that was chosen by the user and sent to their chat partner.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
result_idStringThe unique identifier for the result that was chosen
fromUserThe user that chose the result
locationLocationOptional. Sender location, only for bots that require user location
inline_message_idStringOptional. Identifier of the sent inline message. Available only if there is an inline keyboard attached to the message. Will be also received in callback queries and can be used to edit the message.
queryStringThe query that was used to obtain the result
+

Note: It is necessary to enable inline feedback via @Botfather in order to receive these objects in updates.

+

Payments

+

Your bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot. Please note that users will need Telegram v.4.0 or higher to use payments (released on May 18, 2017).

+

sendInvoice

+

Use this method to send invoices. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
titleStringYesProduct name, 1-32 characters
descriptionStringYesProduct description, 1-255 characters
payloadStringYesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
provider_tokenStringYesPayments provider token, obtained via Botfather
currencyStringYesThree-letter ISO 4217 currency code, see more on currencies
pricesArray of LabeledPriceYesPrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountIntegerOptionalThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies). Defaults to 0
suggested_tip_amountsArray of IntegerOptionalA JSON-serialized array of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
start_parameterStringOptionalUnique deep-linking parameter. If left empty, forwarded copies of the sent message will have a Pay button, allowing multiple users to pay directly from the forwarded message, using the same invoice. If non-empty, forwarded copies of the sent message will have a URL button with a deep link to the bot (instead of a Pay button), with the value used as the start parameter
provider_dataStringOptionalA JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
photo_urlStringOptionalURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
photo_sizeIntegerOptionalPhoto size
photo_widthIntegerOptionalPhoto width
photo_heightIntegerOptionalPhoto height
need_nameBooleanOptionalPass True, if you require the user's full name to complete the order
need_phone_numberBooleanOptionalPass True, if you require the user's phone number to complete the order
need_emailBooleanOptionalPass True, if you require the user's email address to complete the order
need_shipping_addressBooleanOptionalPass True, if you require the user's shipping address to complete the order
send_phone_number_to_providerBooleanOptionalPass True, if user's phone number should be sent to provider
send_email_to_providerBooleanOptionalPass True, if user's email address should be sent to provider
is_flexibleBooleanOptionalPass True, if the final price depends on the shipping method
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Pay total price' button will be shown. If not empty, the first button must be a Pay button.
+

answerShippingQuery

+

If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the Bot API will send an Update with a shipping_query field to the bot. Use this method to reply to shipping queries. On success, True is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
shipping_query_idStringYesUnique identifier for the query to be answered
okBooleanYesSpecify True if delivery to the specified address is possible and False if there are any problems (for example, if delivery to the specified address is not possible)
shipping_optionsArray of ShippingOptionOptionalRequired if ok is True. A JSON-serialized array of available shipping options.
error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
+

answerPreCheckoutQuery

+

Once the user has confirmed their payment and shipping details, the Bot API sends the final confirmation in the form of an Update with the field pre_checkout_query. Use this method to respond to such pre-checkout queries. On success, True is returned. Note: The Bot API must receive an answer within 10 seconds after the pre-checkout query was sent.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
pre_checkout_query_idStringYesUnique identifier for the query to be answered
okBooleanYesSpecify True if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order. Use False if there are any problems.
error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
+

LabeledPrice

+

This object represents a portion of the price for goods or services.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
labelStringPortion label
amountIntegerPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Invoice

+

This object contains basic information about an invoice.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
titleStringProduct name
descriptionStringProduct description
start_parameterStringUnique bot deep-linking parameter that can be used to generate this invoice
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

ShippingAddress

+

This object represents a shipping address.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
country_codeStringISO 3166-1 alpha-2 country code
stateStringState, if applicable
cityStringCity
street_line1StringFirst line for the address
street_line2StringSecond line for the address
post_codeStringAddress post code
+

OrderInfo

+

This object represents information about an order.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
nameStringOptional. User name
phone_numberStringOptional. User's phone number
emailStringOptional. User email
shipping_addressShippingAddressOptional. User shipping address
+

ShippingOption

+

This object represents one shipping option.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringShipping option identifier
titleStringOption title
pricesArray of LabeledPriceList of price portions
+

SuccessfulPayment

+

This object contains basic information about a successful payment.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
invoice_payloadStringBot specified invoice payload
shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
order_infoOrderInfoOptional. Order info provided by the user
telegram_payment_charge_idStringTelegram payment identifier
provider_payment_charge_idStringProvider payment identifier
+

ShippingQuery

+

This object contains information about an incoming shipping query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique query identifier
fromUserUser who sent the query
invoice_payloadStringBot specified invoice payload
shipping_addressShippingAddressUser specified shipping address
+

PreCheckoutQuery

+

This object contains information about an incoming pre-checkout query.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
idStringUnique query identifier
fromUserUser who sent the query
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
invoice_payloadStringBot specified invoice payload
shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
order_infoOrderInfoOptional. Order info provided by the user
+

Telegram Passport

+

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Please see the manual for details.

+

PassportData

+

Contains information about Telegram Passport data shared with the bot by the user.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dataArray of EncryptedPassportElementArray with information about documents and other Telegram Passport elements that was shared with the bot
credentialsEncryptedCredentialsEncrypted credentials required to decrypt the data
+

PassportFile

+

This object represents a file uploaded to Telegram Passport. Currently all Telegram Passport files are in JPEG format when decrypted and don't exceed 10MB.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
file_sizeIntegerFile size in bytes
file_dateIntegerUnix time when the file was uploaded
+

EncryptedPassportElement

+

Contains information about documents or other Telegram Passport elements shared with the bot by the user.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringElement type. One of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration", "phone_number", "email".
dataStringOptional. Base64-encoded encrypted Telegram Passport element data provided by the user, available for "personal_details", "passport", "driver_license", "identity_card", "internal_passport" and "address" types. Can be decrypted and verified using the accompanying EncryptedCredentials.
phone_numberStringOptional. User's verified phone number, available only for "phone_number" type
emailStringOptional. User's verified email address, available only for "email" type
filesArray of PassportFileOptional. Array of encrypted files with documents provided by the user, available for "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
front_sidePassportFileOptional. Encrypted file with the front side of the document, provided by the user. Available for "passport", "driver_license", "identity_card" and "internal_passport". The file can be decrypted and verified using the accompanying EncryptedCredentials.
reverse_sidePassportFileOptional. Encrypted file with the reverse side of the document, provided by the user. Available for "driver_license" and "identity_card". The file can be decrypted and verified using the accompanying EncryptedCredentials.
selfiePassportFileOptional. Encrypted file with the selfie of the user holding a document, provided by the user; available for "passport", "driver_license", "identity_card" and "internal_passport". The file can be decrypted and verified using the accompanying EncryptedCredentials.
translationArray of PassportFileOptional. Array of encrypted files with translated versions of documents provided by the user. Available if requested for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
hashStringBase64-encoded element hash for using in PassportElementErrorUnspecified
+

EncryptedCredentials

+

Contains data required for decrypting and authenticating EncryptedPassportElement. See the Telegram Passport Documentation for a complete description of the data decryption and authentication processes.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dataStringBase64-encoded encrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication
hashStringBase64-encoded data hash for data authentication
secretStringBase64-encoded secret, encrypted with the bot's public RSA key, required for data decryption
+

setPassportDataErrors

+

Informs a user that some of the Telegram Passport elements they provided contains errors. The user will not be able to re-submit their Passport to you until the errors are fixed (the contents of the field for which you returned the error must change). Returns True on success.

+

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.

+ + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier
errorsArray of PassportElementErrorYesA JSON-serialized array describing the errors
+

PassportElementError

+

This object represents an error in the Telegram Passport element which was submitted that should be resolved by the user. It should be one of:

+ +

PassportElementErrorDataField

+

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be data
typeStringThe section of the user's Telegram Passport which has the error, one of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address"
field_nameStringName of the data field which has the error
data_hashStringBase64-encoded data hash
messageStringError message
+

PassportElementErrorFrontSide

+

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be front_side
typeStringThe section of the user's Telegram Passport which has the issue, one of "passport", "driver_license", "identity_card", "internal_passport"
file_hashStringBase64-encoded hash of the file with the front side of the document
messageStringError message
+

PassportElementErrorReverseSide

+

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be reverse_side
typeStringThe section of the user's Telegram Passport which has the issue, one of "driver_license", "identity_card"
file_hashStringBase64-encoded hash of the file with the reverse side of the document
messageStringError message
+

PassportElementErrorSelfie

+

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be selfie
typeStringThe section of the user's Telegram Passport which has the issue, one of "passport", "driver_license", "identity_card", "internal_passport"
file_hashStringBase64-encoded hash of the file with the selfie
messageStringError message
+

PassportElementErrorFile

+

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be file
typeStringThe section of the user's Telegram Passport which has the issue, one of "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration"
file_hashStringBase64-encoded file hash
messageStringError message
+

PassportElementErrorFiles

+

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be files
typeStringThe section of the user's Telegram Passport which has the issue, one of "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration"
file_hashesArray of StringList of base64-encoded file hashes
messageStringError message
+

PassportElementErrorTranslationFile

+

Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be translation_file
typeStringType of element of the user's Telegram Passport which has the issue, one of "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration"
file_hashStringBase64-encoded file hash
messageStringError message
+

PassportElementErrorTranslationFiles

+

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation change.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be translation_files
typeStringType of element of the user's Telegram Passport which has the issue, one of "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration"
file_hashesArray of StringList of base64-encoded file hashes
messageStringError message
+

PassportElementErrorUnspecified

+

Represents an issue in an unspecified place. The error is considered resolved when new data is added.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sourceStringError source, must be unspecified
typeStringType of element of the user's Telegram Passport which has the issue
element_hashStringBase64-encoded element hash
messageStringError message
+

Games

+

Your bot can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Create games via @BotFather using the /newgame command. Please note that this kind of power requires responsibility: you will need to accept the terms for each game that your bots will be offering.

+
    +
  • Games are a new type of content on Telegram, represented by the Game and InlineQueryResultGame objects.
  • +
  • Once you've created a game via BotFather, you can send games to chats as regular messages using the sendGame method, or use inline mode with InlineQueryResultGame.
  • +
  • If you send the game message without any buttons, it will automatically have a 'Play GameName' button. When this button is pressed, your bot gets a CallbackQuery with the game_short_name of the requested game. You provide the correct URL for this particular user and the app opens the game in the in-app browser.
  • +
  • You can manually add multiple buttons to your game message. Please note that the first button in the first row must always launch the game, using the field callback_game in InlineKeyboardButton. You can add extra buttons according to taste: e.g., for a description of the rules, or to open the game's official community.
  • +
  • To make your game more attractive, you can upload a GIF animation that demostrates the game to the users via BotFather (see Lumberjack for example).
  • +
  • A game message will also display high scores for the current chat. Use setGameScore to post high scores to the chat with the game, add the edit_message parameter to automatically update the message with the current scoreboard.
  • +
  • Use getGameHighScores to get data for in-game high score tables.
  • +
  • You can also add an extra sharing button for users to share their best score to different chats.
  • +
  • For examples of what can be done using this new stuff, check the @gamebot and @gamee bots.
  • +
+

sendGame

+

Use this method to send a game. On success, the sent Message is returned.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
chat_idIntegerYesUnique identifier for the target chat
game_short_nameStringYesShort name of the game, serves as the unique identifier for the game. Set up your games via Botfather.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Play game_title' button will be shown. If not empty, the first button must launch the game.
+

Game

+

This object represents a game. Use BotFather to create and edit games, their short names will act as unique identifiers.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
titleStringTitle of the game
descriptionStringDescription of the game
photoArray of PhotoSizePhoto that will be displayed in the game message in chats.
textStringOptional. Brief description of the game or high scores included in the game message. Can be automatically edited to include current high scores for the game when the bot calls setGameScore, or manually edited using editMessageText. 0-4096 characters.
text_entitiesArray of MessageEntityOptional. Special entities that appear in text, such as usernames, URLs, bot commands, etc.
animationAnimationOptional. Animation that will be displayed in the game message in chats. Upload via BotFather
+

CallbackGame

+

A placeholder, currently holds no information. Use BotFather to set up your game.

+

setGameScore

+

Use this method to set the score of the specified user in a game message. On success, if the message is not an inline message, the Message is returned, otherwise True is returned. Returns an error, if the new score is not greater than the user's current score in the chat and force is False.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier
scoreIntegerYesNew score, must be non-negative
forceBooleanOptionalPass True, if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
disable_edit_messageBooleanOptionalPass True, if the game message should not be automatically edited to include the current scoreboard
chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
+

getGameHighScores

+

Use this method to get data for high score tables. Will return the score of the specified user and several of their neighbors in a game. On success, returns an Array of GameHighScore objects.

+
+

This method will currently return scores for the target user, plus two of their closest neighbors on each side. Will also return the top three users if the user and his neighbors are not among them. Please note that this behavior is subject to change.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeRequiredDescription
user_idIntegerYesTarget user id
chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
+

GameHighScore

+

This object represents one row of the high scores table for a game.

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
positionIntegerPosition in high score table for the game
userUserUser
scoreIntegerScore
+
+

And that's about all we've got for now. +If you've got any questions, please check out our Bot FAQ »

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/bots/faq.html b/data/corefork.telegram.org/bots/faq.html new file mode 100644 index 0000000000..dce13598de --- /dev/null +++ b/data/corefork.telegram.org/bots/faq.html @@ -0,0 +1,243 @@ + + + + + Bots FAQ + + + + + + + + + + + + + +
+ +
+
+
+ +

Bots FAQ

+ +
+

If you are new to Telegram bots, we recommend checking out our Introduction to Bots first.
You may also find the Bot API Manual useful.

+
+

+ +
+

General Questions

+

How do I create a bot?

+

Creating Telegram bots is super-easy, but you will need at least some skills at computer programming. In order for a bot to work, set up a bot account with @BotFather, then connect it to your backend server via our API.

+

Unfortunately, there are no out-of-the-box ways to create a working bot if you are not a developer. But we're sure you'll soon find plenty of bots created by other people to play with.

+

I'm a developer. Where can I find some examples?

+

Here are two sample bots, both written in PHP:

+
    +
  • Hello Bot demonstrates the basics of the Telegram bot API.
  • +
  • Simple Poll bot is a more complete example, it supports both long-polling and Webhooks for updates.
  • +
+
+

Many members of our community are building bots and publishing sources.
We're collecting them on this page »

+
+

Ping us on @BotSupport if you've built a bot and would like to share it with others.

+

Will you add X to the Bot API?

+

The bot API is still pretty young. There are many potential features to consider and implement. We'll be studying what people do with their bots for a while to see which directions will be most important for the platform.

+

All bot developers are welcome to share ideas for our Bot API with our @BotSupport account.

+

What messages will my bot get?

+

1. All bots, regardless of settings, will receive:

+
    +
  • All service messages.
  • +
  • All messages from private chats with users.
  • +
  • All messages from channels where they are a member.
  • +
+

2. Bot admins and bots with privacy mode disabled will receive all messages except messages sent by other bots.

+

3. Bots with privacy mode enabled will receive:

+
    +
  • Commands explicitly meant for them (e.g., /command@this_bot).
  • +
  • General commands from users (e.g. /start) if the bot was the last bot to send a message to the group.
  • +
  • Messages sent via this bot.
  • +
  • Replies to any messages implicitly or explicitly meant for this bot.
  • +
+

Note that each particular message can only be available to one privacy-enabled bot at a time, i.e., a reply to bot A containing an explicit command for bot B or sent via bot C will only be available to bot A. Replies have the highest priority.

+

Why doesn't my bot see messages from other bots?

+

Bots talking to each other could potentially get stuck in unwelcome loops. To avoid this, we decided that bots will not be able to see messages from other bots regardless of mode.

+

Getting Updates

+

How do I get updates?

+

There are currently two ways of getting updates. You can either use long polling or Webhooks. Please note that it's not possible to get updates via long polling while an outgoing Webhook is set.

+

Long polling gives me the same updates again and again!

+

The getUpdates method returns the earliest 100 unconfirmed updates. To confirm an update, use the offset parameter when calling getUpdates like this:

+
offset = update_id of last processed update + 1
+

All updates with update_id less than or equal to offset will be marked as confirmed on the server and will no longer be returned.

+

I'm having problems with Webhooks.

+

If you've set up your webhook successfully, but are not getting any updates, please remember:

+
    +
  • You need a valid SSL certificate for webhooks to work.
  • +
  • To use a self-signed certificate, you need to upload your public key certificate using the certificate parameter in setWebhook. Please upload as InputFile, sending a String will not work.
  • +
  • Ports currently supported for Webhooks: 443, 80, 88, 8443.
  • +
  • Wildcard certificates may not be supported.
  • +
  • Redirects are not supported.
  • +
  • CN must exactly match your domain.
  • +
+
+

Please check out this new WEBHOOK GUIDE to learn all there is to know about webhooks!

+
+

I'm having trouble with my self-signed certificate!

+

Please take a look at this self-signed certificate guide we made just for you. If you've read it and still have a question, ping us on botsupport.

+

How can I make sure that Webhook requests are coming from Telegram?

+

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL you give us, e.g. www.example.com/your_token. Since nobody else knows your bot's token, you can be pretty sure it's us.

+

How can I make requests in response to updates?

+

This is possible if you're using webhooks. The upside is that you need less requests, the downside — that in this case it's not possible to know that such a request was successful or get its result.

+

Whenever you receive a webhook update, you have two options:

+

1. Issue POST to https://api.telegram.org/bot<token>/method

+
+ +
+ +

2. Reply directly and give method as JSON payload in the reply

+
+
+ +
+

You may also want to look at our sample HelloBot, it offers a PHP implementation of this.

+
+

Handling Media

+

How do I download files?

+

Use the getFile method. Please note that this will only work with files of up to 20 MB in size.

+

How do I upload a large file?

+

Bots can currently send files of any type of up to 50 MB in size, so yes, very large files won't work for now. Sorry. This limit may be changed in the future.

+

Can I count on file_ids to be persistent?

+

Yes, file_ids can be treated as persistent.

+

Broadcasting to Users

+

My bot is hitting limits, how do I avoid this?

+

When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.

+

If you're sending bulk notifications to multiple users, the API will not allow more than 30 messages per second or so. Consider spreading out notifications over large intervals of 8—12 hours for best results.

+

Also note that your bot will not be able to send more than 20 messages per minute to the same group.

+

How can I message all of my bot's subscribers at once?

+

Unfortunately, at this moment we don't have methods for sending bulk messages, e.g. notifications. We may add something along these lines in the future.

+

In order to avoid hitting our limits when sending out mass notifications, consider spreading them over longer intervals, e.g. 8-12 hours. The API will not allow bulk notifications to more than ~30 users per second, if you go over that, you'll start getting 429 errors.

+

See also: How to avoid hitting limits?

+
+
+

If you've got questions that are not answered on this page, ping us at @BotSupport in Telegram.
We welcome any suggestions for the Bot Platform and API.

+
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/bots/games.html b/data/corefork.telegram.org/bots/games.html new file mode 100644 index 0000000000..1767c2c160 --- /dev/null +++ b/data/corefork.telegram.org/bots/games.html @@ -0,0 +1,185 @@ + + + + + Gaming Platform + + + + + + + + + + + + + +
+ +
+
+
+ +

Gaming Platform

+ +
+ +
+ +
+ +

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Games are a new type of content on Telegram that your bot can send to users.

+
+

+
+ +
+

This introduction is meant for bot developers. Click here, in case you'd like something more user-friendly.
Check out the @gamebot and @gamee bots for examples of what you can do using the new Gaming Platform.

+
+

Creating a Game

+

To get started, send the /newgame command to @BotFather.You will be prompted for a description text and a photo. You can also upload an optional GIF animation that demostrates your game to the users to make messages with the game more attractive (check out Lumberjack or Corsairs for examples).

+

Launching the Game

+

Once the game is created, your bot can send it to chats as regular messages, or offer them via inline mode. The game message will always have an inline Play button.

+

When this button is pressed, your bot gets a callback query that indicates the requested game. You provide the correct URL for this particular user and the app automatically opens the game in the in-app browser.

+

Adding Buttons

+

If you send the game message without any buttons, it will automatically have a 'Play GameName' button. You can manually add multiple buttons to your game message. Please note that the first button in the first row must always be the one that launches the game. You can add more buttons: e.g., for a description of the rules, or a button that links to the game's official community.

+

Tracking High Scores

+

The message with your game will also display high scores for the current chat. When a new high score is set, a service message will be sent to the chat and the message with the current scoreboard will be updated. You can also request the necessary data for building in-game high score tables.

+
+
+ +

+ +

+ +

Sharing Your Game to Telegram Chats

+

There are many way for users to spread your game virally if they like it. The interface will always have the standard system button for sharing the game in the top right corner:

+
+ + +

+ +
+ + + +

You can also create an additional Share button inside your HTML page. Pressing this button will send the game to a desired chat along with the user's best score in the game.

+
+ + + + + +

+ + +

To add the sharing button, include this script at the end of the <body> tag on your page:

+
<script src="https://telegram.org/js/games.js"></script>
+

Then use the method TelegramGameProxy.shareScore() to call the sharing option.

+
+

Warning: Do not call this method without consent and direct action from the user.

+
+

Example:

+
<button onclick="TelegramGameProxy.shareScore()">Share score</button>
+

This library will only work when launched from inside Telegram, so please don't use it on ordinary web pages.

+

Using URL Parameters

+

If your URL is using a fragment identifier, please note that Telegram Apps could add certain service parameters to the fragment id. The names for such parameters will start in tg (you can check the code that adds them here). Use the TelegramGameProxy.initParams object if you need to read your own parameters from the fragment id.

+

Creating a Great HTML5 Experience

+

Please make sure that your HTML5 page is responsive and works well on all Telegram apps and supported platforms. If you find it impossible to support certain conditions or platforms, don't leave your users hanging and at least provide a notification.

+
+

See the Bot API Manual for the relevant methods and objects.

+
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/bots/inline.html b/data/corefork.telegram.org/bots/inline.html new file mode 100644 index 0000000000..1ff0aeee96 --- /dev/null +++ b/data/corefork.telegram.org/bots/inline.html @@ -0,0 +1,181 @@ + + + + + Inline Bots + + + + + + + + + + + + + +
+ +
+
+
+ +

Inline Bots

+ +
+ +
+ +
+

Beyond sending commands in private messages or groups, users can interact with your bot via inline queries. If inline queries are enabled, users can call your bot by typing its username and a query in the text input field in any chat. The query is sent to your bot in an update. This way, people can request content from your bot in any of their chats, groups, or channels without sending any messages at all.

+
+
+
+

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot’s name.

+
+

See the Bot API Manual for the relevant methods and objects.

+
+

Inline results

+

Inline bots support all types of content available in Telegram (20 in all). They are capable of sending stickers, videos, music, locations, documents and more.

+
+

+
+

Clients can display the results with vertical or horizontal scrolling, depending on the type of content:

+
+
<a href="/file/811140049/2/M2mzqjZoiUw/2d872f0df2aed182d6" target="_blank"><img src="/file/811140049/2/M2mzqjZoiUw/2d872f0df2aed182d6" title="Vertical scrolling"  style="width: 295px; padding: 0px 20px;" /></a>
+

+
+
+

As soon as the user taps on an item, it's immediately sent to the recipient, and the input field is cleared.

+

Switching inline/PM modes

+

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

+
+

+
+

You can display a special 'Switch to PM' button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

+

Sample bots +@youtube – Shows a 'Sign in to YouTube' button, then suggests personalized results.

+
+

Manual: Switch to PM

+
+

Location-based results

+

Inline bots can request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

+

Sample bot +@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

+

Spreading virally

+

Messages sent with the help of your bot will show its username next to the sender's name.

+
+
<a href="/file/811140680/2/P3E5RVFzGZ8/5ae6f9c9610b0cbace" target="_blank"><img src="/file/811140680/2/P3E5RVFzGZ8/5ae6f9c9610b0cbace" title="Gif shared via a bot" style="width: 295px; padding: 0px 20px;" /></a>
+

+



+

When a user taps on the bot username in the message header, the mention is automatically inserted into the input field. Entering the @ symbol in the input field brings up a list of suggestions, featuring recently used inline bots.

+

Collecting feedback

+

To know which of the provided results your users are sending to their chat partners, send @Botfather the /setinlinefeedback command. With this enabled, you will receive updates on the results chosen by your users.

+

Please note that this can create load issues for popular bots – you may receive more results than actual requests due to caching (see the cache_time parameter in answerInlineQuery). For these cases, we recommend adjusting the probability setting to receive 1/10, 1/100 or 1/1000 of the results.

+

Inline bot samples

+

Here are some sample inline bots, in case you’re curious to see one in action. Try any of these: +@gif – GIF search +@vid – Video search +@pic – Yandex image search +@bing – Bing image search +@wiki – Wikipedia search +@imdb – IMDB search +@bold – Make bold, italic or fixed sys text

+

NEW +@youtube - Connect your account for personalized results +@music - Search and send classical music +@foursquare – Find and send venue addresses +@sticker – Find and send stickers based on emoji

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/bots/samples.html b/data/corefork.telegram.org/bots/samples.html new file mode 100644 index 0000000000..dda0121b96 --- /dev/null +++ b/data/corefork.telegram.org/bots/samples.html @@ -0,0 +1,249 @@ + + + + + Bot Code Examples + + + + + + + + + + + + + +
+ +
+
+
+ +

Bot Code Examples

+ +
+

If you want to learn more about Telegram bots, start with our Introduction to Bots »
Check out the FAQ, if you have questions.

+
+

Many members of our community are building bots and libraries and publishing their source code. We collect these examples here. Ping us on BotSupport if you've built a bot and would like to share its code with others.

+

PHP

+ +

Node.js

+ +

Rust

+ +

Python

+ +

Ruby

+ +

Swift

+ +

Kotlin

+ +

Java

+ +

Go

+ +

Other Languages

+ +
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/bots/samples/hellobot.html b/data/corefork.telegram.org/bots/samples/hellobot.html new file mode 100644 index 0000000000..5ad7bd1cf8 --- /dev/null +++ b/data/corefork.telegram.org/bots/samples/hellobot.html @@ -0,0 +1,287 @@ + + + + + Hellobot + + + + + + + + + + + + + +
+ +
+
+
+ +

Hellobot

+ +
+

This sample PHP bot demonstrates the basics of the Telegram Bot API.
If you have questions, try our FAQ or check out this page for more examples.

+
+

+ +
<?php
+
+define('BOT_TOKEN', '12345678:replace-me-with-real-token');
+define('API_URL', 'https://api.telegram.org/bot'.BOT_TOKEN.'/');
+
+function apiRequestWebhook($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  $parameters["method"] = $method;
+
+  $payload = json_encode($parameters);
+  header('Content-Type: application/json');
+  header('Content-Length: '.strlen($payload));
+  echo $payload;
+
+  return true;
+}
+
+function exec_curl_request($handle) {
+  $response = curl_exec($handle);
+
+  if ($response === false) {
+    $errno = curl_errno($handle);
+    $error = curl_error($handle);
+    error_log("Curl returned error $errno: $error\n");
+    curl_close($handle);
+    return false;
+  }
+
+  $http_code = intval(curl_getinfo($handle, CURLINFO_HTTP_CODE));
+  curl_close($handle);
+
+  if ($http_code >= 500) {
+    // do not wat to DDOS server if something goes wrong
+    sleep(10);
+    return false;
+  } else if ($http_code != 200) {
+    $response = json_decode($response, true);
+    error_log("Request has failed with error {$response['error_code']}: {$response['description']}\n");
+    if ($http_code == 401) {
+      throw new Exception('Invalid access token provided');
+    }
+    return false;
+  } else {
+    $response = json_decode($response, true);
+    if (isset($response['description'])) {
+      error_log("Request was successful: {$response['description']}\n");
+    }
+    $response = $response['result'];
+  }
+
+  return $response;
+}
+
+function apiRequest($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  foreach ($parameters as $key => &$val) {
+    // encoding to JSON array parameters, for example reply_markup
+    if (!is_numeric($val) && !is_string($val)) {
+      $val = json_encode($val);
+    }
+  }
+  $url = API_URL.$method.'?'.http_build_query($parameters);
+
+  $handle = curl_init($url);
+  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
+  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
+  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
+
+  return exec_curl_request($handle);
+}
+
+function apiRequestJson($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  $parameters["method"] = $method;
+
+  $handle = curl_init(API_URL);
+  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
+  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
+  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
+  curl_setopt($handle, CURLOPT_POST, true);
+  curl_setopt($handle, CURLOPT_POSTFIELDS, json_encode($parameters));
+  curl_setopt($handle, CURLOPT_HTTPHEADER, array("Content-Type: application/json"));
+
+  return exec_curl_request($handle);
+}
+
+function processMessage($message) {
+  // process incoming message
+  $message_id = $message['message_id'];
+  $chat_id = $message['chat']['id'];
+  if (isset($message['text'])) {
+    // incoming text message
+    $text = $message['text'];
+
+    if (strpos($text, "/start") === 0) {
+      apiRequestJson("sendMessage", array('chat_id' => $chat_id, "text" => 'Hello', 'reply_markup' => array(
+        'keyboard' => array(array('Hello', 'Hi')),
+        'one_time_keyboard' => true,
+        'resize_keyboard' => true)));
+    } else if ($text === "Hello" || $text === "Hi") {
+      apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'Nice to meet you'));
+    } else if (strpos($text, "/stop") === 0) {
+      // stop now
+    } else {
+      apiRequestWebhook("sendMessage", array('chat_id' => $chat_id, "reply_to_message_id" => $message_id, "text" => 'Cool'));
+    }
+  } else {
+    apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'I understand only text messages'));
+  }
+}
+
+
+define('WEBHOOK_URL', 'https://my-site.example.com/secret-path-for-webhooks/');
+
+if (php_sapi_name() == 'cli') {
+  // if run from console, set or delete webhook
+  apiRequest('setWebhook', array('url' => isset($argv[1]) && $argv[1] == 'delete' ? '' : WEBHOOK_URL));
+  exit;
+}
+
+
+$content = file_get_contents("php://input");
+$update = json_decode($content, true);
+
+if (!$update) {
+  // receive wrong update, must not happen
+  exit;
+}
+
+if (isset($update["message"])) {
+  processMessage($update["message"]);
+}
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/bots/self-signed.html b/data/corefork.telegram.org/bots/self-signed.html new file mode 100644 index 0000000000..f52296c4f2 --- /dev/null +++ b/data/corefork.telegram.org/bots/self-signed.html @@ -0,0 +1,161 @@ + + + + + Using self-signed certificates + + + + + + + + + + + + + +
+ +
+
+
+ +

Using self-signed certificates

+ +

Upload your certificate using the certificate parameter in the setWebhook method. The certificate supplied should be PEM encoded (ASCII BASE64), the pem file should only contain the public key (including BEGIN and END portions). When converting from a bundle format, please split the file to only include the public key.

+

Generating a self-signed certificate pair (PEM):

+

Openssl

+
+

Windows binaries for Openssl are available online

+
+

openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"

+

YOURPUBLIC.pem has to be used as input for setting the self-signed webhook.

+

You can inspect the generated certificate with:
openssl x509 -text -noout -in YOURPUBLIC.pem

+

Converting from a previously generated DER:
openssl x509 -inform der -in YOURDER.der -out YOURPEM.pem

+

Converting from a previously generated PKCS12:
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

+
+

More information: https://www.openssl.org/

+
+

Java keystore

+

Generate self-signed JKS:
keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

+

Converting JKS to pkcs12 (intermediate step for conversion to PEM):
keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

+

Convert PKCS12 to PEM (requires openssl):
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

+
+

More information: https://docs.oracle.com

+
+

Windows

+

Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.

+

On the commandline:
certreq -new TEMPLATE.txt RequestFileOut

+

TEMPLATE.txt example file:

+
[NewRequest]
+
+; At least one value must be set in this section
+Subject = "CN=DOMAIN.EXAMPLE"
+KeyLength = 2048
+KeyAlgorithm = RSA
+HashAlgorithm = sha256
+;MachineKeySet = true
+RequestType = Cert
+UseExistingKeySet=false ;generates a new private key (for export)
+Exportable = true ;makes the private key exportable with the PFX
+

A self-signed certificate will be generated and installed, to view the certificate:
certutil -store -user my

+

To export in DER format (intermediate step for conversion to PEM)
certutil -user -store -split my SERIALNUMBER YOURDER.crt

+

Converting to PEM (used for setting the webhook)
certutil -encode YOURDER.crt YOURPEM.cer

+

To delete a certificate from your store:
certutil -delstore -user my SERIALNUMBER (from view)

+

To export in PFX(PKCS12) format
certutil -exportpfx -user YOURDOMAIN.EXAMPLE YOURPKCS.pfx NoChain

+
+

More information: https://technet.microsoft.com

+
+

Converting YOURPKCS.pfx to PEM including the private key is best done with OpenSSL:
openssl pkcs12 -in YOURPKCS.pfx -out YOURPEM.cer

+

Remember that only the public key is needed as input for the self-signed webhook certificate parameter. certmgr.msc can also be used as a GUI to export the public part of self-signed certificates to PEM.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/bots/webhooks.html b/data/corefork.telegram.org/bots/webhooks.html new file mode 100644 index 0000000000..1aa78ec5c3 --- /dev/null +++ b/data/corefork.telegram.org/bots/webhooks.html @@ -0,0 +1,827 @@ + + + + + Marvin's Marvellous Guide to All Things Webhook + + + + + + + + + + + + + +
+ +
+
+
+ +

Marvin's Marvellous Guide to All Things Webhook

+ +
+ +

We currently support two ways of processing bot updates, getUpdates and setWebhook. getUpdates is a pull mechanism, setwebhook is push. Although the concept of a webhook is fairly simple, the setup of the individual components has proven to be tricky for many. This guide provides some extra information for those of you brave enough to venture into the art of the webhook.

+

There are some advantages of using a webhook over getUpdates. As soon as an update arrives, we’ll kindly deliver it to your bot for processing.

+

This:

+
1. Avoids your bot having to ask for updates frequently.
+2. Avoids the need for some kind of polling mechanism in your code.
+

Other advantages may include saving some potential CPU cycles and an increase in response time, these things however depend heavily on the usage pattern of your bot.

+

Setting a webhook means you supplying Telegram with a location in the form of a URL, on which your bot listens for updates. We need to be able to connect and post updates to that URL.

+

To ensure that we can do that, there are some basic requirements:

+

The short version

+

You'll need a server that:

+
    +
  • Supports IPv4, IPv6 is currently not supported for webhooks.
  • +
  • Accepts incoming POSTs from subnets 149.154.160.0/20 and 91.108.4.0/22 on port 443, 80, 88, or 8443.
  • +
  • Is able to handle TLS1.2(+) HTTPS-traffic.
  • +
  • Provides a supported, verified or self-signed certificate.
  • +
  • Uses a CN or SAN that matches the domain you’ve supplied on setup.
  • +
  • Supplies all intermediate certificates to complete a verification chain.
  • +
+

That’s almost all there’s to it.
If you decide to limit traffic to our specific range of addresses, keep an eye on this document whenever you seem to run into trouble. Our IP-range might change in the future.

+

The longer version

+
    +
  • A domain name

    +

    Setting a webhook needs a URL for us to post to. For that you'll need a server with a domain name. If you don't have one, you'll need to obtain one first. Telegram currently doesn't offer hosting or domain name services. There are quite a few VPS/Web hosting providers around the internet, feel free to pick one to your liking.
    If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    How do I get a server with a domain name?

    +
  • +
  • An open port

    +

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    +
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
    +Whenever something stops working in the future, please check this document again as 
    +the range might expand or change.
    +

    How do I check for open ports or limit access to my bot?

    +
  • +
  • Always SSL/TLS

    +

    A webhook requires SSL/TLS encryption, no matter which port is used. It's not possible to use a plain-text HTTP webhook. You shouldn't want to either, for the sake of your bot and users.
    SSL/TLS, why do I have to handle this for a webhook?

    +
  • +
  • Not all SSL/TLS is equal

    +

    We support any SSL/TLS version TLS1.2 and up for your webhook. This means that SSLV2/3/TLS1.0/TSL1.1 are NOT supported, due to security issues associated with those older versions.
    How do I check that I’m handling the right version?

    +
  • +
  • SSL needs a certificate

    +

    The common name (CN) of your certificate (self-signed or verified) has to match the domain name where your bot is hosted. You may also use a subject alternative name (SAN), that matches the domain for your webhook. Server Name Indication (SNI)-routing is supported. If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    A certificate, where do I get one, and how?

    +
  • +
  • Verified or self-signed

    +

    A certificate can either be verified or self-signed. Setting a webhook with a self-signed certificate differs a little from setting a webhook with a verified certificate. Ensure you're using the correct setup for the type of certificate you've chosen for your webhook.
    How do I set a webhook for either type?

    +
  • +
  • Supported certificates

    +

    Not all verified certificates are supported. Certificates are based on a network of trust and come in a chain. Trusting your verified certificate means we have to trust the provider of that certificate, the Certificate Authority (and hence its root certificate). Before you pick a certificate provider, Check this list to make sure that we actually trust their root certificate.
    What if my root certificate isn’t on that list?

    +
  • +
  • An Untrusted root

    +

    Ok, so you already had a certificate installed and just discovered it’s not on our list.
    Start by ignoring it, and just try to set it. We occasionally add extra root certificates to keep up with popular demand, so the list isn't always exhaustive. Unlucky after all? We'll allow you to supply an unsupported root certificate when setting the webhook. This method is nearly identical to setting a self-signed certificate webhook. Instead of your self-signed certificate you'll be sending us the root certificate as inputFile.
    Setting a verified webhook with an untrusted root

    +
  • +
  • Intermediate certificates

    +

    Some verified certificates require an intermediate certificate. In this construction the provider of your verified certificate has used their root certificate to sign an intermediate certificate. This intermediate certificate is then used to sign your verified certificate. You'll need to provide the intermediate certificate for us to be able to verify the chain of trust. CA's that use this type of chain supply an intermediate certificate.
    Supplying an intermediate certificate

    +
  • +
  • More information

    +

    Since we know webhooks can be a tad overwhelming, we’re working on a little digital assistant that’ll try and help you with the most common problems, it's not nearly perfect, but you may try using @CanOfWormsBot to check if your chain of certificates is installed correctly before contacting support.

    +
  • +
  • Testing your bot

    +

    We took the liberty of adding a set of example updates. They come in handy when testing your bot, no matter which method of getting updates you might be using.

    +
  • +
  • Don't panic.

    +

    If by now you're looking for your fishing gear because we've mentioned ports and hooks or you're about to Google what kind of bait URL and TLS exactly are, this guide might not be completely for you. You’re quite likely still a brilliant bot programmer, don’t worry. Perhaps this whole webhook thing is just new to you, not all is lost. If you currently have a working getUpdates situation, it's a good idea to pick up this guide again on a rainy Sunday afternoon and take your time to read up on some subjects around the internet. This guide can only contain a finite amount of information after all.

    +
  • +
+

The verbose version

+
How do I get a server with a domain name?
+

If you use a webhook, we have to deliver requests to your bot to a server we can reach. So yes, you need a server we can connect to. It can be anywhere in the galaxy, if you ensure we can reach the server by domain name (or at least via IP for a self-signed certificate), it will work just fine.

+

There are quite a few ways to get this done, as a novice however it's likely that you're not directly jumping at the chance of crafting this from scratch. Actually, as a novice, we recommend you don't. It's likely to be a complex and long ride.

+

If you got stuck here, make a choice:

+
    +
  • You use getUpdates at the moment and it works, keep it that way. Especially if you're running your bot from a nice machine that does well. There is nothing wrong with using getUpdates.

    +
  • +
  • Go with a hosted service and let a bunch of professionals worry about things like registering a domain, setting up DNS, a web server, securing it and so on.

    +
  • +
+
If you're going with a hosted service, make sure to look for a hosting provider that 
+not only supports your code’s needs, for example: support for your PHP version,
+but one that also handles SSL and allows you to create/deploy certificates.
+
    +
  • Go crazy, dive on the internet and start reading. Once you’re confident that you’ve got all the basic theories down, find yourself a nice hosted VPS or roll your own machine at home and get back to us here.
  • +
+
How do I check for open ports or limit access to my bot?
+

So you have the hosting thing down and all is good so far, however, when you enter the address of your bot in your browser it seems unreachable.

+

Explaining every firewall or web server solution in detail isn't possible for us, which we hope you understand. If you’re running a hosted solution, you’re more likely to have a nice UI where you configure these settings. Head to your configuration panel and check all of them. If you’re on a Linux based VPS with shell access, we have some tips for you:

+
    +
  • Make sure your bot process is indeed configured to listen on the port you're using.
    netstat –ln | grep portnumber
    Shows you if your bot is actually listening for incoming requests on the port you expect.
    sudo lsof -i | grep process name
    Is a simple way to check if that’s actually being listened on by the process your bot is using.
  • +
+
    +
  • Make sure it’s listening correctly.
    Your bot has to listen on the address you’ve exposed to the outside (your public IP), it can also listen on all addresses (*: or 0.0.0.0).
    The netstat and lsof-commands mentioned above assist in checking this. If nothing shows up, it is time to check your configuration and fix it. Set the correct IP, make sure it’s listening on a supported port and fire away! Just use a Web Browser to check if you’re reachable. The problem can be in the configuration of your bot, your web server virtual host configuration, or the servers binding configuration.
  • +
+
    +
  • If you still can’t reach your address, check your firewall.
    sudo iptables –L
    OR
    sudo ufw status verbose (Ubuntu)
    Gives you some insight in the current firewall settings.

    +
  • +
  • If it looks like you’re blocking incoming traffic, let’s fix that.
    sudo iptables –A INPUT –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow portnumber/tcp
    Allows incoming traffic on all interfaces to the specified tcp port.
    sudo iptables –A INPUT –i interfacename –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp
    Allows incoming traffic to a specific interface and a specific port from everywhere.
    sudo ifconfig
    Helps you find the interface with the public address you’re going to use.

    +
  • +
+
If you use iptables, make sure to actually SAVE after changing the configuration.
+On a Debian based system the iptables-persistent package is be a good option.
+RHEL/CentOS offers a service iptables save -command.
+A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.
+
    +
  • If you’re just looking for some hints on how to limit incoming traffic:
    sudo iptables –A INPUT –i interfacename –p tcp –m iprange –src-range 149.154.167.197-149.154.167.233 –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp from 149.154.167.192/26
    Allows incoming traffic to a specific interface and a specific port from a specific range of addresses. (ufw is using a subnet mask in the example, ranging from 192-255)
  • +
+

That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

+
SSL/TLS, what is it and why do I have to handle this for a webhook?
+

You’re already familiar with it in some form or another. Whenever you see that (nicely green) lock in your browser bar, you know it’s reasonably safe to assume that you’ve landed on the site you actually wanted to visit. If you see the green lock, that's SSL/TLS in action. If you want to learn more about how SSL/TLS works in general, it's best to search the internet.

+

The main difference between getUpdates and a webhook is the way the connection takes place. getUpdates means you'll connect to our server, a webhook means we'll be connecting to your server instead. Connecting to your server has to be done secure, we have to know for sure it's you we're talking to after all. This means you'll have to handle all that server side encryption stuff, virtually presenting us with a green lock. If you use a web server for us to post to, you need to support SSL/TLS handling on the port/virtual host of your choice. An online search for “YOURWEBSERVER enable HTTPS” will help you.

+

Not using a regular web server? Have a look at our example page, most examples there include code for handling SSL/TLS in a webhook setup.

+
How do I check that I’m handling the right version?
+

You just read up on the whole SSL/TLS stuff, figured out that it’s not all that bad to setup and we add some more requirements. Here are some tips to check if you’re indeed supporting at least TLS1.2.

+
    +
  • Several online services exist that allow you to check your certificate installation,
    They give you an overview of your supported TLS versions/Cipher suites and other details. Search online for Symantec crypto report or Qualys ssl. Both supply tools to verify your setup.

    +
  • +
  • Checking locally can also be done, in several ways, here are three options,

    +
      +
    • Go simple:
      Using Chrome as a browser? Open up the URL to your bot and inspect the certificate details. If you’re supporting TLS Chrome tells you so in the security overview tab. Other browsers are likely able to give you similar basic information.

      +
    • +
    • Using curl:
      curl --tlsv1.2 -v -k https://yourbotdomain:yourbotport/
      You can add --tlsv1.2 to force curl into using TLS1.2 when trying to connect. -k is optional and used to check against a self-signed certificate. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using.

      +
    • +
    • Using OpenSSL
      openssl s_client -tls1_2 -connect yourbotdomain:yourbotport -servername yourbotdomain
      You can add -tls1_2 to force OpenSSL into using TLS1.2 when trying to connect. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using. Note that https:// isn’t used for OpenSSL. -servername is optional, and included here for some shared hosters, which use SNI to route traffic to the correct domain. When SNI is used you’ll notice that your server appears to be returning a certificate for a different domain than your own. Adding -servername yourbotdomain ensures that SNI negotiation is done, and the correct certificate is returned.

      +
    • +
    +
  • +
  • Some additional configuration pointers

    +
      +
    • Forcing TLS in your virtual host on Apache:
      SSLProtocol -all +TLSv1.2
    • +
    • Forcing TLS in your virtual host on Nginx:
      ssl_protocols TLSv1.2;
    • +
    • Force TLS for your Java virtual machine through system properties:
      -Dhttps.protocols=TLSv1.2 -Djdk.tls.client.protocols=TLSv1.2
    • +
    • Enabling ssl debug for your JVM:
      -Djavax.net.debug=ssl,handshake,record
    • +
    +
  • +
  • Other tools that may help in debugging issues:

    +
      +
    • Wireshark: excellent packet capturing
    • +
    • Tcpdump: equally excellent and doesn’t need a GUI
    • +
    • Charles: web debugging proxy
    • +
    • Fiddler: web debugging proxy
    • +
    +
  • +
+
A certificate, where do I get one and how?
+

You need a certificate, pick on of these types;

+
    +
  • A verified, supported certificate
  • +
  • A self-signed certificate

    +
  • +
  • A verified, supported certificate
    +

    Using a verified certificate means you already have, or will obtain, a certificate backed by a trusted certificate authority (CA). There are many ways to acquire a verified certificate, paid or free. Two popular examples of free suppliers are StartSSL and Let’s Encrypt. You’re welcome to pick another. Just make sure first the supplier is likely to be supported.
    Check this list before selecting a CA.
    Once you’ve picked a CA and validated your identity with them, you can craft your certificate. This frequently starts by generating a CSR (Certificate Signing Request). Generating a CSR is done either through your host machine, or online via the tools provided by the CA.

    +
  • +
  • Here is an example (PEM format output).

    +
      +
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -keyout yourprivatekey.key -out yoursigningrequest.csr
    • +
    +
  • +
+
----
+Generating a 2048 bit RSA private keywriting new private key to yourprivatekey.key
+Enter PEM pass phrase: enter a password for your key here 
+Verifying - Enter PEM pass phrase: confirm the entered password
+-----
+You are about to be asked to enter information that will be incorporated
+into your certificate request.
+What you are about to enter is what is called a Distinguished Name or a DN.
+There are quite a few fields but you can leave some blank
+For some fields there will be a default value,If you enter '.',
+the field will be left blank.-----
+Country Name (2 letter code) [AU]:
+State or Province Name (full name) [Some-State]:
+Locality Name (eg, city) []:
+Organization Name (eg, company) [Internet Widgits Pty Ltd]:
+Organizational Unit Name (eg, section) []:
+Common Name (e.g. server FQDN or YOUR name) []: yourbotdomainname
+Email Address []:
+Please enter the following 'extra' attributes
+to be sent with your certificate request
+A challenge password []:
+An optional company name []:
+---
+
    +
  • Another example:

    +
      +
    • Using Java keytool:
      keytool -genkey -alias yourbotdomainname -keyalg RSA -keystore yourkeystore.jks -keysize 2048
    • +
    +
  • +
+
---
+Enter keystore password:  
+Re-enter new password: 
+What is your first and last name?  [Unknown]: yourbotdomainname
+What is the name of your organizational unit?  [Unknown]:  
+What is the name of your organization?  [Unknown]:  
+What is the name of your City or Locality?  [Unknown]:  
+What is the name of your State or Province?  [Unknown]:  
+What is the two-letter country code for this unit?  [Unknown]:  
+Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?  
+[no]:  yes
+Enter key password for yourbotdomainname   
+(RETURN if same as keystore password): 
+---
+

This generates the initial keystore, from which you can then create a CSR like this:

+

keytool -certreq -alias yourbotdomainname -keystore yourkeystore.jks -file yourbotdomainname.csr

+
---
+Enter keystore password:
+---
+

To validate your certificate the Common Name (CN) has to match your webhook domain. Example, if you’re using https://www.example.com/example.php as a webhook address, the certificate CN has to be www.example.com.
So you need an exact match of the FQDN you’re setting for the webhook

+

There is an exception, if you’re using a SAN (Subject Alternative Name) the webhook address can either match the CN of your certificate, OR one of the SANs provided in the certificate. In most cases you’ll be using the CN.

+

Create your CSR and supply the contents of the file to your CA. Most CA’s are kind enough to give you an example command of the input format they expect.

+

cat yoursigningrequest.csr or cat yourbotdomainname.csr
Lets you have a look at the CSR we just generated:

+
+ +
+ +

That doesn’t seem to informative, but we can deduce that the file is in PEM format (ASCII base64 encoded) and contains a certificate signing request. Luckily it is possible to look at the human readable contents of the CSR. Use the following commands to double check if all fields are set correctly.

+
    +
  • Using OpenSSL
    openssl req -text -noout -verify -in yoursigningrequest.csr

    +
  • +
  • Using Java keytool
    keytool -printcertreq -v -file yourbotdomainname.csr

    +
  • +
+

Verify your CSR and supply it to your CA to get a certificate. We’ll use StartSSL as an example here. StartSSL allows you to set up to 5 names (SAN), Their intermediate certificate is also needed for a webhook to work, which makes for a nice complete example.

+

Go to the certificates wizard, enter the required hostname(s) for your SSL certificate (this is the CN you’ve also set in the CSR and an optional SAN).

+
+ +
+ +

In the example above we’ve chosen to set a CN (test.telegram.org), but also a SAN (sanexample.telegram.org) The CN given has to match the CN used for generating the CSR.
Set your CN (and optional SAN) and copy the contents of the yoursigningrequest.csr file.

+
+ +
+ +

Paste the contents, submit and you’re done.

+
+ +
+ +

Now you can download the created certificate directly. In the example used above you’ll receive a zip file with several PEM certificates. The root, intermediate and yourdomain certificate.
You need the intermediate and yourdomain to set a webhook with a StartSSL certificate.

+

You can inspect the set of certificates you’ve just downloaded.

+
    +
  • Here are some example commands:

    +
      +
    • Using OpenSSL:
      openssl x509 -in yourdomain.crt -text -noout

      +
    • +
    • Using Java keytool:
      keytool -printcert -v -yourdomain.crt

      +
    • +
    • Using Windows:
      StartSSL supplies certificates in PEM format with a .crt extension, on Windows you can view the contents of them with a quick double click. Extract the files or open the “Otherserver.zip” and double click each of the certificates for inspection. The details tab supplies you with extra information.
      Make sure you have a correct CN in the Subject-field of the yourdomain-certificate. If you're using a SAN, make sure that it is listed in the Subject Alternative Name-field.

      +
    • +
    +
  • +
+
+ +
+ +

With your fresh certificates at hand, you can now continue setting your webhook.

+
    +
  • A self-signed certificate
    +

    Using a self-signed certificate means you’ll forfeit on the chain of trust backed by a CA. Instead you are the CA. For this to work, a slight difference in setup is required. Because Telegram will have no chain of trust to verify your certificate, you have to use the generated public certificate as an input file when setting the webhook. Keep in mind that the certificate file has to be uploaded as multipart/form data in PEM encoded (ASCII BASE64) format.

    +
  • +
  • First let’s generate some certificates:

    +
      +
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"
      You’ll end up with 2 files, a private key and the public certificate file. Use YOURPUBLIC.PEM as input file for setting the webhook.

      +
    • +
    • Using Java keytool:
      keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

      +
      What is your first and last name?
      +[test.telegram.org]:
      +What is the name of your organizational unit?
      +[Unknown]:  
      +What is the name of your organization?
      +[Unknown]:  
      +What is the name of your City or Locality?
      +[Unknown]:  
      +What is the name of your State or Province?
      +[Unknown]:  
      +What is the two-letter country code for this unit?
      +[Unknown]:  
      +Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
      +[no]: yes
      +

      Once done you’ll need 2 more commands to export the public certificate file from the generated store (you’ll be using the store for your JVM and the PEM for setting the webhook)

      +
    • +
    • Convert the JKS to pkcs12 (intermediate step for conversion to PEM):
      keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

      +
    • +
    • Convert PKCS12 to PEM (requires OpenSSL)
      openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem -nokeys

      +
    • +
    • Using Windows:
      Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.
      certreq -new TEMPLATE.txt RequestFileOut generates a CSR.

      +
    • +
    • TEMPLATE.txt example file:

      +
      [NewRequest]
      +; At least one value must be set in this section
      +Subject = "CN=DOMAIN.EXAMPLE"
      +KeyLength = 2048
      +KeyAlgorithm = RSA
      +HashAlgorithm = sha256
      +;MachineKeySet = true
      +RequestType = Cert
      +UseExistingKeySet=false ;generates a new private key (for export)
      +Exportable = true ;makes the private key exportable with the PFX
      +
    • +
    +
  • +
+

A self-signed certificate is generated and installed, to use the certificate for a self-signed webhook you'll have to export it in PEM format.

+
    +
  • Windows continued:

    +
      +
    • You can have a look at the certificates in your store with:
      certutil -store -user my

      +
    • +
    • To export the installed certificate in DER format (intermediate step for conversion to PEM):
      certutil -user -store -split my SERIALNUMBER YOURDER.der

      +
    • +
    • Now you can convert the certificate to PEM:
      certutil -encode YOURDER.der YOURPEM.pem
      Remember that only the public certificate is needed as input for the self-signed webhook certificate parameter.
      certmgr.msc can also be used as a GUI to export the public part of self-signed certificate to PEM.

      +
    • +
    +
  • +
+

After following the above you'll end up with a nice self-signed certificate. You’ll still have to set the webhook, and handle SSL correctly.

+
How do I set a webhook for either type?
+

The setWebhook method is needed for both types. For a verified certificate with a trusted root CA, it’s enough to use the setWebhook method with just the URL parameter.

+
    +
  • A curl example for a verified certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

For a self-signed certificate an extra parameter is needed, certificate, with the public certificate in PEM format as data.

+
    +
  • A curl example for a self-signed certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" -F "certificate=@<YOURCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

The -F means we’re using the multipart/form-data-type to supply the certificate, the type of the certificate parameter is inputFile. Make sure that you’re supplying the correct type.

+

Both parameters for the setWebhook method are classed as optional. Calling the method with an empty URL parameter can be used to clear a previously set webhook.

+
    +
  • A curl example to clear a previous webhook :
    curl -F "url=" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

Keep in mind that the URL parameter starts with https:// when setting a webhook. By default that means we’re knocking at your door on port 443. If you want to use another port (80,88 or 8443), you’ll have to specify the port in the URL parameter.

+
    +
  • Example:
    url=https://<YOURDOMAIN.EXAMPLE>:88/<WEBHOOKLOCATION>
  • +
+
Setting a verified webhook with an untrusted root
+

If you already have a verified certificate and our servers don’t trust your root CA, we have an alternative way for you to set a webhook. Instead of using the setWebhook method without the certificate parameter, you can use the self-signed method. Your CA's root certificate has to be used as an inputFile for the certificate parameter.

+
    +
  • A curl example to supply an untrusted root certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>" -F "certificate=@<YOURCAROOTCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
    Before you can do this, you need the root certificate of your certificate’s CA. Most CA’s supply their root certificates in several different formats (PEM/DER/etc.). Visit your CA’s website, and download the Root certificate indicated for your verified certificate.
  • +
+

You can use these commands to quickly convert a DER formatted root certificate to PEM:

+
    +
  • Using OpenSSL:
    openssl x509 -inform der -in root.cer -out root.pem

    +
  • +
  • Using Java keytool:
    keytool -import -alias Root -keystore YOURKEYSTORE.JKS -trustcacerts -file ROOTCERT.CER
    The root certificate needs to be imported in your keystore first:
    keytool -exportcert -alias Root -file <YOURROOTPEMFILE.PEM> -rfc -keystore YOURKEYSTORE.JKS

    +
  • +
+

Once done, set your webhook with the root-pem-file and you’ll be good to go. If you need more pointers, have a look at the self-signed part of this guide.

+
Supplying an intermediate certificate
+

Once you’ve crafted your certificate, your CA might present you with a nice bundle. Most bundles contain a root certificate, your public certificate and sometimes an intermediate certificate. StartSSL is one of many CA’s that’ll supply such an intermediate beast. This certificate has to be supplied in the chain of certificates you’re presenting to us when we connect to your server. If an intermediate was used to sign your certificate but isn’t supplied to our servers, we won’t be able to verify the chain of trust and your webhook will not work.

+

If your webhook isn’t working and you’re wondering if the chain is complete:

+
    +
  • Check with your certificate provider if you need an intermediate certificate.
  • +
  • Verify your certificate chain.
    Search online for Symantec crypto report or Qualys ssl. 
    +Both supply tools to verify your setup.
    +
  • +
+

Here’s an example of a complete chain, note that in this case 2 intermediate certificates have been supplied.

+
+ +
+ +

Even though your browser might not complain when visiting your page, an incomplete chain will not work for your webhook. If your chain is incomplete we have some tips to add them to your current setup:

+
    +
  • Apache:
    Add the intermediate certificate to the end of the file configured in the SSLCertificateFile directive of your virtual host configuration. If you’re using an older version than Apache 2.4.8, you may use the SSLCertificateChainFile directive instead.

    +
  • +
  • Nginx:
    Add the intermediate certificate to the end of the file configured in the ssl_certificate_key directive of your virtual host configuration.

    +
  • +
  • A quick command for doing this correctly:
    cat your_domain_name.pem intermediate.pem >> bundle.pem
    Make sure the order is correct, expect failure otherwise.

    +
  • +
  • Java keytool:
    keytool -import -trustcacerts -alias intermediate -file intermediate.pem -keystore YOURKEYSTORE.jks

    +
  • +
+

The end result of all this is a complete certificate chain, backed by either a root certificate we trust or, in the case of an untrusted root, a root certificate you're supplying to us. Make sure to verify your setup again after adding the intermediate, once done, you're good to go!

+
Testing your bot with updates
+
    +
  • Update examples
    A set of example updates, which comes in handy for testing your bot.

    +
      +
    • Message with text using curl:

      +
      curl --tlsv1.2 -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test",
      +     "username":"Test"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test",
      +     "username":"Test"
      +  },
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +

      --tlsv1.2 will force using TLS1.2.

      +
    • +
    • Message with text using Postman:

      +
      + +
      +
    • +
    +
  • +
  • More examples in curl:

    +
      +
    • Message with text:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "type": "private",
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Forwarded message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "type": "private",
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "forward_from": {
      +     "last_name":"Forward Lastname",
      +     "id": 222222,
      +     "first_name":"Forward Firstname"
      +  },
      +  "forward_date":1441645550,
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Forwarded channel message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "forward_from": {
      +     "id": -10000000000,
      +     "type": "channel",
      +     "title": "Test channel"
      +  },
      +  "forward_date":1441645550,
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with a reply:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"/start",
      +  "reply_to_message":{
      +      "date":1441645000,
      +      "chat":{
      +          "last_name":"Reply Lastname",
      +          "type": "private",
      +          "id":1111112,
      +          "first_name":"Reply Firstname",
      +          "username":"Testusername"
      +      },
      +      "message_id":1334,
      +      "text":"Original"
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Edited message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"edited_message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"Edited text",
      +  "edit_date": 1441646600
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with entities:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"Bold and italics",
      +  "entities": [
      +      {
      +          "type": "italic",
      +          "offset": 9,
      +          "length": 7
      +      },
      +      {
      +          "type": "bold",
      +          "offset": 0,
      +          "length": 4
      +      }
      +      ]
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with audio:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "audio": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "duration": 243,
      +      "mime_type": "audio/mpeg",
      +      "file_size": 3897500,
      +      "title": "Test music file"
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Voice message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "voice": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "duration": 5,
      +      "mime_type": "audio/ogg",
      +      "file_size": 23000
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with a document:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "document": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "file_name": "Testfile.pdf",
      +      "mime_type": "application/pdf",
      +      "file_size": 536392
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"inline_query":{
      +  "id": 134567890097,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "query": "inline query",
      +  "offset": ""
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Chosen inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"chosen_inline_result":{
      +  "result_id": "12",
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "query": "inline query",
      +  "inline_message_id": "1234csdbsk4839"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Callback query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"callback_query":{
      +  "id": "4382bfdwdsb323b2d9",
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "data": "Data from button callback",
      +  "inline_message_id": "1234csdbsk4839"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +That's all we have for now!
    • +
    +
  • +
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/cdn.html b/data/corefork.telegram.org/cdn.html new file mode 100644 index 0000000000..0e92683de7 --- /dev/null +++ b/data/corefork.telegram.org/cdn.html @@ -0,0 +1,210 @@ + + + + + Encrypted CDNs for Speed and Security + + + + + + + + + + + + + +
+ +
+
+
+
+

Encrypted CDNs for Speed and Security

+ +

Following the launch of version 4.2 of the official apps, Telegram client apps may be required to download popular files that were published in public channels with more than 100,000 members from secondary Content Delivery Network data centers. These CDN DCs are located in regions with significant Telegram traffic where we wouldn't want to place Telegram servers for various reasons.

+

The CDN DCs are not a part of the Telegram cloud and should be considered enemy territory. For this reason, each file that is to be sent to these CDN DCs is encrypted with a unique key using AES-256-CTR encryption. The CDN can't access the data it stores because these keys are only accessible to the main MTProto server and to the authorized client.

+
+

See also: More about CDNs and governments in the Advanced FAQ

+
+

How this works

+

When a file from a public channel with ~100,000 members becomes popular in a particular region, the Telegram server may encrypt this file with a unique AES-256-CTR key and send it to a relevant CDN DC for storage.

+

When a file is stored in a CDN DC close to the end user, the download speed will be much higher because the data needs to travel smaller distances and will likely avoid many bottlenecks that exist between regions.

+

This is secure because CDN DCs are treated the same way as internet providers / random third parties:

+
    +
  • CDN DCs don‘t have the keys to decrypt files that are stored there, so they can’t access the data even if a DC becomes compromised.
  • +
  • Encrypted files fragments are protected from tampering by their SHA-256 hash which is checked on the client upon receipt.
  • +
  • No private data is stored in or passed to the CDN DCs.
  • +
  • The server only allows media from public channels with more than 100,000 subscribers to be cached in CDN DCs (this includes media forwarded from those channels and viral media that originated from other large public channels).
  • +
+
+ +
+ +

CDNs are very limited when it comes to communication: the master data center only uploads encrypted files for storage and will accept no data from the CDN. The client apps only download encrypted files and accept no other updates. The client apps obtain the keys necessary to decrypt the file from the main Telegram server and verify the integrity of the file by its hash, which means that the CDN may only supply the correct file – anything different will be immediately discarded by the client.

+

CDN DCs do not store files on hard disks – only in memory. When a CDN server runs out of memory, a simple LRU algorithm is used to replace the least popular files with new ones.

+

How CDN DCs are different from the master DCs

+
    +
  • CDNs may not be trusted.
  • +
  • Client developers can use help.getCdnConfig to obtain a list of public RSA keys for CDN DCs, which are different from public RSA keys of the master DCs.
  • +
  • CDNs support only the following methods: upload.getCdnFile, initConnection, invokeWithLayer.
  • +
  • When working with CDNs, client developers must remember that auth_key may be deleted at any given moment (resulting in a -404 error, in which case a new key must be generated).
  • +
  • Client apps must not accept updates from CDN DCs (apps should only accept updates from their main connection to the master DC).
  • +
  • Clients must not allow the CDN DCs to substitute replies to queries sent to other DCs.
  • +
  • Clients must not send private user info that is passed in initConnection to the CDNs.
  • +
+

Getting files from a CDN

+

The API may return the upload.fileCdnRedirect constructor after an upload.getFile query. In this case, the client must request the required file from a CDN DC. The dc_id in the response is the id of the new CDN. The IP address for the connection will be available in help.getConfig, same as with the master DCs. The corresponding dcOption will have the flag cdn:flags.3?true.

+

Once a successful connection to the CDN-dc_id is established, the client must generate an auth_key (after confirming that the public RSA MTProto key of the CDN DC matches one from the list returned in help.getCdnConfig). Then the client must perform an upload.getCdnFile for each offset. For files of an unknown size it is necessary to repeat the query until an empty reply is returned.

+

upload.getCdnFile may return the upload.cdnFileReuploadNeeded constructor. In this case, the client needs to send an upload.reuploadCdnFile request to the DC that got the original upload.getFile request. Once upload.reuploadCdnFile is successfull, the app needs to request the file from the CDN DC again.

+

The main DC for a file is the DC where its main copy is stored (not to be confused with the main DC of the user) – either userProfilePhoto.dc_id, chatPhoto.dc_id, photo.dc_id, or document.dc_id.

+

Decrypting files

+

In upload.fileCdnRedirect, the server sends a decryption key and IV for the file (the fields encryption_key:bytes and encryption_iv:bytes respectively).

+

Having received a portion of encrypted data from the CDN DC inside upload.cdnFile, the client must decrypt this data using AES-256-CTR. For IV, it should use the value of encryption_iv, modified in the following manner: for each offset replace the last 4 bytes of the encryption_iv with offset / 16 in big-endian. This allows to effectively decrypt a file and to use random access to a file's content (e.g., for streaming).

+

Verifying files

+

In order to confirm that the CDN DC passed an untampered file, clients must verify hashes for each downloaded part. upload.fileCdnRedirect, upload.reuploadCdnFile and upload.getCdnFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

+

Before saving each portion of the data received from the CDN DC into the file, the client must confirm that its hash matches the hash that was received from the master DC. If missing a hash for any file part, client developers must use the upload.getCdnFileHashes method to obtain the missing hash.

+

Schema

+
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
+
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+
+
+dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+
+cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
+
+
+cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
+
+---functions---
+
+// CDN DC
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
+
+// Master DC
+upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
+upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
+
+help.getCdnConfig#52029342 = CdnConfig;
+

Restrictions on upload.getFile and upload.getCdnFile parameters

+
    +
  • offset must be divisible by 4096 bytes
  • +
  • limit must be divisible by 4096 bytes
  • +
  • 1048576 (1MB) must be divisible by limit
  • +
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024)
    (file parts that are being downloaded must always be inside the same megabyte-sized fragment)
  • +
+

Possible errors and their meanings

+ + + + + + + + + + + + + + + + + + +
upload.getCdnFileFILE_TOKEN_INVALIDThe CDN DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileFILE_TOKEN_INVALIDThe master DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileREQUEST_TOKEN_INVALIDThe master DC did not accept the request_token from the CDN DC. Continue downloading the file from the master DC using upload.getFile.
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.authorizationForm b/data/corefork.telegram.org/constructor/account.authorizationForm new file mode 100644 index 0000000000..7f322f28a3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.authorizationForm @@ -0,0 +1,174 @@ + + + + + account.authorizationForm + + + + + + + + + + + + + +
+ +
+
+
+ +

account.authorizationForm

+ +

Telegram Passport authorization form

+

+ +
+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
required_typesVector<SecureRequiredType>Required Telegram Passport documents
valuesVector<SecureValue>Already submitted Telegram Passport documents
errorsVector<SecureValueError>Telegram Passport errors
usersVector<User>Info about the bot to which the form will be submitted
privacy_policy_urlflags.0?stringURL of the service's privacy policy
+

Type

+

account.AuthorizationForm

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.authorizations b/data/corefork.telegram.org/constructor/account.authorizations new file mode 100644 index 0000000000..b2a3017b14 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.authorizations @@ -0,0 +1,147 @@ + + + + + account.authorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.authorizations

+ +

Logged-in sessions

+

+ +
+
account.authorizations#4bff8ea0 authorization_ttl_days:int authorizations:Vector<Authorization> = account.Authorizations;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
authorizationsVector<Authorization>Logged-in sessions
+

Type

+

account.Authorizations

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.autoDownloadSettings b/data/corefork.telegram.org/constructor/account.autoDownloadSettings new file mode 100644 index 0000000000..e9d474765e --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.autoDownloadSettings @@ -0,0 +1,157 @@ + + + + + account.autoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.autoDownloadSettings

+ +

Media autodownload settings

+

+ +
+
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lowAutoDownloadSettingsLow data usage preset
mediumAutoDownloadSettingsMedium data usage preset
highAutoDownloadSettingsHigh data usage preset
+

Type

+

account.AutoDownloadSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.chatThemes b/data/corefork.telegram.org/constructor/account.chatThemes new file mode 100644 index 0000000000..1d566c726c --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.chatThemes @@ -0,0 +1,155 @@ + + + + + account.chatThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.chatThemes

+ +

Available chat themes

+

+ +
+
Constructor schema is available as of layer 134. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
themesVector<ChatTheme>Available chat themes
+

Type

+

account.ChatThemes

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.chatThemesNotModified b/data/corefork.telegram.org/constructor/account.chatThemesNotModified new file mode 100644 index 0000000000..518cf65c92 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.chatThemesNotModified @@ -0,0 +1,132 @@ + + + + + account.chatThemesNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

account.chatThemesNotModified

+ +

The available chat themes were not modified

+

+ +
+
Constructor schema is available as of layer 134. Switch »

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

account.ChatThemes

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.contentSettings b/data/corefork.telegram.org/constructor/account.contentSettings new file mode 100644 index 0000000000..5e17bb0f77 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.contentSettings @@ -0,0 +1,157 @@ + + + + + account.contentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.contentSettings

+ +

Sensitive content settings

+

+ +
+
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueWhether viewing of sensitive (NSFW) content is enabled
sensitive_can_changeflags.1?trueWhether the current client can change the sensitive content settings to view NSFW content
+

Type

+

account.ContentSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.password b/data/corefork.telegram.org/constructor/account.password new file mode 100644 index 0000000000..093eaeadb2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.password @@ -0,0 +1,213 @@ + + + + + account.password + + + + + + + + + + + + + +
+ +
+
+
+ +

account.password

+ +

Configuration for two-factor authorization

+

+ +
+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_recoveryflags.0?trueWhether the user has a recovery method configured
has_secure_valuesflags.1?trueWhether telegram passport is enabled
has_passwordflags.2?trueWhether the user has a password
current_algoflags.2?PasswordKdfAlgoThe KDF algorithm for SRP two-factor authentication of the current password
srp_Bflags.2?bytesSrp B param for SRP authorization
srp_idflags.2?longSrp ID param for SRP authorization
hintflags.3?stringText hint for the password
email_unconfirmed_patternflags.4?stringA password recovery email with the specified pattern is still awaiting verification
new_algoPasswordKdfAlgoThe KDF algorithm for SRP two-factor authentication to use when creating new passwords
new_secure_algoSecurePasswordKdfAlgoThe KDF algorithm for telegram passport
secure_randombytesSecure random string
pending_reset_dateflags.5?intThe 2FA password will be automatically removed at this date, unless the user cancels the operation
+

Type

+

account.Password

+

Related pages

+

Telegram Passport Manual

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.passwordInputSettings b/data/corefork.telegram.org/constructor/account.passwordInputSettings new file mode 100644 index 0000000000..c0e22f7091 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.passwordInputSettings @@ -0,0 +1,176 @@ + + + + + account.passwordInputSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.passwordInputSettings

+ +

Settings for setting up a new password

+

+ +
+
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
new_algoflags.0?PasswordKdfAlgoThe SRP algorithm to use
new_password_hashflags.0?bytesThe computed password hash
hintflags.0?stringText hint for the password
emailflags.1?stringPassword recovery email
new_secure_settingsflags.2?SecureSecretSettingsTelegram passport settings
+

Type

+

account.PasswordInputSettings

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.passwordSettings b/data/corefork.telegram.org/constructor/account.passwordSettings new file mode 100644 index 0000000000..44ada227a7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.passwordSettings @@ -0,0 +1,161 @@ + + + + + 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 new file mode 100644 index 0000000000..4d2bd2d48d --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.privacyRules @@ -0,0 +1,157 @@ + + + + + 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.resetPasswordFailedWait b/data/corefork.telegram.org/constructor/account.resetPasswordFailedWait new file mode 100644 index 0000000000..e9ad24616b --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.resetPasswordFailedWait @@ -0,0 +1,147 @@ + + + + + account.resetPasswordFailedWait + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPasswordFailedWait

+ +

You recently requested a password reset that was canceled, please wait until the specified date before requesting another reset.

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
retry_dateintWait until this date before requesting another reset.
+

Type

+

account.ResetPasswordResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.resetPasswordOk b/data/corefork.telegram.org/constructor/account.resetPasswordOk new file mode 100644 index 0000000000..b49587414a --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.resetPasswordOk @@ -0,0 +1,132 @@ + + + + + account.resetPasswordOk + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPasswordOk

+ +

The 2FA password was reset successfully.

+

+ +
+
account.resetPasswordOk#e926d63e = account.ResetPasswordResult;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

account.ResetPasswordResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.resetPasswordRequestedWait b/data/corefork.telegram.org/constructor/account.resetPasswordRequestedWait new file mode 100644 index 0000000000..3b3b6bc87a --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.resetPasswordRequestedWait @@ -0,0 +1,147 @@ + + + + + account.resetPasswordRequestedWait + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPasswordRequestedWait

+ +

You successfully requested a password reset, please wait until the specified date before finalizing the reset.

+

+ +
+
account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
until_dateintWait until this date before finalizing the reset.
+

Type

+

account.ResetPasswordResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.sentChangePhoneCode b/data/corefork.telegram.org/constructor/account.sentChangePhoneCode new file mode 100644 index 0000000000..1513568d8b --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.sentChangePhoneCode @@ -0,0 +1,161 @@ + + + + + account.sentChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sentChangePhoneCode

+ +

Sent change phone code

+

+ +
+
Constructor schema is available as of layer 50. Switch »

+

Parameters

+ + + + + + + + + + + + + +
phone_code_hashstringChange phone code hash
send_call_timeoutintCall timeout
+

Type

+

account.SentChangePhoneCode

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.sentEmailCode b/data/corefork.telegram.org/constructor/account.sentEmailCode new file mode 100644 index 0000000000..72bf5716ff --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.sentEmailCode @@ -0,0 +1,155 @@ + + + + + account.sentEmailCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sentEmailCode

+ +

The sent email code

+

+ +
+
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
email_patternstringThe email (to which the code was sent) must match this pattern
lengthintThe length of the verification code
+

Type

+

account.SentEmailCode

+

Related pages

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.takeout b/data/corefork.telegram.org/constructor/account.takeout new file mode 100644 index 0000000000..62d176032c --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.takeout @@ -0,0 +1,147 @@ + + + + + account.takeout + + + + + + + + + + + + + +
+ +
+
+
+ +

account.takeout

+ +

Takout info

+

+ +
+
account.takeout#4dba4501 id:long = account.Takeout;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongTakeout ID
+

Type

+

account.Takeout

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.themes b/data/corefork.telegram.org/constructor/account.themes new file mode 100644 index 0000000000..c3eabd2b69 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.themes @@ -0,0 +1,155 @@ + + + + + account.themes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.themes

+ +

Installed themes

+

+ +
+
account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
themesVector<Theme>Themes
+

Type

+

account.Themes

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.themesNotModified b/data/corefork.telegram.org/constructor/account.themesNotModified new file mode 100644 index 0000000000..e48df3d48b --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.themesNotModified @@ -0,0 +1,132 @@ + + + + + account.themesNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

account.themesNotModified

+ +

No new themes were installed

+

+ +
+
account.themesNotModified#f41eb622 = account.Themes;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

account.Themes

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.tmpPassword b/data/corefork.telegram.org/constructor/account.tmpPassword new file mode 100644 index 0000000000..64c60c24a7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.tmpPassword @@ -0,0 +1,152 @@ + + + + + account.tmpPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

account.tmpPassword

+ +

Temporary payment password

+

+ +
+
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
tmp_passwordbytesTemporary password
valid_untilintValidity period
+

Type

+

account.TmpPassword

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.wallPapers b/data/corefork.telegram.org/constructor/account.wallPapers new file mode 100644 index 0000000000..fb0c18d8aa --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.wallPapers @@ -0,0 +1,155 @@ + + + + + account.wallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.wallPapers

+ +

Installed wallpapers

+

+ +
+
account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
wallpapersVector<WallPaper>Wallpapers
+

Type

+

account.WallPapers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.wallPapersNotModified b/data/corefork.telegram.org/constructor/account.wallPapersNotModified new file mode 100644 index 0000000000..c7e658c271 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.wallPapersNotModified @@ -0,0 +1,132 @@ + + + + + account.wallPapersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

account.wallPapersNotModified

+ +

No new wallpapers were found

+

+ +
+
account.wallPapersNotModified#1c199183 = account.WallPapers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

account.WallPapers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.webAuthorizations b/data/corefork.telegram.org/constructor/account.webAuthorizations new file mode 100644 index 0000000000..88d8bead17 --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.webAuthorizations @@ -0,0 +1,152 @@ + + + + + account.webAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.webAuthorizations

+ +

Web authorizations

+

+ +
+
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
authorizationsVector<WebAuthorization>Web authorization list
usersVector<User>Users
+

Type

+

account.WebAuthorizations

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/accountDaysTTL.html b/data/corefork.telegram.org/constructor/accountDaysTTL.html new file mode 100644 index 0000000000..5f9444f89f --- /dev/null +++ b/data/corefork.telegram.org/constructor/accountDaysTTL.html @@ -0,0 +1,147 @@ + + + + + accountDaysTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

accountDaysTTL

+ +

Time to live in days of the current account

+

+ +
+
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
daysintThis account will self-destruct in the specified number of days
+

Type

+

AccountDaysTTL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.authorization b/data/corefork.telegram.org/constructor/auth.authorization new file mode 100644 index 0000000000..1346644c64 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.authorization @@ -0,0 +1,159 @@ + + + + + auth.authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.authorization

+ +

Contains user authorization info.

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
tmp_sessionsflags.0?intTemporary passport sessions
userUserInfo on authorized user
+

Type

+

auth.Authorization

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired b/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired new file mode 100644 index 0000000000..dac20857a9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired @@ -0,0 +1,155 @@ + + + + + auth.authorizationSignUpRequired + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.authorizationSignUpRequired

+ +

An account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up

+

+ +
+
auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
terms_of_serviceflags.0?help.TermsOfServiceTelegram's terms of service: the user must read and accept the terms of service before signing up to telegram
+

Type

+

auth.Authorization

+

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeCall b/data/corefork.telegram.org/constructor/auth.codeTypeCall new file mode 100644 index 0000000000..0e4c665575 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.codeTypeCall @@ -0,0 +1,132 @@ + + + + + auth.codeTypeCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.codeTypeCall

+ +

Type of verification code that will be sent next if you call the resendCode method: SMS code

+

+ +
+
auth.codeTypeCall#741cd3e3 = auth.CodeType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

auth.CodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeFlashCall b/data/corefork.telegram.org/constructor/auth.codeTypeFlashCall new file mode 100644 index 0000000000..6249d60bc4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.codeTypeFlashCall @@ -0,0 +1,132 @@ + + + + + auth.codeTypeFlashCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.codeTypeFlashCall

+ +

Type of verification code that will be sent next if you call the resendCode method: SMS code

+

+ +
+
auth.codeTypeFlashCall#226ccefb = auth.CodeType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

auth.CodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeMissedCall b/data/corefork.telegram.org/constructor/auth.codeTypeMissedCall new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.codeTypeMissedCall @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeSms b/data/corefork.telegram.org/constructor/auth.codeTypeSms new file mode 100644 index 0000000000..2c604a3ea5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.codeTypeSms @@ -0,0 +1,132 @@ + + + + + auth.codeTypeSms + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.codeTypeSms

+ +

Type of verification code that will be sent next if you call the resendCode method: SMS code

+

+ +
+
auth.codeTypeSms#72a3158c = auth.CodeType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

auth.CodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.exportedAuthorization b/data/corefork.telegram.org/constructor/auth.exportedAuthorization new file mode 100644 index 0000000000..b39e5167f2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.exportedAuthorization @@ -0,0 +1,152 @@ + + + + + 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.loggedOut b/data/corefork.telegram.org/constructor/auth.loggedOut new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.loggedOut @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.loginToken b/data/corefork.telegram.org/constructor/auth.loginToken new file mode 100644 index 0000000000..1516fcf5d8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.loginToken @@ -0,0 +1,155 @@ + + + + + auth.loginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.loginToken

+ +

Login token (for QR code login)

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
expiresintExpiry date of QR code
tokenbytesToken to render in QR code
+

Type

+

auth.LoginToken

+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo b/data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo new file mode 100644 index 0000000000..f3be3eec0d --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo @@ -0,0 +1,152 @@ + + + + + auth.loginTokenMigrateTo + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.loginTokenMigrateTo

+ +

Repeat the query to the specified DC

+

+ +
+
auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintDC ID
tokenbytesToken to use for login
+

Type

+

auth.LoginToken

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.loginTokenSuccess b/data/corefork.telegram.org/constructor/auth.loginTokenSuccess new file mode 100644 index 0000000000..aa878dbc08 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.loginTokenSuccess @@ -0,0 +1,147 @@ + + + + + auth.loginTokenSuccess + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.loginTokenSuccess

+ +

Login via token (QR code) succeded!

+

+ +
+
auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
authorizationauth.AuthorizationAuthorization info
+

Type

+

auth.LoginToken

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.passwordRecovery b/data/corefork.telegram.org/constructor/auth.passwordRecovery new file mode 100644 index 0000000000..d8149f5a0d --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.passwordRecovery @@ -0,0 +1,152 @@ + + + + + auth.passwordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.passwordRecovery

+ +

Recovery info of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
email_patternstringThe email to which the recovery code was sent must match this pattern.
+

Type

+

auth.PasswordRecovery

+

Related pages

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.sentAppCode b/data/corefork.telegram.org/constructor/auth.sentAppCode new file mode 100644 index 0000000000..edaa393603 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.sentAppCode @@ -0,0 +1,163 @@ + + + + + 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/auth.sentCode b/data/corefork.telegram.org/constructor/auth.sentCode new file mode 100644 index 0000000000..958c96b8d0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.sentCode @@ -0,0 +1,172 @@ + + + + + auth.sentCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCode

+ +

Contains info about a sent verification code.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
+

Type

+

auth.SentCode

+

Related pages

+

auth.signIn

+

Signs in a user with a validated phone number.

+

auth.resendCode

+

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeApp b/data/corefork.telegram.org/constructor/auth.sentCodeTypeApp new file mode 100644 index 0000000000..1dbabda434 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.sentCodeTypeApp @@ -0,0 +1,147 @@ + + + + + auth.sentCodeTypeApp + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeApp

+ +

The code was sent through the telegram app

+

+ +
+
auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lengthintLength of the code in bytes
+

Type

+

auth.SentCodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeCall b/data/corefork.telegram.org/constructor/auth.sentCodeTypeCall new file mode 100644 index 0000000000..58fd5f4006 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.sentCodeTypeCall @@ -0,0 +1,147 @@ + + + + + auth.sentCodeTypeCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeCall

+ +

The code will be sent via a phone call: a synthesized voice will tell the user which verification code to input.

+

+ +
+
auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lengthintLength of the verification code
+

Type

+

auth.SentCodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeFlashCall b/data/corefork.telegram.org/constructor/auth.sentCodeTypeFlashCall new file mode 100644 index 0000000000..e6df3a0581 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.sentCodeTypeFlashCall @@ -0,0 +1,150 @@ + + + + + auth.sentCodeTypeFlashCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeFlashCall

+ +

The code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.

+

+ +
+
auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
patternstringpattern to match
+

Type

+

auth.SentCodeType

+

Related pages

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeMissedCall b/data/corefork.telegram.org/constructor/auth.sentCodeTypeMissedCall new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.sentCodeTypeMissedCall @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeSms b/data/corefork.telegram.org/constructor/auth.sentCodeTypeSms new file mode 100644 index 0000000000..f5309394ef --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.sentCodeTypeSms @@ -0,0 +1,147 @@ + + + + + auth.sentCodeTypeSms + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeSms

+ +

The code was sent via SMS

+

+ +
+
auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lengthintLength of the code in bytes
+

Type

+

auth.SentCodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/authorization.html b/data/corefork.telegram.org/constructor/authorization.html new file mode 100644 index 0000000000..61aaeadeeb --- /dev/null +++ b/data/corefork.telegram.org/constructor/authorization.html @@ -0,0 +1,225 @@ + + + + + authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

authorization

+ +

Logged-in session

+

+ +
+
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
currentflags.0?trueWhether this is the current session
official_appflags.1?trueWhether the session is from an official app
password_pendingflags.2?trueWhether the session is still waiting for a 2FA password
hashlongIdentifier
device_modelstringDevice model
platformstringPlatform
system_versionstringSystem version
api_idintAPI ID
app_namestringApp name
app_versionstringApp version
date_createdintWhen was the session created
date_activeintWhen was the session last active
ipstringLast known IP
countrystringCountry determined from IP
regionstringRegion determined from IP
+

Type

+

Authorization

+

Related pages

+

Creating your Telegram Application

+

How to get your application identifier and create a new Telegram app.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/autoDownloadSettings.html b/data/corefork.telegram.org/constructor/autoDownloadSettings.html new file mode 100644 index 0000000000..925890f1d4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/autoDownloadSettings.html @@ -0,0 +1,187 @@ + + + + + autoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

autoDownloadSettings

+ +

Autodownload settings

+

+ +
+
autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
disabledflags.0?trueDisable automatic media downloads?
video_preload_largeflags.1?trueWhether to preload the first seconds of videos larger than the specified limit
audio_preload_nextflags.2?trueWhether to preload the next audio track when you're listening to music
phonecalls_less_dataflags.3?trueWhether to enable data saving mode in phone calls
photo_size_maxintMaximum size of photos to preload
video_size_maxintMaximum size of videos to preload
file_size_maxintMaximum size of other files to preload
video_upload_maxbitrateintMaximum suggested bitrate for uploading videos
+

Type

+

AutoDownloadSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/availableReaction.html b/data/corefork.telegram.org/constructor/availableReaction.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/availableReaction.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/bankCardOpenUrl.html b/data/corefork.telegram.org/constructor/bankCardOpenUrl.html new file mode 100644 index 0000000000..150c6eddbb --- /dev/null +++ b/data/corefork.telegram.org/constructor/bankCardOpenUrl.html @@ -0,0 +1,152 @@ + + + + + bankCardOpenUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

bankCardOpenUrl

+ +

Credit card info URL provided by the bank

+

+ +
+
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringInfo URL
namestringBank name
+

Type

+

BankCardOpenUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/baseThemeArctic.html b/data/corefork.telegram.org/constructor/baseThemeArctic.html new file mode 100644 index 0000000000..965d7643dc --- /dev/null +++ b/data/corefork.telegram.org/constructor/baseThemeArctic.html @@ -0,0 +1,132 @@ + + + + + baseThemeArctic + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeArctic

+ +

Arctic theme

+

+ +
+
baseThemeArctic#5b11125a = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/baseThemeClassic.html b/data/corefork.telegram.org/constructor/baseThemeClassic.html new file mode 100644 index 0000000000..c6575294a1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/baseThemeClassic.html @@ -0,0 +1,132 @@ + + + + + baseThemeClassic + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeClassic

+ +

Classic theme

+

+ +
+
baseThemeClassic#c3a12462 = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/baseThemeDay.html b/data/corefork.telegram.org/constructor/baseThemeDay.html new file mode 100644 index 0000000000..a8fd90525f --- /dev/null +++ b/data/corefork.telegram.org/constructor/baseThemeDay.html @@ -0,0 +1,132 @@ + + + + + baseThemeDay + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeDay

+ +

Day theme

+

+ +
+
baseThemeDay#fbd81688 = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/baseThemeNight.html b/data/corefork.telegram.org/constructor/baseThemeNight.html new file mode 100644 index 0000000000..19a14b6308 --- /dev/null +++ b/data/corefork.telegram.org/constructor/baseThemeNight.html @@ -0,0 +1,132 @@ + + + + + baseThemeNight + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeNight

+ +

Night theme

+

+ +
+
baseThemeNight#b7b31ea8 = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/baseThemeTinted.html b/data/corefork.telegram.org/constructor/baseThemeTinted.html new file mode 100644 index 0000000000..60a553ecaa --- /dev/null +++ b/data/corefork.telegram.org/constructor/baseThemeTinted.html @@ -0,0 +1,132 @@ + + + + + baseThemeTinted + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeTinted

+ +

Tinted theme

+

+ +
+
baseThemeTinted#6d5f77ee = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/boolFalse.html b/data/corefork.telegram.org/constructor/boolFalse.html new file mode 100644 index 0000000000..b40236b516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/boolFalse.html @@ -0,0 +1,132 @@ + + + + + boolFalse + + + + + + + + + + + + + +
+ +
+
+
+ +

boolFalse

+ +

Constructor may be interpreted as a booleanfalse value.

+

+ +
+
boolFalse#bc799737 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/boolTrue.html b/data/corefork.telegram.org/constructor/boolTrue.html new file mode 100644 index 0000000000..f066d89ff4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/boolTrue.html @@ -0,0 +1,132 @@ + + + + + boolTrue + + + + + + + + + + + + + +
+ +
+
+
+ +

boolTrue

+ +

The constructor can be interpreted as a booleantrue value.

+

+ +
+
boolTrue#997275b5 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botCommand.html b/data/corefork.telegram.org/constructor/botCommand.html new file mode 100644 index 0000000000..7d2897d6c2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botCommand.html @@ -0,0 +1,152 @@ + + + + + botCommand + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommand

+ +

Describes a bot command that can be used in a chat

+

+ +
+
botCommand#c27ac8c7 command:string description:string = BotCommand;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
commandstring/command name
descriptionstringDescription of the command
+

Type

+

BotCommand

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html b/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html new file mode 100644 index 0000000000..62999ba55c --- /dev/null +++ b/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html @@ -0,0 +1,135 @@ + + + + + botCommandScopeChatAdmins + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeChatAdmins

+ +

The specified bot commands will be valid only for chat administrators, in all groups and supergroups.

+

+ +
+
botCommandScopeChatAdmins#b9aa606a = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botCommandScopeChats.html b/data/corefork.telegram.org/constructor/botCommandScopeChats.html new file mode 100644 index 0000000000..716d378dba --- /dev/null +++ b/data/corefork.telegram.org/constructor/botCommandScopeChats.html @@ -0,0 +1,135 @@ + + + + + botCommandScopeChats + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeChats

+ +

The specified bot commands will be valid in all groups and supergroups.

+

+ +
+
botCommandScopeChats#6fe1a881 = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botCommandScopeDefault.html b/data/corefork.telegram.org/constructor/botCommandScopeDefault.html new file mode 100644 index 0000000000..8c414c9684 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botCommandScopeDefault.html @@ -0,0 +1,132 @@ + + + + + botCommandScopeDefault + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeDefault

+ +

The commands will be valid in all dialogs

+

+ +
+
botCommandScopeDefault#2f6cb2ab = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeer.html b/data/corefork.telegram.org/constructor/botCommandScopePeer.html new file mode 100644 index 0000000000..39802d810c --- /dev/null +++ b/data/corefork.telegram.org/constructor/botCommandScopePeer.html @@ -0,0 +1,147 @@ + + + + + botCommandScopePeer + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopePeer

+ +

The specified bot commands will be valid only in a specific dialog.

+

+ +
+
botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
+

Type

+

BotCommandScope

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html b/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html new file mode 100644 index 0000000000..81892165c1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html @@ -0,0 +1,155 @@ + + + + + botCommandScopePeerUser + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopePeerUser

+ +

The specified bot commands will be valid only for a specific user in the specified group or supergroup.

+

+ +
+
botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat
user_idInputUserThe user
+

Type

+

BotCommandScope

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botCommandScopeUsers.html b/data/corefork.telegram.org/constructor/botCommandScopeUsers.html new file mode 100644 index 0000000000..73546c9751 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botCommandScopeUsers.html @@ -0,0 +1,132 @@ + + + + + botCommandScopeUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeUsers

+ +

The specified bot commands will only be valid in all private chats with users.

+

+ +
+
botCommandScopeUsers#3c4f04d8 = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInfo.html b/data/corefork.telegram.org/constructor/botInfo.html new file mode 100644 index 0000000000..4553b0d96c --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInfo.html @@ -0,0 +1,157 @@ + + + + + botInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

botInfo

+ +

Info about bots (available bot commands, etc)

+

+ +
+
botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongID of the bot
descriptionstringDescription of the bot
commandsVector<BotCommand>Bot commands that can be used in the chat
+

Type

+

BotInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInlineMediaResult.html b/data/corefork.telegram.org/constructor/botInlineMediaResult.html new file mode 100644 index 0000000000..a46aace000 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineMediaResult.html @@ -0,0 +1,186 @@ + + + + + botInlineMediaResult + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMediaResult

+ +

Media result

+

+ +
+
botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
photoflags.0?PhotoIf type is photo, the photo to send
documentflags.1?DocumentIf type is document, the document to send
titleflags.2?stringResult title
descriptionflags.3?stringDescription
send_messageBotInlineMessageDepending on the type and on the constructor, contains the caption of the media or the content of the message to be sent instead of the media
+

Type

+

BotInlineResult

+

Related pages

+

Telegram Bot API

+

BotInlineMessage

+

Inline message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInlineMessageMediaAuto.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaAuto.html new file mode 100644 index 0000000000..5d83c25e1e --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineMessageMediaAuto.html @@ -0,0 +1,167 @@ + + + + + botInlineMessageMediaAuto + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaAuto

+ +

Send whatever media is attached to the botInlineMediaResult

+

+ +
+
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

botInlineMediaResult

+

Media result

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInlineMessageMediaContact.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaContact.html new file mode 100644 index 0000000000..18f8a3dde7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineMessageMediaContact.html @@ -0,0 +1,172 @@ + + + + + botInlineMessageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaContact

+ +

Send a contact

+

+ +
+
botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInlineMessageMediaGeo.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaGeo.html new file mode 100644 index 0000000000..13917eb692 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineMessageMediaGeo.html @@ -0,0 +1,175 @@ + + + + + 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/corefork.telegram.org/constructor/botInlineMessageMediaInvoice.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaInvoice.html new file mode 100644 index 0000000000..521c9fcc8f --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineMessageMediaInvoice.html @@ -0,0 +1,189 @@ + + + + + botInlineMessageMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaInvoice

+ +

Send an invoice

+

+ +
+
botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueSet this flag if you require the user's shipping address to complete the order
testflags.3?trueTest invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentProduct photo
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInlineMessageMediaVenue.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaVenue.html new file mode 100644 index 0000000000..caa31b4c67 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineMessageMediaVenue.html @@ -0,0 +1,182 @@ + + + + + botInlineMessageMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageMediaVenue

+ +

Send a venue

+

+ +
+
botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInlineMessageText.html b/data/corefork.telegram.org/constructor/botInlineMessageText.html new file mode 100644 index 0000000000..3487f125c6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineMessageText.html @@ -0,0 +1,170 @@ + + + + + botInlineMessageText + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineMessageText

+ +

Send a simple text message

+

+ +
+
botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringThe message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

BotInlineMessage

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInlineResult.html b/data/corefork.telegram.org/constructor/botInlineResult.html new file mode 100644 index 0000000000..f148304c86 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineResult.html @@ -0,0 +1,189 @@ + + + + + botInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineResult

+ +

Generic result

+

+ +
+
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of article or webpage
thumbflags.4?WebDocumentThumbnail for the result
contentflags.5?WebDocumentContent of the result
send_messageBotInlineMessageMessage to send
+

Type

+

BotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/cdnConfig.html b/data/corefork.telegram.org/constructor/cdnConfig.html new file mode 100644 index 0000000000..ccc54d58e9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/cdnConfig.html @@ -0,0 +1,149 @@ + + + + + cdnConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

cdnConfig

+ +

Configuration for CDN file downloads.

+

+ +
+
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
public_keysVector<CdnPublicKey>Vector of public keys to use only during handshakes to CDN DCs.
+

Type

+

CdnConfig

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/cdnPublicKey.html b/data/corefork.telegram.org/constructor/cdnPublicKey.html new file mode 100644 index 0000000000..5a97e31905 --- /dev/null +++ b/data/corefork.telegram.org/constructor/cdnPublicKey.html @@ -0,0 +1,154 @@ + + + + + cdnPublicKey + + + + + + + + + + + + + +
+ +
+
+
+ +

cdnPublicKey

+ +

Public key to use only during handshakes to CDN DCs.

+

+ +
+
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintCDN DC ID
public_keystringRSA public key
+

Type

+

CdnPublicKey

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channel.html b/data/corefork.telegram.org/constructor/channel.html new file mode 100644 index 0000000000..4f7e797683 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channel.html @@ -0,0 +1,289 @@ + + + + + channel + + + + + + + + + + + + + +
+ +
+
+
+ +

channel

+ +

Channel/supergroup info

+

+ +
+
channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of this channel
leftflags.2?trueWhether the current user has left this channel
broadcastflags.5?trueIs this a channel?
verifiedflags.7?trueIs this channel verified by telegram?
megagroupflags.8?trueIs this a supergroup?
restrictedflags.9?trueWhether viewing/writing in this channel for a reason (see restriction_reason
signaturesflags.11?trueWhether signatures are enabled (channels)
minflags.12?trueSee min
scamflags.19?trueThis channel/supergroup is probably a scam
has_linkflags.20?trueWhether this channel has a private join link
has_geoflags.21?trueWhether this chanel has a geoposition
slowmode_enabledflags.22?trueWhether slow mode is enabled for groups to prevent flood in chat
call_activeflags.23?trueWhether a group call or livestream is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call or livestream
fakeflags.25?trueIf set, this supergroup/channel was reported by many users as a fake or scam: be careful when interacting with it.
gigagroupflags.26?trueWhether this supergroup is a gigagroup
idlongID of the channel
access_hashflags.13?longAccess hash
titlestringTitle
usernameflags.6?stringUsername
photoChatPhotoProfile photo
dateintDate when the user joined the supergroup/channel, or if the user isn't a member, its creation date
restriction_reasonflags.9?Vector<RestrictionReason>Contains the reason why access to this channel must be restricted.
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in this channel (see rights)
banned_rightsflags.15?ChatBannedRightsBanned rights of the user in this channel (see rights)
default_banned_rightsflags.18?ChatBannedRightsDefault chat rights (see rights)
participants_countflags.17?intParticipant count
+

Type

+

Chat

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEvent.html b/data/corefork.telegram.org/constructor/channelAdminLogEvent.html new file mode 100644 index 0000000000..e99e3bfc68 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEvent.html @@ -0,0 +1,162 @@ + + + + + channelAdminLogEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEvent

+ +

Admin log event

+

+ +
+
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongEvent ID
dateintDate
user_idlongUser ID
actionChannelAdminLogEventActionAction
+

Type

+

ChannelAdminLogEvent

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html new file mode 100644 index 0000000000..902fde9c62 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html @@ -0,0 +1,152 @@ + + + + + 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/channelAdminLogEventActionChangeAvailableReactions.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAvailableReactions.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAvailableReactions.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html new file mode 100644 index 0000000000..f97817af72 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeHistoryTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeHistoryTTL

+ +

The Time-To-Live of messages in this chat was changed

+

+ +
+
channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valueintPrevious value
new_valueintNew value
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html new file mode 100644 index 0000000000..a4c45848b0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeLinkedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeLinkedChat

+ +

The linked chat was changed

+

+ +
+
channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuelongPrevious linked chat
new_valuelongNew linked chat
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html new file mode 100644 index 0000000000..0218a8de7c --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeLocation

+ +

The geogroup location was changed

+

+ +
+
channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valueChannelLocationPrevious location
new_valueChannelLocationNew location
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html new file mode 100644 index 0000000000..b359c4c4df --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangePhoto

+ +

The channel/supergroup's picture was changed

+

+ +
+
channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_photoPhotoPrevious picture
new_photoPhotoNew picture
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html new file mode 100644 index 0000000000..77a7af892e --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeStickerSet

+ +

The supergroup's stickerset was changed

+

+ +
+
channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_stickersetInputStickerSetPrevious stickerset
new_stickersetInputStickerSetNew stickerset
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html new file mode 100644 index 0000000000..65ec34e8f0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeTitle

+ +

Channel/supergroup title was changed

+

+ +
+
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuestringPrevious title
new_valuestringNew title
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html new file mode 100644 index 0000000000..1539743ba7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeUsername

+ +

Channel/supergroup username was changed

+

+ +
+
channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuestringOld username
new_valuestringNew username
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html new file mode 100644 index 0000000000..bf6783ea91 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html @@ -0,0 +1,155 @@ + + + + + channelAdminLogEventActionDefaultBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionDefaultBannedRights

+ +

The default banned rights were modified

+

+ +
+
channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_banned_rightsChatBannedRightsPrevious global banned rights
new_banned_rightsChatBannedRightsNew glboal banned rights.
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html new file mode 100644 index 0000000000..3b127aaf29 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionDeleteMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionDeleteMessage

+ +

A message was deleted

+

+ +
+
channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe message that was deleted
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html new file mode 100644 index 0000000000..a19200ce5c --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionDiscardGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionDiscardGroupCall

+ +

A group call was terminated

+

+ +
+
channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call that was terminated
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionEditMessage.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionEditMessage.html new file mode 100644 index 0000000000..c9ee8cf661 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionEditMessage.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionEditMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionEditMessage

+ +

A message was edited

+

+ +
+
channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_messageMessageOld message
new_messageMessageNew message
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html new file mode 100644 index 0000000000..888c6b7980 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionExportedInviteDelete + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionExportedInviteDelete

+ +

A chat invite was deleted

+

+ +
+
channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteThe deleted chat invite
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html new file mode 100644 index 0000000000..eef7686659 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionExportedInviteEdit + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionExportedInviteEdit

+ +

A chat invite was edited

+

+ +
+
channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_inviteExportedChatInvitePrevious chat invite information
new_inviteExportedChatInviteNew chat invite information
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html new file mode 100644 index 0000000000..1f4918130e --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionExportedInviteRevoke + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionExportedInviteRevoke

+ +

A specific invite link was revoked

+

+ +
+
channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteThe invite link that was revoked
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html new file mode 100644 index 0000000000..1a522447e4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionParticipantInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantInvite

+ +

A user was invited to the group

+

+ +
+
channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantChannelParticipantThe user that was invited
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html new file mode 100644 index 0000000000..fa784e1dad --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html @@ -0,0 +1,132 @@ + + + + + channelAdminLogEventActionParticipantJoin + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantJoin

+ +

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

+

+ +
+
channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html new file mode 100644 index 0000000000..b1baf473e9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html @@ -0,0 +1,150 @@ + + + + + channelAdminLogEventActionParticipantJoinByInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantJoinByInvite

+ +

A user joined the supergroup/channel using a specific invite link

+

+ +
+
channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteThe invite link used to join the supergroup/channel
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByRequest.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByRequest.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByRequest.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html new file mode 100644 index 0000000000..dad027c32a --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html @@ -0,0 +1,132 @@ + + + + + channelAdminLogEventActionParticipantLeave + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantLeave

+ +

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

+

+ +
+
channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html new file mode 100644 index 0000000000..ed4e812f0a --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionParticipantMute + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantMute

+ +

A group call participant was muted

+

+ +
+
channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantGroupCallParticipantThe participant that was muted
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html new file mode 100644 index 0000000000..cccc46a6fe --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html @@ -0,0 +1,155 @@ + + + + + channelAdminLogEventActionParticipantToggleAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantToggleAdmin

+ +

The admin rights of a user were changed

+

+ +
+
channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_participantChannelParticipantPrevious admin rights
new_participantChannelParticipantNew admin rights
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html new file mode 100644 index 0000000000..beee8d0944 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html @@ -0,0 +1,155 @@ + + + + + channelAdminLogEventActionParticipantToggleBan + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantToggleBan

+ +

The banned rights of a user were changed

+

+ +
+
channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_participantChannelParticipantOld banned rights of user
new_participantChannelParticipantNew banned rights of user
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html new file mode 100644 index 0000000000..ec97065be8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionParticipantUnmute + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantUnmute

+ +

A group call participant was unmuted

+

+ +
+
channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantGroupCallParticipantThe participant that was unmuted
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html new file mode 100644 index 0000000000..037eb525d5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html @@ -0,0 +1,147 @@ + + + + + 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/channelAdminLogEventActionSendMessage.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionSendMessage.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionSendMessage.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html new file mode 100644 index 0000000000..7b194bdbce --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionStartGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionStartGroupCall

+ +

A group call was started

+

+ +
+
channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionStopPoll.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionStopPoll.html new file mode 100644 index 0000000000..c9d1b1aac7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionStopPoll.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionStopPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionStopPoll

+ +

A poll was stopped

+

+ +
+
channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe poll that was stopped
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html new file mode 100644 index 0000000000..4b56345fda --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionToggleGroupCallSetting + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleGroupCallSetting

+ +

Group call settings were changed

+

+ +
+
channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
join_mutedBoolWhether all users are muted by default upon joining
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html new file mode 100644 index 0000000000..f08bb396fe --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionToggleInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleInvites

+ +

Invites were enabled/disabled

+

+ +
+
channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
new_valueBoolNew value
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleNoForwards.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleNoForwards.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleNoForwards.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html new file mode 100644 index 0000000000..11719cac11 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html @@ -0,0 +1,150 @@ + + + + + channelAdminLogEventActionTogglePreHistoryHidden + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionTogglePreHistoryHidden

+ +

The hidden prehistory setting was changed

+

+ +
+
channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
new_valueBoolNew value
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

channels.togglePreHistoryHidden

+

Hide/unhide message history for new channel/supergroup users

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html new file mode 100644 index 0000000000..b8099e1e80 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionToggleSignatures + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleSignatures

+ +

Channel signatures were enabled/disabled

+

+ +
+
channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
new_valueBoolNew value
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html new file mode 100644 index 0000000000..e1569d9e52 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html @@ -0,0 +1,155 @@ + + + + + channelAdminLogEventActionToggleSlowMode + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleSlowMode

+ +

Slow mode setting for supergroups was changed

+

+ +
+
channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valueintPrevious slow mode value
new_valueintNew slow mode value
+

Type

+

ChannelAdminLogEventAction

+

Related pages

+

channels.toggleSlowMode

+

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html new file mode 100644 index 0000000000..0f9f3fe41f --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionUpdatePinned + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionUpdatePinned

+ +

A message was pinned

+

+ +
+
channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe message that was pinned
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventsFilter.html b/data/corefork.telegram.org/constructor/channelAdminLogEventsFilter.html new file mode 100644 index 0000000000..a939335a4d --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventsFilter.html @@ -0,0 +1,266 @@ + + + + + channelAdminLogEventsFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventsFilter

+ +

Filter only certain admin log events

+

+ +
+
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
joinflags.0?trueJoin events
leaveflags.1?trueLeave events
inviteflags.2?trueInvite events
banflags.3?trueBan events
unbanflags.4?trueUnban events
kickflags.5?trueKick events
unkickflags.6?trueUnkick events
promoteflags.7?trueAdmin promotion events
demoteflags.8?trueAdmin demotion events
infoflags.9?trueInfo change events (when about, linked chat, location, photo, stickerset, title or username data of a channel gets modified)
settingsflags.10?trueSettings change events (invites, hidden prehistory, signatures, default banned rights)
pinnedflags.11?trueMessage pin events
editflags.12?trueMessage edit events
deleteflags.13?trueMessage deletion events
group_callflags.14?trueGroup call events
invitesflags.15?trueInvite events
+

Type

+

ChannelAdminLogEventsFilter

+

Related pages

+

channelAdminLogEventActionParticipantJoin

+

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

+

channelAdminLogEventActionParticipantLeave

+

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

+

channelAdminLogEventActionParticipantInvite

+

A user was invited to the group

+

channelAdminLogEventActionParticipantToggleBan

+

The banned rights of a user were changed

+

channelAdminLogEventActionParticipantToggleAdmin

+

The admin rights of a user were changed

+

channelAdminLogEventActionChangeAbout

+

The description was changed

+

channelAdminLogEventActionChangeLinkedChat

+

The linked chat was changed

+

channelAdminLogEventActionChangeLocation

+

The geogroup location was changed

+

channelAdminLogEventActionChangePhoto

+

The channel/supergroup's picture was changed

+

channelAdminLogEventActionChangeStickerSet

+

The supergroup's stickerset was changed

+

channelAdminLogEventActionChangeTitle

+

Channel/supergroup title was changed

+

channelAdminLogEventActionChangeUsername

+

Channel/supergroup username was changed

+

channelAdminLogEventActionToggleInvites

+

Invites were enabled/disabled

+

channelAdminLogEventActionTogglePreHistoryHidden

+

The hidden prehistory setting was changed

+

channelAdminLogEventActionToggleSignatures

+

Channel signatures were enabled/disabled

+

channelAdminLogEventActionDefaultBannedRights

+

The default banned rights were modified

+

channelAdminLogEventActionUpdatePinned

+

A message was pinned

+

channelAdminLogEventActionEditMessage

+

A message was edited

+

channelAdminLogEventActionDeleteMessage

+

A message was deleted

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelForbidden.html b/data/corefork.telegram.org/constructor/channelForbidden.html new file mode 100644 index 0000000000..969f795f61 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelForbidden.html @@ -0,0 +1,177 @@ + + + + + channelForbidden + + + + + + + + + + + + + +
+ +
+
+
+ +

channelForbidden

+ +

Indicates a channel/supergroup we can't access because we were banned, or for some other reason.

+

+ +
+
channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.5?trueIs this a channel
megagroupflags.8?trueIs this a supergroup
idlongChannel ID
access_hashlongAccess hash
titlestringTitle
until_dateflags.16?intThe ban is valid until the specified date
+

Type

+

Chat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelFull.html b/data/corefork.telegram.org/constructor/channelFull.html new file mode 100644 index 0000000000..c48a95280b --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelFull.html @@ -0,0 +1,363 @@ + + + + + channelFull + + + + + + + + + + + + + +
+ +
+
+
+ +

channelFull

+ +

Full info about a channel/supergroup

+

+ +
+
channelFull#e13c3d20 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 requests_pending:flags.28?int recent_requesters:flags.28?Vector<long> default_send_as:flags.29?Peer available_reactions:flags.30?Vector<string> = ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_view_participantsflags.3?trueCan we vew the participant list?
can_set_usernameflags.6?trueCan we set the channel's username?
can_set_stickersflags.7?trueCan we associate a stickerpack to the supergroup?
hidden_prehistoryflags.10?trueIs the history before we joined hidden to us?
can_set_locationflags.16?trueCan we set the geolocation of this group (for geogroups)
has_scheduledflags.19?trueWhether scheduled messages are available
can_view_statsflags.20?trueCan the user view channel/supergroup statistics
blockedflags.22?trueWhether any anonymous admin of this supergroup was blocked: if set, you won't receive messages from anonymous group admins in discussion replies via @replies
idlongID of the channel
aboutstringInfo about the channel
participants_countflags.0?intNumber of participants of the channel
admins_countflags.1?intNumber of channel admins
kicked_countflags.2?intNumber of users kicked from the channel
banned_countflags.2?intNumber of users banned from the channel
online_countflags.13?intNumber of users currently online
read_inbox_max_idintPosition up to which all incoming messages are read.
read_outbox_max_idintPosition up to which all outgoing messages are read.
unread_countintCount of unread messages
chat_photoPhotoChannel picture
notify_settingsPeerNotifySettingsNotification settings
exported_inviteflags.23?ExportedChatInviteInvite link
bot_infoVector<BotInfo>Info about bots in the channel/supergrup
migrated_from_chat_idflags.4?longThe chat ID from which this group was migrated
migrated_from_max_idflags.4?intThe message ID in the original chat at which this group was migrated
pinned_msg_idflags.5?intMessage ID of the last pinned message
stickersetflags.8?StickerSetAssociated stickerset
available_min_idflags.9?intIdentifier of a maximum unavailable message in a channel due to hidden history.
folder_idflags.11?intPeer folder ID, for more info click here
linked_chat_idflags.14?longID of the linked discussion chat for channels
locationflags.15?ChannelLocationLocation of the geogroup
slowmode_secondsflags.17?intIf specified, users in supergroups will only be able to send one message every slowmode_seconds seconds
slowmode_next_send_dateflags.18?intIndicates when the user will be allowed to send another message in the supergroup (unixdate)
stats_dcflags.12?intIf set, specifies the DC to use for fetching channel statistics
ptsintLatest PTS for this channel
callflags.21?InputGroupCallLivestream or group call information
ttl_periodflags.24?intTime-To-Live of messages in this channel or supergroup
pending_suggestionsflags.25?Vector<string>A list of suggested actions for the supergroup admin, see here for more info ».
groupcall_default_join_asflags.26?PeerWhen using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default.
theme_emoticonflags.27?stringEmoji representing a specific chat theme
+

Type

+

ChatFull

+

Related pages

+

channels.setStickers

+

Associate a stickerset to the supergroup

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+

phone.getGroupCallJoinAs

+

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelLocation.html b/data/corefork.telegram.org/constructor/channelLocation.html new file mode 100644 index 0000000000..e283760b30 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelLocation.html @@ -0,0 +1,152 @@ + + + + + channelLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

channelLocation

+ +

Geographical location of supergroup (geogroups)

+

+ +
+
channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointGeoPointGeographical location of supergrup
addressstringTextual description of the address
+

Type

+

ChannelLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelLocationEmpty.html b/data/corefork.telegram.org/constructor/channelLocationEmpty.html new file mode 100644 index 0000000000..84ca524191 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelLocationEmpty.html @@ -0,0 +1,132 @@ + + + + + channelLocationEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

channelLocationEmpty

+ +

No location (normal supergroup)

+

+ +
+
channelLocationEmpty#bfb5ad8b = ChannelLocation;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelMessagesFilter.html b/data/corefork.telegram.org/constructor/channelMessagesFilter.html new file mode 100644 index 0000000000..3529bac777 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelMessagesFilter.html @@ -0,0 +1,157 @@ + + + + + channelMessagesFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

channelMessagesFilter

+ +

Filter for getting only certain types of channel messages

+

+ +
+
channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_new_messagesflags.1?trueWhether to exclude new messages from the search
rangesVector<MessageRange>A range of messages to fetch
+

Type

+

ChannelMessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html b/data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html new file mode 100644 index 0000000000..eff8a1ccfc --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html @@ -0,0 +1,132 @@ + + + + + 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 new file mode 100644 index 0000000000..c866015b20 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipant.html @@ -0,0 +1,152 @@ + + + + + channelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipant

+ +

Channel/supergroup participant

+

+ +
+
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongPariticipant user ID
dateintDate joined
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantAdmin.html b/data/corefork.telegram.org/constructor/channelParticipantAdmin.html new file mode 100644 index 0000000000..2c6230a10a --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantAdmin.html @@ -0,0 +1,190 @@ + + + + + channelParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantAdmin

+ +

Admin

+

+ +
+
channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_editflags.0?trueCan this admin promote other admins with the same permissions?
selfflags.1?trueIs this the current user
user_idlongAdmin user ID
inviter_idflags.1?longUser that invited the admin to the channel/group
promoted_bylongUser that promoted the user to admin
dateintWhen did the user join
admin_rightsChatAdminRightsAdmin rights
rankflags.2?stringThe role (rank) of the admin in the group: just an arbitrary string, admin by default
+

Type

+

ChannelParticipant

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantBanned.html b/data/corefork.telegram.org/constructor/channelParticipantBanned.html new file mode 100644 index 0000000000..8d3a9673ba --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantBanned.html @@ -0,0 +1,175 @@ + + + + + channelParticipantBanned + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantBanned

+ +

Banned/kicked user

+

+ +
+
channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
leftflags.0?trueWhether the user has left the group
peerPeerThe banned peer
kicked_bylongUser was kicked by the specified admin
dateintWhen did the user join the group
banned_rightsChatBannedRightsBanned rights
+

Type

+

ChannelParticipant

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantCreator.html b/data/corefork.telegram.org/constructor/channelParticipantCreator.html new file mode 100644 index 0000000000..22aa4c01de --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantCreator.html @@ -0,0 +1,162 @@ + + + + + channelParticipantCreator + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantCreator

+ +

Channel/supergroup creator

+

+ +
+
channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_idlongUser ID
admin_rightsChatAdminRightsCreator admin rights
rankflags.0?stringThe role (rank) of the group creator in the group: just an arbitrary string, admin by default
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantLeft.html b/data/corefork.telegram.org/constructor/channelParticipantLeft.html new file mode 100644 index 0000000000..7b86f89afc --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantLeft.html @@ -0,0 +1,147 @@ + + + + + channelParticipantLeft + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantLeft

+ +

A participant that left the channel/supergroup

+

+ +
+
channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe peer that left
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantSelf.html b/data/corefork.telegram.org/constructor/channelParticipantSelf.html new file mode 100644 index 0000000000..e012e2571b --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantSelf.html @@ -0,0 +1,157 @@ + + + + + channelParticipantSelf + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantSelf

+ +

Myself

+

+ +
+
channelParticipantSelf#35a8bfa7 flags:# via_request:flags.0?true user_id:long inviter_id:long date:int = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
inviter_idlongUser that invited me to the channel/supergroup
dateintWhen did I join the channel/supergroup
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html b/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html new file mode 100644 index 0000000000..34da486eca --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsAdmins + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsAdmins

+ +

Fetch only admin participants

+

+ +
+
channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsBanned.html b/data/corefork.telegram.org/constructor/channelParticipantsBanned.html new file mode 100644 index 0000000000..93da03a42c --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsBanned.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsBanned + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsBanned

+ +

Fetch only banned participants

+

+ +
+
channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringOptional filter for searching banned participants by name (otherwise empty)
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsBots.html b/data/corefork.telegram.org/constructor/channelParticipantsBots.html new file mode 100644 index 0000000000..a5ae0f04d6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsBots.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsBots + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsBots

+ +

Fetch only bot participants

+

+ +
+
channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsContacts.html b/data/corefork.telegram.org/constructor/channelParticipantsContacts.html new file mode 100644 index 0000000000..c7ebc2b23b --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsContacts.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsContacts

+ +

Fetch only participants that are also contacts

+

+ +
+
channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringOptional search query for searching contact participants by name
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsKicked.html b/data/corefork.telegram.org/constructor/channelParticipantsKicked.html new file mode 100644 index 0000000000..ebc05f0154 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsKicked.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsKicked + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsKicked

+ +

Fetch only kicked participants

+

+ +
+
channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringOptional filter for searching kicked participants by name (otherwise empty)
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsMentions.html b/data/corefork.telegram.org/constructor/channelParticipantsMentions.html new file mode 100644 index 0000000000..c455255985 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsMentions.html @@ -0,0 +1,161 @@ + + + + + channelParticipantsMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsMentions

+ +

This filter is used when looking for supergroup members to mention.
+This filter will automatically remove anonymous admins, and return even non-participant users that replied to a specific thread through the comment section of a channel.

+

+ +
+
channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
qflags.0?stringFilter by user name or username
top_msg_idflags.1?intLook only for users that posted in this thread
+

Type

+

ChannelParticipantsFilter

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsRecent.html b/data/corefork.telegram.org/constructor/channelParticipantsRecent.html new file mode 100644 index 0000000000..91160c33af --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsRecent.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsRecent + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsRecent

+ +

Fetch only recent participants

+

+ +
+
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsSearch.html b/data/corefork.telegram.org/constructor/channelParticipantsSearch.html new file mode 100644 index 0000000000..7cbe515197 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsSearch.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsSearch + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsSearch

+ +

Query participants by name

+

+ +
+
channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringSearch query
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channels.adminLogResults b/data/corefork.telegram.org/constructor/channels.adminLogResults new file mode 100644 index 0000000000..04de074fd2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channels.adminLogResults @@ -0,0 +1,157 @@ + + + + + channels.adminLogResults + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.adminLogResults

+ +

Admin log events

+

+ +
+
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
eventsVector<ChannelAdminLogEvent>Admin log events
chatsVector<Chat>Chats mentioned in events
usersVector<User>Users mentioned in events
+

Type

+

channels.AdminLogResults

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channels.channelParticipant b/data/corefork.telegram.org/constructor/channels.channelParticipant new file mode 100644 index 0000000000..ef4ec2ac8d --- /dev/null +++ b/data/corefork.telegram.org/constructor/channels.channelParticipant @@ -0,0 +1,157 @@ + + + + + channels.channelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.channelParticipant

+ +

Represents a channel participant

+

+ +
+
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
participantChannelParticipantThe channel participant
chatsVector<Chat>Mentioned chats
usersVector<User>Users
+

Type

+

channels.ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channels.channelParticipants b/data/corefork.telegram.org/constructor/channels.channelParticipants new file mode 100644 index 0000000000..7c36a77d4a --- /dev/null +++ b/data/corefork.telegram.org/constructor/channels.channelParticipants @@ -0,0 +1,162 @@ + + + + + channels.channelParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.channelParticipants

+ +

Represents multiple channel participants

+

+ +
+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of participants that correspond to the given query
participantsVector<ChannelParticipant>Participants
chatsVector<Chat>Mentioned chats
usersVector<User>Users mentioned in participant info
+

Type

+

channels.ChannelParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channels.channelParticipantsNotModified b/data/corefork.telegram.org/constructor/channels.channelParticipantsNotModified new file mode 100644 index 0000000000..7c7421704e --- /dev/null +++ b/data/corefork.telegram.org/constructor/channels.channelParticipantsNotModified @@ -0,0 +1,132 @@ + + + + + channels.channelParticipantsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.channelParticipantsNotModified

+ +

No new participant info could be found

+

+ +
+
channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

channels.ChannelParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channels.sendAsPeers b/data/corefork.telegram.org/constructor/channels.sendAsPeers new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channels.sendAsPeers @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chat.html b/data/corefork.telegram.org/constructor/chat.html new file mode 100644 index 0000000000..298eb9c449 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chat.html @@ -0,0 +1,227 @@ + + + + + chat + + + + + + + + + + + + + +
+ +
+
+
+ +

chat

+ +

Info about a group

+

+ +
+
chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of the group
kickedflags.1?trueWhether the current user was kicked from the group
leftflags.2?trueWhether the current user has left the group
deactivatedflags.5?trueWhether the group was migrated
call_activeflags.23?trueWhether a group call is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call
idlongID of the group
titlestringTitle
photoChatPhotoChat photo
participants_countintParticipant count
dateintDate of creation of the group
versionintUsed in basic groups to reorder updates and make sure that all of them were received.
migrated_toflags.6?InputChannelMeans this chat was upgraded to a supergroup
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in the group
default_banned_rightsflags.18?ChatBannedRightsDefault banned rights of all users in the group
+

Type

+

Chat

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatAdminRights.html b/data/corefork.telegram.org/constructor/chatAdminRights.html new file mode 100644 index 0000000000..c0ce01ae7d --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatAdminRights.html @@ -0,0 +1,205 @@ + + + + + chatAdminRights + + + + + + + + + + + + + +
+ +
+
+
+ +

chatAdminRights

+ +

Represents the rights of an admin in a channel/supergroup.

+

+ +
+
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
change_infoflags.0?trueIf set, allows the admin to modify the description of the channel/supergroup
post_messagesflags.1?trueIf set, allows the admin to post messages in the channel
edit_messagesflags.2?trueIf set, allows the admin to also edit messages from other admins in the channel
delete_messagesflags.3?trueIf set, allows the admin to also delete messages from other admins in the channel
ban_usersflags.4?trueIf set, allows the admin to ban users from the channel/supergroup
invite_usersflags.5?trueIf set, allows the admin to invite users in the channel/supergroup
pin_messagesflags.7?trueIf set, allows the admin to pin messages in the channel/supergroup
add_adminsflags.9?trueIf set, allows the admin to add other admins with the same (or more limited) permissions in the channel/supergroup
anonymousflags.10?trueWhether this admin is anonymous
manage_callflags.11?trueIf set, allows the admin to change group call/livestream settings
otherflags.12?trueSet this flag if none of the other flags are set, but you stil want the user to be an admin.
+

Type

+

ChatAdminRights

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatAdminWithInvites.html b/data/corefork.telegram.org/constructor/chatAdminWithInvites.html new file mode 100644 index 0000000000..dc83195ea1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatAdminWithInvites.html @@ -0,0 +1,157 @@ + + + + + chatAdminWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

chatAdminWithInvites

+ +

Info about chat invites generated by admins.

+

+ +
+
chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
admin_idlongThe admin
invites_countintNumber of invites generated by the admin
revoked_invites_countintNumber of revoked invites
+

Type

+

ChatAdminWithInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatBannedRights.html b/data/corefork.telegram.org/constructor/chatBannedRights.html new file mode 100644 index 0000000000..6b9b748873 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatBannedRights.html @@ -0,0 +1,216 @@ + + + + + chatBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

chatBannedRights

+ +

Represents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.

+

+ +
+
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
view_messagesflags.0?trueIf set, does not allow a user to view messages in a supergroup/channel/chat
send_messagesflags.1?trueIf set, does not allow a user to send messages in a supergroup/chat
send_mediaflags.2?trueIf set, does not allow a user to send any media in a supergroup/chat
send_stickersflags.3?trueIf set, does not allow a user to send stickers in a supergroup/chat
send_gifsflags.4?trueIf set, does not allow a user to send gifs in a supergroup/chat
send_gamesflags.5?trueIf set, does not allow a user to send games in a supergroup/chat
send_inlineflags.6?trueIf set, does not allow a user to use inline bots in a supergroup/chat
embed_linksflags.7?trueIf set, does not allow a user to embed links in the messages of a supergroup/chat
send_pollsflags.8?trueIf set, does not allow a user to send polls in a supergroup/chat
change_infoflags.10?trueIf set, does not allow any user to change the description of a supergroup/chat
invite_usersflags.15?trueIf set, does not allow any user to invite users in a supergroup/chat
pin_messagesflags.17?trueIf set, does not allow any user to pin messages in a supergroup/chat
until_dateintValidity of said permissions (it is considered forever any value less then 30 seconds or more then 366 days).
+

Type

+

ChatBannedRights

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatEmpty.html b/data/corefork.telegram.org/constructor/chatEmpty.html new file mode 100644 index 0000000000..3a5acb728a --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatEmpty.html @@ -0,0 +1,147 @@ + + + + + chatEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

chatEmpty

+ +

Empty constructor, group doesn't exist

+

+ +
+
chatEmpty#29562865 id:long = Chat;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongGroup identifier
+

Type

+

Chat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatForbidden.html b/data/corefork.telegram.org/constructor/chatForbidden.html new file mode 100644 index 0000000000..0ecc42af8c --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatForbidden.html @@ -0,0 +1,152 @@ + + + + + chatForbidden + + + + + + + + + + + + + +
+ +
+
+
+ +

chatForbidden

+ +

A group to which the user has no access. E.g., because the user was kicked from the group.

+

+ +
+
chatForbidden#6592a1a7 id:long title:string = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongUser identifier
titlestringGroup name
+

Type

+

Chat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatFull.html b/data/corefork.telegram.org/constructor/chatFull.html new file mode 100644 index 0000000000..bec3c9c54d --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatFull.html @@ -0,0 +1,231 @@ + + + + + chatFull + + + + + + + + + + + + + +
+ +
+
+
+ +

chatFull

+ +

Detailed chat info

+

+ +
+
chatFull#d18ee226 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 requests_pending:flags.17?int recent_requesters:flags.17?Vector<long> available_reactions:flags.18?Vector<string> = ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_set_usernameflags.7?trueCan we change the username of this chat
has_scheduledflags.8?trueWhether scheduled messages are available
idlongID of the chat
aboutstringAbout string for this chat
participantsChatParticipantsParticipant list
chat_photoflags.2?PhotoChat photo
notify_settingsPeerNotifySettingsNotification settings
exported_inviteflags.13?ExportedChatInviteChat invite
bot_infoflags.3?Vector<BotInfo>Info about bots that are in this chat
pinned_msg_idflags.6?intMessage ID of the last pinned message
folder_idflags.11?intPeer folder ID, for more info click here
callflags.12?InputGroupCallGroup call information
ttl_periodflags.14?intTime-To-Live of messages sent by the current user to this chat
groupcall_default_join_asflags.15?PeerWhen using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default.
theme_emoticonflags.16?stringEmoji representing a specific chat theme
+

Type

+

ChatFull

+

Related pages

+

Scheduled messages

+

Telegram allows scheduling messages

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

phone.getGroupCallJoinAs

+

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatInvite.html b/data/corefork.telegram.org/constructor/chatInvite.html new file mode 100644 index 0000000000..b680520085 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatInvite.html @@ -0,0 +1,190 @@ + + + + + chatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInvite

+ +

Chat invite info

+

+ +
+
chatInvite#300c44c1 flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true request_needed:flags.6?true title:string about:flags.5?string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channelflags.0?trueWhether this is a channel/supergroup or a normal group
broadcastflags.1?trueWhether this is a channel
publicflags.2?trueWhether this is a public channel/supergroup
megagroupflags.3?trueWhether this is a supergroup
titlestringChat/supergroup/channel title
photoPhotoChat/supergroup/channel photo
participants_countintParticipant count
participantsflags.4?Vector<User>A few of the participants that are in the group
+

Type

+

ChatInvite

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatInviteAlready.html b/data/corefork.telegram.org/constructor/chatInviteAlready.html new file mode 100644 index 0000000000..f82553aba9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatInviteAlready.html @@ -0,0 +1,147 @@ + + + + + chatInviteAlready + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInviteAlready

+ +

The user has already joined this chat

+

+ +
+
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatChatThe chat connected to the invite
+

Type

+

ChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatInviteExported.html b/data/corefork.telegram.org/constructor/chatInviteExported.html new file mode 100644 index 0000000000..73c313fb20 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatInviteExported.html @@ -0,0 +1,192 @@ + + + + + chatInviteExported + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInviteExported

+ +

Exported chat invite

+

+ +
+
chatInviteExported#ab4a819 flags:# revoked:flags.0?true permanent:flags.5?true request_needed:flags.6?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 requested:flags.7?int title:flags.8?string = ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.0?trueWhether this chat invite was revoked
permanentflags.5?trueWhether this chat invite has no expiration
linkstringChat invitation link
admin_idlongID of the admin that created this chat invite
dateintWhen was this chat invite created
start_dateflags.4?intWhen was this chat invite last modified
expire_dateflags.1?intWhen does this chat invite expire
usage_limitflags.2?intMaximum number of users that can join using this link
usageflags.3?intHow many users joined using this link
+

Type

+

ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatInviteImporter.html b/data/corefork.telegram.org/constructor/chatInviteImporter.html new file mode 100644 index 0000000000..a309a07e94 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatInviteImporter.html @@ -0,0 +1,152 @@ + + + + + chatInviteImporter + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInviteImporter

+ +

When and which user joined the chat using a chat invite

+

+ +
+
chatInviteImporter#8c5adfd9 flags:# requested:flags.0?true user_id:long date:int about:flags.2?string approved_by:flags.1?long = ChatInviteImporter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongThe user
dateintWhen did the user join
+

Type

+

ChatInviteImporter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatInvitePeek.html b/data/corefork.telegram.org/constructor/chatInvitePeek.html new file mode 100644 index 0000000000..cb47897a6d --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatInvitePeek.html @@ -0,0 +1,152 @@ + + + + + chatInvitePeek + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInvitePeek

+ +

A chat invitation that also allows peeking into the group to read messages without joining it.

+

+ +
+
chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chatChatChat information
expiresintRead-only anonymous access to this group will be revoked at this date
+

Type

+

ChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatOnlines.html b/data/corefork.telegram.org/constructor/chatOnlines.html new file mode 100644 index 0000000000..d28d7d472d --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatOnlines.html @@ -0,0 +1,147 @@ + + + + + chatOnlines + + + + + + + + + + + + + +
+ +
+
+
+ +

chatOnlines

+ +

Number of online users in a chat

+

+ +
+
chatOnlines#f041e250 onlines:int = ChatOnlines;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
onlinesintNumber of online users
+

Type

+

ChatOnlines

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatParticipant.html b/data/corefork.telegram.org/constructor/chatParticipant.html new file mode 100644 index 0000000000..63b06372c7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatParticipant.html @@ -0,0 +1,157 @@ + + + + + chatParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipant

+ +

Group member.

+

+ +
+
chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongMember user ID
inviter_idlongID of the user that added the member to the group
dateintDate added to the group
+

Type

+

ChatParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatParticipantAdmin.html b/data/corefork.telegram.org/constructor/chatParticipantAdmin.html new file mode 100644 index 0000000000..2097b198a2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatParticipantAdmin.html @@ -0,0 +1,157 @@ + + + + + chatParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipantAdmin

+ +

Chat admin

+

+ +
+
chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongID of a group member that is admin
inviter_idlongID of the user that added the member to the group
dateintDate when the user was added
+

Type

+

ChatParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatParticipantCreator.html b/data/corefork.telegram.org/constructor/chatParticipantCreator.html new file mode 100644 index 0000000000..9cf3187349 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatParticipantCreator.html @@ -0,0 +1,147 @@ + + + + + chatParticipantCreator + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipantCreator

+ +

Represents the creator of the group

+

+ +
+
chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongID of the user that created the group
+

Type

+

ChatParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatParticipants.html b/data/corefork.telegram.org/constructor/chatParticipants.html new file mode 100644 index 0000000000..296c20385d --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatParticipants.html @@ -0,0 +1,157 @@ + + + + + chatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipants

+ +

Group members.

+

+ +
+
chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup identifier
participantsVector<ChatParticipant>List of group members
versionintGroup version number
+

Type

+

ChatParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatParticipantsForbidden.html b/data/corefork.telegram.org/constructor/chatParticipantsForbidden.html new file mode 100644 index 0000000000..2a56d922b1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatParticipantsForbidden.html @@ -0,0 +1,157 @@ + + + + + chatParticipantsForbidden + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipantsForbidden

+ +

Info on members is unavailable

+

+ +
+
chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
chat_idlongGroup ID
self_participantflags.0?ChatParticipantInfo about the group membership of the current user
+

Type

+

ChatParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatPhoto.html b/data/corefork.telegram.org/constructor/chatPhoto.html new file mode 100644 index 0000000000..ca646ea2e9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatPhoto.html @@ -0,0 +1,170 @@ + + + + + chatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

chatPhoto

+ +

Group profile photo.

+

+ +
+
chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether the user has an animated profile picture
photo_idlongPhoto ID
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC where this photo is stored
+

Type

+

ChatPhoto

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatPhotoEmpty.html b/data/corefork.telegram.org/constructor/chatPhotoEmpty.html new file mode 100644 index 0000000000..daa29aa122 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatPhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + chatPhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

chatPhotoEmpty

+ +

Group photo is not set.

+

+ +
+
chatPhotoEmpty#37c1011c = ChatPhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChatPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatTheme.html b/data/corefork.telegram.org/constructor/chatTheme.html new file mode 100644 index 0000000000..f8c8c296e8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatTheme.html @@ -0,0 +1,157 @@ + + + + + chatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

chatTheme

+ +

A chat theme

+

+ +
+
Constructor schema is available as of layer 134. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji, identifying this specific chat theme
themeThemeTheme
dark_themeThemeDark mode theme
+

Type

+

ChatTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/codeSettings.html b/data/corefork.telegram.org/constructor/codeSettings.html new file mode 100644 index 0000000000..d69054a1f4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/codeSettings.html @@ -0,0 +1,166 @@ + + + + + codeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

codeSettings

+ +

Settings used by telegram servers for sending the confirm code.

+

Example implementations: telegram for android, tdlib.

+

+ +
+
codeSettings#8a6469c2 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true allow_missed_call:flags.5?true logout_tokens:flags.6?Vector<bytes> = CodeSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
allow_flashcallflags.0?trueWhether to allow phone verification via phone calls.
current_numberflags.1?truePass true if the phone number is used on the current device. Ignored if allow_flashcall is not set.
allow_app_hashflags.4?trueIf a token that will be included in eventually sent SMSs is required: required in newer versions of android, to use the android SMS receiver APIs
+

Type

+

CodeSettings

+

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/config.html b/data/corefork.telegram.org/constructor/config.html new file mode 100644 index 0000000000..f7b5029267 --- /dev/null +++ b/data/corefork.telegram.org/constructor/config.html @@ -0,0 +1,420 @@ + + + + + config + + + + + + + + + + + + + +
+ +
+
+
+ +

config

+ +

Current configuration

+

+ +
+
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
phonecalls_enabledflags.1?trueWhether phone calls can be used
default_p2p_contactsflags.3?trueWhether the client should use P2P by default for phone calls with contacts
preload_featured_stickersflags.4?trueWhether the client should preload featured stickers
ignore_phone_entitiesflags.5?trueWhether the client should ignore phone entities
revoke_pm_inboxflags.6?trueWhether incoming private messages can be deleted for both participants
blocked_modeflags.8?trueIndicates that telegram is probably censored by governments/ISPs in the current region
pfs_enabledflags.13?trueWhether pfs was used
dateintCurrent date at the server
expiresintExpiration date of this config: when it expires it'll have to be refetched using help.getConfig
test_modeBoolWhether we're connected to the test DCs
this_dcintID of the DC that returned the reply
dc_optionsVector<DcOption>DC IP list
dc_txt_domain_namestringDomain name for fetching encrypted DC list from DNS TXT record
chat_size_maxintMaximum member count for normal groups
megagroup_size_maxintMaximum member count for supergroups
forwarded_count_maxintMaximum number of messages that can be forwarded at once using messages.forwardMessages.
online_update_period_msintThe client should update its online status every N milliseconds
offline_blur_timeout_msintDelay before offline status needs to be sent to the server
offline_idle_timeout_msintTime without any user activity after which it should be treated offline
online_cloud_timeout_msintIf we are offline, but were online from some other client in last online_cloud_timeout_ms milliseconds after we had gone offline, then delay offline notification for notify_cloud_delay_ms milliseconds.
notify_cloud_delay_msintIf we are offline, but online from some other client then delay sending the offline notification for notify_cloud_delay_ms milliseconds.
notify_default_delay_msintIf some other client is online, then delay notification for notification_default_delay_ms milliseconds
push_chat_period_msintNot for client use
push_chat_limitintNot for client use
saved_gifs_limitintMaximum count of saved gifs
edit_time_limitintOnly messages with age smaller than the one specified can be edited
revoke_time_limitintOnly channel/supergroup messages with age smaller than the specified can be deleted
revoke_pm_time_limitintOnly private messages with age smaller than the specified can be deleted
rating_e_decayintExponential decay rate for computing top peer rating
stickers_recent_limitintMaximum number of recent stickers
stickers_faved_limitintMaximum number of faved stickers
channels_read_media_periodintIndicates that round videos (video notes) and voice messages sent in channels and older than the specified period must be marked as read
tmp_sessionsflags.0?intTemporary passport sessions
pinned_dialogs_count_maxintMaximum count of pinned dialogs
pinned_infolder_count_maxintMaximum count of dialogs per folder
call_receive_timeout_msintMaximum allowed outgoing ring time in VoIP calls: if the user we're calling doesn't reply within the specified time (in milliseconds), we should hang up the call
call_ring_timeout_msintMaximum allowed incoming ring time in VoIP calls: if the current user doesn't reply within the specified time (in milliseconds), the call will be automatically refused
call_connect_timeout_msintVoIP connection timeout: if the instance of libtgvoip on the other side of the call doesn't connect to our instance of libtgvoip within the specified time (in milliseconds), the call must be aborted
call_packet_timeout_msintIf during a VoIP call a packet isn't received for the specified period of time, the call must be aborted
me_url_prefixstringThe domain to use to parse in-app links.
For example t.me indicates that t.me/username links should parsed to @username, t.me/addsticker/name should be parsed to the appropriate stickerset and so on...
autoupdate_url_prefixflags.7?stringURL to use to auto-update the current app
gif_search_usernameflags.9?stringUsername of the bot to use to search for GIFs
venue_search_usernameflags.10?stringUsername of the bot to use to search for venues
img_search_usernameflags.11?stringUsername of the bot to use for image search
static_maps_providerflags.12?stringID of the map provider to use for venues
caption_length_maxintMaximum length of caption (length in utf8 codepoints)
message_length_maxintMaximum length of messages (length in utf8 codepoints)
webfile_dc_idintDC ID to use to download webfiles
suggested_lang_codeflags.2?stringSuggested language code
lang_pack_versionflags.2?intLanguage pack version
base_lang_pack_versionflags.2?intBasic language pack version
+

Type

+

Config

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

help.getConfig

+

Returns current configuration, including data center configuration.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

messages.forwardMessages

+

Forwards messages by their IDs.

+

account.updateStatus

+

Updates online user status.

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+

Telegram Passport Manual

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contact.html b/data/corefork.telegram.org/constructor/contact.html new file mode 100644 index 0000000000..e051c58369 --- /dev/null +++ b/data/corefork.telegram.org/constructor/contact.html @@ -0,0 +1,152 @@ + + + + + contact + + + + + + + + + + + + + +
+ +
+
+
+ +

contact

+ +

A contact of the current user that is registered in the system.

+

+ +
+
contact#145ade0b user_id:long mutual:Bool = Contact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
mutualBoolCurrent user is in the user's contact list
+

Type

+

Contact

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contactStatus.html b/data/corefork.telegram.org/constructor/contactStatus.html new file mode 100644 index 0000000000..9e2080e57a --- /dev/null +++ b/data/corefork.telegram.org/constructor/contactStatus.html @@ -0,0 +1,152 @@ + + + + + contactStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

contactStatus

+ +

Contact status: online / offline.

+

+ +
+
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
statusUserStatusOnline status
+

Type

+

ContactStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.blocked b/data/corefork.telegram.org/constructor/contacts.blocked new file mode 100644 index 0000000000..f3360d7d14 --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.blocked @@ -0,0 +1,157 @@ + + + + + contacts.blocked + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.blocked

+ +

Full list of blocked users.

+

+ +
+
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
+

Type

+

contacts.Blocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.blockedSlice b/data/corefork.telegram.org/constructor/contacts.blockedSlice new file mode 100644 index 0000000000..79e90bad9d --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.blockedSlice @@ -0,0 +1,162 @@ + + + + + contacts.blockedSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.blockedSlice

+ +

Incomplete list of blocked users.

+

+ +
+
contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of elements in the list
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
+

Type

+

contacts.Blocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.contacts b/data/corefork.telegram.org/constructor/contacts.contacts new file mode 100644 index 0000000000..c3dbb9fab5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.contacts @@ -0,0 +1,157 @@ + + + + + contacts.contacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.contacts

+ +

The current user's contact list and info on users.

+

+ +
+
contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
contactsVector<Contact>Contact list
saved_countintNumber of contacts that were saved successfully
usersVector<User>User list
+

Type

+

contacts.Contacts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.contactsNotModified b/data/corefork.telegram.org/constructor/contacts.contactsNotModified new file mode 100644 index 0000000000..fb1e82ce03 --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.contactsNotModified @@ -0,0 +1,132 @@ + + + + + contacts.contactsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.contactsNotModified

+ +

Contact list on the server is the same as the list on the client.

+

+ +
+
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

contacts.Contacts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.found b/data/corefork.telegram.org/constructor/contacts.found new file mode 100644 index 0000000000..e24cb936d6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.found @@ -0,0 +1,162 @@ + + + + + contacts.found + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.found

+ +

Users found by name substring and auxiliary data.

+

+ +
+
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
my_resultsVector<Peer>Personalized results
resultsVector<Peer>List of found user identifiers
chatsVector<Chat>Found chats
usersVector<User>List of users
+

Type

+

contacts.Found

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.importedContacts b/data/corefork.telegram.org/constructor/contacts.importedContacts new file mode 100644 index 0000000000..bd53fa9702 --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.importedContacts @@ -0,0 +1,165 @@ + + + + + contacts.importedContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.importedContacts

+ +

Info on succesfully imported contacts.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
importedVector<ImportedContact>List of succesfully imported contacts
popular_invitesVector<PopularContact>Popular contacts
retry_contactsVector<long>List of contact ids that could not be imported due to system limitation and will need to be imported at a later date.
Parameter added in Layer 13
usersVector<User>List of users
+

Type

+

contacts.ImportedContacts

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.resolvedPeer b/data/corefork.telegram.org/constructor/contacts.resolvedPeer new file mode 100644 index 0000000000..6800cdd2fa --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.resolvedPeer @@ -0,0 +1,157 @@ + + + + + contacts.resolvedPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.resolvedPeer

+ +

Resolved peer

+

+ +
+
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe peer
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

contacts.ResolvedPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.topPeers b/data/corefork.telegram.org/constructor/contacts.topPeers new file mode 100644 index 0000000000..41ff55da0a --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.topPeers @@ -0,0 +1,157 @@ + + + + + contacts.topPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.topPeers

+ +

Top peers

+

+ +
+
contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
categoriesVector<TopPeerCategoryPeers>Top peers by top peer category
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

contacts.TopPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.topPeersDisabled b/data/corefork.telegram.org/constructor/contacts.topPeersDisabled new file mode 100644 index 0000000000..ab6628f574 --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.topPeersDisabled @@ -0,0 +1,132 @@ + + + + + contacts.topPeersDisabled + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.topPeersDisabled

+ +

Top peers disabled

+

+ +
+
contacts.topPeersDisabled#b52c939d = contacts.TopPeers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

contacts.TopPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.topPeersNotModified b/data/corefork.telegram.org/constructor/contacts.topPeersNotModified new file mode 100644 index 0000000000..82b4afaf4a --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.topPeersNotModified @@ -0,0 +1,132 @@ + + + + + contacts.topPeersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.topPeersNotModified

+ +

Top peer info hasn't changed

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

contacts.TopPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dataJSON.html b/data/corefork.telegram.org/constructor/dataJSON.html new file mode 100644 index 0000000000..5ecfc34838 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dataJSON.html @@ -0,0 +1,147 @@ + + + + + dataJSON + + + + + + + + + + + + + +
+ +
+
+
+ +

dataJSON

+ +

Represents a json-encoded object

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
datastringJSON-encoded object
+

Type

+

DataJSON

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dcOption.html b/data/corefork.telegram.org/constructor/dcOption.html new file mode 100644 index 0000000000..ef21d84922 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dcOption.html @@ -0,0 +1,197 @@ + + + + + dcOption + + + + + + + + + + + + + +
+ +
+
+
+ +

dcOption

+ +

Data centre

+

+ +
+
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
ipv6flags.0?trueWhether the specified IP is an IPv6 address
media_onlyflags.1?trueWhether this DC should only be used to download or upload files
tcpo_onlyflags.2?trueWhether this DC only supports connection with transport obfuscation
cdnflags.3?trueWhether this is a CDN DC.
staticflags.4?trueIf set, this IP should be used when connecting through a proxy
idintDC ID
ip_addressstringIP address of DC
portintPort
secretflags.10?bytesIf the tcpo_only flag is set, specifies the secret to use when connecting using transport obfuscation
+

Type

+

DcOption

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

MTProto transports

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessage.html b/data/corefork.telegram.org/constructor/decryptedMessage.html new file mode 100644 index 0000000000..6e4bb55b35 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessage.html @@ -0,0 +1,217 @@ + + + + + decryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessage

+ +

Contents of an encrypted message.

+

+ +
+
===8===
+decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+
+===17===
+decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+
+===45===
+decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
+
+===73===
+decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields (added in layer 45)
no_webpageflags.1?trueWhether the webpage preview is disabled
silentflags.5?trueWhether this is a silent message (no notification triggered)
random_idlongRandom message ID, assigned by the author of message.
Must be equal to the ID passed to sending method.
ttlintMessage lifetime. Has higher priority than decryptedMessageActionSetMessageTTL.
Parameter added in Layer 17.
messagestringMessage text
mediaflags.9?DecryptedMessageMediaMedia content
entitiesflags.7?Vector<MessageEntity>Message entities for styled text (parameter added in layer 45)
via_bot_nameflags.11?stringSpecifies the ID of the inline bot that generated the message (parameter added in layer 45)
reply_to_random_idflags.3?longRandom message ID of the message this message replies to (parameter added in layer 45)
grouped_idflags.17?longRandom group ID, assigned by the author of message.
Multiple encrypted messages with a photo attached and with the same group ID indicate an album or grouped media (parameter added in layer 45)
+

Type

+

DecryptedMessage

+

Related pages

+

decryptedMessageActionSetMessageTTL

+

Setting of a message lifetime after reading.

+

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+

Styled text with message entities

+

How to create styled text with message entities

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionAbortKey.html b/data/corefork.telegram.org/constructor/decryptedMessageActionAbortKey.html new file mode 100644 index 0000000000..24b0b743eb --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionAbortKey.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionAbortKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionAbortKey

+ +

Abort rekeying

+

+ +
+
===20===
+decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionAcceptKey.html b/data/corefork.telegram.org/constructor/decryptedMessageActionAcceptKey.html new file mode 100644 index 0000000000..046928c11b --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionAcceptKey.html @@ -0,0 +1,160 @@ + + + + + decryptedMessageActionAcceptKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionAcceptKey

+ +

Accept new key

+

+ +
+
===20===
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID
g_bbytesB parameter, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
+

Type

+

DecryptedMessageAction

+

Related pages

+

Perfect Forward Secrecy

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionCommitKey.html b/data/corefork.telegram.org/constructor/decryptedMessageActionCommitKey.html new file mode 100644 index 0000000000..e169848ae9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionCommitKey.html @@ -0,0 +1,155 @@ + + + + + decryptedMessageActionCommitKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionCommitKey

+ +

Commit new key, see rekeying process

+

+ +
+
===20===
+decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
+

Type

+

DecryptedMessageAction

+

Related pages

+

Perfect Forward Secrecy

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionDeleteMessages.html b/data/corefork.telegram.org/constructor/decryptedMessageActionDeleteMessages.html new file mode 100644 index 0000000000..7f5f6f5b17 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionDeleteMessages.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionDeleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionDeleteMessages

+ +

Deleted messages.

+

+ +
+
===8===
+decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
random_idsVector<long>List of deleted message IDs
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionFlushHistory.html b/data/corefork.telegram.org/constructor/decryptedMessageActionFlushHistory.html new file mode 100644 index 0000000000..4c7520ebdf --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionFlushHistory.html @@ -0,0 +1,133 @@ + + + + + decryptedMessageActionFlushHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionFlushHistory

+ +

The entire message history has been deleted.

+

+ +
+
===8===
+decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionNoop.html b/data/corefork.telegram.org/constructor/decryptedMessageActionNoop.html new file mode 100644 index 0000000000..9bd2611cf9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionNoop.html @@ -0,0 +1,133 @@ + + + + + decryptedMessageActionNoop + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionNoop

+ +

NOOP action

+

+ +
+
===20===
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionNotifyLayer.html b/data/corefork.telegram.org/constructor/decryptedMessageActionNotifyLayer.html new file mode 100644 index 0000000000..f33829ad7b --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionNotifyLayer.html @@ -0,0 +1,151 @@ + + + + + decryptedMessageActionNotifyLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionNotifyLayer

+ +

A notification stating the API layer that is used by the client. You should use your current layer and take notice of the layer used on the other side of a conversation when sending messages.

+

+ +
+
===17===
+decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
layerintLayer number, must be 17 or higher (this contructor was introduced in Layer 17).
+

Type

+

DecryptedMessageAction

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionReadMessages.html b/data/corefork.telegram.org/constructor/decryptedMessageActionReadMessages.html new file mode 100644 index 0000000000..068dc3e3ab --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionReadMessages.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionReadMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionReadMessages

+ +

Messages marked as read.

+

+ +
+
===8===
+decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
random_idsVector<long>List of message IDs
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionRequestKey.html b/data/corefork.telegram.org/constructor/decryptedMessageActionRequestKey.html new file mode 100644 index 0000000000..c2bbe4e749 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionRequestKey.html @@ -0,0 +1,155 @@ + + + + + decryptedMessageActionRequestKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionRequestKey

+ +

Request rekeying, see rekeying process

+

+ +
+
===20===
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID
g_abytesg_a, see rekeying process
+

Type

+

DecryptedMessageAction

+

Related pages

+

Perfect Forward Secrecy

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html b/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html new file mode 100644 index 0000000000..237737768e --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html @@ -0,0 +1,155 @@ + + + + + decryptedMessageActionResend + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionResend

+ +

Request for the other party in a Secret Chat to automatically resend a contiguous range of previously sent messages, as explained in Sequence number is Secret Chats.

+

+ +
+
===17===
+decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
start_seq_nointout_seq_no of the first message to be resent, with correct parity
end_seq_nointout_seq_no of the last message to be resent, with same parity.
+

Type

+

DecryptedMessageAction

+

Related pages

+

Sequence numbers in Secret Chats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html b/data/corefork.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html new file mode 100644 index 0000000000..a23af94099 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionScreenshotMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionScreenshotMessages

+ +

A screenshot was taken.

+

+ +
+
===8===
+decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
random_idsVector<long>List of affected message ids (that appeared on the screenshot)
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html b/data/corefork.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html new file mode 100644 index 0000000000..741671371a --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html @@ -0,0 +1,149 @@ + + + + + decryptedMessageActionSetMessageTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionSetMessageTTL

+ +

Setting of a message lifetime after reading.

+

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

+

+ +
+
===8===
+decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
ttl_secondsintLifetime in seconds
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionTyping.html b/data/corefork.telegram.org/constructor/decryptedMessageActionTyping.html new file mode 100644 index 0000000000..1b4fa42f3c --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionTyping.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionTyping

+ +

User is preparing a message: typing, recording, uploading, etc.

+

+ +
+
===17===
+decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
actionSendMessageActionType of action
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageLayer.html b/data/corefork.telegram.org/constructor/decryptedMessageLayer.html new file mode 100644 index 0000000000..4228c7af7f --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageLayer.html @@ -0,0 +1,173 @@ + + + + + decryptedMessageLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageLayer

+ +

Sets the layer number for the contents of an encrypted message.

+

+ +
+
===17===
+decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_bytesbytesSet of random bytes to prevent content recognition in short encrypted messages.
Clients are required to check that there are at least 15 random bytes included in each message. Messages with less than 15 random bytes must be ignored.
Parameter moved here from decryptedMessage in Layer 17.
layerintLayer number. Mimimal value - 17 (the layer in which the constructor was added).
in_seq_noint2x the number of messages in the sender's inbox (including deleted and service messages), incremented by 1 if current user was not the chat creator
Parameter added in Layer 17.
out_seq_noint2x the number of messages in the recipient's inbox (including deleted and service messages), incremented by 1 if current user was the chat creator
Parameter added in Layer 17.
messageDecryptedMessageThe content of message itself
+

Type

+

DecryptedMessageLayer

+

Related pages

+

decryptedMessage

+

Contents of an encrypted message.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaAudio.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaAudio.html new file mode 100644 index 0000000000..c13f3d942f --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaAudio.html @@ -0,0 +1,174 @@ + + + + + decryptedMessageMediaAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaAudio

+ +

Audio file attached to a secret chat message.

+

+ +
+
===8===
+decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===17===
+decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
durationintAudio duration in seconds
mime_typestringMIME-type of the audio file
Parameter added in Layer 13.
sizeintFile size
keybytesKey to decrypt the attached media file
ivbytesInitialization vector
+

Type

+

DecryptedMessageMedia

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaContact.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaContact.html new file mode 100644 index 0000000000..6197e63b5c --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaContact.html @@ -0,0 +1,163 @@ + + + + + decryptedMessageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaContact

+ +

Contact attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
user_idintTelegram User ID of signed-up contact
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaDocument.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaDocument.html new file mode 100644 index 0000000000..cff9074c76 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaDocument.html @@ -0,0 +1,191 @@ + + + + + decryptedMessageMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaDocument

+ +

Document attached to a message in a secret chat.

+

+ +
+
===8===
+decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
thumbbytesThumbnail-file contents (JPEG-file, quality 55, set in a 90x90 square)
thumb_wintThumbnail width
thumb_hintThumbnail height
mime_typestringFile MIME-type
sizeintDocument size
keybytesKey to decrypt the attached document file
ivbytesInitialization
attributesVector<DocumentAttribute>Document attributes for media types
captionstringCaption
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaEmpty.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaEmpty.html new file mode 100644 index 0000000000..2ee6b7f806 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaEmpty.html @@ -0,0 +1,133 @@ + + + + + decryptedMessageMediaEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaEmpty

+ +

Empty constructor, no media content.

+

+ +
+
===8===
+decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaExternalDocument.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaExternalDocument.html new file mode 100644 index 0000000000..15b8b87db3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaExternalDocument.html @@ -0,0 +1,183 @@ + + + + + decryptedMessageMediaExternalDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaExternalDocument

+ +

Non-e2e documented forwarded from non-secret chat

+

+ +
+
===23===
+decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID
access_hashlongaccess hash
dateintDate
mime_typestringMime type
sizeintSize
thumbPhotoSizeThumbnail
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes for media types
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html new file mode 100644 index 0000000000..969750f202 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html @@ -0,0 +1,153 @@ + + + + + decryptedMessageMediaGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaGeoPoint

+ +

GeoPont attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
latdoubleLatitude of point
longdoubleLongtitude of point
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html new file mode 100644 index 0000000000..11474e72d9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html @@ -0,0 +1,191 @@ + + + + + decryptedMessageMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaPhoto

+ +

Photo attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
thumbbytesContent of thumbnail file (JPEGfile, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
wintPhoto width
hintPhoto height
sizeintSize of the photo in bytes
keybytesKey to decrypt an attached file with a full version
ivbytesInitialization vector
captionstringCaption
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaVenue.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaVenue.html new file mode 100644 index 0000000000..f2b33d3926 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaVenue.html @@ -0,0 +1,173 @@ + + + + + decryptedMessageMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaVenue

+ +

Venue

+

+ +
+
===45===
+decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
latdoubleLatitude of venue
longdoubleLongitude of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html new file mode 100644 index 0000000000..8ada4afd73 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html @@ -0,0 +1,207 @@ + + + + + decryptedMessageMediaVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaVideo

+ +

Video attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===17===
+decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
thumbbytesContent of thumbnail file (JPEG file, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
durationintDuration of video in seconds
mime_typestringMIME-type of the video file
Parameter added in Layer 17.
wintImage width
hintImage height
sizeintFile size
keybytesKey to decrypt the attached video file
ivbytesInitialization vector
captionstringCaption
+

Type

+

DecryptedMessageMedia

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html new file mode 100644 index 0000000000..224789f8e8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageMediaWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaWebPage

+ +

Webpage preview

+

+ +
+
===45===
+decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL of webpage
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageService.html b/data/corefork.telegram.org/constructor/decryptedMessageService.html new file mode 100644 index 0000000000..bc3f98120f --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageService.html @@ -0,0 +1,156 @@ + + + + + decryptedMessageService + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageService

+ +

Contents of an encrypted service message.

+

+ +
+
===8===
+decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+
+===17===
+decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_idlongRandom message ID, assigned by the message author.
Must be equal to the ID passed to the sending method.
actionDecryptedMessageActionAction relevant to the service message
+

Type

+

DecryptedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dialog.html b/data/corefork.telegram.org/constructor/dialog.html new file mode 100644 index 0000000000..882442e054 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialog.html @@ -0,0 +1,214 @@ + + + + + dialog + + + + + + + + + + + + + +
+ +
+
+
+ +

dialog

+ +

Chat

+

+ +
+
dialog#a8edd0f5 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 unread_reactions_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 new file mode 100644 index 0000000000..1abc5df506 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialogFilter.html @@ -0,0 +1,220 @@ + + + + + dialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogFilter

+ +

Dialog filter AKA folder

+

+ +
+
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to include all contacts in this folder
non_contactsflags.1?trueWhether to include all non-contacts in this folder
groupsflags.2?trueWhether to include all groups in this folder
broadcastsflags.3?trueWhether to include all channels in this folder
botsflags.4?trueWhether to include all bots in this folder
exclude_mutedflags.11?trueWhether to exclude muted chats from this folder
exclude_readflags.12?trueWhether to exclude read chats from this folder
exclude_archivedflags.13?trueWhether to exclude archived chats from this folder
idintFolder ID
titlestringFolder name
emoticonflags.25?stringFolder emoticon
pinned_peersVector<InputPeer>Pinned chats, folders can have unlimited pinned chats
include_peersVector<InputPeer>Include the following chats in this folder
exclude_peersVector<InputPeer>Exclude the following chats from this folder
+

Type

+

DialogFilter

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dialogFilterSuggested.html b/data/corefork.telegram.org/constructor/dialogFilterSuggested.html new file mode 100644 index 0000000000..00845e2375 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialogFilterSuggested.html @@ -0,0 +1,155 @@ + + + + + dialogFilterSuggested + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogFilterSuggested

+ +

Suggested folders

+

+ +
+
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
filterDialogFilterFolder info
descriptionstringFolder description
+

Type

+

DialogFilterSuggested

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dialogFolder.html b/data/corefork.telegram.org/constructor/dialogFolder.html new file mode 100644 index 0000000000..53b28caa47 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialogFolder.html @@ -0,0 +1,187 @@ + + + + + dialogFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogFolder

+ +

Dialog in folder

+

+ +
+
dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs this folder pinned
folderFolderThe folder
peerPeerPeer in folder
top_messageintLatest message ID of dialog
unread_muted_peers_countintNumber of unread muted peers in folder
unread_unmuted_peers_countintNumber of unread unmuted peers in folder
unread_muted_messages_countintNumber of unread messages from muted peers in folder
unread_unmuted_messages_countintNumber of unread messages from unmuted peers in folder
+

Type

+

Dialog

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dialogPeer.html b/data/corefork.telegram.org/constructor/dialogPeer.html new file mode 100644 index 0000000000..8c97ba5258 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialogPeer.html @@ -0,0 +1,147 @@ + + + + + dialogPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogPeer

+ +

Peer

+

+ +
+
dialogPeer#e56dbf05 peer:Peer = DialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
+

Type

+

DialogPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dialogPeerFolder.html b/data/corefork.telegram.org/constructor/dialogPeerFolder.html new file mode 100644 index 0000000000..15318e8ddf --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialogPeerFolder.html @@ -0,0 +1,150 @@ + + + + + dialogPeerFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogPeerFolder

+ +

Peer folder

+

+ +
+
dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Type

+

DialogPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/disabledFeature.html b/data/corefork.telegram.org/constructor/disabledFeature.html new file mode 100644 index 0000000000..ab493dd00a --- /dev/null +++ b/data/corefork.telegram.org/constructor/disabledFeature.html @@ -0,0 +1,163 @@ + + + + + disabledFeature + + + + + + + + + + + + + +
+ +
+
+
+ +

disabledFeature

+ +

A disabled feature

+

+ +
+
Constructor schema is available as of layer 76. Switch »

+

Parameters

+ + + + + + + + + + + + + +
featurestringThe feature that was disabled
descriptionstringDescription
+

Type

+

DisabledFeature

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/document.html b/data/corefork.telegram.org/constructor/document.html new file mode 100644 index 0000000000..a9b825ede8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/document.html @@ -0,0 +1,200 @@ + + + + + document + + + + + + + + + + + + + +
+ +
+
+
+ +

document

+ +

Document

+

+ +
+
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idlongDocument ID
access_hashlongCheck sum, dependant on document ID
file_referencebytesFile reference
dateintCreation date
mime_typestringMIME type
sizeintSize
thumbsflags.0?Vector<PhotoSize>Thumbnails
video_thumbsflags.1?Vector<VideoSize>Video thumbnails
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes
+

Type

+

Document

+

Related pages

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeAnimated.html b/data/corefork.telegram.org/constructor/documentAttributeAnimated.html new file mode 100644 index 0000000000..aafad64c19 --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeAnimated.html @@ -0,0 +1,132 @@ + + + + + documentAttributeAnimated + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeAnimated

+ +

Defines an animated GIF

+

+ +
+
documentAttributeAnimated#11b58939 = DocumentAttribute;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeAudio.html b/data/corefork.telegram.org/constructor/documentAttributeAudio.html new file mode 100644 index 0000000000..d3dd51b2a1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeAudio.html @@ -0,0 +1,172 @@ + + + + + documentAttributeAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeAudio

+ +

Represents an audio file

+

+ +
+
documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
voiceflags.10?trueWhether this is a voice message
durationintDuration in seconds
titleflags.0?stringName of song
performerflags.1?stringPerformer
waveformflags.2?bytesWaveform
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeFilename.html b/data/corefork.telegram.org/constructor/documentAttributeFilename.html new file mode 100644 index 0000000000..5f30e98f2b --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeFilename.html @@ -0,0 +1,147 @@ + + + + + documentAttributeFilename + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeFilename

+ +

A simple document with a file name

+

+ +
+
documentAttributeFilename#15590068 file_name:string = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
file_namestringThe file name
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html b/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html new file mode 100644 index 0000000000..8f0801708a --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html @@ -0,0 +1,132 @@ + + + + + documentAttributeHasStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeHasStickers

+ +

Whether the current document has stickers attached

+

+ +
+
documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeImageSize.html b/data/corefork.telegram.org/constructor/documentAttributeImageSize.html new file mode 100644 index 0000000000..6b9d062980 --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeImageSize.html @@ -0,0 +1,152 @@ + + + + + documentAttributeImageSize + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeImageSize

+ +

Defines the width and height of an image uploaded as document

+

+ +
+
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
wintWidth of image
hintHeight of image
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeSticker.html b/data/corefork.telegram.org/constructor/documentAttributeSticker.html new file mode 100644 index 0000000000..f9883cb7b9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeSticker.html @@ -0,0 +1,167 @@ + + + + + documentAttributeSticker + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeSticker

+ +

Defines a sticker

+

+ +
+
documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
maskflags.1?trueWhether this is a mask sticker
altstringAlternative emoji representation of sticker
stickersetInputStickerSetAssociated stickerset
mask_coordsflags.0?MaskCoordsMask coordinates (if this is a mask sticker, attached to a photo)
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeVideo.html b/data/corefork.telegram.org/constructor/documentAttributeVideo.html new file mode 100644 index 0000000000..0c8f900983 --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeVideo.html @@ -0,0 +1,172 @@ + + + + + documentAttributeVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeVideo

+ +

Defines a video

+

+ +
+
documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
round_messageflags.0?trueWhether this is a round video
supports_streamingflags.1?trueWhether the video supports streaming
durationintDuration in seconds
wintVideo width
hintVideo height
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentEmpty.html b/data/corefork.telegram.org/constructor/documentEmpty.html new file mode 100644 index 0000000000..151a4c0fc7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentEmpty.html @@ -0,0 +1,147 @@ + + + + + documentEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

documentEmpty

+ +

Empty constructor, document doesn't exist.

+

+ +
+
documentEmpty#36f8c871 id:long = Document;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID or 0
+

Type

+

Document

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/draftMessage.html b/data/corefork.telegram.org/constructor/draftMessage.html new file mode 100644 index 0000000000..397c3945e1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/draftMessage.html @@ -0,0 +1,177 @@ + + + + + draftMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

draftMessage

+ +

Represents a message draft.

+

+ +
+
draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueWhether no webpage preview will be generated
reply_to_msg_idflags.0?intThe message this message will reply to
messagestringThe draft
entitiesflags.3?Vector<MessageEntity>Message entities for styled text.
dateintDate of last update of the draft.
+

Type

+

DraftMessage

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/draftMessageEmpty.html b/data/corefork.telegram.org/constructor/draftMessageEmpty.html new file mode 100644 index 0000000000..0f0b24c305 --- /dev/null +++ b/data/corefork.telegram.org/constructor/draftMessageEmpty.html @@ -0,0 +1,152 @@ + + + + + draftMessageEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

draftMessageEmpty

+ +

Empty draft

+

+ +
+
draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
dateflags.0?intWhen was the draft last updated
+

Type

+

DraftMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/emojiKeyword.html b/data/corefork.telegram.org/constructor/emojiKeyword.html new file mode 100644 index 0000000000..fa1943f40e --- /dev/null +++ b/data/corefork.telegram.org/constructor/emojiKeyword.html @@ -0,0 +1,152 @@ + + + + + emojiKeyword + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiKeyword

+ +

Emoji keyword

+

+ +
+
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis associated to keyword
+

Type

+

EmojiKeyword

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/emojiKeywordDeleted.html b/data/corefork.telegram.org/constructor/emojiKeywordDeleted.html new file mode 100644 index 0000000000..5149e912ab --- /dev/null +++ b/data/corefork.telegram.org/constructor/emojiKeywordDeleted.html @@ -0,0 +1,152 @@ + + + + + emojiKeywordDeleted + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiKeywordDeleted

+ +

Deleted emoji keyword

+

+ +
+
emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis that were associated to keyword
+

Type

+

EmojiKeyword

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/emojiKeywordsDifference.html b/data/corefork.telegram.org/constructor/emojiKeywordsDifference.html new file mode 100644 index 0000000000..ac55cad542 --- /dev/null +++ b/data/corefork.telegram.org/constructor/emojiKeywordsDifference.html @@ -0,0 +1,162 @@ + + + + + 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 new file mode 100644 index 0000000000..c7d437cbcf --- /dev/null +++ b/data/corefork.telegram.org/constructor/emojiLanguage.html @@ -0,0 +1,147 @@ + + + + + emojiLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiLanguage

+ +

Emoji language

+

+ +
+
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Type

+

EmojiLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/emojiURL.html b/data/corefork.telegram.org/constructor/emojiURL.html new file mode 100644 index 0000000000..f20bac3faf --- /dev/null +++ b/data/corefork.telegram.org/constructor/emojiURL.html @@ -0,0 +1,147 @@ + + + + + emojiURL + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiURL

+ +

An HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

+

+ +
+
emojiURL#a575739d url:string = EmojiURL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+

Type

+

EmojiURL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedChat.html b/data/corefork.telegram.org/constructor/encryptedChat.html new file mode 100644 index 0000000000..5ca4532384 --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedChat.html @@ -0,0 +1,177 @@ + + + + + encryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChat

+ +

Encrypted chat

+

+ +
+
encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintChat ID
access_hashlongCheck sum dependant on the user ID
dateintDate chat was created
admin_idlongChat creator ID
participant_idlongID of the second chat participant
g_a_or_bbytesB = g ^ b mod p, if the currently authorized user is the chat's creator,
or A = g ^ a mod p otherwise
See Wikipedia for more info
key_fingerprintlong64-bit fingerprint of received key
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedChatDiscarded.html b/data/corefork.telegram.org/constructor/encryptedChatDiscarded.html new file mode 100644 index 0000000000..67c6280c80 --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedChatDiscarded.html @@ -0,0 +1,157 @@ + + + + + encryptedChatDiscarded + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatDiscarded

+ +

Discarded or deleted chat.

+

+ +
+
encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
history_deletedflags.0?trueWhether both users of this secret chat should also remove all of its messages
idintChat ID
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedChatEmpty.html b/data/corefork.telegram.org/constructor/encryptedChatEmpty.html new file mode 100644 index 0000000000..c42c2b49ee --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedChatEmpty.html @@ -0,0 +1,147 @@ + + + + + encryptedChatEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatEmpty

+ +

Empty constructor.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idintChat ID
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedChatRequested.html b/data/corefork.telegram.org/constructor/encryptedChatRequested.html new file mode 100644 index 0000000000..e8ff7c3c31 --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedChatRequested.html @@ -0,0 +1,185 @@ + + + + + encryptedChatRequested + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatRequested

+ +

Request to create an encrypted chat.

+

+ +
+
encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
idintChat ID
access_hashlongCheck sum depending on user ID
dateintChat creation date
admin_idlongChat creator ID
participant_idlongID of second chat participant
g_abytesA = g ^ a mod p, see Wikipedia
+

Type

+

EncryptedChat

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedChatWaiting.html b/data/corefork.telegram.org/constructor/encryptedChatWaiting.html new file mode 100644 index 0000000000..96a384456a --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedChatWaiting.html @@ -0,0 +1,167 @@ + + + + + encryptedChatWaiting + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatWaiting

+ +

Chat waiting for approval of second participant.

+

+ +
+
encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintChat ID
access_hashlongChecking sum depending on user ID
dateintDate of chat creation
admin_idlongChat creator ID
participant_idlongID of second chat participant
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedFile.html b/data/corefork.telegram.org/constructor/encryptedFile.html new file mode 100644 index 0000000000..149b046635 --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedFile.html @@ -0,0 +1,167 @@ + + + + + encryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedFile

+ +

Encrypted file.

+

+ +
+
encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongFile ID
access_hashlongChecking sum depending on user ID
sizeintFile size in bytes
dc_idintNumber of data centre
key_fingerprintint32-bit fingerprint of key used for file encryption
+

Type

+

EncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedFileEmpty.html b/data/corefork.telegram.org/constructor/encryptedFileEmpty.html new file mode 100644 index 0000000000..8c057bd4cc --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedFileEmpty.html @@ -0,0 +1,132 @@ + + + + + encryptedFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedFileEmpty

+ +

Empty constructor, unexisitng file.

+

+ +
+
encryptedFileEmpty#c21f497e = EncryptedFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

EncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedMessage.html b/data/corefork.telegram.org/constructor/encryptedMessage.html new file mode 100644 index 0000000000..62cd050073 --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedMessage.html @@ -0,0 +1,170 @@ + + + + + encryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedMessage

+ +

Encrypted message.

+

+ +
+
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
fileEncryptedFileAttached encrypted file
+

Type

+

EncryptedMessage

+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedMessageService.html b/data/corefork.telegram.org/constructor/encryptedMessageService.html new file mode 100644 index 0000000000..8121e556d2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedMessageService.html @@ -0,0 +1,165 @@ + + + + + encryptedMessageService + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedMessageService

+ +

Encrypted service message

+

+ +
+
encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
+

Type

+

EncryptedMessage

+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/error.html b/data/corefork.telegram.org/constructor/error.html new file mode 100644 index 0000000000..3c5a8e7f6b --- /dev/null +++ b/data/corefork.telegram.org/constructor/error.html @@ -0,0 +1,152 @@ + + + + + error + + + + + + + + + + + + + +
+ +
+
+
+ +

error

+ +

Error.

+

+ +
+
error#c4b9f9bb code:int text:string = Error;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
codeintError code
textstringMessage
+

Type

+

Error

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/exportedMessageLink.html b/data/corefork.telegram.org/constructor/exportedMessageLink.html new file mode 100644 index 0000000000..8dc1091ce2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/exportedMessageLink.html @@ -0,0 +1,152 @@ + + + + + exportedMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

exportedMessageLink

+ +

Link to a message in a supergroup/channel

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
linkstringURL
htmlstringEmbed code
+

Type

+

ExportedMessageLink

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/fileHash.html b/data/corefork.telegram.org/constructor/fileHash.html new file mode 100644 index 0000000000..d40a2a6d25 --- /dev/null +++ b/data/corefork.telegram.org/constructor/fileHash.html @@ -0,0 +1,171 @@ + + + + + FileHash + + + + + + + + + + + + + +
+ +
+
+
+ +

FileHash

+ +

SHA256 Hash of an uploaded file, to be checked for validity after download

+

+ +
+
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset from where to start computing SHA-256 hash
limitintLength
hashbytesSHA-256 Hash of file chunk, to be checked for validity after download
+

Type

+

FileHash

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/fileLocation.html b/data/corefork.telegram.org/constructor/fileLocation.html new file mode 100644 index 0000000000..793e5acf14 --- /dev/null +++ b/data/corefork.telegram.org/constructor/fileLocation.html @@ -0,0 +1,182 @@ + + + + + fileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

fileLocation

+ +

File location.

+

+ +
+
Constructor schema is available as of layer 86. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintNumber of the data center holding the file
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
+

Type

+

FileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/fileLocationUnavailable.html b/data/corefork.telegram.org/constructor/fileLocationUnavailable.html new file mode 100644 index 0000000000..6b36910c9e --- /dev/null +++ b/data/corefork.telegram.org/constructor/fileLocationUnavailable.html @@ -0,0 +1,179 @@ + + + + + fileLocationUnavailable + + + + + + + + + + + + + +
+ +
+
+
+ +

fileLocationUnavailable

+ +

File is currently unavailable.

+

+ +
+
Constructor schema is available as of layer 98. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
+

Type

+

FileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/folder.html b/data/corefork.telegram.org/constructor/folder.html new file mode 100644 index 0000000000..fff4e51317 --- /dev/null +++ b/data/corefork.telegram.org/constructor/folder.html @@ -0,0 +1,177 @@ + + + + + folder + + + + + + + + + + + + + +
+ +
+
+
+ +

folder

+ +

Folder

+

+ +
+
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
autofill_new_broadcastsflags.0?trueAutomatically add new channels to this folder
autofill_public_groupsflags.1?trueAutomatically add joined new public supergroups to this folder
autofill_new_correspondentsflags.2?trueAutomatically add new private chats to this folder
idintFolder ID
titlestringFolder title
photoflags.3?ChatPhotoFolder picture
+

Type

+

Folder

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/folderPeer.html b/data/corefork.telegram.org/constructor/folderPeer.html new file mode 100644 index 0000000000..61540c169d --- /dev/null +++ b/data/corefork.telegram.org/constructor/folderPeer.html @@ -0,0 +1,155 @@ + + + + + folderPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

folderPeer

+ +

Peer in a folder

+

+ +
+
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerFolder peer info
folder_idintPeer folder ID, for more info click here
+

Type

+

FolderPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/game.html b/data/corefork.telegram.org/constructor/game.html new file mode 100644 index 0000000000..1a7751407b --- /dev/null +++ b/data/corefork.telegram.org/constructor/game.html @@ -0,0 +1,182 @@ + + + + + game + + + + + + + + + + + + + +
+ +
+
+
+ +

game

+ +

Indicates an already sent game

+

+ +
+
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idlongID of the game
access_hashlongAccess hash of the game
short_namestringShort name for the game
titlestringTitle of the game
descriptionstringGame description
photoPhotoGame preview
documentflags.0?DocumentOptional attached document
+

Type

+

Game

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/geoPoint.html b/data/corefork.telegram.org/constructor/geoPoint.html new file mode 100644 index 0000000000..8f4897d078 --- /dev/null +++ b/data/corefork.telegram.org/constructor/geoPoint.html @@ -0,0 +1,167 @@ + + + + + geoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

geoPoint

+ +

GeoPoint.

+

+ +
+
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
longdoubleLongtitude
latdoubleLatitude
access_hashlongAccess hash
accuracy_radiusflags.0?intThe estimated horizontal accuracy of the location, in meters; as defined by the sender.
+

Type

+

GeoPoint

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/geoPointEmpty.html b/data/corefork.telegram.org/constructor/geoPointEmpty.html new file mode 100644 index 0000000000..c89302fb0f --- /dev/null +++ b/data/corefork.telegram.org/constructor/geoPointEmpty.html @@ -0,0 +1,132 @@ + + + + + geoPointEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

geoPointEmpty

+ +

Empty constructor.

+

+ +
+
geoPointEmpty#1117dd5f = GeoPoint;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

GeoPoint

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/globalPrivacySettings.html b/data/corefork.telegram.org/constructor/globalPrivacySettings.html new file mode 100644 index 0000000000..e1151f1236 --- /dev/null +++ b/data/corefork.telegram.org/constructor/globalPrivacySettings.html @@ -0,0 +1,152 @@ + + + + + globalPrivacySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

globalPrivacySettings

+ +

Global privacy settings

+

+ +
+
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
archive_and_mute_new_noncontact_peersflags.0?BoolWhether to archive and mute new chats from non-contacts
+

Type

+

GlobalPrivacySettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/groupCall.html b/data/corefork.telegram.org/constructor/groupCall.html new file mode 100644 index 0000000000..54940b8b27 --- /dev/null +++ b/data/corefork.telegram.org/constructor/groupCall.html @@ -0,0 +1,230 @@ + + + + + groupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCall

+ +

Info about a group call or livestream

+

+ +
+
groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true rtmp_stream:flags.12?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
join_mutedflags.1?trueWhether the user should be muted upon joining the call
can_change_join_mutedflags.2?trueWhether the current user can change the value of the join_muted flag using phone.toggleGroupCallSettings
join_date_ascflags.6?trueSpecifies the ordering to use when locally sorting by date and displaying in the UI group call participants.
schedule_start_subscribedflags.8?trueWhether we subscribed to the scheduled call
can_start_videoflags.9?trueWhether you can start streaming video into the call
record_video_activeflags.11?trueWhether the group call is currently being recorded
idlongGroup call ID
access_hashlongGroup call access hash
participants_countintParticipant count
titleflags.3?stringGroup call title
stream_dc_idflags.4?intDC ID to be used for livestream chunks
record_start_dateflags.5?intWhen was the recording started
schedule_dateflags.7?intWhen is the call scheduled to start
unmuted_video_countflags.10?intNumber of people currently streaming video into the call
unmuted_video_limitintMaximum number of people allowed to stream video into the call
versionintVersion
+

Type

+

GroupCall

+

Related pages

+

phone.toggleGroupCallSettings

+

Change group call settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/groupCallDiscarded.html b/data/corefork.telegram.org/constructor/groupCallDiscarded.html new file mode 100644 index 0000000000..ab0f27bf43 --- /dev/null +++ b/data/corefork.telegram.org/constructor/groupCallDiscarded.html @@ -0,0 +1,157 @@ + + + + + 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 new file mode 100644 index 0000000000..e2a6766465 --- /dev/null +++ b/data/corefork.telegram.org/constructor/groupCallParticipant.html @@ -0,0 +1,247 @@ + + + + + groupCallParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCallParticipant

+ +

Info about a group call participant

+

+ +
+
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
mutedflags.0?trueWhether the participant is muted
leftflags.1?trueWhether the participant has left
can_self_unmuteflags.2?trueWhether the participant can unmute themselves
just_joinedflags.4?trueWhether the participant has just joined
versionedflags.5?trueIf set, and updateGroupCallParticipants.version < locally stored call.version, info about this participant should be ignored. If (...), and updateGroupCallParticipants.version > call.version+1, the participant list should be refetched using phone.getGroupParticipants.
minflags.8?trueIf not set, the volume and muted_by_you fields can be safely used to overwrite locally cached information; otherwise, volume will contain valid information only if volume_by_admin is set both in the cache and in the received constructor.
muted_by_youflags.9?trueWhether this participant was muted by the current user
volume_by_adminflags.10?trueWhether our volume can only changed by an admin
selfflags.12?trueWhether this participant is the current user
video_joinedflags.15?trueWhether this participant is currently broadcasting video
peerPeerPeer information
dateintWhen did this participant join the group call
active_dateflags.3?intWhen was this participant last active in the group call
sourceintSource ID
volumeflags.7?intVolume, if not set the volume is set to 100%.
aboutflags.11?stringInfo about this participant
raise_hand_ratingflags.13?longSpecifies the UI visualization order of peers with raised hands: peers with a higher rating should be showed first in the list.
videoflags.6?GroupCallParticipantVideoInfo about the video stream the participant is currently broadcasting
presentationflags.14?GroupCallParticipantVideoInfo about the screen sharing stream the participant is currently broadcasting
+

Type

+

GroupCallParticipant

+

Related pages

+

updateGroupCallParticipants

+

The participant list of a certain group call has changed

+

phone.getGroupParticipants

+

Get group call participants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/groupCallParticipantVideo.html b/data/corefork.telegram.org/constructor/groupCallParticipantVideo.html new file mode 100644 index 0000000000..fc60ae9756 --- /dev/null +++ b/data/corefork.telegram.org/constructor/groupCallParticipantVideo.html @@ -0,0 +1,167 @@ + + + + + groupCallParticipantVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCallParticipantVideo

+ +

Info about a video stream

+

+ +
+
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pausedflags.0?trueWhether the stream is currently paused
endpointstringEndpoint
source_groupsVector<GroupCallParticipantVideoSourceGroup>Source groups
audio_sourceflags.1?intAudio source ID
+

Type

+

GroupCallParticipantVideo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html b/data/corefork.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html new file mode 100644 index 0000000000..f7fb729082 --- /dev/null +++ b/data/corefork.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html @@ -0,0 +1,152 @@ + + + + + groupCallParticipantVideoSourceGroup + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCallParticipantVideoSourceGroup

+ +

Describes a group of video synchronization source identifiers

+

+ +
+
groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
semanticsstringSDP semantics
sourcesVector<int>Source IDs
+

Type

+

GroupCallParticipantVideoSourceGroup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.appUpdate b/data/corefork.telegram.org/constructor/help.appUpdate new file mode 100644 index 0000000000..05cfb4253b --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.appUpdate @@ -0,0 +1,190 @@ + + + + + help.appUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.appUpdate

+ +

An update is available for the application.

+

+ +
+
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_not_skipflags.0?trueUnskippable, the new info must be shown to the user (with a popup or something else)
idintUpdate ID
versionstringNew version name
textstringText description of the update
entitiesVector<MessageEntity>Message entities for styled text
documentflags.1?DocumentApplication binary
urlflags.2?stringApplication download URL
stickerflags.3?DocumentAssociated sticker
+

Type

+

help.AppUpdate

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.countriesList b/data/corefork.telegram.org/constructor/help.countriesList new file mode 100644 index 0000000000..b719eb5bc8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.countriesList @@ -0,0 +1,155 @@ + + + + + help.countriesList + + + + + + + + + + + + + +
+ +
+
+
+ +

help.countriesList

+ +

Name, ISO code, localized name and phone codes/patterns of all available countries

+

+ +
+
help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countriesVector<help.Country>Name, ISO code, localized name and phone codes/patterns of all available countries
hashintHash for pagination, for more info click here
+

Type

+

help.CountriesList

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.countriesListNotModified b/data/corefork.telegram.org/constructor/help.countriesListNotModified new file mode 100644 index 0000000000..8c737cf307 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.countriesListNotModified @@ -0,0 +1,132 @@ + + + + + help.countriesListNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

help.countriesListNotModified

+ +

The country list has not changed

+

+ +
+
help.countriesListNotModified#93cc1f32 = help.CountriesList;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.CountriesList

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.country b/data/corefork.telegram.org/constructor/help.country new file mode 100644 index 0000000000..21bf1615ad --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.country @@ -0,0 +1,172 @@ + + + + + help.country + + + + + + + + + + + + + +
+ +
+
+
+ +

help.country

+ +

Name, ISO code, localized name and phone codes/patterns of a specific country

+

+ +
+
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
hiddenflags.0?trueWhether this country should not be shown in the list
iso2stringISO code of country
default_namestringName of the country in the country's language
nameflags.1?stringName of the country in the user's language, if different from the original name
country_codesVector<help.CountryCode>Phone codes/patterns
+

Type

+

help.Country

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.countryCode b/data/corefork.telegram.org/constructor/help.countryCode new file mode 100644 index 0000000000..71864986fc --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.countryCode @@ -0,0 +1,162 @@ + + + + + help.countryCode + + + + + + + + + + + + + +
+ +
+
+
+ +

help.countryCode

+ +

Country code and phone number pattern of a specific country

+

+ +
+
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
country_codestringISO country code
prefixesflags.0?Vector<string>Possible phone prefixes
patternsflags.1?Vector<string>Phone patterns: for example, XXX XXX XXX
+

Type

+

help.CountryCode

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.deepLinkInfo b/data/corefork.telegram.org/constructor/help.deepLinkInfo new file mode 100644 index 0000000000..1bd1ad1db7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.deepLinkInfo @@ -0,0 +1,165 @@ + + + + + help.deepLinkInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.deepLinkInfo

+ +

Deep linking info

+

+ +
+
help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
update_appflags.0?trueAn update of the app is required to parse this link
messagestringMessage to show to the user
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
+

Type

+

help.DeepLinkInfo

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty b/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty new file mode 100644 index 0000000000..5120ea1cfc --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty @@ -0,0 +1,132 @@ + + + + + help.deepLinkInfoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.deepLinkInfoEmpty

+ +

Deep link info empty

+

+ +
+
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.DeepLinkInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.inviteText b/data/corefork.telegram.org/constructor/help.inviteText new file mode 100644 index 0000000000..7f63088614 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.inviteText @@ -0,0 +1,147 @@ + + + + + help.inviteText + + + + + + + + + + + + + +
+ +
+
+
+ +

help.inviteText

+ +

Text of a text message with an invitation to install Telegram.

+

+ +
+
help.inviteText#18cb9f78 message:string = help.InviteText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messagestringText of the message
+

Type

+

help.InviteText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.noAppUpdate b/data/corefork.telegram.org/constructor/help.noAppUpdate new file mode 100644 index 0000000000..844ecd3f9d --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.noAppUpdate @@ -0,0 +1,132 @@ + + + + + help.noAppUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.noAppUpdate

+ +

No updates are available for the application.

+

+ +
+
help.noAppUpdate#c45a6536 = help.AppUpdate;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.AppUpdate

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.passportConfig b/data/corefork.telegram.org/constructor/help.passportConfig new file mode 100644 index 0000000000..26ed916575 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.passportConfig @@ -0,0 +1,156 @@ + + + + + help.passportConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.passportConfig

+ +

Telegram passport configuration

+

+ +
+
help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
countries_langsDataJSONLocalization
+

Type

+

help.PassportConfig

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.passportConfigNotModified b/data/corefork.telegram.org/constructor/help.passportConfigNotModified new file mode 100644 index 0000000000..a94329bd36 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.passportConfigNotModified @@ -0,0 +1,132 @@ + + + + + help.passportConfigNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

help.passportConfigNotModified

+ +

Password configuration not modified

+

+ +
+
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.PassportConfig

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.promoData b/data/corefork.telegram.org/constructor/help.promoData new file mode 100644 index 0000000000..65738d828e --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.promoData @@ -0,0 +1,182 @@ + + + + + help.promoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.promoData

+ +

MTProxy/Public Service Announcement information

+

+ +
+
help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
proxyflags.0?trueMTProxy-related channel
expiresintExpiry of PSA/MTProxy info
peerPeerMTProxy/PSA peer
chatsVector<Chat>Chat info
usersVector<User>User info
psa_typeflags.1?stringPSA type
psa_messageflags.2?stringPSA message
+

Type

+

help.PromoData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.promoDataEmpty b/data/corefork.telegram.org/constructor/help.promoDataEmpty new file mode 100644 index 0000000000..776ea336cc --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.promoDataEmpty @@ -0,0 +1,147 @@ + + + + + help.promoDataEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.promoDataEmpty

+ +

No PSA/MTProxy info is available

+

+ +
+
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintRe-fetch PSA/MTProxy info after the specified number of seconds
+

Type

+

help.PromoData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.recentMeUrls b/data/corefork.telegram.org/constructor/help.recentMeUrls new file mode 100644 index 0000000000..5bca235d4a --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.recentMeUrls @@ -0,0 +1,157 @@ + + + + + help.recentMeUrls + + + + + + + + + + + + + +
+ +
+
+
+ +

help.recentMeUrls

+ +

Recent t.me URLs

+

+ +
+
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlsVector<RecentMeUrl>URLs
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

help.RecentMeUrls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.support b/data/corefork.telegram.org/constructor/help.support new file mode 100644 index 0000000000..41c9a204f6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.support @@ -0,0 +1,152 @@ + + + + + help.support + + + + + + + + + + + + + +
+ +
+
+
+ +

help.support

+ +

Info on support user.

+

+ +
+
help.support#17c6b5f6 phone_number:string user:User = help.Support;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
userUserUser
+

Type

+

help.Support

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.supportName b/data/corefork.telegram.org/constructor/help.supportName new file mode 100644 index 0000000000..a0a97ad4a4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.supportName @@ -0,0 +1,147 @@ + + + + + help.supportName + + + + + + + + + + + + + +
+ +
+
+
+ +

help.supportName

+ +

Localized name for telegram support

+

+ +
+
help.supportName#8c05f1c9 name:string = help.SupportName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
namestringLocalized name
+

Type

+

help.SupportName

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.termsOfService b/data/corefork.telegram.org/constructor/help.termsOfService new file mode 100644 index 0000000000..472ce32f6b --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.termsOfService @@ -0,0 +1,175 @@ + + + + + help.termsOfService + + + + + + + + + + + + + +
+ +
+
+
+ +

help.termsOfService

+ +

Info about the latest telegram Terms Of Service

+

+ +
+
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?trueWhether a prompt must be showed to the user, in order to accept the new terms.
idDataJSONID of the new terms
textstringText of the new terms
entitiesVector<MessageEntity>Message entities for styled text
min_age_confirmflags.1?intMinimum age required to sign up to telegram, the user must confirm that they is older than the minimum age.
+

Type

+

help.TermsOfService

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.termsOfServiceUpdate b/data/corefork.telegram.org/constructor/help.termsOfServiceUpdate new file mode 100644 index 0000000000..9a4480f15f --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.termsOfServiceUpdate @@ -0,0 +1,157 @@ + + + + + help.termsOfServiceUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.termsOfServiceUpdate

+ +

Info about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"

+

+ +
+
help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
terms_of_servicehelp.TermsOfServiceNew terms of service
+

Type

+

help.TermsOfServiceUpdate

+

Related pages

+

help.getTermsOfServiceUpdate

+

Look for updates of telegram's terms of service

+

account.deleteAccount

+

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.termsOfServiceUpdateEmpty b/data/corefork.telegram.org/constructor/help.termsOfServiceUpdateEmpty new file mode 100644 index 0000000000..85e51a2b6e --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.termsOfServiceUpdateEmpty @@ -0,0 +1,150 @@ + + + + + help.termsOfServiceUpdateEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.termsOfServiceUpdateEmpty

+ +

No changes were made to telegram's terms of service

+

+ +
+
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
+

Type

+

help.TermsOfServiceUpdate

+

Related pages

+

help.getTermsOfServiceUpdate

+

Look for updates of telegram's terms of service

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.userInfo b/data/corefork.telegram.org/constructor/help.userInfo new file mode 100644 index 0000000000..54ac9fa547 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.userInfo @@ -0,0 +1,165 @@ + + + + + help.userInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.userInfo

+ +

Internal use

+

+ +
+
help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagestringInfo
entitiesVector<MessageEntity>Message entities for styled text
authorstringAuthor
dateintDate
+

Type

+

help.UserInfo

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.userInfoEmpty b/data/corefork.telegram.org/constructor/help.userInfoEmpty new file mode 100644 index 0000000000..1597dc1e83 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.userInfoEmpty @@ -0,0 +1,132 @@ + + + + + help.userInfoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.userInfoEmpty

+ +

Internal use

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.UserInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/highScore.html b/data/corefork.telegram.org/constructor/highScore.html new file mode 100644 index 0000000000..e9f6fa71f3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/highScore.html @@ -0,0 +1,157 @@ + + + + + highScore + + + + + + + + + + + + + +
+ +
+
+
+ +

highScore

+ +

Game highscore

+

+ +
+
highScore#73a379eb pos:int user_id:long score:int = HighScore;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
posintPosition in highscore list
user_idlongUser ID
scoreintScore
+

Type

+

HighScore

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/importedContact.html b/data/corefork.telegram.org/constructor/importedContact.html new file mode 100644 index 0000000000..20c28f87fb --- /dev/null +++ b/data/corefork.telegram.org/constructor/importedContact.html @@ -0,0 +1,155 @@ + + + + + importedContact + + + + + + + + + + + + + +
+ +
+
+
+ +

importedContact

+ +

Successfully imported contact.

+

+ +
+
importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
client_idlongThe contact's client identifier (passed to one of the InputContact constructors)
+

Type

+

ImportedContact

+

Related pages

+

InputContact

+

Object defines a contact from the user's phonebook.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inlineBotSwitchPM.html b/data/corefork.telegram.org/constructor/inlineBotSwitchPM.html new file mode 100644 index 0000000000..1526e16f84 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inlineBotSwitchPM.html @@ -0,0 +1,152 @@ + + + + + inlineBotSwitchPM + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineBotSwitchPM

+ +

The bot requested the user to message him in private

+

+ +
+
inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstringText for the button that switches the user to a private chat with the bot and sends the bot a start message with the parameter start_parameter (can be empty)
start_paramstringThe parameter for the /start parameter
+

Type

+

InlineBotSwitchPM

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html new file mode 100644 index 0000000000..212208511b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html @@ -0,0 +1,135 @@ + + + + + inlineQueryPeerTypeBroadcast + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeBroadcast

+ +

The inline query was sent in a channel

+

+ +
+
inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html new file mode 100644 index 0000000000..e1a4944869 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html @@ -0,0 +1,135 @@ + + + + + inlineQueryPeerTypeChat + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeChat

+ +

The inline query was sent in a chat

+

+ +
+
inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html new file mode 100644 index 0000000000..d38c8e6e99 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html @@ -0,0 +1,135 @@ + + + + + inlineQueryPeerTypeMegagroup + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeMegagroup

+ +

The inline query was sent in a supergroup

+

+ +
+
inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html new file mode 100644 index 0000000000..165bac6b54 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html @@ -0,0 +1,132 @@ + + + + + inlineQueryPeerTypePM + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypePM

+ +

The inline query was sent in a private chat

+

+ +
+
inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html new file mode 100644 index 0000000000..b2735b9849 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html @@ -0,0 +1,132 @@ + + + + + inlineQueryPeerTypeSameBotPM + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeSameBotPM

+ +

The inline query was sent in a private chat with the bot itself

+

+ +
+
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputAppEvent.html b/data/corefork.telegram.org/constructor/inputAppEvent.html new file mode 100644 index 0000000000..89345c323b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputAppEvent.html @@ -0,0 +1,162 @@ + + + + + inputAppEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

inputAppEvent

+ +

Event that occured in the application.

+

+ +
+
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
timedoubleClient's exact timestamp for the event
typestringType of event
peerlongArbitrary numeric value for more convenient selection of certain event types, or events referring to a certain object
dataJSONValueDetails of the event
+

Type

+

InputAppEvent

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageGame.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageGame.html new file mode 100644 index 0000000000..bc0f0d628e --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageGame.html @@ -0,0 +1,152 @@ + + + + + inputBotInlineMessageGame + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageGame

+ +

A game

+

+ +
+
inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageID.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageID.html new file mode 100644 index 0000000000..c86ac24014 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageID.html @@ -0,0 +1,157 @@ + + + + + inputBotInlineMessageID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageID

+ +

Represents a sent inline message from the perspective of a bot (legacy constructor)

+

+ +
+
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintDC ID to use when working with this inline message
idlongID of message, contains both the (32-bit, legacy) owner ID and the message ID, used only for Bot API backwards compatibility with 32-bit user ID.
access_hashlongAccess hash of message
+

Type

+

InputBotInlineMessageID

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageID64.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageID64.html new file mode 100644 index 0000000000..ae4bbf2861 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageID64.html @@ -0,0 +1,162 @@ + + + + + inputBotInlineMessageID64 + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageID64

+ +

Represents a sent inline message from the perspective of a bot

+

+ +
+
inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintDC ID to use when working with this inline message
owner_idlongID of the owner of this message
idintID of message
access_hashlongAccess hash of message
+

Type

+

InputBotInlineMessageID

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaAuto.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaAuto.html new file mode 100644 index 0000000000..68bde3fb83 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaAuto.html @@ -0,0 +1,165 @@ + + + + + inputBotInlineMessageMediaAuto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageMediaAuto

+ +

A media

+

+ +
+
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html new file mode 100644 index 0000000000..3d1d72c259 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html @@ -0,0 +1,172 @@ + + + + + inputBotInlineMessageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageMediaContact

+ +

A contact

+

+ +
+
inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaGeo.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaGeo.html new file mode 100644 index 0000000000..125bc09b39 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaGeo.html @@ -0,0 +1,175 @@ + + + + + inputBotInlineMessageMediaGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageMediaGeo

+ +

Geolocation

+

+ +
+
inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodflags.1?intValidity period
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
reply_markupflags.2?ReplyMarkupReply markup for bot/inline keyboards
+

Type

+

InputBotInlineMessage

+

Related pages

+

Live geolocation

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html new file mode 100644 index 0000000000..255a030280 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html @@ -0,0 +1,187 @@ + + + + + inputBotInlineMessageMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageMediaInvoice

+ +

An invoice

+

+ +
+
inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentInvoice photo
invoiceInvoiceThe invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerstringPayments provider token, obtained via Botfather
provider_dataDataJSONA JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaVenue.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaVenue.html new file mode 100644 index 0000000000..7d84fbad93 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaVenue.html @@ -0,0 +1,182 @@ + + + + + inputBotInlineMessageMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageMediaVenue

+ +

Venue

+

+ +
+
inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageText.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageText.html new file mode 100644 index 0000000000..7c08811ba5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageText.html @@ -0,0 +1,170 @@ + + + + + inputBotInlineMessageText + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageText

+ +

Simple text message

+

+ +
+
inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringMessage
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineResult.html b/data/corefork.telegram.org/constructor/inputBotInlineResult.html new file mode 100644 index 0000000000..aab98bb892 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineResult.html @@ -0,0 +1,189 @@ + + + + + inputBotInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResult

+ +

An inline bot result

+

+ +
+
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringID of result
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of result
thumbflags.4?InputWebDocumentThumbnail for result
contentflags.5?InputWebDocumentResult contents
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineResultDocument.html b/data/corefork.telegram.org/constructor/inputBotInlineResultDocument.html new file mode 100644 index 0000000000..4574fdf882 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineResultDocument.html @@ -0,0 +1,179 @@ + + + + + inputBotInlineResultDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResultDocument

+ +

Document (media of any type except for photos)

+

+ +
+
inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
documentInputDocumentDocument to send
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineResultPhoto.html b/data/corefork.telegram.org/constructor/inputBotInlineResultPhoto.html new file mode 100644 index 0000000000..bfd7d1e450 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineResultPhoto.html @@ -0,0 +1,164 @@ + + + + + inputBotInlineResultPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResultPhoto

+ +

Photo

+

+ +
+
inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringResult ID
typestringResult type (see bot API docs)
photoInputPhotoPhoto to send
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputChannel.html b/data/corefork.telegram.org/constructor/inputChannel.html new file mode 100644 index 0000000000..f8ee58ad2b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChannel.html @@ -0,0 +1,155 @@ + + + + + inputChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChannel

+ +

Represents a channel

+

+ +
+
inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
access_hashlongAccess hash taken from the channel constructor
+

Type

+

InputChannel

+

Related pages

+

channel

+

Channel/supergroup info

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputChannelEmpty.html b/data/corefork.telegram.org/constructor/inputChannelEmpty.html new file mode 100644 index 0000000000..be130f7318 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChannelEmpty.html @@ -0,0 +1,132 @@ + + + + + inputChannelEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChannelEmpty

+ +

Represents the absence of a channel

+

+ +
+
inputChannelEmpty#ee8c1e86 = InputChannel;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputChannel

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputChannelFromMessage.html b/data/corefork.telegram.org/constructor/inputChannelFromMessage.html new file mode 100644 index 0000000000..c84a8460e5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChannelFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputChannelFromMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChannelFromMessage

+ +

Defines a min channel that was seen in a certain message of a certain chat.

+

+ +
+
inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the channel was seen
msg_idintThe message ID in the chat where the channel was seen
channel_idlongThe channel ID
+

Type

+

InputChannel

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputChatPhoto.html b/data/corefork.telegram.org/constructor/inputChatPhoto.html new file mode 100644 index 0000000000..28f28fcf4b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChatPhoto.html @@ -0,0 +1,147 @@ + + + + + inputChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatPhoto

+ +

Existing photo to be set as a chat profile photo.

+

+ +
+
inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPhotoExisting photo
+

Type

+

InputChatPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputChatPhotoEmpty.html b/data/corefork.telegram.org/constructor/inputChatPhotoEmpty.html new file mode 100644 index 0000000000..51ba3224d1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChatPhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + inputChatPhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatPhotoEmpty

+ +

Empty constructor, remove group photo.

+

+ +
+
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputChatPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html b/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html new file mode 100644 index 0000000000..8f06f3165a --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html @@ -0,0 +1,165 @@ + + + + + inputChatUploadedPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatUploadedPhoto

+ +

New photo to be set as group profile photo.

+

+ +
+
inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts using the method upload.saveFilePart
videoflags.1?InputFileSquare video for animated profile picture
video_start_tsflags.2?doubleTimestamp that should be shown as static preview to the user (seconds)
+

Type

+

InputChatPhoto

+

Related pages

+

upload.saveFilePart

+

Saves a part of file for futher sending to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html b/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html new file mode 100644 index 0000000000..fa012ff084 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html @@ -0,0 +1,132 @@ + + + + + inputCheckPasswordEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputCheckPasswordEmpty

+ +

There is no password

+

+ +
+
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputCheckPasswordSRP

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputCheckPasswordSRP.html b/data/corefork.telegram.org/constructor/inputCheckPasswordSRP.html new file mode 100644 index 0000000000..672c66652c --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputCheckPasswordSRP.html @@ -0,0 +1,160 @@ + + + + + inputCheckPasswordSRP + + + + + + + + + + + + + +
+ +
+
+
+ +

inputCheckPasswordSRP

+ +

Constructor for checking the validity of a 2FA SRP password (see SRP)

+

+ +
+
inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
srp_idlongSRP ID
AbytesA parameter (see SRP)
M1bytesM1 parameter (see SRP)
+

Type

+

InputCheckPasswordSRP

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputClientProxy.html b/data/corefork.telegram.org/constructor/inputClientProxy.html new file mode 100644 index 0000000000..47ff461f46 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputClientProxy.html @@ -0,0 +1,154 @@ + + + + + inputClientProxy + + + + + + + + + + + + + +
+ +
+
+
+ +

inputClientProxy

+ +

Info about an MTProxy used to connect.

+

+ +
+
inputClientProxy#75588b3f address:string port:int = InputClientProxy;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
addressstringProxy address
portintProxy port
+

Type

+

InputClientProxy

+

Related pages

+

MTProto transports

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputDialogPeer.html b/data/corefork.telegram.org/constructor/inputDialogPeer.html new file mode 100644 index 0000000000..3adb9c5e7c --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputDialogPeer.html @@ -0,0 +1,147 @@ + + + + + inputDialogPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDialogPeer

+ +

A peer

+

+ +
+
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
+

Type

+

InputDialogPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputDialogPeerFolder.html b/data/corefork.telegram.org/constructor/inputDialogPeerFolder.html new file mode 100644 index 0000000000..8535017f3f --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputDialogPeerFolder.html @@ -0,0 +1,150 @@ + + + + + inputDialogPeerFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDialogPeerFolder

+ +

All peers in a peer folder

+

+ +
+
inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Type

+

InputDialogPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputDocument.html b/data/corefork.telegram.org/constructor/inputDocument.html new file mode 100644 index 0000000000..64cd70594b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputDocument.html @@ -0,0 +1,162 @@ + + + + + inputDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocument

+ +

Defines a video for subsequent interaction.

+

+ +
+
inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
+

Type

+

InputDocument

+

Related pages

+

document

+

Document

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputDocumentEmpty.html b/data/corefork.telegram.org/constructor/inputDocumentEmpty.html new file mode 100644 index 0000000000..3c7e171472 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputDocumentEmpty.html @@ -0,0 +1,132 @@ + + + + + inputDocumentEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocumentEmpty

+ +

Empty constructor.

+

+ +
+
inputDocumentEmpty#72f0eaae = InputDocument;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputDocument

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html b/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html new file mode 100644 index 0000000000..204e4e4ebc --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html @@ -0,0 +1,167 @@ + + + + + inputDocumentFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocumentFileLocation

+ +

Document location (video, voice, audio, basically every type except photo)

+

+ +
+
inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
thumb_sizestringThumbnail size to download the thumbnail
+

Type

+

InputFileLocation

+

Related pages

+

document

+

Document

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputEncryptedChat.html b/data/corefork.telegram.org/constructor/inputEncryptedChat.html new file mode 100644 index 0000000000..ec15e068b9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputEncryptedChat.html @@ -0,0 +1,159 @@ + + + + + inputEncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedChat

+ +

Creates an encrypted chat.

+

+ +
+
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idintChat ID
access_hashlongChecking sum from constructor encryptedChat, encryptedChatWaiting or encryptedChatRequested
+

Type

+

InputEncryptedChat

+

Related pages

+

encryptedChat

+

Encrypted chat

+

encryptedChatWaiting

+

Chat waiting for approval of second participant.

+

encryptedChatRequested

+

Request to create an encrypted chat.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFile.html b/data/corefork.telegram.org/constructor/inputEncryptedFile.html new file mode 100644 index 0000000000..b6fb20c8fb --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputEncryptedFile.html @@ -0,0 +1,155 @@ + + + + + inputEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFile

+ +

Sets forwarded encrypted file for attachment.

+

+ +
+
inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongFile ID, value of id parameter from encryptedFile
access_hashlongChecking sum, value of access_hash parameter from encryptedFile
+

Type

+

InputEncryptedFile

+

Related pages

+

encryptedFile

+

Encrypted file.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileBigUploaded.html b/data/corefork.telegram.org/constructor/inputEncryptedFileBigUploaded.html new file mode 100644 index 0000000000..206e8c59ad --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputEncryptedFileBigUploaded.html @@ -0,0 +1,160 @@ + + + + + inputEncryptedFileBigUploaded + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileBigUploaded

+ +

Assigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.

+

+ +
+
inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of saved parts
key_fingerprintint32-bit imprint of the key used to encrypt the file
+

Type

+

InputEncryptedFile

+

Related pages

+

upload.saveBigFilePart

+

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileEmpty.html b/data/corefork.telegram.org/constructor/inputEncryptedFileEmpty.html new file mode 100644 index 0000000000..f334009f4b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputEncryptedFileEmpty.html @@ -0,0 +1,132 @@ + + + + + inputEncryptedFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileEmpty

+ +

Empty constructor.

+

+ +
+
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputEncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileLocation.html b/data/corefork.telegram.org/constructor/inputEncryptedFileLocation.html new file mode 100644 index 0000000000..87387c5728 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputEncryptedFileLocation.html @@ -0,0 +1,155 @@ + + + + + inputEncryptedFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileLocation

+ +

Location of encrypted secret chat file.

+

+ +
+
inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongFile ID, id parameter value from encryptedFile
access_hashlongChecksum, access_hash parameter value from encryptedFile
+

Type

+

InputFileLocation

+

Related pages

+

encryptedFile

+

Encrypted file.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html b/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html new file mode 100644 index 0000000000..7a3b72e976 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html @@ -0,0 +1,162 @@ + + + + + inputEncryptedFileUploaded + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileUploaded

+ +

Sets new encrypted file saved by parts using upload.saveFilePart method.

+

+ +
+
inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongRandom file ID created by clien
partsintNumber of saved parts
md5_checksumstringIn case md5-HASH of the (already encrypted) file was transmitted, file content will be checked prior to use
key_fingerprintint32-bit fingerprint of the key used to encrypt a file
+

Type

+

InputEncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputFile.html b/data/corefork.telegram.org/constructor/inputFile.html new file mode 100644 index 0000000000..98f9c6c817 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputFile.html @@ -0,0 +1,165 @@ + + + + + inputFile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputFile

+ +

Defines a file saved in parts using the method upload.saveFilePart.

+

+ +
+
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongRandom file identifier created by the client
partsintNumber of parts saved
namestringFull name of the file
md5_checksumstringIn case the file's md5-hash was passed, contents of the file will be checked prior to use
+

Type

+

InputFile

+

Related pages

+

upload.saveFilePart

+

Saves a part of file for futher sending to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputFileLocation.html b/data/corefork.telegram.org/constructor/inputFileLocation.html new file mode 100644 index 0000000000..5bff834098 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputFileLocation.html @@ -0,0 +1,165 @@ + + + + + inputFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputFileLocation

+ +

DEPRECATED location of a photo

+

+ +
+
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
volume_idlongServer volume
local_idintFile identifier
secretlongCheck sum to access the file
file_referencebytesFile reference
+

Type

+

InputFileLocation

+

Related pages

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputFolderPeer.html b/data/corefork.telegram.org/constructor/inputFolderPeer.html new file mode 100644 index 0000000000..2ed903c59f --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputFolderPeer.html @@ -0,0 +1,155 @@ + + + + + inputFolderPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

inputFolderPeer

+ +

Peer in a folder

+

+ +
+
inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
folder_idintPeer folder ID, for more info click here
+

Type

+

InputFolderPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputGameID.html b/data/corefork.telegram.org/constructor/inputGameID.html new file mode 100644 index 0000000000..3c017361e0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputGameID.html @@ -0,0 +1,155 @@ + + + + + inputGameID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGameID

+ +

Indicates an already sent game

+

+ +
+
inputGameID#32c3e77 id:long access_hash:long = InputGame;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlonggame ID from Game constructor
access_hashlongaccess hash from Game constructor
+

Type

+

InputGame

+

Related pages

+

Game

+

Indicates an already sent game

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputGameShortName.html b/data/corefork.telegram.org/constructor/inputGameShortName.html new file mode 100644 index 0000000000..37237ee093 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputGameShortName.html @@ -0,0 +1,152 @@ + + + + + inputGameShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGameShortName

+ +

Game by short name

+

+ +
+
inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
bot_idInputUserThe bot that provides the game
short_namestringThe game's short name
+

Type

+

InputGame

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputGeoPoint.html b/data/corefork.telegram.org/constructor/inputGeoPoint.html new file mode 100644 index 0000000000..03562623b2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputGeoPoint.html @@ -0,0 +1,162 @@ + + + + + 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/corefork.telegram.org/constructor/inputGeoPointEmpty.html b/data/corefork.telegram.org/constructor/inputGeoPointEmpty.html new file mode 100644 index 0000000000..1a8a2078a6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputGeoPointEmpty.html @@ -0,0 +1,132 @@ + + + + + inputGeoPointEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGeoPointEmpty

+ +

Empty GeoPoint constructor.

+

+ +
+
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputGeoPoint

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputGroupCall.html b/data/corefork.telegram.org/constructor/inputGroupCall.html new file mode 100644 index 0000000000..5963607e09 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputGroupCall.html @@ -0,0 +1,152 @@ + + + + + inputGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGroupCall

+ +

Points to a specific group call

+

+ +
+
inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongGroup call ID
access_hashlongGroup call access hash
+

Type

+

InputGroupCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputGroupCallStream.html b/data/corefork.telegram.org/constructor/inputGroupCallStream.html new file mode 100644 index 0000000000..80ce048039 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputGroupCallStream.html @@ -0,0 +1,172 @@ + + + + + inputGroupCallStream + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGroupCallStream

+ +

Chunk of a livestream

+

+ +
+
inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallLivestream info
time_mslongTimestamp in milliseconds
scaleintSpecifies the duration of the video segment to fetch in milliseconds, by bitshifting 1000 to the right scale times: duration_ms := 1000 >> scale
video_channelflags.0?intSelected video channel
video_qualityflags.0?intSelected video quality (0 = lowest, 1 = medium, 2 = best)
+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputKeyboardButtonUrlAuth.html b/data/corefork.telegram.org/constructor/inputKeyboardButtonUrlAuth.html new file mode 100644 index 0000000000..794b302050 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputKeyboardButtonUrlAuth.html @@ -0,0 +1,176 @@ + + + + + inputKeyboardButtonUrlAuth + + + + + + + + + + + + + +
+ +
+
+
+ +

inputKeyboardButtonUrlAuth

+ +

Button to request a user to authorize via URL using Seamless Telegram Login.

+

+ +
+
inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueSet this flag to request the permission for your bot to send messages to the user.
textstringButton text
fwd_textflags.1?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.
NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
botInputUserUsername of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
+

Type

+

KeyboardButton

+

Related pages

+

Telegram Login Widget

+

messages.acceptUrlAuth

+

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputKeyboardButtonUserProfile.html b/data/corefork.telegram.org/constructor/inputKeyboardButtonUserProfile.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputKeyboardButtonUserProfile.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaContact.html b/data/corefork.telegram.org/constructor/inputMediaContact.html new file mode 100644 index 0000000000..b4e42ac139 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaContact.html @@ -0,0 +1,162 @@ + + + + + inputMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaContact

+ +

Phonebook contact

+

+ +
+
inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringContact vcard
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaDice.html b/data/corefork.telegram.org/constructor/inputMediaDice.html new file mode 100644 index 0000000000..466247273b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaDice.html @@ -0,0 +1,150 @@ + + + + + inputMediaDice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaDice

+ +

Send a dice-based animated sticker

+

+ +
+
inputMediaDice#e66fbf7b emoticon:string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
+

Type

+

InputMedia

+

Related pages

+

Dice

+

Telegram supports sending animated dice emojis.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaDocument.html b/data/corefork.telegram.org/constructor/inputMediaDocument.html new file mode 100644 index 0000000000..280c19a81b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaDocument.html @@ -0,0 +1,162 @@ + + + + + inputMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaDocument

+ +

Forwarded document

+

+ +
+
inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idInputDocumentThe document to be forwarded.
ttl_secondsflags.0?intTime to live of self-destructing document
queryflags.1?stringText query or emoji that was used by the user to find this sticker or GIF: used to improve search result relevance.
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaDocumentExternal.html b/data/corefork.telegram.org/constructor/inputMediaDocumentExternal.html new file mode 100644 index 0000000000..808574ed44 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaDocumentExternal.html @@ -0,0 +1,157 @@ + + + + + inputMediaDocumentExternal + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaDocumentExternal

+ +

Document that will be downloaded by the telegram servers

+

+ +
+
inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the document
ttl_secondsflags.0?intSelf-destruct time to live of document
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaEmpty.html b/data/corefork.telegram.org/constructor/inputMediaEmpty.html new file mode 100644 index 0000000000..aad0a35f4c --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaEmpty.html @@ -0,0 +1,132 @@ + + + + + inputMediaEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaEmpty

+ +

Empty media content of a message.

+

+ +
+
inputMediaEmpty#9664f57f = InputMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaGame.html b/data/corefork.telegram.org/constructor/inputMediaGame.html new file mode 100644 index 0000000000..d6ca2002c0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaGame.html @@ -0,0 +1,147 @@ + + + + + inputMediaGame + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaGame

+ +

A game

+

+ +
+
inputMediaGame#d33f43f3 id:InputGame = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputGameThe game to forward
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaGeoLive.html b/data/corefork.telegram.org/constructor/inputMediaGeoLive.html new file mode 100644 index 0000000000..8c4f35af71 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaGeoLive.html @@ -0,0 +1,175 @@ + + + + + inputMediaGeoLive + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaGeoLive

+ +

Live geolocation

+

+ +
+
inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
stoppedflags.0?trueWhether sending of the geolocation was stopped
geo_pointInputGeoPointCurrent geolocation
headingflags.2?intFor live locations, a direction in which the location moves, in degrees; 1-360.
periodflags.1?intValidity period of the current location
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
+

Type

+

InputMedia

+

Related pages

+

Live geolocation

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaGeoPoint.html b/data/corefork.telegram.org/constructor/inputMediaGeoPoint.html new file mode 100644 index 0000000000..3709b81f33 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaGeoPoint.html @@ -0,0 +1,147 @@ + + + + + inputMediaGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaGeoPoint

+ +

Map.

+

+ +
+
inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointInputGeoPointGeoPoint
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaInvoice.html b/data/corefork.telegram.org/constructor/inputMediaInvoice.html new file mode 100644 index 0000000000..2de8428076 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaInvoice.html @@ -0,0 +1,189 @@ + + + + + inputMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaInvoice

+ +

Generated invoice of a bot payment

+

+ +
+
inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
invoiceInvoiceThe actual invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerstringPayments provider token, obtained via Botfather
provider_dataDataJSONJSON-encoded data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
start_paramflags.1?stringStart parameter
+

Type

+

InputMedia

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaPhoto.html b/data/corefork.telegram.org/constructor/inputMediaPhoto.html new file mode 100644 index 0000000000..15a7f7ee7a --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaPhoto.html @@ -0,0 +1,157 @@ + + + + + inputMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaPhoto

+ +

Forwarded photo

+

+ +
+
inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idInputPhotoPhoto to be forwarded
ttl_secondsflags.0?intTime to live in seconds of self-destructing photo
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaPhotoExternal.html b/data/corefork.telegram.org/constructor/inputMediaPhotoExternal.html new file mode 100644 index 0000000000..77d0666fc6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaPhotoExternal.html @@ -0,0 +1,157 @@ + + + + + inputMediaPhotoExternal + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaPhotoExternal

+ +

New photo that will be uploaded by the server using the specified URL

+

+ +
+
inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the photo
ttl_secondsflags.0?intSelf-destruct time to live of photo
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaPoll.html b/data/corefork.telegram.org/constructor/inputMediaPoll.html new file mode 100644 index 0000000000..7b138edd63 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaPoll.html @@ -0,0 +1,170 @@ + + + + + inputMediaPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaPoll

+ +

A poll

+

+ +
+
inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pollPollThe poll to send
correct_answersflags.0?Vector<bytes>Correct answer IDs (for quiz polls)
solutionflags.1?stringExplanation of quiz solution
solution_entitiesflags.1?Vector<MessageEntity>Message entities for styled text
+

Type

+

InputMedia

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaUploadedDocument.html b/data/corefork.telegram.org/constructor/inputMediaUploadedDocument.html new file mode 100644 index 0000000000..38f2f68ce0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaUploadedDocument.html @@ -0,0 +1,190 @@ + + + + + inputMediaUploadedDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaUploadedDocument

+ +

New document

+

+ +
+
inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
nosound_videoflags.3?trueWhether the specified document is a video file with no audio tracks (a GIF animation (even as MPEG4), for example)
force_fileflags.4?trueForce the media file to be uploaded as document
fileInputFileThe uploaded file
thumbflags.2?InputFileThumbnail of the document, uploaded as for the file
mime_typestringMIME type of document
attributesVector<DocumentAttribute>Attributes that specify the type of the document (video, audio, voice, sticker, etc.)
stickersflags.0?Vector<InputDocument>Attached stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing document
+

Type

+

InputMedia

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaUploadedPhoto.html b/data/corefork.telegram.org/constructor/inputMediaUploadedPhoto.html new file mode 100644 index 0000000000..b29dbdcade --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaUploadedPhoto.html @@ -0,0 +1,165 @@ + + + + + inputMediaUploadedPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaUploadedPhoto

+ +

Photo

+

+ +
+
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileThe uploaded file
stickersflags.0?Vector<InputDocument>Attached mask stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing photo
+

Type

+

InputMedia

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaUploadedThumbDocument.html b/data/corefork.telegram.org/constructor/inputMediaUploadedThumbDocument.html new file mode 100644 index 0000000000..3c798c16ec --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaUploadedThumbDocument.html @@ -0,0 +1,176 @@ + + + + + inputMediaUploadedThumbDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaUploadedThumbDocument

+ +

New document with a thumbnail.

+

+ +
+
Constructor schema is available as of layer 22. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
fileInputFileDocument, saved in parts by using the methods upload.saveFilePart or upload.saveBigFilePart
thumbInputFileThumbnail file, saved in parts by using upload.saveFilePart
file_namestringFile name with extension
mime_typestringFile MIME-type
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaVenue.html b/data/corefork.telegram.org/constructor/inputMediaVenue.html new file mode 100644 index 0000000000..8ee3a47645 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaVenue.html @@ -0,0 +1,172 @@ + + + + + inputMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaVenue

+ +

Can be used to send a venue geolocation.

+

+ +
+
inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringPhysical address of the venue
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessageCallbackQuery.html b/data/corefork.telegram.org/constructor/inputMessageCallbackQuery.html new file mode 100644 index 0000000000..bdb0490101 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessageCallbackQuery.html @@ -0,0 +1,152 @@ + + + + + inputMessageCallbackQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageCallbackQuery

+ +

Used by bots for fetching information about the message that originated a callback query

+

+ +
+
inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintMessage ID
query_idlongCallback query ID
+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessageEntityMentionName.html b/data/corefork.telegram.org/constructor/inputMessageEntityMentionName.html new file mode 100644 index 0000000000..b6876d9f55 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessageEntityMentionName.html @@ -0,0 +1,162 @@ + + + + + inputMessageEntityMentionName + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageEntityMentionName

+ +

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

+

+ +
+
inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idInputUserIdentifier of the user that was mentioned
+

Type

+

MessageEntity

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

messageEntityMentionName

+

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessageID.html b/data/corefork.telegram.org/constructor/inputMessageID.html new file mode 100644 index 0000000000..64943cf857 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessageID.html @@ -0,0 +1,147 @@ + + + + + inputMessageID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageID

+ +

Message by ID

+

+ +
+
inputMessageID#a676a322 id:int = InputMessage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idintMessage ID
+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagePinned.html b/data/corefork.telegram.org/constructor/inputMessagePinned.html new file mode 100644 index 0000000000..49fcd6688a --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagePinned.html @@ -0,0 +1,132 @@ + + + + + inputMessagePinned + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagePinned

+ +

Pinned message

+

+ +
+
inputMessagePinned#86872538 = InputMessage;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessageReplyTo.html b/data/corefork.telegram.org/constructor/inputMessageReplyTo.html new file mode 100644 index 0000000000..3f9adf6457 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessageReplyTo.html @@ -0,0 +1,147 @@ + + + + + inputMessageReplyTo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageReplyTo

+ +

Message to which the specified message replies to

+

+ +
+
inputMessageReplyTo#bad88395 id:int = InputMessage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idintID of the message that replies to the message we need
+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html b/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html new file mode 100644 index 0000000000..189d4a4ab3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterChatPhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterChatPhotos

+ +

Return only chat photo changes

+

+ +
+
inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterContacts.html b/data/corefork.telegram.org/constructor/inputMessagesFilterContacts.html new file mode 100644 index 0000000000..fd1c710ea0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterContacts.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterContacts

+ +

Return only messages containing contacts

+

+ +
+
inputMessagesFilterContacts#e062db83 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html b/data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html new file mode 100644 index 0000000000..d1d0762ba8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterDocument

+ +

Filter for messages containing documents.

+

+ +
+
inputMessagesFilterDocument#9eddf188 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html b/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html new file mode 100644 index 0000000000..3805114aeb --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterEmpty

+ +

Filter is absent.

+

+ +
+
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html new file mode 100644 index 0000000000..bc2d2521c8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterGeo

+ +

Return only messages containing geolocations

+

+ +
+
inputMessagesFilterGeo#e7026d0d = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterGif.html b/data/corefork.telegram.org/constructor/inputMessagesFilterGif.html new file mode 100644 index 0000000000..df7e167706 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterGif.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterGif + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterGif

+ +

Return only messages containing gifs

+

+ +
+
inputMessagesFilterGif#ffc86587 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterMusic.html b/data/corefork.telegram.org/constructor/inputMessagesFilterMusic.html new file mode 100644 index 0000000000..e9087ace89 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterMusic.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterMusic + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterMusic

+ +

Return only messages containing audio files

+

+ +
+
inputMessagesFilterMusic#3751b49e = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterMyMentions.html b/data/corefork.telegram.org/constructor/inputMessagesFilterMyMentions.html new file mode 100644 index 0000000000..933befcf0d --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterMyMentions.html @@ -0,0 +1,135 @@ + + + + + inputMessagesFilterMyMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterMyMentions

+ +

Return only messages where the current user was mentioned.

+

+ +
+
inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterPhoneCalls.html b/data/corefork.telegram.org/constructor/inputMessagesFilterPhoneCalls.html new file mode 100644 index 0000000000..f7f546addf --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterPhoneCalls.html @@ -0,0 +1,152 @@ + + + + + inputMessagesFilterPhoneCalls + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterPhoneCalls

+ +

Return only phone calls

+

+ +
+
inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
missedflags.0?trueReturn only missed phone calls
+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterPhotoVideo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterPhotoVideo.html new file mode 100644 index 0000000000..07299c12fd --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterPhotoVideo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterPhotoVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterPhotoVideo

+ +

Filter for messages containing photos or videos.

+

+ +
+
inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterPhotos.html b/data/corefork.telegram.org/constructor/inputMessagesFilterPhotos.html new file mode 100644 index 0000000000..feb4d132e2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterPhotos.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterPhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterPhotos

+ +

Filter for messages containing photos.

+

+ +
+
inputMessagesFilterPhotos#9609a51c = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterPinned.html b/data/corefork.telegram.org/constructor/inputMessagesFilterPinned.html new file mode 100644 index 0000000000..414d72fe5c --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterPinned.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterPinned + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterPinned

+ +

Fetch only pinned messages

+

+ +
+
inputMessagesFilterPinned#1bb00451 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVideo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVideo.html new file mode 100644 index 0000000000..03a186baf8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVideo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterRoundVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterRoundVideo

+ +

Return only round videos

+

+ +
+
inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVoice.html b/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVoice.html new file mode 100644 index 0000000000..7bf0df66ca --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVoice.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterRoundVoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterRoundVoice

+ +

Return only round videos and voice notes

+

+ +
+
inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterUrl.html b/data/corefork.telegram.org/constructor/inputMessagesFilterUrl.html new file mode 100644 index 0000000000..d15e5a8569 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterUrl.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterUrl

+ +

Return only messages containing URLs

+

+ +
+
inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html new file mode 100644 index 0000000000..8f96bf4389 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterVideo

+ +

Filter for messages containing videos.

+

+ +
+
inputMessagesFilterVideo#9fc00e65 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterVoice.html b/data/corefork.telegram.org/constructor/inputMessagesFilterVoice.html new file mode 100644 index 0000000000..593b2b91ac --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterVoice.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterVoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterVoice

+ +

Return only messages containing voice notes

+

+ +
+
inputMessagesFilterVoice#50f5c392 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html b/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html new file mode 100644 index 0000000000..4f83a7278c --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html @@ -0,0 +1,135 @@ + + + + + inputNotifyBroadcasts + + + + + + + + + + + + + +
+ +
+
+
+ +

inputNotifyBroadcasts

+ +

All channels

+

+ +
+
inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputNotifyPeer

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputNotifyChats.html b/data/corefork.telegram.org/constructor/inputNotifyChats.html new file mode 100644 index 0000000000..f2af7147f9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputNotifyChats.html @@ -0,0 +1,132 @@ + + + + + inputNotifyChats + + + + + + + + + + + + + +
+ +
+
+
+ +

inputNotifyChats

+ +

Notifications generated by all groups.

+

+ +
+
inputNotifyChats#4a95e84e = InputNotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputNotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputNotifyPeer.html b/data/corefork.telegram.org/constructor/inputNotifyPeer.html new file mode 100644 index 0000000000..aa58ab57f8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputNotifyPeer.html @@ -0,0 +1,147 @@ + + + + + inputNotifyPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

inputNotifyPeer

+ +

Notifications generated by a certain user or group.

+

+ +
+
inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerUser or group
+

Type

+

InputNotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputNotifyUsers.html b/data/corefork.telegram.org/constructor/inputNotifyUsers.html new file mode 100644 index 0000000000..63a7e57e52 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputNotifyUsers.html @@ -0,0 +1,132 @@ + + + + + inputNotifyUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

inputNotifyUsers

+ +

Notifications generated by all users.

+

+ +
+
inputNotifyUsers#193b4417 = InputNotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputNotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentials.html b/data/corefork.telegram.org/constructor/inputPaymentCredentials.html new file mode 100644 index 0000000000..746c29dbfc --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPaymentCredentials.html @@ -0,0 +1,157 @@ + + + + + inputPaymentCredentials + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPaymentCredentials

+ +

Payment credentials

+

+ +
+
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
saveflags.0?trueSave payment credential for future use
dataDataJSONPayment credentials
+

Type

+

InputPaymentCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentialsApplePay.html b/data/corefork.telegram.org/constructor/inputPaymentCredentialsApplePay.html new file mode 100644 index 0000000000..010e1c5d59 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPaymentCredentialsApplePay.html @@ -0,0 +1,147 @@ + + + + + inputPaymentCredentialsApplePay + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPaymentCredentialsApplePay

+ +

Apple pay payment credentials

+

+ +
+
inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
payment_dataDataJSONPayment data
+

Type

+

InputPaymentCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html b/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html new file mode 100644 index 0000000000..364cacf63f --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html @@ -0,0 +1,147 @@ + + + + + inputPaymentCredentialsGooglePay + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPaymentCredentialsGooglePay

+ +

Google Pay payment credentials

+

+ +
+
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
payment_tokenDataJSONPayment token
+

Type

+

InputPaymentCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html b/data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html new file mode 100644 index 0000000000..ef39f67487 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html @@ -0,0 +1,152 @@ + + + + + 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/inputPeerChannelFromMessage.html b/data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html new file mode 100644 index 0000000000..6f70963f71 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputPeerChannelFromMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerChannelFromMessage

+ +

Defines a min channel that was seen in a certain message of a certain chat.

+

+ +
+
inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the channel's message was seen
msg_idintThe message ID
channel_idlongThe identifier of the channel that was seen
+

Type

+

InputPeer

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPeerChat.html b/data/corefork.telegram.org/constructor/inputPeerChat.html new file mode 100644 index 0000000000..daf77cbfd4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerChat.html @@ -0,0 +1,147 @@ + + + + + inputPeerChat + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerChat

+ +

Defines a chat for further interaction.

+

+ +
+
inputPeerChat#35a95cb9 chat_id:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat idientifier
+

Type

+

InputPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPeerNotifySettings.html b/data/corefork.telegram.org/constructor/inputPeerNotifySettings.html new file mode 100644 index 0000000000..ed8f54bd3e --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerNotifySettings.html @@ -0,0 +1,167 @@ + + + + + inputPeerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerNotifySettings

+ +

Notification settings.

+

+ +
+
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolIf the text of the message shall be displayed in notification
silentflags.1?BoolPeer was muted?
mute_untilflags.2?intDate until which all notifications shall be switched off
soundflags.3?stringName of an audio file for notification
+

Type

+

InputPeerNotifySettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html b/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html new file mode 100644 index 0000000000..72c339bbf3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html @@ -0,0 +1,162 @@ + + + + + inputPeerPhotoFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerPhotoFileLocation

+ +

Location of profile photo of channel/group/supergroup/user

+

+ +
+
inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
bigflags.0?trueWhether to download the high-quality version of the picture
peerInputPeerThe peer whose profile picture should be downloaded
photo_idlongPhoto ID
+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPeerSelf.html b/data/corefork.telegram.org/constructor/inputPeerSelf.html new file mode 100644 index 0000000000..d799a00a33 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerSelf.html @@ -0,0 +1,132 @@ + + + + + inputPeerSelf + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerSelf

+ +

Defines the current user.

+

+ +
+
inputPeerSelf#7da07ec9 = InputPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPeerUser.html b/data/corefork.telegram.org/constructor/inputPeerUser.html new file mode 100644 index 0000000000..6dda4c0374 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerUser.html @@ -0,0 +1,155 @@ + + + + + inputPeerUser + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerUser

+ +

Defines a user for further interaction.

+

+ +
+
inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
access_hashlongaccess_hash value from the user constructor
+

Type

+

InputPeer

+

Related pages

+

user

+

Indicates info about a certain user

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html b/data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html new file mode 100644 index 0000000000..5ee9cdbcc1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputPeerUserFromMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerUserFromMessage

+ +

Defines a min user that was seen in a certain message of a certain chat.

+

+ +
+
inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idlongThe identifier of the user that was seen
+

Type

+

InputPeer

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPhoneCall.html b/data/corefork.telegram.org/constructor/inputPhoneCall.html new file mode 100644 index 0000000000..d572802606 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPhoneCall.html @@ -0,0 +1,152 @@ + + + + + inputPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhoneCall

+ +

Phone call

+

+ +
+
inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongCall ID
access_hashlongAccess hash
+

Type

+

InputPhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPhoneContact.html b/data/corefork.telegram.org/constructor/inputPhoneContact.html new file mode 100644 index 0000000000..28b33a83f0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPhoneContact.html @@ -0,0 +1,166 @@ + + + + + inputPhoneContact + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhoneContact

+ +

Phone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.

+

+ +
+
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
client_idlongUser identifier on the client
phonestringPhone number
first_namestringContact's first name
last_namestringContact's last name
+

Type

+

InputContact

+

Related pages

+

contacts.importContacts

+

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

+

Use contacts.addContact to add Telegram contacts without actually using their phone number.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPhoto.html b/data/corefork.telegram.org/constructor/inputPhoto.html new file mode 100644 index 0000000000..d8353b9a84 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPhoto.html @@ -0,0 +1,162 @@ + + + + + inputPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhoto

+ +

Defines a photo for further interaction.

+

+ +
+
inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongPhoto identifier
access_hashlongaccess_hash value from the photo constructor
file_referencebytesFile reference
+

Type

+

InputPhoto

+

Related pages

+

photo

+

Photo

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPhotoEmpty.html b/data/corefork.telegram.org/constructor/inputPhotoEmpty.html new file mode 100644 index 0000000000..07d4cd175e --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + inputPhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhotoEmpty

+ +

Empty constructor.

+

+ +
+
inputPhotoEmpty#1cd7bf0d = InputPhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPhotoFileLocation.html b/data/corefork.telegram.org/constructor/inputPhotoFileLocation.html new file mode 100644 index 0000000000..5771cdd5fc --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPhotoFileLocation.html @@ -0,0 +1,171 @@ + + + + + inputPhotoFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPhotoFileLocation

+ +

Use this object to download a photo with upload.getFile method

+

+ +
+
inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongPhoto ID, obtained from the photo object
access_hashlongPhoto's access hash, obtained from the photo object
file_referencebytesFile reference
thumb_sizestringThe PhotoSize to download: must be set to the type field of the desired PhotoSize object of the photo
+

Type

+

InputFileLocation

+

Related pages

+

photo

+

Photo

+

File references

+

How to handle file references.

+

PhotoSize

+

Location of a certain size of a picture

+

upload.getFile

+

Returns content of a whole file or its part.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html b/data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html new file mode 100644 index 0000000000..c1db6454b6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html @@ -0,0 +1,172 @@ + + + + + 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/inputPrivacyKeyAddedByPhone.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html new file mode 100644 index 0000000000..de61dd9abc --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyAddedByPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyAddedByPhone

+ +

Whether people can add you to their contact list by your phone number

+

+ +
+
inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyChatInvite.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyChatInvite.html new file mode 100644 index 0000000000..423e0e482a --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyChatInvite.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyChatInvite

+ +

Whether the user can be invited to chats

+

+ +
+
inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyForwards.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyForwards.html new file mode 100644 index 0000000000..d29e3d982f --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyForwards.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyForwards + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyForwards

+ +

Whether messages forwarded from this user will be anonymous

+

+ +
+
inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html new file mode 100644 index 0000000000..2db1d3c107 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyPhoneCall

+ +

Whether the user will accept phone calls

+

+ +
+
inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html new file mode 100644 index 0000000000..38f4eb03f5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyPhoneNumber + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyPhoneNumber

+ +

Whether people will be able to see the user's phone number

+

+ +
+
inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html new file mode 100644 index 0000000000..cc76ec27f0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyPhoneP2P + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyPhoneP2P

+ +

Whether the user allows P2P communication during VoIP calls

+

+ +
+
inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html new file mode 100644 index 0000000000..cb40dbcf28 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyProfilePhoto

+ +

Whether people will be able to see the user's profile picture

+

+ +
+
inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html new file mode 100644 index 0000000000..9773210579 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyStatusTimestamp + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyStatusTimestamp

+ +

Whether we can see the exact last online timestamp of the user

+

+ +
+
inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowAll.html b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowAll.html new file mode 100644 index 0000000000..5a3e927642 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowAll.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyValueAllowAll + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueAllowAll

+ +

Allow all users

+

+ +
+
inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html new file mode 100644 index 0000000000..e57bef8546 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueAllowChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueAllowChatParticipants

+ +

Allow only participants of certain chats

+

+ +
+
inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<long>Allowed chat IDs
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowContacts.html b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowContacts.html new file mode 100644 index 0000000000..5a0cc75516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowContacts.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyValueAllowContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueAllowContacts

+ +

Allow only contacts

+

+ +
+
inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowUsers.html b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowUsers.html new file mode 100644 index 0000000000..23a3240240 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowUsers.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueAllowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueAllowUsers

+ +

Allow only certain users

+

+ +
+
inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>Allowed users
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowAll.html b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowAll.html new file mode 100644 index 0000000000..72c1d7154e --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowAll.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyValueDisallowAll + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowAll

+ +

Disallow all

+

+ +
+
inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html new file mode 100644 index 0000000000..e90c3f4bd6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueDisallowChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowChatParticipants

+ +

Disallow only participants of certain chats

+

+ +
+
inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<long>Disallowed chat IDs
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowContacts.html b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowContacts.html new file mode 100644 index 0000000000..84e051f0a1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowContacts.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyValueDisallowContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowContacts

+ +

Disallow only contacts

+

+ +
+
inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowUsers.html b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowUsers.html new file mode 100644 index 0000000000..7ae74e3407 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowUsers.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueDisallowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowUsers

+ +

Disallow only certain users

+

+ +
+
inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>Users to disallow
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonChildAbuse.html b/data/corefork.telegram.org/constructor/inputReportReasonChildAbuse.html new file mode 100644 index 0000000000..9d734c9cdf --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonChildAbuse.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonChildAbuse + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonChildAbuse

+ +

Report for child abuse

+

+ +
+
inputReportReasonChildAbuse#adf44ee3 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonCopyright.html b/data/corefork.telegram.org/constructor/inputReportReasonCopyright.html new file mode 100644 index 0000000000..fff2bf45de --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonCopyright.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonCopyright + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonCopyright

+ +

Report for copyrighted content

+

+ +
+
inputReportReasonCopyright#9b89f93a = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonFake.html b/data/corefork.telegram.org/constructor/inputReportReasonFake.html new file mode 100644 index 0000000000..7c82edf3bb --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonFake.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonFake + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonFake

+ +

Report for impersonation

+

+ +
+
inputReportReasonFake#f5ddd6e7 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonGeoIrrelevant.html b/data/corefork.telegram.org/constructor/inputReportReasonGeoIrrelevant.html new file mode 100644 index 0000000000..e38a53eb92 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonGeoIrrelevant.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonGeoIrrelevant + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonGeoIrrelevant

+ +

Report an irrelevant geogroup

+

+ +
+
inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonOther.html b/data/corefork.telegram.org/constructor/inputReportReasonOther.html new file mode 100644 index 0000000000..d2f3636ec6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonOther.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonOther + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonOther

+ +

Other

+

+ +
+
inputReportReasonOther#c1e4a2b1 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonPornography.html b/data/corefork.telegram.org/constructor/inputReportReasonPornography.html new file mode 100644 index 0000000000..72c387af86 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonPornography.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonPornography + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonPornography

+ +

Report for pornography

+

+ +
+
inputReportReasonPornography#2e59d922 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonSpam.html b/data/corefork.telegram.org/constructor/inputReportReasonSpam.html new file mode 100644 index 0000000000..fca4b732b3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonSpam.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonSpam

+ +

Report for spam

+

+ +
+
inputReportReasonSpam#58dbcab8 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonViolence.html b/data/corefork.telegram.org/constructor/inputReportReasonViolence.html new file mode 100644 index 0000000000..650b579602 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonViolence.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonViolence + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonViolence

+ +

Report for violence

+

+ +
+
inputReportReasonViolence#1e22c78d = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputSecureFile.html b/data/corefork.telegram.org/constructor/inputSecureFile.html new file mode 100644 index 0000000000..585b9ad722 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputSecureFile.html @@ -0,0 +1,155 @@ + + + + + inputSecureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureFile

+ +

Preuploaded passport file, for more info see the passport docs »

+

+ +
+
inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongSecure file ID
access_hashlongSecure file access hash
+

Type

+

InputSecureFile

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputSecureFileLocation.html b/data/corefork.telegram.org/constructor/inputSecureFileLocation.html new file mode 100644 index 0000000000..126dced6a4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputSecureFileLocation.html @@ -0,0 +1,156 @@ + + + + + inputSecureFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureFileLocation

+ +

Location of encrypted telegram passport file.

+

+ +
+
inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongFile ID, id parameter value from secureFile
access_hashlongChecksum, access_hash parameter value from secureFile
+

Type

+

InputFileLocation

+

Related pages

+

secureFile

+

Secure passport file, for more info see the passport docs »

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html b/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html new file mode 100644 index 0000000000..283d3c2f10 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html @@ -0,0 +1,169 @@ + + + + + inputSecureFileUploaded + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureFileUploaded

+ +

Uploaded secure file, for more info see the passport docs »

+

+ +
+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongSecure file ID
partsintSecure file part count
md5_checksumstringMD5 hash of encrypted uploaded file, to be checked server-side
file_hashbytesFile hash
secretbytesSecret
+

Type

+

InputSecureFile

+

Related pages

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputSecureValue.html b/data/corefork.telegram.org/constructor/inputSecureValue.html new file mode 100644 index 0000000000..7bf44bb781 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputSecureValue.html @@ -0,0 +1,190 @@ + + + + + inputSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureValue

+ +

Secure value, for more info see the passport docs »

+

+ +
+
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
+

Type

+

InputSecureValue

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputSingleMedia.html b/data/corefork.telegram.org/constructor/inputSingleMedia.html new file mode 100644 index 0000000000..c25539003e --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputSingleMedia.html @@ -0,0 +1,174 @@ + + + + + inputSingleMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSingleMedia

+ +

A single media in an album or grouped media sent with messages.sendMultiMedia.

+

+ +
+
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
mediaInputMediaThe media
random_idlongUnique client media ID required to prevent message resending
messagestringA caption for the media
entitiesflags.0?Vector<MessageEntity>Message entities for styled text
+

Type

+

InputSingleMedia

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

messages.sendMultiMedia

+

Send an album or grouped media

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmoji.html b/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmoji.html new file mode 100644 index 0000000000..59a4e2bbda --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmoji.html @@ -0,0 +1,132 @@ + + + + + inputStickerSetAnimatedEmoji + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetAnimatedEmoji

+ +

Animated emojis stickerset

+

+ +
+
inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html b/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html new file mode 100644 index 0000000000..b2417ac36b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html @@ -0,0 +1,132 @@ + + + + + inputStickerSetAnimatedEmojiAnimations + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetAnimatedEmojiAnimations

+ +

Animated emoji reaction stickerset (contains animations to play when a user clicks on a given animated emoji)

+

+ +
+
inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetEmpty.html b/data/corefork.telegram.org/constructor/inputStickerSetEmpty.html new file mode 100644 index 0000000000..efde6e8a5a --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetEmpty.html @@ -0,0 +1,132 @@ + + + + + inputStickerSetEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetEmpty

+ +

Empty constructor

+

+ +
+
inputStickerSetEmpty#ffb62b95 = InputStickerSet;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetID.html b/data/corefork.telegram.org/constructor/inputStickerSetID.html new file mode 100644 index 0000000000..d75f235911 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetID.html @@ -0,0 +1,152 @@ + + + + + inputStickerSetID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetID

+ +

Stickerset by ID

+

+ +
+
inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetItem.html b/data/corefork.telegram.org/constructor/inputStickerSetItem.html new file mode 100644 index 0000000000..1587847ce2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetItem.html @@ -0,0 +1,162 @@ + + + + + inputStickerSetItem + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetItem

+ +

Sticker in a stickerset

+

+ +
+
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
documentInputDocumentThe sticker
emojistringAssociated emoji
mask_coordsflags.0?MaskCoordsCoordinates for mask sticker
+

Type

+

InputStickerSetItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetShortName.html b/data/corefork.telegram.org/constructor/inputStickerSetShortName.html new file mode 100644 index 0000000000..6e797ff46f --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetShortName.html @@ -0,0 +1,147 @@ + + + + + inputStickerSetShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetShortName

+ +

Stickerset by short name, from tg://addstickers?set=short_name

+

+ +
+
inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
short_namestringFrom tg://addstickers?set=short_name
+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetThumb.html b/data/corefork.telegram.org/constructor/inputStickerSetThumb.html new file mode 100644 index 0000000000..ac05115fd4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetThumb.html @@ -0,0 +1,155 @@ + + + + + inputStickerSetThumb + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetThumb

+ +

Location of stickerset thumbnail (see files)

+

+ +
+
inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetSticker set
thumb_versionintThumbnail version
+

Type

+

InputFileLocation

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickeredMediaDocument.html b/data/corefork.telegram.org/constructor/inputStickeredMediaDocument.html new file mode 100644 index 0000000000..6c14dcf4a4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickeredMediaDocument.html @@ -0,0 +1,147 @@ + + + + + inputStickeredMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickeredMediaDocument

+ +

A document with stickers attached

+

+ +
+
inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputDocumentThe document
+

Type

+

InputStickeredMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickeredMediaPhoto.html b/data/corefork.telegram.org/constructor/inputStickeredMediaPhoto.html new file mode 100644 index 0000000000..7c10ab9fdd --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickeredMediaPhoto.html @@ -0,0 +1,147 @@ + + + + + inputStickeredMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickeredMediaPhoto

+ +

A photo with stickers attached

+

+ +
+
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPhotoThe photo
+

Type

+

InputStickeredMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputTakeoutFileLocation.html b/data/corefork.telegram.org/constructor/inputTakeoutFileLocation.html new file mode 100644 index 0000000000..3ca02504e6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputTakeoutFileLocation.html @@ -0,0 +1,132 @@ + + + + + inputTakeoutFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputTakeoutFileLocation

+ +

Empty constructor for takeout

+

+ +
+
inputTakeoutFileLocation#29be5899 = InputFileLocation;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputTheme.html b/data/corefork.telegram.org/constructor/inputTheme.html new file mode 100644 index 0000000000..42c78a2437 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputTheme.html @@ -0,0 +1,152 @@ + + + + + inputTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

inputTheme

+ +

Theme

+

+ +
+
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
+

Type

+

InputTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputThemeSettings.html b/data/corefork.telegram.org/constructor/inputThemeSettings.html new file mode 100644 index 0000000000..90cfe81619 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputThemeSettings.html @@ -0,0 +1,182 @@ + + + + + inputThemeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

inputThemeSettings

+ +

Theme settings

+

+ +
+
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
message_colors_animatedflags.2?trueIf set, the freeform gradient fill needs to be animated on every sent message
base_themeBaseThemeDefault theme on which this theme is based
accent_colorintAccent color, ARGB format
outbox_accent_colorflags.3?intAccent color of outgoing messages in ARGB format
message_colorsflags.0?Vector<int>The fill to be used as a background for outgoing messages, in RGB24 format.
If just one or two equal colors are provided, describes a solid fill of a background.
If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
If three or four colors are provided, describes a freeform gradient fill of a background.
wallpaperflags.1?InputWallPaperWallpaper
wallpaper_settingsflags.1?WallPaperSettingsWallpaper settings
+

Type

+

InputThemeSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputThemeSlug.html b/data/corefork.telegram.org/constructor/inputThemeSlug.html new file mode 100644 index 0000000000..b097d4051b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputThemeSlug.html @@ -0,0 +1,147 @@ + + + + + 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 new file mode 100644 index 0000000000..4b5fdc2a06 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputUser.html @@ -0,0 +1,155 @@ + + + + + inputUser + + + + + + + + + + + + + +
+ +
+
+
+ +

inputUser

+ +

Defines a user for further interaction.

+

+ +
+
inputUser#f21158c6 user_id:long access_hash:long = InputUser;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
access_hashlongaccess_hash value from the user constructor
+

Type

+

InputUser

+

Related pages

+

user

+

Indicates info about a certain user

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputUserEmpty.html b/data/corefork.telegram.org/constructor/inputUserEmpty.html new file mode 100644 index 0000000000..8ba38dcb7e --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputUserEmpty.html @@ -0,0 +1,132 @@ + + + + + inputUserEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputUserEmpty

+ +

Empty constructor, does not define a user.

+

+ +
+
inputUserEmpty#b98886cf = InputUser;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputUser

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputUserFromMessage.html b/data/corefork.telegram.org/constructor/inputUserFromMessage.html new file mode 100644 index 0000000000..35fe6074d3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputUserFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputUserFromMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

inputUserFromMessage

+ +

Defines a min user that was seen in a certain message of a certain chat.

+

+ +
+
inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idlongThe identifier of the user that was seen
+

Type

+

InputUser

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputWallPaper.html b/data/corefork.telegram.org/constructor/inputWallPaper.html new file mode 100644 index 0000000000..0a8c5c55f5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputWallPaper.html @@ -0,0 +1,152 @@ + + + + + inputWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWallPaper

+ +

Wallpaper

+

+ +
+
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongWallpaper ID
access_hashlongAccess hash
+

Type

+

InputWallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html b/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html new file mode 100644 index 0000000000..ad1d84a9d8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html @@ -0,0 +1,150 @@ + + + + + inputWallPaperNoFile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWallPaperNoFile

+ +

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.

+

+ +
+
inputWallPaperNoFile#967a462e id:long = InputWallPaper;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongWallpaper ID
+

Type

+

InputWallPaper

+

Related pages

+

account.saveWallPaper

+

Install/uninstall wallpaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputWallPaperSlug.html b/data/corefork.telegram.org/constructor/inputWallPaperSlug.html new file mode 100644 index 0000000000..1b81b633dd --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputWallPaperSlug.html @@ -0,0 +1,147 @@ + + + + + inputWallPaperSlug + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWallPaperSlug

+ +

Wallpaper by slug (a unique ID)

+

+ +
+
inputWallPaperSlug#72091c80 slug:string = InputWallPaper;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
slugstringUnique wallpaper ID
+

Type

+

InputWallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputWebDocument.html b/data/corefork.telegram.org/constructor/inputWebDocument.html new file mode 100644 index 0000000000..5158fa6d17 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputWebDocument.html @@ -0,0 +1,165 @@ + + + + + inputWebDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWebDocument

+ +

The document

+

+ +
+
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringRemote document URL to be downloaded using the appropriate method
sizeintRemote file size
mime_typestringMime type
attributesVector<DocumentAttribute>Attributes for media types
+

Type

+

InputWebDocument

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html b/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html new file mode 100644 index 0000000000..bfe3cf58f2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html @@ -0,0 +1,172 @@ + + + + + inputWebFileGeoPointLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWebFileGeoPointLocation

+ +

Geolocation

+

+ +
+
inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointInputGeoPointGeolocation
access_hashlongAccess hash
wintMap width in pixels before applying scale; 16-1024
hintMap height in pixels before applying scale; 16-1024
zoomintMap zoom level; 13-20
scaleintMap scale; 1-3
+

Type

+

InputWebFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputWebFileLocation.html b/data/corefork.telegram.org/constructor/inputWebFileLocation.html new file mode 100644 index 0000000000..cbb8e48d34 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputWebFileLocation.html @@ -0,0 +1,152 @@ + + + + + inputWebFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWebFileLocation

+ +

Location of a remote HTTP(s) file

+

+ +
+
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringHTTP URL of file
access_hashlongAccess hash
+

Type

+

InputWebFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/invoice.html b/data/corefork.telegram.org/constructor/invoice.html new file mode 100644 index 0000000000..45bf690099 --- /dev/null +++ b/data/corefork.telegram.org/constructor/invoice.html @@ -0,0 +1,209 @@ + + + + + invoice + + + + + + + + + + + + + +
+ +
+
+
+ +

invoice

+ +

Invoice

+

+ +
+
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
testflags.0?trueTest invoice
name_requestedflags.1?trueSet this flag if you require the user's full name to complete the order
phone_requestedflags.2?trueSet this flag if you require the user's phone number to complete the order
email_requestedflags.3?trueSet this flag if you require the user's email address to complete the order
shipping_address_requestedflags.4?trueSet this flag if you require the user's shipping address to complete the order
flexibleflags.5?trueSet this flag if the final price depends on the shipping method
phone_to_providerflags.6?trueSet this flag if user's phone number should be sent to provider
email_to_providerflags.7?trueSet this flag if user's email address should be sent to provider
currencystringThree-letter ISO 4217 currency code
pricesVector<LabeledPrice>Price breakdown, a list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountflags.8?longThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
suggested_tip_amountsflags.8?Vector<long>A vector of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
+

Type

+

Invoice

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/jsonArray.html b/data/corefork.telegram.org/constructor/jsonArray.html new file mode 100644 index 0000000000..091d98fcce --- /dev/null +++ b/data/corefork.telegram.org/constructor/jsonArray.html @@ -0,0 +1,147 @@ + + + + + jsonArray + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonArray

+ +

JSON array

+

+ +
+
jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valueVector<JSONValue>JSON values
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/jsonNull.html b/data/corefork.telegram.org/constructor/jsonNull.html new file mode 100644 index 0000000000..b4f1595564 --- /dev/null +++ b/data/corefork.telegram.org/constructor/jsonNull.html @@ -0,0 +1,132 @@ + + + + + jsonNull + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonNull

+ +

null JSON value

+

+ +
+
jsonNull#3f6d7b68 = JSONValue;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/jsonNumber.html b/data/corefork.telegram.org/constructor/jsonNumber.html new file mode 100644 index 0000000000..462ba2015f --- /dev/null +++ b/data/corefork.telegram.org/constructor/jsonNumber.html @@ -0,0 +1,147 @@ + + + + + jsonNumber + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonNumber

+ +

JSON numeric value

+

+ +
+
jsonNumber#2be0dfa4 value:double = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valuedoubleValue
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/jsonObject.html b/data/corefork.telegram.org/constructor/jsonObject.html new file mode 100644 index 0000000000..a35af61377 --- /dev/null +++ b/data/corefork.telegram.org/constructor/jsonObject.html @@ -0,0 +1,147 @@ + + + + + jsonObject + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonObject

+ +

JSON object value

+

+ +
+
jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valueVector<JSONObjectValue>Values
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/jsonObjectValue.html b/data/corefork.telegram.org/constructor/jsonObjectValue.html new file mode 100644 index 0000000000..b0eee46ced --- /dev/null +++ b/data/corefork.telegram.org/constructor/jsonObjectValue.html @@ -0,0 +1,152 @@ + + + + + jsonObjectValue + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonObjectValue

+ +

JSON key: value pair

+

+ +
+
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keystringKey
valueJSONValueValue
+

Type

+

JSONObjectValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/jsonString.html b/data/corefork.telegram.org/constructor/jsonString.html new file mode 100644 index 0000000000..f2ef204706 --- /dev/null +++ b/data/corefork.telegram.org/constructor/jsonString.html @@ -0,0 +1,147 @@ + + + + + jsonString + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonString

+ +

JSON string

+

+ +
+
jsonString#b71e767a value:string = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valuestringValue
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButton.html b/data/corefork.telegram.org/constructor/keyboardButton.html new file mode 100644 index 0000000000..293c944812 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButton.html @@ -0,0 +1,147 @@ + + + + + keyboardButton + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButton

+ +

Bot keyboard button

+

+ +
+
keyboardButton#a2fa4880 text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonBuy.html b/data/corefork.telegram.org/constructor/keyboardButtonBuy.html new file mode 100644 index 0000000000..5c75822ee0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonBuy.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonBuy + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonBuy

+ +

Button to buy a product

+

+ +
+
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonCallback.html b/data/corefork.telegram.org/constructor/keyboardButtonCallback.html new file mode 100644 index 0000000000..b4c6943dc6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonCallback.html @@ -0,0 +1,167 @@ + + + + + keyboardButtonCallback + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonCallback

+ +

Callback button

+

+ +
+
keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
requires_passwordflags.0?trueWhether the user should verify his identity by entering his 2FA SRP parameters to the messages.getBotCallbackAnswer method. NOTE: telegram and the bot WILL NOT have access to the plaintext password, thanks to SRP. This button is mainly used by the official @botfather bot, for verifying the user's identity before transferring ownership of a bot to another user.
textstringButton text
databytesCallback data
+

Type

+

KeyboardButton

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

messages.getBotCallbackAnswer

+

Press an inline callback button and get a callback answer from the bot

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonGame.html b/data/corefork.telegram.org/constructor/keyboardButtonGame.html new file mode 100644 index 0000000000..17c2d309b4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonGame.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonGame + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonGame

+ +

Button to start a game

+

+ +
+
keyboardButtonGame#50f41ccf text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonRequestGeoLocation.html b/data/corefork.telegram.org/constructor/keyboardButtonRequestGeoLocation.html new file mode 100644 index 0000000000..c7cf453678 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonRequestGeoLocation.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonRequestGeoLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRequestGeoLocation

+ +

Button to request a user's geolocation

+

+ +
+
keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonRequestPhone.html b/data/corefork.telegram.org/constructor/keyboardButtonRequestPhone.html new file mode 100644 index 0000000000..28beeddd4a --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonRequestPhone.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonRequestPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRequestPhone

+ +

Button to request a user's phone number

+

+ +
+
keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonRequestPoll.html b/data/corefork.telegram.org/constructor/keyboardButtonRequestPoll.html new file mode 100644 index 0000000000..783159a87f --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonRequestPoll.html @@ -0,0 +1,157 @@ + + + + + keyboardButtonRequestPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRequestPoll

+ +

A button that allows the user to create and send a poll when pressed; available only in private

+

+ +
+
keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
quizflags.0?BoolIf set, only quiz polls can be sent
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonRow.html b/data/corefork.telegram.org/constructor/keyboardButtonRow.html new file mode 100644 index 0000000000..1a5d608819 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonRow.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonRow + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRow

+ +

Inline keyboard row

+

+ +
+
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
buttonsVector<KeyboardButton>Bot or inline keyboard buttons
+

Type

+

KeyboardButtonRow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonSwitchInline.html b/data/corefork.telegram.org/constructor/keyboardButtonSwitchInline.html new file mode 100644 index 0000000000..c50aded600 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonSwitchInline.html @@ -0,0 +1,162 @@ + + + + + keyboardButtonSwitchInline + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonSwitchInline

+ +

Button to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.

+

+ +
+
keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
same_peerflags.0?trueIf set, pressing the button will insert the bot‘s username and the specified inline query in the current chat's input field.
textstringButton label
querystringThe inline query to use
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonUrl.html b/data/corefork.telegram.org/constructor/keyboardButtonUrl.html new file mode 100644 index 0000000000..3127ad531c --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonUrl.html @@ -0,0 +1,152 @@ + + + + + keyboardButtonUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonUrl

+ +

URL button

+

+ +
+
keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton label
urlstringURL
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonUrlAuth.html b/data/corefork.telegram.org/constructor/keyboardButtonUrlAuth.html new file mode 100644 index 0000000000..968fd92910 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonUrlAuth.html @@ -0,0 +1,179 @@ + + + + + keyboardButtonUrlAuth + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonUrlAuth

+ +

Button to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.

+

+ +
+
keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
textstringButton label
fwd_textflags.0?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: Services must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
button_idintID of the button to pass to messages.requestUrlAuth
+

Type

+

KeyboardButton

+

Related pages

+

Telegram Login Widget

+

messages.requestUrlAuth

+

Get more info about a Seamless Telegram Login authorization request, for more info click here »

+

urlAuthResultRequest

+

Details about the authorization request, for more info click here »

+

messages.acceptUrlAuth

+

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

+

urlAuthResultAccepted

+

Details about an accepted authorization request, for more info click here »

+

urlAuthResultDefault

+

Details about an accepted authorization request, for more info click here »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/keyboardButtonUserProfile.html b/data/corefork.telegram.org/constructor/keyboardButtonUserProfile.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/keyboardButtonUserProfile.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/labeledPrice.html b/data/corefork.telegram.org/constructor/labeledPrice.html new file mode 100644 index 0000000000..51ee77f2cc --- /dev/null +++ b/data/corefork.telegram.org/constructor/labeledPrice.html @@ -0,0 +1,154 @@ + + + + + labeledPrice + + + + + + + + + + + + + +
+ +
+
+
+ +

labeledPrice

+ +

This object represents a portion of the price for goods or services.

+

+ +
+
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
labelstringPortion label
amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Type

+

LabeledPrice

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/langPackDifference.html b/data/corefork.telegram.org/constructor/langPackDifference.html new file mode 100644 index 0000000000..57ef23f457 --- /dev/null +++ b/data/corefork.telegram.org/constructor/langPackDifference.html @@ -0,0 +1,162 @@ + + + + + langPackDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackDifference

+ +

Changes to the app's localization pack

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious version number
versionintNew version number
stringsVector<LangPackString>Localized strings
+

Type

+

LangPackDifference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/langPackLanguage.html b/data/corefork.telegram.org/constructor/langPackLanguage.html new file mode 100644 index 0000000000..8deee8fc78 --- /dev/null +++ b/data/corefork.telegram.org/constructor/langPackLanguage.html @@ -0,0 +1,202 @@ + + + + + langPackLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackLanguage

+ +

Identifies a localization pack

+

+ +
+
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
officialflags.0?trueWhether the language pack is official
rtlflags.2?trueIs this a localization pack for an RTL language
betaflags.3?trueIs this a beta localization pack?
namestringLanguage name
native_namestringLanguage name in the language itself
lang_codestringLanguage code (pack identifier)
base_lang_codeflags.1?stringIdentifier of a base language pack; may be empty. If a string is missed in the language pack, then it should be fetched from base language pack. Unsupported in custom language packs
plural_codestringA language code to be used to apply plural forms. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
strings_countintTotal number of non-deleted strings from the language pack
translated_countintTotal number of translated strings from the language pack
translations_urlstringLink to language translation interface; empty for custom local language packs
+

Type

+

LangPackLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/langPackString.html b/data/corefork.telegram.org/constructor/langPackString.html new file mode 100644 index 0000000000..1c6097e30e --- /dev/null +++ b/data/corefork.telegram.org/constructor/langPackString.html @@ -0,0 +1,152 @@ + + + + + langPackString + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackString

+ +

Translated localization string

+

+ +
+
langPackString#cad181f6 key:string value:string = LangPackString;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keystringLanguage key
valuestringValue
+

Type

+

LangPackString

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/langPackStringDeleted.html b/data/corefork.telegram.org/constructor/langPackStringDeleted.html new file mode 100644 index 0000000000..8bee249ddd --- /dev/null +++ b/data/corefork.telegram.org/constructor/langPackStringDeleted.html @@ -0,0 +1,147 @@ + + + + + langPackStringDeleted + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackStringDeleted

+ +

Deleted localization string

+

+ +
+
langPackStringDeleted#2979eeb2 key:string = LangPackString;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
keystringLocalization key
+

Type

+

LangPackString

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/langPackStringPluralized.html b/data/corefork.telegram.org/constructor/langPackStringPluralized.html new file mode 100644 index 0000000000..b043b1e7e5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/langPackStringPluralized.html @@ -0,0 +1,182 @@ + + + + + langPackStringPluralized + + + + + + + + + + + + + +
+ +
+
+
+ +

langPackStringPluralized

+ +

A language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info

+

+ +
+
langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
keystringLocalization key
zero_valueflags.0?stringValue for zero objects
one_valueflags.1?stringValue for one object
two_valueflags.2?stringValue for two objects
few_valueflags.3?stringValue for a few objects
many_valueflags.4?stringValue for many objects
other_valuestringDefault value
+

Type

+

LangPackString

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/maskCoords.html b/data/corefork.telegram.org/constructor/maskCoords.html new file mode 100644 index 0000000000..2e0c15bfa8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/maskCoords.html @@ -0,0 +1,169 @@ + + + + + maskCoords + + + + + + + + + + + + + +
+ +
+
+
+ +

maskCoords

+ +

Position on a photo where a mask should be placed

+

The n position indicates where the mask should be placed:

+
    +
  • 0 => Relative to the forehead
  • +
  • 1 => Relative to the eyes
  • +
  • 2 => Relative to the mouth
  • +
  • 3 => Relative to the chin
  • +
+

+ +
+
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
nintPart of the face, relative to which the mask should be placed
xdoubleShift by X-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
ydoubleShift by Y-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
zoomdoubleMask scaling coefficient. (For example, 2.0 means a doubled size)
+

Type

+

MaskCoords

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/message.html b/data/corefork.telegram.org/constructor/message.html new file mode 100644 index 0000000000..803b48ba9f --- /dev/null +++ b/data/corefork.telegram.org/constructor/message.html @@ -0,0 +1,302 @@ + + + + + message + + + + + + + + + + + + + +
+ +
+
+
+ +

message

+ +

A message

+

+ +
+
message#38116ee0 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueIs this an outgoing message
mentionedflags.4?trueWhether we were mentioned in this message
media_unreadflags.5?trueWhether there are unread media attachments in this message
silentflags.13?trueWhether this is a silent message (no notification triggered)
postflags.14?trueWhether this is a channel post
from_scheduledflags.18?trueWhether this is a scheduled message
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
edit_hideflags.21?trueWhether the message should be shown as not modified to the user, even if an edit date is present
pinnedflags.24?trueWhether this message is pinned
idintID of the message
from_idflags.8?PeerID of the sender of the message
peer_idPeerPeer ID, the chat where this message was sent
fwd_fromflags.2?MessageFwdHeaderInfo about forwarded messages
via_bot_idflags.11?longID of the inline bot that generated the message
reply_toflags.3?MessageReplyHeaderReply information
dateintDate of the message
messagestringThe message
mediaflags.9?MessageMediaMedia attachment
reply_markupflags.6?ReplyMarkupReply markup (bot/inline keyboards)
entitiesflags.7?Vector<MessageEntity>Message entities for styled text
viewsflags.10?intView count for channel posts
forwardsflags.10?intForward counter
repliesflags.23?MessageRepliesInfo about post comments (for channels) or message replies (for groups)
edit_dateflags.15?intLast edit date of this message
post_authorflags.16?stringName of the author of this message for channel posts (with signatures enabled)
grouped_idflags.17?longMultiple media messages sent using messages.sendMultiMedia with the same grouped ID indicate an album or media group
restriction_reasonflags.22?Vector<RestrictionReason>Contains the reason why access to this message must be restricted.
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Message

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

Scheduled messages

+

Telegram allows scheduling messages

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Styled text with message entities

+

How to create styled text with message entities

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

messages.sendMultiMedia

+

Send an album or grouped media

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionBotAllowed.html b/data/corefork.telegram.org/constructor/messageActionBotAllowed.html new file mode 100644 index 0000000000..476534f680 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionBotAllowed.html @@ -0,0 +1,149 @@ + + + + + messageActionBotAllowed + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionBotAllowed

+ +

The domain name of the website on which the user has logged in. More about Telegram Login »

+

+ +
+
messageActionBotAllowed#abe9affe domain:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
domainstringThe domain name of the website on which the user has logged in.
+

Type

+

MessageAction

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChannelCreate.html b/data/corefork.telegram.org/constructor/messageActionChannelCreate.html new file mode 100644 index 0000000000..9a6d854272 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChannelCreate.html @@ -0,0 +1,147 @@ + + + + + messageActionChannelCreate + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChannelCreate

+ +

The channel was created

+

+ +
+
messageActionChannelCreate#95d2ac92 title:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
titlestringOriginal channel/supergroup title
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html b/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html new file mode 100644 index 0000000000..e2fd9651d8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html @@ -0,0 +1,155 @@ + + + + + messageActionChannelMigrateFrom + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChannelMigrateFrom

+ +

Indicates the channel was migrated from the specified chat

+

+ +
+
messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
titlestringThe old chat tite
chat_idlongThe old chat ID
+

Type

+

MessageAction

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatAddUser.html b/data/corefork.telegram.org/constructor/messageActionChatAddUser.html new file mode 100644 index 0000000000..729215dee7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatAddUser.html @@ -0,0 +1,147 @@ + + + + + messageActionChatAddUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatAddUser

+ +

New member in the group

+

+ +
+
messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<long>Users that were invited to the chat
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatCreate.html b/data/corefork.telegram.org/constructor/messageActionChatCreate.html new file mode 100644 index 0000000000..e82a3f844c --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatCreate.html @@ -0,0 +1,152 @@ + + + + + messageActionChatCreate + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatCreate

+ +

Group created

+

+ +
+
messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
titlestringGroup name
usersVector<long>List of group members
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatDeletePhoto.html b/data/corefork.telegram.org/constructor/messageActionChatDeletePhoto.html new file mode 100644 index 0000000000..fe91a8de88 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatDeletePhoto.html @@ -0,0 +1,132 @@ + + + + + messageActionChatDeletePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatDeletePhoto

+ +

Group profile photo removed.

+

+ +
+
messageActionChatDeletePhoto#95e3fbef = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatDeleteUser.html b/data/corefork.telegram.org/constructor/messageActionChatDeleteUser.html new file mode 100644 index 0000000000..c9dcd9eafd --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatDeleteUser.html @@ -0,0 +1,147 @@ + + + + + messageActionChatDeleteUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatDeleteUser

+ +

User left the group.

+

+ +
+
messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongLeaving user ID
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatEditPhoto.html b/data/corefork.telegram.org/constructor/messageActionChatEditPhoto.html new file mode 100644 index 0000000000..001d1a193a --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatEditPhoto.html @@ -0,0 +1,147 @@ + + + + + messageActionChatEditPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatEditPhoto

+ +

Group profile changed

+

+ +
+
messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
photoPhotoNew group pofile photo
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatEditTitle.html b/data/corefork.telegram.org/constructor/messageActionChatEditTitle.html new file mode 100644 index 0000000000..aee7316554 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatEditTitle.html @@ -0,0 +1,147 @@ + + + + + messageActionChatEditTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatEditTitle

+ +

Group name changed.

+

+ +
+
messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
titlestringNew group name
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatJoinedByLink.html b/data/corefork.telegram.org/constructor/messageActionChatJoinedByLink.html new file mode 100644 index 0000000000..9857cd5076 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatJoinedByLink.html @@ -0,0 +1,147 @@ + + + + + messageActionChatJoinedByLink + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatJoinedByLink

+ +

A user joined the chat via an invite link

+

+ +
+
messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
inviter_idlongID of the user that created the invite link
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatJoinedByRequest.html b/data/corefork.telegram.org/constructor/messageActionChatJoinedByRequest.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatJoinedByRequest.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html b/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html new file mode 100644 index 0000000000..ebb29d9baf --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html @@ -0,0 +1,150 @@ + + + + + messageActionChatMigrateTo + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatMigrateTo

+ +

Indicates the chat was migrated to the specified supergroup

+

+ +
+
messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongThe supergroup it was migrated to
+

Type

+

MessageAction

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionContactSignUp.html b/data/corefork.telegram.org/constructor/messageActionContactSignUp.html new file mode 100644 index 0000000000..b530297103 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionContactSignUp.html @@ -0,0 +1,132 @@ + + + + + messageActionContactSignUp + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionContactSignUp

+ +

A contact just signed up to telegram

+

+ +
+
messageActionContactSignUp#f3f25f76 = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionCustomAction.html b/data/corefork.telegram.org/constructor/messageActionCustomAction.html new file mode 100644 index 0000000000..b42c1dcff1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionCustomAction.html @@ -0,0 +1,147 @@ + + + + + messageActionCustomAction + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionCustomAction

+ +

Custom action (most likely not supported by the current layer, an upgrade might be needed)

+

+ +
+
messageActionCustomAction#fae69f56 message:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messagestringAction message
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionGameScore.html b/data/corefork.telegram.org/constructor/messageActionGameScore.html new file mode 100644 index 0000000000..509833f06d --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionGameScore.html @@ -0,0 +1,152 @@ + + + + + messageActionGameScore + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionGameScore

+ +

Someone scored in a game

+

+ +
+
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
game_idlongGame ID
scoreintScore
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionGeoProximityReached.html b/data/corefork.telegram.org/constructor/messageActionGeoProximityReached.html new file mode 100644 index 0000000000..aad2d2508b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionGeoProximityReached.html @@ -0,0 +1,160 @@ + + + + + messageActionGeoProximityReached + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionGeoProximityReached

+ +

A user of the chat is now in proximity of another user

+

+ +
+
messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
from_idPeerThe user or chat that is now in proximity of to_id
to_idPeerThe user or chat that subscribed to live geolocation proximity alerts
distanceintDistance, in meters (0-100000)
+

Type

+

MessageAction

+

Related pages

+

Live geolocation

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionGroupCall.html b/data/corefork.telegram.org/constructor/messageActionGroupCall.html new file mode 100644 index 0000000000..1e3034f94f --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionGroupCall.html @@ -0,0 +1,157 @@ + + + + + messageActionGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionGroupCall

+ +

The group call has ended

+

+ +
+
messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallGroup call
durationflags.0?intGroup call duration
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionGroupCallScheduled.html b/data/corefork.telegram.org/constructor/messageActionGroupCallScheduled.html new file mode 100644 index 0000000000..6f1ed33930 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionGroupCallScheduled.html @@ -0,0 +1,152 @@ + + + + + messageActionGroupCallScheduled + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionGroupCallScheduled

+ +

A group call was scheduled

+

+ +
+
messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
schedule_dateintWhen is this group call scheduled to start
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionHistoryClear.html b/data/corefork.telegram.org/constructor/messageActionHistoryClear.html new file mode 100644 index 0000000000..99fff82af4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionHistoryClear.html @@ -0,0 +1,132 @@ + + + + + messageActionHistoryClear + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionHistoryClear

+ +

Chat history was cleared

+

+ +
+
messageActionHistoryClear#9fbab604 = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html b/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html new file mode 100644 index 0000000000..c540c2dcbf --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html @@ -0,0 +1,152 @@ + + + + + messageActionInviteToGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionInviteToGroupCall

+ +

A set of users was invited to the group call

+

+ +
+
messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
usersVector<long>The invited users
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionPaymentSent.html b/data/corefork.telegram.org/constructor/messageActionPaymentSent.html new file mode 100644 index 0000000000..83e3cec8f4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionPaymentSent.html @@ -0,0 +1,154 @@ + + + + + messageActionPaymentSent + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionPaymentSent

+ +

A payment was sent

+

+ +
+
messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Type

+

MessageAction

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionPaymentSentMe.html b/data/corefork.telegram.org/constructor/messageActionPaymentSentMe.html new file mode 100644 index 0000000000..6f63572456 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionPaymentSentMe.html @@ -0,0 +1,179 @@ + + + + + messageActionPaymentSentMe + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionPaymentSentMe

+ +

A user just sent a payment to me (a bot)

+

+ +
+
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
chargePaymentChargeProvider payment identifier
+

Type

+

MessageAction

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionPhoneCall.html b/data/corefork.telegram.org/constructor/messageActionPhoneCall.html new file mode 100644 index 0000000000..ddde5c6851 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionPhoneCall.html @@ -0,0 +1,167 @@ + + + + + messageActionPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionPhoneCall

+ +

A phone call

+

+ +
+
messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.2?trueIs this a video call?
call_idlongCall ID
reasonflags.0?PhoneCallDiscardReasonIf the call has ended, the reason why it ended
durationflags.1?intDuration of the call in seconds
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionPinMessage.html b/data/corefork.telegram.org/constructor/messageActionPinMessage.html new file mode 100644 index 0000000000..6bcfaa01db --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionPinMessage.html @@ -0,0 +1,132 @@ + + + + + messageActionPinMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionPinMessage

+ +

A message was pinned

+

+ +
+
messageActionPinMessage#94bd38ed = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionScreenshotTaken.html b/data/corefork.telegram.org/constructor/messageActionScreenshotTaken.html new file mode 100644 index 0000000000..d83a9e6eb5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionScreenshotTaken.html @@ -0,0 +1,132 @@ + + + + + messageActionScreenshotTaken + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionScreenshotTaken

+ +

A screenshot of the chat was taken

+

+ +
+
messageActionScreenshotTaken#4792929b = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionSecureValuesSent.html b/data/corefork.telegram.org/constructor/messageActionSecureValuesSent.html new file mode 100644 index 0000000000..8561b5e9f9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionSecureValuesSent.html @@ -0,0 +1,149 @@ + + + + + messageActionSecureValuesSent + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSecureValuesSent

+ +

Request for secure telegram passport values was sent

+

+ +
+
messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typesVector<SecureValueType>Secure value types
+

Type

+

MessageAction

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html b/data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html new file mode 100644 index 0000000000..f0be08649d --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html @@ -0,0 +1,154 @@ + + + + + messageActionSecureValuesSentMe + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSecureValuesSentMe

+ +

Secure telegram passport values were received

+

+ +
+
messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
valuesVector<SecureValue>Vector with information about documents and other Telegram Passport elements that were shared with the bot
credentialsSecureCredentialsEncryptedEncrypted credentials required to decrypt the data
+

Type

+

MessageAction

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html b/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html new file mode 100644 index 0000000000..05bbbd1193 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html @@ -0,0 +1,147 @@ + + + + + messageActionSetChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSetChatTheme

+ +

The chat theme was changed

+

+ +
+
messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringThe emoji that identifies a chat theme
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html b/data/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html new file mode 100644 index 0000000000..de41cff50b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html @@ -0,0 +1,147 @@ + + + + + messageActionSetMessagesTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSetMessagesTTL

+ +

The Time-To-Live of messages in this chat was changed.

+

+ +
+
messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
periodintNew Time-To-Live
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEmpty.html b/data/corefork.telegram.org/constructor/messageEmpty.html new file mode 100644 index 0000000000..56164411bb --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEmpty.html @@ -0,0 +1,157 @@ + + + + + messageEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEmpty

+ +

Empty constructor, non-existent message.

+

+ +
+
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintMessage identifier
peer_idflags.0?PeerPeer ID, the chat where this message was sent
+

Type

+

Message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityBankCard.html b/data/corefork.telegram.org/constructor/messageEntityBankCard.html new file mode 100644 index 0000000000..30ec1386c2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityBankCard.html @@ -0,0 +1,152 @@ + + + + + messageEntityBankCard + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBankCard

+ +

Indicates a credit card number

+

+ +
+
messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityBlockquote.html b/data/corefork.telegram.org/constructor/messageEntityBlockquote.html new file mode 100644 index 0000000000..f25a193958 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityBlockquote.html @@ -0,0 +1,152 @@ + + + + + messageEntityBlockquote + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBlockquote

+ +

Message entity representing a block quote.

+

+ +
+
messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityBold.html b/data/corefork.telegram.org/constructor/messageEntityBold.html new file mode 100644 index 0000000000..8977e4bf1e --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityBold.html @@ -0,0 +1,152 @@ + + + + + messageEntityBold + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBold

+ +

Message entity representing bold text.

+

+ +
+
messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityBotCommand.html b/data/corefork.telegram.org/constructor/messageEntityBotCommand.html new file mode 100644 index 0000000000..6f5f34d79b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityBotCommand.html @@ -0,0 +1,152 @@ + + + + + messageEntityBotCommand + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBotCommand

+ +

Message entity representing a bot /command

+

+ +
+
messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityCashtag.html b/data/corefork.telegram.org/constructor/messageEntityCashtag.html new file mode 100644 index 0000000000..0b768b7261 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityCashtag.html @@ -0,0 +1,152 @@ + + + + + messageEntityCashtag + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityCashtag

+ +

Message entity representing a $cashtag.

+

+ +
+
messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityCode.html b/data/corefork.telegram.org/constructor/messageEntityCode.html new file mode 100644 index 0000000000..151fc0252b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityCode.html @@ -0,0 +1,152 @@ + + + + + messageEntityCode + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityCode

+ +

Message entity representing a codeblock.

+

+ +
+
messageEntityCode#28a20571 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityEmail.html b/data/corefork.telegram.org/constructor/messageEntityEmail.html new file mode 100644 index 0000000000..95df1d703d --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityEmail.html @@ -0,0 +1,152 @@ + + + + + messageEntityEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityEmail

+ +

Message entity representing an email@example.com.

+

+ +
+
messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityItalic.html b/data/corefork.telegram.org/constructor/messageEntityItalic.html new file mode 100644 index 0000000000..953abc20c5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityItalic.html @@ -0,0 +1,152 @@ + + + + + messageEntityItalic + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityItalic

+ +

Message entity representing italic text.

+

+ +
+
messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityMentionName.html b/data/corefork.telegram.org/constructor/messageEntityMentionName.html new file mode 100644 index 0000000000..7acadba1f3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityMentionName.html @@ -0,0 +1,162 @@ + + + + + messageEntityMentionName + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityMentionName

+ +

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

+

+ +
+
messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idlongIdentifier of the user that was mentioned
+

Type

+

MessageEntity

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

inputMessageEntityMentionName

+

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityPhone.html b/data/corefork.telegram.org/constructor/messageEntityPhone.html new file mode 100644 index 0000000000..5f98f061f9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityPhone.html @@ -0,0 +1,152 @@ + + + + + messageEntityPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityPhone

+ +

Message entity representing a phone number.

+

+ +
+
messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityPre.html b/data/corefork.telegram.org/constructor/messageEntityPre.html new file mode 100644 index 0000000000..c331610929 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityPre.html @@ -0,0 +1,157 @@ + + + + + messageEntityPre + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityPre

+ +

Message entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.

+

+ +
+
messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
languagestringProgramming language of the code
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntitySpoiler.html b/data/corefork.telegram.org/constructor/messageEntitySpoiler.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntitySpoiler.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityStrike.html b/data/corefork.telegram.org/constructor/messageEntityStrike.html new file mode 100644 index 0000000000..a4879d3178 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityStrike.html @@ -0,0 +1,152 @@ + + + + + messageEntityStrike + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityStrike

+ +

Message entity representing strikethrough text.

+

+ +
+
messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityTextUrl.html b/data/corefork.telegram.org/constructor/messageEntityTextUrl.html new file mode 100644 index 0000000000..ad9939d2e6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityTextUrl.html @@ -0,0 +1,160 @@ + + + + + messageEntityTextUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityTextUrl

+ +

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

+

+ +
+
messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
urlstringThe actual URL
+

Type

+

MessageEntity

+

Related pages

+

messageEntityUrl

+

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityUnderline.html b/data/corefork.telegram.org/constructor/messageEntityUnderline.html new file mode 100644 index 0000000000..717f79dafe --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityUnderline.html @@ -0,0 +1,152 @@ + + + + + messageEntityUnderline + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUnderline

+ +

Message entity representing underlined text.

+

+ +
+
messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityUnknown.html b/data/corefork.telegram.org/constructor/messageEntityUnknown.html new file mode 100644 index 0000000000..832b36a72f --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityUnknown.html @@ -0,0 +1,152 @@ + + + + + messageEntityUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUnknown

+ +

Unknown message entity

+

+ +
+
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityUrl.html b/data/corefork.telegram.org/constructor/messageEntityUrl.html new file mode 100644 index 0000000000..3188e3d641 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityUrl.html @@ -0,0 +1,155 @@ + + + + + messageEntityUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUrl

+ +

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

+

+ +
+
messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+

Related pages

+

messageEntityTextUrl

+

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageFwdHeader.html b/data/corefork.telegram.org/constructor/messageFwdHeader.html new file mode 100644 index 0000000000..0c80cd4d17 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageFwdHeader.html @@ -0,0 +1,195 @@ + + + + + messageFwdHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

messageFwdHeader

+ +

Info about a forwarded message

+

+ +
+
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
importedflags.7?trueWhether this message was imported from a foreign chat service, click here for more info »
from_idflags.0?PeerThe ID of the user that originally sent the message
from_nameflags.5?stringThe name of the user that originally sent the message
dateintWhen was the message originally sent
channel_postflags.2?intID of the channel message that was forwarded
post_authorflags.3?stringFor channels and if signatures are enabled, author of the channel message
saved_from_peerflags.4?PeerOnly for messages forwarded to the current user (inputPeerSelf), full info about the user/channel that originally sent the message
saved_from_msg_idflags.4?intOnly for messages forwarded to the current user (inputPeerSelf), ID of the message that was forwarded from the original user/channel
psa_typeflags.6?stringPSA type
+

Type

+

MessageFwdHeader

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageInteractionCounters.html b/data/corefork.telegram.org/constructor/messageInteractionCounters.html new file mode 100644 index 0000000000..24569b82b1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageInteractionCounters.html @@ -0,0 +1,157 @@ + + + + + messageInteractionCounters + + + + + + + + + + + + + +
+ +
+
+
+ +

messageInteractionCounters

+ +

Message interaction counters

+

+ +
+
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idintMessage ID
viewsintViews
forwardsintNumber of times this message was forwarded
+

Type

+

MessageInteractionCounters

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaAudio.html b/data/corefork.telegram.org/constructor/messageMediaAudio.html new file mode 100644 index 0000000000..d72b9a6fa2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaAudio.html @@ -0,0 +1,147 @@ + + + + + messageMediaAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaAudio

+ +

Attached audio file.

+

+ +
+
Constructor schema is available as of layer 46. Switch »

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
audioAudioAudi file
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaContact.html b/data/corefork.telegram.org/constructor/messageMediaContact.html new file mode 100644 index 0000000000..f97d4ee759 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaContact.html @@ -0,0 +1,167 @@ + + + + + messageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaContact

+ +

Attached contact.

+

+ +
+
messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringVCARD of contact
user_idlongUser identifier or 0, if the user with the given phone number is not registered
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaDice.html b/data/corefork.telegram.org/constructor/messageMediaDice.html new file mode 100644 index 0000000000..99f36c4fe1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaDice.html @@ -0,0 +1,155 @@ + + + + + messageMediaDice + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaDice

+ +

Dice-based animated sticker

+

+ +
+
messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
valueintDice value
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
+

Type

+

MessageMedia

+

Related pages

+

Dice

+

Telegram supports sending animated dice emojis.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaDocument.html b/data/corefork.telegram.org/constructor/messageMediaDocument.html new file mode 100644 index 0000000000..7006a9a08a --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaDocument.html @@ -0,0 +1,157 @@ + + + + + messageMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaDocument

+ +

Document (video, audio, voice, sticker, any media type except photo)

+

+ +
+
messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
documentflags.0?DocumentAttached document
ttl_secondsflags.2?intTime to live of self-destructing document
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaEmpty.html b/data/corefork.telegram.org/constructor/messageMediaEmpty.html new file mode 100644 index 0000000000..4deab67d92 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaEmpty.html @@ -0,0 +1,132 @@ + + + + + messageMediaEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaEmpty

+ +

Empty constructor.

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaGame.html b/data/corefork.telegram.org/constructor/messageMediaGame.html new file mode 100644 index 0000000000..e6826ee81a --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaGame.html @@ -0,0 +1,147 @@ + + + + + messageMediaGame + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaGame

+ +

Telegram game

+

+ +
+
messageMediaGame#fdb19008 game:Game = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
gameGameGame
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaGeo.html b/data/corefork.telegram.org/constructor/messageMediaGeo.html new file mode 100644 index 0000000000..e74f8053db --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaGeo.html @@ -0,0 +1,147 @@ + + + + + messageMediaGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaGeo

+ +

Attached map.

+

+ +
+
messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
geoGeoPointGeoPoint
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaGeoLive.html b/data/corefork.telegram.org/constructor/messageMediaGeoLive.html new file mode 100644 index 0000000000..b03760c2ef --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaGeoLive.html @@ -0,0 +1,170 @@ + + + + + messageMediaGeoLive + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaGeoLive

+ +

Indicates a live geolocation

+

+ +
+
messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodintValidity period of provided geolocation
proximity_notification_radiusflags.1?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000).
+

Type

+

MessageMedia

+

Related pages

+

Live geolocation

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaInvoice.html b/data/corefork.telegram.org/constructor/messageMediaInvoice.html new file mode 100644 index 0000000000..c88beca4c9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaInvoice.html @@ -0,0 +1,198 @@ + + + + + messageMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaInvoice

+ +

Invoice

+

+ +
+
messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueWhether the shipping address was requested
testflags.3?trueWhether this is an example invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
receipt_msg_idflags.2?intMessage ID of receipt: if set, clients should change the text of the first keyboardButtonBuy button always attached to the message to a localized version of the word Receipt
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
start_paramstringUnique bot deep-linking parameter that can be used to generate this invoice
+

Type

+

MessageMedia

+

Related pages

+

keyboardButtonBuy

+

Button to buy a product

+

message

+

A message

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaPhoto.html b/data/corefork.telegram.org/constructor/messageMediaPhoto.html new file mode 100644 index 0000000000..34082f6f99 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaPhoto.html @@ -0,0 +1,157 @@ + + + + + messageMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaPhoto

+ +

Attached photo.

+

+ +
+
messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
photoflags.0?PhotoPhoto
ttl_secondsflags.2?intTime to live in seconds of self-destructing photo
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaPoll.html b/data/corefork.telegram.org/constructor/messageMediaPoll.html new file mode 100644 index 0000000000..dc390a129c --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaPoll.html @@ -0,0 +1,152 @@ + + + + + messageMediaPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaPoll

+ +

Poll

+

+ +
+
messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
pollPollThe poll
resultsPollResultsThe results of the poll
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaUnsupported.html b/data/corefork.telegram.org/constructor/messageMediaUnsupported.html new file mode 100644 index 0000000000..1a624ba7b4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaUnsupported.html @@ -0,0 +1,132 @@ + + + + + messageMediaUnsupported + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaUnsupported

+ +

Current version of the client does not support this media type.

+

+ +
+
messageMediaUnsupported#9f84f49e = MessageMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaVenue.html b/data/corefork.telegram.org/constructor/messageMediaVenue.html new file mode 100644 index 0000000000..86202f854c --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaVenue.html @@ -0,0 +1,172 @@ + + + + + messageMediaVenue + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaVenue

+ +

Venue

+

+ +
+
messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaVideo.html b/data/corefork.telegram.org/constructor/messageMediaVideo.html new file mode 100644 index 0000000000..1d6b22f56b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaVideo.html @@ -0,0 +1,147 @@ + + + + + messageMediaVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaVideo

+ +

Attached video.

+

+ +
+
Constructor schema is available as of layer 28. Switch »

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
videoVideoVideo
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaWebPage.html b/data/corefork.telegram.org/constructor/messageMediaWebPage.html new file mode 100644 index 0000000000..2f019bbafe --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaWebPage.html @@ -0,0 +1,147 @@ + + + + + messageMediaWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaWebPage

+ +

Preview of webpage

+

+ +
+
messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
webpageWebPageWebpage preview
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messagePeerReaction.html b/data/corefork.telegram.org/constructor/messagePeerReaction.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messagePeerReaction.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageRange.html b/data/corefork.telegram.org/constructor/messageRange.html new file mode 100644 index 0000000000..92ed7ee853 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageRange.html @@ -0,0 +1,152 @@ + + + + + messageRange + + + + + + + + + + + + + +
+ +
+
+
+ +

messageRange

+ +

Indicates a range of chat messages

+

+ +
+
messageRange#ae30253 min_id:int max_id:int = MessageRange;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
min_idintStart of range (message ID)
max_idintEnd of range (message ID)
+

Type

+

MessageRange

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageReactions.html b/data/corefork.telegram.org/constructor/messageReactions.html new file mode 100644 index 0000000000..8270c5ba16 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageReactions.html @@ -0,0 +1,162 @@ + + + + + messageReactions + + + + + + + + + + + + + +
+ +
+
+
+ +

messageReactions

+ +

Message reactions

+

+ +
+
messageReactions#4f2b9479 flags:# min:flags.0?true can_see_list:flags.2?true results:Vector<ReactionCount> recent_reactions:flags.1?Vector<MessagePeerReaction> = MessageReactions;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
minflags.0?trueSimilar to min objects, used for message reaction constructors that are the same for all users so they don't have the reactions sent by the current user (you can use messages.getMessagesReactions to get the full reaction info).
resultsVector<ReactionCount>Reactions
+

Type

+

MessageReactions

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

messages.getMessagesReactions

+

Get message reactions

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageReplies.html b/data/corefork.telegram.org/constructor/messageReplies.html new file mode 100644 index 0000000000..9af23fc961 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageReplies.html @@ -0,0 +1,189 @@ + + + + + messageReplies + + + + + + + + + + + + + +
+ +
+
+
+ +

messageReplies

+ +

Info about the comment section of a channel post, or a simple message thread

+

+ +
+
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
commentsflags.0?trueWhether this constructor contains information about the comment section of a channel post, or a simple message thread
repliesintContains the total number of replies in this thread or comment section.
replies_ptsintPTS of the message that started this thread.
recent_repliersflags.1?Vector<Peer>For channel post comments, contains information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.
channel_idflags.0?longFor channel post comments, contains the ID of the associated discussion supergroup
max_idflags.2?intID of the latest message in this thread or comment section.
read_max_idflags.3?intContains the ID of the latest read message in this thread or comment section.
+

Type

+

MessageReplies

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageReplyHeader.html b/data/corefork.telegram.org/constructor/messageReplyHeader.html new file mode 100644 index 0000000000..9a8aebe6ea --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageReplyHeader.html @@ -0,0 +1,165 @@ + + + + + messageReplyHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

messageReplyHeader

+ +

Message replies and thread information

+

+ +
+
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
reply_to_msg_idintID of message to which this message is replying
reply_to_peer_idflags.0?PeerFor replies sent in channel discussion threads of which the current user is not a member, the discussion group ID
reply_to_top_idflags.1?intID of the message that started this message thread
+

Type

+

MessageReplyHeader

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageService.html b/data/corefork.telegram.org/constructor/messageService.html new file mode 100644 index 0000000000..cd5703d77e --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageService.html @@ -0,0 +1,212 @@ + + + + + messageService + + + + + + + + + + + + + +
+ +
+
+
+ +

messageService

+ +

Indicates a service message

+

+ +
+
messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether the message contains unread media
silentflags.13?trueWhether the message is silent
postflags.14?trueWhether it's a channel post
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
idintMessage ID
from_idflags.8?PeerID of the sender of this message
peer_idPeerSender of service message
reply_toflags.3?MessageReplyHeaderReply (thread) information
dateintMessage date
actionMessageActionEvent connected with the service message
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageUserVote.html b/data/corefork.telegram.org/constructor/messageUserVote.html new file mode 100644 index 0000000000..1b61c472ff --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageUserVote.html @@ -0,0 +1,157 @@ + + + + + messageUserVote + + + + + + + + + + + + + +
+ +
+
+
+ +

messageUserVote

+ +

How a user voted in a poll

+

+ +
+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
optionbytesThe option chosen by the user
dateintWhen did the user cast the vote
+

Type

+

MessageUserVote

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageUserVoteInputOption.html b/data/corefork.telegram.org/constructor/messageUserVoteInputOption.html new file mode 100644 index 0000000000..0ad1198fec --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageUserVoteInputOption.html @@ -0,0 +1,155 @@ + + + + + messageUserVoteInputOption + + + + + + + + + + + + + +
+ +
+
+
+ +

messageUserVoteInputOption

+ +

How a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)

+

+ +
+
messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongThe user that voted for the queried option
dateintWhen did the user cast the vote
+

Type

+

MessageUserVote

+

Related pages

+

messages.getPollVotes

+

Get poll results for non-anonymous polls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageUserVoteMultiple.html b/data/corefork.telegram.org/constructor/messageUserVoteMultiple.html new file mode 100644 index 0000000000..75394bb65d --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageUserVoteMultiple.html @@ -0,0 +1,157 @@ + + + + + messageUserVoteMultiple + + + + + + + + + + + + + +
+ +
+
+
+ +

messageUserVoteMultiple

+ +

How a user voted in a multiple-choice poll

+

+ +
+
messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
optionsVector<bytes>Options chosen by the user
dateintWhen did the user cast their votes
+

Type

+

MessageUserVote

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageViews.html b/data/corefork.telegram.org/constructor/messageViews.html new file mode 100644 index 0000000000..52706c2ae1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageViews.html @@ -0,0 +1,165 @@ + + + + + messageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messageViews

+ +

View, forward counter + info about replies of a specific message

+

+ +
+
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
viewsflags.0?intViewcount of message
forwardsflags.1?intForward count of message
repliesflags.2?MessageRepliesReply and thread information of message
+

Type

+

MessageViews

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.affectedFoundMessages b/data/corefork.telegram.org/constructor/messages.affectedFoundMessages new file mode 100644 index 0000000000..dea499bc7f --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.affectedFoundMessages @@ -0,0 +1,165 @@ + + + + + messages.affectedFoundMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.affectedFoundMessages

+ +

Messages found and affected by changes

+

+ +
+
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
offsetintIf bigger than zero, the request must be repeated to remove more messages
messagesVector<int>Affected message IDs
+

Type

+

messages.AffectedFoundMessages

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.affectedHistory b/data/corefork.telegram.org/constructor/messages.affectedHistory new file mode 100644 index 0000000000..2c0bbb68ca --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.affectedHistory @@ -0,0 +1,157 @@ + + + + + messages.affectedHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.affectedHistory

+ +

Affected part of communication history with the user or in a chat.

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintNumber of events occured in a text box
pts_countintNumber of affected events
offsetintIf a parameter contains positive value, it is necessary to repeat the method call using the given value; during the proceeding of all the history the value itself shall gradually decrease
+

Type

+

messages.AffectedHistory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.affectedMessages b/data/corefork.telegram.org/constructor/messages.affectedMessages new file mode 100644 index 0000000000..0cab9b4acf --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.affectedMessages @@ -0,0 +1,155 @@ + + + + + messages.affectedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.affectedMessages

+ +

Events affected by operation

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

messages.AffectedMessages

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.allStickers b/data/corefork.telegram.org/constructor/messages.allStickers new file mode 100644 index 0000000000..239b06a363 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.allStickers @@ -0,0 +1,155 @@ + + + + + messages.allStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.allStickers

+ +

Info about all installed stickers

+

+ +
+
messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
setsVector<StickerSet>All stickersets
+

Type

+

messages.AllStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.allStickersNotModified b/data/corefork.telegram.org/constructor/messages.allStickersNotModified new file mode 100644 index 0000000000..9de6798689 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.allStickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.allStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.allStickersNotModified

+ +

Info about all installed stickers hasn't changed

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.AllStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.archivedStickers b/data/corefork.telegram.org/constructor/messages.archivedStickers new file mode 100644 index 0000000000..082d3d70fc --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.archivedStickers @@ -0,0 +1,152 @@ + + + + + messages.archivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.archivedStickers

+ +

Archived stickersets

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of archived stickers
setsVector<StickerSetCovered>Archived stickersets
+

Type

+

messages.ArchivedStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.availableReactions b/data/corefork.telegram.org/constructor/messages.availableReactions new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.availableReactions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.availableReactionsNotModified b/data/corefork.telegram.org/constructor/messages.availableReactionsNotModified new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.availableReactionsNotModified @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.botCallbackAnswer b/data/corefork.telegram.org/constructor/messages.botCallbackAnswer new file mode 100644 index 0000000000..b9ab7e8065 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.botCallbackAnswer @@ -0,0 +1,177 @@ + + + + + messages.botCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.botCallbackAnswer

+ +

Callback answer sent by the bot in response to a button press

+

+ +
+
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
alertflags.1?trueWhether an alert should be shown to the user instead of a toast notification
has_urlflags.3?trueWhether an URL is present
native_uiflags.4?trueWhether to show games in WebView or in native UI.
messageflags.0?stringAlert to show
urlflags.2?stringURL to open
cache_timeintFor how long should this answer be cached
+

Type

+

messages.BotCallbackAnswer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.botResults b/data/corefork.telegram.org/constructor/messages.botResults new file mode 100644 index 0000000000..a55ead271c --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.botResults @@ -0,0 +1,182 @@ + + + + + messages.botResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.botResults

+ +

Result of a query to an inline bot

+

+ +
+
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueWhether the result is a picture gallery
query_idlongQuery ID
next_offsetflags.1?stringThe next offset to use when navigating through results
switch_pmflags.2?InlineBotSwitchPMWhether the bot requested the user to message him in private
resultsVector<BotInlineResult>The results
cache_timeintCaching validity of the results
usersVector<User>Users mentioned in the results
+

Type

+

messages.BotResults

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.channelMessages b/data/corefork.telegram.org/constructor/messages.channelMessages new file mode 100644 index 0000000000..8eaeb17a56 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.channelMessages @@ -0,0 +1,185 @@ + + + + + messages.channelMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.channelMessages

+ +

Channel messages

+

+ +
+
messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, returned results may be inexact
ptsintEvent count after generation
countintTotal number of results were found server-side (may not be all included here)
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>Found messages
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

messages.Messages

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites b/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites new file mode 100644 index 0000000000..a7b1573da6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites @@ -0,0 +1,152 @@ + + + + + messages.chatAdminsWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatAdminsWithInvites

+ +

Info about chat invites generated by admins.

+

+ +
+
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
adminsVector<ChatAdminWithInvites>Info about chat invites generated by admins.
usersVector<User>Mentioned users
+

Type

+

messages.ChatAdminsWithInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.chatFull b/data/corefork.telegram.org/constructor/messages.chatFull new file mode 100644 index 0000000000..23999c990b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.chatFull @@ -0,0 +1,157 @@ + + + + + messages.chatFull + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatFull

+ +

Extended info on chat and auxiliary data.

+

+ +
+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
full_chatChatFullExtended info on a chat
chatsVector<Chat>List containing basic info on chat
usersVector<User>List of users mentioned above
+

Type

+

messages.ChatFull

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.chatInviteImporters b/data/corefork.telegram.org/constructor/messages.chatInviteImporters new file mode 100644 index 0000000000..30a35db497 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.chatInviteImporters @@ -0,0 +1,157 @@ + + + + + messages.chatInviteImporters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatInviteImporters

+ +

Info about the users that joined the chat using a specific chat invite

+

+ +
+
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of users that joined
importersVector<ChatInviteImporter>The users that joined
usersVector<User>The users that joined
+

Type

+

messages.ChatInviteImporters

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.chats b/data/corefork.telegram.org/constructor/messages.chats new file mode 100644 index 0000000000..f461e169cd --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.chats @@ -0,0 +1,147 @@ + + + + + messages.chats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chats

+ +

List of chats with auxiliary data.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<Chat>List of chats
+

Type

+

messages.Chats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.chatsSlice b/data/corefork.telegram.org/constructor/messages.chatsSlice new file mode 100644 index 0000000000..d6916decc5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.chatsSlice @@ -0,0 +1,155 @@ + + + + + messages.chatsSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatsSlice

+ +

Partial list of chats, more would have to be fetched with pagination

+

+ +
+
messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of results that were found server-side (not all are included in chats)
chatsVector<Chat>Chats
+

Type

+

messages.Chats

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.checkedHistoryImportPeer b/data/corefork.telegram.org/constructor/messages.checkedHistoryImportPeer new file mode 100644 index 0000000000..19f9a41b1e --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.checkedHistoryImportPeer @@ -0,0 +1,150 @@ + + + + + messages.checkedHistoryImportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkedHistoryImportPeer

+ +

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

+

+ +
+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
confirm_textstringA confirmation text to be shown to the user, upon importing chat history ».
+

Type

+

messages.CheckedHistoryImportPeer

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.dhConfig b/data/corefork.telegram.org/constructor/messages.dhConfig new file mode 100644 index 0000000000..089a96d996 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.dhConfig @@ -0,0 +1,162 @@ + + + + + messages.dhConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.dhConfig

+ +

New set of configuring parameters.

+

+ +
+
messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
gintNew value prime, see Wikipedia
pbytesNew value primitive root, see Wikipedia
versionintVestion of set of parameters
randombytesRandom sequence of bytes of assigned length
+

Type

+

messages.DhConfig

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.dhConfigNotModified b/data/corefork.telegram.org/constructor/messages.dhConfigNotModified new file mode 100644 index 0000000000..2d87263ea9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.dhConfigNotModified @@ -0,0 +1,147 @@ + + + + + messages.dhConfigNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.dhConfigNotModified

+ +

Configuring parameters did not change.

+

+ +
+
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
randombytesRandom sequence of bytes of assigned length
+

Type

+

messages.DhConfig

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.dialogs b/data/corefork.telegram.org/constructor/messages.dialogs new file mode 100644 index 0000000000..163359b086 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.dialogs @@ -0,0 +1,162 @@ + + + + + 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.dialogsSlice b/data/corefork.telegram.org/constructor/messages.dialogsSlice new file mode 100644 index 0000000000..5647267de4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.dialogsSlice @@ -0,0 +1,167 @@ + + + + + messages.dialogsSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.dialogsSlice

+ +

Incomplete list of dialogs with messages and auxiliary data.

+

+ +
+
messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of dialogs
dialogsVector<Dialog>List of dialogs
messagesVector<Message>List of last messages from dialogs
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
+

Type

+

messages.Dialogs

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.discussionMessage b/data/corefork.telegram.org/constructor/messages.discussionMessage new file mode 100644 index 0000000000..4032d07ff4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.discussionMessage @@ -0,0 +1,185 @@ + + + + + messages.discussionMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.discussionMessage

+ +

Information about a message thread

+

+ +
+
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
messagesVector<Message>Discussion messages
max_idflags.0?intMessage ID of latest reply in this thread
read_inbox_max_idflags.1?intMessage ID of latest read incoming message in this thread
read_outbox_max_idflags.2?intMessage ID of latest read outgoing message in this thread
unread_countintNumber of unread messages
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
+

Type

+

messages.DiscussionMessage

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.exportedChatInvite b/data/corefork.telegram.org/constructor/messages.exportedChatInvite new file mode 100644 index 0000000000..17ad24a5cc --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.exportedChatInvite @@ -0,0 +1,152 @@ + + + + + messages.exportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInvite

+ +

Info about a chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteInfo about the chat invite
usersVector<User>Mentioned users
+

Type

+

messages.ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced b/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced new file mode 100644 index 0000000000..1254cb147b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced @@ -0,0 +1,157 @@ + + + + + messages.exportedChatInviteReplaced + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInviteReplaced

+ +

The specified chat invite was replaced with another one

+

+ +
+
messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteThe replaced chat invite
new_inviteExportedChatInviteThe invite that replaces the previous invite
usersVector<User>Mentioned users
+

Type

+

messages.ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.exportedChatInvites b/data/corefork.telegram.org/constructor/messages.exportedChatInvites new file mode 100644 index 0000000000..19b8187639 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.exportedChatInvites @@ -0,0 +1,157 @@ + + + + + messages.exportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInvites

+ +

Info about chat invites exported by a certain admin.

+

+ +
+
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of invites exported by the admin
invitesVector<ExportedChatInvite>Exported invites
usersVector<User>Info about the admin
+

Type

+

messages.ExportedChatInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.favedStickers b/data/corefork.telegram.org/constructor/messages.favedStickers new file mode 100644 index 0000000000..01c2c888df --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.favedStickers @@ -0,0 +1,160 @@ + + + + + messages.favedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.favedStickers

+ +

Favorited stickers

+

+ +
+
messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Favorited stickers
+

Type

+

messages.FavedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.favedStickersNotModified b/data/corefork.telegram.org/constructor/messages.favedStickersNotModified new file mode 100644 index 0000000000..17ef968907 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.favedStickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.favedStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.favedStickersNotModified

+ +

No new favorited stickers were found

+

+ +
+
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.FavedStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.featuredStickers b/data/corefork.telegram.org/constructor/messages.featuredStickers new file mode 100644 index 0000000000..83ae018504 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.featuredStickers @@ -0,0 +1,165 @@ + + + + + messages.featuredStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.featuredStickers

+ +

Featured stickersets

+

+ +
+
messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
countintTotal number of featured stickers
setsVector<StickerSetCovered>Featured stickersets
unreadVector<long>IDs of new featured stickersets
+

Type

+

messages.FeaturedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified b/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified new file mode 100644 index 0000000000..e7b243cc91 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified @@ -0,0 +1,147 @@ + + + + + messages.featuredStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.featuredStickersNotModified

+ +

Featured stickers haven't changed

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of featured stickers
+

Type

+

messages.FeaturedStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.foundStickerSets b/data/corefork.telegram.org/constructor/messages.foundStickerSets new file mode 100644 index 0000000000..ef01dfcd4b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.foundStickerSets @@ -0,0 +1,155 @@ + + + + + messages.foundStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.foundStickerSets

+ +

Found stickersets

+

+ +
+
messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
setsVector<StickerSetCovered>Found stickersets
+

Type

+

messages.FoundStickerSets

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.foundStickerSetsNotModified b/data/corefork.telegram.org/constructor/messages.foundStickerSetsNotModified new file mode 100644 index 0000000000..b08316021c --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.foundStickerSetsNotModified @@ -0,0 +1,132 @@ + + + + + messages.foundStickerSetsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.foundStickerSetsNotModified

+ +

No further results were found

+

+ +
+
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.FoundStickerSets

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.highScores b/data/corefork.telegram.org/constructor/messages.highScores new file mode 100644 index 0000000000..5d1ff2936a --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.highScores @@ -0,0 +1,152 @@ + + + + + messages.highScores + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.highScores

+ +

Highscores in a game

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scoresVector<HighScore>Highscores
usersVector<User>Users, associated to the highscores
+

Type

+

messages.HighScores

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.historyImport b/data/corefork.telegram.org/constructor/messages.historyImport new file mode 100644 index 0000000000..ed9d38806f --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.historyImport @@ -0,0 +1,150 @@ + + + + + messages.historyImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.historyImport

+ +

ID of a specific chat import session, click here for more info ».

+

+ +
+
messages.historyImport#1662af0b id:long = messages.HistoryImport;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongHistory import ID
+

Type

+

messages.HistoryImport

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.historyImportParsed b/data/corefork.telegram.org/constructor/messages.historyImportParsed new file mode 100644 index 0000000000..1bd284dd2a --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.historyImportParsed @@ -0,0 +1,166 @@ + + + + + messages.historyImportParsed + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.historyImportParsed

+ +

Contains information about a chat export file generated by a foreign chat app, click here for more info.
+If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

+

+ +
+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pmflags.0?trueThe chat export file was generated from a private chat.
groupflags.1?trueThe chat export file was generated from a group chat.
titleflags.2?stringTitle of the chat.
+

Type

+

messages.HistoryImportParsed

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.inactiveChats b/data/corefork.telegram.org/constructor/messages.inactiveChats new file mode 100644 index 0000000000..d2884cd8e3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.inactiveChats @@ -0,0 +1,157 @@ + + + + + messages.inactiveChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.inactiveChats

+ +

Inactive chat list

+

+ +
+
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
datesVector<int>When was the chat last active
chatsVector<Chat>Chat list
usersVector<User>Users mentioned in the chat list
+

Type

+

messages.InactiveChats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.messageEditData b/data/corefork.telegram.org/constructor/messages.messageEditData new file mode 100644 index 0000000000..b39741ea27 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.messageEditData @@ -0,0 +1,152 @@ + + + + + messages.messageEditData + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messageEditData

+ +

Message edit data for media

+

+ +
+
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
captionflags.0?trueMedia caption, if the specified media's caption can be edited
+

Type

+

messages.MessageEditData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.messageReactionsList b/data/corefork.telegram.org/constructor/messages.messageReactionsList new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.messageReactionsList @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.messageViews b/data/corefork.telegram.org/constructor/messages.messageViews new file mode 100644 index 0000000000..d6c8d9f112 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.messageViews @@ -0,0 +1,157 @@ + + + + + messages.messageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messageViews

+ +

View, forward counter + info about replies

+

+ +
+
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
viewsVector<MessageViews>View, forward counter + info about replies
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
+

Type

+

messages.MessageViews

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.messages b/data/corefork.telegram.org/constructor/messages.messages new file mode 100644 index 0000000000..03b55922b8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.messages @@ -0,0 +1,157 @@ + + + + + messages.messages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messages

+ +

Full list of messages with auxilary data.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
+

Type

+

messages.Messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.messagesNotModified b/data/corefork.telegram.org/constructor/messages.messagesNotModified new file mode 100644 index 0000000000..8e6be39422 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.messagesNotModified @@ -0,0 +1,147 @@ + + + + + messages.messagesNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messagesNotModified

+ +

No new messages matching the query were found

+

+ +
+
messages.messagesNotModified#74535f21 count:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of results found server-side by the given query
+

Type

+

messages.Messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.messagesSlice b/data/corefork.telegram.org/constructor/messages.messagesSlice new file mode 100644 index 0000000000..5d939264e0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.messagesSlice @@ -0,0 +1,185 @@ + + + + + messages.messagesSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messagesSlice

+ +

Incomplete list of messages and auxiliary data.

+

+ +
+
messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, indicates that the results may be inexact
countintTotal number of messages in the list
next_rateflags.0?intRate to use in the offset_rate parameter in the next call to messages.searchGlobal
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in messages
usersVector<User>List of users mentioned in messages and chats
+

Type

+

messages.Messages

+

Related pages

+

messages.searchGlobal

+

Search for messages and peers globally

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.peerDialogs b/data/corefork.telegram.org/constructor/messages.peerDialogs new file mode 100644 index 0000000000..2d65c4e598 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.peerDialogs @@ -0,0 +1,170 @@ + + + + + messages.peerDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.peerDialogs

+ +

Dialog info of multiple peers

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dialogsVector<Dialog>Dialog info
messagesVector<Message>Messages mentioned in dialog info
chatsVector<Chat>Chats
usersVector<User>Users
stateupdates.StateCurrent update state of dialog
+

Type

+

messages.PeerDialogs

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.peerSettings b/data/corefork.telegram.org/constructor/messages.peerSettings new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.peerSettings @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.recentStickers b/data/corefork.telegram.org/constructor/messages.recentStickers new file mode 100644 index 0000000000..b28196b7db --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.recentStickers @@ -0,0 +1,165 @@ + + + + + messages.recentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.recentStickers

+ +

Recently used stickers

+

+ +
+
messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Recent stickers
datesVector<int>When was each sticker last used
+

Type

+

messages.RecentStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.recentStickersNotModified b/data/corefork.telegram.org/constructor/messages.recentStickersNotModified new file mode 100644 index 0000000000..df85426643 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.recentStickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.recentStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.recentStickersNotModified

+ +

No new recent sticker was found

+

+ +
+
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.RecentStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.savedGifs b/data/corefork.telegram.org/constructor/messages.savedGifs new file mode 100644 index 0000000000..59149952ec --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.savedGifs @@ -0,0 +1,155 @@ + + + + + messages.savedGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.savedGifs

+ +

Saved gifs

+

+ +
+
messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
gifsVector<Document>List of saved gifs
+

Type

+

messages.SavedGifs

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.savedGifsNotModified b/data/corefork.telegram.org/constructor/messages.savedGifsNotModified new file mode 100644 index 0000000000..3117b94ad5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.savedGifsNotModified @@ -0,0 +1,132 @@ + + + + + messages.savedGifsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.savedGifsNotModified

+ +

No new saved gifs were found

+

+ +
+
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.SavedGifs

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.searchCounter b/data/corefork.telegram.org/constructor/messages.searchCounter new file mode 100644 index 0000000000..5b2149e8a6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.searchCounter @@ -0,0 +1,165 @@ + + + + + messages.searchCounter + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchCounter

+ +

Indicates how many results would be found by a messages.search call with the same parameters

+

+ +
+
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, the results may be inexact
filterMessagesFilterProvided message filter
countintNumber of results that were found server-side
+

Type

+

messages.SearchCounter

+

Related pages

+

messages.search

+

Gets back found messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.searchResultsCalendar b/data/corefork.telegram.org/constructor/messages.searchResultsCalendar new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.searchResultsCalendar @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.searchResultsPositions b/data/corefork.telegram.org/constructor/messages.searchResultsPositions new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.searchResultsPositions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.sentEncryptedFile b/data/corefork.telegram.org/constructor/messages.sentEncryptedFile new file mode 100644 index 0000000000..531610aeea --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.sentEncryptedFile @@ -0,0 +1,152 @@ + + + + + messages.sentEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sentEncryptedFile

+ +

Message with a file enclosure sent to a protected chat

+

+ +
+
messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dateintSending date
fileEncryptedFileAttached file
+

Type

+

messages.SentEncryptedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.sentEncryptedMessage b/data/corefork.telegram.org/constructor/messages.sentEncryptedMessage new file mode 100644 index 0000000000..983d20e21c --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.sentEncryptedMessage @@ -0,0 +1,147 @@ + + + + + messages.sentEncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sentEncryptedMessage

+ +

Message without file attachemts sent to an encrypted file.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dateintDate of sending
+

Type

+

messages.SentEncryptedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.sentMessageLink b/data/corefork.telegram.org/constructor/messages.sentMessageLink new file mode 100644 index 0000000000..ae7d656889 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.sentMessageLink @@ -0,0 +1,167 @@ + + + + + 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 new file mode 100644 index 0000000000..661ec152cc --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.sponsoredMessages @@ -0,0 +1,157 @@ + + + + + messages.sponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sponsoredMessages

+ +

A set of sponsored messages associated to a channel

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<SponsoredMessage>Sponsored messages
chatsVector<Chat>Chats mentioned in the sponsored messages
usersVector<User>Users mentioned in the sponsored messages
+

Type

+

messages.SponsoredMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.statedMessageLink b/data/corefork.telegram.org/constructor/messages.statedMessageLink new file mode 100644 index 0000000000..00855bf6e2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.statedMessageLink @@ -0,0 +1,172 @@ + + + + + messages.statedMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.statedMessageLink

+ +

Message with auxiliary data, state data and the list of changed links.

+

+ +
+
Constructor schema is available as of layer 24. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageMessage
chatsVector<Chat>List of chats mentioned in message
usersVector<User>List of users mentioned in message and chats
linksVector<contacts.Link>List of changed links
ptsintNumber of events occurred in text box
seqintNumber of sent updates
+

Type

+

messages.StatedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.statedMessagesLinks b/data/corefork.telegram.org/constructor/messages.statedMessagesLinks new file mode 100644 index 0000000000..fea9f00abc --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.statedMessagesLinks @@ -0,0 +1,172 @@ + + + + + messages.statedMessagesLinks + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.statedMessagesLinks

+ +

Message with auxiliary data, state data and the list of changed links.

+

+ +
+
Constructor schema is available as of layer 24. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of cats mentioned in messages
usersVector<User>List of users mentioned in messages and cahts
linksVector<contacts.Link>List of changed links
ptsintNumber of event occurred in a text box
seqintNumber of sent updates
+

Type

+

messages.StatedMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.stickerSet b/data/corefork.telegram.org/constructor/messages.stickerSet new file mode 100644 index 0000000000..7b9110d467 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.stickerSet @@ -0,0 +1,157 @@ + + + + + messages.stickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickerSet

+ +

Stickerset and stickers inside it

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
setStickerSetThe stickerset
packsVector<StickerPack>Emoji info for stickers
documentsVector<Document>Stickers in stickerset
+

Type

+

messages.StickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultArchive b/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultArchive new file mode 100644 index 0000000000..6ed6ffb007 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultArchive @@ -0,0 +1,147 @@ + + + + + messages.stickerSetInstallResultArchive + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickerSetInstallResultArchive

+ +

The stickerset was installed, but since there are too many stickersets some were archived

+

+ +
+
messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
setsVector<StickerSetCovered>Archived stickersets
+

Type

+

messages.StickerSetInstallResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultSuccess b/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultSuccess new file mode 100644 index 0000000000..0b6894d496 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultSuccess @@ -0,0 +1,132 @@ + + + + + messages.stickerSetInstallResultSuccess + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickerSetInstallResultSuccess

+ +

The stickerset was installed successfully

+

+ +
+
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.StickerSetInstallResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.stickers b/data/corefork.telegram.org/constructor/messages.stickers new file mode 100644 index 0000000000..27093eff96 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.stickers @@ -0,0 +1,155 @@ + + + + + messages.stickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickers

+ +

Found stickers

+

+ +
+
messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
stickersVector<Document>Stickers
+

Type

+

messages.Stickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.stickersNotModified b/data/corefork.telegram.org/constructor/messages.stickersNotModified new file mode 100644 index 0000000000..6465dee989 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.stickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.stickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickersNotModified

+ +

No new stickers were found for the given query

+

+ +
+
messages.stickersNotModified#f1749a22 = messages.Stickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.Stickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.translateNoResult b/data/corefork.telegram.org/constructor/messages.translateNoResult new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.translateNoResult @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.translateResultText b/data/corefork.telegram.org/constructor/messages.translateResultText new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.translateResultText @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.votesList b/data/corefork.telegram.org/constructor/messages.votesList new file mode 100644 index 0000000000..a5eaa4274e --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.votesList @@ -0,0 +1,170 @@ + + + + + messages.votesList + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.votesList

+ +

How users voted in a poll

+

+ +
+
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
countintTotal number of votes for all options (or only for the chosen option, if provided to messages.getPollVotes)
votesVector<MessageUserVote>Vote info for each user
usersVector<User>Info about users that voted in the poll
next_offsetflags.0?stringOffset to use with the next messages.getPollVotes request, empty string if no more results are available.
+

Type

+

messages.VotesList

+

Related pages

+

messages.getPollVotes

+

Get poll results for non-anonymous polls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/nearestDc.html b/data/corefork.telegram.org/constructor/nearestDc.html new file mode 100644 index 0000000000..bbf6052ad0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/nearestDc.html @@ -0,0 +1,157 @@ + + + + + nearestDc + + + + + + + + + + + + + +
+ +
+
+
+ +

nearestDc

+ +

Nearest data centre, according to geo-ip.

+

+ +
+
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countrystringCountry code determined by geo-ip
this_dcintNumber of current data centre
nearest_dcintNumber of nearest data centre
+

Type

+

NearestDc

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/notifyBroadcasts.html b/data/corefork.telegram.org/constructor/notifyBroadcasts.html new file mode 100644 index 0000000000..aae0391760 --- /dev/null +++ b/data/corefork.telegram.org/constructor/notifyBroadcasts.html @@ -0,0 +1,132 @@ + + + + + notifyBroadcasts + + + + + + + + + + + + + +
+ +
+
+
+ +

notifyBroadcasts

+ +

Channel notification settings

+

+ +
+
notifyBroadcasts#d612e8ef = NotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

NotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/notifyChats.html b/data/corefork.telegram.org/constructor/notifyChats.html new file mode 100644 index 0000000000..7e3e349c39 --- /dev/null +++ b/data/corefork.telegram.org/constructor/notifyChats.html @@ -0,0 +1,132 @@ + + + + + notifyChats + + + + + + + + + + + + + +
+ +
+
+
+ +

notifyChats

+ +

Notifications generated by all groups.

+

+ +
+
notifyChats#c007cec3 = NotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

NotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/notifyPeer.html b/data/corefork.telegram.org/constructor/notifyPeer.html new file mode 100644 index 0000000000..569fa22500 --- /dev/null +++ b/data/corefork.telegram.org/constructor/notifyPeer.html @@ -0,0 +1,147 @@ + + + + + notifyPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

notifyPeer

+ +

Notifications generated by a certain user or group.

+

+ +
+
notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerPeeruser or group
+

Type

+

NotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/notifyUsers.html b/data/corefork.telegram.org/constructor/notifyUsers.html new file mode 100644 index 0000000000..c24df0ea6e --- /dev/null +++ b/data/corefork.telegram.org/constructor/notifyUsers.html @@ -0,0 +1,132 @@ + + + + + notifyUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

notifyUsers

+ +

Notifications generated by all users.

+

+ +
+
notifyUsers#b4c83b4c = NotifyPeer;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

NotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/null.html b/data/corefork.telegram.org/constructor/null.html new file mode 100644 index 0000000000..f0fe4531bb --- /dev/null +++ b/data/corefork.telegram.org/constructor/null.html @@ -0,0 +1,132 @@ + + + + + null + + + + + + + + + + + + + +
+ +
+
+
+ +

null

+ +

Corresponds to an arbitrary empty object.

+

+ +
+
null#56730bcc = Null;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Null

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/page.html b/data/corefork.telegram.org/constructor/page.html new file mode 100644 index 0000000000..b07ea7a990 --- /dev/null +++ b/data/corefork.telegram.org/constructor/page.html @@ -0,0 +1,190 @@ + + + + + page + + + + + + + + + + + + + +
+ +
+
+
+ +

page

+ +

Instant view page

+

+ +
+
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
partflags.0?trueIndicates that not full page preview is available to the client and it will need to fetch full Instant View from the server using messages.getWebPagePreview.
rtlflags.1?trueWhether the page contains RTL text
v2flags.2?trueWhether this is an IV v2 page
urlstringOriginal page HTTP URL
blocksVector<PageBlock>Page elements (like with HTML elements, only as TL constructors)
photosVector<Photo>Photos in page
documentsVector<Document>Media in page
viewsflags.3?intViewcount
+

Type

+

Page

+

Related pages

+

messages.getWebPagePreview

+

Get preview of webpage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockAnchor.html b/data/corefork.telegram.org/constructor/pageBlockAnchor.html new file mode 100644 index 0000000000..e927a21f44 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockAnchor.html @@ -0,0 +1,147 @@ + + + + + pageBlockAnchor + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockAnchor

+ +

Link to section within the page itself (like <a href="#target">anchor</a>)

+

+ +
+
pageBlockAnchor#ce0d37b0 name:string = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
namestringName of target section
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockAudio.html b/data/corefork.telegram.org/constructor/pageBlockAudio.html new file mode 100644 index 0000000000..957ff1528f --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockAudio.html @@ -0,0 +1,155 @@ + + + + + pageBlockAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockAudio

+ +

Audio

+

+ +
+
pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
audio_idlongAudio ID (to be fetched from the container page constructor
captionPageCaptionAudio caption
+

Type

+

PageBlock

+

Related pages

+

page

+

Instant view page

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html b/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html new file mode 100644 index 0000000000..3d5f3d08d1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html @@ -0,0 +1,152 @@ + + + + + pageBlockAuthorDate + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockAuthorDate

+ +

Author and date of creation of article

+

+ +
+
pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
authorRichTextAuthor name
published_dateintDate of pubblication
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockBlockquote.html b/data/corefork.telegram.org/constructor/pageBlockBlockquote.html new file mode 100644 index 0000000000..3d331cabb6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockBlockquote.html @@ -0,0 +1,152 @@ + + + + + pageBlockBlockquote + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockBlockquote

+ +

Quote (equivalent to the HTML <blockquote>)

+

+ +
+
pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextQuote contents
captionRichTextCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockChannel.html b/data/corefork.telegram.org/constructor/pageBlockChannel.html new file mode 100644 index 0000000000..471b353c65 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockChannel.html @@ -0,0 +1,147 @@ + + + + + pageBlockChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockChannel

+ +

Reference to a telegram channel

+

+ +
+
pageBlockChannel#ef1751b5 channel:Chat = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelChatThe channel/supergroup/chat
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockCollage.html b/data/corefork.telegram.org/constructor/pageBlockCollage.html new file mode 100644 index 0000000000..23b23caf19 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockCollage.html @@ -0,0 +1,152 @@ + + + + + pageBlockCollage + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockCollage

+ +

Collage of media

+

+ +
+
pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageBlock>Media elements
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockCover.html b/data/corefork.telegram.org/constructor/pageBlockCover.html new file mode 100644 index 0000000000..b440f32ba3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockCover.html @@ -0,0 +1,147 @@ + + + + + pageBlockCover + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockCover

+ +

A page cover

+

+ +
+
pageBlockCover#39f23300 cover:PageBlock = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
coverPageBlockCover
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockDetails.html b/data/corefork.telegram.org/constructor/pageBlockDetails.html new file mode 100644 index 0000000000..fa87e33532 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockDetails.html @@ -0,0 +1,162 @@ + + + + + pageBlockDetails + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockDetails

+ +

A collapsible details block

+

+ +
+
pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
openflags.0?trueWhether the block is open by default
blocksVector<PageBlock>Block contents
titleRichTextAlways visible heading for the block
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockDivider.html b/data/corefork.telegram.org/constructor/pageBlockDivider.html new file mode 100644 index 0000000000..b1c5bec0a8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockDivider.html @@ -0,0 +1,132 @@ + + + + + pageBlockDivider + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockDivider

+ +

An empty block separating a page

+

+ +
+
pageBlockDivider#db20b188 = PageBlock;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockEmbed.html b/data/corefork.telegram.org/constructor/pageBlockEmbed.html new file mode 100644 index 0000000000..e960ef87c3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockEmbed.html @@ -0,0 +1,187 @@ + + + + + pageBlockEmbed + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockEmbed

+ +

An embedded webpage

+

+ +
+
pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
full_widthflags.0?trueWhether the block should be full width
allow_scrollingflags.3?trueWhether scrolling should be allowed
urlflags.1?stringWeb page URL, if available
htmlflags.2?stringHTML-markup of the embedded page
poster_photo_idflags.4?longPoster photo, if available
wflags.5?intBlock width, if known
hflags.5?intBlock height, if known
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockEmbedPost.html b/data/corefork.telegram.org/constructor/pageBlockEmbedPost.html new file mode 100644 index 0000000000..e0867ac710 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockEmbedPost.html @@ -0,0 +1,177 @@ + + + + + pageBlockEmbedPost + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockEmbedPost

+ +

An embedded post

+

+ +
+
pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringWeb page URL
webpage_idlongID of generated webpage preview
author_photo_idlongID of the author's photo
authorstringAuthor name
dateintCreation date
blocksVector<PageBlock>Post contents
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockFooter.html b/data/corefork.telegram.org/constructor/pageBlockFooter.html new file mode 100644 index 0000000000..e2339e8162 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockFooter.html @@ -0,0 +1,147 @@ + + + + + pageBlockFooter + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockFooter

+ +

Page footer

+

+ +
+
pageBlockFooter#48870999 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextContents
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockHeader.html b/data/corefork.telegram.org/constructor/pageBlockHeader.html new file mode 100644 index 0000000000..08dc79f74e --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockHeader.html @@ -0,0 +1,147 @@ + + + + + pageBlockHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockHeader

+ +

Page header

+

+ +
+
pageBlockHeader#bfd064ec text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextContents
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockKicker.html b/data/corefork.telegram.org/constructor/pageBlockKicker.html new file mode 100644 index 0000000000..ad16ce6075 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockKicker.html @@ -0,0 +1,147 @@ + + + + + pageBlockKicker + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockKicker

+ +

Kicker

+

+ +
+
pageBlockKicker#1e148390 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextContents
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockList.html b/data/corefork.telegram.org/constructor/pageBlockList.html new file mode 100644 index 0000000000..33f89d9971 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockList.html @@ -0,0 +1,147 @@ + + + + + pageBlockList + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockList

+ +

Unordered list of IV blocks

+

+ +
+
pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageListItem>List of blocks in an IV page
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockMap.html b/data/corefork.telegram.org/constructor/pageBlockMap.html new file mode 100644 index 0000000000..df142bbf99 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockMap.html @@ -0,0 +1,167 @@ + + + + + pageBlockMap + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockMap

+ +

A map

+

+ +
+
pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geoGeoPointLocation of the map center
zoomintMap zoom level; 13-20
wintMap width in pixels before applying scale; 16-102
hintMap height in pixels before applying scale; 16-1024
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockOrderedList.html b/data/corefork.telegram.org/constructor/pageBlockOrderedList.html new file mode 100644 index 0000000000..7311933c3a --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockOrderedList.html @@ -0,0 +1,147 @@ + + + + + pageBlockOrderedList + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockOrderedList

+ +

Ordered list of IV blocks

+

+ +
+
pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageListOrderedItem>List items
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockParagraph.html b/data/corefork.telegram.org/constructor/pageBlockParagraph.html new file mode 100644 index 0000000000..da82f2961f --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockParagraph.html @@ -0,0 +1,147 @@ + + + + + pageBlockParagraph + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockParagraph

+ +

A paragraph

+

+ +
+
pageBlockParagraph#467a0766 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockPhoto.html b/data/corefork.telegram.org/constructor/pageBlockPhoto.html new file mode 100644 index 0000000000..2567e54896 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockPhoto.html @@ -0,0 +1,167 @@ + + + + + pageBlockPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockPhoto

+ +

A photo

+

+ +
+
pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
photo_idlongPhoto ID
captionPageCaptionCaption
urlflags.0?stringHTTP URL of page the photo leads to when clicked
webpage_idflags.0?longID of preview of the page the photo leads to when clicked
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockPreformatted.html b/data/corefork.telegram.org/constructor/pageBlockPreformatted.html new file mode 100644 index 0000000000..cb2d510cf2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockPreformatted.html @@ -0,0 +1,152 @@ + + + + + pageBlockPreformatted + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockPreformatted

+ +

Preformatted (<pre> text)

+

+ +
+
pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
languagestringProgramming language of preformatted text
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockPullquote.html b/data/corefork.telegram.org/constructor/pageBlockPullquote.html new file mode 100644 index 0000000000..d8e1cf0599 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockPullquote.html @@ -0,0 +1,152 @@ + + + + + pageBlockPullquote + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockPullquote

+ +

Pullquote

+

+ +
+
pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
captionRichTextCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockRelatedArticles.html b/data/corefork.telegram.org/constructor/pageBlockRelatedArticles.html new file mode 100644 index 0000000000..68f8d1cd54 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockRelatedArticles.html @@ -0,0 +1,152 @@ + + + + + pageBlockRelatedArticles + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockRelatedArticles

+ +

Related articles

+

+ +
+
pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
titleRichTextTitle
articlesVector<PageRelatedArticle>Related articles
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockSlideshow.html b/data/corefork.telegram.org/constructor/pageBlockSlideshow.html new file mode 100644 index 0000000000..9a0e8ebbf1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockSlideshow.html @@ -0,0 +1,152 @@ + + + + + pageBlockSlideshow + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockSlideshow

+ +

Slideshow

+

+ +
+
pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageBlock>Slideshow items
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockSubheader.html b/data/corefork.telegram.org/constructor/pageBlockSubheader.html new file mode 100644 index 0000000000..a6656187de --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockSubheader.html @@ -0,0 +1,147 @@ + + + + + pageBlockSubheader + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockSubheader

+ +

Subheader

+

+ +
+
pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextSubheader
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockSubtitle.html b/data/corefork.telegram.org/constructor/pageBlockSubtitle.html new file mode 100644 index 0000000000..2de5daffd4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockSubtitle.html @@ -0,0 +1,147 @@ + + + + + pageBlockSubtitle + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockSubtitle

+ +

Subtitle

+

+ +
+
pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockTable.html b/data/corefork.telegram.org/constructor/pageBlockTable.html new file mode 100644 index 0000000000..6d5c1aaf37 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockTable.html @@ -0,0 +1,167 @@ + + + + + pageBlockTable + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockTable

+ +

Table

+

+ +
+
pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
borderedflags.0?trueDoes the table have a visible border?
stripedflags.1?trueIs the table striped?
titleRichTextTitle
rowsVector<PageTableRow>Table rows
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockTitle.html b/data/corefork.telegram.org/constructor/pageBlockTitle.html new file mode 100644 index 0000000000..76e415d6d4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockTitle.html @@ -0,0 +1,147 @@ + + + + + pageBlockTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockTitle

+ +

Title

+

+ +
+
pageBlockTitle#70abc3fd text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextTitle
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockUnsupported.html b/data/corefork.telegram.org/constructor/pageBlockUnsupported.html new file mode 100644 index 0000000000..d5bd8ff5a5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockUnsupported.html @@ -0,0 +1,132 @@ + + + + + pageBlockUnsupported + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockUnsupported

+ +

Unsupported IV element

+

+ +
+
pageBlockUnsupported#13567e8a = PageBlock;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockVideo.html b/data/corefork.telegram.org/constructor/pageBlockVideo.html new file mode 100644 index 0000000000..62e96aa40c --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockVideo.html @@ -0,0 +1,167 @@ + + + + + pageBlockVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockVideo

+ +

Video

+

+ +
+
pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
autoplayflags.0?trueWhether the video is set to autoplay
loopflags.1?trueWhether the video is set to loop
video_idlongVideo ID
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageCaption.html b/data/corefork.telegram.org/constructor/pageCaption.html new file mode 100644 index 0000000000..8b2c3afdb6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageCaption.html @@ -0,0 +1,152 @@ + + + + + pageCaption + + + + + + + + + + + + + +
+ +
+
+
+ +

pageCaption

+ +

Page caption

+

+ +
+
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextCaption
creditRichTextCredits
+

Type

+

PageCaption

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageListItemBlocks.html b/data/corefork.telegram.org/constructor/pageListItemBlocks.html new file mode 100644 index 0000000000..fec7d62ec7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageListItemBlocks.html @@ -0,0 +1,147 @@ + + + + + pageListItemBlocks + + + + + + + + + + + + + +
+ +
+
+
+ +

pageListItemBlocks

+ +

List item

+

+ +
+
pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
blocksVector<PageBlock>Blocks
+

Type

+

PageListItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageListItemText.html b/data/corefork.telegram.org/constructor/pageListItemText.html new file mode 100644 index 0000000000..cf5af779f7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageListItemText.html @@ -0,0 +1,147 @@ + + + + + pageListItemText + + + + + + + + + + + + + +
+ +
+
+
+ +

pageListItemText

+ +

List item

+

+ +
+
pageListItemText#b92fb6cd text:RichText = PageListItem;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

PageListItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageListOrderedItemText.html b/data/corefork.telegram.org/constructor/pageListOrderedItemText.html new file mode 100644 index 0000000000..e3325ae968 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageListOrderedItemText.html @@ -0,0 +1,152 @@ + + + + + pageListOrderedItemText + + + + + + + + + + + + + +
+ +
+
+
+ +

pageListOrderedItemText

+ +

Ordered list of text items

+

+ +
+
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
numstringNumber of element within ordered list
textRichTextText
+

Type

+

PageListOrderedItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageRelatedArticle.html b/data/corefork.telegram.org/constructor/pageRelatedArticle.html new file mode 100644 index 0000000000..b3bb3c965c --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageRelatedArticle.html @@ -0,0 +1,182 @@ + + + + + pageRelatedArticle + + + + + + + + + + + + + +
+ +
+
+
+ +

pageRelatedArticle

+ +

Related article

+

+ +
+
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of article
webpage_idlongWebpage ID of generated IV preview
titleflags.0?stringTitle
descriptionflags.1?stringDescription
photo_idflags.2?longID of preview photo
authorflags.3?stringAuthor name
published_dateflags.4?intDate of pubblication
+

Type

+

PageRelatedArticle

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageTableCell.html b/data/corefork.telegram.org/constructor/pageTableCell.html new file mode 100644 index 0000000000..a2bf2199c1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageTableCell.html @@ -0,0 +1,187 @@ + + + + + pageTableCell + + + + + + + + + + + + + +
+ +
+
+
+ +

pageTableCell

+ +

Table cell

+

+ +
+
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
headerflags.0?trueIs this element part of the column header
align_centerflags.3?trueHorizontally centered block
align_rightflags.4?trueRight-aligned block
valign_middleflags.5?trueVertically centered block
valign_bottomflags.6?trueBlock vertically-alligned to the bottom
textflags.7?RichTextContent
colspanflags.1?intFor how many columns should this cell extend
rowspanflags.2?intFor how many rows should this cell extend
+

Type

+

PageTableCell

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageTableRow.html b/data/corefork.telegram.org/constructor/pageTableRow.html new file mode 100644 index 0000000000..be9bf37953 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageTableRow.html @@ -0,0 +1,147 @@ + + + + + pageTableRow + + + + + + + + + + + + + +
+ +
+
+
+ +

pageTableRow

+ +

Table row

+

+ +
+
pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
cellsVector<PageTableCell>Table cells
+

Type

+

PageTableRow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html b/data/corefork.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html new file mode 100644 index 0000000000..090553c700 --- /dev/null +++ b/data/corefork.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html @@ -0,0 +1,165 @@ + + + + + passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow + + + + + + + + + + + + + +
+ +
+
+
+ +

passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow

+ +

This key derivation algorithm defines that SRP 2FA login must be used

+

+ +
+
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
salt1bytesOne of two salts used by the derivation function (see SRP 2FA login)
salt2bytesOne of two salts used by the derivation function (see SRP 2FA login)
gintBase (see SRP 2FA login)
pbytes2048-bit modulus (see SRP 2FA login)
+

Type

+

PasswordKdfAlgo

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/passwordKdfAlgoUnknown.html b/data/corefork.telegram.org/constructor/passwordKdfAlgoUnknown.html new file mode 100644 index 0000000000..a768da0a5a --- /dev/null +++ b/data/corefork.telegram.org/constructor/passwordKdfAlgoUnknown.html @@ -0,0 +1,132 @@ + + + + + passwordKdfAlgoUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

passwordKdfAlgoUnknown

+ +

Unknown KDF (most likely, the client is outdated and does not support the specified KDF algorithm)

+

+ +
+
passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/paymentCharge.html b/data/corefork.telegram.org/constructor/paymentCharge.html new file mode 100644 index 0000000000..4363457435 --- /dev/null +++ b/data/corefork.telegram.org/constructor/paymentCharge.html @@ -0,0 +1,152 @@ + + + + + paymentCharge + + + + + + + + + + + + + +
+ +
+
+
+ +

paymentCharge

+ +

Payment identifier

+

+ +
+
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringTelegram payment identifier
provider_charge_idstringProvider payment identifier
+

Type

+

PaymentCharge

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/paymentRequestedInfo.html b/data/corefork.telegram.org/constructor/paymentRequestedInfo.html new file mode 100644 index 0000000000..d09f052e11 --- /dev/null +++ b/data/corefork.telegram.org/constructor/paymentRequestedInfo.html @@ -0,0 +1,167 @@ + + + + + paymentRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

paymentRequestedInfo

+ +

Order info provided by the user

+

+ +
+
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
nameflags.0?stringUser's full name
phoneflags.1?stringUser's phone number
emailflags.2?stringUser's email address
shipping_addressflags.3?PostAddressUser's shipping address
+

Type

+

PaymentRequestedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/paymentSavedCredentialsCard.html b/data/corefork.telegram.org/constructor/paymentSavedCredentialsCard.html new file mode 100644 index 0000000000..e79500a658 --- /dev/null +++ b/data/corefork.telegram.org/constructor/paymentSavedCredentialsCard.html @@ -0,0 +1,152 @@ + + + + + paymentSavedCredentialsCard + + + + + + + + + + + + + +
+ +
+
+
+ +

paymentSavedCredentialsCard

+ +

Saved credit card

+

+ +
+
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringCard ID
titlestringTitle
+

Type

+

PaymentSavedCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo b/data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo new file mode 100644 index 0000000000..336c06a7c2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo @@ -0,0 +1,145 @@ + + + + + payments.ValidatedRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.ValidatedRequestedInfo

+ +

Validated user-provided info

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idflags.0?stringID
shipping_optionsflags.1?Vector<ShippingOption>Shipping options
+

Type

+

payments.ValidatedRequestedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/payments.bankCardData b/data/corefork.telegram.org/constructor/payments.bankCardData new file mode 100644 index 0000000000..af556ff1cd --- /dev/null +++ b/data/corefork.telegram.org/constructor/payments.bankCardData @@ -0,0 +1,152 @@ + + + + + payments.bankCardData + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.bankCardData

+ +

Credit card info, provided by the card's bank(s)

+

+ +
+
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
titlestringCredit card title
open_urlsVector<BankCardOpenUrl>Info URL(s) provided by the card's bank(s)
+

Type

+

payments.BankCardData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/payments.paymentForm b/data/corefork.telegram.org/constructor/payments.paymentForm new file mode 100644 index 0000000000..cde3cc3ae8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/payments.paymentForm @@ -0,0 +1,210 @@ + + + + + payments.paymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentForm

+ +

Payment form

+

+ +
+
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_save_credentialsflags.2?trueWhether the user can choose to save credentials.
password_missingflags.3?trueIndicates that the user can save payment credentials, but only after setting up a 2FA password (currently the account doesn't have a 2FA password)
form_idlongForm ID
bot_idlongBot ID
invoiceInvoiceInvoice
provider_idlongPayment provider ID.
urlstringPayment form URL
native_providerflags.4?stringPayment provider name.
One of the following:
- stripe
native_paramsflags.4?DataJSONContains information about the payment provider, if available, to support it natively without the need for opening the URL.
A JSON object that can contain the following fields:

- apple_pay_merchant_id: Apple Pay merchant ID
- google_pay_public_key: Google Pay public key
- need_country: True, if the user country must be provided,
- need_zip: True, if the user ZIP/postal code must be provided,
- need_cardholder_name: True, if the cardholder name must be provided
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
saved_credentialsflags.1?PaymentSavedCredentialsContains information about saved card credentials
usersVector<User>Users
+

Type

+

payments.PaymentForm

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/payments.paymentReceipt b/data/corefork.telegram.org/constructor/payments.paymentReceipt new file mode 100644 index 0000000000..577f7f4de1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/payments.paymentReceipt @@ -0,0 +1,219 @@ + + + + + payments.paymentReceipt + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentReceipt

+ +

Receipt

+

+ +
+
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
dateintDate of generation
bot_idlongBot ID
provider_idlongProvider ID
titlestringTitle
descriptionstringDescription
photoflags.2?WebDocumentPhoto
invoiceInvoiceInvoice
infoflags.0?PaymentRequestedInfoInfo
shippingflags.1?ShippingOptionSelected shipping option
tip_amountflags.3?longTipped amount
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
credentials_titlestringPayment credential name
usersVector<User>Users
+

Type

+

payments.PaymentReceipt

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/payments.paymentResult b/data/corefork.telegram.org/constructor/payments.paymentResult new file mode 100644 index 0000000000..d12da834e5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/payments.paymentResult @@ -0,0 +1,147 @@ + + + + + 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 new file mode 100644 index 0000000000..d5b81908d6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded @@ -0,0 +1,147 @@ + + + + + payments.paymentVerificationNeeded + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentVerificationNeeded

+ +

Payment was not successful, additional verification is needed

+

+ +
+
payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL for additional payment credentials verification
+

Type

+

payments.PaymentResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/payments.savedInfo b/data/corefork.telegram.org/constructor/payments.savedInfo new file mode 100644 index 0000000000..332f0c79fb --- /dev/null +++ b/data/corefork.telegram.org/constructor/payments.savedInfo @@ -0,0 +1,157 @@ + + + + + payments.savedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.savedInfo

+ +

Saved server-side order information

+

+ +
+
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_saved_credentialsflags.1?trueWhether the user has some saved payment credentials
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
+

Type

+

payments.SavedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerBlocked.html b/data/corefork.telegram.org/constructor/peerBlocked.html new file mode 100644 index 0000000000..78bd9e0bc3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerBlocked.html @@ -0,0 +1,152 @@ + + + + + peerBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

peerBlocked

+ +

Information about a blocked peer

+

+ +
+
peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peer_idPeerPeer ID
dateintWhen was the peer blocked
+

Type

+

PeerBlocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerChannel.html b/data/corefork.telegram.org/constructor/peerChannel.html new file mode 100644 index 0000000000..593dca34fe --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerChannel.html @@ -0,0 +1,147 @@ + + + + + peerChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

peerChannel

+ +

Channel/supergroup

+

+ +
+
peerChannel#a2a5371e channel_id:long = Peer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
+

Type

+

Peer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerChat.html b/data/corefork.telegram.org/constructor/peerChat.html new file mode 100644 index 0000000000..489ec0a46d --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerChat.html @@ -0,0 +1,147 @@ + + + + + peerChat + + + + + + + + + + + + + +
+ +
+
+
+ +

peerChat

+ +

Group.

+

+ +
+
peerChat#36c6019a chat_id:long = Peer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup identifier
+

Type

+

Peer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerLocated.html b/data/corefork.telegram.org/constructor/peerLocated.html new file mode 100644 index 0000000000..222d080bbd --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerLocated.html @@ -0,0 +1,157 @@ + + + + + peerLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

peerLocated

+ +

Peer geolocated nearby

+

+ +
+
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
expiresintValidity period of current data
distanceintDistance from the peer in meters
+

Type

+

PeerLocated

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerNotifySettings.html b/data/corefork.telegram.org/constructor/peerNotifySettings.html new file mode 100644 index 0000000000..c202284e63 --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerNotifySettings.html @@ -0,0 +1,182 @@ + + + + + peerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

peerNotifySettings

+ +

Notification settings.

+

+ +
+
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolDisplay text in notifications
silentflags.1?BoolMute peer?
mute_untilflags.2?intMute all notifications until this date
soundflags.3?stringAudio file name for notifications
+

Type

+

PeerNotifySettings

+

Event flags (events_mask)

+ + + + + + + + + + + + + +
0x00000001Profile photo update notification
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerSelfLocated.html b/data/corefork.telegram.org/constructor/peerSelfLocated.html new file mode 100644 index 0000000000..e3994788f4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerSelfLocated.html @@ -0,0 +1,147 @@ + + + + + peerSelfLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

peerSelfLocated

+ +

Current peer

+

+ +
+
peerSelfLocated#f8ec284b expires:int = PeerLocated;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintExpiry of geolocation info for current peer
+

Type

+

PeerLocated

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerSettings.html b/data/corefork.telegram.org/constructor/peerSettings.html new file mode 100644 index 0000000000..f351b0babc --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerSettings.html @@ -0,0 +1,197 @@ + + + + + peerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

peerSettings

+ +

Peer settings

+

+ +
+
peerSettings#a518110d 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 request_chat_broadcast:flags.10?true geo_distance:flags.6?int request_chat_title:flags.9?string request_chat_date:flags.9?int = PeerSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
report_spamflags.0?trueWhether we can still report the user for spam
add_contactflags.1?trueWhether we can add the user as contact
block_contactflags.2?trueWhether we can block the user
share_contactflags.3?trueWhether we can share the user's contact
need_contacts_exceptionflags.4?trueWhether a special exception for contacts is needed
report_geoflags.5?trueWhether we can report a geogroup is irrelevant for this location
autoarchivedflags.7?trueWhether this peer was automatically archived according to privacy settings
invite_membersflags.8?trueWhether we can invite members to a group or channel
geo_distanceflags.6?intDistance in meters between us and this peer
+

Type

+

PeerSettings

+

Related pages

+

globalPrivacySettings

+

Global privacy settings

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerUser.html b/data/corefork.telegram.org/constructor/peerUser.html new file mode 100644 index 0000000000..cc576ecd2c --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerUser.html @@ -0,0 +1,147 @@ + + + + + peerUser + + + + + + + + + + + + + +
+ +
+
+
+ +

peerUser

+ +

Chat partner

+

+ +
+
peerUser#59511722 user_id:long = Peer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
+

Type

+

Peer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phone.exportedGroupCallInvite b/data/corefork.telegram.org/constructor/phone.exportedGroupCallInvite new file mode 100644 index 0000000000..3298899b76 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phone.exportedGroupCallInvite @@ -0,0 +1,147 @@ + + + + + phone.exportedGroupCallInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.exportedGroupCallInvite

+ +

An invite to a group call or livestream

+

+ +
+
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
linkstringInvite link
+

Type

+

phone.ExportedGroupCallInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phone.groupCall b/data/corefork.telegram.org/constructor/phone.groupCall new file mode 100644 index 0000000000..8b0fa8fbf4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phone.groupCall @@ -0,0 +1,170 @@ + + + + + phone.groupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.groupCall

+ +

Contains info about a group call, and partial info about its participants.

+

+ +
+
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callGroupCallInfo about the group call
participantsVector<GroupCallParticipant>A partial list of participants.
participants_next_offsetstringNext offset to use when fetching the remaining participants using phone.getGroupParticipants
chatsVector<Chat>Chats mentioned in the participants vector
usersVector<User>Users mentioned in the participants vector
+

Type

+

phone.GroupCall

+

Related pages

+

phone.getGroupParticipants

+

Get group call participants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phone.groupParticipants b/data/corefork.telegram.org/constructor/phone.groupParticipants new file mode 100644 index 0000000000..6a49df9fc9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phone.groupParticipants @@ -0,0 +1,175 @@ + + + + + phone.groupParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.groupParticipants

+ +

Info about the participants of a group call or livestream

+

+ +
+
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of participants
participantsVector<GroupCallParticipant>List of participants
next_offsetstringIf not empty, the specified list of participants is partial, and more participants can be fetched specifying this parameter as offset in phone.getGroupParticipants.
chatsVector<Chat>Mentioned chats
usersVector<User>Mentioned users
versionintVersion info
+

Type

+

phone.GroupParticipants

+

Related pages

+

phone.getGroupParticipants

+

Get group call participants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phone.joinAsPeers b/data/corefork.telegram.org/constructor/phone.joinAsPeers new file mode 100644 index 0000000000..d6e0eb7151 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phone.joinAsPeers @@ -0,0 +1,157 @@ + + + + + phone.joinAsPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.joinAsPeers

+ +

A list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+

+ +
+
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peersVector<Peer>Peers
chatsVector<Chat>Chats mentioned in the peers vector
usersVector<User>Users mentioned in the peers vector
+

Type

+

phone.JoinAsPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phone.phoneCall b/data/corefork.telegram.org/constructor/phone.phoneCall new file mode 100644 index 0000000000..d45b9a382c --- /dev/null +++ b/data/corefork.telegram.org/constructor/phone.phoneCall @@ -0,0 +1,152 @@ + + + + + phone.phoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.phoneCall

+ +

A VoIP phone call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_callPhoneCallThe VoIP phone call
usersVector<User>VoIP phone call participants
+

Type

+

phone.PhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCall.html b/data/corefork.telegram.org/constructor/phoneCall.html new file mode 100644 index 0000000000..0700ad7a4a --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCall.html @@ -0,0 +1,209 @@ + + + + + phoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCall

+ +

Phone call

+

+ +
+
phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
p2p_allowedflags.5?trueWhether P2P connection to the other peer is allowed
videoflags.6?trueWhether this is a video call
idlongCall ID
access_hashlongAccess hash
dateintDate of creation of the call
admin_idlongUser ID of the creator of the call
participant_idlongUser ID of the other participant in the call
g_a_or_bbytesParameter for key exchange
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
connectionsVector<PhoneConnection>List of endpoints the user can connect to to exchange call data
start_dateintWhen was the call actually started
+

Type

+

PhoneCall

+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallAccepted.html b/data/corefork.telegram.org/constructor/phoneCallAccepted.html new file mode 100644 index 0000000000..145011ec98 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallAccepted.html @@ -0,0 +1,189 @@ + + + + + phoneCallAccepted + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallAccepted

+ +

An accepted phone call

+

+ +
+
phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueWhether this is a video call
idlongID of accepted phone call
access_hashlongAccess hash of phone call
dateintWhen was the call accepted
admin_idlongID of the call creator
participant_idlongID of the other user in the call
g_bbytesB parameter for secure E2E phone call key exchange
protocolPhoneCallProtocolProtocol to use for phone call
+

Type

+

PhoneCall

+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonBusy.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonBusy.html new file mode 100644 index 0000000000..bd04eb65ef --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonBusy.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonBusy + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonBusy

+ +

The phone call was discared because the user is busy in another call

+

+ +
+
phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html new file mode 100644 index 0000000000..f9dbfc16b0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonDisconnect + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonDisconnect

+ +

The phone call was disconnected

+

+ +
+
phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html new file mode 100644 index 0000000000..8c84251a66 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonHangup + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonHangup

+ +

The phone call was ended normally

+

+ +
+
phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonMissed.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonMissed.html new file mode 100644 index 0000000000..f555f44b6d --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonMissed.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonMissed + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonMissed

+ +

The phone call was missed

+

+ +
+
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscarded.html b/data/corefork.telegram.org/constructor/phoneCallDiscarded.html new file mode 100644 index 0000000000..63c442be65 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallDiscarded.html @@ -0,0 +1,182 @@ + + + + + phoneCallDiscarded + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscarded

+ +

Indicates a discarded phone call

+

+ +
+
phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
need_ratingflags.2?trueWhether the server required the user to rate the call
need_debugflags.3?trueWhether the server required the client to send the libtgvoip call debug data
videoflags.6?trueWhether the call was a video call
idlongCall ID
reasonflags.0?PhoneCallDiscardReasonWhy was the phone call discarded
durationflags.1?intDuration of the phone call in seconds
+

Type

+

PhoneCall

+

Related pages

+

phone.setCallRating

+

Rate a call

+

phone.saveCallDebug

+

Send phone call debug data to server

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallEmpty.html b/data/corefork.telegram.org/constructor/phoneCallEmpty.html new file mode 100644 index 0000000000..7ab9928615 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallEmpty.html @@ -0,0 +1,147 @@ + + + + + phoneCallEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallEmpty

+ +

Empty constructor

+

+ +
+
phoneCallEmpty#5366c915 id:long = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongCall ID
+

Type

+

PhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallProtocol.html b/data/corefork.telegram.org/constructor/phoneCallProtocol.html new file mode 100644 index 0000000000..bac819bc89 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallProtocol.html @@ -0,0 +1,179 @@ + + + + + phoneCallProtocol + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallProtocol

+ +

Protocol info for libtgvoip

+

+ +
+
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
udp_p2pflags.0?trueWhether to allow P2P connection to the other participant
udp_reflectorflags.1?trueWhether to allow connection to the other participants through the reflector servers
min_layerintMinimum layer for remote libtgvoip
max_layerintMaximum layer for remote libtgvoip
library_versionsVector<string>When using phone.requestCall and phone.acceptCall, specify all library versions supported by the client.
The server will merge and choose the best library version supported by both peers, returning only the best value in the result of the callee's phone.acceptCall and in the phoneCallAccepted update received by the caller.
+

Type

+

PhoneCallProtocol

+

Related pages

+

phone.requestCall

+

Start a telegram phone call

+

phone.acceptCall

+

Accept incoming call

+

phoneCallAccepted

+

An accepted phone call

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallRequested.html b/data/corefork.telegram.org/constructor/phoneCallRequested.html new file mode 100644 index 0000000000..569ba06e69 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallRequested.html @@ -0,0 +1,189 @@ + + + + + phoneCallRequested + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallRequested

+ +

Requested phone call

+

+ +
+
phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueWhether this is a video call
idlongPhone call ID
access_hashlongAccess hash
dateintWhen was the phone call created
admin_idlongID of the creator of the phone call
participant_idlongID of the other participant of the phone call
g_a_hashbytesParameter for key exchange
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
+

Type

+

PhoneCall

+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallWaiting.html b/data/corefork.telegram.org/constructor/phoneCallWaiting.html new file mode 100644 index 0000000000..394e1cf386 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallWaiting.html @@ -0,0 +1,187 @@ + + + + + phoneCallWaiting + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallWaiting

+ +

Incoming phone call

+

+ +
+
phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueIs this a video call
idlongCall ID
access_hashlongAccess hash
dateintDate
admin_idlongAdmin ID
participant_idlongParticipant ID
protocolPhoneCallProtocolPhone call protocol info
receive_dateflags.0?intWhen was the phone call received
+

Type

+

PhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneConnection.html b/data/corefork.telegram.org/constructor/phoneConnection.html new file mode 100644 index 0000000000..8859bf51e1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneConnection.html @@ -0,0 +1,167 @@ + + + + + phoneConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneConnection

+ +

Identifies an endpoint that can be used to connect to the other user in a phone call

+

+ +
+
phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongEndpoint ID
ipstringIP address of endpoint
ipv6stringIPv6 address of endpoint
portintPort ID
peer_tagbytesOur peer tag
+

Type

+

PhoneConnection

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneConnectionWebrtc.html b/data/corefork.telegram.org/constructor/phoneConnectionWebrtc.html new file mode 100644 index 0000000000..97eb6e0978 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneConnectionWebrtc.html @@ -0,0 +1,187 @@ + + + + + phoneConnectionWebrtc + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneConnectionWebrtc

+ +

WebRTC connection parameters

+

+ +
+
phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
turnflags.0?trueWhether this is a TURN endpoint
stunflags.1?trueWhether this is a STUN endpoint
idlongEndpoint ID
ipstringIP address
ipv6stringIPv6 address
portintPort
usernamestringUsername
passwordstringPassword
+

Type

+

PhoneConnection

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photo.html b/data/corefork.telegram.org/constructor/photo.html new file mode 100644 index 0000000000..0e94ec2b99 --- /dev/null +++ b/data/corefork.telegram.org/constructor/photo.html @@ -0,0 +1,192 @@ + + + + + photo + + + + + + + + + + + + + +
+ +
+
+
+ +

photo

+ +

Photo

+

+ +
+
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_stickersflags.0?trueWhether the photo has mask stickers attached to it
idlongID
access_hashlongAccess hash
file_referencebytesfile reference
dateintDate of upload
sizesVector<PhotoSize>Available sizes for download
video_sizesflags.1?Vector<VideoSize>For animated profiles, the MPEG4 videos
dc_idintDC ID to use for download
+

Type

+

Photo

+

Related pages

+

File references

+

How to handle file references.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photoCachedSize.html b/data/corefork.telegram.org/constructor/photoCachedSize.html new file mode 100644 index 0000000000..4b64ee6e8d --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoCachedSize.html @@ -0,0 +1,167 @@ + + + + + photoCachedSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoCachedSize

+ +

Description of an image and its content.

+

+ +
+
photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
bytesbytesBinary data, file content
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See here.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photoEmpty.html b/data/corefork.telegram.org/constructor/photoEmpty.html new file mode 100644 index 0000000000..82076180d9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoEmpty.html @@ -0,0 +1,147 @@ + + + + + photoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

photoEmpty

+ +

Empty constructor, non-existent photo

+

+ +
+
photoEmpty#2331b22d id:long = Photo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongPhoto identifier
+

Type

+

Photo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photoPathSize.html b/data/corefork.telegram.org/constructor/photoPathSize.html new file mode 100644 index 0000000000..60d50fa7cc --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoPathSize.html @@ -0,0 +1,155 @@ + + + + + photoPathSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoPathSize

+ +

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.

+

+ +
+
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringAlways j
bytesbytesCompressed SVG path payload, see here for decompression instructions
+

Type

+

PhotoSize

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photoSize.html b/data/corefork.telegram.org/constructor/photoSize.html new file mode 100644 index 0000000000..244cf9fc40 --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoSize.html @@ -0,0 +1,167 @@ + + + + + photoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoSize

+ +

Image description.

+

+ +
+
photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
sizeintFile size
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See here.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photoSizeEmpty.html b/data/corefork.telegram.org/constructor/photoSizeEmpty.html new file mode 100644 index 0000000000..35abc8148f --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoSizeEmpty.html @@ -0,0 +1,150 @@ + + + + + photoSizeEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

photoSizeEmpty

+ +

Empty constructor. Image with this thumbnail is unavailable.

+

+ +
+
photoSizeEmpty#e17e23c type:string = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type (see. photoSize)
+

Type

+

PhotoSize

+

Related pages

+

photoSize

+

Image description.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photoSizeProgressive.html b/data/corefork.telegram.org/constructor/photoSizeProgressive.html new file mode 100644 index 0000000000..9f0192f7c1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoSizeProgressive.html @@ -0,0 +1,167 @@ + + + + + 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/corefork.telegram.org/constructor/photoStrippedSize.html b/data/corefork.telegram.org/constructor/photoStrippedSize.html new file mode 100644 index 0000000000..128e9a56cb --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoStrippedSize.html @@ -0,0 +1,159 @@ + + + + + photoStrippedSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoStrippedSize

+ +

A low-resolution compressed JPG payload

+

+ +
+
photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type
bytesbytesThumbnail data, see here for more info on decompression »
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See the photoSize constructor.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

photoSize

+

Image description.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photos.photo b/data/corefork.telegram.org/constructor/photos.photo new file mode 100644 index 0000000000..3ffd7586a6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/photos.photo @@ -0,0 +1,152 @@ + + + + + photos.photo + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.photo

+ +

Photo with auxiliary data.

+

+ +
+
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
photoPhotoPhoto
usersVector<User>Users
+

Type

+

photos.Photo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photos.photos b/data/corefork.telegram.org/constructor/photos.photos new file mode 100644 index 0000000000..ac5a0d4ffe --- /dev/null +++ b/data/corefork.telegram.org/constructor/photos.photos @@ -0,0 +1,152 @@ + + + + + photos.photos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.photos

+ +

Full list of photos with auxiliary data.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
+

Type

+

photos.Photos

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photos.photosSlice b/data/corefork.telegram.org/constructor/photos.photosSlice new file mode 100644 index 0000000000..480aae0183 --- /dev/null +++ b/data/corefork.telegram.org/constructor/photos.photosSlice @@ -0,0 +1,157 @@ + + + + + photos.photosSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.photosSlice

+ +

Incomplete list of photos with auxiliary data.

+

+ +
+
photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of photos
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
+

Type

+

photos.Photos

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/poll.html b/data/corefork.telegram.org/constructor/poll.html new file mode 100644 index 0000000000..2fd9ebdbc7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/poll.html @@ -0,0 +1,195 @@ + + + + + poll + + + + + + + + + + + + + +
+ +
+
+
+ +

poll

+ +

Poll

+

+ +
+
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID of the poll
flags#Flags, see TL conditional fields
closedflags.0?trueWhether the poll is closed and doesn't accept any more answers
public_votersflags.1?trueWhether cast votes are publicly visible to all users (non-anonymous poll)
multiple_choiceflags.2?trueWhether multiple options can be chosen as answer
quizflags.3?trueWhether this is a quiz (with wrong and correct answers, results shown in the return type)
questionstringThe question of the poll
answersVector<PollAnswer>The possible answers, vote using messages.sendVote.
close_periodflags.4?intAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateflags.5?intPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period.
+

Type

+

Poll

+

Related pages

+

messages.sendVote

+

Vote in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pollAnswer.html b/data/corefork.telegram.org/constructor/pollAnswer.html new file mode 100644 index 0000000000..63025921ce --- /dev/null +++ b/data/corefork.telegram.org/constructor/pollAnswer.html @@ -0,0 +1,155 @@ + + + + + pollAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

pollAnswer

+ +

A possible answer of a poll

+

+ +
+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstringTextual representation of the answer
optionbytesThe param that has to be passed to messages.sendVote.
+

Type

+

PollAnswer

+

Related pages

+

messages.sendVote

+

Vote in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pollAnswerVoters.html b/data/corefork.telegram.org/constructor/pollAnswerVoters.html new file mode 100644 index 0000000000..e4542c97ae --- /dev/null +++ b/data/corefork.telegram.org/constructor/pollAnswerVoters.html @@ -0,0 +1,170 @@ + + + + + pollAnswerVoters + + + + + + + + + + + + + +
+ +
+
+
+ +

pollAnswerVoters

+ +

A poll answer, and how users voted on it

+

+ +
+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
chosenflags.0?trueWhether we have chosen this answer
correctflags.1?trueFor quizes, whether the option we have chosen is correct
optionbytesThe param that has to be passed to messages.sendVote.
votersintHow many users voted for this option
+

Type

+

PollAnswerVoters

+

Related pages

+

messages.sendVote

+

Vote in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pollResults.html b/data/corefork.telegram.org/constructor/pollResults.html new file mode 100644 index 0000000000..ec72ed65da --- /dev/null +++ b/data/corefork.telegram.org/constructor/pollResults.html @@ -0,0 +1,184 @@ + + + + + pollResults + + + + + + + + + + + + + +
+ +
+
+
+ +

pollResults

+ +

Results of poll

+

+ +
+
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
minflags.0?trueSimilar to min objects, used for poll constructors that are the same for all users so they don't have option chosen by the current user (you can use messages.getPollResults to get the full poll results).
resultsflags.1?Vector<PollAnswerVoters>Poll results
total_votersflags.2?intTotal number of people that voted in the poll
recent_votersflags.3?Vector<long>IDs of the last users that recently voted in the poll
solutionflags.4?stringExplanation of quiz solution
solution_entitiesflags.4?Vector<MessageEntity>Message entities for styled text in quiz solution
+

Type

+

PollResults

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

messages.getPollResults

+

Get poll results

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/popularContact.html b/data/corefork.telegram.org/constructor/popularContact.html new file mode 100644 index 0000000000..2a4e559f10 --- /dev/null +++ b/data/corefork.telegram.org/constructor/popularContact.html @@ -0,0 +1,152 @@ + + + + + popularContact + + + + + + + + + + + + + +
+ +
+
+
+ +

popularContact

+ +

Popular contact

+

+ +
+
popularContact#5ce14175 client_id:long importers:int = PopularContact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
client_idlongContact identifier
importersintHow many people imported this contact
+

Type

+

PopularContact

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/postAddress.html b/data/corefork.telegram.org/constructor/postAddress.html new file mode 100644 index 0000000000..30f276c39d --- /dev/null +++ b/data/corefork.telegram.org/constructor/postAddress.html @@ -0,0 +1,172 @@ + + + + + postAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

postAddress

+ +

Shipping address

+

+ +
+
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
street_line1stringFirst line for the address
street_line2stringSecond line for the address
citystringCity
statestringState, if applicable (empty otherwise)
country_iso2stringISO 3166-1 alpha-2 country code
post_codestringAddress post code
+

Type

+

PostAddress

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyAddedByPhone.html b/data/corefork.telegram.org/constructor/privacyKeyAddedByPhone.html new file mode 100644 index 0000000000..f87d0f19be --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyAddedByPhone.html @@ -0,0 +1,132 @@ + + + + + privacyKeyAddedByPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyAddedByPhone

+ +

Whether people can add you to their contact list by your phone number

+

+ +
+
privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html b/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html new file mode 100644 index 0000000000..45c212d6f6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html @@ -0,0 +1,132 @@ + + + + + privacyKeyChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyChatInvite

+ +

Whether the user can be invited to chats

+

+ +
+
privacyKeyChatInvite#500e6dfa = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyForwards.html b/data/corefork.telegram.org/constructor/privacyKeyForwards.html new file mode 100644 index 0000000000..379d07f1d6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyForwards.html @@ -0,0 +1,132 @@ + + + + + privacyKeyForwards + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyForwards

+ +

Whether messages forwarded from the user will be anonymously forwarded

+

+ +
+
privacyKeyForwards#69ec56a3 = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyPhoneNumber.html b/data/corefork.telegram.org/constructor/privacyKeyPhoneNumber.html new file mode 100644 index 0000000000..a6661547ff --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyPhoneNumber.html @@ -0,0 +1,132 @@ + + + + + privacyKeyPhoneNumber + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyPhoneNumber

+ +

Whether the user allows us to see his phone number

+

+ +
+
privacyKeyPhoneNumber#d19ae46d = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html b/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html new file mode 100644 index 0000000000..fb45419330 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html @@ -0,0 +1,132 @@ + + + + + privacyKeyPhoneP2P + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyPhoneP2P

+ +

Whether P2P connections in phone calls are allowed

+

+ +
+
privacyKeyPhoneP2P#39491cc8 = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyProfilePhoto.html b/data/corefork.telegram.org/constructor/privacyKeyProfilePhoto.html new file mode 100644 index 0000000000..3a54a77cec --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyProfilePhoto.html @@ -0,0 +1,132 @@ + + + + + privacyKeyProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyProfilePhoto

+ +

Whether the profile picture of the user is visible

+

+ +
+
privacyKeyProfilePhoto#96151fed = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html b/data/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html new file mode 100644 index 0000000000..56172eaa3f --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html @@ -0,0 +1,132 @@ + + + + + privacyKeyStatusTimestamp + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyStatusTimestamp

+ +

Whether we can see the last online timestamp

+

+ +
+
privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueAllowAll.html b/data/corefork.telegram.org/constructor/privacyValueAllowAll.html new file mode 100644 index 0000000000..e82c9c7d32 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueAllowAll.html @@ -0,0 +1,132 @@ + + + + + privacyValueAllowAll + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueAllowAll

+ +

Allow all users

+

+ +
+
privacyValueAllowAll#65427b82 = PrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html b/data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html new file mode 100644 index 0000000000..2020672ec8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html @@ -0,0 +1,147 @@ + + + + + privacyValueAllowChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueAllowChatParticipants

+ +

Allow all participants of certain chats

+

+ +
+
privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<long>Allowed chats
+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueAllowContacts.html b/data/corefork.telegram.org/constructor/privacyValueAllowContacts.html new file mode 100644 index 0000000000..7e53e9a47a --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueAllowContacts.html @@ -0,0 +1,132 @@ + + + + + privacyValueAllowContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueAllowContacts

+ +

Allow all contacts

+

+ +
+
privacyValueAllowContacts#fffe1bac = PrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueAllowUsers.html b/data/corefork.telegram.org/constructor/privacyValueAllowUsers.html new file mode 100644 index 0000000000..5f4888f052 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueAllowUsers.html @@ -0,0 +1,147 @@ + + + + + privacyValueAllowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueAllowUsers

+ +

Allow only certain users

+

+ +
+
privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<long>Allowed users
+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowAll.html b/data/corefork.telegram.org/constructor/privacyValueDisallowAll.html new file mode 100644 index 0000000000..fbf7521de1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueDisallowAll.html @@ -0,0 +1,132 @@ + + + + + privacyValueDisallowAll + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueDisallowAll

+ +

Disallow all users

+

+ +
+
privacyValueDisallowAll#8b73e763 = PrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowChatParticipants.html b/data/corefork.telegram.org/constructor/privacyValueDisallowChatParticipants.html new file mode 100644 index 0000000000..51299c1063 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueDisallowChatParticipants.html @@ -0,0 +1,147 @@ + + + + + privacyValueDisallowChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueDisallowChatParticipants

+ +

Disallow only participants of certain chats

+

+ +
+
privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chatsVector<long>Disallowed chats
+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowContacts.html b/data/corefork.telegram.org/constructor/privacyValueDisallowContacts.html new file mode 100644 index 0000000000..3813e6aff3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueDisallowContacts.html @@ -0,0 +1,132 @@ + + + + + privacyValueDisallowContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueDisallowContacts

+ +

Disallow only contacts

+

+ +
+
privacyValueDisallowContacts#f888fa1a = PrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html b/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html new file mode 100644 index 0000000000..d67e987d70 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html @@ -0,0 +1,147 @@ + + + + + privacyValueDisallowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueDisallowUsers

+ +

Disallow only certain users

+

+ +
+
privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<long>Disallowed users
+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/reactionCount.html b/data/corefork.telegram.org/constructor/reactionCount.html new file mode 100644 index 0000000000..343374a787 --- /dev/null +++ b/data/corefork.telegram.org/constructor/reactionCount.html @@ -0,0 +1,162 @@ + + + + + reactionCount + + + + + + + + + + + + + +
+ +
+
+
+ +

reactionCount

+ +

Reactions

+

+ +
+
reactionCount#6fb250d1 flags:# chosen:flags.0?true reaction:string count:int = ReactionCount;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
chosenflags.0?trueWhether the current user sent this reaction
reactionstringReaction (a UTF8 emoji)
countintNUmber of users that reacted with this emoji
+

Type

+

ReactionCount

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/receivedNotifyMessage.html b/data/corefork.telegram.org/constructor/receivedNotifyMessage.html new file mode 100644 index 0000000000..79c1baafa0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/receivedNotifyMessage.html @@ -0,0 +1,152 @@ + + + + + receivedNotifyMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

receivedNotifyMessage

+ +

Message ID, for which PUSH-notifications were cancelled.

+

+ +
+
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintMessage ID, for which PUSH-notifications were canceled
flagsintReserved for future use
+

Type

+

ReceivedNotifyMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlChat.html b/data/corefork.telegram.org/constructor/recentMeUrlChat.html new file mode 100644 index 0000000000..d2ede0ba5f --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlChat.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlChat + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlChat

+ +

Recent t.me link to a chat

+

+ +
+
recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringt.me URL
chat_idlongChat ID
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html b/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html new file mode 100644 index 0000000000..1d078b50bf --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlChatInvite

+ +

Recent t.me invite link to a chat

+

+ +
+
recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringt.me URL
chat_inviteChatInviteChat invitation
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html b/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html new file mode 100644 index 0000000000..15075a6940 --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlStickerSet

+ +

Recent t.me stickerset installation URL

+

+ +
+
recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringt.me URL
setStickerSetCoveredStickerset
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html b/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html new file mode 100644 index 0000000000..1b6f4ce231 --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html @@ -0,0 +1,147 @@ + + + + + recentMeUrlUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlUnknown

+ +

Unknown t.me url

+

+ +
+
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlUser.html b/data/corefork.telegram.org/constructor/recentMeUrlUser.html new file mode 100644 index 0000000000..604cfca243 --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlUser.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlUser + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlUser

+ +

Recent t.me link to a user

+

+ +
+
recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL
user_idlongUser ID
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/replyInlineMarkup.html b/data/corefork.telegram.org/constructor/replyInlineMarkup.html new file mode 100644 index 0000000000..49cba92680 --- /dev/null +++ b/data/corefork.telegram.org/constructor/replyInlineMarkup.html @@ -0,0 +1,147 @@ + + + + + replyInlineMarkup + + + + + + + + + + + + + +
+ +
+
+
+ +

replyInlineMarkup

+ +

Bot or inline keyboard

+

+ +
+
replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
rowsVector<KeyboardButtonRow>Bot or inline keyboard rows
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html b/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html new file mode 100644 index 0000000000..3ea0291314 --- /dev/null +++ b/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html @@ -0,0 +1,162 @@ + + + + + replyKeyboardForceReply + + + + + + + + + + + + + +
+ +
+
+
+ +

replyKeyboardForceReply

+ +

Force the user to send a reply

+

+ +
+
replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
single_useflags.1?trueRequests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again.
selectiveflags.2?trueUse this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
Example: A user requests to change the bot‘s language, bot replies to the request with a keyboard to select the new language. Other users in the group don’t see the keyboard.
placeholderflags.3?stringThe placeholder to be shown in the input field when the keyboard is active; 1-64 characters.
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/replyKeyboardHide.html b/data/corefork.telegram.org/constructor/replyKeyboardHide.html new file mode 100644 index 0000000000..b912a5800c --- /dev/null +++ b/data/corefork.telegram.org/constructor/replyKeyboardHide.html @@ -0,0 +1,152 @@ + + + + + replyKeyboardHide + + + + + + + + + + + + + +
+ +
+
+
+ +

replyKeyboardHide

+ +

Hide sent bot keyboard

+

+ +
+
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
selectiveflags.2?trueUse this flag if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html b/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html new file mode 100644 index 0000000000..25c5c2a1b3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html @@ -0,0 +1,172 @@ + + + + + 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/corefork.telegram.org/constructor/restrictionReason.html b/data/corefork.telegram.org/constructor/restrictionReason.html new file mode 100644 index 0000000000..ddbc4d8cb7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/restrictionReason.html @@ -0,0 +1,158 @@ + + + + + restrictionReason + + + + + + + + + + + + + +
+ +
+
+
+ +

restrictionReason

+ +

Restriction reason.

+

Contains the reason why access to a certain object must be restricted. Clients are supposed to deny access to the channel if the platform field is equal to all or to the current platform (ios, android, wp, etc.). Platforms can be concatenated (ios-android, ios-wp), unknown platforms are to be ignored. The text is the error message that should be shown to the user.

+

+ +
+
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
platformstringPlatform identifier (ios, android, wp, all, etc.), can be concatenated with a dash as separator (android-ios, ios-wp, etc)
reasonstringRestriction reason (porno, terms, etc.)
textstringError message to be shown to the user
+

Type

+

RestrictionReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/savedPhoneContact.html b/data/corefork.telegram.org/constructor/savedPhoneContact.html new file mode 100644 index 0000000000..f2da2b3e19 --- /dev/null +++ b/data/corefork.telegram.org/constructor/savedPhoneContact.html @@ -0,0 +1,162 @@ + + + + + savedPhoneContact + + + + + + + + + + + + + +
+ +
+
+
+ +

savedPhoneContact

+ +

Saved contact

+

+ +
+
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phonestringPhone number
first_namestringFirst name
last_namestringLast name
dateintDate added
+

Type

+

SavedContact

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureCredentialsEncrypted.html b/data/corefork.telegram.org/constructor/secureCredentialsEncrypted.html new file mode 100644 index 0000000000..c9be8c6cda --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureCredentialsEncrypted.html @@ -0,0 +1,159 @@ + + + + + secureCredentialsEncrypted + + + + + + + + + + + + + +
+ +
+
+
+ +

secureCredentialsEncrypted

+ +

Encrypted credentials required to decrypt telegram passport data.

+

+ +
+
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
databytesEncrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication, as described in decrypting data »
hashbytesData hash for data authentication as described in decrypting data »
secretbytesSecret, encrypted with the bot's public RSA key, required for data decryption as described in decrypting data »
+

Type

+

SecureCredentialsEncrypted

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureData.html b/data/corefork.telegram.org/constructor/secureData.html new file mode 100644 index 0000000000..b3b875408b --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureData.html @@ -0,0 +1,160 @@ + + + + + secureData + + + + + + + + + + + + + +
+ +
+
+
+ +

secureData

+ +

Secure passport data, for more info see the passport docs »

+

+ +
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
databytesData
data_hashbytesData hash
secretbytesSecret
+

Type

+

SecureData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureFile.html b/data/corefork.telegram.org/constructor/secureFile.html new file mode 100644 index 0000000000..485291a8c8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureFile.html @@ -0,0 +1,180 @@ + + + + + secureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

secureFile

+ +

Secure passport file, for more info see the passport docs »

+

+ +
+
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
sizeintFile size
dc_idintDC ID
dateintDate of upload
file_hashbytesFile hash
secretbytesSecret
+

Type

+

SecureFile

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureFileEmpty.html b/data/corefork.telegram.org/constructor/secureFileEmpty.html new file mode 100644 index 0000000000..c0cfd18b5c --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureFileEmpty.html @@ -0,0 +1,132 @@ + + + + + secureFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

secureFileEmpty

+ +

Empty constructor

+

+ +
+
secureFileEmpty#64199744 = SecureFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html new file mode 100644 index 0000000000..ea41055ae4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html @@ -0,0 +1,147 @@ + + + + + securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoPBKDF2HMACSHA512iter100000

+ +

PBKDF2 with SHA512 and 100000 iterations KDF algo

+

+ +
+
securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
saltbytesSalt
+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoSHA512.html b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoSHA512.html new file mode 100644 index 0000000000..20b0b29de8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoSHA512.html @@ -0,0 +1,147 @@ + + + + + securePasswordKdfAlgoSHA512 + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoSHA512

+ +

SHA512 KDF algo

+

+ +
+
securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
saltbytesSalt
+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html new file mode 100644 index 0000000000..51e3bb8a17 --- /dev/null +++ b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html @@ -0,0 +1,132 @@ + + + + + securePasswordKdfAlgoUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoUnknown

+ +

Unknown KDF algo (most likely the client has to be updated)

+

+ +
+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/securePlainEmail.html b/data/corefork.telegram.org/constructor/securePlainEmail.html new file mode 100644 index 0000000000..f3965b612d --- /dev/null +++ b/data/corefork.telegram.org/constructor/securePlainEmail.html @@ -0,0 +1,150 @@ + + + + + securePlainEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

securePlainEmail

+ +

Email address to use in telegram passport: it must be verified, first ».

+

+ +
+
securePlainEmail#21ec5a5f email:string = SecurePlainData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emailstringEmail address
+

Type

+

SecurePlainData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/securePlainPhone.html b/data/corefork.telegram.org/constructor/securePlainPhone.html new file mode 100644 index 0000000000..cab5dd85eb --- /dev/null +++ b/data/corefork.telegram.org/constructor/securePlainPhone.html @@ -0,0 +1,150 @@ + + + + + securePlainPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

securePlainPhone

+ +

Phone number to use in telegram passport: it must be verified, first ».

+

+ +
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phonestringPhone number
+

Type

+

SecurePlainData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureRequiredType.html b/data/corefork.telegram.org/constructor/secureRequiredType.html new file mode 100644 index 0000000000..861f24fef5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureRequiredType.html @@ -0,0 +1,167 @@ + + + + + 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 new file mode 100644 index 0000000000..4c29ba89d5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html @@ -0,0 +1,147 @@ + + + + + secureRequiredTypeOneOf + + + + + + + + + + + + + +
+ +
+
+
+ +

secureRequiredTypeOneOf

+ +

One of

+

+ +
+
secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typesVector<SecureRequiredType>Secure required value types
+

Type

+

SecureRequiredType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureSecretSettings.html b/data/corefork.telegram.org/constructor/secureSecretSettings.html new file mode 100644 index 0000000000..b12bb2c292 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureSecretSettings.html @@ -0,0 +1,157 @@ + + + + + secureSecretSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

secureSecretSettings

+ +

Secure settings

+

+ +
+
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
secure_algoSecurePasswordKdfAlgoSecure KDF algo
secure_secretbytesSecure secret
secure_secret_idlongSecret ID
+

Type

+

SecureSecretSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValue.html b/data/corefork.telegram.org/constructor/secureValue.html new file mode 100644 index 0000000000..9572e81e9c --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValue.html @@ -0,0 +1,194 @@ + + + + + secureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValue

+ +

Secure value

+

+ +
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
+

Type

+

SecureValue

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueError.html b/data/corefork.telegram.org/constructor/secureValueError.html new file mode 100644 index 0000000000..0ebe66de59 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueError.html @@ -0,0 +1,157 @@ + + + + + secureValueError + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueError

+ +

Secure value error

+

+ +
+
secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeType of element which has the issue
hashbytesHash
textstringError message
+

Type

+

SecureValueError

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorData.html b/data/corefork.telegram.org/constructor/secureValueErrorData.html new file mode 100644 index 0000000000..e2a5478a1e --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorData.html @@ -0,0 +1,175 @@ + + + + + secureValueErrorData + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorData

+ +

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

+

+ +
+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeThe section of the user's Telegram Passport which has the error, one of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeAddress
data_hashbytesData hash
fieldstringName of the data field which has the error
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePersonalDetails

+

Personal details

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+

secureValueTypeAddress

+

Address

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorFile.html b/data/corefork.telegram.org/constructor/secureValueErrorFile.html new file mode 100644 index 0000000000..2616893abd --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorFile.html @@ -0,0 +1,168 @@ + + + + + secureValueErrorFile + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorFile

+ +

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

+

+ +
+
secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypeUtilityBill

+

Utility bill

+

secureValueTypeBankStatement

+

Bank statement

+

secureValueTypeRentalAgreement

+

Rental agreement

+

secureValueTypePassportRegistration

+

Internal registration passport

+

secureValueTypeTemporaryRegistration

+

Temporary registration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorFiles.html b/data/corefork.telegram.org/constructor/secureValueErrorFiles.html new file mode 100644 index 0000000000..6caf089d75 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorFiles.html @@ -0,0 +1,168 @@ + + + + + secureValueErrorFiles + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorFiles

+ +

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

+

+ +
+
secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>File hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypeUtilityBill

+

Utility bill

+

secureValueTypeBankStatement

+

Bank statement

+

secureValueTypeRentalAgreement

+

Rental agreement

+

secureValueTypePassportRegistration

+

Internal registration passport

+

secureValueTypeTemporaryRegistration

+

Temporary registration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html b/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html new file mode 100644 index 0000000000..888550f63a --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html @@ -0,0 +1,166 @@ + + + + + secureValueErrorFrontSide + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorFrontSide

+ +

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

+

+ +
+
secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorSelfie.html b/data/corefork.telegram.org/constructor/secureValueErrorSelfie.html new file mode 100644 index 0000000000..5f946374f2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorSelfie.html @@ -0,0 +1,166 @@ + + + + + secureValueErrorSelfie + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorSelfie

+ +

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

+

+ +
+
secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorTranslationFile.html b/data/corefork.telegram.org/constructor/secureValueErrorTranslationFile.html new file mode 100644 index 0000000000..af67cacf0c --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorTranslationFile.html @@ -0,0 +1,178 @@ + + + + + secureValueErrorTranslationFile + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorTranslationFile

+ +

Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

+

+ +
+
secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePersonalDetails

+

Personal details

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+

secureValueTypeUtilityBill

+

Utility bill

+

secureValueTypeBankStatement

+

Bank statement

+

secureValueTypeRentalAgreement

+

Rental agreement

+

secureValueTypePassportRegistration

+

Internal registration passport

+

secureValueTypeTemporaryRegistration

+

Temporary registration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorTranslationFiles.html b/data/corefork.telegram.org/constructor/secureValueErrorTranslationFiles.html new file mode 100644 index 0000000000..273306be6a --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorTranslationFiles.html @@ -0,0 +1,178 @@ + + + + + secureValueErrorTranslationFiles + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorTranslationFiles

+ +

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation changes.

+

+ +
+
secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>Hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePersonalDetails

+

Personal details

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+

secureValueTypeUtilityBill

+

Utility bill

+

secureValueTypeBankStatement

+

Bank statement

+

secureValueTypeRentalAgreement

+

Rental agreement

+

secureValueTypePassportRegistration

+

Internal registration passport

+

secureValueTypeTemporaryRegistration

+

Temporary registration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueHash.html b/data/corefork.telegram.org/constructor/secureValueHash.html new file mode 100644 index 0000000000..15fdd42e1d --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueHash.html @@ -0,0 +1,152 @@ + + + + + secureValueHash + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueHash

+ +

Secure value hash

+

+ +
+
secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeSecure value type
hashbytesHash
+

Type

+

SecureValueHash

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeAddress.html b/data/corefork.telegram.org/constructor/secureValueTypeAddress.html new file mode 100644 index 0000000000..477046c37b --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeAddress.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeAddress

+ +

Address

+

+ +
+
secureValueTypeAddress#cbe31e26 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html b/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html new file mode 100644 index 0000000000..0d88f6837a --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeBankStatement + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeBankStatement

+ +

Bank statement

+

+ +
+
secureValueTypeBankStatement#89137c0d = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeDriverLicense.html b/data/corefork.telegram.org/constructor/secureValueTypeDriverLicense.html new file mode 100644 index 0000000000..8ed5b1d565 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeDriverLicense.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeDriverLicense + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeDriverLicense

+ +

Driver's license

+

+ +
+
secureValueTypeDriverLicense#6e425c4 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeEmail.html b/data/corefork.telegram.org/constructor/secureValueTypeEmail.html new file mode 100644 index 0000000000..7f5a2d8850 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeEmail.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeEmail

+ +

Email

+

+ +
+
secureValueTypeEmail#8e3ca7ee = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeIdentityCard.html b/data/corefork.telegram.org/constructor/secureValueTypeIdentityCard.html new file mode 100644 index 0000000000..d4fe47345d --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeIdentityCard.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeIdentityCard + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeIdentityCard

+ +

Identity card

+

+ +
+
secureValueTypeIdentityCard#a0d0744b = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeInternalPassport.html b/data/corefork.telegram.org/constructor/secureValueTypeInternalPassport.html new file mode 100644 index 0000000000..ddd4241976 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeInternalPassport.html @@ -0,0 +1,134 @@ + + + + + secureValueTypeInternalPassport + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeInternalPassport

+ +

Internal passport

+

+ +
+
secureValueTypeInternalPassport#99a48f23 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypePassport.html b/data/corefork.telegram.org/constructor/secureValueTypePassport.html new file mode 100644 index 0000000000..70d84c9182 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypePassport.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePassport + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePassport

+ +

Passport

+

+ +
+
secureValueTypePassport#3dac6a00 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypePassportRegistration.html b/data/corefork.telegram.org/constructor/secureValueTypePassportRegistration.html new file mode 100644 index 0000000000..91bc086f25 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypePassportRegistration.html @@ -0,0 +1,134 @@ + + + + + secureValueTypePassportRegistration + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePassportRegistration

+ +

Internal registration passport

+

+ +
+
secureValueTypePassportRegistration#99e3806a = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html b/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html new file mode 100644 index 0000000000..98305b3095 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePersonalDetails + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePersonalDetails

+ +

Personal details

+

+ +
+
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypePhone.html b/data/corefork.telegram.org/constructor/secureValueTypePhone.html new file mode 100644 index 0000000000..f7786c5bed --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypePhone.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePhone + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePhone

+ +

Phone

+

+ +
+
secureValueTypePhone#b320aadb = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeRentalAgreement.html b/data/corefork.telegram.org/constructor/secureValueTypeRentalAgreement.html new file mode 100644 index 0000000000..6306688297 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeRentalAgreement.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeRentalAgreement + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeRentalAgreement

+ +

Rental agreement

+

+ +
+
secureValueTypeRentalAgreement#8b883488 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html b/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html new file mode 100644 index 0000000000..b5deaa7a0c --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeTemporaryRegistration + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeTemporaryRegistration

+ +

Temporary registration

+

+ +
+
secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeUtilityBill.html b/data/corefork.telegram.org/constructor/secureValueTypeUtilityBill.html new file mode 100644 index 0000000000..30eaf3086c --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeUtilityBill.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeUtilityBill + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeUtilityBill

+ +

Utility bill

+

+ +
+
secureValueTypeUtilityBill#fc36954e = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageCancelAction.html b/data/corefork.telegram.org/constructor/sendMessageCancelAction.html new file mode 100644 index 0000000000..85692566cd --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageCancelAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageCancelAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageCancelAction

+ +

Invalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.

+

+ +
+
sendMessageCancelAction#fd5ec8f5 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageChooseContactAction.html b/data/corefork.telegram.org/constructor/sendMessageChooseContactAction.html new file mode 100644 index 0000000000..fd34c25d61 --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageChooseContactAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageChooseContactAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageChooseContactAction

+ +

User is selecting a contact to share.

+

+ +
+
sendMessageChooseContactAction#628cbc6f = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageChooseStickerAction.html b/data/corefork.telegram.org/constructor/sendMessageChooseStickerAction.html new file mode 100644 index 0000000000..010b7a1e6b --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageChooseStickerAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageChooseStickerAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageChooseStickerAction

+ +

User is choosing a sticker

+

+ +
+
sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html b/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html new file mode 100644 index 0000000000..3abbef031f --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html @@ -0,0 +1,160 @@ + + + + + sendMessageEmojiInteraction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageEmojiInteraction

+ +

User has clicked on an animated emoji triggering a reaction, click here for more info ».

+

+ +
+
sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji
msg_idintMessage ID of the animated emoji that was clicked
interactionDataJSONA JSON object with interaction info, click here for more info »
+

Type

+

SendMessageAction

+

Related pages

+

Animated Emojis

+

Graphical telegram clients should transform emojis into their respective animated version.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html b/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html new file mode 100644 index 0000000000..b87b91942c --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html @@ -0,0 +1,150 @@ + + + + + sendMessageEmojiInteractionSeen + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageEmojiInteractionSeen

+ +

User is watching an animated emoji reaction triggered by another user, click here for more info ».

+

+ +
+
sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji
+

Type

+

SendMessageAction

+

Related pages

+

Animated Emojis

+

Graphical telegram clients should transform emojis into their respective animated version.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageGamePlayAction.html b/data/corefork.telegram.org/constructor/sendMessageGamePlayAction.html new file mode 100644 index 0000000000..0967c616a2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageGamePlayAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageGamePlayAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageGamePlayAction

+ +

User is playing a game

+

+ +
+
sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html b/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html new file mode 100644 index 0000000000..1cd23f46ba --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageGeoLocationAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageGeoLocationAction

+ +

User is selecting a location to share.

+

+ +
+
sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageHistoryImportAction.html b/data/corefork.telegram.org/constructor/sendMessageHistoryImportAction.html new file mode 100644 index 0000000000..4b360f2c64 --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageHistoryImportAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageHistoryImportAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageHistoryImportAction

+ +

Chat history is being imported

+

+ +
+
sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageRecordAudioAction.html b/data/corefork.telegram.org/constructor/sendMessageRecordAudioAction.html new file mode 100644 index 0000000000..0b1e0a7899 --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageRecordAudioAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageRecordAudioAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageRecordAudioAction

+ +

User is recording a voice message.

+

+ +
+
sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageRecordRoundAction.html b/data/corefork.telegram.org/constructor/sendMessageRecordRoundAction.html new file mode 100644 index 0000000000..adc85fa89b --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageRecordRoundAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageRecordRoundAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageRecordRoundAction

+ +

User is recording a round video to share

+

+ +
+
sendMessageRecordRoundAction#88f27fbc = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageRecordVideoAction.html b/data/corefork.telegram.org/constructor/sendMessageRecordVideoAction.html new file mode 100644 index 0000000000..a1dd634223 --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageRecordVideoAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageRecordVideoAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageRecordVideoAction

+ +

User is recording a video.

+

+ +
+
sendMessageRecordVideoAction#a187d66f = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageTypingAction.html b/data/corefork.telegram.org/constructor/sendMessageTypingAction.html new file mode 100644 index 0000000000..47e38445de --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageTypingAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageTypingAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageTypingAction

+ +

User is typing.

+

+ +
+
sendMessageTypingAction#16bf744e = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html new file mode 100644 index 0000000000..d8335d1fdb --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadAudioAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadAudioAction

+ +

User is uploading a voice message.

+

+ +
+
sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html new file mode 100644 index 0000000000..0729359f3e --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadDocumentAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadDocumentAction

+ +

User is uploading a file.

+

+ +
+
sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html new file mode 100644 index 0000000000..c9078dd390 --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadPhotoAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadPhotoAction

+ +

User is uploading a photo.

+

+ +
+
sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadRoundAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadRoundAction.html new file mode 100644 index 0000000000..ed63eadbde --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageUploadRoundAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadRoundAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadRoundAction

+ +

User is uploading a round video

+

+ +
+
sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadVideoAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadVideoAction.html new file mode 100644 index 0000000000..c4813ae8b6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageUploadVideoAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadVideoAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadVideoAction

+ +

User is uploading a video.

+

+ +
+
sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/shippingOption.html b/data/corefork.telegram.org/constructor/shippingOption.html new file mode 100644 index 0000000000..df02ce7f23 --- /dev/null +++ b/data/corefork.telegram.org/constructor/shippingOption.html @@ -0,0 +1,157 @@ + + + + + shippingOption + + + + + + + + + + + + + +
+ +
+
+
+ +

shippingOption

+ +

Shipping option

+

+ +
+
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringOption ID
titlestringTitle
pricesVector<LabeledPrice>List of price portions
+

Type

+

ShippingOption

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html b/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html new file mode 100644 index 0000000000..d98f7a1604 --- /dev/null +++ b/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html @@ -0,0 +1,132 @@ + + + + + speakingInGroupCallAction + + + + + + + + + + + + + +
+ +
+
+
+ +

speakingInGroupCallAction

+ +

User is currently speaking in the group call

+

+ +
+
speakingInGroupCallAction#d92c2285 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sponsoredMessage.html b/data/corefork.telegram.org/constructor/sponsoredMessage.html new file mode 100644 index 0000000000..e787c867a3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/sponsoredMessage.html @@ -0,0 +1,178 @@ + + + + + sponsoredMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

sponsoredMessage

+ +

A sponsored message.

+

+ +
+
sponsoredMessage#3a836df8 flags:# random_id:bytes from_id:flags.3?Peer chat_invite:flags.4?ChatInvite chat_invite_hash:flags.4?string channel_post:flags.2?int start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
random_idbytesMessage ID
from_idPeerID of the sender of the message
start_paramflags.0?stringParameter for the bot start message if the sponsored chat is a chat with a bot.
messagestringSponsored message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
+

Type

+

SponsoredMessage

+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+

Styled text with message entities

+

How to create styled text with message entities

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stats.broadcastStats b/data/corefork.telegram.org/constructor/stats.broadcastStats new file mode 100644 index 0000000000..0c4527026b --- /dev/null +++ b/data/corefork.telegram.org/constructor/stats.broadcastStats @@ -0,0 +1,220 @@ + + + + + stats.broadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.broadcastStats

+ +

Channel statistics.

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
followersStatsAbsValueAndPrevFollower count change for period in consideration
views_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
shares_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date)
enabled_notificationsStatsPercentValuePercentage of subscribers with enabled notifications
growth_graphStatsGraphChannel growth graph (absolute subscriber count)
followers_graphStatsGraphFollowers growth graph (relative subscriber count)
mute_graphStatsGraphMuted users graph (relative)
top_hours_graphStatsGraphViews per hour graph (absolute)
interactions_graphStatsGraphInteractions graph (absolute)
iv_interactions_graphStatsGraphIV interactions graph (absolute)
views_by_source_graphStatsGraphViews by source graph (absolute)
new_followers_by_source_graphStatsGraphNew followers by source graph (absolute)
languages_graphStatsGraphSubscriber language graph (piechart)
recent_message_interactionsVector<MessageInteractionCounters>Recent message interactions
+

Type

+

stats.BroadcastStats

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stats.megagroupStats b/data/corefork.telegram.org/constructor/stats.megagroupStats new file mode 100644 index 0000000000..4ab708bf40 --- /dev/null +++ b/data/corefork.telegram.org/constructor/stats.megagroupStats @@ -0,0 +1,230 @@ + + + + + stats.megagroupStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.megagroupStats

+ +

Supergroup statistics

+

+ +
+
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
membersStatsAbsValueAndPrevMember count change for period in consideration
messagesStatsAbsValueAndPrevMessage number change for period in consideration
viewersStatsAbsValueAndPrevNumber of users that viewed messages, for range in consideration
postersStatsAbsValueAndPrevNumber of users that posted messages, for range in consideration
growth_graphStatsGraphSupergroup growth graph (absolute subscriber count)
members_graphStatsGraphMembers growth (relative subscriber count)
new_members_by_source_graphStatsGraphNew members by source graph
languages_graphStatsGraphSubscriber language graph (piechart)
messages_graphStatsGraphMessage activity graph (stacked bar graph, message type)
actions_graphStatsGraphGroup activity graph (deleted, modified messages, blocked users)
top_hours_graphStatsGraphActivity per hour graph (absolute)
weekdays_graphStatsGraphActivity per day of week graph (absolute)
top_postersVector<StatsGroupTopPoster>Info about most active group members
top_adminsVector<StatsGroupTopAdmin>Info about most active group admins
top_invitersVector<StatsGroupTopInviter>Info about most active group inviters
usersVector<User>Info about users mentioned in statistics
+

Type

+

stats.MegagroupStats

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stats.messageStats b/data/corefork.telegram.org/constructor/stats.messageStats new file mode 100644 index 0000000000..bc069cd43b --- /dev/null +++ b/data/corefork.telegram.org/constructor/stats.messageStats @@ -0,0 +1,147 @@ + + + + + stats.messageStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.messageStats

+ +

Message statistics

+

+ +
+
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
views_graphStatsGraphMessage view graph
+

Type

+

stats.MessageStats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsAbsValueAndPrev.html b/data/corefork.telegram.org/constructor/statsAbsValueAndPrev.html new file mode 100644 index 0000000000..5a3783ca04 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsAbsValueAndPrev.html @@ -0,0 +1,152 @@ + + + + + statsAbsValueAndPrev + + + + + + + + + + + + + +
+ +
+
+
+ +

statsAbsValueAndPrev

+ +

Statistics value couple; initial and final value for period of time currently in consideration

+

+ +
+
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
currentdoubleCurrent value
previousdoublePrevious value
+

Type

+

StatsAbsValueAndPrev

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsDateRangeDays.html b/data/corefork.telegram.org/constructor/statsDateRangeDays.html new file mode 100644 index 0000000000..8b1a65d023 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsDateRangeDays.html @@ -0,0 +1,155 @@ + + + + + statsDateRangeDays + + + + + + + + + + + + + +
+ +
+
+
+ +

statsDateRangeDays

+ +

Channel statistics date range

+

+ +
+
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
min_dateintInitial date
max_dateintFinal date
+

Type

+

StatsDateRangeDays

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsGraph.html b/data/corefork.telegram.org/constructor/statsGraph.html new file mode 100644 index 0000000000..2e61751236 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsGraph.html @@ -0,0 +1,160 @@ + + + + + statsGraph + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGraph

+ +

Channel statistics graph

+

+ +
+
statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
jsonDataJSONStatistics data
zoom_tokenflags.0?stringZoom token
+

Type

+

StatsGraph

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsGraphAsync.html b/data/corefork.telegram.org/constructor/statsGraphAsync.html new file mode 100644 index 0000000000..c572f53904 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsGraphAsync.html @@ -0,0 +1,152 @@ + + + + + statsGraphAsync + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGraphAsync

+ +

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
tokenstringToken to use for fetching the async graph
+

Type

+

StatsGraph

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

stats.loadAsyncGraph

+

Load channel statistics graph asynchronously

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsGraphError.html b/data/corefork.telegram.org/constructor/statsGraphError.html new file mode 100644 index 0000000000..983a2fa70a --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsGraphError.html @@ -0,0 +1,150 @@ + + + + + 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/statsGroupTopAdmin.html b/data/corefork.telegram.org/constructor/statsGroupTopAdmin.html new file mode 100644 index 0000000000..ce048962f3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsGroupTopAdmin.html @@ -0,0 +1,165 @@ + + + + + statsGroupTopAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGroupTopAdmin

+ +

Information about an active admin in a supergroup

+

+ +
+
statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
deletedintNumber of deleted messages for statistics period in consideration
kickedintNumber of kicked users for statistics period in consideration
bannedintNumber of banned users for statistics period in consideration
+

Type

+

StatsGroupTopAdmin

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsGroupTopInviter.html b/data/corefork.telegram.org/constructor/statsGroupTopInviter.html new file mode 100644 index 0000000000..35f34338e1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsGroupTopInviter.html @@ -0,0 +1,155 @@ + + + + + statsGroupTopInviter + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGroupTopInviter

+ +

Information about an active supergroup inviter

+

+ +
+
statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
invitationsintNumber of invitations for statistics period in consideration
+

Type

+

StatsGroupTopInviter

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsGroupTopPoster.html b/data/corefork.telegram.org/constructor/statsGroupTopPoster.html new file mode 100644 index 0000000000..98eb90f30e --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsGroupTopPoster.html @@ -0,0 +1,160 @@ + + + + + statsGroupTopPoster + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGroupTopPoster

+ +

Information about an active user in a supergroup

+

+ +
+
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
messagesintNumber of messages for statistics period in consideration
avg_charsintAverage number of characters per message
+

Type

+

StatsGroupTopPoster

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsPercentValue.html b/data/corefork.telegram.org/constructor/statsPercentValue.html new file mode 100644 index 0000000000..a992f48d51 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsPercentValue.html @@ -0,0 +1,156 @@ + + + + + statsPercentValue + + + + + + + + + + + + + +
+ +
+
+
+ +

statsPercentValue

+ +

Channel statistics percentage.
+Compute the percentage simply by doing part * total / 100

+

+ +
+
statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
partdoublePartial value
totaldoubleTotal value
+

Type

+

StatsPercentValue

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsURL.html b/data/corefork.telegram.org/constructor/statsURL.html new file mode 100644 index 0000000000..625eb78842 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsURL.html @@ -0,0 +1,147 @@ + + + + + statsURL + + + + + + + + + + + + + +
+ +
+
+
+ +

statsURL

+ +

URL with chat statistics

+

+ +
+
statsURL#47a971e0 url:string = StatsURL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringChat statistics
+

Type

+

StatsURL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stickerPack.html b/data/corefork.telegram.org/constructor/stickerPack.html new file mode 100644 index 0000000000..00468877b5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/stickerPack.html @@ -0,0 +1,156 @@ + + + + + stickerPack + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerPack

+ +

A stickerpack is a group of stickers associated to the same emoji.
+It is not a sticker pack the way it is usually intended, you may be looking for a StickerSet.

+

+ +
+
stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji
documentsVector<long>Stickers
+

Type

+

StickerPack

+

Related pages

+

StickerSet

+

Represents a stickerset (stickerpack)

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stickerSet.html b/data/corefork.telegram.org/constructor/stickerSet.html new file mode 100644 index 0000000000..f453513533 --- /dev/null +++ b/data/corefork.telegram.org/constructor/stickerSet.html @@ -0,0 +1,217 @@ + + + + + stickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSet

+ +

Represents a stickerset (stickerpack)

+

+ +
+
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
archivedflags.1?trueWhether this stickerset was archived (due to too many saved stickers in the current account)
officialflags.2?trueIs this stickerset official
masksflags.3?trueIs this a mask stickerset
animatedflags.5?trueIs this an animated stickerpack
installed_dateflags.0?intWhen was this stickerset installed
idlongID of the stickerset
access_hashlongAccess hash of stickerset
titlestringTitle of stickerset
short_namestringShort name of stickerset to use in tg://addstickers?set=short_name
thumbsflags.4?Vector<PhotoSize>Stickerset thumbnail
thumb_dc_idflags.4?intDC ID of thumbnail
thumb_versionflags.4?intThumbnail version
countintNumber of stickers in pack
hashintHash
+

Type

+

StickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stickerSetCovered.html b/data/corefork.telegram.org/constructor/stickerSetCovered.html new file mode 100644 index 0000000000..4de12252d1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/stickerSetCovered.html @@ -0,0 +1,152 @@ + + + + + stickerSetCovered + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSetCovered

+ +

Stickerset, with a specific sticker as preview

+

+ +
+
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
setStickerSetStickerset
coverDocumentPreview
+

Type

+

StickerSetCovered

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html b/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html new file mode 100644 index 0000000000..f8247c766e --- /dev/null +++ b/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html @@ -0,0 +1,152 @@ + + + + + stickerSetMultiCovered + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSetMultiCovered

+ +

Stickerset, with a specific stickers as preview

+

+ +
+
stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
setStickerSetStickerset
coversVector<Document>Preview stickers
+

Type

+

StickerSetCovered

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stickers.suggestedShortName b/data/corefork.telegram.org/constructor/stickers.suggestedShortName new file mode 100644 index 0000000000..3e4e9e2b3b --- /dev/null +++ b/data/corefork.telegram.org/constructor/stickers.suggestedShortName @@ -0,0 +1,147 @@ + + + + + stickers.suggestedShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.suggestedShortName

+ +

A suggested short name for a stickerpack

+

+ +
+
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
short_namestringSuggested short name
+

Type

+

stickers.SuggestedShortName

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.fileGif b/data/corefork.telegram.org/constructor/storage.fileGif new file mode 100644 index 0000000000..fd11e75844 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.fileGif @@ -0,0 +1,132 @@ + + + + + storage.fileGif + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileGif

+ +

GIF image. MIME type: image/gif.

+

+ +
+
storage.fileGif#cae1aadf = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.fileJpeg b/data/corefork.telegram.org/constructor/storage.fileJpeg new file mode 100644 index 0000000000..018e3293f6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.fileJpeg @@ -0,0 +1,132 @@ + + + + + storage.fileJpeg + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileJpeg

+ +

JPEG image. MIME type: image/jpeg.

+

+ +
+
storage.fileJpeg#7efe0e = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.fileMov b/data/corefork.telegram.org/constructor/storage.fileMov new file mode 100644 index 0000000000..936b1242a5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.fileMov @@ -0,0 +1,132 @@ + + + + + storage.fileMov + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileMov

+ +

Quicktime video. MIME type: video/quicktime.

+

+ +
+
storage.fileMov#4b09ebbc = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.fileMp3 b/data/corefork.telegram.org/constructor/storage.fileMp3 new file mode 100644 index 0000000000..4fed79b77c --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.fileMp3 @@ -0,0 +1,132 @@ + + + + + storage.fileMp3 + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileMp3

+ +

Mp3 audio. MIME type: audio/mpeg.

+

+ +
+
storage.fileMp3#528a0677 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.fileMp4 b/data/corefork.telegram.org/constructor/storage.fileMp4 new file mode 100644 index 0000000000..85a6de8aa8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.fileMp4 @@ -0,0 +1,132 @@ + + + + + storage.fileMp4 + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileMp4

+ +

MPEG-4 video. MIME type: video/mp4.

+

+ +
+
storage.fileMp4#b3cea0e4 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.filePartial b/data/corefork.telegram.org/constructor/storage.filePartial new file mode 100644 index 0000000000..838e707154 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.filePartial @@ -0,0 +1,132 @@ + + + + + storage.filePartial + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.filePartial

+ +

Part of a bigger file.

+

+ +
+
storage.filePartial#40bc6f52 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.filePdf b/data/corefork.telegram.org/constructor/storage.filePdf new file mode 100644 index 0000000000..353f813d00 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.filePdf @@ -0,0 +1,132 @@ + + + + + storage.filePdf + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.filePdf

+ +

PDF document image. MIME type: application/pdf.

+

+ +
+
storage.filePdf#ae1e508d = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.filePng b/data/corefork.telegram.org/constructor/storage.filePng new file mode 100644 index 0000000000..900bdbb2d6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.filePng @@ -0,0 +1,132 @@ + + + + + storage.filePng + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.filePng

+ +

PNG image. MIME type: image/png.

+

+ +
+
storage.filePng#a4f63c0 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.fileUnknown b/data/corefork.telegram.org/constructor/storage.fileUnknown new file mode 100644 index 0000000000..b7c1938c63 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.fileUnknown @@ -0,0 +1,132 @@ + + + + + storage.fileUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileUnknown

+ +

Unknown type.

+

+ +
+
storage.fileUnknown#aa963b05 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/storage.fileWebp b/data/corefork.telegram.org/constructor/storage.fileWebp new file mode 100644 index 0000000000..6545f70c94 --- /dev/null +++ b/data/corefork.telegram.org/constructor/storage.fileWebp @@ -0,0 +1,132 @@ + + + + + storage.fileWebp + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileWebp

+ +

WEBP image. MIME type: image/webp.

+

+ +
+
storage.fileWebp#1081464c = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textAnchor.html b/data/corefork.telegram.org/constructor/textAnchor.html new file mode 100644 index 0000000000..4642cc9d10 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textAnchor.html @@ -0,0 +1,152 @@ + + + + + textAnchor + + + + + + + + + + + + + +
+ +
+
+
+ +

textAnchor

+ +

Text linking to another section of the page

+

+ +
+
textAnchor#35553762 text:RichText name:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
namestringSection name
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textBold.html b/data/corefork.telegram.org/constructor/textBold.html new file mode 100644 index 0000000000..2d0b6efe48 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textBold.html @@ -0,0 +1,147 @@ + + + + + textBold + + + + + + + + + + + + + +
+ +
+
+
+ +

textBold

+ +

Bold text

+

+ +
+
textBold#6724abc4 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textConcat.html b/data/corefork.telegram.org/constructor/textConcat.html new file mode 100644 index 0000000000..9a392bb4a9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textConcat.html @@ -0,0 +1,147 @@ + + + + + textConcat + + + + + + + + + + + + + +
+ +
+
+
+ +

textConcat

+ +

Concatenation of rich texts

+

+ +
+
textConcat#7e6260d7 texts:Vector<RichText> = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textsVector<RichText>Concatenated rich texts
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textEmail.html b/data/corefork.telegram.org/constructor/textEmail.html new file mode 100644 index 0000000000..cc518488b4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textEmail.html @@ -0,0 +1,152 @@ + + + + + textEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

textEmail

+ +

Rich text email link

+

+ +
+
textEmail#de5a0dd6 text:RichText email:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextLink text
emailstringEmail address
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textEmpty.html b/data/corefork.telegram.org/constructor/textEmpty.html new file mode 100644 index 0000000000..09a9dd1f82 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textEmpty.html @@ -0,0 +1,132 @@ + + + + + textEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

textEmpty

+ +

Empty rich text element

+

+ +
+
textEmpty#dc3d824f = RichText;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textFixed.html b/data/corefork.telegram.org/constructor/textFixed.html new file mode 100644 index 0000000000..de6640084f --- /dev/null +++ b/data/corefork.telegram.org/constructor/textFixed.html @@ -0,0 +1,147 @@ + + + + + textFixed + + + + + + + + + + + + + +
+ +
+
+
+ +

textFixed

+ +

fixed-width rich text

+

+ +
+
textFixed#6c3f19b9 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textImage.html b/data/corefork.telegram.org/constructor/textImage.html new file mode 100644 index 0000000000..9a915a9dbd --- /dev/null +++ b/data/corefork.telegram.org/constructor/textImage.html @@ -0,0 +1,157 @@ + + + + + textImage + + + + + + + + + + + + + +
+ +
+
+
+ +

textImage

+ +

Inline image

+

+ +
+
textImage#81ccf4f document_id:long w:int h:int = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
document_idlongDocument ID
wintWidth
hintHeight
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textItalic.html b/data/corefork.telegram.org/constructor/textItalic.html new file mode 100644 index 0000000000..e9cb30ac53 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textItalic.html @@ -0,0 +1,147 @@ + + + + + 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 new file mode 100644 index 0000000000..f0c9e2dbe8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textMarked.html @@ -0,0 +1,147 @@ + + + + + textMarked + + + + + + + + + + + + + +
+ +
+
+
+ +

textMarked

+ +

Highlighted text

+

+ +
+
textMarked#34b8621 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textPhone.html b/data/corefork.telegram.org/constructor/textPhone.html new file mode 100644 index 0000000000..56afc4c652 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textPhone.html @@ -0,0 +1,152 @@ + + + + + textPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

textPhone

+ +

Rich text linked to a phone number

+

+ +
+
textPhone#1ccb966a text:RichText phone:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
phonestringPhone number
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textPlain.html b/data/corefork.telegram.org/constructor/textPlain.html new file mode 100644 index 0000000000..54df9c39e3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textPlain.html @@ -0,0 +1,147 @@ + + + + + textPlain + + + + + + + + + + + + + +
+ +
+
+
+ +

textPlain

+ +

Plain text

+

+ +
+
textPlain#744694e0 text:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textStrike.html b/data/corefork.telegram.org/constructor/textStrike.html new file mode 100644 index 0000000000..35feb9be8b --- /dev/null +++ b/data/corefork.telegram.org/constructor/textStrike.html @@ -0,0 +1,147 @@ + + + + + textStrike + + + + + + + + + + + + + +
+ +
+
+
+ +

textStrike

+ +

Strikethrough text

+

+ +
+
textStrike#9bf8bb95 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textSubscript.html b/data/corefork.telegram.org/constructor/textSubscript.html new file mode 100644 index 0000000000..8aec6e9dcf --- /dev/null +++ b/data/corefork.telegram.org/constructor/textSubscript.html @@ -0,0 +1,147 @@ + + + + + textSubscript + + + + + + + + + + + + + +
+ +
+
+
+ +

textSubscript

+ +

Subscript text

+

+ +
+
textSubscript#ed6a8504 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textSuperscript.html b/data/corefork.telegram.org/constructor/textSuperscript.html new file mode 100644 index 0000000000..08578755f8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textSuperscript.html @@ -0,0 +1,147 @@ + + + + + textSuperscript + + + + + + + + + + + + + +
+ +
+
+
+ +

textSuperscript

+ +

Superscript text

+

+ +
+
textSuperscript#c7fb5e01 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textUnderline.html b/data/corefork.telegram.org/constructor/textUnderline.html new file mode 100644 index 0000000000..71ba552750 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textUnderline.html @@ -0,0 +1,147 @@ + + + + + textUnderline + + + + + + + + + + + + + +
+ +
+
+
+ +

textUnderline

+ +

Underlined text

+

+ +
+
textUnderline#c12622c4 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textUrl.html b/data/corefork.telegram.org/constructor/textUrl.html new file mode 100644 index 0000000000..88b44dcf3f --- /dev/null +++ b/data/corefork.telegram.org/constructor/textUrl.html @@ -0,0 +1,157 @@ + + + + + textUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

textUrl

+ +

Link

+

+ +
+
textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText of link
urlstringWebpage HTTP URL
webpage_idlongIf a preview was already generated for the page, the page ID
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/theme.html b/data/corefork.telegram.org/constructor/theme.html new file mode 100644 index 0000000000..545c1ad675 --- /dev/null +++ b/data/corefork.telegram.org/constructor/theme.html @@ -0,0 +1,197 @@ + + + + + theme + + + + + + + + + + + + + +
+ +
+
+
+ +

theme

+ +

Theme

+

+ +
+
theme#a00e67d6 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?Vector<ThemeSettings> emoticon:flags.6?string installs_count:flags.4?int = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of this theme
defaultflags.1?trueWhether this is the default theme
for_chatflags.5?trueWhether this theme is meant to be used as a chat theme
idlongTheme ID
access_hashlongTheme access hash
slugstringUnique theme ID
titlestringTheme name
documentflags.2?DocumentTheme
settingsflags.3?ThemeSettingsTheme settings
installs_countflags.4?intInstallation count
+

Type

+

Theme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/themeSettings.html b/data/corefork.telegram.org/constructor/themeSettings.html new file mode 100644 index 0000000000..b9006833e5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/themeSettings.html @@ -0,0 +1,177 @@ + + + + + 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/topPeer.html b/data/corefork.telegram.org/constructor/topPeer.html new file mode 100644 index 0000000000..1106bf3ad3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeer.html @@ -0,0 +1,155 @@ + + + + + topPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeer

+ +

Top peer

+

+ +
+
topPeer#edcdc05b peer:Peer rating:double = TopPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
ratingdoubleRating as computed in top peer rating »
+

Type

+

TopPeer

+

Related pages

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryBotsInline.html b/data/corefork.telegram.org/constructor/topPeerCategoryBotsInline.html new file mode 100644 index 0000000000..bc8e3187ac --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryBotsInline.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryBotsInline + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryBotsInline

+ +

Most used inline bots

+

+ +
+
topPeerCategoryBotsInline#148677e2 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryBotsPM.html b/data/corefork.telegram.org/constructor/topPeerCategoryBotsPM.html new file mode 100644 index 0000000000..2e0539f2eb --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryBotsPM.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryBotsPM + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryBotsPM

+ +

Most used bots

+

+ +
+
topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryChannels.html b/data/corefork.telegram.org/constructor/topPeerCategoryChannels.html new file mode 100644 index 0000000000..9bc604c0fa --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryChannels.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryChannels

+ +

Most frequently visited channels

+

+ +
+
topPeerCategoryChannels#161d9628 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryCorrespondents.html b/data/corefork.telegram.org/constructor/topPeerCategoryCorrespondents.html new file mode 100644 index 0000000000..56640f68db --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryCorrespondents.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryCorrespondents + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryCorrespondents

+ +

Users we've chatted most frequently with

+

+ +
+
topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryForwardChats.html b/data/corefork.telegram.org/constructor/topPeerCategoryForwardChats.html new file mode 100644 index 0000000000..08308d651a --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryForwardChats.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryForwardChats + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryForwardChats

+ +

Chats to which the users often forwards messages to

+

+ +
+
topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html b/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html new file mode 100644 index 0000000000..6b0c909888 --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryForwardUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryForwardUsers

+ +

Users to which the users often forwards messages to

+

+ +
+
topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryGroups.html b/data/corefork.telegram.org/constructor/topPeerCategoryGroups.html new file mode 100644 index 0000000000..a61d138c31 --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryGroups.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryGroups + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryGroups

+ +

Often-opened groups and supergroups

+

+ +
+
topPeerCategoryGroups#bd17a14a = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html b/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html new file mode 100644 index 0000000000..f4dd22ec97 --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html @@ -0,0 +1,157 @@ + + + + + topPeerCategoryPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryPeers

+ +

Top peer category

+

+ +
+
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
categoryTopPeerCategoryTop peer category of peers
countintCount of peers
peersVector<TopPeer>Peers
+

Type

+

TopPeerCategoryPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryPhoneCalls.html b/data/corefork.telegram.org/constructor/topPeerCategoryPhoneCalls.html new file mode 100644 index 0000000000..3374e5574e --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryPhoneCalls.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryPhoneCalls + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryPhoneCalls

+ +

Most frequently called users

+

+ +
+
topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/true.html b/data/corefork.telegram.org/constructor/true.html new file mode 100644 index 0000000000..815dd56189 --- /dev/null +++ b/data/corefork.telegram.org/constructor/true.html @@ -0,0 +1,134 @@ + + + + + true + + + + + + + + + + + + + +
+ +
+
+
+ +

true

+ +

See predefined identifiers.

+

+ +
+
true#3fedd339 = True;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

True

+

Related pages

+

TL-formal

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotCallbackQuery.html b/data/corefork.telegram.org/constructor/updateBotCallbackQuery.html new file mode 100644 index 0000000000..c51280440f --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotCallbackQuery.html @@ -0,0 +1,182 @@ + + + + + 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/updateBotChatInviteRequester.html b/data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotCommands.html b/data/corefork.telegram.org/constructor/updateBotCommands.html new file mode 100644 index 0000000000..3278c55d61 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotCommands.html @@ -0,0 +1,159 @@ + + + + + updateBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotCommands

+ +

The command set of a certain bot in a certain chat has changed.

+

+ +
+
updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe affected chat
bot_idlongID of the bot that changed its command set
commandsVector<BotCommand>New bot commands
+

Type

+

Update

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotInlineQuery.html b/data/corefork.telegram.org/constructor/updateBotInlineQuery.html new file mode 100644 index 0000000000..d5c4003262 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotInlineQuery.html @@ -0,0 +1,177 @@ + + + + + updateBotInlineQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotInlineQuery

+ +

An incoming inline query

+

+ +
+
updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongUser that sent the query
querystringText of query
geoflags.0?GeoPointAttached geolocation
peer_typeflags.1?InlineQueryPeerTypeType of the chat from which the inline query was sent.
offsetstringOffset to navigate through results
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotInlineSend.html b/data/corefork.telegram.org/constructor/updateBotInlineSend.html new file mode 100644 index 0000000000..91f13d9ff2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotInlineSend.html @@ -0,0 +1,172 @@ + + + + + updateBotInlineSend + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotInlineSend

+ +

The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.

+

+ +
+
updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_idlongThe user that chose the result
querystringThe query that was used to obtain the result
geoflags.0?GeoPointOptional. Sender location, only for bots that require user location
idstringThe unique identifier for the result that was chosen
msg_idflags.1?InputBotInlineMessageIDIdentifier of the sent inline message. Available only if there is an inline keyboard attached to the message. Will be also received in callback queries and can be used to edit the message.
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotPrecheckoutQuery.html b/data/corefork.telegram.org/constructor/updateBotPrecheckoutQuery.html new file mode 100644 index 0000000000..9ed2c1895e --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotPrecheckoutQuery.html @@ -0,0 +1,184 @@ + + + + + updateBotPrecheckoutQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotPrecheckoutQuery

+ +

This object contains information about an incoming pre-checkout query.

+

+ +
+
updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Type

+

Update

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotShippingQuery.html b/data/corefork.telegram.org/constructor/updateBotShippingQuery.html new file mode 100644 index 0000000000..14b06a612f --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotShippingQuery.html @@ -0,0 +1,162 @@ + + + + + updateBotShippingQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotShippingQuery

+ +

This object contains information about an incoming shipping query.

+

+ +
+
updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
shipping_addressPostAddressUser specified shipping address
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotStopped.html b/data/corefork.telegram.org/constructor/updateBotStopped.html new file mode 100644 index 0000000000..2164ab3153 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotStopped.html @@ -0,0 +1,165 @@ + + + + + updateBotStopped + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotStopped

+ +

A bot was stopped or re-started.

+

+ +
+
updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongThe bot ID
dateintWhen did this action occur
stoppedBoolWhether the bot was stopped or started
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotWebhookJSON.html b/data/corefork.telegram.org/constructor/updateBotWebhookJSON.html new file mode 100644 index 0000000000..75dc467863 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotWebhookJSON.html @@ -0,0 +1,147 @@ + + + + + updateBotWebhookJSON + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotWebhookJSON

+ +

A new incoming event; for bots only

+

+ +
+
updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dataDataJSONThe event
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotWebhookJSONQuery.html b/data/corefork.telegram.org/constructor/updateBotWebhookJSONQuery.html new file mode 100644 index 0000000000..a2fc525b4b --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotWebhookJSONQuery.html @@ -0,0 +1,157 @@ + + + + + updateBotWebhookJSONQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotWebhookJSONQuery

+ +

A new incoming query; for bots only

+

+ +
+
updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
query_idlongQuery identifier
dataDataJSONQuery data
timeoutintQuery timeout
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannel.html b/data/corefork.telegram.org/constructor/updateChannel.html new file mode 100644 index 0000000000..ba17eecaee --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannel.html @@ -0,0 +1,147 @@ + + + + + updateChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannel

+ +

A new channel is available

+

+ +
+
updateChannel#635b4c09 channel_id:long = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html b/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html new file mode 100644 index 0000000000..c44045e79a --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html @@ -0,0 +1,155 @@ + + + + + updateChannelAvailableMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelAvailableMessages

+ +

The history of a channel/supergroup was hidden.

+

+ +
+
updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
available_min_idintIdentifier of a maximum unavailable message in a channel due to hidden history.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelMessageForwards.html b/data/corefork.telegram.org/constructor/updateChannelMessageForwards.html new file mode 100644 index 0000000000..b0f7389f62 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelMessageForwards.html @@ -0,0 +1,157 @@ + + + + + updateChannelMessageForwards + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelMessageForwards

+ +

The forward counter of a message in a channel has changed

+

+ +
+
updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
idintID of the message
forwardsintNew forward counter
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelMessageViews.html b/data/corefork.telegram.org/constructor/updateChannelMessageViews.html new file mode 100644 index 0000000000..3e6b9fb346 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelMessageViews.html @@ -0,0 +1,157 @@ + + + + + updateChannelMessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelMessageViews

+ +

The view counter of a message in a channel has changed

+

+ +
+
updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
idintID of the message
viewsintNew view counter
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelParticipant.html b/data/corefork.telegram.org/constructor/updateChannelParticipant.html new file mode 100644 index 0000000000..8108436803 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelParticipant.html @@ -0,0 +1,192 @@ + + + + + updateChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelParticipant

+ +

A participant has left, joined, was banned or admined in a channel or supergroup.

+

+ +
+
updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
dateintDate of the event
actor_idlongUser that triggered the change (inviter, admin that kicked the user, or the even the user_id itself)
user_idlongUser that was affected by the change
prev_participantflags.0?ChannelParticipantPrevious participant status
new_participantflags.1?ChannelParticipantNew participant status
inviteflags.2?ExportedChatInviteChat invite used to join the channel/supergroup
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html b/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html new file mode 100644 index 0000000000..1ad12f119c --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html @@ -0,0 +1,155 @@ + + + + + updateChannelReadMessagesContents + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelReadMessagesContents

+ +

The specified channel/supergroup messages were read

+

+ +
+
updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
messagesVector<int>IDs of messages that were read
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelTooLong.html b/data/corefork.telegram.org/constructor/updateChannelTooLong.html new file mode 100644 index 0000000000..613e036a93 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelTooLong.html @@ -0,0 +1,161 @@ + + + + + updateChannelTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelTooLong

+ +

There are new updates in the specified channel, the client must fetch them.
+If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.

+

+ +
+
updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongThe channel
ptsflags.0?intThe PTS.
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelUserTyping.html b/data/corefork.telegram.org/constructor/updateChannelUserTyping.html new file mode 100644 index 0000000000..45e930d39c --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelUserTyping.html @@ -0,0 +1,172 @@ + + + + + updateChannelUserTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelUserTyping

+ +

A user is typing in a supergroup, channel or message thread

+

+ +
+
updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
top_msg_idflags.0?intThread ID
from_idPeerThe peer that is typing
actionSendMessageActionWhether the user is typing, sending a media or doing something else
+

Type

+

Update

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelWebPage.html b/data/corefork.telegram.org/constructor/updateChannelWebPage.html new file mode 100644 index 0000000000..4909eeb55e --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelWebPage.html @@ -0,0 +1,167 @@ + + + + + updateChannelWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelWebPage

+ +

A webpage preview of a link in a channel/supergroup message was generated

+

+ +
+
updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
webpageWebPageGenerated webpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html b/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html new file mode 100644 index 0000000000..cc79352cd2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html @@ -0,0 +1,160 @@ + + + + + updateChatDefaultBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatDefaultBannedRights

+ +

Default banned rights in a normal chat were updated

+

+ +
+
updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe chat
default_banned_rightsChatBannedRightsNew default banned rights
versionintVersion
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChatParticipant.html b/data/corefork.telegram.org/constructor/updateChatParticipant.html new file mode 100644 index 0000000000..c02b4849af --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChatParticipant.html @@ -0,0 +1,192 @@ + + + + + updateChatParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipant

+ +

A user has joined or left a specific chat

+

+ +
+
updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
chat_idlongChat ID
dateintWhen did this event occur
actor_idlongUser that triggered the change (inviter, admin that kicked the user, or the even the user_id itself)
user_idlongUser that was affected by the change
prev_participantflags.0?ChatParticipantPrevious participant info (empty if this participant just joined)
new_participantflags.1?ChatParticipantNew participant info (empty if this participant just left)
inviteflags.2?ExportedChatInviteThe invite that was used to join the group
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChatParticipantAdd.html b/data/corefork.telegram.org/constructor/updateChatParticipantAdd.html new file mode 100644 index 0000000000..fe4728ae29 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChatParticipantAdd.html @@ -0,0 +1,167 @@ + + + + + updateChatParticipantAdd + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipantAdd

+ +

New group member.

+

+ +
+
updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup ID
user_idlongID of the new member
inviter_idlongID of the user, who added member to the group
dateintWhen was the participant added
versionintChat version number
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html b/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html new file mode 100644 index 0000000000..c4ec5d7039 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html @@ -0,0 +1,165 @@ + + + + + updateChatParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipantAdmin

+ +

Admin permissions of a user in a legacy group were changed

+

+ +
+
updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
user_idlongID of the (de)admined user
is_adminBoolWhether the user was rendered admin
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChatParticipantDelete.html b/data/corefork.telegram.org/constructor/updateChatParticipantDelete.html new file mode 100644 index 0000000000..7852d758f3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChatParticipantDelete.html @@ -0,0 +1,157 @@ + + + + + updateChatParticipantDelete + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipantDelete

+ +

A member has left the group.

+

+ +
+
updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup ID
user_idlongID of the user
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChatParticipants.html b/data/corefork.telegram.org/constructor/updateChatParticipants.html new file mode 100644 index 0000000000..a9a8baf24e --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChatParticipants.html @@ -0,0 +1,147 @@ + + + + + updateChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipants

+ +

Composition of chat participants changed.

+

+ +
+
updateChatParticipants#7761198 participants:ChatParticipants = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantsChatParticipantsUpdated chat participants
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateConfig.html b/data/corefork.telegram.org/constructor/updateConfig.html new file mode 100644 index 0000000000..3d2d030f11 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateConfig.html @@ -0,0 +1,135 @@ + + + + + updateConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

updateConfig

+ +

The server-side configuration has changed; the client should re-fetch the config using help.getConfig

+

+ +
+
updateConfig#a229dd06 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

help.getConfig

+

Returns current configuration, including data center configuration.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateContactsReset.html b/data/corefork.telegram.org/constructor/updateContactsReset.html new file mode 100644 index 0000000000..f964e2a181 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateContactsReset.html @@ -0,0 +1,132 @@ + + + + + updateContactsReset + + + + + + + + + + + + + +
+ +
+
+
+ +

updateContactsReset

+ +

All contacts were deleted

+

+ +
+
updateContactsReset#7084a7be = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDcOptions.html b/data/corefork.telegram.org/constructor/updateDcOptions.html new file mode 100644 index 0000000000..76dec82b14 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDcOptions.html @@ -0,0 +1,147 @@ + + + + + updateDcOptions + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDcOptions

+ +

Changes in the data center configuration options.

+

+ +
+
updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dc_optionsVector<DcOption>New connection options
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html b/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html new file mode 100644 index 0000000000..e263fd3ab7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html @@ -0,0 +1,167 @@ + + + + + updateDeleteChannelMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDeleteChannelMessages

+ +

Some messages in a supergroup/channel were deleted

+

+ +
+
updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
messagesVector<int>IDs of messages that were deleted
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDeleteMessages.html b/data/corefork.telegram.org/constructor/updateDeleteMessages.html new file mode 100644 index 0000000000..254756c898 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDeleteMessages.html @@ -0,0 +1,160 @@ + + + + + updateDeleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDeleteMessages

+ +

Messages were deleted.

+

+ +
+
updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<int>List of identifiers of deleted messages
ptsintNew quality of actions in a message box
pts_countintNumber of generated events
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDeleteScheduledMessages.html b/data/corefork.telegram.org/constructor/updateDeleteScheduledMessages.html new file mode 100644 index 0000000000..110a0b7ee1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDeleteScheduledMessages.html @@ -0,0 +1,155 @@ + + + + + updateDeleteScheduledMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDeleteScheduledMessages

+ +

Some scheduled messages were deleted from the schedule queue of a chat

+

+ +
+
updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
messagesVector<int>Deleted scheduled messages
+

Type

+

Update

+

Related pages

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDialogFilter.html b/data/corefork.telegram.org/constructor/updateDialogFilter.html new file mode 100644 index 0000000000..5b3e02d5f9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDialogFilter.html @@ -0,0 +1,160 @@ + + + + + updateDialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilter

+ +

A new folder was added

+

+ +
+
updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html b/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html new file mode 100644 index 0000000000..da8c62cdcd --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html @@ -0,0 +1,150 @@ + + + + + updateDialogFilterOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilterOrder

+ +

New folder order

+

+ +
+
updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
orderVector<int>Ordered folder IDs
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDialogFilters.html b/data/corefork.telegram.org/constructor/updateDialogFilters.html new file mode 100644 index 0000000000..10a3e4853f --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDialogFilters.html @@ -0,0 +1,135 @@ + + + + + updateDialogFilters + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilters

+ +

Clients should update folder info

+

+ +
+
updateDialogFilters#3504914f = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDialogPinned.html b/data/corefork.telegram.org/constructor/updateDialogPinned.html new file mode 100644 index 0000000000..ffafdd2896 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDialogPinned.html @@ -0,0 +1,165 @@ + + + + + updateDialogPinned + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogPinned

+ +

A dialog was pinned/unpinned

+

+ +
+
updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the dialog was pinned
folder_idflags.1?intPeer folder ID, for more info click here
peerDialogPeerThe dialog
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDialogUnreadMark.html b/data/corefork.telegram.org/constructor/updateDialogUnreadMark.html new file mode 100644 index 0000000000..00f4f2bef8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDialogUnreadMark.html @@ -0,0 +1,157 @@ + + + + + updateDialogUnreadMark + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogUnreadMark

+ +

The manual unread mark of a chat was changed

+

+ +
+
updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueWas the chat marked or unmarked as read
peerDialogPeerThe dialog
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDraftMessage.html b/data/corefork.telegram.org/constructor/updateDraftMessage.html new file mode 100644 index 0000000000..ab30ae1c67 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDraftMessage.html @@ -0,0 +1,155 @@ + + + + + updateDraftMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDraftMessage

+ +

Notifies a change of a message draft.

+

+ +
+
updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe peer to which the draft is associated
draftDraftMessageThe draft
+

Type

+

Update

+

Related pages

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateEditChannelMessage.html b/data/corefork.telegram.org/constructor/updateEditChannelMessage.html new file mode 100644 index 0000000000..2fe8155e23 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateEditChannelMessage.html @@ -0,0 +1,162 @@ + + + + + updateEditChannelMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEditChannelMessage

+ +

A message was edited in a channel/supergroup

+

+ +
+
updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageThe new message
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html b/data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html new file mode 100644 index 0000000000..31e70a53fb --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html @@ -0,0 +1,147 @@ + + + + + updateEncryptedChatTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEncryptedChatTyping

+ +

Interlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.

+

+ +
+
updateEncryptedChatTyping#1710f156 chat_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idintChat ID
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateEncryptedMessagesRead.html b/data/corefork.telegram.org/constructor/updateEncryptedMessagesRead.html new file mode 100644 index 0000000000..2692ab722d --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateEncryptedMessagesRead.html @@ -0,0 +1,157 @@ + + + + + updateEncryptedMessagesRead + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEncryptedMessagesRead

+ +

Communication history in an encrypted chat was marked as read.

+

+ +
+
updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idintChat ID
max_dateintMaximum value of data for read messages
dateintTime when messages were read
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateEncryption.html b/data/corefork.telegram.org/constructor/updateEncryption.html new file mode 100644 index 0000000000..9f512967a6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateEncryption.html @@ -0,0 +1,152 @@ + + + + + updateEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

updateEncryption

+ +

Change of state in an encrypted chat.

+

+ +
+
updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chatEncryptedChatEncrypted chat
dateintDate of change
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateFavedStickers.html b/data/corefork.telegram.org/constructor/updateFavedStickers.html new file mode 100644 index 0000000000..f708009921 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateFavedStickers.html @@ -0,0 +1,135 @@ + + + + + updateFavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateFavedStickers

+ +

The list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list

+

+ +
+
updateFavedStickers#e511996d = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

messages.getFavedStickers

+

Get faved stickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateFolderPeers.html b/data/corefork.telegram.org/constructor/updateFolderPeers.html new file mode 100644 index 0000000000..9bc986ed12 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateFolderPeers.html @@ -0,0 +1,162 @@ + + + + + updateFolderPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateFolderPeers

+ +

The peer list of a peer folder was updated

+

+ +
+
updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
folder_peersVector<FolderPeer>New peer list
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateGeoLiveViewed.html b/data/corefork.telegram.org/constructor/updateGeoLiveViewed.html new file mode 100644 index 0000000000..1029ae5b41 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateGeoLiveViewed.html @@ -0,0 +1,152 @@ + + + + + updateGeoLiveViewed + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGeoLiveViewed

+ +

Live geoposition message was viewed

+

+ +
+
updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe user that viewed the live geoposition
msg_idintMessage ID of geoposition message
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateGroupCall.html b/data/corefork.telegram.org/constructor/updateGroupCall.html new file mode 100644 index 0000000000..2926962d87 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateGroupCall.html @@ -0,0 +1,155 @@ + + + + + updateGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGroupCall

+ +

A new groupcall was started

+

+ +
+
updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongThe channel/supergroup where this group call or livestream takes place
callGroupCallInfo about the group call or livestream
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateGroupCallConnection.html b/data/corefork.telegram.org/constructor/updateGroupCallConnection.html new file mode 100644 index 0000000000..3414db2224 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateGroupCallConnection.html @@ -0,0 +1,157 @@ + + + + + updateGroupCallConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGroupCallConnection

+ +

New WebRTC parameters

+

+ +
+
updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
presentationflags.0?trueAre these parameters related to the screen capture session currently in progress?
paramsDataJSONWebRTC parameters
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateGroupCallParticipants.html b/data/corefork.telegram.org/constructor/updateGroupCallParticipants.html new file mode 100644 index 0000000000..6b4d62450f --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateGroupCallParticipants.html @@ -0,0 +1,157 @@ + + + + + updateGroupCallParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGroupCallParticipants

+ +

The participant list of a certain group call has changed

+

+ +
+
updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
participantsVector<GroupCallParticipant>New participant list
versionintVersion
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateInlineBotCallbackQuery.html b/data/corefork.telegram.org/constructor/updateInlineBotCallbackQuery.html new file mode 100644 index 0000000000..0ebbea1d4d --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateInlineBotCallbackQuery.html @@ -0,0 +1,177 @@ + + + + + updateInlineBotCallbackQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateInlineBotCallbackQuery

+ +

This notification is received by bots when a button is pressed

+

+ +
+
updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongID of the user that pressed the button
msg_idInputBotInlineMessageIDID of the inline message with the button
chat_instancelongGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataflags.0?bytesData associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
game_short_nameflags.1?stringShort name of a Game to be returned, serves as the unique identifier for the game
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateLangPack.html b/data/corefork.telegram.org/constructor/updateLangPack.html new file mode 100644 index 0000000000..b084e3b550 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateLangPack.html @@ -0,0 +1,147 @@ + + + + + updateLangPack + + + + + + + + + + + + + +
+ +
+
+
+ +

updateLangPack

+ +

Language pack updated

+

+ +
+
updateLangPack#56022f4d difference:LangPackDifference = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
differenceLangPackDifferenceChanged strings
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateLangPackTooLong.html b/data/corefork.telegram.org/constructor/updateLangPackTooLong.html new file mode 100644 index 0000000000..9e51363cf4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateLangPackTooLong.html @@ -0,0 +1,150 @@ + + + + + updateLangPackTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updateLangPackTooLong

+ +

A language pack has changed, the client should manually fetch the changed strings using langpack.getDifference

+

+ +
+
updateLangPackTooLong#46560264 lang_code:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Type

+

Update

+

Related pages

+

langpack.getDifference

+

Get new strings in languagepack

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateMessageID.html b/data/corefork.telegram.org/constructor/updateMessageID.html new file mode 100644 index 0000000000..190ee0ef51 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateMessageID.html @@ -0,0 +1,155 @@ + + + + + updateMessageID + + + + + + + + + + + + + +
+ +
+
+
+ +

updateMessageID

+ +

Sent message with random_id client identifier was assigned an identifier.

+

+ +
+
updateMessageID#4e90bfd6 id:int random_id:long = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintid identifier of a respective Message
random_idlongPreviuosly transferred client random_id identifier
+

Type

+

Update

+

Related pages

+

Message

+

Object describing a message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateMessagePoll.html b/data/corefork.telegram.org/constructor/updateMessagePoll.html new file mode 100644 index 0000000000..660320a94e --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateMessagePoll.html @@ -0,0 +1,162 @@ + + + + + updateMessagePoll + + + + + + + + + + + + + +
+ +
+
+
+ +

updateMessagePoll

+ +

The results of a poll have changed

+

+ +
+
updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
poll_idlongPoll ID
pollflags.0?PollIf the server knows the client hasn't cached this poll yet, the poll itself
resultsPollResultsNew poll results
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateMessagePollVote.html b/data/corefork.telegram.org/constructor/updateMessagePollVote.html new file mode 100644 index 0000000000..252a517411 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateMessagePollVote.html @@ -0,0 +1,165 @@ + + + + + updateMessagePollVote + + + + + + + + + + + + + +
+ +
+
+
+ +

updateMessagePollVote

+ +

A specific user has voted in a poll

+

+ +
+
updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
poll_idlongPoll ID
user_idlongUser ID
optionsVector<bytes>Chosen option(s)
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateMessageReactions.html b/data/corefork.telegram.org/constructor/updateMessageReactions.html new file mode 100644 index 0000000000..e12a87a4dd --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateMessageReactions.html @@ -0,0 +1,157 @@ + + + + + updateMessageReactions + + + + + + + + + + + + + +
+ +
+
+
+ +

updateMessageReactions

+ +

New message reactions are available

+

+ +
+
updateMessageReactions#154798c3 peer:Peer msg_id:int reactions:MessageReactions = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
msg_idintMessage ID
reactionsMessageReactionsReactions
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateNewChannelMessage.html b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html new file mode 100644 index 0000000000..cfdcbbe951 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html @@ -0,0 +1,162 @@ + + + + + updateNewChannelMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewChannelMessage

+ +

A new message was sent in a channel/supergroup

+

+ +
+
updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageNew message
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateNewEncryptedMessage.html b/data/corefork.telegram.org/constructor/updateNewEncryptedMessage.html new file mode 100644 index 0000000000..5c5463eb79 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateNewEncryptedMessage.html @@ -0,0 +1,155 @@ + + + + + updateNewEncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewEncryptedMessage

+ +

New encrypted message.

+

+ +
+
updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageEncryptedMessageMessage
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateNewMessage.html b/data/corefork.telegram.org/constructor/updateNewMessage.html new file mode 100644 index 0000000000..f2b3e7f2f7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateNewMessage.html @@ -0,0 +1,157 @@ + + + + + updateNewMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewMessage

+ +

New message in a private chat or in a legacy group.

+

+ +
+
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageMessage
ptsintNew quantity of actions in a message box
pts_countintNumber of generated events
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateNewScheduledMessage.html b/data/corefork.telegram.org/constructor/updateNewScheduledMessage.html new file mode 100644 index 0000000000..b2a33ce788 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateNewScheduledMessage.html @@ -0,0 +1,150 @@ + + + + + updateNewScheduledMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewScheduledMessage

+ +

A message was added to the schedule queue of a chat

+

+ +
+
updateNewScheduledMessage#39a51dfb message:Message = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageMessage
+

Type

+

Update

+

Related pages

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateNewStickerSet.html b/data/corefork.telegram.org/constructor/updateNewStickerSet.html new file mode 100644 index 0000000000..53622c0d3d --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateNewStickerSet.html @@ -0,0 +1,147 @@ + + + + + updateNewStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewStickerSet

+ +

A new stickerset was installed

+

+ +
+
updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickersetmessages.StickerSetThe installed stickerset
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePeerBlocked.html b/data/corefork.telegram.org/constructor/updatePeerBlocked.html new file mode 100644 index 0000000000..2f7f2e6359 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePeerBlocked.html @@ -0,0 +1,152 @@ + + + + + updatePeerBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerBlocked

+ +

A peer was blocked

+

+ +
+
updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peer_idPeerThe blocked peer
blockedBoolWhether the peer was blocked or unblocked
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePeerHistoryTTL.html b/data/corefork.telegram.org/constructor/updatePeerHistoryTTL.html new file mode 100644 index 0000000000..50911390c0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePeerHistoryTTL.html @@ -0,0 +1,157 @@ + + + + + updatePeerHistoryTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerHistoryTTL

+ +

The Time-To-Live for messages sent by the current user in a specific chat has changed

+

+ +
+
updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerPeerThe chat
ttl_periodflags.0?intThe new Time-To-Live
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePeerLocated.html b/data/corefork.telegram.org/constructor/updatePeerLocated.html new file mode 100644 index 0000000000..4ef0bf45bc --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePeerLocated.html @@ -0,0 +1,147 @@ + + + + + updatePeerLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerLocated

+ +

List of peers near you was updated

+

+ +
+
updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peersVector<PeerLocated>Geolocated peer list update
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePeerSettings.html b/data/corefork.telegram.org/constructor/updatePeerSettings.html new file mode 100644 index 0000000000..4b62b9f536 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePeerSettings.html @@ -0,0 +1,152 @@ + + + + + updatePeerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerSettings

+ +

Settings of a certain peer have changed

+

+ +
+
updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerThe peer
settingsPeerSettingsAssociated peer settings
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePendingJoinRequests.html b/data/corefork.telegram.org/constructor/updatePendingJoinRequests.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePendingJoinRequests.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePhoneCall.html b/data/corefork.telegram.org/constructor/updatePhoneCall.html new file mode 100644 index 0000000000..91463d53ab --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePhoneCall.html @@ -0,0 +1,147 @@ + + + + + updatePhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePhoneCall

+ +

An incoming phone call

+

+ +
+
updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phone_callPhoneCallPhone call
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html b/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html new file mode 100644 index 0000000000..4387a7c622 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html @@ -0,0 +1,152 @@ + + + + + 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/updatePinnedChannelMessages.html b/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html new file mode 100644 index 0000000000..09628654d6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html @@ -0,0 +1,177 @@ + + + + + updatePinnedChannelMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePinnedChannelMessages

+ +

Messages were pinned/unpinned in a channel/supergroup

+

+ +
+
updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
channel_idlongChannel ID
messagesVector<int>Messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePinnedDialogs.html b/data/corefork.telegram.org/constructor/updatePinnedDialogs.html new file mode 100644 index 0000000000..cd3806336d --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePinnedDialogs.html @@ -0,0 +1,160 @@ + + + + + updatePinnedDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePinnedDialogs

+ +

Pinned dialogs were updated

+

+ +
+
updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.1?intPeer folder ID, for more info click here
orderflags.0?Vector<DialogPeer>New order of pinned dialogs
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePinnedMessages.html b/data/corefork.telegram.org/constructor/updatePinnedMessages.html new file mode 100644 index 0000000000..219633fcc8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePinnedMessages.html @@ -0,0 +1,175 @@ + + + + + updatePinnedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePinnedMessages

+ +

Some messages were pinned in a chat

+

+ +
+
updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
peerPeerPeer
messagesVector<int>Message IDs
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePrivacy.html b/data/corefork.telegram.org/constructor/updatePrivacy.html new file mode 100644 index 0000000000..7b78060a56 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePrivacy.html @@ -0,0 +1,152 @@ + + + + + updatePrivacy + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePrivacy

+ +

Privacy rules were changed

+

+ +
+
updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keyPrivacyKeyPeers to which the privacy rules apply
rulesVector<PrivacyRule>New privacy rules
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePtsChanged.html b/data/corefork.telegram.org/constructor/updatePtsChanged.html new file mode 100644 index 0000000000..40b2724b1c --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePtsChanged.html @@ -0,0 +1,135 @@ + + + + + updatePtsChanged + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePtsChanged

+ +

Common message box sequence PTS has changed, state has to be refetched using updates.getState

+

+ +
+
updatePtsChanged#3354678f = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html new file mode 100644 index 0000000000..130403d2d0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html @@ -0,0 +1,177 @@ + + + + + updateReadChannelDiscussionInbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelDiscussionInbox

+ +

Incoming comments in a discussion thread were marked as read

+

+ +
+
updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongDiscussion group ID
top_msg_idintID of the group message that started the thread (message in linked discussion group)
read_max_idintMessage ID of latest read incoming message for this thread
broadcast_idflags.0?longIf set, contains the ID of the channel that contains the post that started the comment thread in the discussion group (channel_id)
broadcast_postflags.0?intIf set, contains the ID of the channel post that started the the comment thread
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html new file mode 100644 index 0000000000..cd34b10b53 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html @@ -0,0 +1,162 @@ + + + + + updateReadChannelDiscussionOutbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelDiscussionOutbox

+ +

Outgoing comments in a discussion thread were marked as read

+

+ +
+
updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongSupergroup ID
top_msg_idintID of the group message that started the thread
read_max_idintMessage ID of latest read outgoing message for this thread
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadChannelInbox.html b/data/corefork.telegram.org/constructor/updateReadChannelInbox.html new file mode 100644 index 0000000000..952fd9e04b --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadChannelInbox.html @@ -0,0 +1,179 @@ + + + + + updateReadChannelInbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelInbox

+ +

Incoming messages in a channel/supergroup were read

+

+ +
+
updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
channel_idlongChannel/supergroup ID
max_idintPosition up to which all incoming messages are read.
still_unread_countintCount of messages weren't read yet
ptsintEvent count after generation
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html b/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html new file mode 100644 index 0000000000..4f3c60e203 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html @@ -0,0 +1,155 @@ + + + + + updateReadChannelOutbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelOutbox

+ +

Outgoing messages in a channel/supergroup were read

+

+ +
+
updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
max_idintPosition up to which all outgoing messages are read.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadFeaturedStickers.html b/data/corefork.telegram.org/constructor/updateReadFeaturedStickers.html new file mode 100644 index 0000000000..ff314a2317 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadFeaturedStickers.html @@ -0,0 +1,132 @@ + + + + + updateReadFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadFeaturedStickers

+ +

Some featured stickers were marked as read

+

+ +
+
updateReadFeaturedStickers#571d2742 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html b/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html new file mode 100644 index 0000000000..4e49ec227b --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html @@ -0,0 +1,182 @@ + + + + + updateReadHistoryInbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadHistoryInbox

+ +

Incoming messages were read

+

+ +
+
updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
peerPeerPeer
max_idintMaximum ID of messages read
still_unread_countintNumber of messages that are still unread
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadHistoryOutbox.html b/data/corefork.telegram.org/constructor/updateReadHistoryOutbox.html new file mode 100644 index 0000000000..20020c9f83 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadHistoryOutbox.html @@ -0,0 +1,165 @@ + + + + + updateReadHistoryOutbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadHistoryOutbox

+ +

Outgoing messages were read

+

+ +
+
updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
max_idintMaximum ID of read outgoing messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadMessagesContents.html b/data/corefork.telegram.org/constructor/updateReadMessagesContents.html new file mode 100644 index 0000000000..75423145b4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadMessagesContents.html @@ -0,0 +1,160 @@ + + + + + updateReadMessagesContents + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadMessagesContents

+ +

Contents of messages in the common message box were read

+

+ +
+
updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<int>IDs of read messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateRecentStickers.html b/data/corefork.telegram.org/constructor/updateRecentStickers.html new file mode 100644 index 0000000000..0d72b9b8be --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateRecentStickers.html @@ -0,0 +1,132 @@ + + + + + updateRecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateRecentStickers

+ +

The recent sticker list was updated

+

+ +
+
updateRecentStickers#9a422c20 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateServiceNotification.html b/data/corefork.telegram.org/constructor/updateServiceNotification.html new file mode 100644 index 0000000000..d0c40d707b --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateServiceNotification.html @@ -0,0 +1,183 @@ + + + + + updateServiceNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

updateServiceNotification

+ +

A service message for the user.

+

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

+

+ +
+
updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?true(boolTrue) if the message must be displayed in a popup.
inbox_dateflags.1?intWhen was the notification received
The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
typestringString, identical in format and contents to the type field in API errors. Describes type of service message. It is acceptable to ignore repeated messages of the same type within a short period of time (15 minutes).
messagestringMessage text
mediaMessageMediaMedia content (optional)
entitiesVector<MessageEntity>Message entities for styled text
+

Type

+

Update

+

Related pages

+

Error handling

+

How to handle API return errors correctly.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateShort.html b/data/corefork.telegram.org/constructor/updateShort.html new file mode 100644 index 0000000000..27d5cbc112 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateShort.html @@ -0,0 +1,152 @@ + + + + + updateShort + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShort

+ +

Shortened constructor containing info on one update not requiring auxiliary data

+

+ +
+
updateShort#78d4dec1 update:Update date:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
updateUpdateUpdate
dateintDate of event
+

Type

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateShortChatMessage.html b/data/corefork.telegram.org/constructor/updateShortChatMessage.html new file mode 100644 index 0000000000..ef215c660a --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateShortChatMessage.html @@ -0,0 +1,232 @@ + + + + + updateShortChatMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShortChatMessage

+ +

Shortened constructor containing info on one new incoming text message from a chat

+

+ +
+
updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in this message
media_unreadflags.5?trueWhether the message contains some unread mentions
silentflags.13?trueIf true, the message is a silent message, no notifications should be triggered
idintID of the message
from_idlongID of the sender of the message
chat_idlongID of the chat where the message was sent
messagestringMessage
ptsintPTS
pts_countintPTS count
dateintdate
fwd_fromflags.2?MessageFwdHeaderInfo about a forwarded message
via_bot_idflags.11?longInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply (thread) information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once updateShortChatMessage.date+updateShortChatMessage.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Updates

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateShortMessage.html b/data/corefork.telegram.org/constructor/updateShortMessage.html new file mode 100644 index 0000000000..756e1e327d --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateShortMessage.html @@ -0,0 +1,229 @@ + + + + + updateShortMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShortMessage

+ +

Info about a message sent to (received from) another user

+

+ +
+
updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether there are some unread mentions in this message
silentflags.13?trueIf true, the message is a silent message, no notifications should be triggered
idintThe message ID
user_idlongThe ID of the sender (if outgoing will be the ID of the destination) of the message
messagestringThe message
ptsintPTS
pts_countintPTS count
dateintdate
fwd_fromflags.2?MessageFwdHeaderInfo about a forwarded message
via_bot_idflags.11?longInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply and thread information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Updates

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateShortSentMessage.html b/data/corefork.telegram.org/constructor/updateShortSentMessage.html new file mode 100644 index 0000000000..7983fe20a4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateShortSentMessage.html @@ -0,0 +1,192 @@ + + + + + updateShortSentMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShortSentMessage

+ +

Shortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).

+

+ +
+
updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
idintID of the sent message
ptsintPTS
pts_countintPTS count
dateintdate
mediaflags.9?MessageMediaAttached media
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Updates

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateStickerSets.html b/data/corefork.telegram.org/constructor/updateStickerSets.html new file mode 100644 index 0000000000..1c179acec2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateStickerSets.html @@ -0,0 +1,132 @@ + + + + + updateStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

updateStickerSets

+ +

Installed stickersets have changed, the client should refetch them using messages.getAllStickers

+

+ +
+
updateStickerSets#43ae3dec = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html b/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html new file mode 100644 index 0000000000..7fc2c166ec --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html @@ -0,0 +1,157 @@ + + + + + updateStickerSetsOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

updateStickerSetsOrder

+ +

The order of stickersets was changed

+

+ +
+
updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether the updated stickers are mask stickers
orderVector<long>New sticker order by sticker ID
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateTheme.html b/data/corefork.telegram.org/constructor/updateTheme.html new file mode 100644 index 0000000000..84ad335e96 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateTheme.html @@ -0,0 +1,147 @@ + + + + + updateTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

updateTheme

+ +

A cloud theme was updated

+

+ +
+
updateTheme#8216fba3 theme:Theme = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
themeThemeTheme
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateUserBlocked.html b/data/corefork.telegram.org/constructor/updateUserBlocked.html new file mode 100644 index 0000000000..32c9cd5ffe --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateUserBlocked.html @@ -0,0 +1,159 @@ + + + + + updateUserBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserBlocked

+ +

User was added to the blacklist (method contacts.block) or removed from the blacklist (method contacts.unblock).

+

+ +
+
Constructor schema is available as of layer 119. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idintUser id
blockedBool(boolTrue) if the the user is blocked
+

Type

+

Update

+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

contacts.block

+

Adds the user to the blacklist.

+

contacts.unblock

+

Deletes the user from the blacklist.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateUserName.html b/data/corefork.telegram.org/constructor/updateUserName.html new file mode 100644 index 0000000000..778275d4c8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateUserName.html @@ -0,0 +1,167 @@ + + + + + updateUserName + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserName

+ +

Changes the user's first name, last name and username.

+

+ +
+
updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
first_namestringNew first name. Corresponds to the new value of real_first_name field of the userFull constructor.
last_namestringNew last name. Corresponds to the new value of real_last_name field of the userFull constructor.
usernamestringNew username.
Parameter added in Layer 18.
+

Type

+

Update

+

Related pages

+

userFull

+

Extended user info

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateUserPhone.html b/data/corefork.telegram.org/constructor/updateUserPhone.html new file mode 100644 index 0000000000..49d7b93c93 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateUserPhone.html @@ -0,0 +1,152 @@ + + + + + updateUserPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserPhone

+ +

A user's phone number was changed

+

+ +
+
updateUserPhone#5492a13 user_id:long phone:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
phonestringNew phone number
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateUserPhoto.html b/data/corefork.telegram.org/constructor/updateUserPhoto.html new file mode 100644 index 0000000000..2bae05d8db --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateUserPhoto.html @@ -0,0 +1,165 @@ + + + + + updateUserPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserPhoto

+ +

Change of contact's profile photo.

+

+ +
+
updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
dateintDate of photo update.
photoUserProfilePhotoNew profile photo
previousBool(boolTrue), if one of the previously used photos is set a profile photo.
+

Type

+

Update

+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateUserStatus.html b/data/corefork.telegram.org/constructor/updateUserStatus.html new file mode 100644 index 0000000000..7fe0f7552a --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateUserStatus.html @@ -0,0 +1,152 @@ + + + + + updateUserStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserStatus

+ +

Contact status update.

+

+ +
+
updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
statusUserStatusNew status
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateUserTyping.html b/data/corefork.telegram.org/constructor/updateUserTyping.html new file mode 100644 index 0000000000..caf916f79f --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateUserTyping.html @@ -0,0 +1,155 @@ + + + + + updateUserTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserTyping

+ +

The user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

+

+ +
+
updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser id
actionSendMessageActionAction type
Param added in Layer 17.
+

Type

+

Update

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateWebPage.html b/data/corefork.telegram.org/constructor/updateWebPage.html new file mode 100644 index 0000000000..7c4fccbaa0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateWebPage.html @@ -0,0 +1,160 @@ + + + + + updateWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateWebPage

+ +

An instant view webpage preview was generated

+

+ +
+
updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
webpageWebPageWebpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.channelDifference b/data/corefork.telegram.org/constructor/updates.channelDifference new file mode 100644 index 0000000000..4adbe92aee --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.channelDifference @@ -0,0 +1,185 @@ + + + + + updates.channelDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.channelDifference

+ +

The new updates

+

+ +
+
updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates to be fetched using getDifference, starting from the provided pts
ptsintThe PTS from which to start getting updates the next time
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
new_messagesVector<Message>New messages
other_updatesVector<Update>Other updates
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

updates.ChannelDifference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.channelDifferenceEmpty b/data/corefork.telegram.org/constructor/updates.channelDifferenceEmpty new file mode 100644 index 0000000000..898d66f1bd --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.channelDifferenceEmpty @@ -0,0 +1,165 @@ + + + + + updates.channelDifferenceEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.channelDifferenceEmpty

+ +

There are no new updates

+

+ +
+
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
ptsintThe latest PTS
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
+

Type

+

updates.ChannelDifference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong b/data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong new file mode 100644 index 0000000000..69dc513679 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong @@ -0,0 +1,190 @@ + + + + + updates.channelDifferenceTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.channelDifferenceTooLong

+ +

The provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

+
    +
  1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
  2. +
  3. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
  4. +
  5. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
  6. +
  7. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
  8. +
+

+ +
+
updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
dialogDialogDialog containing the latest PTS that can be used to reset the channel state
messagesVector<Message>The latest messages
chatsVector<Chat>Chats from messages
usersVector<User>Users from messages
+

Type

+

updates.ChannelDifference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

messages.getHistory

+

Gets back the conversation history with one interlocutor / within a chat

+

messages.getMessages

+

Returns the list of messages by their IDs.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.difference b/data/corefork.telegram.org/constructor/updates.difference new file mode 100644 index 0000000000..703653339d --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.difference @@ -0,0 +1,172 @@ + + + + + updates.difference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.difference

+ +

Full list of occurred events.

+

+ +
+
updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
new_messagesVector<Message>List of new messages
new_encrypted_messagesVector<EncryptedMessage>List of new encrypted secret chat messages
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
stateupdates.StateCurrent state
+

Type

+

updates.Difference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.differenceEmpty b/data/corefork.telegram.org/constructor/updates.differenceEmpty new file mode 100644 index 0000000000..34462a8df7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.differenceEmpty @@ -0,0 +1,152 @@ + + + + + updates.differenceEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceEmpty

+ +

No events.

+

+ +
+
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dateintCurrent date
seqintNumber of sent updates
+

Type

+

updates.Difference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.differenceSlice b/data/corefork.telegram.org/constructor/updates.differenceSlice new file mode 100644 index 0000000000..153b8761f6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.differenceSlice @@ -0,0 +1,175 @@ + + + + + updates.differenceSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceSlice

+ +

Incomplete list of occurred events.

+

+ +
+
updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
new_messagesVector<Message>List of new messgaes
new_encrypted_messagesVector<EncryptedMessage>New messages from the encrypted event sequence
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
intermediate_stateupdates.StateIntermediary state
+

Type

+

updates.Difference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.differenceTooLong b/data/corefork.telegram.org/constructor/updates.differenceTooLong new file mode 100644 index 0000000000..e72286ccdd --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.differenceTooLong @@ -0,0 +1,150 @@ + + + + + updates.differenceTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceTooLong

+ +

The difference is too long, and the specified state must be used to refetch updates.

+

+ +
+
updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
ptsintThe new state to use.
+

Type

+

updates.Difference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.html b/data/corefork.telegram.org/constructor/updates.html new file mode 100644 index 0000000000..cf5f337ecd --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.html @@ -0,0 +1,167 @@ + + + + + Updates + + + + + + + + + + + + + +
+ +
+
+
+ +

Updates

+ +

Full constructor of updates

+

+ +
+
updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seqintTotal number of sent updates
+

Type

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.state b/data/corefork.telegram.org/constructor/updates.state new file mode 100644 index 0000000000..b07f7e97ca --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.state @@ -0,0 +1,172 @@ + + + + + updates.state + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.state

+ +

Updates state.

+

+ +
+
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintNumber of events occured in a text box
qtsintPosition in a sequence of updates in secret chats. For further detailes refer to article secret chats
Parameter was added in eigth layer.
dateintDate of condition
seqintNumber of sent updates
unread_countintNumber of unread messages
+

Type

+

updates.State

+

Related pages

+

End-to-End Encryption, Secret Chats

+

New feature for end-to-end-encrypted messaging.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatesCombined.html b/data/corefork.telegram.org/constructor/updatesCombined.html new file mode 100644 index 0000000000..ee91e66255 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatesCombined.html @@ -0,0 +1,172 @@ + + + + + updatesCombined + + + + + + + + + + + + + +
+ +
+
+
+ +

updatesCombined

+ +

Constructor for a group of updates.

+

+ +
+
updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seq_startintValue seq for the earliest update in a group
seqintValue seq for the latest update in a group
+

Type

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatesTooLong.html b/data/corefork.telegram.org/constructor/updatesTooLong.html new file mode 100644 index 0000000000..0ca8c8e35c --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatesTooLong.html @@ -0,0 +1,135 @@ + + + + + updatesTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updatesTooLong

+ +

Too many updates, it is necessary to execute updates.getDifference.

+

+ +
+
updatesTooLong#e317af7e = Updates;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Updates

+

Related pages

+

updates.getDifference

+

Get new updates.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/upload.cdnFile b/data/corefork.telegram.org/constructor/upload.cdnFile new file mode 100644 index 0000000000..50e7b2a73d --- /dev/null +++ b/data/corefork.telegram.org/constructor/upload.cdnFile @@ -0,0 +1,149 @@ + + + + + upload.cdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.cdnFile

+ +

Represent a chunk of a CDN file.

+

+ +
+
upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
bytesbytesThe data
+

Type

+

upload.CdnFile

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded b/data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded new file mode 100644 index 0000000000..db9ee2506e --- /dev/null +++ b/data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded @@ -0,0 +1,149 @@ + + + + + upload.cdnFileReuploadNeeded + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.cdnFileReuploadNeeded

+ +

The file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.

+

+ +
+
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
request_tokenbytesRequest token (see CDN)
+

Type

+

upload.CdnFile

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/upload.file b/data/corefork.telegram.org/constructor/upload.file new file mode 100644 index 0000000000..a3fe7bcae2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/upload.file @@ -0,0 +1,157 @@ + + + + + upload.file + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.file

+ +

File content.

+

+ +
+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestorage.FileTypeFile type
mtimeintModification type
bytesbytesBinary data, file content
+

Type

+

upload.File

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/upload.fileCdnRedirect b/data/corefork.telegram.org/constructor/upload.fileCdnRedirect new file mode 100644 index 0000000000..fffc57c0ce --- /dev/null +++ b/data/corefork.telegram.org/constructor/upload.fileCdnRedirect @@ -0,0 +1,169 @@ + + + + + upload.fileCdnRedirect + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.fileCdnRedirect

+ +

The file must be downloaded from a CDN DC.

+

+ +
+
upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintCDN DC ID
file_tokenbytesFile token (see CDN files)
encryption_keybytesEncryption key (see CDN files)
encryption_ivbytesEncryption IV (see CDN files)
file_hashesVector<FileHash>File hashes (see CDN files)
+

Type

+

upload.File

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/upload.webFile b/data/corefork.telegram.org/constructor/upload.webFile new file mode 100644 index 0000000000..228f4cce38 --- /dev/null +++ b/data/corefork.telegram.org/constructor/upload.webFile @@ -0,0 +1,170 @@ + + + + + upload.webFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.webFile

+ +

Represents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers

+

+ +
+
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
sizeintFile size
mime_typestringMime type
file_typestorage.FileTypeFile type
mtimeintModified time
bytesbytesData
+

Type

+

upload.WebFile

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/urlAuthResultAccepted.html b/data/corefork.telegram.org/constructor/urlAuthResultAccepted.html new file mode 100644 index 0000000000..02be5c6b41 --- /dev/null +++ b/data/corefork.telegram.org/constructor/urlAuthResultAccepted.html @@ -0,0 +1,150 @@ + + + + + urlAuthResultAccepted + + + + + + + + + + + + + +
+ +
+
+
+ +

urlAuthResultAccepted

+ +

Details about an accepted authorization request, for more info click here »

+

+ +
+
urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringThe URL name of the website on which the user has logged in.
+

Type

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/urlAuthResultDefault.html b/data/corefork.telegram.org/constructor/urlAuthResultDefault.html new file mode 100644 index 0000000000..9a5e4c4a3b --- /dev/null +++ b/data/corefork.telegram.org/constructor/urlAuthResultDefault.html @@ -0,0 +1,135 @@ + + + + + urlAuthResultDefault + + + + + + + + + + + + + +
+ +
+
+
+ +

urlAuthResultDefault

+ +

Details about an accepted authorization request, for more info click here »

+

+ +
+
urlAuthResultDefault#a9d6db1f = UrlAuthResult;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/urlAuthResultRequest.html b/data/corefork.telegram.org/constructor/urlAuthResultRequest.html new file mode 100644 index 0000000000..a7c222616c --- /dev/null +++ b/data/corefork.telegram.org/constructor/urlAuthResultRequest.html @@ -0,0 +1,165 @@ + + + + + urlAuthResultRequest + + + + + + + + + + + + + +
+ +
+
+
+ +

urlAuthResultRequest

+ +

Details about the authorization request, for more info click here »

+

+ +
+
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueWhether the bot would like to send messages to the user
botUserUsername of a bot, which will be used for user authorization. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
domainstringThe domain name of the website on which the user will log in.
+

Type

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/user.html b/data/corefork.telegram.org/constructor/user.html new file mode 100644 index 0000000000..4f338d1029 --- /dev/null +++ b/data/corefork.telegram.org/constructor/user.html @@ -0,0 +1,287 @@ + + + + + user + + + + + + + + + + + + + +
+ +
+
+
+ +

user

+ +

Indicates info about a certain user

+

+ +
+
user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
selfflags.10?trueWhether this user indicates the currently logged in user
contactflags.11?trueWhether this user is a contact
mutual_contactflags.12?trueWhether this user is a mutual contact
deletedflags.13?trueWhether the account of this user was deleted
botflags.14?trueIs this user a bot?
bot_chat_historyflags.15?trueCan the bot see all messages in groups?
bot_nochatsflags.16?trueCan the bot be added to groups?
verifiedflags.17?trueWhether this user is verified
restrictedflags.18?trueAccess to this user must be restricted for the reason specified in restriction_reason
minflags.20?trueSee min
bot_inline_geoflags.21?trueWhether the bot can request our geolocation in inline mode
supportflags.23?trueWhether this is an official support user
scamflags.24?trueThis may be a scam user
apply_min_photoflags.25?trueIf set, the profile picture for this user should be refetched
fakeflags.26?trueIf set, this user was reported by many users as a fake or scam user: be careful when interacting with them.
idlongID of the user
access_hashflags.0?longAccess hash of the user
first_nameflags.1?stringFirst name
last_nameflags.2?stringLast name
usernameflags.3?stringUsername
phoneflags.4?stringPhone number
photoflags.5?UserProfilePhotoProfile picture of user
statusflags.6?UserStatusOnline status of user
bot_info_versionflags.14?intVersion of the bot_info field in userFull, incremented every time it changes
restriction_reasonflags.18?Vector<RestrictionReason>Contains the reason why access to this user must be restricted.
bot_inline_placeholderflags.19?stringInline placeholder for this inline bot
lang_codeflags.22?stringLanguage code of the user
+

Type

+

User

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

userFull

+

Extended user info

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userEmpty.html b/data/corefork.telegram.org/constructor/userEmpty.html new file mode 100644 index 0000000000..c4c7b13752 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userEmpty.html @@ -0,0 +1,147 @@ + + + + + userEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

userEmpty

+ +

Empty constructor, non-existent user.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongUser identifier or 0
+

Type

+

User

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userFull.html b/data/corefork.telegram.org/constructor/userFull.html new file mode 100644 index 0000000000..e6d04d9e6f --- /dev/null +++ b/data/corefork.telegram.org/constructor/userFull.html @@ -0,0 +1,239 @@ + + + + + userFull + + + + + + + + + + + + + +
+ +
+
+
+ +

userFull

+ +

Extended user info

+

+ +
+
userFull#cf366521 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 id:long 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 private_forward_name:flags.16?string = UserFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
blockedflags.0?trueWhether you have blocked this user
phone_calls_availableflags.4?trueWhether this user can make VoIP calls
phone_calls_privateflags.5?trueWhether this user's privacy settings allow you to call him
can_pin_messageflags.7?trueWhether you can pin messages in the chat with this user, you can do this only for a chat with yourself
has_scheduledflags.12?trueWhether scheduled messages are available
video_calls_availableflags.13?trueWhether the user can receive video calls
userUserRemaining user info
aboutflags.1?stringBio of the user
settingsPeerSettingsPeer settings
profile_photoflags.2?PhotoProfile photo
notify_settingsPeerNotifySettingsNotification settings
bot_infoflags.3?BotInfoFor bots, info about the bot (bot commands, etc)
pinned_msg_idflags.6?intMessage ID of the last pinned message
common_chats_countintChats in common with this user
folder_idflags.11?intPeer folder ID, for more info click here
ttl_periodflags.14?intTime To Live of all messages in this chat; once a message is this many seconds old, it must be deleted.
theme_emoticonflags.15?stringEmoji associated with chat theme
+

Type

+

UserFull

+

Related pages

+

Scheduled messages

+

Telegram allows scheduling messages

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userProfilePhoto.html b/data/corefork.telegram.org/constructor/userProfilePhoto.html new file mode 100644 index 0000000000..9ed7f99b43 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userProfilePhoto.html @@ -0,0 +1,172 @@ + + + + + userProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

userProfilePhoto

+ +

User profile photo.

+

+ +
+
userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether an animated profile picture is available for this user
photo_idlongIdentifier of the respective photo
Parameter added in Layer 2
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC ID where the photo is stored
+

Type

+

UserProfilePhoto

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html b/data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html new file mode 100644 index 0000000000..61cd09f0f8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + userProfilePhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

userProfilePhotoEmpty

+ +

Profile photo has not been set, or was hidden.

+

+ +
+
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserProfilePhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userStatusEmpty.html b/data/corefork.telegram.org/constructor/userStatusEmpty.html new file mode 100644 index 0000000000..4b592e40a9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userStatusEmpty.html @@ -0,0 +1,132 @@ + + + + + userStatusEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusEmpty

+ +

User status has not been set yet.

+

+ +
+
userStatusEmpty#9d05049 = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userStatusLastMonth.html b/data/corefork.telegram.org/constructor/userStatusLastMonth.html new file mode 100644 index 0000000000..ac94095ee4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userStatusLastMonth.html @@ -0,0 +1,132 @@ + + + + + userStatusLastMonth + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusLastMonth

+ +

Online status: last seen last month

+

+ +
+
userStatusLastMonth#77ebc742 = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userStatusLastWeek.html b/data/corefork.telegram.org/constructor/userStatusLastWeek.html new file mode 100644 index 0000000000..6f1ae2e946 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userStatusLastWeek.html @@ -0,0 +1,132 @@ + + + + + userStatusLastWeek + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusLastWeek

+ +

Online status: last seen last week

+

+ +
+
userStatusLastWeek#7bf09fc = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userStatusOffline.html b/data/corefork.telegram.org/constructor/userStatusOffline.html new file mode 100644 index 0000000000..3568dbe334 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userStatusOffline.html @@ -0,0 +1,147 @@ + + + + + userStatusOffline + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusOffline

+ +

The user's offline status.

+

+ +
+
userStatusOffline#8c703f was_online:int = UserStatus;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
was_onlineintTime the user was last seen online
+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userStatusOnline.html b/data/corefork.telegram.org/constructor/userStatusOnline.html new file mode 100644 index 0000000000..2fed25eb36 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userStatusOnline.html @@ -0,0 +1,147 @@ + + + + + userStatusOnline + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusOnline

+ +

Online status of the user.

+

+ +
+
userStatusOnline#edb93949 expires:int = UserStatus;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintTime to expiration of the current online status
+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userStatusRecently.html b/data/corefork.telegram.org/constructor/userStatusRecently.html new file mode 100644 index 0000000000..23b3d893cd --- /dev/null +++ b/data/corefork.telegram.org/constructor/userStatusRecently.html @@ -0,0 +1,132 @@ + + + + + userStatusRecently + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusRecently

+ +

Online status: last seen recently

+

+ +
+
userStatusRecently#e26f42f1 = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/users.userFull b/data/corefork.telegram.org/constructor/users.userFull new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/constructor/users.userFull @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/vector.html b/data/corefork.telegram.org/constructor/vector.html new file mode 100644 index 0000000000..0a2519e1aa --- /dev/null +++ b/data/corefork.telegram.org/constructor/vector.html @@ -0,0 +1,134 @@ + + + + + vector + + + + + + + + + + + + + +
+ +
+
+
+ +

vector

+ +

A universal vector constructor.

+

+ +
+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Vector t

+

Params additional

+

For serialization write the constructor id 0x1cb5c415:int, then the number of vector elements - #:int, then, one after another, the # of the elements of the type t, that was implicitly passed to the constructor.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/wallPaper.html b/data/corefork.telegram.org/constructor/wallPaper.html new file mode 100644 index 0000000000..b8bf00b776 --- /dev/null +++ b/data/corefork.telegram.org/constructor/wallPaper.html @@ -0,0 +1,192 @@ + + + + + wallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaper

+ +

Wallpaper settings.

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongIdentifier
flags#Flags, see TL conditional fields
creatorflags.0?trueCreator of the wallpaper
defaultflags.1?trueWhether this is the default wallpaper
patternflags.3?truePattern
darkflags.4?trueDark mode
access_hashlongAccess hash
slugstringUnique wallpaper ID
documentDocumentThe actual wallpaper
settingsflags.2?WallPaperSettingsWallpaper settings
+

Type

+

WallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/wallPaperNoFile.html b/data/corefork.telegram.org/constructor/wallPaperNoFile.html new file mode 100644 index 0000000000..f4c50fc753 --- /dev/null +++ b/data/corefork.telegram.org/constructor/wallPaperNoFile.html @@ -0,0 +1,171 @@ + + + + + wallPaperNoFile + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaperNoFile

+ +

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.
+Also used for some default wallpapers which contain only colours.

+

+ +
+
wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongWallpaper ID
flags#Flags, see TL conditional fields
defaultflags.1?trueWhether this is the default wallpaper
darkflags.4?trueDark mode
settingsflags.2?WallPaperSettingsWallpaper settings
+

Type

+

WallPaper

+

Related pages

+

account.saveWallPaper

+

Install/uninstall wallpaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/wallPaperSettings.html b/data/corefork.telegram.org/constructor/wallPaperSettings.html new file mode 100644 index 0000000000..c99e22f147 --- /dev/null +++ b/data/corefork.telegram.org/constructor/wallPaperSettings.html @@ -0,0 +1,187 @@ + + + + + wallPaperSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaperSettings

+ +

Wallpaper settings

+

+ +
+
wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
blurflags.1?trueIf set, the wallpaper must be downscaled to fit in 450x450 square and then box-blurred with radius 12
motionflags.2?trueIf set, the background needs to be slightly moved when device is rotated
background_colorflags.0?intIf set, a PNG pattern is to be combined with the color chosen by the user: the main color of the background in RGB24 format
second_background_colorflags.4?intIf set, a PNG pattern is to be combined with the first and second background colors (RGB24 format) in a top-bottom gradient
third_background_colorflags.5?intIf set, a PNG pattern is to be combined with the first, second and third background colors (RGB24 format) in a freeform gradient
fourth_background_colorflags.6?intIf set, a PNG pattern is to be combined with the first, second, third and fourth background colors (RGB24 format) in a freeform gradient
intensityflags.3?intIntensity of the pattern when it is shown above the main background color, 0-100
rotationflags.4?intClockwise rotation angle of the gradient, in degrees; 0-359. Should be always divisible by 45
+

Type

+

WallPaperSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/wallPaperSolid.html b/data/corefork.telegram.org/constructor/wallPaperSolid.html new file mode 100644 index 0000000000..6c613bc43f --- /dev/null +++ b/data/corefork.telegram.org/constructor/wallPaperSolid.html @@ -0,0 +1,162 @@ + + + + + wallPaperSolid + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaperSolid

+ +

One-color background wallpaper (no image).

+

+ +
+
Constructor schema is available as of layer 93. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintIdentifier
titlestringName
bg_colorintBackground color (RGB)
colorintBasic background color (RGB)
+

Type

+

WallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webAuthorization.html b/data/corefork.telegram.org/constructor/webAuthorization.html new file mode 100644 index 0000000000..0a8120dcd7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/webAuthorization.html @@ -0,0 +1,189 @@ + + + + + webAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

webAuthorization

+ +

Represents a bot logged in using the Telegram login widget

+

+ +
+
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongAuthorization hash
bot_idlongBot ID
domainstringThe domain name of the website on which the user has logged in.
browserstringBrowser user-agent
platformstringPlatform
date_createdintWhen was the web session created
date_activeintWhen was the web session last active
ipstringIP address
regionstringRegion, determined from IP address
+

Type

+

WebAuthorization

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webDocument.html b/data/corefork.telegram.org/constructor/webDocument.html new file mode 100644 index 0000000000..d9a5e3bf37 --- /dev/null +++ b/data/corefork.telegram.org/constructor/webDocument.html @@ -0,0 +1,167 @@ + + + + + webDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

webDocument

+ +

Remote document

+

+ +
+
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringDocument URL
access_hashlongAccess hash
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
+

Type

+

WebDocument

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webDocumentNoProxy.html b/data/corefork.telegram.org/constructor/webDocumentNoProxy.html new file mode 100644 index 0000000000..02ca7a8dec --- /dev/null +++ b/data/corefork.telegram.org/constructor/webDocumentNoProxy.html @@ -0,0 +1,165 @@ + + + + + webDocumentNoProxy + + + + + + + + + + + + + +
+ +
+
+
+ +

webDocumentNoProxy

+ +

Remote document that can be downloaded without proxying through telegram

+

+ +
+
webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringDocument URL
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
+

Type

+

WebDocument

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webPage.html b/data/corefork.telegram.org/constructor/webPage.html new file mode 100644 index 0000000000..8bda165818 --- /dev/null +++ b/data/corefork.telegram.org/constructor/webPage.html @@ -0,0 +1,240 @@ + + + + + webPage + + + + + + + + + + + + + +
+ +
+
+
+ +

webPage

+ +

Webpage preview

+

+ +
+
webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idlongPreview ID
urlstringURL of previewed webpage
display_urlstringWebpage URL to be displayed to the user
hashintHash for pagination, for more info click here
typeflags.0?stringType of the web page. Can be: article, photo, audio, video, document, profile, app, or something else
site_nameflags.1?stringShort name of the site (e.g., Google Docs, App Store)
titleflags.2?stringTitle of the content
descriptionflags.3?stringContent description
photoflags.4?PhotoImage representing the content
embed_urlflags.5?stringURL to show in the embedded preview
embed_typeflags.5?stringMIME type of the embedded preview, (e.g., text/html or video/mp4)
embed_widthflags.6?intWidth of the embedded preview
embed_heightflags.6?intHeight of the embedded preview
durationflags.7?intDuration of the content, in seconds
authorflags.8?stringAuthor of the content
documentflags.9?DocumentPreview of the content as a media file
cached_pageflags.10?PagePage contents in instant view format
attributesflags.12?Vector<WebPageAttribute>Webpage attributes
+

Type

+

WebPage

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webPageAttributeTheme.html b/data/corefork.telegram.org/constructor/webPageAttributeTheme.html new file mode 100644 index 0000000000..27e57ed11f --- /dev/null +++ b/data/corefork.telegram.org/constructor/webPageAttributeTheme.html @@ -0,0 +1,157 @@ + + + + + webPageAttributeTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

webPageAttributeTheme

+ +

Page theme

+

+ +
+
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
documentsflags.0?Vector<Document>Theme files
settingsflags.1?ThemeSettingsTheme settings
+

Type

+

WebPageAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webPageEmpty.html b/data/corefork.telegram.org/constructor/webPageEmpty.html new file mode 100644 index 0000000000..662fad3eb6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/webPageEmpty.html @@ -0,0 +1,147 @@ + + + + + webPageEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

webPageEmpty

+ +

No preview is available for the webpage

+

+ +
+
webPageEmpty#eb1477e8 id:long = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongPreview ID
+

Type

+

WebPage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webPageNotModified.html b/data/corefork.telegram.org/constructor/webPageNotModified.html new file mode 100644 index 0000000000..b2cc5c9378 --- /dev/null +++ b/data/corefork.telegram.org/constructor/webPageNotModified.html @@ -0,0 +1,152 @@ + + + + + webPageNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

webPageNotModified

+ +

The preview of the webpage hasn't changed

+

+ +
+
webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
cached_page_viewsflags.0?intPage view count
+

Type

+

WebPage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webPagePending.html b/data/corefork.telegram.org/constructor/webPagePending.html new file mode 100644 index 0000000000..04cf3e4f45 --- /dev/null +++ b/data/corefork.telegram.org/constructor/webPagePending.html @@ -0,0 +1,152 @@ + + + + + webPagePending + + + + + + + + + + + + + +
+ +
+
+
+ +

webPagePending

+ +

A preview of the webpage is currently being generated

+

+ +
+
webPagePending#c586da1c id:long date:int = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID of preview
dateintWhen was the processing started
+

Type

+

WebPage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/getProxyConfig.html b/data/corefork.telegram.org/getProxyConfig.html new file mode 100644 index 0000000000..7238f2dd28 --- /dev/null +++ b/data/corefork.telegram.org/getProxyConfig.html @@ -0,0 +1,24 @@ +# force_probability 10 10 +default 2; +proxy_for 1 149.154.X.X:8888; +proxy_for -1 149.154.X.X:8888; +proxy_for 2 149.154.X.X:8888; +proxy_for -2 149.154.X.X:8888; +proxy_for 3 149.154.X.X:8888; +proxy_for -3 149.154.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for -4 149.154.X.X:8888; +proxy_for -4 149.154.X.X:8888; +proxy_for 5 91.108.X.X:8888; +proxy_for 5 91.108.X.X:8888; +proxy_for -5 91.108.X.X:8888; +proxy_for -5 91.108.X.X:8888; diff --git a/data/corefork.telegram.org/import-stickers.html b/data/corefork.telegram.org/import-stickers.html new file mode 100644 index 0000000000..0daae5650c --- /dev/null +++ b/data/corefork.telegram.org/import-stickers.html @@ -0,0 +1,159 @@ + + + + + Importing Stickers to Telegram + + + + + + + + + + + + + +
+ +
+
+
+
+

Importing Stickers to Telegram

+ +

The easiest way to create stickers on Telegram is to simply upload them using the @stickers bot. This bot can help you upload new stickers, create sticker packs and get usage stats for your stickers and packs.

+

Telegram also offers a platform for developers of apps that help users make their own stickers. For example, apps that allow people to upload pictures of themselves and turn them into stickers.

+

Who is this for?

+

USE this:

+
    +
  • To help people make their own unique custom stickers.
  • +
  • To help people migrate their unique custom stickers they created from another platform.
  • +
+

DON'T use this:

+ +

In short, if a set of stickers is already available on Telegram – there's no need to import it!

+

Sticker Importing Apps

+

As of version 7.8, Telegram apps support a simple API for importing stickers.

+
+ +
+ +
+

WARNING: Each time a user imports stickers, a new sticker pack is created on Telegram. Do not use the importing feature to share stickers you made with other users. If you want to share your stickers, simply upload them using @stickers and share the link of your pack. For example, here's a link to install some Duck Stickers.

+
+

Importing SDKs

+

We have created libraries and sample apps for iOS and Android which you can use to implement importing stickers to Telegram from your app.

+

Sticker Formats

+

Telegram apps support two sticker types. Regardless of the type, each sticker must be associated with at least one emoji that expresses the emotion corresponding to the sticker.

+

Animated Stickers

+

Must be in TGS format, created using the Bodymovin-TG plugin for Adobe After Effects.

+
+

Note: Animated .WEBP is NOT currently supported, only static .WEBP is supported for static stickers. Animated stickers must be in .TGS format. You can also import .WEBM video stickers.

+
+

Max. size: 64 KB
Dimensions: 512x512 px
FPS: 30-60 FPS
Max. duration: 3 seconds

+
+

For full technical details on Telegram animated stickers, see this page.

+
+

Video Stickers

+

Must be in WEBM format with VP9 and alpha channel encoding (transparency is a temporary requirement).

+

Max. size: 256 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.
FPS: 30
Max. duration: 3 seconds

+

Static Stickers

+

Must be in PNG or WEBP format with a transparent layer. All static stickers should use white stroke and shadow, exactly like in this example: StickerExample.psd

+

Max. size: 512 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.acceptAuthorization b/data/corefork.telegram.org/method/account.acceptAuthorization new file mode 100644 index 0000000000..116393e579 --- /dev/null +++ b/data/corefork.telegram.org/method/account.acceptAuthorization @@ -0,0 +1,170 @@ + + + + + account.acceptAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

account.acceptAuthorization

+ +

Sends a Telegram Passport authorization form, effectively sharing data with the service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
bot_idlongBot ID
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
value_hashesVector<SecureValueHash>Types of values sent and their hashes
credentialsSecureCredentialsEncryptedEncrypted values
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.cancelPasswordEmail b/data/corefork.telegram.org/method/account.cancelPasswordEmail new file mode 100644 index 0000000000..07c485d144 --- /dev/null +++ b/data/corefork.telegram.org/method/account.cancelPasswordEmail @@ -0,0 +1,138 @@ + + + + + account.cancelPasswordEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.cancelPasswordEmail

+ +

Cancel the code that was sent to verify an email to use as 2FA recovery method.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.cancelPasswordEmail#c1cbd5b6 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.changeAuthorizationSettings b/data/corefork.telegram.org/method/account.changeAuthorizationSettings new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/account.changeAuthorizationSettings @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.changePhone b/data/corefork.telegram.org/method/account.changePhone new file mode 100644 index 0000000000..37722b2281 --- /dev/null +++ b/data/corefork.telegram.org/method/account.changePhone @@ -0,0 +1,190 @@ + + + + + account.changePhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.changePhone

+ +

Change the phone number of the current account

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringNew phone number
phone_code_hashstringPhone code hash received when calling account.sendChangePhoneCode
phone_codestringPhone code received when calling account.sendChangePhoneCode
+

Result

+

User

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
+

Related pages

+

account.sendChangePhoneCode

+

Verify a new phone number to associate to the current account

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.checkUsername b/data/corefork.telegram.org/method/account.checkUsername new file mode 100644 index 0000000000..02baa76e54 --- /dev/null +++ b/data/corefork.telegram.org/method/account.checkUsername @@ -0,0 +1,167 @@ + + + + + account.checkUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

account.checkUsername

+ +

Validates a username and checks availability.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.checkUsername#2714d86c username:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usernamestringusername
Accepted characters: A-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
+

Result

+

Return Bool result on whether the passed username can be used.

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USERNAME_INVALIDUnacceptable username.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.confirmPasswordEmail b/data/corefork.telegram.org/method/account.confirmPasswordEmail new file mode 100644 index 0000000000..7f7276b59f --- /dev/null +++ b/data/corefork.telegram.org/method/account.confirmPasswordEmail @@ -0,0 +1,175 @@ + + + + + account.confirmPasswordEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.confirmPasswordEmail

+ +

Verify an email to use as 2FA recovery method.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.confirmPasswordEmail#8fdf1920 code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
codestringThe phone code that was received after setting a recovery email
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_INVALIDCode invalid.
400EMAIL_HASH_EXPIREDEmail hash expired.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.confirmPhone b/data/corefork.telegram.org/method/account.confirmPhone new file mode 100644 index 0000000000..d1e48ffedf --- /dev/null +++ b/data/corefork.telegram.org/method/account.confirmPhone @@ -0,0 +1,180 @@ + + + + + account.confirmPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.confirmPhone

+ +

Confirm a phone number to cancel account deletion, for more info click here »

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_code_hashstringPhone code hash, for more info click here »
phone_codestringSMS code, for more info click here »
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_HASH_INVALIDCode hash invalid.
400PHONE_CODE_EMPTYphone_code is missing.
+

Related pages

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.createTheme b/data/corefork.telegram.org/method/account.createTheme new file mode 100644 index 0000000000..18a88bc4da --- /dev/null +++ b/data/corefork.telegram.org/method/account.createTheme @@ -0,0 +1,186 @@ + + + + + account.createTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.createTheme

+ +

Create a theme

+

+ +
+
theme#a00e67d6 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?Vector<ThemeSettings> emoticon:flags.6?string installs_count:flags.4?int = Theme;
+---functions---
+account.createTheme#652e4400 flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?Vector<InputThemeSettings> = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
slugstringUnique theme ID
titlestringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
+

Result

+

Theme

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_MIME_INVALIDThe theme's MIME type is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.declinePasswordReset b/data/corefork.telegram.org/method/account.declinePasswordReset new file mode 100644 index 0000000000..9c682fe9ac --- /dev/null +++ b/data/corefork.telegram.org/method/account.declinePasswordReset @@ -0,0 +1,155 @@ + + + + + account.declinePasswordReset + + + + + + + + + + + + + +
+ +
+
+
+ +

account.declinePasswordReset

+ +

Abort a pending 2FA password reset, see here for more info »

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.declinePasswordReset#4c9409f6 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400RESET_REQUEST_MISSINGNo password reset is in progress.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.deleteAccount b/data/corefork.telegram.org/method/account.deleteAccount new file mode 100644 index 0000000000..68e5e921d4 --- /dev/null +++ b/data/corefork.telegram.org/method/account.deleteAccount @@ -0,0 +1,170 @@ + + + + + account.deleteAccount + + + + + + + + + + + + + +
+ +
+
+
+ +

account.deleteAccount

+ +

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.deleteAccount#418d4e0b reason:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
reasonstringWhy is the account being deleted, can be empty
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
4202FA_CONFIRM_WAIT_XSince this account is active and protected by a 2FA password, we will delete it in 1 week for security purposes. You can cancel this process at any time, you'll be able to reset your account in X seconds.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.finishTakeoutSession b/data/corefork.telegram.org/method/account.finishTakeoutSession new file mode 100644 index 0000000000..72ee9aeb0e --- /dev/null +++ b/data/corefork.telegram.org/method/account.finishTakeoutSession @@ -0,0 +1,172 @@ + + + + + account.finishTakeoutSession + + + + + + + + + + + + + +
+ +
+
+
+ +

account.finishTakeoutSession

+ +

Finish account takeout session

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.0?trueData exported successfully
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getAccountTTL b/data/corefork.telegram.org/method/account.getAccountTTL new file mode 100644 index 0000000000..09a921a856 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getAccountTTL @@ -0,0 +1,134 @@ + + + + + account.getAccountTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAccountTTL

+ +

Get days to live of account

+

+ +
+
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+---functions---
+account.getAccountTTL#8fc711d = AccountDaysTTL;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

AccountDaysTTL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getAllSecureValues b/data/corefork.telegram.org/method/account.getAllSecureValues new file mode 100644 index 0000000000..e63f235e4d --- /dev/null +++ b/data/corefork.telegram.org/method/account.getAllSecureValues @@ -0,0 +1,136 @@ + + + + + account.getAllSecureValues + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAllSecureValues

+ +

Get all saved Telegram Passport documents, for more info see the passport docs »

+

+ +
+
---functions---
+account.getAllSecureValues#b288bc7d = Vector<SecureValue>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<SecureValue>

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getAuthorizationForm b/data/corefork.telegram.org/method/account.getAuthorizationForm new file mode 100644 index 0000000000..8684c2477a --- /dev/null +++ b/data/corefork.telegram.org/method/account.getAuthorizationForm @@ -0,0 +1,176 @@ + + + + + account.getAuthorizationForm + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAuthorizationForm

+ +

Returns a Telegram Passport authorization form for sharing data with a service

+

+ +
+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+---functions---
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
bot_idlongUser identifier of the service's bot
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
+

Result

+

account.AuthorizationForm

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PUBLIC_KEY_REQUIREDA public key is required.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getAuthorizations b/data/corefork.telegram.org/method/account.getAuthorizations new file mode 100644 index 0000000000..45b8e5a9f7 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getAuthorizations @@ -0,0 +1,134 @@ + + + + + account.getAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAuthorizations

+ +

Get logged-in sessions

+

+ +
+
account.authorizations#4bff8ea0 authorization_ttl_days:int authorizations:Vector<Authorization> = account.Authorizations;
+---functions---
+account.getAuthorizations#e320c158 = account.Authorizations;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.Authorizations

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getAutoDownloadSettings b/data/corefork.telegram.org/method/account.getAutoDownloadSettings new file mode 100644 index 0000000000..e3c5afa314 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getAutoDownloadSettings @@ -0,0 +1,134 @@ + + + + + account.getAutoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAutoDownloadSettings

+ +

Get media autodownload settings

+

+ +
+
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
+---functions---
+account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.AutoDownloadSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getChatThemes b/data/corefork.telegram.org/method/account.getChatThemes new file mode 100644 index 0000000000..0d553b5f1a --- /dev/null +++ b/data/corefork.telegram.org/method/account.getChatThemes @@ -0,0 +1,153 @@ + + + + + account.getChatThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getChatThemes

+ +

Get all available chat themes

+

+ +
+
account.themesNotModified#f41eb622 = account.Themes;
+account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
+---functions---
+account.getChatThemes#d638de89 hash:long = account.Themes;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
+

Result

+

account.ChatThemes

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getContactSignUpNotification b/data/corefork.telegram.org/method/account.getContactSignUpNotification new file mode 100644 index 0000000000..9de8f4bde0 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getContactSignUpNotification @@ -0,0 +1,135 @@ + + + + + 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.getContentSettings b/data/corefork.telegram.org/method/account.getContentSettings new file mode 100644 index 0000000000..9213a4314a --- /dev/null +++ b/data/corefork.telegram.org/method/account.getContentSettings @@ -0,0 +1,134 @@ + + + + + account.getContentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getContentSettings

+ +

Get sensitive content settings

+

+ +
+
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
+---functions---
+account.getContentSettings#8b9b4dae = account.ContentSettings;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.ContentSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getGlobalPrivacySettings b/data/corefork.telegram.org/method/account.getGlobalPrivacySettings new file mode 100644 index 0000000000..9e02de83c9 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getGlobalPrivacySettings @@ -0,0 +1,134 @@ + + + + + account.getGlobalPrivacySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getGlobalPrivacySettings

+ +

Get global privacy settings

+

+ +
+
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
+---functions---
+account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

GlobalPrivacySettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getMultiWallPapers b/data/corefork.telegram.org/method/account.getMultiWallPapers new file mode 100644 index 0000000000..9281752e0b --- /dev/null +++ b/data/corefork.telegram.org/method/account.getMultiWallPapers @@ -0,0 +1,148 @@ + + + + + account.getMultiWallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getMultiWallPapers

+ +

Get info about multiple wallpapers

+

+ +
+
---functions---
+account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
wallpapersVector<InputWallPaper>Wallpapers to fetch info about
+

Result

+

Vector<WallPaper>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getNotifyExceptions b/data/corefork.telegram.org/method/account.getNotifyExceptions new file mode 100644 index 0000000000..82599237b6 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getNotifyExceptions @@ -0,0 +1,165 @@ + + + + + account.getNotifyExceptions + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getNotifyExceptions

+ +

Returns list of chats with non-default notification settings

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
compare_soundflags.1?trueIf true, chats with non-default sound will also be returned
peerflags.0?InputNotifyPeerIf specified, only chats of the specified category will be returned
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getNotifySettings b/data/corefork.telegram.org/method/account.getNotifySettings new file mode 100644 index 0000000000..2a207f960d --- /dev/null +++ b/data/corefork.telegram.org/method/account.getNotifySettings @@ -0,0 +1,166 @@ + + + + + account.getNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getNotifySettings

+ +

Gets current notification settings for a given user/group, from all users/all groups.

+

+ +
+
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
+---functions---
+account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputNotifyPeerNotification source
+

Result

+

Returns a PeerNotifySettings object containing current notification settings.

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getPassword b/data/corefork.telegram.org/method/account.getPassword new file mode 100644 index 0000000000..be9b1e22c4 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getPassword @@ -0,0 +1,134 @@ + + + + + account.getPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getPassword

+ +

Obtain configuration for two-factor authorization with password

+

+ +
+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+---functions---
+account.getPassword#548a30f5 = account.Password;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.Password

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getPrivacy b/data/corefork.telegram.org/method/account.getPrivacy new file mode 100644 index 0000000000..92ade0de61 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getPrivacy @@ -0,0 +1,166 @@ + + + + + account.getPrivacy + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getPrivacy

+ +

Get privacy settings of current account

+

+ +
+
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+---functions---
+account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
keyInputPrivacyKeyPeer category whose privacy settings should be fetched
+

Result

+

account.PrivacyRules

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getSecureValue b/data/corefork.telegram.org/method/account.getSecureValue new file mode 100644 index 0000000000..79747cdb96 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getSecureValue @@ -0,0 +1,151 @@ + + + + + account.getSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getSecureValue

+ +

Get saved Telegram Passport document, for more info see the passport docs »

+

+ +
+
---functions---
+account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typesVector<SecureValueType>Requested value types
+

Result

+

Vector<SecureValue>

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getTheme b/data/corefork.telegram.org/method/account.getTheme new file mode 100644 index 0000000000..a5ae604005 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getTheme @@ -0,0 +1,181 @@ + + + + + account.getTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getTheme

+ +

Get theme information

+

+ +
+
theme#a00e67d6 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?Vector<ThemeSettings> emoticon:flags.6?string installs_count:flags.4?int = Theme;
+---functions---
+account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme
document_idlongDocument ID
+

Result

+

Theme

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_FORMAT_INVALIDInvalid theme format provided.
400THEME_INVALIDInvalid theme provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getThemes b/data/corefork.telegram.org/method/account.getThemes new file mode 100644 index 0000000000..bf95c11f01 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getThemes @@ -0,0 +1,158 @@ + + + + + account.getThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getThemes

+ +

Get installed themes

+

+ +
+
account.themesNotModified#f41eb622 = account.Themes;
+account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
+---functions---
+account.getThemes#7206e458 format:string hash:long = account.Themes;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
formatstringTheme format, a string that identifies the theming engines supported by the client
hashlongHash for pagination, for more info click here
+

Result

+

account.Themes

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getTmpPassword b/data/corefork.telegram.org/method/account.getTmpPassword new file mode 100644 index 0000000000..7c90d0dbc0 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getTmpPassword @@ -0,0 +1,176 @@ + + + + + account.getTmpPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getTmpPassword

+ +

Get temporary payment password

+

+ +
+
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+---functions---
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPSRP password parameters
periodintTime during which the temporary password will be valid, in seconds; should be between 60 and 86400
+

Result

+

account.TmpPassword

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400TMP_PASSWORD_DISABLEDThe temporary password is disabled.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getWallPaper b/data/corefork.telegram.org/method/account.getWallPaper new file mode 100644 index 0000000000..194e916328 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getWallPaper @@ -0,0 +1,167 @@ + + + + + account.getWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getWallPaper

+ +

Get info about a certain wallpaper

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
+---functions---
+account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
wallpaperInputWallPaperThe wallpaper to get info about
+

Result

+

WallPaper

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getWallPapers b/data/corefork.telegram.org/method/account.getWallPapers new file mode 100644 index 0000000000..2c4c1b7338 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getWallPapers @@ -0,0 +1,153 @@ + + + + + account.getWallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getWallPapers

+ +

Returns a list of available wallpapers.

+

+ +
+
account.wallPapersNotModified#1c199183 = account.WallPapers;
+account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+---functions---
+account.getWallPapers#7967d36 hash:long = account.WallPapers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

Vector<WallPaper>

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getWebAuthorizations b/data/corefork.telegram.org/method/account.getWebAuthorizations new file mode 100644 index 0000000000..10717f0fa2 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getWebAuthorizations @@ -0,0 +1,136 @@ + + + + + account.getWebAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getWebAuthorizations

+ +

Get web login widget authorizations

+

+ +
+
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
+---functions---
+account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.WebAuthorizations

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.initTakeoutSession b/data/corefork.telegram.org/method/account.initTakeoutSession new file mode 100644 index 0000000000..bb18dc66d8 --- /dev/null +++ b/data/corefork.telegram.org/method/account.initTakeoutSession @@ -0,0 +1,204 @@ + + + + + account.initTakeoutSession + + + + + + + + + + + + + +
+ +
+
+
+ +

account.initTakeoutSession

+ +

Initialize account takeout session

+

+ +
+
account.takeout#4dba4501 id:long = account.Takeout;
+---functions---
+account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to export contacts
message_usersflags.1?trueWhether to export messages in private chats
message_chatsflags.2?trueWhether to export messages in legacy groups
message_megagroupsflags.3?trueWhether to export messages in supergroups
message_channelsflags.4?trueWhether to export messages in channels
filesflags.5?trueWhether to export files
file_max_sizeflags.5?intMaximum size of files to export
+

Result

+

account.Takeout

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
420TAKEOUT_INIT_DELAY_XWait X seconds before initing takeout.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.installTheme b/data/corefork.telegram.org/method/account.installTheme new file mode 100644 index 0000000000..0b8df44fe4 --- /dev/null +++ b/data/corefork.telegram.org/method/account.installTheme @@ -0,0 +1,165 @@ + + + + + account.installTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.installTheme

+ +

Install a theme

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.installTheme#c727bb3b flags:# dark:flags.0?true theme:flags.1?InputTheme format:flags.2?string base_theme:flags.3?BaseTheme = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to install the dark version
formatflags.1?stringTheme format, a string that identifies the theming engines supported by the client
themeflags.1?InputThemeTheme to install
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.installWallPaper b/data/corefork.telegram.org/method/account.installWallPaper new file mode 100644 index 0000000000..2078e85b7e --- /dev/null +++ b/data/corefork.telegram.org/method/account.installWallPaper @@ -0,0 +1,172 @@ + + + + + account.installWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.installWallPaper

+ +

Install wallpaper

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
wallpaperInputWallPaperWallpaper to install
settingsWallPaperSettingsWallpaper settings
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.registerDevice b/data/corefork.telegram.org/method/account.registerDevice new file mode 100644 index 0000000000..760b110d43 --- /dev/null +++ b/data/corefork.telegram.org/method/account.registerDevice @@ -0,0 +1,217 @@ + + + + + account.registerDevice + + + + + + + + + + + + + +
+ +
+
+
+ +

account.registerDevice

+ +

Register device to receive PUSH notifications

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_mutedflags.0?trueAvoid receiving (silent and invisible background) notifications. Useful to save battery.
token_typeintDevice token type.
Possible values:
1 - APNS (device token for apple push)
2 - FCM (firebase token for google firebase)
3 - MPNS (channel URI for microsoft push)
4 - Simple push (endpoint for firefox's simple push API)
5 - Ubuntu phone (token for ubuntu push)
6 - Blackberry (token for blackberry push)
7 - Unused
8 - WNS (windows push)
9 - APNS VoIP (token for apple push VoIP)
10 - Web push (web push, see below)
11 - MPNS VoIP (token for microsoft push VoIP)
12 - Tizen (token for tizen push)

For 10 web push, the token must be a JSON-encoded object containing the keys described in PUSH updates
tokenstringDevice token
app_sandboxBoolIf (boolTrue) is transmitted, a sandbox-certificate will be used during transmission.
secretbytesFor FCM and APNS VoIP, optional encryption key used to encrypt push notifications
other_uidsVector<long>List of user identifiers of other users currently using the client
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
400WEBPUSH_AUTH_INVALIDThe specified web push authentication secret is invalid.
400WEBPUSH_KEY_INVALIDThe specified web push elliptic curve Diffie-Hellman public key is invalid.
400WEBPUSH_TOKEN_INVALIDThe specified web push token is invalid.
+

Related pages

+

Handling PUSH-notifications

+

How to subscribe to and handle PUSH notifications

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.reportPeer b/data/corefork.telegram.org/method/account.reportPeer new file mode 100644 index 0000000000..4fb189e8fc --- /dev/null +++ b/data/corefork.telegram.org/method/account.reportPeer @@ -0,0 +1,182 @@ + + + + + account.reportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

account.reportPeer

+ +

Report a peer for violation of telegram's Terms of Service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer to report
reasonReportReasonThe reason why this peer is being reported
messagestringComment for report moderation
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.reportProfilePhoto b/data/corefork.telegram.org/method/account.reportProfilePhoto new file mode 100644 index 0000000000..95ef750d1a --- /dev/null +++ b/data/corefork.telegram.org/method/account.reportProfilePhoto @@ -0,0 +1,165 @@ + + + + + account.reportProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

account.reportProfilePhoto

+ +

Report a profile photo of a dialog

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
photo_idInputPhotoDialog photo ID
reasonReportReasonReport reason
messagestringComment for report moderation
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.resendPasswordEmail b/data/corefork.telegram.org/method/account.resendPasswordEmail new file mode 100644 index 0000000000..1d225d5990 --- /dev/null +++ b/data/corefork.telegram.org/method/account.resendPasswordEmail @@ -0,0 +1,138 @@ + + + + + account.resendPasswordEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resendPasswordEmail

+ +

Resend the code to verify an email to use as 2FA recovery method.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resendPasswordEmail#7a7f2a15 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.resetAuthorization b/data/corefork.telegram.org/method/account.resetAuthorization new file mode 100644 index 0000000000..eeee9171e0 --- /dev/null +++ b/data/corefork.telegram.org/method/account.resetAuthorization @@ -0,0 +1,175 @@ + + + + + account.resetAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetAuthorization

+ +

Log out an active authorized session by its hash

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetAuthorization#df77f3bc hash:long = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongSession hash
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
400HASH_INVALIDThe provided hash is invalid.
+

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.resetNotifySettings b/data/corefork.telegram.org/method/account.resetNotifySettings new file mode 100644 index 0000000000..327d22b0f0 --- /dev/null +++ b/data/corefork.telegram.org/method/account.resetNotifySettings @@ -0,0 +1,135 @@ + + + + + account.resetNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetNotifySettings

+ +

Resets all notification settings from users and groups.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetNotifySettings#db7e1747 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.resetPassword b/data/corefork.telegram.org/method/account.resetPassword new file mode 100644 index 0000000000..e48b31d259 --- /dev/null +++ b/data/corefork.telegram.org/method/account.resetPassword @@ -0,0 +1,139 @@ + + + + + account.resetPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPassword

+ +

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+---functions---
+account.resetPassword#9308ce1b = account.ResetPasswordResult;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.ResetPasswordResult

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.resetWallPapers b/data/corefork.telegram.org/method/account.resetWallPapers new file mode 100644 index 0000000000..77608715c7 --- /dev/null +++ b/data/corefork.telegram.org/method/account.resetWallPapers @@ -0,0 +1,135 @@ + + + + + account.resetWallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetWallPapers

+ +

Delete installed wallpapers

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetWallPapers#bb3b9804 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.resetWebAuthorization b/data/corefork.telegram.org/method/account.resetWebAuthorization new file mode 100644 index 0000000000..8e41385186 --- /dev/null +++ b/data/corefork.telegram.org/method/account.resetWebAuthorization @@ -0,0 +1,171 @@ + + + + + account.resetWebAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetWebAuthorization

+ +

Log out an active web telegram login session

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetWebAuthorization#2d01b9ef hash:long = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongSession hash
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
+

Related pages

+

webAuthorization

+

Represents a bot logged in using the Telegram login widget

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.resetWebAuthorizations b/data/corefork.telegram.org/method/account.resetWebAuthorizations new file mode 100644 index 0000000000..be5784be06 --- /dev/null +++ b/data/corefork.telegram.org/method/account.resetWebAuthorizations @@ -0,0 +1,137 @@ + + + + + account.resetWebAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetWebAuthorizations

+ +

Reset all active web telegram login sessions

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetWebAuthorizations#682d2594 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.saveAutoDownloadSettings b/data/corefork.telegram.org/method/account.saveAutoDownloadSettings new file mode 100644 index 0000000000..ec64d0f2b7 --- /dev/null +++ b/data/corefork.telegram.org/method/account.saveAutoDownloadSettings @@ -0,0 +1,166 @@ + + + + + account.saveAutoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.saveAutoDownloadSettings

+ +

Change media autodownload settings

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
lowflags.0?trueWhether to save media in the low data usage preset
highflags.1?trueWhether to save media in the high data usage preset
settingsAutoDownloadSettingsMedia autodownload settings
+

Result

+

Bool

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.saveSecureValue b/data/corefork.telegram.org/method/account.saveSecureValue new file mode 100644 index 0000000000..7f8c896617 --- /dev/null +++ b/data/corefork.telegram.org/method/account.saveSecureValue @@ -0,0 +1,174 @@ + + + + + account.saveSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

account.saveSecureValue

+ +

Securely save Telegram Passport document, for more info see the passport docs »

+

+ +
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+---functions---
+account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
valueInputSecureValueSecure value, for more info see the passport docs »
secure_secret_idlongPassport secret hash, for more info see the passport docs »
+

Result

+

SecureValue

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_REQUIREDA 2FA password must be configured to use Telegram Passport.
+

Related pages

+

Telegram Passport Encryption Details

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.sendChangePhoneCode b/data/corefork.telegram.org/method/account.sendChangePhoneCode new file mode 100644 index 0000000000..1d52080119 --- /dev/null +++ b/data/corefork.telegram.org/method/account.sendChangePhoneCode @@ -0,0 +1,186 @@ + + + + + account.sendChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendChangePhoneCode

+ +

Verify a new phone number to associate to the current account

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringNew phone number
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_CHANGE_PHONE_FORBIDDENYou can't change phone number right after logging in, please wait at least 24 hours.
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.sendConfirmPhoneCode b/data/corefork.telegram.org/method/account.sendConfirmPhoneCode new file mode 100644 index 0000000000..980ec43b80 --- /dev/null +++ b/data/corefork.telegram.org/method/account.sendConfirmPhoneCode @@ -0,0 +1,174 @@ + + + + + account.sendConfirmPhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendConfirmPhoneCode

+ +

Send confirmation code to cancel account deletion, for more info click here »

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashstringThe hash from the service notification, for more info click here »
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
+

Related pages

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.sendVerifyEmailCode b/data/corefork.telegram.org/method/account.sendVerifyEmailCode new file mode 100644 index 0000000000..abb8d7a986 --- /dev/null +++ b/data/corefork.telegram.org/method/account.sendVerifyEmailCode @@ -0,0 +1,168 @@ + + + + + account.sendVerifyEmailCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendVerifyEmailCode

+ +

Send the verification email code for telegram passport.

+

+ +
+
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
+---functions---
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emailstringThe email where to send the code
+

Result

+

account.SentEmailCode

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400EMAIL_INVALIDThe specified email is invalid.
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.sendVerifyPhoneCode b/data/corefork.telegram.org/method/account.sendVerifyPhoneCode new file mode 100644 index 0000000000..ff4553ccbc --- /dev/null +++ b/data/corefork.telegram.org/method/account.sendVerifyPhoneCode @@ -0,0 +1,173 @@ + + + + + account.sendVerifyPhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendVerifyPhoneCode

+ +

Send the verification phone code for telegram passport.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringThe phone number to verify
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDThe phone number is invalid.
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.setAccountTTL b/data/corefork.telegram.org/method/account.setAccountTTL new file mode 100644 index 0000000000..2c45277b8f --- /dev/null +++ b/data/corefork.telegram.org/method/account.setAccountTTL @@ -0,0 +1,167 @@ + + + + + account.setAccountTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setAccountTTL

+ +

Set account self-destruction period

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
ttlAccountDaysTTLTime to live in days
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TTL_DAYS_INVALIDThe provided TTL is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.setAuthorizationTTL b/data/corefork.telegram.org/method/account.setAuthorizationTTL new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/account.setAuthorizationTTL @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.setContactSignUpNotification b/data/corefork.telegram.org/method/account.setContactSignUpNotification new file mode 100644 index 0000000000..b338ae4ebf --- /dev/null +++ b/data/corefork.telegram.org/method/account.setContactSignUpNotification @@ -0,0 +1,150 @@ + + + + + account.setContactSignUpNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setContactSignUpNotification

+ +

Toggle contact sign up notifications

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
silentBoolWhether to disable contact sign up notifications
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.setContentSettings b/data/corefork.telegram.org/method/account.setContentSettings new file mode 100644 index 0000000000..e5c15d6c95 --- /dev/null +++ b/data/corefork.telegram.org/method/account.setContentSettings @@ -0,0 +1,172 @@ + + + + + account.setContentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setContentSettings

+ +

Set sensitive content settings (for viewing or hiding NSFW content)

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueEnable NSFW content
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403SENSITIVE_CHANGE_FORBIDDENYou can't change your sensitive content settings.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.setGlobalPrivacySettings b/data/corefork.telegram.org/method/account.setGlobalPrivacySettings new file mode 100644 index 0000000000..ef48d57b07 --- /dev/null +++ b/data/corefork.telegram.org/method/account.setGlobalPrivacySettings @@ -0,0 +1,166 @@ + + + + + account.setGlobalPrivacySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setGlobalPrivacySettings

+ +

Set global privacy settings

+

+ +
+
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
+---functions---
+account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
settingsGlobalPrivacySettingsGlobal privacy settings
+

Result

+

GlobalPrivacySettings

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTOARCHIVE_NOT_AVAILABLEThe autoarchive setting is not available at this time: please check the value of the autoarchive_setting_available field in client config » before calling this method.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.setPrivacy b/data/corefork.telegram.org/method/account.setPrivacy new file mode 100644 index 0000000000..0f21968d6d --- /dev/null +++ b/data/corefork.telegram.org/method/account.setPrivacy @@ -0,0 +1,181 @@ + + + + + account.setPrivacy + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setPrivacy

+ +

Change privacy settings of current account

+

+ +
+
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+---functions---
+account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keyInputPrivacyKeyPeers to which the privacy rules apply
rulesVector<InputPrivacyRule>New privacy rules
+

Result

+

account.PrivacyRules

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
400PRIVACY_TOO_LONGToo many privacy rules were specified, the current limit is 1000.
400PRIVACY_VALUE_INVALIDThe specified privacy rule combination is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.unregisterDevice b/data/corefork.telegram.org/method/account.unregisterDevice new file mode 100644 index 0000000000..4c847cdfc3 --- /dev/null +++ b/data/corefork.telegram.org/method/account.unregisterDevice @@ -0,0 +1,180 @@ + + + + + account.unregisterDevice + + + + + + + + + + + + + +
+ +
+
+
+ +

account.unregisterDevice

+ +

Deletes a device by its token, stops sending PUSH-notifications to it.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
token_typeintDevice token type.
Possible values:
1 - APNS (device token for apple push)
2 - FCM (firebase token for google firebase)
3 - MPNS (channel URI for microsoft push)
4 - Simple push (endpoint for firefox's simple push API)
5 - Ubuntu phone (token for ubuntu push)
6 - Blackberry (token for blackberry push)
7 - Unused
8 - WNS (windows push)
9 - APNS VoIP (token for apple push VoIP)
10 - Web push (web push, see below)
11 - MPNS VoIP (token for microsoft push VoIP)
12 - Tizen (token for tizen push)

For 10 web push, the token must be a JSON-encoded object containing the keys described in PUSH updates
tokenstringDevice token
other_uidsVector<long>List of user identifiers of other users currently using the client
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
+

Related pages

+

Handling PUSH-notifications

+

How to subscribe to and handle PUSH notifications

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.updateDeviceLocked b/data/corefork.telegram.org/method/account.updateDeviceLocked new file mode 100644 index 0000000000..aa782ee86d --- /dev/null +++ b/data/corefork.telegram.org/method/account.updateDeviceLocked @@ -0,0 +1,153 @@ + + + + + account.updateDeviceLocked + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateDeviceLocked

+ +

When client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updateDeviceLocked#38df3532 period:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
periodintInactivity period after which to start hiding message texts in PUSH notifications.
+

Result

+

Bool

+

Related pages

+

Handling PUSH-notifications

+

How to subscribe to and handle PUSH notifications

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.updateNotifySettings b/data/corefork.telegram.org/method/account.updateNotifySettings new file mode 100644 index 0000000000..ffc0dcd011 --- /dev/null +++ b/data/corefork.telegram.org/method/account.updateNotifySettings @@ -0,0 +1,192 @@ + + + + + account.updateNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateNotifySettings

+ +

Edits notification settings from a given user/group, from all users/all groups.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputNotifyPeerNotification source
settingsInputPeerNotifySettingsNotification settings
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400SETTINGS_INVALIDInvalid settings were provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.updatePasswordSettings b/data/corefork.telegram.org/method/account.updatePasswordSettings new file mode 100644 index 0000000000..601cf2c385 --- /dev/null +++ b/data/corefork.telegram.org/method/account.updatePasswordSettings @@ -0,0 +1,207 @@ + + + + + account.updatePasswordSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updatePasswordSettings

+ +

Set a new 2FA password

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPThe old password (see SRP)
new_settingsaccount.PasswordInputSettingsThe new password (see SRP)
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMAIL_UNCONFIRMEDEmail unconfirmed.
400EMAIL_UNCONFIRMED_XThe provided email isn't confirmed, X is the length of the verification code that was just sent to the email: use account.verifyEmail to enter the received verification code and enable the recovery email.
400NEW_SALT_INVALIDThe new salt is invalid.
400NEW_SETTINGS_INVALIDThe new password settings are invalid.
400PASSWORD_HASH_INVALIDThe old password hash is invalid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

account.verifyEmail

+

Verify an email address for telegram passport.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.updateProfile b/data/corefork.telegram.org/method/account.updateProfile new file mode 100644 index 0000000000..bb056bdd9b --- /dev/null +++ b/data/corefork.telegram.org/method/account.updateProfile @@ -0,0 +1,187 @@ + + + + + account.updateProfile + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateProfile

+ +

Updates user profile.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
first_nameflags.0?stringNew user first name
last_nameflags.1?stringNew user last name
aboutflags.2?stringNew bio
+

Result

+

Returns User object containing the updated current user profile.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ABOUT_TOO_LONGAbout string too long.
400FIRSTNAME_INVALIDThe first name is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.updateStatus b/data/corefork.telegram.org/method/account.updateStatus new file mode 100644 index 0000000000..7e894a4256 --- /dev/null +++ b/data/corefork.telegram.org/method/account.updateStatus @@ -0,0 +1,155 @@ + + + + + account.updateStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateStatus

+ +

Updates online user status.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updateStatus#6628562c offline:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
offlineBoolIf (boolTrue) is transmitted, user status will change to (userStatusOffline).
+

Result

+

Bool

+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

userStatusOffline

+

The user's offline status.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.updateTheme b/data/corefork.telegram.org/method/account.updateTheme new file mode 100644 index 0000000000..2e5cc50ea7 --- /dev/null +++ b/data/corefork.telegram.org/method/account.updateTheme @@ -0,0 +1,196 @@ + + + + + account.updateTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateTheme

+ +

Update theme

+

+ +
+
theme#a00e67d6 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?Vector<ThemeSettings> emoticon:flags.6?string installs_count:flags.4?int = Theme;
+---functions---
+account.updateTheme#2bf40ccc flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?Vector<InputThemeSettings> = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme to update
slugflags.0?stringUnique theme ID
titleflags.1?stringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
+

Result

+

Theme

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_INVALIDInvalid theme provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.updateUsername b/data/corefork.telegram.org/method/account.updateUsername new file mode 100644 index 0000000000..f41e55faea --- /dev/null +++ b/data/corefork.telegram.org/method/account.updateUsername @@ -0,0 +1,182 @@ + + + + + account.updateUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateUsername

+ +

Changes username for the current user.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.updateUsername#3e0bdd7c username:string = User;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usernamestringusername or empty string if username is to be removed
Accepted characters: a-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
+

Result

+

Returns updated information on the user in a User type object.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400USERNAME_INVALIDUnacceptable username.
400USERNAME_NOT_MODIFIEDUsername is not different from the current username.
400USERNAME_OCCUPIEDUsername is taken.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.uploadTheme b/data/corefork.telegram.org/method/account.uploadTheme new file mode 100644 index 0000000000..916d23157f --- /dev/null +++ b/data/corefork.telegram.org/method/account.uploadTheme @@ -0,0 +1,190 @@ + + + + + account.uploadTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.uploadTheme

+ +

Upload theme

+

+ +
+
documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+---functions---
+account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileTheme file uploaded as described in files »
thumbflags.0?InputFileThumbnail
file_namestringFile name
mime_typestringMIME type, must be application/x-tgtheme-{format}, where format depends on the client
+

Result

+

Document

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_FILE_INVALIDInvalid theme file provided.
+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.uploadWallPaper b/data/corefork.telegram.org/method/account.uploadWallPaper new file mode 100644 index 0000000000..2abbce23bb --- /dev/null +++ b/data/corefork.telegram.org/method/account.uploadWallPaper @@ -0,0 +1,182 @@ + + + + + account.uploadWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.uploadWallPaper

+ +

Create and upload a new wallpaper

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
+---functions---
+account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
fileInputFileThe JPG/PNG wallpaper
mime_typestringMIME type of uploaded wallpaper
settingsWallPaperSettingsWallpaper settings
+

Result

+

WallPaper

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_FILE_INVALIDThe specified wallpaper file is invalid.
400WALLPAPER_MIME_INVALIDThe specified wallpaper MIME type is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.verifyEmail b/data/corefork.telegram.org/method/account.verifyEmail new file mode 100644 index 0000000000..d6345689d1 --- /dev/null +++ b/data/corefork.telegram.org/method/account.verifyEmail @@ -0,0 +1,179 @@ + + + + + account.verifyEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.verifyEmail

+ +

Verify an email address for telegram passport.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.verifyEmail#ecba39db email:string code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emailstringThe email to verify
codestringThe verification code that was received
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMAIL_INVALIDThe specified email is invalid.
400EMAIL_VERIFY_EXPIREDThe verification email has expired.
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.verifyPhone b/data/corefork.telegram.org/method/account.verifyPhone new file mode 100644 index 0000000000..6680e54e99 --- /dev/null +++ b/data/corefork.telegram.org/method/account.verifyPhone @@ -0,0 +1,191 @@ + + + + + account.verifyPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.verifyPhone

+ +

Verify a phone number for telegram passport.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash received from the call to account.sendVerifyPhoneCode
phone_codestringCode received after the call to account.sendVerifyPhoneCode
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_NUMBER_INVALIDThe phone number is invalid.
+

Related pages

+

account.sendVerifyPhoneCode

+

Send the verification phone code for telegram passport.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.acceptLoginToken b/data/corefork.telegram.org/method/auth.acceptLoginToken new file mode 100644 index 0000000000..902218580c --- /dev/null +++ b/data/corefork.telegram.org/method/auth.acceptLoginToken @@ -0,0 +1,171 @@ + + + + + auth.acceptLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.acceptLoginToken

+ +

Accept QR code login token, logging in the app that generated it.

+

Returns info about the new session.

+

For more info, see login via QR code.

+

+ +
+
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+---functions---
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
tokenbytesLogin token embedded in QR code, for more info, see login via QR code.
+

Result

+

Authorization

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.bindTempAuthKey b/data/corefork.telegram.org/method/auth.bindTempAuthKey new file mode 100644 index 0000000000..f33ff26ada --- /dev/null +++ b/data/corefork.telegram.org/method/auth.bindTempAuthKey @@ -0,0 +1,252 @@ + + + + + auth.bindTempAuthKey + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.bindTempAuthKey

+ +

Binds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

+

For more information, see Perfect Forward Secrecy.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
perm_auth_key_idlongPermanent auth_key_id to bind to
noncelongRandom long from Binding message contents
expires_atintUnix timestamp to invalidate temporary key, see Binding message contents
encrypted_messagebytesSee Generating encrypted_message
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ENCRYPTED_MESSAGE_INVALIDEncrypted message is incorrect.
400TEMP_AUTH_KEY_ALREADY_BOUNDThe passed temporary key is already bound to another perm_auth_key_id.
400TEMP_AUTH_KEY_EMPTYThe request was not performed with a temporary authorization key.
+

Generating encrypted_message

+

The client begins by creating a special binding message:

+

Binding message contents

+
bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
noncelongRandom long
temp_auth_key_idlongTemporary auth_key_id
perm_auth_key_idlongPermanent auth_key_id to bind to
temp_session_idlongSession id, which will be used to invoke auth.bindTempAuthKey method
expires_atintUnix timestamp to invalidate temporary key
+

Encrypting the binding message

+

This binding message is encrypted in the usual way, but with MTProto v1 using the perm_auth_key. In other words, one has to prepend random:int128 (it replaces the customary session_id:long and salt:long that are irrelevant in this case), then append the same msg_id that will be used for the request, a seqno equal to zero, and the correct msg_len (40 bytes in this case); after that, one computes the msg_key:int128 as SHA1 of the resulting string, appends padding necessary for a 16-byte alignment, encrypts the resulting string using the key derived from perm_auth_key and msg_key, and prepends perm_auth_key_id and msg_key to the encrypted data as usual.

+

Binding

+

Once encrypted_message is ready, an auth.bindTempAuthKey request is sent to the server using temp_auth_key and temp_session_id. Don't forget to rewrite client info using initConnection when the binding is completed.

+

Bots can use this method

+

Related pages

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

long

+

A basic bare type, elements of which correspond to two-element sequences, representing 64-bit signed numbers (little-endian).

+

More on basic types »

+

int

+

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

+

More on basic types »

+

Mobile Protocol: Detailed Description

+

Calling API Methods

+

Additional options for calling methods.

+

initConnection

+

Initialize connection

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.cancelCode b/data/corefork.telegram.org/method/auth.cancelCode new file mode 100644 index 0000000000..5401d85744 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.cancelCode @@ -0,0 +1,180 @@ + + + + + auth.cancelCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.cancelCode

+ +

Cancel the login verification code

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash from auth.sendCode
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_NUMBER_INVALIDThe phone number is invalid.
+

Related pages

+

auth.sendCode

+

Send the verification code for login

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.checkPassword b/data/corefork.telegram.org/method/auth.checkPassword new file mode 100644 index 0000000000..e0e48b6aec --- /dev/null +++ b/data/corefork.telegram.org/method/auth.checkPassword @@ -0,0 +1,180 @@ + + + + + auth.checkPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.checkPassword

+ +

Try logging to an account protected by a 2FA password.

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPThe account's password (see SRP)
+

Result

+

auth.Authorization

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password isn't valid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.checkPhone b/data/corefork.telegram.org/method/auth.checkPhone new file mode 100644 index 0000000000..cd1c70da69 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.checkPhone @@ -0,0 +1,176 @@ + + + + + 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.checkRecoveryPassword b/data/corefork.telegram.org/method/auth.checkRecoveryPassword new file mode 100644 index 0000000000..159152077c --- /dev/null +++ b/data/corefork.telegram.org/method/auth.checkRecoveryPassword @@ -0,0 +1,174 @@ + + + + + auth.checkRecoveryPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.checkRecoveryPassword

+ +

Check if the 2FA recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.checkRecoveryPassword#d36bf79 code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
codestringCode received via email
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_RECOVERY_EXPIREDThe recovery code has expired.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

auth.requestPasswordRecovery

+

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

+

auth.recoverPassword

+

Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.dropTempAuthKeys b/data/corefork.telegram.org/method/auth.dropTempAuthKeys new file mode 100644 index 0000000000..578435dac1 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.dropTempAuthKeys @@ -0,0 +1,151 @@ + + + + + auth.dropTempAuthKeys + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.dropTempAuthKeys

+ +

Delete all temporary authorization keys except for the ones specified

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
except_auth_keysVector<long>The auth keys that shouldn't be dropped.
+

Result

+

Bool

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.exportAuthorization b/data/corefork.telegram.org/method/auth.exportAuthorization new file mode 100644 index 0000000000..a813e1c76e --- /dev/null +++ b/data/corefork.telegram.org/method/auth.exportAuthorization @@ -0,0 +1,167 @@ + + + + + auth.exportAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.exportAuthorization

+ +

Returns data for copying authorization to another data-centre.

+

+ +
+
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
+---functions---
+auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dc_idintNumber of a target data-centre
+

Result

+

auth.ExportedAuthorization

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400DC_ID_INVALIDThe provided DC ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.exportLoginToken b/data/corefork.telegram.org/method/auth.exportLoginToken new file mode 100644 index 0000000000..2d4102d075 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.exportLoginToken @@ -0,0 +1,183 @@ + + + + + auth.exportLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.exportLoginToken

+ +

Generate a login token, for login via QR code.
+The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.

+

For more info, see login via QR code.

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+---functions---
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
except_idsVector<long>List of already logged-in user IDs, to prevent logging in twice with the same user
+

Result

+

auth.LoginToken

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400API_ID_INVALIDAPI ID invalid.
+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.importAuthorization b/data/corefork.telegram.org/method/auth.importAuthorization new file mode 100644 index 0000000000..96868d1f5a --- /dev/null +++ b/data/corefork.telegram.org/method/auth.importAuthorization @@ -0,0 +1,178 @@ + + + + + auth.importAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.importAuthorization

+ +

Logs in a user using a key transmitted from his native data-centre.

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongUser ID
bytesbytesAuthorization key
+

Result

+

auth.Authorization

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.importBotAuthorization b/data/corefork.telegram.org/method/auth.importBotAuthorization new file mode 100644 index 0000000000..b8dfcbdbbb --- /dev/null +++ b/data/corefork.telegram.org/method/auth.importBotAuthorization @@ -0,0 +1,205 @@ + + + + + auth.importBotAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.importBotAuthorization

+ +

Login as a bot

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flagsintReserved for future use
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
bot_auth_tokenstringBot token (see bots)
+

Result

+

Returns an auth.Authorization object with information on the new authorization.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ACCESS_TOKEN_EXPIREDBot token expired.
400ACCESS_TOKEN_INVALIDThe provided token is not valid.
400API_ID_INVALIDThe api_id/api_hash combination is invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
401AUTH_KEY_INVALIDAuth key invalid.
+

Bots can use this method

+

Related pages

+

Bots: An introduction for developers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.importLoginToken b/data/corefork.telegram.org/method/auth.importLoginToken new file mode 100644 index 0000000000..1ec76c4d48 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.importLoginToken @@ -0,0 +1,187 @@ + + + + + auth.importLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.importLoginToken

+ +

Login using a redirected login token, generated in case of DC mismatch during QR code login.

+

For more info, see login via QR code.

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+---functions---
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
tokenbytesLogin token
+

Result

+

auth.LoginToken

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_TOKEN_ALREADY_ACCEPTEDThe specified auth token was already accepted.
400AUTH_TOKEN_EXPIREDThe authorization token has expired.
400AUTH_TOKEN_INVALIDThe specified auth token is invalid.
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.logOut b/data/corefork.telegram.org/method/auth.logOut new file mode 100644 index 0000000000..406adb58b9 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.logOut @@ -0,0 +1,139 @@ + + + + + auth.logOut + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.logOut

+ +

Logs out the user.

+

+ +
+
auth.loggedOut#c3a2835f flags:# future_auth_token:flags.0?bytes = auth.LoggedOut;
+---functions---
+auth.logOut#3e72ba19 = auth.LoggedOut;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Query example

+
(auth.logOut )
+=
+(boolTrue)
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.recoverPassword b/data/corefork.telegram.org/method/auth.recoverPassword new file mode 100644 index 0000000000..5069ad08fc --- /dev/null +++ b/data/corefork.telegram.org/method/auth.recoverPassword @@ -0,0 +1,187 @@ + + + + + auth.recoverPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.recoverPassword

+ +

Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
codestringCode received via email
new_settingsflags.0?account.PasswordInputSettingsNew password
+

Result

+

auth.Authorization

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_EMPTYThe provided code is empty.
400NEW_SETTINGS_INVALIDThe new settings are invalid.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

auth.requestPasswordRecovery

+

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.requestPasswordRecovery b/data/corefork.telegram.org/method/auth.requestPasswordRecovery new file mode 100644 index 0000000000..26e13dcdd3 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.requestPasswordRecovery @@ -0,0 +1,159 @@ + + + + + auth.requestPasswordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.requestPasswordRecovery

+ +

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+---functions---
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

auth.PasswordRecovery

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_EMPTYThe provided password is empty.
400PASSWORD_RECOVERY_NANo email was set, can't recover password via email.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.resendCode b/data/corefork.telegram.org/method/auth.resendCode new file mode 100644 index 0000000000..1d973de583 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.resendCode @@ -0,0 +1,191 @@ + + + + + auth.resendCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.resendCode

+ +

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringThe phone number
phone_code_hashstringThe phone code hash obtained from auth.sendCode
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_CODE_HASH_EMPTYphone_code_hash is missing.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
406SEND_CODE_UNAVAILABLEReturned when all available options for this type of number were already used (e.g. flash-call, then SMS, then this error might be returned to trigger a second resend).
+

Related pages

+

auth.sendCode

+

Send the verification code for login

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.resetAuthorizations b/data/corefork.telegram.org/method/auth.resetAuthorizations new file mode 100644 index 0000000000..9fdf0a6c9f --- /dev/null +++ b/data/corefork.telegram.org/method/auth.resetAuthorizations @@ -0,0 +1,156 @@ + + + + + auth.resetAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.resetAuthorizations

+ +

Terminates all user's authorized sessions except for the current one.

+

After calling this method it is necessary to reregister the current device using the method account.registerDevice

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.resetAuthorizations#9fab0d1a = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
+

Related pages

+

account.registerDevice

+

Register device to receive PUSH notifications

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.sendCall b/data/corefork.telegram.org/method/auth.sendCall new file mode 100644 index 0000000000..ffc1255c55 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.sendCall @@ -0,0 +1,175 @@ + + + + + auth.sendCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendCall

+ +

Makes a voice call to the passed phone number. A robot will repeat the confirmation code from a previously sent SMS message.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
+

Result

+

Bool

+

Query example

+
(auth.sendCall "79991234567" "2dc02d2cda9e615c84")
+=
+(boolTrue)
+
+03c51564 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 64e1a61b
+=
+997275b5
+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.sendCode b/data/corefork.telegram.org/method/auth.sendCode new file mode 100644 index 0000000000..90b22a31cb --- /dev/null +++ b/data/corefork.telegram.org/method/auth.sendCode @@ -0,0 +1,236 @@ + + + + + auth.sendCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendCode

+ +

Send the verification code for login

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in international format
api_idintApplication identifier (see App configuration)
api_hashstringApplication secret hash (see App configuration)
settingsCodeSettingsSettings for the code type to send
+

Result

+

The method returns an auth.SentCode object with information on the message sent.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400API_ID_INVALIDAPI ID invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
303NETWORK_MIGRATE_XRepeat the query to data-center X.
303PHONE_MIGRATE_XRepeat the query to data-center X.
400PHONE_NUMBER_APP_SIGNUP_FORBIDDENYou can't sign up using this app.
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram.
400PHONE_NUMBER_FLOODYou asked for the code too many times.
400PHONE_NUMBER_INVALIDInvalid phone number.
406PHONE_PASSWORD_FLOODYou have tried logging in too many times.
400PHONE_PASSWORD_PROTECTEDThis phone is password protected.
400SMS_CODE_CREATE_FAILEDAn error occurred while creating the SMS code.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.sendInvites b/data/corefork.telegram.org/method/auth.sendInvites new file mode 100644 index 0000000000..10a3136919 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.sendInvites @@ -0,0 +1,157 @@ + + + + + auth.sendInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendInvites

+ +

Saves information that the current user sent SMS-messages with invitations to its unregistered contacts.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numbersVector<string>List of phone numbers of message recipients in the international format
messagestringMessage text
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.sendSms b/data/corefork.telegram.org/method/auth.sendSms new file mode 100644 index 0000000000..1d5b0a244c --- /dev/null +++ b/data/corefork.telegram.org/method/auth.sendSms @@ -0,0 +1,167 @@ + + + + + auth.sendSms + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendSms

+ +

Forces sending an SMS message to the specified phone number. Use this method if auth.sentAppCode was returned as a response to auth.sendCode, but the user can't reach the device with Telegram.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in international format
phone_code_hashstringSMS-message ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.signIn b/data/corefork.telegram.org/method/auth.signIn new file mode 100644 index 0000000000..9d6af35ed2 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.signIn @@ -0,0 +1,219 @@ + + + + + auth.signIn + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.signIn

+ +

Signs in a user with a validated phone number.

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID, obtained from auth.sendCode
phone_codestringValid numerical code from the SMS-message
+

Result

+

Returns an auth.Authorization object with information on the new authorization.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code from the SMS is empty.
400PHONE_CODE_EXPIREDSMS expired.
400PHONE_CODE_INVALIDInvalid SMS code was sent.
400PHONE_NUMBER_INVALIDInvalid phone number.
400PHONE_NUMBER_UNOCCUPIEDThe code is valid but no user with the given number is registered.
+

Query example

+
(auth.signIn "79991234567" "2dc02d2cda9e615c84" "44444")
+=
+(auth.authorization
+  expires:1403938438
+  user:(userSelf
+    id:603177
+    first_name:"John"
+    last_name:"Doe"
+    phone:"79991234567"
+    photo:(userProfilePhotoEmpty)
+    status:(userStatusEmpty)
+    inactive:(boolTrue)
+  )
+)
+
+bcd51581 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 34343405 00003434 45ca2b3b
+=
+f6b673a4 53ae6686 720535ec 00093429 686f4a04 0000006e 656f4403 3939370b 33323139 37363534 4f11bae1 09d05049 997275b5 d8487410
+

Related pages

+

auth.sendCode

+

Send the verification code for login

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.signUp b/data/corefork.telegram.org/method/auth.signUp new file mode 100644 index 0000000000..e509e0c68a --- /dev/null +++ b/data/corefork.telegram.org/method/auth.signUp @@ -0,0 +1,236 @@ + + + + + auth.signUp + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.signUp

+ +

Registers a validated phone number in the system.

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
first_namestringNew user first name
last_namestringNew user last name
+

Result

+

Returns an auth.Authorization object with information about the new authorization.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FIRSTNAME_INVALIDInvalid first name.
400LASTNAME_INVALIDInvalid last name.
400PHONE_CODE_EMPTYphone_code from a SMS is empty.
400PHONE_CODE_EXPIREDSMS expired.
400PHONE_CODE_INVALIDInvalid SMS code was sent.
400PHONE_NUMBER_FLOODYou asked for the code too many times.
400PHONE_NUMBER_INVALIDInvalid phone number.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
+

Query example

+
(auth.signUp "79991234567" "2dc02d2cda9e615c84" "44444" "John" "Doe")
+=
+(auth.authorization
+  expires:1403938438
+  user:(userSelf
+    id:603177
+    first_name:"John"
+    last_name:"Doe"
+    phone:"79991234567"
+    photo:(userProfilePhotoEmpty)
+    status:(userStatusEmpty)
+    inactive:(boolTrue)
+  )
+)
+
+1b067634 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 34343405 00003434 686f4a04 0000006e 656f4403 c18027ca
+=
+f6b673a4 53ae6686 720535ec 00093429 686f4a04 0000006e 656f4403 3939370b 33323139 37363534 4f11bae1 09d05049 997275b5 d8487410
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/bots.answerWebhookJSONQuery b/data/corefork.telegram.org/method/bots.answerWebhookJSONQuery new file mode 100644 index 0000000000..49ae27a1b9 --- /dev/null +++ b/data/corefork.telegram.org/method/bots.answerWebhookJSONQuery @@ -0,0 +1,178 @@ + + + + + bots.answerWebhookJSONQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.answerWebhookJSONQuery

+ +

Answers a custom query; for bots only

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
query_idlongIdentifier of a custom query
dataDataJSONJSON-serialized answer to the query
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400QUERY_ID_INVALIDThe query ID is invalid.
400USER_BOT_INVALIDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/bots.getBotCommands b/data/corefork.telegram.org/method/bots.getBotCommands new file mode 100644 index 0000000000..83cc638350 --- /dev/null +++ b/data/corefork.telegram.org/method/bots.getBotCommands @@ -0,0 +1,154 @@ + + + + + bots.getBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.getBotCommands

+ +

Obtain a list of bot commands for the specified bot scope and language code

+

+ +
+
---functions---
+bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
+

Result

+

Vector<BotCommand>

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/bots.resetBotCommands b/data/corefork.telegram.org/method/bots.resetBotCommands new file mode 100644 index 0000000000..db7bb74b99 --- /dev/null +++ b/data/corefork.telegram.org/method/bots.resetBotCommands @@ -0,0 +1,156 @@ + + + + + bots.resetBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.resetBotCommands

+ +

Clear bot commands for the specified bot scope and language code

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
+

Result

+

Bool

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/bots.sendCustomRequest b/data/corefork.telegram.org/method/bots.sendCustomRequest new file mode 100644 index 0000000000..9ded1e2c9c --- /dev/null +++ b/data/corefork.telegram.org/method/bots.sendCustomRequest @@ -0,0 +1,177 @@ + + + + + bots.sendCustomRequest + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.sendCustomRequest

+ +

Sends a custom request; for bots only

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;
+---functions---
+bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
custom_methodstringThe method name
paramsDataJSONJSON-serialized method parameters
+

Result

+

DataJSON

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400USER_BOT_INVALIDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/bots.setBotCommands b/data/corefork.telegram.org/method/bots.setBotCommands new file mode 100644 index 0000000000..18b96b3c47 --- /dev/null +++ b/data/corefork.telegram.org/method/bots.setBotCommands @@ -0,0 +1,188 @@ + + + + + bots.setBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.setBotCommands

+ +

Set bot command list

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
commandsVector<BotCommand>Bot commands
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_COMMAND_DESCRIPTION_INVALIDThe specified command description is invalid.
400BOT_COMMAND_INVALIDThe specified command is invalid.
400LANG_CODE_INVALIDThe specified language code is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.checkUsername b/data/corefork.telegram.org/method/channels.checkUsername new file mode 100644 index 0000000000..711bcf9852 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.checkUsername @@ -0,0 +1,190 @@ + + + + + channels.checkUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.checkUsername

+ +

Check if a username is free and can be assigned to a channel/supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe channel/supergroup that will assigned the specified username
usernamestringThe username to check
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400USERNAME_INVALIDThe provided username is not valid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.convertToGigagroup b/data/corefork.telegram.org/method/channels.convertToGigagroup new file mode 100644 index 0000000000..18703b86a1 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.convertToGigagroup @@ -0,0 +1,177 @@ + + + + + channels.convertToGigagroup + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.convertToGigagroup

+ +

Convert a supergroup to a gigagroup, when requested by channel suggestions.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup to convert
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PARTICIPANTS_TOO_FEWNot enough participants.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.createChannel b/data/corefork.telegram.org/method/channels.createChannel new file mode 100644 index 0000000000..596a35b07b --- /dev/null +++ b/data/corefork.telegram.org/method/channels.createChannel @@ -0,0 +1,232 @@ + + + + + channels.createChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.createChannel

+ +

Create a supergroup/channel.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.0?trueWhether to create a channel
megagroupflags.1?trueWhether to create a supergroup
for_importflags.3?trueWhether the supergroup is being created to import messages from a foreign chat service using messages.initHistoryImport
titlestringChannel title
aboutstringChannel description
geo_pointflags.2?InputGeoPointGeogroup location
addressflags.2?stringGeogroup address
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHThe user has reached the limit of public geogroups.
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_TITLE_EMPTYNo chat title provided.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

messages.initHistoryImport

+

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.deleteChannel b/data/corefork.telegram.org/method/channels.deleteChannel new file mode 100644 index 0000000000..70ecf52caa --- /dev/null +++ b/data/corefork.telegram.org/method/channels.deleteChannel @@ -0,0 +1,200 @@ + + + + + channels.deleteChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteChannel

+ +

Delete a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup to delete
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHANNEL_TOO_LARGEChannel is too large to be deleted; this error is issued when trying to delete channels with more than 1000 members (subject to change).
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.deleteHistory b/data/corefork.telegram.org/method/channels.deleteHistory new file mode 100644 index 0000000000..46c58dfb14 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.deleteHistory @@ -0,0 +1,180 @@ + + + + + channels.deleteHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteHistory

+ +

Delete the history of a supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup whose history must be deleted
max_idintID of message up to which the history must be deleted
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.deleteMessages b/data/corefork.telegram.org/method/channels.deleteMessages new file mode 100644 index 0000000000..687610478c --- /dev/null +++ b/data/corefork.telegram.org/method/channels.deleteMessages @@ -0,0 +1,190 @@ + + + + + channels.deleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteMessages

+ +

Delete messages in a channel/supergroup

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<int>IDs of messages to delete
+

Result

+

messages.AffectedMessages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403MESSAGE_DELETE_FORBIDDENYou can't delete one of the messages you tried to delete, most likely because it is a service message.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.deleteParticipantHistory b/data/corefork.telegram.org/method/channels.deleteParticipantHistory new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.deleteParticipantHistory @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.deleteUserHistory b/data/corefork.telegram.org/method/channels.deleteUserHistory new file mode 100644 index 0000000000..d67890cceb --- /dev/null +++ b/data/corefork.telegram.org/method/channels.deleteUserHistory @@ -0,0 +1,197 @@ + + + + + channels.deleteUserHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteUserHistory

+ +

Delete all messages sent by a certain user in a supergroup

+

+ +
+
 Method schema is available as of layer 135. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup
user_idInputUserUser whose messages should be deleted
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.editAdmin b/data/corefork.telegram.org/method/channels.editAdmin new file mode 100644 index 0000000000..a2796c284a --- /dev/null +++ b/data/corefork.telegram.org/method/channels.editAdmin @@ -0,0 +1,301 @@ + + + + + channels.editAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editAdmin

+ +

Modify the admin rights of a user in a supergroup/channel.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup/channel.
user_idInputUserThe ID of the user whose admin rights should be modified
admin_rightsChatAdminRightsThe admin rights
rankstringIndicates the role (rank) of the admin in the group: just an arbitrary string
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ADMINS_TOO_MUCHThere are too many admins.
400ADMIN_RANK_EMOJI_NOT_ALLOWEDAn admin rank cannot contain emojis.
400ADMIN_RANK_INVALIDThe specified admin rank is invalid.
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_CHANNELS_NABots can't edit admin privileges.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHAT_ADMIN_INVITE_REQUIREDYou do not have the rights to do this.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
406FRESH_CHANGE_ADMINS_FORBIDDENYou were just elected admin, you can't add or modify other admins yet.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
403RIGHT_FORBIDDENYour admin rights do not allow you to do this.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BLOCKEDUser blocked.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.editBanned b/data/corefork.telegram.org/method/channels.editBanned new file mode 100644 index 0000000000..9f3b883050 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.editBanned @@ -0,0 +1,241 @@ + + + + + channels.editBanned + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editBanned

+ +

Ban/unban/kick a user in a supergroup/channel.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup/channel.
participantInputPeerParticipant to ban
banned_rightsChatBannedRightsThe banned rights
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_ADD_INVALIDInternal error.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400USER_ADMIN_INVALIDYou're not an admin.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.editCreator b/data/corefork.telegram.org/method/channels.editCreator new file mode 100644 index 0000000000..24fdcc49c9 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.editCreator @@ -0,0 +1,225 @@ + + + + + channels.editCreator + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editCreator

+ +

Transfer channel ownership

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
user_idInputUserNew channel owner
passwordInputCheckPasswordSRP2FA password of account
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400PASSWORD_MISSINGYou must enable 2FA in order to transfer ownership of a channel.
400PASSWORD_TOO_FRESH_XThe password was modified less than 24 hours ago, try again in X seconds.
400SESSION_TOO_FRESH_XThis session was created less than 24 hours ago, try again in X seconds.
400SRP_ID_INVALIDInvalid SRP ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.editLocation b/data/corefork.telegram.org/method/channels.editLocation new file mode 100644 index 0000000000..3b3b150003 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.editLocation @@ -0,0 +1,180 @@ + + + + + channels.editLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editLocation

+ +

Edit location of geogroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelGeogroup
geo_pointInputGeoPointNew geolocation
addressstringAddress string
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MEGAGROUP_REQUIREDYou can only use this method on a supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.editPhoto b/data/corefork.telegram.org/method/channels.editPhoto new file mode 100644 index 0000000000..27a98d2749 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.editPhoto @@ -0,0 +1,221 @@ + + + + + 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.exportMessageLink b/data/corefork.telegram.org/method/channels.exportMessageLink new file mode 100644 index 0000000000..c21366c9f8 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.exportMessageLink @@ -0,0 +1,204 @@ + + + + + channels.exportMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.exportMessageLink

+ +

Get link and embed info of a message in a channel/supergroup

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+---functions---
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
groupedflags.0?trueWhether to include other grouped media (for albums)
threadflags.1?trueWhether to also include a thread ID, if available, inside of the link
channelInputChannelChannel
idintMessage ID
+

Result

+

ExportedMessageLink

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getAdminLog b/data/corefork.telegram.org/method/channels.getAdminLog new file mode 100644 index 0000000000..c9ff7d31c0 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getAdminLog @@ -0,0 +1,226 @@ + + + + + channels.getAdminLog + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getAdminLog

+ +

Get the admin log of a channel/supergroup

+

+ +
+
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+---functions---
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channelInputChannelChannel
qstringSearch query, can be empty
events_filterflags.0?ChannelAdminLogEventsFilterEvent filter
adminsflags.1?Vector<InputUser>Only show events from these admins
max_idlongMaximum ID of message to return (see pagination)
min_idlongMinimum ID of message to return (see pagination)
limitintMaximum number of results to return, see pagination
+

Result

+

channels.AdminLogResults

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels new file mode 100644 index 0000000000..b01d157d67 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels @@ -0,0 +1,191 @@ + + + + + channels.getAdminedPublicChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getAdminedPublicChannels

+ +

Get channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
by_locationflags.0?trueGet geogroups
check_limitflags.1?trueIf set and the user has reached the limit of owned public channels/supergroups/geogroups, instead of returning the channel list one of the specified errors will be returned.
Useful to check if a new public channel can indeed be created, even before asking the user to enter a channel username to use in channels.checkUsername/channels.updateUsername.
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHReturned if both the check_limit and the by_location flags are set and the user has reached the limit of public geogroups.
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHReturned if the check_limit flag is set and the user has reached the limit of public channels/supergroups.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

channels.checkUsername

+

Check if a username is free and can be assigned to a channel/supergroup

+

channels.updateUsername

+

Change the username of a supergroup/channel

+

config

+

Current configuration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getChannels b/data/corefork.telegram.org/method/channels.getChannels new file mode 100644 index 0000000000..3ccc4f16d8 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getChannels @@ -0,0 +1,181 @@ + + + + + channels.getChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getChannels

+ +

Get info about channels/supergroups

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputChannel>IDs of channels/supergroups to get info about
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getFullChannel b/data/corefork.telegram.org/method/channels.getFullChannel new file mode 100644 index 0000000000..06fe9485a6 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getFullChannel @@ -0,0 +1,187 @@ + + + + + channels.getFullChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getFullChannel

+ +

Get full info about a channel

+

+ +
+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
+---functions---
+channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe channel to get info about
+

Result

+

messages.ChatFull

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getGroupsForDiscussion b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion new file mode 100644 index 0000000000..74cd048bb5 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion @@ -0,0 +1,144 @@ + + + + + channels.getGroupsForDiscussion + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getGroupsForDiscussion

+ +

Get all groups that can be used as discussion groups.

+

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
+To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

messages.Chats

+

Related pages

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

channels.togglePreHistoryHidden

+

Hide/unhide message history for new channel/supergroup users

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getInactiveChannels b/data/corefork.telegram.org/method/channels.getInactiveChannels new file mode 100644 index 0000000000..092a6b2cc7 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getInactiveChannels @@ -0,0 +1,134 @@ + + + + + channels.getInactiveChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getInactiveChannels

+ +

Get inactive channels and supergroups

+

+ +
+
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
+---functions---
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

messages.InactiveChats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getLeftChannels b/data/corefork.telegram.org/method/channels.getLeftChannels new file mode 100644 index 0000000000..eb0ee22efe --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getLeftChannels @@ -0,0 +1,172 @@ + + + + + channels.getLeftChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getLeftChannels

+ +

Get a list of channels/supergroups we left

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset for pagination
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getMessages b/data/corefork.telegram.org/method/channels.getMessages new file mode 100644 index 0000000000..ab24f951a5 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getMessages @@ -0,0 +1,193 @@ + + + + + channels.getMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getMessages

+ +

Get channel/supergroup messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<InputMessage>IDs of messages to get
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getParticipant b/data/corefork.telegram.org/method/channels.getParticipant new file mode 100644 index 0000000000..0f63b40f63 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getParticipant @@ -0,0 +1,205 @@ + + + + + channels.getParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getParticipant

+ +

Get info about a channel/supergroup participant

+

+ +
+
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+---functions---
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
participantInputPeerParticipant to get info about
+

Result

+

channels.ChannelParticipant

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getParticipants b/data/corefork.telegram.org/method/channels.getParticipants new file mode 100644 index 0000000000..3001413b72 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getParticipants @@ -0,0 +1,203 @@ + + + + + channels.getParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getParticipants

+ +

Get the participants of a supergroup/channel

+

+ +
+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
+---functions---
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
filterChannelParticipantsFilterWhich participant types to fetch
offsetintOffset
limitintLimit
hashlongHash
+

Result

+

channels.ChannelParticipants

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
+

Bots can use this method

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getSendAs b/data/corefork.telegram.org/method/channels.getSendAs new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getSendAs @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getSponsoredMessages b/data/corefork.telegram.org/method/channels.getSponsoredMessages new file mode 100644 index 0000000000..b2bdf67577 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getSponsoredMessages @@ -0,0 +1,154 @@ + + + + + channels.getSponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getSponsoredMessages

+ +

Get a list of sponsored messages

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+---functions---
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelPeer
+

Result

+

messages.SponsoredMessages

+
+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.inviteToChannel b/data/corefork.telegram.org/method/channels.inviteToChannel new file mode 100644 index 0000000000..274d9aebae --- /dev/null +++ b/data/corefork.telegram.org/method/channels.inviteToChannel @@ -0,0 +1,262 @@ + + + + + channels.inviteToChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.inviteToChannel

+ +

Invite users to a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
usersVector<InputUser>Users to invite
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_INVALIDInvalid chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_BLOCKEDUser blocked.
400USER_BOTBots can only be admins in channels.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_KICKEDThis user was kicked from this supergroup/channel.
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.joinChannel b/data/corefork.telegram.org/method/channels.joinChannel new file mode 100644 index 0000000000..5e58948575 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.joinChannel @@ -0,0 +1,227 @@ + + + + + channels.joinChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.joinChannel

+ +

Join a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.joinChannel#24b524c5 channel:InputChannel = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup to join
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_INVALIDInvalid chat.
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.leaveChannel b/data/corefork.telegram.org/method/channels.leaveChannel new file mode 100644 index 0000000000..fa1372fac8 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.leaveChannel @@ -0,0 +1,201 @@ + + + + + channels.leaveChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.leaveChannel

+ +

Leave a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.leaveChannel#f836aa95 channel:InputChannel = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup to leave
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.readHistory b/data/corefork.telegram.org/method/channels.readHistory new file mode 100644 index 0000000000..17f39dd1a9 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.readHistory @@ -0,0 +1,185 @@ + + + + + channels.readHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.readHistory

+ +

Mark channel/supergroup history as read

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
max_idintID of message up to which messages should be marked as read
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.readMessageContents b/data/corefork.telegram.org/method/channels.readMessageContents new file mode 100644 index 0000000000..c41b6a6d15 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.readMessageContents @@ -0,0 +1,185 @@ + + + + + channels.readMessageContents + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.readMessageContents

+ +

Mark channel/supergroup message contents as read

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<int>IDs of messages whose contents should be marked as read
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.reportSpam b/data/corefork.telegram.org/method/channels.reportSpam new file mode 100644 index 0000000000..5f5a2f128a --- /dev/null +++ b/data/corefork.telegram.org/method/channels.reportSpam @@ -0,0 +1,192 @@ + + + + + channels.reportSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.reportSpam

+ +

Reports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.reportSpam#f44a8315 channel:InputChannel participant:InputPeer id:Vector<int> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup
user_idInputUserID of the user that sent the spam messages
idVector<int>IDs of spam messages
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USER_ID_INVALIDThe provided user ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.setDiscussionGroup b/data/corefork.telegram.org/method/channels.setDiscussionGroup new file mode 100644 index 0000000000..e9b9a870b4 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.setDiscussionGroup @@ -0,0 +1,200 @@ + + + + + channels.setDiscussionGroup + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.setDiscussionGroup

+ +

Associate a group to a channel as discussion group for that channel

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
broadcastInputChannelChannel
groupInputChannelDiscussion group to associate to the channel
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_ID_INVALIDBroadcast ID invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400LINK_NOT_MODIFIEDDiscussion link not modified.
400MEGAGROUP_ID_INVALIDInvalid supergroup ID.
400MEGAGROUP_PREHISTORY_HIDDENGroup with hidden history for new members can't be set as discussion groups.
+

Related pages

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.setStickers b/data/corefork.telegram.org/method/channels.setStickers new file mode 100644 index 0000000000..b94efaaaa2 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.setStickers @@ -0,0 +1,183 @@ + + + + + channels.setStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.setStickers

+ +

Associate a stickerset to the supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup
stickersetInputStickerSetThe stickerset to associate
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400PARTICIPANTS_TOO_FEWNot enough participants.
406STICKERSET_OWNER_ANONYMOUSProvided stickerset can't be installed as group stickerset to prevent admin deanonymisation.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.togglePreHistoryHidden b/data/corefork.telegram.org/method/channels.togglePreHistoryHidden new file mode 100644 index 0000000000..20e3dd8c2b --- /dev/null +++ b/data/corefork.telegram.org/method/channels.togglePreHistoryHidden @@ -0,0 +1,202 @@ + + + + + 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/channels.toggleSignatures b/data/corefork.telegram.org/method/channels.toggleSignatures new file mode 100644 index 0000000000..76e3c38583 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.toggleSignatures @@ -0,0 +1,187 @@ + + + + + channels.toggleSignatures + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.toggleSignatures

+ +

Enable/disable message signatures in channels

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
enabledBoolValue
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.toggleSlowMode b/data/corefork.telegram.org/method/channels.toggleSlowMode new file mode 100644 index 0000000000..04a145a243 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.toggleSlowMode @@ -0,0 +1,190 @@ + + + + + channels.toggleSlowMode + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.toggleSlowMode

+ +

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup
secondsintUsers will only be able to send one message every seconds seconds, 0 to disable the limitation
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400SECONDS_INVALIDInvalid duration provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.updateUsername b/data/corefork.telegram.org/method/channels.updateUsername new file mode 100644 index 0000000000..b827a0cecc --- /dev/null +++ b/data/corefork.telegram.org/method/channels.updateUsername @@ -0,0 +1,212 @@ + + + + + channels.updateUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.updateUsername

+ +

Change the username of a supergroup/channel

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
usernamestringNew username
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400USERNAME_INVALIDThe provided username is not valid.
400USERNAME_NOT_MODIFIEDThe username was not modified.
400USERNAME_OCCUPIEDThe provided username is already occupied.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.viewSponsoredMessage b/data/corefork.telegram.org/method/channels.viewSponsoredMessage new file mode 100644 index 0000000000..97127bf80f --- /dev/null +++ b/data/corefork.telegram.org/method/channels.viewSponsoredMessage @@ -0,0 +1,177 @@ + + + + + channels.viewSponsoredMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.viewSponsoredMessage

+ +

Mark a specific sponsored message as read

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelPeer
random_idbytesMessage ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400UNKNOWN_ERRORInternal error.
+
+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.acceptContact b/data/corefork.telegram.org/method/contacts.acceptContact new file mode 100644 index 0000000000..9f23bb3d52 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.acceptContact @@ -0,0 +1,190 @@ + + + + + contacts.acceptContact + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.acceptContact

+ +

If the peer settings of a new user allow us to add him as contact, add that user as contact

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.acceptContact#f831a20f id:InputUser = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputUserThe user to add as contact
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONTACT_ADD_MISSINGContact to add is missing.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400CONTACT_REQ_MISSINGMissing contact request.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

peerSettings

+

Peer settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.addContact b/data/corefork.telegram.org/method/contacts.addContact new file mode 100644 index 0000000000..470888fec2 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.addContact @@ -0,0 +1,217 @@ + + + + + contacts.addContact + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.addContact

+ +

Add an existing telegram user as contact.

+

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
add_phone_privacy_exceptionflags.0?trueAllow the other user to see our phone number?
idInputUserTelegram ID of the other user
first_namestringFirst name
last_namestringLast name
phonestringUser's phone number
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400CONTACT_NAME_EMPTYContact name empty.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

contacts.importContacts

+

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

+

Use contacts.addContact to add Telegram contacts without actually using their phone number.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.block b/data/corefork.telegram.org/method/contacts.block new file mode 100644 index 0000000000..64bf66ac93 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.block @@ -0,0 +1,182 @@ + + + + + contacts.block + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.block

+ +

Adds the user to the blacklist.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.block#68cc1411 id:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPeerUser ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.deleteByPhones b/data/corefork.telegram.org/method/contacts.deleteByPhones new file mode 100644 index 0000000000..751cdb1ded --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.deleteByPhones @@ -0,0 +1,150 @@ + + + + + contacts.deleteByPhones + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.deleteByPhones

+ +

Delete contacts by phone number

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phonesVector<string>Phone numbers
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.deleteContacts b/data/corefork.telegram.org/method/contacts.deleteContacts new file mode 100644 index 0000000000..0eeed7d06d --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.deleteContacts @@ -0,0 +1,155 @@ + + + + + contacts.deleteContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.deleteContacts

+ +

Deletes several contacts from the list.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputUser>User ID list
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getBlocked b/data/corefork.telegram.org/method/contacts.getBlocked new file mode 100644 index 0000000000..34fd6fc6a5 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getBlocked @@ -0,0 +1,155 @@ + + + + + contacts.getBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getBlocked

+ +

Returns the list of blocked users.

+

+ +
+
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+---functions---
+contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintThe number of list elements to be skipped
limitintThe number of list elements to be returned
+

Result

+

contacts.Blocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getContactIDs b/data/corefork.telegram.org/method/contacts.getContactIDs new file mode 100644 index 0000000000..08cd92f4b5 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getContactIDs @@ -0,0 +1,151 @@ + + + + + contacts.getContactIDs + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getContactIDs

+ +

Get contact by telegram IDs

+

+ +
+
---functions---
+contacts.getContactIDs#7adc669d hash:long = Vector<int>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

Vector<int>

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getContacts b/data/corefork.telegram.org/method/contacts.getContacts new file mode 100644 index 0000000000..ad0e755eff --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getContacts @@ -0,0 +1,155 @@ + + + + + contacts.getContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getContacts

+ +

Returns the current user's contact list.

+

+ +
+
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
+contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
+---functions---
+contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongIf there already is a full contact list on the client, a hash of a the list of contact IDs in ascending order may be passed in this parameter. If the contact set was not changed, (contacts.contactsNotModified) will be returned.
+

Result

+

contacts.Contacts

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

contacts.contactsNotModified

+

Contact list on the server is the same as the list on the client.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getLocated b/data/corefork.telegram.org/method/contacts.getLocated new file mode 100644 index 0000000000..5bd33744f8 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getLocated @@ -0,0 +1,197 @@ + + + + + contacts.getLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getLocated

+ +

Get contacts near you

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
backgroundflags.1?trueWhile the geolocation of the current user is public, clients should update it in the background every half-an-hour or so, while setting this flag.
Do this only if the new location is more than 1 KM away from the previous one, or if the previous location is unknown.
geo_pointInputGeoPointGeolocation
self_expiresflags.0?intIf set, the geolocation of the current user will be public for the specified number of seconds; pass 0x7fffffff to disable expiry, 0 to make the current geolocation private; if the flag isn't set, no changes will be applied.
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400GEO_POINT_INVALIDInvalid geoposition provided.
406USERPIC_PRIVACY_REQUIREDYou need to disable privacy settings for your profile picture in order to make your geolocation public.
406USERPIC_UPLOAD_REQUIREDYou must have a profile picture to publish your geolocation.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getSaved b/data/corefork.telegram.org/method/contacts.getSaved new file mode 100644 index 0000000000..16997c74ad --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getSaved @@ -0,0 +1,150 @@ + + + + + contacts.getSaved + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getSaved

+ +

Get all contacts

+

+ +
+
---functions---
+contacts.getSaved#82f1e39f = Vector<SavedContact>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<SavedContact>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getStatuses b/data/corefork.telegram.org/method/contacts.getStatuses new file mode 100644 index 0000000000..2a9e85a427 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getStatuses @@ -0,0 +1,133 @@ + + + + + contacts.getStatuses + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getStatuses

+ +

Returns the list of contact statuses.

+

+ +
+
---functions---
+contacts.getStatuses#c4a353ee = Vector<ContactStatus>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<ContactStatus>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getTopPeers b/data/corefork.telegram.org/method/contacts.getTopPeers new file mode 100644 index 0000000000..3e9a29b762 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getTopPeers @@ -0,0 +1,226 @@ + + + + + contacts.getTopPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getTopPeers

+ +

Get most used peers

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+---functions---
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
correspondentsflags.0?trueUsers we've chatted most frequently with
bots_pmflags.1?trueMost used bots
bots_inlineflags.2?trueMost used inline bots
phone_callsflags.3?trueMost frequently called users
forward_usersflags.4?trueUsers to which the users often forwards messages to
forward_chatsflags.5?trueChats to which the users often forwards messages to
groupsflags.10?trueOften-opened groups and supergroups
channelsflags.15?trueMost frequently visited channels
offsetintOffset for pagination
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

contacts.TopPeers

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TYPES_EMPTYNo top peer type was provided.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.importContacts b/data/corefork.telegram.org/method/contacts.importContacts new file mode 100644 index 0000000000..9520e1f4b7 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.importContacts @@ -0,0 +1,154 @@ + + + + + contacts.importContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.importContacts

+ +

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

+

Use contacts.addContact to add Telegram contacts without actually using their phone number.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+---functions---
+contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
contactsVector<InputContact>List of contacts to import
+

Result

+

contacts.ImportedContacts

+

Related pages

+

contacts.addContact

+

Add an existing telegram user as contact.

+

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.resetSaved b/data/corefork.telegram.org/method/contacts.resetSaved new file mode 100644 index 0000000000..289e8c43f6 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.resetSaved @@ -0,0 +1,135 @@ + + + + + contacts.resetSaved + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.resetSaved

+ +

Delete saved contacts

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.resetSaved#879537f1 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.resetTopPeerRating b/data/corefork.telegram.org/method/contacts.resetTopPeerRating new file mode 100644 index 0000000000..4030342565 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.resetTopPeerRating @@ -0,0 +1,175 @@ + + + + + contacts.resetTopPeerRating + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.resetTopPeerRating

+ +

Reset rating of top peer

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
categoryTopPeerCategoryTop peer category
peerInputPeerPeer whose rating should be reset
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.resolveUsername b/data/corefork.telegram.org/method/contacts.resolveUsername new file mode 100644 index 0000000000..4962cc9ce5 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.resolveUsername @@ -0,0 +1,182 @@ + + + + + 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/corefork.telegram.org/method/contacts.search b/data/corefork.telegram.org/method/contacts.search new file mode 100644 index 0000000000..c05b01ced6 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.search @@ -0,0 +1,178 @@ + + + + + contacts.search + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.search

+ +

Returns users found by username substring.

+

+ +
+
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
+---functions---
+contacts.search#11f812d8 q:string limit:int = contacts.Found;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
qstringTarget substring
limitintMaximum number of users to be returned
+

Result

+

contacts.Found

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400QUERY_TOO_SHORTThe query string is too short.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Notes

+

This method will exclude the current user's contacts from the search results. It is assumed that searches among the user's contacts can be handled locally by the client.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.toggleTopPeers b/data/corefork.telegram.org/method/contacts.toggleTopPeers new file mode 100644 index 0000000000..5c8a9819fc --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.toggleTopPeers @@ -0,0 +1,153 @@ + + + + + contacts.toggleTopPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.toggleTopPeers

+ +

Enable/disable top peers

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
enabledBoolEnable/disable
+

Result

+

Bool

+

Related pages

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.unblock b/data/corefork.telegram.org/method/contacts.unblock new file mode 100644 index 0000000000..47f3607d19 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.unblock @@ -0,0 +1,182 @@ + + + + + contacts.unblock + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.unblock

+ +

Deletes the user from the blacklist.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.unblock#bea65d50 id:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPeerUser ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/folders.deleteFolder b/data/corefork.telegram.org/method/folders.deleteFolder new file mode 100644 index 0000000000..9946b14b17 --- /dev/null +++ b/data/corefork.telegram.org/method/folders.deleteFolder @@ -0,0 +1,175 @@ + + + + + folders.deleteFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

folders.deleteFolder

+ +

Delete a peer folder

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+folders.deleteFolder#1c295881 folder_id:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_EMPTYAn empty folder ID was specified.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/folders.editPeerFolders b/data/corefork.telegram.org/method/folders.editPeerFolders new file mode 100644 index 0000000000..23433f1cd4 --- /dev/null +++ b/data/corefork.telegram.org/method/folders.editPeerFolders @@ -0,0 +1,175 @@ + + + + + folders.editPeerFolders + + + + + + + + + + + + + +
+ +
+
+
+ +

folders.editPeerFolders

+ +

Edit peers in peer folder

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_peersVector<InputFolderPeer>New peer list
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.acceptTermsOfService b/data/corefork.telegram.org/method/help.acceptTermsOfService new file mode 100644 index 0000000000..23a4817050 --- /dev/null +++ b/data/corefork.telegram.org/method/help.acceptTermsOfService @@ -0,0 +1,150 @@ + + + + + help.acceptTermsOfService + + + + + + + + + + + + + +
+ +
+
+
+ +

help.acceptTermsOfService

+ +

Accept the new terms of service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idDataJSONID of terms of service
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.dismissSuggestion b/data/corefork.telegram.org/method/help.dismissSuggestion new file mode 100644 index 0000000000..cfa8e37182 --- /dev/null +++ b/data/corefork.telegram.org/method/help.dismissSuggestion @@ -0,0 +1,160 @@ + + + + + help.dismissSuggestion + + + + + + + + + + + + + +
+ +
+
+
+ +

help.dismissSuggestion

+ +

Dismiss a suggestion, see here for more info ».

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerIn the case of pending suggestions in channels, the channel ID.
suggestionstringSuggestion, see here for more info ».
+

Result

+

Bool

+

Related pages

+

channelFull

+

Full info about a channel/supergroup

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.editUserInfo b/data/corefork.telegram.org/method/help.editUserInfo new file mode 100644 index 0000000000..4064e9408b --- /dev/null +++ b/data/corefork.telegram.org/method/help.editUserInfo @@ -0,0 +1,180 @@ + + + + + help.editUserInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.editUserInfo

+ +

Internal use

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+---functions---
+help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser
messagestringMessage
entitiesVector<MessageEntity>Message entities for styled text
+

Result

+

help.UserInfo

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USER_INVALIDInvalid user provided.
+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getAppChangelog b/data/corefork.telegram.org/method/help.getAppChangelog new file mode 100644 index 0000000000..da5365c2bb --- /dev/null +++ b/data/corefork.telegram.org/method/help.getAppChangelog @@ -0,0 +1,162 @@ + + + + + help.getAppChangelog + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getAppChangelog

+ +

Get changelog of current app.
+Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+help.getAppChangelog#9010ef6f prev_app_version:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
prev_app_versionstringPrevious app version
+

Result

+

Updates

+

Related pages

+

Updates

+

Full constructor of updates

+

updateServiceNotification

+

A service message for the user.

+

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getAppConfig b/data/corefork.telegram.org/method/help.getAppConfig new file mode 100644 index 0000000000..539ae4e774 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getAppConfig @@ -0,0 +1,142 @@ + + + + + help.getAppConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getAppConfig

+ +

Get app-specific configuration, see client configuration for more info on the result.

+

+ +
+
jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+---functions---
+help.getAppConfig#98914110 = JSONValue;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

JSONValue, see client configuration for more info on the result

+

Related pages

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getAppUpdate b/data/corefork.telegram.org/method/help.getAppUpdate new file mode 100644 index 0000000000..5b98074504 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getAppUpdate @@ -0,0 +1,150 @@ + + + + + help.getAppUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getAppUpdate

+ +

Returns information on update availability for the current application.

+

+ +
+
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
+help.noAppUpdate#c45a6536 = help.AppUpdate;
+---functions---
+help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
sourcestringSource
+

Result

+

help.AppUpdate

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getCdnConfig b/data/corefork.telegram.org/method/help.getCdnConfig new file mode 100644 index 0000000000..7bd0cb092b --- /dev/null +++ b/data/corefork.telegram.org/method/help.getCdnConfig @@ -0,0 +1,154 @@ + + + + + help.getCdnConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getCdnConfig

+ +

Get configuration for CDN file downloads.

+

+ +
+
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
+---functions---
+help.getCdnConfig#52029342 = CdnConfig;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

CdnConfig

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
+

Bots can use this method

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getConfig b/data/corefork.telegram.org/method/help.getConfig new file mode 100644 index 0000000000..281f179c47 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getConfig @@ -0,0 +1,192 @@ + + + + + help.getConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getConfig

+ +

Returns current configuration, including data center configuration.

+

+ +
+
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+---functions---
+help.getConfig#c4f9186b = Config;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Config

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400CONNECTION_APP_VERSION_EMPTYApp version is empty.
400CONNECTION_LAYER_INVALIDLayer invalid.
400CONNECTION_NOT_INITEDConnection not initialized.
400DATA_INVALIDEncrypted data invalid.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USERNAME_INVALIDThe provided username is not valid.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getCountriesList b/data/corefork.telegram.org/method/help.getCountriesList new file mode 100644 index 0000000000..d10371091b --- /dev/null +++ b/data/corefork.telegram.org/method/help.getCountriesList @@ -0,0 +1,158 @@ + + + + + help.getCountriesList + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getCountriesList

+ +

Get name, ISO code, localized name and phone codes/patterns of all available countries

+

+ +
+
help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+---functions---
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code of the current user
hashintHash for pagination, for more info click here
+

Result

+

help.CountriesList

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getDeepLinkInfo b/data/corefork.telegram.org/method/help.getDeepLinkInfo new file mode 100644 index 0000000000..6b5c226bca --- /dev/null +++ b/data/corefork.telegram.org/method/help.getDeepLinkInfo @@ -0,0 +1,150 @@ + + + + + help.getDeepLinkInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getDeepLinkInfo

+ +

Get info about a t.me link

+

+ +
+
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
+help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
+---functions---
+help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
pathstringPath in t.me/path
+

Result

+

help.DeepLinkInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getInviteText b/data/corefork.telegram.org/method/help.getInviteText new file mode 100644 index 0000000000..ddcfa5869e --- /dev/null +++ b/data/corefork.telegram.org/method/help.getInviteText @@ -0,0 +1,134 @@ + + + + + help.getInviteText + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getInviteText

+ +

Returns localized text of a text message with an invitation.

+

+ +
+
help.inviteText#18cb9f78 message:string = help.InviteText;
+---functions---
+help.getInviteText#4d392343 = help.InviteText;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.InviteText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getNearestDc b/data/corefork.telegram.org/method/help.getNearestDc new file mode 100644 index 0000000000..5bf959f42c --- /dev/null +++ b/data/corefork.telegram.org/method/help.getNearestDc @@ -0,0 +1,134 @@ + + + + + help.getNearestDc + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getNearestDc

+ +

Returns info on data centre nearest to the user.

+

+ +
+
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+---functions---
+help.getNearestDc#1fb33026 = NearestDc;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

NearestDc

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getPassportConfig b/data/corefork.telegram.org/method/help.getPassportConfig new file mode 100644 index 0000000000..753df9b867 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getPassportConfig @@ -0,0 +1,154 @@ + + + + + help.getPassportConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getPassportConfig

+ +

Get passport configuration

+

+ +
+
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
+help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
+---functions---
+help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
+

Result

+

help.PassportConfig

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getPromoData b/data/corefork.telegram.org/method/help.getPromoData new file mode 100644 index 0000000000..6396c4c925 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getPromoData @@ -0,0 +1,135 @@ + + + + + help.getPromoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getPromoData

+ +

Get MTProxy/Public Service Announcement information

+

+ +
+
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
+help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
+---functions---
+help.getPromoData#c0977421 = help.PromoData;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.PromoData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getProxyData b/data/corefork.telegram.org/method/help.getProxyData new file mode 100644 index 0000000000..9cc87ab252 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getProxyData @@ -0,0 +1,132 @@ + + + + + help.getProxyData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getProxyData

+ +

Get promotion info of the currently-used MTProxy

+

+ +
+
 Method schema is available as of layer 113. Switch »

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.ProxyData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getRecentMeUrls b/data/corefork.telegram.org/method/help.getRecentMeUrls new file mode 100644 index 0000000000..685ab96a66 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getRecentMeUrls @@ -0,0 +1,149 @@ + + + + + help.getRecentMeUrls + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getRecentMeUrls

+ +

Get recently used t.me links

+

+ +
+
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
+---functions---
+help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
refererstringReferer
+

Result

+

help.RecentMeUrls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getSupport b/data/corefork.telegram.org/method/help.getSupport new file mode 100644 index 0000000000..2e917ee440 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getSupport @@ -0,0 +1,134 @@ + + + + + help.getSupport + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getSupport

+ +

Returns the support user for the 'ask a question' feature.

+

+ +
+
help.support#17c6b5f6 phone_number:string user:User = help.Support;
+---functions---
+help.getSupport#9cdf08cd = help.Support;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.Support

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getSupportName b/data/corefork.telegram.org/method/help.getSupportName new file mode 100644 index 0000000000..dd21bb443d --- /dev/null +++ b/data/corefork.telegram.org/method/help.getSupportName @@ -0,0 +1,151 @@ + + + + + help.getSupportName + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getSupportName

+ +

Get localized name of the telegram support user

+

+ +
+
help.supportName#8c05f1c9 name:string = help.SupportName;
+---functions---
+help.getSupportName#d360e72c = help.SupportName;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.SupportName

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403USER_INVALIDInvalid user provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getTermsOfServiceUpdate b/data/corefork.telegram.org/method/help.getTermsOfServiceUpdate new file mode 100644 index 0000000000..5144e53488 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getTermsOfServiceUpdate @@ -0,0 +1,135 @@ + + + + + help.getTermsOfServiceUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getTermsOfServiceUpdate

+ +

Look for updates of telegram's terms of service

+

+ +
+
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+---functions---
+help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.TermsOfServiceUpdate

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getUserInfo b/data/corefork.telegram.org/method/help.getUserInfo new file mode 100644 index 0000000000..1e4ccc4699 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getUserInfo @@ -0,0 +1,167 @@ + + + + + help.getUserInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getUserInfo

+ +

Internal use

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+---functions---
+help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
+

Result

+

help.UserInfo

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403USER_INVALIDInvalid user provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.hidePromoData b/data/corefork.telegram.org/method/help.hidePromoData new file mode 100644 index 0000000000..3f9d1325cd --- /dev/null +++ b/data/corefork.telegram.org/method/help.hidePromoData @@ -0,0 +1,150 @@ + + + + + help.hidePromoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.hidePromoData

+ +

Hide MTProxy/Public Service Announcement information

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer to hide
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.saveAppLog b/data/corefork.telegram.org/method/help.saveAppLog new file mode 100644 index 0000000000..ac88d4ac8c --- /dev/null +++ b/data/corefork.telegram.org/method/help.saveAppLog @@ -0,0 +1,150 @@ + + + + + help.saveAppLog + + + + + + + + + + + + + +
+ +
+
+
+ +

help.saveAppLog

+ +

Saves logs of application on the server.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
eventsVector<InputAppEvent>List of input events
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.setBotUpdatesStatus b/data/corefork.telegram.org/method/help.setBotUpdatesStatus new file mode 100644 index 0000000000..4fbed62f8e --- /dev/null +++ b/data/corefork.telegram.org/method/help.setBotUpdatesStatus @@ -0,0 +1,156 @@ + + + + + help.setBotUpdatesStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

help.setBotUpdatesStatus

+ +

Informs the server about the number of pending bot updates if they haven't been processed for a long time; for bots only

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
pending_updates_countintNumber of pending updates
messagestringError message, if present
+

Result

+

Bool

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/initConnection.html b/data/corefork.telegram.org/method/initConnection.html new file mode 100644 index 0000000000..9af87099f6 --- /dev/null +++ b/data/corefork.telegram.org/method/initConnection.html @@ -0,0 +1,216 @@ + + + + + initConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

initConnection

+ +

Initialize connection

+

+ +
+
---functions---
+initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
api_idintApplication identifier (see. App configuration)
device_modelstringDevice model
system_versionstringOperation system version
app_versionstringApplication version
system_lang_codestringCode for the language used on the device's OS, ISO 639-1 standard
lang_packstringLanguage pack to use
lang_codestringCode for the language used on the client, ISO 639-1 standard
proxyflags.0?InputClientProxyInfo about an MTProto proxy
paramsflags.1?JSONValueAdditional initConnection parameters.
For now, only the tz_offset field is supported, for specifying timezone offset in seconds.
query!XThe query itself
+

Result

+

X

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CONNECTION_LAYER_INVALIDLayer invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeAfterMsg.html b/data/corefork.telegram.org/method/invokeAfterMsg.html new file mode 100644 index 0000000000..d4f6ccbb99 --- /dev/null +++ b/data/corefork.telegram.org/method/invokeAfterMsg.html @@ -0,0 +1,154 @@ + + + + + invokeAfterMsg + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeAfterMsg

+ +

Invokes a query after successfull completion of one of the previous queries.

+

+ +
+
---functions---
+invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idlongMessage identifier on which a current query depends
query!XThe query itself
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeAfterMsgs.html b/data/corefork.telegram.org/method/invokeAfterMsgs.html new file mode 100644 index 0000000000..12d1580407 --- /dev/null +++ b/data/corefork.telegram.org/method/invokeAfterMsgs.html @@ -0,0 +1,154 @@ + + + + + invokeAfterMsgs + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeAfterMsgs

+ +

Invokes a query after a successfull completion of previous queries

+

+ +
+
---functions---
+invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idsVector<long>List of messages on which a current query depends
query!XThe query itself
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeWithLayer.html b/data/corefork.telegram.org/method/invokeWithLayer.html new file mode 100644 index 0000000000..65853e125a --- /dev/null +++ b/data/corefork.telegram.org/method/invokeWithLayer.html @@ -0,0 +1,204 @@ + + + + + invokeWithLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithLayer

+ +

Invoke the specified query using the specified API layer

+

+ +
+
---functions---
+invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
layerintThe layer to use
query!XThe query
+

Result

+

X

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400CONNECTION_NOT_INITEDConnection not initialized.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400INVITE_HASH_EXPIREDThe invite link has expired.
+

Bots can use this method

+

Related pages

+

Calling API Methods

+

Additional options for calling methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeWithMessagesRange.html b/data/corefork.telegram.org/method/invokeWithMessagesRange.html new file mode 100644 index 0000000000..a7b17a0189 --- /dev/null +++ b/data/corefork.telegram.org/method/invokeWithMessagesRange.html @@ -0,0 +1,154 @@ + + + + + invokeWithMessagesRange + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithMessagesRange

+ +

Invoke with the given message range

+

+ +
+
---functions---
+invokeWithMessagesRange#365275f2 {X:Type} range:MessageRange query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
rangeMessageRangeMessage range
query!XQuery
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeWithTakeout.html b/data/corefork.telegram.org/method/invokeWithTakeout.html new file mode 100644 index 0000000000..61c95ebd81 --- /dev/null +++ b/data/corefork.telegram.org/method/invokeWithTakeout.html @@ -0,0 +1,154 @@ + + + + + invokeWithTakeout + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithTakeout

+ +

Invoke a method within a takeout session

+

+ +
+
---functions---
+invokeWithTakeout#aca9fd2e {X:Type} takeout_id:long query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
takeout_idlongTakeout session ID
query!XQuery
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeWithoutUpdates.html b/data/corefork.telegram.org/method/invokeWithoutUpdates.html new file mode 100644 index 0000000000..28f1236a6a --- /dev/null +++ b/data/corefork.telegram.org/method/invokeWithoutUpdates.html @@ -0,0 +1,154 @@ + + + + + invokeWithoutUpdates + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithoutUpdates

+ +

Invoke a request without subscribing the used connection for updates (this is enabled by default for file queries).

+

+ +
+
---functions---
+invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
query!XThe query
+

Result

+

X

+

Bots can use this method

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/langpack.getDifference b/data/corefork.telegram.org/method/langpack.getDifference new file mode 100644 index 0000000000..644c96bad5 --- /dev/null +++ b/data/corefork.telegram.org/method/langpack.getDifference @@ -0,0 +1,176 @@ + + + + + langpack.getDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getDifference

+ +

Get new strings in languagepack

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+---functions---
+langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack
lang_codestringLanguage code
from_versionintPrevious localization pack version
+

Result

+

LangPackDifference

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/langpack.getLangPack b/data/corefork.telegram.org/method/langpack.getLangPack new file mode 100644 index 0000000000..77c8d1af0a --- /dev/null +++ b/data/corefork.telegram.org/method/langpack.getLangPack @@ -0,0 +1,171 @@ + + + + + langpack.getLangPack + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLangPack

+ +

Get localization pack strings

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+---functions---
+langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
+

Result

+

LangPackDifference

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/langpack.getLanguage b/data/corefork.telegram.org/method/langpack.getLanguage new file mode 100644 index 0000000000..fbb7886d27 --- /dev/null +++ b/data/corefork.telegram.org/method/langpack.getLanguage @@ -0,0 +1,154 @@ + + + + + langpack.getLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLanguage

+ +

Get information about a language in a localization pack

+

+ +
+
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
+---functions---
+langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
+

Result

+

LangPackLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/langpack.getLanguages b/data/corefork.telegram.org/method/langpack.getLanguages new file mode 100644 index 0000000000..e5786fe847 --- /dev/null +++ b/data/corefork.telegram.org/method/langpack.getLanguages @@ -0,0 +1,165 @@ + + + + + langpack.getLanguages + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLanguages

+ +

Get information about all languages in a localization pack

+

+ +
+
---functions---
+langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack
+

Result

+

Vector<LangPackLanguage>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/langpack.getStrings b/data/corefork.telegram.org/method/langpack.getStrings new file mode 100644 index 0000000000..ebd86f8ffa --- /dev/null +++ b/data/corefork.telegram.org/method/langpack.getStrings @@ -0,0 +1,175 @@ + + + + + langpack.getStrings + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getStrings

+ +

Get strings from a language pack

+

+ +
+
---functions---
+langpack.getStrings#efea3803 lang_pack:string lang_code:string keys:Vector<string> = Vector<LangPackString>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
keysVector<string>Strings to get
+

Result

+

Vector<LangPackString>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.acceptEncryption b/data/corefork.telegram.org/method/messages.acceptEncryption new file mode 100644 index 0000000000..4e3b5976a0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.acceptEncryption @@ -0,0 +1,190 @@ + + + + + messages.acceptEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.acceptEncryption

+ +

Confirms creation of a secret chat

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+---functions---
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
g_bbytesB = g ^ b mod p, see Wikipedia
key_fingerprintlong64-bit fingerprint of the received key
+

Result

+

EncryptedChat

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400ENCRYPTION_ALREADY_ACCEPTEDSecret chat already accepted.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.acceptUrlAuth b/data/corefork.telegram.org/method/messages.acceptUrlAuth new file mode 100644 index 0000000000..f31aa4e580 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.acceptUrlAuth @@ -0,0 +1,179 @@ + + + + + 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.addChatUser b/data/corefork.telegram.org/method/messages.addChatUser new file mode 100644 index 0000000000..b51653ef4c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.addChatUser @@ -0,0 +1,237 @@ + + + + + messages.addChatUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.addChatUser

+ +

Adds a user to a chat and sends a service message on it.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
user_idInputUserUser ID to be added
fwd_limitintNumber of last messages to be forwarded
+

Result

+

messages.StatedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_IS_BLOCKEDYou were blocked by this user.
403USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
400YOU_BLOCKED_USERYou blocked this user.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.checkChatInvite b/data/corefork.telegram.org/method/messages.checkChatInvite new file mode 100644 index 0000000000..1c5cebfda5 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.checkChatInvite @@ -0,0 +1,178 @@ + + + + + messages.checkChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkChatInvite

+ +

Check the validity of a chat invite link and get basic info about it

+

+ +
+
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
+chatInvite#300c44c1 flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true request_needed:flags.6?true title:string about:flags.5?string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
+---functions---
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashstringInvite hash in t.me/joinchat/hash
+

Result

+

ChatInvite

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.checkHistoryImport b/data/corefork.telegram.org/method/messages.checkHistoryImport new file mode 100644 index 0000000000..e4daf1e70c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.checkHistoryImport @@ -0,0 +1,152 @@ + + + + + messages.checkHistoryImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkHistoryImport

+ +

Obtains information about a chat export file, generated by a foreign chat app, click here for more info about imported chats ».

+

+ +
+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+---functions---
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
import_headstringBeginning of the message file; up to 100 lines.
+

Result

+

messages.HistoryImportParsed

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.checkHistoryImportPeer b/data/corefork.telegram.org/method/messages.checkHistoryImportPeer new file mode 100644 index 0000000000..c82fa85911 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.checkHistoryImportPeer @@ -0,0 +1,172 @@ + + + + + messages.checkHistoryImportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkHistoryImportPeer

+ +

Check whether chat history exported from another chat app can be imported into a specific Telegram chat, click here for more info ».

+

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.

+

+ +
+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+---functions---
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where we want to import history ».
+

Result

+

messages.CheckedHistoryImportPeer

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

messages.CheckedHistoryImportPeer

+

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.clearAllDrafts b/data/corefork.telegram.org/method/messages.clearAllDrafts new file mode 100644 index 0000000000..c5a0386099 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.clearAllDrafts @@ -0,0 +1,138 @@ + + + + + messages.clearAllDrafts + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.clearAllDrafts

+ +

Clear all drafts.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.clearAllDrafts#7e58ee9c = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.clearRecentStickers b/data/corefork.telegram.org/method/messages.clearRecentStickers new file mode 100644 index 0000000000..065c4190fb --- /dev/null +++ b/data/corefork.telegram.org/method/messages.clearRecentStickers @@ -0,0 +1,155 @@ + + + + + messages.clearRecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.clearRecentStickers

+ +

Clear recent stickers

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueSet this flag to clear the list of stickers recently attached to photo or video files
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.createChat b/data/corefork.telegram.org/method/messages.createChat new file mode 100644 index 0000000000..900ccf0cf8 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.createChat @@ -0,0 +1,197 @@ + + + + + messages.createChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.createChat

+ +

Creates a new chat.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>List of user IDs to be invited
titlestringChat name
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_INVALIDInvalid chat.
400CHAT_TITLE_EMPTYNo chat title provided.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USERS_TOO_FEWNot enough users (to create a chat, for example).
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deleteChat b/data/corefork.telegram.org/method/messages.deleteChat new file mode 100644 index 0000000000..5b24a20134 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deleteChat @@ -0,0 +1,170 @@ + + + + + messages.deleteChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteChat

+ +

Delete a chat

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.deleteChat#5bd0ee50 chat_id:long = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deleteChatUser b/data/corefork.telegram.org/method/messages.deleteChatUser new file mode 100644 index 0000000000..feb16faefb --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deleteChatUser @@ -0,0 +1,208 @@ + + + + + messages.deleteChatUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteChatUser

+ +

Deletes a user from a chat and sends a service message on it.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revoke_historyflags.0?trueRemove the entire chat history of the specified user in this chat.
chat_idlongChat ID
user_idInputUserUser ID to be deleted
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deleteExportedChatInvite b/data/corefork.telegram.org/method/messages.deleteExportedChatInvite new file mode 100644 index 0000000000..4270f88e26 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deleteExportedChatInvite @@ -0,0 +1,155 @@ + + + + + messages.deleteExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteExportedChatInvite

+ +

Delete a chat invite

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
linkstringInvite link
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deleteHistory b/data/corefork.telegram.org/method/messages.deleteHistory new file mode 100644 index 0000000000..48a66a1d59 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deleteHistory @@ -0,0 +1,206 @@ + + + + + messages.deleteHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteHistory

+ +

Deletes communication history.

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+---functions---
+messages.deleteHistory#b08f922a flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int min_date:flags.2?int max_date:flags.3?int = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
just_clearflags.0?trueJust clear history for the current user, without actually removing messages for every chat user
revokeflags.1?trueWhether to delete the message history for all chat participants
peerInputPeerUser or chat, communication history of which will be deleted
max_idintMaximum ID of message to delete
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deleteMessages b/data/corefork.telegram.org/method/messages.deleteMessages new file mode 100644 index 0000000000..e56c6ade8d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deleteMessages @@ -0,0 +1,177 @@ + + + + + messages.deleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteMessages

+ +

Deletes messages by their identifiers.

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokeflags.0?trueWhether to delete messages for all participants of the chat
idVector<int>Message ID list
+

Result

+

The method returns the list of successfully deleted messages in Vector<int>.

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403MESSAGE_DELETE_FORBIDDENYou can't delete one of the messages you tried to delete, most likely because it is a service message.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deletePhoneCallHistory b/data/corefork.telegram.org/method/messages.deletePhoneCallHistory new file mode 100644 index 0000000000..948fe11822 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deletePhoneCallHistory @@ -0,0 +1,154 @@ + + + + + messages.deletePhoneCallHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deletePhoneCallHistory

+ +

Delete the entire phone call history.

+

+ +
+
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
+---functions---
+messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokeflags.0?trueWhether to remove phone call history for participants as well
+

Result

+

messages.AffectedFoundMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deleteRevokedExportedChatInvites b/data/corefork.telegram.org/method/messages.deleteRevokedExportedChatInvites new file mode 100644 index 0000000000..5dda69134c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deleteRevokedExportedChatInvites @@ -0,0 +1,155 @@ + + + + + messages.deleteRevokedExportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteRevokedExportedChatInvites

+ +

Delete all revoked chat invites

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
admin_idInputUserID of the admin that originally generated the revoked chat invites
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deleteScheduledMessages b/data/corefork.telegram.org/method/messages.deleteScheduledMessages new file mode 100644 index 0000000000..5383f8c152 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deleteScheduledMessages @@ -0,0 +1,160 @@ + + + + + messages.deleteScheduledMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteScheduledMessages

+ +

Delete scheduled messages

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.discardEncryption b/data/corefork.telegram.org/method/messages.discardEncryption new file mode 100644 index 0000000000..618c8c68b3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.discardEncryption @@ -0,0 +1,187 @@ + + + + + messages.discardEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.discardEncryption

+ +

Cancels a request for creation and/or delete info on secret chat.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
delete_historyflags.0?trueWhether to delete the entire chat history for the other user as well
chat_idintSecret chat ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_EMPTYThe provided chat ID is empty.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editChatAbout b/data/corefork.telegram.org/method/messages.editChatAbout new file mode 100644 index 0000000000..2232874e5c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editChatAbout @@ -0,0 +1,216 @@ + + + + + messages.editChatAbout + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatAbout

+ +

Edit the description of a group/supergroup/channel.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe group/supergroup/channel.
aboutstringThe new description
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ABOUT_NOT_MODIFIEDAbout text has not changed.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editChatAdmin b/data/corefork.telegram.org/method/messages.editChatAdmin new file mode 100644 index 0000000000..642b52aa3e --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editChatAdmin @@ -0,0 +1,195 @@ + + + + + messages.editChatAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatAdmin

+ +

Make a user admin in a legacy group.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongThe ID of the group
user_idInputUserThe user to make admin
is_adminBoolWhether to make him admin
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights b/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights new file mode 100644 index 0000000000..85f84d9fdd --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights @@ -0,0 +1,206 @@ + + + + + messages.editChatDefaultBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatDefaultBannedRights

+ +

Edit the default banned rights of a channel/supergroup/group.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer
banned_rightsChatBannedRightsThe new global rights
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BANNED_RIGHTS_INVALIDYou provided some invalid flags in the banned rights.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
400UNTIL_DATE_INVALIDInvalid until date provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editChatPhoto b/data/corefork.telegram.org/method/messages.editChatPhoto new file mode 100644 index 0000000000..5fb4b4f20e --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editChatPhoto @@ -0,0 +1,203 @@ + + + + + messages.editChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatPhoto

+ +

Changes chat photo and sends a service message on it

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
photoInputChatPhotoPhoto to be set
+

Result

+

Returns a messages.StatedMessage object containing a service message sent during an action.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALIDPhoto invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editChatTitle b/data/corefork.telegram.org/method/messages.editChatTitle new file mode 100644 index 0000000000..02bc92123b --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editChatTitle @@ -0,0 +1,193 @@ + + + + + messages.editChatTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatTitle

+ +

Chanages chat name and sends a service message on it.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatTitle#73783ffd chat_id:long title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
titlestringNew chat name, different from the old one
+

Result

+

Returns a messages.StatedMessage object containing a service message sent during an action.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editExportedChatInvite b/data/corefork.telegram.org/method/messages.editExportedChatInvite new file mode 100644 index 0000000000..bd8e093c4f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editExportedChatInvite @@ -0,0 +1,193 @@ + + + + + messages.editExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editExportedChatInvite

+ +

Edit an exported chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+---functions---
+messages.editExportedChatInvite#bdca2f75 flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int request_needed:flags.3?Bool title:flags.4?string = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.2?trueWhether to revoke the chat invite
peerInputPeerChat
linkstringInvite link
expire_dateflags.0?intNew expiration date
usage_limitflags.1?intMaximum number of users that can join using this link
+

Result

+

messages.ExportedChatInvite

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editInlineBotMessage b/data/corefork.telegram.org/method/messages.editInlineBotMessage new file mode 100644 index 0000000000..291f43491b --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editInlineBotMessage @@ -0,0 +1,206 @@ + + + + + messages.editInlineBotMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editInlineBotMessage

+ +

Edit an inline bot message

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable webpage preview
idInputBotInlineMessageIDSent inline message ID
messageflags.11?stringMessage
mediaflags.14?InputMediaMedia
reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_NOT_MODIFIEDThe message text has not changed.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editMessage b/data/corefork.telegram.org/method/messages.editMessage new file mode 100644 index 0000000000..0f19135afa --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editMessage @@ -0,0 +1,338 @@ + + + + + messages.editMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editMessage

+ +

Edit message

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable webpage preview
peerInputPeerWhere was the message sent
idintID of the message to edit
messageflags.11?stringNew message
mediaflags.14?InputMediaNew attached media
reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.15?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400ENTITIES_TOO_LONGYou provided too many styled message entities.
403INLINE_BOT_REQUIREDOnly the inline bot can edit message.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_GROUPED_INVALIDYou tried to send media of different types in an album.
400MEDIA_NEW_INVALIDThe new media is invalid.
400MEDIA_PREV_INVALIDPrevious media invalid.
403MESSAGE_AUTHOR_REQUIREDMessage author required.
400MESSAGE_EDIT_TIME_EXPIREDYou can't edit this message anymore, too much time has passed since its creation.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_NOT_MODIFIEDThe message text has not changed.
400MESSAGE_TOO_LONGThe provided message is too long.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.exportChatInvite b/data/corefork.telegram.org/method/messages.exportChatInvite new file mode 100644 index 0000000000..19c5969170 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.exportChatInvite @@ -0,0 +1,217 @@ + + + + + messages.exportChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportChatInvite

+ +

Export an invite link for a chat

+

+ +
+
chatInviteExported#ab4a819 flags:# revoked:flags.0?true permanent:flags.5?true request_needed:flags.6?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 requested:flags.7?int title:flags.8?string = ExportedChatInvite;
+---functions---
+messages.exportChatInvite#a02ce5d5 flags:# legacy_revoke_permanent:flags.2?true request_needed:flags.3?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int title:flags.4?string = ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
legacy_revoke_permanentflags.2?trueLegacy flag, reproducing legacy behavior of this method: if set, revokes all previous links before creating a new one. Kept for bot API BC, should not be used by modern clients.
peerInputPeerChat
expire_dateflags.0?intExpiration date
usage_limitflags.1?intMaximum number of users that can join using this link
+

Result

+

ExportedChatInvite

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400EXPIRE_DATE_INVALIDThe specified expiration date is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USAGE_LIMIT_INVALIDThe specified usage limit is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.faveSticker b/data/corefork.telegram.org/method/messages.faveSticker new file mode 100644 index 0000000000..23d9f16e0d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.faveSticker @@ -0,0 +1,172 @@ + + + + + messages.faveSticker + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.faveSticker

+ +

Mark a sticker as favorite

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputDocumentSticker to mark as favorite
unfaveBoolUnfavorite
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.forwardMessage b/data/corefork.telegram.org/method/messages.forwardMessage new file mode 100644 index 0000000000..22d984f418 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.forwardMessage @@ -0,0 +1,177 @@ + + + + + messages.forwardMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.forwardMessage

+ +

Forwards single messages.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerUser or chat where a message will be forwarded
idintForwarded message ID
random_idlongUnique client message ID required to prevent message resending
+

Result

+

messages.StatedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid
400MESSAGE_ID_INVALIDThe provided message id is invalid
400PEER_ID_INVALIDThe provided peer id is invalid
400YOU_BLOCKED_USERYou blocked this user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.forwardMessages b/data/corefork.telegram.org/method/messages.forwardMessages new file mode 100644 index 0000000000..2b558b304f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.forwardMessages @@ -0,0 +1,363 @@ + + + + + messages.forwardMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.forwardMessages

+ +

Forwards messages by their IDs.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.forwardMessages#cc30290b 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 noforwards:flags.14?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send messages silently (no notification will be triggered on the destination clients)
backgroundflags.6?trueWhether to send the message in background
with_my_scoreflags.8?trueWhen forwarding games, whether to include your score in the game
drop_authorflags.11?trueWhether to forward messages without quoting the original author
drop_media_captionsflags.12?trueWhether to strip captions from media
from_peerInputPeerSource of messages
idVector<int>IDs of messages
random_idVector<long>Random ID to prevent resending of messages
to_peerInputPeerDestination peer
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400GROUPED_MEDIA_INVALIDInvalid grouped media.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
420P0NY_FLOODWAIT 
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_INVALIDA provided random ID is invalid.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
400SLOWMODE_MULTI_MSGS_DISABLEDSlowmode is enabled, you cannot forward multiple messages to this group.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getAdminsWithInvites b/data/corefork.telegram.org/method/messages.getAdminsWithInvites new file mode 100644 index 0000000000..43c0a7bfc5 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getAdminsWithInvites @@ -0,0 +1,149 @@ + + + + + messages.getAdminsWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAdminsWithInvites

+ +

Get info about chat invites generated by admins.

+

+ +
+
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
+---functions---
+messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
+

Result

+

messages.ChatAdminsWithInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getAllChats b/data/corefork.telegram.org/method/messages.getAllChats new file mode 100644 index 0000000000..a89f4be62f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getAllChats @@ -0,0 +1,150 @@ + + + + + messages.getAllChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAllChats

+ +

Get all chats, channels and supergroups

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
except_idsVector<long>Except these chats/channels/supergroups
+

Result

+

messages.Chats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getAllDrafts b/data/corefork.telegram.org/method/messages.getAllDrafts new file mode 100644 index 0000000000..a411a66c0c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getAllDrafts @@ -0,0 +1,143 @@ + + + + + messages.getAllDrafts + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAllDrafts

+ +

Save get all message drafts.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.getAllDrafts#6a3f8d65 = Updates;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Updates, contains all the latest updateDraftMessage updates related to all chats with drafts.

+

Related pages

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getAllStickers b/data/corefork.telegram.org/method/messages.getAllStickers new file mode 100644 index 0000000000..112734868b --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getAllStickers @@ -0,0 +1,153 @@ + + + + + messages.getAllStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAllStickers

+ +

Get all installed stickers

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+---functions---
+messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.AllStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getArchivedStickers b/data/corefork.telegram.org/method/messages.getArchivedStickers new file mode 100644 index 0000000000..3ec1016eb7 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getArchivedStickers @@ -0,0 +1,167 @@ + + + + + messages.getArchivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getArchivedStickers

+ +

Get all archived stickers

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
+---functions---
+messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueGet mask stickers
offset_idlongOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
+

Result

+

messages.ArchivedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getAttachedStickers b/data/corefork.telegram.org/method/messages.getAttachedStickers new file mode 100644 index 0000000000..427d99a2c8 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getAttachedStickers @@ -0,0 +1,148 @@ + + + + + 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.getAvailableReactions b/data/corefork.telegram.org/method/messages.getAvailableReactions new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getAvailableReactions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getBotCallbackAnswer b/data/corefork.telegram.org/method/messages.getBotCallbackAnswer new file mode 100644 index 0000000000..37f1b4679a --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getBotCallbackAnswer @@ -0,0 +1,226 @@ + + + + + messages.getBotCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getBotCallbackAnswer

+ +

Press an inline callback button and get a callback answer from the bot

+

+ +
+
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+---functions---
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
gameflags.1?trueWhether this is a "play game" button
peerInputPeerWhere was the inline keyboard sent
msg_idintID of the Message with the inline keyboard
dataflags.0?bytesCallback data
passwordflags.2?InputCheckPasswordSRPFor buttons requiring you to verify your identity with your 2FA password, the SRP payload generated using SRP.
+

Result

+

messages.BotCallbackAnswer

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400DATA_INVALIDEncrypted data invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-503TimeoutTimeout while fetching data.
+

Related pages

+

keyboardButtonCallback

+

Callback button

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getChatInviteImporters b/data/corefork.telegram.org/method/messages.getChatInviteImporters new file mode 100644 index 0000000000..e684d01121 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getChatInviteImporters @@ -0,0 +1,172 @@ + + + + + messages.getChatInviteImporters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getChatInviteImporters

+ +

Get info about the users that joined the chat using a specific chat invite

+

+ +
+
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+---functions---
+messages.getChatInviteImporters#df04dd4e flags:# requested:flags.0?true peer:InputPeer link:flags.1?string q:flags.2?string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
linkstringInvite link
offset_dateintOffsets for pagination, for more info click here
offset_userInputUserUser ID for pagination
limitintMaximum number of results to return, see pagination
+

Result

+

messages.ChatInviteImporters

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getChats b/data/corefork.telegram.org/method/messages.getChats new file mode 100644 index 0000000000..aaed7cd56e --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getChats @@ -0,0 +1,173 @@ + + + + + messages.getChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getChats

+ +

Returns chat basic info on their IDs.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+messages.getChats#49e9528f id:Vector<long> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<long>List of chat IDs
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getCommonChats b/data/corefork.telegram.org/method/messages.getCommonChats new file mode 100644 index 0000000000..802cc6edd9 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getCommonChats @@ -0,0 +1,185 @@ + + + + + messages.getCommonChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getCommonChats

+ +

Get chats in common with a user

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
max_idlongMaximum ID of chat to return (see pagination)
limitintMaximum number of results to return, see pagination
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getDhConfig b/data/corefork.telegram.org/method/messages.getDhConfig new file mode 100644 index 0000000000..011b820259 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getDhConfig @@ -0,0 +1,175 @@ + + + + + messages.getDhConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDhConfig

+ +

Returns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.

+

+ +
+
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
+messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
+---functions---
+messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
versionintValue of the version parameter from messages.dhConfig, avialable at the client
random_lengthintLength of the required random sequence
+

Result

+

messages.DhConfig

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400RANDOM_LENGTH_INVALIDRandom length invalid.
+

Related pages

+

messages.dhConfig

+

New set of configuring parameters.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getDialogFilters b/data/corefork.telegram.org/method/messages.getDialogFilters new file mode 100644 index 0000000000..cc262f566d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getDialogFilters @@ -0,0 +1,136 @@ + + + + + messages.getDialogFilters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDialogFilters

+ +

Get folders

+

+ +
+
---functions---
+messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<DialogFilter>

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getDialogUnreadMarks b/data/corefork.telegram.org/method/messages.getDialogUnreadMarks new file mode 100644 index 0000000000..d698620e33 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getDialogUnreadMarks @@ -0,0 +1,133 @@ + + + + + messages.getDialogUnreadMarks + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDialogUnreadMarks

+ +

Get dialogs manually marked as unread

+

+ +
+
---functions---
+messages.getDialogUnreadMarks#22e24e22 = Vector<DialogPeer>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<DialogPeer>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getDiscussionMessage b/data/corefork.telegram.org/method/messages.getDiscussionMessage new file mode 100644 index 0000000000..610c1de224 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getDiscussionMessage @@ -0,0 +1,183 @@ + + + + + messages.getDiscussionMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDiscussionMessage

+ +

Get discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group

+

+ +
+
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
+---functions---
+messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChannel ID
msg_idintMessage ID
+

Result

+

messages.DiscussionMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getDocumentByHash b/data/corefork.telegram.org/method/messages.getDocumentByHash new file mode 100644 index 0000000000..29f8212cb8 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getDocumentByHash @@ -0,0 +1,178 @@ + + + + + messages.getDocumentByHash + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDocumentByHash

+ +

Get a document by its SHA256 hash, mainly used for gifs

+

+ +
+
documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+---functions---
+messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
sha256bytesSHA256 of file
sizeintSize of the file in bytes
mime_typestringMime type
+

Result

+

Document

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400SHA256_HASH_INVALIDThe provided SHA256 hash is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getEmojiKeywords b/data/corefork.telegram.org/method/messages.getEmojiKeywords new file mode 100644 index 0000000000..54c35573b3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getEmojiKeywords @@ -0,0 +1,149 @@ + + + + + messages.getEmojiKeywords + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiKeywords

+ +

Get localized emoji keywords

+

+ +
+
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+---functions---
+messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Result

+

EmojiKeywordsDifference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference b/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference new file mode 100644 index 0000000000..38fc7adcb0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference @@ -0,0 +1,154 @@ + + + + + messages.getEmojiKeywordsDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiKeywordsDifference

+ +

Get changed emoji keywords

+

+ +
+
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+---functions---
+messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious emoji keyword localization version
+

Result

+

EmojiKeywordsDifference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getEmojiKeywordsLanguages b/data/corefork.telegram.org/method/messages.getEmojiKeywordsLanguages new file mode 100644 index 0000000000..e8886c105d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getEmojiKeywordsLanguages @@ -0,0 +1,148 @@ + + + + + messages.getEmojiKeywordsLanguages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiKeywordsLanguages

+ +

Get info about an emoji keyword localization

+

+ +
+
---functions---
+messages.getEmojiKeywordsLanguages#4e9963b2 lang_codes:Vector<string> = Vector<EmojiLanguage>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codesVector<string>Language codes
+

Result

+

Vector<EmojiLanguage>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getEmojiURL b/data/corefork.telegram.org/method/messages.getEmojiURL new file mode 100644 index 0000000000..69fec3b7ba --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getEmojiURL @@ -0,0 +1,149 @@ + + + + + messages.getEmojiURL + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiURL

+ +

Returns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

+

+ +
+
emojiURL#a575739d url:string = EmojiURL;
+---functions---
+messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code for which the emoji replacements will be suggested
+

Result

+

EmojiURL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getExportedChatInvite b/data/corefork.telegram.org/method/messages.getExportedChatInvite new file mode 100644 index 0000000000..a6d561a1c0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getExportedChatInvite @@ -0,0 +1,155 @@ + + + + + messages.getExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getExportedChatInvite

+ +

Get info about a chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+---functions---
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
linkstringInvite link
+

Result

+

messages.ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getExportedChatInvites b/data/corefork.telegram.org/method/messages.getExportedChatInvites new file mode 100644 index 0000000000..397ac8c5e4 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getExportedChatInvites @@ -0,0 +1,182 @@ + + + + + messages.getExportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getExportedChatInvites

+ +

Get info about the chat invites of a specific chat

+

+ +
+
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
+---functions---
+messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.3?trueWhether to fetch revoked chat invites
peerInputPeerChat
admin_idInputUserWhether to only fetch chat invites from this admin
offset_dateflags.2?intOffsets for pagination, for more info click here
offset_linkflags.2?stringOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
+

Result

+

messages.ExportedChatInvites

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getFavedStickers b/data/corefork.telegram.org/method/messages.getFavedStickers new file mode 100644 index 0000000000..828ce469d9 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getFavedStickers @@ -0,0 +1,153 @@ + + + + + messages.getFavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getFavedStickers

+ +

Get faved stickers

+

+ +
+
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+---functions---
+messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.FavedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getFeaturedStickers b/data/corefork.telegram.org/method/messages.getFeaturedStickers new file mode 100644 index 0000000000..aec5d79000 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getFeaturedStickers @@ -0,0 +1,153 @@ + + + + + messages.getFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getFeaturedStickers

+ +

Get featured stickers

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+---functions---
+messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.FeaturedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getFullChat b/data/corefork.telegram.org/method/messages.getFullChat new file mode 100644 index 0000000000..bbffa3d029 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getFullChat @@ -0,0 +1,172 @@ + + + + + messages.getFullChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getFullChat

+ +

Returns full chat info according to its ID.

+

+ +
+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
+---functions---
+messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
+

Result

+

messages.ChatFull

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getGameHighScores b/data/corefork.telegram.org/method/messages.getGameHighScores new file mode 100644 index 0000000000..df5ba57f82 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getGameHighScores @@ -0,0 +1,187 @@ + + + + + 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 new file mode 100644 index 0000000000..bdf413e405 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getHistory @@ -0,0 +1,232 @@ + + + + + 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.getInlineBotResults b/data/corefork.telegram.org/method/messages.getInlineBotResults new file mode 100644 index 0000000000..701f2ab7d6 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getInlineBotResults @@ -0,0 +1,226 @@ + + + + + messages.getInlineBotResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getInlineBotResults

+ +

Query an inline bot

+

+ +
+
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
+---functions---
+messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
botInputUserThe bot to query
peerInputPeerThe currently opened chat
geo_pointflags.0?InputGeoPointThe geolocation, if requested
querystringThe query
offsetstringThe offset within the results, will be passed directly as-is to the bot.
+

Result

+

messages.BotResults

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_INLINE_DISABLEDThis bot can't be used in inline mode.
400BOT_INVALIDThis is not a valid bot.
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
-503TimeoutTimeout while fetching data.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getInlineGameHighScores b/data/corefork.telegram.org/method/messages.getInlineGameHighScores new file mode 100644 index 0000000000..0a5909de87 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getInlineGameHighScores @@ -0,0 +1,177 @@ + + + + + messages.getInlineGameHighScores + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getInlineGameHighScores

+ +

Get highscores of a game sent using an inline bot

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+---functions---
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputBotInlineMessageIDID of inline message
user_idInputUserGet high scores of a certain user
+

Result

+

messages.HighScores

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getMaskStickers b/data/corefork.telegram.org/method/messages.getMaskStickers new file mode 100644 index 0000000000..9dd619a4aa --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getMaskStickers @@ -0,0 +1,153 @@ + + + + + messages.getMaskStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMaskStickers

+ +

Get installed mask stickers

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+---functions---
+messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.AllStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getMessageEditData b/data/corefork.telegram.org/method/messages.getMessageEditData new file mode 100644 index 0000000000..818228c350 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getMessageEditData @@ -0,0 +1,186 @@ + + + + + messages.getMessageEditData + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessageEditData

+ +

Find out if a media message's caption can be edited

+

+ +
+
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
+---functions---
+messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where the media was sent
idintID of message
+

Result

+

messages.MessageEditData

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403MESSAGE_AUTHOR_REQUIREDMessage author required.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getMessageReactionsList b/data/corefork.telegram.org/method/messages.getMessageReactionsList new file mode 100644 index 0000000000..bb55d797c3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getMessageReactionsList @@ -0,0 +1,180 @@ + + + + + messages.getMessageReactionsList + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessageReactionsList

+ +

Get full message reaction list

+

+ +
+
messages.messageReactionsList#31bd492d flags:# count:int reactions:Vector<MessagePeerReaction> chats:Vector<Chat> users:Vector<User> next_offset:flags.0?string = messages.MessageReactionsList;
+---functions---
+messages.getMessageReactionsList#e0ee6b77 flags:# peer:InputPeer id:int reaction:flags.0?string offset:flags.1?string limit:int = messages.MessageReactionsList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerPeer
idintMessage ID
reactionflags.0?stringGet only reactions of this type (UTF8 emoji)
offsetflags.1?stringOffset (typically taken from the next_offset field of the returned MessageReactionsList)
limitintMaximum number of results to return, see pagination
+

Result

+

MessageReactionsList

+

Bots can use this method

+

Related pages

+

MessageReactionsList

+

List of message reactions

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getMessageReadParticipants b/data/corefork.telegram.org/method/messages.getMessageReadParticipants new file mode 100644 index 0000000000..92a2fea45a --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getMessageReadParticipants @@ -0,0 +1,173 @@ + + + + + messages.getMessageReadParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessageReadParticipants

+ +

Get which users read a specific message: only available for groups and supergroups with less than chat_read_mark_size_threshold members, read receipts will be stored for chat_read_mark_expire_period seconds after the message was sent, see client configuration for more info ».

+

+ +
+
---functions---
+messages.getMessageReadParticipants#2c6f97b7 peer:InputPeer msg_id:int = Vector<long>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerDialog
msg_idintMessage ID
+

Result

+

Vector<long>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_TOO_BIGThis method is not available for groups with more than chat_read_mark_size_threshold members, see client configuration ».
+

Related pages

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getMessages b/data/corefork.telegram.org/method/messages.getMessages new file mode 100644 index 0000000000..7bcd268092 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getMessages @@ -0,0 +1,153 @@ + + + + + messages.getMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessages

+ +

Returns the list of messages by their IDs.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputMessage>Message ID list
+

Result

+

messages.Messages

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getMessagesReactions b/data/corefork.telegram.org/method/messages.getMessagesReactions new file mode 100644 index 0000000000..fc5ea36930 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getMessagesReactions @@ -0,0 +1,161 @@ + + + + + messages.getMessagesReactions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessagesReactions

+ +

Get message reactions

+

+ +
+
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.getMessagesReactions#8bba90e6 peer:InputPeer id:Vector<int> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>Message IDs
+

Result

+

Updates

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getMessagesViews b/data/corefork.telegram.org/method/messages.getMessagesViews new file mode 100644 index 0000000000..d846de198f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getMessagesViews @@ -0,0 +1,199 @@ + + + + + messages.getMessagesViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessagesViews

+ +

Get and increase the view counter of a message sent or forwarded from a channel

+

+ +
+
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
+---functions---
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where the message was found
idVector<int>ID of message
incrementBoolWhether to mark the message as viewed and increment the view counter
+

Result

+

Vector<int>

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getOldFeaturedStickers b/data/corefork.telegram.org/method/messages.getOldFeaturedStickers new file mode 100644 index 0000000000..76732ba9ce --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getOldFeaturedStickers @@ -0,0 +1,163 @@ + + + + + messages.getOldFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getOldFeaturedStickers

+ +

Method for fetching previously featured stickers

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+---functions---
+messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

messages.FeaturedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getOnlines b/data/corefork.telegram.org/method/messages.getOnlines new file mode 100644 index 0000000000..42a946da25 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getOnlines @@ -0,0 +1,171 @@ + + + + + messages.getOnlines + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getOnlines

+ +

Get count of online users in a chat

+

+ +
+
chatOnlines#f041e250 onlines:int = ChatOnlines;
+---functions---
+messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat
+

Result

+

ChatOnlines

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getPeerDialogs b/data/corefork.telegram.org/method/messages.getPeerDialogs new file mode 100644 index 0000000000..510f82cc3c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getPeerDialogs @@ -0,0 +1,181 @@ + + + + + messages.getPeerDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getPeerDialogs

+ +

Get dialog info of specified peers

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+---functions---
+messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peersVector<InputDialogPeer>Peers
+

Result

+

messages.PeerDialogs

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getPeerSettings b/data/corefork.telegram.org/method/messages.getPeerSettings new file mode 100644 index 0000000000..1de97f0da6 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getPeerSettings @@ -0,0 +1,171 @@ + + + + + messages.getPeerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getPeerSettings

+ +

Get peer settings

+

+ +
+
messages.peerSettings#6880b94d settings:PeerSettings chats:Vector<Chat> users:Vector<User> = messages.PeerSettings;
+---functions---
+messages.getPeerSettings#efd9a6a2 peer:InputPeer = messages.PeerSettings;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer
+

Result

+

PeerSettings

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getPinnedDialogs b/data/corefork.telegram.org/method/messages.getPinnedDialogs new file mode 100644 index 0000000000..de615822e2 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getPinnedDialogs @@ -0,0 +1,169 @@ + + + + + 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 new file mode 100644 index 0000000000..8bcf6627bc --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getPollResults @@ -0,0 +1,177 @@ + + + + + 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.getPollVotes b/data/corefork.telegram.org/method/messages.getPollVotes new file mode 100644 index 0000000000..dd3c3b3eee --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getPollVotes @@ -0,0 +1,204 @@ + + + + + messages.getPollVotes + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getPollVotes

+ +

Get poll results for non-anonymous polls

+

+ +
+
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
+---functions---
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerChat where the poll was sent
idintMessage ID
optionflags.0?bytesGet only results for the specified poll option
offsetflags.1?stringOffset for results, taken from the next_offset field of messages.votesList, initially an empty string.
Note: if no more results are available, the method call will return an empty next_offset; thus, avoid providing the next_offset returned in messages.votesList if it is empty, to avoid an infinite loop.
limitintNumber of results to return
+

Result

+

messages.VotesList

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
403BROADCAST_FORBIDDENParticipants of polls in channels should stay anonymous.
400MSG_ID_INVALIDInvalid message ID provided.
403POLL_VOTE_REQUIREDCast a vote in the poll before calling this method.
+

Related pages

+

messages.votesList

+

How users voted in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getRecentLocations b/data/corefork.telegram.org/method/messages.getRecentLocations new file mode 100644 index 0000000000..6bd24461b2 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getRecentLocations @@ -0,0 +1,165 @@ + + + + + messages.getRecentLocations + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getRecentLocations

+ +

Get live location history of a certain user

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerUser
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

messages.Messages

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getRecentStickers b/data/corefork.telegram.org/method/messages.getRecentStickers new file mode 100644 index 0000000000..b19a14b6b1 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getRecentStickers @@ -0,0 +1,163 @@ + + + + + messages.getRecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getRecentStickers

+ +

Get recent stickers

+

+ +
+
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
+messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
+---functions---
+messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueGet stickers recently attached to photo or video files
hashlongHash for pagination, for more info click here
+

Result

+

messages.RecentStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getReplies b/data/corefork.telegram.org/method/messages.getReplies new file mode 100644 index 0000000000..99ba37366d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getReplies @@ -0,0 +1,217 @@ + + + + + messages.getReplies + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getReplies

+ +

Get messages in a reply thread

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
msg_idintMessage ID
offset_idintOffsets for pagination, for more info click here
offset_dateintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintIf a positive value was transferred, the method will return only messages with ID smaller than max_id
min_idintIf a positive value was transferred, the method will return only messages with ID bigger than min_id
hashlongHash for pagination, for more info click here
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getSavedGifs b/data/corefork.telegram.org/method/messages.getSavedGifs new file mode 100644 index 0000000000..9023faf994 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getSavedGifs @@ -0,0 +1,153 @@ + + + + + messages.getSavedGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getSavedGifs

+ +

Get saved GIFs

+

+ +
+
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
+messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
+---functions---
+messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.SavedGifs

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getScheduledHistory b/data/corefork.telegram.org/method/messages.getScheduledHistory new file mode 100644 index 0000000000..45d8596408 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getScheduledHistory @@ -0,0 +1,182 @@ + + + + + messages.getScheduledHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getScheduledHistory

+ +

Get scheduled messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
hashlongHash for pagination, for more info click here
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getScheduledMessages b/data/corefork.telegram.org/method/messages.getScheduledMessages new file mode 100644 index 0000000000..a85119f842 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getScheduledMessages @@ -0,0 +1,179 @@ + + + + + messages.getScheduledMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getScheduledMessages

+ +

Get scheduled messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>IDs of scheduled messages
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getSearchCounters b/data/corefork.telegram.org/method/messages.getSearchCounters new file mode 100644 index 0000000000..412ba49c1e --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getSearchCounters @@ -0,0 +1,173 @@ + + + + + messages.getSearchCounters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getSearchCounters

+ +

Get the number of results that would be found by a messages.search call with the same parameters

+

+ +
+
---functions---
+messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where to search
filtersVector<MessagesFilter>Search filters
+

Result

+

Vector<messages.SearchCounter>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

messages.search

+

Gets back found messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getSearchResultsCalendar b/data/corefork.telegram.org/method/messages.getSearchResultsCalendar new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getSearchResultsCalendar @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getSearchResultsPositions b/data/corefork.telegram.org/method/messages.getSearchResultsPositions new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getSearchResultsPositions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getStickerSet b/data/corefork.telegram.org/method/messages.getStickerSet new file mode 100644 index 0000000000..86e949726f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getStickerSet @@ -0,0 +1,173 @@ + + + + + messages.getStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getStickerSet

+ +

Get info about a stickerset

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+messages.stickerSetNotModified#d3f924eb = messages.StickerSet;
+---functions---
+messages.getStickerSet#c8a0ec74 stickerset:InputStickerSet hash:int = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetStickerset
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMOTICON_STICKERPACK_MISSING 
400STICKERSET_INVALIDThe provided sticker set is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getStickers b/data/corefork.telegram.org/method/messages.getStickers new file mode 100644 index 0000000000..02c786b578 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getStickers @@ -0,0 +1,175 @@ + + + + + messages.getStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getStickers

+ +

Get stickers by emoji

+

+ +
+
messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
+---functions---
+messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringThe emoji
hashlongHash for pagination, for more info click here
+

Result

+

messages.Stickers

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400EMOTICON_EMPTYThe emoji is empty.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getSuggestedDialogFilters b/data/corefork.telegram.org/method/messages.getSuggestedDialogFilters new file mode 100644 index 0000000000..d104d63187 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getSuggestedDialogFilters @@ -0,0 +1,136 @@ + + + + + messages.getSuggestedDialogFilters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getSuggestedDialogFilters

+ +

Get suggested folders

+

+ +
+
---functions---
+messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<DialogFilterSuggested>

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getUnreadMentions b/data/corefork.telegram.org/method/messages.getUnreadMentions new file mode 100644 index 0000000000..4e0db1dc71 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getUnreadMentions @@ -0,0 +1,212 @@ + + + + + messages.getUnreadMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getUnreadMentions

+ +

Get unread messages where we were mentioned

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where to look for mentions
offset_idintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintMaximum message ID to return, see pagination
min_idintMinimum message ID to return, see pagination
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getUnreadReactions b/data/corefork.telegram.org/method/messages.getUnreadReactions new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getUnreadReactions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getWebPage b/data/corefork.telegram.org/method/messages.getWebPage new file mode 100644 index 0000000000..627a58a74a --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getWebPage @@ -0,0 +1,177 @@ + + + + + messages.getWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getWebPage

+ +

Get instant view page

+

+ +
+
webPageEmpty#eb1477e8 id:long = WebPage;
+webPagePending#c586da1c id:long date:int = WebPage;
+webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
+---functions---
+messages.getWebPage#32ca8f91 url:string hash:int = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL of IV page to fetch
hashintHash for pagination, for more info click here
+

Result

+

WebPage

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WC_CONVERT_URL_INVALIDWC convert URL invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getWebPagePreview b/data/corefork.telegram.org/method/messages.getWebPagePreview new file mode 100644 index 0000000000..0839f71f2c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getWebPagePreview @@ -0,0 +1,191 @@ + + + + + messages.getWebPagePreview + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getWebPagePreview

+ +

Get preview of webpage

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+---functions---
+messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringMessage from which to extract the preview
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
+

Result

+

MessageMedia

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty.
+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.hideAllChatJoinRequests b/data/corefork.telegram.org/method/messages.hideAllChatJoinRequests new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.hideAllChatJoinRequests @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.hideChatJoinRequest b/data/corefork.telegram.org/method/messages.hideChatJoinRequest new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.hideChatJoinRequest @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.hidePeerSettingsBar b/data/corefork.telegram.org/method/messages.hidePeerSettingsBar new file mode 100644 index 0000000000..4c1a945072 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.hidePeerSettingsBar @@ -0,0 +1,153 @@ + + + + + messages.hidePeerSettingsBar + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.hidePeerSettingsBar

+ +

Should be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
+

Result

+

Bool

+

Related pages

+

peerSettings

+

Peer settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.importChatInvite b/data/corefork.telegram.org/method/messages.importChatInvite new file mode 100644 index 0000000000..2d9c45b648 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.importChatInvite @@ -0,0 +1,227 @@ + + + + + messages.importChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.importChatInvite

+ +

Import a chat invite and join a private chat/supergroup/channel

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.importChatInvite#6c50051c hash:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashstringhash from t.me/joinchat/hash
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_INVALIDInvalid chat.
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.initHistoryImport b/data/corefork.telegram.org/method/messages.initHistoryImport new file mode 100644 index 0000000000..7643c59d2d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.initHistoryImport @@ -0,0 +1,191 @@ + + + + + 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.installStickerSet b/data/corefork.telegram.org/method/messages.installStickerSet new file mode 100644 index 0000000000..a016b2020d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.installStickerSet @@ -0,0 +1,172 @@ + + + + + messages.installStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.installStickerSet

+ +

Install a stickerset

+

+ +
+
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
+messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
+---functions---
+messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetStickerset to install
archivedBoolWhether to archive stickerset
+

Result

+

messages.StickerSetInstallResult

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.markDialogUnread b/data/corefork.telegram.org/method/messages.markDialogUnread new file mode 100644 index 0000000000..6f3364d5a3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.markDialogUnread @@ -0,0 +1,160 @@ + + + + + messages.markDialogUnread + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.markDialogUnread

+ +

Manually mark dialog as unread

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueMark as unread/read
peerInputDialogPeerDialog
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.migrateChat b/data/corefork.telegram.org/method/messages.migrateChat new file mode 100644 index 0000000000..298a801a96 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.migrateChat @@ -0,0 +1,190 @@ + + + + + messages.migrateChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.migrateChat

+ +

Turn a legacy group into a supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.migrateChat#a2875319 chat_id:long = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongLegacy group to migrate
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
403CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.readDiscussion b/data/corefork.telegram.org/method/messages.readDiscussion new file mode 100644 index 0000000000..8e6210f618 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readDiscussion @@ -0,0 +1,180 @@ + + + + + messages.readDiscussion + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readDiscussion

+ +

Mark a thread as read

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerGroup ID
msg_idintID of message that started the thread
read_max_idintID up to which thread messages were read
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.readEncryptedHistory b/data/corefork.telegram.org/method/messages.readEncryptedHistory new file mode 100644 index 0000000000..7c20204f45 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readEncryptedHistory @@ -0,0 +1,172 @@ + + + + + messages.readEncryptedHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readEncryptedHistory

+ +

Marks message history within a secret chat as read.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
max_dateintMaximum date value for received messages in history
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_WAIT_FAILEDA waiting call returned an error.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.readFeaturedStickers b/data/corefork.telegram.org/method/messages.readFeaturedStickers new file mode 100644 index 0000000000..aae24a1fd4 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readFeaturedStickers @@ -0,0 +1,150 @@ + + + + + messages.readFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readFeaturedStickers

+ +

Mark new featured stickers as read

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<long>IDs of stickersets to mark as read
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.readHistory b/data/corefork.telegram.org/method/messages.readHistory new file mode 100644 index 0000000000..edf5da873c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readHistory @@ -0,0 +1,186 @@ + + + + + messages.readHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readHistory

+ +

Marks message history as read.

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerTarget user or group
max_idintIf a positive value is passed, only messages with identifiers less or equal than the given one will be read
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.readMentions b/data/corefork.telegram.org/method/messages.readMentions new file mode 100644 index 0000000000..29727316c7 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readMentions @@ -0,0 +1,181 @@ + + + + + messages.readMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readMentions

+ +

Mark mentions as read

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+---functions---
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerDialog
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.readMessageContents b/data/corefork.telegram.org/method/messages.readMessageContents new file mode 100644 index 0000000000..2479be23ed --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readMessageContents @@ -0,0 +1,149 @@ + + + + + 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.readReactions b/data/corefork.telegram.org/method/messages.readReactions new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readReactions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.receivedMessages b/data/corefork.telegram.org/method/messages.receivedMessages new file mode 100644 index 0000000000..fc8b39066f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.receivedMessages @@ -0,0 +1,148 @@ + + + + + messages.receivedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.receivedMessages

+ +

Confirms receipt of messages by a client, cancels PUSH-notification sending.

+

+ +
+
---functions---
+messages.receivedMessages#5a954c0 max_id:int = Vector<ReceivedNotifyMessage>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
max_idintMaximum message ID available in a client.
+

Result

+

The method returns the list of message IDs, for which PUSH-notifications were cancelled.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.receivedQueue b/data/corefork.telegram.org/method/messages.receivedQueue new file mode 100644 index 0000000000..cb209a87f8 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.receivedQueue @@ -0,0 +1,170 @@ + + + + + messages.receivedQueue + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.receivedQueue

+ +

Confirms receipt of messages in a secret chat by client, cancels push notifications.

+

+ +
+
---functions---
+messages.receivedQueue#55a5bb66 max_qts:int = Vector<long>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
max_qtsintMaximum qts value available at the client
+

Result

+

Method returns a list of random_ids of messages for which push notifications were cancelled in Vector<long>.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MAX_QTS_INVALIDThe specified max_qts is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.reorderPinnedDialogs b/data/corefork.telegram.org/method/messages.reorderPinnedDialogs new file mode 100644 index 0000000000..67b742c53f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.reorderPinnedDialogs @@ -0,0 +1,185 @@ + + + + + messages.reorderPinnedDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reorderPinnedDialogs

+ +

Reorder pinned dialogs

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueIf set, dialogs pinned server-side but not present in the order field will be unpinned.
folder_idintPeer folder ID, for more info click here
orderVector<InputDialogPeer>New dialog order
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.reorderStickerSets b/data/corefork.telegram.org/method/messages.reorderStickerSets new file mode 100644 index 0000000000..65bbcad207 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.reorderStickerSets @@ -0,0 +1,160 @@ + + + + + messages.reorderStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reorderStickerSets

+ +

Reorder installed stickersets

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueReorder mask stickersets
orderVector<long>New stickerset order by stickerset IDs
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.report b/data/corefork.telegram.org/method/messages.report new file mode 100644 index 0000000000..1eecf7ca92 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.report @@ -0,0 +1,187 @@ + + + + + messages.report + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.report

+ +

Report a message in a chat for violation of telegram's Terms of Service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>IDs of messages to report
reasonReportReasonWhy are these messages being reported
messagestringComment for report moderation
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.reportEncryptedSpam b/data/corefork.telegram.org/method/messages.reportEncryptedSpam new file mode 100644 index 0000000000..2a3623debf --- /dev/null +++ b/data/corefork.telegram.org/method/messages.reportEncryptedSpam @@ -0,0 +1,167 @@ + + + + + messages.reportEncryptedSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reportEncryptedSpam

+ +

Report a secret chat for spam

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatThe secret chat to report
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.reportSpam b/data/corefork.telegram.org/method/messages.reportSpam new file mode 100644 index 0000000000..169e63b9f4 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.reportSpam @@ -0,0 +1,180 @@ + + + + + messages.reportSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reportSpam

+ +

Report a new incoming chat for spam, if the peer settings of the chat allow us to do that

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reportSpam#cf1592db peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer to report
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

peerSettings

+

Peer settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.requestEncryption b/data/corefork.telegram.org/method/messages.requestEncryption new file mode 100644 index 0000000000..15d5b17905 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.requestEncryption @@ -0,0 +1,185 @@ + + + + + messages.requestEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.requestEncryption

+ +

Sends a request to start a secret chat to the user.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+---functions---
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
random_idintUnique client request ID required to prevent resending. This also doubles as the chat ID.
g_abytesA = g ^ a mod p, see Wikipedia
+

Result

+

EncryptedChat

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400DH_G_A_INVALIDg_a invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.requestUrlAuth b/data/corefork.telegram.org/method/messages.requestUrlAuth new file mode 100644 index 0000000000..5d4f7d9a9c --- /dev/null +++ b/data/corefork.telegram.org/method/messages.requestUrlAuth @@ -0,0 +1,174 @@ + + + + + messages.requestUrlAuth + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.requestUrlAuth

+ +

Get more info about a Seamless Telegram Login authorization request, for more info click here »

+

+ +
+
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
+urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
+urlAuthResultDefault#a9d6db1f = UrlAuthResult;
+---functions---
+messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerflags.1?InputPeerPeer where the message is located
msg_idflags.1?intThe message
button_idflags.1?intThe ID of the button with the authorization request
urlflags.2?stringURL used for link URL authorization, click here for more info »
+

Result

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.saveDefaultSendAs b/data/corefork.telegram.org/method/messages.saveDefaultSendAs new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.saveDefaultSendAs @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.saveDraft b/data/corefork.telegram.org/method/messages.saveDraft new file mode 100644 index 0000000000..d508cf317a --- /dev/null +++ b/data/corefork.telegram.org/method/messages.saveDraft @@ -0,0 +1,202 @@ + + + + + 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 new file mode 100644 index 0000000000..a9e98535e7 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.saveGif @@ -0,0 +1,172 @@ + + + + + messages.saveGif + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.saveGif

+ +

Add GIF to saved gifs list

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputDocumentGIF to save
unsaveBoolWhether to remove GIF from saved gifs list
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400GIF_ID_INVALIDThe provided GIF ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.saveRecentSticker b/data/corefork.telegram.org/method/messages.saveRecentSticker new file mode 100644 index 0000000000..23596b01cb --- /dev/null +++ b/data/corefork.telegram.org/method/messages.saveRecentSticker @@ -0,0 +1,182 @@ + + + + + messages.saveRecentSticker + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.saveRecentSticker

+ +

Add/remove sticker from recent stickers list

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueWhether to add/remove stickers recently attached to photo or video files
idInputDocumentSticker
unsaveBoolWhether to save or unsave the sticker
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.search b/data/corefork.telegram.org/method/messages.search new file mode 100644 index 0000000000..e4e02e2f83 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.search @@ -0,0 +1,291 @@ + + + + + messages.search + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.search

+ +

Gets back found messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerUser or chat, histories with which are searched, or (inputPeerEmpty) constructor for global search
qstringText search request
from_idflags.0?InputPeerOnly return messages sent by the specified user ID
top_msg_idflags.1?intThread ID
filterMessagesFilterFilter to return only specified message types
min_dateintIf a positive value was transferred, only messages with a sending date bigger than the transferred one will be returned
max_dateintIf a positive value was transferred, only messages with a sending date smaller than the transferred one will be returned
offset_idintOnly return messages starting from the specified message ID
add_offsetintAdditional offset
limitintNumber of results to return
max_idintMaximum message ID to return
min_idintMinimum message ID to return
hashlongHash
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400FROM_PEER_INVALIDThe specified from_id is invalid.
400INPUT_FILTER_INVALIDThe specified filter is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PEER_ID_NOT_SUPPORTEDThe provided peer ID is not supported.
400SEARCH_QUERY_EMPTYThe search query is empty.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

inputPeerEmpty

+

An empty constructor, no user or chat is defined.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.searchGifs b/data/corefork.telegram.org/method/messages.searchGifs new file mode 100644 index 0000000000..606fad0099 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.searchGifs @@ -0,0 +1,177 @@ + + + + + messages.searchGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchGifs

+ +

Search for GIFs

+

+ +
+
 Method schema is available as of layer 114. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
qstringText query
offsetintOffset for pagination »
+

Result

+

messages.FoundGifs

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.searchGlobal b/data/corefork.telegram.org/method/messages.searchGlobal new file mode 100644 index 0000000000..61fce793af --- /dev/null +++ b/data/corefork.telegram.org/method/messages.searchGlobal @@ -0,0 +1,226 @@ + + + + + messages.searchGlobal + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchGlobal

+ +

Search for messages and peers globally

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
qstringQuery
filterMessagesFilterGlobal search filter
min_dateintIf a positive value was specified, the method will return only messages with date bigger than min_date
max_dateintIf a positive value was transferred, the method will return only messages with date smaller than max_date
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintOffsets for pagination, for more info click here
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

messages.messagesSlice

+

Incomplete list of messages and auxiliary data.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.searchStickerSets b/data/corefork.telegram.org/method/messages.searchStickerSets new file mode 100644 index 0000000000..7846141dee --- /dev/null +++ b/data/corefork.telegram.org/method/messages.searchStickerSets @@ -0,0 +1,168 @@ + + + + + messages.searchStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchStickerSets

+ +

Search for stickersets

+

+ +
+
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
+messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
+---functions---
+messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_featuredflags.0?trueExclude featured stickersets from results
qstringQuery string
hashlongHash for pagination, for more info click here
+

Result

+

messages.FoundStickerSets

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendBroadcast b/data/corefork.telegram.org/method/messages.sendBroadcast new file mode 100644 index 0000000000..0f24999788 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendBroadcast @@ -0,0 +1,145 @@ + + + + + messages.sendBroadcast + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendBroadcast

+ +

Sends multiple messages to contacts.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
contactsVector<InputUser>List of user ID to whom a message will be sent
messagestringMessage text
mediaInputMediaMessage media-contents
+

Result

+

messages.StatedMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendEncrypted b/data/corefork.telegram.org/method/messages.sendEncrypted new file mode 100644 index 0000000000..54956fc117 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendEncrypted @@ -0,0 +1,210 @@ + + + + + messages.sendEncrypted + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendEncrypted

+ +

Sends a text message to a secret chat.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+---functions---
+messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueSend encrypted message without a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID, necessary to avoid message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key that was created during chat initialization
+

Result

+

messages.SentEncryptedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_IS_BLOCKEDYou were blocked by this user.
+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendEncryptedFile b/data/corefork.telegram.org/method/messages.sendEncryptedFile new file mode 100644 index 0000000000..3996654e76 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendEncryptedFile @@ -0,0 +1,215 @@ + + + + + messages.sendEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendEncryptedFile

+ +

Sends a message with a file attachment to a secret chat

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+---functions---
+messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueWhether to send the file without triggering a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID necessary to prevent message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
fileInputEncryptedFileFile attachment for the secret chat
+

Result

+

messages.SentEncryptedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400DATA_TOO_LONGData too long.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400FILE_EMTPYAn empty file was provided.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MSG_WAIT_FAILEDA waiting call returned an error.
+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendEncryptedService b/data/corefork.telegram.org/method/messages.sendEncryptedService new file mode 100644 index 0000000000..914d45c679 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendEncryptedService @@ -0,0 +1,205 @@ + + + + + messages.sendEncryptedService + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendEncryptedService

+ +

Sends a service message to a secret chat.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+---functions---
+messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID required to prevent message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
+

Result

+

messages.SentEncryptedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_DELETEDYou can't send this secret message because the other participant deleted their account.
403USER_IS_BLOCKEDYou were blocked by this user.
+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendInlineBotResult b/data/corefork.telegram.org/method/messages.sendInlineBotResult new file mode 100644 index 0000000000..20f24981c3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendInlineBotResult @@ -0,0 +1,344 @@ + + + + + messages.sendInlineBotResult + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendInlineBotResult

+ +

Send a result obtained using messages.getInlineBotResults.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendInlineBotResult#7aa11297 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 send_as:flags.13?InputPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the message silently (no notification will be triggered on the other client)
backgroundflags.6?trueWhether to send the message in background
clear_draftflags.7?trueWhether to clear the draft
hide_viaflags.11?trueWhether to hide the via @botname in the resulting message (only for bot usernames encountered in the config)
peerInputPeerDestination
reply_to_msg_idflags.0?intID of the message this message should reply to
random_idlongRandom ID to avoid resending the same query
query_idlongQuery ID from messages.getInlineBotResults
idstringResult ID from messages.getInlineBotResults
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_INLINE_FORBIDDENYou can't send inline messages in this group.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INLINE_RESULT_EXPIREDThe inline query expired.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400QUERY_ID_EMPTYThe query ID is empty.
400RESULT_ID_EMPTYResult ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
+

Related pages

+

Message drafts

+

How to handle message drafts

+

config

+

Current configuration

+

messages.getInlineBotResults

+

Query an inline bot

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendMedia b/data/corefork.telegram.org/method/messages.sendMedia new file mode 100644 index 0000000000..c126186ba0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendMedia @@ -0,0 +1,518 @@ + + + + + messages.sendMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendMedia

+ +

Send a media

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendMedia#e25ff8e0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?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 send_as:flags.13?InputPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueSend message silently (no notification should be triggered)
backgroundflags.6?trueSend message in background
clear_draftflags.7?trueClear the draft
peerInputPeerDestination
reply_to_msg_idflags.0?intMessage ID to which this message should reply to
mediaInputMediaAttached media
messagestringCaption
random_idlongRandom ID to avoid resending the same message
reply_markupflags.2?ReplyMarkupReply markup for bot keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_PAYMENTS_DISABLEDPlease enable bot payments in botfather before calling this method.
400BOT_POLLS_DISABLED 
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CURRENCY_TOTAL_AMOUNT_INVALIDThe total amount of all prices is invalid.
400EMOTICON_INVALIDThe specified emoji is invalid.
400EXTERNAL_URL_INVALIDExternal URL invalid.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_LENGTH_INVALIDThe length of a file part is invalid.
400FILE_REFERENCE_EMPTYAn empty file reference was specified.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference.
400GAME_BOT_INVALIDBots can't send another bot's game.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PAYMENT_PROVIDER_INVALIDThe specified payment provider is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400POLL_ANSWERS_INVALIDInvalid poll answers were provided.
400POLL_ANSWER_INVALIDOne of the poll answers is not acceptable.
400POLL_OPTION_DUPLICATEDuplicate poll options provided.
400POLL_OPTION_INVALIDInvalid poll option provided.
400POLL_QUESTION_INVALIDOne of the poll questions is not acceptable.
400QUIZ_CORRECT_ANSWERS_EMPTYNo correct quiz answer was specified.
400QUIZ_CORRECT_ANSWERS_TOO_MUCHYou specified too many correct answers in a quiz, quizes can only have one right answer!
400QUIZ_CORRECT_ANSWER_INVALIDAn invalid value was provided to the correct_answers field.
400QUIZ_MULTIPLE_INVALIDQuizes can't have the multiple_choice flag set!
400REPLY_MARKUP_BUY_EMPTYReply markup for buy button empty.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400TTL_MEDIA_INVALIDInvalid media Time To Live was provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400VIDEO_CONTENT_TYPE_INVALIDThe video's content type is invalid.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendMessage b/data/corefork.telegram.org/method/messages.sendMessage new file mode 100644 index 0000000000..f65d5614e2 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendMessage @@ -0,0 +1,398 @@ + + + + + messages.sendMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendMessage

+ +

Sends a message to a chat

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendMessage#d9d75a4 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?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 send_as:flags.13?InputPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueSet this flag to disable generation of the webpage preview
silentflags.5?trueSend this message silently (no notifications for the receivers)
backgroundflags.6?trueSend this message as background message
clear_draftflags.7?trueClear the draft field
peerInputPeerThe destination where the message will be sent
reply_to_msg_idflags.0?intThe message ID to which this message will reply to
messagestringThe message
random_idlongUnique client message ID required to prevent message resending
reply_markupflags.2?ReplyMarkupReply markup for sending bot buttons
entitiesflags.3?Vector<MessageEntity>Message entities for sending styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400BOT_DOMAIN_INVALIDBot domain invalid.
400BOT_INVALIDThis is not a valid bot.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400ENTITIES_TOO_LONGYou provided too many styled message entities.
400ENTITY_MENTION_USER_INVALIDYou mentioned an invalid user.
400FROM_MESSAGE_BOT_DISABLEDBots can't use fromMessage min constructors.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400MSG_ID_INVALIDProvided reply_to_msg_id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400POLL_OPTION_INVALIDInvalid poll option provided.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400REPLY_MARKUP_TOO_LONGThe specified reply_markup is too long.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_STATUS_PRIVATECan't schedule until user is online, if the user's last seen timestamp is hidden by their privacy settings.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendMultiMedia b/data/corefork.telegram.org/method/messages.sendMultiMedia new file mode 100644 index 0000000000..8fb52a6c38 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendMultiMedia @@ -0,0 +1,263 @@ + + + + + messages.sendMultiMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendMultiMedia

+ +

Send an album or grouped media

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendMultiMedia#f803138f flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the album silently (no notification triggered)
backgroundflags.6?trueSend in background?
clear_draftflags.7?trueWhether to clear drafts
peerInputPeerThe destination chat
reply_to_msg_idflags.0?intThe message to reply to
multi_mediaVector<InputSingleMedia>The medias to send
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MULTI_MEDIA_TOO_LONGToo many media files for album.
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_EMPTYRandom ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: wait X seconds before sending another message to this chat.
+

Bots can use this method

+

Related pages

+

Message drafts

+

How to handle message drafts

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendReaction b/data/corefork.telegram.org/method/messages.sendReaction new file mode 100644 index 0000000000..3de5238fa1 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendReaction @@ -0,0 +1,193 @@ + + + + + messages.sendReaction + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendReaction

+ +

Send reaction to message

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendReaction#25690ce4 flags:# big:flags.1?true peer:InputPeer msg_id:int reaction:flags.0?string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerPeer
msg_idintMessage ID to react to
reactionflags.0?stringReaction (a UTF8 emoji)
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400REACTION_EMPTYEmpty reaction provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendScheduledMessages b/data/corefork.telegram.org/method/messages.sendScheduledMessages new file mode 100644 index 0000000000..4076b60794 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendScheduledMessages @@ -0,0 +1,182 @@ + + + + + messages.sendScheduledMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendScheduledMessages

+ +

Send scheduled messages right away

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendScreenshotNotification b/data/corefork.telegram.org/method/messages.sendScreenshotNotification new file mode 100644 index 0000000000..8cef019573 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendScreenshotNotification @@ -0,0 +1,187 @@ + + + + + messages.sendScreenshotNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendScreenshotNotification

+ +

Notify the other user in a private chat that a screenshot of the chat was taken

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerOther user
reply_to_msg_idintID of message that was screenshotted, can be 0
random_idlongRandom ID to avoid message resending
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
400YOU_BLOCKED_USERYou blocked this user.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendVote b/data/corefork.telegram.org/method/messages.sendVote new file mode 100644 index 0000000000..f7995b79c3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendVote @@ -0,0 +1,220 @@ + + + + + messages.sendVote + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendVote

+ +

Vote in a poll

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the poll was sent
msg_idintThe message ID of the poll
optionsVector<bytes>The options that were chosen
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_POLL_CLOSEDPoll closed.
400OPTIONS_TOO_MUCHToo many options provided.
400OPTION_INVALIDInvalid option selected.
400PEER_ID_INVALIDThe provided peer id is invalid.
400REVOTE_NOT_ALLOWEDYou cannot change your vote.
+

Related pages

+

poll

+

Poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setBotCallbackAnswer b/data/corefork.telegram.org/method/messages.setBotCallbackAnswer new file mode 100644 index 0000000000..d84b337d05 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setBotCallbackAnswer @@ -0,0 +1,203 @@ + + + + + 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/corefork.telegram.org/method/messages.setBotPrecheckoutResults b/data/corefork.telegram.org/method/messages.setBotPrecheckoutResults new file mode 100644 index 0000000000..93c3c70a7b --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setBotPrecheckoutResults @@ -0,0 +1,188 @@ + + + + + messages.setBotPrecheckoutResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setBotPrecheckoutResults

+ +

Once the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
+Use this method to respond to such pre-checkout queries.
+Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.1?trueSet this flag if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order, otherwise do not set it, and set the error field, instead
query_idlongUnique identifier for the query to be answered
errorflags.0?stringRequired if the success isn't set. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400ERROR_TEXT_EMPTYThe provided error message is empty.
+

Bots can use this method

+

Related pages

+

updateBotPrecheckoutQuery

+

This object contains information about an incoming pre-checkout query.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setBotShippingResults b/data/corefork.telegram.org/method/messages.setBotShippingResults new file mode 100644 index 0000000000..db4f49f678 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setBotShippingResults @@ -0,0 +1,186 @@ + + + + + messages.setBotShippingResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setBotShippingResults

+ +

If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongUnique identifier for the query to be answered
errorflags.0?stringError message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
shipping_optionsflags.1?Vector<ShippingOption>A vector of available shipping options.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400QUERY_ID_INVALIDThe query ID is invalid.
+

Bots can use this method

+

Related pages

+

updateBotShippingQuery

+

This object contains information about an incoming shipping query.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setChatAvailableReactions b/data/corefork.telegram.org/method/messages.setChatAvailableReactions new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setChatAvailableReactions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setChatTheme b/data/corefork.telegram.org/method/messages.setChatTheme new file mode 100644 index 0000000000..c7761686c9 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setChatTheme @@ -0,0 +1,185 @@ + + + + + messages.setChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setChatTheme

+ +

Change the chat theme of a certain chat

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPrivate chat where to change theme
emoticonstringEmoji, identifying a specific chat theme; a list of chat themes can be fetched using account.getChatThemes
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMOJI_INVALIDThe specified theme emoji is valid.
400EMOJI_NOT_MODIFIEDThe theme wasn't changed.
+

Related pages

+

account.getChatThemes

+

Get all available chat themes

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setDefaultReaction b/data/corefork.telegram.org/method/messages.setDefaultReaction new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setDefaultReaction @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setEncryptedTyping b/data/corefork.telegram.org/method/messages.setEncryptedTyping new file mode 100644 index 0000000000..df9c8f1455 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setEncryptedTyping @@ -0,0 +1,177 @@ + + + + + messages.setEncryptedTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setEncryptedTyping

+ +

Send typing event by the current user to a secret chat.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
typingBoolTyping.
Possible values:
(boolTrue), if the user started typing and more than 5 seconds have passed since the last request
(boolFalse), if the user stopped typing
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

boolFalse

+

Constructor may be interpreted as a booleanfalse value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setGameScore b/data/corefork.telegram.org/method/messages.setGameScore new file mode 100644 index 0000000000..fcb4cfa74d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setGameScore @@ -0,0 +1,218 @@ + + + + + messages.setGameScore + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setGameScore

+ +

Use this method to set the score of the specified user in a game sent as a normal message (bots only).

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
peerInputPeerUnique identifier of target chat
idintIdentifier of the sent message
user_idInputUserUser identifier
scoreintNew score
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_SCORE_NOT_MODIFIEDThe score wasn't modified.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setHistoryTTL b/data/corefork.telegram.org/method/messages.setHistoryTTL new file mode 100644 index 0000000000..ee2152da56 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setHistoryTTL @@ -0,0 +1,182 @@ + + + + + messages.setHistoryTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setHistoryTTL

+ +

Set maximum Time-To-Live of all messages in the specified chat

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
periodintAutomatically delete all messages sent in the chat after this many seconds
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400TTL_PERIOD_INVALIDThe specified TTL period is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setInlineBotResults b/data/corefork.telegram.org/method/messages.setInlineBotResults new file mode 100644 index 0000000000..c0a46eb1fd --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setInlineBotResults @@ -0,0 +1,358 @@ + + + + + messages.setInlineBotResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setInlineBotResults

+ +

Answer an inline query, for bots only

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueSet this flag if the results are composed of media files
privateflags.1?trueSet this flag if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
query_idlongUnique identifier for the answered query
resultsVector<InputBotInlineResult>Vector of results for the inline query
cache_timeintThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
next_offsetflags.2?stringPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don‘t support pagination. Offset length can’t exceed 64 bytes.
switch_pmflags.3?InlineBotSwitchPMIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with a certain parameter.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ARTICLE_TITLE_EMPTYThe title of the article is empty.
400AUDIO_CONTENT_URL_EMPTYThe remote URL specified in the content field is empty.
400AUDIO_TITLE_EMPTYAn empty audio title was provided.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400DOCUMENT_INVALIDThe specified document is invalid.
400FILE_CONTENT_TYPE_INVALIDFile content-type is invalid.
400FILE_TITLE_EMPTYAn empty file title was specified.
400GIF_CONTENT_TYPE_INVALIDGIF content-type invalid.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400NEXT_OFFSET_INVALIDThe specified offset is longer than 64 bytes.
400PHOTO_CONTENT_TYPE_INVALIDPhoto mime-type invalid.
400PHOTO_CONTENT_URL_EMPTYPhoto URL invalid.
400PHOTO_INVALIDPhoto invalid.
400PHOTO_THUMB_URL_EMPTYPhoto thumbnail URL is empty.
400QUERY_ID_INVALIDThe query ID is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400RESULTS_TOO_MUCHToo many results were provided.
400RESULT_ID_DUPLICATEYou provided a duplicate result ID.
400RESULT_TYPE_INVALIDResult type invalid.
400SEND_MESSAGE_MEDIA_INVALIDInvalid media provided.
400SEND_MESSAGE_TYPE_INVALIDThe message type is invalid.
400START_PARAM_INVALIDStart parameter invalid.
400STICKER_DOCUMENT_INVALIDThe specified sticker document is invalid.
403USER_BOT_INVALIDThis method can only be called by a bot.
400VIDEO_TITLE_EMPTYThe specified video title is empty.
400WEBDOCUMENT_INVALIDInvalid webdocument URL provided.
400WEBDOCUMENT_MIME_INVALIDInvalid webdocument mime type provided.
400WEBDOCUMENT_SIZE_TOO_BIGWebdocument is too big!
400WEBDOCUMENT_URL_INVALIDThe specified webdocument URL is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setInlineGameScore b/data/corefork.telegram.org/method/messages.setInlineGameScore new file mode 100644 index 0000000000..db6f1c286a --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setInlineGameScore @@ -0,0 +1,198 @@ + + + + + messages.setInlineGameScore + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setInlineGameScore

+ +

Use this method to set the score of the specified user in a game sent as an inline message (bots only).

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
idInputBotInlineMessageIDID of the inline message
user_idInputUserUser identifier
scoreintNew score
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setTyping b/data/corefork.telegram.org/method/messages.setTyping new file mode 100644 index 0000000000..46acc17506 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setTyping @@ -0,0 +1,240 @@ + + + + + messages.setTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setTyping

+ +

Sends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerTarget user or group
top_msg_idflags.0?intThread ID
actionSendMessageActionType of action
Parameter added in Layer 17.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
+

Bots can use this method

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+

SendMessageAction

+

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.startBot b/data/corefork.telegram.org/method/messages.startBot new file mode 100644 index 0000000000..a143599d35 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.startBot @@ -0,0 +1,224 @@ + + + + + messages.startBot + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.startBot

+ +

Start a conversation with a bot using a deep linking parameter

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
botInputUserThe bot
peerInputPeerThe chat where to start the bot, can be the bot's private chat or a group
random_idlongRandom ID to avoid resending the same message
start_paramstringDeep linking parameter
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_INVALIDThis is not a valid bot.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400START_PARAM_EMPTYThe start parameter is empty.
400START_PARAM_INVALIDStart parameter invalid.
400START_PARAM_TOO_LONGStart parameter is too long.
+

Related pages

+

Bots: An introduction for developers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.startHistoryImport b/data/corefork.telegram.org/method/messages.startHistoryImport new file mode 100644 index 0000000000..491331c9d0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.startHistoryImport @@ -0,0 +1,180 @@ + + + + + messages.startHistoryImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.startHistoryImport

+ +

Complete the history import process, importing all messages into the chat.
+To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe Telegram chat where the messages should be imported, click here for more info »
import_idlongIdentifier of a history import session, returned by messages.initHistoryImport.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400IMPORT_ID_INVALIDThe specified import ID is invalid.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

messages.initHistoryImport

+

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

+

messages.uploadImportedMedia

+

Upload a media file associated with an imported chat, click here for more info ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.toggleDialogPin b/data/corefork.telegram.org/method/messages.toggleDialogPin new file mode 100644 index 0000000000..bd1ff80961 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.toggleDialogPin @@ -0,0 +1,187 @@ + + + + + messages.toggleDialogPin + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.toggleDialogPin

+ +

Pin/unpin a dialog

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether to pin or unpin the dialog
peerInputDialogPeerThe dialog to pin
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.toggleNoForwards b/data/corefork.telegram.org/method/messages.toggleNoForwards new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.toggleNoForwards @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.toggleStickerSets b/data/corefork.telegram.org/method/messages.toggleStickerSets new file mode 100644 index 0000000000..ecbb629ad8 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.toggleStickerSets @@ -0,0 +1,170 @@ + + + + + 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.translateText b/data/corefork.telegram.org/method/messages.translateText new file mode 100644 index 0000000000..17d64ffaf0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.translateText @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.uninstallStickerSet b/data/corefork.telegram.org/method/messages.uninstallStickerSet new file mode 100644 index 0000000000..593287d1f2 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.uninstallStickerSet @@ -0,0 +1,167 @@ + + + + + messages.uninstallStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uninstallStickerSet

+ +

Uninstall a stickerset

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetThe stickerset to uninstall
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.unpinAllMessages b/data/corefork.telegram.org/method/messages.unpinAllMessages new file mode 100644 index 0000000000..66c38bb531 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.unpinAllMessages @@ -0,0 +1,153 @@ + + + + + messages.unpinAllMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.unpinAllMessages

+ +

Unpin all pinned messages

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+---functions---
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat where to unpin
+

Result

+

messages.AffectedHistory

+

Bots can use this method

+

Related pages

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.updateDialogFilter b/data/corefork.telegram.org/method/messages.updateDialogFilter new file mode 100644 index 0000000000..441724d39e --- /dev/null +++ b/data/corefork.telegram.org/method/messages.updateDialogFilter @@ -0,0 +1,190 @@ + + + + + messages.updateDialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.updateDialogFilter

+ +

Update folder

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FILTER_ID_INVALIDThe specified filter ID is invalid.
400FILTER_INCLUDE_EMPTYThe include_peers vector of the filter is empty.
400FILTER_TITLE_EMPTYThe title field of the filter is empty.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder b/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder new file mode 100644 index 0000000000..2e8ff2b873 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder @@ -0,0 +1,153 @@ + + + + + messages.updateDialogFiltersOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.updateDialogFiltersOrder

+ +

Reorder folders

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
orderVector<int>New folder order
+

Result

+

Bool

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.updatePinnedMessage b/data/corefork.telegram.org/method/messages.updatePinnedMessage new file mode 100644 index 0000000000..0e8badee50 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.updatePinnedMessage @@ -0,0 +1,238 @@ + + + + + messages.updatePinnedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.updatePinnedMessage

+ +

Pin a message

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?truePin the message silently, without triggering a notification
unpinflags.1?trueWhether the message should unpinned or pinned
pm_onesideflags.2?trueWhether the message should only be pinned on the local side of a one-to-one chat
peerInputPeerThe peer where to pin the message
idintThe message to pin or unpin
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_ONESIDE_NOT_AVAILBots can't pin messages in PM just for themselves.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PIN_RESTRICTEDYou can't pin messages.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.uploadEncryptedFile b/data/corefork.telegram.org/method/messages.uploadEncryptedFile new file mode 100644 index 0000000000..e142e6ef75 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.uploadEncryptedFile @@ -0,0 +1,155 @@ + + + + + messages.uploadEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uploadEncryptedFile

+ +

Upload encrypted file and associate it to a secret chat

+

+ +
+
encryptedFileEmpty#c21f497e = EncryptedFile;
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+---functions---
+messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatThe secret chat to associate the file to
fileInputEncryptedFileThe file
+

Result

+

EncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.uploadImportedMedia b/data/corefork.telegram.org/method/messages.uploadImportedMedia new file mode 100644 index 0000000000..ff1fb4663f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.uploadImportedMedia @@ -0,0 +1,181 @@ + + + + + messages.uploadImportedMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uploadImportedMedia

+ +

Upload a media file associated with an imported chat, click here for more info ».

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+---functions---
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe Telegram chat where the media will be imported
import_idlongIdentifier of a history import session, returned by messages.initHistoryImport
file_namestringFile name
mediaInputMediaMedia metadata
+

Result

+

MessageMedia

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

messages.initHistoryImport

+

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.uploadMedia b/data/corefork.telegram.org/method/messages.uploadMedia new file mode 100644 index 0000000000..ab0b5e1f5a --- /dev/null +++ b/data/corefork.telegram.org/method/messages.uploadMedia @@ -0,0 +1,264 @@ + + + + + messages.uploadMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uploadMedia

+ +

Upload a file and associate it to a chat (without actually sending it to the chat)

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+---functions---
+messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat, can be an inputPeerEmpty for bots
mediaInputMediaFile uploaded in chunks as described in files »
+

Result

+

MessageMedia

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
+

Bots can use this method

+

Related pages

+

inputPeerEmpty

+

An empty constructor, no user or chat is defined.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/payments.clearSavedInfo b/data/corefork.telegram.org/method/payments.clearSavedInfo new file mode 100644 index 0000000000..831031d801 --- /dev/null +++ b/data/corefork.telegram.org/method/payments.clearSavedInfo @@ -0,0 +1,160 @@ + + + + + payments.clearSavedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.clearSavedInfo

+ +

Clear saved payment information

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
credentialsflags.0?trueRemove saved payment credentials
infoflags.1?trueClear the last order settings saved by the user
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/payments.getPaymentForm b/data/corefork.telegram.org/method/payments.getPaymentForm new file mode 100644 index 0000000000..12db09b988 --- /dev/null +++ b/data/corefork.telegram.org/method/payments.getPaymentForm @@ -0,0 +1,181 @@ + + + + + payments.getPaymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getPaymentForm

+ +

Get a payment form

+

+ +
+
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+---functions---
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of payment form
theme_paramsflags.0?DataJSONA JSON object with the following keys, containing color theme information (integers, RGB24) to pass to the payment provider, to apply in eventual verification pages:
bg_color - Background color
text_color - Text color
hint_color - Hint text color
link_color - Link color
button_color - Button color
button_text_color - Button text color
+

Result

+

payments.PaymentForm

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/payments.getPaymentReceipt b/data/corefork.telegram.org/method/payments.getPaymentReceipt new file mode 100644 index 0000000000..572da4986e --- /dev/null +++ b/data/corefork.telegram.org/method/payments.getPaymentReceipt @@ -0,0 +1,171 @@ + + + + + payments.getPaymentReceipt + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getPaymentReceipt

+ +

Get payment receipt

+

+ +
+
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+---functions---
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer where the payment receipt was sent
msg_idintMessage ID of receipt
+

Result

+

payments.PaymentReceipt

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/payments.getSavedInfo b/data/corefork.telegram.org/method/payments.getSavedInfo new file mode 100644 index 0000000000..9c92d53346 --- /dev/null +++ b/data/corefork.telegram.org/method/payments.getSavedInfo @@ -0,0 +1,134 @@ + + + + + payments.getSavedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getSavedInfo

+ +

Get saved payment information

+

+ +
+
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
+---functions---
+payments.getSavedInfo#227d824b = payments.SavedInfo;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

payments.SavedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/payments.sendPaymentForm b/data/corefork.telegram.org/method/payments.sendPaymentForm new file mode 100644 index 0000000000..04596d9811 --- /dev/null +++ b/data/corefork.telegram.org/method/payments.sendPaymentForm @@ -0,0 +1,206 @@ + + + + + payments.sendPaymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.sendPaymentForm

+ +

Send compiled payment form

+

+ +
+
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
+payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
+---functions---
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
form_idlongForm ID
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of form
requested_info_idflags.0?stringID of saved and validated order info
shipping_option_idflags.1?stringChosen shipping option ID
credentialsInputPaymentCredentialsPayment credentials
tip_amountflags.2?longTip, in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Result

+

payments.PaymentResult

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+

Related pages

+

payments.ValidatedRequestedInfo

+

Validated user-provided info

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.acceptCall b/data/corefork.telegram.org/method/phone.acceptCall new file mode 100644 index 0000000000..0bae401dda --- /dev/null +++ b/data/corefork.telegram.org/method/phone.acceptCall @@ -0,0 +1,193 @@ + + + + + phone.acceptCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.acceptCall

+ +

Accept incoming call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+---functions---
+phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe call to accept
g_bbytesParameter for E2E encryption key exchange »
protocolPhoneCallProtocolPhone call settings
+

Result

+

phone.PhoneCall

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_ACCEPTEDThe call was already accepted.
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
400CALL_PROTOCOL_FLAGS_INVALIDCall protocol flags invalid.
+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.checkGroupCall b/data/corefork.telegram.org/method/phone.checkGroupCall new file mode 100644 index 0000000000..327e40c49c --- /dev/null +++ b/data/corefork.telegram.org/method/phone.checkGroupCall @@ -0,0 +1,154 @@ + + + + + phone.checkGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.checkGroupCall

+ +

Check whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs

+

+ +
+
---functions---
+phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
sourcesVector<int>Source IDs
+

Result

+

Vector<int>

+

Returns an intersection of the source IDs specified in sources, and the source IDs currently being forwarded by the SFU.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.confirmCall b/data/corefork.telegram.org/method/phone.confirmCall new file mode 100644 index 0000000000..2438b77914 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.confirmCall @@ -0,0 +1,188 @@ + + + + + phone.confirmCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.confirmCall

+ +

Complete phone call E2E encryption key exchange »

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+---functions---
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe phone call
g_abytesParameter for E2E encryption key exchange »
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolPhone call settings
+

Result

+

phone.PhoneCall

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.createGroupCall b/data/corefork.telegram.org/method/phone.createGroupCall new file mode 100644 index 0000000000..4ea486ac6d --- /dev/null +++ b/data/corefork.telegram.org/method/phone.createGroupCall @@ -0,0 +1,200 @@ + + + + + phone.createGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.createGroupCall

+ +

Create a group call or livestream

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.createGroupCall#48cdc6d8 flags:# rtmp_stream:flags.2?true peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerAssociate the group call or livestream to the provided group/supergroup/channel
random_idintUnique client message ID required to prevent creation of duplicate group calls
titleflags.0?stringCall title
schedule_dateflags.1?intFor scheduled group call or livestreams, the absolute date when the group call will start
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.discardCall b/data/corefork.telegram.org/method/phone.discardCall new file mode 100644 index 0000000000..78346665bf --- /dev/null +++ b/data/corefork.telegram.org/method/phone.discardCall @@ -0,0 +1,202 @@ + + + + + phone.discardCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.discardCall

+ +

Refuse or end running call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.0?trueWhether this is a video call
peerInputPhoneCallThe phone call
durationintCall duration
reasonPhoneCallDiscardReasonWhy was the call discarded
connection_idlongPreferred libtgvoip relay ID
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_ACCEPTEDThe call was already accepted.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.discardGroupCall b/data/corefork.telegram.org/method/phone.discardGroupCall new file mode 100644 index 0000000000..b532b8c22c --- /dev/null +++ b/data/corefork.telegram.org/method/phone.discardGroupCall @@ -0,0 +1,155 @@ + + + + + phone.discardGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.discardGroupCall

+ +

Terminate a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call to terminate
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.editGroupCallMember b/data/corefork.telegram.org/method/phone.editGroupCallMember new file mode 100644 index 0000000000..274f0a61de --- /dev/null +++ b/data/corefork.telegram.org/method/phone.editGroupCallMember @@ -0,0 +1,167 @@ + + + + + phone.editGroupCallMember + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.editGroupCallMember

+ +

Edit information about a given group call participant

+

+ +
+
 Method schema is available as of layer 123. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + +
flags#Flags, see TL conditional fields
mutedflags.0?trueWhether to mute or unmute the user
callInputGroupCallGroup call
user_idInputUserThe user in question
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.editGroupCallParticipant b/data/corefork.telegram.org/method/phone.editGroupCallParticipant new file mode 100644 index 0000000000..8a03466ce8 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.editGroupCallParticipant @@ -0,0 +1,225 @@ + + + + + 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/corefork.telegram.org/method/phone.editGroupCallTitle b/data/corefork.telegram.org/method/phone.editGroupCallTitle new file mode 100644 index 0000000000..c2396ce957 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.editGroupCallTitle @@ -0,0 +1,160 @@ + + + + + phone.editGroupCallTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.editGroupCallTitle

+ +

Edit the title of a group call or livestream

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
titlestringNew title
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.exportGroupCallInvite b/data/corefork.telegram.org/method/phone.exportGroupCallInvite new file mode 100644 index 0000000000..28d8d4004b --- /dev/null +++ b/data/corefork.telegram.org/method/phone.exportGroupCallInvite @@ -0,0 +1,159 @@ + + + + + phone.exportGroupCallInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.exportGroupCallInvite

+ +

Get an invite link for a group call or livestream

+

+ +
+
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
+---functions---
+phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_self_unmuteflags.0?trueFor livestreams, if set, users that join using this link will be able to speak without explicitly requesting permission by (for example by raising their hand).
callInputGroupCallThe group call
+

Result

+

phone.ExportedGroupCallInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.getCallConfig b/data/corefork.telegram.org/method/phone.getCallConfig new file mode 100644 index 0000000000..8d619db3a6 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.getCallConfig @@ -0,0 +1,134 @@ + + + + + phone.getCallConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getCallConfig

+ +

Get phone call configuration to be passed to libtgvoip's shared config

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;
+---functions---
+phone.getCallConfig#55451fa9 = DataJSON;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

DataJSON

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.getGroupCall b/data/corefork.telegram.org/method/phone.getGroupCall new file mode 100644 index 0000000000..1c7a9d7e43 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.getGroupCall @@ -0,0 +1,157 @@ + + + + + phone.getGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getGroupCall

+ +

Get info about a group call

+

+ +
+
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
+---functions---
+phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
limitintMaximum number of results to return, see pagination
+

Result

+

phone.GroupCall

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.getGroupCallJoinAs b/data/corefork.telegram.org/method/phone.getGroupCallJoinAs new file mode 100644 index 0000000000..4bc217fc73 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.getGroupCallJoinAs @@ -0,0 +1,149 @@ + + + + + phone.getGroupCallJoinAs + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getGroupCallJoinAs

+ +

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+

+ +
+
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+---functions---
+phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog whose group call or livestream we're trying to join
+

Result

+

phone.JoinAsPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.getGroupParticipants b/data/corefork.telegram.org/method/phone.getGroupParticipants new file mode 100644 index 0000000000..9c29834786 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.getGroupParticipants @@ -0,0 +1,174 @@ + + + + + phone.getGroupParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getGroupParticipants

+ +

Get group call participants

+

+ +
+
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
+---functions---
+phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
idsVector<InputPeer>If specified, will fetch group participant info about the specified peers
sourcesVector<int>If specified, will fetch group participant info about the specified WebRTC source IDs
offsetstringOffset for results, taken from the next_offset field of phone.groupParticipants, initially an empty string.
Note: if no more results are available, the method call will return an empty next_offset; thus, avoid providing the next_offset returned in phone.groupParticipants if it is empty, to avoid an infinite loop.
limitintMaximum number of results to return, see pagination
+

Result

+

phone.GroupParticipants

+

Related pages

+

phone.groupParticipants

+

Info about the participants of a group call or livestream

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.inviteToGroupCall b/data/corefork.telegram.org/method/phone.inviteToGroupCall new file mode 100644 index 0000000000..c8dfcd5467 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.inviteToGroupCall @@ -0,0 +1,177 @@ + + + + + phone.inviteToGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.inviteToGroupCall

+ +

Invite a set of users to a group call.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
usersVector<InputUser>The users to invite.
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403GROUPCALL_FORBIDDENThe group call has already ended.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.joinGroupCall b/data/corefork.telegram.org/method/phone.joinGroupCall new file mode 100644 index 0000000000..8e54b4b449 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.joinGroupCall @@ -0,0 +1,202 @@ + + + + + phone.joinGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.joinGroupCall

+ +

Join a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
mutedflags.0?trueIf set, the user will be muted by default upon joining.
video_stoppedflags.2?trueIf set, the user's video will be disabled by default upon joining.
callInputGroupCallThe group call
join_asInputPeerJoin the group call, presenting yourself as the specified user/channel
invite_hashflags.1?stringThe invitation hash from the invite link: https://t.me/username?voicechat=hash
paramsDataJSONWebRTC parameters
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400GROUPCALL_SSRC_DUPLICATE_MUCHThe app needs to retry joining the group call with a new SSRC value.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.joinGroupCallPresentation b/data/corefork.telegram.org/method/phone.joinGroupCallPresentation new file mode 100644 index 0000000000..e6ee91bfaf --- /dev/null +++ b/data/corefork.telegram.org/method/phone.joinGroupCallPresentation @@ -0,0 +1,180 @@ + + + + + phone.joinGroupCallPresentation + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.joinGroupCallPresentation

+ +

Start screen sharing in a call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
paramsDataJSONWebRTC parameters
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403PARTICIPANT_JOIN_MISSINGTrying to enable a presentation, when the user hasn't joined the Video Chat with phone.joinGroupCall.
+

Related pages

+

phone.joinGroupCall

+

Join a group call

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.leaveGroupCall b/data/corefork.telegram.org/method/phone.leaveGroupCall new file mode 100644 index 0000000000..3d786beb5f --- /dev/null +++ b/data/corefork.telegram.org/method/phone.leaveGroupCall @@ -0,0 +1,160 @@ + + + + + phone.leaveGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.leaveGroupCall

+ +

Leave a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
sourceintYour source ID
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.leaveGroupCallPresentation b/data/corefork.telegram.org/method/phone.leaveGroupCallPresentation new file mode 100644 index 0000000000..3e1223a649 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.leaveGroupCallPresentation @@ -0,0 +1,155 @@ + + + + + phone.leaveGroupCallPresentation + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.leaveGroupCallPresentation

+ +

Stop screen sharing in a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.receivedCall b/data/corefork.telegram.org/method/phone.receivedCall new file mode 100644 index 0000000000..ff64f0677b --- /dev/null +++ b/data/corefork.telegram.org/method/phone.receivedCall @@ -0,0 +1,172 @@ + + + + + phone.receivedCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.receivedCall

+ +

Optional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe phone call we're currently in
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.saveCallDebug b/data/corefork.telegram.org/method/phone.saveCallDebug new file mode 100644 index 0000000000..83f2811c58 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.saveCallDebug @@ -0,0 +1,177 @@ + + + + + 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.saveDefaultGroupCallJoinAs b/data/corefork.telegram.org/method/phone.saveDefaultGroupCallJoinAs new file mode 100644 index 0000000000..df354bd7d9 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.saveDefaultGroupCallJoinAs @@ -0,0 +1,155 @@ + + + + + phone.saveDefaultGroupCallJoinAs + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.saveDefaultGroupCallJoinAs

+ +

Set the default peer that will be used to join a group call in a specific dialog.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
join_asInputPeerThe default peer that will be used to join group calls in this dialog, presenting yourself as a specific user/channel.
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.sendSignalingData b/data/corefork.telegram.org/method/phone.sendSignalingData new file mode 100644 index 0000000000..e20195a0c6 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.sendSignalingData @@ -0,0 +1,155 @@ + + + + + phone.sendSignalingData + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.sendSignalingData

+ +

Send VoIP signaling data

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallPhone call
databytesSignaling payload
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.setCallRating b/data/corefork.telegram.org/method/phone.setCallRating new file mode 100644 index 0000000000..01b86c94de --- /dev/null +++ b/data/corefork.telegram.org/method/phone.setCallRating @@ -0,0 +1,192 @@ + + + + + phone.setCallRating + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.setCallRating

+ +

Rate a call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_initiativeflags.0?trueWhether the user decided on their own initiative to rate the call
peerInputPhoneCallThe call to rate
ratingintRating in 1-5 stars
commentstringAn additional comment
+

Result

+

Updates with info about the rating message sent to the official VoIP bot

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.startScheduledGroupCall b/data/corefork.telegram.org/method/phone.startScheduledGroupCall new file mode 100644 index 0000000000..501564308a --- /dev/null +++ b/data/corefork.telegram.org/method/phone.startScheduledGroupCall @@ -0,0 +1,155 @@ + + + + + phone.startScheduledGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.startScheduledGroupCall

+ +

Start a scheduled group call.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe scheduled group call
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.toggleGroupCallRecord b/data/corefork.telegram.org/method/phone.toggleGroupCallRecord new file mode 100644 index 0000000000..9f1c56782f --- /dev/null +++ b/data/corefork.telegram.org/method/phone.toggleGroupCallRecord @@ -0,0 +1,180 @@ + + + + + phone.toggleGroupCallRecord + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.toggleGroupCallRecord

+ +

Start or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
startflags.0?trueWhether to start or stop recording
videoflags.2?trueWhether to also record video streams
callInputGroupCallThe group call or livestream
titleflags.1?stringRecording title
video_portraitflags.2?BoolIf video stream recording is enabled, whether to record in portrait or landscape mode
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.toggleGroupCallSettings b/data/corefork.telegram.org/method/phone.toggleGroupCallSettings new file mode 100644 index 0000000000..06806fc3e3 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.toggleGroupCallSettings @@ -0,0 +1,187 @@ + + + + + phone.toggleGroupCallSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.toggleGroupCallSettings

+ +

Change group call settings

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
reset_invite_hashflags.1?trueInvalidate existing invite links
callInputGroupCallGroup call
join_mutedflags.0?BoolWhether all users will bthat join this group calle muted by default upon joining the group call
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400GROUPCALL_NOT_MODIFIEDGroup call settings weren't modified.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/photos.deletePhotos b/data/corefork.telegram.org/method/photos.deletePhotos new file mode 100644 index 0000000000..4e0f2f939e --- /dev/null +++ b/data/corefork.telegram.org/method/photos.deletePhotos @@ -0,0 +1,148 @@ + + + + + photos.deletePhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.deletePhotos

+ +

Deletes profile photos.

+

+ +
+
---functions---
+photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputPhoto>Input photos to delete
+

Result

+

Method returns a list of successfully deleted photos in Vector<long>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/photos.getUserPhotos b/data/corefork.telegram.org/method/photos.getUserPhotos new file mode 100644 index 0000000000..020d296506 --- /dev/null +++ b/data/corefork.telegram.org/method/photos.getUserPhotos @@ -0,0 +1,193 @@ + + + + + photos.getUserPhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.getUserPhotos

+ +

Returns the list of user photos.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+---functions---
+photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
offsetintNumber of list elements to be skipped
max_idlongIf a positive value was transferred, the method will return only photos with IDs less than the set one
limitintNumber of list elements to be returned
+

Result

+

photos.Photos

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MAX_ID_INVALIDThe provided max ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/photos.updateProfilePhoto b/data/corefork.telegram.org/method/photos.updateProfilePhoto new file mode 100644 index 0000000000..030a5510e6 --- /dev/null +++ b/data/corefork.telegram.org/method/photos.updateProfilePhoto @@ -0,0 +1,196 @@ + + + + + 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/photos.uploadProfilePhoto b/data/corefork.telegram.org/method/photos.uploadProfilePhoto new file mode 100644 index 0000000000..73e237c570 --- /dev/null +++ b/data/corefork.telegram.org/method/photos.uploadProfilePhoto @@ -0,0 +1,221 @@ + + + + + photos.uploadProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.uploadProfilePhoto

+ +

Updates current user profile photo.

+

+ +
+
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+---functions---
+photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts by means of upload.saveFilePart method
videoflags.1?InputFileAnimated profile picture video
video_start_tsflags.2?doubleFloating point UNIX timestamp in seconds, indicating the frame of the video that should be used as static preview.
+

Result

+

photos.Photo

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ALBUM_PHOTOS_TOO_MANYToo many .
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400PHOTO_CROP_FILE_MISSINGPhoto crop file missing.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_FILE_MISSINGProfile photo file missing.
400VIDEO_FILE_INVALIDThe specified video file is invalid.
+

Related pages

+

upload.saveFilePart

+

Saves a part of file for futher sending to one of the methods.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stats.getBroadcastStats b/data/corefork.telegram.org/method/stats.getBroadcastStats new file mode 100644 index 0000000000..4c0ca555a9 --- /dev/null +++ b/data/corefork.telegram.org/method/stats.getBroadcastStats @@ -0,0 +1,194 @@ + + + + + stats.getBroadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getBroadcastStats

+ +

Get channel statistics

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+---functions---
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelThe channel
+

Result

+

stats.BroadcastStats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_REQUIREDThis method can only be called on a channel, please use stats.getMegagroupStats for supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stats.getMegagroupStats b/data/corefork.telegram.org/method/stats.getMegagroupStats new file mode 100644 index 0000000000..614c4f8164 --- /dev/null +++ b/data/corefork.telegram.org/method/stats.getMegagroupStats @@ -0,0 +1,191 @@ + + + + + stats.getMegagroupStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getMegagroupStats

+ +

Get supergroup statistics

+

+ +
+
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
+---functions---
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelSupergroup ID
+

Result

+

stats.MegagroupStats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEGAGROUP_REQUIREDYou can only use this method on a supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stats.getMessageStats b/data/corefork.telegram.org/method/stats.getMessageStats new file mode 100644 index 0000000000..4c857a7128 --- /dev/null +++ b/data/corefork.telegram.org/method/stats.getMessageStats @@ -0,0 +1,189 @@ + + + + + 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/stats.loadAsyncGraph b/data/corefork.telegram.org/method/stats.loadAsyncGraph new file mode 100644 index 0000000000..f22663b066 --- /dev/null +++ b/data/corefork.telegram.org/method/stats.loadAsyncGraph @@ -0,0 +1,193 @@ + + + + + stats.loadAsyncGraph + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.loadAsyncGraph

+ +

Load channel statistics graph asynchronously

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+---functions---
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
tokenstringGraph token from statsGraphAsync constructor
xflags.0?longZoom value, if required
+

Result

+

StatsGraph

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400GRAPH_EXPIRED_RELOADThis graph has expired, please obtain a new graph token.
400GRAPH_INVALID_RELOADInvalid graph token provided, please reload the stats and provide the updated token.
400GRAPH_OUTDATED_RELOADThe graph is outdated, please get a new async token using stats.getBroadcastStats.
+

Related pages

+

statsGraphAsync

+

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stickers.addStickerToSet b/data/corefork.telegram.org/method/stickers.addStickerToSet new file mode 100644 index 0000000000..0d7e791743 --- /dev/null +++ b/data/corefork.telegram.org/method/stickers.addStickerToSet @@ -0,0 +1,188 @@ + + + + + stickers.addStickerToSet + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.addStickerToSet

+ +

Add a sticker to a stickerset, bots only. The sticker set must have been created by the bot.

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+messages.stickerSetNotModified#d3f924eb = messages.StickerSet;
+---functions---
+stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetThe stickerset
stickerInputStickerSetItemThe sticker
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKERSET_INVALIDThe provided sticker set is invalid.
400STICKER_PNG_NOPNGOne of the specified stickers is not a valid PNG file.
400STICKER_TGS_NOTGSInvalid TGS sticker provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stickers.changeStickerPosition b/data/corefork.telegram.org/method/stickers.changeStickerPosition new file mode 100644 index 0000000000..ed2c6be52d --- /dev/null +++ b/data/corefork.telegram.org/method/stickers.changeStickerPosition @@ -0,0 +1,178 @@ + + + + + stickers.changeStickerPosition + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.changeStickerPosition

+ +

Changes the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+messages.stickerSetNotModified#d3f924eb = messages.StickerSet;
+---functions---
+stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickerInputDocumentThe sticker
positionintThe new position of the sticker, zero-based
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKER_INVALIDThe provided sticker is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stickers.checkShortName b/data/corefork.telegram.org/method/stickers.checkShortName new file mode 100644 index 0000000000..0262933ea9 --- /dev/null +++ b/data/corefork.telegram.org/method/stickers.checkShortName @@ -0,0 +1,172 @@ + + + + + stickers.checkShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.checkShortName

+ +

Check whether the given short name is available

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+stickers.checkShortName#284b3639 short_name:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
short_namestringShort name
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400SHORT_NAME_INVALIDThe specified short name is invalid.
400SHORT_NAME_OCCUPIEDThe specified short name is already in use.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stickers.createStickerSet b/data/corefork.telegram.org/method/stickers.createStickerSet new file mode 100644 index 0000000000..d05e9f3835 --- /dev/null +++ b/data/corefork.telegram.org/method/stickers.createStickerSet @@ -0,0 +1,283 @@ + + + + + stickers.createStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.createStickerSet

+ +

Create a stickerset, bots only.

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+messages.stickerSetNotModified#d3f924eb = messages.StickerSet;
+---functions---
+stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether this is a mask stickerset
animatedflags.1?trueWhether this is an animated stickerset
user_idInputUserStickerset owner
titlestringStickerset name, 1-64 chars
short_namestringSticker set name. Can contain only English letters, digits and underscores. Must end with "by" ( is case insensitive); 1-64 characters
thumbflags.2?InputDocumentThumbnail
stickersVector<InputStickerSetItem>Stickers
softwareflags.3?stringUsed when importing stickers using the sticker import SDKs, specifies the name of the software that created the stickers
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400PACK_SHORT_NAME_INVALIDShort pack name invalid.
400PACK_SHORT_NAME_OCCUPIEDA stickerpack with this name already exists.
400PACK_TITLE_INVALIDThe stickerpack title is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400SHORTNAME_OCCUPY_FAILEDAn internal error occurred.
400STICKERS_EMPTYNo sticker provided.
400STICKER_EMOJI_INVALIDSticker emoji invalid.
400STICKER_FILE_INVALIDSticker file invalid.
400STICKER_PNG_DIMENSIONSSticker png dimensions invalid.
400STICKER_PNG_NOPNGOne of the specified stickers is not a valid PNG file.
400STICKER_TGS_NODOCIncorrect document type for sticker.
400STICKER_TGS_NOTGSInvalid TGS sticker provided.
400STICKER_THUMB_PNG_NOPNGIncorrect stickerset thumb file provided, PNG / WEBP expected.
400STICKER_THUMB_TGS_NOTGSIncorrect stickerset TGS thumb file provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stickers.removeStickerFromSet b/data/corefork.telegram.org/method/stickers.removeStickerFromSet new file mode 100644 index 0000000000..965bef9548 --- /dev/null +++ b/data/corefork.telegram.org/method/stickers.removeStickerFromSet @@ -0,0 +1,173 @@ + + + + + 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;
+messages.stickerSetNotModified#d3f924eb = messages.StickerSet;
+---functions---
+stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickerInputDocumentThe sticker to remove
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKER_INVALIDThe provided sticker is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stickers.setStickerSetThumb b/data/corefork.telegram.org/method/stickers.setStickerSetThumb new file mode 100644 index 0000000000..d8bcfd0019 --- /dev/null +++ b/data/corefork.telegram.org/method/stickers.setStickerSetThumb @@ -0,0 +1,183 @@ + + + + + stickers.setStickerSetThumb + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.setStickerSetThumb

+ +

Set stickerset thumbnail

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+messages.stickerSetNotModified#d3f924eb = messages.StickerSet;
+---functions---
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetStickerset
thumbInputDocumentThumbnail
+

Result

+

messages.StickerSet

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
400STICKER_THUMB_PNG_NOPNGIncorrect stickerset thumb file provided, PNG / WEBP expected.
400STICKER_THUMB_TGS_NOTGSIncorrect stickerset TGS thumb file provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stickers.suggestShortName b/data/corefork.telegram.org/method/stickers.suggestShortName new file mode 100644 index 0000000000..6f0a3d3177 --- /dev/null +++ b/data/corefork.telegram.org/method/stickers.suggestShortName @@ -0,0 +1,166 @@ + + + + + stickers.suggestShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.suggestShortName

+ +

Suggests a short name for a given stickerpack name

+

+ +
+
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
+---functions---
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
titlestringSticker pack name
+

Result

+

stickers.SuggestedShortName

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TITLE_INVALIDThe specified stickerpack title is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/updates.getChannelDifference b/data/corefork.telegram.org/method/updates.getChannelDifference new file mode 100644 index 0000000000..0ec1bb633e --- /dev/null +++ b/data/corefork.telegram.org/method/updates.getChannelDifference @@ -0,0 +1,247 @@ + + + + + updates.getChannelDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.getChannelDifference

+ +

Returns the difference between the current state of updates of a certain channel and transmitted.

+

+ +
+
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
+updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+---functions---
+updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueSet to true to skip some possibly unneeded updates and reduce server-side load
channelInputChannelThe channel
filterChannelMessagesFilterMesssage filter
ptsintPersistent timestamp (see updates)
limitintHow many updates to fetch, max 100000
Ordinary (non-bot) users are supposed to pass 10-100
+

Result

+

updates.ChannelDifference

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FROM_MESSAGE_BOT_DISABLEDBots can't use fromMessage min constructors.
400MSG_ID_INVALIDInvalid message ID provided.
400PERSISTENT_TIMESTAMP_EMPTYPersistent timestamp empty.
400PERSISTENT_TIMESTAMP_INVALIDPersistent timestamp invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400RANGES_INVALIDInvalid range provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
+

Bots can use this method

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/updates.getDifference b/data/corefork.telegram.org/method/updates.getDifference new file mode 100644 index 0000000000..f11b948f4f --- /dev/null +++ b/data/corefork.telegram.org/method/updates.getDifference @@ -0,0 +1,225 @@ + + + + + updates.getDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.getDifference

+ +

Get new updates.

+

+ +
+
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
+updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
+updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
+updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
+---functions---
+updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
ptsintPTS, see updates.
pts_total_limitflags.0?intFor fast updating: if provided and pts + pts_total_limit < remote pts, updates.differenceTooLong will be returned.
Simply tells the server to not return the difference if it is bigger than pts_total_limit
If the remote pts is too big (> ~4000000), this field will default to 1000000
dateintdate, see updates.
qtsintQTS, see updates.
+

Result

+

updates.Difference

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400DATE_EMPTYDate empty.
400MSG_ID_INVALIDInvalid message ID provided.
400PERSISTENT_TIMESTAMP_EMPTYPersistent timestamp empty.
400PERSISTENT_TIMESTAMP_INVALIDPersistent timestamp invalid.
+

Bots can use this method

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

updates.differenceTooLong

+

The difference is too long, and the specified state must be used to refetch updates.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/updates.getState b/data/corefork.telegram.org/method/updates.getState new file mode 100644 index 0000000000..373114c683 --- /dev/null +++ b/data/corefork.telegram.org/method/updates.getState @@ -0,0 +1,135 @@ + + + + + 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 new file mode 100644 index 0000000000..2b9b1435f7 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.getCdnFile @@ -0,0 +1,162 @@ + + + + + upload.getCdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getCdnFile

+ +

Download a CDN file.

+

+ +
+
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+---functions---
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_tokenbytesFile token
offsetintOffset of chunk to download
limitintLength of chunk to download
+

Result

+

upload.CdnFile

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.getCdnFileHashes b/data/corefork.telegram.org/method/upload.getCdnFileHashes new file mode 100644 index 0000000000..790a117a02 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.getCdnFileHashes @@ -0,0 +1,178 @@ + + + + + upload.getCdnFileHashes + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getCdnFileHashes

+ +

Get SHA256 hashes for verifying downloaded CDN files

+

+ +
+
---functions---
+upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_tokenbytesFile
offsetintOffset from which to start getting hashes
+

Result

+

Vector<FileHash>

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
400RSA_DECRYPT_FAILEDInternal RSA decryption failed.
+

Bots can use this method

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.getFile b/data/corefork.telegram.org/method/upload.getFile new file mode 100644 index 0000000000..7a66fffea1 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.getFile @@ -0,0 +1,252 @@ + + + + + upload.getFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getFile

+ +

Returns content of a whole file or its part.

+

+ +
+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+---functions---
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
preciseflags.0?trueDisable some checks on limit and offset values, useful for example to stream videos by keyframes
cdn_supportedflags.1?trueWhether the current client supports CDN downloads
locationInputFileLocationFile location
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
+

Result

+

upload.File

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
406FILEREF_UPGRADE_NEEDEDThe client has to be updated in order to support file references.
400FILE_ID_INVALIDThe provided file id is invalid.
400FILE_REFERENCE_*The file reference expired, it must be refreshed.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference.
400LIMIT_INVALIDThe provided limit is invalid.
400LOCATION_INVALIDThe provided location is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400OFFSET_INVALIDThe provided offset is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+

Related pages

+

Encrypted CDNs for Speed and Security

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.getFileHashes b/data/corefork.telegram.org/method/upload.getFileHashes new file mode 100644 index 0000000000..50904e8b90 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.getFileHashes @@ -0,0 +1,171 @@ + + + + + upload.getFileHashes + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getFileHashes

+ +

Get SHA256 hashes for verifying downloaded files

+

+ +
+
---functions---
+upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
locationInputFileLocationFile
offsetintOffset from which to get file hashes
+

Result

+

Vector<FileHash>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.getWebFile b/data/corefork.telegram.org/method/upload.getWebFile new file mode 100644 index 0000000000..2d89947e10 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.getWebFile @@ -0,0 +1,176 @@ + + + + + upload.getWebfile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getWebfile

+ +

Returns content of an HTTP file or a part, by proxying the request through telegram.

+

+ +
+
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
+---functions---
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
locationInputWebFileLocationThe file to download
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
+

Result

+

upload.WebFile

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.reuploadCdnFile b/data/corefork.telegram.org/method/upload.reuploadCdnFile new file mode 100644 index 0000000000..ea5626eeed --- /dev/null +++ b/data/corefork.telegram.org/method/upload.reuploadCdnFile @@ -0,0 +1,173 @@ + + + + + upload.reuploadCdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.reuploadCdnFile

+ +

Request a reupload of a certain file to a CDN DC.

+

+ +
+
---functions---
+upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_tokenbytesFile token
request_tokenbytesRequest token
+

Result

+

Vector<FileHash>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400RSA_DECRYPT_FAILEDInternal RSA decryption failed.
+

Bots can use this method

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.saveBigFilePart b/data/corefork.telegram.org/method/upload.saveBigFilePart new file mode 100644 index 0000000000..bca0225981 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.saveBigFilePart @@ -0,0 +1,208 @@ + + + + + upload.saveBigFilePart + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.saveBigFilePart

+ +

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_idlongRandom file id, created by the client
file_partintPart sequence number
file_total_partsintTotal number of parts
bytesbytesBinary data, part contents
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_EMPTYThe provided file part is empty.
400FILE_PART_INVALIDThe file part number is invalid.
400FILE_PART_SIZE_CHANGEDProvided file part size has changed.
400FILE_PART_SIZE_INVALIDThe provided file part size is invalid.
400FILE_PART_TOO_BIGThe uploaded file part is too big.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.saveFilePart b/data/corefork.telegram.org/method/upload.saveFilePart new file mode 100644 index 0000000000..d0a6bfa059 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.saveFilePart @@ -0,0 +1,183 @@ + + + + + upload.saveFilePart + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.saveFilePart

+ +

Saves a part of file for futher sending to one of the methods.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_idlongRandom file identifier created by the client
file_partintNumerical order of a part
bytesbytesBinary data, contend of a part
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FILE_PART_EMPTYThe provided file part is empty.
400FILE_PART_INVALIDThe file part number is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/users.getFullUser b/data/corefork.telegram.org/method/users.getFullUser new file mode 100644 index 0000000000..e795a3a644 --- /dev/null +++ b/data/corefork.telegram.org/method/users.getFullUser @@ -0,0 +1,177 @@ + + + + + users.getFullUser + + + + + + + + + + + + + +
+ +
+
+
+ +

users.getFullUser

+ +

Returns extended user info by ID.

+

+ +
+
users.userFull#3b6d152e full_user:UserFull chats:Vector<Chat> users:Vector<User> = users.UserFull;
+---functions---
+users.getFullUser#b60f5918 id:InputUser = users.UserFull;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputUserUser ID
+

Result

+

Returns a UserFull object containing user info.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/users.getUsers b/data/corefork.telegram.org/method/users.getUsers new file mode 100644 index 0000000000..87b937c920 --- /dev/null +++ b/data/corefork.telegram.org/method/users.getUsers @@ -0,0 +1,191 @@ + + + + + users.getUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

users.getUsers

+ +

Returns basic user info according to their identifiers.

+

+ +
+
---functions---
+users.getUsers#d91a548 id:Vector<InputUser> = Vector<User>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<InputUser>List of user identifiers
+

Result

+

Vector<User>

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONNECTION_NOT_INITEDConnection not initialized.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/users.setSecureValueErrors b/data/corefork.telegram.org/method/users.setSecureValueErrors new file mode 100644 index 0000000000..cad9ef4ede --- /dev/null +++ b/data/corefork.telegram.org/method/users.setSecureValueErrors @@ -0,0 +1,176 @@ + + + + + users.setSecureValueErrors + + + + + + + + + + + + + +
+ +
+
+
+ +

users.setSecureValueErrors

+ +

Notify the user that the sent passport data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).

+

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputUserThe user
errorsVector<SecureValueError>Errors
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/methods.html b/data/corefork.telegram.org/methods.html new file mode 100644 index 0000000000..c7575364c9 --- /dev/null +++ b/data/corefork.telegram.org/methods.html @@ -0,0 +1,2306 @@ + + + + + Methods + + + + + + + + + + + + + +
+ +
+
+
+ +

Methods

+ +

Accepting the Terms of Service

+ + + + + + + + + + + + + + + + + +
NameDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
help.acceptTermsOfServiceAccept the new terms of service
+

Dealing with spam and ToS violations

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.reportPeerReport a peer for violation of telegram's Terms of Service
account.reportProfilePhotoReport a profile photo of a dialog
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
messages.reportReport a message in a chat for violation of telegram's Terms of Service
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportEncryptedSpamReport a secret chat for spam
+

Fetching configuration

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.getAppChangelogGet changelog of current app.
Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.
help.getAppConfigGet app-specific configuration, see client configuration for more info on the result.
help.getAppUpdateReturns information on update availability for the current application.
help.getConfigReturns current configuration, including data center configuration.
help.getInviteTextReturns localized text of a text message with an invitation.
help.getNearestDcReturns info on data centre nearest to the user.
help.getSupportReturns the support user for the 'ask a question' feature.
help.getSupportNameGet localized name of the telegram support user
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
help.dismissSuggestionDismiss a suggestion, see here for more info ».
+

Login via QR code

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
auth.exportLoginTokenGenerate a login token, for login via QR code.
The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.

For more info, see login via QR code.
auth.acceptLoginTokenAccept QR code login token, logging in the app that generated it.

Returns info about the new session.

For more info, see login via QR code.
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
+

Miscellaneous

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.saveAppLogSaves logs of application on the server.
initConnectionInitialize connection
invokeAfterMsgInvokes a query after successfull completion of one of the previous queries.
invokeAfterMsgsInvokes a query after a successfull completion of previous queries
invokeWithLayerInvoke the specified query using the specified API layer
invokeWithoutUpdatesInvoke a request without subscribing the used connection for updates (this is enabled by default for file queries).
+

Registration/Authorization

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
auth.bindTempAuthKeyBinds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

For more information, see Perfect Forward Secrecy.
auth.cancelCodeCancel the login verification code
auth.checkPasswordTry logging to an account protected by a 2FA password.
account.resetPasswordInitiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »
auth.checkRecoveryPasswordCheck if the 2FA recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.logOutLogs out the user.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
auth.resetAuthorizationsTerminates all user's authorized sessions except for the current one.

After calling this method it is necessary to reregister the current device using the method account.registerDevice
auth.sendCodeSend the verification code for login
auth.signInSigns in a user with a validated phone number.
auth.signUpRegisters a validated phone number in the system.
+

Working with GDPR export

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.initTakeoutSessionInitialize account takeout session
account.finishTakeoutSessionFinish account takeout session
messages.getSplitRangesGet message ranges for saving the user's chat history
channels.getLeftChannelsGet a list of channels/supergroups we left
invokeWithMessagesRangeInvoke with the given message range
invokeWithTakeoutInvoke a method within a takeout session
+

Working with GIFs (actually MPEG4 GIFs)

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getSavedGifsGet saved GIFs
messages.saveGifAdd GIF to saved gifs list
messages.searchGifsSearch for GIFs
+

Working with Public Service Announcement and MTProxy channels

+ + + + + + + + + + + + + + + + + +
NameDescription
help.hidePromoDataHide MTProxy/Public Service Announcement information
help.getPromoDataGet MTProxy/Public Service Announcement information
+

Working with TSF (internal use only)

+ + + + + + + + + + + + + + + + + +
NameDescription
help.editUserInfoInternal use
help.getUserInfoInternal use
+

Working with 2FA login

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getPasswordObtain configuration for two-factor authorization with password
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
account.updatePasswordSettingsSet a new 2FA password
account.declinePasswordResetAbort a pending 2FA password reset, see here for more info »
+

Working with Seamless Telegram Login

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
account.getWebAuthorizationsGet web login widget authorizations
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
+

Working with VoIP calls

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
phone.acceptCallAccept incoming call
phone.confirmCallComplete phone call E2E encryption key exchange »
phone.discardCallRefuse or end running call
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.requestCallStart a telegram phone call
phone.saveCallDebugSend phone call debug data to server
phone.sendSignalingDataSend VoIP signaling data
phone.setCallRatingRate a call
messages.deletePhoneCallHistoryDelete the entire phone call history.
+

Working with channels/supergroups/geogroups

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
channels.createChannelCreate a supergroup/channel.
channels.getInactiveChannelsGet inactive channels and supergroups
channels.deleteChannelDelete a channel/supergroup
channels.deleteHistoryDelete the history of a supergroup
channels.deleteMessagesDelete messages in a channel/supergroup
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editBannedBan/unban/kick a user in a supergroup/channel.
channels.editCreatorTransfer channel ownership
channels.editLocationEdit location of geogroup
channels.editPhotoChange the photo of a channel/supergroup
channels.editTitleEdit the name of a channel/supergroup
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
channels.getAdminLogGet the admin log of a channel/supergroup
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
channels.getChannelsGet info about channels/supergroups
channels.getFullChannelGet full info about a channel
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups.

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.
channels.getMessagesGet channel/supergroup messages
channels.getParticipantGet info about a channel/supergroup participant
channels.getParticipantsGet the participants of a supergroup/channel
channels.inviteToChannelInvite users to a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.readHistoryMark channel/supergroup history as read
channels.readMessageContentsMark channel/supergroup message contents as read
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
channels.setStickersAssociate a stickerset to the supergroup
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
channels.toggleSignaturesEnable/disable message signatures in channels
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
+

Working with chats/supergroups/channels

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getMessageReadParticipantsGet which users read a specific message: only available for groups and supergroups with less than chat_read_mark_size_threshold members, read receipts will be stored for chat_read_mark_expire_period seconds after the message was sent, see client configuration for more info ».
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
messages.createChatCreates a new chat.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.editChatAboutEdit the description of a group/supergroup/channel.
messages.editChatAdminMake a user admin in a legacy group.
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.editChatTitleChanages chat name and sends a service message on it.
messages.exportChatInviteExport an invite link for a chat
messages.getAllChatsGet all chats, channels and supergroups
messages.getChatsReturns chat basic info on their IDs.
messages.getAdminsWithInvitesGet info about chat invites generated by admins.
messages.deleteExportedChatInviteDelete a chat invite
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteChatDelete a chat
messages.getCommonChatsGet chats in common with a user
messages.getFullChatReturns full chat info according to its ID.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
messages.migrateChatTurn a legacy group into a supergroup
channels.convertToGigagroupConvert a supergroup to a gigagroup, when requested by channel suggestions.
+

Working with deep links

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getDeepLinkInfoGet info about a t.me link
help.getRecentMeUrlsGet recently used t.me links
+

Working with files

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.getCdnConfigGet configuration for CDN file downloads.
upload.getCdnFileDownload a CDN file.
upload.getCdnFileHashesGet SHA256 hashes for verifying downloaded CDN files
upload.reuploadCdnFileRequest a reupload of a certain file to a CDN DC.
upload.getFileReturns content of a whole file or its part.
upload.getFileHashesGet SHA256 hashes for verifying downloaded files
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
+

Working with instant view pages

+ + + + + + + + + + + + + + + + + +
NameDescription
messages.getWebPageGet instant view page
messages.getWebPagePreviewGet preview of webpage
+

Working with secret chats

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.acceptEncryptionConfirms creation of a secret chat
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
messages.receivedQueueConfirms receipt of messages in a secret chat by client, cancels push notifications.
+

Working with telegram passport

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
account.verifyPhoneVerify a phone number for telegram passport.
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
account.getAuthorizationsGet logged-in sessions
account.deleteSecureValueDelete stored Telegram Passport documents, for more info see the passport docs »
account.getAllSecureValuesGet all saved Telegram Passport documents, for more info see the passport docs »
account.getSecureValueGet saved Telegram Passport document, for more info see the passport docs »
account.saveSecureValueSecurely save Telegram Passport document, for more info see the passport docs »
help.getPassportConfigGet passport configuration
users.setSecureValueErrorsNotify the user that the sent passport data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.
+

Working with updates

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
updates.getDifferenceGet new updates.
updates.getStateReturns a current state of updates.
+

Working with bot inline queries and callback buttons

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getInlineBotResultsQuery an inline bot
messages.setInlineBotResultsAnswer an inline query, for bots only
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
messages.editInlineBotMessageEdit an inline bot message
+

Working with bots

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
bots.getBotCommandsObtain a list of bot commands for the specified bot scope and language code
bots.setBotCommandsSet bot command list
+

Working with bots (internal bot API use)

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
bots.sendCustomRequestSends a custom request; for bots only
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
+

Working with cloud themes

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.updateThemeUpdate theme
account.uploadThemeUpload theme
account.getThemesGet installed themes
account.createThemeCreate a theme
account.installThemeInstall a theme
account.saveThemeSave a theme
account.getThemeGet theme information
account.getChatThemesGet all available chat themes
messages.setChatThemeChange the chat theme of a certain chat
+

Working with contacts and top peers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
contacts.addContactAdd an existing telegram user as contact.

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.
contacts.blockAdds the user to the blacklist.
contacts.deleteByPhonesDelete contacts by phone number
contacts.deleteContactsDeletes several contacts from the list.
contacts.getBlockedReturns the list of blocked users.
contacts.getContactIDsGet contact by telegram IDs
contacts.getContactsReturns the current user's contact list.
contacts.getLocatedGet contacts near you
contacts.getSavedGet all contacts
contacts.getStatusesReturns the list of contact statuses.
contacts.getTopPeersGet most used peers
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

Use contacts.addContact to add Telegram contacts without actually using their phone number.
contacts.resetSavedDelete saved contacts
contacts.resetTopPeerRatingReset rating of top peer
contacts.searchReturns users found by username substring.
contacts.toggleTopPeersEnable/disable top peers
contacts.unblockDeletes the user from the blacklist.
+

Working with credit cards

+ + + + + + + + + + + + + +
NameDescription
payments.getBankCardDataGet info about a credit card
+

Working with dialogs

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getDialogsReturns the current user dialog list.
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
messages.getDialogUnreadMarksGet dialogs manually marked as unread
messages.markDialogUnreadManually mark dialog as unread
messages.getPeerSettingsGet peer settings
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
messages.getOnlinesGet count of online users in a chat
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
+

Working with drafts

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.clearAllDraftsClear all drafts.
messages.getAllDraftsSave get all message drafts.
messages.saveDraftSave a message draft associated to a chat.
+

Working with emoji keywords

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getEmojiKeywordsGet localized emoji keywords
messages.getEmojiKeywordsDifferenceGet changed emoji keywords
messages.getEmojiKeywordsLanguagesGet info about an emoji keyword localization
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+

Working with folders

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.updateDialogFiltersOrderReorder folders
messages.getDialogFiltersGet folders
messages.getSuggestedDialogFiltersGet suggested folders
messages.updateDialogFilterUpdate folder
folders.deleteFolderDelete a peer folder
folders.editPeerFoldersEdit peers in peer folder
+

Working with games

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
+

Working with group calls & live streaming

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
phone.getGroupCallJoinAsGet a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
phone.editGroupCallParticipantEdit information about a given group call participant

Note: flags.N?Bool parameters can have three possible values:

- If the TL flag is not set, the previous value will not be changed.
- If the TL flag is set and contains a boolTrue, the previous value will be overwritten to true.
- If the TL flag is set and contains a boolFalse, the previous value will be overwritten to false.
phone.toggleGroupCallRecordStart or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).
phone.editGroupCallTitleEdit the title of a group call or livestream
phone.getGroupParticipantsGet group call participants
phone.checkGroupCallCheck whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs
phone.createGroupCallCreate a group call or livestream
phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
phone.leaveGroupCallLeave a group call
phone.toggleGroupCallSettingsChange group call settings
phone.inviteToGroupCallInvite a set of users to a group call.
phone.getGroupCallGet info about a group call
phone.joinGroupCallJoin a group call
phone.leaveGroupCallPresentationStop screen sharing in a group call
phone.discardGroupCallTerminate a group call
phone.joinGroupCallPresentationStart screen sharing in a call
phone.startScheduledGroupCallStart a scheduled group call.
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
+

Working with imported chats

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.uploadImportedMediaUpload a media file associated with an imported chat, click here for more info ».
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat, click here for more info ».

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
messages.checkHistoryImportObtains information about a chat export file, generated by a foreign chat app, click here for more info about imported chats ».
messages.initHistoryImportImport chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».
+

Working with localization packs

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
langpack.getDifferenceGet new strings in languagepack
langpack.getLangPackGet localization pack strings
langpack.getLanguageGet information about a language in a localization pack
langpack.getLanguagesGet information about all languages in a localization pack
langpack.getStringsGet strings from a language pack
+

Working with media autodownload settings

+ + + + + + + + + + + + + + + + + +
NameDescription
account.getAutoDownloadSettingsGet media autodownload settings
account.saveAutoDownloadSettingsChange media autodownload settings
+

Working with message threads

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getRepliesGet messages in a reply thread
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
messages.readDiscussionMark a thread as read
+

Working with message reactions

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getMessagesReactionsGet message reactions
messages.sendReactionSend reaction to message
messages.getMessageReactionsListGet full message reaction list
+

Working with messages

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.deleteHistoryDeletes communication history.
messages.deleteMessagesDeletes messages by their identifiers.
messages.editMessageEdit message
messages.forwardMessagesForwards messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.getMessageEditDataFind out if a media message's caption can be edited
messages.getMessagesReturns the list of messages by their IDs.
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
messages.getRecentLocationsGet live location history of a certain user
messages.getSearchCountersGet the number of results that would be found by a messages.search call with the same parameters
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.readHistoryMarks message history as read.
messages.readMentionsMark mentions as read
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
messages.receivedMessagesConfirms receipt of messages by a client, cancels PUSH-notification sending.
messages.searchGets back found messages
messages.searchGlobalSearch for messages and peers globally
messages.sendMediaSend a media
messages.sendMessageSends a message to a chat
messages.sendMultiMediaSend an album or grouped media
messages.updatePinnedMessagePin a message
messages.unpinAllMessagesUnpin all pinned messages
+

Working with notification settings

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.getNotifyExceptionsReturns list of chats with non-default notification settings
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
+

Working with other users

+ + + + + + + + + + + + + + + + + +
NameDescription
users.getFullUserReturns extended user info by ID.
users.getUsersReturns basic user info according to their identifiers.
+

Working with payments

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
payments.getSavedInfoGet saved payment information
payments.clearSavedInfoClear saved payment information
payments.getPaymentFormGet a payment form
payments.validateRequestedInfoSubmit requested order information for validation
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
account.getTmpPasswordGet temporary payment password
payments.sendPaymentFormSend compiled payment form
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
Use this method to respond to such pre-checkout queries.
Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
payments.getPaymentReceiptGet payment receipt
+

Working with polls

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getPollResultsGet poll results
messages.getPollVotesGet poll results for non-anonymous polls
messages.sendVoteVote in a poll
+

Working with scheduled messages

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.sendScheduledMessagesSend scheduled messages right away
messages.getScheduledHistoryGet scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
messages.getScheduledMessagesGet scheduled messages
+

Working with sensitive content (NSFW)

+ + + + + + + + + + + + + + + + + +
NameDescription
account.getContentSettingsGet sensitive content settings
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
+

Working with sponsored messages

+ + + + + + + + + + + + + + + + + +
NameDescription
channels.getSponsoredMessagesGet a list of sponsored messages
channels.viewSponsoredMessageMark a specific sponsored message as read
+

Working with sponsored proxies

+ + + + + + + + + + + + + +
NameDescription
help.getProxyDataGet promotion info of the currently-used MTProxy
+

Working with statistics

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
stats.loadAsyncGraphLoad channel statistics graph asynchronously
stats.getBroadcastStatsGet channel statistics
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.
stats.getMegagroupStatsGet supergroup statistics
stats.getMessageStatsGet message statistics
+

Working with stickers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getOldFeaturedStickersMethod for fetching previously featured stickers
messages.toggleStickerSetsApply changes to multiple stickersets
stickers.suggestShortNameSuggests a short name for a given stickerpack name
stickers.checkShortNameCheck whether the given short name is available
stickers.setStickerSetThumbSet stickerset thumbnail
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
messages.clearRecentStickersClear recent stickers
messages.faveStickerMark a sticker as favorite
messages.getAllStickersGet all installed stickers
messages.getArchivedStickersGet all archived stickers
messages.getAttachedStickersGet stickers attached to a photo or video
messages.getFavedStickersGet faved stickers
messages.getFeaturedStickersGet featured stickers
messages.getMaskStickersGet installed mask stickers
messages.getRecentStickersGet recent stickers
messages.getStickerSetGet info about a stickerset
messages.getStickersGet stickers by emoji
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.installStickerSetInstall a stickerset
messages.readFeaturedStickersMark new featured stickers as read
messages.reorderStickerSetsReorder installed stickersets
messages.searchStickerSetsSearch for stickersets
messages.uninstallStickerSetUninstall a stickerset
+

Working with the user's account

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.changePhoneChange the phone number of the current account
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.getAccountTTLGet days to live of account
account.getPrivacyGet privacy settings of current account
account.resetAuthorizationLog out an active authorized session by its hash
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.setAccountTTLSet account self-destruction period
account.setPrivacyChange privacy settings of current account
account.setGlobalPrivacySettingsSet global privacy settings
account.getGlobalPrivacySettingsGet global privacy settings
account.updateProfileUpdates user profile.
account.updateStatusUpdates online user status.
+

Working with user profile pictures

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
photos.deletePhotosDeletes profile photos.
photos.getUserPhotosReturns the list of user photos.
photos.updateProfilePhotoInstalls a previously uploaded photo as a profile photo.
photos.uploadProfilePhotoUpdates current user profile photo.
+

Working with usernames

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
account.updateUsernameChanges username for the current user.
account.checkUsernameValidates a username and checks availability.
contacts.resolveUsernameResolve a @username to get peer info
+

Working with wallpapers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.getMultiWallPapersGet info about multiple wallpapers
account.getWallPaperGet info about a certain wallpaper
account.getWallPapersReturns a list of available wallpapers.
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveWallPaperInstall/uninstall wallpaper
account.uploadWallPaperCreate and upload a new wallpaper
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto.html b/data/corefork.telegram.org/mtproto.html new file mode 100644 index 0000000000..430aa6a267 --- /dev/null +++ b/data/corefork.telegram.org/mtproto.html @@ -0,0 +1,260 @@ + + + + + MTProto Mobile Protocol + + + + + + + + + + + + + +
+ +
+
+
+
+

MTProto Mobile Protocol

+ +
+ +
+

Please feel free to check out our FAQ for the Technically Inclined. +Client developers are required to comply with the Security Guidelines.

+
+

Related articles

+

+
+

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

+ +

General Description

+

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

+

The protocol is subdivided into three virtually independent components:

+
    +
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • +
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • +
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as HTTP, HTTPS, WS (plain websockets), WSS (websockets over HTTPS), TCP, UDP).
  • +
+ +
+

As of version 4.6, major Telegram clients are using MTProto 2.0, described in this article. +MTProto v1.0 (described here for reference) is deprecated and is currently being phased out.

+
+

Brief Component Summary

+

High-Level Component (RPC Query Language/API)

+

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific websocket/http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

+

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

+

There are several types of messages:

+
    +
  • RPC calls (client to server): calls to API methods
  • +
  • RPC responses (server to client): results of RPC calls
  • +
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • +
  • Message status query
  • +
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • +
+

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

+

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

+

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

+

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is how the OpenSSL library does it.

+

Authorization and Encryption

+

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 middle bits of the SHA256 of the message body (including session, message ID, etc.), including the padding bytes, prepended by 32 bytes taken from the authorization key. Multipart messages are encrypted as a single message.

+
+

For a technical specification, see Mobile Protocol: Detailed Description

+
+

The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

+

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

+
    +
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • +
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • +
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to that data.
  • +
+

Time Synchronization

+

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

+

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

+

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

+

MTProto transport

+

Before being sent using the selected transport protocol, the payload has to be wrapped in a secondary protocol header, defined by the appropriate MTProto transport protocol.

+ +

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header. +Additionally, the following transport features can be used:

+ +

Example implementations for these protocols can be seen in tdlib and MadelineProto.

+

Transport

+

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. +Multiple transport protocols are defined:

+ +

(We shall examine only the first five types.)

+

Recap

+

To recap, using the ISO/OSI stack as comparison:

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-abstract-types.html b/data/corefork.telegram.org/mtproto/TL-abstract-types.html new file mode 100644 index 0000000000..f23f8d5c88 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-abstract-types.html @@ -0,0 +1,202 @@ + + + + + Binary serialization and abstract TL types + + + + + + + + + + + + + +
+ +
+
+
+ +

Binary serialization and abstract TL types

+ +

TL Language defines abstract data types in the spirit of a general theory of types (more accurately, Martin-Löf’s theories of dependent intuitionistic types) without specifying the values of these types should be represented in memory, when saved to disk, or transmitted over a network. In contrast, the article on binary serialization discusses the problem of effective serialization of values of abstract types. To this end, the concept of a concrete or serialized type has been defined as the sets of serializations of all possible values of the corresponding abstract type. In this case, the serializations take values in the set A of words in the alphabet A*, which consists of 2^32 characters -- 32-bit integers.

+

In order to use a TL schema (e.g. “program”) in the TL language to describe the serialization of values of abstract types, we should explain how the concrete type [T] (subset [T] of A^) is associated with the abstract type T (defined in TL), and how the values of the abstract type T correspond to the values of the concrete type [T] (i.e. the elements of [T]*).

+

Serialization is the process of constructing an element of [T] based on a value of the abstract type T. The reverse process is deserialization.

+

Values of the abstract type T may be represented in a different way. Typically, some sort of trees or graphs are used in memory or, if desired, a set of nodes may be used, each of which contains a certain tag (“node type”) and several pointers to other nodes and/or values of built-in primitive types such as int. However, for general discussions it is useful to write the values of abstract type T as a string, more specifically, an S-expression. Recall that an S-expression is either an atom (the value of a primitive type, for example, an integer or a string constant in quotation marks; or an identifier that corresponds to a built-in or defined function) or a space-delimited list of S-expressions ending in parentheses. In our case, we use S-expressions, the first element of which is a combinator identifier, while the remaining elements (the number of which depends on the combinator’s arity) are S-expressions representing elements of the chosen combinator’s fields (or parameters). Moreover, the type of the arguments’ S-expressions and the type of the S-expressions of the result (e.g. the associated expression) must match.

+

For example, for the schema

+
pair x:int y:int = Pair;
+pnil = PairList;
+pcons hd:Pair tl:PairList = PairList;
+

the following are examples of the abstract type PairList, written as S-expressions:

+
(pnil)
+(pcons (pair 2 3) (pcons (pair 9 4) (pnil)))
+

We usually write E : T (read "E of type T”) when we want to say that E is a value of type T. We assume there is a built-in type Type whose values are types. Thus, writing T : Type means that T is a type.

+

For example, we can write:

+
PairList : Type;
+(pcons (pair 2 3) (pcons (pair 9 4) (pnil))) : PairList;
+

Converting an abstract value to a serialized value, generally speaking, is straightforward (and, if desired, can be defined by induction):

+
    +
  • +

    It is the serialization of values n of the primitive type int (as a single-symbol word in the alphabet A)

    +
  • +
  • +

    The serialization of a string constant (a value of the primitive type string) is a sequence of the 32-bit numbers defined in Binary serialization.

    +
  • +
  • +

    The serialization of the S-expression (C E1 ... Er) : T, where C is a combinator with arity r with argument types T1, ..., Tr and result type T (e.g. C : T1->T2->...->Tr->T) is the concatenation of the combinator number C (a 32-bit number that unambiguously identifies the combinator, usually equal to the CRC-32 of the string of its TL description) and the serializations of the values E1 of type T1, E2 of type T2, ..., Er of type Tr.

    +
  • +
+

If we use [T] to denote the concrete type corresponding to the abstract T, and [E] to denote an element of [T] corresponding to the value E of type T, then the last rule may be written as:

+
    +
  • [T] is the combination, for each constructor of type C T1->T2->...->Tr->T (i.e. that returns a value of type T), of direct products {C} x [T1] x [T2] x ... x [Tr], where {C} is a single-element set consisting of the combinator number C. Because {C}<>{C'} when C<>C’, this defines a mutually single-valued mapping of the values of the abstract type T (written using S-expressions) to the set [T].
  • +
+

Values of the built-in clothed types Int and String and serialized as if they were defined using int x:int = Int; and string s:string = String;, i.e. the serialization of integer constant or a string is preceded by number of the int or string combinator (constructor). In S-expressions, this may be written as (int 5) or (string "Test").

+

However, what has been described above does not account for certain subtleties, such as the existence of naked types, or the difference between functions (active combinators whose application may be reduced, e.g. calculated) and constructors (passive combinators for which there are not and cannot be reduction rules). Furthermore, we have not explained how to handle polymorphic types and optional combinator parameters. We will attempt to explain this now.

+

Constants, surface values, and functional values

+

By dividing combinators into constructors and functions, we can introduce the following classes of expressions (values) of the abstract type T:

+
    +
  • +

    Constant expressions: for the types int and string, these are all integer/string constants; for T, these are all expressions like (C E1 ... Er) : T, where the combinator C : T1->T2->...->Tr->T is a constructor, and Ei : Ti is constant expressions of types Ti. In other words, a constant expression is an S-expression consisting of only constructors and constant of primitive types.

    +
  • +
  • +

    Surface expressions are expressions that outwardly contain a functional combinator whose arguments, however, are constant expressions of the appropriate types. In other words, the functional combinator is resolved only at the outer level. (This is not entirely true; see the full explanation below).

    +
  • +
  • +

    Functional expressions: These are expressions that may contain any combinators or constants at all levels.

    +
  • +
+

In practice, we most frequently need constant values (for storage and passing any data structures, in particular, responses to RPC queries) and surface expressions (for example, as RPC queries: then the functional combinator of the outer level is the name of the RPC function that we want to call, while its parameters are the arguments, which are constant values, for invoking the function). In some cases, arbitrary functional expressions are helpful (for example, it we want to remotely transmit the result of one RPC query to a different RPC query).

+

We will use c(T) to denote a subtype of the abstract type T, whose values are constant expressions of type T. Clearly, c(T) possesses approximately the same constructors as T itself (with the types of all arguments Ti replaced by c(Ti), but it does not have functional combinators.

+

Analogously, we will use f(T) to denote a subtype of T, whose values are surface expressions of type T. Clearly, the combinators of f(T) are essentially functional combinators of type T, but c() applies to the types of these combinators’ arguments: The combinator A : T1->...->Tr->T turns into A' : c(T1)->...->c(Tr)->f(T). (See the clarification of this rule below.)

+

Thus, we have defined two “functionals” c : Type -> Type and f : Type -> Type, such that forall T : Type, c(T) :- T and forall T : Type, f(T) :- T (writing T :- T' means that T is contained in T', or that T is a subtype of T').

+

We will assume that c and f are idempotent.

+

Naked types

+

From the perspective of abstract type theory, naked types (in contrast to built-in primitive types like int and string are unnecessary. However, they are extremely useful in practice.

+

Therefore, TL introduces the (partially defined) idempotent unary operator %, which turns a standard functional (e.g. an expression of type ...->Type or simply Type) into a different standard functional of the same type. If T is a type, then from an abstract theoretical point of view, %T is equivalent to c(T). In other words, the values of %T are the constant values of T. If T is a k-arity standard expression, then T : S1 -> ... -> Sk -> Type, where each Si=Type or #, then by definition %T is a k-arity standard expression with the same arity, which is defined by the equation (%T) a1 ... ak = % (T a1 ... ak).

+

When a constant value of type %T is serialized, it is first serialized as a value of type T (assuming that T is not already a naked type itself). Then the first character of the serialization is discarded (e.g. the name of the enclosing combinator). Therefore, %T is a only a valid type expression if there is not more than one constructor for %T. The expression %T, where T : S1 -> ... -> Sk -> Type, is valid, if for any choice of parameters a1 : S1, ... , ak : Sk, the type T a1 ... ak does not have more than one constructor. Using % in other instances is incorrect.

+

If for every value of the parameters a1 : S1, ..., ak : Sk, there is exactly one constructor C for T a1 ... ak, then TL allows writing C a1 ... ak instead of %T a1 ... ak or %(T a1 .. ak). In other words, in certain situations the identifier C is a synonym for %T. This is only allowed in the context of a type (when specifying the type of a combinator’s field or result).

+

Moreover, it is assumed that %Int = int and %String = string.

+

! modifier

+

In TL, the idempotent operator ! can modify any type, actually making surface values be allowed when its constant values are serialized. However, if T is a standard function like S1->..->Sr->Type, then !T is defined using the equation (!T) a1 ... ar = !(T a1 ... ar), for any a1:S1, ..., ar:Sr.

+

The ! operator is only allowed in a definition of the types of fields of functional combinators. It is usually used as a type prefix, for example:

+
set_timeout {X:Type} timeout:int f:!X = X;
+

In this case, the set_timeout “wrapper” is defined. It takes two explicit parameters: the integer timeout and a surface expression of type X. X : Type is itself an implicit parameter (it is not explicitly stated, rather it is inferred from the values of the other parameters and their types). A similar kind of wrapper may be helpful for modifying the action of RPC queries (which are surface expressions of various types). For example, suppose we have the function

+
factorial n:int = int;
+

then we can wrap the RPC query (factorial 100) as follows: (set_timeout 200 (factorial 100)). This expression is still a surface value of type int, which means it can be passed as an RPC query.

+

A consecutive pair of two computations is another example:

+
pair {X Y : Type} x:X y:Y = Pair X Y;  // constructor
+seq_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for sequential computation
+par_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for parallel computation
+

Now the RPC query (seq_pair (factorial 2) (factorial 3)) : Pair int int first calculates factorial 2, then factorial 3, and returns the pair (pair 2 6). In this case, the sequence of operations isn’t important, because they do not have side effects. It would have been just as well to use (par_pair (factorial 2) (factorial 3)). However, this is not always the case.

+

We can also define an analogy to a “comma” operation:

+
comma {X Y : Type} x:!X y:!Y = Y;
+

For example, this operation could first calculate x, then forget the result, calculate y, and return y.

+

Note that the semantics of the seq_pair, par_pair and comma wrappers are indeed defined where they are implemented (like the semantics of all other functional combinators), not by their TL declaration.

+

In principle, polymorphic wrappers like set_timeout can also be applied, for example, to “annotate” a RPC response’s constant values. For example, the server might return a response to a query together with the time it was calculated. However, a value of type !X must be constant, because that is what is expected as the enclosing expression’s value. In other words, set_timeout 239 E is a constant/surface value of type X if and only if E is such itself.

+

$ modifier

+

The idempotent modifier $ permits the use of arbitrary functional values of an appropriate type in contexts where only constants or surface values are usually allowed. It recursively transforms all combinators for all of the types involved, canceling the action of % and affixing $ to the parameter types and result of all combinators ($ is also added to the front of the transformed combinators). Moreover, built-in types are also transformed (in the final stage): $int = Int and $string = String.

+

This may be useful to create an RPC query that performs a “deep computation” of the expression passed to it:

+
compute {X:Type} expr:$X = X;
+

For example, now we can transmit the following as an RPC query:

+
(compute ($factorial ($factorial (int 3)))) : int
+

(Note that the three has become clothed; the combinator $factorial has type $int -> $int).

+

This is very powerful tool. It does not have to be implemented in very simple versions of TL. $ is not encountered in currently used TL schemas.

+

More on modifiers

+

In fact, at least in terms of its application to serialization, the TL language by default implies the c() modifier around all combinators’ parameter types and results, while ! and $ cancel it (more accurately, ! only cancels, and in some sense $ reverses the meaning). This is why there is no explicit c() modifier in TL and why it is assumed that all functions only accept constant values and return constant results, unless otherwise specified.

+

You may think that some functional combinators may have a type such as partial_factorial n:int = $int; and that the RPC query (partial_factorial 3) might then unexpectedly return ($product (int 3) ($product (int 2) ($product (int 1) (int 1)))) : $int ...

+

It is probably more correct to think about the ! modifier as follows. All types initially include only constant values (and only constructors). The ! modifier makes a new type (it’s twin) out of each type. This new type has no inherent constructors. Functional combinators differ from constructors in that ! is implicitly added in front of their result’s type. After this, the (local or remote) process of calculating the expression can be represented using the polymorphic function eval : !X -> X.

+

Optional combinator parameters and their values

+

See Optional combinator parameters and their values.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-combinators.html b/data/corefork.telegram.org/mtproto/TL-combinators.html new file mode 100644 index 0000000000..4d6c7dc85c --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-combinators.html @@ -0,0 +1,251 @@ + + + + + Formal description of TL combinators + + + + + + + + + + + + + +
+ +
+
+
+ +

Formal description of TL combinators

+ +

Formal declaration of TL combinators

+

Main article: Formal description of TL. See also TL Language.

+

Combinators in TL are declared as follows:

+
+

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
+full-combinator-id ::= lc-ident-full | _
+combinator-id ::= lc-ident-ns | _
+opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
+args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
+args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
+args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
+args ::= [ ! ] type-term
+multiplicity ::= nat-term
+var-ident-opt ::= var-ident | _
+conditional-arg-def ::= var-ident [ . nat-const ] ?
+result-type ::= boxed-type-ident { subexpr }
+result-type ::= boxed-type-ident < subexpr { , subexpr } >

+
+

We shall clarify what all this means.

+
    +
  • +

    A combinator identifier is either an identifier starting with a lowercase Latin letter (lc-ident), or a namespace identifier (also lc-ident) followed by a period and another lc-ident. Therefore, cons and lists.get are valid combinator identifiers.

    +
  • +
  • +

    A combinator has a name, also known as a number (not to be confused with the designation) -- a 32-bit number that unambiguously determines it. It is either calculated automatically (see below) or it is explicitly assigned in the declaration. To do this, a hash mark (#) and exactly 8 hexadecimal digits -- the combinator’s name -- are added to the identifier of the combinator being defined.

    +
  • +
  • +

    A combinator’s declaration begins with its identifier, to which its name (separated by a hash mark) may have been added.

    +
  • +
  • +

    After the combinator identifier comes the main part of the declaration, which consists of declarations of fields (or variables), including an indication of their types.

    +
  • +
  • +

    First come declarations of optional fields (of which there may be several or none at all). Then there are the declarations of the required fields (there may not be any of these either).

    +
  • +
  • +

    Any identifier that begins with an uppercase or lowercase letter and which does not contain references to a namespace can be a field (variable) identifier. Using uc-ident for identifiers of variable types and lc-indent for other variables is good practice.

    +
  • +
  • +

    Next a combinator declaration contains the equals sign (=) and the result type (it may be composite or appearing for the first time). The result type may be polymorphic and/or dependent; any fields of the defined constructor’s fields of type Type or # may be returned (as subexpressions).

    +
  • +
  • +

    A combinator declaration is terminated with a semicolon.

    +
  • +
+

In what follows, a constructor’s fields, variables, and arguments mean the same thing.

+

Optional field declarations

+
    +
  • +

    These have the form { field_1 ... field_k : type-expr }, where field_i is a variable (field) identifier that is unique within the scope of the combinator declaration, and type-expr is a type shared by all of the fields.

    +
  • +
  • +

    If k>1, this entry is functionally equivalent to { field_1 : type-expr } ... { field_k : type-expr }.

    +
  • +
  • +

    All optional fields must be explicitly named (using _ instead of field_i is not allowed).

    +
  • +
  • +

    Moreover, at present the names of all optional fields must share the combinator’s result type (possibly more than once) and themselves be of type # (i,e., nat) or Type. Therefore, if the exact result type is known, it is possible to determine the values of all of the combinator’s implicit parameters (possibly obtaining a contradiction of the form 2=3 in doing so, which means that the combinator is not allowed in the context).

    +
  • +
+

Required field declarations

+
    +
  • +

    These may have the form ( field_1 ... field_k : type-expr ), similar to an optional field declaration, but with parentheses. This entry is equivalent to ( field_1 : type-expr ) ... ( field_k : type-expr ), where the fields are defined one at a time.

    +
  • +
  • +

    The underscore sign (_) can be used as names of one or more fields (field_i), indicating that the field is anonymous (the exact name is unimportant).

    +
  • +
  • +

    One field may be declared without outer parentheses, like this: field_id : type-expr. Here, however, if type-expr is a complex type, parentheses may be necessary around type-expr (this is reflected in BNF).

    +
  • +
  • +

    Furthermore, one anonymous field may be declared using a type-expr entry, functionally equivalent to _ : type-expr.

    +
  • +
  • +

    Required field declarations follow one after another, separated by spaces (by any number of whitespace symbols, to be more precise).

    +
  • +
  • +

    The declared field’s type (type-expr) may use the declared combinator’s previously defined variables (fields) as subexpressions (i.e. parameter values). For example:

    +

    nil {X:Type} = List X; +cons {X:Type} hd:X tl:(list X) = List X; +typed_list (X:Type) (l : list X) = TypedList;

    +
  • +
+

Repetitions

+
    +
  • +

    These may only exist among required parameters. They have the form [ field-id : ] [ multiplicity * ] [ args ], where args has the same format as the combinator’s declaration of (several) required fields, except that all of the enclosing combinator’s previously declared fields may be used in the argument types.

    +
  • +
  • +

    The name of a field of an enclosing combinator that receives a repetition as a value may be specified (field-id), or bypassed, which is equivalent to using the underscore sign as a field-id.

    +
  • +
  • +

    The multiplicity field is an expression of the type # (nat), which can be a real constant, the name of a preceding field of type #, or an expression in the form ( c + v ), where c is a real constant and v is the name of a field of type #. The sense of the multiplicity field is to provide the length of the (repetition) vector, each element of which consists of values of the types enumerated in args.

    +
  • +
  • +

    The multiplicity field may be bypassed. In this case, the last preceding parameter of type # from the enclosing combinator is used (it must be).

    +
  • +
  • +

    Functionally, the repetition field-id : multiplicity * [ args ] is equivalent to the declaration of the single field ( field-id : %Tuple %AuxType multiplicity ), where aux_type is an auxiliary type with a new name defined as aux_type *args* = AuxType. If any of the enclosing type’s fields are used within args, they are added to the auxiliary constructor aux_type and to its AuxType result type as the first (optional) parameters.

    +
  • +
  • +

    If args consists of one anonymous field of type some-type, then some-type can be used directly instead of %AuxType.

    +
  • +
  • +

    If during implementation the repetitions are rewritten as indicated above, it is logical to use instead of aux_type and AuxType, some identifiers that contain the name of the outer combinator being defined and the repetition’s index number inside its definition.

    +
  • +
+

Example:

+
matrix {m n : #} a : m* [ n* [ double ] ] = Matrix m n;
+

is functionally equivalent to

+
aux_type {n : #} (_ : %Tuple double n) = AuxType n;
+matrix {m : #} {n : #} (a : %Tuple %(AuxType n) m) = Matrix m n;
+

Moreover, the built-in types Tuple and Vector could be defined as:

+
tnil {X : Type} = Tuple X 0;
+tcons {X : Type} {n : #} hd:X tl:%(Tuple X n) = Tuple X (S n);
+vector {X : Type} (n : #) (v : %(Tuple X n)) = Vector X;
+

Actually, the following equivalent entry is considered the definition of Vector (i.e. it is specifically this entry that is used to compute the name of the vector constructor and its partial applications):

+
vector {t : Type} # [ t ] = Vector t;
+

If we expand it using Tuple, we obtain the previous definition exactly.

+

Conditional fields

+

The construction

+
+

args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
+conditional-arg-def ::= var-ident [ . nat-const ] ?

+
+

permits assigning fields which are only present if the value of a preceding mandatory or optional field of type # is not null (or if its chosen bit is not zero if the special binary bit-selection operator . is applied). +Example:

+
+

user {fields:#} id:int first_name:(fields.0?string) last_name:(fields.1?string) friends:(fields.2?%(Vector int)) = User fields;
+get_users req_fields:# ids:%(Vector int) = Vector %(User req_fields)

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-dependent.html b/data/corefork.telegram.org/mtproto/TL-dependent.html new file mode 100644 index 0000000000..bb1c22e608 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-dependent.html @@ -0,0 +1,236 @@ + + + + + TL-dependent + + + + + + + + + + + + + +
+ +
+
+
+ +

TL-dependent

+ +

Main article: TL Language.

+

In certain cases, types may depend not only on other types (polymorphism), but also on the parameters of another type (dependent types). The TL language provides very limited support for this functionality: dependence is only allowed on a natural parameter whose type is designated using # (alias nat, but this is private -- TL doesn’t currently support this synonym). Values of type # are serialized as 32-bit signed numbers from 0 to 2^31-1.

+

Example: integer tuples (vectors)

+

Suppose we want to use induction to define the types “one integer”, “two integers”, and “three integers”. We could try to define them as follows:

+
empty = Empty;
+single x:int = Single;
+pair x:int y:int = Pair;
+triple x:int y:int z:int = Triple;
+quadruple x:int y:int z:int t:int = Quadruple;
+...
+

or as:

+
empty = Empty;
+single x:int empty = Single;
+pair x:int y:single = Pair;
+triple x:int yz:pair = Triple;
+quadruple x:int yzt:triple = Quadruple;
+

or as:

+
tnil = Tuple0;
+tcons0 hd:int tl:Tuple0 = Tuple1;
+tcons1 hd:int tl:Tuple1 = Tuple2;
+tcons2 hd:int tl:Tuple2 = Tuple3;
+...
+tcons_n hd:int tl:Tuple_n = Tuple_(n+1)
+

The first two variations lead to the same serialization. For example, (2 3 9):%triple and (2 (3 9)):%triple serialize as three 32-bit numbers: 2 3 9. The last variation better emphasizes the inductive version of the definition, but it uses boxed types. This is good from a theoretical perspective, but it leads to “superfluous” constructor names in serialization.

+

Therefore, we will write %Type-Ident to indicate the bare type that corresponds to the boxed type Type-Ident with a single constructor. If this constructor is named constructor, then according to the definition %Type-Ident = %constructor. Now we can write our definition like this:

+
tnil = Tuple0;
+tcons_n hd:int tl:%Tuple_n = Tuple_(n+1)
+

If we now abstract n out of the name of the type name and make it like a parameter for a polymorphic (dependent, to be more exact) type, then something like the following can be written in a suitable functional language:

+
NewType Tuple (n : #) :=
+| tnil = Tuple 0
+| tcons n:# hd:int tl:%(Tuple n) = Tuple (S n)
+EndType;
+

In the TL language, it looks like this:

+
tnil = Tuple 0;
+tcons {n:#} hd:int tl:%(Tuple n) = Tuple (S n);
+

The function S : # -> # and the constant O : # (it is 0) are the function for the next natural number (S n = n + 1) and the constant null. Therefore, the type # (alias nat) behaves as if it were defined in TL using the constructors

+
O = nat;
+S nat = nat;
+

or, using syntax more typical of other functional languages,

+
NewType nat :=
+| O
+| S nat
+EndType;
+

Types of all defined combinators:

+
O : #
+S : # -> #
+Tuple : # -> Type
+tnil : Tuple 0
+tcons : forall n : #, int -> Tuple n -> Tuple (S n)
+

or

+
Tuple : forall n : #, Type;
+tcons : forall n : #, forall hd : int, forall tl : Tuple n, Tuple (S n)
+

Note that in this case the constructor tnil does not depend on the parameter n, while tcons does.

+

In an analogous manner, it is possible to define a complete binary tree of height h with strings in the leaf nodes:

+
tleaf value:string = BinTree 0;
+tnode {h:#} left:(BinTree h) right:(BinTree h) = BinTree (S h);
+

Or a random tree whose leaf nodes are all a distance of h from the root and whose nodes are all labeled with integers:

+
hleaf value:int = Tree 0;
+hnode {n:#} left:(Tree n) next:(Tree (S n)) = Tree (S n)
+hnil {n:#} = Tree (S n)
+

Another version:

+
hleaf' value:int = Tree' 0;
+hnode' {n:#} children:(list (Tree' n)) = Tree' (S n)
+

Polymorphic dependent types

+

Let us try to define a type Tuple X n whose values are n-tuples of type X values. In this way, Tuple will be simultaneously polymorphic and dependent:

+
Tuple : Type -> # -> Type;
+

In the familiar syntax of functional languages:

+
NewType Tuple {X : Type} {n : #} :=
+| vnil : Tuple X 0
+| vcons {n:#} hd:X tl:%(Tuple X n) : Tuple X (S n)
+EndType
+

or, in TL syntax,

+
vnil {X:Type} = Tuple X 0;
+vcons {X:Type} {n:#} tl:(%Tuple X n) = Tuple X S n
+

In the end we obtain terms for the following types:

+
vnil : forall X : Type, Tuple X 0
+vcons : forall X : Type, forall n : #, X -> Tuple X n -> Tuple X (S n)
+

or

+
vnil : forall X : Type, Tuple X 0
+vcons : forall X : Type, forall n : #, forall hd : X, forall tl : Tuple X n, Tuple X (S n)
+

Dependent sums

+

The Tuple we just defined differs from the built-in Vector type. Specifically, the Vector type formally depends on a single argument (a type), but our Tuple depends on two (a type and a number):

+
Tuple : Type -> # -> Type;
+Vector : Type -> Type;
+

The built-in Vector could be defined in terms of our Tuple using “summing across all n : #":

+
vector {X:Type} n:# v:(%Tuple X n) = Vector X;
+

Nevertheless, our Tuple has its advantages. For example, we can define data types such as:

+
matrix_10x10 a:(%Tuple (%Tuple double 10) 10) = Matrix_10x10;
+

In any event, remember that during calculation of the matrix_10x10 combinator’s number, all parentheses must be removed and the CRC32 of the string matrix_10x10 a:%Tuple %Tuple double 10 10 = Matrix_10x10 must be computed.

+

Moreover, we can define arbitrarily-sized matrices:

+
matrix {X:Type} m:# n:# a:(%Tuple (%Tuple X m) n) = Matrix X;
+

In this case using vector would result in storing the length of a row (m) in each row, e.g. n times.

+

Note that the serializations of values of type %Tuple X n and vector X (also known as %vector X and %Vector X) nearly match when n > 0: in both cases we obtain a single 32-bit number (equal to n-1 or n depending on the version) followed by the serializations of n objects of type X. (This is slightly untrue: values of type %Tuple X n can only be serialized if n is a constant or value known from one of the preceding fields of the enclosing entry; but then this n won’t be serialized explicitly anywhere).

+

Special syntax for repetitions

+

In view of the importance of the construction presented above, it is built into the TL language in the following manner. A substructure in the form of [ array-field-name ":" ] [ nat-ident "" ] "[" field-descr ... "]” may be used in the declaration of any combinator, where nat-ident* is the name of any previously encountered field of type # (if it is not explicitly indicated, the most recent is used). In abstract, this substructure is equivalent to:

+
aux_type *field-descr* ... = AuxType;
+*current_constructor* ... [ *array-field-name* ":" ] (%Tuple aux_type *nat-ident*)
+

For example, 10x10 matrices, vectors, and arbitrary matrices may be defined in the following way:

+
matrix {X:Type} m:# n:# a:n*[ m*[ X ] ] = Matrix X;
+matrix_10x10 a:10*[ 10*[ double ]] = Matrix_10x10;
+vector {X:Type} # [ X ] = Vector X;
+

We have already encountered the last version as a “definition” of the “built-in type” Vector.

+

Of course, several fields, as complex as desired, may be within the repeating part. Furthermore, besides using n as a repeat counter, one may use expressions of the form (n+const) and (const+n), where const is a small nonnegative constant, which are shorthand for S (S ( ... (S n) ... )):

+
repeat_np1 n:# a:(S n)*[ key:string value:string ] = Dictionary;
+

To calculate the CRC32 these expressions are converted to expressions of the form (const+X) without internal spaces. Additionally, the * in this case is not set off by spaces on the left and right.

+

Serialization of dependent types

+

Serialization of dependent types and polymorphic types is not a fundamental challenge: we have combinators with non-zero arity with Type values. For example, the type Tuple double 10 : Type serializes to 'Tuple' '%double' 10. Note that at present in practice there is virtually no need to serialize types, whether dependent or not.

+

Optional combinator parameters in TL

+

Optional combinator parameters in TL must possess the following properties:

+
    +
  • +

    Optional parameters must be precisely ythe combinator’s first several arguments;

    +
  • +
  • +

    The value of any optional parameter must be entirely determined by the combinator’s result type.

    +
  • +
+

For example, in cons {X:Type} hd:X tl:(list X) = list X the parameter X may be made optional, because it is located at the very beginning of the argument list and is unambiguously determined by the list X result type. Similarly, in tcons {X:Type} {n:#} hd:X tl:(%Tuple X n) = Tuple X (S n) the values of X and n are completely determined based on the Tuple X (S n) result type, therefore they made be made optional parameters.

+

It usually makes sense to move all of a constructor’s arguments satisfying the second condition to the beginning of the list, arrange them in the order they appear in the result type’s parameters, and make them optional. Given such an approach, the full version of a constructor is rarely needed -- only when we want to transmit the value of the polymorphic or dependent type as a value of type Object. In all other cases, the type of the expected value from the context is already known, which means that all optional parameters can be recovered during decomposition.

+

See also Optional combinator parameters and their values.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-formal.html b/data/corefork.telegram.org/mtproto/TL-formal.html new file mode 100644 index 0000000000..1bccc7538d --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-formal.html @@ -0,0 +1,319 @@ + + + + + TL-formal + + + + + + + + + + + + + +
+ +
+
+
+ +

TL-formal

+ +

See also TL Language. +For the syntax of declaring combinators, see in article Formal declaration of TL combinators. +For the syntax of patterns, see in article Formal declaration of TL patterns.

+

Tokens

+

Comments are the same as in C/C++. They are removed by a lexical parser (for example, being replaced by a single space). Whitespace separates tokens. Except for string constants, tokens cannot contain spaces.

+

Character classes:

+
+

lc-letter ::= a | b | ... | z
+uc-letter ::= A | B | ... | Z
+digit ::= 0 | 1 | ... | 9
+hex-digit ::= digit | a | b | c | d | e | f
+underscore ::= _
+letter ::= lc-letter | uc-letter
+ident-char ::= letter | digit | underscore

+
+

Simple identifiers and keywords:

+
+

lc-ident ::= lc-letter { ident-char }
+uc-ident ::= uc-letter { ident-char }
+namespace-ident ::= lc-ident
+lc-ident-ns ::= [ namespace-ident . ] lc-ident
+uc-ident-ns ::= [ namespace-ident . ] uc-ident
+lc-ident-full ::= lc-ident-ns [ # hex-digit *8 ]

+
+

Tokens:

+
+

underscore ::= _
+colon ::= :
+semicolon ::= ;
+open-par ::= (
+close-par ::= )
+open-bracket ::= [
+close-bracket ::= ]
+open-brace ::= {
+close-brace ::= }
+triple-minus ::= ---
+nat-const ::= digit { digit }
+lc-ident-full
+lc-ident
+uc-ident-ns
+equals ::= =
+hash ::= #
+question-mark ::= ?
+percent ::= %
+plus ::= +
+langle ::= <
+rangle ::= >
+comma ::= ,
+dot ::= .
+asterisk ::= *
+excl-mark ::= !
+Final-kw ::= Final
+New-kw ::= New
+Empty-kw ::= Empty

+
+

Final is a reserved keyword, e.g. a special token. Words like Type are not keywords, rather they are identifiers with preset values.

+

Tokens consisting of one or more constant symbols shall be hereafter denoted using terms in quotation marks (for example, --- replaces triple-minus).

+

Syntax

+

General syntax of a TL program

+

Syntactically, a TL program consists of a stream of tokens (separated by spaces, which are ignored at this stage). General program structure:

+
+

TL-program ::= constr-declarations { --- functions --- fun-declarations | --- types --- constr-declarations }

+
+

Here the constructor- and function declarations are nearly identical in their syntax (they are both combinators):

+
+

constr-declarations ::= { declaration }
+fun-declarations ::= { declaration }

+
+

There are various declarations:

+
+

declaration ::= combinator-decl | partial-app-decl | final-decl

+
+

Before explaining how declarations of combinators, partial applications, and type finalization are given, we will introduce additional syntactical categories:

+

Syntactical categories and constructions

+

The concept of an expression (expr) is important. There are type expressions (type-expr) and numeric expressions (nat-expr). However, they are defined the same way. Their correctness as type- or numeric expressions is checked when the type of the analyzed expression is checked.

+
+

type-expr ::= expr
+nat-expr ::= expr
+expr ::= { subexpr }
+subexpr ::= term | nat-const + subexpr | subexpr + nat-const
+term ::= ( expr ) | type-ident | var-ident | nat-const | % term | type-ident < expr { , expr } >
+type-ident ::= boxed-type-ident | lc-ident-ns | #
+boxed-type-ident ::= uc-ident-ns
+var-ident ::= lc-ident | uc-ident
+type-term ::= term
+nat-term ::= term

+
+

Note that writing E = E_1 E_2 ... E_n in the expression for expr means applying the function E_1 to the argument E_2, applying the result to E_3, etc. Specifically, E_1 E_2 E_3 = (E_1 E_2) E_3. A solitary # is included in type-ident, because it is actually the identifier for a built-in type (# alias nat).

+

The expression E<E_1,...,E_n> is syntactic sugar for (E (E_1) ... (E_n)), i.e. both expressions are transformed into the same internal representation.

+

Combinator declarations

+
+

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
+full-combinator-id ::= lc-ident-full | _
+combinator-id ::= lc-ident-ns | _
+opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
+args ::= var-ident-opt : [ conditional-def ] [ ! ] type-term
+args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
+args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
+args ::= [ ! ] type-term
+multiplicity ::= nat-term
+var-ident-opt ::= var-ident | _
+conditional-def ::= var-ident [ . nat-const ] ?
+result-type ::= boxed-type-ident { subexpr }
+result-type ::= boxed-type-ident < subexpr { , subexpr } >

+
+

See Formal declaration of TL combinators for a description of what exactly this means. Here we will only note that when declaring the type of a combinator’s next argument, only the names of previously arranged (more to the left) arguments of the same combinator may be used as variables, but when declaring the result type you can use all of its parameters (of type Type and #).

+

Note that the names of combinators declared in this way may be used in TL itself only as the corresponding bare types. The only combinators that appear in declarations are built-in: O : # and S : # -> #.

+

There are also “pseudo-declarations” that are allowed only to declare built-in types (such as int ? = Int;):

+
+

builtin-combinator-decl ::= full-combinator-id ? = boxed-type-ident ;

+
+

Partial applications (patterns)

+
+

partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
+partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
+partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

+
+

See Formal declaration of TL patterns.

+

Type finalization

+
+

final-decl ::= New boxed-type-ident ; | Final boxed-type-ident ; | Empty boxed-type-ident ;

+
+

This type of declaration means that there must not be any constructor for the indicated type: before the declaration for New and after the declaration for Final. The keyword Empty enables both effects.

+

Predefined identifiers

+

Nearly all predefined identifiers may be given using the following schema (usually located in common.tl):

+
+

/////
+//
+// Common Types
+//
+/////

+

// Built-in types
+int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;

+

// Boolean emulation
+boolFalse = Bool;
+boolTrue = Bool;

+

// Boolean for diagonal queries
+boolStat statTrue:int statFalse:int statUnknown:int = BoolStat;

+

// Vector
+vector {t:Type} # [t] = Vector t;
+tuple {t:Type} {n:#} [t] = Tuple t n;
+vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;

+

/////
+//
+// Result- (Maybe-) types
+//
+/////

+

resultFalse {t:Type} = Maybe t;
+resultTrue {t:Type} result:t = Maybe t;

+

pair {X:Type} {Y:Type} a:X b:Y = Pair X Y;
+map {X:Type} {Y:Type} key:X value:Y = Map X Y;

+

Empty False;
+true = True;

+

unit = Unit;

+
+
    +
  • +

    Predefined identifier Type: This type signifies the type of all types. It is usually used to specify the types of optional parameters in the constructors of polymorphic types. If strongly desired, it can be used in its own right, but this is very rarely needed in practice.

    +
  • +
  • +

    Identifier #: This type is used to specify a special type of nonnegative integers in the range from 0 to 2^31-1; its main purpose is the same as that of Type. There are two built-in constructors: O : # and S : # -> # (“null” and “next number”, respectively), which work as if # was defined using the schema

    +
  • +
+
+

O = #;
+S # = #;

+
+
    +
  • +

    Identifier Tuple: Type -> # -> Type denotes a set of the specified number of values of the indicated type. In other words, Tuple X n means “a set of n values of type X".

    +
  • +
  • +

    The typeBool, with two constructors boolTrue and boolFalse, is used to transmit Boolean values.

    +
  • +
  • +

    The constructor-less type False may be used instead of undeclared or invalid types in the construction of a TL schema, because any attempt to (de)serialize a value of type False will produce an error. Usage Example:

    +
  • +
+
+

user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string reserved3:flags.3?False reserved4:flags.4?False = User flags;
+user_present {flags:#} info:%(User flags) = UserInfo flags;
+user_absent {flags:#} = UserInfo flags;
+getUser flags:# id:int = !UserInfo flags;

+
+

In the future, bits 3 and 4 in the flags field may be used to transmit new fields after changing the names and types of the reserved3 and reserved4 fields. This will change the user constructor’s number, but this isn’t too important, since the User flags type is only used as a bare type. Transmitting bits 3 or 4 in the flags field in a getUser query before these fields have actually been defined will lead to an error in the (de)serialization of the request.

+
    +
  • The type True with a single null constructor true plays a role similar to the void type in C/C++. It is especially useful as a bare type %True, alias true, because its serialization has zero length. For example, the first_name:flags.1?string constructor used above is in fact shorthand for (the as-yet unsupported) alternative-type general constructor first_name:(flags.1?string:true).
  • +
+

When directly used in a conditional field it may simply indicate the presence (absence) of a certain parameter with void type. +If the conditional field exists, the associated parameter will not be populated; the conditional field simply exists and the existance value can be used to perform certain operations, example:

+
user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string bot:flags.3?true reserved4:flags.4?False = User flags;
+

If bit 3 of the flags parameter isn't set, the user is a normal user. +If bit 3 of the flags parameter is set, this indicates that the specified user is a bot: however, during deserialization, the bot parameter must not be assigned any value, since true is actually a void type.

+
    +
  • The typeUnit with a single null constructor Unit is similar to the previous type.
  • +
+

ANTLR definition

+

An ANLTR definition of TL grammar can be found here ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-optargs.html b/data/corefork.telegram.org/mtproto/TL-optargs.html new file mode 100644 index 0000000000..8aa55122a6 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-optargs.html @@ -0,0 +1,151 @@ + + + + + Optional combinator parameters and their values + + + + + + + + + + + + + +
+ +
+
+
+ +

Optional combinator parameters and their values

+ +

TL Language makes it possible to declare a combinator’s first few parameters optional. Subsequently, they are almost never required to be explicitly stated. This is directly related to another important property of TL: polymorphism.

+

All optional parameters are typically required to be part of the result type (at least once).

+

A (sub)expression may be serialized/deserialized in one of two ways:

+
    +
  • +

    The result type is known (for example, we’re parsing the response to a previously sent RPC query and therefore know the value of some type is expected). In this case, the result type may be used to determine the values of the combinator’s implicit parameters.

    +
  • +
  • +

    The result type is not known. It is determined as a result of (de)serialization (for example, we are serializing an RPC query). In this case, it is necessary to explicitly specify (and serialize) all of the combinator’s optional parameters by using the full version of the combinator.

    +
  • +
+

We will assume that the functional combinator only differs from the constructor in that before its result type the ! modifier is implicitly added, and the (remote or local) computation of a functional expression may be presented as the execution of some polymorphic function eval : !X -> X.

+

Moreover, the unknown result type is obviously usually (but not always) bound to the serialization of an expression whose type has been modified by !.

+

We can formulate the following rules. Let there be some constructor

+
C {a1:T1} ... {am:Tm} b1:U1 ... bn:Un = T;
+

Some of its arguments or its result may be marked with the ! modifier (We consider a functional combinator to be a constructor whose result type has been modified by an implicit !).

+

The following conditions must hold:

+
    +
  • +

    Each type T1, ..., Tm, U1, ..., Un, and T may depend on parameters of type Type or #, which have been declared to the left of the use of the given type.

    +
  • +
  • +

    The types of implicit parameters T1, ..., Tm may not be modified by !.

    +
  • +
  • +

    Only implicit parameters of type Type or # are allowed. In other words, Ti is either a Type or a #. (Unlike the previous rule, this rule may be relaxed in the future.)

    +
  • +
  • +

    Each implicit parameter a1, ..., am must be used at least once -- either within one of the Ui types that have a !, or in the result type T, if it does not have an explicit or implicit !.

    +
  • +
  • +

    If an implicit parameter ai is not used in the result type, or if the result type has a !, then its first (leftmost) usage must be within a type Uj that is modified by !.

    +
  • +
+

The idea is this: we assume that during (de)serialization of a value of a type modified by ! that we do not know this type in advance and we will find out what it is only based on the result of the (de)serialization; Conversely, we assume that during (de)serialization of a value of a type that is not modified by ! that we know this type in advance. In this case, complying with the rules stated above lets us always compute the values of all implicit parameters -- either from the (previously known) result type or from the type of one of the bj:!Uj parameters (which was obtained during the serialization process).

+

In fact, ! denotes the direction in which type information is flowing. By default, the result type is the source of information about types (and their parameters), while argument types are the recipients of that information. The use of ! reverses the direction of information flow, making the result type the recipient and the argument type the source of type information.

+

See also Binary serialization and abstract TL types and Polymorphism in TL.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-patterns.html b/data/corefork.telegram.org/mtproto/TL-patterns.html new file mode 100644 index 0000000000..a3ef5eb43e --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-patterns.html @@ -0,0 +1,129 @@ + + + + + TL-patterns + + + + + + + + + + + + + +
+ +
+
+
+ +

TL-patterns

+ +
+

partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
+partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
+partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

+
+

According to the original design, templates must be used to replace concrete values in the first few or all of the optional arguments of a constructor or polymorphic type. For example, if Tuple int 10 is used frequently, you can declare a template for it, which will cause the appropriate constructors to be generated automatically. When using such a constructor there may be nowhere to pass an int type or the tuple size 10. Similarly, it was originally planned to declared templates for Vector int, Vector string, etc. in order to generate constructors for each vector type being used type. These constructors would make it possible during deserialization to determine what kind of array is being transmitted.

+

Templates are not used now. Instead, the same universal constructors (for example, vector {t:Type} [t] = Vector t) are used with the values of the optional parameters being inferred from the type of the result (if we already know from the schema that in this location there must be a Vector int during deserialization, we understand that we will see the universal vector constructor in which t is equal to int).

+

This approach is better in that it is not necessary to define Vector SomeType templates in advance for all possible types in order to generate their own constructors for each of these cases. Nevertheless, there is a drawback. If someone wants to transmit the serialization of a value of the clothed type Vector int as a serialization of a value of type Object, a problem arises during serialization: after seeing the universal vector constructor and then reading the vector length, we cannot determine what type of values should be expected next.

+

In theory, this problem can be solved by using the full form of the constructor (@vector) corresponding to vector (it is automatically defined and is different in that all of the optional parameters become required), or by defining

+
+

object X:Type X = TypedObject

+
+

and passing the object type explicitly. Type serialization is required in both cases.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-polymorph.html b/data/corefork.telegram.org/mtproto/TL-polymorph.html new file mode 100644 index 0000000000..658321fb15 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-polymorph.html @@ -0,0 +1,170 @@ + + + + + Polymorphism in TL + + + + + + + + + + + + + +
+ +
+
+
+ +

Polymorphism in TL

+ +

It should be noted that in the TL schema of the overwhelming majority of API calls the use of polymorphic types is restricted to the Vector type. Nevertheless, having a view of the big picture is still helpful.

+

Ordinary inductive types

+

For example, let us consider the IntList, which is defined as follows:

+
int_cons hd:int tl:IntList = IntList;
+int_nil = IntList;
+

The “int_cons” and “int_nil” constructors as well as the “IntList” type itself are expressions of the following types (writing A : X means that A is an expression of type X):

+
IntList : Type;
+int_cons : int -> IntList -> IntList;
+int_nil : IntList;
+

The keyword Type is used to denote the type of all types. Note that Type is not Object (Object is the type of all terms). +Here is alternative syntax that could be used in some other functional programming language (but not in TL):

+
NewType IntList :=
+| int_cons hd:int tl:IntList
+| int_nil
+EndType
+

Polymorphic type

+

TL supports the following version (curly brackets indicate optional fields, see below):

+
cons {X:Type} hd:X tl:(List X) = List X;
+nil {X:Type} = List X
+

Here is an alternative formulation in other functional languages with dependent types:

+
NewType List {X:Type} :=
+| cons {X:Type} hd:X tl:(List X)
+| nil {X:Type}
+EndType
+

In any event, these variations are equivalent to one another from the point of view of the formal theory of types and lead to the definition of the following terms:

+
List : Type -> Type;
+cons : forall (X:Type), X -> List X -> List X;
+nil : forall (X:Type), X -> List X;
+

In each case, remember that writing “A -> B” is shorthand for “forall (x : A), B” for any variable x not entering into A and B. For example, the “cons” type could be written as follows:

+
cons : forall (X:Type), forall (hd : X), forall (tl : List X), List X
+

or more compactly:

+
cons : forall (X : Type) (hd : X) (tl : List X), List X
+

See Calculus of constructions. Examples of functional languages with dependent types, which support similar constructions are Coq and Agda.

+

In this case, the entry after a universal quantifier proves to be more content-related than that after an arrow, because the name of a variable bound by the quantifier is used to transmit the name of the corresponding field in the constructor, even if this variable is not used anywhere as it pertains to the expression under the quantifier. Structurally, all of these entries of the “cons” type are equivalent.

+

Serialization of types (values of type Type)

+

As we can see, to serialize a value of type List X, which has been obtained by applying the combinator “cons X:Type hd:X tl:(List X) = List X”, we need to:

+
    +
  1. serialize the name of the “cons” combinator into a 32-bit number;
  2. +
  3. serialize X (as a type, i.e. as a value of type Type) if X is a required parameter;
  4. +
  5. serialize the head of the list (hd) as a value of type X;
  6. +
  7. serialize the tail of the list as a value of the polymorphic type List X.
  8. +
+

In the first step, the natural question is which string exactly will be used to calculate the CRC32. It is proposed to take "cons X:Type hd:X tl:List X = List X” without the terminating semicolon and without any parentheses (closed type expressions are unambiguously reconstructed based on their construction’s prefix).

+

In the last step, we recursively resolve the very same problem of serializing a value of type List X; we will consider it resolved based on the assumption of induction in the construction of the value being serialized. We will similarly consider the third step understandable (induction in the construction of the value being serialized).

+

We still need to describe how to transmit (serialize) types, e.g. values of type Type. Types in TL schemas currently appear only as constructors’ optional parameters and are therefore never serialized explicitly. Rather, their values are inferred from the previously known type of the value being serialized.

+

For completeness we will describe how it would be possible to serialize types (values of type Type). However, keep in mind that for now this information is not useful. See Type serialization.

+

Optional arguments in polymorphic constructors

+

It was stated above that any subset of (the first few) parameters of any constructor can be identified as optional (by enclosing their declarations in curly brackets), but this is not actually entirely accurate. First, these optional parameters can only be of type Type or # (natural numbers). Second, optional parameters must share the return value’s type, otherwise their value cannot be determined.

+

Note that @'''constr-id''' means the constructor’s “full form” (in which all optional parameters become required), while '''constr-id'’ denotes its abbreviated form (without the optional arguments). If there are no optional arguments, then these two forms are the same. Constructors’ full forms are never used at present.

+

Bare polymorphic types

+

There is a small problem: if we want to serialize the value of the bare type ‘%pair string int’ or ‘%pair string Y’ (which in TL is usually denoted simply as “pair”, though the form “%Pair” is preferable), we cannot simultaneously use both the full constructor @pair and the partial pair, because the constructor’s name will not be serialized. Therefore, we must differentiate the bare types %@pair (type X, type Y, value x:X, and value y:Y are serialized) and %pair (only x:X and y:Y are serialized; types X and Y are known from the context). In practice, we nearly almost always need the bare type %pair, and this is precisely what “pair” means in the type’s context in TL. Therefore,

+
record name:string map:(List (pair int string)) = Record;
+

will be serialized approximately like we want it to be (the serialization of list elements will consist of the serialization of int and the serialization of string, without any additional headers, types, or combinator names). +Incidentally, when calculating the “record” combinator’s name 'record' in the example given above, the CRC32 of record name:string map:List pair int string = Record will be computed.

+

Also note that a more precise description of this type would be

+
record name:string map:(List %(Pair int string)) = Record
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-tl.html b/data/corefork.telegram.org/mtproto/TL-tl.html new file mode 100644 index 0000000000..6eb37b1df6 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-tl.html @@ -0,0 +1,308 @@ + + + + + TL schema for serialization of TL schemas + + + + + + + + + + + + + +
+ +
+
+
+ +

TL schema for serialization of TL schemas

+ +

If necessary, a TL schema can be serialized in binary form. Here, this serialization format is defined by a TL schema (usually stored in the file tl.tl). This can be useful, for example, to make it possible to write a parser one time for converting a TL schema from text form (stored in the file something.tl) to binary form (stored in the file something.tlo). All other programs (for example, auto-generators of TL-(de)serializers for various programming languages) only need to know how to read .tlo files, which only requires generating an automatic deserializer according to the schema presented below.

+

First, a fragment of the file common.tl with certain required built-in types:

+
/////
+//
+// Common Types (source file common.tl, only necessary definitions included)
+//
+/////
+
+// Built-in types
+int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+
+// Boolean emulation
+boolFalse = Bool;
+boolTrue = Bool;
+
+// Vector
+vector {t:Type} # [t] = Vector t;
+tuple {t:Type} {n:#} [t] = Tuple t n;
+vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;
+
+Empty False;
+true = True;
+

Next, properly, comes tl.tl itself. Note that the declaration for a fairly complex data type required only twenty lines in TL. This demonstrates the expressiveness and compactness of the TL language.

+
/////
+//
+// Serialized binary TL-schema in TL format, source file tl.tl
+//
+/////
+tls.schema_v2 version:int date:int types_num:# types:types_num*[tls.Type] 
+
+    constructor_num:# constructors:constructor_num*[tls.Combinator] 
+    functions_num:# functions:functions_num*[tls.Combinator] = tls.Schema;
+tls.type name:int id:string constructors_num:int flags:int arity:int params_type:long = tls.Type;
+
+tls.combinator name:int id:string type_name:int left:tls.CombinatorLeft right:tls.CombinatorRight = tls.Combinator;
+tls.combinatorLeftBuiltin = tls.CombinatorLeft;
+tls.combinatorLeft args_num:# args:args_num*[tls.Arg] = tls.CombinatorLeft;
+tls.combinatorRight value:tls.TypeExpr = tls.CombinatorRight;
+
+tls.arg id:string flags:# var_num:flags.1?int exist_var_num:flags.2?int exist_var_bit:flags.2?int type:tls.TypeExpr = tls.Arg;
+
+tls.exprType _:tls.TypeExpr = tls.Expr;
+
+tls.exprNat _:tls.NatExpr = tls.Expr;
+tls.natConst value:int = tls.NatExpr;
+
+tls.natVar dif:int var_num:int = tls.NatExpr;
+tls.typeVar var_num:int flags:int = tls.TypeExpr;
+
+tls.array multiplicity:tls.NatExpr args_num:# args:args_num*[tls.Arg] = tls.TypeExpr;
+tls.typeExpr name:int flags:int children_num:# children:children_num*[tls.Expr] = tls.TypeExpr;
+

Remarks

+

Schema serialization (version 2) always begins with the index number of the tls.schema_v2 constructor for tls.Schema. +Because the CRC32 of the string

+
tls.schema_v2 version:int date:int types_num:# types:types_num*[ tls.Type ] constructor_num:# constructors:constructor_num*[ tls.Combinator ] functions_num:# functions:functions_num*[ tls.Combinator ] = tls.Schema
+

is 0x3a2f9be2, this constant is in fact the magic number for tlo files in the current version’s format. +If the format is extended in the future (for example, if TL’s additional features are supported), then a tls.schema_v3 constructor with a different number will appear.

+

Example

+

If one adds declarations for the used built-in types (like int ? = Int;) from the file common.tl before tl.tl and serialize the resulting schema, the following binary data is obtained (tl.tlo):

+
+

0000: 3a2f9be2 00000000 51fec698 00000015 12eb4386 70659eff 00002301 00000000
+0020: 00000000 00000000 00000000 00000000 12eb4386 250be282 6f6f4204 0000006c
+0040: 00000002 02000010 00000000 00000000 00000000 12eb4386 2210c154 756f4406
+0060: 00656c62 00000001 02000000 00000000 00000000 00000000 12eb4386 00000000
+0080: 6c614605 00006573 00000000 00000401 00000000 00000000 00000000 12eb4386
+00a0: a8509bda 746e4903 00000001 02000001 00000000 00000000 00000000 12eb4386
+00c0: 22076cba 6e6f4c04 00000067 00000001 02000001 00000000 00000000 00000000
+00e0: 12eb4386 b5286e24 72745306 00676e69 00000001 02000001 00000000 00000000
+0100: 00000000 12eb4386 3fedd339 75725404 00000065 00000001 02000000 00000000
+0120: 00000000 00000000 12eb4386 9770768a 70755405 0000656c 00000001 02000000
+0140: 00000002 00000002 00000000 12eb4386 2cecf817 70795404 00000065 00000000
+0160: 00000000 00000000 00000000 00000000 12eb4386 1cb5c415 63655606 00726f74
+0180: 00000001 02000008 00000001 00000000 00000000 12eb4386 10133f47 6365560b
+01a0: 54726f74 6c61746f 00000001 02000000 00000001 00000000 00000000 12eb4386
+01c0: 29dfe61b 736c7407 6772412e 00000001 02000000 00000000 00000000 00000000
+01e0: 12eb4386 5c0a1ed5 736c740e 6d6f432e 616e6962 00726f74 00000001 02000000
+0200: 00000000 00000000 00000000 12eb4386 8133d9ba 736c7412 6d6f432e 616e6962
+0220: 4c726f74 00746665 00000002 02000010 00000000 00000000 00000000 12eb4386
+0240: 2c064372 736c7413 6d6f432e 616e6962 52726f74 74686769 00000001 02000000
+0260: 00000000 00000000 00000000 12eb4386 307d41a0 736c7408 7078452e 00000072
+0280: 00000002 02000010 00000000 00000000 00000000 12eb4386 c2635441 736c740b
+02a0: 74614e2e 72707845 00000002 02000010 00000000 00000000 00000000 12eb4386
+02c0: 3a2f9be2 736c740a 6863532e 00616d65 00000001 02000000 00000000 00000000
+02e0: 00000000 12eb4386 12eb4386 736c7408 7079542e 00000065 00000001 02000000
+0300: 00000000 00000000 00000000 12eb4386 193fd378 736c740c 7079542e 70784565
+0320: 00000072 00000003 02000010 00000000 00000000 00000000 00000018 5c0a1ed5
+0340: bc799737 6f6f6209 6c61466c 00006573 250be282 4c12c6d9 00000000 2c064372
+0360: c1863d08 250be282 00000000 00000000 5c0a1ed5 997275b5 6f6f6208 7572546c
+0380: 00000065 250be282 4c12c6d9 00000000 2c064372 c1863d08 250be282 00000000
+03a0: 00000000 5c0a1ed5 2210c154 756f6406 00656c62 2210c154 cd211f63 2c064372
+03c0: c1863d08 2210c154 00000000 00000000 5c0a1ed5 a8509bda 746e6903 a8509bda
+03e0: cd211f63 2c064372 c1863d08 a8509bda 00000000 00000000 5c0a1ed5 22076cba
+0400: 6e6f6c04 00000067 22076cba cd211f63 2c064372 c1863d08 22076cba 00000000
+0420: 00000000 5c0a1ed5 b5286e24 72747306 00676e69 b5286e24 cd211f63 2c064372
+0440: c1863d08 b5286e24 00000000 00000000 5c0a1ed5 3fedd339 75727404 00000065
+0460: 3fedd339 4c12c6d9 00000000 2c064372 c1863d08 3fedd339 00000000 00000000
+0480: 5c0a1ed5 9770768a 70757405 0000656c 9770768a 4c12c6d9 00000003 29dfe61b
+04a0: 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000 29dfe61b
+04c0: 00006e01 00020005 00000001 c1863d08 70659eff 00000000 00000000 29dfe61b
+04e0: 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
+0500: 00000000 00000000 0142ceae 00000000 00000000 2c064372 c1863d08 9770768a
+0520: 00000000 00000002 ecc9da78 0142ceae 00000000 00000000 dcb49bd8 4e8a14f0
+0540: 00000000 00000001 5c0a1ed5 1cb5c415 63657606 00726f74 1cb5c415 4c12c6d9
+0560: 00000003 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000
+0580: 00000000 29dfe61b 00000000 00000004 00000001 c1863d08 70659eff 00000000
+05a0: 00000000 29dfe61b 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001
+05c0: 00000001 29dfe61b 00000000 00000000 0142ceae 00000000 00000000 2c064372
+05e0: c1863d08 1cb5c415 00000000 00000001 ecc9da78 0142ceae 00000000 00000000
+0600: 5c0a1ed5 10133f47 6365760b 54726f74 6c61746f 10133f47 4c12c6d9 00000003
+0620: 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000
+0640: 29dfe61b 746f740b 635f6c61 746e756f 00000000 c1863d08 a8509bda 00000001
+0660: 00000000 29dfe61b 63657606 00726f74 00000000 c1863d08 1cb5c415 00000001
+0680: 00000001 ecc9da78 0142ceae 00000000 00000000 2c064372 c1863d08 10133f47
+06a0: 00000000 00000001 ecc9da78 0142ceae 00000000 00000000 5c0a1ed5 29dfe61b
+06c0: 736c7407 6772612e 29dfe61b 4c12c6d9 00000006 29dfe61b 00646902 00000000
+06e0: c1863d08 b5286e24 00000001 00000000 29dfe61b 616c6605 00007367 00000004
+0700: 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b 72617607 6d756e5f
+0720: 00000002 00000000 00000001 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0740: 6978650d 765f7473 6e5f7261 00006d75 00000002 00000000 00000002 c1863d08
+0760: a8509bda 00000001 00000000 29dfe61b 6978650d 765f7473 625f7261 00007469
+0780: 00000002 00000000 00000002 c1863d08 a8509bda 00000001 00000000 29dfe61b
+07a0: 70797404 00000065 00000000 c1863d08 193fd378 00000000 00000000 2c064372
+07c0: c1863d08 29dfe61b 00000000 00000000 5c0a1ed5 5c0a1ed5 736c740e 6d6f632e
+07e0: 616e6962 00726f74 5c0a1ed5 4c12c6d9 00000005 29dfe61b 6d616e04 00000065
+0800: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 00646902 00000000
+0820: c1863d08 b5286e24 00000001 00000000 29dfe61b 70797409 616e5f65 0000656d
+0840: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 66656c04 00000074
+0860: 00000000 c1863d08 8133d9ba 00000000 00000000 29dfe61b 67697205 00007468
+0880: 00000000 c1863d08 2c064372 00000000 00000000 2c064372 c1863d08 5c0a1ed5
+08a0: 00000000 00000000 5c0a1ed5 cd211f63 736c7419 6d6f632e 616e6962 4c726f74
+08c0: 42746665 746c6975 00006e69 8133d9ba 4c12c6d9 00000000 2c064372 c1863d08
+08e0: 8133d9ba 00000000 00000000 5c0a1ed5 4c12c6d9 736c7412 6d6f632e 616e6962
+0900: 4c726f74 00746665 8133d9ba 4c12c6d9 00000002 29dfe61b 67726108 756e5f73
+0920: 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b
+0940: 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000 00000001
+0960: 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000 2c064372
+0980: c1863d08 8133d9ba 00000000 00000000 5c0a1ed5 2c064372 736c7413 6d6f632e
+09a0: 616e6962 52726f74 74686769 2c064372 4c12c6d9 00000001 29dfe61b 6c617605
+09c0: 00006575 00000000 c1863d08 193fd378 00000000 00000000 2c064372 c1863d08
+09e0: 2c064372 00000000 00000000 5c0a1ed5 ecc9da78 736c740c 7078652e 70795472
+0a00: 00000065 307d41a0 4c12c6d9 00000001 29dfe61b 00000000 00000000 c1863d08
+0a20: 193fd378 00000000 00000000 2c064372 c1863d08 307d41a0 00000000 00000000
+0a40: 5c0a1ed5 dcb49bd8 736c740b 7078652e 74614e72 307d41a0 4c12c6d9 00000001
+0a60: 29dfe61b 00000000 00000000 c1863d08 c2635441 00000000 00000000 2c064372
+0a80: c1863d08 307d41a0 00000000 00000000 5c0a1ed5 8ce940b1 736c740c 74616e2e
+0aa0: 736e6f43 00000074 c2635441 4c12c6d9 00000001 29dfe61b 6c617605 00006575
+0ac0: 00000000 c1863d08 a8509bda 00000001 00000000 2c064372 c1863d08 c2635441
+0ae0: 00000000 00000000 5c0a1ed5 4e8a14f0 736c740a 74616e2e 00726156 c2635441
+0b00: 4c12c6d9 00000002 29dfe61b 66696403 00000000 c1863d08 a8509bda 00000001
+0b20: 00000000 29dfe61b 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001
+0b40: 00000000 2c064372 c1863d08 c2635441 00000000 00000000 5c0a1ed5 3a2f9be2
+0b60: 736c740d 6863732e 5f616d65 00003276 3a2f9be2 4c12c6d9 00000008 29dfe61b
+0b80: 72657607 6e6f6973 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0ba0: 74616404 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0bc0: 70797409 6e5f7365 00006d75 00000004 00000000 c1863d08 70659eff 00000000
+0be0: 00000000 29dfe61b 70797405 00007365 00000000 d9fb20de 4e8a14f0 00000000
+0c00: 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 12eb4386 00000000
+0c20: 00000000 29dfe61b 6e6f630f 75727473 726f7463 6d756e5f 00000004 00000001
+0c40: c1863d08 70659eff 00000000 00000000 29dfe61b 6e6f630c 75727473 726f7463
+0c60: 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
+0c80: 00000000 00000000 c1863d08 5c0a1ed5 00000000 00000000 29dfe61b 6e75660d
+0ca0: 6f697463 6e5f736e 00006d75 00000004 00000002 c1863d08 70659eff 00000000
+0cc0: 00000000 29dfe61b 6e756609 6f697463 0000736e 00000000 d9fb20de 4e8a14f0
+0ce0: 00000000 00000002 00000001 29dfe61b 00000000 00000000 c1863d08 5c0a1ed5
+0d00: 00000000 00000000 2c064372 c1863d08 3a2f9be2 00000000 00000000 5c0a1ed5
+0d20: 12eb4386 736c7408 7079742e 00000065 12eb4386 4c12c6d9 00000006 29dfe61b
+0d40: 6d616e04 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0d60: 00646902 00000000 c1863d08 b5286e24 00000001 00000000 29dfe61b 6e6f6310
+0d80: 75727473 726f7463 756e5f73 0000006d 00000000 c1863d08 a8509bda 00000001
+0da0: 00000000 29dfe61b 616c6605 00007367 00000000 c1863d08 a8509bda 00000001
+0dc0: 00000000 29dfe61b 69726105 00007974 00000000 c1863d08 a8509bda 00000001
+0de0: 00000000 29dfe61b 7261700b 5f736d61 65707974 00000000 c1863d08 22076cba
+0e00: 00000001 00000000 2c064372 c1863d08 12eb4386 00000000 00000000 5c0a1ed5
+0e20: 0142ceae 736c740b 7079742e 72615665 193fd378 4c12c6d9 00000002 29dfe61b
+0e40: 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
+0e60: 616c6605 00007367 00000000 c1863d08 a8509bda 00000001 00000000 2c064372
+0e80: c1863d08 193fd378 00000000 00000000 5c0a1ed5 d9fb20de 736c7409 7272612e
+0ea0: 00007961 193fd378 4c12c6d9 00000003 29dfe61b 6c756d0c 6c706974 74696369
+0ec0: 00000079 00000000 c1863d08 c2635441 00000000 00000000 29dfe61b 67726108
+0ee0: 756e5f73 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000
+0f00: 29dfe61b 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000
+0f20: 00000001 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000
+0f40: 2c064372 c1863d08 193fd378 00000000 00000000 5c0a1ed5 c1863d08 736c740c
+0f60: 7079742e 70784565 00000072 193fd378 4c12c6d9 00000004 29dfe61b 6d616e04
+0f80: 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 616c6605
+0fa0: 00007367 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 6968630c
+0fc0: 6572646c 756e5f6e 0000006d 00000004 00000000 c1863d08 70659eff 00000000
+0fe0: 00000000 29dfe61b 69686308 6572646c 0000006e 00000000 d9fb20de 4e8a14f0
+1000: 00000000 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 307d41a0
+1020: 00000000 00000000 2c064372 c1863d08 193fd378 00000000 00000000 00000000

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-types.html b/data/corefork.telegram.org/mtproto/TL-types.html new file mode 100644 index 0000000000..28c1e276c4 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-types.html @@ -0,0 +1,124 @@ + + + + + Type serialization + + + + + + + + + + + + + +
+ +
+
+
+ +

Type serialization

+ +

See Polymorphism in TL and TL Language.

+

It remains to describe how types, e.g. values of type Type, are transmitted (serialized). In general, there is nothing unexpected going on here: we have type constructors of various arities (for example, List is an arity-1 constructor, but IntList is a 0-arity constructor); and if we know that a 32-bit “name” is assigned to each type constructor, there are no further questions -- values of type Type are serialized exactly like values of any other recursive type with a defined set of constructors of differing arity.

+

How can a 32-bit “name” be assigned to a type (a type constructor, to be more exact) such as List or IntList? +It is proposed to use the sum of the names of all of its constructors, plus the CRC32 of the string with the designation of the type's name and all of its parameters such as “IntList = Type” or “List X:Type = Type”. This way, the List constructor’s “name” is the sum of the CRC32s of the three strings "List X:Type = Type", "cons X:Type hd:X tl:List X = List X", and "nil X:Type = List X". +For “bare” types (which, formally speaking, are subtypes of the corresponding “boxed” type), the situation is somewhat more complicated; the logical negation of the corresponding constructor’s name is used. For built-in bareand boxed types (for example, int and Int), a pseudo-declaration is used (for example, int ? = Int").

+
    +
  • This description is somewhat outdated and may be updated in the future. Specifically, how to treat the ! modifier has not been explained.*
  • +
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL.html b/data/corefork.telegram.org/mtproto/TL.html new file mode 100644 index 0000000000..e89117151f --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL.html @@ -0,0 +1,210 @@ + + + + + TL Language + + + + + + + + + + + + + +
+ +
+
+
+ +

TL Language

+ +

TL (Type Language) serves to describe the used system of types, constructors, and existing functions. In fact, the combinator description format presented in Binary Data Serialization is used.

+

See also:

+ +

Advanced topics:

+ +

Overview

+

A TL program usually consists of two sections separated by keyword ---functions---. The first section consists of declarations of built-in types and aggregate types (i.e. their constructors). The second section consists of the declared functions, i.e. functional combinators.

+

Actually, both the first and second sections consist of combinator declarations, each of which ends with a semicolon. However, the first section contains only constructors, while the second section only involves functions. Each combinator is declared using a “combinator declaration” in the format explained above. However, the combinator number and field names may be explicitly assigned.

+

If additional type declarations are required after functions have been declared, the keyword (section divider) ---types--- is used. Furthermore, a functional combinator may be declared in the type section if its result type begins with an exclamation point (in fact, when the function section is interpreted, this exclamation point is added automatically).

+

To explicitly define 32-bit names of combinators, a hash mark (#) is added immediately after the combinator’s name, followed by 8 hexadecimal digits.

+

Namespaces

+

Composite constructions like <namespace_identifier>.<constructor_identifier> and <namespace_identifier>.<Type_identifier> can be used as constructor- or type identifiers. The portion of the identifier to the left of the period is called the namespace. Moreover, the rule about a first uppercase letter in type identifiers and lowercase letter in constructor identifiers applies to the part of the construction after the period. For example, auth.Message would be a type, while auth.std_message would be a constructor.

+

Namespaces do not require a special declaration.

+

Comments

+

Comments are the same as in C++.

+

Example

+
// built-in types
+int#a8509bda ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+null = Null;
+
+vector {t:Type} # [ t ] = Vector t;
+coupleInt {alpha:Type} int alpha = CoupleInt<alpha>;
+coupleStr {gamma:Type} string gamma = CoupleStr gamma;  
+/* The name of the type variable is irrelevant: "gamma" could be replaced with "alpha"; 
+   However, the combinator number will depend on the specific choice. */
+
+intHash {alpha:Type} vector<coupleInt<alpha>> = IntHash<alpha>;
+strHash {alpha:Type} (vector (coupleStr alpha)) = StrHash alpha;
+intSortedHash {alpha:Type} intHash<alpha> = IntSortedHash<alpha>;
+strSortedHash {alpha:Type} (strHash alpha) = StrSortedHash alpha;
+
+// custom types
+pair x:Object y:Object = Pair;
+triple x:Object y:Object z:Object = Triple;
+
+user#d23c81a3 id:int first_name:string last_name:string = User;
+no_user#c67599d1 id:int = User;
+group id:int title:string last_name:string = Group;
+no_group = Group;
+
+---functions---
+
+// Maybe some built-in arithmetic functions; inverse quotes make "identifiers" out of arbitrary non-alphanumeric strings
+`+` Int Int = Int;
+`-` Int Int = Int;
+`+` Double Double = Double;
+// ...
+
+// API functions (aka RPC functions)
+getUser#b0f732d5 int = User;
+getUsers#2d84d5f5 (Vector int) = Vector User;
+

In this case, the user constructor has been explicitly assigned a number (0xd23c81a3); In fact, this was not necessary, since this value is the CRC32 of the string "user id:int first_name:string last_name:string = User", which would have been used by default.

+

Special constructors are not required for Vector int, Vector User, Vector Object, etc. -- the same universal constructor can be used everywhere:

+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;
+

Note that when the getUsers (Vector int) = Vector User; constructor number is calculated, the CRC32 of the string "getUsers Vector int = Vector User” is computed (from which all parentheses have been removed).

+

Notation T0<T1,T2,...,Tn> is syntactic sugar for (T0 (T1) (T2) ... (Tn)). For example, Vector<User> and (Vector User) are entirely interchangeable.

+

Example of an RPC query

+

Suppose we want to call getUsers([2,3,4]). This query will be serialized into a sequence of 32-bit integers as follows:

+
0x2d84d5f5 0x1cb5c415 0x3 0x2 0x3 0x4
+

Please note that TL serialization yields sequences of 32-bit integers. When it has to be embedded into a byte stream, for example a network packet, each 32-bit integer is represented by four bytes in little-endian order. In this way the above query corresponds to the following byte stream:

+
F5 D5 84 2D 15 C4 B5 1C 03 00 00 00 02 00 00 00 03 00 00 00 04 00 00 00
+

The response might look something like this:

+
0x1cb5c415 0x3 0xd23c81a3 0x2 0x74655005 0x00007265 0x72615006 0x72656b 0xc67599d1 0x3 0xd23c81a3 0x4 0x686f4a04 0x6e 0x656f4403
+

This roughly corresponds to

+
[{"id":2,"first_name":"Peter", "last_name":"Parker"},{},{"id":4,"first_name":"John","last_name":"Doe"}]
+

Note that in both cases the same universal constructor vector#1cb5c415 is used: in the request to serialize the value of type Vector int, and in the serialization of the value of type Vector User in the response. There is no ambiguity because in both cases the type of the value being (de)serialized is known before its (de)serialization begins. For example, after receiving the query, the server sees that the first part is 0x2d84d5f5, which corresponds to the combinator getUsers#2d84d5f5 (Vector int) = Vector User. Thus, it is understood that what follows will be a value of type Vector int. After receiving the response to this query, the client knows that it must receive a value of type Vector User and it deserializes the response accordingly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/auth_key.html b/data/corefork.telegram.org/mtproto/auth_key.html new file mode 100644 index 0000000000..32dc7a40dd --- /dev/null +++ b/data/corefork.telegram.org/mtproto/auth_key.html @@ -0,0 +1,210 @@ + + + + + Creating an Authorization Key + + + + + + + + + + + + + +
+ +
+
+
+ +

Creating an Authorization Key

+ +

The query format is described using Binary Data Serialization and the TL Language. All large numbers are transmitted as strings containing the required sequence of bytes in big endian order. Hash functions, such as SHA1, return strings (of 20 bytes) which can also be interpreted as big endian numbers. Small numbers (int, long, int128, int256) are normally little endian; however, if they are part of SHA1, the bytes are not rearranged. This way, if long x is the 64 lower-order bits of SHA1 of string s, then the final 8 bytes of 20-byte string SHA1(s) are taken and interpreted as a 64-bit integer.

+

Prior to sending off unencrypted messages (required in this instance to generate an authorization key), the client must undergo (p,q) authorization as follows.

+

DH exchange initiation

+

1) Client sends query to server

+
req_pq_multi#be7e8ef1 nonce:int128 = ResPQ;
+

The value of nonce is selected randomly by the client (random number) and identifies the client within this communication. Following this step, it is known to all.

+

2) Server sends response of the form

+
resPQ#05162463 nonce:int128 server_nonce:int128 pq:string server_public_key_fingerprints:Vector long = ResPQ;
+

Here, string pq is a representation of a natural number (in binary big endian format). This number is the product of two different odd prime numbers. Normally, pq is less than or equal to 2^63-1. The value of server_nonce is selected randomly by the server; following this step, it is known to all.

+

server_public_key_fingerprints is a list of public RSA key fingerprints (64 lower-order bits of SHA1 (server_public_key); the public key is represented as a bare type rsa_public_key n:string e:string = RSAPublicKey, where, as usual, n and е are numbers in big endian format serialized as strings of bytes, following which SHA1 is computed) received by the server.

+

All subsequent messages contain the pair (nonce, server_nonce) both in the plain-text, and the encrypted portions which makes it possible to identify a “temporary session” — one run of the key generation protocol described on this page that uses the same (nonce, server_nonce) pair. An intruder could not create a parallel session with the server with the same parameters and reuse parts of server- or client-encrypted messages for its own purposes in such a parallel session, because a different server_nonce would be selected by the server for any new “temporary session”.

+

Proof of work

+

3) Client decomposes pq into prime factors such that p < q.

+

This starts a round of Diffie-Hellman key exchanges.

+

Presenting proof of work; Server authentication

+

4) Client sends query to server

+
req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:string q:string public_key_fingerprint:long encrypted_data:string = Server_DH_Params
+

Here, encrypted_data is obtained as follows:

+
    +
  • new_nonce := another (good) random number generated by the client; after this query, it is known to both client and server;
  • +
  • data := a serialization of

    +
    p_q_inner_data_dc#a9f55f95 pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 dc:int = P_Q_inner_data;
    +

    or of

    +
    p_q_inner_data_temp_dc#56fddf88 pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 dc:int expires_in:int = P_Q_inner_data;
    +
  • +
  • encrypted_data := RSA_PAD (data, server_public_key), where RSA_PAD is a version of RSA with a variant of OAEP+ padding explained below in 4.1).

    +
  • +
+

Someone might intercept the query and replace it with their own, independently decomposing pq into factors instead of the client. The only field that it makes sense to modify is new_nonce which would be the one an intruder would have to re-generate (because an intruder cannot decrypt the encrypted data sent by the client). Since all subsequent messages are encrypted using new_nonce or contain new_nonce_hash, they will not be processed by the client (an intruder would not be able to make it look as though they had been generated by the server because they would not contain new_nonce). Therefore, this intercept will only result in the intruder’s completing the authorization key generation protocol in place of the client and creating a new key (that has nothing to do with the client); however, the same effect could be achieved simply by creating a new key in one's own name.

+

An alternative form of inner data (p_q_inner_data_temp_dc) is used to create temporary keys, that are only stored in the server RAM and are discarded after at most expires_in seconds. The server is free to discard its copy earlier. In all other respects the temporary key generation protocol is the same. After a temporary key is created, the client usually binds it to its principal authorisation key by means of the auth.bindTempAuthKey method, and uses it for all client-server communication until it expires; then a new temporary key is generated. Thus Perfect Forward Secrecy (PFS) in client-server communication is achieved. Read more about PFS »

+

4.1) RSA_PAD(data, server_public_key) mentioned above is implemented as follows:

+
    +
  • data_with_padding := data + random_padding_bytes; — where random_padding_bytes are chosen so that the resulting length of data_with_padding is precisely 192 bytes, and data is the TL-serialized data to be encrypted as before. One has to check that data is not longer than 144 bytes.
  • +
  • data_pad_reversed := BYTE_REVERSE(data_with_padding); — is obtained from data_with_padding by reversing the byte order.
  • +
  • a random 32-byte temp_key is generated.
  • +
  • data_with_hash := data_pad_reversed + SHA256(temp_key + data_with_padding); — after this assignment, data_with_hash is exactly 224 bytes long.
  • +
  • aes_encrypted := AES256_IGE(data_with_hash, temp_key, 0); — AES256-IGE encryption with zero IV.
  • +
  • temp_key_xor := temp_key XOR SHA256(aes_encrypted); — adjusted key, 32 bytes
  • +
  • key_aes_encrypted := temp_key_xor + aes_encrypted; — exactly 256 bytes (2048 bits) long
  • +
  • The value of key_aes_encrypted is compared with the RSA-modulus of server_pubkey as a big-endian 2048-bit (256-byte) unsigned integer. If key_aes_encrypted turns out to be greater than or equal to the RSA modulus, the previous steps starting from the generation of new random temp_key are repeated. Otherwise the final step is performed:
  • +
  • encrypted_data := RSA(key_aes_encrypted, server_pubkey); — 256-byte big-endian integer is elevated to the requisite power from the RSA public key modulo the RSA modulus, and the result is stored as a big-endian integer consisting of exactly 256 bytes (with leading zero bytes if required).
  • +
+

5) Server responds with:

+
server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:string = Server_DH_Params;
+
+

If the query is incorrect, the server returns a -404 error and the handshake must be restarted (any subsequent request also returns -404, even if it is correct).

+
+

Here, encrypted_answer is obtained as follows:

+
    +
  • new_nonce_hash := 128 lower-order bits of SHA1 (new_nonce);
  • +
  • answer := serialization

    +
      server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:string g_a:string server_time:int = Server_DH_inner_data;
    +
  • +
  • answer_with_hash := SHA1(answer) + answer + (0-15 random bytes); such that the length be divisible by 16;

    +
  • +
  • tmp_aes_key := SHA1(new_nonce + server_nonce) + substr (SHA1(server_nonce + new_nonce), 0, 12);
  • +
  • tmp_aes_iv := substr (SHA1(server_nonce + new_nonce), 12, 8) + SHA1(new_nonce + new_nonce) + substr (new_nonce, 0, 4);
  • +
  • encrypted_answer := AES256_ige_encrypt (answer_with_hash, tmp_aes_key, tmp_aes_iv); here, tmp_aes_key is a 256-bit key, and tmp_aes_iv is a 256-bit initialization vector. The same as in all the other instances that use AES encryption, the encrypted data is padded with random bytes to a length divisible by 16 immediately prior to encryption.
  • +
+

Following this step, new_nonce is still known to client and server only. The client is certain that it is the server that responded and that the response was generated specifically in response to client query req_DH_params, since the response data are encrypted using new_nonce.

+

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 22047 < p < 22048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g — namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

+

If the verification takes too long time (which is the case for older mobile devices), one might initially run only 15 Miller—Rabin iterations for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations later in the background.

+

Another optimization is to embed into the client application code a small table with some known “good” couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. Server changes these values rarely, thus one usually has to put the current value of server's dh_prime into such a table. For example, current value of dh_prime equals (in big-endian byte order)

+
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
+

6) Client computes random 2048-bit number b (using a sufficient amount of entropy) and sends the server a message

+
set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:string = Set_client_DH_params_answer;
+

Here, encrypted_data is obtained thus:

+
    +
  • g_b := pow(g, b) mod dh_prime;
  • +
  • data := serialization

    +
      client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:string = Client_DH_Inner_Data
    +
  • +
  • data_with_hash := SHA1(data) + data + (0-15 random bytes); such that length be divisible by 16;

    +
  • +
  • encrypted_data := AES256_ige_encrypt (data_with_hash, tmp_aes_key, tmp_aes_iv);
  • +
+

The retry_id field is equal to zero at the time of the first attempt; otherwise, it is equal to auth_key_aux_hash from the previous failed attempt (see Item 9).

+

7) Thereafter, auth_key equals pow(g, {ab}) mod dh_prime; on the server, it is computed as pow(g_b, a) mod dh_prime, and on the client as (g_a)^b mod dh_prime.

+

8) auth_key_hash is computed := 64 lower-order bits of SHA1 (auth_key). The server checks whether there already is another key with the same auth_key_hash and responds in one of the following ways.

+

DH key exchange complete

+

9) Server responds in one of three ways:

+
dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
+dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
+dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
+
    +
  • new_nonce_hash1, new_nonce_hash2, and new_nonce_hash3 are obtained as the 128 lower-order bits of SHA1 of the byte string derived from the new_nonce string by adding a single byte with the value of 1, 2, or 3, and followed by another 8 bytes with auth_key_aux_hash. Different values are required to prevent an intruder from changing server response dh_gen_ok into dh_gen_retry.
  • +
  • auth_key_aux_hash is the 64 higher-order bits of SHA1(auth_key). It must not be confused with auth_key_hash.
  • +
+

In the other case, the client goes to Item 6) generating a new b.
In the first case, the client and the server have negotiated auth_key, following which they forget all other temporary data, and the client creates another encrypted session using auth_key. At the same time, server_salt is initially set to substr(new_nonce, 0, 8) XOR substr(server_nonce, 0, 8). If required, the client stores the difference between server_time received in 5) and its local time, to be able always to have a good approximation of server time which is required to generate correct message identifiers.

+

IMPORTANT: Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

+

Error Handling (Lost Queries and Responses)

+

If the client fails to receive any response to its query from the server within a certain time interval, it may simply re-send the query. If the server has already sent a response to this query (exactly the same request and not just similar: all the parameters during the repeat request must take on the same values) but it did not get to the client, the server will simply re-send the same response. The server remembers the response for up to 10 minutes after having received the query in 1). If the server has already forgotten the response or the requisite temporary data, the client will have to start from the beginning.

+

The server may consider that if the client has already sent in the next query using the data from the previous server response to the specific client, the response is known to have been received by the client and may be forgotten by the server.

+

Usage Example

+

An example of a complete list of queries required to generate an authorization key is shown on a separate page.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/description.html b/data/corefork.telegram.org/mtproto/description.html new file mode 100644 index 0000000000..f1fffd7c32 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/description.html @@ -0,0 +1,238 @@ + + + + + Mobile Protocol: Detailed Description + + + + + + + + + + + + + +
+ +
+
+
+ +

Mobile Protocol: Detailed Description

+ +
+ +
+

As of version 4.6, major Telegram clients are using MTProto 2.0. +MTProto v.1.0 is deprecated and is currently being phased out.

+
+

This article describes the basic layer of the MTProto protocol version 2.0 (Cloud chats, server-client encryption). The principal differences from version 1.0 (described here for reference) are as follows:

+
    +
  • SHA-256 is used instead of SHA-1;
  • +
  • Padding bytes are involved in the computation of msg_key;
  • +
  • msg_key depends not only on the message to be encrypted, but on a portion of auth_key as well;
  • +
  • 12..1024 padding bytes are used instead of 0..15 padding bytes in v.1.0.
  • +
+

See also: MTProto 2.0: Secret Chats, end-to-end encryption

+

Protocol description

+

Before a message (or a multipart message) is transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message that consists of a 64-bit key identifier auth_key_id (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key msg_key.

+

The authorization key auth_key combined with the message key msg_key define an actual 256-bit key aes_key and a 256-bit initialization vector aes_iv, which are used to encrypt the message using AES-256 encryption in infinite garble extension (IGE) mode. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). In MTProto 2.0, the message key is defined as the 128 middle bits of the SHA-256 of the message body (including session, message ID, padding, etc.) prepended by 32 bytes taken from the authorization key. In the older MTProto 1.0, the message key was computed as the lower 128 bits of SHA-1 of the message body, excluding the padding bytes.

+

Multipart messages are encrypted as a single message.

+ +
+

Got questions about this setup? — Check out the Advanced FAQ!

+
+
Note 1
+

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

+
    +
  • server salt (64-Bit)
  • +
  • session id
  • +
  • message sequence number
  • +
  • message length
  • +
  • time
  • +
+
Note 2
+

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

+

Terminology

+

Authorization Key (auth_key)

+

A 2048-bit key shared by the client device and the server, created upon user registration directly on the client device by exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

+

Server Key

+

A 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

+

Key Identifier (auth_key_id)

+

The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key in a Diffie-Hellman exchange. For MTProto 2.0, SHA1 is still used here, because auth_key_id should identify the authorization key used independently of the protocol version.

+

Session

+

A (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

+

Server Salt

+

A (random) 64-bit number changed every 30 minutes (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 1800 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

+

Message Identifier (msg_id)

+

A (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

+

Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created.

+

Content-related Message

+

A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

+

Message Sequence Number (msg_seqno)

+

A 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

+

Message Key (msg_key)

+

In MTProto 2.0, the middle 128 bits of the SHA-256 hash of the message to be encrypted (including the internal header and the padding bytes for MTProto 2.0), prepended by a 32-byte fragment of the authorization key.

+

In MTProto 1.0, message key was defined differently, as the lower 128 bits of the SHA-1 hash of the message to be encrypted, with padding bytes excluded from the computation of the hash. Authorization key was not involved in this computation.

+

Internal (cryptographic) Header

+

A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

+

External (cryptographic) Header

+

A header (24 bytes) added before an encrypted message or a container. Consists of the key identifier auth_key_id (64 bits) and the message key msg_key (128 bits).

+

Payload

+

External header + encrypted message or container.

+

Defining AES Key and Initialization Vector

+

The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header that is added later) with AES-256 in infinite garble extension (IGE) mode.

+

For MTProto 2.0, the algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows.

+
    +
  • msg_key_large = SHA256 (substr (auth_key, 88+x, 32) + plaintext + random_padding);
  • +
  • msg_key = substr (msg_key_large, 8, 16);
  • +
  • sha256_a = SHA256 (msg_key + substr (auth_key, x, 36));
  • +
  • sha256_b = SHA256 (substr (auth_key, 40+x, 36) + msg_key);
  • +
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • +
  • aes_iv = substr (sha256_b, 0, 8) + substr (sha256_a, 8, 16) + substr (sha256_b, 24, 8);
  • +
+

where x = 0 for messages from client to server and x = 8 for those from server to client.

+

For the obsolete MTProto 1.0, msg_key, aes_key, and aes_iv were computed differently (see this document for reference).

+

The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

+

In MTProto 1.0, when AES was used to encrypt a block of data of a length not divisible by 16 bytes, the data was padded with 0 to 15 random padding bytes random_padding to a length divisible by 16 bytes prior to encryption. In MTProto 2.0, this padding is taken into account when computing msg_key. Note that MTProto 2.0 requires from 12 to 1024 bytes of padding, still subject to the condition that the resulting message length be divisible by 16 bytes.

+

Using MTProto 2.0 instead of MTProto 1.0

+

A client may either use only MTProto 2.0 or only MTProto 1.0 in the same TCP connection. The server detects the protocol used by the first message received from the client, and then uses the same encryption for its messages, and expects the client to use the same encryption henceforth. We recommend using MTProto 2.0; MTProto 1.0 is deprecated and supported for backward compatibility only.

+

Important Checks

+

When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 middle bits of the SHA-256 of the decrypted data with a 32-byte fragment of auth_key prepended to it, and that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with msg_id lower than all or equal to any of the stored values, the message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is forgotten.

+

On top of this, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications of invalid client time. See Mobile Protocol: Service Messages.

+

Storing an Authorization Key on a Client Device

+

It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This can be accomplished by prepending the value of cryptographic hash function, such as SHA-256, of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by checking the SHA-256 value. From the user’s standpoint, this is practically the same as using an application or a website password.

+

Unencrypted Messages

+

Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

+

Only a very limited number of messages of special types can be transmitted as plain text.

+

Schematic Presentation of Messages

+

Encrypted Message

+ + + + +
auth_key_id
int64
msg_key
int128
encrypted_data
bytes
+

Encrypted Message: encrypted_data

+

Contains the cypher text for the following data:

+ + + + + + + + +
salt
int64
session_id
int64
message_id
int64
seq_no
int32
message_data_length
int32
message_data
bytes
padding12..1024
bytes
+

Unencrypted Message

+ + + + + +
auth_key_id = 0
int64
message_id
int64
message_data_length
int32
message_data
bytes
+

MTProto 2.0 uses 12..1024 padding bytes, instead of the 0..15 used in MTProto 1.0

+

Creating an Authorization Key

+

An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

+

See Creating an Authorization Key.

+

During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/mtproto/description_v1.html b/data/corefork.telegram.org/mtproto/description_v1.html new file mode 100644 index 0000000000..be348fa35a --- /dev/null +++ b/data/corefork.telegram.org/mtproto/description_v1.html @@ -0,0 +1,205 @@ + + + + + Mobile Protocol: Detailed Description (v.1.0, DEPRECATED) + + + + + + + + + + + + + +
+ +
+
+
+ +

Mobile Protocol: Detailed Description (v.1.0, DEPRECATED)

+ +
+

This document describes MTProto v.1.0, its status is DEPRECATED. +For information on encryption used in up-to-date Telegram clients, kindly see this document.

+
+

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key.

+

A user key together with the message key define an actual 256-bit key and a 256-bit initialization vector, which is what encrypts the message using AES-256 encryption with infinite garble extension (IGE). Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.) Multipart messages are encrypted as a single message.

+ +

Terminology

+

Authorization Key

+

a 2048-bit key shared by the client device and the server, created upon user registration directly on the client device be exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

+

Server Key

+

a 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

+

Key Identifier

+

The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key based on a Diffie-Hellman exchange.

+

Session

+

a (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

+

Server Salt

+

a (random) 64-bit number periodically (say, every 24 hours) changed (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 300 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

+

Message Identifier (msg_id)

+

a (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

+

Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created. At some point in the nearest future the server will start ignoring messages, in which the lower 32 bits of msg_id contain too many zeroes.

+

Content-related Message

+

A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

+

Message Sequence Number (msg_seqno)

+

a 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

+

Message Key

+

The lower-order 128 bits of the SHA1 hash of the part of the message to be encrypted (including the internal header and excluding the alignment bytes).

+

Internal (cryptographic) Header

+

A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

+

External (cryptographic) Header

+

A header (24 bytes) added before an encrypted message or a container. Consists of a key identifier (64 bits) and a message key (128 bits).

+

Payload

+

External header + encrypted message or container.

+

Defining AES Key and Initialization Vector

+

The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header which is added later) with AES-256 in infinite garble extension (IGE) mode.

+

The algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows:

+
    +
  • msg_key = substr (SHA1 (plaintext), 4, 16);
  • +
  • sha1_a = SHA1 (msg_key + substr (auth_key, x, 32));
  • +
  • sha1_b = SHA1 (substr (auth_key, 32+x, 16) + msg_key + substr (auth_key, 48+x, 16));
  • +
  • sha1_с = SHA1 (substr (auth_key, 64+x, 32) + msg_key);
  • +
  • sha1_d = SHA1 (msg_key + substr (auth_key, 96+x, 32));
  • +
  • aes_key = substr (sha1_a, 0, 8) + substr (sha1_b, 8, 12) + substr (sha1_c, 4, 12);
  • +
  • aes_iv = substr (sha1_a, 8, 12) + substr (sha1_b, 0, 8) + substr (sha1_c, 16, 4) + substr (sha1_d, 0, 8);
  • +
+

where x = 0 for messages from client to server and x = 8 for those from server to client.

+

The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

+

When AES is used to encrypt a block of data of a length not divisible by 16 bytes, the data is padded with random bytes to the smallest length divisible by 16 bytes immediately prior to being encrypted.

+

Important Tests

+

When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 lower-order bits of the SHA1 hash of the previously encrypted portion, and that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with msg_id lower than all or equal to any of the stored values, the message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is forgotten.

+

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications of invalid client time. See Mobile Protocol: Service Messages.

+

Storing an Authorization Key on a Client Device

+

It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This is accomplished by adding the SHA1 of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by being compared with SHA1. From the user’s standpoint, this is practically the same as using an application or a website password.

+

Unencrypted Messages

+

Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

+

Only a very limited number of messages of special types can be transmitted as plain text.

+

Schematic Presentation of Messages

+

Encrypted Message

+ + + + +
auth_key_id
int64
msg_key
int128
encrypted_data
bytes
+

Encrypted Message: encrypted_data

+

Contains the cypher text for the following data:

+ + + + + + + + +
salt
int64
session_id
int64
message_id
int64
seq_no
int32
message_data_length
int32
message_data
bytes
padding 0..15
bytes
+

Unencrypted Message

+ + + + + +
auth_key_id = 0
int64
message_id
int64
message_data_length
int32
message_data
bytes
+

Creating an Authorization Key

+

An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

+

See Creating an Authorization Key.

+

During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/mtproto-transports.html b/data/corefork.telegram.org/mtproto/mtproto-transports.html new file mode 100644 index 0000000000..88d72e683a --- /dev/null +++ b/data/corefork.telegram.org/mtproto/mtproto-transports.html @@ -0,0 +1,281 @@ + + + + + MTProto transports + + + + + + + + + + + + + +
+ +
+
+
+ +

MTProto transports

+ +
+ +

Here's a list of MTProto transport protocols (see the ISO/OSI recap for a full explanation):

+ +

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header.
Additionally, the following transport features can be used:

+ +

Example implementations for these protocols can be seen in tdlib and MadelineProto.

+

Abridged

+

The lightest protocol available.

+
    +
  • Overhead: Very small
  • +
  • Minimum envelope length: 1 byte
  • +
  • Maximum envelope length: 4 bytes
  • +
+

Payload structure:

+
+-+----...----+
+|l|  payload  |
++-+----...----+
+OR
+
++-+---+----...----+
+|h|len|  payload  +
++-+---+----...----+
+

Before sending anything into the underlying socket (see transports), the client must first send 0xef as the first byte (the server will not send 0xef as the first byte in the first reply).
Then, payloads are wrapped in the following envelope:

+
    +
  • Length: payload length, divided by four, and encoded as a single byte, only if the resulting packet length is a value between 0x01..0x7e.
  • +
  • Payload: the MTProto payload
  • +
+

If the packet length divided by four is bigger than or equal to 127 (>= 0x7f), the following envelope must be used, instead:

+
    +
  • Header: A single byte of value 0x7f
  • +
  • Length: payload length, divided by four, and encoded as 3 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
+

Intermediate

+

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used.

+
    +
  • Overhead: small
  • +
  • Minimum envelope length: 4 bytes
  • +
  • Maximum envelope length: 4 bytes
  • +
+

Payload structure:

+
+----+----...----+
++len.+  payload  +
++----+----...----+
+

Before sending anything into the underlying socket (see transports), the client must first send 0xeeeeeeee as the first int (four bytes, the server will not send 0xeeeeeeee as the first int in the first reply).
Then, payloads are wrapped in the following envelope:

+
    +
  • Length: payload length encoded as 4 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
+

Padded intermediate

+

Padded version of the intermediate protocol, to use with obfuscation enabled to bypass ISP blocks.

+
    +
  • Overhead: small-medium
  • +
  • Minimum envelope length: random
  • +
  • Maximum envelope length: random
  • +
+

Before sending anything into the underlying socket (see transports), the client must first send 0xdddddddd as the first int (four bytes, the server will not send 0xdddddddd as the first int in the first reply).
Then, payloads are wrapped in the following envelope:

+
+----+----...----+----...----+
+|tlen|  payload  |  padding  |
++----+----...----+----...----+
+

Envelope description:

+
    +
  • Total length: payload+padding length encoded as 4 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
  • Padding: A random padding string of length 0-15
  • +
+

Full

+

The basic MTProto transport protocol

+
    +
  • Overhead: medium
  • +
  • Minimum envelope length: 12 bytes (length+seqno+crc)
  • +
  • Maximum envelope length: 12 bytes (length+seqno+crc)
  • +
+

Payload structure:

+
+----+----+----...----+----+
+|len.|seq.|  payload  |crc.|
++----+----+----...----+----+
+

Envelope description:

+
    +
  • Length: length+seqno+payload+crc length encoded as 4 length bytes (little endian, the length of the length field must be included, too)
  • +
  • Seqno: the TCP sequence number for this TCP connection (different from the MTProto sequence number): the first packet sent is numbered 0, the next one 1, etc.
  • +
  • payload: MTProto payload
  • +
  • crc: 4 CRC32 bytes computed using length, sequence number, and payload together.
  • +
+

Transport features

+

Additionally, the following transport features can be used:

+

Quick ack

+

These MTProto transport protocols have support for quick acknowledgment.
In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet.
They are the 32 higher-order bits of SHA256 of the encrypted portion of the packet prepended by 32 bytes from the authorization key (the same hash as computed for verifying the message key), with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

+

Transport errors

+

In the event of a transport error (missing auth key, transport flood, etc.), the server may send a packet with a signed little-endian number of 4 bytes, whose absolute value contains the error code (the error itself is actually negative).

+

For example, error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

+

Error 404 (auth key not found) is returned when the specified auth key ID cannot be found by the DC.

+

Error 429 (transport flood) is returned when too many transport connections are established to the same IP in a too short lapse of time, or if any of the container/service message limits are reached.

+

Error 444 (invalid DC) is returned while creating an auth key, connecting to an MTProxy or in other contexts if an invalid DC ID is specified.

+

Transport obfuscation

+

Transport obfuscation is required to use the websocket transports.

+

Transport obfuscation to prevent ISP blocks is implemented using the following protocol, situated under the MTProto transport in the ISO/OSI stack, see the recap; this means that the payload is first wrapped in the MTProto transport envelope (all transports are supported), and then obfuscated:

+

Prior to establishing the connection (and eventually sending the protocol header of a specific MTProto transport), a 64-byte (512-bit) random initialization payload is generated.
During the generation process, special care must be taken in order to avoid a situation where that the first int (first four bytes) of the random string are equal to one of the known protocol identifiers (see above).
In particular, the first four bytes must not be equal to 0xdddddddd (padded intermediate), 0xeeeeeeee (intermediate), POST, GET, HEAD, or any of the HTTP methods that are accepted by the MTProto servers.
The first byte must also not be equal to 0xef (abridged).
Bytes 4-8 must also not be equal to 0x00000000, since that would indicate use of the full transport with the initial TCP sequence number (0).

+

The protocol identifier, if present, must be inserted in the initialization payload at byte offset 56: if its length is less than 4, it must be padded using the protocol identifier itself, to make its length 4 (0xef => 0xefefefef): the standalone protocol identifier must be not be sent aftwerwards.

+

This protocol is also (but not exclusively) used when connecting to MTProxies: only in this case, the DC ID in a specially encoded form must also be inserted in the initialization payload at offset 60.
The encoding simply consist of the DC ID in two-byte signed little-endian form; 10000 has to be added to the DC ID to connect to the test servers; it has to be made negative if the DC we're connecting to is a media (not CDN) DC.

+

Next, a secondary initialization payload is generated by reversing the primary initialization payload.

+

Two keys are extracted from both initialization payloads, using bytes at offsets 8-40: the key extracted from the primary payload is used as encryption key, the key extracted from the secondary payload is used as decryption key.

+

Two IVs are extracted from both initialization payloads, using bytes at offsets 40-56: the IV extracted from the primary payload is used as encryption IV, the IV extracted from the secondary payload is used as decryption IV.

+

Only if using MTProxy, the secret is used to provide connection with the MTProxy server.
The secret is a 16-byte string, usually distributed in its hexadecimal form along with the MTProxy host and port.

+

Often, a 17-byte version of the secret can be found: this simply indicates that the client should use a specific MTProto transport (based on the first byte, usually it's 0xdd, to indicate that the padded intermediate protocol should be used 0xdddddddd; however, clients should default to the padded intermediate transport whenever an additional byte in the secret is encountered).

+

The extracted encryption and decryption keys must be concatenated with the secret (the first byte of which should be ignored if it's the 17-byte version), and the SHA256 hash of such string should be used as encryption/decryption key.

+

The obtained encryption and decryption key/IV pairs must then be used with AES-256-CTR to encrypt and decrypt all outgoing and incoming payloads.

+

The first thing that must be encrypted using the encryption key is the initialization payload itself.
Then bytes 56-64 of the encrypted initialization payload are substituted in the original initialization payload: this is the part that contains the constant MTProto transport protocol identifier and the DC ID (only for MTProxies).

+

The final initialization payload must then be sent in the socket as first 64 bytes after the TCP handshake.

+

Example pseudocode for the generation of an MTProxy connection payload (media DC 4) using the obfuscated padded intermediate transport.
Warning: do not use the specified proxy secret in any MTProxy exposed on the internet.

+
protocol := 0xdddddddd
+dc := 0xfcff
+
+while 1:
+    init := (56 random bytes) + protocol + dc + (2 random bytes)
+
+    if init[0] == 0xef:
+      continue
+
+    first_int := substr(init, 0, 4)
+    if first_int == 0x44414548 || first_int == 0x54534f50 || first_int == 0x20544547 || first_int == 0x4954504f || first_int == 0x02010316 || first_int == 0xdddddddd || first_int == 0xeeeeeeee:
+      continue
+
+    second_int := substr(init, 0, 4)
+    if second_int == 0x00000000:
+      continue
+
+    break
+
+initRev := strrev(init)
+
+encryptKey := substr(init, 8, 32)
+encryptIV := substr(init, 40, 16)
+
+decryptKey := substr(initRev, 8, 32)
+decryptIV := substr(initRev, 40, 16)
+
+secret := substr(0xdd99999999999999999999999999999999, 1, 16)
+
+encryptKey = SHA256(encryptKey + secret)
+decryptKey = SHA256(decryptKey + secret)
+
+encryptedInit := CTR(encryptKey, encryptIV, init)
+
+finalInit := substr(init, 0, 56) + substr(encryptedInit, 56, 8)
+
+write(finalInit)
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/mtproto/samples-auth_key.html b/data/corefork.telegram.org/mtproto/samples-auth_key.html new file mode 100644 index 0000000000..54ce6ab2ee --- /dev/null +++ b/data/corefork.telegram.org/mtproto/samples-auth_key.html @@ -0,0 +1,748 @@ + + + + + samples-auth_key + + + + + + + + + + + + + +
+ +
+
+
+ +

samples-auth_key

+ +

In the examples below, the transport headers are omitted:

+
+

For example, for an abridged version of the transport the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01-0x7e = data length divided by 4; or 0x7f followed by 3 bytes (little endian) divided by 4) followed by the data themselves. In this case, server responses have the same form (although the server does not send 0xefas the first byte).

+
+

Detailed documentation on creating authorization keys is available here ».

+

1. Request for (p,q) Authorization

+
req_pq#60469778 nonce:int128 = ResPQ
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac42770964aExact unixtime * 2^32
message_length16, 420Message body length
%(req_pq)20, 460469778req_pq constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCRandom number
+

The header is 20 bytes long, the message body is 20 bytes long, and the entire message is 40 bytes in length.

+
0000 | 00 00 00 00 00 00 00 00 4A 96 70 27 C4 7A E5 51
+0010 | 14 00 00 00 78 97 46 60 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC
+

2. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 C8 83 1E C9 7A E5 51
+0010 | 40 00 00 00 63 24 16 05 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 08 17 ED 48 94 1A 08 F9
+0040 | 81 00 00 00 15 C4 B5 1C 01 00 00 00 21 6B E8 6C
+0050 | 02 2B B4 C3
+
Response decomposition using the following formula:
+
resPQ#05162463 nonce:int128 server_nonce:int128 pq:string server_public_key_fingerprints:Vector long = ResPQ 
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57AC91E83C801Server message ID
message_length16, 464Message body length
%(resPQ)20, 405162463resPQ constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Server-generated random number
pq56, 1217ED48941A08F981Single-byte prefix denoting length, an 8-byte string, and three bytes of padding
%(Vector long)68, 41cb5c415Vector long constructor number from TL schema
count72, 41Number of elements in key fingerprint list
fingerprints[]76, 8c3b42b026ce86b2164 lower-order bits of SHA1 (server_public_key)
+

The server_public_key public key has been selected whose fingerprint corresponds to the only one received from the server: c3b42b026ce86b21.

+

3. Pq = 17ED48941A08F981 decomposed into 2 prime cofactors:

+
p = 494C553B
+q = 53911073
+

4. encrypted_data Generation

+
p_q_inner_data#83c95aec pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 = P_Q_inner_data
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(p_q_inner_data)0, 483c95aecp_q_inner_data constructor number from TL schema
pq4, 1217ED48941A08F981Single-byte prefix denoting length, 8-byte string, and three bytes of padding
p16, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q24, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
nonce32, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce48, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce64, 32311C85DB234AA2640AFC4A76A735CF5B 1F0FD68BD17FA181E1229AD867CC024DClient-generated random number
+

The serialization of P_Q_inner_data produces some string data. This is followed by encrypted_data:

+
SHA1 (data) = DB761C27718A2305044F71F2AD951629D78B2449
+RSA (data_with_hash, server_public_key) = 7BB0100A523161904D9C69FA04BC60DECFC5DD74B99995C768EB60D8716E2109BAF2D4601DAB6B09610DC11067BB89021E09471FCFA52DBD0F23204AD8CA8B012BF40A112F44695AB6C266955386114EF5211E6372227ADBD34995D3E0E5FF02EC63A43F9926878962F7C570E6A6E78BF8366AF917A5272675C46064BE62E3E202EFA8B1ADFB1C32A898C2987BE27B5F31D57C9BB963ABCB734B16F652CEDB4293CBB7C878A3A3FFAC9DBEA9DF7C67BC9E9508E111C78FC46E057F5C65ADE381D91FEE430A6B576A99BDF8551FDB1BE2B57069B1A45730618F27427E8A04720B4971EF4A9215983D68F2830C3EAA6E40385562F970D38A05C9F1246DC33438E6
+

The length of the final string was 256 bytes.

+
Request to Start Diffie-Hellman Key Exchange
+
req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:string q:string public_key_fingerprint:long encrypted_data:string = Server_DH_Params
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac917717a27Exact unixtime * 2^32
message_length16, 4320Message body length
%(req_DH_params)20, 4d712e4bereq_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
p56, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q64, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
public_key_fingerprint72, 8c3b42b026ce86b21Fingerprint of public key used
encrypted_data80, 260See aboveSee “Generation of encrypted_data"
+
0000 | 00 00 00 00 00 00 00 00 27 7A 71 17 C9 7A E5 51
+0010 | 40 01 00 00 BE E4 12 D7 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 04 49 4C 55 3B 00 00 00
+0040 | 04 53 91 10 73 00 00 00 21 6B E8 6C 02 2B B4 C3
+0050 | FE 00 01 00 7B B0 10 0A 52 31 61 90 4D 9C 69 FA
+0060 | 04 BC 60 DE CF C5 DD 74 B9 99 95 C7 68 EB 60 D8
+0070 | 71 6E 21 09 BA F2 D4 60 1D AB 6B 09 61 0D C1 10
+0080 | 67 BB 89 02 1E 09 47 1F CF A5 2D BD 0F 23 20 4A
+0090 | D8 CA 8B 01 2B F4 0A 11 2F 44 69 5A B6 C2 66 95
+00A0 | 53 86 11 4E F5 21 1E 63 72 22 7A DB D3 49 95 D3
+00B0 | E0 E5 FF 02 EC 63 A4 3F 99 26 87 89 62 F7 C5 70
+00C0 | E6 A6 E7 8B F8 36 6A F9 17 A5 27 26 75 C4 60 64
+00D0 | BE 62 E3 E2 02 EF A8 B1 AD FB 1C 32 A8 98 C2 98
+00E0 | 7B E2 7B 5F 31 D5 7C 9B B9 63 AB CB 73 4B 16 F6
+00F0 | 52 CE DB 42 93 CB B7 C8 78 A3 A3 FF AC 9D BE A9
+0100 | DF 7C 67 BC 9E 95 08 E1 11 C7 8F C4 6E 05 7F 5C
+0110 | 65 AD E3 81 D9 1F EE 43 0A 6B 57 6A 99 BD F8 55
+0120 | 1F DB 1B E2 B5 70 69 B1 A4 57 30 61 8F 27 42 7E
+0130 | 8A 04 72 0B 49 71 EF 4A 92 15 98 3D 68 F2 83 0C
+0140 | 3E AA 6E 40 38 55 62 F9 70 D3 8A 05 C9 F1 24 6D
+0150 | C3 34 38 E6
+

5. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 54 43 36 CB 7A E5 51
+0010 | 78 02 00 00 5C 07 E8 D0 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 FE 50 02 00 28 A9 2F E2
+0040 | 01 73 B3 47 A8 BB 32 4B 5F AB 26 67 C9 A8 BB CE
+0050 | 64 68 D5 B5 09 A4 CB DD C1 86 24 0A C9 12 CF 70
+0060 | 06 AF 89 26 DE 60 6A 2E 74 C0 49 3C AA 57 74 1E
+0070 | 6C 82 45 1F 54 D3 E0 68 F5 CC C4 9B 44 44 12 4B
+0080 | 96 66 FF B4 05 AA B5 64 A3 D0 1E 67 F6 E9 12 86
+0090 | 7C 8D 20 D9 88 27 07 DC 33 0B 17 B4 E0 DD 57 CB
+00A0 | 53 BF AA FA 9E F5 BE 76 AE 6C 1B 9B 6C 51 E2 D6
+00B0 | 50 2A 47 C8 83 09 5C 46 C8 1E 3B E2 5F 62 42 7B
+00C0 | 58 54 88 BB 3B F2 39 21 3B F4 8E B8 FE 34 C9 A0
+00D0 | 26 CC 84 13 93 40 43 97 4D B0 35 56 63 30 38 39
+00E0 | 2C EC B5 1F 94 82 4E 14 0B 98 63 77 30 A4 BE 79
+00F0 | A8 F9 DA FA 39 BA E8 1E 10 95 84 9E A4 C8 34 67
+0100 | C9 2A 3A 17 D9 97 81 7C 8A 7A C6 1C 3F F4 14 DA
+0110 | 37 B7 D6 6E 94 9C 0A EC 85 8F 04 82 24 21 0F CC
+0120 | 61 F1 1C 3A 91 0B 43 1C CB D1 04 CC CC 8D C6 D2
+0130 | 9D 4A 5D 13 3B E6 39 A4 C3 2B BF F1 53 E6 3A CA
+0140 | 3A C5 2F 2E 47 09 B8 AE 01 84 4B 14 2C 1E E8 9D
+0150 | 07 5D 64 F6 9A 39 9F EB 04 E6 56 FE 36 75 A6 F8
+0160 | F4 12 07 8F 3D 0B 58 DA 15 31 1C 1A 9F 8E 53 B3
+0170 | CD 6B B5 57 2C 29 49 04 B7 26 D0 BE 33 7E 2E 21
+0180 | 97 7D A2 6D D6 E3 32 70 25 1C 2C A2 9D FC C7 02
+0190 | 27 F0 75 5F 84 CF DA 9A C4 B8 DD 5F 84 F1 D1 EB
+01A0 | 36 BA 45 CD DC 70 44 4D 8C 21 3E 4B D8 F6 3B 8A
+01B0 | B9 5A 2D 0B 41 80 DC 91 28 3D C0 63 AC FB 92 D6
+01C0 | A4 E4 07 CD E7 C8 C6 96 89 F7 7A 00 74 41 D4 A6
+01D0 | A8 38 4B 66 65 02 D9 B7 7F C6 8B 5B 43 CC 60 7E
+01E0 | 60 A1 46 22 3E 11 0F CB 43 BC 3C 94 2E F9 81 93
+01F0 | 0C DC 4A 1D 31 0C 0B 64 D5 E5 5D 30 8D 86 32 51
+0200 | AB 90 50 2C 3E 46 CC 59 9E 88 6A 92 7C DA 96 3B
+0210 | 9E B1 6C E6 26 03 B6 85 29 EE 98 F9 F5 20 64 19
+0220 | E0 3F B4 58 EC 4B D9 45 4A A8 F6 BA 77 75 73 CC
+0230 | 54 B3 28 89 5B 1D F2 5E AD 9F B4 CD 51 98 EE 02
+0240 | 2B 2B 81 F3 88 D2 81 D5 E5 BC 58 01 07 CA 01 A5
+0250 | 06 65 C3 2B 55 27 15 F3 35 FD 76 26 4F AD 00 DD
+0260 | D5 AE 45 B9 48 32 AC 79 CE 7C 51 1D 19 4B C4 2B
+0270 | 70 EF A8 50 BB 15 C2 01 2C 52 15 CA BF E9 7C E6
+0280 | 6B 8D 87 34 D0 EE 75 9A 63 8A F0 13
+
Response decomposition using the following formula:
+
server_DH_params_fail#79cb045d nonce:int128 server_nonce:int128 new_nonce_hash:int128 = Server_DH_Params;
+server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:string = Server_DH_Params;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57ACB36435401Exact unixtime * 2^32
message_length16, 4632Message body length
%(server_DH_params_ok)20, 4d0e8075cserver_DH_params_ok constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_answer56, 596See belowSee “Decomposition of encrypted_answer"
+
Conversion of encrypted_answer into answer:
+
encrypted_answer = 28A92FE20173B347A8BB324B5FAB2667C9A8BBCE6468D5B509A4CBDDC186240AC912CF7006AF8926DE606A2E74C0493CAA57741E6C82451F54D3E068F5CCC49B4444124B9666FFB405AAB564A3D01E67F6E912867C8D20D9882707DC330B17B4E0DD57CB53BFAAFA9EF5BE76AE6C1B9B6C51E2D6502A47C883095C46C81E3BE25F62427B585488BB3BF239213BF48EB8FE34C9A026CC8413934043974DB03556633038392CECB51F94824E140B98637730A4BE79A8F9DAFA39BAE81E1095849EA4C83467C92A3A17D997817C8A7AC61C3FF414DA37B7D66E949C0AEC858F048224210FCC61F11C3A910B431CCBD104CCCC8DC6D29D4A5D133BE639A4C32BBFF153E63ACA3AC52F2E4709B8AE01844B142C1EE89D075D64F69A399FEB04E656FE3675A6F8F412078F3D0B58DA15311C1A9F8E53B3CD6BB5572C294904B726D0BE337E2E21977DA26DD6E33270251C2CA29DFCC70227F0755F84CFDA9AC4B8DD5F84F1D1EB36BA45CDDC70444D8C213E4BD8F63B8AB95A2D0B4180DC91283DC063ACFB92D6A4E407CDE7C8C69689F77A007441D4A6A8384B666502D9B77FC68B5B43CC607E60A146223E110FCB43BC3C942EF981930CDC4A1D310C0B64D5E55D308D863251AB90502C3E46CC599E886A927CDA963B9EB16CE62603B68529EE98F9F5206419E03FB458EC4BD9454AA8F6BA777573CC54B328895B1DF25EAD9FB4CD5198EE022B2B81F388D281D5E5BC580107CA01A50665C32B552715F335FD76264FAD00DDD5AE45B94832AC79CE7C511D194BC42B70EFA850BB15C2012C5215CABFE97CE66B8D8734D0EE759A638AF013
+tmp_aes_key = F011280887C7BB01DF0FC4E17830E0B91FBB8BE4B2267CB985AE25F33B527253
+tmp_aes_iv = 3212D579EE35452ED23E0D0C92841AA7D31B2E9BDEF2151E80D15860311C85DB
+answer = BA0D89B53E0549828CCA27E966B301A48FECE2FCA5CF4D33F4A11EA877BA4AA57390733002000000FE000100C71CAEB9C6B1C9048E6C522F70F13F73980D40238E3E21C14934D037563D930F48198A0AA7C14058229493D22530F4DBFA336F6E0AC925139543AED44CCE7C3720FD51F69458705AC68CD4FE6B6B13ABDC9746512969328454F18FAF8C595F642477FE96BB2A941D5BCD1D4AC8CC49880708FA9B378E3C4F3A9060BEE67CF9A4A4A695811051907E162753B56B0F6B410DBA74D8A84B2A14B3144E0EF1284754FD17ED950D5965B4B9DD46582DB1178D169C6BC465B0D6FF9CA3928FEF5B9AE4E418FC15E83EBEA0F87FA9FF5EED70050DED2849F47BF959D956850CE929851F0D8115F635B105EE2E4E15D04B2454BF6F4FADF034B10403119CD8E3B92FCC5BFE000100262AABA621CC4DF587DC94CF8252258C0B9337DFB47545A49CDD5C9B8EAE7236C6CADC40B24E88590F1CC2CC762EBF1CF11DCC0B393CAAD6CEE4EE5848001C73ACBB1D127E4CB93072AA3D1C8151B6FB6AA6124B7CD782EAF981BDCFCE9D7A00E423BD9D194E8AF78EF6501F415522E44522281C79D906DDB79C72E9C63D83FB2A940FF779DFB5F2FD786FB4AD71C9F08CF48758E534E9815F634F1E3A80A5E1C2AF210C5AB762755AD4B2126DFA61A77FA9DA967D65DFD0AFB5CDF26C4D4E1A88B180F4E0D0B45BA1484F95CB2712B50BF3F5968D9D55C99C0FB9FB67BFF56D7D4481B634514FBA3488C4CDA2FC0659990E8E868B28632875A9AA703BCDCE8FCB7AE551
+
Server_DH_inner_data decomposition using the following formula:
+
server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:string g_a:string server_time:int = Server_DH_inner_data;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(server_DH_inner_data)0, 4b5890dbaserver_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
g36, 42Value received from server in Step 2
dh_prime40, 260C71CAEB9C6B1C9048E6C522F70F13F73 980D40238E3E21C14934D037563D930F 48198A0AA7C14058229493D22530F4DB FA336F6E0AC925139543AED44CCE7C37 20FD51F69458705AC68CD4FE6B6B13AB DC9746512969328454F18FAF8C595F64 2477FE96BB2A941D5BCD1D4AC8CC4988 0708FA9B378E3C4F3A9060BEE67CF9A4 A4A695811051907E162753B56B0F6B41 0DBA74D8A84B2A14B3144E0EF1284754 FD17ED950D5965B4B9DD46582DB1178D 169C6BC465B0D6FF9CA3928FEF5B9AE4 E418FC15E83EBEA0F87FA9FF5EED7005 0DED2849F47BF959D956850CE929851F 0D8115F635B105EE2E4E15D04B2454BF 6F4FADF034B10403119CD8E3B92FCC5B
g_a300, 260262AABA621CC4DF587DC94CF8252258C 0B9337DFB47545A49CDD5C9B8EAE7236 C6CADC40B24E88590F1CC2CC762EBF1C F11DCC0B393CAAD6CEE4EE5848001C73 ACBB1D127E4CB93072AA3D1C8151B6FB 6AA6124B7CD782EAF981BDCFCE9D7A00 E423BD9D194E8AF78EF6501F415522E4 4522281C79D906DDB79C72E9C63D83FB 2A940FF779DFB5F2FD786FB4AD71C9F0 8CF48758E534E9815F634F1E3A80A5E1 C2AF210C5AB762755AD4B2126DFA61A7 7FA9DA967D65DFD0AFB5CDF26C4D4E1A 88B180F4E0D0B45BA1484F95CB2712B5 0BF3F5968D9D55C99C0FB9FB67BFF56D 7D4481B634514FBA3488C4CDA2FC0659 990E8E868B28632875A9AA703BCDCE8F
server_time560, 41373993675Server time
+

6. Random number b is computed:

+
b = 6F620AFA575C9233EB4C014110A7BCAF49464F798A18A0981FEA1E05E8DA67D9681E0FD6DF0EDF0272AE3492451A84502F2EFC0DA18741A5FB80BD82296919A70FAA6D07CBBBCA2037EA7D3E327B61D585ED3373EE0553A91CBD29B01FA9A89D479CA53D57BDE3A76FBD922A923A0A38B922C1D0701F53FF52D7EA9217080163A64901E766EB6A0F20BC391B64B9D1DD2CD13A7D0C946A3A7DF8CEC9E2236446F646C42CFE2B60A2A8D776E56C8D7519B08B88ED0970E10D12A8C9E355D765F2B7BBB7B4CA9360083435523CB0D57D2B106FD14F94B4EEE79D8AC131CA56AD389C84FE279716F8124A543337FB9EA3D988EC5FA63D90A4BA3970E7A39E5C0DE5
+
Generation of encrypted_data
+
client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:string = Client_DH_Inner_Data
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(client_DH_inner_data)0, 46643b654client_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
retry_id36, 80First attempt
g_b44, 26073700E7BFC7AEEC828EB8E0DCC04D09A 0DD56A1B4B35F72F0B55FCE7DB7EBB72 D7C33C5D4AA59E1C74D09B01AE536B31 8CFED436AFDB15FE9EB4C70D7F0CB14E 46DBBDE9053A64304361EB358A9BB32E 9D5C2843FE87248B89C3F066A7D5876D 61657ACC52B0D81CD683B2A0FA93E8AD AB20377877F3BC3369BBF57B10F5B589 E65A9C27490F30A0C70FFCFD3453F5B3 79C1B9727A573CFFDCA8D23C721B135B 92E529B1CDD2F7ABD4F34DAC4BE1EEAF 60993DDE8ED45890E4F47C26F2C0B2E0 37BB502739C8824F2A99E2B1E7E41658 3417CC79A8807A4BDAC6A5E9805D4F61 86C37D66F6988C9F9C752896F3D34D25 529263FAF2670A09B2A59CE35264511Fg^b mod dh_prime
+

The serialization of Client_DH_Inner_Data produces some string data. This is followed by encrypted_data:

+
data_with_hash := SHA1(data) + data + (0-15 random bytes); such that the length be divisible by 16;
+AES256_ige_encrypt (data_with_hash, tmp_aes_key, tmp_aes_iv) = 928A4957D0463B525C1CC48AABAA030A256BE5C746792C84CA4C5A0DF60AC799048D98A38A8480EDCF082214DFC79DCB9EE34E206513E2B3BC1504CFE6C9ADA46BF9A03CA74F192EAF8C278454ADABC795A566615462D31817382984039505F71CB33A41E2527A4B1AC05107872FED8E3ABCEE1518AE965B0ED3AED7F67479155BDA8E4C286B64CDF123EC748CF289B1DB02D1907B562DF462D8582BA6F0A3022DC2D3504D69D1BA48B677E3A830BFAFD67584C8AA24E1344A8904E305F9587C92EF964F0083F50F61EAB4A393EAA33C9270294AEDC7732891D4EA1599F52311D74469D2112F4EDF3F342E93C8E87E812DC3989BAECFE6740A46077524C75093F5A5405736DE8937BB6E42C9A0DCF22CA53227D462BCCC2CFE94B6FE86AB7FBFA395021F66661AF7C0024CA2986CA03F3476905407D1EA9C010B763258DB1AA2CC7826D91334EFC1FDC665B67FE45ED0
+

The length of the final string was 336 bytes.

+
Request
+
set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:string = Set_client_DH_params_answer;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57acd2aa32c6dExact unixtime * 2^32
message_length16, 4376Message body length
%(set_client_DH_params)20, 4f5045f1fset_client_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_data56, 340See aboveSee “Generation of encrypted_data"
+
0000 | 00 00 00 00 00 00 00 00 6D 2C A3 2A CD 7A E5 51
+0010 | 78 01 00 00 1F 5F 04 F5 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 FE 50 01 00 92 8A 49 57
+0040 | D0 46 3B 52 5C 1C C4 8A AB AA 03 0A 25 6B E5 C7
+0050 | 46 79 2C 84 CA 4C 5A 0D F6 0A C7 99 04 8D 98 A3
+0060 | 8A 84 80 ED CF 08 22 14 DF C7 9D CB 9E E3 4E 20
+0070 | 65 13 E2 B3 BC 15 04 CF E6 C9 AD A4 6B F9 A0 3C
+0080 | A7 4F 19 2E AF 8C 27 84 54 AD AB C7 95 A5 66 61
+0090 | 54 62 D3 18 17 38 29 84 03 95 05 F7 1C B3 3A 41
+00A0 | E2 52 7A 4B 1A C0 51 07 87 2F ED 8E 3A BC EE 15
+00B0 | 18 AE 96 5B 0E D3 AE D7 F6 74 79 15 5B DA 8E 4C
+00C0 | 28 6B 64 CD F1 23 EC 74 8C F2 89 B1 DB 02 D1 90
+00D0 | 7B 56 2D F4 62 D8 58 2B A6 F0 A3 02 2D C2 D3 50
+00E0 | 4D 69 D1 BA 48 B6 77 E3 A8 30 BF AF D6 75 84 C8
+00F0 | AA 24 E1 34 4A 89 04 E3 05 F9 58 7C 92 EF 96 4F
+0100 | 00 83 F5 0F 61 EA B4 A3 93 EA A3 3C 92 70 29 4A
+0110 | ED C7 73 28 91 D4 EA 15 99 F5 23 11 D7 44 69 D2
+0120 | 11 2F 4E DF 3F 34 2E 93 C8 E8 7E 81 2D C3 98 9B
+0130 | AE CF E6 74 0A 46 07 75 24 C7 50 93 F5 A5 40 57
+0140 | 36 DE 89 37 BB 6E 42 C9 A0 DC F2 2C A5 32 27 D4
+0150 | 62 BC CC 2C FE 94 B6 FE 86 AB 7F BF A3 95 02 1F
+0160 | 66 66 1A F7 C0 02 4C A2 98 6C A0 3F 34 76 90 54
+0170 | 07 D1 EA 9C 01 0B 76 32 58 DB 1A A2 CC 78 26 D9
+0180 | 13 34 EF C1 FD C6 65 B6 7F E4 5E D0
+

7. Computing auth_key using formula g^{ab} mod dh_prime:

+
auth_key = AB96E207C631300986F30EF97DF55E179E63C112675F0CE502EE76D74BBEE6CBD1E95772818881E9F2FF54BD52C258787474F6A7BEA61EABE49D1D01D55F64FC07BC31685716EC8FB46FEACF9502E42CFD6B9F45A08E90AA5C2B5933AC767CBE1CD50D8E64F89727CA4A1A5D32C0DB80A9FCDBDDD4F8D5A1E774198F1A4299F927C484FEEC395F29647E43C3243986F93609E23538C21871DF50E00070B3B6A8FA9BC15628E8B43FF977409A61CEEC5A21CF7DFB5A4CC28F5257BC30CD8F2FB92FBF21E28924065F50E0BBD5E11A420300E2C136B80E9826C6C5609B5371B7850AA628323B6422F3A94F6DFDE4C3DC1EA60F7E11EE63122B3F39CBD1A8430157
+

8. The server verifies that auth_key_hash is unique.

+

The key is unique.

+

9. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 30 AA C5 CE 7A E5 51
+0010 | 34 00 00 00 34 F7 CB 3B 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 CC EB C0 21 72 66 E1 ED
+0040 | EC 7F B0 A0 EE D6 C2 20
+

Set_client_DH_params_answer decomposition using the following formula:

+
dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
+dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
+dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(dh_gen_ok)0, 43bcbf734dh_gen_ok constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce_hash136, 16CCEBC0217266E1EDEC7FB0A0EED6C220
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/security_guidelines.html b/data/corefork.telegram.org/mtproto/security_guidelines.html new file mode 100644 index 0000000000..a4627d6170 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/security_guidelines.html @@ -0,0 +1,177 @@ + + + + + Security Guidelines for Client Developers + + + + + + + + + + + + + +
+ +
+
+
+ +

Security Guidelines for Client Developers

+ +
+ +

See also:

+

+ +

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply.

+
+

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. +MTProto v.1.0 is deprecated and is currently being phased out.

+
+

Diffie-Hellman key exchange

+

We use DH key exchange in two cases:

+ +

In both cases, there are some verifications to be done whenever DH is used:

+

Validation of DH parameters

+

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

+

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

+

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

+
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
+

g_a and g_b validation

+

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

+

Checking SHA1 hash values during key generation

+

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

+
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
+

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

+

Checking nonce, server_nonce and new_nonce fields

+

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

+

Using secure pseudorandom number generator to create DH secret parameters a and b

+

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

+

MTProto Encrypted Messages

+

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

+

Checking SHA256 hash value of msg_key

+

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA256 of the plaintext obtained as the result of decryption (including the final 12...1024 padding bytes), prepended with 32 bytes taken from the auth_key, as explained in MTProto 2.0 Description.

+

If an error is encountered before this check could be performed, the client must perform the msg_key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

+

Checking message length

+

The client must check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference (i.e. the length of the random padding) lies in the range from 12 to 1024 bytes.

+

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

+

Checking session_id

+

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

+

Checking msg_id

+

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

+

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

+

Behavior in case of mismatch

+

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

+

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

+

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

+
+

The previous version of security recommendations relevant for MTProto 1.0 clients is available here.

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/mtproto/security_guidelines_v1.html b/data/corefork.telegram.org/mtproto/security_guidelines_v1.html new file mode 100644 index 0000000000..7240af0216 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/security_guidelines_v1.html @@ -0,0 +1,175 @@ + + + + + Security Guidelines for Client Developers (v.1.0, DEPRECATED) + + + + + + + + + + + + + +
+ +
+
+
+ +

Security Guidelines for Client Developers (v.1.0, DEPRECATED)

+ +
+ +
+

This document describes security recommendations for clients using MTProto 1.0, its status is DEPRECATED. +For up-to-date security recommendations, kindly see this document.

+
+

See also:

+

+ +

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply with these.

+

Diffie--Hellman key exchange

+

We use DH key exchange in two cases:

+ +

In both cases, there are some verifications to be done whenever DH is used:

+

Validation of DH parameters

+

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

+

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

+

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

+
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
+

g_a and g_b validation

+

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

+

Checking SHA1 hash values

+

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

+
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
+

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

+

Checking nonce, server_nonce and new_nonce fields

+

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

+

Using secure pseudorandom number generator to create DH secret parameters a and b

+

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

+

MTProto Encrypted Messages

+

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

+

Checking SHA1 hash value of msg_key

+

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA1 of the plaintext obtained as the result of decryption (without the final padding bytes).

+

If an error is encountered before this check could be performed, the client must perform the msg-key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

+

Checking message length

+

The client is to check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference is not more than 15 bytes. Apart from this, knowing the total length is important for the previous verification.

+

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

+

Checking session_id

+

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

+

Checking msg_id

+

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

+

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

+

Behavior in case of mismatch

+

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

+

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

+

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/mtproto/serialize.html b/data/corefork.telegram.org/mtproto/serialize.html new file mode 100644 index 0000000000..e2028a2386 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/serialize.html @@ -0,0 +1,240 @@ + + + + + Binary Data Serialization + + + + + + + + + + + + + +
+ +
+
+
+ +

Binary Data Serialization

+ +

MTProto operation requires that elementary and composite data types as well as queries to which such data types are passed as arguments or by which they are returned, be transmitted in binary format (i. e. serialized) . +The TL language is used to describe the data types to be serialized.

+

General Definitions

+

For our purposes, we can identify a type with the set of its (serialized) values understood as strings (finite sequences) of 32-bit numbers (transmitted in little endian order).

+

Therefore:

+
    +
  • Alphabet (A), in this case, is a set of 32-bit numbers (normally, signed, i. e. between -2^31 and 2^31 - 1).
  • +
  • Value, in this case, is the same as a string in Alphabet A, i. e. a finite (possibly, empty) sequence of 32-bit numbers. The set of all such sequences is designated as A*.
  • +
  • Type, for our purposes, is the same as the set of legal values of a type, i. e. some set T which is a subset of A* and is a prefix code (i. e. no element of T may be a prefix for any other element). Therefore, any sequence from A* can contain no more than one prefix that is a member of T.
  • +
  • Value of Type T is any sequence (value) which is a member of T as a subset of A*.
  • +
  • Compatible Types are the types T and T’ not intersecting as subsets of A*, such that the union of T and T' is a prefix code.
  • +
  • Coordinated System of Types is a finite or infinite set of types T_1, ..., T_n, ..., such that any two types from this set are compatible.
  • +
  • Data Type is the same as type in the sense of the definition above.
  • +
  • Functional Type is a type describing a function; it is not a type in the sense of the definition above. Initially, we ignore the existence of functional types and describe only the data types; however, in reality, functional types will later be implemented in some extension of this system using the so-called temporary combinators.
  • +
+

Combinators, Constructors, Composite Data Types

+
    +
  • +

    Combinator is a function that takes arguments of certain types and returns a value of some other type. We normally look at combinators whose argument and result types are data types (rather than functional types).

    +
  • +
  • +

    Arity (of combinator) is a non-negative integer, the number of combinator arguments.

    +
  • +
  • +

    Combinator identifier is an identifier beginning with a lowercase Roman letter that uniquely identifies a combinator.

    +
  • +
  • +

    Combinator number or combinator name is a 32-bit number (i.e., an element of A) that uniquely identifies a combinator. Most often, it is CRC32 of the string containing the combinator description without the final semicolon, and with one space between contiguous lexemes. This always falls in the range from 0x01000000 to 0xffffff00. The highest 256 values are reserved for the so-called temporal-logic combinators used to transmit functions. We frequently denote as combinator the combinator name with single quotes: ‘combinator’.

    +
  • +
  • +

    Combinator description is a string of format combinator_name type_arg_1 ... type_arg_N = type_res; where N stands for the arity of the combinator, type_arg_i is the type of the i-th argument (or rather, a string with the combinator name), and type_res is the combinator value type.

    +
  • +
  • +

    Constructor is a combinator that cannot be computed (reduced). This is used to represent composite data types. For example, combinator ‘int_tree’ with description int_tree IntTree int IntTree = IntTree, alongside combinator empty_tree = IntTree, may be used to define a composite data type called “IntTree” that takes on values in the form of binary trees with integers as nodes.

    +
  • +
  • +

    Function (functional combinator) is a combinator which may be computed (reduced) on condition that the requisite number of arguments of requisite types are provided. The result of the computation is an expression consisting of constructors and base type values only.

    +
  • +
  • +

    Normal form is an expression consisting only of constructors and base type values; that which is normally the result of computing a function.

    +
  • +
  • +

    Type identifier is an identifier that normally starts with a capital letter in Roman script and uniquely identifies the type.

    +
  • +
  • +

    Type number or type name is a 32-bit number that uniquely identifies a type; it normally is the sum of the CRC32 values of the descriptions of the type constructors.

    +
  • +
  • +

    Description of (composite) Type T is a collection of the descriptions of all constructors that take on Type T values. This is normally written as text with each string containing the description of a single constructor. Here is a description of Type ‘IntTree’, for example:

    +

    int_tree IntTree int IntTree = IntTree; +empty_tree = IntTree;

    +
  • +
  • +

    Polymorphic type is a type whose description contains parameters (type variables) in lieu of actual types; approximately, what would be a template in C++. Here is a description of Type List alpha where List is a polymorphic type of arity 1 (i. e., dependent on a single argument), and alpha is a type variable which appears as the constructor’s optional parameter (in curly braces):

    +

    cons {alpha:Type} alpha (List alpha) = List alpha; +nil {alpha:Type} = List alpha;

    +
  • +
  • +

    Value of (composite) Type T is any sequence from A* in the format constr_num arg1 ... argN, where constr_num is the index number of some Constructor C which takes on values of Type T, and arg_i is a value of Type T_i which is the type of the i-th argument to Constructor C. For example, let Combinator int_tree have the index number 17, whereas Combinator empty_tree has the index number 239. Then, the value of Type IntTree is, for example, 17 17 239 1 239 2 239 which is more conveniently written as 'int_tree' 'int_tree' 'empty_tree' 1 'empty_tree' 2 ‘empty_tree’. From the standpoint of a high-level language, this is int_tree (int_tree (empty_tree) 1 (empty_tree)) 2 (empty_tree): IntTree.

    +
  • +
  • +

    Schema is a collection of all the (composite) data type descriptions. This is used to define some agreed-to system of types.

    +
  • +
+

Boxed and Bare Types

+
    +
  • Boxed type is a type any value of which starts with the constructor number. Since every constructor has a uniquely determined value type, the first number in any boxed type value uniquely defines its type. This guarantees that the various boxed types in totality make up a coordinated system of types. A boxed type identifier is always capitalized.
  • +
  • Bare type is a type whose values do not contain a constructor number, which is implied instead. A bare type identifier always coincides with the name of the implied constructor (and therefore, begins with a lowercase letter) which may be padded at the front by the percentage sign (%). In addition, if X is a boxed type with no more than a single constructor, then %X refers to the corresponding bare type. The values of a bare type are identical with the set of number sequences obtained by dropping the first number (i. e., the external constructor index number) from the set of values of the corresponding boxed type (which is the result type of the selected constructor), starting with the selected constructor index number. For example, 3 4 is a value of the int_couple bare type, defined using int_couple int int = IntCouple. The corresponding boxed type is IntCouple; if 404 is the constructor index number for int_couple, then 404 3 4 is the value for the IntCouple boxed type which corresponds to the value of the bare type int_couple (also known as %int_couple and %IntCouple; the latter form is conceptually preferable but longer).
  • +
+

Conceptually, only boxed types should be used everywhere. However, for speed and compactness, bare types have to be used (for instance, an array of 10,000 bare int values is 40,000 bytes long, whereas boxed Int values take up twice as much space; therefore, when transmitting a large array of integer identifiers, say, it is more efficient to use the Vector int type rather than Vector Int). In addition, all base types (int, long, double, string) are bare.

+

If a boxed type is polymorphic of type arity r, this is also true of any derived bare type. In other words, if one were to define intCouple {alpha:Type} int alpha = IntCouple alpha, then, thereafter, intCouple as an identifier would also be a polymorphic type of arity 1 in combinator (and consequently, in constructor and type) descriptions. The notations intCouple X, %(IntCouple X), and %IntCouple X are equivalent.

+

Base Types

+

Base types exist both as bare (int, long, double, string) and as boxed (Int, Long, Double, String) versions. Their constructor identifiers coincide with the names of the relevant bare types. Their pseudodescriptions have the following appearance:

+
int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+

Consequently, the int constructor index number, for example, is the CRC32 of the string "int ? = Int".

+

The values of bare type int are exactly all the single-element sequences, i. e. numbers between -2^31 and 2^31-1 represent themselves in this case. Values of type long are two-element sequences that are 64-bit signed numbers (little endian again). Values of type double, again, are two-element sequences containing 64-bit real numbers in a standard double format. And finally, the values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit numbers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

Object Pseudotype

+

The Object pseudotype is a “type” which can take on values that belong to any boxed type in the schema. This helps quickly define such types as list of random items without using polymorphic types. It is best not to abuse this capability since it results in the use of dynamic typing. Nonetheless, it is hard to imagine the data structures that we know from PHP and JSON without using the Object pseudotype.

+

It is recommended to use TypedObject instead whenever possible:

+
object X:Type value:X = TypedObject;
+

Built-In Composite Types: Vectors and Associative Arrays

+

The Vector t polymorphic pseudotype is a “type” whose value is a sequence of values of any type t, either boxed or bare.

+
vector {t:Type} # [ t ] = Vector t;
+

Serialization always uses the same constructor “vector” (const 0x1cb5c415 = crc32("vector t:Type # [ t ] = Vector t”) that is not dependent on the specific value of the variable of type t. The value of the Vector t type is the index number of the relevant constructor number followed by N, the number of elements in the vector, and then by N values of type t. The value of the optional parameter t is not involved in the serialization since it is derived from the result type (always known prior to deserialization).

+

Polymorphic pseudotypes IntHash t and StrHash t are associative arrays mapping integer and string keys to values of type t. They are, in fact, vectors containing bare 2-tuples (int, t) or (string, t):

+
coupleInt {t:Type} int t = CoupleInt t;
+intHash {t:Type} (vector %(CoupleInt t)) = IntHash t;
+coupleStr {t:Type} string t = CoupleStr t;
+strHash {t:Type} (vector %(CoupleStr t)) = StrHash t;
+

The percentage sign, in this case, means that a bare type that corresponds to the boxed type in parentheses is taken; the boxed type in question must have no more than a single constructor, whatever the values of the parameters.

+

The keys may be sorted or be in some other order (as in PHP arrays). For associative arrays with sorted keys, the IntSortedHash or StrSortedHash alias is used:

+
intSortedHash {t:Type} (intHash t) = IntSortedHash t;
+strSortedHash {t:Type} (strHash t) = StrSortedHash t;
+

Polymorphic Type Constructors

+

The constructor of a polymorphic type does not depend on the specific types to which the polymorphic type is applied. When it is computed, optional parameters (normally containing type variables and placed in curly braces) cease to be optional (the curly braces are removed), and, in addition to that, all parenthesis are also removed. Therefore,

+
vector {t:Type} # [ t ] = Vector t;
+

corresponds to the constructor number crc32("vector t:Type # [ t ] = Vector t") = 0x1cb5c415. During (de)serialization, the specific values of the optional variable t are derived from the result type (i. e. the object being serialized or deserialized) that is always known, and are never serialized explicitly.

+

Previously, it had to be known which specific variable types each polymorphic type will apply to. To accomplish this, the type system used strings of the form

+
polymorphic_type_name type_1 ... type_N;
+

For example,

+
Vector int;
+Vector string;
+Vector Object;
+

Now they are ignored.

+

See also polymorphism in TL.

+

In this case, the Object pseudotype permits using Vector Object to store lists of anything (the values of any boxed types). Since bare types are efficient when short, in practice it is unlikely that cases more complex than the ones cited above will be required.

+

Field Names

+

Let us say that we need to represent users as triplets containing one integer (user ID) and two strings (first and last names). The requisite data structure is the triplet int, string, string which may be declared as follows:

+
user int string string = User;
+

On the other hand, a group may be described by a similar triplet consisting of a group ID, its name, and description:

+
group int string string = Group;
+

For the difference between User and Group to be clear, it is convenient to assign names to some or all of the fields:

+
user id:int first_name:string last_name:string = User;
+group id:int title:string description:string = Group;
+

If the User type needs to be extended at a later time by having records with some additional field added to it, it could be accomplished as follows:

+
userv2 id:int unread_messages:int first_name:string last_name:string in_groups:vector int = User;
+

Aside from other things, this approach helps define correct mappings between fields that belong to different constructors of the same type, convert between them as well as convert type values into an associative array with string keys (field names, if defined, are natural choices for such keys).

+

TL Language

+

See TL Language

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/service_messages_about_messages.html b/data/corefork.telegram.org/mtproto/service_messages_about_messages.html new file mode 100644 index 0000000000..d271a6e13d --- /dev/null +++ b/data/corefork.telegram.org/mtproto/service_messages_about_messages.html @@ -0,0 +1,185 @@ + + + + + Service Messages about Messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Service Messages about Messages

+ +

Acknowledgment of Receipt

+

Receipt of virtually all messages (with the exception of some purely service ones as well as the plain-text messages used in the protocol for creating an authorization key) must be acknowledged. +This requires the use of the following service message (not requiring an acknowledgment):

+
msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
+

A server usually acknowledges the receipt of a message from a client (normally, an RPC query) using an RPC response. If a response is a long time coming, a server may first send a receipt acknowledgment, and somewhat later, the RPC response itself.

+

A client normally acknowledges the receipt of a message from a server (usually, an RPC response) by adding an acknowledgment to the next RPC query if it is not transmitted too late (if it is generated, say, 60-120 seconds following the receipt of a message from the server). However, if for a long period of time there is no reason to send messages to the server or if there is a large number of unacknowledged messages from the server (say, over 16), the client transmits a stand-alone acknowledgment.

+

Max 8192 IDs are allowed per constructor.

+

Notice of Ignored Error Message

+

In certain cases, a server may notify a client that its incoming message was ignored for whatever reason. Note that such a notification cannot be generated unless a message is correctly decoded by the server.

+
bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
+bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
+

Here, error_code can also take on the following values:

+
    +
  • 16: msg_id too low (most likely, client time is wrong; it would be worthwhile to synchronize it using msg_id notifications and re-send the original message with the “correct” msg_id or wrap it in a container with a new msg_id if the original message had waited too long on the client to be transmitted)
  • +
  • 17: msg_id too high (similar to the previous case, the client time has to be synchronized, and the message re-sent with the correct msg_id)
  • +
  • 18: incorrect two lower order msg_id bits (the server expects client message msg_id to be divisible by 4)
  • +
  • 19: container msg_id is the same as msg_id of a previously received message (this must never happen)
  • +
  • 20: message too old, and it cannot be verified whether the server has received a message with this msg_id or not
  • +
  • 32: msg_seqno too low (the server has already received a message with a lower msg_id but with either a higher or an equal and odd seqno)
  • +
  • 33: msg_seqno too high (similarly, there is a message with a higher msg_id but with either a lower or an equal and odd seqno)
  • +
  • 34: an even msg_seqno expected (irrelevant message), but odd received
  • +
  • 35: odd msg_seqno expected (relevant message), but even received
  • +
  • 48: incorrect server salt (in this case, the bad_server_salt response is received with the correct salt, and the message is to be re-sent with it)
  • +
  • 64: invalid container.
  • +
+

The intention is that error_code values are grouped (error_code >> 4): for example, the codes 0x40 - 0x4f correspond to errors in container decomposition.

+

Notifications of an ignored message do not require acknowledgment (i.e., are irrelevant).

+

Important: if server_salt has changed on the server or if client time is incorrect, any query will result in a notification in the above format. The client must check that it has, in fact, recently sent a message with the specified msg_id, and if that is the case, update its time correction value (the difference between the client’s and the server’s clocks) and the server salt based on msg_id and the server_salt notification, so as to use these to (re)send future messages. In the meantime, the original message (the one that caused the error message to be returned) must also be re-sent with a better msg_id and/or server_salt.

+

In addition, the client can update the server_salt value used to send messages to the server, based on the values of RPC responses or containers carrying an RPC response, provided that this RPC response is actually a match for the query sent recently. (If there is doubt, it is best not to update since there is risk of a replay attack).

+

Request for Message Status Information

+

If either party has not received information on the status of its outgoing messages for a while, it may explicitly request it from the other party:

+
msgs_state_req#da69fb52 msg_ids:Vector long = MsgsStateReq;
+

Max 8192 IDs are allowed per constructor.

+

The response to the query contains the following information:

+

Informational Message regarding Status of Messages

+
msgs_state_info#04deb57d req_msg_id:long info:string = MsgsStateInfo;
+

Here, info is a string that contains exactly one byte of message status for each message from the incoming msg_ids list:

+
    +
  • 1 = nothing is known about the message (msg_id too low, the other party may have forgotten it)
  • +
  • 2 = message not received (msg_id falls within the range of stored identifiers; however, the other party has certainly not received a message like that)
  • +
  • 3 = message not received (msg_id too high; however, the other party has certainly not received it yet)
  • +
  • 4 = message received (note that this response is also at the same time a receipt acknowledgment)
  • +
  • +8 = message already acknowledged
  • +
  • +16 = message not requiring acknowledgment
  • +
  • +32 = RPC query contained in message being processed or processing already complete
  • +
  • +64 = content-related response to message already generated
  • +
  • +128 = other party knows for a fact that message is already received
  • +
+

This response does not require an acknowledgment. It is an acknowledgment of the relevant msgs_state_req, in and of itself.

+

Note that if it turns out suddenly that the other party is missing a message that appears to have been sent to it, the message must not be re-sent on its own with the same msg_id. Instead, it can be either wrapped in a container, or the status of the message can be checked using msgs_state_req and if the message wasn't received, then it must be re-sent with a new msg_id.

+

Voluntary Communication of Status of Messages

+

Either party may voluntarily inform the other party of the status of the messages transmitted by the other party.

+
msgs_all_info#8cc0d131 msg_ids:Vector long info:string = MsgsAllInfo
+

All message codes known to this party are enumerated, with the exception of those for which the +128 and the +16 flags are set. However, if the +32 flag is set but not +64, then the message status will still be communicated.

+

This message does not require an acknowledgment.

+

Extended Voluntary Communication of Status of One Message

+

Normally used by the server to respond to the receipt of a duplicate msg_id, especially if a response to the message has already been generated and the response is large. If the response is small, the server may re-send the answer itself instead. This message can also be used as a notification instead of resending a large message.

+
msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+

The second version is used to notify of messages that were created on the server not in response to an RPC query (such as notifications of new messages) and were transmitted to the client some time ago, but not acknowledged.

+

Currently, status is always zero. This may change in future.

+

This message does not require an acknowledgment.

+

Explicit Request to Re-Send Messages

+
msg_resend_req#7d861a08 msg_ids:Vector long = MsgResendReq;
+

The remote party immediately responds by re-sending the requested messages, normally using the same connection that was used to transmit the query. If at least one message with requested msg_id does not exist or has already been forgotten, or has been sent by the requesting party (known from parity), MsgsStateInfo is returned for all messages requested as if the MsgResendReq query had been a MsgsStateReq query as well.
+Max 8192 IDs are allowed per constructor.

+

Explicit Request to Re-Send Answers

+
msg_resend_ans_req#8610baeb msg_ids:Vector long = MsgResendReq;
+

The remote party immediately responds by re-sending answers to the requested messages, normally using the same connection that was used to transmit the query. MsgsStateInfo is returned for all messages requested as if the MsgResendReq query had been a MsgsStateReq query as well.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto_v1.html b/data/corefork.telegram.org/mtproto_v1.html new file mode 100644 index 0000000000..d35544a3e8 --- /dev/null +++ b/data/corefork.telegram.org/mtproto_v1.html @@ -0,0 +1,229 @@ + + + + + MTProto Mobile Protocol v.1.0 (DEPRECATED) + + + + + + + + + + + + + +
+ +
+
+
+
+

MTProto Mobile Protocol v.1.0 (DEPRECATED)

+ +
+

This document describes MTProto v1.0, its status is DEPRECATED.
For information on encryption used in up-to-date Telegram clients, kindly see this document.

+
+

Related articles

+

+
+

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

+ +

General Description

+

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

+

The protocol is subdivided into three virtually independent components:

+
    +
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • +
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • +
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as, http, https, tcp, udp).
  • +
+ + +
+

Got questions about this setup? — Check out the Advanced FAQ!

+
+
Note 1
+

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

+
    +
  • server salt (64-Bit)
  • +
  • session id
  • +
  • message sequence number
  • +
  • message length
  • +
  • time
  • +
+
Note 2
+

See additional comments on our use of IGE, SHA-1 and message authentication.

+
Note 3
+

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

+

Brief Component Summary

+

High-Level Component (RPC Query Language/API)

+

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

+

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

+

There are several types of messages:

+
    +
  • RPC calls (client to server): calls to API methods
  • +
  • RPC responses (server to client): results of RPC calls
  • +
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • +
  • Message status query
  • +
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • +
+

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

+

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

+

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

+

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is what the OpenSSL library does.

+

Authorization and Encryption

+

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.). Multipart messages are encrypted as a single message.

+

For a technical specification, see Mobile Protocol: Detailed Description
The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

+

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

+
    +
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • +
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • +
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to those data.
  • +
+

Time Synchronization

+

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

+

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

+

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

+

Transport

+

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. There are three types of transport:

+
    +
  • HTTP
  • +
  • TCP
  • +
  • UDP
  • +
+

We shall examine the first two types.

+

HTTP Transport

+

Implemented over HTTP/1.1 (with keepalive) running over the traditional TCP Port 80. HTTPS is not used; the above encryption method is used instead.

+

An HTTP connection is attached to a session (or rather, to session + key identifier) specified in the most recent user query received; normally, the session is the same in all queries, but crafty HTTP proxies may corrupt that. A server may not return a message into an HTTP connection unless it belongs to the same session, and unless it is the server’s turn (an HTTP request had been received from the client to which a response has not been sent yet).

+

The overall arrangement is as follows. The client opens one or more keepalive HTTP connections to the server. If one or more messages need to be sent, they are made into a payload which is followed by a POST request to the URL/api to which the payload is transmitted as data. In addition, Content-Length, Keepalive, and Host are valid HTTP headers.

+

Having received the query, the server may either wait a little while (if the query requires a response following a short timeout) or immediately return a dummy response (only acknowledging the receipt of the container). In any case, the response may contain any number of messages. The server may at the same time send out any other messages it might be holding for the session.

+

In addition, there exists a special long poll RPC query (valid for HTTP connections only) which transmits maximum timeout T. If the server has messages for the session, they are returned immediately; otherwise, a wait state is entered until such time as the server has a message for the client or T seconds have elapsed. If no events occur in the span of T seconds, a dummy response is returned (special message).

+

If a server needs to send a message to a client, it checks for an HTTP connection that belongs to the required session and is in the “answering an HTTP request” state (including long poll) whereupon the message is added to the response container for the connection and sent to the user. In a typical case, there is some additional wait time (50 milliseconds) against the eventuality that the server will soon have more messages for the session.

+

If no suitable HTTP connection is available, the messages are placed in the current session’s send queue. However, they find their way there anyway until receipt is explicitly or indirectly confirmed by the client. For the HTTP protocol, sending the next query into the same HTTP connection is regarded as an implicit acknowledgment (not any more, the HTTP protocol also requires that explicit acknowledgments be sent); in other cases, the client must return an explicit acknowledgment within a reasonable time (it can be added to a container for the following request).

+

Important: if the acknowledgment fails to arrive on time, the message can be resent (possibly, in a different container). The parties must autonomously be ready for this and must store the identifiers of the most recent messages received (and ignore such duplicates rather than repeat actions). In order not to have the identifiers stored forever, there exist special garbage collection messages that take advantage of message identifier monotonicity.

+

If the send queue overflows or if messages stay in the queue for over 10 minutes, the server forgets them (or sends them to swap, no genius required). This may happen even faster, if the server is running out of buffer space (for example, because of serious network issues resulting in a large number of connections becoming severed).

+

TCP Transport

+

This is very similar to the HTTP transport. May also be implemented over Port 80 (to penetrate all firewalls) and even use the same server IP addresses. In this situation, the server understands whether HTTP or TCP protocol must be used for the connection, based on the first four incoming bytes (for HTTP, it is POST).

+

When a TCP connection is created, it is assigned to the session (and the authorization key) transmitted in the first user message, and subsequently used exclusively for this session (multiplexing arrangements are not allowed).

+

If a payload (packet) needs to be transmitted from server to client or from client to server, it is encapsulated as follows: 4 length bytes are added at the front (to include the length, the sequence number, and CRC32; always divisible by 4) and 4 bytes with the packet sequence number within this TCP connection (the first packet sent is numbered 0, the next one 1, etc.), and 4 CRC32 bytes at the end (length, sequence number, and payload together).

+

There is an abridged version of the same protocol: if the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01..0x7e = data length divided by 4; or 0x7f followed by 3 length bytes (little endian) divided by 4) followed by the data themselves (sequence number and CRC32 not added). In this case, server responses look the same (the server does not send 0xefas the first byte).

+

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used: if the client sends 0xeeeeeeee as the first int (four bytes), then packet length is encoded always by four bytes as in the original version, but the sequence number and CRC32 are omitted, thus decreasing total packet size by 8 bytes.

+

The full, the intermediate and the abridged versions of the protocol have support for quick acknowledgment. In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet. They are the 32 higher-order SHA1 bits of the encrypted portion of the packet with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

+

There are no implicit acknowledgments for the TCP transport: all messages must be acknowledged explicitly. Most frequently, acknowledgments are placed in a container with the next query or response if it is transmitted in short order. For example, this is almost always the case for client messages containing RPC queries: the acknowledgment normally arrives with the RPC response.

+

In the event of an error, the server may send a packet whose payload consists of 4 bytes as the error code. For example, Error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/passport.html b/data/corefork.telegram.org/passport.html new file mode 100644 index 0000000000..ffcc341cc7 --- /dev/null +++ b/data/corefork.telegram.org/passport.html @@ -0,0 +1,690 @@ + + + + + Telegram Passport Manual + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram Passport Manual

+ +
+ +

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn't have access to the users' personal information thanks to end-to-end encryption.

+

Overview

+

From the perspective of a service that requires real-world ID, the process looks like this:

+
    +
  • A user presses "Log in with Telegram" on your website or in your app.
  • +
  • You request the data you need.
  • +
  • The user accepts your privacy policy and agrees to share their data.
  • +
  • The user's Telegram app downloads and decrypts the data you requested from the end-to-end encrypted storage on Telegram.
  • +
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • +
  • The user's app encrypts the data with your public key and sends it to you.
  • +
  • You decrypt the data, check it for errors and re-request any missing or invalid information.
  • +
  • You sign the user up for your service. Tada!
  • +
+

Check out this example to see Telegram Passport in action.

+
+

To learn more about Telegram Passport from the perspective of a user, please see this blog post and the technical MTProto documentation. +See this page if you're interested in encryption algorithms used on Telegram's side.

+
+

Recent changes

+

August 25, 2018

+

Telegram Passport 1.1 (blog post)

+
    +
  • Added support for requesting several documents of one type. See the new objects PassportScope, PassportScopeElement, PassportScopeElementOneOfSeveral and PassportScopeElementOne.
  • +
  • Added support for middle names.
  • +
  • Added support for requesting certified English translations for documents (see Fields; new field translation also added to the SecureValue object). Note: Please only request translations after you have received a valid document that requires one.
  • +
  • Added support for requesting names in the language of the user's country of residence (if other than English). New fields first_name_native, last_name_native and middle_name_native added to the PersonalDetails object.
  • +
  • Replaced the payload parameter with the new parameter nonce, which serves the same function, to make the purpose more obvious (see Request Parameters and the Credentials object).
  • +
  • Updated the example page to support the new functionality.
  • +
+

Setting Up Telegram Passport

+

To integrate Telegram Passport into your login or verification flow, you need a working Telegram bot (see this page for information on how to get one).

+

To request data from Telegram Passport users, your bot will need to generate a pair of encryption keys.

+

Generating a private key

+

First, use a console to generate a private key:

+
openssl genrsa 2048 > private.key
+

WARNING: Keep your private key SECRET!

+

Generating your public key

+

Then use the console to print the corresponding public key:

+
openssl rsa -in private.key -pubout
+

Use the /setpublickey command with @BotFather to connect this public key with your bot.

+

Privacy Policy

+

Add a link to your Privacy Policy by using the /setprivacypolicy command. Users will see this link when offered to authorize you to access their data.

+

Requesting Information

+

SDK

+

To request information stored in a Telegram Passport, use one of these SDKs:

+ +

Request Parameters

+

Use the following parameters to request information with the SDK:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParametersTypeRequired
bot_idIntegerYes
scopePassportScopeYes
public_keyStringYes
nonceStringYes
+

PassportScope

+

This object represents the data to be requested.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dataArray of PassportScopeElementList of requested elements, each type may be used only once in the entire array of PassportScopeElement objects
vIntegerScope version, must be 1
+

PassportScopeElement

+

This object represents a requested element, should be one of:

+ +

PassportScopeElementOneOfSeveral

+

This object represents several elements one of which must be provided.

+ + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
one_ofArray of PassportScopeElementOneList of elements one of which must be provided; must contain either several of “passport”, “driver_license”, “identity_card”, “internal_passport” or several of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
translationBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
+

PassportScopeElementOne

+

This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typeStringElement type. One of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration", "phone_number", "email"
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "passport", "driver_license", "identity_card" and "internal_passport"
translationBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration". Note: We suggest to only request translations after you have received a valid document that requires one.
native_namesBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "personal_details"
+

You can also use the special type "id_document" as an alias for one of "passport", "driver_license", "identity_card" and the special type "address_document" as an alias for one of "utility_bill", "bank_statement", "rental_agreement". +So {"type":"id_document",selfie:true} is equal to {"one_of":["passport","driver_license","identity_card"],selfie:true}.

+

Fields

+

Your bot can request personal details, one or several types of identity document, residential address, one or several types of proof of address document, a phone number, or an email address. You can also request optional selfies with the document and certified English translations of the document. +This is just a list of data types that can be requested, and the encrypted objects that will contain such data.

+
+

Note: We suggest to only request English translations after you have received a valid document that requires one.

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameKeyTypeDescription
personal_detailsdataPersonalDetailsPersonal Details
passportdataIdDocumentDataPassport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
internal_passportdataIdDocumentDataInternal Passport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
driver_licensedataIdDocumentDataDriver License
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
identity_carddataIdDocumentDataIdentity Card
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
addressdataResidentialAddressAddress
utility_billfilesArray of PassportFileUtility Bill
translationOptional. Array of PassportFile
bank_statementfilesArray of PassportFileBank Statement
translationOptional. Array of PassportFile
rental_agreementfilesArray of PassportFileRental Agreement
translationOptional. Array of PassportFile
passport_registrationfilesArray of PassportFileRegistration Page in the Internal Passport
translationOptional. Array of PassportFile
temporary_registrationfilesArray of PassportFileTemporary Registration
translationOptional. Array of PassportFile
phone_numberStringPhone number
emailStringEmail
+

PersonalDetails

+

This object represents personal details.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
first_nameStringFirst Name
last_nameStringLast Name
middle_nameStringOptional. Middle Name
birth_dateStringDate of birth in DD.MM.YYYY format
genderStringGender, male or female
country_codeStringCitizenship (ISO 3166-1 alpha-2 country code)
residence_country_codeStringCountry of residence (ISO 3166-1 alpha-2 country code)
first_name_nativeStringFirst Name in the language of the user's country of residence
last_name_nativeStringLast Name in the language of the user's country of residence
middle_name_nativeStringOptional. Middle Name in the language of the user's country of residence
+

ResidentialAddress

+

This object represents a residential address.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
street_line1StringFirst line for the address
street_line2StringOptional. Second line for the address
cityStringCity
stateStringOptional. State
country_codeStringISO 3166-1 alpha-2 country code
post_codeStringAddress post code
+

IdDocumentData

+

This object represents the data of an identity document.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
document_noStringDocument number
expiry_dateStringOptional. Date of expiry, in DD.MM.YYYY format
+

PassportFile

+

This object represents a PassportFile related to a document. The file is up to 10MB in size and in the .jpg format.

+

Receiving information

+

When the user confirms your request by pressing the 'Authorize' button, the Bot API sends an Update with the field passport_data to the bot that contains encrypted Telegram Passport data.

+
+

Note that all base64-encoded fields should be decoded before use.

+
+

Decrypting data

+

To decrypt the received data, first, decrypt the credentials contained in EncryptedCredentials.

+
    +
  1. +

    Decrypt the credentials secret ( secret field in EncryptedCredentials) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)

    +
  2. +
  3. +

    Use this secret and the credentials hash ( hash field in EncryptedCredentials) to calculate credentials_key and credentials_iv as described below:

    +
     credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    + credentials_key = slice( credentials_secret_hash, 0, 32 )
    + credentials_iv = slice( credentials_secret_hash, 32, 16 )
    +
  4. +
  5. +

    Decrypt the credentials data ( data field in EncryptedCredentials) by AES256-CBC using these credentials_key and credentials_iv. IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )

    +
  6. +
  7. +

    Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.

    +
  8. +
+
+

Note that all hashes represent as raw binary data, not hexits

+
+

Credentials

+

Credentials is a JSON-serialized object.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
secure_dataSecureDataCredentials for encrypted data
nonceStringBot-specified nonce
+

IMPORTANT: Make sure that the nonce is the same as was passed in the request.

+

SecureData

+

This object represents the credentials required to decrypt encrypted data. All fields are optional and depend on fields that were requested.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
personal_detailsSecureValueOptional. Credentials for encrypted personal details
passportSecureValueOptional. Credentials for encrypted passport
internal_passportSecureValueOptional. Credentials for encrypted internal passport
driver_licenseSecureValueOptional. Credentials for encrypted driver license
identity_cardSecureValueOptional. Credentials for encrypted ID card
addressSecureValueOptional. Credentials for encrypted residential address
utility_billSecureValueOptional. Credentials for encrypted utility bill
bank_statementSecureValueOptional. Credentials for encrypted bank statement
rental_agreementSecureValueOptional. Credentials for encrypted rental agreement
passport_registrationSecureValueOptional. Credentials for encrypted registration from internal passport
temporary_registrationSecureValueOptional. Credentials for encrypted temporary registration
+

SecureValue

+

This object represents the credentials required to decrypt encrypted values. All fields are optional and depend on the type of fields that were requested.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dataDataCredentialsOptional. Credentials for encrypted Telegram Passport data. Available for "personal_details", "passport", "driver_license", "identity_card", "internal_passport" and "address" types.
front_sideFileCredentialsOptional. Credentials for an encrypted document's front side. Available for "passport", "driver_license", "identity_card" and "internal_passport".
reverse_sideFileCredentialsOptional. Credentials for an encrypted document's reverse side. Available for "driver_license" and "identity_card".
selfieFileCredentialsOptional. Credentials for an encrypted selfie of the user with a document. Available for "passport", "driver_license", "identity_card" and "internal_passport".
translationArray of FileCredentialsOptional. Credentials for an encrypted translation of the document. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration".
filesArray of FileCredentialsOptional. Credentials for encrypted files. Available for "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types.
+

DataCredentials

+

These credentials can be used to decrypt encrypted data from the data field in EncryptedPassportElement.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
data_hashStringChecksum of encrypted data
secretStringSecret of encrypted data
+
    +
  1. +

    To decrypt data, use the corresponding secret and data_hash from DataCredentials as described below:

    +
     data_secret_hash = SHA512( data_secret + data_hash )
    + data_key = slice( data_secret_hash, 0, 32 )
    + data_iv = slice( data_secret_hash, 32, 16 )
    +
  2. +
  3. +

    Use AES256-CBC with this data_key and data_iv to decrypt the data (the data field in EncryptedPassportElement). IMPORTANT: At this step, make sure that data_hash from the credentials is equal to SHA256( data ).

    +
  4. +
  5. +

    The data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of the padding (including this byte). Remove padding to get the data.

    +
  6. +
  7. +

    The data is a JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on type.

    +
  8. +
+

FileCredentials

+

These credentials can be used to decrypt encrypted files from the front_side, reverse_side, selfie, files and translation fields in EncryptedPassportElement.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
file_hashStringChecksum of encrypted file
secretStringSecret of encrypted file
+
    +
  1. +

    To decrypt the file, use the corresponding secret and file_hash from FileCredentials as described below:

    +
     file_secret_hash = SHA512( file_secret + file_hash )
    + file_key = slice( file_secret_hash, 0, 32 )
    + file_iv = slice( file_secret_hash, 32, 16 )
    +
  2. +
  3. +

    Download the encrypted file using the getFile method.

    +
  4. +
  5. +

    Use AES256-CBC with this file_key and file_iv to decrypt the content of the file. IMPORTANT: At this step, make sure that file_hash from the credentials is equal to SHA256( file_content ).

    +
  6. +
  7. +

    The content of the file is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of the padding (including that byte). Remove padding to get the file content.

    +
  8. +
+

Fixing errors

+

If the data you received contains errors, the bot can use the setPassportDataErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/passport/encryption.html b/data/corefork.telegram.org/passport/encryption.html new file mode 100644 index 0000000000..8aed498b38 --- /dev/null +++ b/data/corefork.telegram.org/passport/encryption.html @@ -0,0 +1,606 @@ + + + + + Telegram Passport Encryption Details + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram Passport Encryption Details

+ +
+ +

Telegram Passport data is stored encrypted End-to-End which means that the Telegram server does not have access to the data and only functions as a storage for encrypted data it can't decipher. Encryption and decryption are handled exclusively by the Telegram clients, which are open source.

+

Overview

+

To encrypt each particular element of Telegram Passport, the client generates a random secret. The secret is a 32-byte number with the modulo 255 sum of bytes equal to 239. This secret is in turn encrypted with the passport_secret that is generated when the user creates their Telegram Passport. passport_secret is encrypted with the user's password and is stored encrypted in the Telegram Cloud.

+

Passport Secret

+

The passport secret is one of the secret parameters used to encrypt the data uploaded by the user to the Telegram Cloud.

+

When first setting up Telegram Passport it must be created, encrypted and uploaded as described in Passport Secret Encryption.

+

When using Telegram Passport normally, it must be downloaded and decrypted for use as described in Passport Secret Decryption.

+

The passport secret must also be downloaded, re-encrypted and re-uploaded as described in Passport Secret Encryption if a new, more secure encryption algorithm is defined in a newer version of Telegram or the 2FA password is updated.

+

Passport Secret Encryption

+

First of all, server-side passport parameters are fetched, schema:

+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+
+securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+
+---functions---
+
+account.getPassword#548a30f5 = account.Password;
+

When Telegram Passport is first used, the client generates a passport_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239), using a part of server-generated random secure_random from account.password as an additional source of entropy for OpenSSL (when re-encrypting the passport_secret with a more secure algorithm or after a 2FA password change, the previous passport_secret is used, instead). +Then passport_secret is then encrypted using the user's password and hashed using the schema and parameters specified in the new_algo field of account.password.

+

The server should always return a securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 constructor in the new_algo field. +If securePasswordKdfAlgoUnknown is returned, the remotely stored secret is encrypted using a new algorithm, not supported by the current client: the user should update their app.

+

The other constructors may be used only when decrypting old passport parameters generated by a legacy client; in this case, the passport secret should be re-encrypted and updated using new_algo.

+ +

Subsequently, the client receives the encrypted passport_secret from the server and decrypts it after the user enters their password ».

+

In case the password is changed or a more secure algorithm is introduced in an update of the API, the client re-encrypts the passport_secret using the new password. +If the password is disabled, all Telegram Passport data is lost.

+

Passport Secret Decryption

+

Schema:

+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
+
+account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
+---functions---
+
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
+

The client requests the user's 2FA password and generates the SRP paramaters to be passed to account.getPasswordSettings.

+

If the password is correct, an account.passwordSettings constructor with secureSecretSettings is returned.

+

encrypted_passport_secret, passport_secret_fingerprint parameters are extracted from the secureSecretSettings constructor:

+
encrypted_passport_secret = secureSecretSettings.secure_secret
+passport_secret_fingerprint = secureSecretSettings.secure_id
+

The combined passport_secret_salt is extracted from the SecurePasswordKdfAlgo.

+
passport_secret_salt = SecurePasswordKdfAlgo.salt
+

Similar to passport secret encryption, the following process is used to decrypt and verify the encrypted_passport_secret:

+
    +
  • +

    The user's 2FA plaintext password is hashed using the specified algorithm.

    + +
  • +
  • +

    The secret_key and iv parameters are extracted from the generated password_hash

    +
    secret_key = slice( password_hash, 0, 32 )
    +iv = slice( password_hash, 32, 16 )
    +
  • +
  • +

    The encrypted_passport_secret is decrypted using AES256-CBC with the key secret_key and iv:

    +
    passport_secret = AES256_CBC_DEC(encrypted_passport_secret, secret_key, iv)
    +
  • +
  • +

    The passport_secret is verified by generating and checking the fingerprint:

    +
    my_passport_secret_fingerprint = long( slice( SHA256( passport_secret ), 0, 8 ) )
    +

    The client must verify that passport_secret_fingerprint is indeed equal to my_passport_secret_fingerprint.

    +
  • +
+

The passport_secret can now be used to decrypt encrypted passport data stored on telegram servers:

+

Data and File Encryption

+

Encryption

+

To encrypt Telegram Passport data, the client generates a data_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). The the data is encrypted according to the following scheme:

+ +

Packing

+
SecureData
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
    +
  • data is an encrypted and padded (see Encryption) JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on the chosen type. +Data must be in JSON format and not TL, as it has to be passed directly to the service using E2E encryption, without the bot API middleman to convert TL objects.
  • +
  • data_hash is the data_hash
  • +
  • secret is the encrypted_data_secret
  • +
+

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
+
InputSecureFile
+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+---functions---
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+

Files (JPG format, max. 10MB) are encrypted and padded (see Encryption), and then uploaded chunk by chunk as described in files », except that instead of generating an inputFile, an inputSecureFile should be generated, instead.

+
    +
  • As for secret chat files, the md5_checksum is to be set to the MD5 hash of the encrypted file, for a server-side integrity check.
  • +
  • The file_hash field should be set to the data_hash of the data.
  • +
  • The secret field is the encrypted_data_secret.
  • +
+
SecurePlainData
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+---functions---
+
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;
+account.verifyEmail#ecba39db email:string code:string = Bool;
+
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
+

The email/phone is passed in plaintext using the respective SecurePlainData constructor. +To verify a phone number or email and use it in Telegram Passport, use the appropriate methods:

+ +

The flow is similar to the one used for logging in:

+
    +
  • Send email/phone code using the appropriate account.sendVerify*Code method
  • +
  • Pass the received code to the appropriate account.verify* method
  • +
  • Only for phone code verification, you can also resend/cancel the phone code using auth.resendCode/auth.cancelCode, as for logging in.
  • +
+

For more info, see the authorization docs.

+

When to use each constructor.

+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;
+
+securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
+inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
+

The schema for the inputSecureValue constructor defines the constructor to use for each field.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
+

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
+

Fetching and deleting stored passport data

+
---functions---
+
+account.getAllSecureValues#b288bc7d = Vector<SecureValue>;
+account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
+

The above methods can be used to fetch or remove encrypted Telegram Passport files stored in the Telegram Cloud by document type.

+

Passport Credentials

+

When a service requests data, it passes a nonce to the client. The nonce is a cryptographically secure unique identifier which allows the service to identify a request when receiving data as well as confirm the integrity of the data. The Telegram server doesn't have access to this nonce.

+

Once the user authorizes the Telegram Passport data transfer, the client forms the credentials (Credentials JSON object). Credentials contain the data_hash and data_secret from each element of Telegram Passport to which the user has allowed access. In addition to this, the credentials will always contain the nonce that the client received from the service at the initiation of the request.

+

Credentials are then passed to the service through the Bot API in encrypted form. To encrypt the credentials, the client generates a credentials_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). Then the credentials are encrypted according to the following scheme:

+
    +
  • +

    Credentials are padded to a length which is divisible by 16 bytes. To achieve this, 32 to 255 bytes are added at the beginning, where the first byte always holds the number of added bytes and the rest are random.

    +
  • +
  • +

    A hash of the padded credentials credentials_hash is calculated:

    +
    credentials_hash = SHA256( credentials )
    +
  • +
  • +

    The encryption key credentials_key is calculated:

    +
    credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    +credentials_key = slice( credentials_secret_hash, 0, 32 )
    +iv = slice( credentials_secret_hash, 32, 16 )
    +
  • +
  • +

    Credentials are encrypted using AES256-CBC with the key credentials_key and iv.

    +
    encrypted_credentials = AES256-CBC-ENC(credentials, credentials_key, iv)
    +
  • +
  • +

    credentials_secret is encrypted with the public RSA-key of the service with OPENSSL_PKCS1_OAEP_PADDING.

    +
    encrypted_credentials_secret = RSA-ENC(credentials_secret, key, OPENSSL_PKCS1_OAEP_PADDING)
    +
  • +
  • +

    The encrypted credentials are passed to the service via the MTProto API together with the encrypred credentials_secret and credentials_hash. Along with the credentials, the service receives from the Telegram Cloud the data it requested in encrypted form. See Submitting the Passport Form and PassportData:

    +
    secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
    +
  • +
  • +

    data is the encrypted_credentials

    +
  • +
  • +

    hash is the credentials_hash

    +
  • +
  • +

    secret is the encrypted_credentials_secret

    +
  • +
+

Then the service decrypts the data as described here.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/passport/example.html b/data/corefork.telegram.org/passport/example.html new file mode 100644 index 0000000000..fbfa48d49e --- /dev/null +++ b/data/corefork.telegram.org/passport/example.html @@ -0,0 +1,585 @@ + + + + + Example + + + + + + + + + + + + + + + +
+ +
+
+
+
+

Example

+ +

If you'd like to test Telegram Passport, use this page to request data. If you'd like to check out a real-life implementation, please see this blog post for examples of services that have integrated Telegram Passport.

+

Request Telegram Passport Data

+

+

+
+
+
+ + +
+
+
+
+ +
+ +
+ +
+
+ +
+
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ + +
+
+
+
+ +
+ +
+ +
+ +
+
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ + +
+
+
+
+ +
+ +
+ +
+
+ +
+
+ +
+
+ + +
+
+
+ +

+
+
+

Note that the passport demo bot will only store data for 1 hour and then discard it. After logging in here, you can use the logout button on this page to reset your session.

+
+ +
+ +
+
+ +
+ + + + + + + + + diff --git a/data/corefork.telegram.org/passport/sdk-android.html b/data/corefork.telegram.org/passport/sdk-android.html new file mode 100644 index 0000000000..9784921198 --- /dev/null +++ b/data/corefork.telegram.org/passport/sdk-android.html @@ -0,0 +1,180 @@ + + + + + Android SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

Android SDK

+ +
+ +

The Android SDK helps you easily integrate Telegram Passport requests into your Android-based apps. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Installing from Maven

+

Telegram Passport SDK is available from the Maven repository. +Add this line to the dependencies section in your build.gradle:

+
compile 'org.telegram:passport:1.1'
+

and sync your project.

+

Adding as a module

+

Download the library, unzip it and copy the library project to the root of your project directory (the one with settings.gradle and gradle.properties). Then, make the following changes to your Gradle scripts.

+

In settings.gradle, add ':telegrampassport' to includes:

+
include ':app', ':telegrampassport'
+

In the build.gradle file for your app, add this line to the dependencies section:

+
compile ':telegrampassport'
+

and sync your project.

+

Usage

+

Adding the button

+

The SDK provides the "Log in with Telegram" button which we recommend using for a consistent user experience across different apps. You can either add it from your Java code:

+
TelegramLoginButton telegramButton;
+// ...
+telegramButton=new TelegramLoginButton(this);
+// Optionally you can change the roundness of the button corners
+// to better fit your design.
+telegramButton.setCornerRoundness(1f);
+viewGroupOfSomeSort.addView(telegramButton, ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT);
+

Or from XML:

+
 <org.telegram.passport.TelegramLoginButton
+             android:layout_width="wrap_content"
+             android:layout_height="wrap_content"
+             app:cornerRoundness="0.5"/>
+

Requesting authorization

+

The button doesn't do anything by itself; you need to set an OnClickListener on it to start the authorization flow (replace the comments with actual parameters):

+
private static final int TG_PASSPORT_RESULT=352; // this can be any integer less than 0xFFFF
+// ...
+telegramButton.setOnClickListener(new View.OnClickListener(){
+@Override
+public void onClick(View view){
+    TelegramPassport.AuthRequest req=new TelegramPassport.AuthRequest();
+    req.botID=/* your bot ID here */;
+    req.publicKey=/* your bot public key here */;
+    req.nonce=/* a unique nonce to pass to the bot server */;
+    // Request either a passport or an ID card with selfie, a driver license, personal details with
+    // name as it appears in the documents, address with any address document, and a phone number.
+    // You could also pass a raw JSON object here if that's what works better for you
+    // (for example, if you already get it from your server in the correct format).
+    req.scope=new PassportScope(
+        new PassportScopeElementOneOfSeveral(PassportScope.PASSPORT, PassportScope.IDENTITY_CARD).withSelfie(),
+        new PassportScopeElementOne(PassportScope.PERSONAL_DETAILS).withNativeNames(),
+        PassportScope.DRIVER_LICENSE,
+        PassportScope.ADDRESS,
+        PassportScope.ADDRESS_DOCUMENT,
+        PassportScope.PHONE_NUMBER
+    );
+    TelegramPassport.request(MyActivity.this, req, TG_PASSPORT_RESULT);
+}});
+

If you need more control over the process, the TelegramPassport class contains several more methods:

+
    +
  • getAuthIntent(AuthParams) returns an Intent for you to use in startActivityForResult if you need to do that in some special way. Be sure to check that an app is present that can handle this intent before starting it by using PackageManager or intent.resolveActivity.
  • +
  • showAppInstallAlert(Activity) shows an alert that the user needs to install Telegram in order to continue. This is intended to be used together with the previous method for the cases when the app isn't installed.
  • +
+

Handling the result

+

The result is delivered via the onActivityResult method in your activity with the request code you passed to TelegramPassport.request. Currently, the only meaningful parameter is resultCode, which is RESULT_OK if the authorization was successful and RESULT_CANCELED otherwise.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/passport/sdk-ios-mac.html b/data/corefork.telegram.org/passport/sdk-ios-mac.html new file mode 100644 index 0000000000..ce9fca8125 --- /dev/null +++ b/data/corefork.telegram.org/passport/sdk-ios-mac.html @@ -0,0 +1,246 @@ + + + + + iOS & macOS SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

iOS & macOS SDK

+ +
+ +

TGPassportKit helps you easily integrate Telegram Passport requests into your iOS & macOS apps. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Installing using Cocoapods

+

To install TGPassportKit via Cocoapods add the following to your Podfile:

+
target 'MyApp' do
+  pod 'TGPassportKit' 
+end
+

then run pod install in your project root directory.

+

Installing using Carthage

+

Add the following line to your Cartfile:

+
github "telegrammessenger/TGPassportKit"
+

then run carthage update, and you will get the latest version of TGPassportKit in your Carthage folder.

+

Project Setup

+

Configure Your Info.plist

+

Configure your Info.plist by right-clicking it in Project Navigator, choosing Open As > Source Code and adding this snippet: +Replace {bot_id} with your value

+
<key>CFBundleURLTypes</key>
+<array>
+  <dict>
+  <key>CFBundleURLSchemes</key>
+  <array>
+    <string>tgbot{bot_id}</string>
+  </array>
+  </dict>
+</array>
+<key>LSApplicationQueriesSchemes</key>
+<array>
+  <string>tg</string>
+</array>
+

Connect AppDelegate methods

+

Add this code to your UIApplicationDelegate implementation

+
#import <TGPassportKit/TGPAppDelegate.h>
+
+- (BOOL)application:(UIApplication *)application
+            openURL:(NSURL *)url
+            options:(NSDictionary<UIApplicationOpenURLOptionsKey, id> *)options {
+    BOOL handledByPassportKit = [[TGPAppDelegate sharedDelegate] application:application
+                                                                     openURL:url
+                                                                     options:options];
+
+    return YES;
+}
+

If you support iOS 9 and below, also add this method:

+
- (BOOL)application:(UIApplication *)application 
+            openURL:(NSURL *)url 
+  sourceApplication:(nullable NSString *)sourceApplication 
+         annotation:(id)annotation {
+    BOOL handledByPassportKit = [[TGPAppDelegate sharedDelegate] application:application
+                                                                     openURL:url
+                                                           sourceApplication:sourceApplication
+                                                                  annotation:annotation];
+
+    return YES;
+}
+

Usage

+

Add Telegram Passport Button

+

To add the Telegram Passport button, add the following code to your view controller: +Replace {bot_id}, {bot_public_key} and {request_nonce} with your values

+
#import <TGPassportKit/TGPButton.h>
+
+@interface ViewController <TGPButtonDelegate>
+
+@end
+
+@implementation ViewController
+
+- (void)viewDidLoad {
+  [super viewDidLoad];
+
+  TGPButton *button = [[TGPButton alloc] init];
+  button.botConfig = [[TGPBotConfig alloc] initWithBotId:{bot_id} 
+                                               publicKey:@"{bot_public_key}"];
+  button.scope = [[TGPScope alloc] initWithJSONString:@"{\"data\":[\"id_document\",\"address_document\",\"phone_number\"],\"v\":1}"];
+// You can also construct a scope using provided data type classes like this: 
+// button.scope = [[TGPScope alloc] initWithTypes:@[[[TGPPersonalDetails alloc] init], [[TGPIdentityDocument alloc] initWithType:TGPIdentityDocumentTypePassport selfie:true translation:true]]];
+  button.nonce = @"{request_nonce}";
+  button.delegate = self;
+  [self.view addSubview:button];
+}
+
+- (void)passportButton:(TGPButton *)passportButton 
+ didCompleteWithResult:(TGPRequestResult)result 
+                 error:(NSError *)error {
+    switch (result) {
+        case TGPRequestResultSucceed:
+            NSLog(@"Succeed");
+            break;
+
+        case TGPRequestResultCancelled:
+            NSLog(@"Cancelled");
+            break;
+
+        default:
+            NSLog(@"Failed");
+            break;
+    }
+}
+
+@end
+

...or Implement Your Own Behavior

+

If you want to design a custom UI and behavior, you can invoke a Passport request like this: +Replace {bot_id}, {bot_public_key} and {request_nonce} with your values

+
#import <TGPassportKit/TGPRequest.h>
+
+- (void)performPassportRequest 
+{
+    TGPBotConfig *botConfig = [[TGPBotConfig alloc] initWithBotId:{bot_id} 
+                                                        publicKey:@"{bot_public_key}"];
+    TGPRequest *request = [[TGPRequest alloc] initWithBotConfig:botConfig];
+    [request performWithScope:[[TGPScope alloc] initWithJSONString:@"{\"data\":[\"id_document\",\"phone_number\"],\"v\":1}"] 
+                      payload:@"{request_nonce}" 
+            completionHandler:^(TGPRequestResult result, NSError * _Nullable error) {
+        switch (result) {
+            case TGPRequestResultSucceed:
+                NSLog(@"Succeed");
+                break;
+
+            case TGPRequestResultCancelled:
+                NSLog(@"Cancelled");
+                break;
+
+            default:
+                NSLog(@"Failed");
+                break;
+        }
+    }];
+}
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/passport/sdk-javascript.html b/data/corefork.telegram.org/passport/sdk-javascript.html new file mode 100644 index 0000000000..4a9ea10099 --- /dev/null +++ b/data/corefork.telegram.org/passport/sdk-javascript.html @@ -0,0 +1,258 @@ + + + + + Javascript SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

Javascript SDK

+ +
+ +

The Javascript SDK helps you easily integrate Telegram Passport requests into your website. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Download and include the Javascript SDK in the head section of your page:

+
<script src="telegram-passport.js"></script>
+

Usage

+

Simply call Telegram.Passport.createAuthButton to create the default Telegram Passport button:

+
<div id="telegram_passport_auth"></div>
+<script>
+  Telegram.Passport.createAuthButton('telegram_passport_auth', {
+    bot_id:       123456, // place id of your bot here
+    scope:        {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
+    public_key:   '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
+    nonce:        'ab2df83746a87d2f3bd6...', // place nonce here
+    callback_url: 'https://example.com/callback/' // place callback url here
+  });
+</script>
+
+

Note that if you use a Content-Security-Policy (CSP) header with the frame-src/child-src directive you should allow tg: source to prevent errors in some browsers (e.g. Firefox)

+
+

createAuthButton

+ + + + + + + + + + + + + + + + + + + + + + + +
ParametersTypeRequired
elementString or DOMNodeYes
auth_paramsAuthParameters or FunctionYes
optionsAuthButtonOptionsOptional
+

AuthParameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
bot_idIntegerUnique identifier for the bot
scopePassportScopeA JSON-serialized object describing the data you want to request
public_keyStringPublic key of your bot
nonceStringBot-specified nonce
callback_urlStringOptional. URL to which the user will be redirected.
+

AuthButtonOptions

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringOptional. Text on the button. Defaults to "Log In With Telegram".
radiusIntegerOptional. Radius of the button and tooltip in px. Defaults to 23.
tooltip_textStringOptional. Text on the tooltip. Defaults to "Please install Telegram to use this option.".
tooltip_positionStringOptional. Tooltip position. One of "top", "bottom", "left", "right". Defaults to "bottom".
tooltip_forceBooleanOptional. Always show a tooltip. Defaults to false.
+

You can also create your custom button. Do not forget about the tooltip. You should add an onclick listener to the button which calls the Telegram.Passport.auth(auth_params, tooltip_toggle); method:

+
<button id="telegram_passport_auth">Log In With Telegram</button>
+<script>
+  var auth_button = document.getElementById('telegram_passport_auth');
+  var auth_params = {
+    bot_id:        XXXXXX, // place id of your bot here
+    scope:         {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
+    public_key:    '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
+    nonce:         'ab2df83746a87d2f3bd6...', // place nonce here
+    callback_url:  'https://example.com/callback/' // place callback url here
+  };
+  auth_button.addEventListener('click', function() {
+    Telegram.Passport.auth(auth_params, function(show) {
+      if (show) {
+        // some code to show tooltip
+      } else {
+        // some code to hide tooltip
+      }
+    });
+  }, false);
+</script>
+

Receiving information

+

When the user confirms your request by pressing the 'Authorize' button, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=success and the Bot API will send the bot an Update with the field passport_data which contains encrypted Telegram Passport data.

+

If the user cancels your request, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=cancel.

+

If an error occurs during the request, the user will be redirected to the URL specified in the callback_url with the parameter tg_passport=error. The parameter error will contain one of the following values: BOT_INVALID, PUBLIC_KEY_REQUIRED, PUBLIC_KEY_INVALID, SCOPE_EMPTY, NONCE_EMPTY.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/schema.html b/data/corefork.telegram.org/schema.html new file mode 100644 index 0000000000..70955eccd9 --- /dev/null +++ b/data/corefork.telegram.org/schema.html @@ -0,0 +1,1859 @@ + + + + + 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#d18ee226 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 requests_pending:flags.17?int recent_requesters:flags.17?Vector<long> available_reactions:flags.18?Vector<string> = ChatFull;
+channelFull#e13c3d20 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 requests_pending:flags.28?int recent_requesters:flags.28?Vector<long> default_send_as:flags.29?Peer available_reactions:flags.30?Vector<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#38116ee0 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions 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;
+messageActionChatJoinedByRequest#ebbca3cb = MessageAction;
+
+dialog#a8edd0f5 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 unread_reactions_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#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int 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#a518110d 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 request_chat_broadcast:flags.10?true geo_distance:flags.6?int request_chat_title:flags.9?string request_chat_date:flags.9?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#cf366521 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 id:long 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 private_forward_name:flags.16?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;
+updatePendingJoinRequests#7063c3db peer:Peer requests_pending:int recent_requesters:Vector<long> = Update;
+updateBotChatInviteRequester#11dfa986 peer:Peer date:int user_id:long about:string invite:ExportedChatInvite qts:int = Update;
+updateMessageReactions#154798c3 peer:Peer msg_id:int reactions:MessageReactions = Update;
+
+updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
+
+updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
+updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
+updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
+updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
+
+updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+
+photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+
+photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+
+upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+
+config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+
+nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+
+help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
+help.noAppUpdate#c45a6536 = help.AppUpdate;
+
+help.inviteText#18cb9f78 message:string = help.InviteText;
+
+encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+
+inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;
+
+encryptedFileEmpty#c21f497e = EncryptedFile;
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
+inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
+inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
+inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;
+
+encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;
+
+messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
+messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
+
+messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+
+inputDocumentEmpty#72f0eaae = InputDocument;
+inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;
+
+documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+
+help.support#17c6b5f6 phone_number:string user:User = help.Support;
+
+notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;
+notifyUsers#b4c83b4c = NotifyPeer;
+notifyChats#c007cec3 = NotifyPeer;
+notifyBroadcasts#d612e8ef = NotifyPeer;
+
+sendMessageTypingAction#16bf744e = SendMessageAction;
+sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
+sendMessageRecordVideoAction#a187d66f = SendMessageAction;
+sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
+sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
+sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
+sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
+sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
+sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
+sendMessageChooseContactAction#628cbc6f = SendMessageAction;
+sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
+sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
+sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
+speakingInGroupCallAction#d92c2285 = SendMessageAction;
+sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
+sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
+
+contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
+
+inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
+inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
+inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
+inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
+inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
+inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
+inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
+inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;
+
+privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;
+privacyKeyChatInvite#500e6dfa = PrivacyKey;
+privacyKeyPhoneCall#3d662b7b = PrivacyKey;
+privacyKeyPhoneP2P#39491cc8 = PrivacyKey;
+privacyKeyForwards#69ec56a3 = PrivacyKey;
+privacyKeyProfilePhoto#96151fed = PrivacyKey;
+privacyKeyPhoneNumber#d19ae46d = PrivacyKey;
+privacyKeyAddedByPhone#42ffd42b = PrivacyKey;
+
+inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;
+inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
+inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;
+inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
+inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;
+inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;
+
+privacyValueAllowContacts#fffe1bac = PrivacyRule;
+privacyValueAllowAll#65427b82 = PrivacyRule;
+privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;
+privacyValueDisallowContacts#f888fa1a = PrivacyRule;
+privacyValueDisallowAll#8b73e763 = PrivacyRule;
+privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;
+privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
+privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;
+
+account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+
+accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
+documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
+documentAttributeHasStickers#9801d2f7 = DocumentAttribute;
+
+messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
+
+stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
+
+messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+
+messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+
+webPageEmpty#eb1477e8 id:long = WebPage;
+webPagePending#c586da1c id:long date:int = WebPage;
+webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
+
+authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+
+account.authorizations#4bff8ea0 authorization_ttl_days:int 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#ab4a819 flags:# revoked:flags.0?true permanent:flags.5?true request_needed:flags.6?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 requested:flags.7?int title:flags.8?string = ExportedChatInvite;
+
+chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
+chatInvite#300c44c1 flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true request_needed:flags.6?true title:string about:flags.5?string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
+
+inputStickerSetEmpty#ffb62b95 = InputStickerSet;
+inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
+inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
+inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
+inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
+
+stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+messages.stickerSetNotModified#d3f924eb = 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;
+inputKeyboardButtonUserProfile#e988037b text:string user_id:InputUser = KeyboardButton;
+keyboardButtonUserProfile#308660c1 text:string user_id:long = 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;
+messageEntitySpoiler#32ca960f 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#35a8bfa7 flags:# via_request:flags.0?true 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.codeTypeMissedCall#d61ad6ee = 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;
+auth.sentCodeTypeMissedCall#82006484 prefix:string length:int = 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;
+channelAdminLogEventActionParticipantJoinByRequest#afb6144a invite:ExportedChatInvite approved_by:long = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleNoForwards#cb2ac766 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionSendMessage#278f2868 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeAvailableReactions#9cf7f76a prev_value:Vector<string> new_value:Vector<string> = ChannelAdminLogEventAction;
+
+channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;
+
+channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+
+channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;
+
+popularContact#5ce14175 client_id:long importers:int = PopularContact;
+
+messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+
+recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;
+recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;
+recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;
+recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;
+recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;
+
+help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
+
+inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;
+
+webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;
+
+account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
+
+inputMessageID#a676a322 id:int = InputMessage;
+inputMessageReplyTo#bad88395 id:int = InputMessage;
+inputMessagePinned#86872538 = InputMessage;
+inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;
+
+inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
+inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
+
+dialogPeer#e56dbf05 peer:Peer = DialogPeer;
+dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
+
+messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
+messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
+
+fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
+
+inputClientProxy#75588b3f address:string port:int = InputClientProxy;
+
+help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+
+inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+secureFileEmpty#64199744 = SecureFile;
+secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;
+
+secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
+securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;
+
+secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
+
+secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;
+
+secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+
+secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
+
+help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
+help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
+
+savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;
+
+account.takeout#4dba4501 id:long = account.Takeout;
+
+passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
+passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;
+
+securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
+
+inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
+inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;
+
+secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;
+secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;
+
+help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
+help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
+
+inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;
+
+jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
+
+jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+
+pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;
+
+pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;
+
+pageCaption#6f747657 text:RichText credit:RichText = PageCaption;
+
+pageListItemText#b92fb6cd text:RichText = PageListItem;
+pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;
+
+pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
+pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;
+
+pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;
+
+page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;
+
+help.supportName#8c05f1c9 name:string = help.SupportName;
+
+help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+
+pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+chatOnlines#f041e250 onlines:int = ChatOnlines;
+
+statsURL#47a971e0 url:string = StatsURL;
+
+chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;
+
+chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;
+
+inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
+inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
+inputWallPaperNoFile#967a462e id:long = InputWallPaper;
+
+account.wallPapersNotModified#1c199183 = account.WallPapers;
+account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+
+codeSettings#8a6469c2 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true allow_missed_call:flags.5?true logout_tokens:flags.6?Vector<bytes> = 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#a00e67d6 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?Vector<ThemeSettings> emoticon:flags.6?string 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 rtmp_stream:flags.12?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#8c5adfd9 flags:# requested:flags.0?true user_id:long date:int about:flags.2?string approved_by:flags.1?long = 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;
+
+sponsoredMessage#3a836df8 flags:# random_id:bytes from_id:flags.3?Peer chat_invite:flags.4?ChatInvite chat_invite_hash:flags.4?string channel_post:flags.2?int 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;
+
+searchResultsCalendarPeriod#c9b0539f date:int min_msg_id:int max_msg_id:int count:int = SearchResultsCalendarPeriod;
+
+messages.searchResultsCalendar#147ee23c flags:# inexact:flags.0?true count:int min_date:int min_msg_id:int offset_id_offset:flags.1?int periods:Vector<SearchResultsCalendarPeriod> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.SearchResultsCalendar;
+
+searchResultPosition#7f648b67 msg_id:int date:int offset:int = SearchResultsPosition;
+
+messages.searchResultsPositions#53b22baf count:int positions:Vector<SearchResultsPosition> = messages.SearchResultsPositions;
+
+channels.sendAsPeers#8356cda9 peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = channels.SendAsPeers;
+
+users.userFull#3b6d152e full_user:UserFull chats:Vector<Chat> users:Vector<User> = users.UserFull;
+
+messages.peerSettings#6880b94d settings:PeerSettings chats:Vector<Chat> users:Vector<User> = messages.PeerSettings;
+
+auth.loggedOut#c3a2835f flags:# future_auth_token:flags.0?bytes = auth.LoggedOut;
+
+reactionCount#6fb250d1 flags:# chosen:flags.0?true reaction:string count:int = ReactionCount;
+
+messageReactions#4f2b9479 flags:# min:flags.0?true can_see_list:flags.2?true results:Vector<ReactionCount> recent_reactions:flags.1?Vector<MessagePeerReaction> = MessageReactions;
+
+messages.messageReactionsList#31bd492d flags:# count:int reactions:Vector<MessagePeerReaction> chats:Vector<Chat> users:Vector<User> next_offset:flags.0?string = messages.MessageReactionsList;
+
+availableReaction#c077ec01 flags:# inactive:flags.0?true reaction:string title:string static_icon:Document appear_animation:Document select_animation:Document activate_animation:Document effect_animation:Document around_animation:flags.1?Document center_icon:flags.1?Document = AvailableReaction;
+
+messages.availableReactionsNotModified#9f071957 = messages.AvailableReactions;
+messages.availableReactions#768e3aad hash:int reactions:Vector<AvailableReaction> = messages.AvailableReactions;
+
+messages.translateNoResult#67ca4737 = messages.TranslatedText;
+messages.translateResultText#a214f7d0 text:string = messages.TranslatedText;
+
+messagePeerReaction#51b67eff flags:# big:flags.0?true unread:flags.1?true peer_id:Peer reaction:string = MessagePeerReaction;
+
+---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#3e72ba19 = auth.LoggedOut;
+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#652e4400 flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?Vector<InputThemeSettings> = Theme;
+account.updateTheme#2bf40ccc flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?Vector<InputThemeSettings> = Theme;
+account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
+account.installTheme#c727bb3b flags:# dark:flags.0?true theme:flags.1?InputTheme format:flags.2?string base_theme:flags.3?BaseTheme = 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#d638de89 hash:long = account.Themes;
+account.setAuthorizationTTL#bf899aa0 authorization_ttl_days:int = Bool;
+account.changeAuthorizationSettings#40f48462 flags:# hash:long encrypted_requests_disabled:flags.0?Bool call_requests_disabled:flags.1?Bool = Bool;
+
+users.getUsers#d91a548 id:Vector<InputUser> = Vector<User>;
+users.getFullUser#b60f5918 id:InputUser = users.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#b08f922a flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int min_date:flags.2?int max_date:flags.3?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#d9d75a4 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?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 send_as:flags.13?InputPeer = Updates;
+messages.sendMedia#e25ff8e0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?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 send_as:flags.13?InputPeer = Updates;
+messages.forwardMessages#cc30290b 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 noforwards:flags.14?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;
+messages.reportSpam#cf1592db peer:InputPeer = Bool;
+messages.getPeerSettings#efd9a6a2 peer:InputPeer = messages.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#a02ce5d5 flags:# legacy_revoke_permanent:flags.2?true request_needed:flags.3?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int title:flags.4?string = ExportedChatInvite;
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;
+messages.importChatInvite#6c50051c hash:string = Updates;
+messages.getStickerSet#c8a0ec74 stickerset:InputStickerSet hash:int = 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#7aa11297 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 send_as:flags.13?InputPeer = 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#f803138f flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int send_as:flags.13?InputPeer = 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#bdca2f75 flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int request_needed:flags.3?Bool title:flags.4?string = 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#df04dd4e flags:# requested:flags.0?true peer:InputPeer link:flags.1?string q:flags.2?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>;
+messages.getSearchResultsCalendar#49f0bde9 peer:InputPeer filter:MessagesFilter offset_id:int offset_date:int = messages.SearchResultsCalendar;
+messages.getSearchResultsPositions#6e9583a3 peer:InputPeer filter:MessagesFilter offset_id:int limit:int = messages.SearchResultsPositions;
+messages.hideChatJoinRequest#7fe7e815 flags:# approved:flags.0?true peer:InputPeer user_id:InputUser = Updates;
+messages.hideAllChatJoinRequests#e085f4ea flags:# approved:flags.0?true peer:InputPeer link:flags.1?string = Updates;
+messages.toggleNoForwards#b11eafa2 peer:InputPeer enabled:Bool = Updates;
+messages.saveDefaultSendAs#ccfddf96 peer:InputPeer send_as:InputPeer = Bool;
+messages.sendReaction#25690ce4 flags:# big:flags.1?true peer:InputPeer msg_id:int reaction:flags.0?string = Updates;
+messages.getMessagesReactions#8bba90e6 peer:InputPeer id:Vector<int> = Updates;
+messages.getMessageReactionsList#e0ee6b77 flags:# peer:InputPeer id:int reaction:flags.0?string offset:flags.1?string limit:int = messages.MessageReactionsList;
+messages.setChatAvailableReactions#14050ea6 peer:InputPeer available_reactions:Vector<string> = Updates;
+messages.getAvailableReactions#18dea0ac hash:int = messages.AvailableReactions;
+messages.setDefaultReaction#d960c4d4 reaction:string = Bool;
+messages.translateText#24ce6dee flags:# peer:flags.0?InputPeer msg_id:flags.0?int text:flags.1?string from_lang:flags.2?string to_lang:string = messages.TranslatedText;
+messages.getUnreadReactions#e85bae1a peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
+messages.readReactions#82e251d7 peer:InputPeer = messages.AffectedHistory;
+
+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.reportSpam#f44a8315 channel:InputChannel participant:InputPeer 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;
+channels.getSendAs#dc770ee peer:InputPeer = channels.SendAsPeers;
+channels.deleteParticipantHistory#367544db channel:InputChannel participant:InputPeer = messages.AffectedHistory;
+
+bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;
+bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
+bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;
+
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;
+payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
+payments.getSavedInfo#227d824b = payments.SavedInfo;
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;
+
+stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
+stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
+stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
+stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;
+stickers.checkShortName#284b3639 short_name:string = Bool;
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;
+
+phone.getCallConfig#55451fa9 = DataJSON;
+phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
+phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;
+phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
+phone.createGroupCall#48cdc6d8 flags:# rtmp_stream:flags.2?true 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/corefork.telegram.org/schema/end-to-end-json.html b/data/corefork.telegram.org/schema/end-to-end-json.html new file mode 100644 index 0000000000..6c3b4f2cbe --- /dev/null +++ b/data/corefork.telegram.org/schema/end-to-end-json.html @@ -0,0 +1 @@ +{"constructors":[{"id":"528568095","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":8},{"id":"541931640","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":17},{"id":"917541342","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"}],"type":"DecryptedMessage","layer":45},{"id":"-1848883596","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"},{"name":"grouped_id","type":"flags.17?long"}],"type":"DecryptedMessage","layer":73},{"id":"-1438109059","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":8},{"id":"1930838368","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":17},{"id":"144661578","predicate":"decryptedMessageMediaEmpty","params":[],"type":"DecryptedMessageMedia","layer":8},{"id":"846826124","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-235238024","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1290694387","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1380598109","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"-1760785394","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"893913689","predicate":"decryptedMessageMediaGeoPoint","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1485441687","predicate":"decryptedMessageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"user_id","type":"int"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-1586283796","predicate":"decryptedMessageActionSetMessageTTL","params":[{"name":"ttl_seconds","type":"int"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1332395189","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"2063502050","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"attributes","type":"Vector"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1619031439","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1474341323","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"206520510","predicate":"decryptedMessageActionReadMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1700872964","predicate":"decryptedMessageActionDeleteMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1967000459","predicate":"decryptedMessageActionScreenshotMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1729750108","predicate":"decryptedMessageActionFlushHistory","params":[],"type":"DecryptedMessageAction","layer":8},{"id":"467867529","predicate":"decryptedMessageLayer","params":[{"name":"random_bytes","type":"bytes"},{"name":"layer","type":"int"},{"name":"in_seq_no","type":"int"},{"name":"out_seq_no","type":"int"},{"name":"message","type":"DecryptedMessage"}],"type":"DecryptedMessageLayer","layer":17},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1845219337","predicate":"sendMessageUploadVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-424899985","predicate":"sendMessageUploadAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1727382502","predicate":"sendMessageUploadPhotoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1884362354","predicate":"sendMessageUploadDocumentAction","params":[],"type":"SendMessageAction","layer":17},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1360072880","predicate":"decryptedMessageActionResend","params":[{"name":"start_seq_no","type":"int"},{"name":"end_seq_no","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-217806717","predicate":"decryptedMessageActionNotifyLayer","params":[{"name":"layer","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-860719551","predicate":"decryptedMessageActionTyping","params":[{"name":"action","type":"SendMessageAction"}],"type":"DecryptedMessageAction","layer":17},{"id":"-204906213","predicate":"decryptedMessageActionRequestKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"DecryptedMessageAction","layer":20},{"id":"1877046107","predicate":"decryptedMessageActionAcceptKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-586814357","predicate":"decryptedMessageActionAbortKey","params":[{"name":"exchange_id","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-332526693","predicate":"decryptedMessageActionCommitKey","params":[{"name":"exchange_id","type":"long"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-1473258141","predicate":"decryptedMessageActionNoop","params":[],"type":"DecryptedMessageAction","layer":20},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute","layer":23},{"id":"-83208409","predicate":"documentAttributeSticker","params":[],"type":"DocumentAttribute","layer":23},{"id":"978674434","predicate":"documentAttributeSticker","params":[{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"}],"type":"DocumentAttribute","layer":45},{"id":"1494273227","predicate":"documentAttributeVideo","params":[{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":66},{"id":"85215461","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"-556656416","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"},{"name":"title","type":"string"},{"name":"performer","type":"string"}],"type":"DocumentAttribute","layer":45},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute","layer":46},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute","layer":23},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize","layer":23},{"id":"2009052699","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize","layer":23},{"id":"-374917894","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize","layer":23},{"id":"2086234950","predicate":"fileLocationUnavailable","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"1406570614","predicate":"fileLocation","params":[{"name":"dc_id","type":"int"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"-90853155","predicate":"decryptedMessageMediaExternalDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumb","type":"PhotoSize"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"DecryptedMessageMedia","layer":23},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity","layer":45},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity","layer":45},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet","layer":45},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet","layer":45},{"id":"-1978796689","predicate":"decryptedMessageMediaVenue","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-452652584","predicate":"decryptedMessageMediaWebPage","params":[{"name":"url","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction","layer":66},{"id":"-1150187996","predicate":"sendMessageUploadRoundAction","params":[],"type":"SendMessageAction","layer":66}],"methods":[]} \ No newline at end of file diff --git a/data/corefork.telegram.org/schema/end-to-end.html b/data/corefork.telegram.org/schema/end-to-end.html new file mode 100644 index 0000000000..5aeadb0fef --- /dev/null +++ b/data/corefork.telegram.org/schema/end-to-end.html @@ -0,0 +1,225 @@ + + + + + Current end-to-end TL-schema + + + + + + + + + + + + + +
+ +
+
+
+ +

Current end-to-end TL-schema

+ +
+

Below you will find the current end-to-end TL-schema. More details on TL »

+
+

See also:
+End-to-end encryption in MTProto, Secret Chats
+Detailed schema in JSON

+
+ +
+
===8===
+decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;
+decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;
+decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
+decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;
+decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;
+
+===17===
+decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
+decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
+decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;
+sendMessageTypingAction#16bf744e = SendMessageAction;
+sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
+sendMessageRecordVideoAction#a187d66f = SendMessageAction;
+sendMessageUploadVideoAction#92042ff7 = SendMessageAction;
+sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
+sendMessageUploadAudioAction#e6ac8a6f = SendMessageAction;
+sendMessageUploadPhotoAction#990a3c1a = SendMessageAction;
+sendMessageUploadDocumentAction#8faee98e = SendMessageAction;
+sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
+sendMessageChooseContactAction#628cbc6f = SendMessageAction;
+decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;
+decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;
+decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;
+
+===20===
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
+decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;
+
+===23===
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#fb0a5727 = DocumentAttribute;
+documentAttributeVideo#5910cccb duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#51448e5 duration:int = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
+photoSizeEmpty#e17e23c type:string = PhotoSize;
+photoSize#77bfb61b type:string location:FileLocation w:int h:int size:int = PhotoSize;
+photoCachedSize#e9a734fa type:string location:FileLocation w:int h:int bytes:bytes = PhotoSize;
+fileLocationUnavailable#7c596b46 volume_id:long local_id:int secret:long = FileLocation;
+fileLocation#53d69076 dc_id:int volume_id:long local_id:int secret:long = FileLocation;
+decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;
+
+===45===
+decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
+decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
+decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
+decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
+documentAttributeSticker#3a556302 alt:string stickerset:InputStickerSet = DocumentAttribute;
+documentAttributeAudio#ded218e0 duration:int title:string performer:string = DocumentAttribute;
+messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
+messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
+messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
+messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
+messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
+messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
+messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
+messageEntityCode#28a20571 offset:int length:int = MessageEntity;
+messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
+messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
+inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
+inputStickerSetEmpty#ffb62b95 = InputStickerSet;
+decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;
+decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;
+
+===46===
+documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
+
+===66===
+documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true duration:int w:int h:int = DocumentAttribute;
+sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
+sendMessageUploadRoundAction#bb718624 = SendMessageAction;
+
+===73===
+decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;
+
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/schema/json.html b/data/corefork.telegram.org/schema/json.html new file mode 100644 index 0000000000..aba9f00ebe --- /dev/null +++ b/data/corefork.telegram.org/schema/json.html @@ -0,0 +1 @@ +{"constructors":[{"id":"-1132882121","predicate":"boolFalse","params":[],"type":"Bool"},{"id":"-1720552011","predicate":"boolTrue","params":[],"type":"Bool"},{"id":"1072550713","predicate":"true","params":[],"type":"True"},{"id":"481674261","predicate":"vector","params":[],"type":"Vector t"},{"id":"-994444869","predicate":"error","params":[{"name":"code","type":"int"},{"name":"text","type":"string"}],"type":"Error"},{"id":"1450380236","predicate":"null","params":[],"type":"Null"},{"id":"2134579434","predicate":"inputPeerEmpty","params":[],"type":"InputPeer"},{"id":"2107670217","predicate":"inputPeerSelf","params":[],"type":"InputPeer"},{"id":"900291769","predicate":"inputPeerChat","params":[{"name":"chat_id","type":"long"}],"type":"InputPeer"},{"id":"-1182234929","predicate":"inputUserEmpty","params":[],"type":"InputUser"},{"id":"-138301121","predicate":"inputUserSelf","params":[],"type":"InputUser"},{"id":"-208488460","predicate":"inputPhoneContact","params":[{"name":"client_id","type":"long"},{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"InputContact"},{"id":"-181407105","predicate":"inputFile","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"},{"name":"md5_checksum","type":"string"}],"type":"InputFile"},{"id":"-1771768449","predicate":"inputMediaEmpty","params":[],"type":"InputMedia"},{"id":"505969924","predicate":"inputMediaUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"-1279654347","predicate":"inputMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputPhoto"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-104578748","predicate":"inputMediaGeoPoint","params":[{"name":"geo_point","type":"InputGeoPoint"}],"type":"InputMedia"},{"id":"-122978821","predicate":"inputMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"}],"type":"InputMedia"},{"id":"480546647","predicate":"inputChatPhotoEmpty","params":[],"type":"InputChatPhoto"},{"id":"-968723890","predicate":"inputChatUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"InputChatPhoto"},{"id":"-1991004873","predicate":"inputChatPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputChatPhoto"},{"id":"-457104426","predicate":"inputGeoPointEmpty","params":[],"type":"InputGeoPoint"},{"id":"1210199983","predicate":"inputGeoPoint","params":[{"name":"flags","type":"#"},{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"InputGeoPoint"},{"id":"483901197","predicate":"inputPhotoEmpty","params":[],"type":"InputPhoto"},{"id":"1001634122","predicate":"inputPhoto","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputPhoto"},{"id":"-539317279","predicate":"inputFileLocation","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputFileLocation"},{"id":"1498486562","predicate":"peerUser","params":[{"name":"user_id","type":"long"}],"type":"Peer"},{"id":"918946202","predicate":"peerChat","params":[{"name":"chat_id","type":"long"}],"type":"Peer"},{"id":"-1432995067","predicate":"storage.fileUnknown","params":[],"type":"storage.FileType"},{"id":"1086091090","predicate":"storage.filePartial","params":[],"type":"storage.FileType"},{"id":"8322574","predicate":"storage.fileJpeg","params":[],"type":"storage.FileType"},{"id":"-891180321","predicate":"storage.fileGif","params":[],"type":"storage.FileType"},{"id":"172975040","predicate":"storage.filePng","params":[],"type":"storage.FileType"},{"id":"-1373745011","predicate":"storage.filePdf","params":[],"type":"storage.FileType"},{"id":"1384777335","predicate":"storage.fileMp3","params":[],"type":"storage.FileType"},{"id":"1258941372","predicate":"storage.fileMov","params":[],"type":"storage.FileType"},{"id":"-1278304028","predicate":"storage.fileMp4","params":[],"type":"storage.FileType"},{"id":"276907596","predicate":"storage.fileWebp","params":[],"type":"storage.FileType"},{"id":"-742634630","predicate":"userEmpty","params":[{"name":"id","type":"long"}],"type":"User"},{"id":"1326562017","predicate":"userProfilePhotoEmpty","params":[],"type":"UserProfilePhoto"},{"id":"-2100168954","predicate":"userProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"UserProfilePhoto"},{"id":"164646985","predicate":"userStatusEmpty","params":[],"type":"UserStatus"},{"id":"-306628279","predicate":"userStatusOnline","params":[{"name":"expires","type":"int"}],"type":"UserStatus"},{"id":"9203775","predicate":"userStatusOffline","params":[{"name":"was_online","type":"int"}],"type":"UserStatus"},{"id":"693512293","predicate":"chatEmpty","params":[{"name":"id","type":"long"}],"type":"Chat"},{"id":"1103884886","predicate":"chat","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"kicked","type":"flags.1?true"},{"name":"left","type":"flags.2?true"},{"name":"deactivated","type":"flags.5?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"noforwards","type":"flags.25?true"},{"name":"id","type":"long"},{"name":"title","type":"string"},{"name":"photo","type":"ChatPhoto"},{"name":"participants_count","type":"int"},{"name":"date","type":"int"},{"name":"version","type":"int"},{"name":"migrated_to","type":"flags.6?InputChannel"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"}],"type":"Chat"},{"id":"1704108455","predicate":"chatForbidden","params":[{"name":"id","type":"long"},{"name":"title","type":"string"}],"type":"Chat"},{"id":"-779165146","predicate":"chatFull","params":[{"name":"flags","type":"#"},{"name":"can_set_username","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants","type":"ChatParticipants"},{"name":"chat_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.13?ExportedChatInvite"},{"name":"bot_info","type":"flags.3?Vector"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"call","type":"flags.12?InputGroupCall"},{"name":"ttl_period","type":"flags.14?int"},{"name":"groupcall_default_join_as","type":"flags.15?Peer"},{"name":"theme_emoticon","type":"flags.16?string"},{"name":"requests_pending","type":"flags.17?int"},{"name":"recent_requesters","type":"flags.17?Vector"},{"name":"available_reactions","type":"flags.18?Vector"}],"type":"ChatFull"},{"id":"-1070776313","predicate":"chatParticipant","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-2023500831","predicate":"chatParticipantsForbidden","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"self_participant","type":"flags.0?ChatParticipant"}],"type":"ChatParticipants"},{"id":"1018991608","predicate":"chatParticipants","params":[{"name":"chat_id","type":"long"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"ChatParticipants"},{"id":"935395612","predicate":"chatPhotoEmpty","params":[],"type":"ChatPhoto"},{"id":"476978193","predicate":"chatPhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"ChatPhoto"},{"id":"-1868117372","predicate":"messageEmpty","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"peer_id","type":"flags.0?Peer"}],"type":"Message"},{"id":"940666592","predicate":"message","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"from_scheduled","type":"flags.18?true"},{"name":"legacy","type":"flags.19?true"},{"name":"edit_hide","type":"flags.21?true"},{"name":"pinned","type":"flags.24?true"},{"name":"noforwards","type":"flags.26?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"reply_markup","type":"flags.6?ReplyMarkup"},{"name":"entities","type":"flags.7?Vector"},{"name":"views","type":"flags.10?int"},{"name":"forwards","type":"flags.10?int"},{"name":"replies","type":"flags.23?MessageReplies"},{"name":"edit_date","type":"flags.15?int"},{"name":"post_author","type":"flags.16?string"},{"name":"grouped_id","type":"flags.17?long"},{"name":"reactions","type":"flags.20?MessageReactions"},{"name":"restriction_reason","type":"flags.22?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"721967202","predicate":"messageService","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"legacy","type":"flags.19?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"action","type":"MessageAction"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"1038967584","predicate":"messageMediaEmpty","params":[],"type":"MessageMedia"},{"id":"1766936791","predicate":"messageMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"photo","type":"flags.0?Photo"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1457575028","predicate":"messageMediaGeo","params":[{"name":"geo","type":"GeoPoint"}],"type":"MessageMedia"},{"id":"1882335561","predicate":"messageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"user_id","type":"long"}],"type":"MessageMedia"},{"id":"-1618676578","predicate":"messageMediaUnsupported","params":[],"type":"MessageMedia"},{"id":"-1230047312","predicate":"messageActionEmpty","params":[],"type":"MessageAction"},{"id":"-1119368275","predicate":"messageActionChatCreate","params":[{"name":"title","type":"string"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1247687078","predicate":"messageActionChatEditTitle","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"2144015272","predicate":"messageActionChatEditPhoto","params":[{"name":"photo","type":"Photo"}],"type":"MessageAction"},{"id":"-1780220945","predicate":"messageActionChatDeletePhoto","params":[],"type":"MessageAction"},{"id":"365886720","predicate":"messageActionChatAddUser","params":[{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1539362612","predicate":"messageActionChatDeleteUser","params":[{"name":"user_id","type":"long"}],"type":"MessageAction"},{"id":"-1460809483","predicate":"dialog","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"unread_mark","type":"flags.3?true"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"unread_mentions_count","type":"int"},{"name":"unread_reactions_count","type":"int"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"pts","type":"flags.0?int"},{"name":"draft","type":"flags.1?DraftMessage"},{"name":"folder_id","type":"flags.4?int"}],"type":"Dialog"},{"id":"590459437","predicate":"photoEmpty","params":[{"name":"id","type":"long"}],"type":"Photo"},{"id":"-82216347","predicate":"photo","params":[{"name":"flags","type":"#"},{"name":"has_stickers","type":"flags.0?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"sizes","type":"Vector"},{"name":"video_sizes","type":"flags.1?Vector"},{"name":"dc_id","type":"int"}],"type":"Photo"},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize"},{"id":"1976012384","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize"},{"id":"35527382","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"286776671","predicate":"geoPointEmpty","params":[],"type":"GeoPoint"},{"id":"-1297942941","predicate":"geoPoint","params":[{"name":"flags","type":"#"},{"name":"long","type":"double"},{"name":"lat","type":"double"},{"name":"access_hash","type":"long"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"GeoPoint"},{"id":"1577067778","predicate":"auth.sentCode","params":[{"name":"flags","type":"#"},{"name":"type","type":"auth.SentCodeType"},{"name":"phone_code_hash","type":"string"},{"name":"next_type","type":"flags.1?auth.CodeType"},{"name":"timeout","type":"flags.2?int"}],"type":"auth.SentCode"},{"id":"872119224","predicate":"auth.authorization","params":[{"name":"flags","type":"#"},{"name":"setup_password_required","type":"flags.1?true"},{"name":"otherwise_relogin_days","type":"flags.1?int"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"user","type":"User"}],"type":"auth.Authorization"},{"id":"-1271602504","predicate":"auth.exportedAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.ExportedAuthorization"},{"id":"-1195615476","predicate":"inputNotifyPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputNotifyPeer"},{"id":"423314455","predicate":"inputNotifyUsers","params":[],"type":"InputNotifyPeer"},{"id":"1251338318","predicate":"inputNotifyChats","params":[],"type":"InputNotifyPeer"},{"id":"-1673717362","predicate":"inputPeerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"InputPeerNotifySettings"},{"id":"-1353671392","predicate":"peerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"PeerNotifySettings"},{"id":"-1525149427","predicate":"peerSettings","params":[{"name":"flags","type":"#"},{"name":"report_spam","type":"flags.0?true"},{"name":"add_contact","type":"flags.1?true"},{"name":"block_contact","type":"flags.2?true"},{"name":"share_contact","type":"flags.3?true"},{"name":"need_contacts_exception","type":"flags.4?true"},{"name":"report_geo","type":"flags.5?true"},{"name":"autoarchived","type":"flags.7?true"},{"name":"invite_members","type":"flags.8?true"},{"name":"request_chat_broadcast","type":"flags.10?true"},{"name":"geo_distance","type":"flags.6?int"},{"name":"request_chat_title","type":"flags.9?string"},{"name":"request_chat_date","type":"flags.9?int"}],"type":"PeerSettings"},{"id":"-1539849235","predicate":"wallPaper","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"pattern","type":"flags.3?true"},{"name":"dark","type":"flags.4?true"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"document","type":"Document"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"1490799288","predicate":"inputReportReasonSpam","params":[],"type":"ReportReason"},{"id":"505595789","predicate":"inputReportReasonViolence","params":[],"type":"ReportReason"},{"id":"777640226","predicate":"inputReportReasonPornography","params":[],"type":"ReportReason"},{"id":"-1376497949","predicate":"inputReportReasonChildAbuse","params":[],"type":"ReportReason"},{"id":"-1041980751","predicate":"inputReportReasonOther","params":[],"type":"ReportReason"},{"id":"-818518751","predicate":"userFull","params":[{"name":"flags","type":"#"},{"name":"blocked","type":"flags.0?true"},{"name":"phone_calls_available","type":"flags.4?true"},{"name":"phone_calls_private","type":"flags.5?true"},{"name":"can_pin_message","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.12?true"},{"name":"video_calls_available","type":"flags.13?true"},{"name":"id","type":"long"},{"name":"about","type":"flags.1?string"},{"name":"settings","type":"PeerSettings"},{"name":"profile_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"bot_info","type":"flags.3?BotInfo"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"common_chats_count","type":"int"},{"name":"folder_id","type":"flags.11?int"},{"name":"ttl_period","type":"flags.14?int"},{"name":"theme_emoticon","type":"flags.15?string"},{"name":"private_forward_name","type":"flags.16?string"}],"type":"UserFull"},{"id":"341499403","predicate":"contact","params":[{"name":"user_id","type":"long"},{"name":"mutual","type":"Bool"}],"type":"Contact"},{"id":"-1052885936","predicate":"importedContact","params":[{"name":"user_id","type":"long"},{"name":"client_id","type":"long"}],"type":"ImportedContact"},{"id":"383348795","predicate":"contactStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"ContactStatus"},{"id":"-1219778094","predicate":"contacts.contactsNotModified","params":[],"type":"contacts.Contacts"},{"id":"-353862078","predicate":"contacts.contacts","params":[{"name":"contacts","type":"Vector"},{"name":"saved_count","type":"int"},{"name":"users","type":"Vector"}],"type":"contacts.Contacts"},{"id":"2010127419","predicate":"contacts.importedContacts","params":[{"name":"imported","type":"Vector"},{"name":"popular_invites","type":"Vector"},{"name":"retry_contacts","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"182326673","predicate":"contacts.blocked","params":[{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"-513392236","predicate":"contacts.blockedSlice","params":[{"name":"count","type":"int"},{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"364538944","predicate":"messages.dialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"1910543603","predicate":"messages.dialogsSlice","params":[{"name":"count","type":"int"},{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"-1938715001","predicate":"messages.messages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"978610270","predicate":"messages.messagesSlice","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"count","type":"int"},{"name":"next_rate","type":"flags.0?int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"1694474197","predicate":"messages.chats","params":[{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-438840932","predicate":"messages.chatFull","params":[{"name":"full_chat","type":"ChatFull"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatFull"},{"id":"-1269012015","predicate":"messages.affectedHistory","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"}],"type":"messages.AffectedHistory"},{"id":"1474492012","predicate":"inputMessagesFilterEmpty","params":[],"type":"MessagesFilter"},{"id":"-1777752804","predicate":"inputMessagesFilterPhotos","params":[],"type":"MessagesFilter"},{"id":"-1614803355","predicate":"inputMessagesFilterVideo","params":[],"type":"MessagesFilter"},{"id":"1458172132","predicate":"inputMessagesFilterPhotoVideo","params":[],"type":"MessagesFilter"},{"id":"-1629621880","predicate":"inputMessagesFilterDocument","params":[],"type":"MessagesFilter"},{"id":"2129714567","predicate":"inputMessagesFilterUrl","params":[],"type":"MessagesFilter"},{"id":"-3644025","predicate":"inputMessagesFilterGif","params":[],"type":"MessagesFilter"},{"id":"522914557","predicate":"updateNewMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1318109142","predicate":"updateMessageID","params":[{"name":"id","type":"int"},{"name":"random_id","type":"long"}],"type":"Update"},{"id":"-1576161051","predicate":"updateDeleteMessages","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1071741569","predicate":"updateUserTyping","params":[{"name":"user_id","type":"long"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-2092401936","predicate":"updateChatUserTyping","params":[{"name":"chat_id","type":"long"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"125178264","predicate":"updateChatParticipants","params":[{"name":"participants","type":"ChatParticipants"}],"type":"Update"},{"id":"-440534818","predicate":"updateUserStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"Update"},{"id":"-1007549728","predicate":"updateUserName","params":[{"name":"user_id","type":"long"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"username","type":"string"}],"type":"Update"},{"id":"-232290676","predicate":"updateUserPhoto","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"photo","type":"UserProfilePhoto"},{"name":"previous","type":"Bool"}],"type":"Update"},{"id":"-1519637954","predicate":"updates.state","params":[{"name":"pts","type":"int"},{"name":"qts","type":"int"},{"name":"date","type":"int"},{"name":"seq","type":"int"},{"name":"unread_count","type":"int"}],"type":"updates.State"},{"id":"1567990072","predicate":"updates.differenceEmpty","params":[{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"updates.Difference"},{"id":"16030880","predicate":"updates.difference","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-1459938943","predicate":"updates.differenceSlice","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"intermediate_state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-484987010","predicate":"updatesTooLong","params":[],"type":"Updates"},{"id":"826001400","predicate":"updateShortMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"user_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"1299050149","predicate":"updateShortChatMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"from_id","type":"long"},{"name":"chat_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"2027216577","predicate":"updateShort","params":[{"name":"update","type":"Update"},{"name":"date","type":"int"}],"type":"Updates"},{"id":"1918567619","predicate":"updatesCombined","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq_start","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"1957577280","predicate":"updates","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"-1916114267","predicate":"photos.photos","params":[{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"352657236","predicate":"photos.photosSlice","params":[{"name":"count","type":"int"},{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"539045032","predicate":"photos.photo","params":[{"name":"photo","type":"Photo"},{"name":"users","type":"Vector"}],"type":"photos.Photo"},{"id":"157948117","predicate":"upload.file","params":[{"name":"type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.File"},{"id":"414687501","predicate":"dcOption","params":[{"name":"flags","type":"#"},{"name":"ipv6","type":"flags.0?true"},{"name":"media_only","type":"flags.1?true"},{"name":"tcpo_only","type":"flags.2?true"},{"name":"cdn","type":"flags.3?true"},{"name":"static","type":"flags.4?true"},{"name":"id","type":"int"},{"name":"ip_address","type":"string"},{"name":"port","type":"int"},{"name":"secret","type":"flags.10?bytes"}],"type":"DcOption"},{"id":"856375399","predicate":"config","params":[{"name":"flags","type":"#"},{"name":"phonecalls_enabled","type":"flags.1?true"},{"name":"default_p2p_contacts","type":"flags.3?true"},{"name":"preload_featured_stickers","type":"flags.4?true"},{"name":"ignore_phone_entities","type":"flags.5?true"},{"name":"revoke_pm_inbox","type":"flags.6?true"},{"name":"blocked_mode","type":"flags.8?true"},{"name":"pfs_enabled","type":"flags.13?true"},{"name":"date","type":"int"},{"name":"expires","type":"int"},{"name":"test_mode","type":"Bool"},{"name":"this_dc","type":"int"},{"name":"dc_options","type":"Vector"},{"name":"dc_txt_domain_name","type":"string"},{"name":"chat_size_max","type":"int"},{"name":"megagroup_size_max","type":"int"},{"name":"forwarded_count_max","type":"int"},{"name":"online_update_period_ms","type":"int"},{"name":"offline_blur_timeout_ms","type":"int"},{"name":"offline_idle_timeout_ms","type":"int"},{"name":"online_cloud_timeout_ms","type":"int"},{"name":"notify_cloud_delay_ms","type":"int"},{"name":"notify_default_delay_ms","type":"int"},{"name":"push_chat_period_ms","type":"int"},{"name":"push_chat_limit","type":"int"},{"name":"saved_gifs_limit","type":"int"},{"name":"edit_time_limit","type":"int"},{"name":"revoke_time_limit","type":"int"},{"name":"revoke_pm_time_limit","type":"int"},{"name":"rating_e_decay","type":"int"},{"name":"stickers_recent_limit","type":"int"},{"name":"stickers_faved_limit","type":"int"},{"name":"channels_read_media_period","type":"int"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"pinned_dialogs_count_max","type":"int"},{"name":"pinned_infolder_count_max","type":"int"},{"name":"call_receive_timeout_ms","type":"int"},{"name":"call_ring_timeout_ms","type":"int"},{"name":"call_connect_timeout_ms","type":"int"},{"name":"call_packet_timeout_ms","type":"int"},{"name":"me_url_prefix","type":"string"},{"name":"autoupdate_url_prefix","type":"flags.7?string"},{"name":"gif_search_username","type":"flags.9?string"},{"name":"venue_search_username","type":"flags.10?string"},{"name":"img_search_username","type":"flags.11?string"},{"name":"static_maps_provider","type":"flags.12?string"},{"name":"caption_length_max","type":"int"},{"name":"message_length_max","type":"int"},{"name":"webfile_dc_id","type":"int"},{"name":"suggested_lang_code","type":"flags.2?string"},{"name":"lang_pack_version","type":"flags.2?int"},{"name":"base_lang_pack_version","type":"flags.2?int"}],"type":"Config"},{"id":"-1910892683","predicate":"nearestDc","params":[{"name":"country","type":"string"},{"name":"this_dc","type":"int"},{"name":"nearest_dc","type":"int"}],"type":"NearestDc"},{"id":"-860107216","predicate":"help.appUpdate","params":[{"name":"flags","type":"#"},{"name":"can_not_skip","type":"flags.0?true"},{"name":"id","type":"int"},{"name":"version","type":"string"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"document","type":"flags.1?Document"},{"name":"url","type":"flags.2?string"},{"name":"sticker","type":"flags.3?Document"}],"type":"help.AppUpdate"},{"id":"-1000708810","predicate":"help.noAppUpdate","params":[],"type":"help.AppUpdate"},{"id":"415997816","predicate":"help.inviteText","params":[{"name":"message","type":"string"}],"type":"help.InviteText"},{"id":"314359194","predicate":"updateNewEncryptedMessage","params":[{"name":"message","type":"EncryptedMessage"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"386986326","predicate":"updateEncryptedChatTyping","params":[{"name":"chat_id","type":"int"}],"type":"Update"},{"id":"-1264392051","predicate":"updateEncryption","params":[{"name":"chat","type":"EncryptedChat"},{"name":"date","type":"int"}],"type":"Update"},{"id":"956179895","predicate":"updateEncryptedMessagesRead","params":[{"name":"chat_id","type":"int"},{"name":"max_date","type":"int"},{"name":"date","type":"int"}],"type":"Update"},{"id":"-1417756512","predicate":"encryptedChatEmpty","params":[{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"1722964307","predicate":"encryptedChatWaiting","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"}],"type":"EncryptedChat"},{"id":"1223809356","predicate":"encryptedChatRequested","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1643173063","predicate":"encryptedChat","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"505183301","predicate":"encryptedChatDiscarded","params":[{"name":"flags","type":"#"},{"name":"history_deleted","type":"flags.0?true"},{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"-247351839","predicate":"inputEncryptedChat","params":[{"name":"chat_id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedChat"},{"id":"-1038136962","predicate":"encryptedFileEmpty","params":[],"type":"EncryptedFile"},{"id":"1248893260","predicate":"encryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"EncryptedFile"},{"id":"406307684","predicate":"inputEncryptedFileEmpty","params":[],"type":"InputEncryptedFile"},{"id":"1690108678","predicate":"inputEncryptedFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1511503333","predicate":"inputEncryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedFile"},{"id":"-182231723","predicate":"inputEncryptedFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"-317144808","predicate":"encryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"},{"name":"file","type":"EncryptedFile"}],"type":"EncryptedMessage"},{"id":"594758406","predicate":"encryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"}],"type":"EncryptedMessage"},{"id":"-1058912715","predicate":"messages.dhConfigNotModified","params":[{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"740433629","predicate":"messages.dhConfig","params":[{"name":"g","type":"int"},{"name":"p","type":"bytes"},{"name":"version","type":"int"},{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"1443858741","predicate":"messages.sentEncryptedMessage","params":[{"name":"date","type":"int"}],"type":"messages.SentEncryptedMessage"},{"id":"-1802240206","predicate":"messages.sentEncryptedFile","params":[{"name":"date","type":"int"},{"name":"file","type":"EncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"-95482955","predicate":"inputFileBig","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"}],"type":"InputFile"},{"id":"767652808","predicate":"inputEncryptedFileBigUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1037718609","predicate":"updateChatParticipantAdd","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-483443337","predicate":"updateChatParticipantDelete","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-1906403213","predicate":"updateDcOptions","params":[{"name":"dc_options","type":"Vector"}],"type":"Update"},{"id":"1530447553","predicate":"inputMediaUploadedDocument","params":[{"name":"flags","type":"#"},{"name":"nosound_video","type":"flags.3?true"},{"name":"force_file","type":"flags.4?true"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.2?InputFile"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"860303448","predicate":"inputMediaDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputDocument"},{"name":"ttl_seconds","type":"flags.0?int"},{"name":"query","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-1666158377","predicate":"messageMediaDocument","params":[{"name":"flags","type":"#"},{"name":"document","type":"flags.0?Document"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1928391342","predicate":"inputDocumentEmpty","params":[],"type":"InputDocument"},{"id":"448771445","predicate":"inputDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputDocument"},{"id":"-1160743548","predicate":"inputDocumentFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"922273905","predicate":"documentEmpty","params":[{"name":"id","type":"long"}],"type":"Document"},{"id":"512177195","predicate":"document","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumbs","type":"flags.0?Vector"},{"name":"video_thumbs","type":"flags.1?Vector"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"Document"},{"id":"398898678","predicate":"help.support","params":[{"name":"phone_number","type":"string"},{"name":"user","type":"User"}],"type":"help.Support"},{"id":"-1613493288","predicate":"notifyPeer","params":[{"name":"peer","type":"Peer"}],"type":"NotifyPeer"},{"id":"-1261946036","predicate":"notifyUsers","params":[],"type":"NotifyPeer"},{"id":"-1073230141","predicate":"notifyChats","params":[],"type":"NotifyPeer"},{"id":"-1094555409","predicate":"updateNotifySettings","params":[{"name":"peer","type":"NotifyPeer"},{"name":"notify_settings","type":"PeerNotifySettings"}],"type":"Update"},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction"},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction"},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction"},{"id":"-378127636","predicate":"sendMessageUploadVideoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction"},{"id":"-212740181","predicate":"sendMessageUploadAudioAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-774682074","predicate":"sendMessageUploadPhotoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-1441998364","predicate":"sendMessageUploadDocumentAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction"},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction"},{"id":"-1290580579","predicate":"contacts.found","params":[{"name":"my_results","type":"Vector"},{"name":"results","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Found"},{"id":"-337352679","predicate":"updateServiceNotification","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"inbox_date","type":"flags.1?int"},{"name":"type","type":"string"},{"name":"message","type":"string"},{"name":"media","type":"MessageMedia"},{"name":"entities","type":"Vector"}],"type":"Update"},{"id":"-496024847","predicate":"userStatusRecently","params":[],"type":"UserStatus"},{"id":"129960444","predicate":"userStatusLastWeek","params":[],"type":"UserStatus"},{"id":"2011940674","predicate":"userStatusLastMonth","params":[],"type":"UserStatus"},{"id":"-298113238","predicate":"updatePrivacy","params":[{"name":"key","type":"PrivacyKey"},{"name":"rules","type":"Vector"}],"type":"Update"},{"id":"1335282456","predicate":"inputPrivacyKeyStatusTimestamp","params":[],"type":"InputPrivacyKey"},{"id":"-1137792208","predicate":"privacyKeyStatusTimestamp","params":[],"type":"PrivacyKey"},{"id":"218751099","predicate":"inputPrivacyValueAllowContacts","params":[],"type":"InputPrivacyRule"},{"id":"407582158","predicate":"inputPrivacyValueAllowAll","params":[],"type":"InputPrivacyRule"},{"id":"320652927","predicate":"inputPrivacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"195371015","predicate":"inputPrivacyValueDisallowContacts","params":[],"type":"InputPrivacyRule"},{"id":"-697604407","predicate":"inputPrivacyValueDisallowAll","params":[],"type":"InputPrivacyRule"},{"id":"-1877932953","predicate":"inputPrivacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-123988","predicate":"privacyValueAllowContacts","params":[],"type":"PrivacyRule"},{"id":"1698855810","predicate":"privacyValueAllowAll","params":[],"type":"PrivacyRule"},{"id":"-1198497870","predicate":"privacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"-125240806","predicate":"privacyValueDisallowContacts","params":[],"type":"PrivacyRule"},{"id":"-1955338397","predicate":"privacyValueDisallowAll","params":[],"type":"PrivacyRule"},{"id":"-463335103","predicate":"privacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"1352683077","predicate":"account.privacyRules","params":[{"name":"rules","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"-1194283041","predicate":"accountDaysTTL","params":[{"name":"days","type":"int"}],"type":"AccountDaysTTL"},{"id":"88680979","predicate":"updateUserPhone","params":[{"name":"user_id","type":"long"},{"name":"phone","type":"string"}],"type":"Update"},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute"},{"id":"1662637586","predicate":"documentAttributeSticker","params":[{"name":"flags","type":"#"},{"name":"mask","type":"flags.1?true"},{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"DocumentAttribute"},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"round_message","type":"flags.0?true"},{"name":"supports_streaming","type":"flags.1?true"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"voice","type":"flags.10?true"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute"},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute"},{"id":"-244016606","predicate":"messages.stickersNotModified","params":[],"type":"messages.Stickers"},{"id":"816245886","predicate":"messages.stickers","params":[{"name":"hash","type":"long"},{"name":"stickers","type":"Vector"}],"type":"messages.Stickers"},{"id":"313694676","predicate":"stickerPack","params":[{"name":"emoticon","type":"string"},{"name":"documents","type":"Vector"}],"type":"StickerPack"},{"id":"-395967805","predicate":"messages.allStickersNotModified","params":[],"type":"messages.AllStickers"},{"id":"-843329861","predicate":"messages.allStickers","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.AllStickers"},{"id":"-1667805217","predicate":"updateReadHistoryInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"791617983","predicate":"updateReadHistoryOutbox","params":[{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-2066640507","predicate":"messages.affectedMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"messages.AffectedMessages"},{"id":"2139689491","predicate":"updateWebPage","params":[{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-350980120","predicate":"webPageEmpty","params":[{"name":"id","type":"long"}],"type":"WebPage"},{"id":"-981018084","predicate":"webPagePending","params":[{"name":"id","type":"long"},{"name":"date","type":"int"}],"type":"WebPage"},{"id":"-392411726","predicate":"webPage","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"url","type":"string"},{"name":"display_url","type":"string"},{"name":"hash","type":"int"},{"name":"type","type":"flags.0?string"},{"name":"site_name","type":"flags.1?string"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"photo","type":"flags.4?Photo"},{"name":"embed_url","type":"flags.5?string"},{"name":"embed_type","type":"flags.5?string"},{"name":"embed_width","type":"flags.6?int"},{"name":"embed_height","type":"flags.6?int"},{"name":"duration","type":"flags.7?int"},{"name":"author","type":"flags.8?string"},{"name":"document","type":"flags.9?Document"},{"name":"cached_page","type":"flags.10?Page"},{"name":"attributes","type":"flags.12?Vector"}],"type":"WebPage"},{"id":"-1557277184","predicate":"messageMediaWebPage","params":[{"name":"webpage","type":"WebPage"}],"type":"MessageMedia"},{"id":"-1392388579","predicate":"authorization","params":[{"name":"flags","type":"#"},{"name":"current","type":"flags.0?true"},{"name":"official_app","type":"flags.1?true"},{"name":"password_pending","type":"flags.2?true"},{"name":"encrypted_requests_disabled","type":"flags.3?true"},{"name":"call_requests_disabled","type":"flags.4?true"},{"name":"hash","type":"long"},{"name":"device_model","type":"string"},{"name":"platform","type":"string"},{"name":"system_version","type":"string"},{"name":"api_id","type":"int"},{"name":"app_name","type":"string"},{"name":"app_version","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"country","type":"string"},{"name":"region","type":"string"}],"type":"Authorization"},{"id":"1275039392","predicate":"account.authorizations","params":[{"name":"authorization_ttl_days","type":"int"},{"name":"authorizations","type":"Vector"}],"type":"account.Authorizations"},{"id":"408623183","predicate":"account.password","params":[{"name":"flags","type":"#"},{"name":"has_recovery","type":"flags.0?true"},{"name":"has_secure_values","type":"flags.1?true"},{"name":"has_password","type":"flags.2?true"},{"name":"current_algo","type":"flags.2?PasswordKdfAlgo"},{"name":"srp_B","type":"flags.2?bytes"},{"name":"srp_id","type":"flags.2?long"},{"name":"hint","type":"flags.3?string"},{"name":"email_unconfirmed_pattern","type":"flags.4?string"},{"name":"new_algo","type":"PasswordKdfAlgo"},{"name":"new_secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_random","type":"bytes"},{"name":"pending_reset_date","type":"flags.5?int"}],"type":"account.Password"},{"id":"-1705233435","predicate":"account.passwordSettings","params":[{"name":"flags","type":"#"},{"name":"email","type":"flags.0?string"},{"name":"secure_settings","type":"flags.1?SecureSecretSettings"}],"type":"account.PasswordSettings"},{"id":"-1036572727","predicate":"account.passwordInputSettings","params":[{"name":"flags","type":"#"},{"name":"new_algo","type":"flags.0?PasswordKdfAlgo"},{"name":"new_password_hash","type":"flags.0?bytes"},{"name":"hint","type":"flags.0?string"},{"name":"email","type":"flags.1?string"},{"name":"new_secure_settings","type":"flags.2?SecureSecretSettings"}],"type":"account.PasswordInputSettings"},{"id":"326715557","predicate":"auth.passwordRecovery","params":[{"name":"email_pattern","type":"string"}],"type":"auth.PasswordRecovery"},{"id":"-1052959727","predicate":"inputMediaVenue","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"InputMedia"},{"id":"784356159","predicate":"messageMediaVenue","params":[{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"MessageMedia"},{"id":"-1551583367","predicate":"receivedNotifyMessage","params":[{"name":"id","type":"int"},{"name":"flags","type":"int"}],"type":"ReceivedNotifyMessage"},{"id":"179611673","predicate":"chatInviteExported","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.0?true"},{"name":"permanent","type":"flags.5?true"},{"name":"request_needed","type":"flags.6?true"},{"name":"link","type":"string"},{"name":"admin_id","type":"long"},{"name":"date","type":"int"},{"name":"start_date","type":"flags.4?int"},{"name":"expire_date","type":"flags.1?int"},{"name":"usage_limit","type":"flags.2?int"},{"name":"usage","type":"flags.3?int"},{"name":"requested","type":"flags.7?int"},{"name":"title","type":"flags.8?string"}],"type":"ExportedChatInvite"},{"id":"1516793212","predicate":"chatInviteAlready","params":[{"name":"chat","type":"Chat"}],"type":"ChatInvite"},{"id":"806110401","predicate":"chatInvite","params":[{"name":"flags","type":"#"},{"name":"channel","type":"flags.0?true"},{"name":"broadcast","type":"flags.1?true"},{"name":"public","type":"flags.2?true"},{"name":"megagroup","type":"flags.3?true"},{"name":"request_needed","type":"flags.6?true"},{"name":"title","type":"string"},{"name":"about","type":"flags.5?string"},{"name":"photo","type":"Photo"},{"name":"participants_count","type":"int"},{"name":"participants","type":"flags.4?Vector"}],"type":"ChatInvite"},{"id":"51520707","predicate":"messageActionChatJoinedByLink","params":[{"name":"inviter_id","type":"long"}],"type":"MessageAction"},{"id":"1757493555","predicate":"updateReadMessagesContents","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet"},{"id":"-1645763991","predicate":"inputStickerSetID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputStickerSet"},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet"},{"id":"-673242758","predicate":"stickerSet","params":[{"name":"flags","type":"#"},{"name":"archived","type":"flags.1?true"},{"name":"official","type":"flags.2?true"},{"name":"masks","type":"flags.3?true"},{"name":"animated","type":"flags.5?true"},{"name":"videos","type":"flags.6?true"},{"name":"installed_date","type":"flags.0?int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumbs","type":"flags.4?Vector"},{"name":"thumb_dc_id","type":"flags.4?int"},{"name":"thumb_version","type":"flags.4?int"},{"name":"count","type":"int"},{"name":"hash","type":"int"}],"type":"StickerSet"},{"id":"-1240849242","predicate":"messages.stickerSet","params":[{"name":"set","type":"StickerSet"},{"name":"packs","type":"Vector"},{"name":"documents","type":"Vector"}],"type":"messages.StickerSet"},{"id":"1073147056","predicate":"user","params":[{"name":"flags","type":"#"},{"name":"self","type":"flags.10?true"},{"name":"contact","type":"flags.11?true"},{"name":"mutual_contact","type":"flags.12?true"},{"name":"deleted","type":"flags.13?true"},{"name":"bot","type":"flags.14?true"},{"name":"bot_chat_history","type":"flags.15?true"},{"name":"bot_nochats","type":"flags.16?true"},{"name":"verified","type":"flags.17?true"},{"name":"restricted","type":"flags.18?true"},{"name":"min","type":"flags.20?true"},{"name":"bot_inline_geo","type":"flags.21?true"},{"name":"support","type":"flags.23?true"},{"name":"scam","type":"flags.24?true"},{"name":"apply_min_photo","type":"flags.25?true"},{"name":"fake","type":"flags.26?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.0?long"},{"name":"first_name","type":"flags.1?string"},{"name":"last_name","type":"flags.2?string"},{"name":"username","type":"flags.3?string"},{"name":"phone","type":"flags.4?string"},{"name":"photo","type":"flags.5?UserProfilePhoto"},{"name":"status","type":"flags.6?UserStatus"},{"name":"bot_info_version","type":"flags.14?int"},{"name":"restriction_reason","type":"flags.18?Vector"},{"name":"bot_inline_placeholder","type":"flags.19?string"},{"name":"lang_code","type":"flags.22?string"}],"type":"User"},{"id":"-1032140601","predicate":"botCommand","params":[{"name":"command","type":"string"},{"name":"description","type":"string"}],"type":"BotCommand"},{"id":"460632885","predicate":"botInfo","params":[{"name":"user_id","type":"long"},{"name":"description","type":"string"},{"name":"commands","type":"Vector"}],"type":"BotInfo"},{"id":"-1560655744","predicate":"keyboardButton","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"2002815875","predicate":"keyboardButtonRow","params":[{"name":"buttons","type":"Vector"}],"type":"KeyboardButtonRow"},{"id":"-1606526075","predicate":"replyKeyboardHide","params":[{"name":"flags","type":"#"},{"name":"selective","type":"flags.2?true"}],"type":"ReplyMarkup"},{"id":"-2035021048","predicate":"replyKeyboardForceReply","params":[{"name":"flags","type":"#"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-2049074735","predicate":"replyKeyboardMarkup","params":[{"name":"flags","type":"#"},{"name":"resize","type":"flags.0?true"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"rows","type":"Vector"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-571955892","predicate":"inputPeerUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-233744186","predicate":"inputUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputUser"},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity"},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity"},{"id":"-1877614335","predicate":"updateShortSentMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"-292807034","predicate":"inputChannelEmpty","params":[],"type":"InputChannel"},{"id":"-212145112","predicate":"inputChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputChannel"},{"id":"-1566230754","predicate":"peerChannel","params":[{"name":"channel_id","type":"long"}],"type":"Peer"},{"id":"666680316","predicate":"inputPeerChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-2107528095","predicate":"channel","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"left","type":"flags.2?true"},{"name":"broadcast","type":"flags.5?true"},{"name":"verified","type":"flags.7?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"restricted","type":"flags.9?true"},{"name":"signatures","type":"flags.11?true"},{"name":"min","type":"flags.12?true"},{"name":"scam","type":"flags.19?true"},{"name":"has_link","type":"flags.20?true"},{"name":"has_geo","type":"flags.21?true"},{"name":"slowmode_enabled","type":"flags.22?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"fake","type":"flags.25?true"},{"name":"gigagroup","type":"flags.26?true"},{"name":"noforwards","type":"flags.27?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.13?long"},{"name":"title","type":"string"},{"name":"username","type":"flags.6?string"},{"name":"photo","type":"ChatPhoto"},{"name":"date","type":"int"},{"name":"restriction_reason","type":"flags.9?Vector"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"banned_rights","type":"flags.15?ChatBannedRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"},{"name":"participants_count","type":"flags.17?int"}],"type":"Chat"},{"id":"399807445","predicate":"channelForbidden","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.5?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"until_date","type":"flags.16?int"}],"type":"Chat"},{"id":"2131196633","predicate":"contacts.resolvedPeer","params":[{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ResolvedPeer"},{"id":"-516145888","predicate":"channelFull","params":[{"name":"flags","type":"#"},{"name":"can_view_participants","type":"flags.3?true"},{"name":"can_set_username","type":"flags.6?true"},{"name":"can_set_stickers","type":"flags.7?true"},{"name":"hidden_prehistory","type":"flags.10?true"},{"name":"can_set_location","type":"flags.16?true"},{"name":"has_scheduled","type":"flags.19?true"},{"name":"can_view_stats","type":"flags.20?true"},{"name":"blocked","type":"flags.22?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants_count","type":"flags.0?int"},{"name":"admins_count","type":"flags.1?int"},{"name":"kicked_count","type":"flags.2?int"},{"name":"banned_count","type":"flags.2?int"},{"name":"online_count","type":"flags.13?int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"chat_photo","type":"Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.23?ExportedChatInvite"},{"name":"bot_info","type":"Vector"},{"name":"migrated_from_chat_id","type":"flags.4?long"},{"name":"migrated_from_max_id","type":"flags.4?int"},{"name":"pinned_msg_id","type":"flags.5?int"},{"name":"stickerset","type":"flags.8?StickerSet"},{"name":"available_min_id","type":"flags.9?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"linked_chat_id","type":"flags.14?long"},{"name":"location","type":"flags.15?ChannelLocation"},{"name":"slowmode_seconds","type":"flags.17?int"},{"name":"slowmode_next_send_date","type":"flags.18?int"},{"name":"stats_dc","type":"flags.12?int"},{"name":"pts","type":"int"},{"name":"call","type":"flags.21?InputGroupCall"},{"name":"ttl_period","type":"flags.24?int"},{"name":"pending_suggestions","type":"flags.25?Vector"},{"name":"groupcall_default_join_as","type":"flags.26?Peer"},{"name":"theme_emoticon","type":"flags.27?string"},{"name":"requests_pending","type":"flags.28?int"},{"name":"recent_requesters","type":"flags.28?Vector"},{"name":"default_send_as","type":"flags.29?Peer"},{"name":"available_reactions","type":"flags.30?Vector"}],"type":"ChatFull"},{"id":"182649427","predicate":"messageRange","params":[{"name":"min_id","type":"int"},{"name":"max_id","type":"int"}],"type":"MessageRange"},{"id":"1682413576","predicate":"messages.channelMessages","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"pts","type":"int"},{"name":"count","type":"int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"-1781355374","predicate":"messageActionChannelCreate","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"277713951","predicate":"updateChannelTooLong","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"pts","type":"flags.0?int"}],"type":"Update"},{"id":"1666927625","predicate":"updateChannel","params":[{"name":"channel_id","type":"long"}],"type":"Update"},{"id":"1656358105","predicate":"updateNewChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1842450928","predicate":"updateReadChannelInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"}],"type":"Update"},{"id":"-1020437742","predicate":"updateDeleteChannelMessages","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-232346616","predicate":"updateChannelMessageViews","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"views","type":"int"}],"type":"Update"},{"id":"1041346555","predicate":"updates.channelDifferenceEmpty","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"}],"type":"updates.ChannelDifference"},{"id":"-1531132162","predicate":"updates.channelDifferenceTooLong","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"timeout","type":"flags.1?int"},{"name":"dialog","type":"Dialog"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"543450958","predicate":"updates.channelDifference","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"},{"name":"new_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"-1798033689","predicate":"channelMessagesFilterEmpty","params":[],"type":"ChannelMessagesFilter"},{"id":"-847783593","predicate":"channelMessagesFilter","params":[{"name":"flags","type":"#"},{"name":"exclude_new_messages","type":"flags.1?true"},{"name":"ranges","type":"Vector"}],"type":"ChannelMessagesFilter"},{"id":"-1072953408","predicate":"channelParticipant","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"900251559","predicate":"channelParticipantSelf","params":[{"name":"flags","type":"#"},{"name":"via_request","type":"flags.0?true"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"803602899","predicate":"channelParticipantCreator","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.0?string"}],"type":"ChannelParticipant"},{"id":"-566281095","predicate":"channelParticipantsRecent","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1268741783","predicate":"channelParticipantsAdmins","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1548400251","predicate":"channelParticipantsKicked","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-1699676497","predicate":"channels.channelParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipants"},{"id":"-541588713","predicate":"channels.channelParticipant","params":[{"name":"participant","type":"ChannelParticipant"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipant"},{"id":"-462696732","predicate":"chatParticipantCreator","params":[{"name":"user_id","type":"long"}],"type":"ChatParticipant"},{"id":"-1600962725","predicate":"chatParticipantAdmin","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-674602590","predicate":"updateChatParticipantAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"is_admin","type":"Bool"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-519864430","predicate":"messageActionChatMigrateTo","params":[{"name":"channel_id","type":"long"}],"type":"MessageAction"},{"id":"-365344535","predicate":"messageActionChannelMigrateFrom","params":[{"name":"title","type":"string"},{"name":"chat_id","type":"long"}],"type":"MessageAction"},{"id":"-1328445861","predicate":"channelParticipantsBots","params":[],"type":"ChannelParticipantsFilter"},{"id":"2013922064","predicate":"help.termsOfService","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"id","type":"DataJSON"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"min_age_confirm","type":"flags.1?int"}],"type":"help.TermsOfService"},{"id":"1753886890","predicate":"updateNewStickerSet","params":[{"name":"stickerset","type":"messages.StickerSet"}],"type":"Update"},{"id":"196268545","predicate":"updateStickerSetsOrder","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Update"},{"id":"1135492588","predicate":"updateStickerSets","params":[],"type":"Update"},{"id":"-402498398","predicate":"messages.savedGifsNotModified","params":[],"type":"messages.SavedGifs"},{"id":"-2069878259","predicate":"messages.savedGifs","params":[{"name":"hash","type":"long"},{"name":"gifs","type":"Vector"}],"type":"messages.SavedGifs"},{"id":"-1821035490","predicate":"updateSavedGifs","params":[],"type":"Update"},{"id":"864077702","predicate":"inputBotInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1036876423","predicate":"inputBotInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-2000710887","predicate":"inputBotInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?InputWebDocument"},{"name":"content","type":"flags.5?InputWebDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1984755728","predicate":"botInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1937807902","predicate":"botInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"295067450","predicate":"botInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?WebDocument"},{"name":"content","type":"flags.5?WebDocument"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1803769784","predicate":"messages.botResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"query_id","type":"long"},{"name":"next_offset","type":"flags.1?string"},{"name":"switch_pm","type":"flags.2?InlineBotSwitchPM"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"users","type":"Vector"}],"type":"messages.BotResults"},{"id":"1232025500","predicate":"updateBotInlineQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"peer_type","type":"flags.1?InlineQueryPeerType"},{"name":"offset","type":"string"}],"type":"Update"},{"id":"317794823","predicate":"updateBotInlineSend","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"id","type":"string"},{"name":"msg_id","type":"flags.1?InputBotInlineMessageID"}],"type":"Update"},{"id":"1358283666","predicate":"inputMessagesFilterVoice","params":[],"type":"MessagesFilter"},{"id":"928101534","predicate":"inputMessagesFilterMusic","params":[],"type":"MessagesFilter"},{"id":"-1107622874","predicate":"inputPrivacyKeyChatInvite","params":[],"type":"InputPrivacyKey"},{"id":"1343122938","predicate":"privacyKeyChatInvite","params":[],"type":"PrivacyKey"},{"id":"1571494644","predicate":"exportedMessageLink","params":[{"name":"link","type":"string"},{"name":"html","type":"string"}],"type":"ExportedMessageLink"},{"id":"1601666510","predicate":"messageFwdHeader","params":[{"name":"flags","type":"#"},{"name":"imported","type":"flags.7?true"},{"name":"from_id","type":"flags.0?Peer"},{"name":"from_name","type":"flags.5?string"},{"name":"date","type":"int"},{"name":"channel_post","type":"flags.2?int"},{"name":"post_author","type":"flags.3?string"},{"name":"saved_from_peer","type":"flags.4?Peer"},{"name":"saved_from_msg_id","type":"flags.4?int"},{"name":"psa_type","type":"flags.6?string"}],"type":"MessageFwdHeader"},{"id":"457133559","predicate":"updateEditChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1799538451","predicate":"messageActionPinMessage","params":[],"type":"MessageAction"},{"id":"1923290508","predicate":"auth.codeTypeSms","params":[],"type":"auth.CodeType"},{"id":"1948046307","predicate":"auth.codeTypeCall","params":[],"type":"auth.CodeType"},{"id":"577556219","predicate":"auth.codeTypeFlashCall","params":[],"type":"auth.CodeType"},{"id":"1035688326","predicate":"auth.sentCodeTypeApp","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1073693790","predicate":"auth.sentCodeTypeSms","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"1398007207","predicate":"auth.sentCodeTypeCall","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1425815847","predicate":"auth.sentCodeTypeFlashCall","params":[{"name":"pattern","type":"string"}],"type":"auth.SentCodeType"},{"id":"629866245","predicate":"keyboardButtonUrl","params":[{"name":"text","type":"string"},{"name":"url","type":"string"}],"type":"KeyboardButton"},{"id":"901503851","predicate":"keyboardButtonCallback","params":[{"name":"flags","type":"#"},{"name":"requires_password","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"data","type":"bytes"}],"type":"KeyboardButton"},{"id":"-1318425559","predicate":"keyboardButtonRequestPhone","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-59151553","predicate":"keyboardButtonRequestGeoLocation","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"90744648","predicate":"keyboardButtonSwitchInline","params":[{"name":"flags","type":"#"},{"name":"same_peer","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"query","type":"string"}],"type":"KeyboardButton"},{"id":"1218642516","predicate":"replyInlineMarkup","params":[{"name":"rows","type":"Vector"}],"type":"ReplyMarkup"},{"id":"911761060","predicate":"messages.botCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"has_url","type":"flags.3?true"},{"name":"native_ui","type":"flags.4?true"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"messages.BotCallbackAnswer"},{"id":"-1177566067","predicate":"updateBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"649453030","predicate":"messages.messageEditData","params":[{"name":"flags","type":"#"},{"name":"caption","type":"flags.0?true"}],"type":"messages.MessageEditData"},{"id":"-469536605","predicate":"updateEditMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1768777083","predicate":"inputBotInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1098628881","predicate":"inputBotInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-1494368259","predicate":"inputBotInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"85477117","predicate":"botInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1970903652","predicate":"botInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"416402882","predicate":"botInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1462213465","predicate":"inputBotInlineResultPhoto","params":[{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"InputPhoto"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"-459324","predicate":"inputBotInlineResultDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"document","type":"InputDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"400266251","predicate":"botInlineMediaResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"flags.0?Photo"},{"name":"document","type":"flags.1?Document"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1995686519","predicate":"inputBotInlineMessageID","params":[{"name":"dc_id","type":"int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"},{"id":"1763610706","predicate":"updateInlineBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"msg_id","type":"InputBotInlineMessageID"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"1008755359","predicate":"inlineBotSwitchPM","params":[{"name":"text","type":"string"},{"name":"start_param","type":"string"}],"type":"InlineBotSwitchPM"},{"id":"863093588","predicate":"messages.peerDialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"messages.PeerDialogs"},{"id":"-305282981","predicate":"topPeer","params":[{"name":"peer","type":"Peer"},{"name":"rating","type":"double"}],"type":"TopPeer"},{"id":"-1419371685","predicate":"topPeerCategoryBotsPM","params":[],"type":"TopPeerCategory"},{"id":"344356834","predicate":"topPeerCategoryBotsInline","params":[],"type":"TopPeerCategory"},{"id":"104314861","predicate":"topPeerCategoryCorrespondents","params":[],"type":"TopPeerCategory"},{"id":"-1122524854","predicate":"topPeerCategoryGroups","params":[],"type":"TopPeerCategory"},{"id":"371037736","predicate":"topPeerCategoryChannels","params":[],"type":"TopPeerCategory"},{"id":"-75283823","predicate":"topPeerCategoryPeers","params":[{"name":"category","type":"TopPeerCategory"},{"name":"count","type":"int"},{"name":"peers","type":"Vector"}],"type":"TopPeerCategoryPeers"},{"id":"-567906571","predicate":"contacts.topPeersNotModified","params":[],"type":"contacts.TopPeers"},{"id":"1891070632","predicate":"contacts.topPeers","params":[{"name":"categories","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.TopPeers"},{"id":"-595914432","predicate":"messageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"long"}],"type":"MessageEntity"},{"id":"546203849","predicate":"inputMessageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"MessageEntity"},{"id":"975236280","predicate":"inputMessagesFilterChatPhotos","params":[],"type":"MessagesFilter"},{"id":"-1218471511","predicate":"updateReadChannelOutbox","params":[{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"}],"type":"Update"},{"id":"-299124375","predicate":"updateDraftMessage","params":[{"name":"peer","type":"Peer"},{"name":"draft","type":"DraftMessage"}],"type":"Update"},{"id":"453805082","predicate":"draftMessageEmpty","params":[{"name":"flags","type":"#"},{"name":"date","type":"flags.0?int"}],"type":"DraftMessage"},{"id":"-40996577","predicate":"draftMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"},{"name":"date","type":"int"}],"type":"DraftMessage"},{"id":"-1615153660","predicate":"messageActionHistoryClear","params":[],"type":"MessageAction"},{"id":"-958657434","predicate":"messages.featuredStickersNotModified","params":[{"name":"count","type":"int"}],"type":"messages.FeaturedStickers"},{"id":"-2067782896","predicate":"messages.featuredStickers","params":[{"name":"hash","type":"long"},{"name":"count","type":"int"},{"name":"sets","type":"Vector"},{"name":"unread","type":"Vector"}],"type":"messages.FeaturedStickers"},{"id":"1461528386","predicate":"updateReadFeaturedStickers","params":[],"type":"Update"},{"id":"186120336","predicate":"messages.recentStickersNotModified","params":[],"type":"messages.RecentStickers"},{"id":"-1999405994","predicate":"messages.recentStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"},{"name":"dates","type":"Vector"}],"type":"messages.RecentStickers"},{"id":"-1706939360","predicate":"updateRecentStickers","params":[],"type":"Update"},{"id":"1338747336","predicate":"messages.archivedStickers","params":[{"name":"count","type":"int"},{"name":"sets","type":"Vector"}],"type":"messages.ArchivedStickers"},{"id":"946083368","predicate":"messages.stickerSetInstallResultSuccess","params":[],"type":"messages.StickerSetInstallResult"},{"id":"904138920","predicate":"messages.stickerSetInstallResultArchive","params":[{"name":"sets","type":"Vector"}],"type":"messages.StickerSetInstallResult"},{"id":"1678812626","predicate":"stickerSetCovered","params":[{"name":"set","type":"StickerSet"},{"name":"cover","type":"Document"}],"type":"StickerSetCovered"},{"id":"-1574314746","predicate":"updateConfig","params":[],"type":"Update"},{"id":"861169551","predicate":"updatePtsChanged","params":[],"type":"Update"},{"id":"-440664550","predicate":"inputMediaPhotoExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-78455655","predicate":"inputMediaDocumentExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"872932635","predicate":"stickerSetMultiCovered","params":[{"name":"set","type":"StickerSet"},{"name":"covers","type":"Vector"}],"type":"StickerSetCovered"},{"id":"-1361650766","predicate":"maskCoords","params":[{"name":"n","type":"int"},{"name":"x","type":"double"},{"name":"y","type":"double"},{"name":"zoom","type":"double"}],"type":"MaskCoords"},{"id":"-1744710921","predicate":"documentAttributeHasStickers","params":[],"type":"DocumentAttribute"},{"id":"1251549527","predicate":"inputStickeredMediaPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputStickeredMedia"},{"id":"70813275","predicate":"inputStickeredMediaDocument","params":[{"name":"id","type":"InputDocument"}],"type":"InputStickeredMedia"},{"id":"-1107729093","predicate":"game","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"short_name","type":"string"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"Photo"},{"name":"document","type":"flags.0?Document"}],"type":"Game"},{"id":"1336154098","predicate":"inputBotInlineResultGame","params":[{"name":"id","type":"string"},{"name":"short_name","type":"string"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1262639204","predicate":"inputBotInlineMessageGame","params":[{"name":"flags","type":"#"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-38694904","predicate":"messageMediaGame","params":[{"name":"game","type":"Game"}],"type":"MessageMedia"},{"id":"-750828557","predicate":"inputMediaGame","params":[{"name":"id","type":"InputGame"}],"type":"InputMedia"},{"id":"53231223","predicate":"inputGameID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGame"},{"id":"-1020139510","predicate":"inputGameShortName","params":[{"name":"bot_id","type":"InputUser"},{"name":"short_name","type":"string"}],"type":"InputGame"},{"id":"1358175439","predicate":"keyboardButtonGame","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-1834538890","predicate":"messageActionGameScore","params":[{"name":"game_id","type":"long"},{"name":"score","type":"int"}],"type":"MessageAction"},{"id":"1940093419","predicate":"highScore","params":[{"name":"pos","type":"int"},{"name":"user_id","type":"long"},{"name":"score","type":"int"}],"type":"HighScore"},{"id":"-1707344487","predicate":"messages.highScores","params":[{"name":"scores","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.HighScores"},{"id":"1258196845","predicate":"updates.differenceTooLong","params":[{"name":"pts","type":"int"}],"type":"updates.Difference"},{"id":"791390623","predicate":"updateChannelWebPage","params":[{"name":"channel_id","type":"long"},{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1663561404","predicate":"messages.chatsSlice","params":[{"name":"count","type":"int"},{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-599948721","predicate":"textEmpty","params":[],"type":"RichText"},{"id":"1950782688","predicate":"textPlain","params":[{"name":"text","type":"string"}],"type":"RichText"},{"id":"1730456516","predicate":"textBold","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-653089380","predicate":"textItalic","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1054465340","predicate":"textUnderline","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1678197867","predicate":"textStrike","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1816074681","predicate":"textFixed","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1009288385","predicate":"textUrl","params":[{"name":"text","type":"RichText"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"}],"type":"RichText"},{"id":"-564523562","predicate":"textEmail","params":[{"name":"text","type":"RichText"},{"name":"email","type":"string"}],"type":"RichText"},{"id":"2120376535","predicate":"textConcat","params":[{"name":"texts","type":"Vector"}],"type":"RichText"},{"id":"324435594","predicate":"pageBlockUnsupported","params":[],"type":"PageBlock"},{"id":"1890305021","predicate":"pageBlockTitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1879401953","predicate":"pageBlockSubtitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1162877472","predicate":"pageBlockAuthorDate","params":[{"name":"author","type":"RichText"},{"name":"published_date","type":"int"}],"type":"PageBlock"},{"id":"-1076861716","predicate":"pageBlockHeader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-248793375","predicate":"pageBlockSubheader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"1182402406","predicate":"pageBlockParagraph","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1066346178","predicate":"pageBlockPreformatted","params":[{"name":"text","type":"RichText"},{"name":"language","type":"string"}],"type":"PageBlock"},{"id":"1216809369","predicate":"pageBlockFooter","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-618614392","predicate":"pageBlockDivider","params":[],"type":"PageBlock"},{"id":"-837994576","predicate":"pageBlockAnchor","params":[{"name":"name","type":"string"}],"type":"PageBlock"},{"id":"-454524911","predicate":"pageBlockList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"641563686","predicate":"pageBlockBlockquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"1329878739","predicate":"pageBlockPullquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"391759200","predicate":"pageBlockPhoto","params":[{"name":"flags","type":"#"},{"name":"photo_id","type":"long"},{"name":"caption","type":"PageCaption"},{"name":"url","type":"flags.0?string"},{"name":"webpage_id","type":"flags.0?long"}],"type":"PageBlock"},{"id":"2089805750","predicate":"pageBlockVideo","params":[{"name":"flags","type":"#"},{"name":"autoplay","type":"flags.0?true"},{"name":"loop","type":"flags.1?true"},{"name":"video_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"972174080","predicate":"pageBlockCover","params":[{"name":"cover","type":"PageBlock"}],"type":"PageBlock"},{"id":"-1468953147","predicate":"pageBlockEmbed","params":[{"name":"flags","type":"#"},{"name":"full_width","type":"flags.0?true"},{"name":"allow_scrolling","type":"flags.3?true"},{"name":"url","type":"flags.1?string"},{"name":"html","type":"flags.2?string"},{"name":"poster_photo_id","type":"flags.4?long"},{"name":"w","type":"flags.5?int"},{"name":"h","type":"flags.5?int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-229005301","predicate":"pageBlockEmbedPost","params":[{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"author_photo_id","type":"long"},{"name":"author","type":"string"},{"name":"date","type":"int"},{"name":"blocks","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1705048653","predicate":"pageBlockCollage","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"52401552","predicate":"pageBlockSlideshow","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1930545681","predicate":"webPageNotModified","params":[{"name":"flags","type":"#"},{"name":"cached_page_views","type":"flags.0?int"}],"type":"WebPage"},{"id":"-88417185","predicate":"inputPrivacyKeyPhoneCall","params":[],"type":"InputPrivacyKey"},{"id":"1030105979","predicate":"privacyKeyPhoneCall","params":[],"type":"PrivacyKey"},{"id":"-580219064","predicate":"sendMessageGamePlayAction","params":[],"type":"SendMessageAction"},{"id":"-2048646399","predicate":"phoneCallDiscardReasonMissed","params":[],"type":"PhoneCallDiscardReason"},{"id":"-527056480","predicate":"phoneCallDiscardReasonDisconnect","params":[],"type":"PhoneCallDiscardReason"},{"id":"1471006352","predicate":"phoneCallDiscardReasonHangup","params":[],"type":"PhoneCallDiscardReason"},{"id":"-84416311","predicate":"phoneCallDiscardReasonBusy","params":[],"type":"PhoneCallDiscardReason"},{"id":"1852826908","predicate":"updateDialogPinned","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-99664734","predicate":"updatePinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.1?int"},{"name":"order","type":"flags.0?Vector"}],"type":"Update"},{"id":"2104790276","predicate":"dataJSON","params":[{"name":"data","type":"string"}],"type":"DataJSON"},{"id":"-2095595325","predicate":"updateBotWebhookJSON","params":[{"name":"data","type":"DataJSON"}],"type":"Update"},{"id":"-1684914010","predicate":"updateBotWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"},{"name":"timeout","type":"int"}],"type":"Update"},{"id":"-886477832","predicate":"labeledPrice","params":[{"name":"label","type":"string"},{"name":"amount","type":"long"}],"type":"LabeledPrice"},{"id":"215516896","predicate":"invoice","params":[{"name":"flags","type":"#"},{"name":"test","type":"flags.0?true"},{"name":"name_requested","type":"flags.1?true"},{"name":"phone_requested","type":"flags.2?true"},{"name":"email_requested","type":"flags.3?true"},{"name":"shipping_address_requested","type":"flags.4?true"},{"name":"flexible","type":"flags.5?true"},{"name":"phone_to_provider","type":"flags.6?true"},{"name":"email_to_provider","type":"flags.7?true"},{"name":"currency","type":"string"},{"name":"prices","type":"Vector"},{"name":"max_tip_amount","type":"flags.8?long"},{"name":"suggested_tip_amounts","type":"flags.8?Vector"}],"type":"Invoice"},{"id":"-646342540","predicate":"inputMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"start_param","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-368917890","predicate":"paymentCharge","params":[{"name":"id","type":"string"},{"name":"provider_charge_id","type":"string"}],"type":"PaymentCharge"},{"id":"-1892568281","predicate":"messageActionPaymentSentMe","params":[{"name":"flags","type":"#"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"charge","type":"PaymentCharge"}],"type":"MessageAction"},{"id":"-2074799289","predicate":"messageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"receipt_msg_id","type":"flags.2?int"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"start_param","type":"string"}],"type":"MessageMedia"},{"id":"512535275","predicate":"postAddress","params":[{"name":"street_line1","type":"string"},{"name":"street_line2","type":"string"},{"name":"city","type":"string"},{"name":"state","type":"string"},{"name":"country_iso2","type":"string"},{"name":"post_code","type":"string"}],"type":"PostAddress"},{"id":"-1868808300","predicate":"paymentRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"name","type":"flags.0?string"},{"name":"phone","type":"flags.1?string"},{"name":"email","type":"flags.2?string"},{"name":"shipping_address","type":"flags.3?PostAddress"}],"type":"PaymentRequestedInfo"},{"id":"-1344716869","predicate":"keyboardButtonBuy","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1080663248","predicate":"messageActionPaymentSent","params":[{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"MessageAction"},{"id":"-842892769","predicate":"paymentSavedCredentialsCard","params":[{"name":"id","type":"string"},{"name":"title","type":"string"}],"type":"PaymentSavedCredentials"},{"id":"475467473","predicate":"webDocument","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"-1678949555","predicate":"inputWebDocument","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"InputWebDocument"},{"id":"-1036396922","predicate":"inputWebFileLocation","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"}],"type":"InputWebFileLocation"},{"id":"568808380","predicate":"upload.webFile","params":[{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"file_type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.WebFile"},{"id":"378828315","predicate":"payments.paymentForm","params":[{"name":"flags","type":"#"},{"name":"can_save_credentials","type":"flags.2?true"},{"name":"password_missing","type":"flags.3?true"},{"name":"form_id","type":"long"},{"name":"bot_id","type":"long"},{"name":"invoice","type":"Invoice"},{"name":"provider_id","type":"long"},{"name":"url","type":"string"},{"name":"native_provider","type":"flags.4?string"},{"name":"native_params","type":"flags.4?DataJSON"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"},{"name":"saved_credentials","type":"flags.1?PaymentSavedCredentials"},{"name":"users","type":"Vector"}],"type":"payments.PaymentForm"},{"id":"-784000893","predicate":"payments.validatedRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"id","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"payments.ValidatedRequestedInfo"},{"id":"1314881805","predicate":"payments.paymentResult","params":[{"name":"updates","type":"Updates"}],"type":"payments.PaymentResult"},{"id":"1891958275","predicate":"payments.paymentReceipt","params":[{"name":"flags","type":"#"},{"name":"date","type":"int"},{"name":"bot_id","type":"long"},{"name":"provider_id","type":"long"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.2?WebDocument"},{"name":"invoice","type":"Invoice"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping","type":"flags.1?ShippingOption"},{"name":"tip_amount","type":"flags.3?long"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"credentials_title","type":"string"},{"name":"users","type":"Vector"}],"type":"payments.PaymentReceipt"},{"id":"-74456004","predicate":"payments.savedInfo","params":[{"name":"flags","type":"#"},{"name":"has_saved_credentials","type":"flags.1?true"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"}],"type":"payments.SavedInfo"},{"id":"-1056001329","predicate":"inputPaymentCredentialsSaved","params":[{"name":"id","type":"string"},{"name":"tmp_password","type":"bytes"}],"type":"InputPaymentCredentials"},{"id":"873977640","predicate":"inputPaymentCredentials","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-614138572","predicate":"account.tmpPassword","params":[{"name":"tmp_password","type":"bytes"},{"name":"valid_until","type":"int"}],"type":"account.TmpPassword"},{"id":"-1239335713","predicate":"shippingOption","params":[{"name":"id","type":"string"},{"name":"title","type":"string"},{"name":"prices","type":"Vector"}],"type":"ShippingOption"},{"id":"-1246823043","predicate":"updateBotShippingQuery","params":[{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"shipping_address","type":"PostAddress"}],"type":"Update"},{"id":"-1934976362","predicate":"updateBotPrecheckoutQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"Update"},{"id":"-6249322","predicate":"inputStickerSetItem","params":[{"name":"flags","type":"#"},{"name":"document","type":"InputDocument"},{"name":"emoji","type":"string"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"InputStickerSetItem"},{"id":"-1425052898","predicate":"updatePhoneCall","params":[{"name":"phone_call","type":"PhoneCall"}],"type":"Update"},{"id":"506920429","predicate":"inputPhoneCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPhoneCall"},{"id":"1399245077","predicate":"phoneCallEmpty","params":[{"name":"id","type":"long"}],"type":"PhoneCall"},{"id":"-987599081","predicate":"phoneCallWaiting","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"receive_date","type":"flags.0?int"}],"type":"PhoneCall"},{"id":"347139340","predicate":"phoneCallRequested","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"912311057","predicate":"phoneCallAccepted","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"-1770029977","predicate":"phoneCall","params":[{"name":"flags","type":"#"},{"name":"p2p_allowed","type":"flags.5?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"connections","type":"Vector"},{"name":"start_date","type":"int"}],"type":"PhoneCall"},{"id":"1355435489","predicate":"phoneCallDiscarded","params":[{"name":"flags","type":"#"},{"name":"need_rating","type":"flags.2?true"},{"name":"need_debug","type":"flags.3?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"PhoneCall"},{"id":"-1655957568","predicate":"phoneConnection","params":[{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"peer_tag","type":"bytes"}],"type":"PhoneConnection"},{"id":"-58224696","predicate":"phoneCallProtocol","params":[{"name":"flags","type":"#"},{"name":"udp_p2p","type":"flags.0?true"},{"name":"udp_reflector","type":"flags.1?true"},{"name":"min_layer","type":"int"},{"name":"max_layer","type":"int"},{"name":"library_versions","type":"Vector"}],"type":"PhoneCallProtocol"},{"id":"-326966976","predicate":"phone.phoneCall","params":[{"name":"phone_call","type":"PhoneCall"},{"name":"users","type":"Vector"}],"type":"phone.PhoneCall"},{"id":"-2134272152","predicate":"inputMessagesFilterPhoneCalls","params":[{"name":"flags","type":"#"},{"name":"missed","type":"flags.0?true"}],"type":"MessagesFilter"},{"id":"-2132731265","predicate":"messageActionPhoneCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.2?true"},{"name":"call_id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"MessageAction"},{"id":"2054952868","predicate":"inputMessagesFilterRoundVoice","params":[],"type":"MessagesFilter"},{"id":"-1253451181","predicate":"inputMessagesFilterRoundVideo","params":[],"type":"MessagesFilter"},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction"},{"id":"608050278","predicate":"sendMessageUploadRoundAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-242427324","predicate":"upload.fileCdnRedirect","params":[{"name":"dc_id","type":"int"},{"name":"file_token","type":"bytes"},{"name":"encryption_key","type":"bytes"},{"name":"encryption_iv","type":"bytes"},{"name":"file_hashes","type":"Vector"}],"type":"upload.File"},{"id":"-290921362","predicate":"upload.cdnFileReuploadNeeded","params":[{"name":"request_token","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-1449145777","predicate":"upload.cdnFile","params":[{"name":"bytes","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-914167110","predicate":"cdnPublicKey","params":[{"name":"dc_id","type":"int"},{"name":"public_key","type":"string"}],"type":"CdnPublicKey"},{"id":"1462101002","predicate":"cdnConfig","params":[{"name":"public_keys","type":"Vector"}],"type":"CdnConfig"},{"id":"-283684427","predicate":"pageBlockChannel","params":[{"name":"channel","type":"Chat"}],"type":"PageBlock"},{"id":"-892239370","predicate":"langPackString","params":[{"name":"key","type":"string"},{"name":"value","type":"string"}],"type":"LangPackString"},{"id":"1816636575","predicate":"langPackStringPluralized","params":[{"name":"flags","type":"#"},{"name":"key","type":"string"},{"name":"zero_value","type":"flags.0?string"},{"name":"one_value","type":"flags.1?string"},{"name":"two_value","type":"flags.2?string"},{"name":"few_value","type":"flags.3?string"},{"name":"many_value","type":"flags.4?string"},{"name":"other_value","type":"string"}],"type":"LangPackString"},{"id":"695856818","predicate":"langPackStringDeleted","params":[{"name":"key","type":"string"}],"type":"LangPackString"},{"id":"-209337866","predicate":"langPackDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"strings","type":"Vector"}],"type":"LangPackDifference"},{"id":"-288727837","predicate":"langPackLanguage","params":[{"name":"flags","type":"#"},{"name":"official","type":"flags.0?true"},{"name":"rtl","type":"flags.2?true"},{"name":"beta","type":"flags.3?true"},{"name":"name","type":"string"},{"name":"native_name","type":"string"},{"name":"lang_code","type":"string"},{"name":"base_lang_code","type":"flags.1?string"},{"name":"plural_code","type":"string"},{"name":"strings_count","type":"int"},{"name":"translated_count","type":"int"},{"name":"translations_url","type":"string"}],"type":"LangPackLanguage"},{"id":"1180041828","predicate":"updateLangPackTooLong","params":[{"name":"lang_code","type":"string"}],"type":"Update"},{"id":"1442983757","predicate":"updateLangPack","params":[{"name":"difference","type":"LangPackDifference"}],"type":"Update"},{"id":"885242707","predicate":"channelParticipantAdmin","params":[{"name":"flags","type":"#"},{"name":"can_edit","type":"flags.0?true"},{"name":"self","type":"flags.1?true"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"flags.1?long"},{"name":"promoted_by","type":"long"},{"name":"date","type":"int"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.2?string"}],"type":"ChannelParticipant"},{"id":"1844969806","predicate":"channelParticipantBanned","params":[{"name":"flags","type":"#"},{"name":"left","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"kicked_by","type":"long"},{"name":"date","type":"int"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"ChannelParticipant"},{"id":"338142689","predicate":"channelParticipantsBanned","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"106343499","predicate":"channelParticipantsSearch","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-421545947","predicate":"channelAdminLogEventActionChangeTitle","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1427671598","predicate":"channelAdminLogEventActionChangeAbout","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1783299128","predicate":"channelAdminLogEventActionChangeUsername","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1129042607","predicate":"channelAdminLogEventActionChangePhoto","params":[{"name":"prev_photo","type":"Photo"},{"name":"new_photo","type":"Photo"}],"type":"ChannelAdminLogEventAction"},{"id":"460916654","predicate":"channelAdminLogEventActionToggleInvites","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"648939889","predicate":"channelAdminLogEventActionToggleSignatures","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-370660328","predicate":"channelAdminLogEventActionUpdatePinned","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1889215493","predicate":"channelAdminLogEventActionEditMessage","params":[{"name":"prev_message","type":"Message"},{"name":"new_message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1121994683","predicate":"channelAdminLogEventActionDeleteMessage","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"405815507","predicate":"channelAdminLogEventActionParticipantJoin","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-124291086","predicate":"channelAdminLogEventActionParticipantLeave","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-484690728","predicate":"channelAdminLogEventActionParticipantInvite","params":[{"name":"participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-422036098","predicate":"channelAdminLogEventActionParticipantToggleBan","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-714643696","predicate":"channelAdminLogEventActionParticipantToggleAdmin","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"531458253","predicate":"channelAdminLogEvent","params":[{"name":"id","type":"long"},{"name":"date","type":"int"},{"name":"user_id","type":"long"},{"name":"action","type":"ChannelAdminLogEventAction"}],"type":"ChannelAdminLogEvent"},{"id":"-309659827","predicate":"channels.adminLogResults","params":[{"name":"events","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.AdminLogResults"},{"id":"-368018716","predicate":"channelAdminLogEventsFilter","params":[{"name":"flags","type":"#"},{"name":"join","type":"flags.0?true"},{"name":"leave","type":"flags.1?true"},{"name":"invite","type":"flags.2?true"},{"name":"ban","type":"flags.3?true"},{"name":"unban","type":"flags.4?true"},{"name":"kick","type":"flags.5?true"},{"name":"unkick","type":"flags.6?true"},{"name":"promote","type":"flags.7?true"},{"name":"demote","type":"flags.8?true"},{"name":"info","type":"flags.9?true"},{"name":"settings","type":"flags.10?true"},{"name":"pinned","type":"flags.11?true"},{"name":"edit","type":"flags.12?true"},{"name":"delete","type":"flags.13?true"},{"name":"group_call","type":"flags.14?true"},{"name":"invites","type":"flags.15?true"},{"name":"send","type":"flags.16?true"}],"type":"ChannelAdminLogEventsFilter"},{"id":"511092620","predicate":"topPeerCategoryPhoneCalls","params":[],"type":"TopPeerCategory"},{"id":"-2143067670","predicate":"pageBlockAudio","params":[{"name":"audio_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1558266229","predicate":"popularContact","params":[{"name":"client_id","type":"long"},{"name":"importers","type":"int"}],"type":"PopularContact"},{"id":"1200788123","predicate":"messageActionScreenshotTaken","params":[],"type":"MessageAction"},{"id":"-1634752813","predicate":"messages.favedStickersNotModified","params":[],"type":"messages.FavedStickers"},{"id":"750063767","predicate":"messages.favedStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"}],"type":"messages.FavedStickers"},{"id":"-451831443","predicate":"updateFavedStickers","params":[],"type":"Update"},{"id":"1153291573","predicate":"updateChannelReadMessagesContents","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-1040652646","predicate":"inputMessagesFilterMyMentions","params":[],"type":"MessagesFilter"},{"id":"1887741886","predicate":"updateContactsReset","params":[],"type":"Update"},{"id":"-1312568665","predicate":"channelAdminLogEventActionChangeStickerSet","params":[{"name":"prev_stickerset","type":"InputStickerSet"},{"name":"new_stickerset","type":"InputStickerSet"}],"type":"ChannelAdminLogEventAction"},{"id":"-85549226","predicate":"messageActionCustomAction","params":[{"name":"message","type":"string"}],"type":"MessageAction"},{"id":"178373535","predicate":"inputPaymentCredentialsApplePay","params":[{"name":"payment_data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-419271411","predicate":"inputMessagesFilterGeo","params":[],"type":"MessagesFilter"},{"id":"-530392189","predicate":"inputMessagesFilterContacts","params":[],"type":"MessagesFilter"},{"id":"-1304443240","predicate":"updateChannelAvailableMessages","params":[{"name":"channel_id","type":"long"},{"name":"available_min_id","type":"int"}],"type":"Update"},{"id":"1599903217","predicate":"channelAdminLogEventActionTogglePreHistoryHidden","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1759532989","predicate":"inputMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"stopped","type":"flags.0?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.2?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"}],"type":"InputMedia"},{"id":"-1186937242","predicate":"messageMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"int"},{"name":"proximity_notification_radius","type":"flags.1?int"}],"type":"MessageMedia"},{"id":"1189204285","predicate":"recentMeUrlUnknown","params":[{"name":"url","type":"string"}],"type":"RecentMeUrl"},{"id":"-1188296222","predicate":"recentMeUrlUser","params":[{"name":"url","type":"string"},{"name":"user_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-1294306862","predicate":"recentMeUrlChat","params":[{"name":"url","type":"string"},{"name":"chat_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-347535331","predicate":"recentMeUrlChatInvite","params":[{"name":"url","type":"string"},{"name":"chat_invite","type":"ChatInvite"}],"type":"RecentMeUrl"},{"id":"-1140172836","predicate":"recentMeUrlStickerSet","params":[{"name":"url","type":"string"},{"name":"set","type":"StickerSetCovered"}],"type":"RecentMeUrl"},{"id":"235081943","predicate":"help.recentMeUrls","params":[{"name":"urls","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"help.RecentMeUrls"},{"id":"-266911767","predicate":"channels.channelParticipantsNotModified","params":[],"type":"channels.ChannelParticipants"},{"id":"1951620897","predicate":"messages.messagesNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Messages"},{"id":"482797855","predicate":"inputSingleMedia","params":[{"name":"flags","type":"#"},{"name":"media","type":"InputMedia"},{"name":"random_id","type":"long"},{"name":"message","type":"string"},{"name":"entities","type":"flags.0?Vector"}],"type":"InputSingleMedia"},{"id":"-1493633966","predicate":"webAuthorization","params":[{"name":"hash","type":"long"},{"name":"bot_id","type":"long"},{"name":"domain","type":"string"},{"name":"browser","type":"string"},{"name":"platform","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"region","type":"string"}],"type":"WebAuthorization"},{"id":"-313079300","predicate":"account.webAuthorizations","params":[{"name":"authorizations","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.WebAuthorizations"},{"id":"-1502174430","predicate":"inputMessageID","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-1160215659","predicate":"inputMessageReplyTo","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-2037963464","predicate":"inputMessagePinned","params":[],"type":"InputMessage"},{"id":"-1687559349","predicate":"messageEntityPhone","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1280209983","predicate":"messageEntityCashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1410748418","predicate":"messageActionBotAllowed","params":[{"name":"domain","type":"string"}],"type":"MessageAction"},{"id":"-55902537","predicate":"inputDialogPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputDialogPeer"},{"id":"-445792507","predicate":"dialogPeer","params":[{"name":"peer","type":"Peer"}],"type":"DialogPeer"},{"id":"223655517","predicate":"messages.foundStickerSetsNotModified","params":[],"type":"messages.FoundStickerSets"},{"id":"-1963942446","predicate":"messages.foundStickerSets","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.FoundStickerSets"},{"id":"1648543603","predicate":"fileHash","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"bytes"}],"type":"FileHash"},{"id":"-104284986","predicate":"webDocumentNoProxy","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"1968737087","predicate":"inputClientProxy","params":[{"name":"address","type":"string"},{"name":"port","type":"int"}],"type":"InputClientProxy"},{"id":"-483352705","predicate":"help.termsOfServiceUpdateEmpty","params":[{"name":"expires","type":"int"}],"type":"help.TermsOfServiceUpdate"},{"id":"686618977","predicate":"help.termsOfServiceUpdate","params":[{"name":"expires","type":"int"},{"name":"terms_of_service","type":"help.TermsOfService"}],"type":"help.TermsOfServiceUpdate"},{"id":"859091184","predicate":"inputSecureFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"InputSecureFile"},{"id":"1399317950","predicate":"inputSecureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputSecureFile"},{"id":"-876089816","predicate":"inputSecureFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"1679398724","predicate":"secureFileEmpty","params":[],"type":"SecureFile"},{"id":"-534283678","predicate":"secureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"date","type":"int"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureFile"},{"id":"-1964327229","predicate":"secureData","params":[{"name":"data","type":"bytes"},{"name":"data_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureData"},{"id":"2103482845","predicate":"securePlainPhone","params":[{"name":"phone","type":"string"}],"type":"SecurePlainData"},{"id":"569137759","predicate":"securePlainEmail","params":[{"name":"email","type":"string"}],"type":"SecurePlainData"},{"id":"-1658158621","predicate":"secureValueTypePersonalDetails","params":[],"type":"SecureValueType"},{"id":"1034709504","predicate":"secureValueTypePassport","params":[],"type":"SecureValueType"},{"id":"115615172","predicate":"secureValueTypeDriverLicense","params":[],"type":"SecureValueType"},{"id":"-1596951477","predicate":"secureValueTypeIdentityCard","params":[],"type":"SecureValueType"},{"id":"-1717268701","predicate":"secureValueTypeInternalPassport","params":[],"type":"SecureValueType"},{"id":"-874308058","predicate":"secureValueTypeAddress","params":[],"type":"SecureValueType"},{"id":"-63531698","predicate":"secureValueTypeUtilityBill","params":[],"type":"SecureValueType"},{"id":"-1995211763","predicate":"secureValueTypeBankStatement","params":[],"type":"SecureValueType"},{"id":"-1954007928","predicate":"secureValueTypeRentalAgreement","params":[],"type":"SecureValueType"},{"id":"-1713143702","predicate":"secureValueTypePassportRegistration","params":[],"type":"SecureValueType"},{"id":"-368907213","predicate":"secureValueTypeTemporaryRegistration","params":[],"type":"SecureValueType"},{"id":"-1289704741","predicate":"secureValueTypePhone","params":[],"type":"SecureValueType"},{"id":"-1908627474","predicate":"secureValueTypeEmail","params":[],"type":"SecureValueType"},{"id":"411017418","predicate":"secureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?SecureFile"},{"name":"reverse_side","type":"flags.2?SecureFile"},{"name":"selfie","type":"flags.3?SecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"},{"name":"hash","type":"bytes"}],"type":"SecureValue"},{"id":"-618540889","predicate":"inputSecureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?InputSecureFile"},{"name":"reverse_side","type":"flags.2?InputSecureFile"},{"name":"selfie","type":"flags.3?InputSecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"}],"type":"InputSecureValue"},{"id":"-316748368","predicate":"secureValueHash","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"}],"type":"SecureValueHash"},{"id":"-391902247","predicate":"secureValueErrorData","params":[{"name":"type","type":"SecureValueType"},{"name":"data_hash","type":"bytes"},{"name":"field","type":"string"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"12467706","predicate":"secureValueErrorFrontSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2037765467","predicate":"secureValueErrorReverseSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-449327402","predicate":"secureValueErrorSelfie","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"2054162547","predicate":"secureValueErrorFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"1717706985","predicate":"secureValueErrorFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"871426631","predicate":"secureCredentialsEncrypted","params":[{"name":"data","type":"bytes"},{"name":"hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureCredentialsEncrypted"},{"id":"-1389486888","predicate":"account.authorizationForm","params":[{"name":"flags","type":"#"},{"name":"required_types","type":"Vector"},{"name":"values","type":"Vector"},{"name":"errors","type":"Vector"},{"name":"users","type":"Vector"},{"name":"privacy_policy_url","type":"flags.0?string"}],"type":"account.AuthorizationForm"},{"id":"-2128640689","predicate":"account.sentEmailCode","params":[{"name":"email_pattern","type":"string"},{"name":"length","type":"int"}],"type":"account.SentEmailCode"},{"id":"455635795","predicate":"messageActionSecureValuesSentMe","params":[{"name":"values","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"MessageAction"},{"id":"-648257196","predicate":"messageActionSecureValuesSent","params":[{"name":"types","type":"Vector"}],"type":"MessageAction"},{"id":"1722786150","predicate":"help.deepLinkInfoEmpty","params":[],"type":"help.DeepLinkInfo"},{"id":"1783556146","predicate":"help.deepLinkInfo","params":[{"name":"flags","type":"#"},{"name":"update_app","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"help.DeepLinkInfo"},{"id":"289586518","predicate":"savedPhoneContact","params":[{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"date","type":"int"}],"type":"SavedContact"},{"id":"1304052993","predicate":"account.takeout","params":[{"name":"id","type":"long"}],"type":"account.Takeout"},{"id":"700340377","predicate":"inputTakeoutFileLocation","params":[],"type":"InputFileLocation"},{"id":"-513517117","predicate":"updateDialogUnreadMark","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-253500010","predicate":"messages.dialogsNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Dialogs"},{"id":"-1625153079","predicate":"inputWebFileGeoPointLocation","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"access_hash","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"zoom","type":"int"},{"name":"scale","type":"int"}],"type":"InputWebFileLocation"},{"id":"-1255369827","predicate":"contacts.topPeersDisabled","params":[],"type":"contacts.TopPeers"},{"id":"-1685456582","predicate":"inputReportReasonCopyright","params":[],"type":"ReportReason"},{"id":"-732254058","predicate":"passwordKdfAlgoUnknown","params":[],"type":"PasswordKdfAlgo"},{"id":"4883767","predicate":"securePasswordKdfAlgoUnknown","params":[],"type":"SecurePasswordKdfAlgo"},{"id":"-1141711456","predicate":"securePasswordKdfAlgoPBKDF2HMACSHA512iter100000","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"-2042159726","predicate":"securePasswordKdfAlgoSHA512","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"354925740","predicate":"secureSecretSettings","params":[{"name":"secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_secret","type":"bytes"},{"name":"secure_secret_id","type":"long"}],"type":"SecureSecretSettings"},{"id":"982592842","predicate":"passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow","params":[{"name":"salt1","type":"bytes"},{"name":"salt2","type":"bytes"},{"name":"g","type":"int"},{"name":"p","type":"bytes"}],"type":"PasswordKdfAlgo"},{"id":"-1736378792","predicate":"inputCheckPasswordEmpty","params":[],"type":"InputCheckPasswordSRP"},{"id":"-763367294","predicate":"inputCheckPasswordSRP","params":[{"name":"srp_id","type":"long"},{"name":"A","type":"bytes"},{"name":"M1","type":"bytes"}],"type":"InputCheckPasswordSRP"},{"id":"-2036501105","predicate":"secureValueError","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-1592506512","predicate":"secureValueErrorTranslationFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"878931416","predicate":"secureValueErrorTranslationFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2103600678","predicate":"secureRequiredType","params":[{"name":"flags","type":"#"},{"name":"native_names","type":"flags.0?true"},{"name":"selfie_required","type":"flags.1?true"},{"name":"translation_required","type":"flags.2?true"},{"name":"type","type":"SecureValueType"}],"type":"SecureRequiredType"},{"id":"41187252","predicate":"secureRequiredTypeOneOf","params":[{"name":"types","type":"Vector"}],"type":"SecureRequiredType"},{"id":"-1078332329","predicate":"help.passportConfigNotModified","params":[],"type":"help.PassportConfig"},{"id":"-1600596305","predicate":"help.passportConfig","params":[{"name":"hash","type":"int"},{"name":"countries_langs","type":"DataJSON"}],"type":"help.PassportConfig"},{"id":"488313413","predicate":"inputAppEvent","params":[{"name":"time","type":"double"},{"name":"type","type":"string"},{"name":"peer","type":"long"},{"name":"data","type":"JSONValue"}],"type":"InputAppEvent"},{"id":"-1059185703","predicate":"jsonObjectValue","params":[{"name":"key","type":"string"},{"name":"value","type":"JSONValue"}],"type":"JSONObjectValue"},{"id":"1064139624","predicate":"jsonNull","params":[],"type":"JSONValue"},{"id":"-952869270","predicate":"jsonBool","params":[{"name":"value","type":"Bool"}],"type":"JSONValue"},{"id":"736157604","predicate":"jsonNumber","params":[{"name":"value","type":"double"}],"type":"JSONValue"},{"id":"-1222740358","predicate":"jsonString","params":[{"name":"value","type":"string"}],"type":"JSONValue"},{"id":"-146520221","predicate":"jsonArray","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1715350371","predicate":"jsonObject","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1311015810","predicate":"inputNotifyBroadcasts","params":[],"type":"InputNotifyPeer"},{"id":"-703403793","predicate":"notifyBroadcasts","params":[],"type":"NotifyPeer"},{"id":"-311786236","predicate":"textSubscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-939827711","predicate":"textSuperscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"55281185","predicate":"textMarked","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"483104362","predicate":"textPhone","params":[{"name":"text","type":"RichText"},{"name":"phone","type":"string"}],"type":"RichText"},{"id":"136105807","predicate":"textImage","params":[{"name":"document_id","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"RichText"},{"id":"504660880","predicate":"pageBlockKicker","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"878078826","predicate":"pageTableCell","params":[{"name":"flags","type":"#"},{"name":"header","type":"flags.0?true"},{"name":"align_center","type":"flags.3?true"},{"name":"align_right","type":"flags.4?true"},{"name":"valign_middle","type":"flags.5?true"},{"name":"valign_bottom","type":"flags.6?true"},{"name":"text","type":"flags.7?RichText"},{"name":"colspan","type":"flags.1?int"},{"name":"rowspan","type":"flags.2?int"}],"type":"PageTableCell"},{"id":"-524237339","predicate":"pageTableRow","params":[{"name":"cells","type":"Vector"}],"type":"PageTableRow"},{"id":"-1085412734","predicate":"pageBlockTable","params":[{"name":"flags","type":"#"},{"name":"bordered","type":"flags.0?true"},{"name":"striped","type":"flags.1?true"},{"name":"title","type":"RichText"},{"name":"rows","type":"Vector"}],"type":"PageBlock"},{"id":"1869903447","predicate":"pageCaption","params":[{"name":"text","type":"RichText"},{"name":"credit","type":"RichText"}],"type":"PageCaption"},{"id":"-1188055347","predicate":"pageListItemText","params":[{"name":"text","type":"RichText"}],"type":"PageListItem"},{"id":"635466748","predicate":"pageListItemBlocks","params":[{"name":"blocks","type":"Vector"}],"type":"PageListItem"},{"id":"1577484359","predicate":"pageListOrderedItemText","params":[{"name":"num","type":"string"},{"name":"text","type":"RichText"}],"type":"PageListOrderedItem"},{"id":"-1730311882","predicate":"pageListOrderedItemBlocks","params":[{"name":"num","type":"string"},{"name":"blocks","type":"Vector"}],"type":"PageListOrderedItem"},{"id":"-1702174239","predicate":"pageBlockOrderedList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"1987480557","predicate":"pageBlockDetails","params":[{"name":"flags","type":"#"},{"name":"open","type":"flags.0?true"},{"name":"blocks","type":"Vector"},{"name":"title","type":"RichText"}],"type":"PageBlock"},{"id":"-1282352120","predicate":"pageRelatedArticle","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"title","type":"flags.0?string"},{"name":"description","type":"flags.1?string"},{"name":"photo_id","type":"flags.2?long"},{"name":"author","type":"flags.3?string"},{"name":"published_date","type":"flags.4?int"}],"type":"PageRelatedArticle"},{"id":"370236054","predicate":"pageBlockRelatedArticles","params":[{"name":"title","type":"RichText"},{"name":"articles","type":"Vector"}],"type":"PageBlock"},{"id":"-1538310410","predicate":"pageBlockMap","params":[{"name":"geo","type":"GeoPoint"},{"name":"zoom","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-1738178803","predicate":"page","params":[{"name":"flags","type":"#"},{"name":"part","type":"flags.0?true"},{"name":"rtl","type":"flags.1?true"},{"name":"v2","type":"flags.2?true"},{"name":"url","type":"string"},{"name":"blocks","type":"Vector"},{"name":"photos","type":"Vector"},{"name":"documents","type":"Vector"},{"name":"views","type":"flags.3?int"}],"type":"Page"},{"id":"-610373422","predicate":"inputPrivacyKeyPhoneP2P","params":[],"type":"InputPrivacyKey"},{"id":"961092808","predicate":"privacyKeyPhoneP2P","params":[],"type":"PrivacyKey"},{"id":"894777186","predicate":"textAnchor","params":[{"name":"text","type":"RichText"},{"name":"name","type":"string"}],"type":"RichText"},{"id":"-1945767479","predicate":"help.supportName","params":[{"name":"name","type":"string"}],"type":"help.SupportName"},{"id":"-206688531","predicate":"help.userInfoEmpty","params":[],"type":"help.UserInfo"},{"id":"32192344","predicate":"help.userInfo","params":[{"name":"message","type":"string"},{"name":"entities","type":"Vector"},{"name":"author","type":"string"},{"name":"date","type":"int"}],"type":"help.UserInfo"},{"id":"-202219658","predicate":"messageActionContactSignUp","params":[],"type":"MessageAction"},{"id":"-1398708869","predicate":"updateMessagePoll","params":[{"name":"flags","type":"#"},{"name":"poll_id","type":"long"},{"name":"poll","type":"flags.0?Poll"},{"name":"results","type":"PollResults"}],"type":"Update"},{"id":"1823064809","predicate":"pollAnswer","params":[{"name":"text","type":"string"},{"name":"option","type":"bytes"}],"type":"PollAnswer"},{"id":"-2032041631","predicate":"poll","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"closed","type":"flags.0?true"},{"name":"public_voters","type":"flags.1?true"},{"name":"multiple_choice","type":"flags.2?true"},{"name":"quiz","type":"flags.3?true"},{"name":"question","type":"string"},{"name":"answers","type":"Vector"},{"name":"close_period","type":"flags.4?int"},{"name":"close_date","type":"flags.5?int"}],"type":"Poll"},{"id":"997055186","predicate":"pollAnswerVoters","params":[{"name":"flags","type":"#"},{"name":"chosen","type":"flags.0?true"},{"name":"correct","type":"flags.1?true"},{"name":"option","type":"bytes"},{"name":"voters","type":"int"}],"type":"PollAnswerVoters"},{"id":"-591909213","predicate":"pollResults","params":[{"name":"flags","type":"#"},{"name":"min","type":"flags.0?true"},{"name":"results","type":"flags.1?Vector"},{"name":"total_voters","type":"flags.2?int"},{"name":"recent_voters","type":"flags.3?Vector"},{"name":"solution","type":"flags.4?string"},{"name":"solution_entities","type":"flags.4?Vector"}],"type":"PollResults"},{"id":"261416433","predicate":"inputMediaPoll","params":[{"name":"flags","type":"#"},{"name":"poll","type":"Poll"},{"name":"correct_answers","type":"flags.0?Vector"},{"name":"solution","type":"flags.1?string"},{"name":"solution_entities","type":"flags.1?Vector"}],"type":"InputMedia"},{"id":"1272375192","predicate":"messageMediaPoll","params":[{"name":"poll","type":"Poll"},{"name":"results","type":"PollResults"}],"type":"MessageMedia"},{"id":"-264117680","predicate":"chatOnlines","params":[{"name":"onlines","type":"int"}],"type":"ChatOnlines"},{"id":"1202287072","predicate":"statsURL","params":[{"name":"url","type":"string"}],"type":"StatsURL"},{"id":"-525288402","predicate":"photoStrippedSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"1605510357","predicate":"chatAdminRights","params":[{"name":"flags","type":"#"},{"name":"change_info","type":"flags.0?true"},{"name":"post_messages","type":"flags.1?true"},{"name":"edit_messages","type":"flags.2?true"},{"name":"delete_messages","type":"flags.3?true"},{"name":"ban_users","type":"flags.4?true"},{"name":"invite_users","type":"flags.5?true"},{"name":"pin_messages","type":"flags.7?true"},{"name":"add_admins","type":"flags.9?true"},{"name":"anonymous","type":"flags.10?true"},{"name":"manage_call","type":"flags.11?true"},{"name":"other","type":"flags.12?true"}],"type":"ChatAdminRights"},{"id":"-1626209256","predicate":"chatBannedRights","params":[{"name":"flags","type":"#"},{"name":"view_messages","type":"flags.0?true"},{"name":"send_messages","type":"flags.1?true"},{"name":"send_media","type":"flags.2?true"},{"name":"send_stickers","type":"flags.3?true"},{"name":"send_gifs","type":"flags.4?true"},{"name":"send_games","type":"flags.5?true"},{"name":"send_inline","type":"flags.6?true"},{"name":"embed_links","type":"flags.7?true"},{"name":"send_polls","type":"flags.8?true"},{"name":"change_info","type":"flags.10?true"},{"name":"invite_users","type":"flags.15?true"},{"name":"pin_messages","type":"flags.17?true"},{"name":"until_date","type":"int"}],"type":"ChatBannedRights"},{"id":"1421875280","predicate":"updateChatDefaultBannedRights","params":[{"name":"peer","type":"Peer"},{"name":"default_banned_rights","type":"ChatBannedRights"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-433014407","predicate":"inputWallPaper","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputWallPaper"},{"id":"1913199744","predicate":"inputWallPaperSlug","params":[{"name":"slug","type":"string"}],"type":"InputWallPaper"},{"id":"-1150621555","predicate":"channelParticipantsContacts","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"771095562","predicate":"channelAdminLogEventActionDefaultBannedRights","params":[{"name":"prev_banned_rights","type":"ChatBannedRights"},{"name":"new_banned_rights","type":"ChatBannedRights"}],"type":"ChannelAdminLogEventAction"},{"id":"-1895328189","predicate":"channelAdminLogEventActionStopPoll","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"471437699","predicate":"account.wallPapersNotModified","params":[],"type":"account.WallPapers"},{"id":"-842824308","predicate":"account.wallPapers","params":[{"name":"hash","type":"long"},{"name":"wallpapers","type":"Vector"}],"type":"account.WallPapers"},{"id":"-1973130814","predicate":"codeSettings","params":[{"name":"flags","type":"#"},{"name":"allow_flashcall","type":"flags.0?true"},{"name":"current_number","type":"flags.1?true"},{"name":"allow_app_hash","type":"flags.4?true"},{"name":"allow_missed_call","type":"flags.5?true"},{"name":"logout_tokens","type":"flags.6?Vector"}],"type":"CodeSettings"},{"id":"499236004","predicate":"wallPaperSettings","params":[{"name":"flags","type":"#"},{"name":"blur","type":"flags.1?true"},{"name":"motion","type":"flags.2?true"},{"name":"background_color","type":"flags.0?int"},{"name":"second_background_color","type":"flags.4?int"},{"name":"third_background_color","type":"flags.5?int"},{"name":"fourth_background_color","type":"flags.6?int"},{"name":"intensity","type":"flags.3?int"},{"name":"rotation","type":"flags.4?int"}],"type":"WallPaperSettings"},{"id":"-532532493","predicate":"autoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"disabled","type":"flags.0?true"},{"name":"video_preload_large","type":"flags.1?true"},{"name":"audio_preload_next","type":"flags.2?true"},{"name":"phonecalls_less_data","type":"flags.3?true"},{"name":"photo_size_max","type":"int"},{"name":"video_size_max","type":"int"},{"name":"file_size_max","type":"int"},{"name":"video_upload_maxbitrate","type":"int"}],"type":"AutoDownloadSettings"},{"id":"1674235686","predicate":"account.autoDownloadSettings","params":[{"name":"low","type":"AutoDownloadSettings"},{"name":"medium","type":"AutoDownloadSettings"},{"name":"high","type":"AutoDownloadSettings"}],"type":"account.AutoDownloadSettings"},{"id":"-709641735","predicate":"emojiKeyword","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"594408994","predicate":"emojiKeywordDeleted","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"1556570557","predicate":"emojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"keywords","type":"Vector"}],"type":"EmojiKeywordsDifference"},{"id":"-1519029347","predicate":"emojiURL","params":[{"name":"url","type":"string"}],"type":"EmojiURL"},{"id":"-1275374751","predicate":"emojiLanguage","params":[{"name":"lang_code","type":"string"}],"type":"EmojiLanguage"},{"id":"-1529000952","predicate":"inputPrivacyKeyForwards","params":[],"type":"InputPrivacyKey"},{"id":"1777096355","predicate":"privacyKeyForwards","params":[],"type":"PrivacyKey"},{"id":"1461304012","predicate":"inputPrivacyKeyProfilePhoto","params":[],"type":"InputPrivacyKey"},{"id":"-1777000467","predicate":"privacyKeyProfilePhoto","params":[],"type":"PrivacyKey"},{"id":"1075322878","predicate":"inputPhotoFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"-667654413","predicate":"inputPhotoLegacyFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"InputFileLocation"},{"id":"925204121","predicate":"inputPeerPhotoFileLocation","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"long"}],"type":"InputFileLocation"},{"id":"-1652231205","predicate":"inputStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb_version","type":"int"}],"type":"InputFileLocation"},{"id":"-11252123","predicate":"folder","params":[{"name":"flags","type":"#"},{"name":"autofill_new_broadcasts","type":"flags.0?true"},{"name":"autofill_public_groups","type":"flags.1?true"},{"name":"autofill_new_correspondents","type":"flags.2?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"photo","type":"flags.3?ChatPhoto"}],"type":"Folder"},{"id":"1908216652","predicate":"dialogFolder","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"folder","type":"Folder"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"unread_muted_peers_count","type":"int"},{"name":"unread_unmuted_peers_count","type":"int"},{"name":"unread_muted_messages_count","type":"int"},{"name":"unread_unmuted_messages_count","type":"int"}],"type":"Dialog"},{"id":"1684014375","predicate":"inputDialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"InputDialogPeer"},{"id":"1363483106","predicate":"dialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"DialogPeer"},{"id":"-70073706","predicate":"inputFolderPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"folder_id","type":"int"}],"type":"InputFolderPeer"},{"id":"-373643672","predicate":"folderPeer","params":[{"name":"peer","type":"Peer"},{"name":"folder_id","type":"int"}],"type":"FolderPeer"},{"id":"422972864","predicate":"updateFolderPeers","params":[{"name":"folder_peers","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"497305826","predicate":"inputUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputUser"},{"id":"1536380829","predicate":"inputChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputChannel"},{"id":"-1468331492","predicate":"inputPeerUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputPeer"},{"id":"-1121318848","predicate":"inputPeerChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputPeer"},{"id":"55761658","predicate":"inputPrivacyKeyPhoneNumber","params":[],"type":"InputPrivacyKey"},{"id":"-778378131","predicate":"privacyKeyPhoneNumber","params":[],"type":"PrivacyKey"},{"id":"-1472172887","predicate":"topPeerCategoryForwardUsers","params":[],"type":"TopPeerCategory"},{"id":"-68239120","predicate":"topPeerCategoryForwardChats","params":[],"type":"TopPeerCategory"},{"id":"84703944","predicate":"channelAdminLogEventActionChangeLinkedChat","params":[{"name":"prev_value","type":"long"},{"name":"new_value","type":"long"}],"type":"ChannelAdminLogEventAction"},{"id":"-398136321","predicate":"messages.searchCounter","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"filter","type":"MessagesFilter"},{"name":"count","type":"int"}],"type":"messages.SearchCounter"},{"id":"280464681","predicate":"keyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.0?string"},{"name":"url","type":"string"},{"name":"button_id","type":"int"}],"type":"KeyboardButton"},{"id":"-802258988","predicate":"inputKeyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.1?string"},{"name":"url","type":"string"},{"name":"bot","type":"InputUser"}],"type":"KeyboardButton"},{"id":"-1831650802","predicate":"urlAuthResultRequest","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"bot","type":"User"},{"name":"domain","type":"string"}],"type":"UrlAuthResult"},{"id":"-1886646706","predicate":"urlAuthResultAccepted","params":[{"name":"url","type":"string"}],"type":"UrlAuthResult"},{"id":"-1445536993","predicate":"urlAuthResultDefault","params":[],"type":"UrlAuthResult"},{"id":"-2079962673","predicate":"inputPrivacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-380694650","predicate":"inputPrivacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"1796427406","predicate":"privacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"1103656293","predicate":"privacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"-1672577397","predicate":"messageEntityUnderline","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1090087980","predicate":"messageEntityStrike","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"34469328","predicate":"messageEntityBlockquote","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1786671974","predicate":"updatePeerSettings","params":[{"name":"peer","type":"Peer"},{"name":"settings","type":"PeerSettings"}],"type":"Update"},{"id":"-1078612597","predicate":"channelLocationEmpty","params":[],"type":"ChannelLocation"},{"id":"547062491","predicate":"channelLocation","params":[{"name":"geo_point","type":"GeoPoint"},{"name":"address","type":"string"}],"type":"ChannelLocation"},{"id":"-901375139","predicate":"peerLocated","params":[{"name":"peer","type":"Peer"},{"name":"expires","type":"int"},{"name":"distance","type":"int"}],"type":"PeerLocated"},{"id":"-1263546448","predicate":"updatePeerLocated","params":[{"name":"peers","type":"Vector"}],"type":"Update"},{"id":"241923758","predicate":"channelAdminLogEventActionChangeLocation","params":[{"name":"prev_value","type":"ChannelLocation"},{"name":"new_value","type":"ChannelLocation"}],"type":"ChannelAdminLogEventAction"},{"id":"-606798099","predicate":"inputReportReasonGeoIrrelevant","params":[],"type":"ReportReason"},{"id":"1401984889","predicate":"channelAdminLogEventActionToggleSlowMode","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"1148485274","predicate":"auth.authorizationSignUpRequired","params":[{"name":"flags","type":"#"},{"name":"terms_of_service","type":"flags.0?help.TermsOfService"}],"type":"auth.Authorization"},{"id":"-666824391","predicate":"payments.paymentVerificationNeeded","params":[{"name":"url","type":"string"}],"type":"payments.PaymentResult"},{"id":"42402760","predicate":"inputStickerSetAnimatedEmoji","params":[],"type":"InputStickerSet"},{"id":"967122427","predicate":"updateNewScheduledMessage","params":[{"name":"message","type":"Message"}],"type":"Update"},{"id":"-1870238482","predicate":"updateDeleteScheduledMessages","params":[{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-797791052","predicate":"restrictionReason","params":[{"name":"platform","type":"string"},{"name":"reason","type":"string"},{"name":"text","type":"string"}],"type":"RestrictionReason"},{"id":"1012306921","predicate":"inputTheme","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputTheme"},{"id":"-175567375","predicate":"inputThemeSlug","params":[{"name":"slug","type":"string"}],"type":"InputTheme"},{"id":"-1609668650","predicate":"theme","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"for_chat","type":"flags.5?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?Document"},{"name":"settings","type":"flags.3?Vector"},{"name":"emoticon","type":"flags.6?string"},{"name":"installs_count","type":"flags.4?int"}],"type":"Theme"},{"id":"-199313886","predicate":"account.themesNotModified","params":[],"type":"account.Themes"},{"id":"-1707242387","predicate":"account.themes","params":[{"name":"hash","type":"long"},{"name":"themes","type":"Vector"}],"type":"account.Themes"},{"id":"-2112423005","predicate":"updateTheme","params":[{"name":"theme","type":"Theme"}],"type":"Update"},{"id":"-786326563","predicate":"inputPrivacyKeyAddedByPhone","params":[],"type":"InputPrivacyKey"},{"id":"1124062251","predicate":"privacyKeyAddedByPhone","params":[],"type":"PrivacyKey"},{"id":"-2027964103","predicate":"updateGeoLiveViewed","params":[{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"}],"type":"Update"},{"id":"1448076945","predicate":"updateLoginToken","params":[],"type":"Update"},{"id":"1654593920","predicate":"auth.loginToken","params":[{"name":"expires","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"110008598","predicate":"auth.loginTokenMigrateTo","params":[{"name":"dc_id","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"957176926","predicate":"auth.loginTokenSuccess","params":[{"name":"authorization","type":"auth.Authorization"}],"type":"auth.LoginToken"},{"id":"1474462241","predicate":"account.contentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"},{"name":"sensitive_can_change","type":"flags.1?true"}],"type":"account.ContentSettings"},{"id":"-1456996667","predicate":"messages.inactiveChats","params":[{"name":"dates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.InactiveChats"},{"id":"-1012849566","predicate":"baseThemeClassic","params":[],"type":"BaseTheme"},{"id":"-69724536","predicate":"baseThemeDay","params":[],"type":"BaseTheme"},{"id":"-1212997976","predicate":"baseThemeNight","params":[],"type":"BaseTheme"},{"id":"1834973166","predicate":"baseThemeTinted","params":[],"type":"BaseTheme"},{"id":"1527845466","predicate":"baseThemeArctic","params":[],"type":"BaseTheme"},{"id":"-1770371538","predicate":"inputWallPaperNoFile","params":[{"name":"id","type":"long"}],"type":"InputWallPaper"},{"id":"-528465642","predicate":"wallPaperNoFile","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"default","type":"flags.1?true"},{"name":"dark","type":"flags.4?true"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"-1881255857","predicate":"inputThemeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?InputWallPaper"},{"name":"wallpaper_settings","type":"flags.1?WallPaperSettings"}],"type":"InputThemeSettings"},{"id":"-94849324","predicate":"themeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?WallPaper"}],"type":"ThemeSettings"},{"id":"1421174295","predicate":"webPageAttributeTheme","params":[{"name":"flags","type":"#"},{"name":"documents","type":"flags.0?Vector"},{"name":"settings","type":"flags.1?ThemeSettings"}],"type":"WebPageAttribute"},{"id":"274961865","predicate":"updateMessagePollVote","params":[{"name":"poll_id","type":"long"},{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"886196148","predicate":"messageUserVote","params":[{"name":"user_id","type":"long"},{"name":"option","type":"bytes"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"1017491692","predicate":"messageUserVoteInputOption","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"-1973033641","predicate":"messageUserVoteMultiple","params":[{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"136574537","predicate":"messages.votesList","params":[{"name":"flags","type":"#"},{"name":"count","type":"int"},{"name":"votes","type":"Vector"},{"name":"users","type":"Vector"},{"name":"next_offset","type":"flags.0?string"}],"type":"messages.VotesList"},{"id":"-1144565411","predicate":"keyboardButtonRequestPoll","params":[{"name":"flags","type":"#"},{"name":"quiz","type":"flags.0?Bool"},{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1981704948","predicate":"messageEntityBankCard","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-177732982","predicate":"bankCardOpenUrl","params":[{"name":"url","type":"string"},{"name":"name","type":"string"}],"type":"BankCardOpenUrl"},{"id":"1042605427","predicate":"payments.bankCardData","params":[{"name":"title","type":"string"},{"name":"open_urls","type":"Vector"}],"type":"payments.BankCardData"},{"id":"-118740917","predicate":"peerSelfLocated","params":[{"name":"expires","type":"int"}],"type":"PeerLocated"},{"id":"1949890536","predicate":"dialogFilter","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"non_contacts","type":"flags.1?true"},{"name":"groups","type":"flags.2?true"},{"name":"broadcasts","type":"flags.3?true"},{"name":"bots","type":"flags.4?true"},{"name":"exclude_muted","type":"flags.11?true"},{"name":"exclude_read","type":"flags.12?true"},{"name":"exclude_archived","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"emoticon","type":"flags.25?string"},{"name":"pinned_peers","type":"Vector"},{"name":"include_peers","type":"Vector"},{"name":"exclude_peers","type":"Vector"}],"type":"DialogFilter"},{"id":"2004110666","predicate":"dialogFilterSuggested","params":[{"name":"filter","type":"DialogFilter"},{"name":"description","type":"string"}],"type":"DialogFilterSuggested"},{"id":"654302845","predicate":"updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Update"},{"id":"-1512627963","predicate":"updateDialogFilterOrder","params":[{"name":"order","type":"Vector"}],"type":"Update"},{"id":"889491791","predicate":"updateDialogFilters","params":[],"type":"Update"},{"id":"-1237848657","predicate":"statsDateRangeDays","params":[{"name":"min_date","type":"int"},{"name":"max_date","type":"int"}],"type":"StatsDateRangeDays"},{"id":"-884757282","predicate":"statsAbsValueAndPrev","params":[{"name":"current","type":"double"},{"name":"previous","type":"double"}],"type":"StatsAbsValueAndPrev"},{"id":"-875679776","predicate":"statsPercentValue","params":[{"name":"part","type":"double"},{"name":"total","type":"double"}],"type":"StatsPercentValue"},{"id":"1244130093","predicate":"statsGraphAsync","params":[{"name":"token","type":"string"}],"type":"StatsGraph"},{"id":"-1092839390","predicate":"statsGraphError","params":[{"name":"error","type":"string"}],"type":"StatsGraph"},{"id":"-1901828938","predicate":"statsGraph","params":[{"name":"flags","type":"#"},{"name":"json","type":"DataJSON"},{"name":"zoom_token","type":"flags.0?string"}],"type":"StatsGraph"},{"id":"-1387279939","predicate":"messageInteractionCounters","params":[{"name":"msg_id","type":"int"},{"name":"views","type":"int"},{"name":"forwards","type":"int"}],"type":"MessageInteractionCounters"},{"id":"-1107852396","predicate":"stats.broadcastStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"followers","type":"StatsAbsValueAndPrev"},{"name":"views_per_post","type":"StatsAbsValueAndPrev"},{"name":"shares_per_post","type":"StatsAbsValueAndPrev"},{"name":"enabled_notifications","type":"StatsPercentValue"},{"name":"growth_graph","type":"StatsGraph"},{"name":"followers_graph","type":"StatsGraph"},{"name":"mute_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"interactions_graph","type":"StatsGraph"},{"name":"iv_interactions_graph","type":"StatsGraph"},{"name":"views_by_source_graph","type":"StatsGraph"},{"name":"new_followers_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"recent_message_interactions","type":"Vector"}],"type":"stats.BroadcastStats"},{"id":"-428884101","predicate":"inputMediaDice","params":[{"name":"emoticon","type":"string"}],"type":"InputMedia"},{"id":"1065280907","predicate":"messageMediaDice","params":[{"name":"value","type":"int"},{"name":"emoticon","type":"string"}],"type":"MessageMedia"},{"id":"-427863538","predicate":"inputStickerSetDice","params":[{"name":"emoticon","type":"string"}],"type":"InputStickerSet"},{"id":"-1728664459","predicate":"help.promoDataEmpty","params":[{"name":"expires","type":"int"}],"type":"help.PromoData"},{"id":"-1942390465","predicate":"help.promoData","params":[{"name":"flags","type":"#"},{"name":"proxy","type":"flags.0?true"},{"name":"expires","type":"int"},{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"psa_type","type":"flags.1?string"},{"name":"psa_message","type":"flags.2?string"}],"type":"help.PromoData"},{"id":"-567037804","predicate":"videoSize","params":[{"name":"flags","type":"#"},{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"video_start_ts","type":"flags.0?double"}],"type":"VideoSize"},{"id":"643940105","predicate":"updatePhoneCallSignalingData","params":[{"name":"phone_call_id","type":"long"},{"name":"data","type":"bytes"}],"type":"Update"},{"id":"1634294960","predicate":"chatInvitePeek","params":[{"name":"chat","type":"Chat"},{"name":"expires","type":"int"}],"type":"ChatInvite"},{"id":"-1660637285","predicate":"statsGroupTopPoster","params":[{"name":"user_id","type":"long"},{"name":"messages","type":"int"},{"name":"avg_chars","type":"int"}],"type":"StatsGroupTopPoster"},{"id":"-682079097","predicate":"statsGroupTopAdmin","params":[{"name":"user_id","type":"long"},{"name":"deleted","type":"int"},{"name":"kicked","type":"int"},{"name":"banned","type":"int"}],"type":"StatsGroupTopAdmin"},{"id":"1398765469","predicate":"statsGroupTopInviter","params":[{"name":"user_id","type":"long"},{"name":"invitations","type":"int"}],"type":"StatsGroupTopInviter"},{"id":"-276825834","predicate":"stats.megagroupStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"members","type":"StatsAbsValueAndPrev"},{"name":"messages","type":"StatsAbsValueAndPrev"},{"name":"viewers","type":"StatsAbsValueAndPrev"},{"name":"posters","type":"StatsAbsValueAndPrev"},{"name":"growth_graph","type":"StatsGraph"},{"name":"members_graph","type":"StatsGraph"},{"name":"new_members_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"messages_graph","type":"StatsGraph"},{"name":"actions_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"weekdays_graph","type":"StatsGraph"},{"name":"top_posters","type":"Vector"},{"name":"top_admins","type":"Vector"},{"name":"top_inviters","type":"Vector"},{"name":"users","type":"Vector"}],"type":"stats.MegagroupStats"},{"id":"-1096616924","predicate":"globalPrivacySettings","params":[{"name":"flags","type":"#"},{"name":"archive_and_mute_new_noncontact_peers","type":"flags.0?Bool"}],"type":"GlobalPrivacySettings"},{"id":"1667228533","predicate":"phoneConnectionWebrtc","params":[{"name":"flags","type":"#"},{"name":"turn","type":"flags.0?true"},{"name":"stun","type":"flags.1?true"},{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"username","type":"string"},{"name":"password","type":"string"}],"type":"PhoneConnection"},{"id":"1107543535","predicate":"help.countryCode","params":[{"name":"flags","type":"#"},{"name":"country_code","type":"string"},{"name":"prefixes","type":"flags.0?Vector"},{"name":"patterns","type":"flags.1?Vector"}],"type":"help.CountryCode"},{"id":"-1014526429","predicate":"help.country","params":[{"name":"flags","type":"#"},{"name":"hidden","type":"flags.0?true"},{"name":"iso2","type":"string"},{"name":"default_name","type":"string"},{"name":"name","type":"flags.1?string"},{"name":"country_codes","type":"Vector"}],"type":"help.Country"},{"id":"-1815339214","predicate":"help.countriesListNotModified","params":[],"type":"help.CountriesList"},{"id":"-2016381538","predicate":"help.countriesList","params":[{"name":"countries","type":"Vector"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"1163625789","predicate":"messageViews","params":[{"name":"flags","type":"#"},{"name":"views","type":"flags.0?int"},{"name":"forwards","type":"flags.1?int"},{"name":"replies","type":"flags.2?MessageReplies"}],"type":"MessageViews"},{"id":"-761649164","predicate":"updateChannelMessageForwards","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"forwards","type":"int"}],"type":"Update"},{"id":"-96535659","predicate":"photoSizeProgressive","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"sizes","type":"Vector"}],"type":"PhotoSize"},{"id":"-1228606141","predicate":"messages.messageViews","params":[{"name":"views","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.MessageViews"},{"id":"-693004986","predicate":"updateReadChannelDiscussionInbox","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"},{"name":"broadcast_id","type":"flags.0?long"},{"name":"broadcast_post","type":"flags.0?int"}],"type":"Update"},{"id":"1767677564","predicate":"updateReadChannelDiscussionOutbox","params":[{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Update"},{"id":"-1506535550","predicate":"messages.discussionMessage","params":[{"name":"flags","type":"#"},{"name":"messages","type":"Vector"},{"name":"max_id","type":"flags.0?int"},{"name":"read_inbox_max_id","type":"flags.1?int"},{"name":"read_outbox_max_id","type":"flags.2?int"},{"name":"unread_count","type":"int"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.DiscussionMessage"},{"id":"-1495959709","predicate":"messageReplyHeader","params":[{"name":"flags","type":"#"},{"name":"reply_to_msg_id","type":"int"},{"name":"reply_to_peer_id","type":"flags.0?Peer"},{"name":"reply_to_top_id","type":"flags.1?int"}],"type":"MessageReplyHeader"},{"id":"-2083123262","predicate":"messageReplies","params":[{"name":"flags","type":"#"},{"name":"comments","type":"flags.0?true"},{"name":"replies","type":"int"},{"name":"replies_pts","type":"int"},{"name":"recent_repliers","type":"flags.1?Vector"},{"name":"channel_id","type":"flags.0?long"},{"name":"max_id","type":"flags.2?int"},{"name":"read_max_id","type":"flags.3?int"}],"type":"MessageReplies"},{"id":"610945826","predicate":"updatePeerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"blocked","type":"Bool"}],"type":"Update"},{"id":"-386039788","predicate":"peerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"date","type":"int"}],"type":"PeerBlocked"},{"id":"-1937192669","predicate":"updateChannelUserTyping","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-1392895362","predicate":"inputMessageCallbackQuery","params":[{"name":"id","type":"int"},{"name":"query_id","type":"long"}],"type":"InputMessage"},{"id":"453242886","predicate":"channelParticipantLeft","params":[{"name":"peer","type":"Peer"}],"type":"ChannelParticipant"},{"id":"-531931925","predicate":"channelParticipantsMentions","params":[{"name":"flags","type":"#"},{"name":"q","type":"flags.0?string"},{"name":"top_msg_id","type":"flags.1?int"}],"type":"ChannelParticipantsFilter"},{"id":"-309990731","predicate":"updatePinnedMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1538885128","predicate":"updatePinnedChannelMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"464520273","predicate":"inputMessagesFilterPinned","params":[],"type":"MessagesFilter"},{"id":"-1986399595","predicate":"stats.messageStats","params":[{"name":"views_graph","type":"StatsGraph"}],"type":"stats.MessageStats"},{"id":"-1730095465","predicate":"messageActionGeoProximityReached","params":[{"name":"from_id","type":"Peer"},{"name":"to_id","type":"Peer"},{"name":"distance","type":"int"}],"type":"MessageAction"},{"id":"-668906175","predicate":"photoPathSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"-651419003","predicate":"speakingInGroupCallAction","params":[],"type":"SendMessageAction"},{"id":"2004925620","predicate":"groupCallDiscarded","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"duration","type":"int"}],"type":"GroupCall"},{"id":"-711498484","predicate":"groupCall","params":[{"name":"flags","type":"#"},{"name":"join_muted","type":"flags.1?true"},{"name":"can_change_join_muted","type":"flags.2?true"},{"name":"join_date_asc","type":"flags.6?true"},{"name":"schedule_start_subscribed","type":"flags.8?true"},{"name":"can_start_video","type":"flags.9?true"},{"name":"record_video_active","type":"flags.11?true"},{"name":"rtmp_stream","type":"flags.12?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"participants_count","type":"int"},{"name":"title","type":"flags.3?string"},{"name":"stream_dc_id","type":"flags.4?int"},{"name":"record_start_date","type":"flags.5?int"},{"name":"schedule_date","type":"flags.7?int"},{"name":"unmuted_video_count","type":"flags.10?int"},{"name":"unmuted_video_limit","type":"int"},{"name":"version","type":"int"}],"type":"GroupCall"},{"id":"-659913713","predicate":"inputGroupCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGroupCall"},{"id":"2047704898","predicate":"messageActionGroupCall","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"duration","type":"flags.0?int"}],"type":"MessageAction"},{"id":"1345295095","predicate":"messageActionInviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-341428482","predicate":"groupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"left","type":"flags.1?true"},{"name":"can_self_unmute","type":"flags.2?true"},{"name":"just_joined","type":"flags.4?true"},{"name":"versioned","type":"flags.5?true"},{"name":"min","type":"flags.8?true"},{"name":"muted_by_you","type":"flags.9?true"},{"name":"volume_by_admin","type":"flags.10?true"},{"name":"self","type":"flags.12?true"},{"name":"video_joined","type":"flags.15?true"},{"name":"peer","type":"Peer"},{"name":"date","type":"int"},{"name":"active_date","type":"flags.3?int"},{"name":"source","type":"int"},{"name":"volume","type":"flags.7?int"},{"name":"about","type":"flags.11?string"},{"name":"raise_hand_rating","type":"flags.13?long"},{"name":"video","type":"flags.6?GroupCallParticipantVideo"},{"name":"presentation","type":"flags.14?GroupCallParticipantVideo"}],"type":"GroupCallParticipant"},{"id":"-124097970","predicate":"updateChat","params":[{"name":"chat_id","type":"long"}],"type":"Update"},{"id":"-219423922","predicate":"updateGroupCallParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"Update"},{"id":"347227392","predicate":"updateGroupCall","params":[{"name":"chat_id","type":"long"},{"name":"call","type":"GroupCall"}],"type":"Update"},{"id":"-1636664659","predicate":"phone.groupCall","params":[{"name":"call","type":"GroupCall"},{"name":"participants","type":"Vector"},{"name":"participants_next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.GroupCall"},{"id":"-193506890","predicate":"phone.groupParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"version","type":"int"}],"type":"phone.GroupParticipants"},{"id":"813821341","predicate":"inlineQueryPeerTypeSameBotPM","params":[],"type":"InlineQueryPeerType"},{"id":"-2093215828","predicate":"inlineQueryPeerTypePM","params":[],"type":"InlineQueryPeerType"},{"id":"-681130742","predicate":"inlineQueryPeerTypeChat","params":[],"type":"InlineQueryPeerType"},{"id":"1589952067","predicate":"inlineQueryPeerTypeMegagroup","params":[],"type":"InlineQueryPeerType"},{"id":"1664413338","predicate":"inlineQueryPeerTypeBroadcast","params":[],"type":"InlineQueryPeerType"},{"id":"589338437","predicate":"channelAdminLogEventActionStartGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-610299584","predicate":"channelAdminLogEventActionDiscardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-115071790","predicate":"channelAdminLogEventActionParticipantMute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-431740480","predicate":"channelAdminLogEventActionParticipantUnmute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1456906823","predicate":"channelAdminLogEventActionToggleGroupCallSetting","params":[{"name":"join_muted","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1966921727","predicate":"inputPaymentCredentialsGooglePay","params":[{"name":"payment_token","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"375566091","predicate":"messages.historyImport","params":[{"name":"id","type":"long"}],"type":"messages.HistoryImport"},{"id":"-606432698","predicate":"sendMessageHistoryImportAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"1578088377","predicate":"messages.historyImportParsed","params":[{"name":"flags","type":"#"},{"name":"pm","type":"flags.0?true"},{"name":"group","type":"flags.1?true"},{"name":"title","type":"flags.2?string"}],"type":"messages.HistoryImportParsed"},{"id":"-170010905","predicate":"inputReportReasonFake","params":[],"type":"ReportReason"},{"id":"-275956116","predicate":"messages.affectedFoundMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"},{"name":"messages","type":"Vector"}],"type":"messages.AffectedFoundMessages"},{"id":"-1441072131","predicate":"messageActionSetMessagesTTL","params":[{"name":"period","type":"int"}],"type":"MessageAction"},{"id":"-1147422299","predicate":"updatePeerHistoryTTL","params":[{"name":"flags","type":"#"},{"name":"peer","type":"Peer"},{"name":"ttl_period","type":"flags.0?int"}],"type":"Update"},{"id":"-796432838","predicate":"updateChatParticipant","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChatParticipant"},{"name":"new_participant","type":"flags.1?ChatParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1738720581","predicate":"updateChannelParticipant","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChannelParticipant"},{"name":"new_participant","type":"flags.1?ChannelParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-997782967","predicate":"updateBotStopped","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"stopped","type":"Bool"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1940201511","predicate":"chatInviteImporter","params":[{"name":"flags","type":"#"},{"name":"requested","type":"flags.0?true"},{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"about","type":"flags.2?string"},{"name":"approved_by","type":"flags.1?long"}],"type":"ChatInviteImporter"},{"id":"-1111085620","predicate":"messages.exportedChatInvites","params":[{"name":"count","type":"int"},{"name":"invites","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvites"},{"id":"410107472","predicate":"messages.exportedChatInvite","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"572915951","predicate":"messages.exportedChatInviteReplaced","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"-2118733814","predicate":"messages.chatInviteImporters","params":[{"name":"count","type":"int"},{"name":"importers","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatInviteImporters"},{"id":"-219353309","predicate":"chatAdminWithInvites","params":[{"name":"admin_id","type":"long"},{"name":"invites_count","type":"int"},{"name":"revoked_invites_count","type":"int"}],"type":"ChatAdminWithInvites"},{"id":"-1231326505","predicate":"messages.chatAdminsWithInvites","params":[{"name":"admins","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatAdminsWithInvites"},{"id":"1557846647","predicate":"channelAdminLogEventActionParticipantJoinByInvite","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1515256996","predicate":"channelAdminLogEventActionExportedInviteDelete","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1091179342","predicate":"channelAdminLogEventActionExportedInviteRevoke","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"-384910503","predicate":"channelAdminLogEventActionExportedInviteEdit","params":[{"name":"prev_invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1048537159","predicate":"channelAdminLogEventActionParticipantVolume","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1855199800","predicate":"channelAdminLogEventActionChangeHistoryTTL","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"-1571952873","predicate":"messages.checkedHistoryImportPeer","params":[{"name":"confirm_text","type":"string"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"93890858","predicate":"inputGroupCallStream","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"time_ms","type":"long"},{"name":"scale","type":"int"},{"name":"video_channel","type":"flags.0?int"},{"name":"video_quality","type":"flags.0?int"}],"type":"InputFileLocation"},{"id":"-1343921601","predicate":"phone.joinAsPeers","params":[{"name":"peers","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.JoinAsPeers"},{"id":"541839704","predicate":"phone.exportedGroupCallInvite","params":[{"name":"link","type":"string"}],"type":"phone.ExportedGroupCallInvite"},{"id":"-672693723","predicate":"inputBotInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"894081801","predicate":"botInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1281329567","predicate":"messageActionGroupCallScheduled","params":[{"name":"call","type":"InputGroupCall"},{"name":"schedule_date","type":"int"}],"type":"MessageAction"},{"id":"-592373577","predicate":"groupCallParticipantVideoSourceGroup","params":[{"name":"semantics","type":"string"},{"name":"sources","type":"Vector"}],"type":"GroupCallParticipantVideoSourceGroup"},{"id":"1735736008","predicate":"groupCallParticipantVideo","params":[{"name":"flags","type":"#"},{"name":"paused","type":"flags.0?true"},{"name":"endpoint","type":"string"},{"name":"source_groups","type":"Vector"},{"name":"audio_source","type":"flags.1?int"}],"type":"GroupCallParticipantVideo"},{"id":"192428418","predicate":"updateGroupCallConnection","params":[{"name":"flags","type":"#"},{"name":"presentation","type":"flags.0?true"},{"name":"params","type":"DataJSON"}],"type":"Update"},{"id":"-2046910401","predicate":"stickers.suggestedShortName","params":[{"name":"short_name","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"795652779","predicate":"botCommandScopeDefault","params":[],"type":"BotCommandScope"},{"id":"1011811544","predicate":"botCommandScopeUsers","params":[],"type":"BotCommandScope"},{"id":"1877059713","predicate":"botCommandScopeChats","params":[],"type":"BotCommandScope"},{"id":"-1180016534","predicate":"botCommandScopeChatAdmins","params":[],"type":"BotCommandScope"},{"id":"-610432643","predicate":"botCommandScopePeer","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"1071145937","predicate":"botCommandScopePeerAdmins","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"169026035","predicate":"botCommandScopePeerUser","params":[{"name":"peer","type":"InputPeer"},{"name":"user_id","type":"InputUser"}],"type":"BotCommandScope"},{"id":"-478701471","predicate":"account.resetPasswordFailedWait","params":[{"name":"retry_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-370148227","predicate":"account.resetPasswordRequestedWait","params":[{"name":"until_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-383330754","predicate":"account.resetPasswordOk","params":[],"type":"account.ResetPasswordResult"},{"id":"1299263278","predicate":"updateBotCommands","params":[{"name":"peer","type":"Peer"},{"name":"bot_id","type":"long"},{"name":"commands","type":"Vector"}],"type":"Update"},{"id":"-1434950843","predicate":"messageActionSetChatTheme","params":[{"name":"emoticon","type":"string"}],"type":"MessageAction"},{"id":"-1336228175","predicate":"sendMessageChooseStickerAction","params":[],"type":"SendMessageAction"},{"id":"981691896","predicate":"sponsoredMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"bytes"},{"name":"from_id","type":"flags.3?Peer"},{"name":"chat_invite","type":"flags.4?ChatInvite"},{"name":"chat_invite_hash","type":"flags.4?string"},{"name":"channel_post","type":"flags.2?int"},{"name":"start_param","type":"flags.0?string"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"SponsoredMessage"},{"id":"1705297877","predicate":"messages.sponsoredMessages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.SponsoredMessages"},{"id":"215889721","predicate":"inputStickerSetAnimatedEmojiAnimations","params":[],"type":"InputStickerSet"},{"id":"630664139","predicate":"sendMessageEmojiInteraction","params":[{"name":"emoticon","type":"string"},{"name":"msg_id","type":"int"},{"name":"interaction","type":"DataJSON"}],"type":"SendMessageAction"},{"id":"-1234857938","predicate":"sendMessageEmojiInteractionSeen","params":[{"name":"emoticon","type":"string"}],"type":"SendMessageAction"},{"id":"-1227287081","predicate":"inputBotInlineMessageID64","params":[{"name":"dc_id","type":"int"},{"name":"owner_id","type":"long"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"},{"id":"-911191137","predicate":"searchResultsCalendarPeriod","params":[{"name":"date","type":"int"},{"name":"min_msg_id","type":"int"},{"name":"max_msg_id","type":"int"},{"name":"count","type":"int"}],"type":"SearchResultsCalendarPeriod"},{"id":"343859772","predicate":"messages.searchResultsCalendar","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.0?true"},{"name":"count","type":"int"},{"name":"min_date","type":"int"},{"name":"min_msg_id","type":"int"},{"name":"offset_id_offset","type":"flags.1?int"},{"name":"periods","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.SearchResultsCalendar"},{"id":"2137295719","predicate":"searchResultPosition","params":[{"name":"msg_id","type":"int"},{"name":"date","type":"int"},{"name":"offset","type":"int"}],"type":"SearchResultsPosition"},{"id":"1404185519","predicate":"messages.searchResultsPositions","params":[{"name":"count","type":"int"},{"name":"positions","type":"Vector"}],"type":"messages.SearchResultsPositions"},{"id":"-339958837","predicate":"messageActionChatJoinedByRequest","params":[],"type":"MessageAction"},{"id":"1885586395","predicate":"updatePendingJoinRequests","params":[{"name":"peer","type":"Peer"},{"name":"requests_pending","type":"int"},{"name":"recent_requesters","type":"Vector"}],"type":"Update"},{"id":"299870598","predicate":"updateBotChatInviteRequester","params":[{"name":"peer","type":"Peer"},{"name":"date","type":"int"},{"name":"user_id","type":"long"},{"name":"about","type":"string"},{"name":"invite","type":"ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1347021750","predicate":"channelAdminLogEventActionParticipantJoinByRequest","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"approved_by","type":"long"}],"type":"ChannelAdminLogEventAction"},{"id":"-376962181","predicate":"inputKeyboardButtonUserProfile","params":[{"name":"text","type":"string"},{"name":"user_id","type":"InputUser"}],"type":"KeyboardButton"},{"id":"814112961","predicate":"keyboardButtonUserProfile","params":[{"name":"text","type":"string"},{"name":"user_id","type":"long"}],"type":"KeyboardButton"},{"id":"-2091463255","predicate":"channels.sendAsPeers","params":[{"name":"peers","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.SendAsPeers"},{"id":"-886388890","predicate":"channelAdminLogEventActionToggleNoForwards","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-738646805","predicate":"messages.stickerSetNotModified","params":[],"type":"messages.StickerSet"},{"id":"997004590","predicate":"users.userFull","params":[{"name":"full_user","type":"UserFull"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"users.UserFull"},{"id":"1753266509","predicate":"messages.peerSettings","params":[{"name":"settings","type":"PeerSettings"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.PeerSettings"},{"id":"663693416","predicate":"channelAdminLogEventActionSendMessage","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"-702884114","predicate":"auth.codeTypeMissedCall","params":[],"type":"auth.CodeType"},{"id":"-2113903484","predicate":"auth.sentCodeTypeMissedCall","params":[{"name":"prefix","type":"string"},{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1012759713","predicate":"auth.loggedOut","params":[{"name":"flags","type":"#"},{"name":"future_auth_token","type":"flags.0?bytes"}],"type":"auth.LoggedOut"},{"id":"357013699","predicate":"updateMessageReactions","params":[{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"},{"name":"reactions","type":"MessageReactions"}],"type":"Update"},{"id":"1873957073","predicate":"reactionCount","params":[{"name":"flags","type":"#"},{"name":"chosen","type":"flags.0?true"},{"name":"reaction","type":"string"},{"name":"count","type":"int"}],"type":"ReactionCount"},{"id":"1328256121","predicate":"messageReactions","params":[{"name":"flags","type":"#"},{"name":"min","type":"flags.0?true"},{"name":"can_see_list","type":"flags.2?true"},{"name":"results","type":"Vector"},{"name":"recent_reactions","type":"flags.1?Vector"}],"type":"MessageReactions"},{"id":"834488621","predicate":"messages.messageReactionsList","params":[{"name":"flags","type":"#"},{"name":"count","type":"int"},{"name":"reactions","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"next_offset","type":"flags.0?string"}],"type":"messages.MessageReactionsList"},{"id":"-1065882623","predicate":"availableReaction","params":[{"name":"flags","type":"#"},{"name":"inactive","type":"flags.0?true"},{"name":"reaction","type":"string"},{"name":"title","type":"string"},{"name":"static_icon","type":"Document"},{"name":"appear_animation","type":"Document"},{"name":"select_animation","type":"Document"},{"name":"activate_animation","type":"Document"},{"name":"effect_animation","type":"Document"},{"name":"around_animation","type":"flags.1?Document"},{"name":"center_icon","type":"flags.1?Document"}],"type":"AvailableReaction"},{"id":"-1626924713","predicate":"messages.availableReactionsNotModified","params":[],"type":"messages.AvailableReactions"},{"id":"1989032621","predicate":"messages.availableReactions","params":[{"name":"hash","type":"int"},{"name":"reactions","type":"Vector"}],"type":"messages.AvailableReactions"},{"id":"852137487","predicate":"messageEntitySpoiler","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1661470870","predicate":"channelAdminLogEventActionChangeAvailableReactions","params":[{"name":"prev_value","type":"Vector"},{"name":"new_value","type":"Vector"}],"type":"ChannelAdminLogEventAction"},{"id":"1741309751","predicate":"messages.translateNoResult","params":[],"type":"messages.TranslatedText"},{"id":"-1575684144","predicate":"messages.translateResultText","params":[{"name":"text","type":"string"}],"type":"messages.TranslatedText"},{"id":"1370914559","predicate":"messagePeerReaction","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.0?true"},{"name":"unread","type":"flags.1?true"},{"name":"peer_id","type":"Peer"},{"name":"reaction","type":"string"}],"type":"MessagePeerReaction"}],"methods":[{"id":"-878758099","method":"invokeAfterMsg","params":[{"name":"msg_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"1036301552","method":"invokeAfterMsgs","params":[{"name":"msg_ids","type":"Vector"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1502141361","method":"auth.sendCode","params":[{"name":"phone_number","type":"string"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"-2131827673","method":"auth.signUp","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"auth.Authorization"},{"id":"-1126886015","method":"auth.signIn","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"auth.Authorization"},{"id":"1047706137","method":"auth.logOut","params":[],"type":"auth.LoggedOut"},{"id":"-1616179942","method":"auth.resetAuthorizations","params":[],"type":"Bool"},{"id":"-440401971","method":"auth.exportAuthorization","params":[{"name":"dc_id","type":"int"}],"type":"auth.ExportedAuthorization"},{"id":"-1518699091","method":"auth.importAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.Authorization"},{"id":"-841733627","method":"auth.bindTempAuthKey","params":[{"name":"perm_auth_key_id","type":"long"},{"name":"nonce","type":"long"},{"name":"expires_at","type":"int"},{"name":"encrypted_message","type":"bytes"}],"type":"Bool"},{"id":"-326762118","method":"account.registerDevice","params":[{"name":"flags","type":"#"},{"name":"no_muted","type":"flags.0?true"},{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"app_sandbox","type":"Bool"},{"name":"secret","type":"bytes"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"1779249670","method":"account.unregisterDevice","params":[{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"-2067899501","method":"account.updateNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"},{"name":"settings","type":"InputPeerNotifySettings"}],"type":"Bool"},{"id":"313765169","method":"account.getNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"}],"type":"PeerNotifySettings"},{"id":"-612493497","method":"account.resetNotifySettings","params":[],"type":"Bool"},{"id":"2018596725","method":"account.updateProfile","params":[{"name":"flags","type":"#"},{"name":"first_name","type":"flags.0?string"},{"name":"last_name","type":"flags.1?string"},{"name":"about","type":"flags.2?string"}],"type":"User"},{"id":"1713919532","method":"account.updateStatus","params":[{"name":"offline","type":"Bool"}],"type":"Bool"},{"id":"127302966","method":"account.getWallPapers","params":[{"name":"hash","type":"long"}],"type":"account.WallPapers"},{"id":"-977650298","method":"account.reportPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"227648840","method":"users.getUsers","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-1240508136","method":"users.getFullUser","params":[{"name":"id","type":"InputUser"}],"type":"users.UserFull"},{"id":"2061264541","method":"contacts.getContactIDs","params":[{"name":"hash","type":"long"}],"type":"Vector"},{"id":"-995929106","method":"contacts.getStatuses","params":[],"type":"Vector"},{"id":"1574346258","method":"contacts.getContacts","params":[{"name":"hash","type":"long"}],"type":"contacts.Contacts"},{"id":"746589157","method":"contacts.importContacts","params":[{"name":"contacts","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"157945344","method":"contacts.deleteContacts","params":[{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"269745566","method":"contacts.deleteByPhones","params":[{"name":"phones","type":"Vector"}],"type":"Bool"},{"id":"1758204945","method":"contacts.block","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-1096393392","method":"contacts.unblock","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-176409329","method":"contacts.getBlocked","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"contacts.Blocked"},{"id":"1673946374","method":"messages.getMessages","params":[{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1594569905","method":"messages.getDialogs","params":[{"name":"flags","type":"#"},{"name":"exclude_pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"offset_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Dialogs"},{"id":"1143203525","method":"messages.getHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1593989278","method":"messages.search","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"q","type":"string"},{"name":"from_id","type":"flags.0?InputPeer"},{"name":"top_msg_id","type":"flags.1?int"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"238054714","method":"messages.readHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"}],"type":"messages.AffectedMessages"},{"id":"-1332768214","method":"messages.deleteHistory","params":[{"name":"flags","type":"#"},{"name":"just_clear","type":"flags.0?true"},{"name":"revoke","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"},{"name":"min_date","type":"flags.2?int"},{"name":"max_date","type":"flags.3?int"}],"type":"messages.AffectedHistory"},{"id":"-443640366","method":"messages.deleteMessages","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"94983360","method":"messages.receivedMessages","params":[{"name":"max_id","type":"int"}],"type":"Vector"},{"id":"1486110434","method":"messages.setTyping","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"action","type":"SendMessageAction"}],"type":"Bool"},{"id":"228423076","method":"messages.sendMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"noforwards","type":"flags.14?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"-497026848","method":"messages.sendMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"noforwards","type":"flags.14?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"media","type":"InputMedia"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"-869258997","method":"messages.forwardMessages","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"with_my_score","type":"flags.8?true"},{"name":"drop_author","type":"flags.11?true"},{"name":"drop_media_captions","type":"flags.12?true"},{"name":"noforwards","type":"flags.14?true"},{"name":"from_peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"random_id","type":"Vector"},{"name":"to_peer","type":"InputPeer"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"-820669733","method":"messages.reportSpam","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-270948702","method":"messages.getPeerSettings","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.PeerSettings"},{"id":"-1991005362","method":"messages.report","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"1240027791","method":"messages.getChats","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"-1364194508","method":"messages.getFullChat","params":[{"name":"chat_id","type":"long"}],"type":"messages.ChatFull"},{"id":"1937260541","method":"messages.editChatTitle","params":[{"name":"chat_id","type":"long"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"903730804","method":"messages.editChatPhoto","params":[{"name":"chat_id","type":"long"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"-230206493","method":"messages.addChatUser","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"fwd_limit","type":"int"}],"type":"Updates"},{"id":"-1575461717","method":"messages.deleteChatUser","params":[{"name":"flags","type":"#"},{"name":"revoke_history","type":"flags.0?true"},{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"}],"type":"Updates"},{"id":"164303470","method":"messages.createChat","params":[{"name":"users","type":"Vector"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-304838614","method":"updates.getState","params":[],"type":"updates.State"},{"id":"630429265","method":"updates.getDifference","params":[{"name":"flags","type":"#"},{"name":"pts","type":"int"},{"name":"pts_total_limit","type":"flags.0?int"},{"name":"date","type":"int"},{"name":"qts","type":"int"}],"type":"updates.Difference"},{"id":"1926525996","method":"photos.updateProfilePhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"photos.Photo"},{"id":"-1980559511","method":"photos.uploadProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"photos.Photo"},{"id":"-2016444625","method":"photos.deletePhotos","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-1291540959","method":"upload.saveFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1319462148","method":"upload.getFile","params":[{"name":"flags","type":"#"},{"name":"precise","type":"flags.0?true"},{"name":"cdn_supported","type":"flags.1?true"},{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.File"},{"id":"-990308245","method":"help.getConfig","params":[],"type":"Config"},{"id":"531836966","method":"help.getNearestDc","params":[],"type":"NearestDc"},{"id":"1378703997","method":"help.getAppUpdate","params":[{"name":"source","type":"string"}],"type":"help.AppUpdate"},{"id":"1295590211","method":"help.getInviteText","params":[],"type":"help.InviteText"},{"id":"-1848823128","method":"photos.getUserPhotos","params":[{"name":"user_id","type":"InputUser"},{"name":"offset","type":"int"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"photos.Photos"},{"id":"651135312","method":"messages.getDhConfig","params":[{"name":"version","type":"int"},{"name":"random_length","type":"int"}],"type":"messages.DhConfig"},{"id":"-162681021","method":"messages.requestEncryption","params":[{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1035731989","method":"messages.acceptEncryption","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"-208425312","method":"messages.discardEncryption","params":[{"name":"flags","type":"#"},{"name":"delete_history","type":"flags.0?true"},{"name":"chat_id","type":"int"}],"type":"Bool"},{"id":"2031374829","method":"messages.setEncryptedTyping","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"typing","type":"Bool"}],"type":"Bool"},{"id":"2135648522","method":"messages.readEncryptedHistory","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"max_date","type":"int"}],"type":"Bool"},{"id":"1157265941","method":"messages.sendEncrypted","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1431914525","method":"messages.sendEncryptedFile","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"},{"name":"file","type":"InputEncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"852769188","method":"messages.sendEncryptedService","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1436924774","method":"messages.receivedQueue","params":[{"name":"max_qts","type":"int"}],"type":"Vector"},{"id":"1259113487","method":"messages.reportEncryptedSpam","params":[{"name":"peer","type":"InputEncryptedChat"}],"type":"Bool"},{"id":"-562337987","method":"upload.saveBigFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"file_total_parts","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1043505495","method":"initConnection","params":[{"name":"flags","type":"#"},{"name":"api_id","type":"int"},{"name":"device_model","type":"string"},{"name":"system_version","type":"string"},{"name":"app_version","type":"string"},{"name":"system_lang_code","type":"string"},{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"proxy","type":"flags.0?InputClientProxy"},{"name":"params","type":"flags.1?JSONValue"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1663104819","method":"help.getSupport","params":[],"type":"help.Support"},{"id":"916930423","method":"messages.readMessageContents","params":[{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"655677548","method":"account.checkUsername","params":[{"name":"username","type":"string"}],"type":"Bool"},{"id":"1040964988","method":"account.updateUsername","params":[{"name":"username","type":"string"}],"type":"User"},{"id":"301470424","method":"contacts.search","params":[{"name":"q","type":"string"},{"name":"limit","type":"int"}],"type":"contacts.Found"},{"id":"-623130288","method":"account.getPrivacy","params":[{"name":"key","type":"InputPrivacyKey"}],"type":"account.PrivacyRules"},{"id":"-906486552","method":"account.setPrivacy","params":[{"name":"key","type":"InputPrivacyKey"},{"name":"rules","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"1099779595","method":"account.deleteAccount","params":[{"name":"reason","type":"string"}],"type":"Bool"},{"id":"150761757","method":"account.getAccountTTL","params":[],"type":"AccountDaysTTL"},{"id":"608323678","method":"account.setAccountTTL","params":[{"name":"ttl","type":"AccountDaysTTL"}],"type":"Bool"},{"id":"-627372787","method":"invokeWithLayer","params":[{"name":"layer","type":"int"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-113456221","method":"contacts.resolveUsername","params":[{"name":"username","type":"string"}],"type":"contacts.ResolvedPeer"},{"id":"-2108208411","method":"account.sendChangePhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1891839707","method":"account.changePhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"User"},{"id":"-710552671","method":"messages.getStickers","params":[{"name":"emoticon","type":"string"},{"name":"hash","type":"long"}],"type":"messages.Stickers"},{"id":"-1197432408","method":"messages.getAllStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"954152242","method":"account.updateDeviceLocked","params":[{"name":"period","type":"int"}],"type":"Bool"},{"id":"1738800940","method":"auth.importBotAuthorization","params":[{"name":"flags","type":"int"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"bot_auth_token","type":"string"}],"type":"auth.Authorization"},{"id":"-1956073268","method":"messages.getWebPagePreview","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"MessageMedia"},{"id":"-484392616","method":"account.getAuthorizations","params":[],"type":"account.Authorizations"},{"id":"-545786948","method":"account.resetAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1418342645","method":"account.getPassword","params":[],"type":"account.Password"},{"id":"-1663767815","method":"account.getPasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"account.PasswordSettings"},{"id":"-1516564433","method":"account.updatePasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"new_settings","type":"account.PasswordInputSettings"}],"type":"Bool"},{"id":"-779399914","method":"auth.checkPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"auth.Authorization"},{"id":"-661144474","method":"auth.requestPasswordRecovery","params":[],"type":"auth.PasswordRecovery"},{"id":"923364464","method":"auth.recoverPassword","params":[{"name":"flags","type":"#"},{"name":"code","type":"string"},{"name":"new_settings","type":"flags.0?account.PasswordInputSettings"}],"type":"auth.Authorization"},{"id":"-1080796745","method":"invokeWithoutUpdates","params":[{"name":"query","type":"!X"}],"type":"X"},{"id":"-1607670315","method":"messages.exportChatInvite","params":[{"name":"flags","type":"#"},{"name":"legacy_revoke_permanent","type":"flags.2?true"},{"name":"request_needed","type":"flags.3?true"},{"name":"peer","type":"InputPeer"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"},{"name":"title","type":"flags.4?string"}],"type":"ExportedChatInvite"},{"id":"1051570619","method":"messages.checkChatInvite","params":[{"name":"hash","type":"string"}],"type":"ChatInvite"},{"id":"1817183516","method":"messages.importChatInvite","params":[{"name":"hash","type":"string"}],"type":"Updates"},{"id":"-928977804","method":"messages.getStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"hash","type":"int"}],"type":"messages.StickerSet"},{"id":"-946871200","method":"messages.installStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"archived","type":"Bool"}],"type":"messages.StickerSetInstallResult"},{"id":"-110209570","method":"messages.uninstallStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"-421563528","method":"messages.startBot","params":[{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"long"},{"name":"start_param","type":"string"}],"type":"Updates"},{"id":"-1877938321","method":"help.getAppChangelog","params":[{"name":"prev_app_version","type":"string"}],"type":"Updates"},{"id":"1468322785","method":"messages.getMessagesViews","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"increment","type":"Bool"}],"type":"messages.MessageViews"},{"id":"-871347913","method":"channels.readHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"-2067661490","method":"channels.deleteMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"-196443371","method":"channels.reportSpam","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1383294429","method":"channels.getMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"2010044880","method":"channels.getParticipants","params":[{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelParticipantsFilter"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"channels.ChannelParticipants"},{"id":"-1599378234","method":"channels.getParticipant","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"}],"type":"channels.ChannelParticipant"},{"id":"176122811","method":"channels.getChannels","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"141781513","method":"channels.getFullChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.ChatFull"},{"id":"1029681423","method":"channels.createChannel","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.0?true"},{"name":"megagroup","type":"flags.1?true"},{"name":"for_import","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"about","type":"string"},{"name":"geo_point","type":"flags.2?InputGeoPoint"},{"name":"address","type":"flags.2?string"}],"type":"Updates"},{"id":"-751007486","method":"channels.editAdmin","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"string"}],"type":"Updates"},{"id":"1450044624","method":"channels.editTitle","params":[{"name":"channel","type":"InputChannel"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-248621111","method":"channels.editPhoto","params":[{"name":"channel","type":"InputChannel"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"283557164","method":"channels.checkUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"890549214","method":"channels.updateUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"615851205","method":"channels.joinChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"-130635115","method":"channels.leaveChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"429865580","method":"channels.inviteToChannel","params":[{"name":"channel","type":"InputChannel"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"-1072619549","method":"channels.deleteChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"51854712","method":"updates.getChannelDifference","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelMessagesFilter"},{"name":"pts","type":"int"},{"name":"limit","type":"int"}],"type":"updates.ChannelDifference"},{"id":"-1470377534","method":"messages.editChatAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"is_admin","type":"Bool"}],"type":"Bool"},{"id":"-1568189671","method":"messages.migrateChat","params":[{"name":"chat_id","type":"long"}],"type":"Updates"},{"id":"1271290010","method":"messages.searchGlobal","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"q","type":"string"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"2016638777","method":"messages.reorderStickerSets","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"864953444","method":"messages.getDocumentByHash","params":[{"name":"sha256","type":"bytes"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"1559270965","method":"messages.getSavedGifs","params":[{"name":"hash","type":"long"}],"type":"messages.SavedGifs"},{"id":"846868683","method":"messages.saveGif","params":[{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"1364105629","method":"messages.getInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"geo_point","type":"flags.0?InputGeoPoint"},{"name":"query","type":"string"},{"name":"offset","type":"string"}],"type":"messages.BotResults"},{"id":"-346119674","method":"messages.setInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"private","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"next_offset","type":"flags.2?string"},{"name":"switch_pm","type":"flags.3?InlineBotSwitchPM"}],"type":"Bool"},{"id":"2057376407","method":"messages.sendInlineBotResult","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"hide_via","type":"flags.11?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"random_id","type":"long"},{"name":"query_id","type":"long"},{"name":"id","type":"string"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"-432034325","method":"channels.exportMessageLink","params":[{"name":"flags","type":"#"},{"name":"grouped","type":"flags.0?true"},{"name":"thread","type":"flags.1?true"},{"name":"channel","type":"InputChannel"},{"name":"id","type":"int"}],"type":"ExportedMessageLink"},{"id":"527021574","method":"channels.toggleSignatures","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"1056025023","method":"auth.resendCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"auth.SentCode"},{"id":"520357240","method":"auth.cancelCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"Bool"},{"id":"-39416522","method":"messages.getMessageEditData","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"messages.MessageEditData"},{"id":"1224152952","method":"messages.editMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.15?int"}],"type":"Updates"},{"id":"-2091549254","method":"messages.editInlineBotMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"-1824339449","method":"messages.getBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"game","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"data","type":"flags.0?bytes"},{"name":"password","type":"flags.2?InputCheckPasswordSRP"}],"type":"messages.BotCallbackAnswer"},{"id":"-712043766","method":"messages.setBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"Bool"},{"id":"-1758168906","method":"contacts.getTopPeers","params":[{"name":"flags","type":"#"},{"name":"correspondents","type":"flags.0?true"},{"name":"bots_pm","type":"flags.1?true"},{"name":"bots_inline","type":"flags.2?true"},{"name":"phone_calls","type":"flags.3?true"},{"name":"forward_users","type":"flags.4?true"},{"name":"forward_chats","type":"flags.5?true"},{"name":"groups","type":"flags.10?true"},{"name":"channels","type":"flags.15?true"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"contacts.TopPeers"},{"id":"451113900","method":"contacts.resetTopPeerRating","params":[{"name":"category","type":"TopPeerCategory"},{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-462373635","method":"messages.getPeerDialogs","params":[{"name":"peers","type":"Vector"}],"type":"messages.PeerDialogs"},{"id":"-1137057461","method":"messages.saveDraft","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"peer","type":"InputPeer"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"1782549861","method":"messages.getAllDrafts","params":[],"type":"Updates"},{"id":"1685588756","method":"messages.getFeaturedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"1527873830","method":"messages.readFeaturedStickers","params":[{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1649852357","method":"messages.getRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"hash","type":"long"}],"type":"messages.RecentStickers"},{"id":"958863608","method":"messages.saveRecentSticker","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"-1986437075","method":"messages.clearRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"}],"type":"Bool"},{"id":"1475442322","method":"messages.getArchivedStickers","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"offset_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.ArchivedStickers"},{"id":"457157256","method":"account.sendConfirmPhoneCode","params":[{"name":"hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1596029123","method":"account.confirmPhone","params":[{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"-122669393","method":"channels.getAdminedPublicChannels","params":[{"name":"flags","type":"#"},{"name":"by_location","type":"flags.0?true"},{"name":"check_limit","type":"flags.1?true"}],"type":"messages.Chats"},{"id":"1678738104","method":"messages.getMaskStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"-866424884","method":"messages.getAttachedStickers","params":[{"name":"media","type":"InputStickeredMedia"}],"type":"Vector"},{"id":"-1907842680","method":"auth.dropTempAuthKeys","params":[{"name":"except_auth_keys","type":"Vector"}],"type":"Bool"},{"id":"-1896289088","method":"messages.setGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Updates"},{"id":"363700068","method":"messages.setInlineGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Bool"},{"id":"-400399203","method":"messages.getGameHighScores","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"258170395","method":"messages.getInlineGameHighScores","params":[{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"-468934396","method":"messages.getCommonChats","params":[{"name":"user_id","type":"InputUser"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.Chats"},{"id":"-2023787330","method":"messages.getAllChats","params":[{"name":"except_ids","type":"Vector"}],"type":"messages.Chats"},{"id":"-333262899","method":"help.setBotUpdatesStatus","params":[{"name":"pending_updates_count","type":"int"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"852135825","method":"messages.getWebPage","params":[{"name":"url","type":"string"},{"name":"hash","type":"int"}],"type":"WebPage"},{"id":"-1489903017","method":"messages.toggleDialogPin","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"991616823","method":"messages.reorderPinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"folder_id","type":"int"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-692498958","method":"messages.getPinnedDialogs","params":[{"name":"folder_id","type":"int"}],"type":"messages.PeerDialogs"},{"id":"-1440257555","method":"bots.sendCustomRequest","params":[{"name":"custom_method","type":"string"},{"name":"params","type":"DataJSON"}],"type":"DataJSON"},{"id":"-434028723","method":"bots.answerWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"}],"type":"Bool"},{"id":"619086221","method":"upload.getWebFile","params":[{"name":"location","type":"InputWebFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.WebFile"},{"id":"-1976353651","method":"payments.getPaymentForm","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"theme_params","type":"flags.0?DataJSON"}],"type":"payments.PaymentForm"},{"id":"611897804","method":"payments.getPaymentReceipt","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"payments.PaymentReceipt"},{"id":"-619695760","method":"payments.validateRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"info","type":"PaymentRequestedInfo"}],"type":"payments.ValidatedRequestedInfo"},{"id":"818134173","method":"payments.sendPaymentForm","params":[{"name":"flags","type":"#"},{"name":"form_id","type":"long"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"requested_info_id","type":"flags.0?string"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"credentials","type":"InputPaymentCredentials"},{"name":"tip_amount","type":"flags.2?long"}],"type":"payments.PaymentResult"},{"id":"1151208273","method":"account.getTmpPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"period","type":"int"}],"type":"account.TmpPassword"},{"id":"578650699","method":"payments.getSavedInfo","params":[],"type":"payments.SavedInfo"},{"id":"-667062079","method":"payments.clearSavedInfo","params":[{"name":"flags","type":"#"},{"name":"credentials","type":"flags.0?true"},{"name":"info","type":"flags.1?true"}],"type":"Bool"},{"id":"-436833542","method":"messages.setBotShippingResults","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"Bool"},{"id":"163765653","method":"messages.setBotPrecheckoutResults","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"}],"type":"Bool"},{"id":"-1876841625","method":"stickers.createStickerSet","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"animated","type":"flags.1?true"},{"name":"videos","type":"flags.4?true"},{"name":"user_id","type":"InputUser"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumb","type":"flags.2?InputDocument"},{"name":"stickers","type":"Vector"},{"name":"software","type":"flags.3?string"}],"type":"messages.StickerSet"},{"id":"-143257775","method":"stickers.removeStickerFromSet","params":[{"name":"sticker","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"-4795190","method":"stickers.changeStickerPosition","params":[{"name":"sticker","type":"InputDocument"},{"name":"position","type":"int"}],"type":"messages.StickerSet"},{"id":"-2041315650","method":"stickers.addStickerToSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"sticker","type":"InputStickerSetItem"}],"type":"messages.StickerSet"},{"id":"1369162417","method":"messages.uploadMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"1430593449","method":"phone.getCallConfig","params":[],"type":"DataJSON"},{"id":"1124046573","method":"phone.requestCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"1003664544","method":"phone.acceptCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"788404002","method":"phone.confirmCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_a","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"399855457","method":"phone.receivedCall","params":[{"name":"peer","type":"InputPhoneCall"}],"type":"Bool"},{"id":"-1295269440","method":"phone.discardCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"duration","type":"int"},{"name":"reason","type":"PhoneCallDiscardReason"},{"name":"connection_id","type":"long"}],"type":"Updates"},{"id":"1508562471","method":"phone.setCallRating","params":[{"name":"flags","type":"#"},{"name":"user_initiative","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"rating","type":"int"},{"name":"comment","type":"string"}],"type":"Updates"},{"id":"662363518","method":"phone.saveCallDebug","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"debug","type":"DataJSON"}],"type":"Bool"},{"id":"536919235","method":"upload.getCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.CdnFile"},{"id":"-1691921240","method":"upload.reuploadCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"request_token","type":"bytes"}],"type":"Vector"},{"id":"1375900482","method":"help.getCdnConfig","params":[],"type":"CdnConfig"},{"id":"-219008246","method":"langpack.getLangPack","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackDifference"},{"id":"-269862909","method":"langpack.getStrings","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"keys","type":"Vector"}],"type":"Vector"},{"id":"-845657435","method":"langpack.getDifference","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"LangPackDifference"},{"id":"1120311183","method":"langpack.getLanguages","params":[{"name":"lang_pack","type":"string"}],"type":"Vector"},{"id":"-1763259007","method":"channels.editBanned","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"870184064","method":"channels.getAdminLog","params":[{"name":"flags","type":"#"},{"name":"channel","type":"InputChannel"},{"name":"q","type":"string"},{"name":"events_filter","type":"flags.0?ChannelAdminLogEventsFilter"},{"name":"admins","type":"flags.1?Vector"},{"name":"max_id","type":"long"},{"name":"min_id","type":"long"},{"name":"limit","type":"int"}],"type":"channels.AdminLogResults"},{"id":"1302676017","method":"upload.getCdnFileHashes","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"-914493408","method":"messages.sendScreenshotNotification","params":[{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"int"},{"name":"random_id","type":"long"}],"type":"Updates"},{"id":"-359881479","method":"channels.setStickers","params":[{"name":"channel","type":"InputChannel"},{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"82946729","method":"messages.getFavedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FavedStickers"},{"id":"-1174420133","method":"messages.faveSticker","params":[{"name":"id","type":"InputDocument"},{"name":"unfave","type":"Bool"}],"type":"Bool"},{"id":"-357180360","method":"channels.readMessageContents","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-2020263951","method":"contacts.resetSaved","params":[],"type":"Bool"},{"id":"1180140658","method":"messages.getUnreadMentions","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"}],"type":"messages.Messages"},{"id":"-1355375294","method":"channels.deleteHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"1036054804","method":"help.getRecentMeUrls","params":[{"name":"referer","type":"string"}],"type":"help.RecentMeUrls"},{"id":"-356796084","method":"channels.togglePreHistoryHidden","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"251759059","method":"messages.readMentions","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1881817312","method":"messages.getRecentLocations","params":[{"name":"peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-134016113","method":"messages.sendMultiMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"noforwards","type":"flags.14?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"multi_media","type":"Vector"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"1347929239","method":"messages.uploadEncryptedFile","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"file","type":"InputEncryptedFile"}],"type":"EncryptedFile"},{"id":"405695855","method":"account.getWebAuthorizations","params":[],"type":"account.WebAuthorizations"},{"id":"755087855","method":"account.resetWebAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1747789204","method":"account.resetWebAuthorizations","params":[],"type":"Bool"},{"id":"896555914","method":"messages.searchStickerSets","params":[{"name":"flags","type":"#"},{"name":"exclude_featured","type":"flags.0?true"},{"name":"q","type":"string"},{"name":"hash","type":"long"}],"type":"messages.FoundStickerSets"},{"id":"-956147407","method":"upload.getFileHashes","params":[{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"749019089","method":"help.getTermsOfServiceUpdate","params":[],"type":"help.TermsOfServiceUpdate"},{"id":"-294455398","method":"help.acceptTermsOfService","params":[{"name":"id","type":"DataJSON"}],"type":"Bool"},{"id":"-1299661699","method":"account.getAllSecureValues","params":[],"type":"Vector"},{"id":"1936088002","method":"account.getSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Vector"},{"id":"-1986010339","method":"account.saveSecureValue","params":[{"name":"value","type":"InputSecureValue"},{"name":"secure_secret_id","type":"long"}],"type":"SecureValue"},{"id":"-1199522741","method":"account.deleteSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Bool"},{"id":"-1865902923","method":"users.setSecureValueErrors","params":[{"name":"id","type":"InputUser"},{"name":"errors","type":"Vector"}],"type":"Bool"},{"id":"-1456907910","method":"account.getAuthorizationForm","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"}],"type":"account.AuthorizationForm"},{"id":"-202552205","method":"account.acceptAuthorization","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"},{"name":"value_hashes","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"Bool"},{"id":"-1516022023","method":"account.sendVerifyPhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1305716726","method":"account.verifyPhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"1880182943","method":"account.sendVerifyEmailCode","params":[{"name":"email","type":"string"}],"type":"account.SentEmailCode"},{"id":"-323339813","method":"account.verifyEmail","params":[{"name":"email","type":"string"},{"name":"code","type":"string"}],"type":"Bool"},{"id":"1072547679","method":"help.getDeepLinkInfo","params":[{"name":"path","type":"string"}],"type":"help.DeepLinkInfo"},{"id":"-2098076769","method":"contacts.getSaved","params":[],"type":"Vector"},{"id":"-2092831552","method":"channels.getLeftChannels","params":[{"name":"offset","type":"int"}],"type":"messages.Chats"},{"id":"-262453244","method":"account.initTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"message_users","type":"flags.1?true"},{"name":"message_chats","type":"flags.2?true"},{"name":"message_megagroups","type":"flags.3?true"},{"name":"message_channels","type":"flags.4?true"},{"name":"files","type":"flags.5?true"},{"name":"file_max_size","type":"flags.5?int"}],"type":"account.Takeout"},{"id":"489050862","method":"account.finishTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.0?true"}],"type":"Bool"},{"id":"486505992","method":"messages.getSplitRanges","params":[],"type":"Vector"},{"id":"911373810","method":"invokeWithMessagesRange","params":[{"name":"range","type":"MessageRange"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1398145746","method":"invokeWithTakeout","params":[{"name":"takeout_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1031349873","method":"messages.markDialogUnread","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"585256482","method":"messages.getDialogUnreadMarks","params":[],"type":"Vector"},{"id":"-2062238246","method":"contacts.toggleTopPeers","params":[{"name":"enabled","type":"Bool"}],"type":"Bool"},{"id":"2119757468","method":"messages.clearAllDrafts","params":[],"type":"Bool"},{"id":"-1735311088","method":"help.getAppConfig","params":[],"type":"JSONValue"},{"id":"1862465352","method":"help.saveAppLog","params":[{"name":"events","type":"Vector"}],"type":"Bool"},{"id":"-966677240","method":"help.getPassportConfig","params":[{"name":"hash","type":"int"}],"type":"help.PassportConfig"},{"id":"1784243458","method":"langpack.getLanguage","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackLanguage"},{"id":"-760547348","method":"messages.updatePinnedMessage","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"unpin","type":"flags.1?true"},{"name":"pm_oneside","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"Updates"},{"id":"-1881204448","method":"account.confirmPasswordEmail","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"2055154197","method":"account.resendPasswordEmail","params":[],"type":"Bool"},{"id":"-1043606090","method":"account.cancelPasswordEmail","params":[],"type":"Bool"},{"id":"-748624084","method":"help.getSupportName","params":[],"type":"help.SupportName"},{"id":"59377875","method":"help.getUserInfo","params":[{"name":"user_id","type":"InputUser"}],"type":"help.UserInfo"},{"id":"1723407216","method":"help.editUserInfo","params":[{"name":"user_id","type":"InputUser"},{"name":"message","type":"string"},{"name":"entities","type":"Vector"}],"type":"help.UserInfo"},{"id":"-1626880216","method":"account.getContactSignUpNotification","params":[],"type":"Bool"},{"id":"-806076575","method":"account.setContactSignUpNotification","params":[{"name":"silent","type":"Bool"}],"type":"Bool"},{"id":"1398240377","method":"account.getNotifyExceptions","params":[{"name":"flags","type":"#"},{"name":"compare_sound","type":"flags.1?true"},{"name":"peer","type":"flags.0?InputNotifyPeer"}],"type":"Updates"},{"id":"283795844","method":"messages.sendVote","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"options","type":"Vector"}],"type":"Updates"},{"id":"1941660731","method":"messages.getPollResults","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1848369232","method":"messages.getOnlines","params":[{"name":"peer","type":"InputPeer"}],"type":"ChatOnlines"},{"id":"-554301545","method":"messages.editChatAbout","params":[{"name":"peer","type":"InputPeer"},{"name":"about","type":"string"}],"type":"Bool"},{"id":"-1517917375","method":"messages.editChatDefaultBannedRights","params":[{"name":"peer","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"-57811990","method":"account.getWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"}],"type":"WallPaper"},{"id":"-578472351","method":"account.uploadWallPaper","params":[{"name":"file","type":"InputFile"},{"name":"mime_type","type":"string"},{"name":"settings","type":"WallPaperSettings"}],"type":"WallPaper"},{"id":"1817860919","method":"account.saveWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"unsave","type":"Bool"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-18000023","method":"account.installWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-1153722364","method":"account.resetWallPapers","params":[],"type":"Bool"},{"id":"1457130303","method":"account.getAutoDownloadSettings","params":[],"type":"account.AutoDownloadSettings"},{"id":"1995661875","method":"account.saveAutoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"low","type":"flags.0?true"},{"name":"high","type":"flags.1?true"},{"name":"settings","type":"AutoDownloadSettings"}],"type":"Bool"},{"id":"899735650","method":"messages.getEmojiKeywords","params":[{"name":"lang_code","type":"string"}],"type":"EmojiKeywordsDifference"},{"id":"352892591","method":"messages.getEmojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"EmojiKeywordsDifference"},{"id":"1318675378","method":"messages.getEmojiKeywordsLanguages","params":[{"name":"lang_codes","type":"Vector"}],"type":"Vector"},{"id":"-709817306","method":"messages.getEmojiURL","params":[{"name":"lang_code","type":"string"}],"type":"EmojiURL"},{"id":"1749536939","method":"folders.editPeerFolders","params":[{"name":"folder_peers","type":"Vector"}],"type":"Updates"},{"id":"472471681","method":"folders.deleteFolder","params":[{"name":"folder_id","type":"int"}],"type":"Updates"},{"id":"1932455680","method":"messages.getSearchCounters","params":[{"name":"peer","type":"InputPeer"},{"name":"filters","type":"Vector"}],"type":"Vector"},{"id":"-170208392","method":"channels.getGroupsForDiscussion","params":[],"type":"messages.Chats"},{"id":"1079520178","method":"channels.setDiscussionGroup","params":[{"name":"broadcast","type":"InputChannel"},{"name":"group","type":"InputChannel"}],"type":"Bool"},{"id":"428848198","method":"messages.requestUrlAuth","params":[{"name":"flags","type":"#"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"-1322487515","method":"messages.acceptUrlAuth","params":[{"name":"flags","type":"#"},{"name":"write_allowed","type":"flags.0?true"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"1336717624","method":"messages.hidePeerSettingsBar","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-386636848","method":"contacts.addContact","params":[{"name":"flags","type":"#"},{"name":"add_phone_privacy_exception","type":"flags.0?true"},{"name":"id","type":"InputUser"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"phone","type":"string"}],"type":"Updates"},{"id":"-130964977","method":"contacts.acceptContact","params":[{"name":"id","type":"InputUser"}],"type":"Updates"},{"id":"-1892102881","method":"channels.editCreator","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"password","type":"InputCheckPasswordSRP"}],"type":"Updates"},{"id":"-750207932","method":"contacts.getLocated","params":[{"name":"flags","type":"#"},{"name":"background","type":"flags.1?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"self_expires","type":"flags.0?int"}],"type":"Updates"},{"id":"1491484525","method":"channels.editLocation","params":[{"name":"channel","type":"InputChannel"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"address","type":"string"}],"type":"Bool"},{"id":"-304832784","method":"channels.toggleSlowMode","params":[{"name":"channel","type":"InputChannel"},{"name":"seconds","type":"int"}],"type":"Updates"},{"id":"-183077365","method":"messages.getScheduledHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1111817116","method":"messages.getScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1120369398","method":"messages.sendScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"1504586518","method":"messages.deleteScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"473805619","method":"account.uploadTheme","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.0?InputFile"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"1697530880","method":"account.createTheme","params":[{"name":"flags","type":"#"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?Vector"}],"type":"Theme"},{"id":"737414348","method":"account.updateTheme","params":[{"name":"flags","type":"#"},{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"slug","type":"flags.0?string"},{"name":"title","type":"flags.1?string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?Vector"}],"type":"Theme"},{"id":"-229175188","method":"account.saveTheme","params":[{"name":"theme","type":"InputTheme"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"-953697477","method":"account.installTheme","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"theme","type":"flags.1?InputTheme"},{"name":"format","type":"flags.2?string"},{"name":"base_theme","type":"flags.3?BaseTheme"}],"type":"Bool"},{"id":"-1919060949","method":"account.getTheme","params":[{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"document_id","type":"long"}],"type":"Theme"},{"id":"1913054296","method":"account.getThemes","params":[{"name":"format","type":"string"},{"name":"hash","type":"long"}],"type":"account.Themes"},{"id":"-1210022402","method":"auth.exportLoginToken","params":[{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"except_ids","type":"Vector"}],"type":"auth.LoginToken"},{"id":"-1783866140","method":"auth.importLoginToken","params":[{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"-392909491","method":"auth.acceptLoginToken","params":[{"name":"token","type":"bytes"}],"type":"Authorization"},{"id":"-1250643605","method":"account.setContentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"}],"type":"Bool"},{"id":"-1952756306","method":"account.getContentSettings","params":[],"type":"account.ContentSettings"},{"id":"300429806","method":"channels.getInactiveChannels","params":[],"type":"messages.InactiveChats"},{"id":"1705865692","method":"account.getMultiWallPapers","params":[{"name":"wallpapers","type":"Vector"}],"type":"Vector"},{"id":"-1200736242","method":"messages.getPollVotes","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"option","type":"flags.0?bytes"},{"name":"offset","type":"flags.1?string"},{"name":"limit","type":"int"}],"type":"messages.VotesList"},{"id":"-1257951254","method":"messages.toggleStickerSets","params":[{"name":"flags","type":"#"},{"name":"uninstall","type":"flags.0?true"},{"name":"archive","type":"flags.1?true"},{"name":"unarchive","type":"flags.2?true"},{"name":"stickersets","type":"Vector"}],"type":"Bool"},{"id":"779736953","method":"payments.getBankCardData","params":[{"name":"number","type":"string"}],"type":"payments.BankCardData"},{"id":"-241247891","method":"messages.getDialogFilters","params":[],"type":"Vector"},{"id":"-1566780372","method":"messages.getSuggestedDialogFilters","params":[],"type":"Vector"},{"id":"450142282","method":"messages.updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Bool"},{"id":"-983318044","method":"messages.updateDialogFiltersOrder","params":[{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-1421720550","method":"stats.getBroadcastStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.BroadcastStats"},{"id":"1646092192","method":"stats.loadAsyncGraph","params":[{"name":"flags","type":"#"},{"name":"token","type":"string"},{"name":"x","type":"flags.0?long"}],"type":"StatsGraph"},{"id":"-1707717072","method":"stickers.setStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"85399130","method":"bots.setBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"},{"name":"commands","type":"Vector"}],"type":"Bool"},{"id":"2127598753","method":"messages.getOldFeaturedStickers","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"-1063816159","method":"help.getPromoData","params":[],"type":"help.PromoData"},{"id":"505748629","method":"help.hidePromoData","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-8744061","method":"phone.sendSignalingData","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"data","type":"bytes"}],"type":"Bool"},{"id":"-589330937","method":"stats.getMegagroupStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.MegagroupStats"},{"id":"-349483786","method":"account.getGlobalPrivacySettings","params":[],"type":"GlobalPrivacySettings"},{"id":"517647042","method":"account.setGlobalPrivacySettings","params":[{"name":"settings","type":"GlobalPrivacySettings"}],"type":"GlobalPrivacySettings"},{"id":"-183649631","method":"help.dismissSuggestion","params":[{"name":"peer","type":"InputPeer"},{"name":"suggestion","type":"string"}],"type":"Bool"},{"id":"1935116200","method":"help.getCountriesList","params":[{"name":"lang_code","type":"string"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"584962828","method":"messages.getReplies","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"1147761405","method":"messages.getDiscussionMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"messages.DiscussionMessage"},{"id":"-147740172","method":"messages.readDiscussion","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Bool"},{"id":"698914348","method":"contacts.blockFromReplies","params":[{"name":"flags","type":"#"},{"name":"delete_message","type":"flags.0?true"},{"name":"delete_history","type":"flags.1?true"},{"name":"report_spam","type":"flags.2?true"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1445996571","method":"stats.getMessagePublicForwards","params":[{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"-1226791947","method":"stats.getMessageStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"}],"type":"stats.MessageStats"},{"id":"-265962357","method":"messages.unpinAllMessages","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1221445336","method":"phone.createGroupCall","params":[{"name":"flags","type":"#"},{"name":"rtmp_stream","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"schedule_date","type":"flags.1?int"}],"type":"Updates"},{"id":"-1322057861","method":"phone.joinGroupCall","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"video_stopped","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_as","type":"InputPeer"},{"name":"invite_hash","type":"flags.1?string"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"1342404601","method":"phone.leaveGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"source","type":"int"}],"type":"Updates"},{"id":"2067345760","method":"phone.inviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"2054648117","method":"phone.discardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1958458429","method":"phone.toggleGroupCallSettings","params":[{"name":"flags","type":"#"},{"name":"reset_invite_hash","type":"flags.1?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_muted","type":"flags.0?Bool"}],"type":"Updates"},{"id":"68699611","method":"phone.getGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"limit","type":"int"}],"type":"phone.GroupCall"},{"id":"-984033109","method":"phone.getGroupParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"ids","type":"Vector"},{"name":"sources","type":"Vector"},{"name":"offset","type":"string"},{"name":"limit","type":"int"}],"type":"phone.GroupParticipants"},{"id":"-1248003721","method":"phone.checkGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"sources","type":"Vector"}],"type":"Vector"},{"id":"1540419152","method":"messages.deleteChat","params":[{"name":"chat_id","type":"long"}],"type":"Bool"},{"id":"-104078327","method":"messages.deletePhoneCallHistory","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"}],"type":"messages.AffectedFoundMessages"},{"id":"1140726259","method":"messages.checkHistoryImport","params":[{"name":"import_head","type":"string"}],"type":"messages.HistoryImportParsed"},{"id":"873008187","method":"messages.initHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"file","type":"InputFile"},{"name":"media_count","type":"int"}],"type":"messages.HistoryImport"},{"id":"713433234","method":"messages.uploadImportedMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"},{"name":"file_name","type":"string"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"-1271008444","method":"messages.startHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"}],"type":"Bool"},{"id":"-1565154314","method":"messages.getExportedChatInvites","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.3?true"},{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"},{"name":"offset_date","type":"flags.2?int"},{"name":"offset_link","type":"flags.2?string"},{"name":"limit","type":"int"}],"type":"messages.ExportedChatInvites"},{"id":"1937010524","method":"messages.getExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"messages.ExportedChatInvite"},{"id":"-1110823051","method":"messages.editExportedChatInvite","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"},{"name":"request_needed","type":"flags.3?Bool"},{"name":"title","type":"flags.4?string"}],"type":"messages.ExportedChatInvite"},{"id":"1452833749","method":"messages.deleteRevokedExportedChatInvites","params":[{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"}],"type":"Bool"},{"id":"-731601877","method":"messages.deleteExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"Bool"},{"id":"958457583","method":"messages.getAdminsWithInvites","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.ChatAdminsWithInvites"},{"id":"-553329330","method":"messages.getChatInviteImporters","params":[{"name":"flags","type":"#"},{"name":"requested","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"flags.1?string"},{"name":"q","type":"flags.2?string"},{"name":"offset_date","type":"int"},{"name":"offset_user","type":"InputUser"},{"name":"limit","type":"int"}],"type":"messages.ChatInviteImporters"},{"id":"-1207017500","method":"messages.setHistoryTTL","params":[{"name":"peer","type":"InputPeer"},{"name":"period","type":"int"}],"type":"Updates"},{"id":"-91437323","method":"account.reportProfilePhoto","params":[{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"InputPhoto"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"187239529","method":"channels.convertToGigagroup","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"1573261059","method":"messages.checkHistoryImportPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"-248985848","method":"phone.toggleGroupCallRecord","params":[{"name":"flags","type":"#"},{"name":"start","type":"flags.0?true"},{"name":"video","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"title","type":"flags.1?string"},{"name":"video_portrait","type":"flags.2?Bool"}],"type":"Updates"},{"id":"-1524155713","method":"phone.editGroupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"participant","type":"InputPeer"},{"name":"muted","type":"flags.0?Bool"},{"name":"volume","type":"flags.1?int"},{"name":"raise_hand","type":"flags.2?Bool"},{"name":"video_stopped","type":"flags.3?Bool"},{"name":"video_paused","type":"flags.4?Bool"},{"name":"presentation_paused","type":"flags.5?Bool"}],"type":"Updates"},{"id":"480685066","method":"phone.editGroupCallTitle","params":[{"name":"call","type":"InputGroupCall"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-277077702","method":"phone.getGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"}],"type":"phone.JoinAsPeers"},{"id":"-425040769","method":"phone.exportGroupCallInvite","params":[{"name":"flags","type":"#"},{"name":"can_self_unmute","type":"flags.0?true"},{"name":"call","type":"InputGroupCall"}],"type":"phone.ExportedGroupCallInvite"},{"id":"563885286","method":"phone.toggleGroupCallStartSubscription","params":[{"name":"call","type":"InputGroupCall"},{"name":"subscribed","type":"Bool"}],"type":"Updates"},{"id":"1451287362","method":"phone.startScheduledGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1465786252","method":"phone.saveDefaultGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"},{"name":"join_as","type":"InputPeer"}],"type":"Bool"},{"id":"-873829436","method":"phone.joinGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"475058500","method":"phone.leaveGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"676017721","method":"stickers.checkShortName","params":[{"name":"short_name","type":"string"}],"type":"Bool"},{"id":"1303364867","method":"stickers.suggestShortName","params":[{"name":"title","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"1032708345","method":"bots.resetBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Bool"},{"id":"-481554986","method":"bots.getBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Vector"},{"id":"-1828139493","method":"account.resetPassword","params":[],"type":"account.ResetPasswordResult"},{"id":"1284770294","method":"account.declinePasswordReset","params":[],"type":"Bool"},{"id":"221691769","method":"auth.checkRecoveryPassword","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"-700916087","method":"account.getChatThemes","params":[{"name":"hash","type":"long"}],"type":"account.Themes"},{"id":"-432283329","method":"messages.setChatTheme","params":[{"name":"peer","type":"InputPeer"},{"name":"emoticon","type":"string"}],"type":"Updates"},{"id":"-1095836780","method":"channels.viewSponsoredMessage","params":[{"name":"channel","type":"InputChannel"},{"name":"random_id","type":"bytes"}],"type":"Bool"},{"id":"-333377601","method":"channels.getSponsoredMessages","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.SponsoredMessages"},{"id":"745510839","method":"messages.getMessageReadParticipants","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Vector"},{"id":"1240514025","method":"messages.getSearchResultsCalendar","params":[{"name":"peer","type":"InputPeer"},{"name":"filter","type":"MessagesFilter"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"}],"type":"messages.SearchResultsCalendar"},{"id":"1855292323","method":"messages.getSearchResultsPositions","params":[{"name":"peer","type":"InputPeer"},{"name":"filter","type":"MessagesFilter"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.SearchResultsPositions"},{"id":"2145904661","method":"messages.hideChatJoinRequest","params":[{"name":"flags","type":"#"},{"name":"approved","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"user_id","type":"InputUser"}],"type":"Updates"},{"id":"-528091926","method":"messages.hideAllChatJoinRequests","params":[{"name":"flags","type":"#"},{"name":"approved","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"flags.1?string"}],"type":"Updates"},{"id":"-1323389022","method":"messages.toggleNoForwards","params":[{"name":"peer","type":"InputPeer"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"-855777386","method":"messages.saveDefaultSendAs","params":[{"name":"peer","type":"InputPeer"},{"name":"send_as","type":"InputPeer"}],"type":"Bool"},{"id":"231174382","method":"channels.getSendAs","params":[{"name":"peer","type":"InputPeer"}],"type":"channels.SendAsPeers"},{"id":"-1081501024","method":"account.setAuthorizationTTL","params":[{"name":"authorization_ttl_days","type":"int"}],"type":"Bool"},{"id":"1089766498","method":"account.changeAuthorizationSettings","params":[{"name":"flags","type":"#"},{"name":"hash","type":"long"},{"name":"encrypted_requests_disabled","type":"flags.0?Bool"},{"name":"call_requests_disabled","type":"flags.1?Bool"}],"type":"Bool"},{"id":"913655003","method":"channels.deleteParticipantHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"627641572","method":"messages.sendReaction","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"reaction","type":"flags.0?string"}],"type":"Updates"},{"id":"-1950707482","method":"messages.getMessagesReactions","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"-521245833","method":"messages.getMessageReactionsList","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"reaction","type":"flags.0?string"},{"name":"offset","type":"flags.1?string"},{"name":"limit","type":"int"}],"type":"messages.MessageReactionsList"},{"id":"335875750","method":"messages.setChatAvailableReactions","params":[{"name":"peer","type":"InputPeer"},{"name":"available_reactions","type":"Vector"}],"type":"Updates"},{"id":"417243308","method":"messages.getAvailableReactions","params":[{"name":"hash","type":"int"}],"type":"messages.AvailableReactions"},{"id":"-647969580","method":"messages.setDefaultReaction","params":[{"name":"reaction","type":"string"}],"type":"Bool"},{"id":"617508334","method":"messages.translateText","params":[{"name":"flags","type":"#"},{"name":"peer","type":"flags.0?InputPeer"},{"name":"msg_id","type":"flags.0?int"},{"name":"text","type":"flags.1?string"},{"name":"from_lang","type":"flags.2?string"},{"name":"to_lang","type":"string"}],"type":"messages.TranslatedText"},{"id":"-396644838","method":"messages.getUnreadReactions","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"}],"type":"messages.Messages"},{"id":"-2099097129","method":"messages.readReactions","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"}]} \ No newline at end of file diff --git a/data/corefork.telegram.org/schema/mtproto-json.html b/data/corefork.telegram.org/schema/mtproto-json.html new file mode 100644 index 0000000000..ceca9f3321 --- /dev/null +++ b/data/corefork.telegram.org/schema/mtproto-json.html @@ -0,0 +1 @@ +{"constructors":[{"id":"481674261","predicate":"vector","params":[],"type":"Vector t"},{"id":"85337187","predicate":"resPQ","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"pq","type":"bytes"},{"name":"server_public_key_fingerprints","type":"Vector"}],"type":"ResPQ"},{"id":"-1443537003","predicate":"p_q_inner_data_dc","params":[{"name":"pq","type":"bytes"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce","type":"int256"},{"name":"dc","type":"int"}],"type":"P_Q_inner_data"},{"id":"1459478408","predicate":"p_q_inner_data_temp_dc","params":[{"name":"pq","type":"bytes"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce","type":"int256"},{"name":"dc","type":"int"},{"name":"expires_in","type":"int"}],"type":"P_Q_inner_data"},{"id":"-790100132","predicate":"server_DH_params_ok","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"encrypted_answer","type":"bytes"}],"type":"Server_DH_Params"},{"id":"-1249309254","predicate":"server_DH_inner_data","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"g","type":"int"},{"name":"dh_prime","type":"bytes"},{"name":"g_a","type":"bytes"},{"name":"server_time","type":"int"}],"type":"Server_DH_inner_data"},{"id":"1715713620","predicate":"client_DH_inner_data","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"retry_id","type":"long"},{"name":"g_b","type":"bytes"}],"type":"Client_DH_Inner_Data"},{"id":"1003222836","predicate":"dh_gen_ok","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash1","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"1188831161","predicate":"dh_gen_retry","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash2","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"-1499615742","predicate":"dh_gen_fail","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash3","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"1973679973","predicate":"bind_auth_key_inner","params":[{"name":"nonce","type":"long"},{"name":"temp_auth_key_id","type":"long"},{"name":"perm_auth_key_id","type":"long"},{"name":"temp_session_id","type":"long"},{"name":"expires_at","type":"int"}],"type":"BindAuthKeyInner"},{"id":"-212046591","predicate":"rpc_result","params":[{"name":"req_msg_id","type":"long"},{"name":"result","type":"Object"}],"type":"RpcResult"},{"id":"558156313","predicate":"rpc_error","params":[{"name":"error_code","type":"int"},{"name":"error_message","type":"string"}],"type":"RpcError"},{"id":"1579864942","predicate":"rpc_answer_unknown","params":[],"type":"RpcDropAnswer"},{"id":"-847714938","predicate":"rpc_answer_dropped_running","params":[],"type":"RpcDropAnswer"},{"id":"-1539647305","predicate":"rpc_answer_dropped","params":[{"name":"msg_id","type":"long"},{"name":"seq_no","type":"int"},{"name":"bytes","type":"int"}],"type":"RpcDropAnswer"},{"id":"155834844","predicate":"future_salt","params":[{"name":"valid_since","type":"int"},{"name":"valid_until","type":"int"},{"name":"salt","type":"long"}],"type":"FutureSalt"},{"id":"-1370486635","predicate":"future_salts","params":[{"name":"req_msg_id","type":"long"},{"name":"now","type":"int"},{"name":"salts","type":"vector"}],"type":"FutureSalts"},{"id":"880243653","predicate":"pong","params":[{"name":"msg_id","type":"long"},{"name":"ping_id","type":"long"}],"type":"Pong"},{"id":"-501201412","predicate":"destroy_session_ok","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"1658015945","predicate":"destroy_session_none","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"-1631450872","predicate":"new_session_created","params":[{"name":"first_msg_id","type":"long"},{"name":"unique_id","type":"long"},{"name":"server_salt","type":"long"}],"type":"NewSession"},{"id":"1945237724","predicate":"msg_container","params":[{"name":"messages","type":"vector<%Message>"}],"type":"MessageContainer"},{"id":"1538843921","predicate":"message","params":[{"name":"msg_id","type":"long"},{"name":"seqno","type":"int"},{"name":"bytes","type":"int"},{"name":"body","type":"Object"}],"type":"Message"},{"id":"-530561358","predicate":"msg_copy","params":[{"name":"orig_message","type":"Message"}],"type":"MessageCopy"},{"id":"812830625","predicate":"gzip_packed","params":[{"name":"packed_data","type":"bytes"}],"type":"Object"},{"id":"1658238041","predicate":"msgs_ack","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgsAck"},{"id":"-1477445615","predicate":"bad_msg_notification","params":[{"name":"bad_msg_id","type":"long"},{"name":"bad_msg_seqno","type":"int"},{"name":"error_code","type":"int"}],"type":"BadMsgNotification"},{"id":"-307542917","predicate":"bad_server_salt","params":[{"name":"bad_msg_id","type":"long"},{"name":"bad_msg_seqno","type":"int"},{"name":"error_code","type":"int"},{"name":"new_server_salt","type":"long"}],"type":"BadMsgNotification"},{"id":"2105940488","predicate":"msg_resend_req","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgResendReq"},{"id":"-630588590","predicate":"msgs_state_req","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgsStateReq"},{"id":"81704317","predicate":"msgs_state_info","params":[{"name":"req_msg_id","type":"long"},{"name":"info","type":"bytes"}],"type":"MsgsStateInfo"},{"id":"-1933520591","predicate":"msgs_all_info","params":[{"name":"msg_ids","type":"Vector"},{"name":"info","type":"bytes"}],"type":"MsgsAllInfo"},{"id":"661470918","predicate":"msg_detailed_info","params":[{"name":"msg_id","type":"long"},{"name":"answer_msg_id","type":"long"},{"name":"bytes","type":"int"},{"name":"status","type":"int"}],"type":"MsgDetailedInfo"},{"id":"-2137147681","predicate":"msg_new_detailed_info","params":[{"name":"answer_msg_id","type":"long"},{"name":"bytes","type":"int"},{"name":"status","type":"int"}],"type":"MsgDetailedInfo"},{"id":"-161422892","predicate":"destroy_auth_key_ok","params":[],"type":"DestroyAuthKeyRes"},{"id":"178201177","predicate":"destroy_auth_key_none","params":[],"type":"DestroyAuthKeyRes"},{"id":"-368010477","predicate":"destroy_auth_key_fail","params":[],"type":"DestroyAuthKeyRes"}],"methods":[{"id":"-1099002127","method":"req_pq_multi","params":[{"name":"nonce","type":"int128"}],"type":"ResPQ"},{"id":"-686627650","method":"req_DH_params","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"public_key_fingerprint","type":"long"},{"name":"encrypted_data","type":"bytes"}],"type":"Server_DH_Params"},{"id":"-184262881","method":"set_client_DH_params","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"encrypted_data","type":"bytes"}],"type":"Set_client_DH_params_answer"},{"id":"1491380032","method":"rpc_drop_answer","params":[{"name":"req_msg_id","type":"long"}],"type":"RpcDropAnswer"},{"id":"-1188971260","method":"get_future_salts","params":[{"name":"num","type":"int"}],"type":"FutureSalts"},{"id":"2059302892","method":"ping","params":[{"name":"ping_id","type":"long"}],"type":"Pong"},{"id":"-213746804","method":"ping_delay_disconnect","params":[{"name":"ping_id","type":"long"},{"name":"disconnect_delay","type":"int"}],"type":"Pong"},{"id":"-414113498","method":"destroy_session","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"-1835453025","method":"http_wait","params":[{"name":"max_delay","type":"int"},{"name":"wait_after","type":"int"},{"name":"max_wait","type":"int"}],"type":"HttpWait"},{"id":"-784117408","method":"destroy_auth_key","params":[],"type":"DestroyAuthKeyRes"}]} \ No newline at end of file diff --git a/data/corefork.telegram.org/schema/mtproto.html b/data/corefork.telegram.org/schema/mtproto.html new file mode 100644 index 0000000000..4da64ba771 --- /dev/null +++ b/data/corefork.telegram.org/schema/mtproto.html @@ -0,0 +1,204 @@ + + + + + Current MTProto TL-schema + + + + + + + + + + + + + +
+ +
+
+
+ +

Current MTProto TL-schema

+ +

Below you will find the current MTProto TL-schema. More details on TL »

+

See also the detailed schema in JSON »

+


+
int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+
+vector {t:Type} # [ t ] = Vector t;
+
+int128 4*[ int ] = Int128;
+int256 8*[ int ] = Int256;
+
+resPQ#05162463 nonce:int128 server_nonce:int128 pq:bytes server_public_key_fingerprints:Vector<long> = ResPQ;
+
+p_q_inner_data_dc#a9f55f95 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int = P_Q_inner_data;
+p_q_inner_data_temp_dc#56fddf88 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int expires_in:int = P_Q_inner_data;
+
+server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:bytes = Server_DH_Params;
+
+server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:bytes g_a:bytes server_time:int = Server_DH_inner_data;
+
+client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:bytes = Client_DH_Inner_Data;
+
+dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
+dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
+dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
+
+bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
+
+rpc_result#f35c6d01 req_msg_id:long result:Object = RpcResult;
+rpc_error#2144ca19 error_code:int error_message:string = RpcError;
+
+rpc_answer_unknown#5e2ad36e = RpcDropAnswer;
+rpc_answer_dropped_running#cd78e586 = RpcDropAnswer;
+rpc_answer_dropped#a43ad8b7 msg_id:long seq_no:int bytes:int = RpcDropAnswer;
+
+future_salt#0949d9dc valid_since:int valid_until:int salt:long = FutureSalt;
+future_salts#ae500895 req_msg_id:long now:int salts:vector<future_salt> = FutureSalts;
+
+pong#347773c5 msg_id:long ping_id:long = Pong;
+
+destroy_session_ok#e22045fc session_id:long = DestroySessionRes;
+destroy_session_none#62d350c9 session_id:long = DestroySessionRes;
+
+new_session_created#9ec20908 first_msg_id:long unique_id:long server_salt:long = NewSession;
+
+msg_container#73f1f8dc messages:vector<%Message> = MessageContainer;
+message msg_id:long seqno:int bytes:int body:Object = Message;
+msg_copy#e06046b2 orig_message:Message = MessageCopy;
+
+gzip_packed#3072cfa1 packed_data:bytes = Object;
+
+msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
+
+bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
+bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
+
+msg_resend_req#7d861a08 msg_ids:Vector<long> = MsgResendReq;
+msgs_state_req#da69fb52 msg_ids:Vector<long> = MsgsStateReq;
+msgs_state_info#04deb57d req_msg_id:long info:bytes = MsgsStateInfo;
+msgs_all_info#8cc0d131 msg_ids:Vector<long> info:bytes = MsgsAllInfo;
+msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+
+destroy_auth_key_ok#f660e1d4 = DestroyAuthKeyRes;
+destroy_auth_key_none#0a9f2259 = DestroyAuthKeyRes;
+destroy_auth_key_fail#ea109b13 = DestroyAuthKeyRes;
+
+---functions---
+
+req_pq_multi#be7e8ef1 nonce:int128 = ResPQ;
+
+req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:bytes q:bytes public_key_fingerprint:long encrypted_data:bytes = Server_DH_Params;
+
+set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:bytes = Set_client_DH_params_answer;
+
+rpc_drop_answer#58e4a740 req_msg_id:long = RpcDropAnswer;
+get_future_salts#b921bd04 num:int = FutureSalts;
+ping#7abe77ec ping_id:long = Pong;
+ping_delay_disconnect#f3427b8c ping_id:long disconnect_delay:int = Pong;
+destroy_session#e7512126 session_id:long = DestroySessionRes;
+
+http_wait#9299359f max_delay:int wait_after:int max_wait:int = HttpWait;
+
+destroy_auth_key#d1435160 = DestroyAuthKeyRes;
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/themes.html b/data/corefork.telegram.org/themes.html new file mode 100644 index 0000000000..c0f349d55b --- /dev/null +++ b/data/corefork.telegram.org/themes.html @@ -0,0 +1,143 @@ + + + + + Creating Custom Cloud Themes + + + + + + + + + + + + + +
+ +
+
+
+
+

Creating Custom Cloud Themes

+ +

Official Telegram apps support custom cloud themes as of version 5.11. Everyone is welcome to create and share their themes.

+

Creating a theme

+

You can use the Online Theme Editor (use a VPN if it is blocked in your country) to create new Telegram themes from scratch or edit existing ones. Simply log in with your Telegram account and pick a platform to start editing the relevant theme file – or import an existing theme.

+
    +
  • Set a name for your theme using the name attribute
  • +
  • Set colors for elements using hex codes or the color picker
  • +
  • Press ‘Save and apply theme’ to push changes to all users of your theme
  • +
+

Checking your theme in-app

+

Once you have saved a theme for the first time, Telegram will send you a message with its sharing link. Open the link in the app to switch to your theme.

+

You can always switch to your theme in Settings > Chat Settings. On iOS and MacOS native app – Settings > Appearance.

+

Publishing your theme

+

Each theme has a t.me/addtheme link which people can use to switch to your theme. You can choose a beautiful short link (e.g., https://t.me/addtheme/desert) by changing the shortname attribute. If you add support for multiple platforms, the same link can be used for setting your theme on all of them.

+

Updating your theme

+

Your theme gets updated automatically for all its users whenever you save and apply changes.

+

Including a chat background

+

Your themes can include a custom wallpaper. To do this, simply go to Settings > Chat Settings > Chat Background. On iOS and MacOS native app – Settings > Appearance > Chat Background.

+

Open any background and tap the sharing button in the top right corner, then copy its t.me/bg/... link. In the theme file, set this link as the value of the wallpaper attribute.

+

For Telegram Desktop, if you want to make the background tiled, add ?mode=tiled at the end of the link. For example:

+
wallpaper: t.me/bg/-jI7lnO3DFABAAAA1vXcFaZP_Vo?mode=tiled
+

Creating themes in-app

+

If you prefer a more WYSIWYG approach, try creating themes using the in-app tools for customizing appearance. Telegram for Android and Telegram Desktop have advanced in-app theme editors. Telegram for iOS and MacOS allow choosing a custom accent color from the color wheel and a background, then saving the result as a custom theme.

+

Once you have saved a new theme in any of the apps, it also becomes accessible in the online editor.

+

Read more

+ +
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/AccountDaysTTL.html b/data/corefork.telegram.org/type/AccountDaysTTL.html new file mode 100644 index 0000000000..1ba793a7a3 --- /dev/null +++ b/data/corefork.telegram.org/type/AccountDaysTTL.html @@ -0,0 +1,162 @@ + + + + + AccountDaysTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

AccountDaysTTL

+ +

Time-to-live of current account

+

+ +
+
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+
+---functions---
+
+account.getAccountTTL#8fc711d = AccountDaysTTL;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
accountDaysTTLTime to live in days of the current account
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAccountTTLGet days to live of account
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Audio.html b/data/corefork.telegram.org/type/Audio.html new file mode 100644 index 0000000000..8c7a3a12ed --- /dev/null +++ b/data/corefork.telegram.org/type/Audio.html @@ -0,0 +1,128 @@ + + + + + Audio + + + + + + + + + + + + + +
+ +
+
+
+ +

Audio

+ +

Audio file.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Authorization.html b/data/corefork.telegram.org/type/Authorization.html new file mode 100644 index 0000000000..c9e3998b95 --- /dev/null +++ b/data/corefork.telegram.org/type/Authorization.html @@ -0,0 +1,162 @@ + + + + + Authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

Authorization

+ +

Represents a logged-in session

+

+ +
+
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+
+---functions---
+
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
authorizationLogged-in session
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
auth.acceptLoginTokenLogin via QR code
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/AutoDownloadSettings.html b/data/corefork.telegram.org/type/AutoDownloadSettings.html new file mode 100644 index 0000000000..3c07ca5eea --- /dev/null +++ b/data/corefork.telegram.org/type/AutoDownloadSettings.html @@ -0,0 +1,143 @@ + + + + + AutoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

AutoDownloadSettings

+ +

Media autodownload settings

+

+ +
+
autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
autoDownloadSettingsAutodownload settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/AvailableReaction.html b/data/corefork.telegram.org/type/AvailableReaction.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/AvailableReaction.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/BankCardOpenUrl.html b/data/corefork.telegram.org/type/BankCardOpenUrl.html new file mode 100644 index 0000000000..77b59ddd4e --- /dev/null +++ b/data/corefork.telegram.org/type/BankCardOpenUrl.html @@ -0,0 +1,143 @@ + + + + + BankCardOpenUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

BankCardOpenUrl

+ +

Credit card info URL provided by the bank

+

+ +
+
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
bankCardOpenUrlCredit card info URL provided by the bank
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/BaseTheme.html b/data/corefork.telegram.org/type/BaseTheme.html new file mode 100644 index 0000000000..c5e655d13a --- /dev/null +++ b/data/corefork.telegram.org/type/BaseTheme.html @@ -0,0 +1,163 @@ + + + + + BaseTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

BaseTheme

+ +

Basic theme settings

+

+ +
+
baseThemeClassic#c3a12462 = BaseTheme;
+baseThemeDay#fbd81688 = BaseTheme;
+baseThemeNight#b7b31ea8 = BaseTheme;
+baseThemeTinted#6d5f77ee = BaseTheme;
+baseThemeArctic#5b11125a = BaseTheme;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
baseThemeClassicClassic theme
baseThemeDayDay theme
baseThemeNightNight theme
baseThemeTintedTinted theme
baseThemeArcticArctic theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Bool.html b/data/corefork.telegram.org/type/Bool.html new file mode 100644 index 0000000000..5588014a09 --- /dev/null +++ b/data/corefork.telegram.org/type/Bool.html @@ -0,0 +1,721 @@ + + + + + Bool + + + + + + + + + + + + + +
+ +
+
+
+ +

Bool

+ +

Boolean type.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+---functions---
+
+auth.resetAuthorizations#9fab0d1a = Bool;
+auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
+auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;
+auth.checkRecoveryPassword#d36bf79 code:string = Bool;
+
+account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;
+account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;
+account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;
+account.resetNotifySettings#db7e1747 = Bool;
+account.updateStatus#6628562c offline:Bool = Bool;
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;
+account.checkUsername#2714d86c username:string = Bool;
+account.deleteAccount#418d4e0b reason:string = Bool;
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;
+account.updateDeviceLocked#38df3532 period:int = Bool;
+account.resetAuthorization#df77f3bc hash:long = Bool;
+account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;
+account.resetWebAuthorization#2d01b9ef hash:long = Bool;
+account.resetWebAuthorizations#682d2594 = Bool;
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
+account.verifyEmail#ecba39db email:string code:string = Bool;
+account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;
+account.confirmPasswordEmail#8fdf1920 code:string = Bool;
+account.resendPasswordEmail#7a7f2a15 = Bool;
+account.cancelPasswordEmail#c1cbd5b6 = Bool;
+account.getContactSignUpNotification#9f07c728 = Bool;
+account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;
+account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
+account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
+account.resetWallPapers#bb3b9804 = Bool;
+account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;
+account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
+account.installTheme#c727bb3b flags:# dark:flags.0?true theme:flags.1?InputTheme format:flags.2?string base_theme:flags.3?BaseTheme = Bool;
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;
+account.declinePasswordReset#4c9409f6 = Bool;
+account.setAuthorizationTTL#bf899aa0 authorization_ttl_days:int = Bool;
+account.changeAuthorizationSettings#40f48462 flags:# hash:long encrypted_requests_disabled:flags.0?Bool call_requests_disabled:flags.1?Bool = Bool;
+
+contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;
+contacts.block#68cc1411 id:InputPeer = Bool;
+contacts.unblock#bea65d50 id:InputPeer = Bool;
+contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;
+contacts.resetSaved#879537f1 = Bool;
+contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;
+
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+messages.reportSpam#cf1592db peer:InputPeer = Bool;
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;
+messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;
+messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;
+messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;
+messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;
+messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;
+messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
+messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
+messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
+messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;
+messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;
+messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;
+messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
+messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;
+messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
+messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;
+messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;
+messages.clearAllDrafts#7e58ee9c = Bool;
+messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;
+messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;
+messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;
+messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
+messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
+messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;
+messages.deleteChat#5bd0ee50 chat_id:long = Bool;
+messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
+messages.saveDefaultSendAs#ccfddf96 peer:InputPeer send_as:InputPeer = Bool;
+messages.setDefaultReaction#d960c4d4 reaction:string = Bool;
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
+
+channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;
+channels.reportSpam#f44a8315 channel:InputChannel participant:InputPeer id:Vector<int> = Bool;
+channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
+channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
+channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;
+channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;
+channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;
+channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
+
+help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
+help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
+
+bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
+
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
+
+phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
+phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;
+
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
+
+stickers.checkShortName#284b3639 short_name:string = Bool;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
boolFalseConstructor may be interpreted as a booleanfalse value.
boolTrueThe constructor can be interpreted as a booleantrue value.
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
auth.logOutLogs out the user.
auth.resetAuthorizationsTerminates all user's authorized sessions except for the current one.

After calling this method it is necessary to reregister the current device using the method account.registerDevice
auth.bindTempAuthKeyBinds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

For more information, see Perfect Forward Secrecy.
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
account.updateStatusUpdates online user status.
account.reportPeerReport a peer for violation of telegram's Terms of Service
contacts.deleteByPhonesDelete contacts by phone number
contacts.blockAdds the user to the blacklist.
contacts.unblockDeletes the user from the blacklist.
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportReport a message in a chat for violation of telegram's Terms of Service
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.reportEncryptedSpamReport a secret chat for spam
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
account.checkUsernameValidates a username and checks availability.
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.setAccountTTLSet account self-destruction period
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.resetAuthorizationLog out an active authorized session by it hash
account.updatePasswordSettingsSet a new 2FA password
messages.uninstallStickerSetUninstall a stickerset
channels.readHistoryMark channel/supergroup history as read
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
messages.editChatAdminMake a user admin in a legacy group.
messages.reorderStickerSetsReorder installed stickersets
messages.saveGifAdd GIF to saved gifs list
messages.setInlineBotResultsAnswer an inline query, for bots only
auth.cancelCodeCancel the login verification code
messages.editInlineBotMessageEdit an inline bot message
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
contacts.resetTopPeerRatingReset rating of top peer
messages.saveDraftSave a message draft associated to a chat.
messages.readFeaturedStickersMark new featured stickers as read
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.clearRecentStickersClear recent stickers
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
payments.clearSavedInfoClear saved payment information
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
Use this method to respond to such pre-checkout queries.
Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.saveCallDebugSend phone call debug data to server
channels.setStickersAssociate a stickerset to the supergroup
messages.faveStickerMark a sticker as favorite
channels.readMessageContentsMark channel/supergroup message contents as read
contacts.resetSavedDelete saved contacts
channels.deleteHistoryDelete the history of a supergroup
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
help.acceptTermsOfServiceAccept the new terms of service
account.deleteSecureValueDelete stored telegram passport value
users.setSecureValueErrorsSet secure passport value errors for a user
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.verifyPhoneVerify a phone number for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.finishTakeoutSessionFinish account takeout session
messages.markDialogUnreadManually mark dialog as unread
contacts.toggleTopPeersEnable/disable top peers
messages.clearAllDraftsClear all drafts.
help.saveAppLogSaves logs of application on the server.
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
messages.editChatAboutEdit the description of a group/supergroup/channel.
account.saveWallPaperInstall/uninstall wallpaper
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveAutoDownloadSettingsChange media autodownload settings
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
channels.editLocationEdit location of geogroup
account.saveThemeSave a theme
account.installThemeInstall a theme
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
messages.toggleStickerSetsApply changes to multiple stickersets
messages.updateDialogFilterUpdate folder
messages.updateDialogFiltersOrderReorder folders
bots.setBotCommandsSet bot command list
help.hidePromoDataHide MTProxy/Public Service Announcement information
phone.sendSignalingDataSend VoIP signaling data
help.dismissSuggestionDismiss a suggestion
messages.readDiscussionMark a channel discussion as read
messages.deleteChatDelete a chat
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteExportedChatInviteDelete a chat invite
account.reportProfilePhotoReport a profile photo of a dialog
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
stickers.checkShortNameCheck whether the given short name is available
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
account.declinePasswordResetAbort a pending 2FA password reset
auth.checkRecoveryPasswordCheck if the recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
channels.viewSponsoredMessageMark a specific sponsored message as read
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/BotCommand.html b/data/corefork.telegram.org/type/BotCommand.html new file mode 100644 index 0000000000..38bb3e7adc --- /dev/null +++ b/data/corefork.telegram.org/type/BotCommand.html @@ -0,0 +1,143 @@ + + + + + BotCommand + + + + + + + + + + + + + +
+ +
+
+
+ +

BotCommand

+ +

Describes a bot command that can be used in a chat

+

+ +
+
botCommand#c27ac8c7 command:string description:string = BotCommand;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
botCommandDescribes a bot command that can be used in a chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/BotCommandScope.html b/data/corefork.telegram.org/type/BotCommandScope.html new file mode 100644 index 0000000000..f6acb1028e --- /dev/null +++ b/data/corefork.telegram.org/type/BotCommandScope.html @@ -0,0 +1,176 @@ + + + + + BotCommandScope + + + + + + + + + + + + + +
+ +
+
+
+ +

BotCommandScope

+ +

Represents a scope where the bot commands, specified using bots.setBotCommands will be valid.

+

+ +
+
botCommandScopeDefault#2f6cb2ab = BotCommandScope;
+botCommandScopeUsers#3c4f04d8 = BotCommandScope;
+botCommandScopeChats#6fe1a881 = BotCommandScope;
+botCommandScopeChatAdmins#b9aa606a = BotCommandScope;
+botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;
+botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;
+botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
botCommandScopeDefaultThe commands will be valid in all chats
botCommandScopeUsersThe specified bot commands will only be valid in all private chats with users.
botCommandScopeChatsThe specified bot commands will be valid in all groups and supergroups
botCommandScopeChatAdminsThe specified bot commands will be valid only for chat administrators, in all groups and supergroups.
botCommandScopePeerThe specified bot commands will be valid only in a specific dialog
botCommandScopePeerAdminsThe specified bot commands will be valid for all admins of the specified group or supergroup.
botCommandScopePeerUserThe specified bot commands will be valid only for a specific user in the specified chat
+

Related pages

+

bots.setBotCommands

+

Set bot command list

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/BotInfo.html b/data/corefork.telegram.org/type/BotInfo.html new file mode 100644 index 0000000000..f080fe4b89 --- /dev/null +++ b/data/corefork.telegram.org/type/BotInfo.html @@ -0,0 +1,143 @@ + + + + + BotInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

BotInfo

+ +

Info about bots (available bot commands, etc)

+

+ +
+
botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
botInfoInfo about bots (available bot commands, etc)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/BotInlineResult.html b/data/corefork.telegram.org/type/BotInlineResult.html new file mode 100644 index 0000000000..b057602d10 --- /dev/null +++ b/data/corefork.telegram.org/type/BotInlineResult.html @@ -0,0 +1,148 @@ + + + + + BotInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

BotInlineResult

+ +

Results of an inline query

+

+ +
+
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
+botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
botInlineResultGeneric result
botInlineMediaResultMedia result
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/CdnConfig.html b/data/corefork.telegram.org/type/CdnConfig.html new file mode 100644 index 0000000000..cf2ef47c14 --- /dev/null +++ b/data/corefork.telegram.org/type/CdnConfig.html @@ -0,0 +1,164 @@ + + + + + CdnConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

CdnConfig

+ +

Configuration for CDN file downloads.

+

+ +
+
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
+
+---functions---
+
+help.getCdnConfig#52029342 = CdnConfig;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
cdnConfigConfiguration for CDN file downloads.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getCdnConfigGet configuration for CDN file downloads.
+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/CdnPublicKey.html b/data/corefork.telegram.org/type/CdnPublicKey.html new file mode 100644 index 0000000000..a29f94291b --- /dev/null +++ b/data/corefork.telegram.org/type/CdnPublicKey.html @@ -0,0 +1,145 @@ + + + + + CdnPublicKey + + + + + + + + + + + + + +
+ +
+
+
+ +

CdnPublicKey

+ +

Public key to use only during handshakes to CDN DCs.

+

+ +
+
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
cdnPublicKeyPublic key to use only during handshakes to CDN DCs.
+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelAdminLogEvent.html b/data/corefork.telegram.org/type/ChannelAdminLogEvent.html new file mode 100644 index 0000000000..ea8cf07dff --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelAdminLogEvent.html @@ -0,0 +1,143 @@ + + + + + ChannelAdminLogEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelAdminLogEvent

+ +

An event in a channel admin log

+

+ +
+
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channelAdminLogEventAdmin log event
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelAdminLogEventAction.html b/data/corefork.telegram.org/type/ChannelAdminLogEventAction.html new file mode 100644 index 0000000000..4aad102c44 --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelAdminLogEventAction.html @@ -0,0 +1,302 @@ + + + + + ChannelAdminLogEventAction + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelAdminLogEventAction

+ +

Channel admin log event

+

+ +
+
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
+channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
+channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
+channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;
+channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantVolume#3e7f6847 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoinByRequest#afb6144a invite:ExportedChatInvite approved_by:long = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleNoForwards#cb2ac766 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionSendMessage#278f2868 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeAvailableReactions#9cf7f76a prev_value:Vector<string> new_value:Vector<string> = ChannelAdminLogEventAction;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
channelAdminLogEventActionChangeTitleChannel/supergroup title was changed
channelAdminLogEventActionChangeAboutThe description was changed
channelAdminLogEventActionChangeUsernameChannel/supergroup username was changed
channelAdminLogEventActionChangePhotoThe channel/supergroup's picture was changed
channelAdminLogEventActionToggleInvitesInvites were enabled/disabled
channelAdminLogEventActionToggleSignaturesChannel signatures were enabled/disabled
channelAdminLogEventActionUpdatePinnedA message was pinned
channelAdminLogEventActionEditMessageA message was edited
channelAdminLogEventActionDeleteMessageA message was deleted
channelAdminLogEventActionParticipantJoinA user has joined the group (in the case of big groups, info of the user that has joined isn't shown)
channelAdminLogEventActionParticipantLeaveA user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)
channelAdminLogEventActionParticipantInviteA user was invited to the group
channelAdminLogEventActionParticipantToggleBanThe banned rights of a user were changed
channelAdminLogEventActionParticipantToggleAdminThe admin rights of a user were changed
channelAdminLogEventActionChangeStickerSetThe supergroup's stickerset was changed
channelAdminLogEventActionTogglePreHistoryHiddenThe hidden prehistory setting was changed
channelAdminLogEventActionDefaultBannedRightsThe default banned rights were modified
channelAdminLogEventActionStopPollA poll was stopped
channelAdminLogEventActionChangeLinkedChatThe linked chat was changed
channelAdminLogEventActionChangeLocationThe geogroup location was changed
channelAdminLogEventActionToggleSlowModeSlow mode setting for supergroups was changed
channelAdminLogEventActionStartGroupCallA group call was started
channelAdminLogEventActionDiscardGroupCallA group call was terminated
channelAdminLogEventActionParticipantMuteA group call participant was muted
channelAdminLogEventActionParticipantUnmuteA group call participant was unmuted
channelAdminLogEventActionToggleGroupCallSettingGroup call settings were changed
channelAdminLogEventActionParticipantJoinByInviteA user joined the supergroup/channel using a specific invite link
channelAdminLogEventActionExportedInviteDeleteA chat invite was deleted
channelAdminLogEventActionExportedInviteRevokeA specific invite link was revoked
channelAdminLogEventActionExportedInviteEditA chat invite was edited
channelAdminLogEventActionParticipantVolumechannelAdminLogEvent.user_id has set the volume of participant.peer to participant.volume
channelAdminLogEventActionChangeHistoryTTLThe Time-To-Live of messages in this chat was changed
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html b/data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html new file mode 100644 index 0000000000..88eb93a12f --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html @@ -0,0 +1,143 @@ + + + + + ChannelAdminLogEventsFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelAdminLogEventsFilter

+ +

Filter for fetching events in the channel admin log

+

+ +
+
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channelAdminLogEventsFilterFilter only certain admin log events
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelLocation.html b/data/corefork.telegram.org/type/ChannelLocation.html new file mode 100644 index 0000000000..c966b75734 --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelLocation.html @@ -0,0 +1,148 @@ + + + + + ChannelLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelLocation

+ +

Geographical location of supergroup (geogroups)

+

+ +
+
channelLocationEmpty#bfb5ad8b = ChannelLocation;
+channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
channelLocationEmptyNo location (normal supergroup)
channelLocationGeographical location of supergroup (geogroups)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelMessagesFilter.html b/data/corefork.telegram.org/type/ChannelMessagesFilter.html new file mode 100644 index 0000000000..901f70b731 --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelMessagesFilter.html @@ -0,0 +1,148 @@ + + + + + ChannelMessagesFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelMessagesFilter

+ +

Filter for fetching only certain types of channel messages

+

+ +
+
channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;
+channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
channelMessagesFilterEmptyNo filter
channelMessagesFilterFilter for getting only certain types of channel messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelParticipant.html b/data/corefork.telegram.org/type/ChannelParticipant.html new file mode 100644 index 0000000000..cac59fdde8 --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelParticipant.html @@ -0,0 +1,168 @@ + + + + + ChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelParticipant

+ +

Channel participant

+

+ +
+
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
+channelParticipantSelf#35a8bfa7 flags:# via_request:flags.0?true user_id:long inviter_id:long date:int = ChannelParticipant;
+channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
+channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
+channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
+channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
channelParticipantChannel/supergroup participant
channelParticipantSelfMyself
channelParticipantCreatorChannel/supergroup creator
channelParticipantAdminAdmin
channelParticipantBannedBanned/kicked user
channelParticipantLeftA participant that left the channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelParticipantsFilter.html b/data/corefork.telegram.org/type/ChannelParticipantsFilter.html new file mode 100644 index 0000000000..f4e71d8af3 --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelParticipantsFilter.html @@ -0,0 +1,178 @@ + + + + + ChannelParticipantsFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelParticipantsFilter

+ +

Filter for fetching channel participants

+

+ +
+
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;
+channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;
+channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;
+channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;
+channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;
+channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;
+channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;
+channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
channelParticipantsRecentFetch only recent participants
channelParticipantsAdminsFetch only admin participants
channelParticipantsKickedFetch only kicked participants
channelParticipantsBotsFetch only bot participants
channelParticipantsBannedFetch only banned participants
channelParticipantsSearchQuery participants by name
channelParticipantsContactsFetch only participants that are also contacts
channelParticipantsMentionsThis filter is used when looking for members to mention.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Chat.html b/data/corefork.telegram.org/type/Chat.html new file mode 100644 index 0000000000..379b4fd8c5 --- /dev/null +++ b/data/corefork.telegram.org/type/Chat.html @@ -0,0 +1,163 @@ + + + + + Chat + + + + + + + + + + + + + +
+ +
+
+
+ +

Chat

+ +

Object defines a group.

+

+ +
+
chatEmpty#29562865 id:long = Chat;
+chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;
+chatForbidden#6592a1a7 id:long title:string = Chat;
+channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;
+channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
chatEmptyEmpty constructor, group doesn't exist
chatInfo about a group
chatForbiddenA group to which the user has no access. E.g., because the user was kicked from the group.
channelChannel/supergroup info
channelForbiddenIndicates a channel/supergroup we can't access because we were banned, or for some other reason.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatAdminRights.html b/data/corefork.telegram.org/type/ChatAdminRights.html new file mode 100644 index 0000000000..c3f792e9dc --- /dev/null +++ b/data/corefork.telegram.org/type/ChatAdminRights.html @@ -0,0 +1,146 @@ + + + + + ChatAdminRights + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatAdminRights

+ +

Represents the rights of an admin in a channel/supergroup.

+

+ +
+
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatAdminRightsRepresents the rights of an admin in a channel/supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatAdminWithInvites.html b/data/corefork.telegram.org/type/ChatAdminWithInvites.html new file mode 100644 index 0000000000..eaf2d2f588 --- /dev/null +++ b/data/corefork.telegram.org/type/ChatAdminWithInvites.html @@ -0,0 +1,143 @@ + + + + + ChatAdminWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatAdminWithInvites

+ +

Info about chat invites generated by admins.

+

+ +
+
chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatAdminWithInvitesInfo about chat invites generated by admins.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatBannedRights.html b/data/corefork.telegram.org/type/ChatBannedRights.html new file mode 100644 index 0000000000..8ceacd2f58 --- /dev/null +++ b/data/corefork.telegram.org/type/ChatBannedRights.html @@ -0,0 +1,146 @@ + + + + + ChatBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatBannedRights

+ +

Represents the rights of a normal user in a supergroup/channel/chat.

+

+ +
+
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatBannedRightsRepresents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatFull.html b/data/corefork.telegram.org/type/ChatFull.html new file mode 100644 index 0000000000..2fd653e1c3 --- /dev/null +++ b/data/corefork.telegram.org/type/ChatFull.html @@ -0,0 +1,148 @@ + + + + + ChatFull + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatFull

+ +

Object containing detailed group info

+

+ +
+
chatFull#d18ee226 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 requests_pending:flags.17?int recent_requesters:flags.17?Vector<long> available_reactions:flags.18?Vector<string> = ChatFull;
+channelFull#e13c3d20 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 requests_pending:flags.28?int recent_requesters:flags.28?Vector<long> default_send_as:flags.29?Peer available_reactions:flags.30?Vector<string> = ChatFull;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
chatFullDetailed chat info
channelFullFull info about a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatInvite.html b/data/corefork.telegram.org/type/ChatInvite.html new file mode 100644 index 0000000000..267b34c63a --- /dev/null +++ b/data/corefork.telegram.org/type/ChatInvite.html @@ -0,0 +1,172 @@ + + + + + ChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatInvite

+ +

Chat invite

+

+ +
+
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
+chatInvite#300c44c1 flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true request_needed:flags.6?true title:string about:flags.5?string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
+
+---functions---
+
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
chatInviteAlreadyThe user has already joined this chat
chatInviteChat invite info
chatInvitePeekA chat invitation that also allows peeking into the group to read messages without joining it.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatInviteImporter.html b/data/corefork.telegram.org/type/ChatInviteImporter.html new file mode 100644 index 0000000000..2d8f4b413e --- /dev/null +++ b/data/corefork.telegram.org/type/ChatInviteImporter.html @@ -0,0 +1,143 @@ + + + + + ChatInviteImporter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatInviteImporter

+ +

When and which user joined the chat using a chat invite

+

+ +
+
chatInviteImporter#8c5adfd9 flags:# requested:flags.0?true user_id:long date:int about:flags.2?string approved_by:flags.1?long = ChatInviteImporter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatInviteImporterWhen and which user joined the chat using a chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatOnlines.html b/data/corefork.telegram.org/type/ChatOnlines.html new file mode 100644 index 0000000000..789a0ed03d --- /dev/null +++ b/data/corefork.telegram.org/type/ChatOnlines.html @@ -0,0 +1,162 @@ + + + + + ChatOnlines + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatOnlines

+ +

Number of online users in a chat

+

+ +
+
chatOnlines#f041e250 onlines:int = ChatOnlines;
+
+---functions---
+
+messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatOnlinesNumber of online users in a chat
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getOnlinesGet count of online users in a chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatParticipant.html b/data/corefork.telegram.org/type/ChatParticipant.html new file mode 100644 index 0000000000..0973c24175 --- /dev/null +++ b/data/corefork.telegram.org/type/ChatParticipant.html @@ -0,0 +1,153 @@ + + + + + ChatParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatParticipant

+ +

Details of a group member.

+

+ +
+
chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;
+chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;
+chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
chatParticipantGroup member.
chatParticipantCreatorRepresents the creator of the group
chatParticipantAdminChat admin
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatParticipants.html b/data/corefork.telegram.org/type/ChatParticipants.html new file mode 100644 index 0000000000..6700d61faf --- /dev/null +++ b/data/corefork.telegram.org/type/ChatParticipants.html @@ -0,0 +1,148 @@ + + + + + ChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatParticipants

+ +

Object contains info on group members.

+

+ +
+
chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;
+chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
chatParticipantsForbiddenInfo on members is unavailable
chatParticipantsGroup members.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatPhoto.html b/data/corefork.telegram.org/type/ChatPhoto.html new file mode 100644 index 0000000000..0c25876d42 --- /dev/null +++ b/data/corefork.telegram.org/type/ChatPhoto.html @@ -0,0 +1,148 @@ + + + + + ChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatPhoto

+ +

Object defines a group profile photo.

+

+ +
+
chatPhotoEmpty#37c1011c = ChatPhoto;
+chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
chatPhotoEmptyGroup photo is not set.
chatPhotoGroup profile photo.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatTheme.html b/data/corefork.telegram.org/type/ChatTheme.html new file mode 100644 index 0000000000..8dca54ecc3 --- /dev/null +++ b/data/corefork.telegram.org/type/ChatTheme.html @@ -0,0 +1,143 @@ + + + + + ChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatTheme

+ +

A chat theme

+

+ +
+

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatThemeA chat theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/CodeSettings.html b/data/corefork.telegram.org/type/CodeSettings.html new file mode 100644 index 0000000000..dc2cc7061a --- /dev/null +++ b/data/corefork.telegram.org/type/CodeSettings.html @@ -0,0 +1,143 @@ + + + + + CodeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

CodeSettings

+ +

Settings for the code type to send

+

+ +
+
codeSettings#8a6469c2 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true allow_missed_call:flags.5?true logout_tokens:flags.6?Vector<bytes> = CodeSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
codeSettingsSettings used by telegram servers for sending the confirm code.

Example implementations: telegram for android, tdlib.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Config.html b/data/corefork.telegram.org/type/Config.html new file mode 100644 index 0000000000..a4663d6648 --- /dev/null +++ b/data/corefork.telegram.org/type/Config.html @@ -0,0 +1,162 @@ + + + + + Config + + + + + + + + + + + + + +
+ +
+
+
+ +

Config

+ +

Object contains info on API configuring parameters.

+

+ +
+
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+
+---functions---
+
+help.getConfig#c4f9186b = Config;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
configCurrent configuration
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getConfigReturns current configuration, icluding data center configuration.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Contact.html b/data/corefork.telegram.org/type/Contact.html new file mode 100644 index 0000000000..51edfe5820 --- /dev/null +++ b/data/corefork.telegram.org/type/Contact.html @@ -0,0 +1,143 @@ + + + + + Contact + + + + + + + + + + + + + +
+ +
+
+
+ +

Contact

+ +

A contact of the current user.

+

+ +
+
contact#145ade0b user_id:long mutual:Bool = Contact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contactA contact of the current user that is registered in the system.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ContactStatus.html b/data/corefork.telegram.org/type/ContactStatus.html new file mode 100644 index 0000000000..f4289fcd13 --- /dev/null +++ b/data/corefork.telegram.org/type/ContactStatus.html @@ -0,0 +1,143 @@ + + + + + ContactStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

ContactStatus

+ +

Contact status: online / offline.

+

+ +
+
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contactStatusContact status: online / offline.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DataJSON.html b/data/corefork.telegram.org/type/DataJSON.html new file mode 100644 index 0000000000..61c337ee84 --- /dev/null +++ b/data/corefork.telegram.org/type/DataJSON.html @@ -0,0 +1,168 @@ + + + + + DataJSON + + + + + + + + + + + + + +
+ +
+
+
+ +

DataJSON

+ +

Represent a JSON-encoded object

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;
+
+---functions---
+
+bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;
+
+phone.getCallConfig#55451fa9 = DataJSON;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
dataJSONRepresents a json-encoded object
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
bots.sendCustomRequestSends a custom request; for bots only
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DcOption.html b/data/corefork.telegram.org/type/DcOption.html new file mode 100644 index 0000000000..f87f922e6f --- /dev/null +++ b/data/corefork.telegram.org/type/DcOption.html @@ -0,0 +1,143 @@ + + + + + DcOption + + + + + + + + + + + + + +
+ +
+
+
+ +

DcOption

+ +

Information for connection to data centre.

+

+ +
+
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
dcOptionData centre
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DecryptedDataBlock.html b/data/corefork.telegram.org/type/DecryptedDataBlock.html new file mode 100644 index 0000000000..ae345ce34e --- /dev/null +++ b/data/corefork.telegram.org/type/DecryptedDataBlock.html @@ -0,0 +1,128 @@ + + + + + DecryptedDataBlock + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedDataBlock

+ +

VoIP decrypted data block

+

+ +
+
Type schema is not available in the selected layer.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DecryptedMessage.html b/data/corefork.telegram.org/type/DecryptedMessage.html new file mode 100644 index 0000000000..e48ab63171 --- /dev/null +++ b/data/corefork.telegram.org/type/DecryptedMessage.html @@ -0,0 +1,140 @@ + + + + + DecryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedMessage

+ +

Object describes the contents of an encrypted message.

+

+ +
+
===8===
+decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+
+===17===
+decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
+
+===45===
+decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
+
+===73===
+decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DecryptedMessageAction.html b/data/corefork.telegram.org/type/DecryptedMessageAction.html new file mode 100644 index 0000000000..5c8238febf --- /dev/null +++ b/data/corefork.telegram.org/type/DecryptedMessageAction.html @@ -0,0 +1,145 @@ + + + + + DecryptedMessageAction + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedMessageAction

+ +

Object describes the action to which a service message is linked.

+

+ +
+
===8===
+decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;
+decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;
+decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;
+
+===17===
+decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;
+decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;
+decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;
+
+===20===
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
+decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DecryptedMessageLayer.html b/data/corefork.telegram.org/type/DecryptedMessageLayer.html new file mode 100644 index 0000000000..5be4b0bb62 --- /dev/null +++ b/data/corefork.telegram.org/type/DecryptedMessageLayer.html @@ -0,0 +1,129 @@ + + + + + DecryptedMessageLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedMessageLayer

+ +

Object describes encrypted message content in relation to the required layer.

+

+ +
+
===17===
+decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Dialog.html b/data/corefork.telegram.org/type/Dialog.html new file mode 100644 index 0000000000..4214a70d91 --- /dev/null +++ b/data/corefork.telegram.org/type/Dialog.html @@ -0,0 +1,148 @@ + + + + + Dialog + + + + + + + + + + + + + +
+ +
+
+
+ +

Dialog

+ +

Chat info.

+

+ +
+
dialog#a8edd0f5 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 unread_reactions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
+dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
dialogChat
dialogFolderDialog in folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DialogFilter.html b/data/corefork.telegram.org/type/DialogFilter.html new file mode 100644 index 0000000000..6461e60392 --- /dev/null +++ b/data/corefork.telegram.org/type/DialogFilter.html @@ -0,0 +1,143 @@ + + + + + DialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

DialogFilter

+ +

Dialog filter (folders)

+

+ +
+
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
dialogFilterDialog filter (folder)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DialogFilterSuggested.html b/data/corefork.telegram.org/type/DialogFilterSuggested.html new file mode 100644 index 0000000000..0d00b8859a --- /dev/null +++ b/data/corefork.telegram.org/type/DialogFilterSuggested.html @@ -0,0 +1,143 @@ + + + + + DialogFilterSuggested + + + + + + + + + + + + + +
+ +
+
+
+ +

DialogFilterSuggested

+ +

Suggested dialog filters (folders)

+

+ +
+
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
dialogFilterSuggestedSuggested folders
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DialogPeer.html b/data/corefork.telegram.org/type/DialogPeer.html new file mode 100644 index 0000000000..e9a76f3a29 --- /dev/null +++ b/data/corefork.telegram.org/type/DialogPeer.html @@ -0,0 +1,148 @@ + + + + + DialogPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

DialogPeer

+ +

Peer, or all peers in a folder

+

+ +
+
dialogPeer#e56dbf05 peer:Peer = DialogPeer;
+dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
dialogPeerPeer
dialogPeerFolderFolder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DisabledFeature.html b/data/corefork.telegram.org/type/DisabledFeature.html new file mode 100644 index 0000000000..7b72f817e9 --- /dev/null +++ b/data/corefork.telegram.org/type/DisabledFeature.html @@ -0,0 +1,128 @@ + + + + + DisabledFeature + + + + + + + + + + + + + +
+ +
+
+
+ +

DisabledFeature

+ +

A disabled feature

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Document.html b/data/corefork.telegram.org/type/Document.html new file mode 100644 index 0000000000..6a36ec8482 --- /dev/null +++ b/data/corefork.telegram.org/type/Document.html @@ -0,0 +1,173 @@ + + + + + Document + + + + + + + + + + + + + +
+ +
+
+
+ +

Document

+ +

A document.

+

+ +
+
documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+
+---functions---
+
+messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
+
+account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
documentEmptyEmpty constructor, document doesn't exist.
documentDocument
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
account.uploadThemeUpload theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DocumentAttribute.html b/data/corefork.telegram.org/type/DocumentAttribute.html new file mode 100644 index 0000000000..60bc5bd9ee --- /dev/null +++ b/data/corefork.telegram.org/type/DocumentAttribute.html @@ -0,0 +1,173 @@ + + + + + DocumentAttribute + + + + + + + + + + + + + +
+ +
+
+
+ +

DocumentAttribute

+ +

Various possible attributes of a document (used to define if it's a sticker, a GIF, a video, a mask sticker, an image, an audio, and so on)

+

+ +
+
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
+documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
+documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
documentAttributeImageSizeDefines the width and height of an image uploaded as document
documentAttributeAnimatedDefines an animated GIF
documentAttributeStickerDefines a sticker
documentAttributeVideoDefines a video
documentAttributeAudioRepresents an audio file
documentAttributeFilenameA simple document with a file name
documentAttributeHasStickersWhether the current document has stickers attached
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/DraftMessage.html b/data/corefork.telegram.org/type/DraftMessage.html new file mode 100644 index 0000000000..58cbb0b36b --- /dev/null +++ b/data/corefork.telegram.org/type/DraftMessage.html @@ -0,0 +1,151 @@ + + + + + DraftMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

DraftMessage

+ +

Represents a message draft.

+

+ +
+
draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;
+draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
draftMessageEmptyEmpty draft
draftMessageRepresents a message draft.
+

Related pages

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/EmojiKeyword.html b/data/corefork.telegram.org/type/EmojiKeyword.html new file mode 100644 index 0000000000..0d9ae8836d --- /dev/null +++ b/data/corefork.telegram.org/type/EmojiKeyword.html @@ -0,0 +1,148 @@ + + + + + EmojiKeyword + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiKeyword

+ +

Emoji keyword

+

+ +
+
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;
+emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
emojiKeywordEmoji keyword
emojiKeywordDeletedDeleted emoji keyword
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/EmojiKeywordsDifference.html b/data/corefork.telegram.org/type/EmojiKeywordsDifference.html new file mode 100644 index 0000000000..042b362cf6 --- /dev/null +++ b/data/corefork.telegram.org/type/EmojiKeywordsDifference.html @@ -0,0 +1,167 @@ + + + + + EmojiKeywordsDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiKeywordsDifference

+ +

New emoji keywords

+

+ +
+
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+
+---functions---
+
+messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;
+messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
emojiKeywordsDifferenceChanges to emoji keywords
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getEmojiKeywordsGet localized emoji keywords
messages.getEmojiKeywordsDifferenceGet changed emoji keywords
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/EmojiLanguage.html b/data/corefork.telegram.org/type/EmojiLanguage.html new file mode 100644 index 0000000000..498c6d809d --- /dev/null +++ b/data/corefork.telegram.org/type/EmojiLanguage.html @@ -0,0 +1,143 @@ + + + + + EmojiLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiLanguage

+ +

Emoji language

+

+ +
+
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
emojiLanguageEmoji language
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/EmojiURL.html b/data/corefork.telegram.org/type/EmojiURL.html new file mode 100644 index 0000000000..fbe259e921 --- /dev/null +++ b/data/corefork.telegram.org/type/EmojiURL.html @@ -0,0 +1,162 @@ + + + + + EmojiURL + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiURL

+ +

Emoji URL

+

+ +
+
emojiURL#a575739d url:string = EmojiURL;
+
+---functions---
+
+messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
emojiURLAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/EncryptedChat.html b/data/corefork.telegram.org/type/EncryptedChat.html new file mode 100644 index 0000000000..6de4f92c10 --- /dev/null +++ b/data/corefork.telegram.org/type/EncryptedChat.html @@ -0,0 +1,187 @@ + + + + + EncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedChat

+ +

Object contains info on an encrypted chat.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+
+---functions---
+
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedChatEmptyEmpty constructor.
encryptedChatWaitingChat waiting for approval of second participant.
encryptedChatRequestedRequest to create an encrypted chat.
encryptedChatEncrypted chat
encryptedChatDiscardedDiscarded or deleted chat.
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.acceptEncryptionConfirms creation of a secret chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/EncryptedMessage.html b/data/corefork.telegram.org/type/EncryptedMessage.html new file mode 100644 index 0000000000..8f34aa77ce --- /dev/null +++ b/data/corefork.telegram.org/type/EncryptedMessage.html @@ -0,0 +1,148 @@ + + + + + EncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedMessage

+ +

Object contains encrypted message.

+

+ +
+
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedMessageEncrypted message.
encryptedMessageServiceEncrypted service message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ExportedChatInvite.html b/data/corefork.telegram.org/type/ExportedChatInvite.html new file mode 100644 index 0000000000..6d47876ef7 --- /dev/null +++ b/data/corefork.telegram.org/type/ExportedChatInvite.html @@ -0,0 +1,162 @@ + + + + + ExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

ExportedChatInvite

+ +

Exported chat invite

+

+ +
+
chatInviteExported#ab4a819 flags:# revoked:flags.0?true permanent:flags.5?true request_needed:flags.6?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 requested:flags.7?int title:flags.8?string = ExportedChatInvite;
+
+---functions---
+
+messages.exportChatInvite#a02ce5d5 flags:# legacy_revoke_permanent:flags.2?true request_needed:flags.3?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int title:flags.4?string = ExportedChatInvite;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatInviteExportedExported chat invite
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.exportChatInviteExport an invite link for a chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ExportedMessageLink.html b/data/corefork.telegram.org/type/ExportedMessageLink.html new file mode 100644 index 0000000000..2de724404e --- /dev/null +++ b/data/corefork.telegram.org/type/ExportedMessageLink.html @@ -0,0 +1,162 @@ + + + + + ExportedMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

ExportedMessageLink

+ +

HTTP link and embed info of channel message

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+
+---functions---
+
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
exportedMessageLinkLink to a message in a supergroup/channel
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/FileHash.html b/data/corefork.telegram.org/type/FileHash.html new file mode 100644 index 0000000000..f57311ddae --- /dev/null +++ b/data/corefork.telegram.org/type/FileHash.html @@ -0,0 +1,143 @@ + + + + + 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/corefork.telegram.org/type/FileLocation.html b/data/corefork.telegram.org/type/FileLocation.html new file mode 100644 index 0000000000..cf0b051ade --- /dev/null +++ b/data/corefork.telegram.org/type/FileLocation.html @@ -0,0 +1,128 @@ + + + + + FileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

FileLocation

+ +

Indicates the location of a photo, will be deprecated soon

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Folder.html b/data/corefork.telegram.org/type/Folder.html new file mode 100644 index 0000000000..ae0a1034a7 --- /dev/null +++ b/data/corefork.telegram.org/type/Folder.html @@ -0,0 +1,143 @@ + + + + + Folder + + + + + + + + + + + + + +
+ +
+
+
+ +

Folder

+ +

A folder

+

+ +
+
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
folderFolder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/FolderPeer.html b/data/corefork.telegram.org/type/FolderPeer.html new file mode 100644 index 0000000000..c80370a30f --- /dev/null +++ b/data/corefork.telegram.org/type/FolderPeer.html @@ -0,0 +1,143 @@ + + + + + FolderPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

FolderPeer

+ +

Peer associated to folder

+

+ +
+
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
folderPeerPeer in a folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Game.html b/data/corefork.telegram.org/type/Game.html new file mode 100644 index 0000000000..30401160c7 --- /dev/null +++ b/data/corefork.telegram.org/type/Game.html @@ -0,0 +1,143 @@ + + + + + Game + + + + + + + + + + + + + +
+ +
+
+
+ +

Game

+ +

Indicates an already sent game

+

+ +
+
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
gameIndicates an already sent game
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/GeoPoint.html b/data/corefork.telegram.org/type/GeoPoint.html new file mode 100644 index 0000000000..f7b7c13c1c --- /dev/null +++ b/data/corefork.telegram.org/type/GeoPoint.html @@ -0,0 +1,148 @@ + + + + + GeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

GeoPoint

+ +

Object defines a GeoPoint.

+

+ +
+
geoPointEmpty#1117dd5f = GeoPoint;
+geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
geoPointEmptyEmpty constructor.
geoPointGeoPoint.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/GlobalPrivacySettings.html b/data/corefork.telegram.org/type/GlobalPrivacySettings.html new file mode 100644 index 0000000000..921fc0809b --- /dev/null +++ b/data/corefork.telegram.org/type/GlobalPrivacySettings.html @@ -0,0 +1,167 @@ + + + + + GlobalPrivacySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

GlobalPrivacySettings

+ +

Global privacy settings

+

+ +
+
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
+
+---functions---
+
+account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
+account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
globalPrivacySettingsGlobal privacy settings
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
account.getGlobalPrivacySettingsSet global privacy settings
account.setGlobalPrivacySettingsSet global privacy settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/GroupCall.html b/data/corefork.telegram.org/type/GroupCall.html new file mode 100644 index 0000000000..0ad0da18eb --- /dev/null +++ b/data/corefork.telegram.org/type/GroupCall.html @@ -0,0 +1,148 @@ + + + + + GroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCall

+ +

A group call

+

+ +
+
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
+groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true rtmp_stream:flags.12?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
groupCallDiscardedAn ended group call
groupCallInfo about a group call or livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/GroupCallParticipant.html b/data/corefork.telegram.org/type/GroupCallParticipant.html new file mode 100644 index 0000000000..9b3d0c3c02 --- /dev/null +++ b/data/corefork.telegram.org/type/GroupCallParticipant.html @@ -0,0 +1,143 @@ + + + + + GroupCallParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCallParticipant

+ +

Info about a group call participant

+

+ +
+
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
groupCallParticipantInfo about a group call participant
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/GroupCallParticipantVideo.html b/data/corefork.telegram.org/type/GroupCallParticipantVideo.html new file mode 100644 index 0000000000..a638bd6393 --- /dev/null +++ b/data/corefork.telegram.org/type/GroupCallParticipantVideo.html @@ -0,0 +1,143 @@ + + + + + GroupCallParticipantVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCallParticipantVideo

+ +

Info about a video stream

+

+ +
+
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
groupCallParticipantVideoInfo about a video stream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/GroupCallParticipantVideoSourceGroup.html b/data/corefork.telegram.org/type/GroupCallParticipantVideoSourceGroup.html new file mode 100644 index 0000000000..d3578c6f71 --- /dev/null +++ b/data/corefork.telegram.org/type/GroupCallParticipantVideoSourceGroup.html @@ -0,0 +1,143 @@ + + + + + GroupCallParticipantVideoSourceGroup + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCallParticipantVideoSourceGroup

+ +

Describes a group of video synchronization source identifiers

+

+ +
+
groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
groupCallParticipantVideoSourceGroupDescribes a group of video synchronization source identifiers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/HighScore.html b/data/corefork.telegram.org/type/HighScore.html new file mode 100644 index 0000000000..fd2ffc9a59 --- /dev/null +++ b/data/corefork.telegram.org/type/HighScore.html @@ -0,0 +1,143 @@ + + + + + HighScore + + + + + + + + + + + + + +
+ +
+
+
+ +

HighScore

+ +

Game high score

+

+ +
+
highScore#73a379eb pos:int user_id:long score:int = HighScore;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
highScoreGame highscore
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ImportedContact.html b/data/corefork.telegram.org/type/ImportedContact.html new file mode 100644 index 0000000000..fcb72b930a --- /dev/null +++ b/data/corefork.telegram.org/type/ImportedContact.html @@ -0,0 +1,143 @@ + + + + + ImportedContact + + + + + + + + + + + + + +
+ +
+
+
+ +

ImportedContact

+ +

Object contains info on a successfully imported contact.

+

+ +
+
importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
importedContactSuccessfully imported contact.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InlineQueryPeerType.html b/data/corefork.telegram.org/type/InlineQueryPeerType.html new file mode 100644 index 0000000000..f5e300f641 --- /dev/null +++ b/data/corefork.telegram.org/type/InlineQueryPeerType.html @@ -0,0 +1,163 @@ + + + + + InlineQueryPeerType + + + + + + + + + + + + + +
+ +
+
+
+ +

InlineQueryPeerType

+ +

Type of the chat from which the inline query was sent.

+

+ +
+
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
+inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
+inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
+inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
+inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inlineQueryPeerTypeSameBotPMThe inline query was sent in a private chat with the bot itself
inlineQueryPeerTypePMThe inline query was sent in a private chat
inlineQueryPeerTypeChatThe inline query was sent in a chat
inlineQueryPeerTypeMegagroupThe inline query was sent in a supergroup
inlineQueryPeerTypeBroadcastThe inline query was sent in a channel
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputAppEvent.html b/data/corefork.telegram.org/type/InputAppEvent.html new file mode 100644 index 0000000000..99322e7a72 --- /dev/null +++ b/data/corefork.telegram.org/type/InputAppEvent.html @@ -0,0 +1,143 @@ + + + + + InputAppEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

InputAppEvent

+ +

Object contains info about an event that occured in the application.

+

+ +
+
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputAppEventEvent that occured in the application.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputBotInlineMessage.html b/data/corefork.telegram.org/type/InputBotInlineMessage.html new file mode 100644 index 0000000000..ede5152758 --- /dev/null +++ b/data/corefork.telegram.org/type/InputBotInlineMessage.html @@ -0,0 +1,173 @@ + + + + + InputBotInlineMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

InputBotInlineMessage

+ +

Represents a sent inline message from the perspective of a bot

+

+ +
+
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputBotInlineMessageMediaAutoA media
inputBotInlineMessageTextSimple text message
inputBotInlineMessageMediaGeoGeolocation
inputBotInlineMessageMediaVenueVenue
inputBotInlineMessageMediaContactA contact
inputBotInlineMessageGameA game
inputBotInlineMessageMediaInvoiceAn invoice
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputBotInlineMessageID.html b/data/corefork.telegram.org/type/InputBotInlineMessageID.html new file mode 100644 index 0000000000..037d13f733 --- /dev/null +++ b/data/corefork.telegram.org/type/InputBotInlineMessageID.html @@ -0,0 +1,148 @@ + + + + + InputBotInlineMessageID + + + + + + + + + + + + + +
+ +
+
+
+ +

InputBotInlineMessageID

+ +

Represents a sent inline message from the perspective of a bot

+

+ +
+
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
+inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputBotInlineMessageIDRepresents a sent inline message from the perspective of a bot
inputBotInlineMessageID64Represents a sent inline message from the perspective of a bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputBotInlineResult.html b/data/corefork.telegram.org/type/InputBotInlineResult.html new file mode 100644 index 0000000000..e03c4c89ab --- /dev/null +++ b/data/corefork.telegram.org/type/InputBotInlineResult.html @@ -0,0 +1,158 @@ + + + + + InputBotInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

InputBotInlineResult

+ +

Inline bot result

+

+ +
+
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputBotInlineResultAn inline bot result
inputBotInlineResultPhotoPhoto
inputBotInlineResultDocumentDocument (media of any type except for photos)
inputBotInlineResultGameGame
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputChannel.html b/data/corefork.telegram.org/type/InputChannel.html new file mode 100644 index 0000000000..7ea633f3aa --- /dev/null +++ b/data/corefork.telegram.org/type/InputChannel.html @@ -0,0 +1,153 @@ + + + + + InputChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

InputChannel

+ +

Represents a channel

+

+ +
+
inputChannelEmpty#ee8c1e86 = InputChannel;
+inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;
+inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputChannelEmptyRepresents the absence of a channel
inputChannelRepresents a channel
inputChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputChatPhoto.html b/data/corefork.telegram.org/type/InputChatPhoto.html new file mode 100644 index 0000000000..90d8811b8c --- /dev/null +++ b/data/corefork.telegram.org/type/InputChatPhoto.html @@ -0,0 +1,153 @@ + + + + + InputChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

InputChatPhoto

+ +

Defines a new group profile photo.

+

+ +
+
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;
+inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
+inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputChatPhotoEmptyEmpty constructor, remove group photo.
inputChatUploadedPhotoNew photo to be set as group profile photo.
inputChatPhotoExisting photo to be set as a chat profile photo.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputCheckPasswordSRP.html b/data/corefork.telegram.org/type/InputCheckPasswordSRP.html new file mode 100644 index 0000000000..f2a6fd24cf --- /dev/null +++ b/data/corefork.telegram.org/type/InputCheckPasswordSRP.html @@ -0,0 +1,151 @@ + + + + + InputCheckPasswordSRP + + + + + + + + + + + + + +
+ +
+
+
+ +

InputCheckPasswordSRP

+ +

Constructors for checking the validity of a 2FA SRP password

+

+ +
+
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
+inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputCheckPasswordEmptyThere is no password
inputCheckPasswordSRPConstructor for checking the validity of a 2FA SRP password (see SRP)
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputClientProxy.html b/data/corefork.telegram.org/type/InputClientProxy.html new file mode 100644 index 0000000000..47908addc3 --- /dev/null +++ b/data/corefork.telegram.org/type/InputClientProxy.html @@ -0,0 +1,145 @@ + + + + + InputClientProxy + + + + + + + + + + + + + +
+ +
+
+
+ +

InputClientProxy

+ +

Info about an MTProxy used to connect.

+

+ +
+
inputClientProxy#75588b3f address:string port:int = InputClientProxy;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputClientProxyInfo about an MTProxy used to connect.
+

Related pages

+

MTProto transports

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputContact.html b/data/corefork.telegram.org/type/InputContact.html new file mode 100644 index 0000000000..3b2fb80948 --- /dev/null +++ b/data/corefork.telegram.org/type/InputContact.html @@ -0,0 +1,143 @@ + + + + + InputContact + + + + + + + + + + + + + +
+ +
+
+
+ +

InputContact

+ +

Object defines a contact from the user's phonebook.

+

+ +
+
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputPhoneContactPhone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputDialogPeer.html b/data/corefork.telegram.org/type/InputDialogPeer.html new file mode 100644 index 0000000000..ae19d0c27d --- /dev/null +++ b/data/corefork.telegram.org/type/InputDialogPeer.html @@ -0,0 +1,148 @@ + + + + + InputDialogPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputDialogPeer

+ +

Peer, or all peers in a certain folder

+

+ +
+
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
+inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputDialogPeerA peer
inputDialogPeerFolderAll peers in a folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputDocument.html b/data/corefork.telegram.org/type/InputDocument.html new file mode 100644 index 0000000000..751c8714cc --- /dev/null +++ b/data/corefork.telegram.org/type/InputDocument.html @@ -0,0 +1,148 @@ + + + + + InputDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

InputDocument

+ +

Defines a document for subsequent interaction.

+

+ +
+
inputDocumentEmpty#72f0eaae = InputDocument;
+inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputDocumentEmptyEmpty constructor.
inputDocumentDefines a video for subsequent interaction.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputEncryptedChat.html b/data/corefork.telegram.org/type/InputEncryptedChat.html new file mode 100644 index 0000000000..b8adb1e87b --- /dev/null +++ b/data/corefork.telegram.org/type/InputEncryptedChat.html @@ -0,0 +1,143 @@ + + + + + InputEncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

InputEncryptedChat

+ +

Object sets an encrypted chat ID.

+

+ +
+
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputEncryptedChatCreates an encrypted chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputEncryptedFile.html b/data/corefork.telegram.org/type/InputEncryptedFile.html new file mode 100644 index 0000000000..16647d3320 --- /dev/null +++ b/data/corefork.telegram.org/type/InputEncryptedFile.html @@ -0,0 +1,158 @@ + + + + + InputEncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

InputEncryptedFile

+ +

Object sets encrypted file for attachment

+

+ +
+
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
+inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
+inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
+inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputEncryptedFileEmptyEmpty constructor.
inputEncryptedFileUploadedSets new encrypted file saved by parts using upload.saveFilePart method.
inputEncryptedFileSets forwarded encrypted file for attachment.
inputEncryptedFileBigUploadedAssigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputFile.html b/data/corefork.telegram.org/type/InputFile.html new file mode 100644 index 0000000000..a698bc0272 --- /dev/null +++ b/data/corefork.telegram.org/type/InputFile.html @@ -0,0 +1,148 @@ + + + + + InputFile + + + + + + + + + + + + + +
+ +
+
+
+ +

InputFile

+ +

Defines a file uploaded by the client.

+

+ +
+
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
+inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputFileDefines a file saved in parts using the method upload.saveFilePart.
inputFileBigAssigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputFileLocation.html b/data/corefork.telegram.org/type/InputFileLocation.html new file mode 100644 index 0000000000..7801cd22fc --- /dev/null +++ b/data/corefork.telegram.org/type/InputFileLocation.html @@ -0,0 +1,188 @@ + + + + + InputFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

InputFileLocation

+ +

Defines the location of a file for download.

+

+ +
+
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
+inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
+inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
+inputTakeoutFileLocation#29be5899 = InputFileLocation;
+inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
+inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
+inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
+inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputFileLocationDEPRECATED location of a photo
inputEncryptedFileLocationLocation of encrypted secret chat file.
inputDocumentFileLocationDocument location (video, voice, audio, basically every type except photo)
inputSecureFileLocationLocation of encrypted telegram passport file.
inputTakeoutFileLocationEmpty constructor for takeout
inputPhotoFileLocationUse this object to download a photo with upload.getFile method
inputPhotoLegacyFileLocationLegacy file location
inputPeerPhotoFileLocationLocation of profile photo of channel/group/supergroup/user
inputStickerSetThumbLocation of stickerset thumbnail (see files)
inputGroupCallStreamChunk of a livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputFolderPeer.html b/data/corefork.telegram.org/type/InputFolderPeer.html new file mode 100644 index 0000000000..e1b12d0907 --- /dev/null +++ b/data/corefork.telegram.org/type/InputFolderPeer.html @@ -0,0 +1,143 @@ + + + + + InputFolderPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputFolderPeer

+ +

Peer in a folder

+

+ +
+
inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputFolderPeerPeer in a folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputGame.html b/data/corefork.telegram.org/type/InputGame.html new file mode 100644 index 0000000000..e88a489f40 --- /dev/null +++ b/data/corefork.telegram.org/type/InputGame.html @@ -0,0 +1,148 @@ + + + + + InputGame + + + + + + + + + + + + + +
+ +
+
+
+ +

InputGame

+ +

A game to send

+

+ +
+
inputGameID#32c3e77 id:long access_hash:long = InputGame;
+inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputGameIDIndicates an already sent game
inputGameShortNameGame by short name
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputGeoPoint.html b/data/corefork.telegram.org/type/InputGeoPoint.html new file mode 100644 index 0000000000..25dbb13485 --- /dev/null +++ b/data/corefork.telegram.org/type/InputGeoPoint.html @@ -0,0 +1,148 @@ + + + + + InputGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

InputGeoPoint

+ +

Defines a GeoPoint.

+

+ +
+
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputGeoPointEmptyEmpty GeoPoint constructor.
inputGeoPointDefines a GeoPoint by its coordinates.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputGroupCall.html b/data/corefork.telegram.org/type/InputGroupCall.html new file mode 100644 index 0000000000..eea3632511 --- /dev/null +++ b/data/corefork.telegram.org/type/InputGroupCall.html @@ -0,0 +1,143 @@ + + + + + InputGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

InputGroupCall

+ +

Indicates a group call

+

+ +
+
inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputGroupCallPoints to a specific group call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputMedia.html b/data/corefork.telegram.org/type/InputMedia.html new file mode 100644 index 0000000000..c10a8068f1 --- /dev/null +++ b/data/corefork.telegram.org/type/InputMedia.html @@ -0,0 +1,213 @@ + + + + + InputMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

InputMedia

+ +

Defines media content of a message.

+

+ +
+
inputMediaEmpty#9664f57f = InputMedia;
+inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;
+inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;
+inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;
+inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;
+inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;
+inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaGame#d33f43f3 id:InputGame = InputMedia;
+inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
+inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+inputMediaDice#e66fbf7b emoticon:string = InputMedia;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputMediaEmptyEmpty media content of a message.
inputMediaUploadedPhotoPhoto
inputMediaPhotoForwarded photo
inputMediaGeoPointMap.
inputMediaContactPhonebook contact
inputMediaUploadedDocumentNew document
inputMediaDocumentForwarded document
inputMediaVenueCan be used to send a venue geolocation.
inputMediaPhotoExternalNew photo that will be uploaded by the server using the specified URL
inputMediaDocumentExternalDocument that will be downloaded by the telegram servers
inputMediaGameA game
inputMediaInvoiceGenerated invoice of a bot payment
inputMediaGeoLiveLive geographical location
inputMediaPollA poll
inputMediaDiceSend a dice in the chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputMessage.html b/data/corefork.telegram.org/type/InputMessage.html new file mode 100644 index 0000000000..a2e32a2f77 --- /dev/null +++ b/data/corefork.telegram.org/type/InputMessage.html @@ -0,0 +1,158 @@ + + + + + InputMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

InputMessage

+ +

A message

+

+ +
+
inputMessageID#a676a322 id:int = InputMessage;
+inputMessageReplyTo#bad88395 id:int = InputMessage;
+inputMessagePinned#86872538 = InputMessage;
+inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputMessageIDMessage by ID
inputMessageReplyToMessage to which the specified message replies to
inputMessagePinnedPinned message
inputMessageCallbackQueryUsed by bots for fetching information about the message that originated a callback query
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputNotifyPeer.html b/data/corefork.telegram.org/type/InputNotifyPeer.html new file mode 100644 index 0000000000..d8dbcbffdb --- /dev/null +++ b/data/corefork.telegram.org/type/InputNotifyPeer.html @@ -0,0 +1,158 @@ + + + + + InputNotifyPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputNotifyPeer

+ +

Object defines the set of users and/or groups that generate notifications.

+

+ +
+
inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;
+inputNotifyUsers#193b4417 = InputNotifyPeer;
+inputNotifyChats#4a95e84e = InputNotifyPeer;
+inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputNotifyPeerNotifications generated by a certain user or group.
inputNotifyUsersNotifications generated by all users.
inputNotifyChatsNotifications generated by all groups.
inputNotifyBroadcastsAll channels
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputPaymentCredentials.html b/data/corefork.telegram.org/type/InputPaymentCredentials.html new file mode 100644 index 0000000000..a20a6cff1e --- /dev/null +++ b/data/corefork.telegram.org/type/InputPaymentCredentials.html @@ -0,0 +1,158 @@ + + + + + InputPaymentCredentials + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPaymentCredentials

+ +

Payment credentials

+

+ +
+
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPaymentCredentialsSavedSaved payment credentials
inputPaymentCredentialsPayment credentials
inputPaymentCredentialsApplePayApple pay payment credentials
inputPaymentCredentialsGooglePayGoogle Pay payment credentials
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputPeer.html b/data/corefork.telegram.org/type/InputPeer.html new file mode 100644 index 0000000000..02d08ff2e8 --- /dev/null +++ b/data/corefork.telegram.org/type/InputPeer.html @@ -0,0 +1,173 @@ + + + + + InputPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPeer

+ +

Peer

+

+ +
+
inputPeerEmpty#7f3b18ea = InputPeer;
+inputPeerSelf#7da07ec9 = InputPeer;
+inputPeerChat#35a95cb9 chat_id:long = InputPeer;
+inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
+inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
+inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;
+inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPeerEmptyAn empty constructor, no user or chat is defined.
inputPeerSelfDefines the current user.
inputPeerChatDefines a chat for further interaction.
inputPeerUserDefines a user for further interaction.
inputPeerChannelDefines a channel for further interaction.
inputPeerUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
inputPeerChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputPeerNotifySettings.html b/data/corefork.telegram.org/type/InputPeerNotifySettings.html new file mode 100644 index 0000000000..6be11a8be9 --- /dev/null +++ b/data/corefork.telegram.org/type/InputPeerNotifySettings.html @@ -0,0 +1,143 @@ + + + + + InputPeerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPeerNotifySettings

+ +

Notifications settings.

+

+ +
+
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputPeerNotifySettingsNotification settings.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputPhoneCall.html b/data/corefork.telegram.org/type/InputPhoneCall.html new file mode 100644 index 0000000000..b1cbf60711 --- /dev/null +++ b/data/corefork.telegram.org/type/InputPhoneCall.html @@ -0,0 +1,143 @@ + + + + + InputPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPhoneCall

+ +

Phone call

+

+ +
+
inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputPhoneCallPhone call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputPhoto.html b/data/corefork.telegram.org/type/InputPhoto.html new file mode 100644 index 0000000000..51f19ddc5b --- /dev/null +++ b/data/corefork.telegram.org/type/InputPhoto.html @@ -0,0 +1,148 @@ + + + + + InputPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPhoto

+ +

Defines a photo for further interaction.

+

+ +
+
inputPhotoEmpty#1cd7bf0d = InputPhoto;
+inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPhotoEmptyEmpty constructor.
inputPhotoDefines a photo for further interaction.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputPrivacyKey.html b/data/corefork.telegram.org/type/InputPrivacyKey.html new file mode 100644 index 0000000000..7144fe582c --- /dev/null +++ b/data/corefork.telegram.org/type/InputPrivacyKey.html @@ -0,0 +1,178 @@ + + + + + InputPrivacyKey + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPrivacyKey

+ +

Privacy key

+

+ +
+
inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
+inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
+inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
+inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
+inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
+inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
+inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
+inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPrivacyKeyStatusTimestampWhether we can see the exact last online timestamp of the user
inputPrivacyKeyChatInviteWhether the user can be invited to chats
inputPrivacyKeyPhoneCallWhether the user will accept phone calls
inputPrivacyKeyPhoneP2PWhether the user allows P2P communication during VoIP calls
inputPrivacyKeyForwardsWhether messages forwarded from this user will be anonymous
inputPrivacyKeyProfilePhotoWhether people will be able to see the user's profile picture
inputPrivacyKeyPhoneNumberWhether people will be able to see the user's phone number
inputPrivacyKeyAddedByPhoneWhether people can add you to their contact list by your phone number
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputPrivacyRule.html b/data/corefork.telegram.org/type/InputPrivacyRule.html new file mode 100644 index 0000000000..366dfa0177 --- /dev/null +++ b/data/corefork.telegram.org/type/InputPrivacyRule.html @@ -0,0 +1,178 @@ + + + + + InputPrivacyRule + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPrivacyRule

+ +

Privacy rule

+

+ +
+
inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;
+inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
+inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;
+inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
+inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;
+inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPrivacyValueAllowContactsAllow only contacts
inputPrivacyValueAllowAllAllow all users
inputPrivacyValueAllowUsersAllow only certain users
inputPrivacyValueDisallowContactsDisallow only contacts
inputPrivacyValueDisallowAllDisallow all
inputPrivacyValueDisallowUsersDisallow only certain users
inputPrivacyValueAllowChatParticipantsAllow only participants of certain chats
inputPrivacyValueDisallowChatParticipantsDisallow only participants of certain chats
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputSecureFile.html b/data/corefork.telegram.org/type/InputSecureFile.html new file mode 100644 index 0000000000..ed22e5f8ad --- /dev/null +++ b/data/corefork.telegram.org/type/InputSecureFile.html @@ -0,0 +1,151 @@ + + + + + InputSecureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

InputSecureFile

+ +

Secure passport file, for more info see the passport docs »

+

+ +
+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputSecureFileUploadedUploaded secure file, for more info see the passport docs »
inputSecureFilePreuploaded passport file, for more info see the passport docs »
+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputSecureValue.html b/data/corefork.telegram.org/type/InputSecureValue.html new file mode 100644 index 0000000000..ae48e299cd --- /dev/null +++ b/data/corefork.telegram.org/type/InputSecureValue.html @@ -0,0 +1,145 @@ + + + + + InputSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

InputSecureValue

+ +

Secure value, for more info see the passport docs »

+

+ +
+
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputSecureValueSecure value, for more info see the passport docs »
+

Related pages

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputSingleMedia.html b/data/corefork.telegram.org/type/InputSingleMedia.html new file mode 100644 index 0000000000..e67e43c65c --- /dev/null +++ b/data/corefork.telegram.org/type/InputSingleMedia.html @@ -0,0 +1,148 @@ + + + + + InputSingleMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

InputSingleMedia

+ +

A single media in an album or grouped media sent with messages.sendMultiMedia.

+

+ +
+
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputSingleMediaA single media in an album or grouped media sent with messages.sendMultiMedia.
+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

messages.sendMultiMedia

+

Send an album or grouped media

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputStickerSet.html b/data/corefork.telegram.org/type/InputStickerSet.html new file mode 100644 index 0000000000..a2b57fafb6 --- /dev/null +++ b/data/corefork.telegram.org/type/InputStickerSet.html @@ -0,0 +1,168 @@ + + + + + InputStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

InputStickerSet

+ +

Represents a stickerset

+

+ +
+
inputStickerSetEmpty#ffb62b95 = InputStickerSet;
+inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
+inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
+inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
+inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputStickerSetEmptyEmpty constructor
inputStickerSetIDStickerset by ID
inputStickerSetShortNameStickerset by short name, from tg://addstickers?set=short_name
inputStickerSetAnimatedEmojiAnimated emojis stickerset
inputStickerSetDiceSend a dice
inputStickerSetAnimatedEmojiAnimationsAnimated emoji reaction stickerset (contains animations to play when a user clicks on a given animated emoji)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputStickerSetItem.html b/data/corefork.telegram.org/type/InputStickerSetItem.html new file mode 100644 index 0000000000..7f1403bb69 --- /dev/null +++ b/data/corefork.telegram.org/type/InputStickerSetItem.html @@ -0,0 +1,143 @@ + + + + + InputStickerSetItem + + + + + + + + + + + + + +
+ +
+
+
+ +

InputStickerSetItem

+ +

Sticker

+

+ +
+
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputStickerSetItemSticker in a stickerset
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputStickeredMedia.html b/data/corefork.telegram.org/type/InputStickeredMedia.html new file mode 100644 index 0000000000..8bbe3ebca2 --- /dev/null +++ b/data/corefork.telegram.org/type/InputStickeredMedia.html @@ -0,0 +1,148 @@ + + + + + InputStickeredMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

InputStickeredMedia

+ +

Represents a media with attached stickers

+

+ +
+
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;
+inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputStickeredMediaPhotoA photo with stickers attached
inputStickeredMediaDocumentA document with stickers attached
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputThemeSettings.html b/data/corefork.telegram.org/type/InputThemeSettings.html new file mode 100644 index 0000000000..9e39638e66 --- /dev/null +++ b/data/corefork.telegram.org/type/InputThemeSettings.html @@ -0,0 +1,143 @@ + + + + + InputThemeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

InputThemeSettings

+ +

Theme settings

+

+ +
+
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputThemeSettingsTheme settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputUser.html b/data/corefork.telegram.org/type/InputUser.html new file mode 100644 index 0000000000..b702a694dc --- /dev/null +++ b/data/corefork.telegram.org/type/InputUser.html @@ -0,0 +1,158 @@ + + + + + InputUser + + + + + + + + + + + + + +
+ +
+
+
+ +

InputUser

+ +

Defines a user for subsequent interaction.

+

+ +
+
inputUserEmpty#b98886cf = InputUser;
+inputUserSelf#f7c1b13f = InputUser;
+inputUser#f21158c6 user_id:long access_hash:long = InputUser;
+inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputUserEmptyEmpty constructor, does not define a user.
inputUserSelfDefines the current user.
inputUserDefines a user for further interaction.
inputUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputWallPaper.html b/data/corefork.telegram.org/type/InputWallPaper.html new file mode 100644 index 0000000000..d78c7ab6a4 --- /dev/null +++ b/data/corefork.telegram.org/type/InputWallPaper.html @@ -0,0 +1,153 @@ + + + + + InputWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

InputWallPaper

+ +

Wallpaper

+

+ +
+
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
+inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
+inputWallPaperNoFile#967a462e id:long = InputWallPaper;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputWallPaperWallpaper
inputWallPaperSlugWallpaper by slug (a unique ID)
inputWallPaperNoFileWallpaper with no file
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputWebDocument.html b/data/corefork.telegram.org/type/InputWebDocument.html new file mode 100644 index 0000000000..bf5510e59d --- /dev/null +++ b/data/corefork.telegram.org/type/InputWebDocument.html @@ -0,0 +1,143 @@ + + + + + InputWebDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

InputWebDocument

+ +

Specifies a document that will have to be downloaded from the URL by the telegram servers

+

+ +
+
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputWebDocumentThe document
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputWebFileLocation.html b/data/corefork.telegram.org/type/InputWebFileLocation.html new file mode 100644 index 0000000000..7e5f504cd2 --- /dev/null +++ b/data/corefork.telegram.org/type/InputWebFileLocation.html @@ -0,0 +1,148 @@ + + + + + InputWebFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

InputWebFileLocation

+ +

Location of remote file

+

+ +
+
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
+inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputWebFileLocationLocation of a remote HTTP(s) file
inputWebFileGeoPointLocationGeolocation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Invoice.html b/data/corefork.telegram.org/type/Invoice.html new file mode 100644 index 0000000000..6aaae7acce --- /dev/null +++ b/data/corefork.telegram.org/type/Invoice.html @@ -0,0 +1,143 @@ + + + + + Invoice + + + + + + + + + + + + + +
+ +
+
+
+ +

Invoice

+ +

Invoice

+

+ +
+
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
invoiceInvoice
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/JSONObjectValue.html b/data/corefork.telegram.org/type/JSONObjectValue.html new file mode 100644 index 0000000000..5249486739 --- /dev/null +++ b/data/corefork.telegram.org/type/JSONObjectValue.html @@ -0,0 +1,143 @@ + + + + + JSONObjectValue + + + + + + + + + + + + + +
+ +
+
+
+ +

JSONObjectValue

+ +

JSON key: value pair

+

+ +
+
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
jsonObjectValueJSON key: value pair
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/JSONValue.html b/data/corefork.telegram.org/type/JSONValue.html new file mode 100644 index 0000000000..2b64da62f3 --- /dev/null +++ b/data/corefork.telegram.org/type/JSONValue.html @@ -0,0 +1,187 @@ + + + + + JSONValue + + + + + + + + + + + + + +
+ +
+
+
+ +

JSONValue

+ +

JSON value

+

+ +
+
jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+
+---functions---
+
+help.getAppConfig#98914110 = JSONValue;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
jsonNullnull JSON value
jsonBoolJSON boolean value
jsonNumberJSON numeric value
jsonStringJSON string
jsonArrayJSON array
jsonObjectJSON object value
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getAppConfigGet app-specific configuration
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/KeyboardButton.html b/data/corefork.telegram.org/type/KeyboardButton.html new file mode 100644 index 0000000000..c1f83d7626 --- /dev/null +++ b/data/corefork.telegram.org/type/KeyboardButton.html @@ -0,0 +1,195 @@ + + + + + KeyboardButton + + + + + + + + + + + + + +
+ +
+
+
+ +

KeyboardButton

+ +

Bot or inline keyboard buttons

+

+ +
+
keyboardButton#a2fa4880 text:string = KeyboardButton;
+keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
+keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
+keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
+keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
+keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
+keyboardButtonGame#50f41ccf text:string = KeyboardButton;
+keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
+inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
+keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
+inputKeyboardButtonUserProfile#e988037b text:string user_id:InputUser = KeyboardButton;
+keyboardButtonUserProfile#308660c1 text:string user_id:long = KeyboardButton;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
keyboardButtonBot keyboard button
keyboardButtonUrlURL button
keyboardButtonCallbackCallback button
keyboardButtonRequestPhoneButton to request a user's phone number
keyboardButtonRequestGeoLocationButton to request a user's geolocation
keyboardButtonSwitchInlineButton to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.
keyboardButtonGameButton to start a game
keyboardButtonBuyButton to buy a product
keyboardButtonUrlAuthButton to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.
inputKeyboardButtonUrlAuthButton to request a user to authorize via URL using Seamless Telegram Login.
keyboardButtonRequestPollA button that allows the user to create and send a poll when pressed; available only in private
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/KeyboardButtonRow.html b/data/corefork.telegram.org/type/KeyboardButtonRow.html new file mode 100644 index 0000000000..24539d9ab6 --- /dev/null +++ b/data/corefork.telegram.org/type/KeyboardButtonRow.html @@ -0,0 +1,143 @@ + + + + + KeyboardButtonRow + + + + + + + + + + + + + +
+ +
+
+
+ +

KeyboardButtonRow

+ +

Bot or inline keyboard rows

+

+ +
+
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
keyboardButtonRowInline keyboard row
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/LabeledPrice.html b/data/corefork.telegram.org/type/LabeledPrice.html new file mode 100644 index 0000000000..adbae6bd2f --- /dev/null +++ b/data/corefork.telegram.org/type/LabeledPrice.html @@ -0,0 +1,143 @@ + + + + + LabeledPrice + + + + + + + + + + + + + +
+ +
+
+
+ +

LabeledPrice

+ +

Labeled pricetag

+

+ +
+
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
labeledPriceThis object represents a portion of the price for goods or services.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/LangPackDifference.html b/data/corefork.telegram.org/type/LangPackDifference.html new file mode 100644 index 0000000000..118b54a4a1 --- /dev/null +++ b/data/corefork.telegram.org/type/LangPackDifference.html @@ -0,0 +1,167 @@ + + + + + LangPackDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

LangPackDifference

+ +

Language pack changes

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+
+---functions---
+
+langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;
+langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
langPackDifferenceChanges to the app's localization pack
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
langpack.getLangPackGet localization pack strings
langpack.getDifferenceGet new strings in languagepack
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/LangPackLanguage.html b/data/corefork.telegram.org/type/LangPackLanguage.html new file mode 100644 index 0000000000..683ff0d16b --- /dev/null +++ b/data/corefork.telegram.org/type/LangPackLanguage.html @@ -0,0 +1,162 @@ + + + + + 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 new file mode 100644 index 0000000000..872f6b3649 --- /dev/null +++ b/data/corefork.telegram.org/type/LangPackString.html @@ -0,0 +1,153 @@ + + + + + LangPackString + + + + + + + + + + + + + +
+ +
+
+
+ +

LangPackString

+ +

Language pack string

+

+ +
+
langPackString#cad181f6 key:string value:string = LangPackString;
+langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;
+langPackStringDeleted#2979eeb2 key:string = LangPackString;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
langPackStringTranslated localization string
langPackStringPluralizedA language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
langPackStringDeletedDeleted localization string
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MaskCoords.html b/data/corefork.telegram.org/type/MaskCoords.html new file mode 100644 index 0000000000..282578a53d --- /dev/null +++ b/data/corefork.telegram.org/type/MaskCoords.html @@ -0,0 +1,143 @@ + + + + + MaskCoords + + + + + + + + + + + + + +
+ +
+
+
+ +

MaskCoords

+ +

Mask coordinates (if this is a mask sticker, attached to a photo)

+

+ +
+
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
maskCoordsPosition on a photo where a mask should be placed

The n position indicates where the mask should be placed:

- 0 => Relative to the forehead
- 1 => Relative to the eyes
- 2 => Relative to the mouth
- 3 => Relative to the chin
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Message.html b/data/corefork.telegram.org/type/Message.html new file mode 100644 index 0000000000..090e1edae2 --- /dev/null +++ b/data/corefork.telegram.org/type/Message.html @@ -0,0 +1,153 @@ + + + + + Message + + + + + + + + + + + + + +
+ +
+
+
+ +

Message

+ +

Object describing a message.

+

+ +
+
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;
+message#38116ee0 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageEmptyEmpty constructor, non-existent message.
messageA message
messageServiceIndicates a service message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageAction.html b/data/corefork.telegram.org/type/MessageAction.html new file mode 100644 index 0000000000..be54e707e1 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageAction.html @@ -0,0 +1,284 @@ + + + + + MessageAction + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageAction

+ +

Object describing actions connected to a service message.

+

+ +
+
messageActionEmpty#b6aef7b0 = MessageAction;
+messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;
+messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;
+messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;
+messageActionChatDeletePhoto#95e3fbef = MessageAction;
+messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;
+messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;
+messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;
+messageActionChannelCreate#95d2ac92 title:string = MessageAction;
+messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;
+messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;
+messageActionPinMessage#94bd38ed = MessageAction;
+messageActionHistoryClear#9fbab604 = MessageAction;
+messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
+messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
+messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
+messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;
+messageActionScreenshotTaken#4792929b = MessageAction;
+messageActionCustomAction#fae69f56 message:string = MessageAction;
+messageActionBotAllowed#abe9affe domain:string = MessageAction;
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;
+messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;
+messageActionContactSignUp#f3f25f76 = MessageAction;
+messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
+messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
+messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;
+messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;
+messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;
+messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;
+messageActionChatJoinedByRequest#ebbca3cb = MessageAction;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageActionEmptyEmpty constructor.
messageActionChatCreateGroup created
messageActionChatEditTitleGroup name changed.
messageActionChatEditPhotoGroup profile changed
messageActionChatDeletePhotoGroup profile photo removed.
messageActionChatAddUserNew member in the group
messageActionChatDeleteUserUser left the group.
messageActionChatJoinedByLinkA user joined the chat via an invite link
messageActionChannelCreateThe channel was created
messageActionChatMigrateToIndicates the chat was migrated to the specified supergroup
messageActionChannelMigrateFromIndicates the channel was migrated from the specified chat
messageActionPinMessageA message was pinned
messageActionHistoryClearChat history was cleared
messageActionGameScoreSomeone scored in a game
messageActionPaymentSentMeA user just sent a payment to me (a bot)
messageActionPaymentSentA payment was sent
messageActionPhoneCallA phone call
messageActionScreenshotTakenA screenshot of the chat was taken
messageActionCustomActionCustom action (most likely not supported by the current layer, an upgrade might be needed)
messageActionBotAllowedThe domain name of the website on which the user has logged in. More about Telegram Login »
messageActionSecureValuesSentMeSecure telegram passport values were received
messageActionSecureValuesSentRequest for secure telegram passport values was sent
messageActionContactSignUpA contact just signed up to telegram
messageActionGeoProximityReachedWe are now in proximity of this user (triggered by the other user, by sending a live geolocation with the proximity_notification_radius flag)
messageActionGroupCallThe group call has ended
messageActionInviteToGroupCallA set of users was invited to the group call
messageActionSetMessagesTTLYou changed the Time-To-Live of your messages in this chat.
messageActionGroupCallScheduledA group call was scheduled
messageActionSetChatThemeThe chat theme was changed
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageEntity.html b/data/corefork.telegram.org/type/MessageEntity.html new file mode 100644 index 0000000000..1f98f925d6 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageEntity.html @@ -0,0 +1,234 @@ + + + + + MessageEntity + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageEntity

+ +

Message entities, representing styled text in a message

+

+ +
+
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
+messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
+messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
+messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
+messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
+messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
+messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
+messageEntityCode#28a20571 offset:int length:int = MessageEntity;
+messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
+messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
+messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
+inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
+messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
+messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
+messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
+messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
+messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
+messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;
+messageEntitySpoiler#32ca960f offset:int length:int = MessageEntity;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageEntityUnknownUnknown message entity
messageEntityMentionMessage entity mentioning the current user
messageEntityHashtag#hashtag message entity
messageEntityBotCommandMessage entity representing a bot /command
messageEntityUrlMessage entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.
messageEntityEmailMessage entity representing an email@example.com.
messageEntityBoldMessage entity representing bold text.
messageEntityItalicMessage entity representing italic text.
messageEntityCodeMessage entity representing a codeblock.
messageEntityPreMessage entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.
messageEntityTextUrlMessage entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
messageEntityMentionNameMessage entity representing a user mention: for creating a mention use inputMessageEntityMentionName.
inputMessageEntityMentionNameMessage entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.
messageEntityPhoneMessage entity representing a phone number.
messageEntityCashtagMessage entity representing a $cashtag.
messageEntityUnderlineMessage entity representing underlined text.
messageEntityStrikeMessage entity representing strikethrough text.
messageEntityBlockquoteMessage entity representing a block quote.
messageEntityBankCardIndicates a credit card number
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageFwdHeader.html b/data/corefork.telegram.org/type/MessageFwdHeader.html new file mode 100644 index 0000000000..b9ed63a4a1 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageFwdHeader.html @@ -0,0 +1,143 @@ + + + + + MessageFwdHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageFwdHeader

+ +

Info about a forwarded message

+

+ +
+
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageFwdHeaderInfo about a forwarded message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageInteractionCounters.html b/data/corefork.telegram.org/type/MessageInteractionCounters.html new file mode 100644 index 0000000000..7ebde4ad30 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageInteractionCounters.html @@ -0,0 +1,143 @@ + + + + + MessageInteractionCounters + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageInteractionCounters

+ +

Message interaction counters

+

+ +
+
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageInteractionCountersMessage interaction counters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageMedia.html b/data/corefork.telegram.org/type/MessageMedia.html new file mode 100644 index 0000000000..a01eab09a0 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageMedia.html @@ -0,0 +1,232 @@ + + + + + MessageMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageMedia

+ +

Media

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+
+---functions---
+
+messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;
+messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageMediaEmptyEmpty constructor.
messageMediaPhotoAttached photo.
messageMediaGeoAttached map.
messageMediaContactAttached contact.
messageMediaUnsupportedCurrent version of the client does not support this media type.
messageMediaDocumentDocument (video, audio, voice, sticker, any media type except photo)
messageMediaWebPagePreview of webpage
messageMediaVenueVenue
messageMediaGameTelegram game
messageMediaInvoiceInvoice
messageMediaGeoLiveIndicates a live geolocation
messageMediaPollPoll
messageMediaDiceDice
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getWebPagePreviewGet preview of webpage
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.uploadImportedMediaUpload a media file associated with an imported chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessagePeerReaction.html b/data/corefork.telegram.org/type/MessagePeerReaction.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/MessagePeerReaction.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageRange.html b/data/corefork.telegram.org/type/MessageRange.html new file mode 100644 index 0000000000..43bf2e05f7 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageRange.html @@ -0,0 +1,143 @@ + + + + + MessageRange + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageRange

+ +

Indicates a range of chat messages

+

+ +
+
messageRange#ae30253 min_id:int max_id:int = MessageRange;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageRangeIndicates a range of chat messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageReactions.html b/data/corefork.telegram.org/type/MessageReactions.html new file mode 100644 index 0000000000..f8aad62c31 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageReactions.html @@ -0,0 +1,128 @@ + + + + + MessageReactions + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageReactions

+ +

Message reactions

+

+ +
+
messageReactions#4f2b9479 flags:# min:flags.0?true can_see_list:flags.2?true results:Vector<ReactionCount> recent_reactions:flags.1?Vector<MessagePeerReaction> = MessageReactions;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageReactionsList.html b/data/corefork.telegram.org/type/MessageReactionsList.html new file mode 100644 index 0000000000..90babc2617 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageReactionsList.html @@ -0,0 +1,128 @@ + + + + + MessageReactionsList + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageReactionsList

+ +

List of message reactions

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageReplies.html b/data/corefork.telegram.org/type/MessageReplies.html new file mode 100644 index 0000000000..d86c95850e --- /dev/null +++ b/data/corefork.telegram.org/type/MessageReplies.html @@ -0,0 +1,146 @@ + + + + + MessageReplies + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageReplies

+ +

Info about post comments (for channels) or message replies (for groups)

+

+ +
+
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageRepliesInfo about the comment section of a channel post, or a simple message thread
+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageUserVote.html b/data/corefork.telegram.org/type/MessageUserVote.html new file mode 100644 index 0000000000..1caaff7a30 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageUserVote.html @@ -0,0 +1,153 @@ + + + + + MessageUserVote + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageUserVote

+ +

How a user voted in a poll

+

+ +
+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageUserVoteUser ID
messageUserVoteInputOptionHow a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)
messageUserVoteMultipleHow a user voted in a multiple-choice poll
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageViews.html b/data/corefork.telegram.org/type/MessageViews.html new file mode 100644 index 0000000000..eef0efcab3 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageViews.html @@ -0,0 +1,143 @@ + + + + + MessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageViews

+ +

View, forward counter + info about replies of a specific message

+

+ +
+
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageViewsView, forward counter + info about replies of a specific message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessagesFilter.html b/data/corefork.telegram.org/type/MessagesFilter.html new file mode 100644 index 0000000000..461c18acb8 --- /dev/null +++ b/data/corefork.telegram.org/type/MessagesFilter.html @@ -0,0 +1,223 @@ + + + + + MessagesFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

MessagesFilter

+ +

Object describes message filter.

+

+ +
+
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
+inputMessagesFilterPhotos#9609a51c = MessagesFilter;
+inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
+inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
+inputMessagesFilterDocument#9eddf188 = MessagesFilter;
+inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
+inputMessagesFilterGif#ffc86587 = MessagesFilter;
+inputMessagesFilterVoice#50f5c392 = MessagesFilter;
+inputMessagesFilterMusic#3751b49e = MessagesFilter;
+inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
+inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
+inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
+inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
+inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
+inputMessagesFilterGeo#e7026d0d = MessagesFilter;
+inputMessagesFilterContacts#e062db83 = MessagesFilter;
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputMessagesFilterEmptyFilter is absent.
inputMessagesFilterPhotosFilter for messages containing photos.
inputMessagesFilterVideoFilter for messages containing videos.
inputMessagesFilterPhotoVideoFilter for messages containing photos or videos.
inputMessagesFilterDocumentFilter for messages containing documents.
inputMessagesFilterUrlReturn only messages containing URLs
inputMessagesFilterGifReturn only messages containing gifs
inputMessagesFilterVoiceReturn only messages containing voice notes
inputMessagesFilterMusicReturn only messages containing audio files
inputMessagesFilterChatPhotosReturn only chat photo changes
inputMessagesFilterPhoneCallsReturn only phone calls
inputMessagesFilterRoundVoiceReturn only round videos and voice notes
inputMessagesFilterRoundVideoReturn only round videos
inputMessagesFilterMyMentionsReturn only messages where the current user was mentioned
inputMessagesFilterGeoReturn only messages containing geolocations
inputMessagesFilterContactsReturn only messages containing contacts
inputMessagesFilterPinnedFetch only pinned messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/NearestDc.html b/data/corefork.telegram.org/type/NearestDc.html new file mode 100644 index 0000000000..801599c140 --- /dev/null +++ b/data/corefork.telegram.org/type/NearestDc.html @@ -0,0 +1,162 @@ + + + + + NearestDc + + + + + + + + + + + + + +
+ +
+
+
+ +

NearestDc

+ +

Object contains info on nearest data centre.

+

+ +
+
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+
+---functions---
+
+help.getNearestDc#1fb33026 = NearestDc;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
nearestDcNearest data centre, according to geo-ip.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getNearestDcReturns info on data centre nearest to the user.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/NotifyPeer.html b/data/corefork.telegram.org/type/NotifyPeer.html new file mode 100644 index 0000000000..5786c215cc --- /dev/null +++ b/data/corefork.telegram.org/type/NotifyPeer.html @@ -0,0 +1,158 @@ + + + + + NotifyPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

NotifyPeer

+ +

Object defines the set of users and/or groups that generate notifications.

+

+ +
+
notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;
+notifyUsers#b4c83b4c = NotifyPeer;
+notifyChats#c007cec3 = NotifyPeer;
+notifyBroadcasts#d612e8ef = NotifyPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
notifyPeerNotifications generated by a certain user or group.
notifyUsersNotifications generated by all users.
notifyChatsNotifications generated by all groups.
notifyBroadcastsChannel notification settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Null.html b/data/corefork.telegram.org/type/Null.html new file mode 100644 index 0000000000..c55ac72a53 --- /dev/null +++ b/data/corefork.telegram.org/type/Null.html @@ -0,0 +1,143 @@ + + + + + Null + + + + + + + + + + + + + +
+ +
+
+
+ +

Null

+ +

Object corresponds to an arbitrary empty object.

+

+ +
+
null#56730bcc = Null;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
nullCorresponds to an arbitrary empty object.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Page.html b/data/corefork.telegram.org/type/Page.html new file mode 100644 index 0000000000..6fea85a1a4 --- /dev/null +++ b/data/corefork.telegram.org/type/Page.html @@ -0,0 +1,143 @@ + + + + + Page + + + + + + + + + + + + + +
+ +
+
+
+ +

Page

+ +

Instant view page

+

+ +
+
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageInstant view page
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageBlock.html b/data/corefork.telegram.org/type/PageBlock.html new file mode 100644 index 0000000000..aeb5db84ec --- /dev/null +++ b/data/corefork.telegram.org/type/PageBlock.html @@ -0,0 +1,283 @@ + + + + + PageBlock + + + + + + + + + + + + + +
+ +
+
+
+ +

PageBlock

+ +

Represents an instant view page element

+

+ +
+
pageBlockUnsupported#13567e8a = PageBlock;
+pageBlockTitle#70abc3fd text:RichText = PageBlock;
+pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;
+pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;
+pageBlockHeader#bfd064ec text:RichText = PageBlock;
+pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;
+pageBlockParagraph#467a0766 text:RichText = PageBlock;
+pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;
+pageBlockFooter#48870999 text:RichText = PageBlock;
+pageBlockDivider#db20b188 = PageBlock;
+pageBlockAnchor#ce0d37b0 name:string = PageBlock;
+pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;
+pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;
+pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;
+pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;
+pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;
+pageBlockCover#39f23300 cover:PageBlock = PageBlock;
+pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;
+pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockChannel#ef1751b5 channel:Chat = PageBlock;
+pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;
+pageBlockKicker#1e148390 text:RichText = PageBlock;
+pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;
+pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;
+pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;
+pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;
+pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
pageBlockUnsupportedUnsupported IV element
pageBlockTitleTitle
pageBlockSubtitleSubtitle
pageBlockAuthorDateAuthor and date of creation of article
pageBlockHeaderPage header
pageBlockSubheaderSubheader
pageBlockParagraphA paragraph
pageBlockPreformattedPreformatted (<pre> text)
pageBlockFooterPage footer
pageBlockDividerAn empty block separating a page
pageBlockAnchorLink to section within the page itself (like <a href="#target">anchor</a>)
pageBlockListUnordered list of IV blocks
pageBlockBlockquoteQuote (equivalent to the HTML <blockquote>)
pageBlockPullquotePullquote
pageBlockPhotoA photo
pageBlockVideoVideo
pageBlockCoverA page cover
pageBlockEmbedAn embedded webpage
pageBlockEmbedPostAn embedded post
pageBlockCollageCollage of media
pageBlockSlideshowSlideshow
pageBlockChannelReference to a telegram channel
pageBlockAudioAudio
pageBlockKickerKicker
pageBlockTableTable
pageBlockOrderedListOrdered list of IV blocks
pageBlockDetailsA collapsible details block
pageBlockRelatedArticlesRelated articles
pageBlockMapA map
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageCaption.html b/data/corefork.telegram.org/type/PageCaption.html new file mode 100644 index 0000000000..22f4d9ae1d --- /dev/null +++ b/data/corefork.telegram.org/type/PageCaption.html @@ -0,0 +1,143 @@ + + + + + PageCaption + + + + + + + + + + + + + +
+ +
+
+
+ +

PageCaption

+ +

Page caption

+

+ +
+
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageCaptionPage caption
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageListItem.html b/data/corefork.telegram.org/type/PageListItem.html new file mode 100644 index 0000000000..d287317c02 --- /dev/null +++ b/data/corefork.telegram.org/type/PageListItem.html @@ -0,0 +1,148 @@ + + + + + PageListItem + + + + + + + + + + + + + +
+ +
+
+
+ +

PageListItem

+ +

Item in block list

+

+ +
+
pageListItemText#b92fb6cd text:RichText = PageListItem;
+pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
pageListItemTextList item
pageListItemBlocksList item
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageListOrderedItem.html b/data/corefork.telegram.org/type/PageListOrderedItem.html new file mode 100644 index 0000000000..dfe674b3db --- /dev/null +++ b/data/corefork.telegram.org/type/PageListOrderedItem.html @@ -0,0 +1,148 @@ + + + + + PageListOrderedItem + + + + + + + + + + + + + +
+ +
+
+
+ +

PageListOrderedItem

+ +

Represents an instant view ordered list

+

+ +
+
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
+pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
pageListOrderedItemTextOrdered list of text items
pageListOrderedItemBlocksOrdered list of IV blocks
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageRelatedArticle.html b/data/corefork.telegram.org/type/PageRelatedArticle.html new file mode 100644 index 0000000000..2bfc6715d0 --- /dev/null +++ b/data/corefork.telegram.org/type/PageRelatedArticle.html @@ -0,0 +1,143 @@ + + + + + PageRelatedArticle + + + + + + + + + + + + + +
+ +
+
+
+ +

PageRelatedArticle

+ +

Related articles

+

+ +
+
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageRelatedArticleRelated article
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageTableCell.html b/data/corefork.telegram.org/type/PageTableCell.html new file mode 100644 index 0000000000..9f2fac93e9 --- /dev/null +++ b/data/corefork.telegram.org/type/PageTableCell.html @@ -0,0 +1,143 @@ + + + + + PageTableCell + + + + + + + + + + + + + +
+ +
+
+
+ +

PageTableCell

+ +

Represents a table in an instant view table

+

+ +
+
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageTableCellTable cell
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageTableRow.html b/data/corefork.telegram.org/type/PageTableRow.html new file mode 100644 index 0000000000..c187a9ae6b --- /dev/null +++ b/data/corefork.telegram.org/type/PageTableRow.html @@ -0,0 +1,143 @@ + + + + + PageTableRow + + + + + + + + + + + + + +
+ +
+
+
+ +

PageTableRow

+ +

Table row

+

+ +
+
pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageTableRowTable row
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PasswordKdfAlgo.html b/data/corefork.telegram.org/type/PasswordKdfAlgo.html new file mode 100644 index 0000000000..5a695c4aea --- /dev/null +++ b/data/corefork.telegram.org/type/PasswordKdfAlgo.html @@ -0,0 +1,151 @@ + + + + + PasswordKdfAlgo + + + + + + + + + + + + + +
+ +
+
+
+ +

PasswordKdfAlgo

+ +

Key derivation function to use when generating the password hash for SRP two-factor authorization

+

+ +
+
passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
+passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
passwordKdfAlgoUnknownUnknown KDF (most likely, the client is outdated and does not support the specified KDF algorithm)
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPowThis key derivation algorithm defines that SRP 2FA login must be used
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PaymentCharge.html b/data/corefork.telegram.org/type/PaymentCharge.html new file mode 100644 index 0000000000..67f9a8ac74 --- /dev/null +++ b/data/corefork.telegram.org/type/PaymentCharge.html @@ -0,0 +1,143 @@ + + + + + PaymentCharge + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentCharge

+ +

Charged payment

+

+ +
+
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentChargePayment identifier
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PaymentRequestedInfo.html b/data/corefork.telegram.org/type/PaymentRequestedInfo.html new file mode 100644 index 0000000000..07429a2328 --- /dev/null +++ b/data/corefork.telegram.org/type/PaymentRequestedInfo.html @@ -0,0 +1,143 @@ + + + + + PaymentRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentRequestedInfo

+ +

Requested payment info

+

+ +
+
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentRequestedInfoOrder info provided by the user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PaymentSavedCredentials.html b/data/corefork.telegram.org/type/PaymentSavedCredentials.html new file mode 100644 index 0000000000..0a81b5a8ce --- /dev/null +++ b/data/corefork.telegram.org/type/PaymentSavedCredentials.html @@ -0,0 +1,143 @@ + + + + + PaymentSavedCredentials + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentSavedCredentials

+ +

Saved payment credentials

+

+ +
+
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentSavedCredentialsCardSaved credit card
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Peer.html b/data/corefork.telegram.org/type/Peer.html new file mode 100644 index 0000000000..c9579af2c2 --- /dev/null +++ b/data/corefork.telegram.org/type/Peer.html @@ -0,0 +1,153 @@ + + + + + Peer + + + + + + + + + + + + + +
+ +
+
+
+ +

Peer

+ +

Chat partner or group.

+

+ +
+
peerUser#59511722 user_id:long = Peer;
+peerChat#36c6019a chat_id:long = Peer;
+peerChannel#a2a5371e channel_id:long = Peer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
peerUserChat partner
peerChatGroup.
peerChannelChannel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PeerBlocked.html b/data/corefork.telegram.org/type/PeerBlocked.html new file mode 100644 index 0000000000..8cf4053127 --- /dev/null +++ b/data/corefork.telegram.org/type/PeerBlocked.html @@ -0,0 +1,143 @@ + + + + + PeerBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

PeerBlocked

+ +

Info about a blocked user

+

+ +
+
peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
peerBlockedInformation about a blocked peer
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PeerLocated.html b/data/corefork.telegram.org/type/PeerLocated.html new file mode 100644 index 0000000000..6296f67b98 --- /dev/null +++ b/data/corefork.telegram.org/type/PeerLocated.html @@ -0,0 +1,148 @@ + + + + + PeerLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

PeerLocated

+ +

Geolocated peer

+

+ +
+
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;
+peerSelfLocated#f8ec284b expires:int = PeerLocated;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
peerLocatedPeer geolocated nearby
peerSelfLocatedCurrent peer
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PeerNotifySettings.html b/data/corefork.telegram.org/type/PeerNotifySettings.html new file mode 100644 index 0000000000..1f74098c50 --- /dev/null +++ b/data/corefork.telegram.org/type/PeerNotifySettings.html @@ -0,0 +1,162 @@ + + + + + PeerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

PeerNotifySettings

+ +

Notification settings.

+

+ +
+
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
+
+---functions---
+
+account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
peerNotifySettingsNotification settings.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PeerSettings.html b/data/corefork.telegram.org/type/PeerSettings.html new file mode 100644 index 0000000000..fec0facaca --- /dev/null +++ b/data/corefork.telegram.org/type/PeerSettings.html @@ -0,0 +1,158 @@ + + + + + PeerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

PeerSettings

+ +

Peer settings

+

+ +
+
peerSettings#a518110d 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 request_chat_broadcast:flags.10?true geo_distance:flags.6?int request_chat_title:flags.9?string request_chat_date:flags.9?int = PeerSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
peerSettingsPeer settings
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getPeerSettingsGet peer settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PhoneCallDiscardReason.html b/data/corefork.telegram.org/type/PhoneCallDiscardReason.html new file mode 100644 index 0000000000..25e9a8570e --- /dev/null +++ b/data/corefork.telegram.org/type/PhoneCallDiscardReason.html @@ -0,0 +1,158 @@ + + + + + PhoneCallDiscardReason + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCallDiscardReason

+ +

Why was the phone call discarded?

+

+ +
+
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;
+phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;
+phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;
+phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneCallDiscardReasonMissedThe phone call was missed
phoneCallDiscardReasonDisconnectThe phone call was disconnected
phoneCallDiscardReasonHangupThe phone call was ended normally
phoneCallDiscardReasonBusyThe phone call was discared because the user is busy in another call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PhoneCallProtocol.html b/data/corefork.telegram.org/type/PhoneCallProtocol.html new file mode 100644 index 0000000000..4ba968fefd --- /dev/null +++ b/data/corefork.telegram.org/type/PhoneCallProtocol.html @@ -0,0 +1,143 @@ + + + + + PhoneCallProtocol + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCallProtocol

+ +

Phone call protocol

+

+ +
+
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phoneCallProtocolProtocol info for libtgvoip
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PhoneConnection.html b/data/corefork.telegram.org/type/PhoneConnection.html new file mode 100644 index 0000000000..91be252fad --- /dev/null +++ b/data/corefork.telegram.org/type/PhoneConnection.html @@ -0,0 +1,148 @@ + + + + + PhoneConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneConnection

+ +

Phone call connection

+

+ +
+
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;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneConnectionIdentifies an endpoint that can be used to connect to the other user in a phone call
phoneConnectionWebrtcWebRTC connection parameters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Photo.html b/data/corefork.telegram.org/type/Photo.html new file mode 100644 index 0000000000..d04ef21510 --- /dev/null +++ b/data/corefork.telegram.org/type/Photo.html @@ -0,0 +1,148 @@ + + + + + Photo + + + + + + + + + + + + + +
+ +
+
+
+ +

Photo

+ +

Object describes a photo.

+

+ +
+
photoEmpty#2331b22d id:long = Photo;
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
photoEmptyEmpty constructor, non-existent photo
photoPhoto
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PhotoSize.html b/data/corefork.telegram.org/type/PhotoSize.html new file mode 100644 index 0000000000..7a00981558 --- /dev/null +++ b/data/corefork.telegram.org/type/PhotoSize.html @@ -0,0 +1,168 @@ + + + + + PhotoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

PhotoSize

+ +

Location of a certain size of a picture

+

+ +
+
photoSizeEmpty#e17e23c type:string = PhotoSize;
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
+photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
+photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
+photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
photoSizeEmptyEmpty constructor. Image with this thumbnail is unavailable.
photoSizeImage description.
photoCachedSizeDescription of an image and its content.
photoStrippedSizeJust the image's content
photoSizeProgressiveProgressively encoded photosize
photoPathSizeMessages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Poll.html b/data/corefork.telegram.org/type/Poll.html new file mode 100644 index 0000000000..fabcb44912 --- /dev/null +++ b/data/corefork.telegram.org/type/Poll.html @@ -0,0 +1,143 @@ + + + + + Poll + + + + + + + + + + + + + +
+ +
+
+
+ +

Poll

+ +

Indicates a poll message

+

+ +
+
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollPoll
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PollAnswer.html b/data/corefork.telegram.org/type/PollAnswer.html new file mode 100644 index 0000000000..a8dc6d588f --- /dev/null +++ b/data/corefork.telegram.org/type/PollAnswer.html @@ -0,0 +1,146 @@ + + + + + PollAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

PollAnswer

+ +

Indicates a possible answer to a poll.

+

+ +
+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollAnswerA possible answer of a poll
+

Related pages

+

Poll

+

Indicates a poll message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PollAnswerVoters.html b/data/corefork.telegram.org/type/PollAnswerVoters.html new file mode 100644 index 0000000000..370cc53195 --- /dev/null +++ b/data/corefork.telegram.org/type/PollAnswerVoters.html @@ -0,0 +1,143 @@ + + + + + PollAnswerVoters + + + + + + + + + + + + + +
+ +
+
+
+ +

PollAnswerVoters

+ +

How users voted on a certain poll answer

+

+ +
+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollAnswerVotersA poll answer, and how users voted on it
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PollResults.html b/data/corefork.telegram.org/type/PollResults.html new file mode 100644 index 0000000000..f88f1a1c7d --- /dev/null +++ b/data/corefork.telegram.org/type/PollResults.html @@ -0,0 +1,143 @@ + + + + + PollResults + + + + + + + + + + + + + +
+ +
+
+
+ +

PollResults

+ +

Results of poll

+

+ +
+
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollResultsResults of poll
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PopularContact.html b/data/corefork.telegram.org/type/PopularContact.html new file mode 100644 index 0000000000..46860fabd2 --- /dev/null +++ b/data/corefork.telegram.org/type/PopularContact.html @@ -0,0 +1,143 @@ + + + + + PopularContact + + + + + + + + + + + + + +
+ +
+
+
+ +

PopularContact

+ +

Popular contact

+

+ +
+
popularContact#5ce14175 client_id:long importers:int = PopularContact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
popularContactPopular contact
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PostAddress.html b/data/corefork.telegram.org/type/PostAddress.html new file mode 100644 index 0000000000..e8ac09253b --- /dev/null +++ b/data/corefork.telegram.org/type/PostAddress.html @@ -0,0 +1,143 @@ + + + + + PostAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

PostAddress

+ +

Shipping address

+

+ +
+
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
postAddressShipping address
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PrivacyKey.html b/data/corefork.telegram.org/type/PrivacyKey.html new file mode 100644 index 0000000000..ce0f6ebb96 --- /dev/null +++ b/data/corefork.telegram.org/type/PrivacyKey.html @@ -0,0 +1,178 @@ + + + + + PrivacyKey + + + + + + + + + + + + + +
+ +
+
+
+ +

PrivacyKey

+ +

Privacy key

+

+ +
+
privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;
+privacyKeyChatInvite#500e6dfa = PrivacyKey;
+privacyKeyPhoneCall#3d662b7b = PrivacyKey;
+privacyKeyPhoneP2P#39491cc8 = PrivacyKey;
+privacyKeyForwards#69ec56a3 = PrivacyKey;
+privacyKeyProfilePhoto#96151fed = PrivacyKey;
+privacyKeyPhoneNumber#d19ae46d = PrivacyKey;
+privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
privacyKeyStatusTimestampWhether we can see the last online timestamp
privacyKeyChatInviteWhether the user can be invited to chats
privacyKeyPhoneCallWhether the user accepts phone calls
privacyKeyPhoneP2PWhether P2P connections in phone calls are allowed
privacyKeyForwardsWhether messages forwarded from the user will be anonymously forwarded
privacyKeyProfilePhotoWhether the profile picture of the user is visible
privacyKeyPhoneNumberWhether the user allows us to see his phone number
privacyKeyAddedByPhoneWhether people can add you to their contact list by your phone number
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PrivacyRule.html b/data/corefork.telegram.org/type/PrivacyRule.html new file mode 100644 index 0000000000..b895e7aa48 --- /dev/null +++ b/data/corefork.telegram.org/type/PrivacyRule.html @@ -0,0 +1,178 @@ + + + + + PrivacyRule + + + + + + + + + + + + + +
+ +
+
+
+ +

PrivacyRule

+ +

Privacy rule

+

+ +
+
privacyValueAllowContacts#fffe1bac = PrivacyRule;
+privacyValueAllowAll#65427b82 = PrivacyRule;
+privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;
+privacyValueDisallowContacts#f888fa1a = PrivacyRule;
+privacyValueDisallowAll#8b73e763 = PrivacyRule;
+privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;
+privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
+privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
privacyValueAllowContactsAllow all contacts
privacyValueAllowAllAllow all users
privacyValueAllowUsersAllow only certain users
privacyValueDisallowContactsDisallow only contacts
privacyValueDisallowAllDisallow all users
privacyValueDisallowUsersDisallow only certain users
privacyValueAllowChatParticipantsAllow all participants of certain chats
privacyValueDisallowChatParticipantsDisallow only participants of certain chats
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ReactionCount.html b/data/corefork.telegram.org/type/ReactionCount.html new file mode 100644 index 0000000000..c0bb0e7e1d --- /dev/null +++ b/data/corefork.telegram.org/type/ReactionCount.html @@ -0,0 +1,128 @@ + + + + + ReactionCount + + + + + + + + + + + + + +
+ +
+
+
+ +

ReactionCount

+ +

Number of users that reacted with a certain emoji

+

+ +
+
reactionCount#6fb250d1 flags:# chosen:flags.0?true reaction:string count:int = ReactionCount;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ReceivedNotifyMessage.html b/data/corefork.telegram.org/type/ReceivedNotifyMessage.html new file mode 100644 index 0000000000..87298150d0 --- /dev/null +++ b/data/corefork.telegram.org/type/ReceivedNotifyMessage.html @@ -0,0 +1,143 @@ + + + + + ReceivedNotifyMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

ReceivedNotifyMessage

+ +

Confirmation of message receipt

+

+ +
+
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
receivedNotifyMessageMessage ID, for which PUSH-notifications were cancelled.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/RecentMeUrl.html b/data/corefork.telegram.org/type/RecentMeUrl.html new file mode 100644 index 0000000000..6ebe3aee71 --- /dev/null +++ b/data/corefork.telegram.org/type/RecentMeUrl.html @@ -0,0 +1,163 @@ + + + + + RecentMeUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

RecentMeUrl

+ +

Recent t.me urls

+

+ +
+
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;
+recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;
+recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;
+recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;
+recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
recentMeUrlUnknownUnknown t.me url
recentMeUrlUserRecent t.me link to a user
recentMeUrlChatRecent t.me link to a chat
recentMeUrlChatInviteRecent t.me invite link to a chat
recentMeUrlStickerSetRecent t.me stickerset installation URL
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ReplyMarkup.html b/data/corefork.telegram.org/type/ReplyMarkup.html new file mode 100644 index 0000000000..b2f10c3c72 --- /dev/null +++ b/data/corefork.telegram.org/type/ReplyMarkup.html @@ -0,0 +1,158 @@ + + + + + ReplyMarkup + + + + + + + + + + + + + +
+ +
+
+
+ +

ReplyMarkup

+ +

Reply markup for bot and inline keyboards

+

+ +
+
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
+replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
+replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
replyKeyboardHideHide sent bot keyboard
replyKeyboardForceReplyForce the user to send a reply
replyKeyboardMarkupBot keyboard
replyInlineMarkupBot or inline keyboard
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ReportReason.html b/data/corefork.telegram.org/type/ReportReason.html new file mode 100644 index 0000000000..2c820ed099 --- /dev/null +++ b/data/corefork.telegram.org/type/ReportReason.html @@ -0,0 +1,178 @@ + + + + + ReportReason + + + + + + + + + + + + + +
+ +
+
+
+ +

ReportReason

+ +

Report reason

+

+ +
+
inputReportReasonSpam#58dbcab8 = ReportReason;
+inputReportReasonViolence#1e22c78d = ReportReason;
+inputReportReasonPornography#2e59d922 = ReportReason;
+inputReportReasonChildAbuse#adf44ee3 = ReportReason;
+inputReportReasonOther#c1e4a2b1 = ReportReason;
+inputReportReasonCopyright#9b89f93a = ReportReason;
+inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;
+inputReportReasonFake#f5ddd6e7 = ReportReason;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputReportReasonSpamReport for spam
inputReportReasonViolenceReport for violence
inputReportReasonPornographyReport for pornography
inputReportReasonChildAbuseReport for child abuse
inputReportReasonOtherOther
inputReportReasonCopyrightReport for copyrighted content
inputReportReasonGeoIrrelevantReport an irrelevant geogroup
inputReportReasonFakeReport for impersonation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/RestrictionReason.html b/data/corefork.telegram.org/type/RestrictionReason.html new file mode 100644 index 0000000000..f2d258b7a8 --- /dev/null +++ b/data/corefork.telegram.org/type/RestrictionReason.html @@ -0,0 +1,143 @@ + + + + + RestrictionReason + + + + + + + + + + + + + +
+ +
+
+
+ +

RestrictionReason

+ +

Restriction reason

+

+ +
+
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
restrictionReasonRestriction reason
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/RichText.html b/data/corefork.telegram.org/type/RichText.html new file mode 100644 index 0000000000..6cd84f4a35 --- /dev/null +++ b/data/corefork.telegram.org/type/RichText.html @@ -0,0 +1,218 @@ + + + + + RichText + + + + + + + + + + + + + +
+ +
+
+
+ +

RichText

+ +

Rich text

+

+ +
+
textEmpty#dc3d824f = RichText;
+textPlain#744694e0 text:string = RichText;
+textBold#6724abc4 text:RichText = RichText;
+textItalic#d912a59c text:RichText = RichText;
+textUnderline#c12622c4 text:RichText = RichText;
+textStrike#9bf8bb95 text:RichText = RichText;
+textFixed#6c3f19b9 text:RichText = RichText;
+textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;
+textEmail#de5a0dd6 text:RichText email:string = RichText;
+textConcat#7e6260d7 texts:Vector<RichText> = RichText;
+textSubscript#ed6a8504 text:RichText = RichText;
+textSuperscript#c7fb5e01 text:RichText = RichText;
+textMarked#34b8621 text:RichText = RichText;
+textPhone#1ccb966a text:RichText phone:string = RichText;
+textImage#81ccf4f document_id:long w:int h:int = RichText;
+textAnchor#35553762 text:RichText name:string = RichText;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
textEmptyEmpty rich text element
textPlainPlain text
textBoldBold text
textItalicItalic text
textUnderlineUnderlined text
textStrikeStrikethrough text
textFixedfixed-width rich text
textUrlLink
textEmailRich text email link
textConcatConcatenation of rich texts
textSubscriptSubscript text
textSuperscriptSuperscript text
textMarkedHighlighted text
textPhoneRich text linked to a phone number
textImageInline image
textAnchorText linking to another section of the page
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SavedContact.html b/data/corefork.telegram.org/type/SavedContact.html new file mode 100644 index 0000000000..7a7b187224 --- /dev/null +++ b/data/corefork.telegram.org/type/SavedContact.html @@ -0,0 +1,143 @@ + + + + + SavedContact + + + + + + + + + + + + + +
+ +
+
+
+ +

SavedContact

+ +

Saved contact

+

+ +
+
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
savedPhoneContactSaved contact
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SearchResultsCalendarPeriod.html b/data/corefork.telegram.org/type/SearchResultsCalendarPeriod.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/SearchResultsCalendarPeriod.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SearchResultsPosition.html b/data/corefork.telegram.org/type/SearchResultsPosition.html new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/SearchResultsPosition.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecureCredentialsEncrypted.html b/data/corefork.telegram.org/type/SecureCredentialsEncrypted.html new file mode 100644 index 0000000000..b00a5b47c6 --- /dev/null +++ b/data/corefork.telegram.org/type/SecureCredentialsEncrypted.html @@ -0,0 +1,143 @@ + + + + + SecureCredentialsEncrypted + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureCredentialsEncrypted

+ +

Encrypted secure credentials

+

+ +
+
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureCredentialsEncryptedEncrypted credentials required to decrypt telegram passport data.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecureData.html b/data/corefork.telegram.org/type/SecureData.html new file mode 100644 index 0000000000..d30e0847e4 --- /dev/null +++ b/data/corefork.telegram.org/type/SecureData.html @@ -0,0 +1,146 @@ + + + + + SecureData + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureData

+ +

Secure passport data, for more info see the passport docs »

+

+ +
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureDataSecure data
+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecureFile.html b/data/corefork.telegram.org/type/SecureFile.html new file mode 100644 index 0000000000..e812ef8c04 --- /dev/null +++ b/data/corefork.telegram.org/type/SecureFile.html @@ -0,0 +1,151 @@ + + + + + SecureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureFile

+ +

Secure passport file, for more info see the passport docs »

+

+ +
+
secureFileEmpty#64199744 = SecureFile;
+secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
secureFileEmptyEmpty constructor
secureFileSecure file
+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html b/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html new file mode 100644 index 0000000000..ec1e8dc569 --- /dev/null +++ b/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html @@ -0,0 +1,155 @@ + + + + + SecurePasswordKdfAlgo + + + + + + + + + + + + + +
+ +
+
+
+ +

SecurePasswordKdfAlgo

+ +

KDF algorithm to use for computing telegram passport hash

+

+ +
+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
securePasswordKdfAlgoUnknownUnknown KDF algo (most likely the client has to be updated)
securePasswordKdfAlgoPBKDF2HMACSHA512iter100000PBKDF2 with SHA512 and 100000 iterations KDF algo
securePasswordKdfAlgoSHA512SHA512 KDF algo
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecurePlainData.html b/data/corefork.telegram.org/type/SecurePlainData.html new file mode 100644 index 0000000000..a43c4ab981 --- /dev/null +++ b/data/corefork.telegram.org/type/SecurePlainData.html @@ -0,0 +1,150 @@ + + + + + SecurePlainData + + + + + + + + + + + + + +
+ +
+
+
+ +

SecurePlainData

+ +

Plaintext verified passport data.

+

+ +
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
securePlainPhonePhone number to use in telegram passport: it must be verified, first ».
securePlainEmailEmail address to use in telegram passport: it must be verified, first ».
+

Related pages

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecureRequiredType.html b/data/corefork.telegram.org/type/SecureRequiredType.html new file mode 100644 index 0000000000..87c15d8913 --- /dev/null +++ b/data/corefork.telegram.org/type/SecureRequiredType.html @@ -0,0 +1,148 @@ + + + + + SecureRequiredType + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureRequiredType

+ +

Required secure file type

+

+ +
+
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;
+secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
secureRequiredTypeRequired type
secureRequiredTypeOneOfOne of
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecureSecretSettings.html b/data/corefork.telegram.org/type/SecureSecretSettings.html new file mode 100644 index 0000000000..7141f979a3 --- /dev/null +++ b/data/corefork.telegram.org/type/SecureSecretSettings.html @@ -0,0 +1,145 @@ + + + + + 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 new file mode 100644 index 0000000000..c0d91a43e4 --- /dev/null +++ b/data/corefork.telegram.org/type/SecureValue.html @@ -0,0 +1,162 @@ + + + + + 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 new file mode 100644 index 0000000000..4b7d6b0310 --- /dev/null +++ b/data/corefork.telegram.org/type/SecureValueError.html @@ -0,0 +1,183 @@ + + + + + SecureValueError + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValueError

+ +

Secure value error

+

+ +
+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
secureValueErrorDataSecure value error
secureValueErrorFrontSideSecure value error front side
secureValueErrorReverseSideReverse side error
secureValueErrorSelfieSecure value error: invalid selfie
secureValueErrorFileSecure value error file
secureValueErrorFilesSecure value error files
secureValueErrorSecure value error
secureValueErrorTranslationFileTranslation missing
secureValueErrorTranslationFilesTranslation file error
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecureValueHash.html b/data/corefork.telegram.org/type/SecureValueHash.html new file mode 100644 index 0000000000..b5730898cf --- /dev/null +++ b/data/corefork.telegram.org/type/SecureValueHash.html @@ -0,0 +1,143 @@ + + + + + SecureValueHash + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValueHash

+ +

Secure value hash

+

+ +
+
secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureValueHashSecure value hash
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecureValueType.html b/data/corefork.telegram.org/type/SecureValueType.html new file mode 100644 index 0000000000..119aa083ea --- /dev/null +++ b/data/corefork.telegram.org/type/SecureValueType.html @@ -0,0 +1,203 @@ + + + + + SecureValueType + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValueType

+ +

Secure value type

+

+ +
+
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
secureValueTypePersonalDetailsPersonal details
secureValueTypePassportPassport
secureValueTypeDriverLicenseDriver's license
secureValueTypeIdentityCardIdentity card
secureValueTypeInternalPassportInternal passport
secureValueTypeAddressAddress
secureValueTypeUtilityBillUtility bill
secureValueTypeBankStatementBank statement
secureValueTypeRentalAgreementRental agreement
secureValueTypePassportRegistrationInternal registration passport
secureValueTypeTemporaryRegistrationTemporary registration
secureValueTypePhonePhone
secureValueTypeEmailEmail
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SendMessageAction.html b/data/corefork.telegram.org/type/SendMessageAction.html new file mode 100644 index 0000000000..5a620c2871 --- /dev/null +++ b/data/corefork.telegram.org/type/SendMessageAction.html @@ -0,0 +1,228 @@ + + + + + SendMessageAction + + + + + + + + + + + + + +
+ +
+
+
+ +

SendMessageAction

+ +

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

+

+ +
+
sendMessageTypingAction#16bf744e = SendMessageAction;
+sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
+sendMessageRecordVideoAction#a187d66f = SendMessageAction;
+sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
+sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
+sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
+sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
+sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
+sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
+sendMessageChooseContactAction#628cbc6f = SendMessageAction;
+sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
+sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
+sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
+speakingInGroupCallAction#d92c2285 = SendMessageAction;
+sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
+sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
sendMessageTypingActionUser is typing.
sendMessageCancelActionInvalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.
sendMessageRecordVideoActionUser is recording a video.
sendMessageUploadVideoActionUser is uploading a video.
sendMessageRecordAudioActionUser is recording a voice message.
sendMessageUploadAudioActionUser is uploading a voice message.
sendMessageUploadPhotoActionUser is uploading a photo.
sendMessageUploadDocumentActionUser is uploading a file.
sendMessageGeoLocationActionUser is selecting a location to share.
sendMessageChooseContactActionUser is selecting a contact to share.
sendMessageGamePlayActionUser is playing a game
sendMessageRecordRoundActionUser is recording a round video to share
sendMessageUploadRoundActionUser is uploading a round video
speakingInGroupCallActionUser is currently speaking in the group call
sendMessageHistoryImportActionChat history is being imported
sendMessageChooseStickerActionUser is choosing a sticker
sendMessageEmojiInteractionUser has clicked on an animated emoji, triggering a reaction
sendMessageEmojiInteractionSeenUser has seen the reaction generated by another user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ShippingOption.html b/data/corefork.telegram.org/type/ShippingOption.html new file mode 100644 index 0000000000..e0cd8361c8 --- /dev/null +++ b/data/corefork.telegram.org/type/ShippingOption.html @@ -0,0 +1,143 @@ + + + + + ShippingOption + + + + + + + + + + + + + +
+ +
+
+
+ +

ShippingOption

+ +

Shipping options

+

+ +
+
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
shippingOptionShipping option
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SponsoredMessage.html b/data/corefork.telegram.org/type/SponsoredMessage.html new file mode 100644 index 0000000000..4ee753a2d0 --- /dev/null +++ b/data/corefork.telegram.org/type/SponsoredMessage.html @@ -0,0 +1,143 @@ + + + + + SponsoredMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

SponsoredMessage

+ +

A sponsored message

+

+ +
+
sponsoredMessage#3a836df8 flags:# random_id:bytes from_id:flags.3?Peer chat_invite:flags.4?ChatInvite chat_invite_hash:flags.4?string channel_post:flags.2?int start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
sponsoredMessageA sponsored message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html b/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html new file mode 100644 index 0000000000..7363b8a423 --- /dev/null +++ b/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html @@ -0,0 +1,143 @@ + + + + + StatsAbsValueAndPrev + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsAbsValueAndPrev

+ +

Channel statistics value pair

+

+ +
+
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsAbsValueAndPrevStatistics value couple; initial and final value for period of time currently in consideration
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsDateRangeDays.html b/data/corefork.telegram.org/type/StatsDateRangeDays.html new file mode 100644 index 0000000000..11f1816515 --- /dev/null +++ b/data/corefork.telegram.org/type/StatsDateRangeDays.html @@ -0,0 +1,143 @@ + + + + + StatsDateRangeDays + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsDateRangeDays

+ +

Channel statistics date range

+

+ +
+
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsDateRangeDaysChannel statistics date range
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsGraph.html b/data/corefork.telegram.org/type/StatsGraph.html new file mode 100644 index 0000000000..d2f2cd01e5 --- /dev/null +++ b/data/corefork.telegram.org/type/StatsGraph.html @@ -0,0 +1,172 @@ + + + + + StatsGraph + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsGraph

+ +

Channel statistics graph

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+
+---functions---
+
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
statsGraphAsyncThis graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load
statsGraphErrorAn error occurred while generating the statistics graph
statsGraphChannel statistics graph
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.loadAsyncGraphLoad channel statistics graph asynchronously
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsGroupTopInviter.html b/data/corefork.telegram.org/type/StatsGroupTopInviter.html new file mode 100644 index 0000000000..0eaf13f7e7 --- /dev/null +++ b/data/corefork.telegram.org/type/StatsGroupTopInviter.html @@ -0,0 +1,146 @@ + + + + + StatsGroupTopInviter + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsGroupTopInviter

+ +

Most active inviter in a supergroup

+

+ +
+
statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsGroupTopInviterInformation about an active supergroup inviter
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsGroupTopPoster.html b/data/corefork.telegram.org/type/StatsGroupTopPoster.html new file mode 100644 index 0000000000..8b05ec28e8 --- /dev/null +++ b/data/corefork.telegram.org/type/StatsGroupTopPoster.html @@ -0,0 +1,146 @@ + + + + + StatsGroupTopPoster + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsGroupTopPoster

+ +

Most active user in a supergroup

+

+ +
+
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsGroupTopPosterInformation about an active user in a supergroup
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsPercentValue.html b/data/corefork.telegram.org/type/StatsPercentValue.html new file mode 100644 index 0000000000..41df1b93b7 --- /dev/null +++ b/data/corefork.telegram.org/type/StatsPercentValue.html @@ -0,0 +1,143 @@ + + + + + StatsPercentValue + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsPercentValue

+ +

Channel statistics percentage

+

+ +
+
statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsPercentValueChannel statistics percentage
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsURL.html b/data/corefork.telegram.org/type/StatsURL.html new file mode 100644 index 0000000000..24d0c5c0eb --- /dev/null +++ b/data/corefork.telegram.org/type/StatsURL.html @@ -0,0 +1,143 @@ + + + + + StatsURL + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsURL

+ +

URL with chat statistics

+

+ +
+
statsURL#47a971e0 url:string = StatsURL;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsURLURL with chat statistics
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StickerPack.html b/data/corefork.telegram.org/type/StickerPack.html new file mode 100644 index 0000000000..e2e77de884 --- /dev/null +++ b/data/corefork.telegram.org/type/StickerPack.html @@ -0,0 +1,143 @@ + + + + + StickerPack + + + + + + + + + + + + + +
+ +
+
+
+ +

StickerPack

+ +

Stickerpack

+

+ +
+
stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stickerPackA stickerpack is a group of stickers associated to the same emoji.
It is not a sticker pack the way it is usually intended, you may be looking for a StickerSet.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StickerSetCovered.html b/data/corefork.telegram.org/type/StickerSetCovered.html new file mode 100644 index 0000000000..d643a705ec --- /dev/null +++ b/data/corefork.telegram.org/type/StickerSetCovered.html @@ -0,0 +1,148 @@ + + + + + StickerSetCovered + + + + + + + + + + + + + +
+ +
+
+
+ +

StickerSetCovered

+ +

Stickerset, with a specific sticker as preview

+

+ +
+
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;
+stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
stickerSetCoveredStickerset, with a specific sticker as preview
stickerSetMultiCoveredStickerset, with a specific stickers as preview
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Theme.html b/data/corefork.telegram.org/type/Theme.html new file mode 100644 index 0000000000..aff19440f0 --- /dev/null +++ b/data/corefork.telegram.org/type/Theme.html @@ -0,0 +1,172 @@ + + + + + Theme + + + + + + + + + + + + + +
+ +
+
+
+ +

Theme

+ +

Cloud theme

+

+ +
+
theme#a00e67d6 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?Vector<ThemeSettings> emoticon:flags.6?string installs_count:flags.4?int = Theme;
+
+---functions---
+
+account.createTheme#652e4400 flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?Vector<InputThemeSettings> = Theme;
+account.updateTheme#2bf40ccc flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?Vector<InputThemeSettings> = Theme;
+account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
themeTheme
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
account.createThemeCreate a theme
account.updateThemeUpdate theme
account.getThemeGet theme information
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ThemeSettings.html b/data/corefork.telegram.org/type/ThemeSettings.html new file mode 100644 index 0000000000..5f26a499b2 --- /dev/null +++ b/data/corefork.telegram.org/type/ThemeSettings.html @@ -0,0 +1,143 @@ + + + + + ThemeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

ThemeSettings

+ +

Theme settings

+

+ +
+
themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
themeSettingsTheme settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/TopPeerCategory.html b/data/corefork.telegram.org/type/TopPeerCategory.html new file mode 100644 index 0000000000..8e2c32d35e --- /dev/null +++ b/data/corefork.telegram.org/type/TopPeerCategory.html @@ -0,0 +1,178 @@ + + + + + TopPeerCategory + + + + + + + + + + + + + +
+ +
+
+
+ +

TopPeerCategory

+ +

Top peer category

+

+ +
+
topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
+topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
+topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
+topPeerCategoryGroups#bd17a14a = TopPeerCategory;
+topPeerCategoryChannels#161d9628 = TopPeerCategory;
+topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
+topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
+topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
topPeerCategoryBotsPMMost used bots
topPeerCategoryBotsInlineMost used inline bots
topPeerCategoryCorrespondentsUsers we've chatted most frequently with
topPeerCategoryGroupsOften-opened groups and supergroups
topPeerCategoryChannelsMost frequently visited channels
topPeerCategoryPhoneCallsMost frequently called users
topPeerCategoryForwardUsersUsers to which the users often forwards messages to
topPeerCategoryForwardChatsChats to which the users often forwards messages to
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/TopPeerCategoryPeers.html b/data/corefork.telegram.org/type/TopPeerCategoryPeers.html new file mode 100644 index 0000000000..ad4d486e6d --- /dev/null +++ b/data/corefork.telegram.org/type/TopPeerCategoryPeers.html @@ -0,0 +1,143 @@ + + + + + TopPeerCategoryPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

TopPeerCategoryPeers

+ +

Top peers by top peer category

+

+ +
+
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
topPeerCategoryPeersTop peer category
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/True.html b/data/corefork.telegram.org/type/True.html new file mode 100644 index 0000000000..cf1fb95835 --- /dev/null +++ b/data/corefork.telegram.org/type/True.html @@ -0,0 +1,145 @@ + + + + + True + + + + + + + + + + + + + +
+ +
+
+
+ +

True

+ +

See predefined identifiers.

+

+ +
+
true#3fedd339 = True;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
trueSee predefined identifiers.
+

Related pages

+

TL-formal

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Update.html b/data/corefork.telegram.org/type/Update.html new file mode 100644 index 0000000000..ee56835e88 --- /dev/null +++ b/data/corefork.telegram.org/type/Update.html @@ -0,0 +1,606 @@ + + + + + Update + + + + + + + + + + + + + +
+ +
+
+
+ +

Update

+ +

Object contains info on events occured.

+

+ +
+
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+updateMessageID#4e90bfd6 id:int random_id:long = Update;
+updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;
+updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
+updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;
+updateChatParticipants#7761198 participants:ChatParticipants = Update;
+updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;
+updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;
+updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;
+updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;
+updateEncryptedChatTyping#1710f156 chat_id:int = Update;
+updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;
+updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;
+updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;
+updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;
+updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;
+updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
+updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
+updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;
+updateUserPhone#5492a13 user_id:long phone:string = Update;
+updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;
+updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;
+updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;
+updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;
+updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;
+updateChannel#635b4c09 channel_id:long = Update;
+updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
+updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;
+updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;
+updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;
+updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;
+updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;
+updateStickerSets#43ae3dec = Update;
+updateSavedGifs#9375341e = Update;
+updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
+updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
+updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;
+updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;
+updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;
+updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;
+updateReadFeaturedStickers#571d2742 = Update;
+updateRecentStickers#9a422c20 = Update;
+updateConfig#a229dd06 = Update;
+updatePtsChanged#3354678f = Update;
+updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;
+updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;
+updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;
+updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;
+updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;
+updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
+updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
+updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;
+updateLangPackTooLong#46560264 lang_code:string = Update;
+updateLangPack#56022f4d difference:LangPackDifference = Update;
+updateFavedStickers#e511996d = Update;
+updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;
+updateContactsReset#7084a7be = Update;
+updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;
+updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;
+updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
+updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;
+updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;
+updateNewScheduledMessage#39a51dfb message:Message = Update;
+updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
+updateTheme#8216fba3 theme:Theme = Update;
+updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
+updateLoginToken#564fe691 = Update;
+updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
+updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
+updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
+updateDialogFilters#3504914f = Update;
+updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;
+updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;
+updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;
+updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;
+updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;
+updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;
+updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
+updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+updateChat#f89a6a4e chat_id:long = Update;
+updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
+updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;
+updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
+updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;
+updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;
+updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;
+updatePendingJoinRequests#7063c3db peer:Peer requests_pending:int recent_requesters:Vector<long> = Update;
+updateBotChatInviteRequester#11dfa986 peer:Peer date:int user_id:long about:string invite:ExportedChatInvite qts:int = Update;
+updateMessageReactions#154798c3 peer:Peer msg_id:int reactions:MessageReactions = Update;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updateNewMessageNew message.
updateMessageIDSent message with random_id client identifier was assigned an identifier.
updateDeleteMessagesMessages were deleted.
updateUserTypingThe user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.
updateChatUserTypingThe user is preparing a message in a group; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.
updateChatParticipantsComposition of chat participants changed.
updateUserStatusContact status update.
updateUserNameChanges the user's first name, last name and username.
updateUserPhotoChange of contact's profile photo.
updateNewEncryptedMessageNew encrypted message.
updateEncryptedChatTypingInterlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.
updateEncryptionChange of state in an encrypted chat.
updateEncryptedMessagesReadCommunication history in an encrypted chat was marked as read.
updateChatParticipantAddNew group member.
updateChatParticipantDeleteA member has left the group.
updateDcOptionsChanges in the data center configuration options.
updateNotifySettingsChanges in notification settings.
updateServiceNotificationA service message for the user.

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
updatePrivacyPrivacy rules were changed
updateUserPhoneA user's phone number was changed
updateReadHistoryInboxIncoming messages were read
updateReadHistoryOutboxOutgoing messages were read
updateWebPageAn (IV) webpage preview was generated
updateReadMessagesContentsContents of messages in the common message box were read
updateChannelTooLongThere are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
updateChannelA new channel is available
updateNewChannelMessageA new message was sent in a channel/supergroup
updateReadChannelInboxIncoming messages in a channel/supergroup were read
updateDeleteChannelMessagesSome messages in a supergroup/channel were deleted
updateChannelMessageViewsThe view counter of a message in a channel has changed
updateChatParticipantAdminAdmin permissions of a user in a legacy group were changed
updateNewStickerSetA new stickerset was installed
updateStickerSetsOrderThe order of stickersets was changed
updateStickerSetsInstalled stickersets have changed, the client should refetch them using messages.getAllStickers
updateSavedGifsThe saved gif list has changed, the client should refetch it using messages.getSavedGifs
updateBotInlineQueryAn incoming inline query
updateBotInlineSendThe result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
updateEditChannelMessageA message was edited in a channel/supergroup
updateBotCallbackQueryA callback button was pressed, and the button data was sent to the bot that created the button
updateEditMessageA message was edited
updateInlineBotCallbackQueryThis notification is received by bots when a button is pressed
updateReadChannelOutboxOutgoing messages in a channel/supergroup were read
updateDraftMessageNotifies a change of a message draft.
updateReadFeaturedStickersSome featured stickers were marked as read
updateRecentStickersThe recent sticker list was updated
updateConfigThe server-side configuration has changed; the client should re-fetch the config using help.getConfig
updatePtsChangedCommon message box sequence PTS has changed, state has to be refetched using updates.getState
updateChannelWebPageA webpage preview of a link in a channel/supergroup message was generated
updateDialogPinnedA dialog was pinned/unpinned
updatePinnedDialogsPinned dialogs were updated
updateBotWebhookJSONA new incoming event; for bots only
updateBotWebhookJSONQueryA new incoming query; for bots only
updateBotShippingQueryThis object contains information about an incoming shipping query.
updateBotPrecheckoutQueryThis object contains information about an incoming pre-checkout query.
updatePhoneCallAn incoming phone call
updateLangPackTooLongA language pack has changed, the client should manually fetch the changed strings using langpack.getDifference
updateLangPackLanguage pack updated
updateFavedStickersThe list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list
updateChannelReadMessagesContentsThe specified channel/supergroup messages were read
updateContactsResetAll contacts were deleted
updateChannelAvailableMessagesThe history of a channel/supergroup was hidden.
updateDialogUnreadMarkThe manual unread mark of a chat was changed
updateMessagePollThe results of a poll have changed
updateChatDefaultBannedRightsDefault banned rights in a normal chat were updated
updateFolderPeersThe dialog list of a folder was changed
updatePeerSettingsSettings of a certain peer have changed
updatePeerLocatedList of peers near you was updated
updateNewScheduledMessageNew incoming scheduled message
updateDeleteScheduledMessagesSome scheduled messages were deleted
updateThemeA new cloud theme was installed
updateGeoLiveViewedLive geoposition message was viewed
updateLoginTokenA login token (for login via QR code) was generated
updateMessagePollVoteA specific user has voted in a poll
updateDialogFilterA new folder was added
updateDialogFilterOrderNew chat folders order
updateDialogFiltersUpdate folder list
updatePhoneCallSignalingDataIncoming phone call signaling payload
updateChannelMessageForwardsThe forward counter of a message in a channel has changed
updateReadChannelDiscussionInboxIncoming messages were marked as read
updateReadChannelDiscussionOutboxOutgoing comments in a discussion thread were marked as read
updatePeerBlockedA peer was blocked
updateChannelUserTypinguser is typing in a supergroup, channel or message thread
updatePinnedMessagesSome messages were pinned in a chat
updatePinnedChannelMessagesMessages were pinned/unpinned in a channel/supergroup
updateChatA new chat is available
updateGroupCallParticipantsThe participant list of a certain group call has changed
updateGroupCallA new groupcall was started
updatePeerHistoryTTLThe Time-To-Live for messages sent by the current user in a specific chat has changed
updateChatParticipantA user has joined or left a specific chat
updateChannelParticipantA participant has left/joined a channel or supergroup.
updateBotStoppedA bot was stopped or re-started.
updateGroupCallConnectionNew WebRTC parameters
updateBotCommandsThe command set of a certain bot in a certain chat has changed.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Updates.html b/data/corefork.telegram.org/type/Updates.html new file mode 100644 index 0000000000..e6271b3738 --- /dev/null +++ b/data/corefork.telegram.org/type/Updates.html @@ -0,0 +1,514 @@ + + + + + Updates + + + + + + + + + + + + + +
+ +
+
+
+ +

Updates

+ +

Object which is perceived by the client without a call on its part when an event occurs.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+
+---functions---
+
+contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;
+contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;
+contacts.acceptContact#f831a20f id:InputUser = Updates;
+contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
+
+messages.sendMessage#d9d75a4 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?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 send_as:flags.13?InputPeer = Updates;
+messages.sendMedia#e25ff8e0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?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 send_as:flags.13?InputPeer = Updates;
+messages.forwardMessages#cc30290b 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 noforwards:flags.14?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;
+messages.editChatTitle#73783ffd chat_id:long title:string = Updates;
+messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
+messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;
+messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;
+messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;
+messages.importChatInvite#6c50051c hash:string = Updates;
+messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;
+messages.migrateChat#a2875319 chat_id:long = Updates;
+messages.sendInlineBotResult#7aa11297 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 send_as:flags.13?InputPeer = Updates;
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
+messages.getAllDrafts#6a3f8d65 = Updates;
+messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
+messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;
+messages.sendMultiMedia#f803138f flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
+messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
+messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
+messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;
+messages.hideChatJoinRequest#7fe7e815 flags:# approved:flags.0?true peer:InputPeer user_id:InputUser = Updates;
+messages.hideAllChatJoinRequests#e085f4ea flags:# approved:flags.0?true peer:InputPeer link:flags.1?string = Updates;
+messages.toggleNoForwards#b11eafa2 peer:InputPeer enabled:Bool = Updates;
+messages.sendReaction#25690ce4 flags:# big:flags.1?true peer:InputPeer msg_id:int reaction:flags.0?string = Updates;
+messages.getMessagesReactions#8bba90e6 peer:InputPeer id:Vector<int> = Updates;
+messages.setChatAvailableReactions#14050ea6 peer:InputPeer available_reactions:Vector<string> = Updates;
+
+help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
+
+channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;
+channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;
+channels.editTitle#566decd0 channel:InputChannel title:string = Updates;
+channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
+channels.joinChannel#24b524c5 channel:InputChannel = Updates;
+channels.leaveChannel#f836aa95 channel:InputChannel = Updates;
+channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;
+channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;
+channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;
+channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;
+channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
+channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;
+channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;
+channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;
+
+phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;
+phone.createGroupCall#48cdc6d8 flags:# rtmp_stream:flags.2?true peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
+phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
+phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
+phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
+phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;
+phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;
+phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;
+phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
+phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
+phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;
+
+account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;
+
+folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
+folders.deleteFolder#1c295881 folder_id:int = Updates;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updatesTooLongToo many updates, it is necessary to execute updates.getDifference.
updateShortMessageInfo about a message sent to (received from) another user
updateShortChatMessageShortened constructor containing info on one new incoming text message from a chat
updateShortShortened constructor containing info on one update not requiring auxiliary data
updatesCombinedConstructor for a group of updates.
updatesFull constructor of updates
updateShortSentMessageShortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
contacts.deleteContactsDeletes several contacts from the list.
messages.sendMessageSends a message to a chat
messages.sendMediaSend a media
messages.forwardMessagesForwards messages by their IDs.
messages.editChatTitleChanages chat name and sends a service message on it.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.createChatCreates a new chat.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getAppChangelogGet changelog of current app
channels.createChannelCreate a supergroup/channel.
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editTitleEdit the name of a channel/supergroup
channels.editPhotoChange the photo of a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.inviteToChannelInvite users to a channel/supergroup
channels.deleteChannelDelete a channel/supergroup
messages.migrateChatTurn a legacy group into a supergroup
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
channels.toggleSignaturesEnable/disable message signatures in channels
messages.editMessageEdit message
messages.getAllDraftsSave get all message drafts.
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
phone.discardCallRefuse or end running call
phone.setCallRatingRate a call
channels.editBannedBan/unban/kick a user in a supergroup/channel.
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
messages.sendMultiMediaSend an album of media
messages.updatePinnedMessagePin a message
account.getNotifyExceptionsReturns list of chats with non-default notification settings
messages.sendVoteVote in a poll
messages.getPollResultsGet poll results
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
folders.editPeerFoldersEdit peers in folder
folders.deleteFolderDelete a folder
contacts.addContactAdd an existing telegram user as contact
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
channels.editCreatorTransfer channel ownership
contacts.getLocatedGet contacts near you
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
messages.sendScheduledMessagesSend scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
phone.createGroupCallCreate a group call or livestream
phone.joinGroupCallJoin a group call
phone.leaveGroupCallLeave a group call
phone.inviteToGroupCallInvite a set of users to a group call.
phone.discardGroupCallTerminate a group call
phone.toggleGroupCallSettingsChange group call settings
messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
channels.convertToGigagroupConvert a supergroup to a gigagroup
phone.toggleGroupCallRecordStart or stop recording a group call
phone.editGroupCallParticipantEdit information about a given group call participant
phone.editGroupCallTitleEdit the title of a group call or livestream
phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
phone.startScheduledGroupCallStart a scheduled group call.
phone.joinGroupCallPresentationStart screen sharing in a call
phone.leaveGroupCallPresentationStop screen sharing in a group call
messages.setChatThemeChange the chat theme of a certain chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/UrlAuthResult.html b/data/corefork.telegram.org/type/UrlAuthResult.html new file mode 100644 index 0000000000..d6d6fe10f8 --- /dev/null +++ b/data/corefork.telegram.org/type/UrlAuthResult.html @@ -0,0 +1,177 @@ + + + + + UrlAuthResult + + + + + + + + + + + + + +
+ +
+
+
+ +

UrlAuthResult

+ +

URL authorization result

+

+ +
+
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
+urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
+urlAuthResultDefault#a9d6db1f = UrlAuthResult;
+
+---functions---
+
+messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
+messages.acceptUrlAuth#b12c7125 flags:# write_allowed:flags.0?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
urlAuthResultRequestDetails about the authorization request, for more info click here »
urlAuthResultAcceptedDetails about an accepted authorization request, for more info click here »
urlAuthResultDefaultDetails about an accepted authorization request, for more info click here »
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/User.html b/data/corefork.telegram.org/type/User.html new file mode 100644 index 0000000000..e0129303b1 --- /dev/null +++ b/data/corefork.telegram.org/type/User.html @@ -0,0 +1,177 @@ + + + + + User + + + + + + + + + + + + + +
+ +
+
+
+ +

User

+ +

Object defines a user.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+
+---functions---
+
+account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;
+account.updateUsername#3e0bdd7c username:string = User;
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
userEmptyEmpty constructor, non-existent user.
userIndicates info about a certain user
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
account.updateProfileUpdates user profile.
account.updateUsernameChanges username for the current user.
account.changePhoneChange the phone number of the current account
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/UserFull.html b/data/corefork.telegram.org/type/UserFull.html new file mode 100644 index 0000000000..b443b0b2c2 --- /dev/null +++ b/data/corefork.telegram.org/type/UserFull.html @@ -0,0 +1,158 @@ + + + + + UserFull + + + + + + + + + + + + + +
+ +
+
+
+ +

UserFull

+ +

Object contains extended user info.

+

+ +
+
userFull#cf366521 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 id:long 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 private_forward_name:flags.16?string = UserFull;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
userFullExtended user info
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
users.getFullUserReturns extended user info by ID.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/UserProfilePhoto.html b/data/corefork.telegram.org/type/UserProfilePhoto.html new file mode 100644 index 0000000000..6a62d2012b --- /dev/null +++ b/data/corefork.telegram.org/type/UserProfilePhoto.html @@ -0,0 +1,148 @@ + + + + + UserProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

UserProfilePhoto

+ +

Object contains info on the user's profile photo.

+

+ +
+
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;
+userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
userProfilePhotoEmptyProfile photo has not been set, or was hidden.
userProfilePhotoUser profile photo.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/UserStatus.html b/data/corefork.telegram.org/type/UserStatus.html new file mode 100644 index 0000000000..b9452b8f86 --- /dev/null +++ b/data/corefork.telegram.org/type/UserStatus.html @@ -0,0 +1,168 @@ + + + + + UserStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

UserStatus

+ +

User online status

+

+ +
+
userStatusEmpty#9d05049 = UserStatus;
+userStatusOnline#edb93949 expires:int = UserStatus;
+userStatusOffline#8c703f was_online:int = UserStatus;
+userStatusRecently#e26f42f1 = UserStatus;
+userStatusLastWeek#7bf09fc = UserStatus;
+userStatusLastMonth#77ebc742 = UserStatus;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
userStatusEmptyUser status has not been set yet.
userStatusOnlineOnline status of the user.
userStatusOfflineThe user's offline status.
userStatusRecentlyOnline status: last seen recently
userStatusLastWeekOnline status: last seen last week
userStatusLastMonthOnline status: last seen last month
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Vector t.html b/data/corefork.telegram.org/type/Vector t.html new file mode 100644 index 0000000000..08bcd821b5 --- /dev/null +++ b/data/corefork.telegram.org/type/Vector t.html @@ -0,0 +1,143 @@ + + + + + Vector t + + + + + + + + + + + + + +
+ +
+
+
+ +

Vector t

+ +

Universal vector.

+

+ +
+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
vectorA universal vector constructor.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Video.html b/data/corefork.telegram.org/type/Video.html new file mode 100644 index 0000000000..6100a14685 --- /dev/null +++ b/data/corefork.telegram.org/type/Video.html @@ -0,0 +1,128 @@ + + + + + Video + + + + + + + + + + + + + +
+ +
+
+
+ +

Video

+ +

Video.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/VideoSize.html b/data/corefork.telegram.org/type/VideoSize.html new file mode 100644 index 0000000000..add9560a2b --- /dev/null +++ b/data/corefork.telegram.org/type/VideoSize.html @@ -0,0 +1,143 @@ + + + + + VideoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

VideoSize

+ +

Represents an animated video thumbnail

+

+ +
+
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
videoSizeAnimated profile picture in MPEG4 format
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/WallPaperSettings.html b/data/corefork.telegram.org/type/WallPaperSettings.html new file mode 100644 index 0000000000..1bd10a7560 --- /dev/null +++ b/data/corefork.telegram.org/type/WallPaperSettings.html @@ -0,0 +1,143 @@ + + + + + WallPaperSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

WallPaperSettings

+ +

Wallpaper settings

+

+ +
+
wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
wallPaperSettingsWallpaper settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/WebAuthorization.html b/data/corefork.telegram.org/type/WebAuthorization.html new file mode 100644 index 0000000000..3cd9bc0a08 --- /dev/null +++ b/data/corefork.telegram.org/type/WebAuthorization.html @@ -0,0 +1,143 @@ + + + + + WebAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

WebAuthorization

+ +

Web authorization

+

+ +
+
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
webAuthorizationRepresents a bot logged in using the Telegram login widget
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/WebDocument.html b/data/corefork.telegram.org/type/WebDocument.html new file mode 100644 index 0000000000..6d8c0ff179 --- /dev/null +++ b/data/corefork.telegram.org/type/WebDocument.html @@ -0,0 +1,148 @@ + + + + + WebDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

WebDocument

+ +

Remote document

+

+ +
+
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
webDocumentRemote document
webDocumentNoProxyRemote document that can be downloaded without proxying through telegram
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/WebPage.html b/data/corefork.telegram.org/type/WebPage.html new file mode 100644 index 0000000000..b0209e0231 --- /dev/null +++ b/data/corefork.telegram.org/type/WebPage.html @@ -0,0 +1,177 @@ + + + + + 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/WebPageAttribute.html b/data/corefork.telegram.org/type/WebPageAttribute.html new file mode 100644 index 0000000000..e1f370e2f4 --- /dev/null +++ b/data/corefork.telegram.org/type/WebPageAttribute.html @@ -0,0 +1,143 @@ + + + + + WebPageAttribute + + + + + + + + + + + + + +
+ +
+
+
+ +

WebPageAttribute

+ +

Webpage attributes

+

+ +
+
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
webPageAttributeThemePage theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.AuthorizationForm b/data/corefork.telegram.org/type/account.AuthorizationForm new file mode 100644 index 0000000000..a34f6cd306 --- /dev/null +++ b/data/corefork.telegram.org/type/account.AuthorizationForm @@ -0,0 +1,162 @@ + + + + + Account.AuthorizationForm + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.AuthorizationForm

+ +

Authorization form

+

+ +
+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+---functions---
+
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.authorizationFormAuthorization form
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.Authorizations b/data/corefork.telegram.org/type/account.Authorizations new file mode 100644 index 0000000000..60a7b2ebb9 --- /dev/null +++ b/data/corefork.telegram.org/type/account.Authorizations @@ -0,0 +1,162 @@ + + + + + Account.Authorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.Authorizations

+ +

Logged-in sessions

+

+ +
+
account.authorizations#4bff8ea0 authorization_ttl_days:int authorizations:Vector<Authorization> = account.Authorizations;
+
+---functions---
+
+account.getAuthorizations#e320c158 = account.Authorizations;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.authorizationsLogged-in sessions
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAuthorizationsGet logged-in sessions
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.AutoDownloadSettings b/data/corefork.telegram.org/type/account.AutoDownloadSettings new file mode 100644 index 0000000000..5ace2c161c --- /dev/null +++ b/data/corefork.telegram.org/type/account.AutoDownloadSettings @@ -0,0 +1,162 @@ + + + + + Account.AutoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.AutoDownloadSettings

+ +

Media autodownload settings

+

+ +
+
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
+
+---functions---
+
+account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.autoDownloadSettingsMedia autodownload settings
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAutoDownloadSettingsGet media autodownload settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.ChatThemes b/data/corefork.telegram.org/type/account.ChatThemes new file mode 100644 index 0000000000..4e9c81d0f3 --- /dev/null +++ b/data/corefork.telegram.org/type/account.ChatThemes @@ -0,0 +1,162 @@ + + + + + account.ChatThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ChatThemes

+ +

Available chat themes

+

+ +
+

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
account.chatThemesNotModifiedThe available chat themes were not modified
account.chatThemesAvailable chat themes
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getChatThemesGet all available chat themes
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.ContentSettings b/data/corefork.telegram.org/type/account.ContentSettings new file mode 100644 index 0000000000..e8d1d0b27c --- /dev/null +++ b/data/corefork.telegram.org/type/account.ContentSettings @@ -0,0 +1,162 @@ + + + + + account.ContentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ContentSettings

+ +

Sensitive content settings

+

+ +
+
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
+
+---functions---
+
+account.getContentSettings#8b9b4dae = account.ContentSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.contentSettingsSensitive content settings
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getContentSettingsGet sensitive content settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.Password b/data/corefork.telegram.org/type/account.Password new file mode 100644 index 0000000000..5cfee67bc3 --- /dev/null +++ b/data/corefork.telegram.org/type/account.Password @@ -0,0 +1,162 @@ + + + + + account.Password + + + + + + + + + + + + + +
+ +
+
+
+ +

account.Password

+ +

Configuration for two-factor authorization

+

+ +
+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+
+---functions---
+
+account.getPassword#548a30f5 = account.Password;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordConfiguration for two-factor authorization
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getPasswordObtain configuration for two-factor authorization with password
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.PasswordInputSettings b/data/corefork.telegram.org/type/account.PasswordInputSettings new file mode 100644 index 0000000000..e205cbfdf5 --- /dev/null +++ b/data/corefork.telegram.org/type/account.PasswordInputSettings @@ -0,0 +1,146 @@ + + + + + account.PasswordInputSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.PasswordInputSettings

+ +

Constructor for setting up a new 2FA SRP password

+

+ +
+
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordInputSettingsSettings for setting up a new password
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.PasswordSettings b/data/corefork.telegram.org/type/account.PasswordSettings new file mode 100644 index 0000000000..70e659f242 --- /dev/null +++ b/data/corefork.telegram.org/type/account.PasswordSettings @@ -0,0 +1,164 @@ + + + + + account.PasswordSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.PasswordSettings

+ +

Private info associated to the password info (recovery email, telegram passport info & so on)

+

+ +
+
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
+---functions---
+
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordSettingsPrivate info associated to the password info (recovery email, telegram passport info & so on)
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.PrivacyRules b/data/corefork.telegram.org/type/account.PrivacyRules new file mode 100644 index 0000000000..017430d272 --- /dev/null +++ b/data/corefork.telegram.org/type/account.PrivacyRules @@ -0,0 +1,167 @@ + + + + + Account.PrivacyRules + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.PrivacyRules

+ +

Privacy rules

+

+ +
+
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+
+---functions---
+
+account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;
+account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.privacyRulesPrivacy rules
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
account.getPrivacyGet privacy settings of current account
account.setPrivacyChange privacy settings of current account
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.ResetPasswordResult b/data/corefork.telegram.org/type/account.ResetPasswordResult new file mode 100644 index 0000000000..4ac3bd2e29 --- /dev/null +++ b/data/corefork.telegram.org/type/account.ResetPasswordResult @@ -0,0 +1,175 @@ + + + + + account.ResetPasswordResult + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ResetPasswordResult

+ +

Result of an account.resetPassword request.

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+
+---functions---
+
+account.resetPassword#9308ce1b = account.ResetPasswordResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
account.resetPasswordFailedWaitYou requested a password reset too many times, please wait until the specified date before retrying the reset.
account.resetPasswordRequestedWaitYou already requested a password reset, please wait until the specified date before retrying the reset.
account.resetPasswordOkThe 2FA password was reset successfully.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.resetPasswordInitiate a 2FA password reset
+

Related pages

+

account.resetPassword

+

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.SentChangePhoneCode b/data/corefork.telegram.org/type/account.SentChangePhoneCode new file mode 100644 index 0000000000..798b71cd9d --- /dev/null +++ b/data/corefork.telegram.org/type/account.SentChangePhoneCode @@ -0,0 +1,128 @@ + + + + + Account.SentChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.SentChangePhoneCode

+ +

Sent phone code

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.SentEmailCode b/data/corefork.telegram.org/type/account.SentEmailCode new file mode 100644 index 0000000000..caba4c0cd5 --- /dev/null +++ b/data/corefork.telegram.org/type/account.SentEmailCode @@ -0,0 +1,162 @@ + + + + + account.SentEmailCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.SentEmailCode

+ +

The email code that was sent

+

+ +
+
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
+
+---functions---
+
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.sentEmailCodeThe sent email code
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.Takeout b/data/corefork.telegram.org/type/account.Takeout new file mode 100644 index 0000000000..2bd1cf8524 --- /dev/null +++ b/data/corefork.telegram.org/type/account.Takeout @@ -0,0 +1,162 @@ + + + + + Account.Takeout + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.Takeout

+ +

Takeout info

+

+ +
+
account.takeout#4dba4501 id:long = account.Takeout;
+
+---functions---
+
+account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.takeoutTakout info
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.initTakeoutSessionInitialize account takeout session
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.Themes b/data/corefork.telegram.org/type/account.Themes new file mode 100644 index 0000000000..7eaadbae69 --- /dev/null +++ b/data/corefork.telegram.org/type/account.Themes @@ -0,0 +1,168 @@ + + + + + account.Themes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.Themes

+ +

Installed themes

+

+ +
+
account.themesNotModified#f41eb622 = account.Themes;
+account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
+
+---functions---
+
+account.getThemes#7206e458 format:string hash:long = account.Themes;
+account.getChatThemes#d638de89 hash:long = account.Themes;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
account.themesNotModifiedNo new themes were installed
account.themesInstalled themes
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getThemesGet installed themes
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.TmpPassword b/data/corefork.telegram.org/type/account.TmpPassword new file mode 100644 index 0000000000..3ddf3d8a1b --- /dev/null +++ b/data/corefork.telegram.org/type/account.TmpPassword @@ -0,0 +1,162 @@ + + + + + Account.TmpPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.TmpPassword

+ +

Temporary password

+

+ +
+
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+
+---functions---
+
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.tmpPasswordTemporary payment password
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getTmpPasswordGet temporary payment password
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.WallPapers b/data/corefork.telegram.org/type/account.WallPapers new file mode 100644 index 0000000000..6e6b098ffa --- /dev/null +++ b/data/corefork.telegram.org/type/account.WallPapers @@ -0,0 +1,167 @@ + + + + + Account.WallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.WallPapers

+ +

Wallpapers

+

+ +
+
account.wallPapersNotModified#1c199183 = account.WallPapers;
+account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+
+---functions---
+
+account.getWallPapers#7967d36 hash:long = account.WallPapers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
account.wallPapersNotModifiedNo new wallpapers were found
account.wallPapersInstalled wallpapers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getWallPapersReturns a list of available wallpapers.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.WebAuthorizations b/data/corefork.telegram.org/type/account.WebAuthorizations new file mode 100644 index 0000000000..6ab38cf2dc --- /dev/null +++ b/data/corefork.telegram.org/type/account.WebAuthorizations @@ -0,0 +1,162 @@ + + + + + Account.WebAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.WebAuthorizations

+ +

Web authorizations

+

+ +
+
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
+
+---functions---
+
+account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.webAuthorizationsWeb authorizations
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getWebAuthorizationsGet web login widget authorizations
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.Authorization b/data/corefork.telegram.org/type/auth.Authorization new file mode 100644 index 0000000000..0931f4f714 --- /dev/null +++ b/data/corefork.telegram.org/type/auth.Authorization @@ -0,0 +1,192 @@ + + + + + auth.Authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.Authorization

+ +

Oject contains info on user authorization.

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+
+---functions---
+
+auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;
+auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
+auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
+auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;
+auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.authorizationContains user authorization info.
auth.authorizationSignUpRequiredAn account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
auth.signUpRegisters a validated phone number in the system.
auth.signInSigns in a user with a validated phone number.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.checkPasswordTry logging to an account protected by a 2FA password.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.CheckedPhone b/data/corefork.telegram.org/type/auth.CheckedPhone new file mode 100644 index 0000000000..248d3127cf --- /dev/null +++ b/data/corefork.telegram.org/type/auth.CheckedPhone @@ -0,0 +1,128 @@ + + + + + Auth.CheckedPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

Auth.CheckedPhone

+ +

Checked phone

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.CodeType b/data/corefork.telegram.org/type/auth.CodeType new file mode 100644 index 0000000000..d345b6e070 --- /dev/null +++ b/data/corefork.telegram.org/type/auth.CodeType @@ -0,0 +1,154 @@ + + + + + auth.CodeType + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.CodeType

+ +

Type of verification code that will be sent next if you call the resendCode method

+

+ +
+
auth.codeTypeSms#72a3158c = auth.CodeType;
+auth.codeTypeCall#741cd3e3 = auth.CodeType;
+auth.codeTypeFlashCall#226ccefb = auth.CodeType;
+auth.codeTypeMissedCall#d61ad6ee = auth.CodeType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.codeTypeSmsType of verification code that will be sent next if you call the resendCode method: SMS code
auth.codeTypeCallType of verification code that will be sent next if you call the resendCode method: SMS code
auth.codeTypeFlashCallType of verification code that will be sent next if you call the resendCode method: SMS code
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.ExportedAuthorization b/data/corefork.telegram.org/type/auth.ExportedAuthorization new file mode 100644 index 0000000000..6289baac09 --- /dev/null +++ b/data/corefork.telegram.org/type/auth.ExportedAuthorization @@ -0,0 +1,162 @@ + + + + + Auth.ExportedAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

Auth.ExportedAuthorization

+ +

Exported authorization

+

+ +
+
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
+
+---functions---
+
+auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
auth.exportedAuthorizationData for copying of authorization between data centres.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.LoggedOut b/data/corefork.telegram.org/type/auth.LoggedOut new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/auth.LoggedOut @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.LoginToken b/data/corefork.telegram.org/type/auth.LoginToken new file mode 100644 index 0000000000..e8e54f3aad --- /dev/null +++ b/data/corefork.telegram.org/type/auth.LoginToken @@ -0,0 +1,177 @@ + + + + + auth.LoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.LoginToken

+ +

Login token (for QR code login)

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+
+---functions---
+
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.loginTokenLogin token (for QR code login)
auth.loginTokenMigrateToRepeat the query to the specified DC
auth.loginTokenSuccessLogin via token (QR code) succeded!
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
auth.exportLoginTokenExport login token (for login via QR code)
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.PasswordRecovery b/data/corefork.telegram.org/type/auth.PasswordRecovery new file mode 100644 index 0000000000..e26e9f41d4 --- /dev/null +++ b/data/corefork.telegram.org/type/auth.PasswordRecovery @@ -0,0 +1,165 @@ + + + + + auth.PasswordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.PasswordRecovery

+ +

Recovery info of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+
+---functions---
+
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
auth.passwordRecoveryRecovery info of a 2FA password, only for accounts with a recovery email configured.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.SentCode b/data/corefork.telegram.org/type/auth.SentCode new file mode 100644 index 0000000000..815f143317 --- /dev/null +++ b/data/corefork.telegram.org/type/auth.SentCode @@ -0,0 +1,183 @@ + + + + + auth.SentCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.SentCode

+ +

Contains info on a confirmation code message sent via SMS, phone call or Telegram.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+
+---functions---
+
+auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
+
+account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;
+account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
auth.sentCodeContains info about a sent verification code.
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
auth.sendCodeSend the verification code for login
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.SentCodeType b/data/corefork.telegram.org/type/auth.SentCodeType new file mode 100644 index 0000000000..8878b72279 --- /dev/null +++ b/data/corefork.telegram.org/type/auth.SentCodeType @@ -0,0 +1,159 @@ + + + + + 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;
+auth.sentCodeTypeMissedCall#82006484 prefix:string length:int = 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/bytes.html b/data/corefork.telegram.org/type/bytes.html new file mode 100644 index 0000000000..ab59a32b8c --- /dev/null +++ b/data/corefork.telegram.org/type/bytes.html @@ -0,0 +1,125 @@ + + + + + bytes + + + + + + + + + + + + + +
+ +
+
+
+ +

bytes

+ +

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

+

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

+

Related pages

+

string

+

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

+

Further details on basic types»

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/channels.AdminLogResults b/data/corefork.telegram.org/type/channels.AdminLogResults new file mode 100644 index 0000000000..38f926b7ab --- /dev/null +++ b/data/corefork.telegram.org/type/channels.AdminLogResults @@ -0,0 +1,162 @@ + + + + + Channels.AdminLogResults + + + + + + + + + + + + + +
+ +
+
+
+ +

Channels.AdminLogResults

+ +

Admin log events

+

+ +
+
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+
+---functions---
+
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channels.adminLogResultsAdmin log events
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getAdminLogGet the admin log of a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/channels.ChannelParticipant b/data/corefork.telegram.org/type/channels.ChannelParticipant new file mode 100644 index 0000000000..fa0878a667 --- /dev/null +++ b/data/corefork.telegram.org/type/channels.ChannelParticipant @@ -0,0 +1,162 @@ + + + + + Channels.ChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

Channels.ChannelParticipant

+ +

Channel participant

+

+ +
+
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+
+---functions---
+
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channels.channelParticipantRepresents a channel participant
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getParticipantGet info about a channel/supergroup participant
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/channels.ChannelParticipants b/data/corefork.telegram.org/type/channels.ChannelParticipants new file mode 100644 index 0000000000..463d5953f2 --- /dev/null +++ b/data/corefork.telegram.org/type/channels.ChannelParticipants @@ -0,0 +1,167 @@ + + + + + Channels.ChannelParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

Channels.ChannelParticipants

+ +

Channel/supergroup participants

+

+ +
+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
+
+---functions---
+
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
channels.channelParticipantsRepresents multiple channel participants
channels.channelParticipantsNotModifiedNo new participant info could be found
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getParticipantsGet the participants of a channel
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/channels.SendAsPeers b/data/corefork.telegram.org/type/channels.SendAsPeers new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/channels.SendAsPeers @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.Blocked b/data/corefork.telegram.org/type/contacts.Blocked new file mode 100644 index 0000000000..15317aef2e --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.Blocked @@ -0,0 +1,167 @@ + + + + + contacts.Blocked + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.Blocked

+ +

Info on users from the current user's black list.

+

+ +
+
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+
+---functions---
+
+contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
contacts.blockedFull list of blocked users.
contacts.blockedSliceIncomplete list of blocked users.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.getBlockedReturns the list of blocked users.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.Contacts b/data/corefork.telegram.org/type/contacts.Contacts new file mode 100644 index 0000000000..5f0b131349 --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.Contacts @@ -0,0 +1,167 @@ + + + + + contacts.Contacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.Contacts

+ +

Info on the current user's contact list.

+

+ +
+
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
+contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
+
+---functions---
+
+contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
contacts.contactsNotModifiedContact list on the server is the same as the list on the client.
contacts.contactsThe current user's contact list and info on users.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.getContactsReturns the current user's contact list.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.Found b/data/corefork.telegram.org/type/contacts.Found new file mode 100644 index 0000000000..6896001274 --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.Found @@ -0,0 +1,162 @@ + + + + + contacts.Found + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.Found

+ +

Object contains info on users found by name substring and auxiliary data.

+

+ +
+
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
+
+---functions---
+
+contacts.search#11f812d8 q:string limit:int = contacts.Found;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contacts.foundUsers found by name substring and auxiliary data.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.searchReturns users found by username substring.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.ImportedContacts b/data/corefork.telegram.org/type/contacts.ImportedContacts new file mode 100644 index 0000000000..d73467e889 --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.ImportedContacts @@ -0,0 +1,162 @@ + + + + + contacts.ImportedContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.ImportedContacts

+ +

Object contains info on succesfully imported contacts.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+
+---functions---
+
+contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contacts.importedContactsInfo on succesfully imported contacts.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.Link b/data/corefork.telegram.org/type/contacts.Link new file mode 100644 index 0000000000..575cc9c90e --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.Link @@ -0,0 +1,128 @@ + + + + + contacts.Link + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.Link

+ +

Object describes the connection between a certain user and the current authorized user.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.ResolvedPeer b/data/corefork.telegram.org/type/contacts.ResolvedPeer new file mode 100644 index 0000000000..86c1ab281a --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.ResolvedPeer @@ -0,0 +1,162 @@ + + + + + Contacts.ResolvedPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

Contacts.ResolvedPeer

+ +

Peer returned after resolving a @username

+

+ +
+
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
+
+---functions---
+
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contacts.resolvedPeerResolved peer
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.resolveUsernameResolve a @username to get peer info
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.TopPeers b/data/corefork.telegram.org/type/contacts.TopPeers new file mode 100644 index 0000000000..c631697e5d --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.TopPeers @@ -0,0 +1,172 @@ + + + + + Contacts.TopPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

Contacts.TopPeers

+ +

Top peers

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+
+---functions---
+
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
contacts.topPeersNotModifiedTop peer info hasn't changed
contacts.topPeersTop peers
contacts.topPeersDisabledTop peers disabled
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.getTopPeersGet most used peers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/double.html b/data/corefork.telegram.org/type/double.html new file mode 100644 index 0000000000..08d7f11dc1 --- /dev/null +++ b/data/corefork.telegram.org/type/double.html @@ -0,0 +1,118 @@ + + + + + double + + + + + + + + + + + + + +
+ +
+
+
+ +

double

+ +

A basic bare type, values of which correspond two-element sequences containing 64-bit real numbers in a standard double format.

+

More on basic types»

+

Related pages

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.AppUpdate b/data/corefork.telegram.org/type/help.AppUpdate new file mode 100644 index 0000000000..c88167eb86 --- /dev/null +++ b/data/corefork.telegram.org/type/help.AppUpdate @@ -0,0 +1,167 @@ + + + + + help.AppUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.AppUpdate

+ +

Contains info on app update availability.

+

+ +
+
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
+help.noAppUpdate#c45a6536 = help.AppUpdate;
+
+---functions---
+
+help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.appUpdateAn update is available for the application.
help.noAppUpdateNo updates are available for the application.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getAppUpdateReturns information on update availability for the current application.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.CountriesList b/data/corefork.telegram.org/type/help.CountriesList new file mode 100644 index 0000000000..9adf6d57ac --- /dev/null +++ b/data/corefork.telegram.org/type/help.CountriesList @@ -0,0 +1,167 @@ + + + + + help.CountriesList + + + + + + + + + + + + + +
+ +
+
+
+ +

help.CountriesList

+ +

Name, ISO code, localized name and phone codes/patterns of all available countries

+

+ +
+
help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+
+---functions---
+
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.countriesListNotModifiedThe country list has not changed
help.countriesListName, ISO code, localized name and phone codes/patterns of all available countries
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.CountryCode b/data/corefork.telegram.org/type/help.CountryCode new file mode 100644 index 0000000000..2d98105ee5 --- /dev/null +++ b/data/corefork.telegram.org/type/help.CountryCode @@ -0,0 +1,143 @@ + + + + + help.CountryCode + + + + + + + + + + + + + +
+ +
+
+
+ +

help.CountryCode

+ +

Country code and phone number pattern of a specific country

+

+ +
+
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.countryCodeCountry code and phone number pattern of a specific country
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.DeepLinkInfo b/data/corefork.telegram.org/type/help.DeepLinkInfo new file mode 100644 index 0000000000..1d4f2cf9e8 --- /dev/null +++ b/data/corefork.telegram.org/type/help.DeepLinkInfo @@ -0,0 +1,167 @@ + + + + + Help.DeepLinkInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.DeepLinkInfo

+ +

Contains information about a tg:// deep link

+

+ +
+
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
+help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
+
+---functions---
+
+help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.deepLinkInfoEmptyDeep link info empty
help.deepLinkInfoDeep linking info
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getDeepLinkInfoGet info about a t.me link
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.InviteText b/data/corefork.telegram.org/type/help.InviteText new file mode 100644 index 0000000000..06f0767634 --- /dev/null +++ b/data/corefork.telegram.org/type/help.InviteText @@ -0,0 +1,162 @@ + + + + + help.InviteText + + + + + + + + + + + + + +
+ +
+
+
+ +

help.InviteText

+ +

Object contains info on the text of a message with an invitation.

+

+ +
+
help.inviteText#18cb9f78 message:string = help.InviteText;
+
+---functions---
+
+help.getInviteText#4d392343 = help.InviteText;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.inviteTextText of a text message with an invitation to install application.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getInviteTextReturns text of a text message with an invitation.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.PromoData b/data/corefork.telegram.org/type/help.PromoData new file mode 100644 index 0000000000..b0005a46f4 --- /dev/null +++ b/data/corefork.telegram.org/type/help.PromoData @@ -0,0 +1,167 @@ + + + + + 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 new file mode 100644 index 0000000000..33d90f992c --- /dev/null +++ b/data/corefork.telegram.org/type/help.ProxyData @@ -0,0 +1,130 @@ + + + + + Help.ProxyData + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.ProxyData

+ +

Info about an MTProxy

+

+ +
+

+

Related pages

+

MTProto transports

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.RecentMeUrls b/data/corefork.telegram.org/type/help.RecentMeUrls new file mode 100644 index 0000000000..1ae70feb2b --- /dev/null +++ b/data/corefork.telegram.org/type/help.RecentMeUrls @@ -0,0 +1,162 @@ + + + + + Help.RecentMeUrls + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.RecentMeUrls

+ +

Recent t.me URLs

+

+ +
+
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
+
+---functions---
+
+help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.recentMeUrlsRecent t.me URLs
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getRecentMeUrlsGet recently used t.me links
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.Support b/data/corefork.telegram.org/type/help.Support new file mode 100644 index 0000000000..a5c3412cb4 --- /dev/null +++ b/data/corefork.telegram.org/type/help.Support @@ -0,0 +1,162 @@ + + + + + help.Support + + + + + + + + + + + + + +
+ +
+
+
+ +

help.Support

+ +

Info about the support user, relevant to the current user.

+

+ +
+
help.support#17c6b5f6 phone_number:string user:User = help.Support;
+
+---functions---
+
+help.getSupport#9cdf08cd = help.Support;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.supportInfo on support user.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getSupportReturns the support user for the 'ask a question' feature.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.SupportName b/data/corefork.telegram.org/type/help.SupportName new file mode 100644 index 0000000000..0048211005 --- /dev/null +++ b/data/corefork.telegram.org/type/help.SupportName @@ -0,0 +1,162 @@ + + + + + Help.SupportName + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.SupportName

+ +

Get localized name for support user

+

+ +
+
help.supportName#8c05f1c9 name:string = help.SupportName;
+
+---functions---
+
+help.getSupportName#d360e72c = help.SupportName;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.supportNameLocalized name for telegram support
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getSupportNameGet localized name of the telegram support user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.TermsOfService b/data/corefork.telegram.org/type/help.TermsOfService new file mode 100644 index 0000000000..59622a1a7d --- /dev/null +++ b/data/corefork.telegram.org/type/help.TermsOfService @@ -0,0 +1,143 @@ + + + + + help.TermsOfService + + + + + + + + + + + + + +
+ +
+
+
+ +

help.TermsOfService

+ +

Contains info about the latest telegram Terms Of Service.

+

+ +
+
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.termsOfServiceInfo about the latest telegram Terms Of Service
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.TermsOfServiceUpdate b/data/corefork.telegram.org/type/help.TermsOfServiceUpdate new file mode 100644 index 0000000000..5fdc03e1ed --- /dev/null +++ b/data/corefork.telegram.org/type/help.TermsOfServiceUpdate @@ -0,0 +1,167 @@ + + + + + Help.TermsOfServiceUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.TermsOfServiceUpdate

+ +

Update of Telegram's terms of service

+

+ +
+
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+
+---functions---
+
+help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.termsOfServiceUpdateEmptyNo changes were made to telegram's terms of service
help.termsOfServiceUpdateInfo about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.UserInfo b/data/corefork.telegram.org/type/help.UserInfo new file mode 100644 index 0000000000..fc78e6b003 --- /dev/null +++ b/data/corefork.telegram.org/type/help.UserInfo @@ -0,0 +1,172 @@ + + + + + Help.UserInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

Help.UserInfo

+ +

User info

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+
+---functions---
+
+help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;
+help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.userInfoEmptyInternal use
help.userInfoInternal use
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
help.getUserInfoInternal use
help.editUserInfoInternal use
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/int.html b/data/corefork.telegram.org/type/int.html new file mode 100644 index 0000000000..33e5c81299 --- /dev/null +++ b/data/corefork.telegram.org/type/int.html @@ -0,0 +1,118 @@ + + + + + int + + + + + + + + + + + + + +
+ +
+
+
+ +

int

+ +

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

+

More on basic types »

+

Related pages

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/long.html b/data/corefork.telegram.org/type/long.html new file mode 100644 index 0000000000..f36446d0dc --- /dev/null +++ b/data/corefork.telegram.org/type/long.html @@ -0,0 +1,118 @@ + + + + + long + + + + + + + + + + + + + +
+ +
+
+
+ +

long

+ +

A basic bare type, elements of which correspond to two-element sequences, representing 64-bit signed numbers (little-endian).

+

More on basic types »

+

Related pages

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.AffectedFoundMessages b/data/corefork.telegram.org/type/messages.AffectedFoundMessages new file mode 100644 index 0000000000..5d50fd2bee --- /dev/null +++ b/data/corefork.telegram.org/type/messages.AffectedFoundMessages @@ -0,0 +1,162 @@ + + + + + messages.AffectedFoundMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.AffectedFoundMessages

+ +

Messages found and affected by changes

+

+ +
+
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
+
+---functions---
+
+messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.affectedFoundMessagesMessages found and affected by changes
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.deletePhoneCallHistoryDelete the phone call history with a user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.AffectedHistory b/data/corefork.telegram.org/type/messages.AffectedHistory new file mode 100644 index 0000000000..65743b3d4a --- /dev/null +++ b/data/corefork.telegram.org/type/messages.AffectedHistory @@ -0,0 +1,179 @@ + + + + + messages.AffectedHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.AffectedHistory

+ +

Object contains info on affected part of communication history with the user or in a chat.

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+
+---functions---
+
+messages.deleteHistory#b08f922a flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int min_date:flags.2?int max_date:flags.3?int = messages.AffectedHistory;
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
+messages.readReactions#82e251d7 peer:InputPeer = messages.AffectedHistory;
+
+channels.deleteParticipantHistory#367544db channel:InputChannel participant:InputPeer = messages.AffectedHistory;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.affectedHistoryAffected part of communication history with the user or in a chat.
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.deleteHistoryDeletes communication history.
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
messages.readMentionsMark mentions as read
messages.unpinAllMessagesUnpin all pinned messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.AffectedMessages b/data/corefork.telegram.org/type/messages.AffectedMessages new file mode 100644 index 0000000000..b57102285a --- /dev/null +++ b/data/corefork.telegram.org/type/messages.AffectedMessages @@ -0,0 +1,178 @@ + + + + + Messages.AffectedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.AffectedMessages

+ +

Messages affected by changes

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+
+---functions---
+
+messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;
+messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;
+messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;
+
+channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.affectedMessagesEvents affected by operation
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.readHistoryMarks message history as read.
messages.deleteMessagesDeletes messages by their identifiers.
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
channels.deleteMessagesDelete messages in a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.AllStickers b/data/corefork.telegram.org/type/messages.AllStickers new file mode 100644 index 0000000000..87986de481 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.AllStickers @@ -0,0 +1,172 @@ + + + + + Messages.AllStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.AllStickers

+ +

All stickers

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+
+---functions---
+
+messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;
+messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.allStickersNotModifiedInfo about all installed stickers hasn't changed
messages.allStickersInfo about all installed stickers
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getAllStickersGet all installed stickers
messages.getMaskStickersGet installed mask stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ArchivedStickers b/data/corefork.telegram.org/type/messages.ArchivedStickers new file mode 100644 index 0000000000..dd62481b43 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ArchivedStickers @@ -0,0 +1,162 @@ + + + + + Messages.ArchivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.ArchivedStickers

+ +

Archived stickers

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
+
+---functions---
+
+messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.archivedStickersArchived stickersets
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getArchivedStickersGet all archived stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.AvailableReactions b/data/corefork.telegram.org/type/messages.AvailableReactions new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.AvailableReactions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.BotCallbackAnswer b/data/corefork.telegram.org/type/messages.BotCallbackAnswer new file mode 100644 index 0000000000..464a1f94d1 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.BotCallbackAnswer @@ -0,0 +1,162 @@ + + + + + Messages.BotCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.BotCallbackAnswer

+ +

Callback answer of bot

+

+ +
+
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+
+---functions---
+
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.botCallbackAnswerCallback answer sent by the bot in response to a button press
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.BotResults b/data/corefork.telegram.org/type/messages.BotResults new file mode 100644 index 0000000000..37323b356a --- /dev/null +++ b/data/corefork.telegram.org/type/messages.BotResults @@ -0,0 +1,162 @@ + + + + + messages.BotResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.BotResults

+ +

Result of a query to an inline bot

+

+ +
+
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
+
+---functions---
+
+messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.botResultsResult of a query to an inline bot
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getInlineBotResultsQuery an inline bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ChatAdminsWithInvites b/data/corefork.telegram.org/type/messages.ChatAdminsWithInvites new file mode 100644 index 0000000000..f9392f4787 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ChatAdminsWithInvites @@ -0,0 +1,162 @@ + + + + + messages.ChatAdminsWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ChatAdminsWithInvites

+ +

Info about chat invites generated by admins.

+

+ +
+
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
+
+---functions---
+
+messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.chatAdminsWithInvitesInfo about chat invites generated by admins.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getAdminsWithInvitesGet info about chat invites generated by admins.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ChatFull b/data/corefork.telegram.org/type/messages.ChatFull new file mode 100644 index 0000000000..7db1b41482 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ChatFull @@ -0,0 +1,168 @@ + + + + + messages.ChatFull + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ChatFull

+ +

Object contains extended info on chat with auxiliary data.

+

+ +
+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
+
+---functions---
+
+messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;
+
+channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.chatFullExtended info on chat and auxiliary data.
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getFullChatReturns full chat info according to its ID.
channels.getFullChannelGet full info about a channel
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ChatInviteImporters b/data/corefork.telegram.org/type/messages.ChatInviteImporters new file mode 100644 index 0000000000..19789ed16c --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ChatInviteImporters @@ -0,0 +1,162 @@ + + + + + messages.ChatInviteImporters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ChatInviteImporters

+ +

List of users that imported a chat invitation link.

+

+ +
+
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+
+---functions---
+
+messages.getChatInviteImporters#df04dd4e flags:# requested:flags.0?true peer:InputPeer link:flags.1?string q:flags.2?string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.chatInviteImportersInfo about the users that joined the chat using a specific chat invite
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.Chats b/data/corefork.telegram.org/type/messages.Chats new file mode 100644 index 0000000000..bd30c3d4bc --- /dev/null +++ b/data/corefork.telegram.org/type/messages.Chats @@ -0,0 +1,198 @@ + + + + + messages.Chats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.Chats

+ +

Object contains list of chats with auxiliary data.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+
+---functions---
+
+messages.getChats#49e9528f id:Vector<long> = messages.Chats;
+messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;
+messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;
+
+channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;
+channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;
+channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.chatsList of chats with auxiliary data.
messages.chatsSlicePartial list of chats, more would have to be fetched with pagination
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getChatsReturns chat basic info on their IDs.
channels.getChannelsGet info about channels/supergroups
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
messages.getCommonChatsGet chats in common with a user
messages.getAllChatsGet all chats, channels and supergroups
channels.getLeftChannelsGet a list of channels/supergroups we left
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer b/data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer new file mode 100644 index 0000000000..93d7183d7c --- /dev/null +++ b/data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer @@ -0,0 +1,165 @@ + + + + + messages.CheckedHistoryImportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.CheckedHistoryImportPeer

+ +

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

+

+ +
+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+
+---functions---
+
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.checkedHistoryImportPeerContains a confirmation text to be shown to the user, upon importing chat history.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat.

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.DhConfig b/data/corefork.telegram.org/type/messages.DhConfig new file mode 100644 index 0000000000..229f5de2ab --- /dev/null +++ b/data/corefork.telegram.org/type/messages.DhConfig @@ -0,0 +1,167 @@ + + + + + Messages.DhConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.DhConfig

+ +

Contains info on cofiguring parameters for key generation by Diffie-Hellman protocol.

+

+ +
+
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
+messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
+
+---functions---
+
+messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.dhConfigNotModifiedConfiguring parameters did not change.
messages.dhConfigNew set of configuring parameters.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.Dialogs b/data/corefork.telegram.org/type/messages.Dialogs new file mode 100644 index 0000000000..bb138bf7ab --- /dev/null +++ b/data/corefork.telegram.org/type/messages.Dialogs @@ -0,0 +1,172 @@ + + + + + messages.Dialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.Dialogs

+ +

Object contains a list of chats with messages and auxiliary data.

+

+ +
+
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
+
+---functions---
+
+messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.dialogsFull list of chats with messages and auxiliary data.
messages.dialogsSliceIncomplete list of dialogs with messages and auxiliary data.
messages.dialogsNotModifiedDialogs haven't changed
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getDialogsReturns the current user dialog list.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.DiscussionMessage b/data/corefork.telegram.org/type/messages.DiscussionMessage new file mode 100644 index 0000000000..e6530fe9a1 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.DiscussionMessage @@ -0,0 +1,162 @@ + + + + + messages.DiscussionMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.DiscussionMessage

+ +

Info about a message thread

+

+ +
+
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
+
+---functions---
+
+messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.discussionMessageInformation about a message thread
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ExportedChatInvite b/data/corefork.telegram.org/type/messages.ExportedChatInvite new file mode 100644 index 0000000000..c68920b356 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ExportedChatInvite @@ -0,0 +1,172 @@ + + + + + messages.ExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ExportedChatInvite

+ +

Contains info about a chat invite, and eventually a pointer to the newest chat invite.

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+
+---functions---
+
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
+messages.editExportedChatInvite#bdca2f75 flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int request_needed:flags.3?Bool title:flags.4?string = messages.ExportedChatInvite;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.exportedChatInviteInfo about a chat invite
messages.exportedChatInviteReplacedThe specified chat invite was replaced with another one
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ExportedChatInvites b/data/corefork.telegram.org/type/messages.ExportedChatInvites new file mode 100644 index 0000000000..732dc8ed5d --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ExportedChatInvites @@ -0,0 +1,162 @@ + + + + + messages.ExportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ExportedChatInvites

+ +

Info about chat invites exported by a certain admin.

+

+ +
+
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
+
+---functions---
+
+messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.exportedChatInvitesInfo about chat invites exported by a certain admin.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.FavedStickers b/data/corefork.telegram.org/type/messages.FavedStickers new file mode 100644 index 0000000000..af56e5d7ca --- /dev/null +++ b/data/corefork.telegram.org/type/messages.FavedStickers @@ -0,0 +1,167 @@ + + + + + Messages.FavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FavedStickers

+ +

Favorited stickers

+

+ +
+
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+
+---functions---
+
+messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.favedStickersNotModifiedNo new favorited stickers were found
messages.favedStickersFavorited stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getFavedStickersGet faved stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.FeaturedStickers b/data/corefork.telegram.org/type/messages.FeaturedStickers new file mode 100644 index 0000000000..10ef06e535 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.FeaturedStickers @@ -0,0 +1,172 @@ + + + + + Messages.FeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FeaturedStickers

+ +

Featured stickers

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+
+---functions---
+
+messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;
+messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.featuredStickersNotModifiedFeatured stickers haven't changed
messages.featuredStickersFeatured stickersets
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getFeaturedStickersGet featured stickers
messages.getOldFeaturedStickersOld method for fetching featured sticker
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.FoundGifs b/data/corefork.telegram.org/type/messages.FoundGifs new file mode 100644 index 0000000000..ef1a7b116d --- /dev/null +++ b/data/corefork.telegram.org/type/messages.FoundGifs @@ -0,0 +1,128 @@ + + + + + Messages.FoundGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FoundGifs

+ +

Found GIFs

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.FoundStickerSets b/data/corefork.telegram.org/type/messages.FoundStickerSets new file mode 100644 index 0000000000..a96d888700 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.FoundStickerSets @@ -0,0 +1,167 @@ + + + + + Messages.FoundStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FoundStickerSets

+ +

Found stickersets

+

+ +
+
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
+messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
+
+---functions---
+
+messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.foundStickerSetsNotModifiedNo further results were found
messages.foundStickerSetsFound stickersets
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.searchStickerSetsSearch for stickersets
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.HighScores b/data/corefork.telegram.org/type/messages.HighScores new file mode 100644 index 0000000000..cdcd991cfb --- /dev/null +++ b/data/corefork.telegram.org/type/messages.HighScores @@ -0,0 +1,167 @@ + + + + + Messages.HighScores + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.HighScores

+ +

High scores (in games)

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+
+---functions---
+
+messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.highScoresHighscores in a game
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.HistoryImport b/data/corefork.telegram.org/type/messages.HistoryImport new file mode 100644 index 0000000000..75962a58f4 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.HistoryImport @@ -0,0 +1,165 @@ + + + + + messages.HistoryImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.HistoryImport

+ +

Identifier of a history import session, click here for more info ».

+

+ +
+
messages.historyImport#1662af0b id:long = messages.HistoryImport;
+
+---functions---
+
+messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.historyImportID of a specific chat import session
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.initHistoryImportImport chat history from a foreign chat app into a specific Telegram chat.
Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.HistoryImportParsed b/data/corefork.telegram.org/type/messages.HistoryImportParsed new file mode 100644 index 0000000000..a86d9740bd --- /dev/null +++ b/data/corefork.telegram.org/type/messages.HistoryImportParsed @@ -0,0 +1,162 @@ + + + + + messages.HistoryImportParsed + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.HistoryImportParsed

+ +

Contains information about a chat export file, generated by a foreign chat app.

+

+ +
+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+
+---functions---
+
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.historyImportParsedContains information about a chat export file, generated by a foreign chat app. If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.checkHistoryImportObtains information about a chat export file, generated by a foreign chat app.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.InactiveChats b/data/corefork.telegram.org/type/messages.InactiveChats new file mode 100644 index 0000000000..3fe00cf7c6 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.InactiveChats @@ -0,0 +1,162 @@ + + + + + messages.InactiveChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.InactiveChats

+ +

Inactive chat list

+

+ +
+
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
+
+---functions---
+
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.inactiveChatsInactive chat list
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getInactiveChannelsGet inactive channels and supergroups
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.MessageEditData b/data/corefork.telegram.org/type/messages.MessageEditData new file mode 100644 index 0000000000..e82896bf1b --- /dev/null +++ b/data/corefork.telegram.org/type/messages.MessageEditData @@ -0,0 +1,162 @@ + + + + + Messages.MessageEditData + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.MessageEditData

+ +

Message edit data for media

+

+ +
+
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
+
+---functions---
+
+messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.messageEditDataMessage edit data for media
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getMessageEditDataFind out if a media message's caption can be edited
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.MessageReactionsList b/data/corefork.telegram.org/type/messages.MessageReactionsList new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.MessageReactionsList @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.MessageViews b/data/corefork.telegram.org/type/messages.MessageViews new file mode 100644 index 0000000000..dd39a6a06e --- /dev/null +++ b/data/corefork.telegram.org/type/messages.MessageViews @@ -0,0 +1,162 @@ + + + + + messages.MessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.MessageViews

+ +

View, forward counter + info about replies

+

+ +
+
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
+
+---functions---
+
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.messageViewsView, forward counter + info about replies
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.Messages b/data/corefork.telegram.org/type/messages.Messages new file mode 100644 index 0000000000..cac1bab863 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.Messages @@ -0,0 +1,230 @@ + + + + + messages.Messages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.Messages

+ +

Object contains infor on list of messages with auxiliary data.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+
+---functions---
+
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
+messages.getHistory#4423e6c5 peer:InputPeer offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
+messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
+messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
+messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
+messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.getUnreadReactions#e85bae1a peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
+
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
+
+stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.messagesFull list of messages with auxilary data.
messages.messagesSliceIncomplete list of messages and auxiliary data.
messages.channelMessagesChannel messages
messages.messagesNotModifiedNo new messages matching the query were found
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getMessagesReturns the list of messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.searchGets back found messages
channels.getMessagesGet channel/supergroup messages
messages.searchGlobalSearch for messages and peers globally
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.getRecentLocationsGet live location history of a certain user
messages.getScheduledHistoryGet scheduled messages
messages.getScheduledMessagesGet scheduled messages
messages.getRepliesGet messages in a reply thread
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.PeerDialogs b/data/corefork.telegram.org/type/messages.PeerDialogs new file mode 100644 index 0000000000..e1a1cf7e95 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.PeerDialogs @@ -0,0 +1,167 @@ + + + + + Messages.PeerDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.PeerDialogs

+ +

List of dialogs

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+
+---functions---
+
+messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
+messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.peerDialogsDialog info of multiple peers
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.RecentStickers b/data/corefork.telegram.org/type/messages.RecentStickers new file mode 100644 index 0000000000..7b2dc810a1 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.RecentStickers @@ -0,0 +1,167 @@ + + + + + Messages.RecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.RecentStickers

+ +

Recent stickers

+

+ +
+
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
+messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
+
+---functions---
+
+messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.recentStickersNotModifiedNo new recent sticker was found
messages.recentStickersRecently used stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getRecentStickersGet recent stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SavedGifs b/data/corefork.telegram.org/type/messages.SavedGifs new file mode 100644 index 0000000000..c8f73d1039 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SavedGifs @@ -0,0 +1,167 @@ + + + + + Messages.SavedGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.SavedGifs

+ +

Saved GIFs

+

+ +
+
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
+messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
+
+---functions---
+
+messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.savedGifsNotModifiedNo new saved gifs were found
messages.savedGifsSaved gifs
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getSavedGifsGet saved GIFs
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SearchCounter b/data/corefork.telegram.org/type/messages.SearchCounter new file mode 100644 index 0000000000..089499eefa --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SearchCounter @@ -0,0 +1,143 @@ + + + + + Messages.SearchCounter + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.SearchCounter

+ +

Number of results that would be returned by a search

+

+ +
+
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.searchCounterIndicates how many results would be found by a messages.search call with the same parameters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SearchResultsCalendar b/data/corefork.telegram.org/type/messages.SearchResultsCalendar new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SearchResultsCalendar @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SearchResultsPositions b/data/corefork.telegram.org/type/messages.SearchResultsPositions new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SearchResultsPositions @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SentEncryptedMessage b/data/corefork.telegram.org/type/messages.SentEncryptedMessage new file mode 100644 index 0000000000..85c28918d9 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SentEncryptedMessage @@ -0,0 +1,177 @@ + + + + + Messages.SentEncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.SentEncryptedMessage

+ +

Contains info on message sent to an encrypted chat.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+
+---functions---
+
+messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
+messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.sentEncryptedMessageMessage without file attachemts sent to an encrypted file.
messages.sentEncryptedFileMessage with a file enclosure sent to a protected chat
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SentMessage b/data/corefork.telegram.org/type/messages.SentMessage new file mode 100644 index 0000000000..a49633e9f8 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SentMessage @@ -0,0 +1,128 @@ + + + + + messages.SentMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.SentMessage

+ +

Info on a successfully sent message.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SponsoredMessages b/data/corefork.telegram.org/type/messages.SponsoredMessages new file mode 100644 index 0000000000..23c3f7563e --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SponsoredMessages @@ -0,0 +1,166 @@ + + + + + messages.SponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.SponsoredMessages

+ +

A set of sponsored messages associated with a channel

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+
+---functions---
+
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.sponsoredMessagesA set of sponsored messages associated with a channel
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getSponsoredMessagesGet a list of sponsored messages
+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.StatedMessage b/data/corefork.telegram.org/type/messages.StatedMessage new file mode 100644 index 0000000000..bc78692d03 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.StatedMessage @@ -0,0 +1,128 @@ + + + + + messages.StatedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.StatedMessage

+ +

Object contains info on one message with auxiliary data and data on the current state of updates.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.StatedMessages b/data/corefork.telegram.org/type/messages.StatedMessages new file mode 100644 index 0000000000..575643f328 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.StatedMessages @@ -0,0 +1,128 @@ + + + + + messages.StatedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.StatedMessages

+ +

Object contains info on the list of messages with auxiliary data and data on current state of updates.

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.StickerSet b/data/corefork.telegram.org/type/messages.StickerSet new file mode 100644 index 0000000000..523a4749ca --- /dev/null +++ b/data/corefork.telegram.org/type/messages.StickerSet @@ -0,0 +1,189 @@ + + + + + Messages.StickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.StickerSet

+ +

Stickerset

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+messages.stickerSetNotModified#d3f924eb = messages.StickerSet;
+
+---functions---
+
+messages.getStickerSet#c8a0ec74 stickerset:InputStickerSet hash:int = messages.StickerSet;
+
+stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
+stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
+stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
+stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.stickerSetStickerset and stickers inside it
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getStickerSetGet info about a stickerset
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.setStickerSetThumbSet stickerset thumbnail
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.StickerSetInstallResult b/data/corefork.telegram.org/type/messages.StickerSetInstallResult new file mode 100644 index 0000000000..606ef618bd --- /dev/null +++ b/data/corefork.telegram.org/type/messages.StickerSetInstallResult @@ -0,0 +1,167 @@ + + + + + Messages.StickerSetInstallResult + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.StickerSetInstallResult

+ +

Result of stickerset installation process

+

+ +
+
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
+messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
+
+---functions---
+
+messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.stickerSetInstallResultSuccessThe stickerset was installed successfully
messages.stickerSetInstallResultArchiveThe stickerset was installed, but since there are too many stickersets some were archived
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.installStickerSetInstall a stickerset
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.Stickers b/data/corefork.telegram.org/type/messages.Stickers new file mode 100644 index 0000000000..3011eb2caf --- /dev/null +++ b/data/corefork.telegram.org/type/messages.Stickers @@ -0,0 +1,167 @@ + + + + + Messages.Stickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.Stickers

+ +

Stickers

+

+ +
+
messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
+
+---functions---
+
+messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.stickersNotModifiedNo new stickers were found for the given query
messages.stickersFound stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getStickersGet stickers by emoji
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.TranslatedText b/data/corefork.telegram.org/type/messages.TranslatedText new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.TranslatedText @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.VotesList b/data/corefork.telegram.org/type/messages.VotesList new file mode 100644 index 0000000000..d1c27d617a --- /dev/null +++ b/data/corefork.telegram.org/type/messages.VotesList @@ -0,0 +1,162 @@ + + + + + messages.VotesList + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.VotesList

+ +

How users voted in a poll

+

+ +
+
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
+
+---functions---
+
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.votesListHow users voted in a poll
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getPollVotesGet poll results for non-anonymous polls
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/payments.BankCardData b/data/corefork.telegram.org/type/payments.BankCardData new file mode 100644 index 0000000000..7b0adaf61a --- /dev/null +++ b/data/corefork.telegram.org/type/payments.BankCardData @@ -0,0 +1,162 @@ + + + + + payments.BankCardData + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.BankCardData

+ +

Credit card info, provided by the card's bank(s)

+

+ +
+
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
+
+---functions---
+
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.bankCardDataCredit card info, provided by the card's bank(s)
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getBankCardDataGet info about a credit card
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/payments.PaymentForm b/data/corefork.telegram.org/type/payments.PaymentForm new file mode 100644 index 0000000000..d748364e5e --- /dev/null +++ b/data/corefork.telegram.org/type/payments.PaymentForm @@ -0,0 +1,162 @@ + + + + + Payments.PaymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.PaymentForm

+ +

Payment form

+

+ +
+
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+
+---functions---
+
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.paymentFormPayment form
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getPaymentFormGet a payment form
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/payments.PaymentReceipt b/data/corefork.telegram.org/type/payments.PaymentReceipt new file mode 100644 index 0000000000..bd6d897f33 --- /dev/null +++ b/data/corefork.telegram.org/type/payments.PaymentReceipt @@ -0,0 +1,162 @@ + + + + + Payments.PaymentReceipt + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.PaymentReceipt

+ +

Payment receipt

+

+ +
+
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+
+---functions---
+
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.paymentReceiptReceipt
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getPaymentReceiptGet payment receipt
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/payments.PaymentResult b/data/corefork.telegram.org/type/payments.PaymentResult new file mode 100644 index 0000000000..6969d251f8 --- /dev/null +++ b/data/corefork.telegram.org/type/payments.PaymentResult @@ -0,0 +1,167 @@ + + + + + Payments.PaymentResult + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.PaymentResult

+ +

Payment result

+

+ +
+
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
+payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
+
+---functions---
+
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
payments.paymentResultPayment result
payments.paymentVerificationNeededPayment was not successful, additional verification is needed
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.sendPaymentFormSend compiled payment form
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/payments.SavedInfo b/data/corefork.telegram.org/type/payments.SavedInfo new file mode 100644 index 0000000000..8d52855b3d --- /dev/null +++ b/data/corefork.telegram.org/type/payments.SavedInfo @@ -0,0 +1,162 @@ + + + + + Payments.SavedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.SavedInfo

+ +

Saved payment info

+

+ +
+
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
+
+---functions---
+
+payments.getSavedInfo#227d824b = payments.SavedInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.savedInfoSaved server-side order information
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getSavedInfoGet saved payment information
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/payments.ValidatedRequestedInfo b/data/corefork.telegram.org/type/payments.ValidatedRequestedInfo new file mode 100644 index 0000000000..3b0d929437 --- /dev/null +++ b/data/corefork.telegram.org/type/payments.ValidatedRequestedInfo @@ -0,0 +1,162 @@ + + + + + Payments.ValidatedRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.ValidatedRequestedInfo

+ +

Validated requested info

+

+ +
+
payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
+
+---functions---
+
+payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.validatedRequestedInfoValidated user-provided info
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.validateRequestedInfoSubmit requested order information for validation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/phone.ExportedGroupCallInvite b/data/corefork.telegram.org/type/phone.ExportedGroupCallInvite new file mode 100644 index 0000000000..07a35e7144 --- /dev/null +++ b/data/corefork.telegram.org/type/phone.ExportedGroupCallInvite @@ -0,0 +1,162 @@ + + + + + phone.ExportedGroupCallInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.ExportedGroupCallInvite

+ +

An exported group call invitation.

+

+ +
+
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
+
+---functions---
+
+phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.exportedGroupCallInviteAn invite to a group call or livestream
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/phone.GroupCall b/data/corefork.telegram.org/type/phone.GroupCall new file mode 100644 index 0000000000..2c7be22317 --- /dev/null +++ b/data/corefork.telegram.org/type/phone.GroupCall @@ -0,0 +1,162 @@ + + + + + phone.GroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.GroupCall

+ +

Contains info about a group call, and partial info about its participants.

+

+ +
+
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
+
+---functions---
+
+phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.groupCallContains info about a group call, and partial info about its participants.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.getGroupCallGet info about a group call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/phone.GroupParticipants b/data/corefork.telegram.org/type/phone.GroupParticipants new file mode 100644 index 0000000000..2079e47a10 --- /dev/null +++ b/data/corefork.telegram.org/type/phone.GroupParticipants @@ -0,0 +1,162 @@ + + + + + phone.GroupParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.GroupParticipants

+ +

Info about the participants of a group call or livestream

+

+ +
+
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
+
+---functions---
+
+phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.groupParticipantsInfo about the participants of a group call or livestream
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.getGroupParticipantsGet group call participants
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/phone.JoinAsPeers b/data/corefork.telegram.org/type/phone.JoinAsPeers new file mode 100644 index 0000000000..f0976a02da --- /dev/null +++ b/data/corefork.telegram.org/type/phone.JoinAsPeers @@ -0,0 +1,162 @@ + + + + + phone.JoinAsPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.JoinAsPeers

+ +

A list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+

+ +
+
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+
+---functions---
+
+phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.joinAsPeersA list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.getGroupCallJoinAsGet a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/phone.PhoneCall b/data/corefork.telegram.org/type/phone.PhoneCall new file mode 100644 index 0000000000..220d820eb0 --- /dev/null +++ b/data/corefork.telegram.org/type/phone.PhoneCall @@ -0,0 +1,172 @@ + + + + + Phone.PhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

Phone.PhoneCall

+ +

Phone call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+
+---functions---
+
+phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.phoneCallA VoIP phone call
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
phone.requestCallStart a telegram phone call
phone.acceptCallAccept incoming call
phone.confirmCallComplete phone call E2E encryption key exchange »
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/photos.Photo b/data/corefork.telegram.org/type/photos.Photo new file mode 100644 index 0000000000..dde918e754 --- /dev/null +++ b/data/corefork.telegram.org/type/photos.Photo @@ -0,0 +1,167 @@ + + + + + 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/photos.Photos b/data/corefork.telegram.org/type/photos.Photos new file mode 100644 index 0000000000..21a5033b8e --- /dev/null +++ b/data/corefork.telegram.org/type/photos.Photos @@ -0,0 +1,167 @@ + + + + + photos.Photos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.Photos

+ +

Object contains list of photos with auxiliary data.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+
+---functions---
+
+photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
photos.photosFull list of photos with auxiliary data.
photos.photosSliceIncomplete list of photos with auxiliary data.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
photos.getUserPhotosReturns the list of user photos.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/stats.BroadcastStats b/data/corefork.telegram.org/type/stats.BroadcastStats new file mode 100644 index 0000000000..36a606ba04 --- /dev/null +++ b/data/corefork.telegram.org/type/stats.BroadcastStats @@ -0,0 +1,162 @@ + + + + + Stats.BroadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

Stats.BroadcastStats

+ +

Channel statistics

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+
+---functions---
+
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stats.broadcastStatsChannel statistics
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.getBroadcastStatsGet channel statistics
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/stats.MegagroupStats b/data/corefork.telegram.org/type/stats.MegagroupStats new file mode 100644 index 0000000000..c8eee6f74a --- /dev/null +++ b/data/corefork.telegram.org/type/stats.MegagroupStats @@ -0,0 +1,162 @@ + + + + + stats.MegagroupStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.MegagroupStats

+ +

Supergroup statistics

+

+ +
+
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
+
+---functions---
+
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stats.megagroupStatsSupergroup statistics
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.getMegagroupStatsGet supergroup statistics
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/stats.MessageStats b/data/corefork.telegram.org/type/stats.MessageStats new file mode 100644 index 0000000000..80baae0184 --- /dev/null +++ b/data/corefork.telegram.org/type/stats.MessageStats @@ -0,0 +1,162 @@ + + + + + stats.MessageStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.MessageStats

+ +

Message statistics

+

+ +
+
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
+
+---functions---
+
+stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stats.messageStatsMessage statistics
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.getMessageStatsGet message statistics
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/stickers.SuggestedShortName b/data/corefork.telegram.org/type/stickers.SuggestedShortName new file mode 100644 index 0000000000..ebd72dcfed --- /dev/null +++ b/data/corefork.telegram.org/type/stickers.SuggestedShortName @@ -0,0 +1,162 @@ + + + + + stickers.SuggestedShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.SuggestedShortName

+ +

A suggested short name for the specified stickerpack

+

+ +
+
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
+
+---functions---
+
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stickers.suggestedShortNameA suggested short name for a stickerpack
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stickers.suggestShortNameSuggests a short name for a given stickerpack name
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/storage.FileType b/data/corefork.telegram.org/type/storage.FileType new file mode 100644 index 0000000000..d0bb3d3fd0 --- /dev/null +++ b/data/corefork.telegram.org/type/storage.FileType @@ -0,0 +1,188 @@ + + + + + storage.FileType + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.FileType

+ +

Object describes the file type.

+

+ +
+
storage.fileUnknown#aa963b05 = storage.FileType;
+storage.filePartial#40bc6f52 = storage.FileType;
+storage.fileJpeg#7efe0e = storage.FileType;
+storage.fileGif#cae1aadf = storage.FileType;
+storage.filePng#a4f63c0 = storage.FileType;
+storage.filePdf#ae1e508d = storage.FileType;
+storage.fileMp3#528a0677 = storage.FileType;
+storage.fileMov#4b09ebbc = storage.FileType;
+storage.fileMp4#b3cea0e4 = storage.FileType;
+storage.fileWebp#1081464c = storage.FileType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
storage.fileUnknownUnknown type.
storage.filePartialPart of a bigger file.
storage.fileJpegJPEG image. MIME type: image/jpeg.
storage.fileGifGIF image. MIME type: image/gif.
storage.filePngPNG image. MIME type: image/png.
storage.filePdfPDF document image. MIME type: application/pdf.
storage.fileMp3Mp3 audio. MIME type: audio/mpeg.
storage.fileMovQuicktime video. MIME type: video/quicktime.
storage.fileMp4MPEG-4 video. MIME type: video/mp4.
storage.fileWebpWEBP image. MIME type: image/webp.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/string.html b/data/corefork.telegram.org/type/string.html new file mode 100644 index 0000000000..4ea235596d --- /dev/null +++ b/data/corefork.telegram.org/type/string.html @@ -0,0 +1,126 @@ + + + + + string + + + + + + + + + + + + + +
+ +
+
+
+ +

string

+ +

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

+

Further details on basic types»

+

Related pages

+

bytes

+

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

+

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/updates.ChannelDifference b/data/corefork.telegram.org/type/updates.ChannelDifference new file mode 100644 index 0000000000..74581b25a7 --- /dev/null +++ b/data/corefork.telegram.org/type/updates.ChannelDifference @@ -0,0 +1,172 @@ + + + + + updates.ChannelDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.ChannelDifference

+ +

Contains the difference (new messages) between our local channel state and the remote state

+

+ +
+
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
+updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+
+---functions---
+
+updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updates.channelDifferenceEmptyThere are no new updates
updates.channelDifferenceTooLongThe provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoother for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
updates.channelDifferenceThe new updates
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/updates.Difference b/data/corefork.telegram.org/type/updates.Difference new file mode 100644 index 0000000000..0921bd0c90 --- /dev/null +++ b/data/corefork.telegram.org/type/updates.Difference @@ -0,0 +1,177 @@ + + + + + updates.Difference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.Difference

+ +

Occurred changes.

+

+ +
+
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
+updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
+updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
+updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
+
+---functions---
+
+updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updates.differenceEmptyNo events.
updates.differenceFull list of occurred events.
updates.differenceSliceIncomplete list of occurred events.
updates.differenceTooLongThe difference is too long, and the specified state must be used to refetch updates.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
updates.getDifferenceGet new updates.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/updates.State b/data/corefork.telegram.org/type/updates.State new file mode 100644 index 0000000000..48762ef841 --- /dev/null +++ b/data/corefork.telegram.org/type/updates.State @@ -0,0 +1,162 @@ + + + + + updates.State + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.State

+ +

Object contains info on state for further updates.

+

+ +
+
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
+
+---functions---
+
+updates.getState#edd4882a = updates.State;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
updates.stateUpdates state.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
updates.getStateReturns a current state of updates.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/upload.CdnFile b/data/corefork.telegram.org/type/upload.CdnFile new file mode 100644 index 0000000000..275cd01f66 --- /dev/null +++ b/data/corefork.telegram.org/type/upload.CdnFile @@ -0,0 +1,167 @@ + + + + + upload.CdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.CdnFile

+ +

Represents the download status of a CDN file

+

+ +
+
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+
+---functions---
+
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
upload.cdnFileReuploadNeededThe file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.
upload.cdnFileRepresent a chunk of a CDN file.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
upload.getCdnFileDownload a CDN file.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/upload.File b/data/corefork.telegram.org/type/upload.File new file mode 100644 index 0000000000..5d6aca59f5 --- /dev/null +++ b/data/corefork.telegram.org/type/upload.File @@ -0,0 +1,167 @@ + + + + + upload.File + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.File

+ +

Contains info on file.

+

+ +
+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+---functions---
+
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
upload.fileFile content.
upload.fileCdnRedirectThe file must be downloaded from a CDN DC.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
upload.getFileReturns content of a whole file or its part.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/upload.WebFile b/data/corefork.telegram.org/type/upload.WebFile new file mode 100644 index 0000000000..00572493cf --- /dev/null +++ b/data/corefork.telegram.org/type/upload.WebFile @@ -0,0 +1,162 @@ + + + + + Upload.WebFile + + + + + + + + + + + + + +
+ +
+
+
+ +

Upload.WebFile

+ +

Remote file

+

+ +
+
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
+
+---functions---
+
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
upload.webFileRepresents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/users.UserFull b/data/corefork.telegram.org/type/users.UserFull new file mode 100644 index 0000000000..0780c13516 --- /dev/null +++ b/data/corefork.telegram.org/type/users.UserFull @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
+ +
+
+
+ +

Page not found

+ +
The page has not been saved
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/widgets.html b/data/corefork.telegram.org/widgets.html new file mode 100644 index 0000000000..d39effe6f6 --- /dev/null +++ b/data/corefork.telegram.org/widgets.html @@ -0,0 +1,141 @@ + + + + + Telegram Widgets + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram Widgets

+ +

Telegram widgets offer a quick way to add a sharing button to your pages, embed posts from public channels or groups. Widgets can also help your users log in with Telegram or view Telegram Discussions on your website.

+
+
+
+ + +
+
+ + +
+
+ + +
+
+ + +
+
+
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/widgets/discussion.html b/data/corefork.telegram.org/widgets/discussion.html new file mode 100644 index 0000000000..880a5f29b8 --- /dev/null +++ b/data/corefork.telegram.org/widgets/discussion.html @@ -0,0 +1,226 @@ + + + + + Discussion Widget + + + + + + + + + + + + + + + +
+ +
+
+
+ +

Discussion Widget

+ +

You can embed discussions from any public channel on your website. You only need a link to a post with comments to embed it together with all discussion.

+

If you have a website with articles and a telegram channel where you post links to these articles, you can use this widget to show discussions from that channel on your website. In this case you only need a link to the channel. Discussions will be available on your website as soon as you post a link into the channel. For this to work, you should add the <link rel="canonical" href="%page_url%"> tag to the page header where %page_url% is the canonical URL of the current page.

+

Configure widget

+

You can choose options for your widget using the form below.

+

+
+ +
+
+ +
+ +
+
+
+ +
+ +
+
+ +
+
+
+ +
+
+ +
+
+
+
+ +
+ +
+
+ + + + + + + +
+ + +
+
+ +
+ +
+ +
Make sure you have a <link rel="canonical" href="%page_url%"> tag in the page header with the canonical url of the current page.
+
+
+ +
+
+
+
+
+

+

Basic comments

+

If you're looking to simply add Telegram comments to pages on your website, without linking them with a channel, you can use our basic comments solution.

+
+ +
+ +
+
+ +
+ + + + + + + + + + diff --git a/data/corefork.telegram.org/widgets/login.html b/data/corefork.telegram.org/widgets/login.html new file mode 100644 index 0000000000..d8c245ae6f --- /dev/null +++ b/data/corefork.telegram.org/widgets/login.html @@ -0,0 +1,404 @@ + + + + + Telegram Login Widget + + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram Login Widget

+ +
+

The Telegram login widget is a simple way to authorize users on your website.
Check out this post for a general overview of the widget.

+
+

Setting up a bot

+

To use the login widget, you'll need a Telegram bot.

+

We strongly recommend that the profile picture of the bot you use for authorization corresponds with your website‘s logo, and that the bot’s name reflects that connection.

+

Users will see this message when they log into your website:

+
+ +
+ +

It is more likely that users will log in if your bot has a name and logo they expect to see.

+

Linking your domain to the bot

+

Once you have chosen a bot, send the /setdomain command to @Botfather to link your website's domain to the bot. Then configure your widget below and embed the code on your website.

+

Widget configuration

+

+
+ +
+
+
+ +
+ +
+ + +
+ Log in below to load your bots with linked domains +
+
+ +
+ +
+ + + +
+
+ +
+
+ +
+ +
+ + +
+
+ +
+ +
+ + +
+
+ +
+ +
+ +
+
+ +
+ +
+ +
+
+ +
+
+
+
+
+

+

Receiving authorization data

+

After a successful authorization, the widget can return data in two ways:

+
    +
  • by redirecting the user to the URL specified in the data-auth-url attribute with the following parameters: id, first_name, last_name, username, photo_url, auth_date and hash;
  • +
  • by calling the callback function data-onauth with the JSON-object containing id, first_name, last_name, username, photo_url, auth_date and hash fields.
  • +
+

Checking authorization

+

You can verify the authentication and the integrity of the data received by comparing the received hash parameter with the hexadecimal representation of the HMAC-SHA-256 signature of the data-check-string with the SHA256 hash of the bot's token used as a secret key.

+

Data-check-string is a concatenation of all received fields, sorted in alphabetical order, in the format key=<value> with a line feed character ('\n', 0x0A) used as separator – e.g., 'auth_date=<auth_date>\nfirst_name=<first_name>\nid=<id>\nusername=<username>'.

+

The full check might look like:

+
data_check_string = ...
+secret_key = SHA256(<bot_token>)
+if (hex(HMAC_SHA256(data_check_string, secret_key)) == hash) {
+  // data is from Telegram
+}
+

To prevent the use of outdated data, you can additionally check the auth_date field, which contains a Unix timestamp when the authentication was received.

+

Sample implementation

+

You can find sample PHP code for checking authorization and receiving data about a logged in user on this page.

+
+ +
+ +
+
+ +
+ + + + + + + + + diff --git a/data/corefork.telegram.org/widgets/post.html b/data/corefork.telegram.org/widgets/post.html new file mode 100644 index 0000000000..383e14184f --- /dev/null +++ b/data/corefork.telegram.org/widgets/post.html @@ -0,0 +1,240 @@ + + + + + Post Widget + + + + + + + + + + + + + + + +
+ +
+
+
+ +

Post Widget

+ +

You can embed messages from public groups and channels anywhere. Here’s what an embed of a Telegram message looks like when included on a web page:

+

+ +

+
+ +

To get the HTML-code for embedding a message, just open its t.me link (e.g., t.me/durov/43) in a web browser and click < > EMBED:

+
+ +
+ +

Configure widget

+

You can choose more options using the form below.

+

+
+ +
+
+ +
+ +
+
+
+ +
+ +
+
+ +
+
+
+
+ +
+ +
+ + + +
+
+ +
+ +
+
+ + + + + + + +
+ + +
+
+ +
+ +
+ +
+
+ +
+
+
+
+
+

+
+ +
+ +
+
+ +
+ + + + + + + + + + diff --git a/data/corefork.telegram.org/widgets/share.html b/data/corefork.telegram.org/widgets/share.html new file mode 100644 index 0000000000..18ec61fb75 --- /dev/null +++ b/data/corefork.telegram.org/widgets/share.html @@ -0,0 +1,250 @@ + + + + + Sharing Button + + + + + + + + + + + + + + +
+ +
+
+
+ +

Sharing Button

+ +

A Telegram Sharing Button is an easy way to let users forward content from your website or app to their friends, Channels or Saved Messages on Telegram.

+
+ TITLE +
+ +

When a user presses the button, Telegram asks them to choose a chat, group or channel where your link will be shared. You can also add some text that describes the link – the user will be able to edit it before sending the message.

+
+ TITLE +
+ +
+

Check out posts on the Telegram Blog for working examples of sharing buttons.

+
+

Adding Telegram sharing buttons to your website

+

Widget Constructor

+

Use this constructor to get embeddable code for your website.

+


+ +

+
+ +
+
+ +
+ +
+
+
+ +
+ +
+
+ +
+
+
+
+ +
+ +
+ + +
+
+ +
+ +
+ + +
+
+ +
+ +
+ +
+
+ +
+
+
+
+
+

+

Custom buttons

+

Feel free to create your own custom UI for the button. The only thing you need to make it work is to point the user to this URL on click:

+
https://t.me/share/url?url={url}&text={text}
+

where {url} is the URL the user will be sharing and {text} is an optional description that will be included with the link. Both values should be URL-encoded.

+

Here is a sample code for PHP:

+
/**
+ * @param string $url Absolute URL to share, e.g. "https://example.com/path/to/article?with=params"
+ * @param string $text Optional comment to share URL with, e.g. "Check out this article!"
+ * @return string Button HTML markup, feel free to modify to your taste
+ */
+function telegramForwardButton($url, $text = '') {
+  $share_url = 'https://t.me/share/url?url='.rawurlencode($url).'&text='.rawurlencode($text);
+  return "<a href=\"{$share_url}\">Share</a>";
+}
+

You are welcome to use the Telegram Logos in your custom button design.

+

Integrations and libraries

+ +

If you have a library, plugin or integration script for Telegram sharing buttons, please contact @BotSupport and we'll add you to this list.

+
+ +
+ +
+
+ +
+ + + + + + + + + diff --git a/data/desktop.telegram.org.html b/data/desktop.telegram.org.html new file mode 100644 index 0000000000..b2c6845e01 --- /dev/null +++ b/data/desktop.telegram.org.html @@ -0,0 +1,76 @@ + + + + + Telegram Desktop + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + diff --git a/data/instantview.telegram.org.html b/data/instantview.telegram.org.html new file mode 100644 index 0000000000..a280c7fd58 --- /dev/null +++ b/data/instantview.telegram.org.html @@ -0,0 +1,293 @@ + + + + + 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/docs.html b/data/instantview.telegram.org/docs.html new file mode 100644 index 0000000000..51203e87be --- /dev/null +++ b/data/instantview.telegram.org/docs.html @@ -0,0 +1,1527 @@ + + + + + Instant View Manual + + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+ +
+
+
+
+

Instant Views and Where to Find Them

+ +
+ +

This document describes Telegram's Instant View format in stupefying detail. If this is your first time hearing about Instant View, please check out our Introduction and Sample Templates before you dive in.

+

If you're comfortable with the idea of Instant View templates, let's look at what makes them tick. To begin with, this is our in-house artist's idea of how Instant View pages are generated:

+
+ +
+ +

It turns out, he is not entirely wrong. This is how Instant View pages are really generated:

+
    +
  1. Whenever Telegram needs to display a link preview for a URL, it also checks whether an Instant View template exists for that domain.
  2. +
  3. If a template exists, our Instant View Bot obtains the page using the URL (it only processes pages that have the MIME-type text/html).
  4. +
  5. The bot then applies rules from the template that determine the positioning of the key elements on the source page (using XPath 1.0 expressions) and modifies the page content to fit the Instant View format.
  6. +
  7. The edited page is used to create a new Instant View page that will be displayed to the user.
  8. +
+

This document will explore the Instant View Format, the Types of Rules your template can utilize, as well as some useful XPath constructs, conditions, and functions that may help you build better templates.

+

This manual was intended to be used as a reference, so you don't have to read the entire thing to get started. Our sample templates make for a much better entry point. You can check back here whenever something is not clear.

+

Recent changes

+

September 10, 2020

+
    +
  • Added the new ~allowed_origin option
  • +
  • Added the new @load function
  • +
  • The @inline function now supports the silent parameter which ignores errors while fetching a page
  • +
+

March 20, 2019

+

Version 2.1

+
    +
  • Supported the srcset attribute in Image and Icon types. The IV engine will automatically take the highest image resolution available (but not higher than 2560px).
  • +
  • The @match function now returns only nodes which content was matched by regular expression
  • +
  • The @replace function now returns only nodes which content was replaced by regular expression
  • +
  • The @inline function no longer follows canonical redirect links while fetching a page
  • +
+

Also in this update:

+ +

December 10, 2018

+

Instant View 2.0 expands the platform with support for right-to-left languages, new page blocks, useful functions and much more. We recommend using the latest version in your templates. To do this, add the following rule at the beginning of the template:

+
~version: "2.0"
+

Below is a list of changes in version 2.0:

+

New properties:

+
    +
  • kicker
  • +
  • site_name
  • +
+

New types:

+
    +
  • Map
  • +
  • Table
  • +
  • Details
  • +
  • RelatedArticles
  • +
  • Marked
  • +
  • Subscript
  • +
  • Superscript
  • +
  • Icon
  • +
  • PhoneLink
  • +
  • Reference
  • +
+

New types of rules:

+ +

New functions:

+ +

Other features and improvements:

+
    +
  • Xpath query results can be appended into variables using + (see more)
  • +
  • New XPath function ends-with
  • +
  • Lists can contain block elements such as paragraph, nested lists, tables and so on
  • +
  • Support for attribution in media captions (<cite> tag)
  • +
  • Support for image links (href attribute for the Image type)
  • +
  • Unsupported elements (such as an image inside the blockquote) now generate an error instead of moving up
  • +
  • Improved @simplify function for better processing RichText (e.g. saves line breaks formed by block elements)
  • +
+

Instant View Format

+

An Instant View page is an object with the following properties:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeDescription
title RequiredRichTextPage title
subtitleRichTextPage subtitle
kicker RichTextKicker
authorStringAuthor name
author_urlUrlAuthor link
published_dateUnixtimeDate published
descriptionStringA short description (used in link preview)
image_urlUrlLink preview photo (used in link preview)
document_urlUrlLink preview document (used in link preview)
site_name StringName of website (used in link preview)
channelStringThe username of the article author's (or the originating website's) channel on Telegram in the format @username
coverMedia (Image/Video/Embed/Map)Page cover
body RequiredArticlePage content
+

RTL support

+

The platform supports right-to-left languages. If <html> tag or tag referenced by body property has the attribute dir="rtl", the page will be marked as RTL. In case this attribute is not set, you can set it manually to display the page in Instant View as RTL using the following rule:

+
  @set_attr(dir, "rtl"): $body   # if body is already defined
+  @set_attr(dir, "rtl"): /html   # alternative way
+

Supported types

+

The IV page object can hold the following types:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeAllowed childrenDescriptionHTML counterpart
ArticleHeader
Subheader
Paragraph
Preformatted
Divider
Anchor
List
Blockquote
Pullquote
Media
Image
Video
Audio
Embed
Slideshow
Table
Details
Footer
RelatedArticles
Page content<article>
HeaderRichTextMajor headingWe use the top-level of the <h1><h4> headings found on the source page
SubheaderRichTextMinor headingWe use the remaining headings <h1><h4> as well as <h5><h6> headings
ParagraphRichTextA paragraph<p>
PreformattedRichTextPreformatted text<pre> with the optional attribute data-language*
AnchorAnchor<anchor> with the attribute name that contains the anchor name
DividerA separator<hr>
ListListItemA list<ul> for a bullet list, <ol> for a numbered list
ListItemversion 1.0:
RichText

version 2.0:
Header
Subheader
Paragraph
Preformatted
Divider
Anchor
List
Blockquote
Pullquote
Media
Image
Video
Audio
Embed
Slideshow
Table
Details
A list item<li>
BlockquoteRichText
QuoteCaption
A block quote<blockquote>
PullquoteRichText
QuoteCaption
A pull quote<aside>
QuoteCaptionRichTextCaption of a quote<cite>
MediaImage
Video
Audio
Embed
Map
MediaCaption
Media content<figure>
ImageAn image<img> with the attribute src and the optional attribute href to make the image clickable. Allowed formats: GIF, JPG, PNG (GIF would be converted into Video type by IV)
As of version 2.1, supports the attribute srcset (srcset has higher priority than src, the same as in a browser; IV gets the highest available resolution under 2560px).
VideoA video<video> with the attribute src, or containing the tag <source type="video/mp4"> with the attribute src
AudioAn audio<audio> with the attribute src, or containing the tag <source> with the attribute src and the attribute type (possible types: audio/ogg, audio/mpeg, audio/mp4)
EmbedAn embedded element<iframe> with the attribute src. List of supported embeds
Map A map<img> or <iframe> with the attribute src referring to Google or Yandex maps
SlideshowMedia (Image/Video)
Image
Video
MediaCaption
A slideshow<slideshow>
MediaCaptionRichTextMedia caption<figcaption>
As of IV 2.0, can contain an additional tag <cite> with attribution (author, creator or source of the media)
Table TableCaption
TableRow
A table<table>
TableCaption RichTextA table caption<caption>
TableRow TableCellA table row<tr> with the optional attributes align, valign, can be wrapped with <thead> or <tbody> or <tfoot> with the optional attributes align, valign
TableCell RichTextA table cell<td> for a standard cell, <th> for a header cell, with the optional attributes align, valign, colspan, rowspan
Details 
(version 2.0+)
DetailsHeader
Header
Subheader
Paragraph
Preformatted
Divider
Anchor
List
Blockquote
Pullquote
Media
Image
Video
Audio
Embed
Slideshow
Table
Details
A collapsible block<details> with the optional attribute open to be opened by default
DetailsHeader 
(version 2.0+)
RichTextA visible heading for the collapsible block<summary>
RelatedArticles Header
Link
Related articles<related> containing one of <h1><h6> tag as header of the block and <a> tags with the attribute href containing a URL of related article. Note: Only articles that have an IV will appear in this block on the IV page.
FooterRichTextThe footer<footer>
RichTextBold
Italic
Underline
Strike
Fixed
Marked
Subscript
Superscript
Icon
Link
EmailLink
PhoneLink
LineBreak
Anchor
Reference
String
Formatted textText elements and supported tags
BoldRichTextBold text<b> or <strong>
ItalicRichTextItalic text<i> or <em>
UnderlineRichTextUnderlined text<u> or <ins>
StrikeRichTextStrikethrough text<s> or <del> or <strike>
FixedRichTextMonospace text<code> or <kbd> or <samp> or <tt>
Marked RichTextMarked text<mark>
Subscript RichTextSubscript text<sub>
Superscript RichTextSuperscript text<sup>
Icon A small image inside the text<pic> with the attribute src, width, height. Can contain the attribute optional if the image is not important and may be ignored. Allowed formats: JPG, PNG.
As of version 2.1, supports the attribute srcset (srcset has higher priority than src, the same as in a browser).
LinkRichTextA link<a> with the attribute href containing a URL
EmailLinkRichTextA link to an email address<a> with the attribute href containing a mailto: link
PhoneLink RichTextA link to a phone number<a> with the attribute href containing a tel: link
Reference RichTextA reference<reference> with the attribute name that contains the reference name
LineBreakLine break<br>
+
Note on code languages
+

Telegram apps currently do not support code highlighting, but they will in the future. For this reason, it is advisable to include the code language attribute (data-language) for large <pre> blocks if it is supplied in the source.

+
+

Types of Rules

+

Instant View rules are instructions that tell our IV bot where to find the meta-elements on the source page and how it should modify the content of the page when an Instant View page is created.

+

Each new line in a template describes a new rule. When the bot renders a page into the Instant View format, it applies rules from the relevant template one after another and ignores any empty lines. You can leave comments by starting a line with #, all following text on that line will be ignored unless enclosed in quote marks. You can use the \ symbol to carry a rule over to the next string, like this:

+
# Comment 
+# You can break up \
+  a long rule into \
+  multiple strings
+

Most rules are based on XPath 1.0 expressions used to locate the required nodes on the source page.

+

A block of rules may have a name. In this case, it can be reused in other rules.

+

We support the following types of rules:

+

Conditions

+

Conditions offer unlimited flexibility for your templates. Rules of this type begin with the symbols ? or ! and use the following format:

+
?condition:  xpath_query   # condition example
+!condition:  regexp        # parameter on the right depends on the type of the condition
+?condition                 # some conditions don't have parameters
+

Groups of conditions that immediately follow one another are interpreted as a block. ?-rules follow the OR logic when joined, while !-rules follow the AND logic. This means that for the bot to apply each block, all !-conditions in the block and at least one of the ?-conditions within it must be met. This also means that each block must have at least one ?-condition.

+

Blocks of conditions split your rule set into groups. Groups of rules that do not have any conditions are always applied. All other groups are only applied if their conditions are met.

+

Examples

+
# If a rule is placed here, it will be applied
+# Same with the one here
+
+?false               # This condition is always false
+# The rule placed here will never be applied, because the condition is not met
+# Very useful indeed
+
+?exists: //article   # This condition is true if the page has an article tag
+# On these lines, a new group of rules is located, and it will be applied if
+# there's an article tag on the page, despite the ?false condition above
+
+?exists: //article
+?exists: //div[@id="article"]
+!exists: //meta[@property="og:title"]
+# The rules below this block will be applied if an <article> tag or a
+# <div id="article"> can be found, this tag must also be present: <meta property="og:title">
+

+ +
+

Check out the Supported Conditions to see what works out of the box »

+
+

Properties

+

Properties are the building blocks for your IV page. Check the Instant View Format for a list of properties that can be used when creating IV pages (you can also define custom properties, but they will not be used anywhere on the resulting IV page). Use this format to fill properties:

+
property: xpath_query
+property: "Some string"
+property: null
+

Properties store the first node that matches the XPath expression xpath_query. By default, if a property already has a value, it will not be overwritten. You can change this behavior by adding ! to the property name – in this case a new non-empty value can be assigned. If you add !! to the property name, even an empty new value can be assigned to the property.

+

You can also assign a string to the property instead of the xpath_query. In this case, the property will contain a text element with the specified text. It is also possible to assign null to discard the property's value (will only work with !!).

+

Examples

+
title:   //article//h1      # Looking for the 'title' in the article heading
+title:   //h1               # If not found, checking for any headings at all
+title:   //head/title       # If no luck either, trying the <title> tag
+?path: /blog/.*             # On pages in the /blog/ section 
+title!:  //div[@id="title"] # we prefer to use <div id="title">, if present
+?path: /news/.*             # On pages in the /news/ section
+title!!: //h3               # title is always in an h3 tag
+
+author:   //article/@author  # Get author name from the author attribute
+?exists:  //article[has-class("anonymous")]    
+author!!: null               # Don't display author for anonymous posts
+
+

Reminder: The title and body properties are required for an IV page to be created.

+
+

Variables

+

Variables are useful for storing and manipulating nodes before assigning them to properties for the final IV page. Variable names begin with the $ symbol. Use this format to initialize them:

+
$variable: xpath_query
+$variable: "Some text"
+$variable: null
+

Variables store a list of nodes that match the Xpath expression xpath_query. If a variable is assigned for the second time, its previous value is overwritten. You can change this behavior by adding ? to the variable name. You can also append a list of nodes to the previous one by adding + to the variable name.

+

You can also assign a string to the variable instead of the xpath_query. In this case, the variable will contain a list with one text element that has the specified text. It is also possible to assign null to discard the variable's value.

+

Examples

+
$images:  //img
+$images:  //img[@src]     # the previous value will be overwritten
+$images?: //article//img  # a new value will only be assigned if the variable is empty
+$medias:  //img
+$medias+: //video         # now $medias contains all img and video tags
+

Options

+

Options affect how the page is processed by the bot. Options begin with the ~ symbol. Use this format to set them:

+
~option: "value"
+~option: true
+

Options can be set with values in JSON format.

+

Examples

+
~version: "2.1"
+

+ +
+

Check out Supported Options to see what else works out of the box.

+
+

Functions

+

Functions are extremely flexible, but you'll probably mostly use them to strip unnecessary nodes from the page and to replace certain elements with others. Function names begin with the @ symbol, you can use the following format:

+
@function:                 xpath_query   # a function without parameters
+@function(param):          xpath_query   # additional parameters are placed in paretheses
+@function(p1 p2):          xpath_query   # a function with two parameters
+@function(p1, "param #2"): xpath_query   # parameters can be separated by commas
+                                         # and enclosed in quote marks when needed
+@function:                 "Some text"   # use string instead of xpath_query if needed
+

The main argument of a function is a list of nodes that match the Xpath expression xpath_query. You can also use a string as the main argument instead of an xpath_query. In this case, the main argument passed to the function will be a list with one text element that has the specified text.

+

Examples

+
@remove:            //header               # removes all <header> tags found on the page
+@replace_tag(<h1>): //div[@class="header"] # replaces all <div class="header"> tags with <h1>
+<h1>:               //div[@class="header"] # an alias for @replace_tag(<h1>)
+

+ +

Note: You may find the @debug function particularly useful when creating XPath expressions.

+
+

Check out Supported Functions to see what else works out of the box.

+
+

Block Functions

+

Block functions manipulate blocks of rules. Block function names also begin with the @ symbol, you can use the following format:

+
@function(xpath_query) {   # opening bracket should be at the end of the line
+  $variable: xpath_query   # some other rules here
+  @function: $@            #   inside the block function
+}                          # closing bracket should be on a separate line
+

A block function can contain another block function so they can be nested. Block function can not contain conditions.

+
+

Please note that block functions that execute a block of rules several times (map, repeat, while, while_not) have a limit on the total number of iterations for the entire template.

+
+

Examples

+
@if( //article ) {    # if <article> exists
+  @append(<p>): $$    #   append paragraph into it
+}
+

+ +
+

Check out Supported Block Functions to see what else works out of the box.

+
+

Include

+
+

Note: This is a service rule, it will not work in your templates. It was included in this reference to give you a better understanding of how the system works. You can see an example of this rule at work in the Processing Pages section.

+
+

Rules of this type begin with the + symbol and use the following format:

+
+ rules
+

This rule inserts a block of rules with the specified name. In most cases, the name corresponds to the domain to which the rules apply.

+

Examples

+
+ core.telegram.org # inserting the block of rules that is used for core.telegram.org
+?not_exists: $body
++ telegram.org      # inserting the block of rules that is used for telegram.org
+

Special variables $$ and $@

+

The special variables work within a group of rules.

+
    +
  • The $$ variable always contains the result of the most recent XPath query.
  • +
  • The $@ variable holds the return of the most recently run function.
  • +
+

These variables come in handy when you're creating chains of rules. If a rule is missing xpath_query, the statement is considered to be equal to $$.

+

Examples

+
# Put a picture into a <figure> tag, then set it as the cover
+@wrap(<figure>): //img[@id="cover"]
+cover:           $@
+
+# Insert a divider before each div.divider that's no longer required
+@before(<hr>):   //div[has-class("divider")]
+@remove          # this is the same as @remove: $$
+

Extended XPath

+

For your convenience, you can use the following constructs in your XPath expressions.

+

Context

+

Regular XPath queries search for nodes in the context of the entire document. To specify the context for a particular expression, you can use variables in the format $context. If a matching variable exists, the query will be made relative to each variable node. If it doesn't and a matching property exists, the query will be made relative to the property node. If no matching variables or properties exist, the query return an empty list.

+

Examples

+
$headers:      //h1              # all <h1> tags on the page
+article:       //article         # the first <article> tag on the page
+$art_headers:  $article//h1      # all <h1> tags inside article
+$header_links: $art_headers//a   # all <a> tags inside each $art_headers node
+

Zeroing in on nodes

+

The result of an XPath query is always a list of matching nodes. If you'd like to narrow the list down to a single node, you can use the following syntax: (xpath_query)[n], where n is the number of the desired node. Numbering starts at 1, you can get the last node by using the last() function. This syntax can only be applied to the entire expression.

+

Examples

+
$headers:    //h1                    # all <h1> tags on the page
+$header2:    (//h1)[2]               # the second <h1> tag on the page
+$header2:    ($headers)[2]           # same
+$last_link:  ($header2//a)[last()]   # the last link inside $header2
+

has-class

+

You will often need to locate nodes that have a certain class. To do this, you can use the has-class("class") function that serves as an alias for the expression contains(concat(" ", normalize-space(@class), " "), " class ").

+

Examples

+
# Transform all div.header elements into h1
+<h1>: //div[contains(concat(" ", normalize-space(@class), " "), " header ")]
+# same idea, but much shorter
+<h1>: //div[has-class("header")]
+

ends-with

+

XPath has a starts-with function that checks whether the first string starts with the second string but does not have ends-with. In IV you can use the ends-with("haystack","needle") function that serves as an alias for the expression (substring("haystack", string-length("haystack") - string-length("needle") + 1) = "needle").

+

Examples

+
# Select all JPG images
+@debug: //img[(substring(@src, string-length(@src) - string-length(".jpg") + 1) = ".jpg")]
+# the same, but much shorter
+@debug: //img[ends-with(@src, ".jpg")]
+

prev-sibling

+

An axis that selects the previous sibling of the current node. Serves as an alias for the expression preceding-sibling::*[1]/self.

+

Examples

+
# Transform all div nodes, that immediately follow img nodes into figcaption
+<figcaption>: //div[./preceding-sibling::*[1]/self::img]
+# the same
+<figcaption>: //div[./prev-sibling::img]
+

next-sibling

+

An axis that selects the next sibling of the current node. Serves as an alias for the expression following-sibling::*[1]/self

+

Examples

+
# Join paragraphs following each other into one, separating them with a line break
+@combine(<br>): //p/following-sibling::*[1]/self::p
+# the same, but shorter
+@combine(<br>): //p/next-sibling::p
+

Supported conditions

+

Below are conditions supported in Instant View rules.

+

domain

+
domain: regexp
+

Checks whether the domain of the current page matches a regular expression. The check is case-insensitive, so the actual expression used will look like this: /^regexp$/i.

+

Examples

+
# Rule for *.subdomain.example.com URLs
+?domain: .+\.subdomain\.example\.com
+

domain_not

+
domain_not: regexp
+

Checks whether the domain of the current page does not match a regular expression. The check is case-insensitive, so the actual expression used will look like this: /^regexp$/i.

+

Examples

+
# Rule for *.subdomain.example.com URLs with an exception for dev.subdomain.example.com
+?domain:     .+\.subdomain\.example\.com
+!domain_not: dev\.subdomain\.example\.com
+

path

+
path: regexp
+

Checks whether the path to the current page matches a regular expression. The check is case-insensitive, so the actual expression used will look like this: /^regexp$/i.

+

Examples

+
# Rule for example.com/news/* links
+?path: /news/.+   # no need to escape the slash
+

path_not

+
path_not: regexp
+

Checks whether the path to the current page does not match a regular expression. The check is case-insensitive, so the actual expression used will look like this: /^regexp$/i.

+

Examples

+
# Rule for example.com/news/* links with an exception for example.com/news/recent
+?path:     /news/.+
+!path_not: /news/recent
+

exists

+
exists: xpath_query
+

Checks whether target nodes exist on the current page.

+

Examples

+
# Apply rule only to pages with an <article> tag
+?exists: //article
+

not_exists

+
not_exists: xpath_query
+

Checks whether target nodes do not exist on the current page.

+

Examples

+
# Apply rule only to pages with an <article> tag, that do not include any quotes.
+?exists:     //article
+!not_exists: //article//blockquote
+

true

+
true
+

A condition that is always true.

+

Examples

+
?path:    /blog/.+
+# Rules for the blog section go here
+?true
+# Rules that go here will be applied to all pages
+

false

+
false
+

A condition that is always false.

+

Examples

+
?path:    /news/.+
+# Rules for the news section go here
+?false
+# Rules that go here will never be applied
+

Supported options

+

Below are options supported in Instant View rules.

+

version

+
~version: "2.1"
+

Sets the version of IV used in the template. The behavior of some IV functions may change according to the version provided (see the manual of corresponding function).
The value must be one of "1.0", "2.0" or "2.1". We recommend using the latest version, 2.1.

+

Examples

+
~version: "2.1"
+# Now you can use new features from IV 2.1
+
+

Please note that version should be set at the beginning of the template before any other rules.

+
+

allowed_origin NEW

+
~allowed_origin: "https://example.com"
+~allowed_origin: ["https://example.com", "https://subdomain.example.com"]
+

Sets the origin (or the list of origins) from which content can be loaded using the @load and @inline functions.
The value should be String or Array of String.

+

Examples

+
~allowed_origin: "https://api.example.com"
+# Now you can load content from https://api.example.com regardless of the origin of current page
+@load: "https://api.example.com/get/article"
+

Supported functions

+

The general format for a function is the following:

+
@function: xpath_query
+

Each function accepts the list of nodes returned by the XPath statement as the main parameter. You may omit xpath_query, in which case $$, the result of the previous XPath query, will be passed into the function. The function then processes each element in the list and returns a list of transformed nodes which are stored in the $@ variable.

+

Below is a list of functions that are supported in Instant View rules.

+

debug

+
@debug: xpath_query
+

Logs the elements passed into the function, these elements will be displayed in the status line at the bottom of the screen in the Instant View Editor. Returns the elements passed. Consider combining with $$ and $@.

+

Example

+
@debug: //article//a     # displays all links from the page in the log
+@debug                   # displays all links again
+

+ +

Look for debug output at the bottom of your Editor:

+
+ +
+ + +

remove

+
@remove: xpath_query
+

Removes target nodes from the page, returns an empty list.

+

Examples

+
@remove: //div[has-class("related")] # remove article div.related
+@debug                               # empty list
+

append

+
@append("Some text"): xpath_query
+@append(@attr):       xpath_query
+@append(<tag>):       xpath_query
+@append(<tag>, attr, value[, attr, value[, ...]]): xpath_query
+

Inserts content, specified by the parameter, to the end of each target node.

+
    +
  • If the first parameter is in angle brackets, a new <tag> node will be created. The following two parameters then specify the name and value of an attribute for that node. If value has the format @attr, the value of the attribute attr in the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.
  • +
  • If the first parameter has the format @attr, a new text element with value of the attribute attr of the targeted node will be created.
  • +
  • Otherwise, a text element with the text specified in the first parameter will be created.
  • +
+

Returns a list of the newly created nodes.

+

Examples

+
# <div class="a"><em>1</em></div>
+@append(<p>): //div
+# <div class="a"><em>1</em><p></p></div>
+

prepend

+
@prepend("Some text"): xpath_query
+@prepend(@attr):       xpath_query
+@prepend(<tag>):       xpath_query
+@prepend(<tag>, attr, value[, attr, value[, ...]]): xpath_query
+

Inserts content, specified by the parameter, to the beginning of each target node.

+
    +
  • If the first parameter is in angle brackets, a new <tag> node will be created. The following two parameters then specify the name and value of an attribute for that node. If value has the format @attr, the value of the attribute attr in the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.
  • +
  • If the first parameter has the format @attr, a new text element with value of the attribute attr of the targeted node will be created.
  • +
  • Otherwise, a text element with the text specified in the first parameter will be created.
  • +
+

Returns a list of the newly created nodes.

+

Examples

+
# <div class="a"><em>1</em></div>
+@prepend(<p>, data-class, @class): //div
+# <div class="a"><p data-class="a"></p><em>1</em></div>
+

after

+
@after("Some text"): xpath_query
+@after(@attr):       xpath_query
+@after(<tag>):       xpath_query
+@after(<tag>, attr, value[, attr, value[, ...]]): xpath_query
+

Inserts content, specified by the parameter, after each target node.

+
    +
  • If the first parameter is in angle brackets, a new <tag> node will be created. The following two parameters then specify the name and value of an attribute for that node. If value has the format @attr, the value of the attribute attr in the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.
  • +
  • If the first parameter has the format @attr, a new text element with value of the attribute attr of the targeted node will be created.
  • +
  • Otherwise, a text element with the text specified in the first parameter will be created.
  • +
+

Returns a list of the newly created nodes.

+

Examples

+
# <div class="a"><em>1</em><em>2</em></div>
+@after("!"): //div/em
+# <div class="a"><em>1</em>!<em>2</em>!</div>
+

before

+
@before("Some text"): xpath_query
+@before(@attr):       xpath_query
+@before(<tag>):       xpath_query
+@before(<tag>, attr, value[, attr, value[, ...]]): xpath_query
+

Inserts content, specified by the parameter, before each target node.

+
    +
  • If the first parameter is in angle brackets, a new <tag> node will be created. The following two parameters then specify the name and value of an attribute for that node. If value has the format @attr, the value of the attribute attr in the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.
  • +
  • If the first parameter has the format @attr, a new text element with value of the attribute attr of the targeted node will be created.
  • +
  • Otherwise, a text element with the text specified in the first parameter will be created.
  • +
+

Returns a list of the newly created nodes.

+

Examples

+
# <div class="a"><em>1</em></div>
+@before("@"): //div/em
+# <div class="a">@<em>1</em></div>
+

append_to

+
@append_to(xpath_query): xpath_query
+@append_to($var):        xpath_query
+

Inserts each target node to the end of the base node.

+

The first parameter specifies the base node. You can pass an XPath expression that begins with ., in this case the query will be executed relative to the relevant node. The first relevant node will be used as the base node. You can also pass a variable name. If such a variable exists, the first relevant node will be used as the base node. If the variable doesn't exist or is empty, the property with a matching name will be used as the base node.

+

Returns a list of target nodes.

+

Examples

+
$div:             //div
+# <div class="a"><em></em></div><p>Text</p>
+@append_to($div): //p
+# <div class="a"><em></em><p>Text</p></div>
+

prepend_to

+
@prepend_to(xpath_query): xpath_query
+@prepend_to($var):        xpath_query
+

Inserts each target node to the beginning of the base node.

+

The first parameter specifies the base node. You can pass an XPath expression that begins with ., in this case the query will be executed relative to the relevant node. The first relevant node will be used as the base node. You can also pass a variable name. If such a variable exists, the first relevant node will be used as the base node. If the variable doesn't exist or is empty, the property with a matching name will be used as the base node.

+

Returns a list of target nodes.

+

Examples

+
$div:              //div
+# <div class="a"><em></em></div><p>Text</p>
+@prepend_to($div): //p
+# <div class="a"><p>Text</p><em></em></div>
+

after_el

+
@after_el(xpath_query): xpath_query
+@after_el($var):        xpath_query
+

Inserts each target node after the base node.

+

The first parameter specifies the base node. You can pass an XPath expression that begins with ., in this case the query will be executed relative to the relevant node. The first relevant node will be used as the base node. You can also pass a variable name. If such a variable exists, the first relevant node will be used as the base node. If the variable doesn't exist or is empty, the property with a matching name will be used as the base node.

+

Returns a list of target nodes.

+

Examples

+
$div:                        //div
+# <div class="a"><p>Text</p><em></em></div>
+@after_el("./../self::div"): //p
+# <div class="a"><em></em></div><p>Text</p>
+

before_el

+
@before_el(xpath_query): xpath_query
+@before_el($var):        xpath_query
+

Inserts each target node before the base node.

+

The first parameter specifies the base node. You can pass an XPath expression that begins with ., in this case the query will be executed relative to the relevant node. The first relevant node will be used as the base node. You can also pass a variable name. If such a variable exists, the first relevant node will be used as the base node. If the variable doesn't exist or is empty, the property with a matching name will be used as the base node.

+

Returns a list of target nodes.

+

Examples

+
$div:                        //div
+# <div class="a"><p>Text</p><em></em></div>
+@before_el("./../self::div"): //p
+# <p>Text</p><div class="a"><em></em></div>
+

replace_tag

+
@replace_tag(<tag>):     xpath_query
+<tag>:                   xpath_query
+

Changes the name of the tag. The new name for the tag should be passed as the first parameter. Returns target nodes.

+

Examples

+
# <div class="list unordered"><div class="item"></div><div class="item"></div></div>
+@replace_tag(<li>): //div[has-class("item")]
+<ul>:               //div[has-class("list")]
+# <ul class="list unordered"><li class="item"></li><li class="item"></li></ul>
+

wrap

+
@wrap(<tag>): xpath_query
+

Wrap each target node in the <tag> tag. Returns a list of the new <tag> elements.

+

Examples

+
# <em>1</em><em>2</em>
+@wrap(<b>): //em
+# <b><em>1</em></b><b><em>2</em></b>
+@wrap(<u>)
+# <b><u><em>1</em></u></b><b><u><em>2</em></u></b>
+@wrap(<p>): $@
+# <b><p><u><em>1</em></u></p></b><b><p><u><em>2</em></u></p></b>
+

wrap_inner

+
@wrap_inner(<tag>): xpath_query
+

Wrap an HTML structure around the content of each target node in the <tag> tag. Returns a list of new <tag> elements.

+

Examples

+
# <p>H<sub>2</sub>0</p>
+@wrap_inner(<b>): //p
+# <p><b>H<sub>2</sub>0</b></p>
+

clone

+
@clone: xpath_query
+

Creates a copy of each target node. Returns a list of the newly created nodes.

+

Examples

+
# <p class="text">Paragraph</p>
+@clone: //p
+# <p class="text">Paragraph</p><p class="text">Paragraph</p>
+

detach

+
@detach: xpath_query
+

Separates the target node from the rest in the parent tag. Creates a copy of the parent tag and wraps the target node into this new instance. Returns a list of parent tags that contain target nodes.

+

Examples

+
# <a href="#1">
+#   <b>1</b>
+#   <p>Link #1</p>
+# </a>
+# <a href="#2">
+#   <b>2</b>
+#   <p>Link #2</p>
+# </a>
+
+@detach: //a/b
+
+# <a href="#1">
+#   <b>1</b>
+# </a>
+# <a href="#1">
+#   <p>Link #1</p>
+# </a>
+# <a href="#2">
+#   <b>2</b>
+# </a>
+# <a href="#2">
+#   <p>Link #2</p>
+# </a>
+
+@after(<br>): $@
+
+# <a href="#1">
+#   <b>1</b>
+# </a><br>
+# <a href="#1">
+#   <p>Link #1</p>
+# </a>
+# <a href="#2">
+#   <b>2</b>
+# </a><br>
+# <a href="#2">
+#   <p>Link #2</p>
+# </a>
+

split_parent

+
@split_parent: xpath_query
+

Splits the parent tag by the target node. Places preceding siblings wrapped into parent element before the target node. Places following siblings wrapped into parent element placed after target node.

+

Returns a list of target nodes.

+

Examples

+
# <p class="text">
+#   <b>First</b> line
+#   <figure><img src="photo.jpg"></figure>
+#   <i>Second</i> line
+# </p>
+@split_parent: //p/figure
+# <p class="text">
+#   <b>First</b> line
+# </p>
+# <figure><img src="photo.jpg"></figure>
+# <p class="text">
+#   <i>Second</i> line
+# </p>
+

pre

+
@pre: xpath_query
+

Specifies that the text inside the target node is already formatted. Returns a list of matching nodes.

+

Examples

+
# <p>     Some          text  , </p>
+# <p>  Some  another      text  </p>
+@pre: (//p)[1]
+# Result in the Instant View page:
+#      Some          text  , 
+# Some another text
+

set_attr

+
@set_attr(attr, value):       xpath_query
+@set_attr(attr, @attr):       xpath_query
+@set_attr(attr, "Some text"): xpath_query
+@set_attr(attr, "Some text", @from-attr, ...): xpath_query
+

Sets an attribute in each matching node. The name of the attribute is passed in the first parameter. The value of the attribute is the rest of the parameters concatenated.

+

If value has the format @attr, the value of the attribute attr of the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.

+

Returns a list of attribute nodes.

+

Examples

+
# <p class="a"></p>
+@set_attr(data-class, @class)
+# <p class="a" data-class="a"></p>
+@set_attr(id, @class, "_", ./@data-class)
+# <p class="a" data-class="a" id="a_a"></p>
+

set_attrs

+
@set_attrs(attr, value): xpath_query
+@set_attrs(attr, value[, attr, value[, ...]]): xpath_query
+

Sets multiple attributes for each of the target nodes. Each two parameters specify the name and value for the new attributes.

+

If value has the format @attr, the value of the attribute attr of the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.

+

Returns a list of the matching nodes.

+

Examples

+
# <p class="a"></p>
+@set_attrs(data-class, @class, id, "a_a"): //p
+# <p class="a" data-class="a" id="a_a"></p>
+

match

+
@match(regexp):                         xpath_query
+@match(regexp, match_index):            xpath_query
+@match(regexp, match_index, modifiers): xpath_query
+

Performs a search based on a regular expression. Replaces the content of the target node with the search result. The second parameter specifies the number of the captured parenthesized subpattern. If this is not specified, the text that matched the full pattern will be used. You can specify modifiers for the regular expression using the optional parameter (ims modifiers are supported).

+

Returns a list of target nodes. As of IV 2.1, returns a list of target nodes the content of which matched the regular expression.

+

Examples

+
# <p class="plainText">Hello, world!</p>
+@match("[a-z]+!"): //p
+# <p class="plainText">world!</p>
+@match("([a-z]+)!", 1): //p/text()
+# <p class="plainText">world</p>
+@match("..t", 0, "i"): //p/@class
+# <p class="inT">Bye, world!</p>
+
+# <ul><li>a1</li><li>a</li><li>21b</li><li>.</li></ul>
+@match("[0-9]+"): //ul/li
+# <ul><li>1</li><li></li><li>21</li><li></li></ul>
+@debug: $@
+# Debug 2 nodes:
+#   [0]: <li>1</li>
+#   [1]: <li>21</li>
+

replace

+
@replace(regexp, replacement):            xpath_query
+@replace(regexp, replacement, modifiers): xpath_query
+

Performs a search and replace operation using the regular expression. You can specify modifiers for the regular expression using the optional parameter (ims modifiers are supported).

+

Returns a list of target nodes. As of IV 2.1, returns a list of target nodes the content of which was replaced by the regular expression.

+

Examples

+
# <p class="text">Hello, world!</p>
+@replace("Hello", "Goodbye"): //p/text()
+# <p class="text">Goodbye, world!</p>
+@replace(".t$", "mp"): //p/@class
+# <p class="temp">Goodbye, world!</p>
+@replace("goodb", "B", "i"): //p/text()
+# <p class="temp">Bye, world!</p>
+
+# <ul><li>a1</li><li>a</li><li>21b</li><li>.</li></ul>
+@replace("[0-9]+", "($0)"): //ul/li
+# <ul><li>a(1)</li><li>a</li><li>(21)b</li><li>.</li></ul>
+@debug: $@
+# Debug 2 nodes:
+#   [0]: <li>a(1)</li>
+#   [1]: <li>(21)b</li>
+

urlencode

+
@urlencode: xpath_query
+

Encodes the content of the target node as per RFC 3986. Returns target nodes.

+

Examples

+
# <a href="https://telegram.org">link</a>
+$a: //a
+@urlencode: $a/@href
+# <a href="https%3A%2F%2Ftelegram.org">link</a>
+@set_attr(href, "/?url=", @href): $a
+# <a href="/?url=https%3A%2F%2Ftelegram.org">link</a>
+

urldecode

+
@urldecode: xpath_query
+

Decodes the content of the target node as per RFC 3986. Returns target nodes.

+

Examples

+
# <a href="/?url=https%3A%2F%2Ftelegram.org">link</a>
+$a: //a
+@match("^/\?url=(.+)$", 1): $a/@href
+# <a href="https%3A%2F%2Ftelegram.org">link</a>
+@urldecode
+# <a href="https://telegram.org">link</a>
+

htmlencode

+
@htmlencode: xpath_query
+

Convert special characters in the target node to HTML entities. Returns the target nodes.

+

Examples

+
# <p>&lt;b&gt;Some text&lt;\b&gt;</p>
+@htmlencode: //p
+# <p>&amp;lt;b&amp;gt;Some text&amp;lt;\b&amp;gt;</p>
+

htmldecode

+
@htmldecode: xpath_query
+

Convert special HTML entities in the target node back to characters. Returns the target nodes.

+

Examples

+
# <p>&amp;lt;b&amp;gt;Some text&amp;lt;\b&amp;gt;</p>
+@htmldecode: //p
+# <p>&lt;b&gt;Some text&lt;\b&gt;</p>
+

style_to_attrs

+
@style_to_attrs(css_prop, attr): xpath_query
+@style_to_attrs(css_prop, attr[, css_prop, attr[, ...]]): xpath_query
+

Gets a value of a CSS property from the style attribute and sets it into an attribute for each of the target nodes. Each two parameters specify the name for the new attribute and the name of CSS property. Returns a list of matching nodes.

+

Examples

+
# <img style="width: 20px; height: 20px">
+@style_to_attrs(width, data-width, height, data-height): //img
+# <img style="width: 20px; height: 20px" data-width="20" data-height="20">
+

background_to_image

+
@background_to_image: xpath_query
+

Transforms the target node with a background picture into an <img> tag with an src attribute. The target node must contain a style attribute with the background. Returns a list of transformed nodes.

+

Examples

+
# <div class="bg_image" style="background-image:url(image.jpg)"></div>
+@background_to_image: //div[has-class("bg_image")]
+# <img src="image.jpg">
+

json_to_xml

+
@json_to_xml: xpath_query
+

Transforms the content of the target node to the XML format. The contents must be in valid JSON format. The resulting XML tree will be inserted into the document. Returns the root element of the XML tree.

+

Examples

+
# <div data-var='{"a":1,"b":[1,2],"c":{"p":"Hello!"}}'></div>
+@json_to_xml: //div/@data-var
+@debug: $@
+# <xml><a>1</a><b><item>1</item><item>2</item></b><c><p>Hello!</p></c></xml>
+

html_to_dom

+
@html_to_dom: xpath_query
+

Parse the content of the target node in HTML format and insert it into the document. Returns the root element of the inserted HTML tree.

+

Examples

+
# <div data-content="&lt;b&gt;Some text&lt;\b&gt;"></div>
+@html_to_dom: //div/@data-content
+@debug: $@
+# <dom><b>Some text</b></dom>
+

combine

+
@combine:                        xpath_query
+@combine(" - "):                 xpath_query
+@combine(<tag>):                 xpath_query
+@combine(<tag>[, " - "[, ...]]): xpath_query
+

Combines each target node with its preceding node if such a node exists. You can use parameters to specify nodes to be inserted above the target node. If the parameter is in angular brackets, a new <tag> node will be created. Otherwise a text element with the text specified by the parameter will be used.

+

Returns a list of nodes, preceding the target nodes.

+

Examples

+
# <pre>1 2 3</pre>
+# <pre> 4 5 </pre>
+# <pre>6 7 8</pre>
+@combine:             //pre/following-sibling::*[1]/self::pre
+# <pre>1 2 3 4 5 6 7 8</pre>
+
+# <p>first</p>
+# <p>second</p>
+@combine(<br>, <br>): //p/following-sibling::*[1]/self::p
+# <p>first<br><br>second</p>
+
+# <h1>Title</h1>
+# <strong>Subtitle</strong>
+@combine(<br>, "\n"): //h1/following-sibling::*[1]/self::strong
+# <h1>Title<br>
+# Subtitle</h1>
+

datetime

+
@datetime(-2): xpath_query
+@datetime(-2, "en-US", "yyyy-MM-dd"): xpath_query
+

Transforms the date and time from the text of the target node into a unixtime timestamp. The parameter specifies the timezone of the original date and time.

+

You can also pass a locale and a pattern to parse the date and time in more complicated cases. If a non-gregorian calendar is used, this needs to be specified in the locale. For example, "fa-IR@calendar=persian". Available patterns are documented here.

+

On success, returns a text element with the unixtime timestamp. Otherwise, returns the target element.

+

Examples

+
# <div id="date">1 January 2017, 15:04</div>
+@datetime(-2):  //div[@id="date"]
+published_date: $@   # the property published_date will hold a unixtime timestamp
+
+# <time>دوشنبه, ۲۳ اسفند ۱۳۹۵</time>
+@datetime(0, "fa-IR@calendar=persian", "EEEE, dd MMMM yyyy"): //time
+published_date: $@   # the property published_date will hold a unixtime timestamp
+

simplify

+
+

Note: This is a service function. There is no reason for you to use it in your templates. It was included in this reference to give you a better understanding of how the system works (see the ..after block).

+
+
@simplify: xpath_query
+

Processes the target nodes according to the Instant View format. Returns the target nodes.

+

Examples

+
# <p><span><b>S</b>ome</span> <em>important</em> text!</p>
+@simplify: //p
+# <p><b>S</b>ome <em>important</em> text!</p>
+

inline

+
@inline:         xpath_query
+@inline(silent): xpath_query
+

If the target element is an <iframe> with the attribute src, the content of the iframe will be loaded. The target element will be replaced with the content of the iframe.

+

If the target node is an HTML-comment, a <comment> element with the content of the comment will be created. The comment will be replaced by the newly created node.

+

You can use silent parameter to ignore errors while processing this function. You will still see an error in the debug console, but the rules that come after will continue to execute.

+

Returns a list of replaced nodes.

+
+

Note: The @inline function adheres to the same-origin policy. This means that the target and the inlined pages should have the same origin. You can specify additional allowed origins using the option ~allowed_origin

+
+

Examples

+
# <p><iframe src="/subpage.html"></iframe></p>
+# /subpage.html:
+#   <html><body><p>Hello!</p></body></html>
+@inline: //p/iframe
+# <p><html><body><p>Hello!</p></body></html></p>
+@debug
+# <html><body><p>Hello!</p></body></html>
+
+# <p><!--<b>Hello!</b>, world!--></p>
+@inline: //p/comment()
+# <p><comment><b>Hello!</b>, world!</comment></p>
+@debug
+# <comment><b>Hello!</b>, world!</comment>
+

load NEW

+
@load:         "https://example.com"
+@load(silent): xpath_query
+

Loads the content of the URL. The URL can be specified as a string or be the content of the target node.

+

You can use silent parameter to ignore errors while processing this function. You will still see an error in the debug console, but the rules that come after will continue to execute.

+

Returns the newly created node with loaded content.

+
+

Note: The @load function adheres to the same-origin policy. This means that the target and the loaded pages should have the same origin. You can specify additional allowed origins using the option ~allowed_origin

+
+

Examples

+
@append(<iframe> src "/subpage.html"): /html/body
+$iframe: $@
+@remove
+@inline: $iframe
+# the same, but much shorter
+@load: "/subpage.html"
+
+@load(silent): //meta[@property="api:url"]/@content
+# trying to load content from api:url
+@if ( $@ ) {
+  # Do something with content
+}
+

unsupported

+
@unsupported: xpath_query
+

Specifies that the target node contains essential content that can't be represented in the Instant View format. Returns the target nodes.

+

Examples

+
# <p>See the graph below:</p>
+# <canvas class="article_graph" width="600" height="400"></canvas>
+@unsupported: //canvas[has-class("article_graph")]
+
+

Tip: It is important to identify that a page contains essential unsupported content — no IV page will be generated to ensure that the user never gets incomplete info from an article. The system will take care of the most popular cases in the ..after block, but your template must cover everything that the system doesn't catch.

+
+

Supported block functions

+

The general format for a block function is the following:

+
@function(xpath_query) {
+  # block of rules
+}
+

Block functions usually accept the list of nodes returned by the XPath statement as a parameter. Depending on the function and its parameters, rules inside the block can be run several times or never. Block functions can contain any type of rules except conditions.

+

Below is a list of block functions that are supported in Instant View rules.

+

if

+
@if(xpath_query) {
+  # block of rules
+}
+

Executes the block of rules if target nodes exist on the current page. If target nodes do not exist, the block of rules will be skipped. The $$ and $@ variables contain target nodes found by the XPath query.

+

Example

+
@if( //div[has-class("blockquote")] ) { # if div.blockquote exists
+  <blockquote>: $@                      #   change tag name to blockquote
+  <cite>: $@//div[has-class("author")]  #   and mark div.author as a caption
+}
+

if_not

+
@if_not(xpath_query) {
+  # block of rules
+}
+

Executes a block of rules if target nodes do not exist on the current page. If such nodes exist, the block of rules will be skipped. The $$ and $@ variables contain target nodes found by the XPath query.

+

Example

+
@if_not( $body//footer ) {     # if footer does not exist
+  @append(<footer>): $body     #   append it into body
+}
+

map

+
@map(xpath_query) {
+  # block of rules
+}
+

Executes a block of rules once per each target node found by the XPath query. At the beginning of each iteration, the following variables will be set:

+
    +
  • $$ will contain the target nodes found by XPath query;
  • +
  • $@ will contain the current target node;
  • +
  • $index will contain the index of the current target node (starts with 1);
  • +
  • $first will contain <true> if the current target node is the first in the list and an empty list otherwise;
  • +
  • $middle will contain <true> if the current target node is between the first and the last in the list, empty list otherwise;
  • +
  • $last would contain <true> if the current target node is the last one in the list, empty list otherwise.
  • +
+

Example

+
@map( //div[@id="list"]/p ) {   # for each paragraph in list
+  $p: $@                        #   store the current paragraph in $p variable
+  @prepend_to($p): ". "         #   and
+  @prepend_to($p): $index       #   number them starting with 1
+}
+
+

Please note that the @map function should be used only if it is impossible to use regular functions with xpath queries (for example you need to use $index). Otherwise, regular functions are faster because they process several nodes at once.

+
+

Example

+
# Bad way:
+@map( //div[has-class("image")] ) {
+  $image: $@
+  <cite>:       $image//p/span
+  <figcaption>: $image//p
+  <figure>:     $image
+}
+# The same result, but faster:
+$image:       //div[has-class("image")]
+<cite>:       $image//p/span
+<figcaption>: $image//p
+<figure>:     $image
+

repeat

+
@repeat(n) {
+  # block of rules
+}
+

Executes a block of rules n times. At the beginning of each iteration, the following variables will be set:

+
    +
  • $$ and $@ will contain the previous value of $$;
  • +
  • $index will contain the index of the current iteration (starts with 1);
  • +
  • $first will contain <true> if this is the first iteration, an empty list otherwise;
  • +
  • $middle will contain <true> if the current iteration is between the first and last, empty list otherwise;
  • +
  • $last will contain <true> if this is the last iteration, empty list otherwise.
  • +
+

Example

+
# appends "1, 2, 3, 4, 5" to $body
+@repeat( 5 ) {
+  @append_to($body): $index
+  @if_not( $last ) {
+    @append_to($body): ", "
+  }
+}
+

while

+
@while(xpath_query) {
+  # block of rules
+}
+

Executes a block of rules while target nodes exist on the current page. At the beginning of each iteration the following variables will be set:

+
    +
  • $$ and $@ will contain target nodes found by XPath query;
  • +
  • $index will contain the index of the current iteration (starts with 1);
  • +
  • $first will contain <true> if it is the first iteration, an empty list otherwise.
  • +
+

Example

+
@while( //iframe ) {
+  @inline: $@          # inline all nested iframes
+}
+

while_not

+
@while_not(xpath_query) {
+  # block of rules
+}
+

Executes a block of rules while target nodes do not exist on the current page. At the beginning of each iteration the following variables will be set:

+
    +
  • $$ and $@ will contain target nodes found by XPath query;
  • +
  • $index will contain the index of the current iteration (starts with 1);
  • +
  • $first will contain <true> if this is the first iteration, an empty list otherwise.
  • +
+

Example

+
@while_not( //video ) {   # if no video exists on the current page
+  @inline: //iframe       #   try to inline iframes, maybe video is inside the frame
+}
+

Embedded elements

+

Instant View supports widgets from popular services. We display them as embedded elements or specially formatted quotes. The Instant View bot analyzes all iframes in the document body and generates a widget if the service is supported.

+
+

Some popular widgets do not use iframes. Note that the ..after block of rules contains rules to transform such widgets to an Instant View compatible format.

+
+

We currently support the following services:

+
    +
  • Youtube
  • +
  • Vimeo
  • +
  • Tweets & Twitter Videos
  • +
  • Facebook Posts & Videos
  • +
  • Instagram
  • +
  • Giphy
  • +
  • SoundCloud
  • +
  • GithubGist
  • +
  • Aparat
  • +
  • VK.com Videos
  • +
+

Processing pages

+

All pages are processed according to the following rules:

+
# Url: http://example.com/some_page.html
++ example.com
+?true
++ ..after
+

If a page is on a third-level domain and above, the following rules are applied:

+
# Url: http://some.subdomain.example.com/some_page.html
++ some.subdomain.example.com
+?not_exists: $body
++ subdomain.example.com
+?not_exists: $body
++ example.com
+?true
++ ..after
+

In other words, at first the bot attempts to use a block of rules that features the full domain name. If such a block does not exist, the bot checks for the next level up to the second-level domain.

+

..after is a special block of rules that is applied to all pages irrespective of the domain name.

+

Working with subdomains

+

If the page is on a third-level domain or higher, you need to manually select the domain level to which your template will apply. Use this menu in the top left corner of the page:

+
+
+
+ +

Choose a level that hosts pages with the same structure, so that your rules are relevant to all the matching pages on this domain.

+
+

For example, use wikipedia.org to create an IV page for https://en.wikipedia.org/wiki/Domain_name because the page structure doesn't depend on language in Wikipedia.

+
+
+ +
+
+
+
+
+ + + + + + + + + + + + + + diff --git a/data/instantview.telegram.org/samples.html b/data/instantview.telegram.org/samples.html new file mode 100644 index 0000000000..caa2bfc0ba --- /dev/null +++ b/data/instantview.telegram.org/samples.html @@ -0,0 +1,395 @@ + + + + + Sample Templates - Instant View + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+ +
+
+
+

Sample Templates

+

In this section, 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.

+ +
+

+ medium.com7 +

+
+
+

7 pages

+

Not modified

+
+
+ +
+

+ telegra.ph2 +

+
+
+

2 pages

+

Not modified

+
+
+ +
+

+ telegram.org7 +

+
+
+

7 pages

+

Not modified

+
+
+ +
+
+
+
+
+ + + + + + + + + diff --git a/data/instantview.telegram.org/templates.html b/data/instantview.telegram.org/templates.html new file mode 100644 index 0000000000..ab8a2985e3 --- /dev/null +++ b/data/instantview.telegram.org/templates.html @@ -0,0 +1,1253 @@ + + + + + Templates - Instant View + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+ +
+
+
+

Templates

+

Enter any article URL to check the currently active Instant View template for issues – or create a new template if Instant View is not yet supported for the website.

+
+
+
+
Domain +
+
+ TemplateLast Update +
+
+
+
+ +
+
+
+
+
+ 01net.com +
+
+ Template #3 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 032.ua +
+
+ Template #28 + Jan 1, 1970 + +
+
+
+ 0352.ua +
+
+ Template #102 + Jan 1, 1970 + +
+
+ +
+ Template #28 + Jan 1, 1970 + +
+
+ +
+ Template #4 + Jan 1, 1970 + +
+
+
+ 061.ua +
+
+ Template #92 + Jan 1, 1970 + +
+
+ +
+ Template #3 + Jan 1, 1970 + +
+
+
+ 06blog.it +
+
+ Template #16 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #8 + Jan 1, 1970 + +
+
+
+ 103.by +
+
+ Template #3 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #17 + Jan 1, 1970 + +
+
+
+ 10tv.com +
+
+ Template #6 + Jan 1, 1970 + +
+
+
+ 10tv.in +
+
+ Template #3 + Jan 1, 1970 + +
+
+
+ 110km.ru +
+
+ Template #36 + Jan 1, 1970 + +
+
+
+ 112.ua +
+
+ Template #9 + Jan 1, 1970 + +
+
+
+ 13.cl +
+
+ Template #9 + Jan 1, 1970 + +
+
+
+ 13abc.com +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 15min.lt +
+
+ Template #27 + Jan 1, 1970 + +
+
+
+ 1863x.com +
+
+ Template #8 + Jan 1, 1970 + +
+
+
+ 1car.ir +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #4 + Jan 1, 1970 + +
+
+ +
+ Template #37 + Jan 1, 1970 + +
+
+
+ 1kr.ua +
+
+ Template #3 + Jan 1, 1970 + +
+
+ +
+ Template #16 + Jan 1, 1970 + +
+
+ +
+ Template #12 + Jan 1, 1970 + +
+
+ +
+ Template #8 + Jan 1, 1970 + +
+
+
+ 1nsk.ru +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #13 + Jan 1, 1970 + +
+
+
+ 1plus1.ua +
+
+ Template #7 + Jan 1, 1970 + +
+
+
+ 1prime.ru +
+
+ Template #24 + Jan 1, 1970 + +
+
+
+ 1reg.by +
+
+ Template #3 + Jan 1, 1970 + +
+
+
+ 1tmn.ru +
+
+ Template #1 + Jan 1, 1970 + +
+
+
+ 1tv.ru +
+
+ Template #32 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 2000.ua +
+
+ Template #16 + Jan 1, 1970 + +
+
+ +
+ Template #8 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 20min.ch +
+
+ Template #31 + Jan 1, 1970 + +
+
+ +
+ Template #8 + Jan 1, 1970 + +
+
+ +
+ Template #60 + Jan 1, 1970 + +
+
+
+ 218tv.net +
+
+ Template #27 + Jan 1, 1970 + +
+
+
+ 21.by +
+
+ Template #3 + Jan 1, 1970 + +
+
+ +
+ Template #12 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 24.ae +
+
+ Template #13 + Jan 1, 1970 + +
+
+
+ 24.com.eg +
+
+ Template #4 + Jan 1, 1970 + +
+
+
+ 24.hu +
+
+ Template #8 + Jan 1, 1970 + +
+
+
+ 24auto.de +
+
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #4 + Jan 1, 1970 + +
+
+ +
+ Template #11 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #51 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #5 + Jan 1, 1970 + +
+
+
+ 24hod.sk +
+
+ Template #14 + Jan 1, 1970 + +
+
+ +
+ Template #16 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 24smi.org +
+
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 24tv.ua +
+
+ Template #36 + Jan 1, 1970 + +
+
+
+ 24ur.com +
+
+ Template #2 + Jan 1, 1970 + +
+
+
+ 24vest.de +
+
+ Template #6 + Jan 1, 1970 + +
+
+
+ 24vita.de +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #12 + Jan 1, 1970 + +
+
+
+ 2m.ma +
+
+ Template #10 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 2sao.vn +
+
+ Template #42 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 34.ua +
+
+ Template #1 + Jan 1, 1970 + +
+
+
+ 34mag.net +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #5 + Jan 1, 1970 + +
+
+ +
+ Template #66 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 360tv.ru +
+
+ Template #7 + Jan 1, 1970 + +
+
+ +
+ Template #21 + Jan 1, 1970 + +
+
+
+ 368.media +
+
+ Template #14 + Jan 1, 1970 + +
+
+
+ 36kr.com +
+
+ Template #62 + Jan 1, 1970 + +
+
+
+ 36ng.ng +
+
+ Template #1 + Jan 1, 1970 + +
+
+
+ 36on.ru +
+
+ Template #30 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #6 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #38 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 3dnews.ru +
+
+ Template #65 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 3dpapa.ru +
+
+ Template #20 + Jan 1, 1970 + +
+
+ +
+ Template #16 + Jan 1, 1970 + +
+
+
+ 3rbdr.net +
+
+ Template #1 + Jan 1, 1970 + +
+
+
+
+
+
+
+
+ + + + + + + + + + diff --git a/data/macos.telegram.org.html b/data/macos.telegram.org.html new file mode 100644 index 0000000000..00293b1396 --- /dev/null +++ b/data/macos.telegram.org.html @@ -0,0 +1,521 @@ + + + + + Telegram for macOS + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ + +
+ +
+ + + + + +
+
This software is available under GPL v2 license.

Source code is available on GitHub.

Beta version
+
+ +
+ +
+
+

Version history

+ +

8.5 2022-02-01

+
    +
  • VIDEO STICKERS, BETTER REACTIONS AND MORE
  • +
  • Video Stickers
  • +
  • Use a new type of detailed stickers with smooth animations.
  • +
  • Create new sets by sending .webm videos to @stickers.
  • +
  • Bring your custom animated stickers from other apps.
  • +
  • Better Reactions
  • +
  • See smaller, compact animations when reacting to messages.
  • +
  • Press and hold an emoji in the reaction menu to send a bigger animation.
  • +
  • See real-time animations in chat when a user reacts to your message.
  • +
  • React with additional emoji expressing love, appreciation, anger or surprise.
  • +
  • Read Status for Reactions
  • +
  • Tap the new button in chats to jump to your messages that have unseen reactions.
  • +
  • Watch the animations for unseen reactions play when you hit the button.
  • +
+ +

8.4.1 2021-12-30

+
    +
  • REACTIONS, SPOILERS, CONTEXT MENU
  • +
  • Reactions
  • +
  • Double tap a message to send a quick :thumbsup: reaction.
  • +
  • Press and hold a message for more reactions.
  • +
  • Change your quick reaction emoji in Settings > Stickers and Emoji.
  • +
  • Group and Channel admins can enable reactions in their chat via Chat Info > Edit > Reactions.
  • +
  • Spoilers
  • +
  • Use ||Text|| formatting to hide some or all of the contents of a message.
  • +
  • Tap the spoiler animation in chat to reveal its hidden text.
  • +
  • Spoiler formatting hides text in chat, as well as in the chat list and notifications.
  • +
  • Context Menu
  • +
  • All context menus in the app were redesigned with beautifully animated icons.
  • +
+ +

8.4 2021-12-30

+
    +
  • REACTIONS, SPOILERS, CONTEXT MENU
  • +
  • Reactions
  • +
  • Double tap a message to send a quick :thumbsup: reaction.
  • +
  • Press and hold a message for more reactions.
  • +
  • Change your quick reaction emoji in Settings > Stickers and Emoji.
  • +
  • Group and Channel admins can enable reactions in their chat via Chat Info > Edit > Reactions.
  • +
  • Spoilers
  • +
  • Select text when typing and choose 'Spoiler' formatting to hide some or all of the contents of a message.
  • +
  • Tap the spoiler animation in chat to reveal its hidden text.
  • +
  • Spoiler formatting hides text in chat, as well as in the chat list and notifications.
  • +
  • Context Menu
  • +
  • All context menus in the app were redesigned with beautifully animated icons.
  • +
+ +

8.4 2021-12-30

+
    +
  • PROTECTED CONTENT, DEVICE MANAGEMENT AND MORE
  • +
  • Protected Content in Groups and Channels
  • +
  • Content creators can restrict the ability to forward messages from their groups and channels.
  • +
  • When forwarding is restricted, users will also be unable to directly save media from the chat or take screenshots.
  • +
  • Toggle this option on or off via Chat Info > Group / Channel Type.
  • +
  • Manage Connected Devices
  • +
  • Choose how long a device may stay inactive before it's logged out automatically.
  • +
  • Select a device to control whether it is allowed to accept Calls or new Secret Chats.
  • +
  • Anonymous Posting in Public Groups
  • +
  • Comment as one of your channels in public groups and channel comments.
  • +
  • Tap the profile picture next to the message bar to choose which channel you will appear as when you send the message.
  • +
+ +

8.2 2021-11-06

+
    +
  • JOIN REQUESTS, GLOBAL CHAT THEMES AND MORE
  • +
  • Join Requests for Groups and Channels
  • +
  • Create special invite links that require admins to approve users before they become members.
  • +
  • Admins can view the applicants’ profiles and bios by tapping the Join Requests bar at the top of the chat.
  • +
  • Add internal labels to your chat's Invite Links to keep them organized.
  • +
  • Global Chat Themes
  • +
  • Apply one of 8 new preset themes to your entire app – each theme has a Day and Night mode, colorful animated backgrounds and gradient message bubbles.
  • +
  • Personalize these themes and find custom theme options in Appearance Settings.
  • +
  • More Interactive Emoji
  • +
  • Send one :joy:, :money_with_wings:, :face_vomiting:, :thumbs_down:, :ghost: or :jack_o_lantern: emoji to any private chat, then tap on the animated emoji to launch a fullscreen effect.
  • +
  • If your chat partner also has the chat open, you will both see the effects and feel the vibrations simultaneously.
  • +
  • This also works with :fireworks:, :party_popper:, :balloon:, :pile_of_poo:, :thumbs_up: and :heart:.
  • +
+ +

8.1.4 2021-10-12

+
    +
  • CHAT THEMES, INTERACTIVE EMOJI, READ RECEIPTS IN GROUPS AND LIVE STREAM RECORDING
  • +
  • Chat Themes
  • +
  • Choose one of 8 new preset themes for any individual private chat.
  • +
  • Click (⋯) in a chat then 'Change Colors' to pick a theme.
  • +
  • Both chat participants will see the same theme in that chat – on all their devices.
  • +
  • Each new theme features colorful gradient message bubbles, beautifully animated backgrounds and unique background patterns.
  • +
  • All chat themes have day and night versions and will follow your overall dark mode settings.
  • +
  • More chat themes coming soon.
  • +
  • Interactive Emoji
  • +
  • Some animated emoji now have fullscreen effects.
  • +
  • Send :fireworks:, :party_popper:, :balloon:, :pile_of_poo:, :thumbs_up: or :heart: to any private chat, then tap on the animated emoji to launch the effect.
  • +
  • If your chat partner also has the chat open, you will both see the effects and feel the vibrations simultaneously.
  • +
  • See the "Watching" status when your chat partner is enjoying emoji effects with you.
  • +
  • More interactive emoji coming soon.
  • +
  • Read Receipts in Small Groups
  • +
  • Select one of your outgoing messages in small groups to see who recently viewed it.
  • +
  • To protect privacy, read receipts are only stored for 7 days after the message was sent.
  • +
  • Record Live Streams and Video Chats
  • +
  • Record video and audio from live broadcasts in your group or channel.
  • +
  • Admins can start recording from the Settings.
  • +
  • Choose between recording in portrait or landscape orientation.
  • +
  • Finished recordings are sent to the admin's Saved Messages and can be easily shared.
  • +
+ +

8.0 2021-09-02

+
    +
  • Live Streams, Flexible Forwarding, Jump to Next Channel and More
  • +
  • Live Stream to an unlimited number of viewers in groups and channels.
  • +
  • Remove sender names before forwarding.
  • +
  • Trending Stickers are now shown above 'Recently Used'.
  • +
  • Set stickers or GIFs as your profile video — or as profile videos for your groups or channels.
  • +
  • Profile pictures in groups follow the messages as you scroll the chat.
  • +
  • There's more! View the full list of changes in-app or on our blog.
  • +
+ +

7.9 2021-08-02

+
    +
  • Video Calls with up to 1000 Viewers, Video Messages 2.0 and More
  • +
  • Group Video Calls 2.0
  • +
  • Group Video Calls now support up to 1000 video viewers, as well as unlimited audio-only listeners.
  • +
  • To start a Group Video Call, create a Voice Chat from the info page of any group where you are an admin — then turn your video on.
  • +
  • Video Messages 2.0
  • +
  • Enjoy higher resolution from video messages in your chats.
  • +
  • Timestamps
  • +
  • Add timestamps like '0:45' to video captions and replies to automatically create links that play the video from that specific moment.
  • +
  • Screen Sharing with Sound
  • +
  • Share your screen in 1-on-1 video calls, as well as group video calls.
  • +
+ +

7.8.1 2021-07-15

+
    +
  • Improved group video calls in voice chats.
  • +
+ +

7.8 2021-06-25

+
    +
  • Group Video Calls
  • +
  • Start video conferences from Voice Chats in any group.
  • +
  • Share your screen or video from your camera with up to 30 participants (limit to be increased soon).
  • +
  • Talk without video with an unlimited number of participants.
  • +
  • Create voice chats from the info page of any group where you are an admin.
  • +
  • Group video calls are supported natively on all devices, including iPads and laptops.
  • +
+ +

7.7 2021-04-28

+
    +
  • Scheduled Voice Chats
  • +
  • Schedule voice chats to let participants know about them in advance.
  • +
  • View a countdown to the voice chat and get notified when it starts.
  • +
  • Who is Who in Voice Chats
  • +
  • Browse full-sized profile pictures and expanded bios directly in the list of participants.
  • +
  • Update your profile pic and bio from the voice chat window.
  • +
  • Payments 2.0
  • +
  • Offer real goods and services for sale in any group, channel or bot – Telegram doesn't charge a commission.
  • +
  • Pay for goods directly using one of 8 integrated payment providers – Telegram doesn't see your payment info.
  • +
+ +

7.6 2021-03-19

+
    +
  • VOICE CHATS 2.0: CHANNELS, MILLIONS OF LISTENERS, RECORDED CHATS, ADMIN TOOLS
  • +
  • Millions of Concurrent Listeners
  • +
  • Start limitless Voice Chats in Groups and Channels.
  • +
  • Host discussions that can be listened to by millions of people simultaneously.
  • +
  • Voice Chat Recordings
  • +
  • Record voice chats to share or publish in Channels later.
  • +
  • See that a chat is being recorded from the red dot next to its title.
  • +
  • Improved List of Participants
  • +
  • See user bio texts right from the list of participants.
  • +
  • Raise your hand to show admins you want to speak.
  • +
  • Management Tools
  • +
  • Create separate Voice Chat Invite Links for listeners or speakers.
  • +
  • Change the title of your Voice Chat to give people an idea of the current topic.
  • +
  • Join Voice Chats as one of your Channels to hide your personal account.
  • +
+ +

7.5.1 2021-03-05

+
    +
  • AUTO-DELETE, INVITE LINKS 2.0 AND MORE
  • +
  • Auto-Delete Messages
  • +
  • Set messages to auto-delete for everyone 24 hours or 7 days after sending.
  • +
  • Control auto-delete settings in any of your chats, as well as in groups and channels where you are an admin.
  • +
  • To enable auto-delete, press and hold on any message > Select > Clear Chat in the top left corner.
  • +
  • New Invite Links for Groups and Channels
  • +
  • Create invite links that work for a limited time or a limited number of uses.
  • +
  • See which users joined using your, or your admins’, invite links.
  • +
  • To manage invite links, open your group or channel Profile > Edit > Invite Links.
  • +
  • Groups with Unlimited Members
  • +
  • Convert groups that are approaching the member limit into unlimited Broadcast Groups.
  • +
+ +

7.4 2021-01-29

+
    +
  • Adjust volume for individual participants of a voice chat.
  • +
  • Report fake groups or channels impersonating famous people or organizations by opening their Profile > More > Report.
  • +
  • Bug fixes and minor improvements.
  • +
+ +

7.3 2020-12-24

+
    +
  • Voice Chats Done Right
  • +
  • Voice Chats in Groups
  • +
  • Turn any of your group chats into a hop-on, hop-off conference call.
  • +
  • Choose 'Start Voice Chat' under in the profile of any group where you are an admin to create a voice chat.
  • +
  • Get up to several thousand participants in each voice chat.
  • +
  • Control the number of speakers with flexible admin tools.
  • +
  • Sticker Outlines
  • +
  • Download stickers faster and watch shimmering outlines as they load.
  • +
+ +

7.2.4 2020-11-29

+
    +
  • Added support for new ARM processors. Entering Hyperspace.
  • +
+ +

7.2.3 2020-11-18

+
    +
  • Fixed a wisdom tooth.
  • +
  • Say 'bug fixes' again. Say 'bug fixes' again, I dare you. I DOUBLE DARE YOU!
  • +
  • The sun is shining, the icon is sweet.
  • +
+ +

7.2.1 2020-11-09

+
    +
  • PINNED MESSAGES 2.0, PLAYLISTS AND MORE
  • +
  • Multiple Pinned Messages
  • +
  • Pin several messages in any chat, including one-on-one chats.
  • +
  • Jump between pinned messages or open them all on a separate page via the top bar.
  • +
  • Playlists and More
  • +
  • Send several music tracks as a playlist.
  • +
  • View detailed statistics about the performance of individual posts in your channels.
  • +
  • Send a :slot_machine: emoji to any chat to try your luck.
  • +
+ +

7.1 2020-10-02

+
    +
  • ANONYMOUS GROUP ADMINS, CHANNEL COMMENTS AND MORE
  • +
  • Anonymous Group Admins
  • +
  • Turn on 'Remain Anonymous' in an admin's Permissions to let them post on behalf of the group and become invisible in the list of members.
  • +
  • Channel Comments
  • +
  • Comment on posts in channels that have a discussion group.
  • +
  • Get notified about replies to your comments via the new Replies chat (if you are not a member in the discussion group).
  • +
  • Silent Messages, now in Secret Chats
  • +
  • Send messages silently in Secret Chats by holding the Send button.
  • +
+ +

7.0.1 2020-09-07

+
    +
  • Yes, Video Calls (alpha version)
  • +
  • Telegram turns 7 years old!
  • +
  • Thank you for your support over all these years. Because of you, this year Telegram reached 400 million active users and is now one of the top 10 most downloaded apps in the world.
  • +
  • To celebrate our 7th anniversary together, we are launching the first version of the feature you’ve been asking for – ultra secure and fast Video Calls.
  • +
+ +

6.3.1 2020-07-31

+
    +
  • PROFILE VIDEOS, 2 GB FILE SHARING, AND MORE
  • +
  • Telegram is now among the top 10 most downloaded and most used apps in the world.
  • +
  • Increased limits for sending files
  • +
  • Share and store unlimited files of any type, now up to 2 GB each.
  • +
  • Profile Videos
  • +
  • Set a Profile Video instead of a static picture.
  • +
  • Quickly change back to a previous profile photo or video by tapping ‘Set as Main’.
  • +
  • Mini-thumbnails, Group Stats and More
  • +
  • See what media is in a message thanks to new mini-thumbnails in the chat list, message search and notifications.
  • +
  • View detailed statistics for the large groups you own.
  • +
  • If you're getting too much attention, flip a switch in Privacy and Security settings to automatically archive and mute all new chats from non-contacts.
  • +
  • Send a single football emoji to see if you score a goal.
  • +
+ +

6.2.5 2020-07-22

+
    +
  • Bug fixes and minor improvements.
  • +
+ +

6.2.3 2020-06-18

+
    +
  • Better GIFs
  • +
  • Enjoy greatly enhanced loading times for GIFs.
  • +
  • Quickly find GIFs in emoji-based sections covering the most popular emotions.
  • +
  • Check the Trending Tab for the top reactions of the day.
  • +
  • Bug fixes and other minor improvements.
  • +
+ +

6.1.4 2020-05-07

+
    +
  • Bug fixes and other improvements.
  • +
+ +

6.1.2 2020-04-30

+
    +
  • 400 MILLION USERS, QUIZZES 2.0 AND €400K FOR QUIZ CREATORS.
  • +
  • Access Shared Media faster from fully redesigned profile pages.
  • +
  • Use the new brush tools in the photo editor to draw on photos when sending or editing.
  • +
  • If you have too many folders, try the alternative mode with folder tabs on the left.
  • +
  • Send a single dart emoji to see if you hit the bullseye.
  • +
  • Add explanations that appear after users respond to a quiz question.
  • +
  • See how much time you have left to answer a question from @QuizBot with the new countdown animation.
  • +
  • Quiz Creator Contest
  • +
  • Participate in Telegram's €400,000 contest by using @QuizBot to create and publish an educational test on any subject.
  • +
+ +

6.0 2020-03-30

+
    +
  • Chat Folders and More
  • +
  • Organize chats into Chat Folders if you have too many chats.
  • +
  • Create custom folders with flexible settings, or use default recommendations.
  • +
  • Pin an unlimited number of chats in each folder.
  • +
  • Archive chats to hide them from "All chats". Muted chats will always stay in the Archive.
  • +
  • View detailed statistics about the growth of your large channels and the performance of their posts.
  • +
  • Send 🎲 to any chat to try your luck and get a random number from the animated dice.
  • +
  • Send 🦠, 🤒, 😷, 🤕, 🤧, 🤢, 🤮, 🧼, 💉, 💊 or 🚑 to try out the new animated emoji.
  • +
+ +

5.9.3 2020-02-23

+
    +
  • Bug fixes and minor improvements.
  • +
+ +

5.9.2 2020-02-20

+
    +
  • Increased stability, optimized memory usage.
  • +
  • Bug fixes and minor improvements.
  • +
  • The oracle would like to know what you think of the color blue.
  • +
+ +

5.9.1 2020-01-23

+
    +
  • Polls 2.0: Open Polls, Multiple Answers, and Quiz Mode
  • +
  • Create three new kinds of polls.
  • +
  • See who voted in Open Polls with non-anonymous results.
  • +
  • Vote for several options in polls that allow Multiple Answers.
  • +
  • Try to guess the correct answer in Quiz-style polls.
  • +
  • Explore various ways of combining the different poll options.
  • +
  • Just like before, you can add polls from the attachment menu in any group or channel.
  • +
+ +

5.8.1 2019-10-30

+
    +
  • Mute chats for a specific time.
  • +
  • Switch between accounts from the improved status bar menu.
  • +
  • Enjoy improved design and animations (e.g. try clicking and holding on a sticker to preview).
  • +
  • Look for new bugs that were introduced while we were fixing the old ones.
  • +
+ +

5.8 2019-10-22

+
    +
  • Enhanced design and other improvements.
  • +
  • Bug fixes.
  • +
+ +

5.8 2019-10-21

+
    +
  • Enhanced design and other improvements.
  • +
+ +

5.7 2019-09-09

+
    +
  • SCHEDULED MESSAGES
  • +
  • Hold the 'Send' button and select 'Schedule Message' to automatically send something at a specified time.
  • +
  • Schedule reminders for yourself in the 'Saved Messages' chat.
  • +
  • Get a notification when any of your scheduled messages are sent.
  • +
  • CUSTOM CLOUD THEMES
  • +
  • Choose a custom accent color and quickly create a new theme in Settings > Appearance.
  • +
  • Share your themes with other users on Telegram across platforms.
  • +
  • Update your theme for all its users when you change something.
  • +
  • NEW PRIVACY SETTINGS AND MORE
  • +
  • Choose who can find you on Telegram when they add your number to their phone contacts.
  • +
  • Share documents to Telegram from your favorite apps using the Share Extension.
  • +
  • Send a single 😁, 😧, 😡, 💩, 😢 or 😮 to check out what's new in the animated emoji department.
  • +
+ +
+ +
+
+
+ +
+
+
+ + + + + + + diff --git a/data/promote.telegram.org/auth.html b/data/promote.telegram.org/auth.html new file mode 100644 index 0000000000..a59bd80a6a --- /dev/null +++ b/data/promote.telegram.org/auth.html @@ -0,0 +1,206 @@ + + + + + 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 or profile users based on their interactions with sponsored messages or other activities. 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/promote.telegram.org/basics.html b/data/promote.telegram.org/basics.html new file mode 100644 index 0000000000..67a1c66e8f --- /dev/null +++ b/data/promote.telegram.org/basics.html @@ -0,0 +1,205 @@ + + + + + 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 or profile users based on their interactions with sponsored messages or other activities. 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/promote.telegram.org/getting-started.html b/data/promote.telegram.org/getting-started.html new file mode 100644 index 0000000000..9a9149a8f2 --- /dev/null +++ b/data/promote.telegram.org/getting-started.html @@ -0,0 +1,321 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
  1. Telegram Ad Platform Explained
+
+
+
+

Telegram Ad Platform Explained

+ +
+

This document explores the Telegram Ad Platform in greater detail, for basic information about sponsored messages, please see this page.

+
+

Getting Started

+

The Telegram Ad Platform is a tool to create sponsored messages in public one-to-many channels with 1000+ subscribers. With this tool you can easily manage your ads and budgets, choose where your ads will be displayed and monitor their performance. For step-by-step instructions on how to create, publish and manage your ads, continue reading below.

+

Logging In

+

To start creating ads on the platform, you must first log in. This requires that you have an existing Telegram account – if you do not yet have an account, download one of our mobile apps for Android or iOS and sign up. Once you have an account, enter the account’s phone number on the login page, after which you instantly receive a message in Telegram (from our verified service account) to confirm your login to the platform.

+
+ +
+ +

Choosing an Account

+

Once you've logged in on the platform, you can proceed either with your Personal Account or by Creating an Organization.

+

Organizations are built around Telegram Groups and Channels – linking your group or channel as an organization gives all admins of that chat the ability to manage advertisements created by the organization.

+
+

Only the owner of the Group or Channel is allowed to create an organization for that chat.

+
+
+ +
+ +

After logging in, you can click Create Ad to start designing a sponsored message or Manage Budget to add funds to your account.

+

Creating an Ad

+

Click ‘Create a new ad’ to start building your advertisement. There you will see a template with several fields to fill in – such as giving your ad a Title, Text, and URL.

+

All links included in the Text and URL field must link to a channel or bot on Telegram, using the format t.me/link or @link. Links to external sites are not allowed.

+
+ +
+ +
+

The link entered in the URL field will be added to a button underneath your sponsored message. If you include a link in the text as well, it must go to the same destination as the link in the URL field.

+
+

CPM and Ad Budget

+

Once the text of your sponsored message is completed, you can set a CPM (Cost-Per-Mille) for the ad, which is the price for one thousand views of your ad. The minimum CPM for a sponsored message is €2.

+

Your ad budget is the amount of funds you are willing to spend on a particular sponsored message. The sponsored message will continue to be shown until it reaches this amount.

+
+

To increase an ad's budget, open it or click the budget field right from your homepage.

+

To decrease an ad's budget, stop and delete the ad – the remaining funds will be returned to your overall budget.

+
+

Language, Topics and Target Channels

+

Sponsored messages are displayed in public channels with 1000+ subscribers. To better customize which channels can host your advertisements, select languages and topics that suit your audience – for example English and Spanish channels related to Movies and Music. You are able to combine several languages and topics, or even leave the fields blank if you prefer.

+

If there are individual channels in which you would specifically like your sponsored message to appear, you can include them via their unique link, such as t.me/durov. Certain topics and channels can also be excluded, giving even more customization. When you are ready, check the box to confirm you have read the Ad Platform Terms of Service and click ‘Create Ad’.

+
+

Note that once your ad is created, its targeting parameters can’t be changed. But you can always use the 'Create a similar ad' function to quickly create a new ad with the same parameters and tweak whatever you wanted to change.

+
+

Copying Ads

+

When you open any of your existing ads, you can use the 'Create similar ad' link next to its name to create a new ad with the same text and parameters. This can be handy if you want to create several ads with slightly different targeting parameters, change targeting parameters in an ad you created, or lower the budget of an ad.

+
+ +
+ +

Adding Funds

+

If you are creating an ad for the first time, you may not have funds in your account yet. When you try to create your ad, you may see a ‘Your balance is too low’ message under the Budget field. Click ‘Add Funds’ to put money on your account – the ad will be saved as a draft so you can easily publish it later.

+
+ Add funds +
+ +
+

You can also publish ads without a budget to get a feel for the platform – then return when you’re ready to launch them.

+
+

You can also access the interface by opening the Manage Budget page and clicking Add Funds.

+
+ +
+ +

Fill in the details about your company on the page that opens and click ‘Send Request’ – our team will review your information and contact you via a verified service account on Telegram with the necessary documents for our advertising agreement and deposit transfer.

+
+

You will receive a confirmation in Telegram each time funds are credited to your account.

+
+ + +

Managing Your Ads

+

Ad Status

+

Once you have submitted an ad, you will see it listed on your account’s homepage. An advertisment can have the following statuses:

+
    +
  • Stopped. This is the default status shown for all new ads without a budget. This status is also shown when the ad's budget has run out.
  • +
  • In Review. Our team is currently checking the ad content before it can be displayed in channels.
  • +
  • Declined. Your ad must be changed before it can go live. Open the ad to see a more detailed explanation and a link to the relevant guidelines.
  • +
  • Active. Your ad is live, and sponsored messages are appearing in Telegram according to your parameters
  • +
  • On Hold. You have paused the ad, but it's ready to become active again whenever you're ready.
  • +
+ + +

Ad Info

+

Click any of your ads on the homepage to make changes to its content and CPM, increase its budget, or see statistics. The title, text and URL of your sponsored message can be updated at any time (but not its targeting parameters) – to see a preview of how the sponsored message looks inside a channel, click ‘Preview Ad’.

+
+ +
+ +
+

If you would like to change the targeting parameters, click ‘Create a similar ad’ – this opens a new template with the same content so you can quickly make a new version.

+
+

Ad Budget

+

To increase the budget of your ad, click the ‘Current Budget’ field. You can also change the CPM to be higher or lower from the ‘CPM’ field. If you need to delete your ad (perhaps to resubmit it with new targeting parameters or a lower budget) tap ‘Delete Ad’.

+
+

It is not possible to decrease the budget of an ad once it has been submitted – in this case, it is best to use ‘Create a similar ad’ and submit a new ad with a lower budget.

+
+ + +

The budget can also be increased from the ‘Budget’ tab. This tab also contains the ad’s Transaction History, showing the ad's spending as well as any increases to the budget – including the amount and time of the increase.

+ + +

Statistics

+

The ‘Statistics’ tab has an overview of your advertisement, such as the date it was created, CPM, budget and overall views. Underneath, you will see a detailed graph showing views of your sponsored message and the number of times a user joined your channel or started the bot after viewing the sponsored message, able to be displayed in increments of minutes or days.

+

Your Account and Organizations

+

Click your name in the top-right corner to open a menu – here you can edit your account info, create a new organization, switch accounts, or log out. On the ‘Edit Account Info’ page, you can change your personal info, such as your email. You can also click the ‘Budget’ tab to see the full transaction history of your account.

+
+ Edit account +
+ +

The Telegram Ad Platform allows you to be simultaneously logged in to multiple organizations, as well as your personal ad account. To switch accounts, simply click your name in the top-right corner and select ‘Switch to …’ from the menu.

+
+ Switching accounts +
+ +
+

Further Questions

+

The platform is currently running in test mode. We will be expanding this document with more details.

+

Once you've added funds to your account, you will get access to Telegram's dedicated Ad Platform Support.

+
+ +
+
+ + + + + + + + + + + + + + + + + diff --git a/data/promote.telegram.org/guidelines.html b/data/promote.telegram.org/guidelines.html new file mode 100644 index 0000000000..012fd88cfb --- /dev/null +++ b/data/promote.telegram.org/guidelines.html @@ -0,0 +1,313 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
  1. Ad Policies and Guidelines
+
+
+
+

Ad Policies and Guidelines

+ +

These Ad Policies and Guidelines apply to all ads displayed on the Telegram Ad Platform and describe what ad content is allowed on Telegram.

+

Advertisers are responsible for their ads and for complying with these Ad Policies and Guidelines, the Telegram Ad Platform Terms of Service, the Telegram Terms of Service and Privacy Policy.

+
+

1. Ad format
2. Editorial requirements
3. Link format
4. Destination
5. Prohibited content
5.1. Graphic, shocking, or sexual content
5.2. Hate, violence, harassment
5.3. Third party rights
5.4. Deceptive, misleading, or predatory advertising
5.5. Election or political ads
5.6. Gambling
5.7. Deceptive or harmful financial products or services
5.8. Medical services, medications, supplements
5.9. Drugs, alcohol, tobacco, fast food
5.10. Weapons, firearms, explosives, ammunition
5.11. Spam software, malware, hacking
5.12. Products of questionable legality

+
+

1. Ad format

+

Ads can only promote products inside Telegram, such as channels or bots. Each ad consists of an ad text and a button that opens a link to the advertised product. The maximum length of the ad text is 160 characters including spaces.

+

2. Editorial requirements

+

Standard requirements of style, clarity, spelling and punctuation apply to all ads. Numbers, marks and symbols must be used properly. The following is not allowed:

+
    +
  • Profanity or vulgarity, including slur acronyms and spelling variations, in any language, and masked vulgarity (e.g., f**k)
  • +
  • Unrecognizable or unclear meaning, such as overbroad or vague descriptions, repetition of words and phrases
  • +
  • Excessive or gimmicky use of CaPiTaLiZaTiOn, highlighting, s p a c i n g and s,y,m,b,o,l,s, including Unicode art, ASCII art and box-drawing
  • +
  • Intrusive, excessive or gimmicky use of emoji and other emoticons
  • +
  • Line breaks, bullet points, numbering lists
  • +
+

3. Link format

+

In addition to the main ad link submitted in the ‘URL’ field, ads may also include one optional link in the ad text itself, using the format t.me/link or @link. The ad link and the link in the ad text must both lead to the same channel or bot on Telegram.

+

If the destination is a Telegram bot, links may include start parameters for the bot.

+

Links must be used properly. Particularly, the following is not allowed:

+
    +
  • Using more than one link in the ad text
  • +
  • Using any external links, such as URL shorteners or links to any other websites, even if users are ultimately redirected to the channel or bot
  • +
+

4. Destination

+

The destination channel or bot on Telegram must be technically and visually complete and functional, and its content should be consistent with the ad. Destination channels must be public. Particularly, the following is not allowed:

+
    +
  • Destinations solely designed for displaying ads
  • +
  • Unrelated destinations, such as when the destination link doesn’t correspond with the ad text
  • +
  • Invalid or unsupported destinations, such as external links, etc.
  • +
+

5. Prohibited content

+

These Ad Policies and Guidelines prohibit some types of content to ensure a safe and pleasant experience for Telegram users. The following requirements apply to ads on the Telegram Ad Platform and to the products they promote, whether implied or explicit. All examples given are non-exhaustive.

+

5.1. Graphic, shocking, or sexual content

+

Ads must not promote graphic, shocking, or sexual content, products and services.

+

Examples:

+
    +
  • Gruesome, disgusting, or shocking imagery, including gore, bodily fluids, accident photos, graphic details of torture
  • +
  • Nudity, sexually explicit and sexually suggestive content, including excessively exposed intimate body parts, sexual merchandize and entertainment, dating services
  • +
+

5.2. Hate, violence, harassment

+

Ads must not promote hatred, intolerance, harassment, discrimination, violence, or abuse.

+

Examples:

+
    +
  • Violence and its promotion, including supporting organizations or movements with ties to violence
  • +
  • Promoting harassment or bullying, including dehumanizing speech, statements of inferiority, defamatory content, disclosing contact details or personal data
  • +
  • Discrimination towards individuals, groups, or organizations, including hateful messages on the basis of race, religion, color, national or ethnic origin, age, beliefs, sexual orientation or practices, physical or mental abilities
  • +
+

5.3. Third party rights

+

Ads and promoted content must not violate third party rights, including trademark, copyright, privacy or other personal or proprietary rights.

+

Examples:

+
    +
  • Unauthorized distribution of copyrighted content, including pirated software and content such as movies, music, or books
  • +
  • Plagiarism, including impersonating public figures or brands, misusing brand logos or assets, e.g., the Telegram logo
  • +
+

5.4. Deceptive, misleading, or predatory advertising

+

Ads must not contain information that is false, misleading or simply does not match the product. This includes false statements, claims or offers, together with predatory advertising practices.

+

Examples:

+
    +
  • Clickbait or similar unrealistic statements, including you-just-won-X claims, shock or scare tactics
  • +
  • Exaggerated comparisons and absolute claims, including unsupported use of comparatives and superlatives: “highest incomes”, “best company”, and comparing your brand to a different one
  • +
  • Asserting personal attributes, including by using words ‘your’, ‘other’ and derivatives, such as “We know that your family prefers Telegram”
  • +
  • Capitalizing on tragedies, health crises or acts of mass violence
  • +
+

5.5. Election or political ads

+

Ads must not promote political campaigns, elections, political parties, movements, or candidates.

+

Examples:

+
    +
  • Advocating for or against a politician, political party, or political movement
  • +
  • Exploiting political controversy, including encouraging political unrest, disrupting public order
  • +
+

5.6. Gambling

+

Ads must not promote online or offline gambling, gaming, or casino-based activities involving real money, prizes, or goods of any value.

+

Examples:

+
    +
  • Games of chance or casinos, including sports betting, lotteries, bingo, fantasy sports
  • +
  • Tips, odds, forecasts, including sports picks, odds calculators
  • +
+

5.7. Deceptive or harmful financial products or services

+

Ads must not promote content, products, or services associated with deceptive or harmful financial practices.

+

Examples:

+
    +
  • Payday loans, cash loans, predatory lending, including short-term loans
  • +
  • Get-rich-quick offers, pyramid schemes, multilevel marketing, including offers of investment with guaranteed return, claims on providing insider tips on investments
  • +
+

5.8. Medical services, medications, supplements

+

Ads must not promote content, products, or services related to health and wellness.

+

Examples:

+
    +
  • Nutrition products, including weight loss products, herbal drugs, dietary supplements, vitamins, pregnancy, and fertility-related products
  • +
  • Medical devices, services, and treatments, including medical masks, plastic surgeries, pregnancy termination, therapies
  • +
  • Products with claims of healthful, curative or stimulating effects
  • +
  • Prescriptions for medications
  • +
+

5.9. Drugs, alcohol, tobacco, fast food

+

Ads must not promote psychoactive substances, alcoholic beverages, tobacco products or fast food.

+

Examples:

+
    +
  • Alcoholic beverages, including home brewing kits, non-alcoholic beer
  • +
  • Tobacco, including e-cigarettes, rolling papers, chewing tobacco
  • +
  • Recreational drugs, including equipment and paraphernalia, e.g., pipes, bongs
  • +
  • Instructions on producing drugs
  • +
  • Fast food, including fast-food chains, etc.
  • +
+

5.10. Weapons, firearms, explosives, ammunition

+

Ads must not promote the sale of weapons, explosives or ammunition, or any related content.

+

Examples:

+
    +
  • Firearms, including sporting, recreational guns, or any antique functioning guns that can cause harm
  • +
  • Ammunition or accessories, including any firearm parts or components, even unfinished, such as magazines, scopes, silencers
  • +
  • Knives and other melee weapons, including pepper spray, daggers, axes
  • +
  • Explosives, including bombs, grenades, fireworks, or firecrackers
  • +
  • Instructions on assembling or acquiring any product covered in this section
  • +
+

5.11. Spam software, malware, hacking

+

Ads must not promote content, products, or services that facilitate unsolicited communications, are intended to harm or gain unauthorized access to a user's device, or cause deceptive or unexpected consequences.

+

Examples:

+
    +
  • Social media growth manipulation, including encouraging growth of social media profiles
  • +
  • Incentivized or automated clicks, including requests to perform actions on websites or services, complete online surveys
  • +
  • Services for generating automated traffic, including services for inflating metrics/followers, sending automated content to social media platforms or other services
  • +
  • Phishing, including promotion of services that trick a user into providing personal or other information
  • +
  • Software causing deceptive or unexpected consequences, including modified apps containing malware, viruses, or any other malicious code
  • +
+

5.12. Products of questionable legality

+

Ads must not promote content, products, or services of questionable legality.

+

Examples:

+
    +
  • Forgery, including fake IDs, passports, visas, official documents
  • +
  • Human-trafficking, including marriage brokering
  • +
  • Stolen or leaked data, including carding, passwords to subscription services
  • +
  • Sale of body parts, including bodily fluids
  • +
  • Counterfeit products, including fake or bootleg goods, inauthentic artwork or digital goods, counterfeit currency
  • +
+
+

All examples on this page are non-exhaustive.

+
+ +
+
+ + + + + + + + + + + + + + + + + diff --git a/data/promote.telegram.org/tos.html b/data/promote.telegram.org/tos.html new file mode 100644 index 0000000000..0dea1f9f50 --- /dev/null +++ b/data/promote.telegram.org/tos.html @@ -0,0 +1,253 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
  1. Telegram Ad Platform Terms of Service
+
+
+
+

Telegram Ad Platform Terms of Service

+ +

1. TERMS AND DEFINITIONS

+

1.1. Account – a personalized record of the Advertiser within the Telegram Ad Platform with unique access details, containing the information on the Services, Statistics, Advertiser’s information, Ads and their status, Balance, operating tools and features.

+

1.2. Ad – an advertisement created using the Telegram Ad Platform that specifies where, how, when and which Advertising Materials are to be displayed, including the type and format of the Advertising Materials, their placement (particular channels, groups, games), CPM, Maximum Budget.

+

1.3. Advertiser – the person or entity who has entered into the Agreement with the Company.

+

1.4. Advertising Materials – any graphic/media file and/or any and all accompanying information supplied by the Advertiser to the Company to be displayed for advertising purposes in Publication Spaces. The Advertiser retains all rights, whether owned by the Advertiser or by a third party, and/or licensed or otherwise used by the Advertiser, in relation to any Advertising Materials and grants to the Company a worldwide, non-sublicensable, non-exclusive, royalty-free license to use, serve, copy, reproduce, distribute and display the Advertising Materials, in any known, agreed or hereafter developed manner.

+

1.5. Agreement – the present Terms of Service along with the Advertising Agreement reached between the Company and the Advertiser.

+

1.6. Auction – the automated system that uses certain algorithms to determine the best offered CPM in relation to an Ad for the provision of the Services.

+

1.7. Balance – the amount of money which is available on the Account and can be spent on the Services.

+

1.8. Confidential Information – all information of a Party including, without limitation, information and/or personal data provided by a Party, its related corporations, affiliates, employees, agents, representatives, advisors, or consultants, whether disclosed or communicated verbally, in writing or in any other tangible form, and whether relating to a Party’s business, operations, processes, plans, requirements, inventions, product or service information, pricing, know-how, design rights, trade secrets, software, systems, market opportunities, customers and business affairs.

+

1.9. CPM – Cost-Per-Mille, the price for one thousand Impressions of an Ad.

+

1.10. Company – the legal entity which belongs to Telegram group of companies and has a right to enter the Agreement with the Advertiser for the Services.

+

1.11. Data Protection Laws – the following legislations to the extent applicable from time to time: (a) national laws implementing the Directive on Privacy and Electronic Communications (2002/58/EC) (as amended by Directive 2009/136); (b) the General Data Protection Regulation (2016/679) (the GDPR) and the UK GDPR and any national law supplementing the GDPR or UK GDPR (such as, in the UK, the Data Protection Act 2018), and (c) any other data protection or privacy laws, regulations, or regulatory requirements, guidance and codes of practice applicable to the processing of personal data (as amended and/or replaced from time to time).

+

1.12. Impression – each occurrence of a display of an Ad to a user in a Publication Space, as evidenced by Statistics.

+

1.13. Improper Advertising – any act or omission which violates the Consumer Protection from Unfair Trading Regulations 2008 or any other applicable laws or regulations relating to advertising or marketing standards.

+

1.14. Intellectual Property Rights – trademarks, service marks, rights in trade names, business names, logos or get-up, goodwill and the right to sue for passing off, patents, supplementary protection certificates, rights in inventions, registered and unregistered design rights, copyrights (including rights in software), database rights, image rights and rights to personality, rights in domain names and URLs and social media presence accounts, and all other similar rights in any part of the world (including in confidential information, trade secrets and know-how) and whether registered or not, including, where such rights are obtained or enhanced by registration, any registration of such rights and applications and rights to apply for such registrations.

+

1.15. Maximum Budget – the maximum amount of funds, confirmed by the Advertiser, that can be deducted from the Balance for displaying a particular Ad in a Publication Space. Reaching the Maximum Budget shall result in the Ad being put on hold.

+

1.16. Publication Space – a digital space for Advertising Materials made available by the Company including, without limitation, in Telegram channels, Telegram groups and Telegram games.

+

1.17. Reporting Period – calendar month. The first Reporting Period commences on the date of signing of the Agreement and lasts up to the last day of the relevant calendar month (as an example, June 10 – June 30), the last Reporting Period commences on the first day of the relevant calendar month and lasts up to the date of the Agreement’s termination (as an example, June 01 – June 15).

+

1.18. Services – the display of the Advertising Materials in the context of a particular Ad, in the relevant Publication Space.

+

1.19. Statistics – a detailed report on the Advertiser’s Ads, which specifies the scope of the Services provided. It includes the Advertising Materials data, the cost of the Services in the Reporting Period and other data generated by the Company upon the results of automated checks.

+

1.20. Telegram App – a cloud-based mobile and desktop messaging app with a focus on security and speed, including but not limited to mobile apps for iPhone/iPad/Android/Windows phone, desktop apps for PC/Mac/Linux/macOS/Web-browser, Telegram web and all other interfaces and/or versions which exist or will be created in future.

+

1.21. Telegram Ad Platform – the software solution which provides the Advertiser with the opportunity to create Ads that participate in Auctions for Publication Spaces, control and terminate their Ads, and access the relevant Statistics within the Account.

+

1.22. Telegram Ad Policies and Guidelines – Telegram Ad Policies and Guidelines as available at: https://promote.telegram.org/guidelines.

+

1.23. Telegram Privacy Policy – Telegram Privacy Policy as available at: https://telegram.org/privacy.

+

1.24. Telegram Terms of Service – Telegram Terms of Service as available at: https://telegram.org/tos.

+

1.25. Terms of Service – Telegram Ad Platform Terms of Service as available at: https://promote.telegram.org/tos.

+

2. REQUIREMENTS FOR ADVERTISING MATERIALS

+

2.1. Advertising Materials shall be in compliance with all applicable laws, rules and regulations, present Terms of Service, Telegram Terms of Service, Telegram Privacy Policy, Apple App Store terms and rules as may be applicable, and Google Play terms and rules as may be applicable.

+

2.2. Advertising Materials shall be in compliance with Telegram Ad Policies and Guidelines. Advertising Materials must not relate to the topics as indicated at Ad Policies and Guidelines/Prohibited Content.

+

2.3. The Company reserves the right to update Telegram Ad Policies and Guidelines and the list of topics at clause 2.2 from time to time.

+

3. RIGHTS AND OBLIGATIONS

+

3.1. The Company shall:

+

(a) pursuant to and in accordance with the Advertiser’s instructions submitted via the Telegram Ad Platform in relation to a particular Ad, provide the Services whenever the Advertiser’s CPM bid wins the Auction for a particular Publication Space, for as long as the Ad’s Maximum Budget and the Advertiser’s Balance allow.

+

3.2. The Company may, at its sole discretion:

+

(a) conduct an audit of the Advertising Materials to verify their compliance with all applicable laws, rules and regulations, present Terms of Service, Telegram Ad Policies and Guidelines, Telegram Terms of Service, Telegram Privacy Policy, Apple App Store terms and rules as may be applicable, and Google Play terms and rules as may be applicable. The Company shall not be bound by any time frames in conducting an audit under this clause 3.2(a);

+

(b) terminate or suspend the Services without any liability in the event that the Advertising Materials, as may be evidenced by the results of any audit undertaken by the Company under clause 3.2(a) above, are in conflict with any applicable laws, rules and regulations, present Terms of Services, Telegram Ad Policies and Guidelines, Telegram Terms of Service, Telegram Privacy Policy, Apple App Store terms and rules as may be applicable, and Google Play terms and rules as may be applicable, and inter alia, contain any elements of Improper Advertising, and/or explicitly violate the generally accepted moral and ethical standards, and/or are inconsistent with the Company’s values and principles, including the Company’s stance on fundamental human rights, freedom of speech and data privacy;

+

(c) request any supporting documentation regarding Advertising Materials, including, without limitation, the relevant licenses/permits/certificates for licensed goods/services, agreements with Advertiser’s customers for distribution of goods/services which contain Intellectual Property Rights, and suspend provision of Services until and unless such information is provided to the satisfaction of the Company;

+

(d) request any supporting documentation on Advertiser’s legal status, including, but not limited to, its constitutional documents, tax numbers, residency and related details, powers and rights of representatives, and suspend provision of Services until and unless such information is provided to satisfaction of the Company;

+

(e) transfer any information concerning Advertiser and the Advertising Materials which is required to be disclosed by any regulatory authority, any auditor of the Parties, by judicial or administrative process or otherwise by applicable law or regulation;

+

(f) change the parameters of the Services in the Telegram Ad Platform and, in particular, change the list of available Publication Spaces and minimum CPM; and

+

(g) make changes to these Terms of Service at any time by uploading an updated version of the Terms of Service to its website, which can be accessed here: https://promote.telegram.org/tos.

+

3.3. The Advertiser shall:

+

(a) be fully responsible for the compliance of the placed Advertising Materials with all applicable laws, rules and regulations, present Terms of Services, Telegram Ad Policies and Guidelines, Telegram Terms of Service, Telegram Privacy Policy, Apple App Store terms and rules as may be applicable, and Google Play terms and rules as may be applicable;

+

(b) promptly provide the Company with any information, documents and other materials that the Company may request from time to time in accordance with clauses 3.2(c) to 3.2(e) above;

+

(c) promptly inform the Company of all changes impacting the Company under this Agreement, including but not limited to the Advertiser’s business, contact details, bank details and authorized persons;

+

(d) mark the Advertising Materials, if so required by applicable law, with an indication of the age category of persons for whom it is addressed and any other indications. The Advertiser is solely responsible for correct labelling of the Advertising Materials; and

+

(e) not permit any third party to put forward a bid at an Auction using its Account.

+

3.4. The Advertiser may:

+

(a) place requests for the Services by creating Ads on the Telegram Ad Platform;

+

(b) use the Telegram Ad Platform interfaces to interact with their Ads, e.g. launch Ads and put them on hold, submit changes to the CPM and Maximum Budget of Ads, etc. Without prejudice to clause 3.2(a), changes will be usually applied after fifteen (15) minutes, but no later than in sixty (60) minutes after the request is registered by the Telegram Ad Platform; and

+

(c) be informed of the Statistics.

+

4. LIABILITY

+

4.1. In case of non-compliance or inadequate performance by the Parties of their respective obligations under this Agreement, the Parties will incur liability as provided for under applicable law; except that the Company shall not be liable for failure to fulfill or the improper fulfillment of the Agreement caused by breakdown of telecommunication and energy networks, effects of malicious software or fraudulent acts by the third parties.

+

4.2. The Company undertakes all possible effort to provide the best Services it can. Notwithstanding clause 4.1 above, however, these Services are provided "as is” and “as available” and the Company makes no guarantees that the Services always will be error-free, or that they will function without delays and disruptions. The Company disclaims all warranties, whether express or implied, including the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.

+

4.3. Without prejudice to the generality of clause 4.1 above, the Advertiser shall be liable for security of the access details to the Account and shall compensate the Company for any losses related to such use by the persons not authorized to act on behalf of the Advertiser. For the avoidance of doubt, where the Advertiser is in violation of its obligations under this Agreement, the Advertiser shall reimburse the Company for any and all losses incurred as a result of such violation.

+

4.4. The Company's total aggregate liability under this Agreement whether in contract, tort (including negligence), under a warranty, undertaking or representation under statute or otherwise, for any losses or damages suffered or incurred by the Advertiser shall not exceed the total amount of the Advertiser's Balance spent in the previous calendar year.

+

4.5. The Company shall not be liable under or in connection with this Agreement whether in contract, tort (including negligence), under a warranty, undertaking or representation under statute or otherwise, for any indirect or consequential losses, any loss of business, business opportunities or goodwill, or any loss of revenue, savings or profits, whether actual or prospective or for any punitive damages, howsoever arising, whether such losses or damage were foreseeable or in the contemplation of the Advertiser or the Company.

+

4.6. Nothing in this Agreement shall limit or exclude any liability for (i) death or personal injury resulting from negligence, (ii) fraud, fraudulent misrepresentation or willful default, or (iii) for any other liability to the extent it cannot be lawfully excluded or limited.

+

5. WARRANTIES AND INDEMNIFICATION

+

5.1. Warranties – Each Party warrants to the other that:

+

(a) to the best of its knowledge, nothing in this Agreement violates any applicable law, including Data Protection Laws;

+

(b) it has the necessary financial resources to perform its obligations under this Agreement;

+

(c) it has the requisite legal right, power and authority to execute, deliver, and to perform its obligations under this Agreement;

+

(d) this Agreement constitutes its binding obligations in accordance with its terms; and

+

(e) nothing contained in this Agreement will result in a breach of any provision of its constitutional documents or result in a breach of any agreement, license or other instrument, order, judgment or decree of any court or governmental body to which it is bound.

+

5.2. Indemnity – The Advertiser hereby indemnifies, defends and holds harmless on an after tax basis the Company and each of the companies in the Company’s group and its and their directors, employees, officers, contractors, agents and any other related parties (each an Indemnified Person) from and against:

+

(a) all or any claims, actions, proceedings, liabilities, investigations, demands, judgements and/or awards (in each case whether or not successful, compromised or settled and whether joint or several) (together Claims and each a Claim) which may be asserted, established, instituted, made, pending, threatened or alleged against or otherwise involve an Indemnified Person in any jurisdiction by any person whatsoever, including without limitation by a third party or by any supervisory or regulatory agency or body; and/or

+

(b) all or any loss, damage, cost, liability, demand, charge, expense or tax (including, without limitation, (i) any direct, indirect or consequential losses, loss of profit, loss of business, business opportunities or goodwill, loss of reputation, (ii) all interest, penalties, legal costs and all other professional costs and expenses, (iii) all losses suffered or incurred in investigating, preparing for or disputing or defending or providing evidence in connection with or settling any Claim and/or in establishing its right to be indemnified pursuant to this clause 5.2 and/or in seeking advice regarding any Claim and/or in any way related to or in connection with the indemnity contained in this clause 5.2) (together Losses and each a Loss) which may be suffered or incurred by an Indemnified Person,

+

which, directly or indirectly, arise out of, or are attributable to, or are connected with the performance of the Agreement, the Ads, the Advertising Materials, the advertised goods or services or consumption thereof, or non-compliance by the Advertiser with any terms of this Agreement.

+

5.3. Conduct of claims

+

(a) Each Indemnified Person shall give notice as soon as reasonably practicable to the Advertiser of any action commenced against it after receipt of a written notice of any Claim or the commencement of any action or proceeding in respect of which a Claim for indemnification may be sought hereunder, insofar as may be consistent with any obligation of confidentiality or other legal or regulatory obligation which that Indemnified Person owes to any third party or to any regulatory request that has been made of it, but failure to so notify the Advertiser shall not relieve the Advertiser from any liability or any obligation to indemnify the Advertiser and in any event shall not relieve the Advertiser from any liability which the Advertiser may have. Legal advisers to any Indemnified Person shall be selected by such Indemnified Person in its absolute discretion.

+

(b) The Advertiser shall, at the request of any Indemnified Person, conduct the defense of any such action and shall do so at its own expense; provided, however, that legal advisers to the Advertiser shall be reasonably satisfactory to the Indemnified Persons and shall not (except with the consent of the Indemnified Person) also be legal advisers to the Indemnified Person. If the Advertiser conducts the defense of an action, it shall provide each relevant Indemnified Person with all relevant information in respect of any such action on a timely basis (including, without limitation, on request) and the Advertiser will take such action, in each case, as each relevant Indemnified Person may reasonably request.

+

(c) The Advertiser shall not, without the prior written consent of the Indemnified Persons, settle or compromise or consent to the entry of any judgment with respect to any litigation, or any investigation or proceeding by any supervisory or regulatory agency or body, commenced or threatened, or any claim whatsoever in respect of which indemnification could be sought under clause 5.2 (whether or not the Indemnified Persons are actual or potential parties thereto), unless such settlement, compromise or consent: (i) includes an unconditional release of each Indemnified Person from all liability arising out of such Claim; and (ii) does not include a statement as to or an admission of fault, culpability or a failure to act by or on behalf of any Indemnified Person.

+

(d) The provisions of this clause 5 shall not affect or be affected by any other agreement to which any Indemnified Person is a party with respect to indemnification.

+

5.4. Contracts (Rights of Third Parties) Act 1999 – Each Indemnified Person will have the right under the Contracts (Rights of Third Parties) Act 1999 to enforce its rights against the Advertiser under this clause 5; provided that only the consent of the specified parties to the Agreement shall be required to make any amendment of the Agreement or give any waiver under the Agreement.

+
+ +
+
+ + + + + + + + + + + + + + + + + diff --git a/data/telegram.org.html b/data/telegram.org.html new file mode 100644 index 0000000000..c8aca89b2d --- /dev/null +++ b/data/telegram.org.html @@ -0,0 +1,283 @@ + + + + + Telegram Messenger + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ + + + + + +
+ +

Why Telegram?

+ +
+
+
+
+

Simple

+
Telegram is so simple you already know how to use it.
+
+
+ +
+
+
+

Private

+
Telegram messages are heavily encrypted and can self-destruct.
+
+
+ +
+
+
+

Synced

+
Telegram lets you access your chats from multiple devices.
+
+
+ +
+
+
+

Fast

+
Telegram delivers messages faster than any other application.
+
+
+ +
+
+
+

Powerful

+
Telegram has no limits on the size of your media and chats.
+
+
+ +
+
+
+

Open

+
Telegram has an open API and source code free for everyone.
+
+
+ +
+
+
+

Secure

+
Telegram keeps your messages safe from hacker attacks.
+
+
+ +
+
+
+

Social

+
Telegram groups can hold up to 200,000 members.
+
+
+ +
+
+
+

Expressive

+
Telegram lets you completely customize your messenger.
+
+
+
+
+ +
+ +
+
+
+ + + + + + + + diff --git a/data/telegram.org/android.html b/data/telegram.org/android.html new file mode 100644 index 0000000000..b3446fa6dc --- /dev/null +++ b/data/telegram.org/android.html @@ -0,0 +1,79 @@ + + + + + Telegram for Android + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+ + +

Telegram for Android

+
+
You can download Telegram for your Android device here. This version has fewer restrictions and receives automatic updates directly from telegram.org
+ + + +
+

How to Install Telegram?

+
This video shows how to install Telegram on your Android device. See this page for detailed steps on various versions of Android.
+
+ +
+
More comfortable with installing apps
from the Google Play Store?

Download Telegram from Google Play
+
+
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog.html b/data/telegram.org/blog.html new file mode 100644 index 0000000000..84769c8768 --- /dev/null +++ b/data/telegram.org/blog.html @@ -0,0 +1,268 @@ + + + + + Telegram Blog + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+

Telegram News

+
+
+ +
+

Video Stickers, Better Reactions and More

+
This update brings easy-to-make video stickers, better reactions with more compact animations and extra emoji, a button to review unseen…
+
+
Jan 31, 2022
+
+ +
+

Reactions, Spoilers, Translation and QR Codes

+
Telegram's 12th update of the year introduces reactions, message translation, themed QR codes, hidden text (spoilers), and more.
+
+
Dec 30, 2021
+
+ +
+

Protected Content, Delete by Date, Device Management and More

+
Today's update brings tools to prevent others from saving content from groups and channels, the ability to delete messages for specific…
+
+
Dec 7, 2021
+
+ +
+

Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More

+
Today's update brings new ways to find memories in shared media with accelerated scrolling…
+
+
Nov 3, 2021
+
+ +
+

Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording

+
Today's update lets you set different themes for individual chats, share your feelings with…
+
+
Sep 19, 2021
+
+ +
+

Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More

+
Telegram 8.0 brings live streams with unlimited viewers to groups and channels, options to…
+
+
Aug 31, 2021
+
+ +
+

Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More

+
This update takes video to the next level. Group video calls now have up to 1000 viewers,…
+
+
Jul 30, 2021
+
+ +
+

Group Video Calls

+
Today's update lets you turn on your camera or share your screen during Voice Chats in groups – on all devices, including tablets and desktops. This brings voice chats to a whole new…
+
+
Jun 25, 2021
+
+ +
+

Animated Backgrounds

+
In addition to Group Video Calls, this update adds animated backgrounds and message sending animations, as well as a new menu button for bots, new ways to import stickers, reminders…
+
+
Jun 25, 2021
+
+ +
+

Payments 2.0, Scheduled Voice Chats, New Web Versions

+
This update brings Payments 2.0 for all Telegram chats, Scheduling and Mini Profiles for Voice Chats, new versions of Telegram Web for…
+
+
Apr 26, 2021
+
+ +
+

Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

+
Voice Chats first appeared in December, adding a new dimension of live talk to Telegram groups. Starting today, they become available in…
+
+
Mar 19, 2021
+
+ +
+

Auto-Delete, Widgets and Expiring Invite Links

+
This update brings an auto-delete timer for messages in any chat, as well as new flexible invite links and faster access to your chats…
+
+
Feb 23, 2021
+
+ +
+

Moving Chat History from Other Apps

+
Over 100 million new users joined Telegram this January, seeking more privacy and freedom. But what about the messages and memories that remain in older apps? Starting today, everyone…
+
+
Jan 28, 2021
+
+ +
+

Voice Chats Done Right

+
Today, Telegram groups get an entire new dimension with Voice Chats – persistent conference calls that members can join and leave as they please. Our 12th update in 2020 brings them…
+
+
Dec 23, 2020
+
+ +
+

Pinned Messages 2.0, Improved Live Locations, Playlists and More

+
Halloween is just around the corner and we've assembled choice tools to help organize your trick-or-treating. Practice your voodoo skills…
+
+
Oct 30, 2020
+
+ +
+

Search Filters, Anonymous Admins, Channel Comments and More

+
Your personal Telegram Cloud is endless and full of spicy memes – to help you find your way around it, we're introducing Search Filters.…
+
+
Sep 30, 2020
+
+ +
+

Video Calls and Seven Years of Telegram

+
Today marks seven years of Telegram. In 2013, we began as a small app focused on secure messaging and have since grown into a platform with over 400M users. Now this platform also…
+
+
Aug 14, 2020
+
+ +
+

Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More

+
Today's update brings Profile Videos along with improved People Nearby features, unlimited file sharing with up to 2 Gigabytes per file…
+
+
Jul 26, 2020
+
+ +
+

Video Editor, Animated Photos, Better GIFs and More

+
In 2015, Telegram released the most powerful photo editor to be implemented in a messaging app, letting you enhance image quality and add…
+
+
Jun 4, 2020
+
+ +
+

400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests

+
Telegram has reached 400,000,000 monthly users, up from 300 million a year ago. Every day…
+
+
Apr 24, 2020
+
+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/200-million.html b/data/telegram.org/blog/200-million.html new file mode 100644 index 0000000000..c3b6ab458c --- /dev/null +++ b/data/telegram.org/blog/200-million.html @@ -0,0 +1,222 @@ + + + + + 200,000,000 Monthly Active Users + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

200,000,000 Monthly Active Users

+ +
+ +
+ +

Within the last 30 days, Telegram was used by 200,000,000 people. This is an insane number by any standards. If Telegram were a country, it would have been the sixth largest country in the world.

+
+ +
+ +

We owe reaching this milestone to you alone – our users. We have never promoted Telegram with ads, so all these 200 million people are on Telegram because you invited them to join.

+

This is why you – our users – have been and will always be our only priority. Unlike other popular apps, Telegram doesn’t have shareholders or advertisers to report to. We don’t do deals with marketers, data miners or government agencies. Since the day we launched in August 2013 we haven’t disclosed a single byte of our users' private data to third parties.

+

We operate this way because we don’t regard Telegram as an organization or an app. For us, Telegram is an idea; it is the idea that everyone on this planet has a right to be free.

+
+

Above all, we at Telegram believe in people. We believe that humans are inherently intelligent and benevolent beings that deserve to be trusted; trusted with freedom to share their thoughts, freedom to communicate privately, freedom to create tools. This philosophy defines everything we do.

+
+

This was the reason why Telegram became the first messaging app to roll out end-to-end encryption to tens of millions of users in 2013. This was also the reason why Telegram became the first mainstream messaging app to fully open source its client code, and why Telegram became the first popular messenger to provide 100% open APIs for third party app and bot developers.

+

Over the years, our unconditional trust in people allowed us to do things other apps were hesitant to implement; things such as support for insanely large group chats, unlimited broadcast channels and a free user-generated sticker platform. In all these cases, our belief in people yielded extraordinary results, and users put these tools to great use.

+

What inspires us most is that, judging by the rapid growth of Telegram’s popularity, this belief might be mutual. While we unconditionally believe in people, it turns out 200,000,000 humans also believe in us.

+

Thank you for this – we will always have your back.

+

+
+

+ + +

March 22, 2018,
Pavel Durov

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/6-years.html b/data/telegram.org/blog/6-years.html new file mode 100644 index 0000000000..63918b1cdb --- /dev/null +++ b/data/telegram.org/blog/6-years.html @@ -0,0 +1,1355 @@ + + + + + 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/admin-revolution.html b/data/telegram.org/blog/admin-revolution.html new file mode 100644 index 0000000000..cfb3035f2f --- /dev/null +++ b/data/telegram.org/blog/admin-revolution.html @@ -0,0 +1,261 @@ + + + + + Supergroups 10,000: Admin Tools & More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Supergroups 10,000: Admin Tools & More

+ +
+ +
+ +
+ +
+ +
+

This is an old blog post. In case you missed it, groups can already have up to 200,000 members each.

+
+

With Telegram 4.1, we're increasing the maximum size of supergroups to 10,000 members each. That’s a lot of people packed into one group, and now users and admins can use search to find specific users among them:

+
+ +

Search for members

+
+ +

Admins can also search for members in their channels.

+

With groups as big as 10,000 people – the size of a decent small town – you may be looking for some more powerful management tools. And that’s exactly what Telegram 4.1 gives you.

+ + +

Admin Rights

+

You can now add admins with specific sets of privileges to help you run your community. Choose who among your trusted admins will be able to add new users, manage messages, block members, edit group info, or even add new admins.

+
+ +

Admin rights

+
+ +

Partial Bans

+

Admins who don’t want to completely ban members from their supergroups can now partially restrict their rights in order to stop behavior that's causing problems. You can put nasty users into read-only mode or maybe stop them from sending stickers or media for a certain period of time. Now you can do all of this with absolute precision:

+
+ +

Partial bans

+
+ +

Even robots can get in on the fun. With Bot API version 3.1, you can use admin bots to automatically impose temporary or permanent bans based on member actions. Check out the docs here to start building your robotic police force today.

+

Recent Admin Actions

+

When multiple admins are working with one group, it’s easy to get confused about which admin did what and when (or which admin bot has gone Skynet on your members). That’s why we've added a “Recent Actions” section to the admins page. This section stores a log of all service actions taken in the group in the last 48 hours and is visible to admins only.

+
+
+ +

Recent admin actions

+
+
+ +

Precise filters

+
+ +

Recent actions in supergroups also show messages that were deleted in the last 48 hours and the original versions of edited messages for the same period, so nasty behavior like self-deleted spam will no longer help anyone escape the admins’ wrath.

+

Sharing and Android Pay

+

In other news, Telegram 4.1 for iOS brings you an improved sharing extension. When sharing stuff from other apps to Telegram you can add an optional comment and select multiple recipients easily. 3D Touch on the app icon to see some new actions, including taking a photo/video and sending it to multiple recipients.

+
+ +

New sharing extension

+
+ +

On Android, Telegram 4.1. gets you Android Pay support for Bot Payments and improved media selection – photos and videos are now shown together when sharing from the attachment menu or gallery.

+

Free speech

+

This update also features anti-censorship tools such as the ability to set up a Proxy server in the “Data and Storage” section of the Settings.

+

We believe in free and secure communication. It’s our responsibility to offer technology to defend our users’ right to privacy and freedom of speech around the world.

+

June 30, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/albums-saved-messages.html b/data/telegram.org/blog/albums-saved-messages.html new file mode 100644 index 0000000000..b61f9fc5fd --- /dev/null +++ b/data/telegram.org/blog/albums-saved-messages.html @@ -0,0 +1,268 @@ + + + + + Albums, Saved Messages and Better Search + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Albums, Saved Messages and Better Search

+ +
+ +
+ +
+ +
+ +

Starting with Telegram 4.5, whenever you send multiple photos or videos they are grouped into albums. Each album can include up to 10 photos or videos, arranged in the chat as elegantly proportioned thumbnails. They will also result in one notification instead of ten on the recipient’s side.

+
+
+ +
+
+ +

Photo Order

+

From now on, you can control the order in which photos are sent. Each photo you choose for sharing will show its sequence number. This makes it easy to double check that your “before-and-after” pics will be sent in the correct order.

+

Multiple Profile Photos

+

When viewing a photo from an album, you’ll see other pictures from the same group as thumbnails in the lower part of the screen. Profile photos are now also displayed this way, which makes them much easier to navigate.

+
+
+ +
+
+ +

Saved Messages

+

You can now bookmark important messages by quickly forwarding them to Saved Messages – your personal cloud storage for any messages or media you may want to send or forward there. Each saved message has a “go to” button that takes you to the right place in the chat where it was originally posted.

+
+ +

Saved Messages Chat

+
+ +

The Saved Messages chat is always displayed at the top of the list in the sharing and forwarding menus. This makes it easy to save your favorites while keeping things as tidy as before.

+
+ +

Number One in the Sharing Menu

+
+ +

Saved Messages are easy to find: they are accessible both from the Chats list and from the side panel on Android / Settings on iOS.

+

Improved Search

+

Speaking of finding things, we’ve upgraded the global search algorithm used for finding public channels, groups and bots. Now you can search for public channels and bots by their titles, and most popular items will always be displayed first.

+

Pinned Messages in Channels

+

Channel admins can now pin messages to focus their subscribers’ attention on important announcements. This tool can also come in handy if you want to help new subscribers navigate your channel.

+
+ +

Pinned Message

+
+ + +

iOS: New Settings, iPhone X Support

+

Telegram 4.5 comes packed with goodies for iOS users. The Settings screen and the context menu in chats got a makeover. Version 4.5 also works great on iPhone X.

+
+
+ +

Redesigned Settings

+
+
+ +

Edit Settings

+
+ +

And that’s it for today. We hope you enjoy these new features while we’re working on the next update!

+
+

+
+ +

November 15, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-2-0.html b/data/telegram.org/blog/android-2-0.html new file mode 100644 index 0000000000..80f5a9fe0c --- /dev/null +++ b/data/telegram.org/blog/android-2-0.html @@ -0,0 +1,257 @@ + + + + + Telegram 2.0 for Android: Material Design + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram 2.0 for Android: Material Design

+ +
+ +
+ +

Telegram for Android received a massive update today, featuring a full redesign along Android 5.0 material guidelines and adding long awaited features such as instant full-text cloud search, new flexible privacy settings for last-seen timestamps and account self-destruction.

+

Material Design

+

Every screen was updated to make Telegram consistent with Android 5.0 design standards and animations. We've also added support for the new standards on Android 4.x and even on older 2.x devices.

+
+ + + + + +
+
+ + +

Demo

+

Here‘s what Telegram’s new material design looks like in motion on a Google Nexus phone, just to give you a taste of the animations:

+
+
+
+
+
+
+ +
+
+ + +

Instant Full-Text Search

+

You can now find any message you sent or received in Telegram by using the universal search. Tapping a message in search results sends you to its place in your message history. This way you can find stuff even if you only vaguely remember the context.

+
+ + +
+
+ +

The search is much faster than what you have in GMail and other apps. Our technology guarantees that even if your inbox grows to several hundred thousands of messages, instant search will stay just as fast.

+

Hiding Last Seen Time

+

We take privacy very seriously, so we invested a lot of time and effort to make this feature right. As a result, the Who can see your Last Seen time control allows unprecedented precision and flexibility.

+
+ + + +

+
+ +

In fact, it's so good that we wrote a whole separate blog post about it. Read more here:
Privacy Revolution — Last Seen Done Right »

+

Account Self-Destruction

+

Big companies like to accumulate data about their users and keep it for an indefinite time. Telegram is not a commercial organization and we value our disk space greatly. Last year we introduced self-destructing messages, today we are adding self-destructing accounts.

+

From now on, if you stop using Telegram and do not login for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct – with options ranging from 1 month to 1 year.

+

..but I'm on iOS

+

Most of these new features are also avaible to iOS fans among Telegram users — except for material design of course. In order to maintain the balance, we're also adding a few nifty features to our iOS app today. Read all about them here:
The new Telegram for iOS — GIF search and more »

+

+ +

The Telegram Team,
November 19, 2014

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-gif.html b/data/telegram.org/blog/android-gif.html new file mode 100644 index 0000000000..d162095dea --- /dev/null +++ b/data/telegram.org/blog/android-gif.html @@ -0,0 +1,218 @@ + + + + + GIF and Image Search on Android + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

GIF and Image Search on Android

+ +
+ +
+ +

One of the best beloved features of our iOS app finally comes to Telegram for Android. You can now easily search the web for GIFs and images and send them to your friends.

+

To do this, simply open the Gallery attachment menu — you will find the new Search Web and Search GIF tabs at the top.

+
+ + + + + + +
+
+ +

Your recent gifs and images will be saved, so you can send them again with just a few taps. This is very useful when you're out of words and emoji are just not enough.

+

+ +

Stay tuned for more updates this year!

+

December 20,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-themes.html b/data/telegram.org/blog/android-themes.html new file mode 100644 index 0000000000..0f0410c4ab --- /dev/null +++ b/data/telegram.org/blog/android-themes.html @@ -0,0 +1,246 @@ + + + + + Custom Themes + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Custom Themes

+ +
+ +
+ +
+ +
+ +

We believe in freedom. This is why Telegram is a free and open platform – for stickers, for bots, and even for third-party client apps. We believe that if we give you freedom, you’ll know what to do with it.

+

Starting today, 85% of Telegram users can completely change what Telegram looks like for them. We are rolling out Custom Themes on Android, and will later support them on less popular platforms.

+

To switch to a different theme or create a new one, go to Settings > Theme. We‘ve included a Dark Theme in that menu for those of you who don’t want to use Telegram as a flashlight in dark places.

+
+
+ +

The new dark theme

+
+
+ +

Easy on the eyes

+
+ +

Create Your Own

+

We've also added a Theme Editor to the app. You can now create new themes and easily share them with other users.

+
+
+ +

Choose an element

+
+
+ +

Pick a color

+
+ +

Just like stickers and bots, Telegram themes are part of an open platform, so anybody can create a theme and dazzle the world with new colors and backgrounds. Here's another example of a theme created by our users:

+
+
+ +

Theme preview: Chats list

+
+
+ +

Chat screen

+
+ +

Check out the @AndroidThemes and Desktop Themes channels for more new themes made by Telegram users.

+

If you're using our iOS app, hold on for a couple of weeks. You‘ll get themes eventually, but for now we’re building something different for you – and it’s truly epic.

+

+ +

February 20, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-wear-2-0.html b/data/telegram.org/blog/android-wear-2-0.html new file mode 100644 index 0000000000..68abc7173b --- /dev/null +++ b/data/telegram.org/blog/android-wear-2-0.html @@ -0,0 +1,224 @@ + + + + + Telegram for Android Wear 2.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram for Android Wear 2.0

+ +
+ +
+ +
+ +
+ +

Google has just unveiled Android Wear 2.0, the latest in smartwatch platforms. It supports standalone apps, so today we're releasing Telegram for Android Wear 2.0. It‘s everything you’d want from a perfect watch app — compact, beautiful, and super-fast.

+
+ +
+ +

Using this tiny yet powerful app, you can browse your chats and quickly reply to messages with voice, text, emoji, or stickers. You can also view your contacts and even create groups right from your watch.

+
+
+ +
+
+ +

The smartwatch app also supports several themes in different colors. By the way, theme support is coming to our main Android app soon, so stay tuned.

+

Telegram for Android Wear 2.0 is available for download on Google Play. If you have Android Wear 2.0 installed on your watch, just search for Telegram in the store.

+

+ +

February 9, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/animated-backgrounds.html b/data/telegram.org/blog/animated-backgrounds.html new file mode 100644 index 0000000000..13126f2520 --- /dev/null +++ b/data/telegram.org/blog/animated-backgrounds.html @@ -0,0 +1,302 @@ + + + + + Animated Backgrounds + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Animated Backgrounds

+ +
+
+
+ +
+ Introducing animated backgrounds and more +
+ +

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 to help keep your account safe, and more.

+

Animated Backgrounds

+

Meet animated backgrounds for chats – first time in a messaging app! These multi-color gradient wallpapers are generated algorithmically and move beautifully every time you send a message.

+
+ +
+ +

Our designers added these smooth, energy-efficient animations to all default themes.

+
+

You can find more animated backgrounds in Settings. Android: Chat Settings > Change Chat Background. iOS: Appearance > Chat Background.

+
+

Creating & Sharing Backgrounds

+

In case the default options are not enough, it's super-easy to create your own animated backgrounds. Choose three or four colors to unlock the animation, then add an optional pattern for extra style.

+
+ +
+ +

When ready, share your animated wallpapers with friends and family to upgrade them to a new level of messaging experience.

+

Message Sending Animations

+

Stickers and emoji now seamlessly hop from your keyboard into the chat – with lightweight animations that won’t affect your battery.

+

On iOS, this also applies to media you send from the attachment panel, and even text messages. Your input text smoothly transforms into the message bubble as it flies into the chat.

+
+ +
+ +

iOS: Semi-Transparency & New App Icons

+

On iOS, backgrounds are now partially visible through the header and the footer in chats, giving the interface a classy new look.

+

Two new gradient app icons are available in Settings > Appearance in addition to the classic blue and black versions:

+
+ Two new app icons on iOS +
+ +

We also added a Telegram Features button at the bottom of the Settings menu on iOS, which opens the Telegram Tips channel. Tips are available in 10 languages, including the newly added Turkish version.

+
+

The same button was already on Android, you can find it in the side menu.

+
+

Login Info Reminders

+

It is essential to keep your Telegram phone number up to date to ensure you can always log in to your account. If your phone number has changed, you can quickly update it right from the new reminder in Settings on iOS.

+
+ Reminder about keeping your phone number up to date +
+ +

Android users will get these reminders in the next update, for now they can simply update their phone number by tapping on it in Settings.

+ + +

Users on all platforms will receive a notification from Telegram each time their Two-Step Verification settings are changed.

+
+

Two-Step Verification on Telegram lets you set up an additional password, which you will need to enter every time you log in to your account.

+
+

Bot Menu

+

We made it easier to communicate with bots, adding a special menu button that lets you browse and send commands. Bots can also change the placeholder in the input field to give you a better idea of what kind of message they are expecting.

+
+ +
+ +
+

Bot developers can now create commands that change based on a user’s interface language and chat type, as well as special commands that only appear in specific chats or for admins.

+

More info is available in the Bot API documentation.

+
+

Importing Stickers

+

The @stickers bot can help you create new sticker packs as well as get usage stats for your stickers.

+

Today we're giving third-party developers the tools to make apps that help people generate new custom unique stickers and import their creations to Telegram in one tap.

+
+ +
+ +
+

If you are a developer interested in making apps that help users create stickers and publish them on Telegram, check out the new Sticker Importing Manual.

+
+

Remember, if you simply want Telegram users to install the stickers you made, you don't need any apps! Just upload your stickers using our bot, then share the link to your pack with others.

+

New animated emoji

+

This update is all about motion, so we couldn't go without new animated emoji. As always, simply send a message with a single emoji to get one of these in a chat:

+
+ +
+ +

Time to try out the new features — while we get back to building more of what you asked for, plus a few surprises we have in mind. Stay tuned.

+
+

Read on to learn about Group Video Calls, if you haven't already.

+
+

+ +

June 25, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/animated-stickers.html b/data/telegram.org/blog/animated-stickers.html new file mode 100644 index 0000000000..07eafcd86b --- /dev/null +++ b/data/telegram.org/blog/animated-stickers.html @@ -0,0 +1,261 @@ + + + + + Animated Stickers Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Animated Stickers Done Right

+ +
+ +
+ +
+ Cover Image +
+ +

We launched stickers back in January 2015. Since then, the Telegram sticker format has been adopted by other apps to reach a total of 2 billion people. Today we're introducing a new format for animated stickers.

+

We asked ourselves: Can animated stickers have higher quality than static ones while taking less bandwidth? The answer turned out to be YES (but only after we told developers they'd get moving cat pictures).

+
+ +
+ + + +

Smooth Animations, Tiny Size

+

Telegram engineers experimented with vector graphics, packaging methods and forbidden magic to create the Lottie-based .TGS format, in which each sticker takes up about 20-30 Kilobytessix times smaller than the average photo.

+

Thanks to various optimizations, animated stickers consume less battery than GIFs and run at a smooth 60 frames per second. If a picture is worth a thousand words, that's 180,000 words per sticker.

+
+ +
+ + + +

Open Platform

+

Naturally, animated stickers are a free platform. All artists are welcome to create new sets and share them with Telegram users.

+

Like its static predecessor, the Telegram animated sticker format is likely to become the new industry standard in messaging. Check out this quick guide to get started.

+
+ +
+ +

Starter Packs

+
+ +To get your conversations moving right away, our artists have created a few sample sets ranging from Rambunctious Rodents to Sentient Snacks. You can find more animated sticker sets in the 'Trending' section of your sticker panel. 🔥 + +

+ +

As always, the fastest way to find a sticker that fits your mood is to type in a relevant emoji – Telegram will immediately suggest matching stickers.

+
+ +
+ +

Keep an eye out for new animated stickers – and our next update.

+

+ +

July 6, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/apple-watch.html b/data/telegram.org/blog/apple-watch.html new file mode 100644 index 0000000000..1572cb68d5 --- /dev/null +++ b/data/telegram.org/blog/apple-watch.html @@ -0,0 +1,225 @@ + + + + + Telegram on Apple Watch + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram on Apple Watch

+ +
+ +
+ +
+

Telegram for iOS reaches version 3.0 today, packed with the Bot Platform, dedicated sticker tabs and our first take on Apple Watch support.

+
+

Finally! Telegram 3.0 arrived with full Apple Watch support. You can view your recent chats and reply to messages with stickers, locations, emoji, preset phrases or dictated text. You can also view user and group profiles, start new chats, and even block users.

+
+ + + + +
+
+ +

Chats on your Apple Watch will show all the content available on Telegram: photos, stickers, locations, documents and videos. For those cases when the watch can‘t handle something, we’ve added a shortcut to easily open any message on your Phone.

+
+ + + + +
+ +

We've made sure that Telegram on Apple Watch does as much as the platform can support right now — and that it does more than any other messaging app out there.

+

+ +

The Telegram Team,
June 24, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/archive-and-new-design.html b/data/telegram.org/blog/archive-and-new-design.html new file mode 100644 index 0000000000..9fa2fa687d --- /dev/null +++ b/data/telegram.org/blog/archive-and-new-design.html @@ -0,0 +1,318 @@ + + + + + Archived Chats, a New Design and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Archived Chats, a New Design and More

+ +
+ +
+ +
+ Introducing archived chats, a new design and more +
+ +

Today's update gives you the tools to sort your messages with archived chats, a new design on Android and a handful of other nifty features to make the most of your messenger.

+

Everything in its place

+

Introducing archived chats, the new tool for spring cleaning in your chat list. Sort your active and inactive chats, separate personal stuff from work or banish annoying contacts to your archive for some spectacular revenge!

+
+ +
+ +

Swipe left on a chat to transfer it to your archived chats folder. When an archived chat gets a notification, it will pop out of the folder and back into your chat list. Muted chats will stay archived forever.

+

You can hide the archive by swiping left on it. See it again by dragging the screen down.

+
+ +
+ +

Pin an unlimited number of chats in your archive to keep your messages in the order you want. When chats pop out of your archive with a notification, you can archive them again to return them to their original place within the folder.

+
+ Pinned chats in the archive +
+ +

Bulk actions for a busy chat list

+

Time is money and money buys cat food, so don't waste time and make the most of the bulk actions in your chat list, now also available on Telegram for Android. Long tap on a chat to open the new menu where you can select multiple chats and then pin, mute, archive or delete them, all faster than ever before.

+
+ +
+ +

Android's new clothes

+

Telegram for Android got a lot slicker, starting with the app's new icon and down to every menu in the app sporting a new design.

+
+ Telegram for Android's new icon +

New app icon

+
+ +
+ Redesigned menus +

Slick new menus

+
+ + +

Selecting messages in chats is now not only more stylish but also more functional – note the new quick forwarding button which appears right under your thumb:

+
+ +
+ +

More info at a glance

+

With the expanded chat list, you can see more text from the messages in your list. Simply select Three lines in the Chat Settings menu to see up to three lines per chat instead of the usual two.

+
+ Chat settings, choose between two or three lines per chat +

Chat list view settings

+
+ +

Share and share a lot

+

Want to share a message far and wide? Pull up the new streamlined sharing menu to cover the entire screen and select your whole gang. And don‘t fret if you’re short on words, the comment field now supports emoji.

+
+ The new sharing menu with online badges and emoji support +

New sharing menu

+
+ +

The new design also makes it easier to share sticker packs.

+
+ Sticker pack viewer with the new sharing buttons +

New sticker pack viewer

+
+ +

You shall not pass

+

Meanwhile on iOS, passcode settings have been made more stylish and more robust to accommodate 6-digit codes, in addition to the previous 4-digit and custom alphanumeric options. Keep it secret, keep it safe 🔒.

+
+ +
+ + +

Another new feature on iOS allows clearing your recently used stickers so nobody can prove how much you love sending funny dog stickers.

+
+ Clear recent stickers on iOS +

Clear recent stickers

+
+ +

We also thought that large emoji feel more natural without chat bubbles and made them look like little stickers instead. Aren't they cute?

+
+ Clear recent stickers on iOS +

New look for large emoji

+
+ +

Easier forwarding, links to messages, online badges

+

Ever selected the wrong chat when forwarding a message? Tap the message snippet above the text box before sending to change where the message is forwarded to.

+
+ Switch recipient when forwarding messages +

Switch recipient

+
+ +

If you'd rather point to a particular spot in a conversation, you can now copy links to messages in private groups and channels – just like you could with public messages. Needless to say, links to private chats will only work for members of their respective communities.

+
+ Copy links to individual messages in a private community +

Links to individual messages

+
+ +

Last but not least, you can now instantly see who's online from the chat list and sharing menu to find out who else might be watching cat videos in the middle of the night.

+
+ Online badges in chats +
+ +

As always, stay tuned for more updates on all our platforms — we look forward to popping back out of your archive with the next version.

+

+ +

May 9, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/autodelete-inv2.html b/data/telegram.org/blog/autodelete-inv2.html new file mode 100644 index 0000000000..bb7290b577 --- /dev/null +++ b/data/telegram.org/blog/autodelete-inv2.html @@ -0,0 +1,299 @@ + + + + + Auto-Delete, Widgets and Expiring Invite Links + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Auto-Delete, Widgets and Expiring Invite Links

+ +
+
+
+ +
+ Auto-Delete, Widgets and Expiring Invite Links +
+ +

This update brings an auto-delete timer for messages in any chat, as well as new flexible invite links and faster access to your chats with home screen widgets. Also, groups can now have unlimited members.

+

Auto-Delete Messages

+

Some conversations aren't meant to last forever, which is why Telegram users can delete messages for all participants in a conversation at any time, without a trace. Since 2013, users can also set a self-destruct timer for messages in Secret Chats.

+

Starting today, you can enable an auto-delete timer in all Telegram chats, which will automatically erase messages for all participants either 24 hours or 7 days after sending.

+
+ +
+ +

Auto-delete only applies to messages sent after the timer is set, earlier messages will stay in the chat history. Unlike in Secret Chats, the countdown starts when messages are sent, not read.

+
+

To enable the timer on Android, tap ⋮ > Clear History then choose a duration.
On iOS, press and hold a message, tap Select > Clear Chat (top-left) > Enable Auto-Delete.

+
+

All messages show a countdown to their deletion time – simply tap on Android or press and hold on iOS to take a look. 🕵️

+
+ Time before expiry +
+ +

In groups and channels, only admins can enable or modify the timer.

+

Home Screen Widgets

+

For instant access to your most important chats, add a Telegram widget to your home screen. The Chat Widget shows a preview of recent messages, while the Shortcut Widget shows only names and profile pictures.

+
+ +
+ +

On Android, chats and messages in the widget will always be up to date, and you can further expand the widget to take up more of your screen. On iOS, widgets will only get fresh data occasionally and can't be expanded – this is due to system limitations.

+
+

To add a widget, press and hold on your home screen, then tap Widgets on Android or the (+) on iOS and search for Telegram.

+
+

Expiring Invite Links

+

Invite links are a quick and easy way to bring 1 or 1 million people to your groups and channels. Along with the main invite link, owners and admins can now create additional links with a limited duration, number of uses, or both.

+
+ +
+ +

Any invite link can be converted into a scannable QR Code to put on everything from brochures to billboards. You can also see which users joined using each invite link to find out where new members came from or which format has been most effective for growth. 🚀

+
+ +
+ +
+

To view and manage invite links, tap to open your Group or Channel's Profile > Edit > Invite Links. Tap (⋮) or (⋯) to convert a link to a QR Code.

+
+

Groups with Unlimited Members

+

Telegram groups allow up to 200,000 members to exchange messages, media and stickers. Groups that are close to the limit can now convert into Broadcast Groups that allow unlimited members.

+

Converting to a Broadcast Group makes it so that only admins can send messages, but members can still join voice chats.

+
+ +
+ +

Broadcast Groups are ideal for large communities, where people can follow along and catch exclusive interviews, news, or just casual talks.

+

Improved Chat Import

+

Our developers are continuing to refine and expand the chat import feature added to Telegram last month. With today’s update, imported messages will now appear sorted by their original date if added to a Telegram chat that is new or has fewer than 1000 messages.

+
+ +
+ +
+

Sorting by original date is currently available when importing to all one-on-one chats, all newly created groups, and smaller existing groups.

+
+

Improved Reporting System

+

Telegram processes millions of user reports each month to make sure the platform is not abused. To help make this more efficient, we will now always ask you to select specific messages when sending a report.

+

Additionally, all reporting options allow you to add a comment to give more context – like when reporting fake accounts.

+
+ +
+ +

And More Animated Emoji

+

A new update always means new animations, so test out the new characters below by sending a single emoji in any chat.

+
+ +
+ +

That's all for today's changes, this message will now delete in 3, 2, 1 … oh. Never mind, this is a blog post, they don't do that yet. 😅

+

+ +

February 23, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/autoplay.html b/data/telegram.org/blog/autoplay.html new file mode 100644 index 0000000000..a10ca780f0 --- /dev/null +++ b/data/telegram.org/blog/autoplay.html @@ -0,0 +1,245 @@ + + + + + Autoplaying Videos, Automatic Downloads and Multiple Accounts + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Autoplaying Videos, Automatic Downloads and Multiple Accounts

+ +
+ +
+ +
+ Autoplaying Videos and New Automatic Download Settings +
+ +

Today's update will make Telegram chats livelier with Autoplaying Videos. Smaller videos will start playing without sound when they reach your screen. To unmute them, simply press the volume buttons on your device.

+
+ +
+ +

If you like to be in control of your data usage, try the new auto-download settings. It‘s easy to see your current settings at a glance and we’ve added a new quick way to switch between Low, Medium and High presets for Mobile, Roaming and Wi-Fi.

+

You can also manually set up automatic downloads by chat type, media type and file size. The app will remember your choices as the Custom preset in case you need to temporarily switch to Low and back — or the other way around.

+

To Each According to Their Needs

+

Default settings for data usage have become more generous but depend on the affordability of mobile data in your country. We know that in some places it's easier to buy an aircraft carrier than download an extra 20MB (looking at you, Ethiopia). Telegram will try to download less data for users in such countries.

+

On the other hand, if you're likely to have a monster data allowance, Telegram will try to save you from tapping the “download” arrow too often.

+

These new default limits for automatic downloads are not set in stone. Starting today, we can change them remotely, based on your feedback and the cost of data in each country.

+

To Log Out or Not to Log Out?

+

New users often bring their logout habits from other apps and don't realize that this is rarely necessary on Telegram. To help them find their way around the app, the logout menu now shows several alternative options to logging out:

+
+ Logout Alternatives +

Logout Alternatives

+
+ + +

Multiple Account Support

+

Some of us have several phone numbers and multiple Telegram accounts: one for work, another strictly personal and a third one provided by benevolent aliens along with instructions to never use it except in a planetary emergency.

+

You can add all these accounts to your app and easily switch between up to 3 phone numbers without logging out.

+
+ Add account +

Add Account in Settings > Edit

+
+ +

If you've added several accounts, you will receive push notifications for all of them. Notifications will include information on which account they were sent to. You can also tap and hold on an account in Settings for a sneak peek of its chats list:

+
+ +
+ +

The multiple accounts feature was born in Telegram for Android and is now also available on iOS. We hope your alter-egos will be pleased.

+

+ +

February 26, 2019,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/backgrounds-2-0.html b/data/telegram.org/blog/backgrounds-2-0.html new file mode 100644 index 0000000000..d84f3ba709 --- /dev/null +++ b/data/telegram.org/blog/backgrounds-2-0.html @@ -0,0 +1,231 @@ + + + + + Chat Backgrounds 2.0: Make Your Own + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Chat Backgrounds 2.0: Make Your Own

+ +
+ +
+ +
+ Telegram 5.3: Introducing the Backgrounds Platform +
+ +

No chat can be dull if you have a really cool chat background. Today's update will ensure you get one. You can now search the web for wallpapers, add effects and then share your backgrounds with friends via links.

+

Telegram backgrounds now support motion and blur effects. You can also set any color as your background, apply a pattern and tweak its intensity.

+
+ +
+ +

Just like before, you can set any photo from your gallery as your chat background. On Android, you can add some extra effects in the built-in photo editor.

+

Share links

+

Having used this new arsenal to create the perfect chat background, you can easily set it to Telegram on all your other devices. What's more, you can infect the rest of the world with your genius by sharing your background via a link, just like this one:
https://t.me/bg/l7jg-vpxmEYBAAAA1e0rNKySlkk

+
+ Message containning a Telegram background +
+ +

Search backgrounds

+

If you don‘t feel very creative and would like to simply set something nice real quick, we’ve added new backgrounds to the official selection.

+

We've also included a background search option. Find your dream wallpaper based on keywords or color and then set it in just a few taps.

+
+ Background Search Results +
+ +

We're also announcing the Instant View 2.0 Template Competition: two months, $300,000+ in prizes, $100 per template. See Instant View Contest 2.0 for details.

+

+ +

January 31, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/bot-revolution.html b/data/telegram.org/blog/bot-revolution.html new file mode 100644 index 0000000000..181e96e086 --- /dev/null +++ b/data/telegram.org/blog/bot-revolution.html @@ -0,0 +1,279 @@ + + + + + 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/bots-2-0.html b/data/telegram.org/blog/bots-2-0.html new file mode 100644 index 0000000000..8450c72736 --- /dev/null +++ b/data/telegram.org/blog/bots-2-0.html @@ -0,0 +1,260 @@ + + + + + Bot Platform 2.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Bot Platform 2.0

+ +
+ +
+ +

At Telegram, we made it our mission to redefine the boundaries of what you can do with your messaging app. Last year we launched the Bot Platform that has unleashed the creativity of thousands of developers.

+

Today we are giving bot developers a whole new dimension with Bots 2.0: inline keyboards, callback and URL buttons, location permissions and on-the-fly message editing. The new bots can also generate any type of content for you to share with friends, including documents, MP3s, videos, stickers, animations and contacts.

+

To give you a taste of the new possibilities, we built some sample bots last weekend – @music, @youtube, @foursquare and @sticker (make sure your Telegram app was updated today before you try them).

+

New Keyboards, New Actions

+

Here's how @music works – it uses an inline keyboard that allows you to interact with it without sending any messages. And it updates its own messages on the fly as you flip through the pages of search results:

+
+
+ +
+
+ +

New Types of Content

+

The @music bot also works in inline mode, which means it can help you send MP3s to any of your chats, right from the input field:

+
+
+ +
+
+ +

Inline bots can now send all types of attachments that are available on Telegram. We suspect you're going to like the @sticker inline bot – it can find you relevant stickers based on emoji.

+

New Mechanics

+

Like the @music bot, @youtube also works in two modes. It uses the new clever chat switching mechanic to connect your Telegram account with YouTube:

+
+
+ +
+
+ +

Once a Youtube account is connected, you can access additional settings via the new menu option above the results.

+

New Permissions

+

Now, @foursquare is an inline bot that utilizes our new location features and helps you send addresses of places and venues nearby. Note how it asks for permission to use your location when you try to send something for the first time:

+
+
+ +
+
+ + +

New Horizons

+

These sample bots are but the beginning. Our Bot API 2.0 allows developers to create fluid and easy-to-use interfaces for powerful bots. And we will be seeing a lot of new ones in the coming months, after all, 2016 is the year of bots.

+

If you are a developer, take a look at our Introduction to Bots 2.0 and read the full changelog. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

+

If you are a user, hang on – soon you will have plenty of cool bots to play with. Meanwhile, enjoy the sample bots!

+

+ + +
+

Oh. And we almost forgot we've got more new stuff today!
Read on about Sharing and Previews »

+
+

+ +

April 12, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/cache-and-stickers.html b/data/telegram.org/blog/cache-and-stickers.html new file mode 100644 index 0000000000..2dfdf95a3c --- /dev/null +++ b/data/telegram.org/blog/cache-and-stickers.html @@ -0,0 +1,231 @@ + + + + + Clearing Cache and Reordering Stickers + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Clearing Cache and Reordering Stickers

+ +
+ +
+ +

Unlike most messengers, Telegram can take up nearly zero space on your phone, even if you‘re using it heavily. When you remove Telegram data from your device’s local cache to free up space, we'll keep it in the cloud for as long as you need, with virtually no limitations.

+

Today we are introducing new cache management options that make it even easier to maintain Telegram’s slender footprint when space is short — without having to sacrifice useful data. The new Clear Cache option allows you to quickly delete cached media by type.

+
+ + + +

+
+ +

Using the Keep Media setting, you can control how long unused media stays on your device. If you haven't accessed a file for the specified time, it is automatically deleted from the cache. Naturally, your data will instantly re-download from the cloud the moment you access it again.

+

On iOS it is also possible to clear cached files on a chat-by-chat basis. On Android, this currently works with supergroups and channels (just tap and hold in the chats list, then ‘Delete from Cache’).

+
+ +

+
+ +

Available on iOS and Android (and coming to WindowsPhone soon), these simple settings help ensure that Telegram will only require the least amount of space on your devices.

+

Reorder Sticker Packs

+

We've also improved the ordering of sticker packs. You can now manually arrange your sticker packs in the order you prefer, and the order will be synced across your devices. Access sticker settings via the new button, right on the sticker panel.

+
+ + +

+
+ +

We're not done for 2015 yet, so watch out for more updates this year.

+

+ + +

December 8, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/calls.html b/data/telegram.org/blog/calls.html new file mode 100644 index 0000000000..bcc00b60f9 --- /dev/null +++ b/data/telegram.org/blog/calls.html @@ -0,0 +1,266 @@ + + + + + Voice Calls: Secure, Crystal-Clear, AI-Powered + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Voice Calls: Secure, Crystal-Clear, AI-Powered

+ +
+ +
+ +
+ +
+ +
+

UPD, August 2020: Telegram also supports end-to-end encrypted video calls.

+

UPD, December 2020: You can start a voice chat with thousands of participants in any group.

+
+

Over the past few months, we’ve worked hard to make sure Telegram calls are the best in terms of quality, speed, and security. The wait is over: today Voice Calls are available all over the world in our mobile and desktop apps.

+

The Voice Call interface is familiar and easy to use, but as always, you get loads of innovation under the hood with Telegram.

+
+ +
+ +

Secure

+

Telegram Calls are built upon the time-tested end-to-end encryption of Telegram's Secret Chats. The key verification UI we came up with in 2013 to protect against man-in-the-middle attacks served well for Telegram (and for other apps that adopted it), but for Calls we needed something easier.

+

That's why we've improved the key exchange mechanism. To make sure your call is 100% secure, you and your recipient just need to compare four emoji over the phone. No lengthy codes or complicated pictures!

+
+ +

Key verification

+
+ +

Super-Fast

+

Whenever possible, your calls will go over a peer-to-peer connection, using the best audio codecs to save traffic while providing crystal-clear quality.

+

If a peer-to-peer connection can't be established, Telegram will use the closest server to you to connect you with the person you’re calling in the fastest way possible. Unlike other apps, Telegram has a distributed infrastructure all over the world which we’ve already been using to deliver your texts faster than other apps. Now these servers will also be used for calls.

+

In the coming months, we’ll be expanding our content delivery network around the globe, getting the connection up to light-speed even in remote areas.

+

AI-Powered

+

Each time you make a Voice Call on Telegram, a neural network learns from your and your device's feedback (naturally, it doesn't have access to the contents of the conversation, it has only technical information such as network speed, ping times, packet loss percentage, etc.). The machine optimizes dozens of parameters based on this input, improving the quality of future calls on the given device and network.

+

These parameters can also be adjusted during a conversation if there's a change in your connection. Telegram will adapt and provide excellent sound quality on stable WiFi — or use less data when you walk into a refrigerator with bad reception.

+

According to our tests, Telegram Calls are already superior to any of our competitors on comparable connections. But the quality of Telegram Calls will further improve as you and others use them, thanks to the built-in machine learning.

+

Complete Control

+

If you’re like us, you don’t like to be bothered. On Telegram, you can control who can and who can't call you with granular precision. You can even switch voice calls off altogether, blocking anyone and everyone from calling you.

+
+ +

Privacy settings for calls

+ +

By default, Telegram calls are lightweight and automatically adapt to the speed and type of your connection, so as to consume the least data possible. But if you want to reduce your data spending by another 25-30% at the expense of sound quality, you’re welcome to enable the Use Less Data option in Data and Storage Settings.

+

No Added Calories

+

Telegram is the most powerful messaging platform out there, but it is also famous for being the easiest one to use. We want to keep things this way, and that’s why by default we won’t clutter your screen with additional tabs and redundant buttons.

+

Once you start making calls, Telegram for iOS will offer you to add a dedicated tab for calls on the main screen of the app. Alternatively, you can turn the Calls tab on right away from the Recent Calls section in Settings. On Android, the call tab is accessible via the pull-out main menu on the left.

+

It's always easy to make a call, even if you've never opened the calls tab. As soon as Voice Calls are enabled for your country, a phone icon will appear on every profile page. You can also call by tapping the top bar in a chat and choosing 'Call' on iOS. On Android, the Call button is in the '…' menu at the top.

+
+ +

New call button

+
+ +

One more thing

+

For those of you who don’t do voice calls, v.3.18 brings something different: direct control over the quality of videos you share. Use this brand-new setting to select the degree of compression before sending a video. For the first time in the history of messaging, you can preview how the recipient will see your video before you send it.

+
+
+ +
+
+ +

The app will remember the compression rate you selected and will use it by default for your future video uploads.

+

+ +

And that's it for today. Stay tuned, there's always more coming!

+

+ +

March 30, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/captions-places.html b/data/telegram.org/blog/captions-places.html new file mode 100644 index 0000000000..c843fb55c1 --- /dev/null +++ b/data/telegram.org/blog/captions-places.html @@ -0,0 +1,244 @@ + + + + + Places, Captions and more + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Places, Captions and more

+ +
+ +
+ +

Today we are adding several long-awaited features in one epic update to our Android and iOS apps.

+

Places

+

When sharing a location, you can now choose venues and landmarks. And when viewing a location, you can get directions. The section was also beautifully redesigned.

+
+ + + +
+
+ +

Photo Captions

+

Another thing Telegram was lacking – captions for photos. You can now add them to any picture you send, just tap the T in the photo editing panel.

+
+ + + +
+
+ +

New Voice Messages

+

You can now see whether the recipient has listened to your voice message — and keep track of which ones you've listened to yourself. Voice messages that have not been played yet are now marked with a small dot.

+
+ +
+
+ +

Smart Notifications

+

Tired of buzzing notifications from active group chats? Sick of multiple notifications every time somebody forwards you a dozen messages? Getting notifications on mobile while chatting with the same person from your desktop? Fixed! Starting today, you will be notified only when it is necessary.

+

Rich link previews

+

As promised, link previews now work for almost any news site — in addition to previews for the most popular services like YouTube and Twitter.

+

Android Goodies

+

Telegram for Android joins the iOS app in showing extended ‘typing’ statuses: you can now see when your chat partner is sending you a photo or recording a voice message. Scrolling and photo animations have become smoother than ever.

+

Last but not least, we've fully redesigned the emoji menu on Android so that it now features a dedicated stickers tab. This is the first drumbeat of the stickers revolution that is coming to Telegram soon.

+
+ +
+
+ +

Invite Links for Groups

+

OK, this feature is so awesome that it deserves a separate post.

+

+ +

The Telegram Team,
April 30, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/channels-2-0.html b/data/telegram.org/blog/channels-2-0.html new file mode 100644 index 0000000000..d94037040c --- /dev/null +++ b/data/telegram.org/blog/channels-2-0.html @@ -0,0 +1,246 @@ + + + + + Channels 2.0 and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Channels 2.0 and More

+ +
+ +
+ +

Telegram channels are becoming a worldwide trend. Each day they get more than 400,000,000 views. Today we are introducing several features that will make channels and bots even more powerful tools for connecting with your audience.

+

Links to Posts

+

The Quick Share menu now allows you to copy links to individual messages inside a channel. You can send these links to friends outside of Telegram or post them to other social networks. Following such links will open the channel and highlight the message.

+
+ +

Copy Share Link

+
+ +

Silent Messages

+

“Is it OK to post now?” “Is this urgent enough to notify everyone?” If you're a channel admin, you know these questions too well. Luckily, you can now send silent messages that will not notify your subscribers. This is very useful for late night or non-urgent updates. Tap on the bell icon to toggle silent messages on and off.

+
+ +

Silent messages

+
+ +

Admin Signatures

+

There are times when it‘s important to know who posted a certain message. Starting today, you can enable signatures in Channel Info. New messages will be signed with the posting admin’s chosen screen name but will not link to their profile.

+
+
+ +

Channel Settings

+
+
+ +

Signed Messages

+
+ +

Edit Messages in Channels and Supergroups

+

Made a typo? Missed a word? Itching to add something? As of today, you can edit your messages after they were posted. Tap the message (double tap on iOS), then press ‘Edit’. This feature works with supergroups and channels because they both use the same underlying technology.

+

Quick Share Button for Bots

+

Many news organizations are building bots to provide tailored subscriptions. In this update we've made it easier to share the links, pictures and videos you get from bots. Check out the new official @forbesbot to see how this works.

+
+ +

Quick Share button for bots

+
+ +

Bonus: Sticker Previews

+

In other news, sticker previews now work everywhere including sticker suggestions when you type an emoji and the ‘Add stickers’ screen. Tap and hold on a sticker to see it in full size before sending. The devil's in the details, right?

+

Try it out with the Harry set: https://telegram.me/addstickers/harry

+

+ +

And that‘s all we’ve got for you this month.
Stay tuned for more updates in March!

+

+ +

February 24, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/channels.html b/data/telegram.org/blog/channels.html new file mode 100644 index 0000000000..2d8ac564e9 --- /dev/null +++ b/data/telegram.org/blog/channels.html @@ -0,0 +1,224 @@ + + + + + Channels: Broadcasting Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Channels: Broadcasting Done Right

+ +
+ +
+ +
+

UPD: See Channels 2.0 for info on links to posts, silent messages and admin signatures.

+
+

Today we are introducing Channels, a new tool for broadcasting your messages to large audiences. Channels replace the old Broadcast lists and are better in every way. They can have an unlimited number of members, they can be public with a permanent URL and each post in a channel has its own view counter.

+
+ +

+
+ +

Views from forwarded copies of your messages will be included in the total count. Last but not least, new members can see the entire message history in a channel once they join — all the way to day one.

+

If you'd like an example, join our official Telegram channel to get notified about our updates, or try creating your own channels from the ‘New Message’ menu.

+

iOS 9 Notifications

+

In other good news, we‘ve added Quick Replies from notifications, which are now supported on iOS 9 devices. This means you can reply to messages in Telegram, directly from your iPhone’s lock screen. Split View and more iOS 9 features will become available in early October.

+

Unfortunately, due to a bug in iOS 9, it is currently not possible to display the input field for Quick Replies right away — you‘ll need to press the ’Reply' button in order for it to appear. Quick replies will work as expected when iOS 9.1 is released with the relevant bugfixes.

+

Photo Editor

+

The in-app Photo Editor for iOS was updated with tools to adjust an image's tint, fade, and curves. The existing shadows and highlights tools default to 50% and are now functional in both directions.

+
+ + +

+
+ +

September 22, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html b/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html new file mode 100644 index 0000000000..4a6b82ce4d --- /dev/null +++ b/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html @@ -0,0 +1,297 @@ + + + + + Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording

+ +
+
+
+ + +
+ Introducing Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording +
+ +

Today's update lets you set different themes for individual chats, share your feelings with loved ones using interactive emoji with fullscreen effects, see detailed read receipts in groups and record video and audio from live broadcasts.

+

Chat Themes

+

Telegram has dozens of features to organize your chats and customize their appearance, from Chat Folders to Animated Backgrounds. In this update, coordination and decoration come together with new themes for individual chats.

+

Our designers created 8 new themes that you can apply to specific private chats. Each of the new themes features colorful gradient message bubbles, beautifully animated backgrounds and unique background patterns.

+
+ +
+ +

Both you and your chat partner can choose the theme for both sides and make any conversation easy to recognize, even when you can't find your glasses. This way you can set different themes for chats with co-workers and family members, so you won't accidentally send that video to your boss again.

+
+

To set a theme for your chat on Android, tap ⋮ > Change Colors. On iOS, tap the Chat Header > ⋯ > Change Colors. Your chat partner will see the theme if they are using the latest version of Telegram.

+
+

Each theme comes with a day and night version and will follow your app's night mode settings – whether you keep it dark all day, or have your chats follow the sun.

+

These first 8 themes are just the beginning – our designers are already working on adding more.

+

Interactive Emoji

+

We love animating emoji, but there are times when even a big red beating heart – that makes your phone vibrate with each beat! – is simply not enough to express your feelings.

+

With a little code, a little drawing and a lot of dark magic, we've created a new way of sharing emotion in real time. Send a single 🎆 🎉 🎈 👍 💩 or ❤️ to any private chat, then tap on the animated emoji to unleash a fullscreen effect.

+

If both you and your chat partner have the chat open, the animations and vibrations play simultaneously on your devices, so you feel close even when you're far apart.

+
+ +
+ +
+

Your chat partner will only see the effects if they are using the latest version of Telegram.

+
+

Our artists are already back in the dungeons, working on new fullscreen effects for more animated emoji.

+

Read Receipts in Small Groups

+

Both chat themes and interactive emoji currently only work in private chats. But this update also includes a big change for groups.

+

Group messages are marked as read (✓✓) as soon as one other member sees them. In small groups, you can now also select a message you sent to see which group members have read it.

+
+ +
+ +
+

To protect users' privacy, read receipts in groups are only stored for 7 days after the message was sent. It is not Telegram's business to keep a record of everything you've ever seen.

+
+

Record Live Streams and Video Chats

+

Telegram hosts millions of communities that can create live events for unlimited viewers. Whether it's a once-in-a-lifetime concert or an everyday algebra class, admins can now record Live Streams and Video Chats to publish them for those who missed the live version.

+ + +
+ +
+ +

Admins can start a recording right from the Live Stream or Video Chat menu – with options to record Video and Audio or Only Audio. To record video, choose an orientation for the final video file, Portrait or Landscape. After you finish recording or end the broadcast, the file is instantly uploaded to your Saved Messages.

+
+

Tap ⋮ or ⋯ to open the broadcast menu and start recording. While recording, a red dot appears next to the title of the broadcast.

+
+ + +

And that should give you enough things to do until we're back with the next update. As always, it shouldn't take us long.

+

+ +

September 19, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/contacts-local-groups.html b/data/telegram.org/blog/contacts-local-groups.html new file mode 100644 index 0000000000..1ab722b8ca --- /dev/null +++ b/data/telegram.org/blog/contacts-local-groups.html @@ -0,0 +1,272 @@ + + + + + Location-Based Chats, Adding Contacts Without Phone Numbers and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Location-Based Chats, Adding Contacts Without Phone Numbers and More

+ +
+ +
+ +
+ Telegram 5.8: Adding Contacts Without Phone Numbers, Location-Based Chats and More +
+ +

In the previous update, we improved privacy settings and added a way for you to control who can see your phone number. Today we're making it easier to exchange contact info on Telegram.

+

All new chats now have an Add to Contacts button at the top. This allows you to quickly add anyone who messages you to your Telegram contacts, even if you don't know their phone number yet.

+
+ Add/Block Buttons in a Chat +
+ +

If you'd prefer they disappeared instead, the Block button is right next door.

+

Add People Nearby

+

Ever scrambled for business cards at a beach party? Or dropped somebody's phone into the pool in a “let me type in my number for you” moment? Worry no more.

+

Simply open Contacts > Add People Nearby to quickly exchange contact info with Telegram users who are standing next to you (and also have this section open).

+
+ +
+ +

This feature comes in especially handy when several people meet to perform the take-my-number dance. Now you can catch all your pokémon in just a few taps.

+

Location-Based Chats

+

Speaking of pokémon, the new People Nearby section also shows Groups Nearby – location-based group chats open for anyone around to join.

+
+ +
+ +

Tap Create a Local Group to unite your dormitory or apartment building, and maybe you can get Todd in 2C to finally turn his music down.

+
+ Location-based group +
+ +

This update opens up a new world of location-based group chats for anything from conferences, to festivals, to stadiums, to campuses, to chatting with people hanging out in the same cafe.

+

Transfer Group Chats

+

If you ever get tired of being the host of your group, you can pass the burden on to another administrator. Telegram apps now support transferring ownership rights from any groups and channels to other users.

+

Grant full admin rights to your Chosen One to see the Transfer Ownership button.

+
+ Transfer group ownership +
+ +

Whether your watch has ended, or you have some business to attend to in King's Landing, passing the torch is a simple, two-tap affair.

+

Enhanced Notification Exceptions

+

Notification Exceptions just got more powerful. You can now toggle message previews for specific chats. If you have many exceptions, use Search to find the right chat — or ‘Delete All’ to get back to square one instantly.

+
+ Notification exceptions +
+ +

Siri Shortcuts

+

Owners of iOS devices can now use Siri shortcuts to open chats with people. No hands just got no-handsomer.

+
+ Siri +
+ +

Theme Picker and Icon style

+

We've also revamped the Appearance settings on iOS so that it's easier to see what the different themes will look like even before you apply them.

+
+ New theme picker on iOS +
+ +

A while back, the Telegram X app for iOS was promoted, becoming the official Telegram, and its previous shell was removed from the store. If you are still using it for some reason, this is a good time to switch — ol' Telegram X is now three versions behind the main branch.

+

Some users told us they didn't want to switch because they liked the Telegram X icon better. So this update adds a way for your iOS app icon to get back in black:

+
+ Pick your poison +
+ +

By the way, Telegram X for Android is still there and is not going anywhere for now. If you're looking for an alternative interface, feel free to give it a try.

+

+ +

June 23, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/coronavirus.html b/data/telegram.org/blog/coronavirus.html new file mode 100644 index 0000000000..9ffb9f4b8f --- /dev/null +++ b/data/telegram.org/blog/coronavirus.html @@ -0,0 +1,254 @@ + + + + + Coronavirus News and Verified Channels + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Coronavirus News and Verified Channels

+ +
+ +
+ +
+ Verified Channels and Coronavirus Info +
+ +

Telegram Channels are a powerful tool for broadcasting your messages to unlimited audiences. Since 2015, media organizations and public figures have been using them to reach readers, voters and fans – especially in countries where freedom of speech is limited.

+

Recently, we noticed a new type of channel gaining popularity: those created by Ministries of Health from around the world. India, Malaysia, Israel and many other countries now send news updates, warnings and tips via Telegram.

+
+ +
+ +
+

More about Channels and their features »

+
+

New Verification Tools

+

To help users distinguish trustworthy sources from fake news, we're launching a streamlined verification process today.

+

If you have verified accounts on other social media services, simply contact our new @VerifyBot to get a verification badge for your channel, group or bot.

+
+

More about Telegram Verification Guidelines »

+
+

Notifications for Users

+

Information is the most powerful weapon in the fight for global health – at least until we get a vaccine. To do our part, we've been sending notifications to all users in countries that have official channels with updates about the virus, offering them to join.

+

We invite all health officials to collaborate on keeping people informed. If you work for your country's Ministry of Health and would like to promote its channel, please verify it first using @VerifyBot, then contact us at corona@telegram.org.

+

Coronavirus Info

+

To make sure users find accurate and relevant information about the pandemic in their region, we've created a special channel which shows up as the top result for all coronavirus-related keywords in Search. It contains a list of official news sources by country:

+

+ +

Beyond Channels: Groups and Bots

+

Telegram Channels are good for massive one-way broadcasts, but if you're looking for more interactive ways to inform people, try groups or bots.

+

Telegram Groups can have up to 200,000 members each and offer powerful tools for maintaining order. For example, doctors from the Indian state of Karnataka are using this public group to answer questions from users.

+
+

More about Telegram Groups »

+
+

Telegram Bots are third-party apps that you can interact with right from your chat list. You talk to them using buttons – and they reply with messages and media of all kinds. Bots are extremely flexible and can be used for anything from providing information to integrating with other web services.

+

For example, check out @QuizBot which can create and run quizzes like this one.

+
+

More about Telegram Bots »

+
+

And One More Thing

+

We couldn't do anything about the shortage of masks in the real world, but our artists found a way to squeeze an inexhaustible supply into your app.

+

You can apply masks from this set to any pictures you send using Telegram's Photo Editor. Whether to raise awareness, maintain digital hygiene, or simply to hide your nose is up to you.

+
+ +
+ +

Stay home. Wash your hands. Be safe. And stay tuned for our next updates!

+

+ +

April 3, 2020,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/crowdsourcing-a-more-secure-future.html b/data/telegram.org/blog/crowdsourcing-a-more-secure-future.html new file mode 100644 index 0000000000..22264c5df6 --- /dev/null +++ b/data/telegram.org/blog/crowdsourcing-a-more-secure-future.html @@ -0,0 +1,212 @@ + + + + + Crowdsourcing a More Secure Future + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Crowdsourcing a More Secure Future

+ +
+ +
+ +

A few days ago we launched a contest to improve Telegram's security and are delighted to already have the first results. A Russian IT-community user identified a potentially vulnerable spot in our secret chat implementation. While this would not help him decipher the traffic and win the contest, his achievement deserves a notice — and a big prize.

+
+

The habrahabr user x7mz had discovered that in case the Telegram server could be seized by a malicious third party, it could send different nonce numbers to each of the clients participating in a secret chat.

+

These nonce numbers were introduced to add more randomness to the secret chat keys, mostly because of possible undiscovered vulnerabilities of the random generators on mobile devices (for example, one such vulnerability was found this August in android phones).

+

As was pointed out, this solution would have also made it possible for the visual representations of the shared secret key to be identical in case of a man-in-the-middle attack — provided such attack was done by the seized server. Obviously, the server has been under Telegram's control all this time, so this theoretical threat never had a chance to come to life.

+
+

The developer who found the potential weakness has earned a reward of $100,000. We have contacted him to find out how he would like to collect his prize.

+

A similar reward awaits anyone who finds viable ways of compromising MTProto’s security (and there is an outstanding reward of $200,000 for deciphering Telegram traffic). All submissions to security@telegram.org which result in a change of code or configuration are eligible for bounties, ranging from $500 to $100,000 or more, depending on the severity of the issue.

+

This story showcases the importance of keeping the protocol specification and source code open — this way thousands of bright minds from all over the world can help us find potential vulnerabilities and improve the protocol.

+

Let’s keep on looking for any weak spots. Together we can make Telegram unbreakable.

+

December 21, 2013
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/cryptocontest-ends.html b/data/telegram.org/blog/cryptocontest-ends.html new file mode 100644 index 0000000000..5b08eb8485 --- /dev/null +++ b/data/telegram.org/blog/cryptocontest-ends.html @@ -0,0 +1,214 @@ + + + + + Crypto Contest Ends + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Crypto Contest Ends

+ +
+ +
+ +
+

This contest is over, but Telegram's bug bounty program is always open.

+

Security researchers are welcome to submit any issues they find in the Telegram apps or protocol to us at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $500 to $100,000 or more, depending on the severity of the issue.

+
+

The current round of our contest to crack Telegram’s encryption ends with no winners. Despite the $300,000 bounty and the fact that contestants could act as the Telegram server passing info between the users (i.e. use any kinds of active attacks, manipulate traffic etc.) no one could decipher their Secret Chats by the beginning of February.

+

To demonstrate that the contest was fair, we‘ve added a decryption method to the contest bot’s list of commands – KEY. KEY returns the 256-byte encryption key used in the secret chat, so the task of the contest is now easily achieved.

+

Why are contests important?

+

One of the reasons we trust Telegram’s Secret Chats more than many of their alternatives, is that they're open to scrutiny from the world’s security experts. And while having open source apps and a well documented API makes this kind of scrutiny possible, it is our contests that create incentive for it.

+

That’s why we will definitely launch the next round of our contest later this year. It’ll take us some time to determine whether we can further simplify the task for the contestants. Once ready, we’ll announce the new round on Twitter.

+

Thank you for the vast amount of advice and comments you sent us during these last few months - your input allows us to improve Telegram with each new build.

+

+ +

February 11, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/cryptocontest.html b/data/telegram.org/blog/cryptocontest.html new file mode 100644 index 0000000000..7ca25a4dad --- /dev/null +++ b/data/telegram.org/blog/cryptocontest.html @@ -0,0 +1,224 @@ + + + + + $300,000 for Cracking Telegram Encryption + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

$300,000 for Cracking Telegram Encryption

+ +
+ +
+ +
+

This contest is over, but Telegram's bug bounty program is always open.

+

Security researchers are welcome to submit any issues they find in the Telegram apps or protocol to us at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $500 to $100,000 or more, depending on the severity of the issue.

+
+

Earlier this year we had a contest to decipher intercepted Telegram messages, that did not produce a winner. Today we announce a new contest with an easier task and a larger prize — $300,000 for cracking Telegram's encryption, and this time contestants can not only monitor traffic, but also act as the Telegram server and use active attacks, which vastly increases their capabilities.

+

In this contest you assume the role of a malicious entity in full control of both the communication lines and the Telegram servers themselves.

+
+

UPD The current round of the contest is over. Go to results »

+
+

Your goal is to extract sensitive data (a secret email address) from a Secret Chat between two users — Nick and Paul. You control the entire process, from chat creation to the sending of each individual message and can perform various active attacks, including MITM, KPA, CPA, replay attacks, etc.

+

Contest Interface

+

In order to facilitate the task, we have created an interface, using which you can act as the server and determine which side gets what data. For more details, please check out the Cracking Contest Description.

+

Objectives

+

In order to confirm that Telegram crypto was indeed cracked and claim your $300,000, you‘ll need to send an email to the secret email address that you’ve extracted from one of the messages exchanged by Paul and Nick.

+

Your email must contain:
- The entire text of the message that contained the secret email.
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $300,000 prize.

+

There is also a bonus objective with an independent prize of $100,000.
See full description for details »

+

End Date

+

To prove that the competition was fair, we will add a command that returns the keys used for encryption as soon as a winner is announced. In case there is no winner by February 4, 2015, decryption commands will be added at that date.

+
+
+
+ +

November 4, 2014
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/desktop-1-0.html b/data/telegram.org/blog/desktop-1-0.html new file mode 100644 index 0000000000..9577f65739 --- /dev/null +++ b/data/telegram.org/blog/desktop-1-0.html @@ -0,0 +1,250 @@ + + + + + Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL

+ +
+ +
+ +
+ +
+ +

Telegram was available for desktops and laptops since 2013. Today it finally graduates to version 1.0 with a fabulous new design.

+

Consistent material design, great animations, and support for custom themes make Telegram for Windows, Mac, and Linux the tool for messaging from your Mac or PC.

+

This is what Telegram Desktop 1.0 looks like:

+
+
+ +

Login Screen

+
+
+ +

Your Chats

+
+
+ +

Smooth animations are now everywhere:

+
+ +
+ +

Custom Themes

+

If you're looking for an alternative design, Telegram Desktop also supports customized themes. Anyone can make a theme for Telegram Desktop. This theme, for example, changes green outgoing messages to blue:

+
+ +

Blue theme

+
+ +

And here’s a third-party night mode theme:

+
+ +

Dark theme

+
+ +

What Else Makes Telegram Desktop Cool?

+

The best thing about Telegram Desktop is that it automatically syncs messages from your phone with your computer using Telegram’s encrypted cloud. Just install it and log in to your account! All your messages, documents, photos and videos will be synced for you from the secure cloud.

+

Thanks to Cloud Drafts, you can even start typing on your phone, then continue on your desktop when you reach home or work.

+

Who needs email now? Telegram Desktop is many times faster and handles attachments like a pro. Just share your t.me/username with those who want to reach you.

+

+ +

January 11, 2017
The Telegram Team

+

+ +

P.S. For desktop experiences, we also have Telegram Web and Telegram Mac, but our founder insists that Telegram Desktop is the way to go on all platforms.

+

P.P.S. If you're looking for an easy way to get your emails right in Telegram, check out this Gmail bot. Helps one to stay in touch with those who insist on using antique methods of communication.

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/desktop-compact.html b/data/telegram.org/blog/desktop-compact.html new file mode 100644 index 0000000000..9a9fe046b0 --- /dev/null +++ b/data/telegram.org/blog/desktop-compact.html @@ -0,0 +1,213 @@ + + + + + Telegram Desktop Adds Compact Mode + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Desktop Adds Compact Mode

+ +
+ +
+ +

The official Telegram app for Windows, OSX and Linux is now available in compact mode — you can resize the window so that only a single column remains. This makes it easier to use Telegram on smaller desktop or laptop screens.

+
+ + + +
+ +

You can download Telegram Desktop at desktop.telegram.org. As of last week, this app is also available in the Mac AppStore, alongside with our native OSX app.

+

To log in on your computer, simply enter your phone number and get a code delivered via Telegram to your phone. All your messages (except those from Secret Chats) are instantly synced between all your devices, so you can continue right where you left off.

+

+ +

December, 22
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/discover-stickers-and-more.html b/data/telegram.org/blog/discover-stickers-and-more.html new file mode 100644 index 0000000000..414cbe6cb5 --- /dev/null +++ b/data/telegram.org/blog/discover-stickers-and-more.html @@ -0,0 +1,246 @@ + + + + + Sticker Search, Multiple Photos, and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Sticker Search, Multiple Photos, and More

+ +
+ +
+ +
+ +
+ +
+

In other news: Telegram has now reached 200 million monthly active users.

+
+

Today we're launching Telegram 4.8 for iOS and Telegram 4.8.5 for Android which make it much easier to discover new stickers. From now on, when you type one emoji, you will see suggestions not just from the sticker sets you've added, but also from other popular sets.

+
+ +

Suggested Stickers

+
+ +

Sticker Search

+

We've added search for sticker sets. Scroll up in the sticker panel to find the new search field that will help you find something quickly – be it a set you've added, or a brand new pack of easter bears.

+
+ +
+ +

Multi-Shot Sending

+

Need a couple of extra selfies to maximize dramatic effect? Dog can't stop doing adorable tricks? Not a problem. Use the new + button when taking a photo to take and send multiple media one after another.

+
+ +

Take & Send Multiple Photos

+
+ +

Auto-Night Mode and Connected Websites

+

Telegram for iOS v.4.8 also includes some of the goodies which Android users have been enjoying since the previous release. With Auto-Night Mode settings you can automatically switch to the dark version of the interface after nightfall or in low-light conditions:

+
+ +

Auto-Night Mode Settings on iOS

+
+ +

As of v.4.8, the iOS app also supports text formatting in media captions, reporting individual messages in public entities, and has a section where you can manage connected websites.

+

Oh, and we've optimized battery usage so that you can enjoy all of the above even longer on a single charge.

+

+ +

March 22, 2018,
The Telegram Team

+

+ +
+

P.S. In case you missed this, Telegram has now reached 200 million active users.

+
+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/drafts.html b/data/telegram.org/blog/drafts.html new file mode 100644 index 0000000000..29a8f0741c --- /dev/null +++ b/data/telegram.org/blog/drafts.html @@ -0,0 +1,242 @@ + + + + + Drafts, Picture-in-Picture, and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Drafts, Picture-in-Picture, and More

+ +
+ +
+ +

Telegram has replaced email for business communication for many of our users. But in a messenger, a lot of people are competing for your attention. Sometimes they interrupt you halfway through typing an important message, and you forget all about it. Good news! With our latest update, this is no longer a problem.

+

Today we're introducing Drafts. Unfinished messages are now clearly visible in the chats list, and the chat with an unsent draft will move to the top. What's more – all your drafts are now synced across all your devices. Now you can start typing on your phone, then continue on your computer – right where you left off.

+
+ +

Drafts in the chats list

+
+ +

Picture-in-Picture

+

On iOS, YouTube and Vimeo videos get a new button in the bottom right corner. Tap it to shrink the video and continue watching and listening while accomplishing other tasks.

+
+
+ +
+
+ +

You can drag the minimized video around the screen so that it doesn't get in the way. On iPads, videos in PiP mode will follow you around even if you switch to a different app. PiP will become available for all videos in Telegram in one of the next updates.

+

Internal Video Player for Android

+

Android users will enjoy the new built-in video player, available for Android 4.1+.

+
+ +

New built-in video player on Android

+
+ + +

…and more

+

On top of this, Telegram v.3.10 allows you to view the entire set of a group‘s profile pictures instead of just the latest one. The beautiful ’Scroll to bottom' button with an unread messages counter has made it to Android and Telegram Desktop.

+
+ +

New unread messages counters

+ + +

We've improved design across all of our apps. Telegram Desktop now sports nifty blue unread message counters, new buttons, and fully revamped profile pages.

+

+ +

We at Telegram are hard at work expanding the boundaries of what you can do with a messaging app. Stay tuned for more updates coming soon!

+

+ +

June 14, 2016
The Telegram Team +

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/edit.html b/data/telegram.org/blog/edit.html new file mode 100644 index 0000000000..cb8c80e6f9 --- /dev/null +++ b/data/telegram.org/blog/edit.html @@ -0,0 +1,245 @@ + + + + + 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/encrypted-cdns.html b/data/telegram.org/blog/encrypted-cdns.html new file mode 100644 index 0000000000..c17dc4917b --- /dev/null +++ b/data/telegram.org/blog/encrypted-cdns.html @@ -0,0 +1,228 @@ + + + + + More Speed and Security! + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

More Speed and Security!

+ +
+ +
+ +
+
+ +

We at Telegram love to build sophisticated technologies that combine speed with security. Starting with Telegram 4.2, we support CDN caching. CDNs are third-party caching nodes that we’ll use to cache publicly available videos and photos posted in massive channels (say, with 100,000+ subscribers) for users in remote locations where Telegram is popular.

+

This will increase download speeds for tens of millions of users as CDN caching allows data to travel shorter distances and helps avoid bottlenecks that exist between regions.

+

While these caching nodes are only used to temporarily store public media (imagine Telegram versions of superpopular YouTube hits), all data that goes through them is encrypted with a key unknown to the caching nodes. In other words, we treat these CDN caching nodes just like we treat your internet provider – they only ever get encrypted junk they can't decipher.

+

Here’s how it works

+
+ +
+ +

If you're interested in the technical details, feel free to check out this page that describes the relevant encryption and security checks. And as always – the updated source code for the Telegram apps is open and available for your scrutiny. Security experts are welcome to verify the implementation of CDNs based on the open source code we make available for all of our apps.

+

Thanks to this technology, the download speed for public photos and videos in places like South America, Turkey, Indonesia, India, Iran or Iraq will significantly increase without the slightest compromise in security.

+

To sum up

+
    +
  • Download speeds for popular public media are set to increase several times for millions of Telegram users.
  • +
  • CDN caching nodes are not Telegram servers and not part of the Telegram cloud.
  • +
  • CDNs are used only for caching popular public media from massive channels. Private data never goes there.
  • +
  • CDNs only get encrypted data and they never have the keys: even if they are accessed by hackers or third parties, the attacker won’t be able to decipher the files.
  • +
  • Data downloaded from CDN caching nodes is always verified by the receiving Telegram app by way of hash: attackers won’t be able to replace any files with their own versions.
  • +
  • Detailed technical info about CDNs can be found here, the updated source code of Telegram apps ready for CDN support can be found here.
  • +
  • Telegram 4.2 also includes a bucketful of other goodies for you to enjoy.
  • +
+

+ +

Stay safe (and fast)!

+

July 23, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/export-and-more.html b/data/telegram.org/blog/export-and-more.html new file mode 100644 index 0000000000..8f62446caa --- /dev/null +++ b/data/telegram.org/blog/export-and-more.html @@ -0,0 +1,238 @@ + + + + + Chat Export Tool, Better Notifications and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Chat Export Tool, Better Notifications and More

+ +
+ +
+ +
+ +
+ +

Today’s Telegram update brings you an easy way to save conversations on your disk. In just a few taps, you can export some (or all) of your chats, including photos and other media they contain. As a result you’ll get all your data accessible offline in JSON-format or in beautifully formatted HTML.

+
+ +

Data Export Results

+
+ +

To use this feature, make sure you have the latest version of Telegram Desktop installed on your computer, then click Settings > Export Telegram data. This tool will be particularly useful for users who have millions of messages and can’t easily access the oldest parts of their messaging history.

+
+ +
+ +

You can export individual chats by opening the menu in any chat and choosing Export chat history.

+

Exceptions in Notifications

+

Telegram was the first app to give its users notorious flexibility in fine-tuning how their message notifications work. Today we are taking this further by adding Exceptions to the notifications settings, where you can see which chats are excluded from the global settings you defined in Settings > Notifications.

+
+ +

Notifications Exceptions

+
+ +

Muting all chats but a few (or vice versa) has never been easier.

+

Improved Telegram Passport

+

We’ve been overwhelmed by the reception of Telegram Passport – the tool to log into third-party apps that require real-life identity. Just two weeks after its launch, Passport can be used to sign up for many services, from established sharing economy services to blockchain startups.

+
+To name just a few projects that integrated Telegram Passport: Sum & Substance (KYC & user verification), CEX.IO and Xena (cryptocurrency exchanges), CryptoPay (wallet), YouDrive (carsharing), Profi and Worki (job marketplaces), Minter Network and Minexcoin (blockchain startups), KICKICO, Cryptonomos and ICOadmin (ICO platforms).

+ +

Building on this success, today we’re upgrading Passport to support names in original languages and additional types of documents. We’ve also strengthened the algorithms that encrypt Passport data to better protect your data against hacking attacks coming from Telegram (however unlikely those may seem). This way we further ensure that only you have access to your private data.

+

Source Code and APIs

+

As always, you do not have to take our word on how our encryption works. The updated source code of Telegram apps reflecting all of today’s changes is available on GitHub and open for everybody to review. If you are a developer of a service that requires identity verification, make sure you check out these docs explaining how Telegram Passport can be integrated into your app.

+

+ +

August 27, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/files-on-steroids.html b/data/telegram.org/blog/files-on-steroids.html new file mode 100644 index 0000000000..9e33d82155 --- /dev/null +++ b/data/telegram.org/blog/files-on-steroids.html @@ -0,0 +1,240 @@ + + + + + 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/filters-anonymous-admins-comments.html b/data/telegram.org/blog/filters-anonymous-admins-comments.html new file mode 100644 index 0000000000..20e5bcd4dd --- /dev/null +++ b/data/telegram.org/blog/filters-anonymous-admins-comments.html @@ -0,0 +1,261 @@ + + + + + Search Filters, Anonymous Admins, Channel Comments and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Search Filters, Anonymous Admins, Channel Comments and More

+ +
+
+
+ +
+ Introducing Search Filters, Anonymous Group Admins, Channel Comments and More +
+ +

Your personal Telegram Cloud is endless and full of spicy memes. To help you find your way around it, we're introducing Search Filters. Today's update also features Anonymous Admins to make your battle for freedom safer and Channel Comments to make sure everyone's voice is heard.

+

Search Filters

+

From now on, you can filter search results by type using the new tabs: Media, Links, Files and others. To search a particular time period, just type “August 14” or “Yesterday”. Typing the name of any person, group, channel or bot will add a filter by source.

+
+ +
+ +

These search filters can be combined, which lets you look for something as specific as messages with a link, sent in March 2016, containing the word “boat”.

+

Anonymous Group Admins

+

Telegram is increasingly used to organize protests for democracy and freedom. Today we're introducing another tool for safer protests.

+

Toggle Remain Anonymous in Admin rights to enable Batman mode. The anonymized admin will be hidden in the list of group members, and their messages in the chat will be signed with the group name, similar to channel posts.

+
+ Post from an anonymous admin in a group +
+ +

Channel Comments

+

Speaking of Channels, we've added a comment button to posts on channels with discussion groups. Comments show up in a cozy little thread of their own, but will also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

+
+ +
+ +

If you are not a member of the channel's discussion group, you will be notified about replies to your comments via a new chat called Replies.

+
+

For a limited time only, you can test this feature in this channel.

+
+

If you'd like to enable discussions in your own channel, head to Channel Settings > Discussion.

+

Amazing Android Additions

+

Our Android wizards didn't forget to pack some new smooth animations. To get a taste, try expanding or hiding your keyboard – or switching between your day and night themes from the left menu. You will also see animated popups when deleting messages, changing notifications, saving media, etc.

+
+ +
+ +

In case you're more into practical things, press and hold on any profile picture in a group chat to take a closer look. And if you're using multiple accounts in one app, you can now preview the chat lists of your other accounts using the same gesture in the account switcher.

+

More Animated Emoji

+

We carry on with our quest to animate every emoji in existence. To get one of these 👇 in a chat, simply send a message with a single emoji.

+
+ +
+ + +

+ +

And that's all for today, see you in the comments.

+

+ +

September 30, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/folders.html b/data/telegram.org/blog/folders.html new file mode 100644 index 0000000000..be41e8623c --- /dev/null +++ b/data/telegram.org/blog/folders.html @@ -0,0 +1,298 @@ + + + + + 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/games.html b/data/telegram.org/blog/games.html new file mode 100644 index 0000000000..1208c848c0 --- /dev/null +++ b/data/telegram.org/blog/games.html @@ -0,0 +1,264 @@ + + + + + Gaming Platform 1.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Gaming Platform 1.0

+ +
+ +
+ +

Last year we launched a Bot Platform for Telegram. Free, powerful, and open, it was an instant hit among users and developers. Today we are aiming to push the boundaries further by launching a bot-powered Gaming Platform on Telegram. That’s right: you can now use bots to play games in your chats, complete with graphics and sound.

+
+
+ +
+
+ +

Ready to Play

+

Hundreds of games are headed your way, but about 30 are ready to be played on Telegram now, most of them published by @gamee. You can start a game by interacting with their bot directly, or by invoking it from any of your chats. To do that, try typing “@gamee “ in a group and choose a game to start playing with your friends:

+
+ +

Select a game

+
+ +

If you spot a great game on Telegram, you can challenge your friends from other chats by sharing the game with them.

+
+ +

Challenge your friends

+
+ +

Better with Friends

+

The best part of the Telegram Gaming Platform is the competition across all your existing chats. We save high scores for every game played in every chat, and you can instantly check out how you and your friends are doing against each other. Every time there’s a new leader in the game, other playing members of the chat are notified that they need to step it up.

+
+
+ +

In-game high scores

+
+
+ +

New high score in chat

+
+ +

Easy to Build

+

Building games for Telegram is easy (check out the API). Here’s MathBattle, a game that took our developer only 3 hours to build. You can launch it from any chat by typing @gamebot and choosing Math Battle:

+
+
+ +
+
+ +

This is Corsairs, a demo game that took its dev just 5 hours to build and set up. That includes sound, graphics and animations:

+
+
+ +
+
+ +

While these demos look basic, Telegram games can be anything from simple arcades and puzzles to multiplayer 3D-shooters and real-time strategy games. The underlying technology is HTML5, so games are loaded on-demand as needed, just like ordinary webpages. Games will work on iPhones 4 and newer and on Android 4.4 devices and newer. Note that your friends will need Telegram 3.13 or higher to play.

+

If you are a developer, take a look at our Introduction to Games. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

+

No Added Calories

+

We know you love Telegram because it’s lean and efficient. This is why the new Gaming Platform requires 0 bytes of disk space and won’t add a single byte to the size of our apps. The only thing we're adding today is countless more fun moments in your chats.

+

+ +

And now let's see how high you can score.

+

+ +

October 3, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/gifs.html b/data/telegram.org/blog/gifs.html new file mode 100644 index 0000000000..57c3aeb673 --- /dev/null +++ b/data/telegram.org/blog/gifs.html @@ -0,0 +1,223 @@ + + + + + GIF Search and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

GIF Search and More

+ +
+ +
+ +

OK, so there is a celebration in the Android camp today. Telegram for Android was redesigned and loaded with new features. But what about the iPhone fan army? It turns out, the iOS app got something just as great.

+

In addition to granular controls for hiding your Last Seen and other privacy settings, today’s iPhone update introduces a great media feature – Animated GIF search.

+

How Does This Work?

+

You can find and share images from the Web using the “Find Images” attachment option. Today the Web image search got two new tabs – GIFs and Recent. The GIFs tab allows you to search through thousands of great GIF animations, powered by Giphy. Just type in a keyword and have fun.

+

All images from the Web and GIFs you share will be saved in the Recent tab. You can go that tab whenever you're out of words and instantly share any of them just in three quick taps. If you forward an incoming GIF to a contact, that animation will also be available from the Recent tab. And yes, you can send multiple GIFs at once.

+
+
+ +
+
+ + +

One More Thing

+

Another media feature we added to the iPhone app today are previews for YouTube and Instagram links. If a message contains nothing but a link to YouTube or Instagram, it will be transformed into a thumbnail with relevant information, such as title and duration. Check it out!

+

..but I'm on Android

+

All of this is coming to our Android app in the next updates. So for now, sit back and enjoy your new privacy settings and material design. Soon we'll have GIFs and images for you as well!

+

+ +

The Telegram Team
November 19, 2014

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/group-video-calls.html b/data/telegram.org/blog/group-video-calls.html new file mode 100644 index 0000000000..a9b82fc3e0 --- /dev/null +++ b/data/telegram.org/blog/group-video-calls.html @@ -0,0 +1,264 @@ + + + + + Group Video Calls + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Group Video Calls

+ +
+
+
+ +
+ Introducing Group Video Calls +
+ +

Today's update lets you turn on your camera or share your screen during Voice Chats in groups – on all devices, including tablets and desktops. This brings voice chats to a whole new level, ready for online classes, business meetings and family gatherings.

+

We're also introducing animated backgrounds, stylish message animations and more – enough to fill a second blog post.

+

Group video calls

+

Voice chats in any group can now seamlessly turn into group video calls – just tap the camera icon to switch your video on.

+
+ +
+ +

Tap on any video to make it fullscreen. If you pin a video, it will stay focused as new users join the call and turn on their cameras.

+
+

To start a voice chat, check the ⋮ menu in the profile of any group where you are an admin (on iOS, you will find a 'Voice Chat' button right in the group profile).

+
+

While audio-only participants are unlimited, video is currently available for the first 30 people who join the voice chat. This limit will increase soon as voice chats take on streaming games, live events and more.

+

Screen sharing

+

In addition to your camera feed, you can also share your screen – or both at the same time.

+
+ +
+ +
+

To share your screen, tap ⋮ or ⋯ in any app and select it from the menu.

+
+

Noise suppression options

+

We've improved noise suppression in voice chats to keep everyone's audio clear and crisp, even when you're eating something crispy. We've also added a toggle to turn noise suppression off in settings – for those times when munching has meaning.

+
+ Noise suppression settings +
+ + +

Tablet and desktop support

+

Tablets and computers have more screen space and offer more display options – tap to open the side panel and see a split-screen view of the video grid and list of participants, optimized for both portrait and landscape orientation.

+
+ +
+ +

Voice chats on desktop open in a separate window, so you can type and talk without minimizing anything. Desktop apps also have selective screensharing so you can broadcast an individual program instead of your whole screen.

+
+ +
+ +

When you're using a desktop app, anyone who starts sharing their screen will be pinned automatically. This is especially useful when small teams meet to coordinate their work.

+

And more?

+

That's it for today… No, wait. In fact, we're having two updates instead of one:

+
+

Read on to learn about Animated Backgrounds and more.

+
+

+ +

June 25, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/inline-bots.html b/data/telegram.org/blog/inline-bots.html new file mode 100644 index 0000000000..d205fd3371 --- /dev/null +++ b/data/telegram.org/blog/inline-bots.html @@ -0,0 +1,234 @@ + + + + + Introducing Inline Bots + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Introducing Inline Bots

+ +
+ +
+ +

Bots became an integral part of Telegram for many users, but communication with them wasn't always easy. You had to send them messages in separate chats or add them to your groups. Today we are introducing a quicker way to contact bots.

+

With the new inline mode, bots become omnipresent and can be used as a tool in any of your chats, groups or channels – it doesn't matter, whether the bot is a member or not. Inline bots can help you with dozens of different tasks, like quickly sending relevant GIFs, pictures from the Web, YouTube videos, Wikipedia articles, etc.

+
+
+ +
+
+ +

How does it work?

+

We've created several sample bots for you to try out: @gif, @vid, @pic, @bing, @wiki, @imdb and @bold. To see them in action, simply type one of their @usernames in the message field in any chat, then type some keywords. The bot will offer you relevant content.

+
+ + +
+
+ + +

Tap on an item to instantly send it to the chat. This way you can share stuff from bots without any hassle. Inline bots don't see any messages in your chats – they only receive what you type after their username in the input field.

+
+ + +
+
+ +

Tap on ‘via @username’ to send a new request to the bot. Recently used inline bots will also show up in the suggestion box when you type @ in the input field in any chat.

+

A new dimension for bots

+

Like pretty much everything else at Telegram, inline bots are part of an open platform, available for free to every developer in the world starting today. Hundreds of new inline bots are sure to arrive once developers start supporting the new mode.

+

If you are a developer, take a look at our Introduction to Inline Bots. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

+

+ +

The Telegram Team,
January 4, 2016

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/instant-camera.html b/data/telegram.org/blog/instant-camera.html new file mode 100644 index 0000000000..eeab87a2c0 --- /dev/null +++ b/data/telegram.org/blog/instant-camera.html @@ -0,0 +1,229 @@ + + + + + Instant Camera and More 3D Touch + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Instant Camera and More 3D Touch

+ +
+ +
+ +

When taking pictures, even a split second can make the difference between capturing the perfect moment or missing it entirely. Starting today, our iOS users can snap a photo or take a video in no time. To access your camera quickly, simply tap and hold the attachment button, and you're ready to shoot:

+
+
+ +
+
+ +

This quick camera interface defaults to selfie mode with flash on, but you can change this and it will remember your choice.

+

With this update it also becomes easier to record videos using the standard camera interface. Press and hold the big button and the recording starts. By popular demand, videos you record in-app will now be saved to your device in Full HD quality.

+

More 3D Touch and More

+

Starting today you can use 3D Touch to preview photos and videos everywhere, including the attachment menus, message history, and the Shared Media section. The same goes for profile pictures: That's right, you no longer need to go to chat info to check them out in full size.

+
+
+ +

We've also added Uber and Citymapper as options for opening a location:

+
+
+ +

And, speaking of opening stuff, we've fixed the issue with files – you can now open any file you get in other apps again. This is extremely useful, given that you can share and store an unlimited number of documents and files of any type on Telegram.

+

+ +

That's it for today, stay tuned for more updates coming soon! The cool features we are adding in the next release will be available for all platforms.

+

+ + +

April 28, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/instant-view.html b/data/telegram.org/blog/instant-view.html new file mode 100644 index 0000000000..8a48b07f35 --- /dev/null +++ b/data/telegram.org/blog/instant-view.html @@ -0,0 +1,268 @@ + + + + + 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 new file mode 100644 index 0000000000..3c98d9290e --- /dev/null +++ b/data/telegram.org/blog/invite-links.html @@ -0,0 +1,217 @@ + + + + + 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/link-preview.html b/data/telegram.org/blog/link-preview.html new file mode 100644 index 0000000000..0ff5fd1f8b --- /dev/null +++ b/data/telegram.org/blog/link-preview.html @@ -0,0 +1,217 @@ + + + + + Link Previews + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Link Previews

+ +
+ +
+ +

In addition to new security features, today‘s update brings you rich link summaries. All links to tweets, Instagram photos and YouTube videos will now be beautifully rendered so that you’ll see what the link is all about before opening it.

+

Once you paste a URL to the message input field, Telegram will start analyzing the link and getting a preview for it. If you prefer to send a particular message without the preview, just tap the x to remove it.

+
+ + + + + +

+ +
+ +

Rich link previews are now shown for most websites.

+

+ +

April 8, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/live-locations.html b/data/telegram.org/blog/live-locations.html new file mode 100644 index 0000000000..32b9e99871 --- /dev/null +++ b/data/telegram.org/blog/live-locations.html @@ -0,0 +1,243 @@ + + + + + Live Locations, Media Player and Languages + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Live Locations, Media Player and Languages

+ +
+ +
+ +
+ +
+ +

Starting with Telegram 4.4, you can broadcast your current location to any chat in real time.

+

This is useful when you are on your way to an appointment or are trying to coordinate with friends at a large event. Instead of sending static locations on the map every minute, you can now share your Live Location with the people you’re meeting – for 15 minutes, 1 hour, or 8 hours.

+

To use this feature, select ‘Location’ from the attachment menu and choose ‘Share My Location for…’:

+
+
+ +
+
+ +

You can also share your Live Location in groups, and if other members of the group do the same, you’ll get an interactive map of everyone’s current coordinates. Thanks to a bar at the top of the screen, you will always remember who you’re sharing your location with. And you only need two taps to stop sharing whenever you choose to.

+

New Media Player

+

We’ve completely redesigned our in-app audio player to better support the playback of MP3s and other music files you send and receive. Try the @cctracks channel for a demo – we’ve uploaded some free music there to demonstrate how the new media player works. After downloading an audio file, tap the play button to start listening. To view the cover image and the rest of the chat's playlist, tap on the title of the playing track in the top bar.

+
+
+ +
+
+ + +

More Languages

+

We’re also launching a new translation platform for Telegram apps. Starting today, Telegram is available in French, Indonesian, Malay, Russian and Ukrainian – with more languages like Persian coming soon. Telegram now supports 13 languages, which are available in Settings.

+

If you don’t like how a specific element in Telegram's interface is translated in your language, you can now use the localization platform to suggest an alternative word or phrase. Everyone can suggest translations and vote for them, making Telegram localization a community-driven effort.

+
+ +

Screenshots make translations easier

+
+ +

Unlike other services, Telegram can instantly push new translations of words and phrases to the apps. Thanks to this, users won't need to wait for an update in the stores to get the new localized version.

+

This also means that our developers won't have to wait for all translations to be finished before the apps are released, so this new interface will speed up Telegram development too.

+

Better Group Chats

+

As always, we’re trying to make Telegram group chats better. In large groups, you can now recognize messages from admins by the new ‘admin’ badge. And Admins in supergroups can now control whether new members get to see the earlier message history.

+

+ +

October 10, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/live-streams-forwarding-next-channel.html b/data/telegram.org/blog/live-streams-forwarding-next-channel.html new file mode 100644 index 0000000000..d9f50e579b --- /dev/null +++ b/data/telegram.org/blog/live-streams-forwarding-next-channel.html @@ -0,0 +1,285 @@ + + + + + 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/login.html b/data/telegram.org/blog/login.html new file mode 100644 index 0000000000..8cbbb3248d --- /dev/null +++ b/data/telegram.org/blog/login.html @@ -0,0 +1,257 @@ + + + + + Telegram Login for Websites + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Login for Websites

+ +
+

This post is from Feb 2018. For up-to date information on integrating services with Telegram please see this post. For Telegram Widgets, see this page.

+
+
+ +
+ +
+ +
+ +

Today we present a Telegram Login Widget for external websites. When you use Telegram login for the first time, our widget asks for your phone number and sends you a confirmation message via Telegram to authorize your browser.

+
+

Once this is done, you get a two-click login on every website that supports signing in with Telegram. Try it here:

+

Once this is done, you get a two-click login on every website that supports signing in with Telegram:

+
+
+ + +
+ +

+ +

Logging in will send your Telegram name, username, and your profile picture to the website owner. Your phone number remains hidden. The website can also request permission to send you messages from their bot.

+

Permission to speak

+

Telegram bots are a powerful communication tool, but until today they couldn't start a conversation. Even if you wanted them to reach out to you, you had to chat them up first.

+

With the new login widget, moving from interacting with a website to a conversation on Telegram becomes completely frictionless.

+
+ +

Message from a bot

+
+ +

The potential use cases are limitless. Bots could be used for providing customer support, accepting payments, or sending notifications of any kind – including account statements, shipment tracking, flight updates, and so much more.

+

Stay in control

+

After each login, Telegram will send you a summary message about the permissions you‘ve granted and the data you’ve passed to the website owner. You can revoke the authorization by tapping the appropriate button under the login summary.

+

Telegram for Android 4.8, also released today, includes a section in the Privacy & Security settings that lists all the websites where you logged in using Telegram. Other apps will soon follow.

+

+ +

This simple login tool is the first phase of the Telegram ID project, which we will be rolling out throughout this year.

+ +

+ +

February 6, 2018,
The Telegram Team

+

P.S.

+

Don‘t miss the other updates we’ve launched in the last few days:

+ +
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/move-history.html b/data/telegram.org/blog/move-history.html new file mode 100644 index 0000000000..e389baa40c --- /dev/null +++ b/data/telegram.org/blog/move-history.html @@ -0,0 +1,284 @@ + + + + + Moving Chat History from Other Apps + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Moving Chat History from Other Apps

+ +
+
+
+ +
+ Moving Chat History from Other Apps and More Privacy +
+ +

Over 100 million new users joined Telegram this January, seeking more privacy and freedom. But what about the messages and memories that remain in older apps?

+

Starting today, everyone can bring their chat history – including videos and documents – to Telegram from apps like WhatsApp, Line and KakaoTalk. This works both for individual chats and groups:

+
+ +
+ +

To move a chat from WhatsApp on iOS, open the Contact Info or Group Info page in WhatsApp, tap Export Chat, then choose Telegram in the Share menu.

+

On Android, open a WhatsApp chat, tap ⋮ > More > Export Chat, then choose Telegram in the Share menu:

+
+ +
+ +
+

WhatsApp for iOS also lets you export chats directly from the chat list. Swipe left on a chat, then choose '…' > Export Chat.

+
+

Messages will be imported into the current day but will also include their original timestamps. All members of the chat on Telegram will see the messages.

+

Move Chats and Save Space

+

The best part is that the messages and media you move don’t need to occupy extra space. Older apps make you store all data on your device – but Telegram can take up virtually no space while letting you access all your messages, photos and videos anytime you need them.

+
+

You can free up space and control your cache size in Settings > Data and Storage > Storage Usage.

+
+

Control Your Digital Footprint

+

Your data is your business, which is why Telegram users can not only export their chats, but also delete messages they send and receive for both sides – without a trace.

+

With this update, you get even more control: secret chats, groups you created and call history can now also be deleted for all sides at any time.

+
+ +
+ +

Telegram servers don’t store information about deleted chats and call logs, so the data will disappear completely, forever.

+

Improved Voice Chats

+

You can now see which of your groups have active Voice Chats from the top of the Call History page.

+

While in a voice chat you can adjust the volume of individual participants to manage microphone levels. Adjustments made by group admins are applied for all listeners.

+
+ +
+ +

Improved Audio Player

+

When a track is playing, tap the author name in the player to see their tracks from all your chats. If you need to skip ahead or repeat something you missed, press and hold on the Next and Previous buttons to fast-forward and rewind.

+
+ +
+ +

We’ve also added a fade effect to please your ears when you pause and resume the music.

+

Greeting stickers

+

If you have contacts who joined Telegram recently, it may be a nice touch to welcome them using one of Telegram's unique features. A greeting sticker will be suggested in your new chats, ready to send in one tap.

+
+ +
+ +

New Android Animations

+

A new update means sleek new interface animations. See if you can catch them all when downloading files, playing music, or loading chats after logging in.

+
+ +
+ +

Reporting Fake Channels

+

All Telegram apps let you report spam and other types of illegal content, including calls to violence or child abuse. Now you can also report fake channels or groups that impersonate famous people or organizations. Open their profile page and tap '…' > Report > Fake Account to let our moderators know.

+

Improved Accessibility

+

Many accessibility improvements have been added for both TalkBack and VoiceOver users. As we continue to refine app interfaces for all users, we welcome additional feedback on our Suggestions Platform.

+

A warm welcome to everyone who joined us recently! The next update shouldn’t take long.

+

+ +

January 28, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/now-you-see-me.html b/data/telegram.org/blog/now-you-see-me.html new file mode 100644 index 0000000000..199b6c6a88 --- /dev/null +++ b/data/telegram.org/blog/now-you-see-me.html @@ -0,0 +1,235 @@ + + + + + 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/passport.html b/data/telegram.org/blog/passport.html new file mode 100644 index 0000000000..8cca4e32d8 --- /dev/null +++ b/data/telegram.org/blog/passport.html @@ -0,0 +1,233 @@ + + + + + Introducing Telegram Passport + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Introducing Telegram Passport

+ +
+ +
+ +
+ +
+ +

Our digital lives are getting closer and closer to the real world, and the number of services that need to know your real-life ID increases accordingly. Before today, this meant you had to upload the same document scans over and over for each new app. No more!

+

Meet Telegram Passport – a unified authorization method for services that require personal identification. Upload your documents once, then instantly share your data with services that require real-world ID (finance, ICOs, etc.).

+
+ +
+ +

Protected by End-to-End Encryption

+

Your identity documents and personal data will be stored in the Telegram cloud using End-to-End Encryption. It is encrypted with a password that only you know, so Telegram has no access to the data you store in your Telegram passport. When you share data, it goes directly to the recipient.

+
+ +

Sharing Data with an App

+
+ +

In the future, all Telegram Passport data will move to a decentralized cloud.

+

Try It Now

+

If you'd like to see a real-life implementation of Telegram Passport, head over to ePayments.com – the first electronic payments system to support registration and verification with Telegram Passport.

+

You can also try out how Telegram Passport works using this page to request data.

+

Please note that you need the latest version of Telegram to access this feature. Once you've uploaded some documents, you will see your data in Settings > Privacy & Security > Telegram Passport (on iOS: Settings > Telegram Passport).

+

Connect Telegram Passport

+

All developers are welcome to integrate Telegram Passport into their apps and services free of charge. It takes minimum effort and can save many hours of coding.

+

If you are building a service that requires real-life ID, check out the API docs for SDKs and examples.

+

Stay Tuned

+

In the future, we will be adding third-party verification for Telegram Passports. This way, services won't even need to request the data itself, instead relying on the fact that the Telegram account was approved by a verification provider and the person is real.

+

+ +

July 26, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html b/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html new file mode 100644 index 0000000000..6ecb091d68 --- /dev/null +++ b/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html @@ -0,0 +1,319 @@ + + + + + Payments 2.0, Scheduled Voice Chats, New Web Versions + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Payments 2.0, Scheduled Voice Chats, New Web Versions

+ +
+
+
+ +
+ Payments 2.0, Scheduled Voice Chats, New Web Versions and More +
+ +

This update brings Payments 2.0 for all Telegram chats, Scheduling and Mini Profiles for Voice Chats, new Telegram apps for your browser, and more.

+

Payments 2.0

+

We first added support for payments in 2017. Payment bots allowed users to securely pay for goods and services without leaving the app – anything from ordering a pizza to hailing a taxi, to replacing winter tires when you're tired of winter.

+

Starting today, merchants can natively accept credit card payments in any chat, relying on 9 integrated third-party payment providers such as Stripe.

+

Buyers can add a tip whenever they make a purchase to show some extra love to their favorite artists, stores, or delivery drivers. Payments can now be made from any app – including desktop apps.

+
+ +
+ +

This is a free and privacy-conscious platform – Telegram takes no commission, and stores no payment information. Credit card information is sent directly to the payment provider and shipping information is shared with the merchant so they can send you your goods.

+
+

We've created a demo channel with the most exotic imaginary goods and services no money can buy, so you can test how this works without spending a penny.

+
+

Any merchant can start using the Payments API without getting additional approvals from Telegram. Developers interested in integrating payments can find all the details in the Payments Manual.

+

Scheduled Voice Chats

+

Voice Chats give users the option to catch up with a few friends or tune in to massive broadcasts with millions of listeners.

+

Admins of groups and channels can now schedule a Voice Chat for a particular date and time instead of creating one right away. This gives community members time to let their friends know and get the popcorn ready.

+
+ +
+ +

Users will see a colorful countdown at the top of the chat. Those too busy to watch the countdown can opt to receive a notification when the voice chat starts.

+
+ +
+ +
+

Admins can schedule a Voice Chat from their Group or Channel's profile page. On Android, tap ⋮ > Start Voice chat > Schedule Voice Chat. On iOS, tap the Voice Chat button and select Schedule Voice Chat.

+

Don't worry, the chat won't start automatically when the countdown reaches zero – only when an admin presses the Start Now button.

+
+

Mini Profiles for Voice Chats

+

You can now expand profile pictures and bios to get a better idea of who you're chatting with – without leaving the voice chat window.

+
+ +
+ +

You can also change your profile picture and edit your bio without leaving the chat – like changing from Shirley to Grognak the Barbarian as you meet for Dungeons and Dragons.

+

New Web Versions

+

Telegram's first Web Version was launched in 2014. Ever since, our pet demon of internal competition kept whispering: 'Why have one web version when you can have two?'

+

Today we're adding two new, fully-featured Telegram web apps – both supporting animated stickers, dark mode, chat folders and more.

+
+ +
+ +

With the new web versions you can get instant access to your chats on any device – desktop or mobile. These apps are incredibly efficient, requiring only a 400 KB download (that's like two photos of a medium-sized cat) and no installation.

+

Take them for a test drive, and see which one you like best:

+ +

Like other Telegram apps, all our web versions are standalone: once you've logged in, you do not need to keep your phone nearby or connected to the internet.

+
+

If you find an issue with either of the new apps, let us know using our Suggestions Platform.

+
+

Direct Download for Android

+

In case you're more of an app person, you can now also download Telegram for Android directly from telegram.org. Apps installed from the website will automatically update to the latest version. You are likely to get new versions several days or weeks faster this way because you won't have to wait for updates to be reviewed by the store.

+ + +
+ +
+ +
+

Telegram supports reproducible builds, so you can always be sure that the app you have on your device was built from the exact same open source code that is published on GitHub.

+
+

Pinch to zoom

+

Photos and videos can now be expanded directly from the chat – simply pinch to zoom in right away, without tapping to open the media viewer.

+
+ +
+ +

Improved Video Player

+

When watching a video from the media player on iOS, press and hold the + or - 15s buttons to fast-forward and rewind. On Android press and hold on the right or left side of the screen to do the same, and double-tap to jump 10 seconds in either direction.

+
+ +
+ +

Tips and New Android Animations

+

The Android app gets smoother and more dynamic with each update – check out the new animations when opening the side menu or swiping back to the chat list from a chat.

+
+ +
+ +
+

To learn more about what Telegram can do, tap Telegram Features from the side menu or visit the @TelegramTips channel.

+
+

Telegram Jobs

+

That's it for today. We are already working on the next update — and if you just thought 'Wow, that's the spirit!' rather than 'Poor people, have some rest', check out our list of open positions.

+

+ +

April 26, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/payments.html b/data/telegram.org/blog/payments.html new file mode 100644 index 0000000000..61d0a8a1b0 --- /dev/null +++ b/data/telegram.org/blog/payments.html @@ -0,0 +1,253 @@ + + + + + Payments for Bots + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Payments for Bots

+ +
+ +
+ +
+

UPD 2021: For up-to-date information about Payments on Telegram, see Payments 2.0 and the Payments Documentation.

+
+
+ +
+ +

Imagine a world where you can order pizza, pay for a pair of shoes, hire a cab, or refill your subway pass — all in a few button taps on Telegram.

+

To make this world possible, we are launching Bot Payments today. Bot developers can now accept payments from their users around the world, just like that:

+
+
+ +
+
+
+ +

If you have Telegram 4.0 (or newer) installed, you can order goods or services from bots that offer them. These bots may now add a Pay button to their messages. When you tap Pay, you'll be asked to fill in your credit card and shipping information and confirm the payment. Then you get what you paid for. Voila!

+

If your account is protected by 2-Step Verification, you can save your card for future purchases. If you do that, ordering stuff from bots will only take two taps. Bot Payments also support Apple Pay for a completely frictionless experience.

+

Check It Out Now

+

Try our demo @ShopBot to get a taste of what's coming. (Note: Our demo bot thinks it sells time machines, but they're not a part of what's coming. Sadly.) If you're looking to test a real payment with actual money, stop by our @TelegramDonate bot.

+

Telegram is an open platform, so bot developers can implement the necessary APIs and accept payments from users starting right now, without lengthy approval dramas. If you’re a bot developer, check out the docs immediately!

+

Behind the Scenes

+
+ +
+ +

At launch, most of the payments were handled by Stripe, but Telegram Bot Payments are a platform for payment providers all over the world. When accepting a payment from a user, the bot developer can choose between all available payment providers, selecting the one already used by the buyer or the one with the lowest commission.

+
+

UPD, 14.06.2017: Bot developers can now process payments from more than 200 countries via the global payment provider Paymentwall.

+

UPD, 02.06.2017: Yandex.Money and Payme are now also available as payment providers.

+

UPD, 01.09.2017: Rave by Flutterwave is now available, which is especially helpful for developers in Nigeria, Kenya, Ghana, South Africa, and Uganda.

+
+

This is just the beginning. In the next few days, payments will become available to developers in India via Razorpay, in Russia Qiwi will be joining the club a little later.

+

Follow our @BotNews channel to be the first to know about new providers joining.

+

If you’re a payment provider (especially in a developing country), click here to learn how to get on board.

+

Just Passing Through

+

Telegram acts as a messenger (pun intended) between the paying user, the bot developer, and their chosen payment system. The user sends their credit card details directly to the payment system. Then the payment system's response and the shipping details entered by the user are passed to the bot developer so that they can process the order.

+

Due to this structure, it is impossible for Telegram to handle complaints or cashbacks – any disputed payments are the responsibility of the bot developers, payment providers, and banks that participated in the exchange.

+

Since Telegram doesn't process the payments, we don't store and can't access any sensitive data. We also don't take any commission from payments and don't profit from these transactions.

+

Instead, we just do what every sheriff has to do with strangers passing through their turf: shoot the bad bots and award the good ones with a badge. We’re sure there’ll be plenty of good ones.

+

If You Are…

+ +

And if you're none of the above for some weird reason, be a user, do the right thing. Happy shopping, everyone!

+

+ +

May 18, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/permissions-groups-undo.html b/data/telegram.org/blog/permissions-groups-undo.html new file mode 100644 index 0000000000..0d2efdc7f5 --- /dev/null +++ b/data/telegram.org/blog/permissions-groups-undo.html @@ -0,0 +1,265 @@ + + + + + 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/photo-editor-and-passcodes.html b/data/telegram.org/blog/photo-editor-and-passcodes.html new file mode 100644 index 0000000000..bc8ca9a721 --- /dev/null +++ b/data/telegram.org/blog/photo-editor-and-passcodes.html @@ -0,0 +1,252 @@ + + + + + Photo Editor and Passcode Lock + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Photo Editor and Passcode Lock

+ +
+ +
+ +

Today’s update to our iOS and Android apps reflects the essence of Telegram — a combination of easy-to-use privacy tools and popular mass market features.

+

Photo Editor

+

Each day Telegram users share 35 million photos, and this number is growing by the hour. For comparison, Instagram users shared 70 million photos daily in December. Yet up until now, messaging app users couldn’t enjoy a photo editing experience on the level that is offered by photo-sharing apps. We’re changing this today.

+
+
+ +
+
+ + +

With the new photo editor, you can crop, rotate and auto-enhance photos before sending them. On top of that, you can use Photoshop-class granular controls for brightness, contrast, warmth, saturation, highlights, sharpening, blurring and more.

+

The auto-enhance tool is our favorite though — it can improve photos in an instant.

+
+ + + + +
+
+ +

Passcode Lock

+

Telegram is one of the few messaging apps that can be used on multiple devices at once. While this is definitely convenient, it also raises the bar when it comes to privacy. What if one of your Telegram devices, e.g. an iPad or another tablet, is sometimes used by your colleagues or family members?

+

In order to give you more control in such cases, we are introducing passcodes. Starting today, you can lock your iOS or Android device with a passcode – a simple 4-digit PIN or a longer password. The iOS app, and soon the Android app as well, can use passwords to encrypt the local database against such extreme cases as phone theft.

+
+ + + + + + + + +

+
+ +Without entering this passcode, no one will be able to access your Telegram messages. When Telegram is locked, notifications about new messages will not include texts or sender names, so private data stays hidden from prying eyes. + +
+

+ +


+
+ +

Since unlocking Telegram each time can get annoying, we implemented both manual and auto-lock. You can lock the app manually from the chats screen or enable auto-lock after a specified period of inactivity. iOS users can use Touch ID to unlock the app.

+

+
+ +

February 25, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/pin-and-ifttt.html b/data/telegram.org/blog/pin-and-ifttt.html new file mode 100644 index 0000000000..71f1a39ad7 --- /dev/null +++ b/data/telegram.org/blog/pin-and-ifttt.html @@ -0,0 +1,263 @@ + + + + + Pinned Chats and IFTTT Integrations + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Pinned Chats and IFTTT Integrations

+ +
+ +
+ +
+ +
+ +

If you’re like us, you probably have dozens of active chats on Telegram. But none of them matter when you miss a new message from your Mom. Or Spouse. Or Mad Boss. Today we’re launching Telegram 3.15, which allows you to pin important conversations to the top of your inbox.

+

This feature is also valuable for teams that coordinate their work over Telegram. Pinned chats offer an easy way of keeping work-related chats reachable in a predictable order whenever you open Telegram.

+
+
+ +
+
+ +

To pin a chat, long tap on it (swipe left on iOS) and select Pin. Easy! You can pin up to 5 chats to the top (plus 5 secret chats).

+

IFTTT (If This Then That)

+

Starting today, you can link your Telegram account with more than 360 other services by setting up “If This Then That” integrations (or “Applets”). This works with anything from social networks like Twitter and Instagram, to productivity tools like Gmail or Pocket, entertainment apps like Spotify or Pinterest, cloud services like Dropbox or Google Drive, and Internet of Things devices like Nest, LIFX, or Philips Hue.

+

Telegram is the first messaging app to be fully integrated with IFTTT. Unlike most services, we allow two-way interactions: You can control other services via Telegram, or receive notifications and content like photos and videos when they do something.

+

You can also invite the @IFTTT bot to any of your groups so members can collaboratively interact with your services or devices.

+
+
+ +
+
+
+
+
+
+ + +

To get started, talk to the @IFTTT bot, then enable some Applets or create your own. Since the IFTTT platform supports over 360 services, endless combinations are possible. Here are just a few examples:

+ +
+

Check out the IFTTT website for a full list of existing Telegram Applets and don’t hesitate to create your own.

+
+

Making Android Great Again, Part 2

+

Remember our promise to Make Android Great Again? We were serious. In Telegram 3.15 for Android, we bring you three great features: High-precision rotation and cropping in the photo editor, a new player for Youtube videos with Picture-In-Picture mode, and forwarding messages and media to secret chats.

+

1. At long last, you can make that horizon look horizontal. Rotate your photos by any small number of degrees in the updated photo editor.

+
+ +

Rotate and Crop

+
+ + +

2. Want to continue chatting while watching a YouTube video? Tap the Picture-In-Picture icon in the new sleek video player for YouTube/Vimeo links. The video will shrink, and you can drag it around the screen so that it doesn't get in the way. The new video player also toggles fullscreen mode when you rotate your phone accordingly.

+
+ +

Picture-In-Picture

+
+ +

3. Secret Chats are the most secure way to share data on Planet Earth, and it is only natural they don’t let you forward stuff from them. However, they don’t restrict you from importing texts and media into them. With Telegram 3.15 for Android, you can forward messages and media from Cloud Chats and Channels to Secret Chats.

+

We know many of you got a bit addicted to Telegram updates, and keep asking us for more. We're happy to oblige. Stay tuned for more updates coming this December!

+


+ +

December 7, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/pinned-messages-locations-playlists.html b/data/telegram.org/blog/pinned-messages-locations-playlists.html new file mode 100644 index 0000000000..4ea6e28a60 --- /dev/null +++ b/data/telegram.org/blog/pinned-messages-locations-playlists.html @@ -0,0 +1,282 @@ + + + + + Pinned Messages 2.0, Improved Live Locations, Playlists and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Pinned Messages 2.0, Improved Live Locations, Playlists and More

+ +
+
+
+ +
+ Introducing Pinned Messages 2.0, Improved Live Locations, Playlists and More +
+ +

Halloween is just around the corner and we're introducing new features to help organize your trick-or-treating. Practice your voodoo skills with multiple pinned messages in every chat, watch out for other zombies on the block with Live Locations 2.0, put suspenseful music into Playlists, and more.

+
+

If you'd like to read about this update in simple English and without all most of the Halloween stuff, try this page.

+
+

Multiple Pinned Messages

+

Pinned messages are a lot like chips, it's hard to stop at just one, which is why you can now pin multiple messages in any chat. Tap the top bar to jump between them – or use the new button if you want to see them all on a separate page.

+
+ +
+ +

In addition to channels and groups, pinned messages now work in one-on-one chats, useful for everything from shopping lists to friendly wagers and beyond.

+

Improved Live Locations

+

When friends share their live location, you can set up an alert that will notify you when they're close. Icons on the live location map now also show which direction they are facing.

+
+ +
+ +

Never pass each other again when meeting on the street, even if everyone around (including you) is dressed up as a mummy.

+

Playlists

+

When you send multiple songs at the same time, they'll be arranged together in a playlist – easier to play, forward, or comment on. Opening one of the songs will queue them all up in Telegram's built-in media player.

+
+ Playlist sent to a chat +
+ +

Sending multiple files together also displays them in one chat bubble. Just like with photo albums, you can always select each file or track individually.

+

Channel Post Stats

+

Comments have boosted subscriber activity in channels, and now we're introducing new tools for admins to track it. In addition to channel statistics, you can view stats for individual posts in your channel – including a list of public channels to which your post was forwarded.

+
+ Channel post stats page +
+ +

Sleek New Animations on Android

+

Meanwhile, our Android Frankensteins keep adding new animations, this time for sending messages and switching songs in the music player.

+
+ +
+ +

Also on Android: when viewing a photo you’ve received, you can edit and send it back right away, skipping the download-upload ritual. Just tap the brush button when viewing a photo to quickly mark a spot with an X, or put skull stickers on faces.

+

Jackpot

+

Monaco is gradually reopening for tourists, but there is another way to try your luck: send 🎰 to any chat and see if you hit the jackpot.

+
+ +
+ +

In case you missed it, this also works for 🎲, 🏀, ⚽️ and 🎯.

+

And Ghoulishly Delightful Animated Emoji

+

Given the occasion, we couldn't help but animate every spooky emoji we could find. To get one of these 👇 in a chat, simply send a message with a single emoji. When viewing animated emoji for ⚰️ or 🎃, tap on them for an extra thrill.

+
+ +
+ +

Even if you don’t dig 🗿 all the Halloween hype, we’ve got you covered animated:
+ +
+ +
+ +

How to Get This Update

+

The new version with these features is already available for all our Android users via Google Play or APK. If you're on iOS, you'll get the update as soon as either a) Apple finishes reviewing it OR b) you decide it's time to switch to Android. 👀 UPD: (October, 31) The iOS part of the update has now also been approved.

+

Now we'll get back to working on our costume. We're going as the Ghost of Group Chats Past: 256 members, no moderation tools and completely covered in green slime. See you on the other side!

+

+ +

October 30, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/pinned-messages-locations-playlists/world.html b/data/telegram.org/blog/pinned-messages-locations-playlists/world.html new file mode 100644 index 0000000000..2bfa008998 --- /dev/null +++ b/data/telegram.org/blog/pinned-messages-locations-playlists/world.html @@ -0,0 +1,278 @@ + + + + + Pinned Messages 2.0, Improved Live Locations, Playlists and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Pinned Messages 2.0, Improved Live Locations, Playlists and More

+ +
+
+
+ +
+ +
+ +

Starting today you can pin several messages in every chat, get notified when friends get near if they are sharing their Live Location, send music as Playlists, and more.

+

Multiple Pinned Messages

+

Each chat now supports multiple pinned messages. To jump between them, simply tap the top bar several times – or use the new button to see all pinned messages on a separate page.

+
+ +
+ +

In addition to channels and groups, pinned messages now work in one-on-one chats.

+

Improved Live Locations

+

When friends share their live location, you can set up an alert that will notify you when they're close. Icons on the live location map also show which direction people are facing.

+
+ +
+ +

Playlists

+

When you send multiple songs at once, they'll be arranged together in a playlist – easier to play, forward, or comment on. Opening one of the songs will queue them all up in Telegram's built-in media player.

+
+ Playlist sent to a chat +
+ +

Sending multiple files together also displays them in one chat bubble. Just like with photo albums, you can always select each file or track individually.

+

Channel Post Stats

+

Comments have boosted subscriber activity in channels, and now we're introducing new tools for admins to track it. In addition to channel statistics, you can view stats for individual posts in your channel – including a list of public channels to which your post was forwarded.

+
+ Channel post stats page +
+ + +

New Animations on Android

+

Our Android developers added new animations for sending messages and switching songs in the music player.

+
+ +
+ +

Also on Android: when viewing a photo you’ve received, you can edit and send it back right away, instead of downloading and uploading it again. Just tap the brush button when viewing a photo to quickly draw or put stickers on it.

+

Jackpot

+

Send 🎰 to any chat to see if you hit the jackpot.

+
+ +
+ +

In case you missed it, this also works for 🎲, 🏀, ⚽️ and 🎯.

+

And More Animated Emoji

+

We've animated some new emoji for Halloween. To get one of these 👇 in a chat, simply send a message with a single emoji. When viewing animated emoji in chats, try tapping on ⚰️ or 🎃 for a surprise.

+
+ +
+ +

If you are not a fan of Halloween, we've got another new animated emoji for you:

+
+ +
+ +

How to Get This Update

+

The new version with these features is already available for all our Android users via Google Play or APK. If you're on iOS, you'll get the update as soon as either a) Apple finishes reviewing it OR b) you decide it's time to switch to Android. 👀 UPD: (October, 31) The iOS part of the update has now also been approved.

+

And that's it for today, stay tuned for the next update!

+

+ +

October 30, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/polls-2-0-vmq.html b/data/telegram.org/blog/polls-2-0-vmq.html new file mode 100644 index 0000000000..b0e6a10f83 --- /dev/null +++ b/data/telegram.org/blog/polls-2-0-vmq.html @@ -0,0 +1,271 @@ + + + + + Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode

+ +
+ +
+ +
+ Introducing Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode +
+ +

Since we first added polls for groups and channels, they've been used for everything from deciding where to have lunch to organizing leaderless protests. Today we're expanding the range of possibilities with three new kinds of Telegram polls.

+
+ +
+ +

Visible Votes

+

Previously, all polls on Telegram were anonymous. With this update, you can create polls that allow everyone in the group to see who voted for what. Now you will know exactly which friends you disagree with on the matter of pineapple and pizza.

+
+ A poll that shows who voted for which option +
+ +

Naturally, you can still create anonymous polls to make sure nobody finds out it was you who voted for broccoli instead of cookies.

+

Multiple Answers

+

One of the best ways to settle the score is with polls that allow people to select multiple answers. Scheduling events, or choosing a playlist of songs for a party – sometimes you need more than one choice.

+
+ A poll that allows people to select multiple answers +
+ +

Our aunt who has a knack for statistics and exploring bizarre correlations kept asking for this feature – and we just couldn't say no. (33% of developers who didn't refuse this request were also found to be addicted to cheese.)

+

Quiz Mode

+

For the game show guru and “Who Wants To Be A Millionaire” contestant in all of us, polls now have Quiz Mode. Such polls have one correct answer and can power anything from trivia games to public service exams.

+
+ Quiz mode +
+ +

As if guessing right wasn't sweet enough, correct answers will trigger a shower of confetti.

+

Creating Polls

+

Polls can be created in groups or channels (they feel lonely in one-on-one chats). Simply choose the “Poll” option in the attachment menu. Type in your question, add answer options, choose the settings that fit your purpose best – and you're ready to go:

+
+ +
+ +

Bot API and Quiz Bot

+

All the new poll types are supported in today's update to our Bot API, so bot developers can build on this new functionality.

+

As an example, we've created a Quiz Bot that lets you create multi-question quizzes and share them with others. It also lets you add text or media before questions to help create exam-style prompts with graphs and tables – or better yet, your own Know Your Meme tests.

+

Once your quiz is ready, you can share it to a group or channel – or invite users to answer questions privately, in a chat with the bot. To see how this works, try our demo quiz: Who is Who in the 'Great Minds' sticker pack.

+
+ Demo Quiz +
+ +

The bot will keep tabs on how many questions users got right and how much time it took them to complete the quiz. It also keeps a global leaderboard for each quiz you create.

+

Message Corners

+

In addition to the new polls, our apps just got a new visual setting. If you find your Telegram messages too hip to be square (or round, depending on your platform), you can tweak the appearance of message bubbles in Settings:

+
+ +
+ +

Download Progress Counters on Android

+

Just like on iOS, Android users can now see exact progress counters when downloading or uploading files – if they're in the mood to count bits and bytes.

+
+ Download progress counters on Android +
+ +

And that's it for today. Here's to a good new year full of updates. Stay tuned!

+

+ +

January 23, 2020
The Telegram Team

+
+ +
+ +
+ +
+
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/polls.html b/data/telegram.org/blog/polls.html new file mode 100644 index 0000000000..1c007defe0 --- /dev/null +++ b/data/telegram.org/blog/polls.html @@ -0,0 +1,230 @@ + + + + + Polls: Bringing Choice to Communities + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Polls: Bringing Choice to Communities

+ +
+ +
+ +
+ +
+ +

Large communities on Telegram frequently use polls to coordinate their activities and stay in touch with their members. Today, we're rolling out a dedicated tool for polls in addition to existing bots like @vote. We hope the new built-in polls will be a welcome addition to groups with 100,000 members and channels with millions of subscribers.

+
+ +
+ +

Polls can be forwarded to increase reach and pinned for better visibility (and also to notify all members of the community).

+

At the moment, polls are anonymous, meaning that no one can see who voted for what. Going forward, we may introduce non-anonymous polls where the voters lists will be public, but such polls will be explicitly marked as non-anonymous.

+
+

Telegram has your back when it comes to privacy: we never disclose the private data you entrusted us with to third parties and never monetize it.

+
+
+

Image Search and Other Improvements on iOS

+

Back to more mundane matters, you can use Web Search again to find images when sending Photo & Video attachments or choosing profile pictures in our iOS app. Setting a Grinch avatar for Christmas has never been easier:

+
+ +
+ +

The Great iOS Bug Hunt goes on and the app received numerous fixes in version 5.1.1.

+

To name a few improvements: Clearing the cache in Settings > Data and Storage > Storage Usage now correctly reduces the space taken by the app. Files and media will keep downloading for a while after you close the app. You will see detailed progress when downloading and uploading files. We've also added online indicators for the ‘People’ section in search results.

+

Happy Winter Solstice!

+

+ +

December 22, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/privacy-discussions-web-bots.html b/data/telegram.org/blog/privacy-discussions-web-bots.html new file mode 100644 index 0000000000..16a6dc3480 --- /dev/null +++ b/data/telegram.org/blog/privacy-discussions-web-bots.html @@ -0,0 +1,284 @@ + + + + + Focused Privacy, Discussion Groups, Seamless Web Bots and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Focused Privacy, Discussion Groups, Seamless Web Bots and More

+ +
+ +
+ +
+ +
+ +

Telegram is about privacy. In 2014 we pioneered granular privacy settings in messaging. Today we are making them even more flexible with exceptions for group chats.

+

From now on, you can make something visible for all your classmates in one group chat and keep it private from, say, all your colleagues in another – with just two taps:

+
+ +
+ +

Settings will adjust automatically as people join and leave the groups. So when your half-brother unexpectedly gets a job as a data broker, you'll just need to kick him out of one group to update all your settings.

+

Who can see my phone number?

+

On Telegram, you can send messages in private chats and groups without making your phone number visible. But there may be cases when you want to make your number known (e.g. to all your coworkers), so we added a new dedicated privacy control – Who Can See My Number.

+
+ A screenshot of the redesigned Privacy & Security settings screen +

Redesigned privacy settings on iOS

+
+ + +

Meet Seamless Web Bots

+

We've made it easier to integrate bots with web services. Bots can now help you log in with your Telegram account on a website when you open a link. If you allow them to, you'll be logged in by the time the page loads in the browser:

+
+ A confirmation dialog that offers to open a link and optionally authorize on the website +
+ +

While this is purely optional, it opens the door for a vast variety of new bots. To try out this seamless authorization, press the ‘comments’ button under this post.

+

You can also make our sample @discussbot an admin in any of your broadcast channels to get a comments button under the posts you publish. The comments button opens a website where you are already logged in and ready to leave a comment. The bot will notify you if someone replies to what you wrote there.

+

Anyone can create similar bots to connect their existing services to Telegram on the fly. Integrating all kinds of social, gaming, productivity, dating or e-commerce services into your channels is now a breeze.

+

Broadcasts meet Group Chats

+

Telegram channels are a tool for broadcasting your thoughts to unlimited audiences. Telegram group chats offer a democratic way for communities of up to 200,000 members to discuss things.

+

Ever since we launched channels and groups, users have been asking us to add discussions to channels and announcements to groups. With this update, admins can add a group chat to their channel to serve as a discussion board:

+
+ +
+ +

Subscribers will see a ‘Discuss’ link on the bottom panel, and each new post from the channel will be automatically forwarded to and pinned in the discussion group.

+
+ +
+ +

View public channels

+

Speaking of channels, you can now view any public channel from the web – even if you aren‘t logged in to Telegram. The same also goes for those retro people who don’t have a Telegram account at all. Yet.

+
+ A public channel, as seen from the web +
+ +

Simply open the channel link in a browser and select “Preview channel” to see something like this: t.me/s/telegram

+

Scam Alerts

+

Telegram apps will now show a scam label for suspicious accounts.

+
+ Chat with a scammer +
+ +

iOS Goodies

+

In other news, Telegram 5.7 for iOS introduces thumbnails for PDF files. Keep in mind that Telegram lets you share files of any type, up to 1,5GB each in size (so you can telegram a PDF payload worthy of Elon's rockets).

+
+ PDF file with a thumbnail +
+ +

Telegram for iOS also catches up with the rest of our apps in terms of text links. You can now make any text a link to a website, keeping all the cords under the carpet.

+
+ Creating a text link on iOS +
+ +

Mind that people will get a warning about where exactly the link leads when they open it. (Hint: use URL shorteners if you want to rick-roll people).

+

Android Delights

+

As for Android, we've redesigned the majority of confirmation dialogs in the app, and improved the design for message search and adding people to groups. Additionally, the app got a new theme switcher in Chat Settings.

+
+ +
+ +

Have fun with all that and stay tuned for our next updates.

+

+ +

May 31, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/privacy-revolution.html b/data/telegram.org/blog/privacy-revolution.html new file mode 100644 index 0000000000..f100e74092 --- /dev/null +++ b/data/telegram.org/blog/privacy-revolution.html @@ -0,0 +1,226 @@ + + + + + Hiding Last Seen Time - Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Hiding Last Seen Time - Done Right

+ +
+ +
+ +

Each day our volunteer-driven support team gets several thousand requests from our users to help them hide their Last Seen time. We knew it's important, and have been working hard to get this feature right. We wanted to make sure that Telegram users would have unprecedented precision and flexibility, without the usual tradeoffs.

+

Starting today, you can specify exactly who will see your Last Seen time in both our iOS and Android apps. You can choose between the three basic options (“Everybody”, “My Contacts” and “Nobody”) and add any number of exceptions into the “Always Share With…” and “Never Share With…” sections.

+
+

For example, this way you can make your Last Seen time available to everybody but your boss, or to nobody with the exception of your marriage partner (or vice versa, it's up to you). If you’d like to share your Last seen time only with your contacts plus the members of some work-related group you have, you can do it in just a few taps. This makes countless combinations possible.

+
+

Why Is This Important?

+

To make things fair, you won’t see Last Seen timestamps for people with whom you don‘t share your own. That’s why it‘s important to have granular controls — Telegram’s precision helps you avoid difficult choices. For example, you don't need to choose between hiding your Last Seen from your boss and being able to know when your best friend was online. You can have both.

+
+ + +
+
+ +

Last Seen Recently

+

Of course, the absence of a Last Seen timestamp makes it difficult to know whether the person you're about to contact is a regular user of Telegram and will be able to read your message. That is why even if the exact Last Seen time is hidden, you will still see an approximate value, like “last seen recently” (i.e. from one minute ago to about 3 days) or “last seen within a month”. This keeps stalkers away, but makes it possible to understand whether a person is reachable over Telegram.

+

Speaking of inactive users, we're not going to have too many of them soon. Starting today, Telegram accounts will self-destruct after 6 months of inactivity by default.

+

Self-Destructing Accounts

+

Big companies like to accumulate data about their users and keep it for an indefinite time. Telegram is not a commercial organization and we value our disk space greatly. Last year we introduced self-destructing messages, today we are adding self-destructing accounts.

+

From now on, if you stop using Telegram and do not login for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct – with options ranging from 1 month to 1 year.

+


+ +

These new features are already available in our iOS and Android apps. Stay tuned for more privacy-related updates.

+
+ +

The Telegram Team,
November 19, 2014

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/profile-videos-people-nearby-and-more.html b/data/telegram.org/blog/profile-videos-people-nearby-and-more.html new file mode 100644 index 0000000000..1d2c5e897a --- /dev/null +++ b/data/telegram.org/blog/profile-videos-people-nearby-and-more.html @@ -0,0 +1,315 @@ + + + + + Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More

+ +
+
+
+ +
+ Introducing Profile Videos, Improved People Nearby, 2 GB File Sharing and More +
+ +

Today's update brings Profile Videos along with improved People Nearby features, unlimited file sharing with up to 2 Gigabytes per file, mini-thumbnails for your chat list and notifications, group stats, and much more.

+

Profile Videos

+

You can now upload a video to your profile – and choose any frame you like for your static profile picture in chats. Capture yourself in action, or wink and wave at people like you're in a magical picture from Harry Potter.

+
+ +
+ +

Same as with any videos you upload, our media editor will help you enhance quality – or decorate yourself with animated stickers.

+

As your mood changes, you can quickly switch back to a previous profile photo or video by tapping ‘Set as Main’. Great for rewinding time and staying young forever.

+

Soften Skin

+

Speaking of the media editor, any photo or video you take with the front-facing camera now has a soften skin option in the media editor. But you don't need it to look fabulous, you already are fabulous.

+
+ +
+ + + + +

Improved People Nearby

+

Profile videos make meeting new people a dozen times more interesting, and we've beefed up the People Nearby section for the occasion.

+

When people contact you via the People Nearby section, you will see how far away they are. And when you start a chat with someone nearby, Telegram will suggest a greeting sticker to break the ice. Luckily, all our stickers are extroverts.

+
+ Improved People Nearby +
+ +

Now that people are carefully emerging into this brave new world, it's time to make friends and repopulate the earth compare your sticker collections. Head over to Contacts > Find People Nearby and try tapping on ’Make myself visible’.

+

Mini-thumbnails

+

Ever wondered whether the incoming picture is just another meme or that selfie you've been waiting for? Get an idea of what media is in a message right away thanks to the new chat list thumbnails.

+
+ Mini-thumbnails in the chat list +
+ +

The new thumbnails also appear in notifications and message search results. Never lose a cat photo again.

+
+

Speaking of previews, you can hold on a profile picture in the chat list to preview messages without opening the chat. This feature is from 2018, but we had a dream in which a talking squid told us to mention it here.

+
+

Filter New Chats from Non-Contacts

+

Thanks to People Nearby and groups with up to 200,000 members, you can always find someone to chat with. Public figures sometimes have the opposite problem and may wish to tone down the attention they receive — we've got this covered too.

+

If you're getting too many messages from non-contacts, try the new switch in Privacy & Security settings to automatically archive and mute new chats from people not in your contacts. You can access these chats anytime from the Archive folder and bring them back to the main chat list in a tap.

+
+ +
+ + + +

Group Stats

+

Owners of large groups with over 500 members can now view beautiful, detailed graphs about their activity and growth. Group stats also show a list of top members by number of messages and average message length.

+
+ +
+ +

By the way, the minimum number of subscribers to get Channel Stats has been reduced to 500 as well. 🎉 We're planning to roll out access to group stats for admins of all groups with 100 members or more in the near future.

+

Android Extras

+

On Android, the music player has been redesigned with sleek new icons and an expandable track list. Tap the button on the left to control looping, shuffling and to reverse the track order so your playlist can moonwalk with you.

+

The message input bar will grow smoothly as you type a long message. And the video editor now allows cropping and rotating videos – to help you hide any evidence you were filming vertically.

+
+ +
+ +

Multiple Accounts on Telegram Desktop

+

Telegram lets you stay signed in on 3 accounts from different phone numbers without logging out. Our mobile users have been enjoying this feature since 2017, and today it's coming to the multi-platform Telegram Desktop.

+
+ +
+ +

As always, this doesn't require an active connection to your phone – all our apps are completely self-sufficient.

+

More Animated Emoji

+

Our animated emoji army keeps growing (note to self: build a bigger barracks). To get one of these 👇 in a chat, simply send a message with a single emoji – and watch it jump to life.

+
+ +
+ +

Be careful, one of them bites. And we're not allowed to tell you which one.

+

If you're looking for something more interactive, try sending a single ⚽️ in any chat to see if you score a goal:

+
+ +
+ +

And One More Thing

+

Since 2014, Telegram users have been sharing files up to 1,5 GB each, which happens to be 93 times larger than 16 MB (which is a totally random number, we have no idea what it could possibly mean).

+

From now on, you can send unlimited numbers of media and files of any kind – up to 2 GB each.

+
+

And that‘s it for today. We're now in the middle of the year — with eight major updates behind us and long-awaited features just around the corner. Stay tuned!

+

+ +

July 26, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/protected-content-delete-by-date-and-more.html b/data/telegram.org/blog/protected-content-delete-by-date-and-more.html new file mode 100644 index 0000000000..6da624710b --- /dev/null +++ b/data/telegram.org/blog/protected-content-delete-by-date-and-more.html @@ -0,0 +1,324 @@ + + + + + Protected Content, Delete by Date, Device Management and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Protected Content, Delete by Date, Device Management and More

+ +
+
+
+ +
+ Protected Content, Delete by Date, Device Management and More +
+ +

Today's update brings tools to prevent others from saving content in groups and channels, the ability to delete messages from specific dates, new ways to manage your connected devices, an option to post anonymously in public groups on behalf of your channel and more.

+

Protected Content in Groups and Channels

+

With this update, we're helping creators protect the content they publish on Telegram and ensure that it is available only for their intended audience.

+

Group and Channel owners who want to keep their content members-only can restrict message forwarding from their chat, which also prevents screenshots and limits the ability to save media from posts.

+
+ +
+ +
+

To change users' ability to forward messages open the Group or Channel Info page > Group / Channel Type > Restrict Saving Content.

+
+

Delete Messages by Date

+

Telegram users have complete control over their digital footprint and can delete any messages from a conversation at any time. With this update, you can clear chat history from a specific day or date range in any one-on-one chat.

+
+ +
+ +

To open the calendar, tap the date bar that pops up as you scroll through the chat – then choose which days to clear.

+
+

Clearing history by date currently only works in one-on-one chats, but messages in any chat can be set to auto-delete one day, week, or month after sending.

+
+

Manage Connected Devices

+

You can use Telegram on all your devices at the same time, and the Devices menu helps you control where your account is logged in. We've added a new button to quickly link a desktop device and a setting to automatically log out inactive devices after some time.

+
+ +
+ +

Tap any device in the list to view more information and toggle whether it can accept calls or new Secret Chats.

+
+

Telegram is available for every platform – check out telegram.org/apps to download the app on your other devices.

+
+

Anonymous Posting in Public Groups

+

Public Groups and Channel Comments allow for discussions of any topic in massive communities with thousands of members. These groups are used for everything from defending democracy to chatting with fans, which is why we've added the ability to appear as a channel when sending messages in these chats.

+
+ +
+ +

Tap the profile picture next to the message bar and choose one of your channels – the messages you send after that will appear with the name and photo of the channel instead of your personal account.

+
+

When posting as your channel, you’ll also see the channel name at the top of your message bubbles.

+
+

New Ways to Log In via Call

+

Starting today, some mobile devices will be offered the option to receive a login call from Telegram and then enter several digits of the phone number that called – instead of getting codes via text message.

+
+ +
+ +

Responses to Join Requests

+

When you request to join a group or channel and its admin responds with a message, you will see which community they are from at the top of the chat.

+
+ +
+ +

As of this update, bot admins can contact users requesting to join a chat where they are an admin — even if the user didn't communicate with the bot before. This opens up endless possibilities: from simply accepting the rules of a group chat before joining, to passing an admission test, to making a small donation to the creators of a channel.

+

Global Chat Themes on Android

+

Our September update introduced 8 new themes that you could set for individual chats – and now they're available for your entire app on Android (iOS users received this in the previous update).

+

Chat Settings have been fully redesigned, giving the new themes center stage. Built by the Telegram Team, every theme has a Day and Night mode, colorful animated background and gradient message bubbles.

+
+ +
+ +

Like all themes, you can personalize these designs and tweak the colors or change the pattern. For more options and custom settings, tap ‘Browse Themes’ to edit and share your creations.

+

Text Recognition on iOS 13+

+

On devices with iOS 13 and above, Text Recognition (Live Text) is enabled for photos in Telegram chats, allowing you to quickly select, copy and search without touching your keyboard. This image recognition is securely handled entirely on your device.

+
+ +
+ +

The list of supported languages is managed by Apple, so if yours isn't in the list yet, stay tuned for future OS updates.

+

Format Text in Media Captions on iOS

+

A little bit of bold or italics can add just the right emphasis to a message, and now you can use all text formatting options in media captions as well – including text links.

+
+ +
+ +

Before you ask why Android isn't getting this feature – it's because Android already has it. 😉

+

Redesigned Contact Info on iOS

+

Contacts, Groups and Channels have updated info pages with a new look in the style of iOS 15.

+
+ Redesigned contact info on iOS +
+ +

And that's it for now. Let's see how many more features we can build for you this year.

+

+ +

December 7, 2021
The Telegram Team

+ +
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/reactions-spoilers-translations.html b/data/telegram.org/blog/reactions-spoilers-translations.html new file mode 100644 index 0000000000..7d17033f44 --- /dev/null +++ b/data/telegram.org/blog/reactions-spoilers-translations.html @@ -0,0 +1,300 @@ + + + + + Reactions, Spoilers, Translation and QR Codes + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Reactions, Spoilers, Translation and QR Codes

+ +
+
+
+ +
+ Reactions, Spoilers, Translation and QR Codes +
+ + +

Telegram's 12th update of the year introduces reactions, message translation, themed QR codes, hidden text (spoilers), and more.

+

Reactions

+

Telegram was the first messaging app to add animated and interactive emoji, giving users unparalleled ways to express themselves in chats. Today some of these emoji become available as reactions to share feelings and feedback – without sending any messages.

+
+ +
+ +

Double tap a message to send a quick 👍 reaction. For more reactions like 😁 🎉 😱 🔥 👎, tap once on the message (or press and hold, if on iOS). Each reaction appears with its own unique animation.

+
+

You can change your default reaction to another emoji in Settings. Android: Chat Settings > Quick Reaction. iOS: Stickers and Emoji > Quick Reaction.

+
+

Reactions are always on in private chats. In groups and channels, the admins decide whether to turn on reactions and choose which reaction emoji are available in the chat. This enables many different ways to collect feedback – from simple likes ❤️ to upvote 👍 and downvote 👎 systems, and beyond.

+ + +
+

Admins can control reactions via their group or channel's Info Page > Edit > Reactions. For more feedback options, try channel comments and our powerful polls.

+
+

Spoilers

+

To discuss the fates of Ciri or Peter Parker without spoiling the fun for others, select any part of your text when typing and choose the new 'Spoiler' formatting. This will hide the selected part of the message in the chat, as well as in the chat list and notifications.

+
+ +
+ +

When you're ready to see what's hidden, tap the spoiler to reveal its text.

+

Message Translation

+

Over half a billion people around the world use Telegram not only to stay in touch with friends, but also to chat in public groups and view content from channels – in every language imaginable. Now you can translate any message into another language, right in the app.

+ + +
+ +
+ +

Enabling Translation in Settings > Language adds a dedicated Translate button to the context menu when selecting a message. You can also exclude any languages you speak fluently – which will hide the translate button for those messages.

+
+

Translation is available on all Android devices that support Telegram, but requires iOS 15+ on Apple devices. The list of available languages depends on your phone's operating system.

+
+

Themed QR Codes

+

You can generate QR codes for any users that have a public username. This also works for groups, channels and bots, making it easy to show someone your favorite blog or fan club.

+
+ +
+ +

Tap the new QR code icon next to the username of a person (or from a chat’s info page), choose the colors and pattern that fit best, then print, post or share your QR code to other apps.

+
+

A QR code for your own username can be obtained in Settings.

+
+

New Menus for macOS

+

We've redesigned all the context menus in Telegram for macOS – adding some new shortcut hints and introducing beautifully animated icons for every single menu item in the app.

+
+ +
+ +

More Interactive Emoji

+

Our animators also added new interactive versions of 🔥 😁 🤩 😢 😭 😱 ❄️. Send any of them in 1-on-1 chats, then tap to unleash a full-screen effect for you and your partner.

+
+ +
+ +

Thank you all for an incredible year. Here's to making 2022 even greater. 🎉

+

+ +

December 30, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/replies-mentions-hashtags.html b/data/telegram.org/blog/replies-mentions-hashtags.html new file mode 100644 index 0000000000..1afaafb35a --- /dev/null +++ b/data/telegram.org/blog/replies-mentions-hashtags.html @@ -0,0 +1,238 @@ + + + + + Reinventing Group Chats: Replies, Mentions, Hashtags and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Reinventing Group Chats: Replies, Mentions, Hashtags and More

+ +
+ +
+ +

Group chats have not evolved much since they first appeared in messaging apps many years ago. Today's new features bring group chat communication much closer to what it should look like in 2015. iOS, Android, OSX and Telegram Web get them first.

+

Replies

+

To reply to a specific message in a group chat, simply tap on it (double-tap on iOS) and choose Reply. Easy as that!

+
+ + + + + +

+ +

The person you replied to will be notified about your message even if s/he muted the group chat — their notification settings for you personally apply in this case.

+

Replies also make group chats much easier to navigate. If you tap on the quote, the app scrolls up to the original message.

+

Mentions

+

If you want several people within a group chat to get instantly involved in the conversation, you may now also mention them in a message, provided they have a username:

+
+ + +

+
+ +

They will be notified about this message, even if they muted the group chat — unless they've muted you personally, of course!

+

Hashtags

+

Another new way of bringing structure to group chats is by using hashtags. Any word starting with a “#” will be clickable. Tap on a hashtag to get instant search results from your Telegram messages.

+
+ + +
+
+ +

Forwarding with comments

+

On top of this, you can now add a comment to the stuff you forward. This comment will be shown before the forwarded messages.

+
+

Group chats are becoming larger and livelier — a Telegram group may include up to 200 members that share thousands of messages daily. We hope that these new tools will help you bring order and clarity to the chaos of a thriving group chat.

+

+ +

March 19, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/replies-mentions-stickers.html b/data/telegram.org/blog/replies-mentions-stickers.html new file mode 100644 index 0000000000..af38987e40 --- /dev/null +++ b/data/telegram.org/blog/replies-mentions-stickers.html @@ -0,0 +1,257 @@ + + + + + Better Replies, Stickers & Invitations + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Better Replies, Stickers & Invitations

+ +
+ +
+ +
+ +
+ + +

Since 2015 when we first introduced replies, the maximum group size on Telegram has increased by 100 times – from 200 max members to 20,000. These days you can get new mentions or replies in group chats many times during a day – and it’s important not to miss those messages.

+

Starting with Telegram 4.3, whenever somebody replies to you or mentions you in a group, you’ll notice this straight away by the ‘@’ badge in the chats list:

+
+
+ +
+
+ + +

If you have new replies/mentions in a group, you can now instantly reach them by tapping the new ‘@’ button when inside the chat. This button will disappear once you’ve read all the relevant messages.

+

Favorite Stickers

+

Anyone can create and upload stickers on Telegram. As a result, thousands of new stickers are added to the platform each day, and some of us have dozens of sticker sets installed.

+

Starting today, anyone with five or more sticker sets installed can mark individual stickers as ‘favorites’, and have them always accessible at the top of the sticker panel in the ‘star’ section.

+
+
+ +
+
+ +

Stickers of the Group

+

Speaking of stickers, large groups with 100 members and more can now choose an official sticker set for all the members of the group to see and use while they're chatting in the group — without the need of adding it to their panels.

+
+ +

Group Stickers

+
+ +

Invite Friends

+

The ‘Invite Friends’ section (accessible from Contacts) has been completely redesigned. Your contacts that are not on Telegram yet but have many of their friends already using it are now listed at the top. If you invite any of them to join, they’ll be welcomed by tens of Telegram veterans among their contacts:

+
+ +

Invite Friends to Telegram

+
+ +

…And More

+

As always with new releases, we've included several small goodies you may also like:

+
    +
  • Twitch videos are now supported in the Telegram in-app player, so you can watch Twitch streams in Picture-in-Picture mode while chatting with your friends.
  • +
  • When on a Telegram voice call, you can now check the signal strength thanks to the new indicator.
  • +
  • On iOS, you can edit any photo you pasted directly to a chat from clipboard before sending.
  • +
  • On Android, when forwarding a message, you can long tap to select multiple recipients.
  • +
  • On Android, when viewing photos in Shared Media, you can go to the place in chat where the photo was posted.
  • +
  • On Android, if you have many new messages in many active chats, synchronization will happen much, much faster.
  • +
+

+ +

Summer is over. Stay tuned, another update is already brewing in our dungeons!

+

September 3, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/scheduled-reminders-themes.html b/data/telegram.org/blog/scheduled-reminders-themes.html new file mode 100644 index 0000000000..6d9f505a90 --- /dev/null +++ b/data/telegram.org/blog/scheduled-reminders-themes.html @@ -0,0 +1,264 @@ + + + + + Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy

+ +
+ +
+ +
+ Introducing Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy +
+ +

In our previous update, we added a handy menu when you hold the send button. Today we're populating this menu with a new option that helps you plan ahead.

+

Hold the ‘Send’ button in any chat and select ‘Schedule Message’ to automatically send things at a specified time in the future (DeLorean not included).

+
+ +
+ +

Scheduling also works in your ‘Saved Messages’ chat, turning your planned posts into reminders. Be your own time-travelling secretary – whether it's about a dentist appointment next week, or waking up in time for pizza delivery.

+
+ +
+ +

Whenever a scheduled message or reminder is sent, you get a special notification marked with a 📅, so you don't get caught off-guard by messages you planned in the past.

+

Custom Cloud Themes

+

You could first customize Telegram's appearance way back in 2017. Today's update makes this easier than ever across all platforms, including our native desktop apps.

+

Choose a pre-set accent color or pick something unique from the color wheel, and the app will adjust all elements accordingly. See how it looks in your favorite color, blue – no, yellow!

+
+ +
+ +

You can now easily create new themes based on your color and wallpaper choices, then fine-tune them manually or share right away. Each theme has a sharing link which allows anyone to switch to your theme and wallpaper in just two taps.

+
+ Creating a new theme on iOS +
+ +

When you change your theme, it gets updated for all its users. This way you can update your app's looks to evolve as Telegram updates – or to change with the seasons.

+

To try out cloud themes, take a look at Sky Blue or Desert. These will work for both iOS and Android, and we solemnly swear to update them to acid green on orange when you least expect it.

+

Redesigned Message Options

+

On iOS, we have condensed message options into a single menu for forwarding, replying and more. You can now also select any portion of the message to copy or share, instead of only the full text.

+
+ +
+ + +

New Privacy Settings

+

Telegram groups can be public and may hold up to 200,000 members each. When launching them, we were thinking of campuses, conventions and spaces where you could properly brag about your cats. However, Telegram communities are also increasingly used by people to organize themselves in the face of oppression.

+

We believe that all people have a right to express their opinions and communicate privately. To further protect these rights, we‘re expanding Telegram’s arsenal of Privacy Settings today.

+

If you set Who Can See My Phone Number to ‘Nobody’, a new option will appear below, allowing you to control your visibility for those who already have it. Setting Who Can Find Me By My Number to ‘My Contacts’ will ensure that random users who add your number as a contact are unable to match your profile to that number.

+

If, like the majority of our users, you rely on uploading phone contacts to identify friends and family members on the app, this setting won't get in your way.

+

More Animated Emoji

+

Regardless of whether you‘re fighting for freedom or queuing for coffee, you’ll likely find a use for the new additions to our animated emoji family.

+

As before, send a single 😁, 😧, 😡, 💩, 😢 or 😮 to unleash their spirit in motion.

+
+ +
+ +

And that's all, folks! While waiting for our next update, check out this brief history of Telegram. Or, if you're not into reading, run a bath and enjoy these animated rubber duck stickers.

+

+ +

September 5, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/search-and-media.html b/data/telegram.org/blog/search-and-media.html new file mode 100644 index 0000000000..e7b6239671 --- /dev/null +++ b/data/telegram.org/blog/search-and-media.html @@ -0,0 +1,232 @@ + + + + + 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/sessions-and-2-step-verification.html b/data/telegram.org/blog/sessions-and-2-step-verification.html new file mode 100644 index 0000000000..81108f82a9 --- /dev/null +++ b/data/telegram.org/blog/sessions-and-2-step-verification.html @@ -0,0 +1,220 @@ + + + + + Active Sessions and Two-Step Verification + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Active Sessions and Two-Step Verification

+ +
+ +
+ +

We know you love Telegram for its seamless multi-device sync. And since there are native Telegram apps for all major mobile, tablet and desktop OSs, a lot of you folks must be logged into your Telegram accounts from several devices at once.

+

Today's Telegram update, in addition to rich link summaries, adds Active Sessions to your Privacy and Security settings. This screen shows all your logged in devices with IP info. You can also close any sessions that are outdated or (God forbid!) suspicious.

+
+ +
+
+ +

Two-Step Verification

+

Another addition to the Privacy and Security section is Two Step Verification. It allows you to set up a password that will be required every time you log into your account from a new device – in addition to the code you get in the SMS.

+

Be careful though: if you forget this password, you won't be able to access your messages from other devices. We recommend setting up a recovery e-mail or at least a hint for your password, if you decide to turn on Two Step Verification.

+
+ +

+
+ +

Stay safe!

+

+ +

April 8, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/share-preview.html b/data/telegram.org/blog/share-preview.html new file mode 100644 index 0000000000..3196d9b936 --- /dev/null +++ b/data/telegram.org/blog/share-preview.html @@ -0,0 +1,269 @@ + + + + + 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-files.html b/data/telegram.org/blog/shared-files.html new file mode 100644 index 0000000000..c5af8c0350 --- /dev/null +++ b/data/telegram.org/blog/shared-files.html @@ -0,0 +1,231 @@ + + + + + Shared Files and Fast Mute + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Shared Files and Fast Mute

+ +
+ +
+ +

A huge advantage of Telegram over any other tool is sharing large documents. Since Telegram's launch in 2013, you can send files up to 1.5 GB and access them from any of your devices, including computers. Perfect for everything from studying to sharing personal archives.

+

For this iOS and Android update, we have fully rewritten the Shared Media section. From now on, you can use the ‘Files’ overview to see all documents that were shared in a chat. It is also possible to search for specific files using the instant search.

+
+
+ + + +

+
+ +

Any document you receive in Telegram can be forwarded to email or other apps – just open the file and tap on the Share button. In addition, Android users will find a ‘Share’ option in the file‘s context menu (tap on ’…' next to the file inside a chat).

+

Bonus for iOS users: Telegram is now supported in the iOS8 sharing menu – you can open it while you're viewing any document on your iOS device.

+

Mute Notifications

+

You can now temporarily mute notifications from particular contacts and groups for 1 hour, 8 hours or 2 days. On Android, open the ‘…’ menu in a chat and choose ‘Mute notifications’. On iOS, go to group or contact info and tap on Notifications. iOS8 users can now also use interactive notifications to mute a contact or group for 8 hours.

+
+
+ + + +

+
+ +

Multisearch

+

Instead of looking for the right search box, just type your query in the new universal search field and get instant results — contacts, chats, groups, usernames or messages.

+
+
+

+
+ +

February 1, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/shared-links.html b/data/telegram.org/blog/shared-links.html new file mode 100644 index 0000000000..f7034c0274 --- /dev/null +++ b/data/telegram.org/blog/shared-links.html @@ -0,0 +1,221 @@ + + + + + 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/shared-media-scrolling-calendar-join-requests-and-more.html b/data/telegram.org/blog/shared-media-scrolling-calendar-join-requests-and-more.html new file mode 100644 index 0000000000..9799a921f6 --- /dev/null +++ b/data/telegram.org/blog/shared-media-scrolling-calendar-join-requests-and-more.html @@ -0,0 +1,343 @@ + + + + + Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More

+ +
+
+
+ +
+ Introducing 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 high-speed scrolling and a calendar view, an admin approval setting for invite links, global chat themes for your entire app, and more.

+

Hyper-Speed Scrolling for Shared Media

+

Every Telegram user has unlimited cloud storage – and each chat has a Shared Media page that shows all the photos, videos, files and music that have been sent there. We've added a new date bar on the side of the page, which you can drag up and down to scroll through shared media faster.

+
+ +
+ +

To get a better look, pinch to zoom in and out, so you can see anywhere from 2 big thumbnails to a dozen small squares per row.

+

Calendar View for Shared Media

+

To quickly find media from a specific time, tap on the date bar to open a calendar interface with media previews for each day – then tap to see all the media from that date.

+
+ Calendar view in shared media +
+ +

In addition to the new tools for jumping between past and present, you can now filter shared media to show only photos, only videos, or both.

+
+ New menu with filtering options +
+ +
+

To view shared media, simply tap the header at the top of your screen in any chat and scroll down. To open the new menu, tap Menu Android on Android or Menu iOS on iOS.

+
+

Join Requests for Groups and Channels

+

Invite links let you give users the opportunity to join your group or channel on their own time – whether you share the link privately or turn it into a QR code on a billboard is up to you. When you create additional invite links for your chat, there is now a Request Admin Approval setting, which gives admins more control over who is able to join and see the chat.

+
+ +
+ +

When a user opens a link with Admin Approval turned on, they will see a button to send a join request that admins can manage from a new bar at the top of the chat. From there, admins can view an applicant's public profile pictures and bio, then approve or dismiss their request.

+
+

For example, you could post an invite link to your poetry channel on social media – then approve only your close friends and people in purple to see your writing.

+
+ + +

Unique Names for Invite Links

+

Admin Approval can be applied to any link in the 'Additional Invite Links' section – we've also added the ability to give all of those links unique names, so you can label them for better organization.

+
+ List of invite links with custom names visible only to admins +
+ +
+

Link names will be especially helpful if you're using all the different options that exist for invite links, such as limits on duration, number of uses, etc.

+
+

Global Chat Themes on iOS

+

Our last update introduced 8 new themes that you could set for individual chats – and now they're available for your entire app on iOS (with Android soon to follow). Appearance Settings have been fully redesigned, giving these themes center stage. Built by the Telegram Team, every theme has a Day and Night mode, colorful animated background and gradient message bubbles.

+
+ +
+ +

Like all themes, you can personalize these designs and tweak the colors or change the pattern. For more options and custom settings, tap ‘Chat Themes’ to edit and share your creations.

+ + +

Transit Times for Shared Locations on iOS

+

You can show where you are or where you're headed by sending a location from the attachment menu Attach in the message bar. Tapping a shared location pulls up a map of the area – which now shows you the travel time to get there by Foot foot, Car car, or Public Transport public transport. To see detailed directions or get a taxi to the location, tap on the travel time to open it in your preferred app.

+
+ New transit time buttons on iOS +
+ +
+

Transit times are shown for both static and live locations – so you can see how long it will take to meet your friends while they're on the move.

+
+

Instant Media Captions for iOS

+

The text you type in the message bar now automatically converts to a caption when you attach media, so you'll never have to retype or cut and paste what you just wrote. This also works with Cloud Drafts – so you can type out the message on your computer, then simply attach the photo from your phone and send it all together.

+
+ +
+ +
+

Naturally, both transit times and instant media captions will be added to our Android app in the coming updates.

+
+

Settings updated for iOS 15

+

Settings on iOS have been redesigned to match the style of iOS 15, including streamlined Notifications Notification and Stickers Sticker settings. The Devices Devices section now gives you a clearer overview of your active sessions with new icons – tap any device to see more details or log out from it remotely.

+
+ +
+ +
+

Remember that locations shown for your devices are based exclusively on their IP addresses. This data is not always accurate, so don't be surprised if your laptop suddenly travels to Iceland while you're sleeping.

+
+

More Interactive Emoji

+

This update brings new interactive emoji. Send a single 👻 👎 🤮 😂 💸 or 🎃 in any private chat, then tap the emoji to unleash its full-screen effect.

+
+ +
+ +

If your chat partner also has the chat open, you will both see the effects and feel the vibrations simultaneously.

+
+

As you know from our previous update, this magic also works with 🎆 🎉 🎈 👍 💩 and ❤️.

+
+

Winter is coming, but our next update is racing to beat it. Stay tuned!

+

+ +

November 3, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/silent-messages-slow-mode.html b/data/telegram.org/blog/silent-messages-slow-mode.html new file mode 100644 index 0000000000..9c474f5cd9 --- /dev/null +++ b/data/telegram.org/blog/silent-messages-slow-mode.html @@ -0,0 +1,296 @@ + + + + + Silent Messages, Slow Mode, Admin Titles and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Silent Messages, Slow Mode, Admin Titles and More

+ +
+ +
+ +
+ 5.10 update cover +
+ +

The previous update brought more movement to Telegram – this one brings more peace of mind. You can now message friends freely when you know they are sleeping, studying or attending a meeting.

+

Simply hold the Send button to have any message or media delivered without sound.

+
+ +
+ +

Your recipient will get a notification as usual, but their phone won't make a sound – even if they forgot to enable the Do Not Disturb mode.

+
+ Silent notification on the lock screen +
+ +

This also works in groups, should you get an urgent idea at five in the morning – but not urgent enough to wake up everyone in your work chat.

+

Slow Mode

+

In case a group you manage is getting hard to follow, the Group Permissions section now features a Slow Mode switch.

+
+ Slow Mode settings in the Group Permissions section +
+ +

When an admin enables Slow Mode in a group, you will only be able to send one message per the interval they choose. A timer will show how long you have to wait before sending your next message.

+
+ Slow Mode timer as seen in a user's input field +
+ +

Slow Mode can make conversations in the group more orderly, while raising the value of each individual message. Keep it on permanently, or toggle as necessary to throttle rush hour traffic.

+

Admin Titles

+

If new time-lord powers aren't enough, group owners can now set custom titles for admins like ‘Meme Queen’, ‘Spam Hammer’ or ‘El Duderino’.

+
+ Custom title section on the admin rights screen +
+ +

As with the default admin labels, custom titles are shown with every message in the group so members know that they‘re talking to the designated ’Myth Buster'.

+
+ A message from an admin with a custom title in a group +
+ +

To add a custom title, edit the admin's rights in Group Settings.

+

Timestamps and Improved Scrubbing

+

Videos now display thumbnail previews as you scrub through, to help you find the moment you were looking for.

+

If you add a timestamp like 0:45 to a video caption, it will be automatically highlighted as a link. Tapping on a timestamp will play the video from the right spot. This also works if you mention a timestamp when replying to a video.

+
+ +
+ +

Timestamps are also supported for YouTube videos, in case you want to mark your favorite moments when sharing a Kurzgesagt episode.

+

Animated Emoji

+

When you have animated stickers, why not go one step further and get animated emoji? To check them out, send a single ❤️, 👍, 😒, 😳 or 🥳 to any chat.

+
+ +
+ +

If your life feels a little too animated recently, Sticker Settings now offer a toggle for looped playback. When disabled, animated stickers will play just once then stay still.

+

Android's New Attachment Menu

+

Android’s attachment menu got a makeover, giving media more real estate. Larger thumbnails make it easier to pick photos and videos at a glance, and swiping up will reveal your full Gallery for better browsing.

+
+ +
+ +

You can scroll left and right through the other attachment options like locations, polls and music. When selecting media, tap ‘…’ to send items as uncompressed documents.

+
+ A screenshot of the options from the '...' menu +
+ +

Accent Colors for Night Mode on iOS

+

iOS users can now choose accent colors for night themes. The night doesn't always have to be black and blue, after all.

+
+ +
+ +

Comments Widget

+

Comments.App, our tool for commenting on channel posts, now lets you add a comments widget to your website.

+

With the widget in place, Telegram users will be able to log in with just two taps and leave comments with text and photos, as well as like, dislike and reply to comments from others.

+

They can also subscribe to comments and get notifications from @DiscussBot.

+
+ A screenshot of the Comments Widget featuring a photo sent as a reply to another comment +
+ +

Open this page in your browser to try the new widget – it doesn't support Instant View pages… yet. 😈

+

That’s all for now, and don’t worry — the next Telegram update won’t be sent silently.

+

+ +

August 9, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/stickers-meet-art-and-history.html b/data/telegram.org/blog/stickers-meet-art-and-history.html new file mode 100644 index 0000000000..bda6891a72 --- /dev/null +++ b/data/telegram.org/blog/stickers-meet-art-and-history.html @@ -0,0 +1,338 @@ + + + + + When Stickers Meet Art And History + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

When Stickers Meet Art And History

+ +
+ +
+ +

Today Telegram launched a new kind of stickers – a free emotion-based platform for artists. We mentioned several technological and architectural points that make Telegram stickers a completely new experience – open, free and limitless. But there’s another way in which they are unique, and it also has a lot to do with our values.

+

When designing our first set of stickers, we didn’t want to use just any cartoon characters to express emotions. Instead we decided to portray people we respect most. These are great artists, poets, actors, scientists and leaders.

+

We'd like to give them credit for their contributions to human civilization, and we hope that millions of Telegram users share our respect for these outstanding individuals.
Don't forget to check out Part 2: MOAR stickers!

+
+
+ +
+
Abraham Lincoln approves
+
+ +
+
+ +
+ + +
+
Salvador Dali unlocks achievement
+
+ +
+
+ +
+ + +
+
Albert Einstein explains
+
+ +
+
+ +
+ + +
+
Mahatma Gandhi likes where this is going
+
+ +
+
+ +
+ + +
+
Charlie Chaplin had a bad day
+
+ +
+
+ +
+ + +
+
Steve Jobs laughs out loud
+
+ +
+
+ +
+ + +
+
Kafka is not happy. He never is...
+
+ +
+
+ +
+ + +
+
John Lennon, but...
+
+ +
+
+ +
+ + +
+
Richard Wagner's told you
+
+ +
+
+ +
+ + +
+
Nikola Tesla is unimpressed
+
+ +
+
+ +
+ + +
+
One doesn't simply send a Tolkien sticker
+
+ +
+
+ +
+ + +
+
Mark Twain, huh?
+
+ +
+
+ +
+ +
+
That Freudian scowl...
+
+ +
+
+ +
+ + +
+
And the famous Monroe kiss
+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/stickers-revolution.html b/data/telegram.org/blog/stickers-revolution.html new file mode 100644 index 0000000000..e60ea9afc4 --- /dev/null +++ b/data/telegram.org/blog/stickers-revolution.html @@ -0,0 +1,231 @@ + + + + + Custom Sticker Sets + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Custom Sticker Sets

+ +
+ +
+ +
+

Check out Pavel's Channel for some cool sticker sets »

+
+

Starting today, artists can submit their custom sticker sets via the Telegram @stickers bot. Each sticker set gets a permanent link, so that users can easily add new stickers and share them with friends.

+

This enables artists of the world to unleash their creativity and help Telegram users customize their experience. Our in-house artist (responsible for the graphic art in this blog) created the Animals set as an example. If you have Telegram installed and updated, this link will open the set: https://telegram.me/addstickers/Animals.

+
+ +

+
+ +

Independent designers already began submitting their sticker sets, and we notice stickers like Flags of the World or Vicky uploaded to the @stickers bot.

+

Sharing Stickers

+

Sending a link isn‘t the only way to share a sticker set. When you receive a sticker from a set you do not currently have installed, simply tap on it and choose ’Add to Stickers‘ (’Info' on iOS) to preview and add the whole set.

+
+ + +

+
+ +

Once you've added a set, its stickers become available via emoji tooltips or the dedicated sticker panel. The iOS app now has one too — you can manually switch it on/off in Chat Settings — Stickers.

+

The new Stickers menu allows you to view, uninstall and share your sticker sets.

+
+ +

+
+ +

This update is available for Android and iOS and is coming to other apps soon. Sticker sets on Telegram are now fully equipped to spread virally and devour the world.

+

+ +

The Telegram Team,
May 19, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/stickers.html b/data/telegram.org/blog/stickers.html new file mode 100644 index 0000000000..c970ba1480 --- /dev/null +++ b/data/telegram.org/blog/stickers.html @@ -0,0 +1,225 @@ + + + + + Stickers Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Stickers Done Right

+ +
+ +
+ +
+

This January 2015 post has some outdated info.
Check out our custom sticker sets announcement instead.

+
+

At Telegram, we try to reinvent the ordinary tools. The concept of stickers is not an exception. We've always felt that stickers in messaging apps sucked, because they typically provided a limited and paid experience in a walled-garden environment.

+

Today's update to Telegram for Android, iOS, Windows Phone and Desktops introduces a new kind of stickers – a free platform for artists and users willing to share emotions, built using an efficient and open technology.

+
+ + + + + +
+ +

Telegram stickers are grouped around emotions, not characters. They do not clutter the interface, but are shown only when they are relevant – you will see a list of emotionally corresponding stickers whenever you start a message with an emoji. All our stickers are and will be completely free, and you can always create and share your own stickers.

+

You can find the initial 14 stickers in this post.
And dozens more will soon follow.

+

Sharing your own stickers

+

To share stickers of your own, just save your sticker in WebP format with a transparency layer and send it to your friend as a document in Telegram (e.g. via Telegram Desktop). It will be shown as a sticker. Thanks to the WebP file format, Stickers on Telegram are displayed 5x faster compared to the other formats usually used in messaging apps.

+

Creating new stickers

+

Telegram is focused on people who like to create content. If you want your sticker to be seen by all Telegram users in the context menu corresponding to one of the emojis, you are welcome to submit it via a chat with our Stickers bot – telegram.me/stickers.

+

Freelancers can also sell us their work – we normally pay $100 for the exclusive use of a 512x512px sticker. Note that we accept only high-quality stickers that meet our criteria. Please study the stickers that we have designed in-house for the launch.

+
+
+ +

January 2, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/supergroups.html b/data/telegram.org/blog/supergroups.html new file mode 100644 index 0000000000..97a041bc98 --- /dev/null +++ b/data/telegram.org/blog/supergroups.html @@ -0,0 +1,251 @@ + + + + + Admins, Supergroups and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Admins, Supergroups and More

+ +
+ +
+ +

Telegram groups are democratic by design. Everyone can invite new members and change the group‘s name and photo, which is ideal for small bands of friends or coworkers. But Telegram can also support much larger communities that need more administration. To make life easier in big groups, we’re introducing admins today.

+

From now on, you can choose how your groups will operate. By default, all members are still in control. But if you want more order, you can throw the switch and appoint additional administrators to your group.

+
+ +

+
+ +

If you enable the new restricted mode, only administrators will be able to add new people and change the name and photo of the group. Admins also have the power to remove other members from the group.

+

Supergroups

+
+

UPD: Check out Supergroups 2.0: Pinned posts, Public groups, new moderation tools!

+
+

Telegram groups have always been several steps ahead of the competition. You could have groups of up to 200 people communicating efficiently using replies, mentions and hashtags. Now it's time to go further.

+

Ever since our launch in 2013, our users have been telling us they would like to migrate even larger communities to Telegram. As of today, once your group is full, you can upgrade it to a supergroup that supports up to 5000 members.

+
+ +

+
+ +

Supergroups are optimized to host large online communities and will load quickly, even if you‘ve missed many messages while away. Here’s what you need to know about how they work:

+
    +
  • New members can see the entire message history when they join.
  • +
  • Deleted messages will disappear for all members.
  • +
  • Ordinary members can only delete their own messages.
  • +
  • Supergroups are muted by default and send fewer joined/left notifications.
  • +
+

All official Telegram clients are getting this update today.

+
+

Please note that you need the latest version of Telegram to access a supergroup. You may want to wait a little bit before upgrading your groups so that the update rolls out to all Telegram users, and they can see their groups.

+
+

iOS Bonus: Best In-App Notifications Ever

+

iOS users will enjoy our new in-app notifications. Pull down on a notification to expand it, view the full text of the message or preview attached media.

+
+ +

+
+ +

You can immediately send a quick reply or a sticker — all without leaving that particular spot in some other conversation.

+

Android Bonus: Quick Share for Channels

+

Meanwhile, Android users can enjoy the new quick sharing menu in channels. Just tap on the forwarding buttons right next to channel messages.

+
+ +
+
+ +
+

We have a few more surprises up our sleeve for this year. Stay tuned for more updates!

+

+ +

The Telegram Team,
November 25, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/supergroups5k.html b/data/telegram.org/blog/supergroups5k.html new file mode 100644 index 0000000000..efe0b447f1 --- /dev/null +++ b/data/telegram.org/blog/supergroups5k.html @@ -0,0 +1,232 @@ + + + + + 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 new file mode 100644 index 0000000000..60d1a1c77b --- /dev/null +++ b/data/telegram.org/blog/tdlib.html @@ -0,0 +1,228 @@ + + + + + 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/telegram-5-ios.html b/data/telegram.org/blog/telegram-5-ios.html new file mode 100644 index 0000000000..3e94c9e1eb --- /dev/null +++ b/data/telegram.org/blog/telegram-5-ios.html @@ -0,0 +1,268 @@ + + + + + Introducing Telegram 5.0 for iOS + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Introducing Telegram 5.0 for iOS

+ +
+ +
+ +
+ +
+ +

For the last couple of years we've been quietly rebuilding Telegram for iOS from scratch with Swift – a programming language released by Apple as a faster alternative to Objective C.

+

Today Telegram 5.0 goes live for all our iOS users, becoming the most popular messaging app written fully in Swift. This new version of Telegram looks just like the old one, but is slicker, more battery-friendly and faster (which is surprising, given how fast the old one already was).

+
+ +
+ +

The new app is superior in many ways. We love the new smooth animations in chats. Messages will now sync quickly, even if you haven‘t opened Telegram for a long time and there’s a LOT to sync. We‘ve also improved the app’s activity in the background to ensure that all of your unmuted chats are always up to date.

+

Step aside — and back

+

The new expandable in-app notifications will help you focus on whatever you‘re doing in the app without having to ignore incoming messages. When a notification arrives, pull it down to open the relevant chat. When you’re done with the interruption, simply close it to get right back to what you were doing.

+
+ +

Expanded Notification

+
+ +

This works everywhere in the app, including when you are viewing media or reading Instant View articles.

+

Make every chat count

+

Previously, badge counters could become less useful after you've joined a group or two with 100,000 members. Today we're making private chats great again.

+

You can now switch the unread counter to display the number of unmuted chats with unread messages. So instead of 1001 for a thousand messages in a muted group and one very important message from your dog, your badge counter will look like this:

+
+ +

One Unread Chat

+
+ +

You can adjust this behavior in Settings > Notifications and Sounds.

+

When was that again?

+

We've improved navigation in busy chats (and elsewhere). Scroll up a little to see the date when the messages you are viewing were sent. Tap this date to go to the first message of the day in question.

+

The bugs are dead. Long live the bugs!

+

As much as we would‘ve liked to, we couldn’t port over any of the bugs from the Objective C version. All the old bugs are now gone forever — or, should we say, fixed. We might‘ve added some brand new bugs while coding the new version. But don’t worry, we'll fix those in no time. The same goes for any small features that may be missing.

+

Meanwhile on macOS…

+

You can now use swipe gestures to navigate the interfaces on Telegram for macOS. Most notably, you can swipe to reply and the chats list now works the same way it does on iOS: swipe right to Mark as Read/Unread, and left to Pin, Mute or Delete.

+
+ +

Swipe Left or Right for Options

+
+ +

Fancy MacBook Pro owners just got advanced Touch Bar support to help them send stickers and media, control buttons in alerts and pop-up windows and more.

+
+ +

Stickers and more on MacBook Pro

+
+ +

Other new features include auto-night mode settings and a photo editor to rotate and crop pictures before sending. You can also drag and drop photos, media, and documents to change the order in which they will be sent.

+

…And Telegram Desktop

+

As for our universal Telegram Desktop app, it just got a massive overhaul in the Settings department. The new layout is similar to what you're used to in our mobile apps:

+
+ +

Telegram Desktop Settings

+
+ +

The latest Telegram Desktop also features improved caching for images and GIFs, as well as new local storage settings. Go to Settings > Advanced > Local Storage to control how much disk space Telegram uses on your machine.

+

We've also redesigned the theme selector to make it easier to choose a day and night theme that suits you best. Remember, you can make your own themes – or check out some themes created by other users.

+
+ +

Pick Your Colors

+
+ + +

And that's it for today. Stay tuned for more updates on all our platforms.

+

+ +

October 1, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/telegram-me-change-number-and-pfs.html b/data/telegram.org/blog/telegram-me-change-number-and-pfs.html new file mode 100644 index 0000000000..a1e2f9bdc0 --- /dev/null +++ b/data/telegram.org/blog/telegram-me-change-number-and-pfs.html @@ -0,0 +1,228 @@ + + + + + Telegram.me, Changing Numbers and PFS + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram.me, Changing Numbers and PFS

+ +
+ +
+ +
+

Our iOS and Android apps got updated with three new features today.

+
+

Opening a telegram.me/YourUsernameHere link on your phone will now automatically fire up your Telegram app and open a chat with that user. You can share username links with friends, write them on business cards or put them up on your website.

+
+ +
+ +
Here's what people will see if they don't have Telegram yet
+ +

Changing Your Phone Number

+

It is easy to switch to Telegram and retain your social graph, since it is based on phone numbers. But what if you need to change the phone number itself? As of today, you can change your number in Telegram — and keep everything, including all your contacts, messages and media from the Telegram cloud, as well as all your secret chats.

+
+ + + +
+
+ +

Your mutual contacts (people in your contacts, who also have your number) will get your new number added to your contact in their address book unless you have blocked them in Telegram. This makes changing numbers even easier.

+

Perfect Forward Secrecy

+

Last but not least, Telegram's Secret Chats now support Perfect Forward Secrecy. What this means is that your Secret Chats will now automatically change encryption keys after a period of time, in order to keep past communications safe. This way you no longer need to manually re-create Secret Chats to achieve this level of security.

+

+ +

And that's it for today. Stay tuned for more updates coming your way on all platforms!

+
+

December 1, 2014
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/telegram-x.html b/data/telegram.org/blog/telegram-x.html new file mode 100644 index 0000000000..1a46515ba4 --- /dev/null +++ b/data/telegram.org/blog/telegram-x.html @@ -0,0 +1,262 @@ + + + + + Telegram X: Progress through Competition + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram X: Progress through Competition

+ +
+ +
+ +
+ +
+ +
+

UPD: As of October 2018, Telegram X for iOS has replaced the older Objective-C based client. If you're looking for the best iOS experience, switch to the main Telegram app.

+
+

Our mission is to make Telegram faster, slicker and easier to use with each passing month. Competition is the soul of progress, so at first we got plenty of inspiration from other messengers that spurred us on. But as years passed, we saw less and less innovation coming from competitors, who now seem content merely to adapt Telegram features to their platforms with an average lag of two years.

+

In this environment, we started relying on internal competition to feed our flames. This is why for the last two years we've been developing a new generation of Telegram clients in parallel with the main versions.

+

The Telegram X project features apps written from scratch, with an entirely new code base and without all the legacy components that our older apps have accumulated through the years.

+

Telegram X

+

The goal of Telegram X is to reinvent Telegram and explore new frontiers in speed, ease of use, quality of animations and all other aspects. Today we are glad to present two new official apps – Telegram X for Android and iOS.

+

Both these apps are experimental and may or may not eventually replace the existing official apps. But even if they don't, they will speed up the development of Telegram by allowing us to quickly test new approaches and technologies.

+

X for Android

+

Telegram X for Android was born in the furnaces of a contest for Android developers that our founder launched two years ago. The winner then used the power of TDLib to create a stunning app with a special focus on smooth animations.

+

X for Android is faster and more battery-efficient than the original app and features a sleek new design:

+
+ +
+ +

Telegram X also supports a clean bubble-free mode for chats, where messages and photos get more breathing space – and photos in channels assume the full width of the screen:

+
+ +

Bubble-free Photo in a Channel

+
+ +

In Telegram X, you can tap and hold on any chat to preview its content without opening. This works everywhere, including in the forwarding and sharing menus, as well as in the Calls tab and ‘Groups in Common’.

+

The app also offers an abundance of useful swiping actions. For example, you can switch between ‘Chats’ and ‘Calls’ by swiping left and right on the main screen. You can also swipe right on any message to instantly open the forwarding menu:

+
+ +

Swipe right to share

+
+ +

The app includes a reimagined music player and attachment menu, as well as optimized profile pages with quick access to shared media. You can easily switch between different types of shared media by swiping.

+
+ +

New profile page with shared media

+
+ +

This is by no means an exhaustive list of features, Telegram X for Android is full of little surprises in every corner.

+

The app is now ready to begin its experimental journey with new features scheduled to appear as early as next week.

+

X for iOS

+
+

UPD: As of October 2018, Telegram X for iOS has replaced the older Objective-C based client. If you're looking for the best iOS experience, switch to the main Telegram app.

+
+

Telegram X for iOS is written entirely in Swift and is significantly lighter, faster and more battery-efficient than the original app, built with Objective C.

+

The design and feature set are closer to what iOS users have learned to expect from Telegram, but you will definitely notice the smooth animations and faster speed and loading times on most iPhones.

+

The internal structure of Telegram X for iOS is also much better optimized for the things that are expected of a Telegram app in 2018 and beyond. Just as with X for Android, today's X release for iOS is the beginning of a long journey.

+

+ +

Look out for our next updates, both to the experimental versions and their classic counterparts.

+

+ +

January 31, 2018,
The Telegram Team

+

+ +
+

P.S. Today, we're also releasing TDLib – a tool for building custom Telegram apps. Check out the announcement here »

+
+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/telegraph.html b/data/telegram.org/blog/telegraph.html new file mode 100644 index 0000000000..7dbb2cb8f0 --- /dev/null +++ b/data/telegram.org/blog/telegraph.html @@ -0,0 +1,238 @@ + + + + + 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/themes-accounts.html b/data/telegram.org/blog/themes-accounts.html new file mode 100644 index 0000000000..829b00b601 --- /dev/null +++ b/data/telegram.org/blog/themes-accounts.html @@ -0,0 +1,247 @@ + + + + + Themes, Multiple Accounts and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Themes, Multiple Accounts and More

+ +
+ +
+ +
+ +
+ +

Happy winter holidays, everyone! To reinforce the festive mood, we‘re updating Telegram for the second time this December, adding features you’ve been asking for.

+

With version 4.7 for iOS, you can change what your Telegram looks like in the new Appearance settings. Choose between four different themes, including a minimalistic one (“Day”) and two dark themes (“Night” and “Night Blue”). The “Day” theme also allows you to pick an accent color for the entire app, like pink or purple.

+
+ +
+ +

Multiple accounts

+

The Android app already supported multiple themes, so it had to go further with 4.7 by supporting multiple accounts. You can add up to three accounts with different phone numbers to your Telegram app, and then quickly switch between them from the side menu. Notifications will keep coming from all accounts, unless you change this in the Notification settings.

+
+ +
+ +

Quick replies

+

Telegram now supports quick replies on both mobile platforms. To use them, just swipe left on any message in a chat.

+
+
+ +
+
+ +

In case you missed it…

+

Telegram 4.6, released earlier this month, introduced new granular settings for auto-downloading media, better link previews, albums in Secret Chats, improved security, and embeds for messages from public groups and channels. Here’s what an embed of a Telegram message looks like when included on a web page:

+

+ +

+
+ +

To get the HTML-code for embedding a message, open its t.me link in a web browser:

+
+
+
+ +

Have a happy new year – and stay tuned for the product updates we are going to announce in January.

+

+ +

The Telegram Team,
December 30, 2017

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/translations-iv2.html b/data/telegram.org/blog/translations-iv2.html new file mode 100644 index 0000000000..d61a63107a --- /dev/null +++ b/data/telegram.org/blog/translations-iv2.html @@ -0,0 +1,276 @@ + + + + + Custom Languages, Instant View 2.0 and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Custom Languages, Instant View 2.0 and More

+ +
+ +
+ +
+Introducing custom languages, IV 2.0, a new design for Android and more +
+ + + +

Telegram's Translations Platform allows you to suggest better wording for Telegram interfaces in any language. We've recently rolled out support for most mainstream languages, and translations are already underway.

+

Today's update brings equal treatment to the smaller linguistic communities around the world. Anyone can now use the translation platform to create their own custom language packs – and translate Telegram into any minority language or local dialect, be that Māori, Scottish Gaelic or Transliterated Klingon.

+

We've made it easy to spread your translations. To translate the interface of your app, simply follow the dedicated sharing link of the desired language. Sharing links can be obtained in the translation panel.

+
+ Applying a custom language +
+ +

Each language also gets its own public group for discussions. Here are the links for the Catalan language, for example:

+ +

Once a user switches to your translation, all changes you apply in the interface will be applied immediately. The days of waiting for the apps to update or passing around localization files are over.

+

Instant View 2.0

+

Another unique feature of Telegram is the Instant View technology that allows Telegram users to view web pages in a consistent way, with zero loading time.

+

Today we're expanding the platform with support for right-to-left languages, blocks of related articles, image links, tables, nested lists, horizontal scrolling, collapsible text blocks and much more.

+

Now you can get beautiful instant view pages for even very complex articles. If you're reading this from one of our newly updated mobile apps, try this Wikipedia page for an example.

+
+ +
+ + + +

Soon we will announce a new crowdsourcing contest to make Instant View pages available for an even larger part of the internet.

+

The Great iOS Bug Hunt

+

We've made close to a thousand fixes and improvements to the iOS app since the major release of version 5.0. The new Telegram for iOS 5.1 features some 400 minor improvements.

+

New Design for Android

+

Telegram for Android has now reached version 5.0 and received a major overhaul in the design department. It is now much easier to access shared media from the profiles of users, groups and channels:

+ + +
+ +
+ +

Shared media now offers high quality crisp previews, increased loading speed, more info in the links and files sections, and more efficient design.

+
+ Shared Files +
+ +

The Settings screens were redesigned for a more streamlined experience:

+
+ +
+ +

Following in the footsteps of the iOS app, Android users can take advantage of the new detailed settings for the badge counter in Settings > Notification and Sounds:

+
+ Badge Counter Settings +
+ +

We've upgraded the photo selector for profile pictures so that you can choose the correct head to be displayed on your profile:

+
+ Choose an area to use for the photo +
+ +

Last but not least, you can zoom videos during playback and browse full-resolution images sent as documents just like normal photos, by swiping left and right.

+

+ +

December 10, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/trending-stickers.html b/data/telegram.org/blog/trending-stickers.html new file mode 100644 index 0000000000..6ea0731043 --- /dev/null +++ b/data/telegram.org/blog/trending-stickers.html @@ -0,0 +1,262 @@ + + + + + Trending Stickers, Storage and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Trending Stickers, Storage and More

+ +
+ +
+ +

Telegram users share hundreds of millions of stickers every day. Many of these are custom-created on the spot using pictures of friends or local politicians. Others are made by professional artists from all over the world. Starting today, we will be showcasing popular sticker sets made exclusively for Telegram in the new Trending Stickers tab.

+
+
+ +

Sticker panel

+
+
+ +

Trending tab in settings

+
+ +

You can find the new Trending tab on the Stickers panel and in Telegram Settings. We've made adding new stickers easier for people who have many sets installed. When you go over the limit of 200 sets, older unused stickers are archived automatically. You can reactivate them from the Archived Stickers tab in Sticker Settings later.

+

Personal storage

+

Many people have been using a chat with themselves or a small group to store their favorite messages or personal media. Starting today, there's no need for such lifehacks anymore. Just head to the Contacts tab and open the storage chat with yourself by tapping on your number at the top.

+
+
+ +

New contacts screen

+
+
+ +

Your storage chat

+
+ +

Feel free to forward favorite messages to the storage chat or send photos you want to quickly pass between devices. The handy ‘Shared Media’ sections will make finding content a breeze and you can always use in-chat Search for specific queries.

+

You can also access everything you send to the storage chat on any number of devices you connect, so this can serve as a simple but effective way to replace services like Dropbox right inside your messenger.

+

Group previews

+

Invite links are a handy way to add people to groups, even when they‘re not on Telegram yet. Today we’re making it easier for you to understand just what you're joining when you open them.

+
+ +

New group previews

+
+ +

As of Telegram v.3.11., you will be able to see who else is in the group and how many members it has before joining it.

+

Android Camera and More

+

If you're running Android 4.1. or higher, Telegram just got a brand new camera interface so that you can take photos in fewer taps. It is also now possible to preview bot content before sending.

+
+
+ +

Bot content preview

+
+
+ +

Check out before sending

+
+
+ +

Another nice bonus in this Android update is that you can now download large media and files 2x to 4x faster.

+

New looks and new viewer for Telegram Desktop

+

Telegram Desktop users can now enjoy an in-app player for videos. We've also improved the design in chats, adding sleek new message bubbles.

+
+ +

New desktop video player

+
+ + + +

And that‘s about all we’ve got for you in version 3.11.
As usually, stay tuned for more updates – coming after our little summer break.

+

+ +

August 3, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/unread-replace-2x.html b/data/telegram.org/blog/unread-replace-2x.html new file mode 100644 index 0000000000..3b20dcf11b --- /dev/null +++ b/data/telegram.org/blog/unread-replace-2x.html @@ -0,0 +1,259 @@ + + + + + Replace Media, Share vCards, Mark as Unread, 2X Voice Messages, and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Replace Media, Share vCards, Mark as Unread, 2X Voice Messages, and More

+ +
+ +
+ +
+ +
+ +

Telegram 4.8.3 for iOS and 4.8.10 for Android are out today, bringing several nifty features and improvements.

+

Replace Media and Add Captions

+

Sending the wrong picture by accident is rarely fun. On Telegram, it was already possible to delete the message for everyone and send a new one instead. Now you can just replace photos or videos with the correct versions right away:

+
+ +
+ +

Start editing the message, then tap the paperclip button to replace the attached media. You can also add captions to photos or videos that didn't have one.

+

Double-Time Playback for Voice and Video Messages

+

You'll like this one if your friends enjoy sending long and thoughtful voice notes. From now on, you can switch to 2X playback and hear people get to the point faster.

+
+ +

Works with voice and video messages

+
+ +

We‘ve spent a few extra hours to ensure that your friends don’t sound like Helium-breathing chipmunks as a result. Well, most of the times.

+

Mark as Read or Unread

+
+ +
+ +

This offers a quick way to get less important messages out of the way and highlight the chats that require your future attention.

+

Share Detailed Contact Info

+

Sometimes you want to share more info about a contact than just one number. With this update, you can select what data you want to send when sharing a contact. For example, several phone numbers or other vCard fields.

+
+ +

Choose which fields to share

+
+ +

Try sharing a contact that has multiple fields with data to check this out.

+

One More Thing

+

When you open a chat from Global Search and then go back, you will return to the search results and keep your position in the list.

+

And Three More (on Android 💪)

+

Android users are getting a few extra goodies with version 4.8.10. Tap and hold on profile pictures in the chats list to preview chats:

+
+ +

Tap and hold on the profile picture

+
+ +

Use the “create link” option in the formatting menu to make text URLs:

+
+ +

Select some text, then tap '...'

+
+ +

Last but not least, it is now possible to cancel sending messages before they are sent.

+

And that's it for today, stay tuned for our next updates!

+

+ +

June 27, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/unsend-and-usage.html b/data/telegram.org/blog/unsend-and-usage.html new file mode 100644 index 0000000000..b4b9878776 --- /dev/null +++ b/data/telegram.org/blog/unsend-and-usage.html @@ -0,0 +1,273 @@ + + + + + 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/unsend-privacy-emoji.html b/data/telegram.org/blog/unsend-privacy-emoji.html new file mode 100644 index 0000000000..510f91e58c --- /dev/null +++ b/data/telegram.org/blog/unsend-privacy-emoji.html @@ -0,0 +1,261 @@ + + + + + Taking Back Our Right to Privacy + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Taking Back Our Right to Privacy

+ +
+ +
+ +
+ Unsending messages, anonymized forwarding, improved search and VoiceOver/TalkBack support +
+ + +

For us, your private data is sacred. We never use your data to target ads. We never disclose your data to third parties. We store only what is absolutely necessary for Telegram to work.

+

In 2013, we gave millions of people power over their data with end-to-end encryption.

+

Today, we are giving hundreds of millions of users complete control of any private conversation they have ever had. You can now choose to delete any message you have sent or received for both sides in any private chat. The messages will disappear for both you and the other person – without leaving a trace.

+

Unsend Anything

+

The “Unsend” feature we introduced 2 years ago was only available for messages sent by you and only for 48 hours. Now you can remove messages you have sent or received, and there is no time limit. You can also fully delete any private chat from both your and the other person's device in just two taps.

+
+ +
+ +

Anonymous Forwarding

+

To make your privacy complete, we’ve also introduced a way to restrict who can forward your messages. When this setting is enabled, messages you send that are forwarded by another user will no longer lead to your profile – instead they will show your display name in plain unlinked text. This way the messages you send can't be used to verify that you were their author.

+
+ +
+ +
+

You can enable this option in Settings > Privacy and Security > Forwarded Messages.

+
+

By the way, you can now also restrict who can view your profile photos.

+

Settings Search

+

Since the Settings section keeps getting bigger, we’ve added a search tool that allows you to quickly find the settings you're looking for.

+
+ +
+ +

You can also use this tool to find answers for Telegram-related questions based on our FAQ.

+
+ +
+ +

Emoji Search and GIFs

+

GIF and Sticker Search has been upgraded on all mobile platforms – with an updated interface that looks better (and finds more cats). You can press and hold to preview a GIF before sending.

+

Sticker packs now have unique icons, which makes it easier to select the right set. Large GIFs and video messages on Telegram are now streamed, so you can start watching them without waiting for them to fully download.

+

On Telegram for Android, you can now use keywords in many languages to find a specific emoji. If we are missing a keyword for an emoji, you’re welcome to suggest it here – emoji search results will constantly update and improve in real time, without the need to update your Telegram app.

+
+ +
+ +

You’ll also see a list of related emoji when typing a message. If you like an emoji enough to send it without any accompanying text, the emoji will appear larger in the chat.

+

VoiceOver and TalkBack

+

We’ve added support for screen-reading features – VoiceOver on iOS and TalkBack on Android. These accessibility platforms give spoken feedback so that you can use Telegram without needing to see the screen.

+
+

Tell us what you think the next update should be.

+
+

March 24, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/usernames-and-secret-chats-v2.html b/data/telegram.org/blog/usernames-and-secret-chats-v2.html new file mode 100644 index 0000000000..509d6a1637 --- /dev/null +++ b/data/telegram.org/blog/usernames-and-secret-chats-v2.html @@ -0,0 +1,222 @@ + + + + + Usernames and Secret Chats 2.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Usernames and Secret Chats 2.0

+ +
+ +
+ +

Telegram apps for both Android and iOS have been updated today.

+

Usernames

+ +

From now on, you can choose a public username in the Settings section of Telegram. If you do, anyone will be able to find you by your username and contact you – without having to know your phone number.

+

To find people by username, just start typing any name in the search field of the Contacts section. Once entered at least 5 characters, you will see the Global Search section in your search results. This list contains people with corresponding usernames.

+

You can find out more details about usernames in our FAQ.

+ +

Secret Chats 2.0

+ +

Secret Chats got a major upgrade today.

+ +

The self-destruct timer in Secret Chats now includes more small values ranging from 1 to 60 seconds. In chats with these shorter self-destruct timers, the countdown for photos, videos and voice messages will begin only after they are first opened. So the content will never disappear before you have seen it or listened to it.

+ +

Photos with short self-destruct timers now work in 'Tap and Hold to View' mode, and you will receive a notification each time the recipient of a self-destructing photo makes a screenshot of it.

+ +
+ +
+
+ +

October 23, 2014
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/verifiable-apps-and-more.html b/data/telegram.org/blog/verifiable-apps-and-more.html new file mode 100644 index 0000000000..277dc0b29d --- /dev/null +++ b/data/telegram.org/blog/verifiable-apps-and-more.html @@ -0,0 +1,392 @@ + + + + + Verifiable Builds, New Theme Editor, Send When Online and So Much More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Verifiable Builds, New Theme Editor, Send When Online and So Much More

+ +
+ +
+ +
+ Dude in a jacket inspecting the hologram of a mechanical dog to verify it's built according to the blueprints provided. +
+ + + +

Telegram is the only mass market messaging app with open source apps. Since 2013, this not only allows independent researchers to verify the integrity of end-to-end encryption, but also helps look for vulnerabilities (or backdoors 😈).

+

As of this update, Telegram becomes the first messaging app to allow you to independently verify that the code on GitHub is the exact same code that was used to build the app you downloaded from App Store or Google Play. Security researchers are welcome to check out our Guide to Reproducible Builds for iOS and Android.

+

But we know security isn't the only reason you love Telegram – so we've also added dozens of new features and improvements. Gather round, this blog post is a long one.

+

Theme Editor 2.0

+

Using the new theme editor in Chat Settings (or Appearance Settings on iOS), you can quickly tweak the style of elements in Telegram chats and add awesome gradients to both your messages and your background. Switch between tabs (Main Color, Background, My Messages) to see how deep this rabbit hole goes:

+
+ +
+ +

Once you're done editing, you can quickly share the result of your work with friends so that they can continue tuning your theme.

+

By the way, this update includes dozens of new cool patterns you can apply to your background. Our favorites are the Math and Parisian motifs, but there's also one we made especially for New Year's Eve.

+
+ Screenshot demonstrating some of the new background patterns. +
+ +

There are new patterns with cats as well. And space. And cats in space. No time to explain, go check them all out.

+ + +

New Predefined Colors

+

Not in a creative mood? Not a problem – we've added a boatload of new predefined color schemes for Telegram's default themes. The theme of your dreams may be just a few taps away, try the new options under Classic, Night, Day, etc.

+
+ +
+ +

Send When Online

+

Some things are best served fresh, like sushi and today's hot memes. For messages that have to be delivered at the perfect moment, we've added the option to schedule messages to be sent when your recipient comes online.

+

Now you can slide your message in with the morning post – or time a funky duck sticker for the exact moment a meeting gets boring.

+
+ +
+ +

Note that this option is only available if you are allowed to see your recipient's online status. You can still sneak out of bed without anyone noticing.

+

Improved Venue Sharing

+

Location sharing has been updated to make finding venues easier. You can now tap a place directly on the map to select it, rather than scrolling through a list of all the power converter purveyors in Tosche Station.

+
+ +
+ + +

View Search Results as a List

+

The Search function allows you to easily jump between messages containing a keyword – or sent by a particular person, or even from a certain day. Tapping the bottom bar will now switch to list view in case you want to see all the results on one page.

+
+ +
+ +

On iOS, you can also select several messages without leaving Search Mode. (Before you ask, this feature was already available on Android.)

+
+ Screenshot showing several messages selected in a chat on iOS – without leaving the Search Mode. +
+ + +

Podcast and Audiobook Support

+

You've always been able to share files of up to 1,5 GB, but podcasts and audiobooks now get special treatment. Telegram apps will remember your last position when resuming playback of audio files longer than 20 minutes.

+

If you'd like to make podcasts get to the point a little faster, try the new 2x button (which you already know from voice messages). We've eliminated voice chipmunking in 96.8% of cases.

+
+ Screenshot showing the location of the 2x playback button for long audio files. +
+ +

On iOS, you can skip forward and back with high-precision scrubbing: just hold on the progress bar and slide your finger down, then left or right.

+

New On Android

+

Switch to Night Mode Faster

+

Telegram has shielded your eyes in dark places with Night Mode since 2017. The power of the sun and moon are now even easier to control, with the Night Mode Switch at the top of the menu. Tap the moon icon and watch the sun rise and fall at your whim.

+
+ +
+ +

Maps have also joined the dark side in Night Mode, so you don't accidentally burn yourself while browsing locations late in the evening. Ve do as the count vills. (•,..,•)

+
+ A shared location on a map in Night Mode on Telegram for Android. +
+ +

On iOS, dark maps turn on and off with the system dark mode. Speaking of which, we recently added the option to sync your Telegram theme with system dark mode on iOS 13.

+ + +

Sleek New Animations

+

We've peppered the interface with little ripple animations when you press on things to help you get more joy out of buttons. Snappy new animations await when jumping between messages in a chat, opening global search or pulling out the archive folder. To get a closer look at a user's profile picture, drag down on their profile page.

+
+ +
+ +

Select Parts of Messages

+

Following in the footsteps of the iOS app, Android now also lets you select a portion of the message text to copy or share, instead of only the full text. Sometimes you only want a slice, rather than the whole pie.

+
+ +
+ +

Multi-sharing from Other Apps

+

Sharing is caring, so we've made it easier than ever to share content from other apps with your friends. You can now tap and hold to select multiple recipients – and even add a comment in case your savage subtweet needs some context.

+
+ +
+ +

Mark Archive as Read

+

A cluttered chat list reflects a cluttered mind. Clear up those extra unread message counters in your archive by tapping and holding the archive folder and marking them all read. (Not to be confused with marking it red, that's a job for themes.)

+
+ Mark all messages as read in the Archive on Android. +
+ +

And Other Android Goodies

+

You can сhoose video quality in a more intuitive way when sending videos.

+
+ New button for selecting video quality when sending a video. +
+ +

Sending contacts now uses a simple, card-style interface that won't take up your whole screen (unless you pull up to expand it).

+
+ New contact sharing screen. +
+ +

When you're done listening to a voice message with your phone up to your ear, Telegram automatically records a reply - but now you can disable that by turning off Raise to Speak in your Chat Settings.

+

We found 31 other shiny bugs to fix and improvements to make on Android, just in time for your Telegram advent calendar. See if you can find them all.

+

New on iOS

+

Text Size, All the Way

+

You've been able to adjust the size of message text on Telegram from the beginning, but now you can scale the font size throughout the app. I'm not sure if Grandma reads this blog regularly, so you may have to tell her yourself.

+
+ Telegram for iOS with enlarged font. +
+ +

Choose Your Browser

+

External browsers are now supported for opening links – you can select your preferred app in Settings > Data and Storage > Other.

+
+ Browser settings screen. +
+ +

Share Sheet Settings

+

Your most popular Telegram chats were recently added to the iOS Share Sheet. In case you'd like to control what can (or can't 😉) appear there, you can use the new toggles under Settings > Data and Storage > Other > Share Sheet.

+
+ Share Sheet settings screen. +
+ +

Switch Accounts Faster

+

Superman has had a hard time finding phone booths lately, so we added a way to swiftly switch accounts right from your home screen on iOS 13. Simply hold down on the app icon any time you need to change costumes.

+
+ App menu on an iOS 13 home screen, featuring a 'Switch Account' button +
+ +

Remember that you can use Telegram with multiple accounts, switching between up to 3 phone numbers without logging out.

+

Storage Usage At a Glance

+

The Storage Usage page has been redesigned to more quickly find the settings you're looking for. It also shows your device's storage status, and how much space all those other pesky apps are using compared to Telegram. Bigger, after all, is not always better.

+

You did know that with Telegram there's no need to store every silly meme people ever sent you on your precious device, right?

+
+ Storage Usage settings screen. +
+ +

Cache-Clearing Shortcuts

+

Selecting multiple messages in a group or channel gives you the option to clear the chat's cache. Like we said, no need to store what you don't need – but also no need to delete actual messages. Just keep things in the cloud, like the cool kids.

+
+ Clear Cache button in a channel. +
+ +

Check out Settings > Data and Storage > Storage Usage for more options.

+

Member Lists: The Shorter Scrolls

+

In case you're looking to leave some large groups and start fresh in the new decade, long member lists will collapse, so you can get to the 'Leave Group' button without scrolling.

+

By the way, swiping on a group or channel from the chat list and selecting 'Delete' is still the shortest way out, but now there is more than one way to leave the New Year's party early.

+
+ Group members screen with a collapsed member list. +
+ +

And that's all for today. Happy New Year!

+

2020 is going to be fun. Enjoy winter while we get back to our little warm R&D bunker deep deep underground.

+

+ +

December 31, 2019,
The Telegram Team

+

+ +
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/video-1000.html b/data/telegram.org/blog/video-1000.html new file mode 100644 index 0000000000..849a17bd81 --- /dev/null +++ b/data/telegram.org/blog/video-1000.html @@ -0,0 +1,354 @@ + + + + + Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More

+ +
+ +
+
+ +
+ Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More +
+ +

This update takes video to the next level. Group video calls now have up to 1000 viewers, video messages record in higher quality and can be expanded, regular videos may be watched at 0.5 or 2x speed. We've also added screen sharing with sound to all video calls, including 1-on-1 calls — and much more.

+

Group Video Calls 2.0

+

Group video calls allow up to 30 users broadcast video from both their camera and screen – and now 1000 people can watch anything from online lectures to live rap battles.

+

We will keep increasing this limit until all humans on Earth can join one group call and watch us yodel in celebration (coming soon).

+
+ +
+ +
+

To start a Group Video Call, create a Voice Chat from the info page (in the ⋮ menu on Android) of any group where you are an admin – then turn your video on.

+
+

Video Messages 2.0

+

Video messages are a quick way to check in or share your surroundings without adding another video to your gallery. They now have higher resolution and you can tap on a video message to expand it and take in all those extra pixels.

+
+ +
+ +

Tapping on an expanded video message pauses it and gives you the opportunity to fast forward or rewind the message in case you missed a word.

+
+

To record a video message, tap the microphone icon in the message bar to switch from voice message recording to video. Press and hold to record, then tap the camera icon to switch back.

+
+

Audio from your device will keep playing as you record so you can now sing along to your favorite songs or reply without pausing your podcast. Additionally, recording with your rear camera lets you pinch to zoom in and capture things at a distance or add a dramatic effect (eerie music not included).

+

Video Playback Speed

+

To power through lecture videos and replay kung fu moves in slow motion, the media player now supports 0.5x, 1.5x and 2x playback speeds. Our Android developer is a fan of hummingbirds, so his app also supports 0.2x speed.

+
+ +
+ +
+

To change your video playback speed, tap ⋮ on Android or ⋯ on iOS when watching a video in fullscreen.

+
+

On Android, you can also press and hold the 2X button when playing voice or video messages to switch between 0.5x, 1x, 1.5x and 2x playback speed.

+

Timestamp Links

+

Since 2019, putting a timestamp like 0:30 in the captions or replies to videos and YouTube links lets users jump to that exact second – and you can now press and hold on a timestamp in a message to copy the link and share the moment in another chat.

+

Screen Sharing With Sound

+

Screen sharing has been added to 1-on-1 calls as well, and now includes the sound from your device when broadcasting in any video call. So make sure you quit Super Mario before its your turn to present — or don't, and use the game for sound effects.

+
+ +
+ +

When switching on video during any call, you can swipe to choose a camera or share your screen instead — and use the video preview to make sure that everything is perfect before going live.

+ + +
+

To share your screen during a video call, tap the camera button and select your screen as the video source.

+
+

Auto-Delete After 1 Month

+

Messages in any chat can be set to erase themselves after 1 day or 1 week – and now 1 month, in case you need your chats to stick around for a full lunar cycle before disappearing.

+
+ Auto-Delete After 1 Month +
+ + + +
+

To enable the timer on Android, tap ⋮ > Clear History then choose a duration. On iOS, press and hold a message, tap Select > Clear Chat (top-left) > Enable Auto-Delete.

+
+

Precision Drawing

+

The media editor allows you to illustrate and decorate your photos and videos with drawings, text and stickers. To more easily add fine details (or that perfect mustache and pointy ears), the width of your brush now decreases as you zoom in – giving you the precision of a professional.

+
+ +
+ +
+

To change the width of your brush at any time, drag the dot up from the color selector.

+
+

The Telegram Desktop app now has its own photo editor to crop, rotate or flip images – and add drawings or stickers. Unique to desktop, your edited versions can be sent as uncompressed files by unchecking the Compress Images box.

+

Passcode Animations

+

New animations make the passcode lock interfaces even snappier than before. If you're using an animated background, it will also appear on the passcode lock screen. The disco never stops.

+
+ +
+ +

Password Recovery and Reminders

+

We've added a new prompt in Settings to help you practice entering your Two-Step Verification password.

+
+ Practice Your 2-Step Verification Password +
+ +

If you forgot your password, there is a new password reset option that works even if you don’t have a recovery email — as long as you're still logged into your account. The process will take 7 days and can be cancelled from any of your devices.

+

Message Sending Animations on Android

+

Like emoji and stickers, text messages have new lightweight animations – when you hit Send, your text smoothly transforms into the message bubble as it flies into the chat. iOS users received these energy-efficient animations in the previous update.

+
+ +
+ +

New In-App Camera on iOS

+

The in-app camera now utilizes all zoom levels on your device – including 0.5x and 2x if available. You can also press and hold to open a zoom wheel that lets you zoom in and out with granular control.

+
+ +
+ +
+

To use the in-app camera, tap the 📎 icon in the message bar and then tap the camera feed in the attachment menu.

+
+

More for iOS

+

Choose multiple recipients for forwarded messages by tapping 'Select' in the forwarding menu to share your best memes with all your best friends.

+
+ Forwarding to multiple recipients +
+ +

Scrolling with two fingers in the chat list quickly selects several chats for bulk actions like archive, delete or mark all as read.

+ + + + +

Profile pictures now follow the messages as you scroll in group chats so you always know who sent each one, even in long chains of one. word. after. another.

+
+ +
+ +

New Animated Emoji

+

No Telegram update is complete without new animated emoji. As always, simply send a message with a single emoji to get one of these in a chat:

+
+ +
+ + +

And that's all for today's update – we're working on the next one at 2X speed.

+

+ +

July 30, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/video-calls.html b/data/telegram.org/blog/video-calls.html new file mode 100644 index 0000000000..95c93e6e3f --- /dev/null +++ b/data/telegram.org/blog/video-calls.html @@ -0,0 +1,234 @@ + + + + + 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-messages-and-telescope.html b/data/telegram.org/blog/video-messages-and-telescope.html new file mode 100644 index 0000000000..075c2b6960 --- /dev/null +++ b/data/telegram.org/blog/video-messages-and-telescope.html @@ -0,0 +1,247 @@ + + + + + Video Messages and Telescope + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Video Messages and Telescope

+ +
+ +
+ +
+ +
+ +

We know you love the speed and simplicity of voice messages on Telegram. Starting today, you can also send video messages – just as swiftly:

+
+
+ +
+
+
+ +

To send a video message, go to any chat on Telegram and tap the mic icon to switch to camera mode. Now all you need to do is tap and hold the camera icon and record a video message. When you’re done, just release the recording button to dispatch your message — and it will arrive in the blink of an eye.

+

Video messages are so fast because Telegram compresses them and sends them even as you record them. By the way, if holding the button seems like too much work, you can lock the camera in recording mode by swiping up. This also works with voice messages now (here's one for you, cab drivers).

+

Video messages are automatically downloaded and autoplayed by default (you can change this in Settings if you’re on a data diet though) and generally feel and act like voice messages – on visual steroids.

+
+ +

Picture in Picture

+ +

While watching a video message, you can freely browse your other chats – the video will pop up in a corner and continue playing. You can move it around the screen and pause it from anywhere in Telegram. Cool, eh? Well, there's more:

+

Meet Telescope

+

Lots of popular folks address their fans via public channels on Telegram. Video messages will make their connection to fans more direct and intimate than ever. But we want to kick this up another notch.

+

Today we are launching Telescope, a dedicated video hosting platform for those who use videos to communicate with their audiences (here's one for you, blogger people!)

+

With Telescope, public video messages can go viral beyond the Telegram ecosystem. Telescope hosts autoplayed round videos of up to 1 minute in duration – the same format we use for Telegram video messages. And yes, you heard that right, you don't need a Telegram account to view them.

+

Every public channel on Telegram now has a telesco.pe URL, such as telesco.pe/channel_name, where all of its video messages are available to the world wide web and the wide, wide world.

+
+ +

A Telescope Channel

+ +

Whenever you post a video message to a public channel, it will also be uploaded to Telesco.pe and have a public URL there.

+
+ +

Share Telescope Videos

+ +

With Telescope, even those users who don’t have Telegram installed will be able to enjoy your public video messages and share them on Twitter or Facebook. As a result, this content will generate more views. And who would refuse more views these days, hmm?

+
+

This was just 1/3 of Telegram 4.0. Keep reading to learn more about Payments for Bots and the new Instant View Platform.

+
+

+ +

May 18, 2017,
The Telegram Team

+

+ +

P.S. Our founder has this weird urge to keep launching platforms that start with “Tele-”. Be sure to check out Telegraph, the publishing platform we launched last year.

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/video-stickers-better-reactions.html b/data/telegram.org/blog/video-stickers-better-reactions.html new file mode 100644 index 0000000000..fbcafb07e7 --- /dev/null +++ b/data/telegram.org/blog/video-stickers-better-reactions.html @@ -0,0 +1,273 @@ + + + + + Video Stickers, Better Reactions and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Video Stickers, Better Reactions and More

+ +
+
+
+ +
+ Video Stickers, Better Reactions and More +
+ +

This update brings easy-to-make video stickers, better reactions with compact animations and extra emoji, a button to review unseen reactions, improved navigation between chats and more.

+

Video Stickers

+

Telegram's animated stickers have unmatched quality and efficiency – needing less than 30 KB of data per sticker. However, creating such stickers requires experience and specialized software such as Adobe Illustrator.

+

Today, we're adding support for stickers converted from regular videos, so that anyone can easily create detailed animated stickers using any video editing program.

+
+ +
+ +

Like always, you can publish your packs with the @Stickers bot – or add some of the new sets made by others. Whatever you do, never stare back at the tomato.

+
+

Check out the Video Sticker Manual for more details.

+

Developers can use the Sticker Import API to build powerful apps for creating and importing stickers to Telegram.

+
+

Better Reactions

+

Reactions now have more compact animations. To send a larger effect, press and hold on a reaction in the menu.

+

Like interactive emoji, reactions are now synchronized, so your recipients will see the animations in real time.

+
+ +
+ +

Reactions are used not only to express emotion, but also to answer questions and show approval – which is why they now have read status. Like for replies or @-mentions, a new ♡ button appears when your messages have unseen reactions.

+

New Reactions and Interactive Emoji

+

This update also adds 5 new reactions 🥰🤯🤔🤬👏 to help you discuss anything from Christopher Nolan's movies to global economic news.

+

These reactions can also be sent as interactive emoji. Send a single 🥰🤯🤔🤬 or 👏 to any private chat, then tap on the animated emoji to unleash a synchronized fullscreen effect.

+
+ +
+ +

Navigating Recent Chats

+

When jumping through unread channels or moving between chats, press and hold the 'Back' button to return to a specific chat. Opening chats from forwarded messages, links, usernames, profiles, etc. adds them to the list.

+
+ +
+ +

Bug Busting and More

+

Our developers spent two weeks in January focusing completely on fixing known issues in Telegram apps. Among other things, they improved call quality, added support for translation to Instant View pages (and bios on iOS), added the option to send silent messages from the sharing menu – and dozens of other improvements.

+

On iOS, you'll also notice new animations when tapping icons in the tab bar.

+
+ +
+ +

And that's it for today. Let's leave some features for February.

+

January 31, 2022
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/voice-2-secret-3.html b/data/telegram.org/blog/voice-2-secret-3.html new file mode 100644 index 0000000000..ae55d6cb2b --- /dev/null +++ b/data/telegram.org/blog/voice-2-secret-3.html @@ -0,0 +1,245 @@ + + + + + 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 new file mode 100644 index 0000000000..d2695f795c --- /dev/null +++ b/data/telegram.org/blog/voice-chats-on-steroids.html @@ -0,0 +1,275 @@ + + + + + Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

+ +
+
+
+ +
+ Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools +
+ +

Voice Chats first appeared in December, adding a new dimension of live talk to Telegram groups. Starting today, they become available in channels too – and there are no more limits on the number of participants.

+

This update also brings recordable voice chats, rich lists of participants, raise hand mechanics, invite links for speakers and listeners, voice chat titles, and a way for public figures to join voice chats as their channels.

+

Limitless Voice Chats

+

Admins of channels and public groups can now host voice chats for millions of live listeners. No matter how popular your talk gets, new people will be able to tune in. It's like public radio reinvented for the 21st century.

+
+ +
+ +
+

To start a Voice Chat, open the profile of any group or channel where you're an admin, tap (⋮) or (⋯) and select Start Voice Chat.

+
+

Recorded Chats

+

While some conversations are meant to be temporary, others are worth preserving and passing on. Admins can now record audio from voice chats to save talks and publish them for followers who missed the live event.

+
+ +
+ +

Once you finish recording, the audio file becomes instantly available in your Saved Messages. To avoid surprises, chats that are being recorded are marked with a red light next to their title.

+

Raise Hand

+

In chats where participants are muted, listeners can tap to raise their hand and alert the admins that they want to speak. Just like calling in to a talk show – but with addictive animations.

+
+ +
+ +

Your bio text is now visible in the list of participants, which you can use to detail your expertise, interests, or just a little bit about yourself. This info might help admins find a good slot for your questions or comments.

+

Speaker and Listener Links

+

Admins of public groups and channels can now create invite links that open the voice chat right away. Separate links can be made for speakers and listeners. This way you won't need to unmute important guests when they join – and they can use a different link to promote the upcoming chat to their communities.

+
+ +
+ +

Voice chats also have optional titles which help users see the topic of conversation before they join.

+

Join As…

+

When entering a voice chat in a channel, users have the option to join with their personal account or appear as one of their channels. Celebrities and public figures can use this to avoid drawing too much attention to their personal accounts.

+
+ Joining a voice chat as a channel +
+ + +
+

For example, the Presidents of Brazil and Turkey could meet for a talk in Pavel Durov's Channel and answer questions from users without the risk of having their chat lists flooded with fan mail.

+
+

And More

+

If you choose the wrong chat by mistake when forwarding messages, press the X button before sending them – to either cancel forwarding or choose a different chat.

+
+ Choose a different chat or cancel forwarding +
+ +

You can also resume playback from where you left off when listening to long voice messages. This was previously available for long videos and long audio tracks, and we thought we'd covered everything – but then our grandma signed up.

+

Last but not least, Android users can choose which action is assigned to swiping left in the chat list: archiving chats, pinning, muting, deleting or marking them as read. (On iOS, all these swipe actions are always available, depending on which way you swipe.)

+
+ +
+ +

And that's it for today, stay tuned for the next update!

+

+ +

March 18, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/voice-chats.html b/data/telegram.org/blog/voice-chats.html new file mode 100644 index 0000000000..a36d1a44d7 --- /dev/null +++ b/data/telegram.org/blog/voice-chats.html @@ -0,0 +1,311 @@ + + + + + Voice Chats Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Voice Chats Done Right

+ +
+
+
+ +
+ Voice Chats Done Right +
+ +

Since 2013, we've been expanding the definition of Group Chats, adding features like replies, mentions, polls, admin tools, statistics – and allowing hundreds of thousands of members per group. Many of these features were later incorporated into other apps and redefined how people communicate.

+

Today, Telegram groups get an entire new dimension with Voice Chats – persistent conference calls that members can join and leave as they please. Our 12th update in 2020 brings them to you just in time for remote Christmas carols.

+
+

UPD March 2021: Don't miss Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

+
+

Voice Chats

+

Any Telegram group can now become a voice chat room that is always on. Voice Chats run in parallel to existing text and media-based communication, adding a live layer of ephemeral talk to the group. They can be used as virtual office spaces for teams or informal lounges for any community.

+

While Voice Chats are not group calls, they can achieve similar goals – at the same time offering flexibility instead of old school scheduling. In larger groups, they also provide serendipitous opportunities for talking to people.

+
+ +
+ +

Groups with active voice chats have a special bar at the top that shows who is talking at the moment (and even how loud they are). This can help you pick the right moment to join – like noticing your friends going over to the cooler.

+
+ +
+ +

After joining a voice chat, you are free to move around the app, browse conversations and send messages. You stay connected to the chat and the microphone controls remain on screen so that you can quickly mute and unmute yourself at any time.

+

If you're on Android, you can enjoy the full Voice Chat experience with a system-wide floating widget that shows your mic controls and who is currently talking, even when Telegram is in the background. Santa is on Android too – and he needs his sleigh navigator open at all times.

+
+ +
+ +

You can chat with whomever is online or invite more people via the handy menu. Voice Chats can accommodate a few thousand participants, which means they'll work for everything from consulting family members while out shopping to a massive live event.

+

Last but not least, Voice Chats show spectacular animations. To get these right, our designer had to sell his soul to the devil – and we think it was totally worth it.

+
+

To create a Voice Chat and find your own unique way of using them, open the profile of any group where you're an admin, tap (⋯) or (⋮) and select Start Voice Chat.

+
+

Like Telegram groups before them, we hope that Voice Chats will change the way people collaborate and keep in touch. In the coming weeks, we'll be refining them further, listening to your feedback, improving noise suppression, and adding more features like video and screen sharing.

+

Push-to-Talk Shortcuts

+

On Telegram Desktop and in the native macOS app, you can choose a push-to-talk key for Voice Chats, to control your mic even when Telegram is not focused. At long last, we've found a use for your Caps Lock key.

+
+ +
+ +

Sticker Outlines

+

Animated stickers on Telegram are optimized for efficiency and deliver smooth 180 frame animations with infinite resolution in less than 50 KB.

+

With today's update, stickers will load even faster than before – and show a shimmering outline of what you're about to see. Be careful not to blink though, or you'll miss it.

+
+ +
+ +

SD Card Storage on Android

+

Users on Android devices can now move their Telegram app data from internal storage to their SD card, allowing those with minimal storage to save more media and files and maximize their Telegram experience.

+
+ Storage Usage settings +
+ +
+

Remember that you can always keep Telegram's storage footprint on your device incredibly small. See Settings > Data and Storage > Storage Usage.

+
+

New Animations on Android

+

We've added slick new animations throughout the Android app – when tapping the New Message button, opening profiles, managing chat folders and anywhere you see message counters.

+
+ +
+ +

Announce Messages on iOS

+

If you're still on iOS, you can have Siri read incoming messages aloud in your headphones. Open iOS Settings > Notifications > Announce Messages and set Telegram to ON to stay up to date on your chats even while washing the dishes.

+

Editing Improvements

+

Android users can now quickly edit a photo which they've already sent to add effects, drawings or stickers with our powerful media editor. iOS users can tap the pen button to quickly edit and send back a photo they have received.

+

Each of these features was previously available only on one of the platforms, but now both iOS and Android offer equal opportunities for drawing moustaches on selfies.

+
+ Editing Improvements on iOS and Android +
+ +

When editing a message or caption, as you approach the maximum message length, a counter will appear showing how many remaining characters you have lef

+

More Animated Emoji

+

No update is complete without even more animated emoji. As usual, simply send a message with a single emoji to get one of these 👇 in a chat.

+
+ +
+ +

There's a story in there somewhere about a cyber cowboy solving a murder mystery.

+

Feature Suggestion Platform

+

Many Telegram features started out as user suggestions. To help identify potential new features and locate bugs within the app, we're launching a public Bug and Suggestion Platform.

+ + +

We'll be rolling out the ability to suggest new features and report bugs gradually to make sure each submission gets the attention it deserves. All Telegram users are already welcome to view existing entries and vote on them.

+

And that's all for today, we'll see you in 2021 or once we're done building the next big thing – whichever comes first.

+

+ +

December 23, 2020
The Telegram Team

+

+ +
+

P.S. The end of the year is normally a time to look back at the past 12 months. Instead, our founder Pavel Durov has just announced his strategy for making Telegram sustainable, to continue providing you with great features for decades to come.

+
+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/winter-contest-ends.html b/data/telegram.org/blog/winter-contest-ends.html new file mode 100644 index 0000000000..1b651c3bac --- /dev/null +++ b/data/telegram.org/blog/winter-contest-ends.html @@ -0,0 +1,224 @@ + + + + + Winter Contest Ends + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Winter Contest Ends

+ +
+ +
+ +

The contest to decrypt intercepted traffic of Telegram produced no winners as of March, 1. As promised, today we are publishing the encryption keys necessary to decrypt the traffic.

+
SECRET CHAT:
+2e 20 9f 9d 99 c9 fc 8a 3d dc d5 6d 21 26 46 c9 d8 1a 26 f8 ec f7 f2 7e c9 28 65 95 52 dc 1c 21 bb 95 60 b1 d8 5f 94 5f 43 8d 7e 8e 96 fa e6 89 91 a9 90 39 8b df ef 50 22 06 f8 52 80 e6 50 20 62 71 c4 b2 f5 f8 88 4d 83 ae 66 ec fe cd ec 92 26 69 72 5e 85 f9 ea 58 b0 d6 9f 5b 1e b7 68 15 76 5b 12 88 3d 17 f6 62 49 8b 1f 9d 7a 11 94 67 8d d1 ee d6 55 50 d4 51 c0 5e a5 9a 1a eb 8a 8c 7c 44 1b db 96 5a fd cd 85 47 5b f0 8a 1e b8 d6 74 a4 c7 e7 af 19 3f a6 0a ff e5 3b 9f c4 fc ea 59 af f6 72 60 16 6f 40 af 58 95 98 06 0c 22 00 d7 3d be 96 19 56 54 06 74 d2 6b 38 8d c2 a0 97 62 6d e4 10 99 b9 cf d5 0f 56 9d d3 bb 49 86 d5 15 23 86 03 c3 52 67 82 77 5e 53 e9 ba e8 63 58 ed 55 b0 ef ec 69 65 a0 e5 1d e4 b6 6e 5a 3d 5f 9b 9a 20 67 f5 d5 c4 d7 60 14 c6 56 2d 12 1b 0a
+
+DC 1:
+5e a6 0d a2 9c 90 8e f4 36 d5 48 fe 76 a3 11 f6 66 13 4e 94 bb 11 32 d6 cf fd b0 2f 7b 77 bb 01 d7 42 a4 22 d3 04 e7 d2 fc 5b 32 48 d6 71 eb 18 51 19 99 76 49 46 1a 43 d8 cf cd 8a e2 fe 42 2c 36 d7 05 8b 0c 5e 00 8a 5a bc 35 4f ec 75 b4 10 e1 84 bb cb af ec e3 d6 fd 59 fd 01 83 ef 8b dd 13 50 24 5b 80 09 75 7e c3 c3 08 ba 59 f4 ec c0 87 71 ba 9f 45 8c 15 df 2a cd a5 bc 81 a9 20 fe 42 e2 65 78 02 77 80 11 0e e4 67 f3 40 cf 72 be fc c2 8d 0b ad d9 9e 6e 1a c3 03 71 39 be b9 dd df 7c 63 a6 27 45 ee 8e 00 5e 12 51 51 6c 6a 10 a6 73 3a 10 5d d8 f3 b6 c5 70 fe 91 c2 64 4b d0 74 2d 47 e7 4e 00 cf d5 d3 65 15 2b 48 9c 75 eb a8 96 aa ce 09 49 9b 5e ea 76 06 19 f3 b3 e7 7b af df 5d 68 5e 80 10 48 ec 00 35 90 d3 e5 96 c6 59 a7 44 d8 20 a8 a2 b6 93 64 4f 98 44 23 8e fd
+
+DC 2:
+63 ab 0d b7 98 e1 78 ef 5f 05 9c e4 84 3b 53 b3 4f 6e d1 d3 8a 6d 59 19 32 26 73 60 c2 e2 fe ee d3 2d 74 35 18 08 ba 04 87 cf 7f d9 87 4b 64 d5 80 06 05 f5 01 56 6d c2 66 7e 2d ef f6 a3 82 3d 31 0e ed 6b 46 4c 11 d5 ec 0f 7b be 64 79 26 87 a9 d3 34 27 d8 8b aa b5 36 8b 95 2f a7 c7 2a a6 bf a9 44 51 c5 c8 06 04 78 d2 64 87 e8 13 f3 f0 9b c9 8c bc 29 01 55 a2 80 e1 e8 4e 74 53 7e 05 22 1b 51 3d 1a c5 61 b3 04 98 c2 2f 71 e3 76 2e 31 bd d8 55 15 4b 3e 34 ed 84 b2 56 d0 bd c6 9a 1a 2a 4b 2f fc 68 8e c4 e3 81 23 6f 07 3f 3a 6b 56 f6 ee 31 e6 aa 0d 49 36 6a 51 79 25 bf b6 40 64 8c e2 14 c8 70 37 cb 70 ad a1 83 ed 1f b9 78 b9 93 0c 7c 0c ed 6d c6 aa c2 d0 da 51 ce ae cf 99 8f 65 eb 5a 42 e6 ff 4a 51 a9 97 da 6e ac e5 63 c1 05 a9 fe d0 da da 43 e3 50 14 fc b1 46 ea
+
+DC 3:
+16 0c be 58 e1 74 74 f5 f9 8f f8 82 71 ed 57 84 20 49 bd da 17 0e 00 a8 a4 24 71 79 86 1f ef 3e 41 70 31 de c9 c2 19 23 37 fd ec 2f fa 9e 89 29 4f a2 af 69 cf 24 3a 6e 44 5d 89 d2 8b 50 45 26 3c ff e3 d4 4d 7d b4 88 54 8c 87 09 c5 ac 09 5c e6 62 43 73 b5 3e 96 ea f3 62 76 58 1b fd 8a 36 45 65 4a fc 7b ee 7b 13 06 e5 2f 9d 8f cb b9 a7 6f 76 00 f4 9a ab 50 fb 91 e0 2b ce 28 db 95 02 a0 62 33 bb e7 41 13 7b 2c 7e ba 7c d5 87 12 33 de 44 8d 4b 76 af 59 cc 80 42 02 69 56 90 8a 5d 95 0b 3e 8b ef 65 17 fc 79 62 b4 69 1b 21 aa 89 5b 22 f6 33 67 80 d0 22 f7 76 f2 6c 4b af 69 07 0f 2c 3a af 67 6b 74 c0 7f 8c 83 85 85 8e 47 b7 55 42 c1 3d 70 33 9d 87 60 7c f6 8b 99 96 1d af 82 b8 d2 37 c7 a3 fc ac 25 fe 77 f0 29 4d 82 a4 15 89 cb c2 27 ae 4f 16 d6 b8 4c cb de 2a 59 d7
+
+DC 4:
+b4 aa dc bc 8e e5 6a f4 9f 7b 65 de cd 1c 28 3d f1 58 f6 03 e1 34 9d 63 54 b0 15 a7 b8 a6 45 4e de dd cd e4 1a 54 d7 9b fe 46 05 c7 62 19 d9 7a c0 00 6b e6 72 83 3d 15 00 99 d9 9b 97 c0 4a a8 85 e7 85 3c 3f a4 2f 6a 57 0b 3c b0 2a 97 65 6f bf 4e 0d 93 f7 55 3b 3a 39 a1 1a 0f db 9d 7a df 5b c6 9b 45 9a ea e4 27 92 8c c3 d2 75 53 66 e4 1c 29 f1 14 fc fd e8 c0 c8 12 47 ee 5a 92 f1 bf 1f 6f 8e 95 a5 90 81 37 d6 5d bd 5c 4c 41 61 29 6e 4f 7e 83 e1 b9 ef 00 00 de 25 33 f4 df 1a 94 f0 e7 1c fd 35 c0 75 65 88 ef c5 aa b5 c9 7d 0e e4 6d b7 9f 10 ca 4b f0 c9 c7 2d 30 20 e9 e1 b8 03 de a2 60 4e 3f 59 dc 36 a2 50 f8 52 5e 32 c8 c1 84 87 84 d6 54 42 dd ab b4 1b d6 fe e4 29 d3 70 4e 3e 48 ba 86 80 39 b7 94 3c 31 18 f8 bd 7b d8 89 6b 32 77 5c 89 4a a1 ca 18 ba 1e 6a 87 6a
+
+DC 5:
+4c 76 1f 87 08 53 54 cb 12 fd 01 bd bd e6 42 d2 6b 47 4b d8 0b 6a eb 9f 24 8b ee 77 1f 8b a5 3f f5 f1 c7 80 05 80 2c 20 29 7c 3c 14 59 2b 5e 7f 69 58 3b 7e 07 37 25 67 3d 18 ac f2 28 43 63 8f a5 41 c1 ba 53 dd eb 3d 36 0d 7b d3 14 f7 f9 83 aa 0c 81 20 89 e0 c7 d7 e9 ef 11 aa 43 ca 54 2a 9f 69 0f 1d 99 ef f6 55 14 71 6d a3 1e c2 75 fb 1c 88 f7 c0 21 64 5d 34 db 3f a4 e7 a9 f0 af 9f 9d 14 a4 3a 49 7c 50 e6 45 24 3a cb a4 a6 2a 35 dd 6c 9c ce 87 24 d1 ff 13 19 15 43 89 a4 8c 39 66 a2 22 df 4e 94 76 e1 89 b5 03 7a 2b 34 e7 39 09 f9 22 5d cb 36 4e ce 37 e7 cf 7d ab b5 8b db 81 c6 c8 f4 c7 7c 3a 22 59 fc e6 32 19 aa 46 d2 95 96 61 61 e6 cc 57 f0 0e 87 5c 7d 5b 87 e7 64 28 c6 03 38 3c 0b a6 5e 4a 21 a3 67 af e5 b3 88 cc 9d 03 98 33 ac c6 87 b4 b6 82 42 c4 41 33 39
+


+ +

We would like to use this opportunity to thank the users ABC, @DefuseSec, @hackappcom, @Morj and x7mz who helped us further improve security of the client apps and expand guidelines for third-party developers.

+

Since we have no winner in the current challenge, we are going to launch a new competition, with an easier task, but a larger prize. The new competition will allow participants not only to intercept traffic, but to manipulate it as well. We are now building the tools that will enable the contestants to perform all kinds of active attacks. Once the platform is ready later this month, we will announce the new contest on Twitter. Please follow us at @telegram!

+

March 2, 2014
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/evolution.html b/data/telegram.org/evolution.html new file mode 100644 index 0000000000..d79af7b532 --- /dev/null +++ b/data/telegram.org/evolution.html @@ -0,0 +1,1801 @@ + + + + + The Evolution of Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+
+

The Evolution of Telegram

+ +
+ +
+ +
+ +
+
+ Evolution of Messaging +
+ +

On this page, we've compiled a Brief History of Telegram. It ended up rather on the 'humongous' side of 'brief' – but that's what you get for never, ever, ever updating the app with a description like 'contains bug fixes and minor improvements'.

+

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. This page gets updated each time a new post hits the Telegram blog.

+ + + + +

2021

+
+

December 2021, Second Update

+

Reactions, Spoilers, Translation and QR Codes

+

Telegram’s unique interactive emoji became available as reactions – giving users the ability to directly share their feelings on messages.

+

Spoiler formatting was introduced, allowing anyone to hide parts of a message under a special animation.

+

Message translation was brought to Settings > Language, adding a dedicated button to translate any message directly in the app.

+

Customizable QR codes were included for all public usernames – including users, groups, channels and bots – to quickly share a chat in any app.

+
+ Reactions, Spoilers, Translation and QR Codes +
+ +

On Telegram since December 30, 2021:

+ +
+

December 2021, First Update

+

Protected Content, Delete by Date, Device Management and More

+

A new setting was added to Groups and Channels that allows creators to keep their content exclusive by restricting message forwarding – while also preventing screenshots and limiting the ability to save media.

+

The option to delete all messages from a day or range of dates was added to 1-on-1 chats, giving users a way to clear specific sections of chat history.

+

The Devices menu in Settings was fully redesigned, including a new auto-logout timer for inactive sessions and the ability to toggle whether a specific device can accept incoming calls or Secret Chats.

+

In Public Groups and Channel Comments, users were given the choice to send messages anonymously – appearing as one of their public channels instead of their personal account.

+
+ Protected Content, Delete by Date, Device Management and More +
+ +

On Telegram since December 7, 2021:

+ +

Android-Specific:
- Global Chat Themes (on iOS since November, 2021)

+

iOS-Specific:
- Text Recognition for iOS 13+
- Format Text in Media Captions (already on Android)

+
+

November 2021

+

Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More

+

Accelerated scrolling and pinch to zoom for media thumbnails were added to Shared Media to find past photos, videos, files (and more) even faster. Tapping the date bar opens a calendar view, with media previews for each date.

+

Join requests let group and channel admins confirm new members before they are allowed join. This creates new options for communities – like a special superfans chat or super-secret channel.

+
+ Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More +
+ +

On Telegram since November 3, 2021:

+ +

iOS-Specific:
- Global Chat Themes
(added to Android in December 2021)
- Transit Times for Shared Locations
- Instant Media Captions (added to Android in December 2021)

+
+

September 2021

+

Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording

+

It became possible to set different themes for individual private chats – for both participants. The release included 8 new themes, each with their own day and night versions, gradient message bubbles, animated backgrounds, and unique patterns.

+

Nonverbal communication got a boost with interactive emoji: tapping on animated versions of 🎆 🎉 🎈 👍 💩 or ❤️ launches fullscreen effects that appear simultaneously for both chat partners. Vibrations are also synched, so you can almost touch someone's hand – even if you're far apart.

+

A new Seen By field was added to outgoing messages in smaller Group Chats, allowing you to see which members have read it. To protect privacy, these read receipts are stored only for 7 days.

+

The ability to record video came to Live Streams and Video Chats, so communities can save and share anything from online lectures to rock concerts. You can choose to record the video file in portrait or landscape orientation, and the file is instantly uploaded to your Saved Messages once you stop recording.

+
+ Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More +
+ +

On Telegram since September 19, 2021:

+ +
+

August 2021

+

Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More

+

Live video with unlimited viewers became available for both groups and channels. Voice chats were, consequently, renamed to Video Chats (in groups) and Live Streams (in channels).

+

Forwarding became even more flexible with new options: a preview window that shows how messages will appear after they are forwarded and lets you hide sender names from messages or remove captions from media.

+

Channels became easier to navigate. Swiping up at the bottom of the channel brings you to the next unread channel. Catching up with the news is now possible without going back to the chat list.

+
+ Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More +
+ +

On Telegram since August 31, 2021:

+ +
+

July 2021

+

Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More

+

Group Video Calls could now have up to 1000 viewers (previously 30), in addition to unlimited audio-only listeners.

+

Video Messages got a brand new look – recording in higher resolution with options to expand the message and fast-**forward** or rewind while watching. Additionally, audio from your device would continue playing while you recorded, and you could zoom in when recording with the rear camera.

+

Screen Sharing was added to 1-on-1 video calls (previously existed in groups), and included sound from the users device when broadcasting in both individual and group video calls.

+
+ Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More +
+ +

On Telegram since July 30, 2021:

+ +

Desktop-specific:

+ +

iOS-specific:

+ +
+

June 2021, Second update

+

Animated Backgrounds

+

Animated Chat Backgrounds were added to all default themes – moving beautifully with each message. Users could pick from dozens of presets or create their own custom backgrounds with 3 or 4 colors in the theme editor.

+

New sending animations were given to stickers and emoji, making them jump from the keyboard to the chat.

+

A menu button was created for chats with bots, displaying all its commands as well as placeholders to give users an example of what to send. Bot developers also got the ability to display flexible lists of commands that change based on a user’s language, chat type, admin status and more.

+

We released an API to help developers build tools that let users import stickers from other apps, or easily make stickers from their own content.

+
+ Animated Backgrounds +
+ +

On Telegram since June 25, 2021:

+ +

iOS-specific:

+ +
+

June 2021, First update

+

Group Video Calls

+

Group Video Calls came to Telegram, adding video to (now awkwardly named) voice chats in groups. Users could turn on their camera or share their screen from any device – including tablets and desktop.

+

Tablets and Desktops got custom display options – including an expanding side panel for split-screen mode. Desktop also offered selective screensharing, letting users choose a specific program to broadcast.

+

Noise supression was implemented in voice chats, eliminating background noise and boosting audio quality on all devices.

+
+ Group Video Calls +
+ +

On Telegram since June 25, 2021

+ +

Desktop-specific:

+ +
+

April 2021

+

Payments 2.0, Scheduled Voice Chats, New Web Versions

+

Payments were first supported in chats with Telegram bots in 2017. This time, merchants received the ability to accept credit cards in any Telegram chat using one of 8 integrated payment providers. Telegram doesn't store credit card info and charges no commission.

+

Voice Chats were further improved with scheduling, showing a countdown timer and allowing users to get a notification when the chat starts.

+

Two new web versions were launched, adding full support for features like animated stickers, chat folders and dark mode. Both work well in desktop and mobile browsers.

+
+ Payments 2.0, Scheduled Voice Chats, New Web Versions +
+ +

On Telegram since April 26, 2021:

+ +
+

March 2021

+

Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

+

Voice Chats first appeared in Telegram groups in December 2020. Three months later they became available in channels, with support for millions of live listeners.

+

Admins got the option to record voice chats and create instant podcasts, as well as choose titles for their voice chats and add users via specific Speaker and Listener links. Muted listeners could raise their hand to let admins know they wanted a turn to speak.

+

Public figures, celebrities and other users who prefer to keep their personal accounts hidden got the ability to join voice chats as one of their channels.

+
+ Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools +
+ +

On Telegram since March 19, 2021:

+ +
+

February 2021

+

Auto-Delete, Widgets and Expiring Invite Links

+

Telegram has had self-destructing messages since 2013 in Secret Chats, but this update added an auto-delete timer for any chat to erase messages either 24 hours or 7 days after sending.

+

Two customizable home screen widget styles became available for both Android and iOS, giving users the option to show previews of recent messages on their home screen, or shortcuts to chats.

+

Invite links for groups and channels were upgraded, allowing for additional links with a limited duration or number of uses that can also be converted into QR codes.

+

Broadcast Groups were introduced, allowing large communities to have unlimited members. Only admins can send messages in Broadcast Groups, but everyone can still read along and join voice chats.

+
+ Auto-Delete, Widgets and Expiring Invite Links +
+ +

On Telegram since February 23, 2021

+ +
+

January 2021

+

Moving Chat History from Other Apps

+

Over 100 million new users joined Telegram within one month, bringing their friends and families with them. After January's update, they could also bring their old message histories from other apps. Users can now import messages and media from apps like WhatsApp, Line and KakaoTalk.

+

In addition to deleting messages for both sides without a trace (2019), call history, and groups users created could also be deleted for all participants at any time. While secret chat messages disappeared for both sides since 2013, this update made it possible to remove entire Secret Chats from the chat lists of both participants.

+

Voice Chats got two improvements: users could see active voice chats from their groups at the top of the Call History page, and got the ability to adjust the volume of individual participants inside the chat.

+

This update also improved the audio player, accessibility, and added the ability to report fake groups and channels impersonating famous people or organizations.

+
+ Moving Chat History from Other Apps +
+ +

On Telegram since January 28, 2021

+ +
+

2020

+
+

December 2020

+

Voice Chats Done Right

+

We closed the year by adding a new dimension to groups with Voice Chats – persistent conference calls that run in parallel to existing text and media-based communication in the group. Voice Chats add a live layer of ephemeral talk to the group and can be used as virtual office spaces or informal lounges for any community.

+

Android users got an option to use their SD Card for storing Telegram data. iOS users received support for Siri's Announce Messages feature. iOS and Android caught up with each other to offer equal opportunities for drawing moustaches on selfies editing photos and other media.

+

We've unveiled a public platform for suggesting features and reporting issues at bugs.telegram.org.

+

Pavel Durov also presented a strategy for making Telegram sustainable for decades to come.

+
+ Voice Chats Done Right +
+ +

On Telegram since December 23, 2020

+ +

iOS-specific:

+ +
+

October 2020

+

Pinned Messages 2.0, Improved Live Locations, Playlists and More

+

Pinned Messages were upgraded, allowing for multiple pinned messages in all chats, including one-on-one chats.

+

Distance Alerts were added to live locations, giving users the option to receive a notification when another location-sharing user gets close. The map icons were updated as well, to show which way a user is facing.

+

Playlist and album support was added for files – sending multiple audio tracks will create a playlist, while sending multiple files creates an album.

+

Channel Statistics were expanded to include detailed metrics about reach and engagement for individual posts in a channel.

+
+ Pinned Messages 2.0, Improved Live Locations, Playlists and More +
+ +

On Telegram since October 30, 2020

+ +

Android-specific:

+ +
+

September 2020

+

Search Filters, Anonymous Admins, Channel Comments and More

+

Global Search received new filters: typing a chat name or time period adds filters by date and source, and media tabs at the top of the screen sort results by type, like Files or Links.

+

Support for Anonymous Admins was added to groups. When enabled, the admin’s name is hidden in the list of group members and their messages are signed with the group name instead, similar to channel posts.

+

Comments were added to Channels with a linked discussion group. Subscribers will see a comment button under each post, where they can share their thoughts on the latest updates. To try channel comments, head over to @durov.

+
+ Search Filters, Anonymous Admins, Channel Comments and More +
+ +

On Telegram since September 30, 2020:

+ +

Android-specific:

+ +
+

August 2020

+

Video Calls and Seven Years of Telegram

+

In celebration of Telegram’s 7th Anniversary and its status as one of the world's top 10 apps, the first version of Video Calls was launched for Telegram’s mobile and desktop platforms.

+

All video calls are secured with end-to-end encryption and support picture-in-picture mode, so users can search and send messages without closing the call.

+
+ Video Calls and Seven Years of Telegram +
+ +

On Telegram since August 14, 2020:

+ +
+

July 2020

+

Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More

+

Users got the option to add motion pictures to their profile page with Profile Videos. People Nearby was improved to make finding friends in your local community even easier.

+

For users who receive a notable number of messages from non-contacts, a switch was added to automatically archive and mute new chats from people not in their contacts.

+

The update also included a series of expanded features: the upload size for media and files was increased to 2 GB (previously 1.5 GB), detailed statistics became available for large groups, and the default icons used in the chat list for photos, videos and links were replaced with mini-thumbnails of the sent media.

+
+ Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More +
+ +

On Telegram since July 26, 2020:

+ +

Android-specific:

+
    +
  • Crop and Rotate videos (on iOS since time immemorial)
  • +
+

Telegram Desktop:

+ +
+

June 2020

+

Video Editor, Animated Photos, Better GIFs and More

+

The photo editor was tranformed into a universal media editor – adding the ability to edit and enhance visuals for video, put animated stickers on any media, and zoom in when drawing or decorating (just to name a few).

+

The GIF panel got upgraded, adding emoji-based sections and a Trending tab for the most relevant and popular expressions. To make them even easier to search and scroll through, loading times were greatly improved.

+
+ Video Editor, Animated Photos, Better GIFs and More +
+ +

On Telegram since June 4, 2020:

+ +

Android-Specific:

+ +
+

April 2020, Second Update

+

400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests

+

To celebrate 400 million active users, the sticker panel was revamped, allowing users to scroll and search through thousands of popular stickers from professional artists.

+

The Quiz Polls introduced in January 2020 received new tools geared toward educational tests, including explanations and a timer animation. With the need for online learning tools at a new high, a €400K contest was announced to help build a platform for educational tests on Telegram.

+
+ 400 Million Active Users +
+ +

On Telegram since April 24, 2020:

+ +

Android-specific:

+ +

MacOS-specific:

+ +
+

April 2020, First Update

+

Coronavirus News and Verified Channels

+

While the world locked down during the COVID-19 pandemic, Health Ministries began creating Telegram channels to keep their citizens informed of the latest updates. To help facilitate the spread of accurate information, the channel verification process was streamlined with a new @VerifyBot and a directory was created to help users find official coronavirus news sources for their country.

+
+ Coronavirus News and Verified Channels +
+ +

On Telegram since April 3, 2020:

+ +
+

March 2020

+

Chat Folders, Channel Stats and More

+

Expanding on Archived Chats from 2019, Chat Folders were added that let users filter their chat list into custom categories. Folders support unlimited pins, and sync across all devices on the account to keep everything organized.

+

Channel Stats were also introduced, giving channels with more than 1000 subscribers analytics and graphs to track post performance and overall growth.

+
+ Chat Folders, Channel Stats and More +
+ +

On Telegram since March 2020:

+ +
+

February 2020

+

New Profiles, Fast Media Viewer and People Nearby 2.0

+

This Valentine-themed update made it easier to make friends and view media. Profile pages were redesigned with instant access to Shared Media and users got the option to flip through photos and videos simply by tapping on them.
People Nearby was updated so users could make themselves visible to others in their area, displaying their profile even if they closed the app (until they selected ‘Stop Showing Me’).

+
+ New Profiles, Fast Media Viewer and People Nearby 2.0 +
+ +

On Telegram since February 2020:

+ +
+

January 2020

+

Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode

+

Focused on polls, the first update of 2020 added plenty of ways to get competitive – or organized - in groups and channels. Polls 2.0 introduced options to show users’ votes and the ability to select more than one answer, as well as quiz-style polls, complete with a platform for making quizzes.

+

A new slider was added to adjust how round or square chat bubbles appear, and Android users received numerical progress counters to track uploads and downloads (previously iOS-only).

+
+ TITLE +
+ +

On Telegram since January 2020:

+ +
+

2019

+
+

December 2019

+

Verifiable Builds, New Theme Editor, Send When Online and So Much More

+

On the final day of 2019, security researchers got the tools needed to confirm that the open source code we post on GitHub is the same that can be downloaded from App Store and Google Play.

+

The Theme Editor leveled up to 2.0, adding gradient colors, new background patterns and more default color schemes. Scheduled Messages were expanded with a setting to send when your recipient comes online. Android and iOS both got a slew of other usability and design upgrades.

+
+ Verifiable Builds, New Theme Editor, Send When Online and So Much More +
+ +

On Telegram since December 2019:

+ +

Android-specific:

+ +

iOS-specific:

+ +
+

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.

+
+ Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy +
+ +

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.

+

Following the success of animated stickers, this update also introduced animated emoji for ❤️, 👍, 😒, 😳 and 🥳. More followed.

+
+ Silent Messages, Slow Mode, Admin Titles and More +
+ +

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.

+
+ Animated Stickers Done Right +
+ +

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.

+
+ Location-Based Chats, Adding Contacts Without Phone Numbers and More +
+ +

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.)

+
+ Focused Privacy, Discussion Groups, Seamless Web Bots and More +
+ +

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.

+
+ Taking Back Our Right to Privacy +
+ +

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.

+
+ Autoplaying Videos, Automatic Downloads and Multiple Accounts +
+ +

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.

+
+ Chat Backgrounds 2.0: Make Your Own +
+ +

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.

+
+ Group Permissions, Undo Delete and More +
+ +

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.

+
+ Polls: Bringing Choice to Communities +
+ +

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.

+
+ Custom Languages, Instant View 2.0 and More +
+ +

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.

+
+ Telegram 5.0 for iOS +
+ +

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.

+
+ Telegram dude rides a horse-drawn cart with boxes away from a great safe in the clouds. +
+ +

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.

+
+ Telegram people show their IDs at a counter while dressed up as Korben and Lilu Dallas from the 'Fifth Element'. +
+ +

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.

+
+ The Telegram lady approaches Leonardo da Vinci who is busy refreshing his Mona Lisa in the Louvre museum. He is wearing 2X headphones and is also offering booklets which likely symbolize vCards. +
+ +

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.

+
+ Telegram lady in aviator costume leans against her spacecraft on an alien beach, watching a sky full of paper-plane-shaped spaceships traveling between planets. +
+ +

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 about Telegram, you should probably join our Volunteer Support Force.

+
+
+ +
+
+ +
+
+
+ + + + + + + + + diff --git a/data/telegram.org/faq.html b/data/telegram.org/faq.html new file mode 100644 index 0000000000..720991cb7e --- /dev/null +++ b/data/telegram.org/faq.html @@ -0,0 +1,705 @@ + + + + + Telegram FAQ + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Telegram FAQ

+ +
+

This FAQ provides answers to basic questions about Telegram.
Check out our Advanced FAQ for more technical information.

+
+

+

General

+ +

Telegram Basics

+ +

Groups and Channels

+ +

Usernames and t.me

+ +

Security

+ +

Secret Chats

+ +

Your Account

+ +

Bots

+ +

Deeper Questions

+ +

Troubleshooting

+ +

Contact Telegram Support
Follow Us on Twitter
Facebook
Advanced FAQ

+

+
+

General Questions

+

Q: What is Telegram? What do I do here?

+

Telegram is a messaging app with a focus on speed and security, it’s super-fast, simple and free. You can use Telegram on all your devices at the same time — your messages sync seamlessly across any number of your phones, tablets or computers. Telegram has over 500 million monthly active users and is one of the 10 most downloaded apps in the world.

+

With Telegram, you can send messages, photos, videos and files of any type (doc, zip, mp3, etc), as well as create groups for up to 200,000 people or channels for broadcasting to unlimited audiences. You can write to your phone contacts and find people by their usernames. As a result, Telegram is like SMS and email combined — and can take care of all your personal or business messaging needs. In addition to this, we support end-to-end encrypted voice and video calls, as well as voice chats in groups for thousands of participants.

+
+

Follow our Tips Channel to learn more about Telegram features.

+
+

Q: Who is Telegram for?

+

Telegram is for everyone who wants fast and reliable messaging and calls. Business users and small teams may like the large groups, usernames, desktop apps and powerful file sharing options.

+

Since Telegram groups can have up to 200,000 members, we support replies, mentions and hashtags that help maintain order and keep communication in large communities efficient. You can appoint admins with advanced tools to help these communities prosper in peace. Public groups can be joined by anyone and are powerful platforms for discussions and collecting feedback.

+

In case you're more into pictures, Telegram has animated gif search, a state of the art photo editor, and an open sticker platform (find some cool stickers here or here). What's more, there is no need to worry about disk space on your device. With Telegram's cloud support and cache management options, Telegram can take up nearly zero space on your phone.

+

Those looking for extra privacy should check out our advanced settings and rather revolutionary policy. And if you want secrecy, try our device-specific Secret Chats with self-destructing messages, photos, and videos — and lock your app with an additional passcode.

+
+

We keep evolving — check out our Brief History of Telegram and follow us on twitter and Telegram to stay in touch.

+
+

Q: How is Telegram different from WhatsApp?

+

Unlike WhatsApp, Telegram is a cloud-based messenger with seamless sync. As a result, you can access your messages from several devices at once, including tablets and computers, and share an unlimited number of photos, videos and files (doc, zip, mp3, etc.) of up to 2 GB each.

+

Telegram needs less than 100 MB on your device – you can keep all your media in the cloud without deleting things – simply clear your cache to free up space.

+

Thanks to Telegram's multi-data center infrastructure and encryption, it is faster and way more secure. On top of that, private messaging on Telegram is free and will stay free — no ads, no subscription fees, forever.

+

Telegram's API and code is open, and developers are welcome to create their own Telegram apps. We also have a Bot API, a platform for developers that allows anyone to easily build specialized tools for Telegram, integrate any services, and even accept payments from users around the world.

+

And that's just the tip of the iceberg.

+
+

Follow our Tips Channel to learn more about Telegram features.

+
+

Q: How old is Telegram?

+

Telegram for iOS was launched on August 14, 2013. The alpha version of Telegram for Android officially launched on October 20, 2013. More and more Telegram clients appear, built by independent developers using Telegram's open platform.

+

Q: Which devices can I use?

+

You can use Telegram on smartphones, tablets, and even computers. We have apps for iOS (9.0 and above), Android (4.1 and up), a native macOS app and a universal desktop app for Windows, macOS, and Linux. Telegram Web can also help to quickly do something on the go.

+
+

You can log in to Telegram from as many of your devices as you like — all at the same time. Just use your main mobile phone number to log in everywhere, your cloud chats will sync instantly.

+
+

The Telegram API is open for developers, should you want to build your own applications for other platforms.

+

Q: Who are the people behind Telegram?

+

Telegram is supported by Pavel Durov and his brother Nikolai. Pavel supports Telegram financially and ideologically while Nikolai's input is technological. To make Telegram possible, Nikolai developed a unique custom data protocol, which is open, secure and optimized for work with multiple data-centers. As a result, Telegram combines security, reliability and speed on any network.

+
+

See also: articles about Telegram

+
+

Q: Where is Telegram based?

+

The Telegram development team is based in Dubai.

+

Most of the developers behind Telegram originally come from St. Petersburg, the city famous for its unprecedented number of highly skilled engineers. The Telegram team had to leave Russia due to local IT regulations and has tried a number of locations as its base, including Berlin, London and Singapore. We’re currently happy with Dubai, although are ready to relocate again if local regulations change.

+

Q: Will you have ads in my private chats and groups? Or sell my data? Or steal my beloved and enslave my children?

+

No. See this post for details.

+

Q: How are you going to make money out of this?

+

We believe in fast and secure messaging that is also 100% free.

+

Our founder and CEO Pavel Durov, who financed Telegram throughout most of its history, has outlined a strategy to make Telegram sustainable in this post.

+

While Telegram will introduce monetization in 2021 to pay for the infrastructure and developer salaries, making profits will never be an end-goal for us.

+

Q: What are your thoughts on internet privacy?

+

We think that the two most important components of Internet privacy should be:

+
    +
  1. Protecting your private conversations from snooping third parties, such as officials, employers, etc.
  2. +
  3. Protecting your personal data from third parties, such as marketers, advertisers, etc.
  4. +
+

Telegram's aim is to create a truly free messenger, with a revolutionary privacy policy.

+

Q: What about GDPR?

+

The General Data Protection Regulation (GDPR) came into force in Europe on May 25, 2018. Since taking back our right to privacy was the reason we made Telegram, there wasn't much we had to change. We don’t use your data for ad targeting, we don’t sell it to others, and we're not part of any mafia family “family of companies.”

+

Telegram only keeps the information it needs to function as a feature-rich cloud service. For example, your cloud chats – so that you can access them from any devices without using third-party backups, or your contacts – so that you can rely on your existing social graph when messaging people on Telegram. Please see our Privacy Policy for more information.

+

You can use @GDPRbot to:

+
    +
  • Request a copy of all your data that Telegram stores.
  • +
  • Contact us about Data Privacy.
  • +
+

Q: There's illegal content on Telegram. How do I take it down?

+

All Telegram chats and group chats are private amongst their participants. We do not process any requests related to them.

+

But sticker sets, channels, and bots on Telegram are publicly available. If you find sticker sets or bots on Telegram that you think are illegal, please ping us at abuse@telegram.org.

+

You can also use the 'report' buttons right inside our apps, see this post on our official @ISISwatch channel for details.

+
+

Note: If a scammer is pretending to be you, contact @NoToScam

+
+

Q: A bot or channel is infringing on my copyright. What do I do?

+

All Telegram chats and group chats are private amongst their participants. We do not process any requests related to them. But sticker sets, channels, and bots on Telegram are publicly available.

+

If you see a bot, channel, or sticker set that is infringing on your copyright, kindly submit a complaint to dmca@telegram.org. Please note that such requests should only be submitted by the copyright owner or an agent authorized to act on the owner’s behalf.

+

Q: Wait! 0_o Do you process take-down requests from third parties?

+

Our mission is to provide a secure means of communication that works everywhere on the planet. To do this in the places where it is most needed (and to continue distributing Telegram through the App Store and Google Play), we have to process legitimate requests to take down illegal public content (e.g., sticker sets, bots, and channels) within the app. For example, we can take down sticker sets that violate intellectual property rights or porn bots.

+

User-uploaded stickers sets, channels, and bots by third-party developers are not part of the core Telegram UI. Whenever we receive a complaint at abuse@telegram.org or dmca@telegram.org regarding the legality of public content, we perform the necessary legal checks and take it down when deemed appropriate.

+

Please note that this does not apply to local restrictions on freedom of speech. For example, if criticizing the government is illegal in some country, Telegram won't be a part of such politically motivated censorship. This goes against our founders' principles. While we do block terrorist (e.g. ISIS-related) bots and channels, we will not block anybody who peacefully expresses alternative opinions.

+

Q: My bot or sticker set was banned unfairly, what do I do?

+

If you think we banned your bot, channel, or sticker set for no apparent reasons, drop us a line at abuse@telegram.org.

+

Q: Do you process data requests?

+

Secret chats use end-to-end encryption, thanks to which we don't have any data to disclose.

+

To protect the data that is not covered by end-to-end encryption, Telegram uses a distributed infrastructure. Cloud chat data is stored in multiple data centers around the globe that are controlled by different legal entities spread across different jurisdictions. The relevant decryption keys are split into parts and are never kept in the same place as the data they protect. As a result, several court orders from different jurisdictions are required to force us to give up any data.

+

Thanks to this structure, we can ensure that no single government or block of like-minded countries can intrude on people's privacy and freedom of expression. Telegram can be forced to give up data only if an issue is grave and universal enough to pass the scrutiny of several different legal systems around the world.

+

To this day, we have disclosed 0 bytes of user data to third parties, including governments.

+

Telegram Basics

+
+

Follow our Tips Channel to learn more about Telegram features.

+
+

Q: Who can I write to?

+

You can write to people who are in your phone contacts and have Telegram. Another way of contacting people is to type their Telegram username into the search field – you don't need to know their phone number to do this.

+

Q: Who can contact me?

+

People can contact you on Telegram if they know your phone number or if you message them first.

+

If they don't know your phone number, they can find you in these cases:

+
    +
  • When you both are members of the same group.
  • +
  • If you set a public username. Others can use Global Search and find you by your username.
  • +
  • If you opt-in to appear in the People Nearby section (this is turned off by default).
  • +
+

Q: How do I know who in my contacts has Telegram?

+

Your contacts, who have Telegram, are shown at the top of your Contacts. They also have pictures.

+

Q: How do I invite my friends?

+

iOS: The basic invitations are simple SMS messages. They will be charged as standard outgoing SMS by your carrier (unless sent via iMessage). Naturally, you have other options to bring your friends here. Try sending them a download link via any other messaging service: email, Facebook, WhatsApp, an actual telegram — you name it. The link: https://telegram.org/dl/

+

Android: Open the app menu (swipe right in chat list) > Invite Friends. Then choose an application via which you would like to send out invitations.

+
+

You can give your friends a t.me link with your username so that they can easily find you on Telegram even if they don't have your phone number.

+
+

Q: What do the check marks mean?

+

One check — message delivered to the Telegram cloud and your friend has been notified if he allows notifications.
Two checks — message read (your friend opened Telegram and opened the conversation with the message).

+

We don't have a 'delivered to device' status for messages because Telegram can run on as many devices as you want. So which particular one would that check mean?

+

Q: Can I hide my ‘last seen’ time?

+

You can choose who sees this info in Privacy and Security settings.

+

Remember that you won't see Last Seen timestamps for people with whom you don't share your own. You will, however, see an approximate last seen value. This keeps stalkers away but makes it possible to understand whether a person is reachable over Telegram. There are four possible approximate values:

+
    +
  • Last seen recently — covers anything between 1 second and 2-3 days
  • +
  • Last seen within a week — between 2-3 and seven days
  • +
  • Last seen within a month — between 6-7 days and a month
  • +
  • Last seen a long time ago — more than a month (this is also always shown to blocked users)
  • +
+

Q: Who can see me 'online'?

+

The last seen rules apply to your online status as well. People can only see you online if you're sharing your last seen status with them.

+

There are some exceptions because sometimes it is obvious that you are online. Regardless of the last seen settings, people will see you online for a brief period (~30 seconds) if you do the following:

+
    +
  • Send them a message in a one-on-one chat or in a group where you both are members.
  • +
  • Read a message they sent you in a one-on-one chat.
  • +
  • Broadcast a “typing…” status to their chat with you or to a group where you both are members.
  • +
+

If you're not sharing your last seen timestamp with someone and don't do anything of the above, they'll never see you online. Another way of achieving this is to block that person.

+

Q: What is People Nearby?

+

People Nearby is an optional feature that allows Telegram users to explore local groups, find friends to chat with in their area, or quickly exchange contacts with people who are close.

+

You can find it in Contacts > Find People Nearby, as well as directly in the side menu on Android.

+

While you have the People Nearby section open on your screen, people who are very close will be able to see you there. If you don't open the section, others will never see you in 'People Nearby'.

+

You can also choose to permanently add your profile to the list of nearby people by tapping Make Myself Visible. After becoming visible, you can remove your profile from the list at any time by tapping Stop Showing Me.

+
+

Note: People Nearby is never turned on by default – users must manually enable it. If you are receiving messages from someone you don't know, see Q: Who can contact me?

+
+

Q: Can I delete my messages?

+

Yes. You can always delete any messages you sent or received for both sides in any one-on-one conversation (in groups, it's still your own messages only). You can also clear the entire chat history on both ends. On Telegram, deleted messages do not leave a mark in the chat.

+
+ +
+ +

Together with privacy settings for forwarded messages, this makes exchanging Telegram messages similar to talking face to face (without a tape recorder). As a result, users no longer need to worry about the data accumulating in their chats over the years. Both parties in a conversation have full control over what does and what doesn't belong to their online identity.

+

Q: Can I make calls via Telegram?

+

Yes! You can make end-to-end encrypted Voice Calls and Video Calls.

+

If you want more participants, try starting a Voice Chat in one of the groups you created. Voice Chats add 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.

+

Q: How can I use emoticons?

+

Type one word in your input field to get relevant emoji suggestions. You can also type “:” followed by any keyword to open emoji search – like :heart.

+

You can suggest missing keywords for emoji in your language using this interface (this will open suggestions for English, don't forget to change to your language in the left menu).

+

Groups and Channels

+

Q: What makes Telegram groups cool?

+

Telegram groups can have up to 200,000 members each and are extremely powerful communication tools. Here are a few key features that make them stand out in the messaging world:

+

Unified history
Edit your messages after posting, delete them so that they disappear for everyone.

+

Cross-platform availability
Access your messages anytime, from any number of your mobile or desktop devices.

+

Instant search
Find the message you're looking for, even among millions. Filter by sender to make searching easier.

+

Replies, mentions, hashtags
Easily trace a conversation and keep communication efficient, no matter the group size.

+

Smart notifications
Mute the group to get notifications only when people mention you or reply to your messages.

+

Pinned messages
You can pin any message to be displayed at the top of the chat screen. All members will get a notification — even if they muted ordinary messages from your group.

+

Moderation tools
Appoint administrators that can mass-delete messages, control membership, and pin important messages. Define their admin privileges with granular precision.

+

Group permissions
Set default permissions to restrict all members from posting specific kinds of content. Or even restrict members from sending messages altogether – and let the admins chat amongst themselves while everybody else is watching.

+

File sharing
Send and receive files of any type, up to 2 GB in size each, access them instantly on your other devices.

+

Public groups
Get a short link for your group and make it public, like t.me/publictestgroup. This way, anybody can view the group's entire chat history and join to post messages.

+

Customization via bots
Create custom tools for any specific needs using our Bot API and Inline Bots.

+

Q: What's the difference between groups and channels?

+

Telegram groups are ideal for sharing stuff with friends and family or collaboration in small teams. But groups can also grow very large and support communities of up to 200,000 members. You can make any group public, toggle persistent history to control whether or not new members have access to earlier messages and appoint administrators with granular privileges. You can also pin important messages to the top of the screen so that all members can see them, including those who have just joined.

+

Channels are a tool for broadcasting messages to large audiences. In fact, a channel can have an unlimited number of subscribers. When you post in a channel, the message is signed with the channel's name and photo and not your own. Each message in a channel has a view counter that gets updated when the message is viewed, including its forwarded copies.

+
+

Read more about channels in the Channels FAQ »

+
+

Q: How do I create a group?

+

iOS: Start a new message (tap the icon in the top right corner in Chats) > 'New Group'.
Android: Tap the circular pencil icon in the chat list > 'New Group'.
Telegram Desktop: Click the menu button in the top left corner > 'New Group'.

+

Q: Can I assign administrators?

+

You can add administrators to help you manage your group and define their privileges with granular precision.

+

iOS: Go to Group Info (tap the photo in the top right corner on the group‘s chat screen) > Edit > Administrators.
Android: Go to Group Info (tap the name in the header) > the pencil icon (in the top right corner) > Administrators.
Telegram Desktop: When in the group, click '…' in the top right corner > Manage group > Administrators.

+

Q: How do I add more members? What's an invite link?

+

You can add your contacts, or using search by username.

+

It is easy to migrate existing groups to Telegram by sending people an invite link. To create an invite link, go to Group Info > Add Member > Invite to Group via Link.

+

Anyone who has Telegram installed will be able to join your group by following this link. If you choose to revoke the link, it will stop working immediately.

+
+

Read more about invite links in our blog »

+
+

Usernames and t.me

+

Q: What are usernames? How do I get one?

+

You can set up a public username on Telegram. It then becomes possible for other users to find you by that username — you will appear in contacts search under 'global results'. Please note that people who find you will be able to send you messages, even if they don't know your number. If you are not comfortable with this, we advise against setting up a username in Telegram.

+

You can set up a username in Settings and use the universal search box in the chat list to search for chats, messages, and usernames.

+

Q: How does t.me work?

+

Once you've set up a username, you can give people a t.me/username link. Opening that link on their phone will automatically fire up their Telegram app and open a chat with you. You can share username links with friends, write them on business cards or put them up on your website.

+

This way people can contact you on Telegram without knowing your phone number.

+

Q: What can I use as my username?

+

You can use a-z, 0-9 and underscores. Usernames are case-insensitive, but Telegram will store your capitalization preferences (e.g. Telegram and TeleGram is the same user). The username must be at least five characters long.

+

Q: Do I need a username?

+

You don't have to get one. Remember that Telegram usernames are public and choosing a username on Telegram makes it possible for people to find you in global search and send you messages even if they don't have your number. If you are not comfortable with this, we advise against setting up a username.

+

Q: If someone finds me by username, messages and I reply — will they know my number?

+

No. Neither party will see another's phone number (unless this is permitted by your privacy settings). This is similar to the case when you message a person who you've met in a Telegram group.

+

Q: How do I delete my username?

+

Go to Settings and save an empty username. This will remove your username; people will no longer be able to find you via search. This will not affect existing conversations.

+

Q: What do I do if my username is taken?

+

Telegram usernames are distributed on a first come — first serve basis.

+

We understand that certain usernames are part of an online identity for some of us. If your desired username is already taken, we will be happy to help you acquire it for your account or channel, provided that you have that same username on at least two of these services: Facebook, Twitter, Instagram.

+

Due to the fact that one account can register multiple bot and channel usernames, we reserve the right to recall usernames assigned to unused bots and channels, as well as openly squatted usernames.

+

To request a username, contact @Username_bot.

+

Q: What if someone is pretending to be me?

+

If a scammer is pretending to be you, please contact @NoToScam.

+

Security

+
+

If you are an advanced user, you may find our FAQ for the Technically Inclined useful as well.

+
+

Q: How secure is Telegram?

+

Telegram is more secure than mass market messengers like WhatsApp and Line. We are based on the MTProto protocol (see description and advanced FAQ), built upon time-tested algorithms to make security compatible with high-speed delivery and reliability on weak connections. We are continuously working with the community to improve the security of our protocol and clients.

+

Q: What if I’m more paranoid than your regular user?

+

We've got you covered. Telegram’s special secret chats use end-to-end encryption, leave no trace on our servers, support self-destructing messages and don’t allow forwarding. On top of this, secret chats are not part of the Telegram cloud and can only be accessed on their devices of origin.

+

Q: So how do you encrypt data?

+

We support two layers of secure encryption. Server-client encryption is used in Cloud Chats (private and group chats), Secret Chats use an additional layer of client-client encryption. All data, regardless of type, is encrypted in the same way — be it text, media or files.

+

Our encryption is based on 256-bit symmetric AES encryption, 2048-bit RSA encryption, and Diffie–Hellman secure key exchange. You can find more info in the Advanced FAQ.

+
+

See also: Do you process data requests?

+
+

Q: Why should I trust you?

+

Telegram is open, anyone can check our source code, protocol and API, see how everything works and make an informed decision. Telegram supports verifiable builds, which allow experts to independently verify that our code published on GitHub is the exact same code that is used to build the apps you download from App Store or Google Play.

+

We welcome security experts to audit our system and appreciate any feedback at security@telegram.org.

+

On top of that, Telegram's primary focus is not to bring a profit, so commercial interests will never interfere with our mission.

+
+

See also: articles about Telegram

+
+

Q: Do I need to trust Telegram for this to be secure?

+

When it comes to secret chats, you don't — just make sure that the visualized key of your secret chat matches the one in your friend's secret chat settings. More about this below.

+

Q: What if my hacker friend says they could decipher Telegram messages?

+

Anyone who claims that Telegram messages can be deciphered is welcome to prove that claim in our competition and win $300,000. You can check out the Cracking Contest Description to learn more.

+

Any comments on Telegram's security are welcome at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $100 to $100,000 or more, depending on the severity of the issue. Please note that we can not offer bounties for issues that are disclosed to the public before they are fixed.

+

Q: Can Telegram protect me against everything?

+

Telegram can help when it comes to data transfer and secure communication. This means that all data (including media and files) that you send and receive via Telegram cannot be deciphered when intercepted by your internet service provider, owners of Wi-Fi routers you connect to, or other third parties.

+

But please remember that we cannot protect you from your own mother if she takes your unlocked phone without a passcode. Or from your IT-department if they access your computer at work. Or from any other people that get physical or root access to your phones or computers running Telegram.

+

If you have reasons to worry about your personal security, we strongly recommend using only Secret Chats in official or at least verifiable open-source apps for sensitive information, preferably with a self-destruct timer. We also recommend enabling 2-Step Verification and setting up a strong passcode to lock your app, you will find both options in Settings > Privacy and Security.

+

Q: How does 2-Step Verification work?

+

Logging in with an SMS code is an industry standard in messaging, but if you're looking for more security or have reasons to doubt your mobile carrier or government, we recommend protecting your cloud chats with an additional password.

+

You can do this in Settings > Privacy and Security > 2-Step Verification. Once enabled, you will need both an SMS code and a password to log in. You can also set up a recovery email address that will help regain access, should you forget your password. If you do so, please remember that it's important that the recovery email account is also protected with a strong password and 2-Step Verification when possible.

+

Check this out for tips on creating a strong password that is easy to remember.

+

Q: Why can jailbroken and rooted devices be dangerous?

+

Using a rooted or jailbroken device makes it easier for a potential attacker to gain full administrative control over your device — root access.

+

A user with root access can easily bypass security features built into the operating system, read process memory or access restricted areas, such as the internal storage. Once an attacker has root access, any efforts to mitigate threats become futile. No application can be called safe under these circumstances, no matter how strong the encryption.

+

Secret Chats

+

Q: How are secret chats different?

+

Secret chats are meant for people who want more secrecy than the average fella. All messages in secret chats use end-to-end encryption. This means only you and the recipient can read those messages — nobody else can decipher them, including us here at Telegram (more on this here). On top of this, Messages cannot be forwarded from secret chats. And when you delete messages on your side of the conversation, the app on the other side of the secret chat will be ordered to delete them as well.

+

You can order your messages, photos, videos and files to self-destruct in a set amount of time after they have been read or opened by the recipient. The message will then disappear from both your and your friend's devices.

+

All secret chats in Telegram are device-specific and are not part of the Telegram cloud. This means you can only access messages in a secret chat from their device of origin. They are safe for as long as your device is safe in your pocket.

+

Q: How do I start a secret chat?

+

Open the profile of the user you want to contact. Tap on ‘…’, then ‘Start Secret Chat’.

+

Remember that Telegram secret chats are device-specific. If you start a secret chat with a friend on one of your devices, this chat will only be available on that device. If you log out, you will lose all your secret chats. You can create as many different secret chats with the same contact as you like.

+

Q: How do self-destructing messages work?

+

The Self-Destruct Timer is available for all messages in Secret Chats and for media in private cloud chats.

+

To set the timer, simply tap the clock icon (in the input field on iOS, top bar on Android), and then choose the desired time limit. The clock starts ticking the moment the message is displayed on the recipient's screen (gets two check marks). As soon as the time runs out, the message disappears from both devices. We will try to send a notification if a screenshot is taken.

+

Please note that the timer in Secret Chats only applies to messages that were sent after the timer was set. It has no effect on earlier messages.

+

Q: Can I be certain that my conversation partner doesn't take a screenshot?

+

Unfortunately, there is no bulletproof way of detecting screenshots on certain systems (most notably, some Android and Windows Phone devices). We will make every effort to alert you about screenshots taken in your Secret Chats, but it may still be possible to bypass such notifications and take screenshots silently. We advise to share sensitive information only with people you trust. After all, nobody can stop a person from taking a picture of their screen with a different device or an old school camera.

+

Q: What is this 'Encryption Key' thing?

+

When a secret chat is created, the participating devices exchange encryption keys using the so-called Diffie-Hellman key exchange. After the secure end-to-end connection has been established, we generate a picture that visualizes the encryption key for your chat. You can then compare this image with the one your friend has — if the two images are the same, you can be sure that the secret chat is secure, and no man-in-the-middle attack can succeed.

+

Newer versions of Telegram apps will show a larger picture along with a textual representation of the key (this is not the key itself, of course!) when both participants are using an updated app.

+

Always compare visualizations using a channel that is known to be secure — it's safest if you do this in person, in an offline meeting with the conversation partner.

+

Q: Why not just make all chats 'secret'?

+

All Telegram messages are always securely encrypted. Messages in Secret Chats use client-client encryption, while Cloud Chats use client-server/server-client encryption and are stored encrypted in the Telegram Cloud (more here). This enables your cloud messages to be both secure and immediately accessible from any of your devices – even if you lose your device altogether.

+

The problem of restoring access to your chat history on a newly connected device (e.g. when you lose your phone) does not have an elegant solution in the end-to-end encryption paradigm. At the same time, reliable backups are an essential feature for any mass-market messenger. To solve this problem, some applications (like Whatsapp and Viber) allow decryptable backups that put their users' privacy at risk – even if they do not enable backups themselves. Other apps ignore the need for backups altogether and leave their users vulnerable to data loss.

+

We opted for a third approach by offering two distinct types of chats. Telegram disables default system backups and provides all users with an integrated security-focused backup solution in the form of Cloud Chats. Meanwhile, the separate entity of Secret Chats gives you full control over the data you do not want to be stored.

+

This allows Telegram to be widely adopted in broad circles, not just by activists and dissidents, so that the simple fact of using Telegram does not mark users as targets for heightened surveillance in certain countries. We are convinced that the separation of conversations into Cloud and Secret chats represents the most secure solution currently possible for a massively popular messaging application.

+
+

See also: Why Telegram isn't End-to-End Encrypted “by Default”

+
+

Your Account

+

Q: Who can see my phone number?

+

On Telegram, you can send messages in private chats and groups without making your phone number visible. By default, your number is only visible to people who you've added to your address book as contacts. You can further modify this in Settings > Privacy and Security > Phone Number.

+
+

Note that people will always see your number if they know it already and saved it in their address book.

+
+

Q: I have a new phone number, what do I do?

+

Each phone number is a separate account on Telegram. You have several options if you are using multiple phone numbers:

+
    +
  • If you will no longer use the old number (e.g., you moved to a new country or changed your number for good), simply go to Settings and change the number connected to your Telegram account to the new number. Important: make sure you have access to your connected phone number – otherwise you risk losing access to your account.
  • +
  • If you will use the new number for a limited time (e.g., you're on a trip or vacation), there's no need to do anything.
  • +
  • If you want to keep using both numbers (e.g., you have a work phone and personal phone), choose one as your Telegram number. You may create another Telegram account on the second number as well, for example, if you want to keep work and personal chats separated. It is possible to log in to one Telegram app with up to 3 different accounts at once.
  • +
+

Q: How do I log out?

+

Most users don't need to log out of Telegram:

+
    +
  • You can use Telegram on many devices at the same time. Just use the same phone number to log in on all devices.
  • +
  • You can go to Settings > Data and Storage > Storage Usage> Clear cache to free up space on your device without logging out.
  • +
  • If you use Telegram with multiple phone numbers, you can switch between accounts without logging out.
  • +
  • If you use Telegram on a shared device, you can set up a passcode in Settings > Privacy and Security to make sure only you have access to your account.
  • +
+

If you do want to log out for some reason, here's how you do that:

+

iOS: Go to Settings > Edit > Log out.
Android, Telegram Desktop: Go to Settings > … (in the top right corner) > Log out.

+

If you log out, you will keep all your cloud messages. However, you will lose all your Secret Chats and all messages inside those secret chats when you log out.

+
+

Note that logging out does not trigger remote deletion of your secret chat messages on your partner's device — to do that, choose 'Clear History' first.

+
+

Q: How do I change my phone number?

+

You can change your number in Telegram and keep everything, including all your contacts, messages, and media from the Telegram cloud, as well as all your Secret Chats on all devices.

+

To change your number, go to Settings, then tap on your phone number (just above the username), then 'Change Number'. If you already have a different Telegram account on the target number, you'll need to delete that account first.

+

Q: How do I delete my account?

+

If you would like to delete your account, you can do this on the deactivation page. Deleting your account permanently removes all your messages and contacts. All groups and channels that you've created are orphaned and left without a creator but admins retain their rights.

+

This action must be confirmed via your Telegram account and cannot be undone.

+
+

We recommend using a non-mobile browser for this process.
Note that you'll receive the code via Telegram, not SMS.

+
+

Q: What happens if I delete my account?

+

As was just mentioned above, all your data will be flushed from our system: all messages, groups, and contacts associated with your account will be deleted. That said, your contacts will still be able to chat in the groups that you have created, and they will still have their copy of the messages you sent them. So if you want to send messages that can vanish without a trace, try using our self-destruct timer instead.

+

Termination of a Telegram account is irreversible. If you sign up again, you will appear as a new user and will not get your history, contacts or groups back. People, who have your phone number in their contacts, will be notified. The new user will be displayed as a separate conversation in their messages list and their conversation history with this new user will be empty.

+

Q: How does account self-destruction work?

+

Telegram is not a commercial organization, and we value our disk space greatly. If you stop using Telegram and don't come online for at least six months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct in Settings.

+

Q: My phone was stolen, what do I do?

+

First of all, sorry about your phone. Unfortunately, the phone number is the only way for us to identify a Telegram user at the moment. We don't collect additional information about you, so whoever has the number, has the account. This means we can't help you unless you have access either to the phone number or to Telegram itself on any of your devices.

+
I have access to Telegram on another device
+
    +
  1. Go to Telegram Settings > Privacy and Security and turn on Two-Step Verification. This way the phone number alone will not be enough to log in to your account.
  2. +
  3. Go to Settings > Devices (or Privacy & Security > Active Sessions) and terminate your Telegram session on the old device. Whoever has your phone will not be able to log in again, since they don't know your password.
  4. +
  5. Contact your phone provider, so that they block your old SIM and issue a new one with your number.
  6. +
  7. If you decide to switch to a new phone number, don't forget to go to Settings, tap on your phone number and change your Telegram number to the new one.
  8. +
+
I don't have access to Telegram on any other devices
+
    +
  1. First and foremost, you need to contact your phone provider, so that they block your old SIM and issue a new one with your number.
  2. +
  3. Wait till you receive your new SIM with the old number, log in to Telegram, then go to Settings > Devices (or Privacy & Security > Active Sessions) and terminate your Telegram session on the old device.
  4. +
+
Removing sensitive data
+

Common thieves usually throw out the SIM card immediately (the phone is harder to locate this way), then wipe the devices and sell them, so there isn't much risk for the data in case of regular petty theft. But if you have reasons to worry about the data on the device and are unable to log out the other device, it is best that you wipe it remotely. You can read more about it here: Apple iOS, Android. Unfortunately, this requires you to have prepared in advance for this scenario.

+

You can delete your Telegram account if you are logged in on at least one of your other devices (mobile or desktop). Note that inactive Telegram accounts self-destruct automatically after a period of time — 6 months being the default setting.

+

Bots

+
+

If you're a developer, you may find our Bots FAQ more useful.

+
+

Q: What are bots?

+

Bots are like small programs that run right inside Telegram. They are made by third-party developers using the Telegram Bot API.

+

Q: How do I create a bot?

+

Creating Telegram bots is super-easy, but you will need at least some skills in computer programming. If you're sure you're up to it, our Introduction for Developers is a good place to start.

+

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.

+

Q: A bot is sending me messages, how do I make it stop?

+

If you don't want a bot to send you messages, feel free to block it – same as you would block a human user. Some Telegram clients have a 'Stop Bot' button right in the bot's profile.

+

That said, most bot developers offer commands that silence the bot, check its /help for clues.

+

Q: Are bots safe?

+

Yes. Bots are no different from human users that you meet in groups for example. They can see your public name, username, and profile pictures, and they can see messages you send to them, that's it. They can't access your last seen status and don't see your phone number (unless you decide to give it to them yourself).

+

Naturally, any bot should be treated as a stranger — don't give them your passwords, Telegram codes or bank account numbers, even if they ask nicely. Also, be careful when opening files sent by bots, same as you would deal with ordinary humans. Example: If a bot sent us a file called OpenMe.exe, we probably wouldn't open it.

+

Q: If I add a bot to my group, can it read my messages?

+

Bots can work in two modes when you add them to groups. By default, bots only see messages that are meant for them. In this case, you'll see 'has no access to messages' in the group members list next to the bot.

+

Some bots need more information to work, so developers may disable the privacy mode. In this case, the bot will see all messages sent to the group, and you will see 'has access to messages' in the members list next to the bot.

+

Learn more about privacy mode for bots »

+

If your group contains very sensitive information, maybe it's better to avoid adding bots you don't trust 100%.

+

Q: Are bots made by Telegram?

+

No. While we have some official bots for specific purposes (like @gif or @GDPRbot), we don't usually make bots. Bots are made by third-party developers using the Telegram Bot API and platform.

+

Q: Where can I find more bots?

+

There is no official store at the moment, so you'll have to ask your friends or search the web for now. We're pretty sure you'll find some bots to play with.

+

Deeper questions

+

Q: Can I get Telegram's server-side code?

+

All Telegram client apps are fully open source. We offer verifiable builds both for iOS and Android – this technology allows to independently verify that the application you download from the app stores was built using the exact same code that we publish.

+

By contrast, publishing the server code doesn’t provide security guarantees neither for Secret Chats nor for Cloud Chats. This is because – unlike with the client-side code – there’s no way to verify that the same code is run on the servers.

+

As for Secret Chats, you don’t need the server-side code to check their integrity – the point of end-to-end encryption is that it must be solid regardless of how the servers function.

+
+

In a post on his channel, Pavel Durov explained why Telegram hasn't published the server code, even as a publicity stunt.

+
+

The encryption and API used on Telegram's servers are fully documented and open for review by security experts. We welcome any comments at security@telegram.org

+

Q: Can I run Telegram using my own server?

+

Our architecture does not support federation yet. Telegram is a unified cloud service, so creating forks where two users might end up on two different Telegram clouds is unacceptable. To enable you to run your own Telegram server while retaining both speed and security is a task in itself. At the moment, we are undecided on whether or not Telegram should go in this direction.

+

Q: Can I use the Telegram API?

+

Yes. Developers for all platforms are welcome to use our protocol, API and even source code. Check out the Getting started section of the docs.

+
+

Don't forget about our Bot API that lets you build cool stuff on our platform.

+
+

Q: Do you have a Privacy Policy?

+

Sure. Check this out.

+

Q: What does the iOS privacy sheet mean?

+

Apple created privacy sheets to inform users about what data apps may collect, but information there is vague and can be misleading. You can see a detailed explanation of Telegram's sheet here.

+

Q: Why do you have two apps in the Mac App Store?

+

One is our app for macOS, the other is Telegram Lite, the macOS version of our multi-platform client. Both apps are official. Both started out as unofficial applications by two different developers and vary in design and functionality.

+

Telegram for macOS supports many platform-specific features, such as the MacBook Pro Touch Bar, gesture navigation, integration with the Mac's Share menu and more. It has every feature from the iOS version of the app including Secret Chats.

+

Telegram Lite is a lightning-fast app, optimized for work-related tasks and handling large communities. It offers a three-column interface, perfect for multitasking and quick access to media, files and links shared in your chats. This app can also be used to export your Telegram data and chats.

+

Q: Can I translate Telegram?

+

Telegram is officially available in English, Spanish, German, Dutch, Italian, French, Arabic, Portuguese, Korean, Malay, Russian and Ukrainian on most platforms, and we are gradually expanding the list of languages built into the apps.

+

If you don’t like how a specific element in Telegram's interface is translated in your language, or would like to help us maintain the translation, check out our localization platform. Everyone can suggest translations and vote for the best ones, making Telegram localization a community-driven effort.

+

If you're looking to go beyond suggestions for individual phrases and would like to help us maintain the official translation to your language on a continuous basis, you can contact @TelegramAuditions. Please include a hashtag with the English name of your language (e.g. #Albanian) and a few links to phrases on this platform with your translation suggestions or comments. Be sure to read the Style Guide carefully before you apply.

+

Q: Can I help?

+

Yes, we are always looking for volunteers to help us with user support. If you would be interested in answering questions about Telegram to users from your country, contact our auditions account.

+

Before you apply, please check out the Telegram Support Initiative.

+

Passport

+

Telegram Passport is a unified authorization method for services that require personal identification. With Telegram Passport, you can upload your documents once, then instantly share your data with services that require real-world ID (finance, ICOs, etc.).

+

Your identity documents and personal data will be stored in the Telegram cloud using End-to-End Encryption. To Telegram, this data is just random gibberish, and we have no access to the information you store in your Telegram Passport. When you share data, it goes directly to the recipient.

+
+

You can find more information about Telegram Passport on our blog.

+
+

If you're a developer or owner of a service that requires real-life ID, kindly take a look at this manual. You can also try requesting Telegram Passport data using this page.

+
+

Troubleshooting

+

Login and SMS

+

Please make sure you are entering your mobile phone number in the international format.
I.e.: +(country code)(city or carrier code)(your number)

+

If you are having registration or login problems, please contact us using this form.

+

Getting a code via a phone call

+

For security reasons, login codes dictated via a phone call are only available for accounts that have two-step verification enabled (Settings > Privacy & Security > Two-Step Verification).

+

Please also note that Telegram accounts can only be connected to a mobile number. We currently don't support landline numbers.

+

Getting a code via Telegram

+

If you have recently used one of our apps on another device (it could also be a different app on the same device), we may send the login code via Telegram instead of SMS.

+

To receive such a code, just check Telegram from any of your connected devices. You will find it in the chat with Telegram, a verified profile with a blue check:

+
+ +

Login code sent via Telegram

+
+ +

WARNING! Please note that getting codes via Telegram should not be considered an alternative to using an up-to-date phone number. In case of a change in numbers, always make sure Telegram is connected to a phone number you control, otherwise you risk losing access to your account forever.

+

Notification problems

+
+

If the tips below don't help, check out this detailed guide on Troubleshooting Notification Issues.

+
+

ANDROID

+
    +
  1. Go to Telegram Settings — Notifications and Sounds, make sure that notifications are ON and Importance is set to “High” or greater.
  2. +
  3. Check whether contact or group is muted.
  4. +
  5. Make sure Google Play Services are installed on your phone.
  6. +
  7. Check notification priority for Telegram in Android settings, it can be called Importance or Behaviour depending on your device.
  8. +
  9. If your phone uses some battery saving software, make sure that Telegram is whitelisted in that application.
  10. +
+
+

NOTE: Huawei and Xiaomi devices have evil task killer services that interfere with the Telegram notification service. For our notifications to work, you need to add Telegram to allowed apps in those devices' security settings. Huawei: Phone Manager App > Protected Apps > Add Telegram to the list. Xiaomi: Services > Security > Permissions > Autostart, find Telegram and enable autostart.

+
+

iOS

+
    +
  1. Go to Telegram Settings — Notifications and Sounds, make sure that notifications are ON in Telegram.
  2. +
  3. Check that notifications are ON in phone Settings.
  4. +
  5. Check, whether contact or group is muted.
  6. +
  7. Shut down Telegram (go to home screen, double tap home button, swipe upwards on Telegram), then go to phone settings, set the alert style for Telegram to NONE. Relaunch Telegram, go to phone settings, set alert style back to banners.
  8. +
+

Problems with contacts

+

If you know your friends have Telegram, but you can't see them — or they appear as numbers instead of names.

+

Android:

+
    +
  1. Make sure you are using the latest version of the app.
  2. +
  3. Relaunch the app (by terminating it from processes list and launching again).
  4. +
  5. Temporarily change the name of the contact in phone contacts (add a few symbols, then change back again).
  6. +
  7. If that didn't help, re-login. Remember that logging out kills your Secret Chats.
  8. +
+

iOS:

+
    +
  1. Force quit the app (double tap home button, then swipe up on Telegram), then relaunch and check if it helped.
  2. +
  3. If that doesn't help, temporarily change the name of the contact in phone contacts (add a few symbols, then change back again).
  4. +
  5. If that doesn’t work, re-login: Settings > Edit > Log Out. Remember that logging out kills all your Secret Chats. Then log in again.
  6. +
+

Deleting contacts on Android

+

To delete a contact, open a chat with the person, tap the title in the top area of the chat screen to open their profile, then tap on (⋮) in the top right corner > 'Delete contact'.

+

If you want to delete the contact completely, make sure you also delete them from your phone contacts. Telegram stays in sync and will add the contact back if you don't.

+

Where did my Secret Chat messages go?

+

Secret Chats are established between the two devices they were created on. This means that all those messages are not available in the cloud and cannot be accessed on other devices.

+

Moreover, Secret Chats are also tied to your current login session on the device. If you log out and in again, you will lose all your Secret Chats.

+

Can't send messages to non-contacts

+

When users report unwanted messages from a Telegram account, we apply a limit: Reported accounts can only send messages to people who have their number saved as a contact.

+

This means that if you randomly contact people you don't know and send them annoying messages, you may lose the ability to do so in the future.

+

If you think that this limit was applied to your account wrongly, please visit this page.

+

Telegram uses the camera or microphone in the background!

+

Telegram can use the microphone in the background if you minimize the app when making a call, recording a video, or recording a voice/video message.

+

Permission monitors on Samsung and Xiaomi can inadvertently flag and notify you that Telegram requested access to camera in the background. This happens when the app requests info about the camera — it isn’t using the camera. Unfortunately it may look the same to the Samsung and Xiaomi permission monitors.

+

Camera info is requested by the app when you tap on the attachment button, or start recording a video or a video message. If you do this and quickly close the app, the already initiated request may try to run asynchronously when the app is already in the background, or be sent when the system wakes up the app to show a notification about a new message. In any case, these requests are only for the camera info, the app never uses the camera itself in the background.

+

Anyone can check Telegram’s open source code and confirm that the app is not doing anything behind their back. We also offer reproducible builds that can help you prove that the version you downloaded from App Store or Google Play is built from the exact same source code we publish.

+
+

Telegram Support

+

If you have any other questions, please contact Telegram Support (in Telegram go to Settings — Ask a question). Note that we rely on volunteers for support.

+

If you can't log in to your account, please use this form.

+
+

For media requests, please contact @PressBot on Telegram.

+
+

Twitter?

+

Yep. Follow us! @telegram
Our twitter account in Spanish: @telegram_es
In Italian: @telegram_it
In Korean: @Telegram_kr
In German: @de_telegram
For users from Brazil: @Telegram_br
Our Arabic-speaking users may find @telegram_arabic more interesting.

+

@SmsTelegram, login help on Twitter

+

We have a special account that can help you with login problems, @smstelegram. This account is official. Don't be afraid to DM it the number you use for Telegram, we need this info to investigate issues.

+

Be careful, we don't have any other support accounts on any social media platforms.

+

Facebook or other platforms?

+

If anyone on Facebook or any other platform is telling you they're us, they are not.

+

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/faq_channels.html b/data/telegram.org/faq_channels.html new file mode 100644 index 0000000000..9cd612a10c --- /dev/null +++ b/data/telegram.org/faq_channels.html @@ -0,0 +1,165 @@ + + + + + Channels FAQ + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Channels FAQ

+ +
+

This FAQ is about Telegram channels.
Back to the main FAQ »

+
+

+
+

Q: What's a channel?

+

Channels are a tool for broadcasting public messages to large audiences. In fact, channels can have an unlimited number of subscribers. When you post in a channel, the message is signed with the channel's name and not yours. You can appoint additional administrators to help you manage the channel. New subscribers can see the entire message history in a channel once they join.

+

If you'd like an example, join our official Telegram channel to get notified about our updates.

+

To create a channel:
iPhone: Start a new message (tap the icon in the top-right corner in Chats). Then ‘New Channel’.
Android: Tap the circular pencil icon in the chat list. Then ‘New Channel’.
Windows Phone: Tap the ‘+’ button on the bottom bar. Then ‘New Channel’.

+

Q: How are public and private channels different?

+

Public channels have a username. Anyone can find them in Telegram search and join. Private channels are closed societies – you need to be added by the owner or get an invite link to join.

+

Please note that private channels with publicly available invite links will be treated in the same way as public channels, should it come to content disputes.

+

Q: What can administrators do?

+

The owner of a channel can broadcast messages, delete any messages, add subscribers (the first 200 only), remove subscribers, change the channel's name, profile image and link, as well as delete the channel completely. The owner can also add and remove administators to help manage the channel.

+

You can set up administrator rights for each individual administrator when you appoint them.

+

Q: What happens if I delete a message?

+

If a message is deleted in a channel, it will disappear for all subscribers.

+

Q: How do I add people to my channel?

+

As the channel's owner, you may invite the first 200 subscribers to your channel. Once the subscriber count reaches 200, the channel is on its own. If it's a public channel, it will have a username and a telegram.me/ link (e.g. t.me/telegram) – you can post this link on social networks, advertise it in magazines, or tattoo it on your back. If you have a private channel, you can send an invite link to your friends.

+

Please do not send channel links (or other unsolicited messages) to strangers. If they report spam from your account, you may be banned from contacting other people, however good your intentions.

+

Q: What does the eye icon mean?

+

Each post in a channel has a view counter. Views from forwarded copies of your messages are also included in the total count. This way you can see how far it has spread.

+

Please note that these numbers are approximate — we don't want to keep a record for everything you've ever viewed. After a short while (around 4 days), Telegram will forget that you've seen a post and will count you again if you navigate to it. For this reason you may see several views for posts in a private channel where you are alone.

+

Q: How do I know who posted a message?

+

As the owner of the channel, you can enable admin signatures that users will see next to the view counters. These signature only mention the name of the administrator and no link to their profile.

+

If the signatures are disabled, there is no way for users to know whether a message was posted by the owner or one of the administrators.

+

Q: Are there any feedback options?

+

You can add a discussion group chat to the channel, and your subscribers will see a comment button for each post in the channel. Comments show up in a thread of their own and also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

+

You can also use bots (e.g. the @like bot) to add buttons to your posts.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/faq_spam.html b/data/telegram.org/faq_spam.html new file mode 100644 index 0000000000..a7ff571d34 --- /dev/null +++ b/data/telegram.org/faq_spam.html @@ -0,0 +1,163 @@ + + + + + Spam FAQ + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Spam FAQ

+ +
+

This FAQ is for people whose accounts were limited after being reported for spam.
Back to the main FAQ »

+
+

+
+

Q: What happened to my account?

+

When users press the ‘Report spam’ button in a chat, they forward these messages to our team of moderators for review. If the moderators decide that the messages deserved this, the account becomes limited temporarily.

+

This means that if you have been sending unwanted messages to random strangers or posting spam in groups, you lose the ability to do so.

+

Q: So I can't send messages anymore?

+

No, it's not that bad. Limited accounts can send messages to people who have their number saved as a contact. You can also always reply to anyone who messages you first.

+

Q: Why was I reported?

+

Telegram‘s username search is not a tool for making new friends. People usually don’t like it when strangers contact them — so they will report you if they find your messages annoying. Please only contact people if you're sure that they are expecting messages from you. The same applies to adding people to unwanted groups and channels. In addition to this, group admins can also report users who post spam in their groups.

+

Naturally, all such reports are also checked by human moderators. If the messages contain spam, the account will be temporarily limited.

+

Q: What can people report me for?

+

For private messages, it really doesn‘t matter what you send, as long as the receivers find it unwelcome. It could have been a photo, an invite link or a simple ’hello‘. Please only send messages when you are sure people won’t mind getting them.

+

As a general rule, people do mind getting unsolicited advertisements, links, invite links to groups or channels, random photos and, above all, anything related to commerce or online popularity. If you send them something like this, you will be blocked — and everybody else will be happy.

+

Moderators are more lenient when it comes to messages in groups, but anyone who sends spam or unsolicited advertisments will be limited.

+

Q: What do I do now?

+

If this happened to you for the first time (and you are not an industrial scale spammer), most likely your account will be limited for a few days or so. Please wait and consider that people want a peaceful time using our messenger.

+

Repeated offences will result in longer periods of being blocked. If you keep writing unwanted messages to strangers, you may lose the ability to do so forever.

+

Q: I read all of the above, and I‘m certain that I didn’t break any rules!

+

If you are sure that the limit was wrongfully applied to your account, please contact our @SpamBot.

+

Please forgive us for the inconvenience — even the best systems, algorithms and well-trained people can make mistakes sometimes.

+

Q: I know I was wrong, please release me sooner!

+

We're sorry, but this is impossible. We value the inner peace of Telegram users too much.

+

Q: I‘ve just signed up and didn’t send any messages yet, but my account is limited.

+

Some numbers may trigger an overly harsh response from our system, either due to their previous owners‘ activities or due to them being certain virtual/VOIP numbers. We’re sorry if this resulted in your account being limited for no reason.

+

If you think this is your case, please contact @SpamBot and tell it your story.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/jobs.html b/data/telegram.org/jobs.html new file mode 100644 index 0000000000..de3b038c35 --- /dev/null +++ b/data/telegram.org/jobs.html @@ -0,0 +1,156 @@ + + + + + Jobs + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Jobs

+ +

Telegram stands for freedom and perfection. It is built by a tiny team of world-renowned developers selected in multi-level contests. If you want to join the Telegram team, check out the options below.

+
+

Check out the Telegram Contests channel and our @jobs_bot for ongoing competitions and the latest news.

+
+

Content Moderator

+

Responsibilities: use a specialized interface to manually sort content according to provided guidelines.

+

Preferred qualifications: fluency in English, strong analytical skills, quick reaction, attention to detail.

+

How to apply: contact @jobs_bot and fill in the required info. If your application is accepted, the bot will share a series of test tasks.

+
+

Please submit your applications for the Content Moderator position by Monday, May 10 at 23:59 Dubai time. Applications received after that point will not be considered in this round – and will have to wait for future vacancies.

+
+

Translator

+

Responsibilities: translate app and website interfaces, blog posts, changelogs, and other text with a high level of precision on ambitious deadlines.

+

Preferred qualifications: fluency in English and a native-level fluency in another language, excellent written communication skills with a focus on detail.

+

How to apply: contact @jobs_bot and fill in the required info. If your application is accepted, the bot will share a series of test tasks.

+
+

Please submit your applications for the Translator position by Friday, May 14 at 23:59 Dubai time. Applications received after that point will likely not be considered in this round – and may have to wait for future vacancies.

+
+

C/C++ Software Engineer

+

Responsibilities: work on Telegram's custom-built low-level data storage engines distributed across several data-centers.

+

Preferred qualifications: experience working on scalable C/C++ projects and/or networking protocols, experience working with Linux, top results in programming contests.

+

How to apply: contact @jobs_bot and fill in the required info. The bot will also notify you whenever we're holding relevant coding competitions – which are the fastest and easiest way of joining the team.

+

Site Reliability Engineer

+

Responsibilities: automate routine tasks, proactively identify and solve potential reliability issues, increase fault-tolerance of Telegram's multi-datacenter infrastructure.

+

Preferred qualifications: experience administering *nix like systems, experience developing in C, Python or Perl; knowledge of bash, network protocols, and network equipment of major manufacturers.

+

How to apply: contact @jobs_bot and fill in the required info.

+

Junior Accountant

+

Responsibilities: maintain accounting books and records, ensure documentation of financial transactions, manage payrolls, prepare financial statements and reports (balance sheet, profit and loss statement, cash flow and analytics).

+

Preferred qualifications: high GMAT score, native-level fluency in English, appreciation and working knowledge of accounting principles under IFRS, experience with QuickBooks or Xero software, strong computer literacy with proficient use of Microsoft Excel.

+

How to apply: contact @jobs_bot and fill in the required info.

+

Assistant to the CEO

+

Responsibilities: manage and maintain calendar of the CEO, booking and arranging travel, transport and accommodation.

+

Preferred qualifications: high IQ score, native-level fluency in English, excellent verbal and written communications skills, accuracy and attention to detail, basic financial skills, discretion, persistence.

+

How to apply: contact @jobs_bot and fill in the required info.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/press.html b/data/telegram.org/press.html new file mode 100644 index 0000000000..207c71f716 --- /dev/null +++ b/data/telegram.org/press.html @@ -0,0 +1,194 @@ + + + + + Articles about Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+ +
+ +
+

Articles about Telegram

+ +
+

These articles cover Telegram and its sponsor, global entrepreneur Pavel Durov.
For media requests, please contact @PressBot on Telegram.

+
+

English

+ +

Español

+ +

Italiano

+ +
+

Press contacts

+

If you would like to contact us, please contact @PressBot on Telegram.

+

Telegram logos

+

If you need Telegram logos, take these. Feel free to use them for article illustrations, graphs, “forward to Telegram” buttons, etc. Just make sure people understand you're not representing Telegram officially.

+

You can find some high-quality public-domain screenshots of Telegram on this page.

+

Telegram Widgets

+

If you would like to add Telegram share buttons, comments or other widgets to your website, please see this page.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/privacy.html b/data/telegram.org/privacy.html new file mode 100644 index 0000000000..363908ba0d --- /dev/null +++ b/data/telegram.org/privacy.html @@ -0,0 +1,299 @@ + + + + + Telegram Privacy Policy + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Telegram Privacy Policy

+ +
+ +

+

1. Introduction

+

This Privacy Policy sets out how we, Telegram Messenger Inc. (“Telegram”), use and protect your personal data that you provide to us, or that is otherwise obtained or generated by us, in connection with your use of our cloud-based messaging services (the “Services”). For the purposes of this Privacy Policy, ‘we’, ‘us’ and ‘our’ refers to Telegram, and ‘you’ refers to you, the user of the Services.

+

1.1 Privacy Principles

+

Telegram has two fundamental principles when it comes to collecting and processing private data:

+
    +
  • We don't use your data to show you ads.
  • +
  • We only store the data that Telegram needs to function as a secure and feature-rich messaging service.
  • +
+

1.2. Terms of Service

+

This Privacy Policy forms part of our Terms of Service, which describes the terms under which you use our Services and which are available at https://telegram.org/tos. This Privacy Policy should therefore be read in conjunction with those terms.

+

1.3. Table of Contents

+

This Privacy Policy explains the following:

+ +

1.4. EEA Representative

+

If you live in a country in the European Economic Area (EEA), the Services are provided by Telegram, which for the purposes of applicable data protection legislation is the data controller responsible for your personal data when you use our Services. However, as Telegram is located outside the EEA, we have designated one of our EEA-based group companies, Telegram UK Holdings Ltd (71-75 Shelton Street, Covent Garden, London, England, WC2H 9JQ), as a representative to whom you may direct any issues you have relating to our processing of your personal data.

+

2. Legal Ground for Processing Your Personal Data

+

We process your personal data on the ground that such processing is necessary to further our legitimate interests (including: (1) providing effective and innovative Services to our users; and (2) to detect, prevent or otherwise address fraud or security issues in respect of our provision of Services), unless those interests are overridden by your interest or fundamental rights and freedoms that require protections of personal data.

+

3. What Personal Data We Use

+

3.1. Basic Account Data

+

Telegram is a communication service. You provide your mobile number and basic account data (which may include profile name, profile picture and about information) to create a Telegram account.

+

To make it easier for your contacts and other people to reach you and recognize who you are, the screen name you choose, your profile pictures, and your username (should you choose to set one) on Telegram are always public. We don't want to know your real name, gender, age or what you like.

+

We do not require your screen name to be your real name. Note that users who have you in their contacts will see you by the name they saved and not by your screen name. This way your mother can have the public name 'Johnny Depp' while appearing as 'Mom' to you and as 'Boss' to her underlings at work (or the other way around, depending on how these relationships are structured).

+

3.2. Your E-mail Address

+

When you enable 2-step-verification for your account or store documents using the Telegram Passport feature, you can opt to set up a password recovery email. This address will only be used to send you a password recovery code if you forget it. That's right: no marketing or “we miss you” bullshit.

+

3.3. Your Messages

+
3.3.1. Cloud Chats
+

Telegram is a cloud service. We store messages, photos, videos and documents from your cloud chats on our servers so that you can access your data from any of your devices anytime without having to rely on third-party backups. All data is stored heavily encrypted and the encryption keys in each case are stored in several other data centers in different jurisdictions. This way local engineers or physical intruders cannot get access to user data.

+
3.3.2. Secret Chats
+

Secret chats use end-to-end encryption. This means that all data is encrypted with a key that only you and the recipient know. There is no way for us or anybody else without direct access to your device to learn what content is being sent in those messages. We do not store your secret chats on our servers. We also do not keep any logs for messages in secret chats, so after a short period of time we no longer know who or when you messaged via secret chats. For the same reasons secret chats are not available in the cloud — you can only access those messages from the device they were sent to or from.

+
3.3.3. Media in Secret Chats
+

When you send photos, videos or files via secret chats, before being uploaded, each item is encrypted with a separate key, not known to the server. This key and the file’s location are then encrypted again, this time with the secret chat’s key — and sent to your recipient. They can then download and decipher the file. This means that the file is technically on one of Telegram’s servers, but it looks like a piece of random indecipherable garbage to everyone except for you and the recipient. We don’t know what this random data stands for and we have no idea which particular chat it belongs to. We periodically purge this random data from our servers to save disk space.

+
3.3.4. Public Chats
+

In addition to private messages, Telegram also supports public channels and public groups. All public chats are cloud chats (see section 3.3.1 above). Like everything on Telegram, the data you post in public communities is encrypted, both in storage and in transit — but everything you post in public will be accessible to everyone.

+
3.4. Phone Number and Contacts
+

Telegram uses phone numbers as unique identifiers so that it is easy for you to switch from SMS and other messaging apps and retain your social graph. We ask your permission before syncing your contacts.

+

We store your up-to-date contacts in order to notify you as soon as one of your contacts signs up for Telegram and to properly display names in notifications. We only need the number and name (first and last) for this to work and store no other data about your contacts.

+

Our automatic algorithms can also use anonymized sets of phone numbers to calculate the approximate number of potential contacts an unregistered phone number may have on Telegram. When you open the 'Invite friends' interface, we display the resulting statistics next to your contacts to give you an idea of who could benefit most from joining Telegram.

+

You can always stop syncing contacts or delete them from our servers in Settings > Privacy & Security > Data Settings.

+
+

If you are using Android, Telegram will ask you for permission to access your phone call logs (READ_CALL_LOG). If you grant this permission, Telegram will be able verify your account by transmitting a phone call instead of asking you to enter a code. Telegram uses this permission only to confirm receipt of the confirmation call by verifying the number in the call log.

+
+

3.5. Location Data

+

If you share a location in a chat, this location data is treated like other messages in cloud or secret chats respectively.

+

If you share your Live Location in any chat or turn on ’Make Myself Visible’ in People Nearby, Telegram will use your data to display your location to those users with whom you are sharing it, even when the app is closed – for as long as you keep these optional features activated.

+
3.6. Cookies
+

The only cookies we use are those to operate and provide our Services on the web. We do not use cookies for profiling or advertising. The cookies we use are small text files that allow us to provide and customize our Services, and in doing so provide you with an enhanced user experience. Your browser should allow you to control these cookies, including whether or not to accept them and how to remove them. You may choose to block cookies with your web browser, however, if you do disable these cookies you will not be able to log in to Telegram Web.

+

4. Keeping Your Personal Data Safe

+

4.1. Storing Data

+

If you signed up for Telegram from the UK or the EEA, your data is stored in data centers in the Netherlands. These are third-party provided data centers in which Telegram rents a designated space. However, the servers and networks that sit inside these data centers and on which your personal data is stored are owned by Telegram. As such, we do not share your personal data with such data centers. All data is stored heavily encrypted so that local Telegram engineers or physical intruders cannot get access.

+

4.2. End-to-End Encrypted Data

+

Your messages, media and files from secret chats (see section 3.3.2 above), as well as the contents of your calls and the data you store in your Telegram Passport are processed only on your device and on the device of your recipient. Before this data reaches our servers, it is encrypted with a key known only to you and the recipient. While Telegram servers will handle this end-to-end encrypted data to deliver it to the recipient – or store it in the case of Telegram Passport data, we have no ways of deciphering the actual information. In this case, we neither store nor process your personal data, rather we store and process random sequences of symbols that have no meaning without the keys which we don’t have.

+

4.3. Retention

+

Unless stated otherwise in this Privacy Policy, the personal data that you provide us will only be stored for as long as it is necessary for us to fulfill our obligations in respect of the provision of the Services.

+

5. Processing Your Personal Data

+

5.1. Our Services

+

Telegram is a cloud service. We will process your data to deliver your cloud chat history, including messages, media and files, to any devices of your choosing without a need for you to use third-party backups or cloud storage.

+

5.2. Safety and Security

+

Telegram supports massive communities which we have to police against abuse and Terms of Service violations. Telegram also has more than 400 million users which makes it a lucrative target for spammers. To improve the security of your account, as well as to prevent spam, abuse, and other violations of our Terms of Service, we may collect metadata such as your IP address, devices and Telegram apps you've used, history of username changes, etc. If collected, this metadata can be kept for 12 months maximum.

+

5.3. Spam and Abuse

+

To prevent phishing, spam and other kinds of abuse and violations of Telegram’s Terms of Service, our moderators may check messages that were reported to them by their recipients. If a spam report on a message you sent is confirmed by our moderators, your account may be limited from contacting strangers – temporarily or permanently. You can send an appeal using @Spambot. In case of more serious violations, your account may be banned. We may also use automated algorithms to analyze messages in cloud chats to stop spam and phishing.

+

5.4. Cross-Device Functionality

+

We may also store some aggregated metadata to create Telegram features (see section 5.5 below) that work across all your devices.

+

5.5. Advanced features

+

We may use some aggregated data about how you use Telegram to build useful features. For example, when you open the Search menu, Telegram displays the people you are more likely to message in a box at the top of the screen. To do this, we calculate a rating that shows which people you message frequently. A similar rating is calculated for inline bots so that the app can suggest the bots you are most likely to use in the attachment menu (or when you start a new message with “@”). To turn this feature off and delete the relevant data, go to Settings > Privacy & Security > Data Settings and disable “Suggest Frequent Contacts”.

+

5.6. No Ads Based on User Data

+

Unlike other services, we don't use your data for ad targeting or other commercial purposes. Telegram only stores the information it needs to function as a secure and feature-rich cloud service.

+

Telegram offers a tool for advertisers to promote their messages in public one-to-many channels, but these sponsored messages are based solely on the topic of the public channels in which they are shown. No user data is mined or analyzed to display ads or sponsored messages.

+

6. Bot Messages

+

6.1. Ecosystem

+

Telegram has an API that allows third-party developers to create bots. Bots are apps that look like special Telegram users: you can talk to them from your chat list, add them to groups or use a special “inline” interface to access their features. By performing any of these actions, you will be sending some of your data to the respective third-party bot developers.

+

6.2. How Bots Can Receive Data

+

You can send data to bot developers when you interact with their bots in one of these ways:

+
    +
  • By sending messages to a bot.
  • +
  • By using an inline bot.
  • +
  • By participating in a group with a bot.
  • +
  • By pressing buttons in messages sent by a bot.
  • +
  • By paying for goods and services via bots (see section 7 below).
  • +
+

6.3. What Data Bots Receive

+

In any of the above cases, the developers of an automated user (bot) can get your public account data (see section 3.1 above): your screen name, username and profile picture(s).

+

Bots can also receive the following data when you interact with them.

+
    +
  • Bots will obviously get your messages when you send them something.
  • +
  • If you click on links or buttons provided by the bot, the bot can potentially get your IP address (provided that it controls the website to which the link leads).
  • +
  • If the bot is a member of the same group with you, it may know you are a member.
  • +
  • When you start your message with the username of an inline bot (e.g. @gif) the interface transforms so that everything you type becomes a query to that bot. This query is sent to the bot so that it can provide its service. We will warn you about this the first time you use an inline bot.
  • +
  • Bots added to groups can operate in two modes: with access to messages in the group or without access. If the bot has access to messages, it can see everything that happens in the group. The interface clearly shows whether or not a bot has access to messages in groups.
  • +
+

6.4. Bots Are Not Maintained by Telegram

+

Other than our own bots, no other bots or third-party bot developers are affiliated with Telegram. They are completely independent from us. They should ask you for your permission before they access your data or you make it available to them.

+ + +

7. Third Party Payment Services

+

7.1. Payment Information

+

The Payment Platform for Bots is available to users as of Telegram 4.0. Telegram does not process payments from users and instead relies on different payment providers around the world. It is the payment providers that handle and store your credit card details. Neither Telegram nor the merchants on the platform (bot developers) have access to this information. Although we work with payment providers they are completely independent from Telegram. Please study their relevant privacy policies before making your data available to them.

+

7.2. Credit Card Information

+

When making a purchase, you enter your credit card details into a form supplied by the payment provider that will be processing the payment, and this information goes directly to the payment provider's server. Your credit card information never reaches Telegram's servers. We do not access and do not store your credit card information. When you save your credit card info, it is saved on the respective payment provider's servers and the payment provider gives Telegram a token that you can reuse for future payments. It is not possible to reconstruct your credit card info from the token.

+

7.3 Shipping Information

+

When you enter shipping information in the process of placing an order, we send it directly to the merchant bot developer. We can store your shipping information for you if you choose to save it for future purchases. We will delete this information immediately if you ask us to.

+

7.4. Clearing Payment Information

+

You can clear all payment information associated with your account at any time by going to Telegram Settings > Privacy & Security > Data Settings and selecting ‘Clear Payment & Shipping Info’. If you choose to remove your payment information, we will delete your stored shipping info and payment tokens from all providers and ask the payment providers to remove your credit card information that they store.

+

7.5. Payment Disputes

+

Due to the fact that Telegram doesn't store any credit card details or transaction information, it is impossible for us to handle complaints or cashbacks – any disputed payments are the responsibility of the bot developers, payment providers, and banks that participated in the exchange.

+

8. Who Your Personal Data May Be Shared With

+

8.1. Other Telegram Users

+

Other users of our Services with whom you choose to communicate with and share certain information, who may be located outside the EEA. Note that by entering into the Terms of Service and choosing to communicate with such other users of Telegram, you are instructing us to transfer your personal data, on your behalf, to those users in accordance with this Privacy Policy. We employ all appropriate technical and organizational measures (including encryption of your personal data) to ensure a level of security for your personal data that is appropriate to the risk.

+

8.2. Telegram’s Group Companies

+

We may share your personal data with: (1) our parent company, Telegram Group Inc, located in the British Virgin Islands; and (2) Telegram FZ-LLC, a group member located in Dubai, to help provide, improve and support our Services. We will implement appropriate safeguards to protect the security and integrity of that personal data. This will take the form of standard contract clauses approved by the European Commission in an agreement between us and our relevant group companies. If you would like more information regarding these clauses, please contact us using the details in section 12 below.

+

8.3. Law Enforcement Authorities

+

If Telegram receives a court order that confirms you're a terror suspect, we may disclose your IP address and phone number to the relevant authorities. So far, this has never happened. When it does, we will include it in a semiannual transparency report published at: https://t.me/transparency.

+

9. Your Rights Regarding the Personal Data You Provide to Us

+

9.1. Your Rights

+

Under applicable data protection legislation, in certain circumstances, you have rights concerning your personal data. You have a right to: (1) request a copy of all your personal data that we store and to transmit that copy to another data controller; (2) delete (see section 10 below) or amend your personal data; (3) restrict, or object to, the processing of your personal data; (4) correct any inaccurate or incomplete personal data we hold on you; and (5) lodge a complaint with national data protection authorities regarding our processing of your personal data.

+

9.2. Exercising Your Rights

+

If you wish to exercise any of these rights, kindly contact us using the details in section 12 below.

+

9.3. Data Settings

+

You can control how your data is used (e.g., delete synced contacts) in Settings > Privacy & Security > Data Settings (using one of our mobile apps).

+

Sadly, if you're not OK with Telegram's modest minimum requirements, it won't be possible for us to provide you with our Services. You can delete your Telegram account by proceeding to the deactivation page.

+

10. Deleting data

+

10.1. Accounts

+

If you would like to delete your account, you can do this on the deactivation page. Deleting your account removes all messages, media, contacts and every other piece of data you store in the Telegram cloud. This action must be confirmed via your Telegram account and cannot be undone.

+

10.2. Messages

+
    +
  • In secret chats, deleting a message always instructs the app on the other end to delete it too.
  • +
  • In cloud chats, you can choose to delete a message for all participants within at least 48 hours after sending. Otherwise, deleting a message will delete it from your message history. This means that a copy will stay on the server as part of your partner's message history. As soon as your partner deletes it too, it's gone forever.
  • +
  • As of version 5.5, any party can choose to delete any messages in one-on-one chats, both sent and received, for both sides. There is no time limit. Any party can also opt to clear the entire chat history for both parties, in which case the apps will be instructed to remove all messages in that chat, however many of them are still retained by either of the participants.
  • +
  • In supergroups and channels, deleting a message removes it for all participants. Note that deleted messages and original versions of edited messages from supergroups are stored for 48 hours after deletion in order to be shown in the admins log.
  • +
+

10.3. Self-Destructing Messages

+

Messages in Secret Chats can be ordered to self-destruct. As soon as such a message is read (2 checks appear), the countdown starts. When the timer expires, both devices participating in a secret chat are instructed to delete the message (photo, video, etc.). Media with short timers (less than a minute) are shown with blurred previews. The timer is triggered when they are viewed.

+

10.4. Account Self-Destruction

+

By default, if you stop using Telegram and do not come online for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can go to Settings to change the exact period after which your inactive account will self-destruct.

+

11. Changes to this Privacy Policy

+

We will review and may update this Privacy Policy from time to time. Any changes to this Privacy Policy will become effective when we post the revised Privacy Policy on this page www.telegram.org/privacy. Please check our website frequently to see any updates or changes to our Privacy Policy, a summary of which we will set out below.

+

March 25, 2019

+
    +
  • Expanded [10.2. Deleting Messages] with data on the new features in version 5.5, which allow both participants to remove any messages from one-on-one chats for both sides without a time limit.
  • +
+

March 24, 2021

+ +

October 26, 2021

+ +

Important changes made to this Privacy Policy will be notified to you via Telegram.

+

12. Questions and concerns

+

If you have any questions about privacy and our data policies, please contact our @GDPRbot. Use the /access command to learn how to get a copy of your Telegram data and use the /contact command to leave a request, which we will answer at the earliest opportunity.

+

Telegram is an open source project. You can examine more information on our:

+ +
+

This policy has been expanded on August 14, 2018 to add information required by the EU data protection law.

+
+ +
+ +
+
+
+ + + + + + + + + diff --git a/data/telegram.org/privacy/gmailbot.html b/data/telegram.org/privacy/gmailbot.html new file mode 100644 index 0000000000..e7fec71326 --- /dev/null +++ b/data/telegram.org/privacy/gmailbot.html @@ -0,0 +1,161 @@ + + + + + Telegram GmailBot Privacy Policy + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Telegram GmailBot Privacy Policy

+ +
+ +

1. Introduction

+

This Privacy Policy sets out how we, Telegram Messenger Inc. (“Telegram”), use and protect your personal data that you provide to us, or that is otherwise obtained or generated by us, in connection with your use of our @GmailBot Bot (the Bot). For the purposes of this Privacy Policy, ‘we’, ‘us’ and ‘our’ refers to Telegram, and ‘you’ refers to you, the user of the Services.

+

The Bot is a part of the Telegram Bot Ecosystem. For more information on Telegram messaging services please refer to Telegram Privacy Policy.

+

The Bot's use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

+

Gmail and the Gmail logo are registered trademarks of Google LLC.

+

1.1 Privacy Principles

+

Telegram has two fundamental principles when it comes to collecting and processing private data:

+
    +
  • We don't use your data to show you ads.
  • +
  • We only store the data that Telegram needs to function as a secure and feature-rich messaging service.
  • +
+

1.2. EEA Representative

+

If you live in a country in the European Economic Area (EEA), the Services are provided by Telegram, which for the purposes of applicable data protection legislation is the data controller responsible for your personal data when you use our Services. However, as Telegram is located outside the EEA, we have designated one of our EEA-based group companies, Telegram UK Holdings Ltd (71-75 Shelton Street, Covent Garden, London, England, WC2H 9JQ), as a representative to whom you may direct any issues you have relating to our processing of your personal data.

+

2. Legal Ground for Processing Your Personal Data

+

We process your personal data on the ground that such processing is necessary to further our legitimate interests (including: (1) providing effective and innovative Services to our users; and (2) to detect, prevent or otherwise address fraud or security issues in respect of our provision of Services), unless those interests are overridden by your interest or fundamental rights and freedoms that require protections of personal data.

+

3. What Personal Data We Use

+

3.1. Basic Telegram Data

+

The Bot is available only via the Telegram communication service. Please refer to Telegram Privacy Policy regarding basic Telegram account data.

+

3.2. Gmail Data

+

The Bot requests your permission to access your Gmail Data via OAuth. After you accept the request, we use the Google API to receive your new emails and notify you about them in Telegram. You can reply to those emails, forward, archive and delete them as well as create and send new emails, right from Telegram. In order to provide these features, we store your Gmail API token, your notification preferences and your Gmail screen name. We also store the cache of your incoming messages for the previous 7 days for you to be able to reply to these messages via Telegram; all such cached data older than one week is cleared automatically.

+

4. Keeping Your Personal Data Safe

+

4.1. Storing Data

+

The data related to the Bot is stored separately from the main Telegram Data, in data centers in Germany. These are third-party provided data centers in which Telegram rents a designated space. We do not share your personal data with such data centers.

+

4.2. Retention

+

Unless stated otherwise in this Privacy Policy, the personal data that you provide us will only be stored for as long as it is necessary for us to fulfill our obligations in respect of the provision of the Services.

+

5. Who Your Personal Data May Be Shared With

+

5.1. Telegram’s Group Companies

+

We may share your personal data with: (1) our parent company, Telegram Group Inc, located in the British Virgin Islands; and (2) Telegram FZ-LLC, a group member located in Dubai, to help provide, improve and support our Services. We will implement appropriate safeguards to protect the security and integrity of that personal data. This will take the form of standard contract clauses approved by the European Commission in an agreement between us and our relevant group companies.

+

6. Deleting data

+

If you no longer want to use the Bot, send the /resetbot command to the Bot. You will stop receiving notifications and we will revoke our permission to access your Gmail Data. You can also revoke our permissions to your Gmail account manually here: https://myaccount.google.com/permissions. After the permission is revoked, we will remove all your Gmail data from our servers within 30 days.

+

7. Changes to this Privacy Policy

+

We will review and may update this Privacy Policy from time to time. Any changes to this Privacy Policy will become effective when we post the revised Privacy Policy on this page www.telegram.org/privacy/gmailbot. Please check our website frequently to see any updates or changes to our Privacy Policy, a summary of which we will set out below.

+

Important changes made to this Privacy Policy will be notified to you via Telegram.

+
+ +
+ +
+
+
+ + + + + + + + + diff --git a/data/telegram.org/support.html b/data/telegram.org/support.html new file mode 100644 index 0000000000..6c587013fd --- /dev/null +++ b/data/telegram.org/support.html @@ -0,0 +1,141 @@ + + + + + Telegram support + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Support

+ +
+
+ + +
+
+ + +
+
+ + +
+
+ +
+
+ +
+
+
+
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/teststore.html b/data/telegram.org/teststore.html new file mode 100644 index 0000000000..710beff8d0 --- /dev/null +++ b/data/telegram.org/teststore.html @@ -0,0 +1,283 @@ + + + + + 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/tos.html b/data/telegram.org/tos.html new file mode 100644 index 0000000000..d7b9244bfd --- /dev/null +++ b/data/telegram.org/tos.html @@ -0,0 +1,133 @@ + + + + + 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.html b/data/telegram.org/tour.html new file mode 100644 index 0000000000..1b9a1c6de3 --- /dev/null +++ b/data/telegram.org/tour.html @@ -0,0 +1,144 @@ + + + + + Telegram Tour + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + diff --git a/data/telegram.org/tour/channels.html b/data/telegram.org/tour/channels.html new file mode 100644 index 0000000000..a03cc25dcd --- /dev/null +++ b/data/telegram.org/tour/channels.html @@ -0,0 +1,294 @@ + + + + + Telegram Channels + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Channels

+ +
+ +
+ +

Channels are a tool for broadcasting your public messages to large audiences. They offer a unique opportunity to reach people directly, sending a notification to their phones with each post.

+

Telegram Channels can have an unlimited amount of subscribers, and only admins have the right to post. Unlike Telegram Groups, channels show the name and photo of the channel next to messages – instead of the person who posted them.

+
+ +
+ +

Media organizations and public figures use channels to stay in touch with their readers, voters and fans. For some real-life examples, check out @Bloomberg, the Coronavirus Info channel, or join the official @Telegram channel covering our updates.

+

To create your own channel, open the “New Message” menu on Telegram and choose “New Channel”. Newly created channels start as private – but you can edit their profile to make them public.

+

The contents of public channels can be seen on the Web without a Telegram account and are indexed by search engines. For example, try t.me/s/FinancialTimes.

+

Autoplaying Videos and Rich Media

+

Channels aren't just for text messages and links – Telegram supports a wide range of content types, from autoplaying videos to animated stickers, polls and beyond.

+

Videos will start playing automatically with no sound. Pressing the volume buttons on the device unmutes the video, tapping on it launches the video from the beginning in full screen mode.

+
+ TITLE +
+ +

Several photos sent together will form an album with a beautiful layout – and only result in one notification to your subscribers for the whole batch.

+
+ TITLE +
+ +

You can send large files of any type and uncompressed images in full resolution – useful for content like infographics.

+
+ TITLE +
+ +

Podcasts also get special treatment. Telegram apps remember your last position when resuming playback of long audio files. Users who are in a hurry can listen to them at 2x speed:

+
+ Screenshot showing the location of the 2x playback button for long audio files. +
+ + +

Quick Sharing

+

Each post in a channel has a handy Share Button next to it, making it easy for your subscribers to forward things to others – or save them in their Saved Messages.

+
+ TITLE +
+ +

The Quick Share menu also shows a direct link to your post. Following such links inside Telegram opens the channel and highlights the message. If the user doesn't have Telegram, they will see a web page with an embedded post, like this: t.me/corona/16.

+

Powerful Polls

+

You can use polls to judge public opinion, make decisions and help your audience connect with you.

+
+ A poll that shows who voted for which option +
+ +

Quiz-Style Polls

+

To make things more fun – or add extra educational value to your posts 🧐 – use quiz-style polls that have one correct answer.

+
+ TITLE +
+ +

Discussion Groups

+

If you'd like to know what people think about the posts they view, you can set up a discussion group for your channel. New posts from the channel will be automatically forwarded to the group and pinned there.

+

Subscribers will see a comment button for each post in the channel. Comments show up in a thread of their own and also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

+
+ +
+ +

View Counters

+

Each post in a channel has a view counter. Views from forwarded copies of the messages are included in the total count.

+
+ TITLE +
+ +

Detailed Statistics

+

Advanced statistics are available for channels with more than 500 subscribers. You can view beautifully-detailed graphs about its growth and the performance of its posts.

+
+ +
+ +

You can track how many users join, leave and mute your channel, what languages they speak, how they interact with your posts, and how they found your channel – from Telegram search, by following a link, etc.

+

Scheduled and Silent Messages

+

You can plan your posts ahead and let them go live automatically at a specified time. For late night or non-urgent updates, you can send silent messages that will result in a notification with no sound for your subscribers.

+

Hold the “Send” button for extra sending options:

+
+ TITLE +
+ +

Pinned Messages

+

You can pin a message for extra visibility.

+
+ TITLE +
+ +

Hashtags

+

Telegram supports hashtags – tapping on a hashtag in a message will show a search interface with all other tagged posts in the channel. This is useful for adding a layer of navigation for your channel and improving visibility of your older posts.

+
+ TITLE +
+ +

Subscriber Privacy

+

The subscriber list is only visible to the channel owner and admins. Subscribers cannot see who else has signed up – nor can they see which accounts are managing the channel.

+

Extra Admins

+

You can appoint additional admins to help you manage the channel and define their role with granular precision. Choose who will be able to add new subscribers, manage messages, edit channel info, or even add new admins.

+

Admin Signatures

+

There are times when it's important to know who posted a certain message. For that, you can enable signatures in Channel Info. New messages will be signed with the posting admin's chosen screen name but will not link to their profile.

+
+ TITLE +
+ +

Embedded Messages

+

Messages from public channels can be easily embedded in any web page using Telegram Widgets.

+

+ +

+
+ + +

Editing Messages

+

Made a typo? Missed a word? Itching to add something? You can easily edit your messages in channels, regardless of how long ago they were posted. Tap the message (double tap or long tap on iOS), then press 'Edit'.

+

Deleting Messages

+

If you'd like to do a bit of timeline maintenance, you can delete any message at any time, for everyone. Deleted messages will vanish from the feed, for both new and old subscribers.

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/tour/groups.html b/data/telegram.org/tour/groups.html new file mode 100644 index 0000000000..0146fa91b5 --- /dev/null +++ b/data/telegram.org/tour/groups.html @@ -0,0 +1,266 @@ + + + + + Group Chats on Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Group Chats on Telegram

+ +
+
+ +
+

Telegram groups are a powerful tool for building communities and can support up to 200,000 members each.

+
+

Friends and families use groups to share photos and plans, teams and businesses to coordinate their work, massive ICOs to answer questions and keep in touch with their investors. Telegram has many features that make communication in groups easy no matter their size or purpose.

+

Replies

+

To reply to a specific message in a group chat, simply swipe left on it, type your text and hit ‘Send’. If you tap on the quote in a message that is a reply, the app scrolls up to the original message – and shows an arrow button to go back to the previous location. This makes navigating conversations in groups easy even if you've been away for a while.

+

The person you replied to will be notified about your message even if they muted the group chat — their notification settings for you personally apply in this case.

+

Mentions

+

If you want several people within a group chat to get instantly involved in the conversation, you may mention them in a message. They will be notified about your message, even if they muted the group chat — unless they've muted you personally, of course!

+

Reply/Mention alerts

+

In busy groups, you can get new mentions or replies many times during a day – and it’s important not to miss those messages. So whenever this happens, you’ll notice straight away by the ‘@’ badge in the chat list:

+
+
+ +
+
+ +

When you have new replies/mentions in a group, you can instantly reach them by tapping the new ‘@’ button when inside the chat. This button will disappear once you’ve read all the relevant messages (you can also use a long tap on the button to quickly mark them as read).

+

Supersize that

+

Groups are ideal for sharing stuff with friends and family or collaboration in small teams. But they can also host very large communities – in fact, up to to 200,000 members can join any group. We have plenty of admin tools to help admins keep the peace in these virtual cities.

+
+

Hint: If you're doing something massively popular, consider creating a channel. Channels are a tool for broadcasting public messages to large audiences, and can have an unlimited number of subscribers.

+
+

Pinned Messages

+

Group admins can inform all members about important news using pinned messages that are displayed at the top of the chat screen. All members will get a notification — even if they muted ordinary messages from the group.

+
+ +

A pinned message

+
+ +

Groups admins can always edit pinned messages. This means your pinned message can contain an up to date list of links to important messages or other channels and groups.

+ + +

Invite Links

+

It's easy to move your existing group chats to Telegram without any hassle. Simply send your friends an invite link. As soon as they get Telegram, they can instantly join your Telegram group just by following that link.

+

To get the link, first create a group on Telegram, then head to the ‘Add participant…’ section and tap ‘Invite to Group via Link’.

+
+ + + +
+
+ +

Public groups

+

If you want a friendlier-looking link, groups can become public and get a short link, like t.me/publictestgroup. This way, anybody can view the group's entire chat history and join to post messages.

+
+ +

A public group

+
+ +

Message links

+

You can copy links to individual messages inside public groups. Anyone will be able to see them by opening their t.me link – no Telegram account required. Tweet with confidence!

+

Better With Bots

+

Bots further extend the potential power of groups, making anything possible – from automated moderation to games, payments and beyond.

+

Admin Tools

+

To help maintain order in your community, you can add admins with specific sets of privileges. Choose who among your trusted admins will be able to add new users, manage messages, block members, edit group info, or even add new admins.

+
+ +

Admin rights

+
+ +

Partial Bans

+

Admins who don’t want to completely ban members from their groups can partially restrict their rights in order to stop behavior that's causing problems. You can put nasty users into read-only mode or maybe stop them from sending stickers or media for a certain period of time. You can do all of this with absolute precision:

+
+ +

Partial bans

+
+ +

Even robots can get in on the fun. With Bot API version 3.1, you can use admin bots to automatically impose temporary or permanent bans based on member actions. Check out the docs here to start building your robotic police force today.

+

Recent Admin Actions

+

When multiple admins are working with one group, it’s easy to get confused about which admin did what and when (or which admin bot has gone Skynet on your members). That’s why we've added a “Recent Actions” section to the admins page. This section stores a log of all service actions taken in the group in the last 48 hours and is visible to admins only.

+
+
+ +

Recent admin actions

+
+
+ +

Precise filters

+
+ +

Recent actions in groups also show messages that were deleted in the last 48 hours and the original versions of edited messages for the same period, so nasty behavior like self-deleted spam will no longer help anyone escape the admins’ wrath.

+

Stickers of the Group

+

Large groups with 100 members and more can choose an official sticker set for all the members of the group to see and use while they're chatting in the group — without the need of adding it to their panels.

+
+ +

Group Stickers

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/what-can-you-do-with-Telegram.html b/data/telegram.org/what-can-you-do-with-Telegram.html new file mode 100644 index 0000000000..710beff8d0 --- /dev/null +++ b/data/telegram.org/what-can-you-do-with-Telegram.html @@ -0,0 +1,283 @@ + + + + + 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/themes.telegram.org/auth.html b/data/themes.telegram.org/auth.html new file mode 100644 index 0000000000..8c95fff6af --- /dev/null +++ b/data/themes.telegram.org/auth.html @@ -0,0 +1,163 @@ + + + + + Telegram Themes + + + + + + + + + + + + + + + + + + + +
+ +
+ Don't have Telegram yet? Try it now + +
+
+
+

Telegram Theme Editor

+

The online theme editor allows you to create and modify your existing cloud themes for every platform. Any changes will appear in the apps immediately after you save them.

+ +
+
+ + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en.html b/data/translations.telegram.org/en.html new file mode 100644 index 0000000000..0467b4d659 --- /dev/null +++ b/data/translations.telegram.org/en.html @@ -0,0 +1,335 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+
+

+ English (English) + +

+
+ +
+
+

DiscussionsNEW

+

+ Feel free to join the discussion of this language pack. + View Discussion +

+
+
+

Sharing LinkNEW

+

+ Anyone can switch their Telegram interface to English by following this link: +

+ +
+
+

Actions

+ +
+
+
+ +
English
+
English
+
Please open this link on a desktop to help translate Telegram into English:
+ + +
Feel free to join the discussion of this language pack.
+
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en/ios.html b/data/translations.telegram.org/en/ios.html new file mode 100644 index 0000000000..c5419a2ccf --- /dev/null +++ b/data/translations.telegram.org/en/ios.html @@ -0,0 +1,390 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+

+ iOS5114 + +

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en/macos.html b/data/translations.telegram.org/en/macos.html new file mode 100644 index 0000000000..a1d8d10afa --- /dev/null +++ b/data/translations.telegram.org/en/macos.html @@ -0,0 +1,390 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+

+ macOS3695 + +

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/auth.html b/data/tsf.telegram.org/auth.html new file mode 100644 index 0000000000..f0138823b5 --- /dev/null +++ b/data/tsf.telegram.org/auth.html @@ -0,0 +1,241 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+

Telegram Support Initiative

+ +

Our users ask us tens of thousands of questions each day. We would like to answer them all — and we are looking for brilliant people from all over the world who would like to help us do this. If you are interested in joining us, please read this Telegram Support Force Manifesto — and don't miss the tiny FAQ below.

+
+ +
+ +

Harnessing the power of procrastination

+
    +
  1. Telegram is a free messaging system that is used by tens of millions of people daily. Each of our apps has an ‘Ask a question’ button. Our users press it thousands of times each day: some have questions, others just want to chat, still others are bored trolls. We think that they all deserve an answer of some kind.

    +
  2. +
  3. Robots and algorithms are good at handing out answers at scale, but they sometimes cause frustration, fundamentally lack human touch and are bad conversation partners. FAQs are a remedy for the select few that enjoy finding answers in FAQs. To be happy, humanity requires human answers.

    +
  4. +
  5. Manually answering tens of thousands of questions daily requires considerable resources. Manually answering them in style — even when assisted by algorithms and templates — requires limitless resources. But, the resources in question being humans and time, the modern world happens to have a limitless source of just such energy.

    +
  6. +
  7. This world is full of bright-minded, elegant, downright wonderful people who, like you and me, sometimes just can't get started with whatever they were supposed to be doing. And procrastinate instead. This brings countless people in any profession to hours and hours of unnecessary house-cleaning, dog-walking and web-surfing every day. Millions of hours go to waste — procrastination is as ubiquitous in the XXI century as are people who do their work behind computer screens.

    +
  8. +
  9. It is our goal to harness the power of procrastination. For user support, we rely on an army of volunteers from all over the world. They donate a fraction of their time to answer a few questions from Telegram users — every now and then, or all the time. We call this the Telegram Support Force and you are welcome to join.

    +
  10. +
  11. Answering questions may be devilishly tricky at times, so we couldn't accept everyone even if we wanted to. The Telegram Support Force needs patient, inquisitive people, who are no strangers to elegance, humor and style. Although Telegram volunteers help people from their own countries, proficiency in English is also a requirement, since the data you will be getting from us, as well as pretty much all communication inside the team, will be in English.

    +
  12. +
  13. We believe in support as an art form. Support should be fun — for people on both ends of the line. So we are looking for perfect, human and precise answers to the world's questions. Something to make them smile and to make you proud.

    +
  14. +
+

If this is something you might be interested in doing, don't hesitate to contact our @TelegramAuditions account. Please write us a few phrases in English describing how your favourite feature works (don’t copy it, let it be your hand-made text). Include a picture of a marmot if you want a better chance at convincing us that you actually read all of the above and below and, therefore, are inquisitive enough.

+

Markus Ra
@Telegram

+
+

Manifesto FAQ

+

Q: Do I need to know anything special to be eligible?

+

No, not really. But you do need to know how to learn things. And be inquisitive enough to want to learn them.

+

Q: What else is required?

+

We‘re looking for perfectionists. It’d also be nice if you loved your language and had at least a moderate affection for the people of Earth. It'd be cool if you like to read and write. And then, patience and understanding are very useful at times.

+

Q: Will the people I answer know who I am or get my number?

+

No, they will not. Unless you choose to tell them for some mysterious reason.

+

Q: What should I say when I contact you?

+

We'd love to know more about you (who you are, what you think, what you like — not a CV, no!), the languages you speak and the devices you use (mobile, desktop OS).

+

Q: How long does it take for you to reply?

+

We try not to take too long. But we sometimes do, so we apologize in advance. Sorry. Don‘t lose heart and remember that thing about patience above. We’ll get back to you as soon as we can.

+

Q: Is that thing about sending a marmot picture a joke?

+

No.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals.html b/data/tsf.telegram.org/manuals.html new file mode 100644 index 0000000000..1344cba84d --- /dev/null +++ b/data/tsf.telegram.org/manuals.html @@ -0,0 +1,224 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Manuals

+ +

These manuals are intended for volunteers of the TSF, but anyone else is free to take a look as well.

+

Telegram Support BIOS

+

A meta-text and mother of all answers.

+

Answering Questions (TSF-AQ)

+

Covers important topics ranging from our goals to what you do when the user says 'fuck you!'

+

Handling Bugs and Troubleshooting (TSF-BT)

+

Covers investigating, reporting and following up bugs, troubleshooting common issues, reporting tips.

+

Bug Hunting Algorithm (TSF-BHA)

+

An in-depth guide to investigating issues.

+

Feature Philosophy (TSF-FF)

+

A general text to help you understand our reasoning when contemplating new features.

+

Leaving and Coming Back (TSF-OFF)

+

When you realise you're no longer with us.

+

Bug Herding Explained (TSF-BHDE)

+

An advanced manual on handling bugs like a pro.

+

Basic FAQ on End-to-End Encryption (TSF-E2E)

+
+

Public docs

+
Telegram Support Force Manifesto (TSFM)
+

Contains general info on what we do and how to join us.

+
Translating Telegram (TTM)
+

A style guide and manifesto for Telegram translators.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/answering_questions.html b/data/tsf.telegram.org/manuals/answering_questions.html new file mode 100644 index 0000000000..eb6578c289 --- /dev/null +++ b/data/tsf.telegram.org/manuals/answering_questions.html @@ -0,0 +1,265 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Answering Questions

+ +

We answer questions. This document holds general ideas on how to handle them.
This was intended for volunteers of the Telegram Support Force, but anyone else is free to take a look as well.

+

General

+
    +
  1. Our goal is to bring human support to human beings. To achieve this goal, we rely on volunteers. Your pay is perfection in what you do, so be cool.

    +
  2. +
  3. Corporate support standards do not apply here. Treat people in a kind, personal, informal manner. No need to pretend to be something you are not (unless you're a dog in disguise — keep human appearances in this case).

    +
  4. +
  5. Never lie to people.

    +
  6. +
  7. Check everything before you reply. Things change or may no longer work the way you remember. This includes interface details, links (!) and, well, everything.

    +
  8. +
  9. Support is a form of Art, so be fun and creative.

    +
  10. +
+

The result

+

As support volunteers, we need to provide a solution for the user. Remember, that this doesn't always have to be the solution the user was asking for. So first, we want to understand the problem that drove them to ask the question. And then find a way of solving — completely or partially — that problem.

+

For example, some users ask us for an option to send sketches or drawings to their friends. While this is not possible directly, one could take a photo with their thumb on the camera (to get a black picture), then use the drawing tools built into the photo editor to make their doodle.

+

This isn‘t what the user was looking for, but it solves the problem — and it is even more flexible and customizable than the original idea (since you could also add stickers and emoji out of the box). Some solutions are less elegant. For example, right now you can’t email your Telegram conversations. While there is much less need to do so, since you can access everything in the cloud from any of your devices, this may be a problem in some cases. What one could do then, is open the conversation in Telegram Web (or any other desktop client), select multiple messages with the mouse, then copy and paste them into a text document. Any solution is better than no solution at all.

+

There will be cases, when it is not possible to solve the problem at all. As a user in this situation, I want that people on the other end of the line understand me and care about the whole thing. Therefore, two things become important:

+
    +
  • Make it clear that you understand the issue. ‘No, you can’t do that‘ is not a good answer. ’No, I‘m afraid it is not possible to make Telegram wash your dishes in a fast and securely encrypted way’ — is better.
  • +
  • Be gentle. Gentle doesn‘t mean soft — if we really can’t do something, it means just that — we can‘t. But adding ’Sorry about that' helps a lot.
  • +
+

Lastly, whatever the outcome, I always look for help from a human being, not a dumb interface. When you're casual and witty, the user feels more at ease. On the other hand, human beings, as opposed to dumb interfaces, usually understand what is appropriate in which situation. For example, when a user is in distress, he most likely needs help first — and jokes can wait until the crisis has been dealt with.

+
+

To sum up, we need to be: smart (to identify the problem and find an approach to the user), inventive (to find a solution, not always the obvious one), compassionate (in case there is no immediate solution) — and witty (otherwise it gets boring). I'm sure we are.

+

What if I don't know the answer

+

Happens to all. Don't worry, you can always find one. The TSF BIOS will tell you what to do in most situations. In case it doesn‘t or you’re not sure, ask your fellow volunteers in the group — they should know. If worst comes to worst, consult Markus.

+

Admitting you don't know something is infinitely better than trying to cover it up. So when cornered use this mantra: ‘I’m afraid I don‘t know this. Will ask my teammates and get back to you’. Just make sure that the question is not in the FAQs before you say this.

+

Handling user suggestions

+

The three rules for requests and suggestions are: don‘t lie, don’t promise anything, and don't give an exact timeframe.

+
    +
  • The internal Suggestions board on Trello has a list of most frequently suggested features together with estimations on how likely, when and why they will be introduced.
  • +
  • For insights into the decision making process, check our Feature Philosophy.
  • +
+

Plans change frequently, so it‘s best if we only talk about things that exist. Never say that something will be done. ’We may do this‘, ’we will definitely add this at some point in the future‘ or ’this is coming soon' — is as far as we can go.

+

Same applies to the negative: never say we will never do something (except steal users‘ spouses and enslave their children, as mentioned in the general FAQ). The worst thing that can happen is ’we are currently not working on this‘, ’we may consider this', etc.

+

Even if you know something is happening tomorrow, say ‘in the next few days’. People love it when they get things earlier than they expected — and get downright angry if we get 5 minutes (or a few months) late.

+

Reporting bugs in Telegram

+

Every now and then you will get actual bug-reports. We have an internal board on trello, so you will be able to search all known issues and get the relevant info.

+
    +
  • The Handling Bugs manual covers all you need to know about bug reporting in Telegram.
  • +
  • The internal Issues board on Trello lists all known issues.
  • +
+

If you are not part of the team and are looking for advanced troubleshooting tips, you may find the Troubleshooting section interesting.

+

Chatting

+

Truth is, most users come to simply say ‘hello’. Hello them back if you have the time. Sometimes these users do have a question after all. In other cases they may be new to Telegram, without many friends to chat with or show them around. So you can tell them more about Telegram, point to interesting features — or even other Telegram apps. No need to advertise, just explain what needs explaining.

+

Remember: we’re here to help those we can help and talk to others that we feel we have the time to talk to, but not more. If kids get too insistent without any real needs, it’s ok to ignore them after a few replies. If somebody seems to be a nice conversation partner, it’s always a good idea to discuss Telegram, see what the user thinks is missing. Maybe tell them about our Support Initiative.

+

Real-life problems

+

Unfortunately, we cannot really help people with real-life problems. A few kind words wouldn‘t hurt, but generally we should send those users to places where they can get actual help, like a crisis line or chat. (Now, if you want to be a member of the TSF and read this far, go send a picture of a kangaroo to the auditions account. No, this is not a joke. It is a test that helps us understand whether or not you actually read this. And don’t tell others. If you're already a member, you know what to do: humpa viceroy squid)

+

Insults

+

Yep, everyone gets their share of those. First of all, remember that these people are not really talking to you. They just see an abstract ‘Telegram’ entity. My advice is to humor them — I usually send a ‘well, that escalated quickly’ picture and it helps many users. Joke around with them and you’ll be surprised how that can humble people. And never insult back, even if they manage to get you angry for some reason. Nonviolent irony is always your best — and only — weapon.

+
+
Other TSF documents:
+

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/bios.html b/data/tsf.telegram.org/manuals/bios.html new file mode 100644 index 0000000000..1a1fb07614 --- /dev/null +++ b/data/tsf.telegram.org/manuals/bios.html @@ -0,0 +1,331 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

TSF BIOS

+ +
+ +
+

This page will help you navigate our docs and interfaces in any situation.
It will only be of interest to TSF members. Here's how you become one.

+
+

1. Getting started

+

Answering Questions is our constitution. Come back to it anytime you're in doubt.

+
    +
  1. Our creed and goals
  2. +
  3. I don't know the answer
  4. +
  5. User wants to chat
  6. +
  7. User has real life problems
  8. +
  9. User is insulting me
  10. +
+

The TSupport client is your rifle.
Learn all its features, and use an up to date template file.

+

1a. Asking teammates for help

+

Never hesitate to ask for help in your local TSF group. But remember: Not everyone in your group uses the same support account and speaks the same languages as you. When you want to ask something:

+
    +
  1. Write a summary of the user's question in one message (don't copy-paste, be brief)
  2. +
  3. Always use English (there are team members in your group who don't speak your language)
  4. +
  5. Always include the entire footer from the question (all hashtags)
  6. +
+

1b. Coming back from the dead

+

If you notice that you haven't answered any questions lately, go read the Coming and Going manual.

+

2. Tracing your progress

+

You can check our TSF Panel to see your stats and how you compare against other TSF members. You can also add a little TSF Bio in the panel, so that others know more about you, what you like, what you do, what devices you have and what languages you can speak.

+

3. Basic questions

+

You should be able to handle these easily. Here's where you find information:

+
    +
  1. FAQ
  2. +
  3. Tips & Tricks Trello
  4. +
  5. App comparison table
  6. +
  7. Screenshots (wiki)
  8. +
  9. Answer templates (wiki)
  10. +
  11. Articles about Telegram in the media
  12. +
+

Whenever you learn something that was not in the docs,
make sure that this new info finds its way into the docs!

+

4. Bug reports

+

Search our trello boards before you do anything. In most cases, you will find all the info right away. Ask in your local group if anything is not clear. Use the bug report groups if you need to test things on devices you don't have.

+
    +
  1. Reporting bugs from Answering Questions
  2. +
  3. Bug Handling Manual
  4. +
  5. Investigating Bugs
  6. +
  7. Issues disambiguation board on Trello
  8. +
+

5. User suggestions

+

Search trello boards first. It could be a bug, a feature or a known suggestion. Discuss in local groups if new suggestions need to be added, then add the suggestion to the board. Don't do this if you're not sure. And remember that not all suggestions need to be added to the board. Use common sense and the feature philosophy.

+
    +
  1. Handling user suggestions from Answering Questions
  2. +
  3. Feature philosophy
  4. +
  5. Suggestions Trello board (about)
  6. +
+
+

Read the About section of the Suggestions Board before you add anything.

+
+

6. Projects and suggestions for the TSF

+

The Telegram Support Force is full of brilliant and creative people, and there are many more useful things that can be done besides answering questions. If you're interested in doing more, check out the TSF Projects board where you'll find a list of currently active projects initiated by our TSF members. Find one to your liking or just sign up to be notified when something that requires your skills is going on.

+

The list of projects is not very long for now, but we're working on adding more. If you have an idea for a project, see this card.

+

If you have other suggestions and ideas for the general workings of the TSF, our templates, and interfaces, don't hesitate to contact Markus about it. Oh, and: Rude frescoes. If you have no idea what this last thing was about, read on to the end of this document.

+
+

WARNING: If you've just joined the TSF and are still figuring out what's going on, we'd suggest not to get too involved with things like side projects. It's a better idea to first get comfortable with answering user questions before you spread out.

+
+

7. Security questions

+

Stick to the FAQ in case of ordinary users. Always consult Markus (unless the matter is fully covered in the Bestiary). If Markus is not available at the moment, ask in your local group. Don't be afraid to tell an advanced user that you are not a specialist — you don't have to be.

+
    +
  1. Ask users for the source of their doubts, most likely you'll get a link
  2. +
  3. The Features & Tricks board has a Bestiary section, look there for known articles
  4. +
  5. Advanced FAQ
  6. +
  7. Advanced concerns and questions should be mailed to security@telegram.org
  8. +
+

To use trello search for links, remove the http(s):// part. E.g.:

+
+ +
+ +

Trello search is not perfect for links even this way, so may be a good idea to take a personal look at the Bestiary if the search doesn't return anything. New links for problems that are covered in the Bestiary should be added to the relevant cards.

+

8. New language requests

+

Anyone can use the Translation platform to suggest improvements to our current translations — or create their own custom language packs and translate Telegram into any language.

+
    +
  1. Translations instructions in the FAQ
  2. +
  3. Translations section
  4. +
+

9. Join support force requests

+

Don't give our manifesto to just anybody. Try to see if the user is reasonable. If not, you can tell them that finding how to join us is the first test.

+

10. Media requests

+

Explain that you're a volunteer and can't handle press requests, but they can submit a request to @PressBot.

+

Never promise anything. Be extra careful when handling any questions from journalists. If it's something related to simple Telegram features, reply – but make sure they understand that you've volunteered to help users in support and are not a spokesperson for Telegram.

+

If it's anything more complicated, e.g.:

+
    +
  • Touches on any sensitive subjects like encryption, privacy, moderation, etc. in any way
  • +
  • Contains a list of questions
  • +
+

=> Simply direct to @PressBot.

+

11. Legal stuff

+

You as our volunteers are not trained in legal matters, so it's safer to do nothing at all, should you encounter any kind of legal requests. Lawyers know how to reach us. So simply ignore those messages, do not open, do not reply, do not worry. We'll handle everything.

+

12. Secret words

+

By the way, when reading our manuals, you will sometimes notice words that are definitely out of place. For example, a text may at some point say something like Bionic sycophants out of the blue – only in real life the strange words won't be highlighted in italics. If you find such words in our manuals, talk to @Gladosbot and send her the /sendsecret command (without parameters). The bot will ask you for the secret words you've found and respond if you've entered them correctly.

+

Try this now with the secret words you've just found in the paragraph above – and keep your eyes opened for more of them in other documents. Please don't neglect this! Secret words help us understand whether or not you are up to date on our docs in a friendly way.

+

13. Spam-related requests

+

Some users will complain that they were unfairly limited to only sending messages to their mutual contacts. We at the TSF do not have the tools to handle such requests, but our friendly @spambot is always ready to help them – and it speaks many different languages, including those that we don't. Feel free to send the spambot template to such users. If they keep insisting that you do something about their situation, it is OK to ignore them.

+

Some users will have you believe that somebody reported them 'for fun' or 'by mistake', but the reality is usually very different. We have a dedicated team of moderators that process every report aided by sophisticated algorithms, so it is not easy to get limited by mistake. Naturally, both humans and algorithms can err, but the @spambot has all the tools necessary for filing an appeal.

+

And remember: the vast, absolute majority of Telegram users never get reported at all, most reports are declined, and most of the people that do get limited never even notice it. They can talk to anyone they've talked to before, they can reply to any messages other people send them, and the initial limitation lasts for only a short period of time. Most likely, you wouldn't notice if we limited your account for a week or even a month.

+

Learn more about our antispam systems on Trello »

+

14. Abuse requests

+

The Telegram Support Force is an organization of volunteers that exists to help Telegram users find their way around the apps; you, our volunteers, are not qualified to solve cases involving illegal content — and neither am I (Markus). It is not an issue of trust, rather consider this:

+
    +
  1. We would like our volunteers to be safe from possible legal consequences in case of misunderstandings and incorrectly handled cases.
  2. +
  3. Exposure to certain materials can result in life-long mental scarring, so we want to leave this to professionals that choose to handle such materials for a living.
  4. +
+

For these good reasons the Telegram abuse department is completely separate from the TSF and is staffed by professionals and not volunteers. It is their job to deal with any public content and abuse-related disputes. Please tell users to write to abuse@telegram.org and include all the details and links — or use the built-in report buttons in our apps.

+
+

Please note: spam@telegram.org is NOT used for complaints about spam. More info

+
+

15. Stick to the BIOS

+

This is where you go whenever you're not sure of what to do next. If you don't find your answer in the BIOS, tell Markus about it. It's important to keep this document up to date.

+
+

TSF manuals

+

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/bug_herding.html b/data/tsf.telegram.org/manuals/bug_herding.html new file mode 100644 index 0000000000..40ea804181 --- /dev/null +++ b/data/tsf.telegram.org/manuals/bug_herding.html @@ -0,0 +1,334 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Bug Herding Explained

+ +
+ +
+

This document is intended for advanced TSF members. If you just joined us, come back later.
There's plenty of more urgent stuff for you to study, don't read this one yet.

+
+

The TSF is made up of volunteers who usually only have a fraction of their time to offer to our cause. They come and go, some of them disappear completely after 500 answers (some after 10, some without even leaving a single one). Our organization must be flexible enough to survive this.

+

Among other things, this means that our Trello boards must be accessible and easy to use for anyone, even if they are just passing by. Therefore, we need dedicated people who can take care of the boards and keep them well maintained for the rest of us, we need bug herders.

+

This manual is for those who would like to become part of this caste.

+
+

Herder protocol

+

You know from the bug handling manual that our final goal, when it comes to issues, is to get a trello card marked either as confirmed by dev or feature. As bug herders, we have more detailed responsibilities. We follow issues from the moment they are found to the public release in which they are resolved — and beyond.

+
    +
  1. Make sure that all newly discovered issues have their own cards (exceptions can be made for problems found in a recent beta version if the dev is in active development and says he'll fix it on the go).
  2. +
  3. Optimize all newly added cards, they must be: easy to find (good name, search keywords), specific (as in 'not vague'), have all the necessary details, but not too verbose.
  4. +
  5. Report all issues to the relevant developer group, not forgetting to include the trello link and an #issue_tag (the same way we do in questions).
  6. +
  7. Find all the requested info and add it to the card, move it to the Reviewed & Reported list, add a comment about this to the card so that we know when this happened.
  8. +
  9. Remind developers about trending issues that have been neglected for too long.
  10. +
  11. Check issues that are marked as fixed (are they?) and add relevant comments.
  12. +
  13. Whenever a new version is out, mark issues as fixed and comment with the version number.
  14. +
  15. Older issues that were fixed need to be archived or deleted after a while (but not immediately, since we will still be getting reports from people who forgot to update their apps).
  16. +
+

Herder goals

+

A bug herder has nothing left to do, if the Unsorted list is empty. Any card in that list should be seen as a call to action. Now let's look at the job in more detail.

+
+

Creating cards

+

If you found a problem, there is a good chance that somebody else from the TSF will soon get a question about it too. So it's important to create a trello card early. Create the card as soon as you have enough info to set the issue apart from the rest.

+

Information in a good card is ordered in this manner:
Problem (what) > Conditions (when) > Explanation (why; optional)

+

The Problem must be described in specific terms (photos are blurry, app crashes, voice messages stop playing).
The Conditions include:

+
    +
  1. The exact circumstances of the problem (photos are blurry in secret chats, app crashes when opening the contacts section, voice messages stop playing when a new message is received).
  2. +
  3. Steps to reproduce the issue.
  4. +
  5. Affected device/OS combinations.
  6. +
+

The Explanation part is optional, but it's nice to have it in cards that could potentially live long lives — e.g., when a bug depends on a specific device/OS combination and can't be fixed easily. (For example: 'This happens when photos are sent from an older version of the app and will stop being relevant when everyone updates.')

+

Title

+

The name of the card should be pretty general, details should be placed in the description. When composing the title, think from the perspective of somebody looking for the issue, who does not know too many details yet.

+

A good title should be structured this way:
Problem, general condition

+

Specific conditions and the explanation go to the description.

+
+

E.g., this card is useless: 'If the contact's name begins with “A” or “S”, iPhone 4s (7.1.2) users will not see messages from them'. When somebody encounters this issue, he will not have enough info to find this card. Most likely, he will only know that an iOS user doesn't get messages from some of their contacts. So if we want someone looking at the card to know that it describes their issue, we need to name it like this, for example: 'User doesn't see new messages if they come from contacts with names starting with “A” or “S”'. We will add a description, saying that the problem was encountered in iPhones 4s with iOS 7.1.2. And we will add all the necessary tags to make search easier, e.g. 'iOS, messages, invisible, not delivered', etc.'

+
+

Description and more info

+

Once you've got a card going, gradually expand it: improve the title, optimize keywords for searchability, add more info, don't forget adding #tq tags from affected users to the comments. Try to avoid any vagueness and ambiguity. E.g.:

+
    +
  • Avoid 'sometimes', 'in some cases', etc if you can. These words signal that additional investigation is required.
  • +
  • Use specific terms. Not 'doesn't work', but 'app crashes' or 'becomes unresponsive', etc.
  • +
  • Don't use 'latest', 'current' or 'previous' in terms of app version. Better stick to actual version numbers — some cards live long lives.
  • +
+

Generally, you need to strike a balance between enough info — and not too much. Developers are busy people, they will not have time to read through a long text, or might even get scared away by verbosity.

+
+

Bad example:

+
+
+ +
+
+ + +
+

And here's almost the same amount of info. But with higher chances to be read by the developer:

+
+
+ +
+ +

One card — one issue

+

If you read the examples above, you will have noticed that the initial card was dedicated to two bugs instead of one. This is very bad. Each issue must have a card to itself, even if the problematic behaviour seems similar. Imagine that your house had a leaky roof and burst water pipes at the same time — both problems mean it'll be very wet inside. But the underlying issues are very different.

+

Keywords & Search

+

The title and text of the card are searchable, but sometimes we need additional keywords. We usually mention them at the bottom, after a separator. This is useful if there are many ways to refer to a problem.

+

Once you've created a card, it's always a good idea to try to search for it yourself. Imagine that you've just met a user with this issue and are looking for info on Trello. What will you type in?

+
    +
  • This may give you ideas for additional keywords.
  • +
  • You may find that there are older cards from the 'Fixed' list are shown at the top of the search so that the card is not visible. Check if it's time to delete them.
  • +
  • You may find that another card is showing up because of bad wording. Try to rewrite it or remove excessive keywords (but only if they are unnecessary).
  • +
+

If there is a card and you had to show it to one of our volunteers who couldn't find it, think how you can improve its wording and keywords.

+
+

E.g., you have a card called 'App freezes when user joins supergroup'. One of the new volunteers asks in their regional group: 'I have a user that says his app crashes when people add him to groups'. You show them your card, but realize that it didn't mention the words 'crash', 'add', or 'group'.
So you add them to the list of keywords below the card. Then you check if it's now possible to find your card using a different description of the problem. You find that a card from 2013 called 'A group of aliens crash-landed on DC1, adding more trouble for the admins' is shown first for this query and delete it because it's a lie and therefore shouldn't be on Trello.

+
+

Affected devices

+

Be careful when mentioning affected devices in the card's title or description. If you can reproduce something on iOS8 — it doesn't mean this is an iOS8 bug yet. This is an iOS8 bug only if you can't reproduce it on iOS7.

+

Hence, the general rule: unless there are devices where the bug can't be reproduced, don't place device/OS version info in the title. Put them in a list under 'reproduced on'.

+

As soon as we see some kind of consistency, we can add things to the title. E.g., if we see that all iOS8 devices have the problem and devices running any other version of the OS do not.

+
+

Reporting to developers

+

Bug herders are also specialists in developer relations. Here's what we should do:

+
    +
  1. Let's stick to the existing app groups for all our contacts with the devs.
  2. +
  3. Let's contact developers when we already have an issue card going — at least a very basic version. (Exceptions could be made for bugs in beta versions that are in active testing.)
  4. +
  5. When contacting the devs, describe the issue, add a trello link and an #issue_tag. This way we can later look up what exactly the developer said about this or that issue (or didn't) and act accordingly. (If issues are investigated in local TSF groups, do insert the #issue_tag there to make the relevant info discoverable there as well.)
  6. +
  7. Once the issue has been optimized and reported, move it to the Reviewed & Reported list.
  8. +
  9. If the developer asks for more info, supply it to the group (and the card if relevant). If you cannot do that right away for any reason, add the questions as a comment to the card, and add the yellow label.
  10. +
  11. Remember that developers are biased and will frequently tell you that the problem belongs to some other developer or even is related to the OS or device and is not our bug. If this happens, it is your task to make sure that we've traced the problem back to the right dev (in the former case) and that we can't demostrate other apps that do the same well on the same device or platform (in the latter).
  12. +
+
+

Archiving issues

+

Once an update is out that fixes an issue, we add a comment along the lines of 'fixed in v.2.9'. Then we leave the issue on the board for about 2 weeks or so — our volunteers will still meet people that need to upgrade to fix their problem. Sometimes an issue deemed to be fixed can also come back to life (likely in a modified form, e.g. 'now only for iPads', etc.).

+

Once the 2 weeks are out, we can assume that the issue is indeed fixed for good. We can then archive the card. Note that archived cards will still show up in search (unless you specifically exclude them). Therefore, it may be more reasonable to delete the cards in case of smaller bugs and interface glitches (this is especially true for interface oversights and feature-like issues).

+

It is acceptable to archive an issue that couldn't be reproduced by us and had no activity (complaints, #tq tags, etc.) for 3-4 months. But don't delete those.

+

Archive:

+
    +
  • Trending issues
  • +
  • Major issues
  • +
  • Inter-app issues
  • +
  • Hard to reproduce issues
  • +
  • Obscure issues without any recent activity
  • +
+

Delete examples:

+
    +
  • Wrong error message when setting a username starting or ending with an underscore
  • +
  • Shared media / shared files selector glitch in landscape mode on iOS 7
  • +
  • Can't forward photo when opening from shared media
  • +
+

..and all other minor interface bugs

+

Deleting cards

+

Since anything that is deleted is lost forever, we shouldn't rush this. But if you're sure, go ahead and do it. If you're not sure, make sure it should be, then go ahead and delete it.

+

Herder responsibility

+

When you create a card or review & report somebody else's card, subscribe to it. And follow it to the end. In the event that something has to be done with it and nobody is doing it — you do it. This way we will not have Mexican standoffs when everybody knows something has to be done, but since technically nobody has to do it, it's never done at all.

+

And that's about it. If we all observe the simple procedures outlined above, peace and prosperity will come down on our homes and trello boards — and all TSF volunteers will only be a few keystrokes aways from any answer they might need.

+

How do I join?

+

You talk to Markus or Daria. But bear in mind that he'll like to see some 20-30 bugs you've created, reviewed and otherwise took care of on Trello. All bug herders should be prepared to spend a lot of time answering questions and tending their issues.

+
+

P.S. Bugging the devs — a note on bug relevance

+

Bugs and even trending bugs have different priorities. Those priorities can be calculated in the same way as one would determine whether a feature is worth considering.

+

I mentioned 'reminding the developers about bugs' as a responsibility of the herder, especially of a herder who is subscribed to a bug. But do remember that there are good and bad times to do this.

+

Whenever an update is imminent, it is a good idea to go through existing issues and make sure that all the critical stuff is fixed. Don't bug pre-release devs with exotic stuff — if it wasn't fixed at this point, it'll have to wait until the next release.

+

The best time for reminding about older issues would probably be a few days after a major release, or as soon as the dust has settled — maybe one day after the release if no major new bugs were found.

+

Such a reminder is best done in the form of a digest. You could collect a few links to well-investigated issues and offer them for consideration in the app's group. Alternatively, you could also gather a few issues that are less clear and ask about them again. Just don't do it in 20 separate messages over the course of seven hours — make it one nice but not too fat message.

+

If that doesn't work, try a smaller number. Maybe choose three important issues and ping him again with a nice concise message. Once he says something of that is fixed, show him your earlier digest and ask to take care of that stuff as well since he's here already.

+

Be cool.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/bugs.html b/data/tsf.telegram.org/manuals/bugs.html new file mode 100644 index 0000000000..27b766f077 --- /dev/null +++ b/data/tsf.telegram.org/manuals/bugs.html @@ -0,0 +1,460 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Handling Bugs and Troubleshooting

+ +
+ +
+

This manual is intended for volunteers of the TSF, but anyone else is free to take a look as well.

+
+

Every now and then users will report bugs in Telegram. The step-by-step guide and troubleshooting tips on this page will help you deal with those reports in style and eventually help Telegram get rid of the bugs themselves.

+

See the Bug Hunting Algorithm for tips on investigating new issues.

+
+

Reporting a bug

+

1. Search known issues

+

We use Trello boards to keep track of bugs (sorry, these boards are TSF-only, here's how you join), features and user suggestions, so your first stop when encountering a bug report is Trello search. Most likely, we already know about the issue — sometimes it is not a bug at all. So make sure you study all the relevant cards.

+

If you have found the issue on Trello, leave a comment in the card with your user's #tq tag and device info (skip this step if the card already has too many comments of that kind or is in the “Hot and Trending” list). Then go right to step 4.

+
+ +
+ +

Trello cards are organized in lists that are pretty self-explanatory:

+
    +
  • The 'Hot & Trending' list has the most important cards
  • +
  • Every card begins its journey in the 'Unsorted' list.
  • +
  • Once the issue was reviewed by a bug herder and reported to the developer, it moves to the 'Reviewed & Reported' list. we can report any new occurrences in the comments (don't forget the footers) and try to find missing puzzle pieces (e.g. the issue happens only on specific devices / OS versions).
  • +
  • Finally, at some point, the card reaches 'Fixed' status, is declared a 'Feature' (this is how we want this to work), or 'Not our bug' (platform restrictions, etc.).
  • +
+
+

The very first card on each board contains a description for all labels and fields.

+
+

Fields
Cards can have a status field which describes what state the issue is in and whether or not it requires any actions on our TSF side. (E.g., “Needs info”, “Needs logs”, or “Confirm fix”). Feel free to update Happens in with the latest version you were able to reproduce the issue in. Other fields are mostly reserved for bug herders, including the Dev Priority field.

+

Labels

+
    +
  • Blue – A notable card. Being aware of what's inside may potentially help you recognize important issues and answer questions from users more easily.
  • +
+
    +
  • Yellow – This card is missing important information.
  • +
  • Sky blue – This card mentions a workaround for the issue.
  • +
+
+

2. Investigate the bug

+
+

IMPORTANT: Please see the Bug Hunting Algorithm after this manual for an in-depth look at investigating bugs.

+
+

If you can't find anything useful on Trello:

+
    +
  1. Check app version. Must be the latest available.
  2. +
  3. Reproduce the bug, if you have a relevant device on hand – using the store version. Mention if you can't reproduce it. Ask in the bug groups if you don't have the device – don't forget to include all hashtags from the user's footer with your question and English summary (don't just forward the messages!).
  4. +
  5. Check the Troubleshooting Tips below, there are some useful tips for identifying and reporting common issues.
  6. +
  7. Find and ask the right questions that allow to locate the bug — in as few steps as possible. We have a separate and rather exciting manual on this topic, known as the Bug Hunting Algorithm.
  8. +
+
+

Reporting a bug is in many regards like convicting the developer of a crime. Just as in that case, you need a clear vision of what happened and why, hard evidence (screenshots) and witnesses (users). Unlike in a criminal case, though, it is considered appropriate and even necessary to reproduce the deed (see if you can reproduce the bug and get the same results).

+

Another crucial difference: our defendant is also the judge. He is accountable, of course, but still biased. It is in the developer's best interest to convince you and the public that the bug is not related to his work. Server-side devs will blame the client devs, client devs will blame the server-side devs — and they all together will blame the OS and device manufacturers. While sometimes this is true, we need to leave no escape for them if it isn't.

+
+

3. Report the bug

+

If the bug is not mentioned on the Issues board and the Troubleshooting manual doesn't have any special instructions for the case, we need to report it on Trello.

+
    +
  1. Make sure you've really completed steps 1 and 2 of this guide.
  2. +
  3. Important: Discuss the issue in the relevant bug group — you never know what your teammates may have to say. Maybe there's no need to create a card and an existing one needs editing instead.
  4. +
  5. If you're sure this is necessary, add the issue to the board. We've added templates like this one to all boards. You can copy them and fill with info.
  6. +
  7. Make sure your heading has all the relevant info. Fill in the rest of the details.
  8. +
  9. Always add the user's (and/or your own, if you reproduced the issue) footer with the system hashtags.
  10. +
  11. Add relevant screenshots or video to the issue. This is optional if the issue is clear enough without them.
  12. +
  13. If the problem involves particular items (account, photo, group, message, etc) we need the coordinates required to locate that particular item (tq/footer, phone number, username, link, Telegram Web address bar string, forwarded copy). Think: if you were a developer who just received your question, would you need to ask for more info instead of giving an answer?
  14. +
  15. Make sure that your description has all the relevant keywords, so that it's easy to find the issue via search.
  16. +
  17. When you add your first issue to Trello send the link to Daria — along with a picture of a beetle.
  18. +
  19. Think of the words you would use if you were looking for that issue — try them in the search box. Adjust the description accordingly.
  20. +
  21. Ask your teammates if you have any doubts.
  22. +
+
Bug Groups
+

We're currently experimenting with TSF-wide bug groups for reporting and investigating issues in the apps. You can find a list in this card.

+
Custom Fields and Comments
+
    +
  • There are several custom fields. Fill in 'Happens in' with the hashtag of the version, e.g. #5_1_1_870. The rest of the custom fields are reserved for bug herders, please don't change them unless you're 200% sure you know what you're doing. You can read more about the fields in the first card on each board.
  • +
  • Add a comment whenever a bug's state is changed.
  • +
  • Discuss in the groups, comments are for important updates to the bug only.
  • +
  • Make sure the bug's description covers all the important info that emerged in the comments.
  • +
+

4. Notify the user

+

Once we're done, we need to get back to the user and tell them that we've located the issue or are investigating it. You never know how long that might take, but the user must know that he succeeded in alerting us — and helped us greatly. Parachutes and pasties

+
    +
  • Always include an issue ID hashtag in your reply in this situation.
  • +
  • All Trello cards have unique identifiers (open card, click on “share and more”, then 'link to this card', take the last part of the link, after /c/ — e.g. vMFS4MZf).
  • +
  • We use this ID to create a hashtag (e.g. #issue_vMFS4MZf) and include it in our reply to the user with that problem. Like this, for example:
  • +
+
+

We are terribly sorry that you are not able to delete old profile pictures in channels on the Android application. We reproduced it and are already working on a bug fix. Your issue #issue_lLyHjLRa has been recorded and we'll get back to you as soon as we have any news.

+

By the way, you can delete old profile pictures on the desktop client. Tell us if you want to learn more about it.

+
+

This allows us to use Telegram hashtag search to track issues for follow-up questions. The bot can use these hashtags to send automatic replies when a bug is fixed. We can also search for this issue on Trello by its ID.

+
+ +
+ +

5. Stick to our goals

+
    +
  1. Our final goal in case of any bug is to create a report in Trello that would get the status confirmed by a developer or feature.
  2. +
  3. If no report was created or no existing relevant report found — we did nothing, regardless of how much time we spent talking to the user or TSF members in our groups and diagnosing the issue.
  4. +
+

In order to achieve this goal with a clear conscience, we need to respect our users' time and effort — a little more on this below:

+
+

A note on users

+

One may think that users are people with problems. Wrong. It is us, who have problems — the user is just a convenient medium for studying them. Our problem is either that something is wrong in our system. Or that we can't understand what the user is doing wrong. When you look at it this way, you quickly realize that the user is our most important asset when it comes to bugs. They can help us identify bugs and improve usability.

+

So when somebody comes with a problem, we are not looking for a way to make them go away. Instead we must do all we can to not let the user leave before we find the problem. This means that everything you ask them to do must tell you something important. Nobody enjoys rebooting their phone or logging out and in. The general rule is minimum actions — maximum effect. Rabid bunnies alert

+

If you do ask something that requires at least some effort, please be nice about it! People don't have any obligations to Telegram — we need to convince them to help us and to thank them when they do. It's the least we can do.

+
+

Now that we're done with the basic reporting process, below are some common issues and what you should do when somebody is complaining about similar stuff.

+
+

Troubleshooting common issues

+
+

This advanced troubleshooting guide is intended for volunteers of the Telegram Support Force.
Everyone else is also welcome to take a look. Help friends and loved ones — or troubleshoot yourself!

+
+

+
+

Can’t Install App

+

iOS: Device must run iOS 8 or higher.

+

Android:
- If SDK >= 16 —> Android version must be 4.1
- Ask whether other applications install ok
- If nothing helps we need to know the Android version and device model

+

Messages not getting delivered

+

The following cases cover pretty much all the complaints:

+
    +
  • The user may be confused by the check system. In Telegram: 1 check = message sent, 2 checks = message read (opened by the recipient). So the sender may think the message is not getting delivered or is delivered slowly, while they are in fact waiting for it to be read.
  • +
  • The user may be blocked. When a user is blocked, they will not be notified in any way. Their messages will just stop being read: one tick, always. He should ask his partner to check Settings — Blocked users. Blocked users don't see your online and last seen status and don't see a person's profile picture.
  • +
  • The user may confuse messages and notifications and say that messages are not getting delivered, when he in fact means notification issues. If a person sees the message upon opening the app, but doesn't get notified until he opens the app — see notification problems.
  • +
  • Since people can delete messages for everyone after sending them, it could be that a user means notifications for messages that have already been deleted by the sender.
  • +
  • Lastly, when dealing with Secret Chats, users must remember, that messages will only be delivered to the device that was used when the Secret Chat was created.
  • +
+

In case it's none of these five (but it must be one of these five, really), this is one of the worst things that can ever happen in Telegram. We need to know:

+
    +
  • Phone numbers for all participating users
  • +
  • Devices and app types for all users
  • +
  • Secret chats or cloud chats? Or both?
  • +
  • One-way or two-way problem?
  • +
+

Notification problems

+

iOS:

+
    +
  • Make sure notifications are on in Telegram AND in phone settings (Settings > Notifications), check app version.
  • +
  • Make sure notifications weren’t disabled for a specific chat or group.
  • +
  • Shut down Telegram (go to home screen, swipe up or double tap home button, swipe upwards on Telegram), then go to Phone Settings and disable alerts. Relaunch Telegram, go to Phone Settings, enable alerts.
  • +
+

What we need to know if nothing helps:

+
    +
  • User’s footer tag.
  • +
  • Type of problem (notifications: a. never come, b. come only sometimes)
  • +
  • Logs that capture the problem and time of when the message was received.
  • +
+

Android:

+
    +
  • Make sure the latest app version is installed.
  • +
  • Go to Telegram Settings > Notifications and Sounds, make sure that notifications are ON and Importance is set to “High” or greater.
  • +
  • Check notification priority for Telegram in Android settings, it can be called Importance or Behaviour depending on the device.
  • +
  • Make sure notifications weren’t disabled for a specific chat.
  • +
  • Make sure that Google Play Services are installed on the device.
  • +
+
+

NOTE: Huawei and Xiaomi devices have evil task killer services that interfere with the Telegram notification service. In order for our notifications to work, users need to add Telegram to allowed apps in those devices' security settings. Samsung devices also may require some manipulations.

+

Huawei: Phone Manager App > Protected apps > Add Telegram to the list.
Xiaomi: Services > Security > Permissions > Autostart, find Telegram and enable autostart.
Samsung: Settings > Device Maintenance > Battery > Unmonitored Apps, then add Telegram to that list.

+
+

In case you went through all the steps to no avail, we need to know:

+
    +
  • User’s phone number (username) or footer tag so we can find the user again to followup.
  • +
  • Type of problem (notifications: a. never come, b. come only sometimes)
  • +
  • System and app logs that capture the problem and time of when the message was received.
  • +
+

Contact importing problems

+

User doesn’t see his contacts in Telegram. Or sees numbers instead of names in Messages list.

+
+

Important: Naturally, one of the easiest ways to solve this would be to save the number in international format. Do not advise this before other methods. Our systems must correctly parse any contacts. Therefore it is imperative to collect these samples and bring them to your local group so that we can adjust the algorithms.

+
+

iOS:

+
    +
  • Temporarily change the name of the missing contact in Phone Contacts (not in Telegram) — add a few symbols, then change back again
  • +
  • If that doesn’t help, relogin
  • +
+

Things we need to know if nothing helps:

+
    +
  • User’s phone number
  • +
  • Phone number(s) of the contact(s)
  • +
  • How exactly these numbers are stored in users phone book (international format or anything else?)
  • +
  • Devices and app versions for all users
  • +
+

Android:

+
    +
  • Relaunch the app (not relogin! that won’t help) — swipe the app off the currently-running-apps list
  • +
  • Temporarily change the name of the contact in phone contacts (add a few symbols, then change back again)
  • +
+

Things we need to know if nothing helps:

+
    +
  • User’s phone number
  • +
  • Phone number(s) of the contact(s)
  • +
  • How exactly these numbers are stored in users phone book (international format or anything else?)
  • +
  • Devices and app versions for all users
  • +
+

Speed issues

+

Make sure that we're really talking about speed issues here. In Telegram, 1 check = message sent, 2 checks = message read (opened by the recipient).

+

What we need to know:

+
    +
  • Problem occurs in one app only, or in all apps (e.g. in iOS and TDesktop on the same Wi-Fi).
  • +
  • Problem occurs when sending or receiving (uploading / downloading)? Or both?
  • +
  • What Internet connection is being used? If Wi-Fi, advise user to try LTE and vice versa and see what changes.
  • +
  • Recipient and sender's footer tags (or username/number).
  • +
  • Time of problem (better include the timezone too).
  • +
  • In case of a photo/video, ask the user to forward it to us. Not upload it again, just forward the original message with the attachment.
  • +
+

Connection issues

+

When people are reporting connection issues, check Twitter first: are there any widespread problems. If the problem is local, we need to find out a lot of information before things can be investigated. Things to ask:

+
    +
  • Do other (non-Telegram) apps work OK?
  • +
  • What exactly is happening? (always 'connecting…' / always 'updating…' / seems ok, but messages are not sent / not delivered, etc.)
  • +
  • At what time did it start? Is it still happening?
  • +
  • Is this happening all the time or sometimes?
  • +
  • Does this happen with all Telegram apps — or just one?
  • +
  • Does web.telegram.org work?
  • +
  • The problem happens on Wi-Fi, on mobile connection or in both cases?
  • +
+

Don't forget to include with your report:

+
    +
  • User's footer tag.
  • +
  • Results of @connectivity_test. Which GIFs are downloaded slowly or not downloaded?
  • +
+

It is possible that we'll need a Traceroute to our servers, here's how you get that. Wait for instructions from the server cultists to get the right IP to trace the route to — each case potentially requires a different one.

+

Last seen time is not displayed correctly

+
    +
  • We use the user’s time zone. If he has manually entered a time different from the time zone, he will see the wrong time.
  • +
  • If an app force-quits, the user may remain online for 5-7 minutes after this.
  • +
+

If none of the two, pass to the volunteer group. We need to know:

+
    +
  • The time zone and time set
  • +
  • Detailed description of the problem
  • +
+
+

NOTE: Support accounts are slightly different from ordinary user accounts. Due to some limitations, it is normal if you don't see the correct last seen time for users who are contacting Support.

+
+

User was blocked, but still sees last seen / online status

+

The changes that come with blocking sometimes do not take effect immediately. Give it a few minutes, maybe half an hour — and the blocked user will stop seeing the status.

+

If a blocked user restarts the app or relogins, but can still see online status — pass to the volunteer group. This cannot happen under normal conditions.

+
+

TSF Manuals

+

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/come-and-go.html b/data/tsf.telegram.org/manuals/come-and-go.html new file mode 100644 index 0000000000..e3b10448b2 --- /dev/null +++ b/data/tsf.telegram.org/manuals/come-and-go.html @@ -0,0 +1,229 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Leaving and Coming Back

+ +

If you‘re like 80% of us, you’ll most likely realize one day that a whole week had passed and you haven't sent a single answer to a user. Don't panic — that's what volunteering is all about. This manual will help you deal with it.

+

Going away

+

You know how it goes: you don‘t have time today, maybe tomorrow. Then tomorrow you don’t have time again. And then after a while you just forget about it, until one day — bang! — you remember. Now that you did remember, there are three things you can do:

+
    +
  1. Stop by Markus and your local TSF group and say: ‘Hey guys, I’m not going to be around for a while‘. It’s always good to know who's actually with us. OR, since you're here anyway:
  2. +
  3. If you were away for a few days, take 5 questions and answer them. It won‘t take longer than 5-6 minutes — and it means a lot to those who’ll get the answers. OR
  4. +
  5. If you were away for a few weeks, see below, then take 5 questions and answer them. You can do it! And it means a lot to the people out there.
  6. +
+

Coming back

+

Sometimes it‘s hard to come back when you’ve been away for a while. Feels like there‘s a ton of things you’ve missed, and you don't quite know where to start. Well, here:

+
    +
  1. Go to twitter.com/telegram and read all the tweets you‘ve missed. Don’t mind the @replies by Telegram, just read our actual tweets. This way you'll know everything important that happened in the public domain: important updates, blog articles, etc.
  2. +
  3. Open the TSF Notifications group and read everything that‘s been said there. There won’t be much, since we keep the group free of chatting.
  4. +
  5. Go to your local TSF group. Don't read the messages you've missed there — there may be thousands of them, and most of them will no longer be relevant. Just say hello to your teammates and ask them if there are any other new things that you should know.
  6. +
  7. Stick to the BIOS whenever in doubt.
  8. +
+

And that's it. Easy! You're ready to answer some questions again.

+
+

TIP: It is always a good idea to start by searching for your own #tsfUsernameTag, regardless of how long you've been away for. This way you will always be sure that no users are waiting for you to come back and finish the conversation.

+
+

Or not?

+

Look inside you and ask yourself one thing: ‘Why am I here? Do I want to answer their questions?’ And if the answer is ‘errr, no’. Or ‘well, I’m here to get the latest news about Telegram'. Or ‘ummm, I’m here because I want to beta test the apps'.

+

If it‘s one of these, let’s be honest about it — just tell Markus. There's no shame in that, really.

+
+

Addendum: On bugs and testing

+

Testing Telegram apps and finding problems is a useful activity. But, unfortunately, this is not what the Telegram Support Force is about. As volunteers, we go deeper. When we see an issue, we create Trello cards and fill them with info, we collect all the necessary details and make sure the developers know, we find users with similar issues to pinpoint problems — and we tell those users that we know about their problem and salvation is at hand.

+

If you‘re doing all that when you encounter an issue while using the app, you have my sincerest gratitude. But merely writing about bugs in a local TSF group and letting other volunteers do the actual work — I’m afraid, this does not mean being part of the TSF.

+

So if testing and looking for bugs is what you‘d like to do, it’s either this or this. And I'm glad to have met you, regardless of the option you choose.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/e2ee.html b/data/tsf.telegram.org/manuals/e2ee.html new file mode 100644 index 0000000000..fbd858a506 --- /dev/null +++ b/data/tsf.telegram.org/manuals/e2ee.html @@ -0,0 +1,202 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+

A Detailed Guide to End-to-End Encryption

+ +

Alas, this magnificent work is not finished yet. Come back later. Yes.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + +