From dc47aa32d30247cf8b352dd43bb2cd6709c6b5f7 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sat, 21 Aug 2021 21:36:22 +0000 Subject: [PATCH] Update content of files --- data/core.telegram.org.html | 252 - data/core.telegram.org/animated_stickers.html | 138 - data/core.telegram.org/api.html | 252 - .../api/account-deletion.html | 129 - .../api/animated-emojis.html | 148 - 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 | 150 - data/core.telegram.org/api/config.html | 320 - data/core.telegram.org/api/datacenter.html | 151 - 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 | 237 - .../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 | 550 - data/core.telegram.org/api/folders.html | 179 - data/core.telegram.org/api/geochats.html | 115 - data/core.telegram.org/api/invoking.html | 154 - data/core.telegram.org/api/layers.html | 1446 - 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 | 165 - data/core.telegram.org/api/optimisation.html | 150 - data/core.telegram.org/api/passport.html | 670 - 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 | 985 - data/core.telegram.org/api/qr-login.html | 154 - .../core.telegram.org/api/recent-actions.html | 154 - data/core.telegram.org/api/requests.html | 133 - data/core.telegram.org/api/rights.html | 133 - .../api/scheduled-messages.html | 156 - data/core.telegram.org/api/search.html | 179 - data/core.telegram.org/api/srp.html | 255 - data/core.telegram.org/api/stats.html | 297 - data/core.telegram.org/api/terms.html | 140 - 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 | 130 - data/core.telegram.org/api/web-events.html | 177 - data/core.telegram.org/apple_privacy.html | 118 - data/core.telegram.org/bots.html | 434 - data/core.telegram.org/bots/2-0-intro.html | 230 - .../core.telegram.org/bots/api-changelog.html | 626 - data/core.telegram.org/bots/api.html | 9256 -- 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 | 247 - .../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.contentSettings | 157 - .../constructor/account.password | 208 - .../constructor/account.passwordInputSettings | 176 - .../constructor/account.passwordSettings | 161 - .../constructor/account.privacyRules | 157 - .../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.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 - .../constructor/botCommand.html | 152 - .../constructor/botInfo.html | 157 - .../constructor/botInlineMediaResult.html | 186 - .../botInlineMessageMediaAuto.html | 167 - .../botInlineMessageMediaContact.html | 172 - .../constructor/botInlineMessageMediaGeo.html | 175 - .../botInlineMessageMediaVenue.html | 182 - .../constructor/botInlineMessageText.html | 170 - .../constructor/botInlineResult.html | 189 - .../constructor/cdnConfig.html | 149 - .../constructor/cdnPublicKey.html | 154 - .../constructor/channel.html | 272 - .../constructor/channelAdminLogEvent.html | 162 - ...channelAdminLogEventActionChangeAbout.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 - ...channelAdminLogEventActionEditMessage.html | 152 - ...lAdminLogEventActionParticipantInvite.html | 147 - ...nelAdminLogEventActionParticipantJoin.html | 132 - ...elAdminLogEventActionParticipantLeave.html | 132 - ...nLogEventActionParticipantToggleAdmin.html | 155 - ...minLogEventActionParticipantToggleBan.html | 155 - .../channelAdminLogEventActionStopPoll.html | 147 - ...annelAdminLogEventActionToggleInvites.html | 147 - ...nLogEventActionTogglePreHistoryHidden.html | 150 - ...elAdminLogEventActionToggleSignatures.html | 147 - ...nnelAdminLogEventActionToggleSlowMode.html | 155 - ...hannelAdminLogEventActionUpdatePinned.html | 147 - .../channelAdminLogEventsFilter.html | 256 - .../constructor/channelForbidden.html | 177 - .../constructor/channelFull.html | 334 - .../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 | 152 - .../constructor/channels.channelParticipants | 157 - .../channels.channelParticipantsNotModified | 132 - data/core.telegram.org/constructor/chat.html | 217 - .../constructor/chatAdminRights.html | 195 - .../constructor/chatBannedRights.html | 215 - .../constructor/chatEmpty.html | 147 - .../constructor/chatForbidden.html | 152 - .../constructor/chatFull.html | 209 - .../constructor/chatInvite.html | 190 - .../constructor/chatInviteAlready.html | 147 - .../constructor/chatInviteEmpty.html | 132 - .../constructor/chatInviteExported.html | 147 - .../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 | 167 - .../constructor/chatPhotoEmpty.html | 132 - .../constructor/codeSettings.html | 166 - .../core.telegram.org/constructor/config.html | 420 - .../constructor/contact.html | 152 - .../constructor/contactStatus.html | 152 - .../constructor/contacts.blocked | 157 - .../constructor/contacts.blockedSlice | 162 - .../constructor/contacts.contacts | 157 - .../constructor/contacts.contactsNotModified | 132 - .../constructor/contacts.found | 162 - .../constructor/contacts.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/encryptedChat.html | 177 - .../constructor/encryptedChatDiscarded.html | 147 - .../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 - data/core.telegram.org/constructor/error.html | 152 - .../constructor/exportedMessageLink.html | 152 - .../constructor/fileHash.html | 171 - .../constructor/fileLocation.html | 182 - .../fileLocationToBeDeprecated.html | 152 - .../constructor/fileLocationUnavailable.html | 179 - .../core.telegram.org/constructor/folder.html | 177 - .../constructor/folderPeer.html | 155 - data/core.telegram.org/constructor/game.html | 182 - .../constructor/geoPoint.html | 167 - .../constructor/geoPointEmpty.html | 132 - .../constructor/globalPrivacySettings.html | 152 - .../constructor/help.appUpdate | 185 - .../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 - .../constructor/inputAppEvent.html | 162 - .../inputBotInlineMessageGame.html | 152 - .../constructor/inputBotInlineMessageID.html | 157 - .../inputBotInlineMessageMediaAuto.html | 165 - .../inputBotInlineMessageMediaContact.html | 172 - .../inputBotInlineMessageMediaGeo.html | 175 - .../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/inputGeoPointEmpty.html | 132 - .../inputKeyboardButtonUrlAuth.html | 176 - .../constructor/inputMediaContact.html | 162 - .../constructor/inputMediaDice.html | 150 - .../constructor/inputMediaDocument.html | 157 - .../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 - .../inputPaymentCredentialsAndroidPay.html | 152 - .../inputPaymentCredentialsApplePay.html | 147 - .../inputPaymentCredentialsSaved.html | 152 - .../constructor/inputPeerChannel.html | 155 - .../inputPeerChannelFromMessage.html | 160 - .../constructor/inputPeerChat.html | 147 - .../constructor/inputPeerEmpty.html | 132 - .../constructor/inputPeerNotifySettings.html | 167 - .../inputPeerPhotoFileLocation.html | 170 - .../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 - .../inputReportReasonGeoIrrelevant.html | 132 - .../constructor/inputReportReasonOther.html | 147 - .../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 - .../constructor/inputStickerSetDice.html | 150 - .../constructor/inputStickerSetEmpty.html | 132 - .../constructor/inputStickerSetID.html | 152 - .../constructor/inputStickerSetItem.html | 162 - .../constructor/inputStickerSetShortName.html | 147 - .../constructor/inputStickerSetThumb.html | 160 - .../inputStickeredMediaDocument.html | 147 - .../constructor/inputStickeredMediaPhoto.html | 147 - .../constructor/inputTakeoutFileLocation.html | 132 - .../constructor/inputTheme.html | 152 - .../constructor/inputThemeSettings.html | 177 - .../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 | 132 - .../constructor/inputWallPaperSlug.html | 147 - .../constructor/inputWebDocument.html | 165 - .../inputWebFileGeoPointLocation.html | 172 - .../constructor/inputWebFileLocation.html | 152 - .../constructor/invoice.html | 199 - .../constructor/jsonArray.html | 147 - .../constructor/jsonBool.html | 147 - .../constructor/jsonNull.html | 132 - .../constructor/jsonNumber.html | 147 - .../constructor/jsonObject.html | 147 - .../constructor/jsonObjectValue.html | 152 - .../constructor/jsonString.html | 147 - .../constructor/keyboardButton.html | 147 - .../constructor/keyboardButtonBuy.html | 147 - .../constructor/keyboardButtonCallback.html | 167 - .../constructor/keyboardButtonGame.html | 147 - .../keyboardButtonRequestGeoLocation.html | 147 - .../keyboardButtonRequestPhone.html | 147 - .../keyboardButtonRequestPoll.html | 157 - .../constructor/keyboardButtonRow.html | 147 - .../keyboardButtonSwitchInline.html | 162 - .../constructor/keyboardButtonUrl.html | 152 - .../constructor/keyboardButtonUrlAuth.html | 179 - .../constructor/labeledPrice.html | 154 - .../constructor/langPackDifference.html | 162 - .../constructor/langPackLanguage.html | 202 - .../constructor/langPackString.html | 152 - .../constructor/langPackStringDeleted.html | 147 - .../constructor/langPackStringPluralized.html | 182 - .../constructor/maskCoords.html | 169 - .../constructor/message.html | 297 - .../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 - .../messageActionHistoryClear.html | 132 - .../constructor/messageActionPaymentSent.html | 154 - .../messageActionPaymentSentMe.html | 179 - .../constructor/messageActionPhoneCall.html | 167 - .../constructor/messageActionPinMessage.html | 132 - .../messageActionScreenshotTaken.html | 132 - .../messageActionSecureValuesSent.html | 149 - .../messageActionSecureValuesSentMe.html | 154 - .../constructor/messageEmpty.html | 147 - .../constructor/messageEntityBankCard.html | 152 - .../constructor/messageEntityBlockquote.html | 152 - .../constructor/messageEntityBold.html | 152 - .../constructor/messageEntityBotCommand.html | 152 - .../constructor/messageEntityCashtag.html | 152 - .../constructor/messageEntityCode.html | 152 - .../constructor/messageEntityEmail.html | 152 - .../constructor/messageEntityHashtag.html | 152 - .../constructor/messageEntityItalic.html | 152 - .../constructor/messageEntityMention.html | 155 - .../constructor/messageEntityMentionName.html | 162 - .../constructor/messageEntityPhone.html | 152 - .../constructor/messageEntityPre.html | 157 - .../constructor/messageEntityStrike.html | 152 - .../constructor/messageEntityTextUrl.html | 160 - .../constructor/messageEntityUnderline.html | 152 - .../constructor/messageEntityUnknown.html | 152 - .../constructor/messageEntityUrl.html | 155 - .../constructor/messageFwdHeader.html | 187 - .../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 | 207 - .../constructor/messageUserVote.html | 157 - .../messageUserVoteInputOption.html | 155 - .../constructor/messageUserVoteMultiple.html | 157 - .../constructor/messageViews.html | 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 - .../constructor/messages.chatFull | 157 - .../constructor/messages.chats | 147 - .../constructor/messages.chatsSlice | 155 - .../constructor/messages.dhConfig | 162 - .../constructor/messages.dhConfigNotModified | 147 - .../constructor/messages.dialogs | 162 - .../constructor/messages.dialogsNotModified | 147 - .../constructor/messages.dialogsSlice | 167 - .../constructor/messages.discussionMessage | 180 - .../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.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.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/pageBlockTable.html | 167 - .../constructor/pageBlockTitle.html | 147 - .../constructor/pageBlockUnsupported.html | 132 - .../constructor/pageBlockVideo.html | 167 - .../constructor/pageCaption.html | 152 - .../constructor/pageListItemBlocks.html | 147 - .../constructor/pageListItemText.html | 147 - .../pageListOrderedItemBlocks.html | 152 - .../constructor/pageListOrderedItemText.html | 152 - .../constructor/pageRelatedArticle.html | 182 - .../constructor/pageTableCell.html | 187 - .../constructor/pageTableRow.html | 147 - ...BKDF2HMACSHA512iter100000SHA256ModPow.html | 165 - .../constructor/passwordKdfAlgoUnknown.html | 132 - .../constructor/paymentCharge.html | 152 - .../constructor/paymentRequestedInfo.html | 167 - .../paymentSavedCredentialsCard.html | 152 - .../payments.ValidatedRequestedInfo | 145 - .../constructor/payments.bankCardData | 152 - .../constructor/payments.paymentForm | 207 - .../constructor/payments.paymentReceipt | 199 - .../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 | 190 - .../constructor/peerUser.html | 147 - .../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 | 172 - .../constructor/photoEmpty.html | 147 - .../constructor/photoPathSize.html | 155 - .../constructor/photoSize.html | 172 - .../constructor/photoSizeEmpty.html | 150 - .../constructor/photoSizeProgressive.html | 172 - .../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/privacyKeyPhoneNumber.html | 132 - .../constructor/privacyKeyPhoneP2P.html | 132 - .../constructor/privacyKeyProfilePhoto.html | 132 - .../privacyKeyStatusTimestamp.html | 132 - .../constructor/privacyValueAllowAll.html | 132 - .../privacyValueAllowChatParticipants.html | 147 - .../privacyValueAllowContacts.html | 132 - .../constructor/privacyValueAllowUsers.html | 147 - .../constructor/privacyValueDisallowAll.html | 132 - .../privacyValueDisallowChatParticipants.html | 147 - .../privacyValueDisallowContacts.html | 132 - .../privacyValueDisallowUsers.html | 147 - .../constructor/receivedNotifyMessage.html | 152 - .../constructor/recentMeUrlChat.html | 152 - .../constructor/recentMeUrlChatInvite.html | 152 - .../constructor/recentMeUrlStickerSet.html | 152 - .../constructor/recentMeUrlUnknown.html | 147 - .../constructor/recentMeUrlUser.html | 152 - .../constructor/replyInlineMarkup.html | 147 - .../constructor/replyKeyboardForceReply.html | 157 - .../constructor/replyKeyboardHide.html | 152 - .../constructor/replyKeyboardMarkup.html | 167 - .../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 - .../sendMessageGamePlayAction.html | 132 - .../sendMessageGeoLocationAction.html | 132 - .../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 - .../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 | 212 - .../constructor/stickerSetCovered.html | 152 - .../constructor/stickerSetMultiCovered.html | 152 - .../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 - data/core.telegram.org/constructor/theme.html | 192 - .../constructor/themeSettings.html | 172 - .../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/updateBotInlineQuery.html | 172 - .../constructor/updateBotInlineSend.html | 172 - .../updateBotPrecheckoutQuery.html | 184 - .../constructor/updateBotShippingQuery.html | 162 - .../constructor/updateBotWebhookJSON.html | 147 - .../updateBotWebhookJSONQuery.html | 157 - .../constructor/updateChannel.html | 147 - .../updateChannelAvailableMessages.html | 155 - .../updateChannelMessageForwards.html | 157 - .../updateChannelMessageViews.html | 157 - .../constructor/updateChannelParticipant.html | 182 - .../updateChannelReadMessagesContents.html | 155 - .../constructor/updateChannelTooLong.html | 161 - .../constructor/updateChannelUserTyping.html | 172 - .../constructor/updateChannelWebPage.html | 167 - .../updateChatDefaultBannedRights.html | 160 - .../constructor/updateChatParticipantAdd.html | 167 - .../updateChatParticipantAdmin.html | 165 - .../updateChatParticipantDelete.html | 157 - .../constructor/updateChatParticipants.html | 147 - .../constructor/updateChatUserTyping.html | 160 - .../constructor/updateConfig.html | 135 - .../constructor/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 - .../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 | 157 - .../constructor/updateNewChannelMessage.html | 162 - .../updateNewEncryptedMessage.html | 152 - .../constructor/updateNewMessage.html | 157 - .../updateNewScheduledMessage.html | 150 - .../constructor/updateNewStickerSet.html | 147 - .../constructor/updateNotifySettings.html | 152 - .../constructor/updatePeerBlocked.html | 152 - .../constructor/updatePeerLocated.html | 147 - .../constructor/updatePeerSettings.html | 152 - .../constructor/updatePhoneCall.html | 147 - .../updatePhoneCallSignalingData.html | 152 - .../updatePinnedChannelMessages.html | 177 - .../constructor/updatePinnedDialogs.html | 160 - .../constructor/updatePinnedMessages.html | 175 - .../constructor/updatePrivacy.html | 152 - .../constructor/updatePtsChanged.html | 135 - .../updateReadChannelDiscussionInbox.html | 177 - .../updateReadChannelDiscussionOutbox.html | 162 - .../constructor/updateReadChannelInbox.html | 179 - .../constructor/updateReadChannelOutbox.html | 155 - .../updateReadFeaturedStickers.html | 132 - .../constructor/updateReadHistoryInbox.html | 182 - .../constructor/updateReadHistoryOutbox.html | 165 - .../updateReadMessagesContents.html | 160 - .../constructor/updateRecentStickers.html | 132 - .../constructor/updateSavedGifs.html | 132 - .../updateServiceNotification.html | 183 - .../constructor/updateShort.html | 152 - .../constructor/updateShortChatMessage.html | 227 - .../constructor/updateShortMessage.html | 224 - .../constructor/updateShortSentMessage.html | 187 - .../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 | 282 - .../constructor/userEmpty.html | 147 - .../constructor/userForeign.html | 177 - .../constructor/userFull.html | 229 - .../constructor/userProfilePhoto.html | 177 - .../constructor/userProfilePhotoEmpty.html | 132 - .../constructor/userRequest.html | 182 - .../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 | 180 - .../constructor/wallPaper.html | 192 - .../constructor/wallPaperNoFile.html | 162 - .../constructor/wallPaperSettings.html | 177 - .../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/contestfaq.html | 152 - .../core.telegram.org/css/bootstrap-extra.css | 3274 - data/core.telegram.org/css/bootstrap.min.css | 10 - data/core.telegram.org/css/core-widgets.css | 105 - data/core.telegram.org/css/telegram-extra.css | 246 - data/core.telegram.org/css/telegram.css | 4866 - data/core.telegram.org/import-stickers.html | 156 - data/core.telegram.org/js/bootstrap.min.js | 11 - data/core.telegram.org/js/core-widgets.js | 279 - data/core.telegram.org/js/jquery-ui.min.js | 9 - data/core.telegram.org/js/jquery.min.js | 4 - data/core.telegram.org/js/main.js | 675 - .../js/telegram-passport2.js | 413 - .../method/account.acceptAuthorization | 170 - .../method/account.cancelPasswordEmail | 138 - .../method/account.changePhone | 185 - .../method/account.checkUsername | 167 - .../method/account.confirmPasswordEmail | 175 - .../method/account.confirmPhone | 180 - .../method/account.createTheme | 169 - .../method/account.deleteAccount | 170 - .../method/account.deleteSecureValue | 153 - .../method/account.finishTakeoutSession | 172 - .../method/account.getAccountTTL | 134 - .../method/account.getAllSecureValues | 136 - .../method/account.getAuthorizationForm | 159 - .../method/account.getAuthorizations | 134 - .../method/account.getAutoDownloadSettings | 134 - .../account.getContactSignUpNotification | 135 - .../method/account.getContentSettings | 134 - .../method/account.getGlobalPrivacySettings | 135 - .../method/account.getMultiWallPapers | 148 - .../method/account.getNotifyExceptions | 165 - .../method/account.getNotifySettings | 166 - .../method/account.getPassword | 134 - .../method/account.getPasswordSettings | 170 - .../method/account.getPrivacy | 166 - .../method/account.getSecureValue | 151 - .../core.telegram.org/method/account.getTheme | 181 - .../method/account.getThemes | 158 - .../method/account.getTmpPassword | 176 - .../method/account.getWallPaper | 150 - .../method/account.getWallPapers | 153 - .../method/account.getWebAuthorizations | 136 - .../method/account.initTakeoutSession | 204 - .../method/account.installTheme | 165 - .../method/account.installWallPaper | 155 - .../method/account.registerDevice | 202 - .../method/account.reportPeer | 177 - .../method/account.resendPasswordEmail | 138 - .../method/account.resetAuthorization | 175 - .../method/account.resetNotifySettings | 135 - .../method/account.resetWallPapers | 135 - .../method/account.resetWebAuthorization | 154 - .../method/account.resetWebAuthorizations | 137 - .../method/account.saveAutoDownloadSettings | 165 - .../method/account.saveSecureValue | 157 - .../method/account.saveTheme | 155 - .../method/account.saveWallPaper | 160 - .../method/account.sendChangePhoneCode | 171 - .../method/account.sendConfirmPhoneCode | 174 - .../method/account.sendVerifyEmailCode | 151 - .../method/account.sendVerifyPhoneCode | 156 - .../method/account.setAccountTTL | 167 - .../account.setContactSignUpNotification | 150 - .../method/account.setContentSettings | 155 - .../method/account.setGlobalPrivacySettings | 150 - .../method/account.setPrivacy | 176 - .../method/account.unregisterDevice | 180 - .../method/account.updateDeviceLocked | 153 - .../method/account.updateNotifySettings | 187 - .../method/account.updatePasswordSettings | 202 - .../method/account.updateProfile | 187 - .../method/account.updateStatus | 155 - .../method/account.updateTheme | 179 - .../method/account.updateUsername | 182 - .../method/account.uploadTheme | 190 - .../method/account.uploadWallPaper | 160 - .../method/account.verifyEmail | 174 - .../method/account.verifyPhone | 181 - .../method/auth.acceptLoginToken | 171 - .../method/auth.bindTempAuthKey | 257 - data/core.telegram.org/method/auth.cancelCode | 180 - .../method/auth.checkPassword | 180 - data/core.telegram.org/method/auth.checkPhone | 176 - .../method/auth.dropTempAuthKeys | 151 - .../method/auth.exportAuthorization | 167 - .../method/auth.exportLoginToken | 166 - .../method/auth.importAuthorization | 178 - .../method/auth.importBotAuthorization | 200 - .../method/auth.importLoginToken | 172 - data/core.telegram.org/method/auth.logOut | 140 - .../method/auth.recoverPassword | 172 - .../method/auth.requestPasswordRecovery | 154 - data/core.telegram.org/method/auth.resendCode | 186 - .../method/auth.resetAuthorizations | 156 - data/core.telegram.org/method/auth.sendCall | 175 - data/core.telegram.org/method/auth.sendCode | 241 - .../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 | 241 - .../method/bots.answerWebhookJSONQuery | 178 - .../method/bots.sendCustomRequest | 177 - .../method/bots.setBotCommands | 151 - .../method/channels.checkUsername | 190 - .../method/channels.createChannel | 220 - .../method/channels.deleteChannel | 195 - .../method/channels.deleteHistory | 180 - .../method/channels.deleteMessages | 190 - .../method/channels.deleteUserHistory | 199 - .../method/channels.editAdmin | 291 - .../method/channels.editBanned | 221 - .../method/channels.editCreator | 215 - .../method/channels.editLocation | 180 - .../method/channels.editPhoto | 211 - .../method/channels.editTitle | 201 - .../method/channels.exportMessageLink | 204 - .../method/channels.getAdminLog | 226 - .../method/channels.getAdminedPublicChannels | 191 - .../method/channels.getChannels | 181 - .../method/channels.getFullChannel | 182 - .../method/channels.getGroupsForDiscussion | 144 - .../method/channels.getInactiveChannels | 134 - .../method/channels.getLeftChannels | 172 - .../method/channels.getMessages | 193 - .../method/channels.getParticipant | 200 - .../method/channels.getParticipants | 208 - .../method/channels.inviteToChannel | 262 - .../method/channels.joinChannel | 222 - .../method/channels.leaveChannel | 201 - .../method/channels.readHistory | 185 - .../method/channels.readMessageContents | 185 - .../method/channels.reportSpam | 192 - .../method/channels.setDiscussionGroup | 185 - .../method/channels.setStickers | 178 - .../method/channels.togglePreHistoryHidden | 202 - .../method/channels.toggleSignatures | 182 - .../method/channels.toggleSlowMode | 200 - .../method/channels.updateUsername | 212 - .../method/contacts.acceptContact | 185 - .../method/contacts.addContact | 212 - data/core.telegram.org/method/contacts.block | 182 - .../method/contacts.blockFromReplies | 179 - .../method/contacts.deleteByPhones | 150 - .../method/contacts.deleteContacts | 155 - .../method/contacts.getBlocked | 155 - .../method/contacts.getContactIDs | 151 - .../method/contacts.getContacts | 155 - .../method/contacts.getLocated | 192 - .../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 | 187 - data/core.telegram.org/method/contacts.search | 178 - .../method/contacts.toggleTopPeers | 153 - .../core.telegram.org/method/contacts.unblock | 167 - .../method/folders.deleteFolder | 158 - .../method/folders.editPeerFolders | 175 - .../method/help.acceptTermsOfService | 150 - .../method/help.dismissSuggestion | 151 - .../method/help.editUserInfo | 163 - .../method/help.getAppChangelog | 162 - .../method/help.getAppConfig | 142 - .../method/help.getAppUpdate | 150 - .../method/help.getCdnConfig | 154 - data/core.telegram.org/method/help.getConfig | 202 - .../method/help.getCountriesList | 159 - .../method/help.getDeepLinkInfo | 150 - .../method/help.getInviteText | 134 - .../method/help.getNearestDc | 134 - .../method/help.getPassportConfig | 154 - .../method/help.getPromoData | 136 - .../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 | 151 - 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 | 219 - .../method/invokeWithMessagesRange.html | 154 - .../method/invokeWithTakeout.html | 171 - .../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 | 174 - .../method/messages.addChatUser | 227 - .../method/messages.checkChatInvite | 178 - .../method/messages.clearAllDrafts | 138 - .../method/messages.clearRecentStickers | 155 - .../method/messages.createChat | 197 - .../method/messages.deleteChatUser | 198 - .../method/messages.deleteHistory | 201 - .../method/messages.deleteMessages | 177 - .../method/messages.deleteScheduledMessages | 160 - .../method/messages.discardEncryption | 177 - .../method/messages.editChatAbout | 211 - .../method/messages.editChatAdmin | 195 - .../messages.editChatDefaultBannedRights | 201 - .../method/messages.editChatPhoto | 208 - .../method/messages.editChatTitle | 193 - .../method/messages.editInlineBotMessage | 206 - .../method/messages.editMessage | 323 - .../method/messages.exportChatInvite | 188 - .../method/messages.faveSticker | 172 - .../method/messages.forwardMessage | 177 - .../method/messages.forwardMessages | 343 - .../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.getChats | 173 - .../method/messages.getCommonChats | 185 - .../method/messages.getDhConfig | 175 - .../method/messages.getDialogFilters | 136 - .../method/messages.getDialogUnreadMarks | 133 - .../method/messages.getDialogs | 218 - .../method/messages.getDiscussionMessage | 162 - .../method/messages.getDocumentByHash | 178 - .../method/messages.getEmojiKeywords | 149 - .../messages.getEmojiKeywordsDifference | 154 - .../method/messages.getEmojiKeywordsLanguages | 148 - .../method/messages.getEmojiURL | 149 - .../method/messages.getFavedStickers | 153 - .../method/messages.getFeaturedStickers | 153 - .../method/messages.getFullChat | 172 - .../method/messages.getGameHighScores | 187 - .../method/messages.getHistory | 237 - .../method/messages.getInlineBotResults | 221 - .../method/messages.getInlineGameHighScores | 177 - .../method/messages.getMaskStickers | 153 - .../method/messages.getMessageEditData | 186 - .../method/messages.getMessageReactionsList | 178 - .../method/messages.getMessages | 153 - .../method/messages.getMessagesReactions | 153 - .../method/messages.getMessagesViews | 199 - .../method/messages.getOldFeaturedStickers | 163 - .../method/messages.getOnlines | 171 - .../method/messages.getPeerDialogs | 186 - .../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 | 196 - .../method/messages.getSavedGifs | 153 - .../method/messages.getScheduledHistory | 182 - .../method/messages.getScheduledMessages | 179 - .../method/messages.getSearchCounters | 156 - .../method/messages.getSplitRanges | 133 - .../method/messages.getStatsURL | 181 - .../method/messages.getStickerSet | 167 - .../method/messages.getStickers | 158 - .../method/messages.getSuggestedDialogFilters | 136 - .../method/messages.getUnreadMentions | 207 - .../method/messages.getWebPage | 177 - .../method/messages.getWebPagePreview | 191 - .../method/messages.hidePeerSettingsBar | 153 - .../method/messages.importChatInvite | 222 - .../method/messages.installStickerSet | 172 - .../method/messages.markDialogUnread | 160 - .../method/messages.migrateChat | 185 - .../method/messages.readDiscussion | 164 - .../method/messages.readEncryptedHistory | 172 - .../method/messages.readFeaturedStickers | 150 - .../method/messages.readHistory | 181 - .../method/messages.readMentions | 181 - .../method/messages.readMessageContents | 149 - .../method/messages.receivedMessages | 148 - .../method/messages.receivedQueue | 165 - .../method/messages.reorderPinnedDialogs | 185 - .../method/messages.reorderStickerSets | 160 - data/core.telegram.org/method/messages.report | 177 - .../method/messages.reportEncryptedSpam | 167 - .../method/messages.reportSpam | 175 - .../method/messages.requestEncryption | 185 - .../method/messages.requestUrlAuth | 164 - .../method/messages.saveDraft | 197 - .../core.telegram.org/method/messages.saveGif | 172 - .../method/messages.saveRecentSticker | 182 - data/core.telegram.org/method/messages.search | 286 - .../method/messages.searchGifs | 172 - .../method/messages.searchGlobal | 226 - .../method/messages.searchStickerSets | 168 - .../method/messages.sendBroadcast | 145 - .../method/messages.sendEncrypted | 205 - .../method/messages.sendEncryptedFile | 210 - .../method/messages.sendEncryptedService | 200 - .../method/messages.sendInlineBotResult | 329 - .../method/messages.sendMedia | 438 - .../method/messages.sendMessage | 378 - .../method/messages.sendMultiMedia | 238 - .../method/messages.sendReaction | 185 - .../method/messages.sendScheduledMessages | 177 - .../messages.sendScreenshotNotification | 182 - .../method/messages.sendVote | 205 - .../method/messages.setBotCallbackAnswer | 198 - .../method/messages.setBotPrecheckoutResults | 188 - .../method/messages.setBotShippingResults | 186 - .../method/messages.setEncryptedTyping | 177 - .../method/messages.setGameScore | 213 - .../method/messages.setInlineBotResults | 313 - .../method/messages.setInlineGameScore | 198 - .../method/messages.setTyping | 240 - .../method/messages.startBot | 219 - .../method/messages.toggleDialogPin | 177 - .../method/messages.toggleStickerSets | 170 - .../method/messages.uninstallStickerSet | 167 - .../method/messages.unpinAllMessages | 153 - .../method/messages.updateDialogFilter | 180 - .../method/messages.updateDialogFiltersOrder | 153 - .../method/messages.updatePinnedMessage | 223 - .../method/messages.uploadEncryptedFile | 155 - .../method/messages.uploadMedia | 254 - .../method/payments.clearSavedInfo | 160 - .../method/payments.getBankCardData | 149 - .../method/payments.getPaymentForm | 166 - .../method/payments.getPaymentReceipt | 166 - .../method/payments.getSavedInfo | 134 - .../method/payments.sendPaymentForm | 190 - .../method/payments.validateRequestedInfo | 181 - .../core.telegram.org/method/phone.acceptCall | 193 - .../method/phone.confirmCall | 188 - .../method/phone.discardCall | 202 - .../method/phone.getCallConfig | 134 - .../method/phone.receivedCall | 172 - .../method/phone.requestCall | 213 - .../method/phone.saveCallDebug | 177 - .../method/phone.sendSignalingData | 156 - .../method/phone.setCallRating | 192 - .../method/photos.deletePhotos | 148 - .../method/photos.getUserPhotos | 188 - .../method/photos.updateProfilePhoto | 191 - .../method/photos.uploadProfilePhoto | 216 - .../method/stats.getBroadcastStats | 194 - .../method/stats.getMegagroupStats | 165 - .../method/stats.getMessagePublicForwards | 208 - .../method/stats.getMessageStats | 185 - .../method/stats.loadAsyncGraph | 188 - .../method/stickers.addStickerToSet | 177 - .../method/stickers.changeStickerPosition | 177 - .../method/stickers.createStickerSet | 257 - .../method/stickers.removeStickerFromSet | 172 - .../method/stickers.setStickerSetThumb | 172 - .../method/updates.getChannelDifference | 237 - .../method/updates.getDifference | 215 - .../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 | 186 - .../method/users.setSecureValueErrors | 176 - data/core.telegram.org/methods.html | 2084 - 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 | 210 - .../mtproto/description.html | 242 - .../mtproto/description_v1.html | 205 - .../mtproto/mtproto-transports.html | 293 - .../mtproto/samples-auth_key.html | 752 - .../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 | 184 - 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 | 485 - data/core.telegram.org/schema.html | 1651 - .../schema/end-to-end-json.html | 1 - data/core.telegram.org/schema/end-to-end.html | 225 - data/core.telegram.org/schema/json.html | 1 - .../schema/mtproto-json.html | 1 - data/core.telegram.org/schema/mtproto.html | 206 - data/core.telegram.org/tdlib.html | 147 - data/core.telegram.org/tdlib/docs.html | 233 - .../tdlib/docs/td__api_8h.html | 3046 - .../tdlib/docs/td__json__client_8h.html | 430 - .../tdlib/docs/td__log_8h.html | 295 - .../tdlib/getting-started.html | 198 - .../tdlib/notification-api.html | 210 - data/core.telegram.org/tdlib/options.html | 465 - 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 | 662 - data/core.telegram.org/type/BotCommand.html | 143 - data/core.telegram.org/type/BotInfo.html | 143 - .../type/BotInlineMessage.html | 163 - .../type/BotInlineResult.html | 148 - data/core.telegram.org/type/CdnConfig.html | 164 - data/core.telegram.org/type/CdnPublicKey.html | 145 - .../type/ChannelAdminLogEvent.html | 143 - .../type/ChannelAdminLogEventAction.html | 243 - .../type/ChannelAdminLogEventsFilter.html | 143 - .../type/ChannelLocation.html | 148 - .../type/ChannelMessagesFilter.html | 148 - .../type/ChannelParticipant.html | 164 - .../type/ChannelParticipantsFilter.html | 178 - data/core.telegram.org/type/Chat.html | 163 - .../type/ChatAdminRights.html | 146 - .../type/ChatBannedRights.html | 146 - data/core.telegram.org/type/ChatFull.html | 148 - data/core.telegram.org/type/ChatInvite.html | 172 - 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/CodeSettings.html | 143 - data/core.telegram.org/type/Config.html | 162 - data/core.telegram.org/type/Contact.html | 143 - .../core.telegram.org/type/ContactStatus.html | 143 - data/core.telegram.org/type/DataJSON.html | 168 - data/core.telegram.org/type/DcOption.html | 143 - .../type/DecryptedDataBlock.html | 128 - .../type/DecryptedMessage.html | 140 - .../type/DecryptedMessageAction.html | 145 - .../type/DecryptedMessageLayer.html | 129 - .../type/DecryptedMessageMedia.html | 149 - data/core.telegram.org/type/Dialog.html | 148 - data/core.telegram.org/type/DialogFilter.html | 143 - .../type/DialogFilterSuggested.html | 143 - data/core.telegram.org/type/DialogPeer.html | 148 - .../type/DisabledFeature.html | 128 - data/core.telegram.org/type/Document.html | 173 - .../type/DocumentAttribute.html | 173 - data/core.telegram.org/type/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 | 167 - .../type/ExportedMessageLink.html | 162 - data/core.telegram.org/type/FileHash.html | 143 - data/core.telegram.org/type/FileLocation.html | 143 - 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/HighScore.html | 143 - .../type/ImportedContact.html | 143 - .../type/InlineBotSwitchPM.html | 143 - .../core.telegram.org/type/InputAppEvent.html | 143 - .../type/InputBotInlineMessage.html | 168 - .../type/InputBotInlineMessageID.html | 143 - .../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 | 183 - .../type/InputFolderPeer.html | 143 - data/core.telegram.org/type/InputGame.html | 148 - .../core.telegram.org/type/InputGeoPoint.html | 148 - 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 | 163 - .../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 | 258 - .../core.telegram.org/type/MessageEntity.html | 233 - .../type/MessageFwdHeader.html | 143 - .../type/MessageInteractionCounters.html | 143 - data/core.telegram.org/type/MessageMedia.html | 227 - data/core.telegram.org/type/MessageRange.html | 143 - .../type/MessageReactionsList.html | 128 - .../type/MessageReplies.html | 146 - .../type/MessageReplyHeader.html | 143 - .../type/MessageUserVote.html | 153 - data/core.telegram.org/type/MessageViews.html | 143 - .../type/MessagesFilter.html | 223 - data/core.telegram.org/type/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 | 173 - .../type/RestrictionReason.html | 143 - data/core.telegram.org/type/RichText.html | 218 - data/core.telegram.org/type/SavedContact.html | 143 - .../type/SecureCredentialsEncrypted.html | 143 - data/core.telegram.org/type/SecureData.html | 146 - data/core.telegram.org/type/SecureFile.html | 151 - .../type/SecurePasswordKdfAlgo.html | 155 - .../type/SecurePlainData.html | 150 - .../type/SecureRequiredType.html | 148 - .../type/SecureSecretSettings.html | 145 - data/core.telegram.org/type/SecureValue.html | 162 - .../type/SecureValueError.html | 183 - .../type/SecureValueHash.html | 143 - .../type/SecureValueType.html | 203 - .../type/SendMessageAction.html | 203 - .../type/ShippingOption.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 | 162 - data/core.telegram.org/type/StickerPack.html | 143 - data/core.telegram.org/type/StickerSet.html | 143 - .../type/StickerSetCovered.html | 148 - data/core.telegram.org/type/Theme.html | 172 - .../core.telegram.org/type/ThemeSettings.html | 143 - data/core.telegram.org/type/TopPeer.html | 143 - .../type/TopPeerCategory.html | 178 - .../type/TopPeerCategoryPeers.html | 143 - data/core.telegram.org/type/True.html | 145 - data/core.telegram.org/type/Update.html | 562 - data/core.telegram.org/type/Updates.html | 428 - .../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 - .../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.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.AffectedHistory | 178 - .../type/messages.AffectedMessages | 178 - .../type/messages.AllStickers | 172 - .../type/messages.ArchivedStickers | 162 - .../type/messages.BotCallbackAnswer | 162 - .../type/messages.BotResults | 162 - data/core.telegram.org/type/messages.ChatFull | 168 - data/core.telegram.org/type/messages.Chats | 198 - data/core.telegram.org/type/messages.DhConfig | 167 - data/core.telegram.org/type/messages.Dialogs | 172 - .../type/messages.DiscussionMessage | 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.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 - .../core.telegram.org/type/messages.SavedGifs | 167 - .../type/messages.SearchCounter | 143 - .../type/messages.SentEncryptedMessage | 177 - .../type/messages.SentMessage | 128 - .../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 - 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 - 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/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/desktop.telegram.org.html | 75 - data/desktop.telegram.org/changelog.html | 262 - .../css/bootstrap.min.css | 10 - data/desktop.telegram.org/css/telegram.css | 4866 - data/desktop.telegram.org/js/main.js | 675 - data/instantview.telegram.org.html | 293 - data/instantview.telegram.org/auth.html | 294 - data/instantview.telegram.org/checklist.html | 624 - .../css/bootstrap-extra.css | 3274 - .../css/bootstrap.min.css | 10 - .../css/codemirror.css | 372 - .../css/instantview.css | 3110 - .../instantview.telegram.org/css/telegram.css | 4866 - data/instantview.telegram.org/docs.html | 1527 - .../js/bootstrap.min.js | 11 - .../js/codemirror-instantview.js | 113 - .../js/codemirror/codemirror.js | 8890 -- .../js/codemirror/runmode.js | 72 - .../js/codemirror/simple.js | 213 - .../js/instantview.js | 1237 - .../instantview.telegram.org/js/jquery.min.js | 4 - data/instantview.telegram.org/js/main.js | 675 - data/instantview.telegram.org/rules.html | 251 - data/instantview.telegram.org/samples.html | 395 - data/instantview.telegram.org/templates.html | 79721 ---------------- data/macos.telegram.org.html | 404 - data/macos.telegram.org/css/bootstrap.min.css | 10 - data/macos.telegram.org/css/telegram.css | 4866 - data/macos.telegram.org/js/main.js | 675 - data/telegram.org.html | 284 - data/telegram.org/android.html | 79 - data/telegram.org/api.html | 284 - data/telegram.org/apple_privacy.html | 178 - data/telegram.org/blog.html | 268 - data/telegram.org/blog/200-million.html | 222 - data/telegram.org/blog/400-million.html | 272 - 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-streaming.html | 241 - 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 - .../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/gif-revolution.html | 224 - 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 - .../blog/instant-view-contest-200K.html | 273 - 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 - data/telegram.org/blog/login.html | 257 - data/telegram.org/blog/masks.html | 248 - data/telegram.org/blog/moar-stickers.html | 343 - data/telegram.org/blog/move-history.html | 284 - .../blog/new-profiles-people-nearby.html | 263 - data/telegram.org/blog/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 - .../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 - .../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 | 257 - .../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 - data/telegram.org/blog/video-editor-gifs.html | 252 - .../blog/video-messages-and-telescope.html | 247 - 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/crypto_contest.html | 209 - data/telegram.org/css/bootstrap-extra.css | 3274 - data/telegram.org/css/bootstrap.min.css | 10 - data/telegram.org/css/telegram.css | 4866 - data/telegram.org/evolution.html | 1612 - 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/js/bootstrap.min.js | 11 - data/telegram.org/js/games.js | 206 - data/telegram.org/js/jquery.min.js | 4 - data/telegram.org/js/main.js | 675 - data/telegram.org/js/telegram-widget.js | 515 - data/telegram.org/js/tgsticker.js | 456 - data/telegram.org/press.html | 194 - data/telegram.org/privacy.html | 294 - data/telegram.org/privacy/gmailbot.html | 161 - data/telegram.org/support.html | 138 - data/telegram.org/template31.html | 284 - data/telegram.org/teststore.html | 284 - 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 - data/telegram.org/tour/quizbot.html | 213 - data/telegram.org/tour/screenshots.html | 217 - data/telegram.org/verify.html | 151 - .../what-can-you-do-with-Telegram.html | 284 - data/themes.telegram.org.html | 162 - data/themes.telegram.org/auth.html | 163 - .../css/bootstrap-extra.css | 3274 - .../themes.telegram.org/css/bootstrap.min.css | 10 - .../themes.telegram.org/css/jquery-ui.min.css | 6 - data/themes.telegram.org/css/telegram.css | 4866 - data/themes.telegram.org/css/themes.css | 2001 - data/themes.telegram.org/js/bootstrap.min.js | 11 - data/themes.telegram.org/js/jquery-ui.min.js | 9 - data/themes.telegram.org/js/jquery.min.js | 4 - data/themes.telegram.org/js/main-aj.js | 1134 - data/themes.telegram.org/js/themes.js | 805 - data/translations.telegram.org.html | 297 - data/translations.telegram.org/en.html | 333 - .../translations.telegram.org/en/android.html | 388 - .../en/android_x.html | 388 - data/translations.telegram.org/en/ios.html | 388 - data/translations.telegram.org/en/macos.html | 388 - .../en/tdesktop.html | 388 - data/tsf.telegram.org.html | 240 - data/tsf.telegram.org/auth.html | 241 - data/tsf.telegram.org/css/billboard.css | 359 - data/tsf.telegram.org/css/bootstrap-extra.css | 3274 - data/tsf.telegram.org/css/bootstrap.min.css | 10 - data/tsf.telegram.org/css/health.css | 1375 - data/tsf.telegram.org/css/jquery-ui.min.css | 6 - data/tsf.telegram.org/css/tchart.min.css | 1 - data/tsf.telegram.org/css/telegram.css | 4866 - data/tsf.telegram.org/css/tsf.css | 2473 - data/tsf.telegram.org/js/billboard.min.js | 13 - data/tsf.telegram.org/js/bootstrap.min.js | 11 - data/tsf.telegram.org/js/jquery-ui.min.js | 9 - data/tsf.telegram.org/js/jquery.min.js | 4 - data/tsf.telegram.org/js/main-aj.js | 1134 - data/tsf.telegram.org/js/main.js | 675 - data/tsf.telegram.org/js/stats.js | 683 - data/tsf.telegram.org/js/tchart.min.js | 1 - data/tsf.telegram.org/js/tsf.js | 1236 - 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 - .../tsf.telegram.org/manuals/bug_hunting.html | 270 - data/tsf.telegram.org/manuals/bugs.html | 460 - .../tsf.telegram.org/manuals/come-and-go.html | 229 - .../tsf.telegram.org/manuals/e2ee-simple.html | 284 - data/tsf.telegram.org/manuals/e2ee.html | 202 - .../manuals/feature_philosophy.html | 263 - data/web.telegram.org.html | 1 - 1929 files changed, 508481 deletions(-) delete mode 100644 data/core.telegram.org.html delete mode 100644 data/core.telegram.org/animated_stickers.html delete mode 100644 data/core.telegram.org/api.html delete mode 100644 data/core.telegram.org/api/account-deletion.html delete mode 100644 data/core.telegram.org/api/animated-emojis.html delete mode 100644 data/core.telegram.org/api/auth.html delete mode 100644 data/core.telegram.org/api/bots.html delete mode 100644 data/core.telegram.org/api/bots/buttons.html delete mode 100644 data/core.telegram.org/api/bots/commands.html delete mode 100644 data/core.telegram.org/api/bots/games.html delete mode 100644 data/core.telegram.org/api/bots/inline.html delete mode 100644 data/core.telegram.org/api/channel.html delete mode 100644 data/core.telegram.org/api/config.html delete mode 100644 data/core.telegram.org/api/datacenter.html delete mode 100644 data/core.telegram.org/api/dice.html delete mode 100644 data/core.telegram.org/api/discussion.html delete mode 100644 data/core.telegram.org/api/drafts.html delete mode 100644 data/core.telegram.org/api/end-to-end.html delete mode 100644 data/core.telegram.org/api/end-to-end/pfs.html delete mode 100644 data/core.telegram.org/api/end-to-end/seq_no.html delete mode 100644 data/core.telegram.org/api/end-to-end/video-calls.html delete mode 100644 data/core.telegram.org/api/end-to-end/voice-calls.html delete mode 100644 data/core.telegram.org/api/end-to-end_v1.html delete mode 100644 data/core.telegram.org/api/entities.html delete mode 100644 data/core.telegram.org/api/errors.html delete mode 100644 data/core.telegram.org/api/file_reference.html delete mode 100644 data/core.telegram.org/api/files.html delete mode 100644 data/core.telegram.org/api/folders.html delete mode 100644 data/core.telegram.org/api/geochats.html delete mode 100644 data/core.telegram.org/api/invoking.html delete mode 100644 data/core.telegram.org/api/layers.html delete mode 100644 data/core.telegram.org/api/live-location.html delete mode 100644 data/core.telegram.org/api/mentions.html delete mode 100644 data/core.telegram.org/api/min.html delete mode 100644 data/core.telegram.org/api/obtaining_api_id.html delete mode 100644 data/core.telegram.org/api/offsets.html delete mode 100644 data/core.telegram.org/api/optimisation.html delete mode 100644 data/core.telegram.org/api/passport.html delete mode 100644 data/core.telegram.org/api/pattern.html delete mode 100644 data/core.telegram.org/api/payments.html delete mode 100644 data/core.telegram.org/api/pfs.html delete mode 100644 data/core.telegram.org/api/pin.html delete mode 100644 data/core.telegram.org/api/poll.html delete mode 100644 data/core.telegram.org/api/push-updates.html delete mode 100644 data/core.telegram.org/api/qr-login.html delete mode 100644 data/core.telegram.org/api/recent-actions.html delete mode 100644 data/core.telegram.org/api/requests.html delete mode 100644 data/core.telegram.org/api/rights.html delete mode 100644 data/core.telegram.org/api/scheduled-messages.html delete mode 100644 data/core.telegram.org/api/search.html delete mode 100644 data/core.telegram.org/api/srp.html delete mode 100644 data/core.telegram.org/api/stats.html delete mode 100644 data/core.telegram.org/api/terms.html delete mode 100644 data/core.telegram.org/api/threads.html delete mode 100644 data/core.telegram.org/api/top-rating.html delete mode 100644 data/core.telegram.org/api/updates.html delete mode 100644 data/core.telegram.org/api/url-authorization.html delete mode 100644 data/core.telegram.org/api/web-events.html delete mode 100644 data/core.telegram.org/apple_privacy.html delete mode 100644 data/core.telegram.org/bots.html delete mode 100644 data/core.telegram.org/bots/2-0-intro.html delete mode 100644 data/core.telegram.org/bots/api-changelog.html delete mode 100644 data/core.telegram.org/bots/api.html delete mode 100644 data/core.telegram.org/bots/faq.html delete mode 100644 data/core.telegram.org/bots/games.html delete mode 100644 data/core.telegram.org/bots/inline.html delete mode 100644 data/core.telegram.org/bots/samples.html delete mode 100644 data/core.telegram.org/bots/samples/hellobot.html delete mode 100644 data/core.telegram.org/bots/self-signed.html delete mode 100644 data/core.telegram.org/bots/webhooks.html delete mode 100644 data/core.telegram.org/cdn.html delete mode 100644 data/core.telegram.org/cdn/faq_ir.html delete mode 100644 data/core.telegram.org/cdn/faq_ir/durov.html delete mode 100644 data/core.telegram.org/constructor/account.authorizationForm delete mode 100644 data/core.telegram.org/constructor/account.authorizations delete mode 100644 data/core.telegram.org/constructor/account.autoDownloadSettings delete mode 100644 data/core.telegram.org/constructor/account.contentSettings delete mode 100644 data/core.telegram.org/constructor/account.password delete mode 100644 data/core.telegram.org/constructor/account.passwordInputSettings delete mode 100644 data/core.telegram.org/constructor/account.passwordSettings delete mode 100644 data/core.telegram.org/constructor/account.privacyRules delete mode 100644 data/core.telegram.org/constructor/account.sentChangePhoneCode delete mode 100644 data/core.telegram.org/constructor/account.sentEmailCode delete mode 100644 data/core.telegram.org/constructor/account.takeout delete mode 100644 data/core.telegram.org/constructor/account.themes delete mode 100644 data/core.telegram.org/constructor/account.themesNotModified delete mode 100644 data/core.telegram.org/constructor/account.tmpPassword delete mode 100644 data/core.telegram.org/constructor/account.wallPapers delete mode 100644 data/core.telegram.org/constructor/account.wallPapersNotModified delete mode 100644 data/core.telegram.org/constructor/account.webAuthorizations delete mode 100644 data/core.telegram.org/constructor/accountDaysTTL.html delete mode 100644 data/core.telegram.org/constructor/auth.authorization delete mode 100644 data/core.telegram.org/constructor/auth.authorizationSignUpRequired delete mode 100644 data/core.telegram.org/constructor/auth.codeTypeCall delete mode 100644 data/core.telegram.org/constructor/auth.codeTypeFlashCall delete mode 100644 data/core.telegram.org/constructor/auth.codeTypeSms delete mode 100644 data/core.telegram.org/constructor/auth.exportedAuthorization delete mode 100644 data/core.telegram.org/constructor/auth.loginToken delete mode 100644 data/core.telegram.org/constructor/auth.loginTokenMigrateTo delete mode 100644 data/core.telegram.org/constructor/auth.loginTokenSuccess delete mode 100644 data/core.telegram.org/constructor/auth.passwordRecovery delete mode 100644 data/core.telegram.org/constructor/auth.sentAppCode delete mode 100644 data/core.telegram.org/constructor/auth.sentCode delete mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeApp delete mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeCall delete mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall delete mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeSms delete mode 100644 data/core.telegram.org/constructor/authorization.html delete mode 100644 data/core.telegram.org/constructor/autoDownloadSettings.html delete mode 100644 data/core.telegram.org/constructor/bankCardOpenUrl.html delete mode 100644 data/core.telegram.org/constructor/baseThemeArctic.html delete mode 100644 data/core.telegram.org/constructor/baseThemeClassic.html delete mode 100644 data/core.telegram.org/constructor/baseThemeDay.html delete mode 100644 data/core.telegram.org/constructor/baseThemeNight.html delete mode 100644 data/core.telegram.org/constructor/baseThemeTinted.html delete mode 100644 data/core.telegram.org/constructor/boolFalse.html delete mode 100644 data/core.telegram.org/constructor/boolTrue.html delete mode 100644 data/core.telegram.org/constructor/botCommand.html delete mode 100644 data/core.telegram.org/constructor/botInfo.html delete mode 100644 data/core.telegram.org/constructor/botInlineMediaResult.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaAuto.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaContact.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaGeo.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageText.html delete mode 100644 data/core.telegram.org/constructor/botInlineResult.html delete mode 100644 data/core.telegram.org/constructor/cdnConfig.html delete mode 100644 data/core.telegram.org/constructor/cdnPublicKey.html delete mode 100644 data/core.telegram.org/constructor/channel.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEvent.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventsFilter.html delete mode 100644 data/core.telegram.org/constructor/channelForbidden.html delete mode 100644 data/core.telegram.org/constructor/channelFull.html delete mode 100644 data/core.telegram.org/constructor/channelLocation.html delete mode 100644 data/core.telegram.org/constructor/channelLocationEmpty.html delete mode 100644 data/core.telegram.org/constructor/channelMessagesFilter.html delete mode 100644 data/core.telegram.org/constructor/channelMessagesFilterEmpty.html delete mode 100644 data/core.telegram.org/constructor/channelParticipant.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantAdmin.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantBanned.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantCreator.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantLeft.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantSelf.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsAdmins.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsBanned.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsBots.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsContacts.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsKicked.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsMentions.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsRecent.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsSearch.html delete mode 100644 data/core.telegram.org/constructor/channels.adminLogResults delete mode 100644 data/core.telegram.org/constructor/channels.channelParticipant delete mode 100644 data/core.telegram.org/constructor/channels.channelParticipants delete mode 100644 data/core.telegram.org/constructor/channels.channelParticipantsNotModified delete mode 100644 data/core.telegram.org/constructor/chat.html delete mode 100644 data/core.telegram.org/constructor/chatAdminRights.html delete mode 100644 data/core.telegram.org/constructor/chatBannedRights.html delete mode 100644 data/core.telegram.org/constructor/chatEmpty.html delete mode 100644 data/core.telegram.org/constructor/chatForbidden.html delete mode 100644 data/core.telegram.org/constructor/chatFull.html delete mode 100644 data/core.telegram.org/constructor/chatInvite.html delete mode 100644 data/core.telegram.org/constructor/chatInviteAlready.html delete mode 100644 data/core.telegram.org/constructor/chatInviteEmpty.html delete mode 100644 data/core.telegram.org/constructor/chatInviteExported.html delete mode 100644 data/core.telegram.org/constructor/chatInvitePeek.html delete mode 100644 data/core.telegram.org/constructor/chatOnlines.html delete mode 100644 data/core.telegram.org/constructor/chatParticipant.html delete mode 100644 data/core.telegram.org/constructor/chatParticipantAdmin.html delete mode 100644 data/core.telegram.org/constructor/chatParticipantCreator.html delete mode 100644 data/core.telegram.org/constructor/chatParticipants.html delete mode 100644 data/core.telegram.org/constructor/chatParticipantsForbidden.html delete mode 100644 data/core.telegram.org/constructor/chatPhoto.html delete mode 100644 data/core.telegram.org/constructor/chatPhotoEmpty.html delete mode 100644 data/core.telegram.org/constructor/codeSettings.html delete mode 100644 data/core.telegram.org/constructor/config.html delete mode 100644 data/core.telegram.org/constructor/contact.html delete mode 100644 data/core.telegram.org/constructor/contactStatus.html delete mode 100644 data/core.telegram.org/constructor/contacts.blocked delete mode 100644 data/core.telegram.org/constructor/contacts.blockedSlice delete mode 100644 data/core.telegram.org/constructor/contacts.contacts delete mode 100644 data/core.telegram.org/constructor/contacts.contactsNotModified delete mode 100644 data/core.telegram.org/constructor/contacts.found delete mode 100644 data/core.telegram.org/constructor/contacts.importedContacts delete mode 100644 data/core.telegram.org/constructor/contacts.resolvedPeer delete mode 100644 data/core.telegram.org/constructor/contacts.topPeers delete mode 100644 data/core.telegram.org/constructor/contacts.topPeersDisabled delete mode 100644 data/core.telegram.org/constructor/contacts.topPeersNotModified delete mode 100644 data/core.telegram.org/constructor/dataJSON.html delete mode 100644 data/core.telegram.org/constructor/dcOption.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessage.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionNoop.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionResend.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionTyping.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageLayer.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaAudio.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaContact.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaDocument.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaVideo.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageService.html delete mode 100644 data/core.telegram.org/constructor/dialog.html delete mode 100644 data/core.telegram.org/constructor/dialogFilter.html delete mode 100644 data/core.telegram.org/constructor/dialogFilterSuggested.html delete mode 100644 data/core.telegram.org/constructor/dialogFolder.html delete mode 100644 data/core.telegram.org/constructor/dialogPeer.html delete mode 100644 data/core.telegram.org/constructor/dialogPeerFolder.html delete mode 100644 data/core.telegram.org/constructor/disabledFeature.html delete mode 100644 data/core.telegram.org/constructor/document.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeAnimated.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeAudio.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeFilename.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeHasStickers.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeImageSize.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeSticker.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeVideo.html delete mode 100644 data/core.telegram.org/constructor/documentEmpty.html delete mode 100644 data/core.telegram.org/constructor/draftMessage.html delete mode 100644 data/core.telegram.org/constructor/draftMessageEmpty.html delete mode 100644 data/core.telegram.org/constructor/emojiKeyword.html delete mode 100644 data/core.telegram.org/constructor/emojiKeywordDeleted.html delete mode 100644 data/core.telegram.org/constructor/emojiKeywordsDifference.html delete mode 100644 data/core.telegram.org/constructor/emojiLanguage.html delete mode 100644 data/core.telegram.org/constructor/emojiURL.html delete mode 100644 data/core.telegram.org/constructor/encryptedChat.html delete mode 100644 data/core.telegram.org/constructor/encryptedChatDiscarded.html delete mode 100644 data/core.telegram.org/constructor/encryptedChatEmpty.html delete mode 100644 data/core.telegram.org/constructor/encryptedChatRequested.html delete mode 100644 data/core.telegram.org/constructor/encryptedChatWaiting.html delete mode 100644 data/core.telegram.org/constructor/encryptedFile.html delete mode 100644 data/core.telegram.org/constructor/encryptedFileEmpty.html delete mode 100644 data/core.telegram.org/constructor/encryptedMessage.html delete mode 100644 data/core.telegram.org/constructor/encryptedMessageService.html delete mode 100644 data/core.telegram.org/constructor/error.html delete mode 100644 data/core.telegram.org/constructor/exportedMessageLink.html delete mode 100644 data/core.telegram.org/constructor/fileHash.html delete mode 100644 data/core.telegram.org/constructor/fileLocation.html delete mode 100644 data/core.telegram.org/constructor/fileLocationToBeDeprecated.html delete mode 100644 data/core.telegram.org/constructor/fileLocationUnavailable.html delete mode 100644 data/core.telegram.org/constructor/folder.html delete mode 100644 data/core.telegram.org/constructor/folderPeer.html delete mode 100644 data/core.telegram.org/constructor/game.html delete mode 100644 data/core.telegram.org/constructor/geoPoint.html delete mode 100644 data/core.telegram.org/constructor/geoPointEmpty.html delete mode 100644 data/core.telegram.org/constructor/globalPrivacySettings.html delete mode 100644 data/core.telegram.org/constructor/help.appUpdate delete mode 100644 data/core.telegram.org/constructor/help.countriesList delete mode 100644 data/core.telegram.org/constructor/help.countriesListNotModified delete mode 100644 data/core.telegram.org/constructor/help.country delete mode 100644 data/core.telegram.org/constructor/help.countryCode delete mode 100644 data/core.telegram.org/constructor/help.deepLinkInfo delete mode 100644 data/core.telegram.org/constructor/help.deepLinkInfoEmpty delete mode 100644 data/core.telegram.org/constructor/help.inviteText delete mode 100644 data/core.telegram.org/constructor/help.noAppUpdate delete mode 100644 data/core.telegram.org/constructor/help.passportConfig delete mode 100644 data/core.telegram.org/constructor/help.passportConfigNotModified delete mode 100644 data/core.telegram.org/constructor/help.promoData delete mode 100644 data/core.telegram.org/constructor/help.promoDataEmpty delete mode 100644 data/core.telegram.org/constructor/help.recentMeUrls delete mode 100644 data/core.telegram.org/constructor/help.support delete mode 100644 data/core.telegram.org/constructor/help.supportName delete mode 100644 data/core.telegram.org/constructor/help.termsOfService delete mode 100644 data/core.telegram.org/constructor/help.termsOfServiceUpdate delete mode 100644 data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty delete mode 100644 data/core.telegram.org/constructor/help.userInfo delete mode 100644 data/core.telegram.org/constructor/help.userInfoEmpty delete mode 100644 data/core.telegram.org/constructor/highScore.html delete mode 100644 data/core.telegram.org/constructor/importedContact.html delete mode 100644 data/core.telegram.org/constructor/inlineBotSwitchPM.html delete mode 100644 data/core.telegram.org/constructor/inputAppEvent.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageGame.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageID.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageText.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineResult.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineResultDocument.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineResultGame.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineResultPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputChannel.html delete mode 100644 data/core.telegram.org/constructor/inputChannelEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputChannelFromMessage.html delete mode 100644 data/core.telegram.org/constructor/inputChatPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputChatPhotoEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputChatUploadedPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputCheckPasswordEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputCheckPasswordSRP.html delete mode 100644 data/core.telegram.org/constructor/inputClientProxy.html delete mode 100644 data/core.telegram.org/constructor/inputDialogPeer.html delete mode 100644 data/core.telegram.org/constructor/inputDialogPeerFolder.html delete mode 100644 data/core.telegram.org/constructor/inputDocument.html delete mode 100644 data/core.telegram.org/constructor/inputDocumentEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputDocumentFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedChat.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFile.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileUploaded.html delete mode 100644 data/core.telegram.org/constructor/inputFile.html delete mode 100644 data/core.telegram.org/constructor/inputFileBig.html delete mode 100644 data/core.telegram.org/constructor/inputFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputFolderPeer.html delete mode 100644 data/core.telegram.org/constructor/inputGameID.html delete mode 100644 data/core.telegram.org/constructor/inputGameShortName.html delete mode 100644 data/core.telegram.org/constructor/inputGeoPoint.html delete mode 100644 data/core.telegram.org/constructor/inputGeoPointEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html delete mode 100644 data/core.telegram.org/constructor/inputMediaContact.html delete mode 100644 data/core.telegram.org/constructor/inputMediaDice.html delete mode 100644 data/core.telegram.org/constructor/inputMediaDocument.html delete mode 100644 data/core.telegram.org/constructor/inputMediaDocumentExternal.html delete mode 100644 data/core.telegram.org/constructor/inputMediaEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputMediaGame.html delete mode 100644 data/core.telegram.org/constructor/inputMediaGeoLive.html delete mode 100644 data/core.telegram.org/constructor/inputMediaGeoPoint.html delete mode 100644 data/core.telegram.org/constructor/inputMediaInvoice.html delete mode 100644 data/core.telegram.org/constructor/inputMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputMediaPhotoExternal.html delete mode 100644 data/core.telegram.org/constructor/inputMediaPoll.html delete mode 100644 data/core.telegram.org/constructor/inputMediaUploadedDocument.html delete mode 100644 data/core.telegram.org/constructor/inputMediaUploadedPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html delete mode 100644 data/core.telegram.org/constructor/inputMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/inputMessageCallbackQuery.html delete mode 100644 data/core.telegram.org/constructor/inputMessageEntityMentionName.html delete mode 100644 data/core.telegram.org/constructor/inputMessageID.html delete mode 100644 data/core.telegram.org/constructor/inputMessagePinned.html delete mode 100644 data/core.telegram.org/constructor/inputMessageReplyTo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterContacts.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterDocument.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterGeo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterGif.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterMusic.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhotos.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPinned.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterUrl.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterVideo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterVoice.html delete mode 100644 data/core.telegram.org/constructor/inputNotifyBroadcasts.html delete mode 100644 data/core.telegram.org/constructor/inputNotifyChats.html delete mode 100644 data/core.telegram.org/constructor/inputNotifyPeer.html delete mode 100644 data/core.telegram.org/constructor/inputNotifyUsers.html delete mode 100644 data/core.telegram.org/constructor/inputPaymentCredentials.html delete mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsAndroidPay.html delete mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html delete mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html delete mode 100644 data/core.telegram.org/constructor/inputPeerChannel.html delete mode 100644 data/core.telegram.org/constructor/inputPeerChannelFromMessage.html delete mode 100644 data/core.telegram.org/constructor/inputPeerChat.html delete mode 100644 data/core.telegram.org/constructor/inputPeerEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputPeerNotifySettings.html delete mode 100644 data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputPeerSelf.html delete mode 100644 data/core.telegram.org/constructor/inputPeerUser.html delete mode 100644 data/core.telegram.org/constructor/inputPeerUserFromMessage.html delete mode 100644 data/core.telegram.org/constructor/inputPhoneCall.html delete mode 100644 data/core.telegram.org/constructor/inputPhoneContact.html delete mode 100644 data/core.telegram.org/constructor/inputPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputPhotoEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputPhotoFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyForwards.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowContacts.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowContacts.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonChildAbuse.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonCopyright.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonOther.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonPornography.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonSpam.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonViolence.html delete mode 100644 data/core.telegram.org/constructor/inputSecureFile.html delete mode 100644 data/core.telegram.org/constructor/inputSecureFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputSecureFileUploaded.html delete mode 100644 data/core.telegram.org/constructor/inputSecureValue.html delete mode 100644 data/core.telegram.org/constructor/inputSingleMedia.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetAnimatedEmoji.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetDice.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetID.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetItem.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetShortName.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetThumb.html delete mode 100644 data/core.telegram.org/constructor/inputStickeredMediaDocument.html delete mode 100644 data/core.telegram.org/constructor/inputStickeredMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputTakeoutFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputTheme.html delete mode 100644 data/core.telegram.org/constructor/inputThemeSettings.html delete mode 100644 data/core.telegram.org/constructor/inputThemeSlug.html delete mode 100644 data/core.telegram.org/constructor/inputUser.html delete mode 100644 data/core.telegram.org/constructor/inputUserEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputUserFromMessage.html delete mode 100644 data/core.telegram.org/constructor/inputUserSelf.html delete mode 100644 data/core.telegram.org/constructor/inputWallPaper.html delete mode 100644 data/core.telegram.org/constructor/inputWallPaperNoFile.html delete mode 100644 data/core.telegram.org/constructor/inputWallPaperSlug.html delete mode 100644 data/core.telegram.org/constructor/inputWebDocument.html delete mode 100644 data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html delete mode 100644 data/core.telegram.org/constructor/inputWebFileLocation.html delete mode 100644 data/core.telegram.org/constructor/invoice.html delete mode 100644 data/core.telegram.org/constructor/jsonArray.html delete mode 100644 data/core.telegram.org/constructor/jsonBool.html delete mode 100644 data/core.telegram.org/constructor/jsonNull.html delete mode 100644 data/core.telegram.org/constructor/jsonNumber.html delete mode 100644 data/core.telegram.org/constructor/jsonObject.html delete mode 100644 data/core.telegram.org/constructor/jsonObjectValue.html delete mode 100644 data/core.telegram.org/constructor/jsonString.html delete mode 100644 data/core.telegram.org/constructor/keyboardButton.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonBuy.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonCallback.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonGame.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestPhone.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestPoll.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonRow.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonSwitchInline.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonUrl.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonUrlAuth.html delete mode 100644 data/core.telegram.org/constructor/labeledPrice.html delete mode 100644 data/core.telegram.org/constructor/langPackDifference.html delete mode 100644 data/core.telegram.org/constructor/langPackLanguage.html delete mode 100644 data/core.telegram.org/constructor/langPackString.html delete mode 100644 data/core.telegram.org/constructor/langPackStringDeleted.html delete mode 100644 data/core.telegram.org/constructor/langPackStringPluralized.html delete mode 100644 data/core.telegram.org/constructor/maskCoords.html delete mode 100644 data/core.telegram.org/constructor/message.html delete mode 100644 data/core.telegram.org/constructor/messageActionBotAllowed.html delete mode 100644 data/core.telegram.org/constructor/messageActionChannelCreate.html delete mode 100644 data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatAddUser.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatCreate.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatDeletePhoto.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatDeleteUser.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatEditPhoto.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatEditTitle.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatJoinedByLink.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatMigrateTo.html delete mode 100644 data/core.telegram.org/constructor/messageActionContactSignUp.html delete mode 100644 data/core.telegram.org/constructor/messageActionCustomAction.html delete mode 100644 data/core.telegram.org/constructor/messageActionEmpty.html delete mode 100644 data/core.telegram.org/constructor/messageActionGameScore.html delete mode 100644 data/core.telegram.org/constructor/messageActionGeoProximityReached.html delete mode 100644 data/core.telegram.org/constructor/messageActionHistoryClear.html delete mode 100644 data/core.telegram.org/constructor/messageActionPaymentSent.html delete mode 100644 data/core.telegram.org/constructor/messageActionPaymentSentMe.html delete mode 100644 data/core.telegram.org/constructor/messageActionPhoneCall.html delete mode 100644 data/core.telegram.org/constructor/messageActionPinMessage.html delete mode 100644 data/core.telegram.org/constructor/messageActionScreenshotTaken.html delete mode 100644 data/core.telegram.org/constructor/messageActionSecureValuesSent.html delete mode 100644 data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html delete mode 100644 data/core.telegram.org/constructor/messageEmpty.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBankCard.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBlockquote.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBold.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBotCommand.html delete mode 100644 data/core.telegram.org/constructor/messageEntityCashtag.html delete mode 100644 data/core.telegram.org/constructor/messageEntityCode.html delete mode 100644 data/core.telegram.org/constructor/messageEntityEmail.html delete mode 100644 data/core.telegram.org/constructor/messageEntityHashtag.html delete mode 100644 data/core.telegram.org/constructor/messageEntityItalic.html delete mode 100644 data/core.telegram.org/constructor/messageEntityMention.html delete mode 100644 data/core.telegram.org/constructor/messageEntityMentionName.html delete mode 100644 data/core.telegram.org/constructor/messageEntityPhone.html delete mode 100644 data/core.telegram.org/constructor/messageEntityPre.html delete mode 100644 data/core.telegram.org/constructor/messageEntityStrike.html delete mode 100644 data/core.telegram.org/constructor/messageEntityTextUrl.html delete mode 100644 data/core.telegram.org/constructor/messageEntityUnderline.html delete mode 100644 data/core.telegram.org/constructor/messageEntityUnknown.html delete mode 100644 data/core.telegram.org/constructor/messageEntityUrl.html delete mode 100644 data/core.telegram.org/constructor/messageFwdHeader.html delete mode 100644 data/core.telegram.org/constructor/messageInteractionCounters.html delete mode 100644 data/core.telegram.org/constructor/messageMediaAudio.html delete mode 100644 data/core.telegram.org/constructor/messageMediaContact.html delete mode 100644 data/core.telegram.org/constructor/messageMediaDice.html delete mode 100644 data/core.telegram.org/constructor/messageMediaDocument.html delete mode 100644 data/core.telegram.org/constructor/messageMediaEmpty.html delete mode 100644 data/core.telegram.org/constructor/messageMediaGame.html delete mode 100644 data/core.telegram.org/constructor/messageMediaGeo.html delete mode 100644 data/core.telegram.org/constructor/messageMediaGeoLive.html delete mode 100644 data/core.telegram.org/constructor/messageMediaInvoice.html delete mode 100644 data/core.telegram.org/constructor/messageMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/messageMediaPoll.html delete mode 100644 data/core.telegram.org/constructor/messageMediaUnsupported.html delete mode 100644 data/core.telegram.org/constructor/messageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/messageMediaVideo.html delete mode 100644 data/core.telegram.org/constructor/messageMediaWebPage.html delete mode 100644 data/core.telegram.org/constructor/messageRange.html delete mode 100644 data/core.telegram.org/constructor/messageReplies.html delete mode 100644 data/core.telegram.org/constructor/messageReplyHeader.html delete mode 100644 data/core.telegram.org/constructor/messageService.html delete mode 100644 data/core.telegram.org/constructor/messageUserVote.html delete mode 100644 data/core.telegram.org/constructor/messageUserVoteInputOption.html delete mode 100644 data/core.telegram.org/constructor/messageUserVoteMultiple.html delete mode 100644 data/core.telegram.org/constructor/messageViews.html delete mode 100644 data/core.telegram.org/constructor/messages.affectedHistory delete mode 100644 data/core.telegram.org/constructor/messages.affectedMessages delete mode 100644 data/core.telegram.org/constructor/messages.allStickers delete mode 100644 data/core.telegram.org/constructor/messages.allStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.archivedStickers delete mode 100644 data/core.telegram.org/constructor/messages.botCallbackAnswer delete mode 100644 data/core.telegram.org/constructor/messages.botResults delete mode 100644 data/core.telegram.org/constructor/messages.channelMessages delete mode 100644 data/core.telegram.org/constructor/messages.chatFull delete mode 100644 data/core.telegram.org/constructor/messages.chats delete mode 100644 data/core.telegram.org/constructor/messages.chatsSlice delete mode 100644 data/core.telegram.org/constructor/messages.dhConfig delete mode 100644 data/core.telegram.org/constructor/messages.dhConfigNotModified delete mode 100644 data/core.telegram.org/constructor/messages.dialogs delete mode 100644 data/core.telegram.org/constructor/messages.dialogsNotModified delete mode 100644 data/core.telegram.org/constructor/messages.dialogsSlice delete mode 100644 data/core.telegram.org/constructor/messages.discussionMessage delete mode 100644 data/core.telegram.org/constructor/messages.favedStickers delete mode 100644 data/core.telegram.org/constructor/messages.favedStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.featuredStickers delete mode 100644 data/core.telegram.org/constructor/messages.featuredStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.foundStickerSets delete mode 100644 data/core.telegram.org/constructor/messages.foundStickerSetsNotModified delete mode 100644 data/core.telegram.org/constructor/messages.highScores delete mode 100644 data/core.telegram.org/constructor/messages.inactiveChats delete mode 100644 data/core.telegram.org/constructor/messages.messageEditData delete mode 100644 data/core.telegram.org/constructor/messages.messageViews delete mode 100644 data/core.telegram.org/constructor/messages.messages delete mode 100644 data/core.telegram.org/constructor/messages.messagesNotModified delete mode 100644 data/core.telegram.org/constructor/messages.messagesSlice delete mode 100644 data/core.telegram.org/constructor/messages.peerDialogs delete mode 100644 data/core.telegram.org/constructor/messages.recentStickers delete mode 100644 data/core.telegram.org/constructor/messages.recentStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.savedGifs delete mode 100644 data/core.telegram.org/constructor/messages.savedGifsNotModified delete mode 100644 data/core.telegram.org/constructor/messages.searchCounter delete mode 100644 data/core.telegram.org/constructor/messages.sentEncryptedFile delete mode 100644 data/core.telegram.org/constructor/messages.sentEncryptedMessage delete mode 100644 data/core.telegram.org/constructor/messages.sentMessageLink delete mode 100644 data/core.telegram.org/constructor/messages.statedMessageLink delete mode 100644 data/core.telegram.org/constructor/messages.statedMessagesLinks delete mode 100644 data/core.telegram.org/constructor/messages.stickerSet delete mode 100644 data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive delete mode 100644 data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess delete mode 100644 data/core.telegram.org/constructor/messages.stickers delete mode 100644 data/core.telegram.org/constructor/messages.stickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.votesList delete mode 100644 data/core.telegram.org/constructor/nearestDc.html delete mode 100644 data/core.telegram.org/constructor/notifyBroadcasts.html delete mode 100644 data/core.telegram.org/constructor/notifyChats.html delete mode 100644 data/core.telegram.org/constructor/notifyPeer.html delete mode 100644 data/core.telegram.org/constructor/notifyUsers.html delete mode 100644 data/core.telegram.org/constructor/null.html delete mode 100644 data/core.telegram.org/constructor/page.html delete mode 100644 data/core.telegram.org/constructor/pageBlockAnchor.html delete mode 100644 data/core.telegram.org/constructor/pageBlockAudio.html delete mode 100644 data/core.telegram.org/constructor/pageBlockAuthorDate.html delete mode 100644 data/core.telegram.org/constructor/pageBlockBlockquote.html delete mode 100644 data/core.telegram.org/constructor/pageBlockChannel.html delete mode 100644 data/core.telegram.org/constructor/pageBlockCollage.html delete mode 100644 data/core.telegram.org/constructor/pageBlockCover.html delete mode 100644 data/core.telegram.org/constructor/pageBlockDetails.html delete mode 100644 data/core.telegram.org/constructor/pageBlockDivider.html delete mode 100644 data/core.telegram.org/constructor/pageBlockEmbed.html delete mode 100644 data/core.telegram.org/constructor/pageBlockEmbedPost.html delete mode 100644 data/core.telegram.org/constructor/pageBlockFooter.html delete mode 100644 data/core.telegram.org/constructor/pageBlockHeader.html delete mode 100644 data/core.telegram.org/constructor/pageBlockKicker.html delete mode 100644 data/core.telegram.org/constructor/pageBlockList.html delete mode 100644 data/core.telegram.org/constructor/pageBlockMap.html delete mode 100644 data/core.telegram.org/constructor/pageBlockOrderedList.html delete mode 100644 data/core.telegram.org/constructor/pageBlockParagraph.html delete mode 100644 data/core.telegram.org/constructor/pageBlockPhoto.html delete mode 100644 data/core.telegram.org/constructor/pageBlockPreformatted.html delete mode 100644 data/core.telegram.org/constructor/pageBlockPullquote.html delete mode 100644 data/core.telegram.org/constructor/pageBlockRelatedArticles.html delete mode 100644 data/core.telegram.org/constructor/pageBlockSlideshow.html delete mode 100644 data/core.telegram.org/constructor/pageBlockSubheader.html delete mode 100644 data/core.telegram.org/constructor/pageBlockSubtitle.html delete mode 100644 data/core.telegram.org/constructor/pageBlockTable.html delete mode 100644 data/core.telegram.org/constructor/pageBlockTitle.html delete mode 100644 data/core.telegram.org/constructor/pageBlockUnsupported.html delete mode 100644 data/core.telegram.org/constructor/pageBlockVideo.html delete mode 100644 data/core.telegram.org/constructor/pageCaption.html delete mode 100644 data/core.telegram.org/constructor/pageListItemBlocks.html delete mode 100644 data/core.telegram.org/constructor/pageListItemText.html delete mode 100644 data/core.telegram.org/constructor/pageListOrderedItemBlocks.html delete mode 100644 data/core.telegram.org/constructor/pageListOrderedItemText.html delete mode 100644 data/core.telegram.org/constructor/pageRelatedArticle.html delete mode 100644 data/core.telegram.org/constructor/pageTableCell.html delete mode 100644 data/core.telegram.org/constructor/pageTableRow.html delete mode 100644 data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html delete mode 100644 data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html delete mode 100644 data/core.telegram.org/constructor/paymentCharge.html delete mode 100644 data/core.telegram.org/constructor/paymentRequestedInfo.html delete mode 100644 data/core.telegram.org/constructor/paymentSavedCredentialsCard.html delete mode 100644 data/core.telegram.org/constructor/payments.ValidatedRequestedInfo delete mode 100644 data/core.telegram.org/constructor/payments.bankCardData delete mode 100644 data/core.telegram.org/constructor/payments.paymentForm delete mode 100644 data/core.telegram.org/constructor/payments.paymentReceipt delete mode 100644 data/core.telegram.org/constructor/payments.paymentResult delete mode 100644 data/core.telegram.org/constructor/payments.paymentVerificationNeeded delete mode 100644 data/core.telegram.org/constructor/payments.savedInfo delete mode 100644 data/core.telegram.org/constructor/peerBlocked.html delete mode 100644 data/core.telegram.org/constructor/peerChannel.html delete mode 100644 data/core.telegram.org/constructor/peerChat.html delete mode 100644 data/core.telegram.org/constructor/peerLocated.html delete mode 100644 data/core.telegram.org/constructor/peerNotifySettings.html delete mode 100644 data/core.telegram.org/constructor/peerSelfLocated.html delete mode 100644 data/core.telegram.org/constructor/peerSettings.html delete mode 100644 data/core.telegram.org/constructor/peerUser.html delete mode 100644 data/core.telegram.org/constructor/phone.phoneCall delete mode 100644 data/core.telegram.org/constructor/phoneCall.html delete mode 100644 data/core.telegram.org/constructor/phoneCallAccepted.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscarded.html delete mode 100644 data/core.telegram.org/constructor/phoneCallEmpty.html delete mode 100644 data/core.telegram.org/constructor/phoneCallProtocol.html delete mode 100644 data/core.telegram.org/constructor/phoneCallRequested.html delete mode 100644 data/core.telegram.org/constructor/phoneCallWaiting.html delete mode 100644 data/core.telegram.org/constructor/phoneConnection.html delete mode 100644 data/core.telegram.org/constructor/phoneConnectionWebrtc.html delete mode 100644 data/core.telegram.org/constructor/photo.html delete mode 100644 data/core.telegram.org/constructor/photoCachedSize.html delete mode 100644 data/core.telegram.org/constructor/photoEmpty.html delete mode 100644 data/core.telegram.org/constructor/photoPathSize.html delete mode 100644 data/core.telegram.org/constructor/photoSize.html delete mode 100644 data/core.telegram.org/constructor/photoSizeEmpty.html delete mode 100644 data/core.telegram.org/constructor/photoSizeProgressive.html delete mode 100644 data/core.telegram.org/constructor/photoStrippedSize.html delete mode 100644 data/core.telegram.org/constructor/photos.photo delete mode 100644 data/core.telegram.org/constructor/photos.photos delete mode 100644 data/core.telegram.org/constructor/photos.photosSlice delete mode 100644 data/core.telegram.org/constructor/poll.html delete mode 100644 data/core.telegram.org/constructor/pollAnswer.html delete mode 100644 data/core.telegram.org/constructor/pollAnswerVoters.html delete mode 100644 data/core.telegram.org/constructor/pollResults.html delete mode 100644 data/core.telegram.org/constructor/popularContact.html delete mode 100644 data/core.telegram.org/constructor/postAddress.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyAddedByPhone.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyChatInvite.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyForwards.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyPhoneCall.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyPhoneNumber.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyPhoneP2P.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyProfilePhoto.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html delete mode 100644 data/core.telegram.org/constructor/privacyValueAllowAll.html delete mode 100644 data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/privacyValueAllowContacts.html delete mode 100644 data/core.telegram.org/constructor/privacyValueAllowUsers.html delete mode 100644 data/core.telegram.org/constructor/privacyValueDisallowAll.html delete mode 100644 data/core.telegram.org/constructor/privacyValueDisallowChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/privacyValueDisallowContacts.html delete mode 100644 data/core.telegram.org/constructor/privacyValueDisallowUsers.html delete mode 100644 data/core.telegram.org/constructor/receivedNotifyMessage.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlChat.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlChatInvite.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlStickerSet.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlUnknown.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlUser.html delete mode 100644 data/core.telegram.org/constructor/replyInlineMarkup.html delete mode 100644 data/core.telegram.org/constructor/replyKeyboardForceReply.html delete mode 100644 data/core.telegram.org/constructor/replyKeyboardHide.html delete mode 100644 data/core.telegram.org/constructor/replyKeyboardMarkup.html delete mode 100644 data/core.telegram.org/constructor/restrictionReason.html delete mode 100644 data/core.telegram.org/constructor/savedPhoneContact.html delete mode 100644 data/core.telegram.org/constructor/secureCredentialsEncrypted.html delete mode 100644 data/core.telegram.org/constructor/secureData.html delete mode 100644 data/core.telegram.org/constructor/secureFile.html delete mode 100644 data/core.telegram.org/constructor/secureFileEmpty.html delete mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html delete mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html delete mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html delete mode 100644 data/core.telegram.org/constructor/securePlainEmail.html delete mode 100644 data/core.telegram.org/constructor/securePlainPhone.html delete mode 100644 data/core.telegram.org/constructor/secureRequiredType.html delete mode 100644 data/core.telegram.org/constructor/secureRequiredTypeOneOf.html delete mode 100644 data/core.telegram.org/constructor/secureSecretSettings.html delete mode 100644 data/core.telegram.org/constructor/secureValue.html delete mode 100644 data/core.telegram.org/constructor/secureValueError.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorData.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorFile.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorFiles.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorFrontSide.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorReverseSide.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorSelfie.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorTranslationFile.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html delete mode 100644 data/core.telegram.org/constructor/secureValueHash.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeAddress.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeBankStatement.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeDriverLicense.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeEmail.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeIdentityCard.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeInternalPassport.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePassport.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePassportRegistration.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePersonalDetails.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePhone.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeUtilityBill.html delete mode 100644 data/core.telegram.org/constructor/sendMessageCancelAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageChooseContactAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageGamePlayAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageGeoLocationAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageRecordAudioAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageRecordRoundAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageRecordVideoAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageTypingAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadAudioAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadRoundAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadVideoAction.html delete mode 100644 data/core.telegram.org/constructor/shippingOption.html delete mode 100644 data/core.telegram.org/constructor/stats.broadcastStats delete mode 100644 data/core.telegram.org/constructor/stats.megagroupStats delete mode 100644 data/core.telegram.org/constructor/stats.messageStats delete mode 100644 data/core.telegram.org/constructor/statsAbsValueAndPrev.html delete mode 100644 data/core.telegram.org/constructor/statsDateRangeDays.html delete mode 100644 data/core.telegram.org/constructor/statsGraph.html delete mode 100644 data/core.telegram.org/constructor/statsGraphAsync.html delete mode 100644 data/core.telegram.org/constructor/statsGraphError.html delete mode 100644 data/core.telegram.org/constructor/statsGroupTopAdmin.html delete mode 100644 data/core.telegram.org/constructor/statsGroupTopInviter.html delete mode 100644 data/core.telegram.org/constructor/statsGroupTopPoster.html delete mode 100644 data/core.telegram.org/constructor/statsPercentValue.html delete mode 100644 data/core.telegram.org/constructor/statsURL.html delete mode 100644 data/core.telegram.org/constructor/stickerPack.html delete mode 100644 data/core.telegram.org/constructor/stickerSet.html delete mode 100644 data/core.telegram.org/constructor/stickerSetCovered.html delete mode 100644 data/core.telegram.org/constructor/stickerSetMultiCovered.html delete mode 100644 data/core.telegram.org/constructor/storage.fileGif delete mode 100644 data/core.telegram.org/constructor/storage.fileJpeg delete mode 100644 data/core.telegram.org/constructor/storage.fileMov delete mode 100644 data/core.telegram.org/constructor/storage.fileMp3 delete mode 100644 data/core.telegram.org/constructor/storage.fileMp4 delete mode 100644 data/core.telegram.org/constructor/storage.filePartial delete mode 100644 data/core.telegram.org/constructor/storage.filePdf delete mode 100644 data/core.telegram.org/constructor/storage.filePng delete mode 100644 data/core.telegram.org/constructor/storage.fileUnknown delete mode 100644 data/core.telegram.org/constructor/storage.fileWebp delete mode 100644 data/core.telegram.org/constructor/textAnchor.html delete mode 100644 data/core.telegram.org/constructor/textBold.html delete mode 100644 data/core.telegram.org/constructor/textConcat.html delete mode 100644 data/core.telegram.org/constructor/textEmail.html delete mode 100644 data/core.telegram.org/constructor/textEmpty.html delete mode 100644 data/core.telegram.org/constructor/textFixed.html delete mode 100644 data/core.telegram.org/constructor/textImage.html delete mode 100644 data/core.telegram.org/constructor/textItalic.html delete mode 100644 data/core.telegram.org/constructor/textMarked.html delete mode 100644 data/core.telegram.org/constructor/textPhone.html delete mode 100644 data/core.telegram.org/constructor/textPlain.html delete mode 100644 data/core.telegram.org/constructor/textStrike.html delete mode 100644 data/core.telegram.org/constructor/textSubscript.html delete mode 100644 data/core.telegram.org/constructor/textSuperscript.html delete mode 100644 data/core.telegram.org/constructor/textUnderline.html delete mode 100644 data/core.telegram.org/constructor/textUrl.html delete mode 100644 data/core.telegram.org/constructor/theme.html delete mode 100644 data/core.telegram.org/constructor/themeSettings.html delete mode 100644 data/core.telegram.org/constructor/topPeer.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryBotsInline.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryBotsPM.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryChannels.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryForwardChats.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryGroups.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryPeers.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html delete mode 100644 data/core.telegram.org/constructor/true.html delete mode 100644 data/core.telegram.org/constructor/updateBotCallbackQuery.html delete mode 100644 data/core.telegram.org/constructor/updateBotInlineQuery.html delete mode 100644 data/core.telegram.org/constructor/updateBotInlineSend.html delete mode 100644 data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html delete mode 100644 data/core.telegram.org/constructor/updateBotShippingQuery.html delete mode 100644 data/core.telegram.org/constructor/updateBotWebhookJSON.html delete mode 100644 data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html delete mode 100644 data/core.telegram.org/constructor/updateChannel.html delete mode 100644 data/core.telegram.org/constructor/updateChannelAvailableMessages.html delete mode 100644 data/core.telegram.org/constructor/updateChannelMessageForwards.html delete mode 100644 data/core.telegram.org/constructor/updateChannelMessageViews.html delete mode 100644 data/core.telegram.org/constructor/updateChannelParticipant.html delete mode 100644 data/core.telegram.org/constructor/updateChannelReadMessagesContents.html delete mode 100644 data/core.telegram.org/constructor/updateChannelTooLong.html delete mode 100644 data/core.telegram.org/constructor/updateChannelUserTyping.html delete mode 100644 data/core.telegram.org/constructor/updateChannelWebPage.html delete mode 100644 data/core.telegram.org/constructor/updateChatDefaultBannedRights.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipantAdd.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipantAdmin.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipantDelete.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/updateChatUserTyping.html delete mode 100644 data/core.telegram.org/constructor/updateConfig.html delete mode 100644 data/core.telegram.org/constructor/updateContactsReset.html delete mode 100644 data/core.telegram.org/constructor/updateDcOptions.html delete mode 100644 data/core.telegram.org/constructor/updateDeleteChannelMessages.html delete mode 100644 data/core.telegram.org/constructor/updateDeleteMessages.html delete mode 100644 data/core.telegram.org/constructor/updateDeleteScheduledMessages.html delete mode 100644 data/core.telegram.org/constructor/updateDialogFilter.html delete mode 100644 data/core.telegram.org/constructor/updateDialogFilterOrder.html delete mode 100644 data/core.telegram.org/constructor/updateDialogFilters.html delete mode 100644 data/core.telegram.org/constructor/updateDialogPinned.html delete mode 100644 data/core.telegram.org/constructor/updateDialogUnreadMark.html delete mode 100644 data/core.telegram.org/constructor/updateDraftMessage.html delete mode 100644 data/core.telegram.org/constructor/updateEditChannelMessage.html delete mode 100644 data/core.telegram.org/constructor/updateEditMessage.html delete mode 100644 data/core.telegram.org/constructor/updateEncryptedChatTyping.html delete mode 100644 data/core.telegram.org/constructor/updateEncryptedMessagesRead.html delete mode 100644 data/core.telegram.org/constructor/updateEncryption.html delete mode 100644 data/core.telegram.org/constructor/updateFavedStickers.html delete mode 100644 data/core.telegram.org/constructor/updateFolderPeers.html delete mode 100644 data/core.telegram.org/constructor/updateGeoLiveViewed.html delete mode 100644 data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html delete mode 100644 data/core.telegram.org/constructor/updateLangPack.html delete mode 100644 data/core.telegram.org/constructor/updateLangPackTooLong.html delete mode 100644 data/core.telegram.org/constructor/updateLoginToken.html delete mode 100644 data/core.telegram.org/constructor/updateMessageID.html delete mode 100644 data/core.telegram.org/constructor/updateMessagePoll.html delete mode 100644 data/core.telegram.org/constructor/updateMessagePollVote.html delete mode 100644 data/core.telegram.org/constructor/updateNewChannelMessage.html delete mode 100644 data/core.telegram.org/constructor/updateNewEncryptedMessage.html delete mode 100644 data/core.telegram.org/constructor/updateNewMessage.html delete mode 100644 data/core.telegram.org/constructor/updateNewScheduledMessage.html delete mode 100644 data/core.telegram.org/constructor/updateNewStickerSet.html delete mode 100644 data/core.telegram.org/constructor/updateNotifySettings.html delete mode 100644 data/core.telegram.org/constructor/updatePeerBlocked.html delete mode 100644 data/core.telegram.org/constructor/updatePeerLocated.html delete mode 100644 data/core.telegram.org/constructor/updatePeerSettings.html delete mode 100644 data/core.telegram.org/constructor/updatePhoneCall.html delete mode 100644 data/core.telegram.org/constructor/updatePhoneCallSignalingData.html delete mode 100644 data/core.telegram.org/constructor/updatePinnedChannelMessages.html delete mode 100644 data/core.telegram.org/constructor/updatePinnedDialogs.html delete mode 100644 data/core.telegram.org/constructor/updatePinnedMessages.html delete mode 100644 data/core.telegram.org/constructor/updatePrivacy.html delete mode 100644 data/core.telegram.org/constructor/updatePtsChanged.html delete mode 100644 data/core.telegram.org/constructor/updateReadChannelDiscussionInbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadChannelInbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadChannelOutbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadFeaturedStickers.html delete mode 100644 data/core.telegram.org/constructor/updateReadHistoryInbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadHistoryOutbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadMessagesContents.html delete mode 100644 data/core.telegram.org/constructor/updateRecentStickers.html delete mode 100644 data/core.telegram.org/constructor/updateSavedGifs.html delete mode 100644 data/core.telegram.org/constructor/updateServiceNotification.html delete mode 100644 data/core.telegram.org/constructor/updateShort.html delete mode 100644 data/core.telegram.org/constructor/updateShortChatMessage.html delete mode 100644 data/core.telegram.org/constructor/updateShortMessage.html delete mode 100644 data/core.telegram.org/constructor/updateShortSentMessage.html delete mode 100644 data/core.telegram.org/constructor/updateStickerSets.html delete mode 100644 data/core.telegram.org/constructor/updateStickerSetsOrder.html delete mode 100644 data/core.telegram.org/constructor/updateTheme.html delete mode 100644 data/core.telegram.org/constructor/updateUserBlocked.html delete mode 100644 data/core.telegram.org/constructor/updateUserName.html delete mode 100644 data/core.telegram.org/constructor/updateUserPhone.html delete mode 100644 data/core.telegram.org/constructor/updateUserPhoto.html delete mode 100644 data/core.telegram.org/constructor/updateUserStatus.html delete mode 100644 data/core.telegram.org/constructor/updateUserTyping.html delete mode 100644 data/core.telegram.org/constructor/updateWebPage.html delete mode 100644 data/core.telegram.org/constructor/updates.channelDifference delete mode 100644 data/core.telegram.org/constructor/updates.channelDifferenceEmpty delete mode 100644 data/core.telegram.org/constructor/updates.channelDifferenceTooLong delete mode 100644 data/core.telegram.org/constructor/updates.difference delete mode 100644 data/core.telegram.org/constructor/updates.differenceEmpty delete mode 100644 data/core.telegram.org/constructor/updates.differenceSlice delete mode 100644 data/core.telegram.org/constructor/updates.differenceTooLong delete mode 100644 data/core.telegram.org/constructor/updates.html delete mode 100644 data/core.telegram.org/constructor/updates.state delete mode 100644 data/core.telegram.org/constructor/updatesCombined.html delete mode 100644 data/core.telegram.org/constructor/updatesTooLong.html delete mode 100644 data/core.telegram.org/constructor/upload.cdnFile delete mode 100644 data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded delete mode 100644 data/core.telegram.org/constructor/upload.file delete mode 100644 data/core.telegram.org/constructor/upload.fileCdnRedirect delete mode 100644 data/core.telegram.org/constructor/upload.webFile delete mode 100644 data/core.telegram.org/constructor/urlAuthResultAccepted.html delete mode 100644 data/core.telegram.org/constructor/urlAuthResultDefault.html delete mode 100644 data/core.telegram.org/constructor/urlAuthResultRequest.html delete mode 100644 data/core.telegram.org/constructor/user.html delete mode 100644 data/core.telegram.org/constructor/userEmpty.html delete mode 100644 data/core.telegram.org/constructor/userForeign.html delete mode 100644 data/core.telegram.org/constructor/userFull.html delete mode 100644 data/core.telegram.org/constructor/userProfilePhoto.html delete mode 100644 data/core.telegram.org/constructor/userProfilePhotoEmpty.html delete mode 100644 data/core.telegram.org/constructor/userRequest.html delete mode 100644 data/core.telegram.org/constructor/userStatusEmpty.html delete mode 100644 data/core.telegram.org/constructor/userStatusLastMonth.html delete mode 100644 data/core.telegram.org/constructor/userStatusLastWeek.html delete mode 100644 data/core.telegram.org/constructor/userStatusOffline.html delete mode 100644 data/core.telegram.org/constructor/userStatusOnline.html delete mode 100644 data/core.telegram.org/constructor/userStatusRecently.html delete mode 100644 data/core.telegram.org/constructor/vector.html delete mode 100644 data/core.telegram.org/constructor/videoSize.html delete mode 100644 data/core.telegram.org/constructor/wallPaper.html delete mode 100644 data/core.telegram.org/constructor/wallPaperNoFile.html delete mode 100644 data/core.telegram.org/constructor/wallPaperSettings.html delete mode 100644 data/core.telegram.org/constructor/wallPaperSolid.html delete mode 100644 data/core.telegram.org/constructor/webAuthorization.html delete mode 100644 data/core.telegram.org/constructor/webDocument.html delete mode 100644 data/core.telegram.org/constructor/webDocumentNoProxy.html delete mode 100644 data/core.telegram.org/constructor/webPage.html delete mode 100644 data/core.telegram.org/constructor/webPageAttributeTheme.html delete mode 100644 data/core.telegram.org/constructor/webPageEmpty.html delete mode 100644 data/core.telegram.org/constructor/webPageNotModified.html delete mode 100644 data/core.telegram.org/constructor/webPagePending.html delete mode 100644 data/core.telegram.org/contest300K.html delete mode 100644 data/core.telegram.org/contestfaq.html delete mode 100644 data/core.telegram.org/css/bootstrap-extra.css delete mode 100644 data/core.telegram.org/css/bootstrap.min.css delete mode 100644 data/core.telegram.org/css/core-widgets.css delete mode 100644 data/core.telegram.org/css/telegram-extra.css delete mode 100644 data/core.telegram.org/css/telegram.css delete mode 100644 data/core.telegram.org/import-stickers.html delete mode 100644 data/core.telegram.org/js/bootstrap.min.js delete mode 100644 data/core.telegram.org/js/core-widgets.js delete mode 100644 data/core.telegram.org/js/jquery-ui.min.js delete mode 100644 data/core.telegram.org/js/jquery.min.js delete mode 100644 data/core.telegram.org/js/main.js delete mode 100644 data/core.telegram.org/js/telegram-passport2.js delete mode 100644 data/core.telegram.org/method/account.acceptAuthorization delete mode 100644 data/core.telegram.org/method/account.cancelPasswordEmail delete mode 100644 data/core.telegram.org/method/account.changePhone delete mode 100644 data/core.telegram.org/method/account.checkUsername delete mode 100644 data/core.telegram.org/method/account.confirmPasswordEmail delete mode 100644 data/core.telegram.org/method/account.confirmPhone delete mode 100644 data/core.telegram.org/method/account.createTheme delete mode 100644 data/core.telegram.org/method/account.deleteAccount delete mode 100644 data/core.telegram.org/method/account.deleteSecureValue delete mode 100644 data/core.telegram.org/method/account.finishTakeoutSession delete mode 100644 data/core.telegram.org/method/account.getAccountTTL delete mode 100644 data/core.telegram.org/method/account.getAllSecureValues delete mode 100644 data/core.telegram.org/method/account.getAuthorizationForm delete mode 100644 data/core.telegram.org/method/account.getAuthorizations delete mode 100644 data/core.telegram.org/method/account.getAutoDownloadSettings delete mode 100644 data/core.telegram.org/method/account.getContactSignUpNotification delete mode 100644 data/core.telegram.org/method/account.getContentSettings delete mode 100644 data/core.telegram.org/method/account.getGlobalPrivacySettings delete mode 100644 data/core.telegram.org/method/account.getMultiWallPapers delete mode 100644 data/core.telegram.org/method/account.getNotifyExceptions delete mode 100644 data/core.telegram.org/method/account.getNotifySettings delete mode 100644 data/core.telegram.org/method/account.getPassword delete mode 100644 data/core.telegram.org/method/account.getPasswordSettings delete mode 100644 data/core.telegram.org/method/account.getPrivacy delete mode 100644 data/core.telegram.org/method/account.getSecureValue delete mode 100644 data/core.telegram.org/method/account.getTheme delete mode 100644 data/core.telegram.org/method/account.getThemes delete mode 100644 data/core.telegram.org/method/account.getTmpPassword delete mode 100644 data/core.telegram.org/method/account.getWallPaper delete mode 100644 data/core.telegram.org/method/account.getWallPapers delete mode 100644 data/core.telegram.org/method/account.getWebAuthorizations delete mode 100644 data/core.telegram.org/method/account.initTakeoutSession delete mode 100644 data/core.telegram.org/method/account.installTheme delete mode 100644 data/core.telegram.org/method/account.installWallPaper delete mode 100644 data/core.telegram.org/method/account.registerDevice delete mode 100644 data/core.telegram.org/method/account.reportPeer delete mode 100644 data/core.telegram.org/method/account.resendPasswordEmail delete mode 100644 data/core.telegram.org/method/account.resetAuthorization delete mode 100644 data/core.telegram.org/method/account.resetNotifySettings delete mode 100644 data/core.telegram.org/method/account.resetWallPapers delete mode 100644 data/core.telegram.org/method/account.resetWebAuthorization delete mode 100644 data/core.telegram.org/method/account.resetWebAuthorizations delete mode 100644 data/core.telegram.org/method/account.saveAutoDownloadSettings delete mode 100644 data/core.telegram.org/method/account.saveSecureValue delete mode 100644 data/core.telegram.org/method/account.saveTheme delete mode 100644 data/core.telegram.org/method/account.saveWallPaper delete mode 100644 data/core.telegram.org/method/account.sendChangePhoneCode delete mode 100644 data/core.telegram.org/method/account.sendConfirmPhoneCode delete mode 100644 data/core.telegram.org/method/account.sendVerifyEmailCode delete mode 100644 data/core.telegram.org/method/account.sendVerifyPhoneCode delete mode 100644 data/core.telegram.org/method/account.setAccountTTL delete mode 100644 data/core.telegram.org/method/account.setContactSignUpNotification delete mode 100644 data/core.telegram.org/method/account.setContentSettings delete mode 100644 data/core.telegram.org/method/account.setGlobalPrivacySettings delete mode 100644 data/core.telegram.org/method/account.setPrivacy delete mode 100644 data/core.telegram.org/method/account.unregisterDevice delete mode 100644 data/core.telegram.org/method/account.updateDeviceLocked delete mode 100644 data/core.telegram.org/method/account.updateNotifySettings delete mode 100644 data/core.telegram.org/method/account.updatePasswordSettings delete mode 100644 data/core.telegram.org/method/account.updateProfile delete mode 100644 data/core.telegram.org/method/account.updateStatus delete mode 100644 data/core.telegram.org/method/account.updateTheme delete mode 100644 data/core.telegram.org/method/account.updateUsername delete mode 100644 data/core.telegram.org/method/account.uploadTheme delete mode 100644 data/core.telegram.org/method/account.uploadWallPaper delete mode 100644 data/core.telegram.org/method/account.verifyEmail delete mode 100644 data/core.telegram.org/method/account.verifyPhone delete mode 100644 data/core.telegram.org/method/auth.acceptLoginToken delete mode 100644 data/core.telegram.org/method/auth.bindTempAuthKey delete mode 100644 data/core.telegram.org/method/auth.cancelCode delete mode 100644 data/core.telegram.org/method/auth.checkPassword delete mode 100644 data/core.telegram.org/method/auth.checkPhone delete mode 100644 data/core.telegram.org/method/auth.dropTempAuthKeys delete mode 100644 data/core.telegram.org/method/auth.exportAuthorization delete mode 100644 data/core.telegram.org/method/auth.exportLoginToken delete mode 100644 data/core.telegram.org/method/auth.importAuthorization delete mode 100644 data/core.telegram.org/method/auth.importBotAuthorization delete mode 100644 data/core.telegram.org/method/auth.importLoginToken delete mode 100644 data/core.telegram.org/method/auth.logOut delete mode 100644 data/core.telegram.org/method/auth.recoverPassword delete mode 100644 data/core.telegram.org/method/auth.requestPasswordRecovery delete mode 100644 data/core.telegram.org/method/auth.resendCode delete mode 100644 data/core.telegram.org/method/auth.resetAuthorizations delete mode 100644 data/core.telegram.org/method/auth.sendCall delete mode 100644 data/core.telegram.org/method/auth.sendCode delete mode 100644 data/core.telegram.org/method/auth.sendInvites delete mode 100644 data/core.telegram.org/method/auth.sendSms delete mode 100644 data/core.telegram.org/method/auth.signIn delete mode 100644 data/core.telegram.org/method/auth.signUp delete mode 100644 data/core.telegram.org/method/bots.answerWebhookJSONQuery delete mode 100644 data/core.telegram.org/method/bots.sendCustomRequest delete mode 100644 data/core.telegram.org/method/bots.setBotCommands delete mode 100644 data/core.telegram.org/method/channels.checkUsername delete mode 100644 data/core.telegram.org/method/channels.createChannel delete mode 100644 data/core.telegram.org/method/channels.deleteChannel delete mode 100644 data/core.telegram.org/method/channels.deleteHistory delete mode 100644 data/core.telegram.org/method/channels.deleteMessages delete mode 100644 data/core.telegram.org/method/channels.deleteUserHistory delete mode 100644 data/core.telegram.org/method/channels.editAdmin delete mode 100644 data/core.telegram.org/method/channels.editBanned delete mode 100644 data/core.telegram.org/method/channels.editCreator delete mode 100644 data/core.telegram.org/method/channels.editLocation delete mode 100644 data/core.telegram.org/method/channels.editPhoto delete mode 100644 data/core.telegram.org/method/channels.editTitle delete mode 100644 data/core.telegram.org/method/channels.exportMessageLink delete mode 100644 data/core.telegram.org/method/channels.getAdminLog delete mode 100644 data/core.telegram.org/method/channels.getAdminedPublicChannels delete mode 100644 data/core.telegram.org/method/channels.getChannels delete mode 100644 data/core.telegram.org/method/channels.getFullChannel delete mode 100644 data/core.telegram.org/method/channels.getGroupsForDiscussion delete mode 100644 data/core.telegram.org/method/channels.getInactiveChannels delete mode 100644 data/core.telegram.org/method/channels.getLeftChannels delete mode 100644 data/core.telegram.org/method/channels.getMessages delete mode 100644 data/core.telegram.org/method/channels.getParticipant delete mode 100644 data/core.telegram.org/method/channels.getParticipants delete mode 100644 data/core.telegram.org/method/channels.inviteToChannel delete mode 100644 data/core.telegram.org/method/channels.joinChannel delete mode 100644 data/core.telegram.org/method/channels.leaveChannel delete mode 100644 data/core.telegram.org/method/channels.readHistory delete mode 100644 data/core.telegram.org/method/channels.readMessageContents delete mode 100644 data/core.telegram.org/method/channels.reportSpam delete mode 100644 data/core.telegram.org/method/channels.setDiscussionGroup delete mode 100644 data/core.telegram.org/method/channels.setStickers delete mode 100644 data/core.telegram.org/method/channels.togglePreHistoryHidden delete mode 100644 data/core.telegram.org/method/channels.toggleSignatures delete mode 100644 data/core.telegram.org/method/channels.toggleSlowMode delete mode 100644 data/core.telegram.org/method/channels.updateUsername delete mode 100644 data/core.telegram.org/method/contacts.acceptContact delete mode 100644 data/core.telegram.org/method/contacts.addContact delete mode 100644 data/core.telegram.org/method/contacts.block delete mode 100644 data/core.telegram.org/method/contacts.blockFromReplies delete mode 100644 data/core.telegram.org/method/contacts.deleteByPhones delete mode 100644 data/core.telegram.org/method/contacts.deleteContacts delete mode 100644 data/core.telegram.org/method/contacts.getBlocked delete mode 100644 data/core.telegram.org/method/contacts.getContactIDs delete mode 100644 data/core.telegram.org/method/contacts.getContacts delete mode 100644 data/core.telegram.org/method/contacts.getLocated delete mode 100644 data/core.telegram.org/method/contacts.getSaved delete mode 100644 data/core.telegram.org/method/contacts.getStatuses delete mode 100644 data/core.telegram.org/method/contacts.getTopPeers delete mode 100644 data/core.telegram.org/method/contacts.importContacts delete mode 100644 data/core.telegram.org/method/contacts.resetSaved delete mode 100644 data/core.telegram.org/method/contacts.resetTopPeerRating delete mode 100644 data/core.telegram.org/method/contacts.resolveUsername delete mode 100644 data/core.telegram.org/method/contacts.search delete mode 100644 data/core.telegram.org/method/contacts.toggleTopPeers delete mode 100644 data/core.telegram.org/method/contacts.unblock delete mode 100644 data/core.telegram.org/method/folders.deleteFolder delete mode 100644 data/core.telegram.org/method/folders.editPeerFolders delete mode 100644 data/core.telegram.org/method/help.acceptTermsOfService delete mode 100644 data/core.telegram.org/method/help.dismissSuggestion delete mode 100644 data/core.telegram.org/method/help.editUserInfo delete mode 100644 data/core.telegram.org/method/help.getAppChangelog delete mode 100644 data/core.telegram.org/method/help.getAppConfig delete mode 100644 data/core.telegram.org/method/help.getAppUpdate delete mode 100644 data/core.telegram.org/method/help.getCdnConfig delete mode 100644 data/core.telegram.org/method/help.getConfig delete mode 100644 data/core.telegram.org/method/help.getCountriesList delete mode 100644 data/core.telegram.org/method/help.getDeepLinkInfo delete mode 100644 data/core.telegram.org/method/help.getInviteText delete mode 100644 data/core.telegram.org/method/help.getNearestDc delete mode 100644 data/core.telegram.org/method/help.getPassportConfig delete mode 100644 data/core.telegram.org/method/help.getPromoData delete mode 100644 data/core.telegram.org/method/help.getProxyData delete mode 100644 data/core.telegram.org/method/help.getRecentMeUrls delete mode 100644 data/core.telegram.org/method/help.getSupport delete mode 100644 data/core.telegram.org/method/help.getSupportName delete mode 100644 data/core.telegram.org/method/help.getTermsOfServiceUpdate delete mode 100644 data/core.telegram.org/method/help.getUserInfo delete mode 100644 data/core.telegram.org/method/help.hidePromoData delete mode 100644 data/core.telegram.org/method/help.saveAppLog delete mode 100644 data/core.telegram.org/method/help.setBotUpdatesStatus delete mode 100644 data/core.telegram.org/method/initConnection.html delete mode 100644 data/core.telegram.org/method/invokeAfterMsg.html delete mode 100644 data/core.telegram.org/method/invokeAfterMsgs.html delete mode 100644 data/core.telegram.org/method/invokeWithLayer.html delete mode 100644 data/core.telegram.org/method/invokeWithMessagesRange.html delete mode 100644 data/core.telegram.org/method/invokeWithTakeout.html delete mode 100644 data/core.telegram.org/method/invokeWithoutUpdates.html delete mode 100644 data/core.telegram.org/method/langpack.getDifference delete mode 100644 data/core.telegram.org/method/langpack.getLangPack delete mode 100644 data/core.telegram.org/method/langpack.getLanguage delete mode 100644 data/core.telegram.org/method/langpack.getLanguages delete mode 100644 data/core.telegram.org/method/langpack.getStrings delete mode 100644 data/core.telegram.org/method/messages.acceptEncryption delete mode 100644 data/core.telegram.org/method/messages.acceptUrlAuth delete mode 100644 data/core.telegram.org/method/messages.addChatUser delete mode 100644 data/core.telegram.org/method/messages.checkChatInvite delete mode 100644 data/core.telegram.org/method/messages.clearAllDrafts delete mode 100644 data/core.telegram.org/method/messages.clearRecentStickers delete mode 100644 data/core.telegram.org/method/messages.createChat delete mode 100644 data/core.telegram.org/method/messages.deleteChatUser delete mode 100644 data/core.telegram.org/method/messages.deleteHistory delete mode 100644 data/core.telegram.org/method/messages.deleteMessages delete mode 100644 data/core.telegram.org/method/messages.deleteScheduledMessages delete mode 100644 data/core.telegram.org/method/messages.discardEncryption delete mode 100644 data/core.telegram.org/method/messages.editChatAbout delete mode 100644 data/core.telegram.org/method/messages.editChatAdmin delete mode 100644 data/core.telegram.org/method/messages.editChatDefaultBannedRights delete mode 100644 data/core.telegram.org/method/messages.editChatPhoto delete mode 100644 data/core.telegram.org/method/messages.editChatTitle delete mode 100644 data/core.telegram.org/method/messages.editInlineBotMessage delete mode 100644 data/core.telegram.org/method/messages.editMessage delete mode 100644 data/core.telegram.org/method/messages.exportChatInvite delete mode 100644 data/core.telegram.org/method/messages.faveSticker delete mode 100644 data/core.telegram.org/method/messages.forwardMessage delete mode 100644 data/core.telegram.org/method/messages.forwardMessages delete mode 100644 data/core.telegram.org/method/messages.getAllChats delete mode 100644 data/core.telegram.org/method/messages.getAllDrafts delete mode 100644 data/core.telegram.org/method/messages.getAllStickers delete mode 100644 data/core.telegram.org/method/messages.getArchivedStickers delete mode 100644 data/core.telegram.org/method/messages.getAttachedStickers delete mode 100644 data/core.telegram.org/method/messages.getBotCallbackAnswer delete mode 100644 data/core.telegram.org/method/messages.getChats delete mode 100644 data/core.telegram.org/method/messages.getCommonChats delete mode 100644 data/core.telegram.org/method/messages.getDhConfig delete mode 100644 data/core.telegram.org/method/messages.getDialogFilters delete mode 100644 data/core.telegram.org/method/messages.getDialogUnreadMarks delete mode 100644 data/core.telegram.org/method/messages.getDialogs delete mode 100644 data/core.telegram.org/method/messages.getDiscussionMessage delete mode 100644 data/core.telegram.org/method/messages.getDocumentByHash delete mode 100644 data/core.telegram.org/method/messages.getEmojiKeywords delete mode 100644 data/core.telegram.org/method/messages.getEmojiKeywordsDifference delete mode 100644 data/core.telegram.org/method/messages.getEmojiKeywordsLanguages delete mode 100644 data/core.telegram.org/method/messages.getEmojiURL delete mode 100644 data/core.telegram.org/method/messages.getFavedStickers delete mode 100644 data/core.telegram.org/method/messages.getFeaturedStickers delete mode 100644 data/core.telegram.org/method/messages.getFullChat delete mode 100644 data/core.telegram.org/method/messages.getGameHighScores delete mode 100644 data/core.telegram.org/method/messages.getHistory delete mode 100644 data/core.telegram.org/method/messages.getInlineBotResults delete mode 100644 data/core.telegram.org/method/messages.getInlineGameHighScores delete mode 100644 data/core.telegram.org/method/messages.getMaskStickers delete mode 100644 data/core.telegram.org/method/messages.getMessageEditData delete mode 100644 data/core.telegram.org/method/messages.getMessageReactionsList delete mode 100644 data/core.telegram.org/method/messages.getMessages delete mode 100644 data/core.telegram.org/method/messages.getMessagesReactions delete mode 100644 data/core.telegram.org/method/messages.getMessagesViews delete mode 100644 data/core.telegram.org/method/messages.getOldFeaturedStickers delete mode 100644 data/core.telegram.org/method/messages.getOnlines delete mode 100644 data/core.telegram.org/method/messages.getPeerDialogs delete mode 100644 data/core.telegram.org/method/messages.getPeerSettings delete mode 100644 data/core.telegram.org/method/messages.getPinnedDialogs delete mode 100644 data/core.telegram.org/method/messages.getPollResults delete mode 100644 data/core.telegram.org/method/messages.getPollVotes delete mode 100644 data/core.telegram.org/method/messages.getRecentLocations delete mode 100644 data/core.telegram.org/method/messages.getRecentStickers delete mode 100644 data/core.telegram.org/method/messages.getReplies delete mode 100644 data/core.telegram.org/method/messages.getSavedGifs delete mode 100644 data/core.telegram.org/method/messages.getScheduledHistory delete mode 100644 data/core.telegram.org/method/messages.getScheduledMessages delete mode 100644 data/core.telegram.org/method/messages.getSearchCounters delete mode 100644 data/core.telegram.org/method/messages.getSplitRanges delete mode 100644 data/core.telegram.org/method/messages.getStatsURL delete mode 100644 data/core.telegram.org/method/messages.getStickerSet delete mode 100644 data/core.telegram.org/method/messages.getStickers delete mode 100644 data/core.telegram.org/method/messages.getSuggestedDialogFilters delete mode 100644 data/core.telegram.org/method/messages.getUnreadMentions delete mode 100644 data/core.telegram.org/method/messages.getWebPage delete mode 100644 data/core.telegram.org/method/messages.getWebPagePreview delete mode 100644 data/core.telegram.org/method/messages.hidePeerSettingsBar delete mode 100644 data/core.telegram.org/method/messages.importChatInvite delete mode 100644 data/core.telegram.org/method/messages.installStickerSet delete mode 100644 data/core.telegram.org/method/messages.markDialogUnread delete mode 100644 data/core.telegram.org/method/messages.migrateChat delete mode 100644 data/core.telegram.org/method/messages.readDiscussion delete mode 100644 data/core.telegram.org/method/messages.readEncryptedHistory delete mode 100644 data/core.telegram.org/method/messages.readFeaturedStickers delete mode 100644 data/core.telegram.org/method/messages.readHistory delete mode 100644 data/core.telegram.org/method/messages.readMentions delete mode 100644 data/core.telegram.org/method/messages.readMessageContents delete mode 100644 data/core.telegram.org/method/messages.receivedMessages delete mode 100644 data/core.telegram.org/method/messages.receivedQueue delete mode 100644 data/core.telegram.org/method/messages.reorderPinnedDialogs delete mode 100644 data/core.telegram.org/method/messages.reorderStickerSets delete mode 100644 data/core.telegram.org/method/messages.report delete mode 100644 data/core.telegram.org/method/messages.reportEncryptedSpam delete mode 100644 data/core.telegram.org/method/messages.reportSpam delete mode 100644 data/core.telegram.org/method/messages.requestEncryption delete mode 100644 data/core.telegram.org/method/messages.requestUrlAuth delete mode 100644 data/core.telegram.org/method/messages.saveDraft delete mode 100644 data/core.telegram.org/method/messages.saveGif delete mode 100644 data/core.telegram.org/method/messages.saveRecentSticker delete mode 100644 data/core.telegram.org/method/messages.search delete mode 100644 data/core.telegram.org/method/messages.searchGifs delete mode 100644 data/core.telegram.org/method/messages.searchGlobal delete mode 100644 data/core.telegram.org/method/messages.searchStickerSets delete mode 100644 data/core.telegram.org/method/messages.sendBroadcast delete mode 100644 data/core.telegram.org/method/messages.sendEncrypted delete mode 100644 data/core.telegram.org/method/messages.sendEncryptedFile delete mode 100644 data/core.telegram.org/method/messages.sendEncryptedService delete mode 100644 data/core.telegram.org/method/messages.sendInlineBotResult delete mode 100644 data/core.telegram.org/method/messages.sendMedia delete mode 100644 data/core.telegram.org/method/messages.sendMessage delete mode 100644 data/core.telegram.org/method/messages.sendMultiMedia delete mode 100644 data/core.telegram.org/method/messages.sendReaction delete mode 100644 data/core.telegram.org/method/messages.sendScheduledMessages delete mode 100644 data/core.telegram.org/method/messages.sendScreenshotNotification delete mode 100644 data/core.telegram.org/method/messages.sendVote delete mode 100644 data/core.telegram.org/method/messages.setBotCallbackAnswer delete mode 100644 data/core.telegram.org/method/messages.setBotPrecheckoutResults delete mode 100644 data/core.telegram.org/method/messages.setBotShippingResults delete mode 100644 data/core.telegram.org/method/messages.setEncryptedTyping delete mode 100644 data/core.telegram.org/method/messages.setGameScore delete mode 100644 data/core.telegram.org/method/messages.setInlineBotResults delete mode 100644 data/core.telegram.org/method/messages.setInlineGameScore delete mode 100644 data/core.telegram.org/method/messages.setTyping delete mode 100644 data/core.telegram.org/method/messages.startBot delete mode 100644 data/core.telegram.org/method/messages.toggleDialogPin delete mode 100644 data/core.telegram.org/method/messages.toggleStickerSets delete mode 100644 data/core.telegram.org/method/messages.uninstallStickerSet delete mode 100644 data/core.telegram.org/method/messages.unpinAllMessages delete mode 100644 data/core.telegram.org/method/messages.updateDialogFilter delete mode 100644 data/core.telegram.org/method/messages.updateDialogFiltersOrder delete mode 100644 data/core.telegram.org/method/messages.updatePinnedMessage delete mode 100644 data/core.telegram.org/method/messages.uploadEncryptedFile delete mode 100644 data/core.telegram.org/method/messages.uploadMedia delete mode 100644 data/core.telegram.org/method/payments.clearSavedInfo delete mode 100644 data/core.telegram.org/method/payments.getBankCardData delete mode 100644 data/core.telegram.org/method/payments.getPaymentForm delete mode 100644 data/core.telegram.org/method/payments.getPaymentReceipt delete mode 100644 data/core.telegram.org/method/payments.getSavedInfo delete mode 100644 data/core.telegram.org/method/payments.sendPaymentForm delete mode 100644 data/core.telegram.org/method/payments.validateRequestedInfo delete mode 100644 data/core.telegram.org/method/phone.acceptCall delete mode 100644 data/core.telegram.org/method/phone.confirmCall delete mode 100644 data/core.telegram.org/method/phone.discardCall delete mode 100644 data/core.telegram.org/method/phone.getCallConfig delete mode 100644 data/core.telegram.org/method/phone.receivedCall delete mode 100644 data/core.telegram.org/method/phone.requestCall delete mode 100644 data/core.telegram.org/method/phone.saveCallDebug delete mode 100644 data/core.telegram.org/method/phone.sendSignalingData delete mode 100644 data/core.telegram.org/method/phone.setCallRating delete mode 100644 data/core.telegram.org/method/photos.deletePhotos delete mode 100644 data/core.telegram.org/method/photos.getUserPhotos delete mode 100644 data/core.telegram.org/method/photos.updateProfilePhoto delete mode 100644 data/core.telegram.org/method/photos.uploadProfilePhoto delete mode 100644 data/core.telegram.org/method/stats.getBroadcastStats delete mode 100644 data/core.telegram.org/method/stats.getMegagroupStats delete mode 100644 data/core.telegram.org/method/stats.getMessagePublicForwards delete mode 100644 data/core.telegram.org/method/stats.getMessageStats delete mode 100644 data/core.telegram.org/method/stats.loadAsyncGraph delete mode 100644 data/core.telegram.org/method/stickers.addStickerToSet delete mode 100644 data/core.telegram.org/method/stickers.changeStickerPosition delete mode 100644 data/core.telegram.org/method/stickers.createStickerSet delete mode 100644 data/core.telegram.org/method/stickers.removeStickerFromSet delete mode 100644 data/core.telegram.org/method/stickers.setStickerSetThumb delete mode 100644 data/core.telegram.org/method/updates.getChannelDifference delete mode 100644 data/core.telegram.org/method/updates.getDifference delete mode 100644 data/core.telegram.org/method/updates.getState delete mode 100644 data/core.telegram.org/method/upload.getCdnFile delete mode 100644 data/core.telegram.org/method/upload.getCdnFileHashes delete mode 100644 data/core.telegram.org/method/upload.getFile delete mode 100644 data/core.telegram.org/method/upload.getFileHashes delete mode 100644 data/core.telegram.org/method/upload.getWebFile delete mode 100644 data/core.telegram.org/method/upload.reuploadCdnFile delete mode 100644 data/core.telegram.org/method/upload.saveBigFilePart delete mode 100644 data/core.telegram.org/method/upload.saveFilePart delete mode 100644 data/core.telegram.org/method/users.getFullUser delete mode 100644 data/core.telegram.org/method/users.getUsers delete mode 100644 data/core.telegram.org/method/users.setSecureValueErrors delete mode 100644 data/core.telegram.org/methods.html delete mode 100644 data/core.telegram.org/mtproto.html delete mode 100644 data/core.telegram.org/mtproto/TL-abstract-types.html delete mode 100644 data/core.telegram.org/mtproto/TL-combinators.html delete mode 100644 data/core.telegram.org/mtproto/TL-dependent.html delete mode 100644 data/core.telegram.org/mtproto/TL-formal.html delete mode 100644 data/core.telegram.org/mtproto/TL-optargs.html delete mode 100644 data/core.telegram.org/mtproto/TL-patterns.html delete mode 100644 data/core.telegram.org/mtproto/TL-polymorph.html delete mode 100644 data/core.telegram.org/mtproto/TL-tl.html delete mode 100644 data/core.telegram.org/mtproto/TL-types.html delete mode 100644 data/core.telegram.org/mtproto/TL.html delete mode 100644 data/core.telegram.org/mtproto/auth_key.html delete mode 100644 data/core.telegram.org/mtproto/description.html delete mode 100644 data/core.telegram.org/mtproto/description_v1.html delete mode 100644 data/core.telegram.org/mtproto/mtproto-transports.html delete mode 100644 data/core.telegram.org/mtproto/samples-auth_key.html delete mode 100644 data/core.telegram.org/mtproto/security_guidelines.html delete mode 100644 data/core.telegram.org/mtproto/security_guidelines_v1.html delete mode 100644 data/core.telegram.org/mtproto/serialize.html delete mode 100644 data/core.telegram.org/mtproto/service_messages.html delete mode 100644 data/core.telegram.org/mtproto/service_messages_about_messages.html delete mode 100644 data/core.telegram.org/mtproto_v1.html delete mode 100644 data/core.telegram.org/passport.html delete mode 100644 data/core.telegram.org/passport/encryption.html delete mode 100644 data/core.telegram.org/passport/example.html delete mode 100644 data/core.telegram.org/passport/sdk-android.html delete mode 100644 data/core.telegram.org/passport/sdk-ios-mac.html delete mode 100644 data/core.telegram.org/passport/sdk-javascript.html delete mode 100644 data/core.telegram.org/reproducible-builds.html delete mode 100644 data/core.telegram.org/schema.html delete mode 100644 data/core.telegram.org/schema/end-to-end-json.html delete mode 100644 data/core.telegram.org/schema/end-to-end.html delete mode 100644 data/core.telegram.org/schema/json.html delete mode 100644 data/core.telegram.org/schema/mtproto-json.html delete mode 100644 data/core.telegram.org/schema/mtproto.html delete mode 100644 data/core.telegram.org/tdlib.html delete mode 100644 data/core.telegram.org/tdlib/docs.html delete mode 100644 data/core.telegram.org/tdlib/docs/td__api_8h.html delete mode 100644 data/core.telegram.org/tdlib/docs/td__json__client_8h.html delete mode 100644 data/core.telegram.org/tdlib/docs/td__log_8h.html delete mode 100644 data/core.telegram.org/tdlib/getting-started.html delete mode 100644 data/core.telegram.org/tdlib/notification-api.html delete mode 100644 data/core.telegram.org/tdlib/options.html delete mode 100644 data/core.telegram.org/techfaq.html delete mode 100644 data/core.telegram.org/themes.html delete mode 100644 data/core.telegram.org/type/AccountDaysTTL.html delete mode 100644 data/core.telegram.org/type/Audio.html delete mode 100644 data/core.telegram.org/type/Authorization.html delete mode 100644 data/core.telegram.org/type/AutoDownloadSettings.html delete mode 100644 data/core.telegram.org/type/BankCardOpenUrl.html delete mode 100644 data/core.telegram.org/type/BaseTheme.html delete mode 100644 data/core.telegram.org/type/Bool.html delete mode 100644 data/core.telegram.org/type/BotCommand.html delete mode 100644 data/core.telegram.org/type/BotInfo.html delete mode 100644 data/core.telegram.org/type/BotInlineMessage.html delete mode 100644 data/core.telegram.org/type/BotInlineResult.html delete mode 100644 data/core.telegram.org/type/CdnConfig.html delete mode 100644 data/core.telegram.org/type/CdnPublicKey.html delete mode 100644 data/core.telegram.org/type/ChannelAdminLogEvent.html delete mode 100644 data/core.telegram.org/type/ChannelAdminLogEventAction.html delete mode 100644 data/core.telegram.org/type/ChannelAdminLogEventsFilter.html delete mode 100644 data/core.telegram.org/type/ChannelLocation.html delete mode 100644 data/core.telegram.org/type/ChannelMessagesFilter.html delete mode 100644 data/core.telegram.org/type/ChannelParticipant.html delete mode 100644 data/core.telegram.org/type/ChannelParticipantsFilter.html delete mode 100644 data/core.telegram.org/type/Chat.html delete mode 100644 data/core.telegram.org/type/ChatAdminRights.html delete mode 100644 data/core.telegram.org/type/ChatBannedRights.html delete mode 100644 data/core.telegram.org/type/ChatFull.html delete mode 100644 data/core.telegram.org/type/ChatInvite.html delete mode 100644 data/core.telegram.org/type/ChatOnlines.html delete mode 100644 data/core.telegram.org/type/ChatParticipant.html delete mode 100644 data/core.telegram.org/type/ChatParticipants.html delete mode 100644 data/core.telegram.org/type/ChatPhoto.html delete mode 100644 data/core.telegram.org/type/CodeSettings.html delete mode 100644 data/core.telegram.org/type/Config.html delete mode 100644 data/core.telegram.org/type/Contact.html delete mode 100644 data/core.telegram.org/type/ContactStatus.html delete mode 100644 data/core.telegram.org/type/DataJSON.html delete mode 100644 data/core.telegram.org/type/DcOption.html delete mode 100644 data/core.telegram.org/type/DecryptedDataBlock.html delete mode 100644 data/core.telegram.org/type/DecryptedMessage.html delete mode 100644 data/core.telegram.org/type/DecryptedMessageAction.html delete mode 100644 data/core.telegram.org/type/DecryptedMessageLayer.html delete mode 100644 data/core.telegram.org/type/DecryptedMessageMedia.html delete mode 100644 data/core.telegram.org/type/Dialog.html delete mode 100644 data/core.telegram.org/type/DialogFilter.html delete mode 100644 data/core.telegram.org/type/DialogFilterSuggested.html delete mode 100644 data/core.telegram.org/type/DialogPeer.html delete mode 100644 data/core.telegram.org/type/DisabledFeature.html delete mode 100644 data/core.telegram.org/type/Document.html delete mode 100644 data/core.telegram.org/type/DocumentAttribute.html delete mode 100644 data/core.telegram.org/type/DraftMessage.html delete mode 100644 data/core.telegram.org/type/EmojiKeyword.html delete mode 100644 data/core.telegram.org/type/EmojiKeywordsDifference.html delete mode 100644 data/core.telegram.org/type/EmojiLanguage.html delete mode 100644 data/core.telegram.org/type/EmojiURL.html delete mode 100644 data/core.telegram.org/type/EncryptedChat.html delete mode 100644 data/core.telegram.org/type/EncryptedFile.html delete mode 100644 data/core.telegram.org/type/EncryptedMessage.html delete mode 100644 data/core.telegram.org/type/Error.html delete mode 100644 data/core.telegram.org/type/ExportedChatInvite.html delete mode 100644 data/core.telegram.org/type/ExportedMessageLink.html delete mode 100644 data/core.telegram.org/type/FileHash.html delete mode 100644 data/core.telegram.org/type/FileLocation.html delete mode 100644 data/core.telegram.org/type/Folder.html delete mode 100644 data/core.telegram.org/type/FolderPeer.html delete mode 100644 data/core.telegram.org/type/Game.html delete mode 100644 data/core.telegram.org/type/GeoPoint.html delete mode 100644 data/core.telegram.org/type/GlobalPrivacySettings.html delete mode 100644 data/core.telegram.org/type/HighScore.html delete mode 100644 data/core.telegram.org/type/ImportedContact.html delete mode 100644 data/core.telegram.org/type/InlineBotSwitchPM.html delete mode 100644 data/core.telegram.org/type/InputAppEvent.html delete mode 100644 data/core.telegram.org/type/InputBotInlineMessage.html delete mode 100644 data/core.telegram.org/type/InputBotInlineMessageID.html delete mode 100644 data/core.telegram.org/type/InputBotInlineResult.html delete mode 100644 data/core.telegram.org/type/InputChannel.html delete mode 100644 data/core.telegram.org/type/InputChatPhoto.html delete mode 100644 data/core.telegram.org/type/InputCheckPasswordSRP.html delete mode 100644 data/core.telegram.org/type/InputClientProxy.html delete mode 100644 data/core.telegram.org/type/InputContact.html delete mode 100644 data/core.telegram.org/type/InputDialogPeer.html delete mode 100644 data/core.telegram.org/type/InputDocument.html delete mode 100644 data/core.telegram.org/type/InputEncryptedChat.html delete mode 100644 data/core.telegram.org/type/InputEncryptedFile.html delete mode 100644 data/core.telegram.org/type/InputFile.html delete mode 100644 data/core.telegram.org/type/InputFileLocation.html delete mode 100644 data/core.telegram.org/type/InputFolderPeer.html delete mode 100644 data/core.telegram.org/type/InputGame.html delete mode 100644 data/core.telegram.org/type/InputGeoPoint.html delete mode 100644 data/core.telegram.org/type/InputMedia.html delete mode 100644 data/core.telegram.org/type/InputMessage.html delete mode 100644 data/core.telegram.org/type/InputNotifyPeer.html delete mode 100644 data/core.telegram.org/type/InputPaymentCredentials.html delete mode 100644 data/core.telegram.org/type/InputPeer.html delete mode 100644 data/core.telegram.org/type/InputPeerNotifySettings.html delete mode 100644 data/core.telegram.org/type/InputPhoneCall.html delete mode 100644 data/core.telegram.org/type/InputPhoto.html delete mode 100644 data/core.telegram.org/type/InputPrivacyKey.html delete mode 100644 data/core.telegram.org/type/InputPrivacyRule.html delete mode 100644 data/core.telegram.org/type/InputSecureFile.html delete mode 100644 data/core.telegram.org/type/InputSecureValue.html delete mode 100644 data/core.telegram.org/type/InputSingleMedia.html delete mode 100644 data/core.telegram.org/type/InputStickerSet.html delete mode 100644 data/core.telegram.org/type/InputStickerSetItem.html delete mode 100644 data/core.telegram.org/type/InputStickeredMedia.html delete mode 100644 data/core.telegram.org/type/InputTheme.html delete mode 100644 data/core.telegram.org/type/InputThemeSettings.html delete mode 100644 data/core.telegram.org/type/InputUser.html delete mode 100644 data/core.telegram.org/type/InputWallPaper.html delete mode 100644 data/core.telegram.org/type/InputWebDocument.html delete mode 100644 data/core.telegram.org/type/InputWebFileLocation.html delete mode 100644 data/core.telegram.org/type/Invoice.html delete mode 100644 data/core.telegram.org/type/JSONObjectValue.html delete mode 100644 data/core.telegram.org/type/JSONValue.html delete mode 100644 data/core.telegram.org/type/KeyboardButton.html delete mode 100644 data/core.telegram.org/type/KeyboardButtonRow.html delete mode 100644 data/core.telegram.org/type/LabeledPrice.html delete mode 100644 data/core.telegram.org/type/LangPackDifference.html delete mode 100644 data/core.telegram.org/type/LangPackLanguage.html delete mode 100644 data/core.telegram.org/type/LangPackString.html delete mode 100644 data/core.telegram.org/type/MaskCoords.html delete mode 100644 data/core.telegram.org/type/Message.html delete mode 100644 data/core.telegram.org/type/MessageAction.html delete mode 100644 data/core.telegram.org/type/MessageEntity.html delete mode 100644 data/core.telegram.org/type/MessageFwdHeader.html delete mode 100644 data/core.telegram.org/type/MessageInteractionCounters.html delete mode 100644 data/core.telegram.org/type/MessageMedia.html delete mode 100644 data/core.telegram.org/type/MessageRange.html delete mode 100644 data/core.telegram.org/type/MessageReactionsList.html delete mode 100644 data/core.telegram.org/type/MessageReplies.html delete mode 100644 data/core.telegram.org/type/MessageReplyHeader.html delete mode 100644 data/core.telegram.org/type/MessageUserVote.html delete mode 100644 data/core.telegram.org/type/MessageViews.html delete mode 100644 data/core.telegram.org/type/MessagesFilter.html delete mode 100644 data/core.telegram.org/type/NearestDc.html delete mode 100644 data/core.telegram.org/type/NotifyPeer.html delete mode 100644 data/core.telegram.org/type/Null.html delete mode 100644 data/core.telegram.org/type/Page.html delete mode 100644 data/core.telegram.org/type/PageBlock.html delete mode 100644 data/core.telegram.org/type/PageCaption.html delete mode 100644 data/core.telegram.org/type/PageListItem.html delete mode 100644 data/core.telegram.org/type/PageListOrderedItem.html delete mode 100644 data/core.telegram.org/type/PageRelatedArticle.html delete mode 100644 data/core.telegram.org/type/PageTableCell.html delete mode 100644 data/core.telegram.org/type/PageTableRow.html delete mode 100644 data/core.telegram.org/type/PasswordKdfAlgo.html delete mode 100644 data/core.telegram.org/type/PaymentCharge.html delete mode 100644 data/core.telegram.org/type/PaymentRequestedInfo.html delete mode 100644 data/core.telegram.org/type/PaymentSavedCredentials.html delete mode 100644 data/core.telegram.org/type/Peer.html delete mode 100644 data/core.telegram.org/type/PeerBlocked.html delete mode 100644 data/core.telegram.org/type/PeerLocated.html delete mode 100644 data/core.telegram.org/type/PeerNotifySettings.html delete mode 100644 data/core.telegram.org/type/PeerSettings.html delete mode 100644 data/core.telegram.org/type/PhoneCall.html delete mode 100644 data/core.telegram.org/type/PhoneCallDiscardReason.html delete mode 100644 data/core.telegram.org/type/PhoneCallProtocol.html delete mode 100644 data/core.telegram.org/type/PhoneConnection.html delete mode 100644 data/core.telegram.org/type/Photo.html delete mode 100644 data/core.telegram.org/type/PhotoSize.html delete mode 100644 data/core.telegram.org/type/Poll.html delete mode 100644 data/core.telegram.org/type/PollAnswer.html delete mode 100644 data/core.telegram.org/type/PollAnswerVoters.html delete mode 100644 data/core.telegram.org/type/PollResults.html delete mode 100644 data/core.telegram.org/type/PopularContact.html delete mode 100644 data/core.telegram.org/type/PostAddress.html delete mode 100644 data/core.telegram.org/type/PrivacyKey.html delete mode 100644 data/core.telegram.org/type/PrivacyRule.html delete mode 100644 data/core.telegram.org/type/ReceivedNotifyMessage.html delete mode 100644 data/core.telegram.org/type/RecentMeUrl.html delete mode 100644 data/core.telegram.org/type/ReplyMarkup.html delete mode 100644 data/core.telegram.org/type/ReportReason.html delete mode 100644 data/core.telegram.org/type/RestrictionReason.html delete mode 100644 data/core.telegram.org/type/RichText.html delete mode 100644 data/core.telegram.org/type/SavedContact.html delete mode 100644 data/core.telegram.org/type/SecureCredentialsEncrypted.html delete mode 100644 data/core.telegram.org/type/SecureData.html delete mode 100644 data/core.telegram.org/type/SecureFile.html delete mode 100644 data/core.telegram.org/type/SecurePasswordKdfAlgo.html delete mode 100644 data/core.telegram.org/type/SecurePlainData.html delete mode 100644 data/core.telegram.org/type/SecureRequiredType.html delete mode 100644 data/core.telegram.org/type/SecureSecretSettings.html delete mode 100644 data/core.telegram.org/type/SecureValue.html delete mode 100644 data/core.telegram.org/type/SecureValueError.html delete mode 100644 data/core.telegram.org/type/SecureValueHash.html delete mode 100644 data/core.telegram.org/type/SecureValueType.html delete mode 100644 data/core.telegram.org/type/SendMessageAction.html delete mode 100644 data/core.telegram.org/type/ShippingOption.html delete mode 100644 data/core.telegram.org/type/StatsAbsValueAndPrev.html delete mode 100644 data/core.telegram.org/type/StatsDateRangeDays.html delete mode 100644 data/core.telegram.org/type/StatsGraph.html delete mode 100644 data/core.telegram.org/type/StatsGroupTopAdmin.html delete mode 100644 data/core.telegram.org/type/StatsGroupTopInviter.html delete mode 100644 data/core.telegram.org/type/StatsGroupTopPoster.html delete mode 100644 data/core.telegram.org/type/StatsPercentValue.html delete mode 100644 data/core.telegram.org/type/StatsURL.html delete mode 100644 data/core.telegram.org/type/StickerPack.html delete mode 100644 data/core.telegram.org/type/StickerSet.html delete mode 100644 data/core.telegram.org/type/StickerSetCovered.html delete mode 100644 data/core.telegram.org/type/Theme.html delete mode 100644 data/core.telegram.org/type/ThemeSettings.html delete mode 100644 data/core.telegram.org/type/TopPeer.html delete mode 100644 data/core.telegram.org/type/TopPeerCategory.html delete mode 100644 data/core.telegram.org/type/TopPeerCategoryPeers.html delete mode 100644 data/core.telegram.org/type/True.html delete mode 100644 data/core.telegram.org/type/Update.html delete mode 100644 data/core.telegram.org/type/Updates.html delete mode 100644 data/core.telegram.org/type/UrlAuthResult.html delete mode 100644 data/core.telegram.org/type/User.html delete mode 100644 data/core.telegram.org/type/UserFull.html delete mode 100644 data/core.telegram.org/type/UserProfilePhoto.html delete mode 100644 data/core.telegram.org/type/UserStatus.html delete mode 100644 data/core.telegram.org/type/Vector t.html delete mode 100644 data/core.telegram.org/type/Video.html delete mode 100644 data/core.telegram.org/type/VideoSize.html delete mode 100644 data/core.telegram.org/type/WallPaper.html delete mode 100644 data/core.telegram.org/type/WallPaperSettings.html delete mode 100644 data/core.telegram.org/type/WebAuthorization.html delete mode 100644 data/core.telegram.org/type/WebDocument.html delete mode 100644 data/core.telegram.org/type/WebPage.html delete mode 100644 data/core.telegram.org/type/WebPageAttribute.html delete mode 100644 data/core.telegram.org/type/account.AuthorizationForm delete mode 100644 data/core.telegram.org/type/account.Authorizations delete mode 100644 data/core.telegram.org/type/account.AutoDownloadSettings delete mode 100644 data/core.telegram.org/type/account.ContentSettings delete mode 100644 data/core.telegram.org/type/account.Password delete mode 100644 data/core.telegram.org/type/account.PasswordInputSettings delete mode 100644 data/core.telegram.org/type/account.PasswordSettings delete mode 100644 data/core.telegram.org/type/account.PrivacyRules delete mode 100644 data/core.telegram.org/type/account.SentChangePhoneCode delete mode 100644 data/core.telegram.org/type/account.SentEmailCode delete mode 100644 data/core.telegram.org/type/account.Takeout delete mode 100644 data/core.telegram.org/type/account.Themes delete mode 100644 data/core.telegram.org/type/account.TmpPassword delete mode 100644 data/core.telegram.org/type/account.WallPapers delete mode 100644 data/core.telegram.org/type/account.WebAuthorizations delete mode 100644 data/core.telegram.org/type/auth.Authorization delete mode 100644 data/core.telegram.org/type/auth.CheckedPhone delete mode 100644 data/core.telegram.org/type/auth.CodeType delete mode 100644 data/core.telegram.org/type/auth.ExportedAuthorization delete mode 100644 data/core.telegram.org/type/auth.LoginToken delete mode 100644 data/core.telegram.org/type/auth.PasswordRecovery delete mode 100644 data/core.telegram.org/type/auth.SentCode delete mode 100644 data/core.telegram.org/type/auth.SentCodeType delete mode 100644 data/core.telegram.org/type/bytes.html delete mode 100644 data/core.telegram.org/type/channels.AdminLogResults delete mode 100644 data/core.telegram.org/type/channels.ChannelParticipant delete mode 100644 data/core.telegram.org/type/channels.ChannelParticipants delete mode 100644 data/core.telegram.org/type/contacts.Blocked delete mode 100644 data/core.telegram.org/type/contacts.Contacts delete mode 100644 data/core.telegram.org/type/contacts.Found delete mode 100644 data/core.telegram.org/type/contacts.ImportedContacts delete mode 100644 data/core.telegram.org/type/contacts.Link delete mode 100644 data/core.telegram.org/type/contacts.ResolvedPeer delete mode 100644 data/core.telegram.org/type/contacts.TopPeers delete mode 100644 data/core.telegram.org/type/double.html delete mode 100644 data/core.telegram.org/type/help.AppUpdate delete mode 100644 data/core.telegram.org/type/help.CountriesList delete mode 100644 data/core.telegram.org/type/help.Country delete mode 100644 data/core.telegram.org/type/help.CountryCode delete mode 100644 data/core.telegram.org/type/help.DeepLinkInfo delete mode 100644 data/core.telegram.org/type/help.InviteText delete mode 100644 data/core.telegram.org/type/help.PassportConfig delete mode 100644 data/core.telegram.org/type/help.PromoData delete mode 100644 data/core.telegram.org/type/help.ProxyData delete mode 100644 data/core.telegram.org/type/help.RecentMeUrls delete mode 100644 data/core.telegram.org/type/help.Support delete mode 100644 data/core.telegram.org/type/help.SupportName delete mode 100644 data/core.telegram.org/type/help.TermsOfService delete mode 100644 data/core.telegram.org/type/help.TermsOfServiceUpdate delete mode 100644 data/core.telegram.org/type/help.UserInfo delete mode 100644 data/core.telegram.org/type/int.html delete mode 100644 data/core.telegram.org/type/long.html delete mode 100644 data/core.telegram.org/type/messages.AffectedHistory delete mode 100644 data/core.telegram.org/type/messages.AffectedMessages delete mode 100644 data/core.telegram.org/type/messages.AllStickers delete mode 100644 data/core.telegram.org/type/messages.ArchivedStickers delete mode 100644 data/core.telegram.org/type/messages.BotCallbackAnswer delete mode 100644 data/core.telegram.org/type/messages.BotResults delete mode 100644 data/core.telegram.org/type/messages.ChatFull delete mode 100644 data/core.telegram.org/type/messages.Chats delete mode 100644 data/core.telegram.org/type/messages.DhConfig delete mode 100644 data/core.telegram.org/type/messages.Dialogs delete mode 100644 data/core.telegram.org/type/messages.DiscussionMessage delete mode 100644 data/core.telegram.org/type/messages.FavedStickers delete mode 100644 data/core.telegram.org/type/messages.FeaturedStickers delete mode 100644 data/core.telegram.org/type/messages.FoundGifs delete mode 100644 data/core.telegram.org/type/messages.FoundStickerSets delete mode 100644 data/core.telegram.org/type/messages.HighScores delete mode 100644 data/core.telegram.org/type/messages.InactiveChats delete mode 100644 data/core.telegram.org/type/messages.MessageEditData delete mode 100644 data/core.telegram.org/type/messages.MessageViews delete mode 100644 data/core.telegram.org/type/messages.Messages delete mode 100644 data/core.telegram.org/type/messages.PeerDialogs delete mode 100644 data/core.telegram.org/type/messages.RecentStickers delete mode 100644 data/core.telegram.org/type/messages.SavedGifs delete mode 100644 data/core.telegram.org/type/messages.SearchCounter delete mode 100644 data/core.telegram.org/type/messages.SentEncryptedMessage delete mode 100644 data/core.telegram.org/type/messages.SentMessage delete mode 100644 data/core.telegram.org/type/messages.StatedMessage delete mode 100644 data/core.telegram.org/type/messages.StatedMessages delete mode 100644 data/core.telegram.org/type/messages.StickerSet delete mode 100644 data/core.telegram.org/type/messages.StickerSetInstallResult delete mode 100644 data/core.telegram.org/type/messages.Stickers delete mode 100644 data/core.telegram.org/type/messages.VotesList delete mode 100644 data/core.telegram.org/type/payments.BankCardData delete mode 100644 data/core.telegram.org/type/payments.PaymentForm delete mode 100644 data/core.telegram.org/type/payments.PaymentReceipt delete mode 100644 data/core.telegram.org/type/payments.PaymentResult delete mode 100644 data/core.telegram.org/type/payments.SavedInfo delete mode 100644 data/core.telegram.org/type/payments.ValidatedRequestedInfo delete mode 100644 data/core.telegram.org/type/phone.PhoneCall delete mode 100644 data/core.telegram.org/type/photos.Photo delete mode 100644 data/core.telegram.org/type/photos.Photos delete mode 100644 data/core.telegram.org/type/stats.BroadcastStats delete mode 100644 data/core.telegram.org/type/stats.MegagroupStats delete mode 100644 data/core.telegram.org/type/stats.MessageStats delete mode 100644 data/core.telegram.org/type/storage.FileType delete mode 100644 data/core.telegram.org/type/string.html delete mode 100644 data/core.telegram.org/type/updates.ChannelDifference delete mode 100644 data/core.telegram.org/type/updates.Difference delete mode 100644 data/core.telegram.org/type/updates.State delete mode 100644 data/core.telegram.org/type/upload.CdnFile delete mode 100644 data/core.telegram.org/type/upload.File delete mode 100644 data/core.telegram.org/type/upload.WebFile delete mode 100644 data/core.telegram.org/widgets.html delete mode 100644 data/core.telegram.org/widgets/discussion.html delete mode 100644 data/core.telegram.org/widgets/login.html delete mode 100644 data/core.telegram.org/widgets/post.html delete mode 100644 data/core.telegram.org/widgets/share.html delete mode 100644 data/desktop.telegram.org.html delete mode 100644 data/desktop.telegram.org/changelog.html delete mode 100644 data/desktop.telegram.org/css/bootstrap.min.css delete mode 100644 data/desktop.telegram.org/css/telegram.css delete mode 100644 data/desktop.telegram.org/js/main.js delete mode 100644 data/instantview.telegram.org.html delete mode 100644 data/instantview.telegram.org/auth.html delete mode 100644 data/instantview.telegram.org/checklist.html delete mode 100644 data/instantview.telegram.org/css/bootstrap-extra.css delete mode 100644 data/instantview.telegram.org/css/bootstrap.min.css delete mode 100644 data/instantview.telegram.org/css/codemirror.css delete mode 100644 data/instantview.telegram.org/css/instantview.css delete mode 100644 data/instantview.telegram.org/css/telegram.css delete mode 100644 data/instantview.telegram.org/docs.html delete mode 100644 data/instantview.telegram.org/js/bootstrap.min.js delete mode 100644 data/instantview.telegram.org/js/codemirror-instantview.js delete mode 100644 data/instantview.telegram.org/js/codemirror/codemirror.js delete mode 100644 data/instantview.telegram.org/js/codemirror/runmode.js delete mode 100644 data/instantview.telegram.org/js/codemirror/simple.js delete mode 100644 data/instantview.telegram.org/js/instantview.js delete mode 100644 data/instantview.telegram.org/js/jquery.min.js delete mode 100644 data/instantview.telegram.org/js/main.js delete mode 100644 data/instantview.telegram.org/rules.html delete mode 100644 data/instantview.telegram.org/samples.html delete mode 100644 data/instantview.telegram.org/templates.html delete mode 100644 data/macos.telegram.org.html delete mode 100644 data/macos.telegram.org/css/bootstrap.min.css delete mode 100644 data/macos.telegram.org/css/telegram.css delete mode 100644 data/macos.telegram.org/js/main.js delete mode 100644 data/telegram.org.html delete mode 100644 data/telegram.org/android.html delete mode 100644 data/telegram.org/api.html delete mode 100644 data/telegram.org/apple_privacy.html delete mode 100644 data/telegram.org/blog.html delete mode 100644 data/telegram.org/blog/200-million.html delete mode 100644 data/telegram.org/blog/400-million.html delete mode 100644 data/telegram.org/blog/6-years.html delete mode 100644 data/telegram.org/blog/admin-revolution.html delete mode 100644 data/telegram.org/blog/albums-saved-messages.html delete mode 100644 data/telegram.org/blog/android-2-0.html delete mode 100644 data/telegram.org/blog/android-gif.html delete mode 100644 data/telegram.org/blog/android-streaming.html delete mode 100644 data/telegram.org/blog/android-themes.html delete mode 100644 data/telegram.org/blog/android-wear-2-0.html delete mode 100644 data/telegram.org/blog/animated-backgrounds.html delete mode 100644 data/telegram.org/blog/animated-stickers.html delete mode 100644 data/telegram.org/blog/apple-watch.html delete mode 100644 data/telegram.org/blog/archive-and-new-design.html delete mode 100644 data/telegram.org/blog/autodelete-inv2.html delete mode 100644 data/telegram.org/blog/autoplay.html delete mode 100644 data/telegram.org/blog/backgrounds-2-0.html delete mode 100644 data/telegram.org/blog/bot-revolution.html delete mode 100644 data/telegram.org/blog/bots-2-0.html delete mode 100644 data/telegram.org/blog/cache-and-stickers.html delete mode 100644 data/telegram.org/blog/calls.html delete mode 100644 data/telegram.org/blog/captions-places.html delete mode 100644 data/telegram.org/blog/channels-2-0.html delete mode 100644 data/telegram.org/blog/channels.html delete mode 100644 data/telegram.org/blog/contacts-local-groups.html delete mode 100644 data/telegram.org/blog/coronavirus.html delete mode 100644 data/telegram.org/blog/crowdsourcing-a-more-secure-future.html delete mode 100644 data/telegram.org/blog/cryptocontest-ends.html delete mode 100644 data/telegram.org/blog/cryptocontest.html delete mode 100644 data/telegram.org/blog/desktop-1-0.html delete mode 100644 data/telegram.org/blog/desktop-compact.html delete mode 100644 data/telegram.org/blog/discover-stickers-and-more.html delete mode 100644 data/telegram.org/blog/drafts.html delete mode 100644 data/telegram.org/blog/edit.html delete mode 100644 data/telegram.org/blog/encrypted-cdns.html delete mode 100644 data/telegram.org/blog/export-and-more.html delete mode 100644 data/telegram.org/blog/files-on-steroids.html delete mode 100644 data/telegram.org/blog/filters-anonymous-admins-comments.html delete mode 100644 data/telegram.org/blog/folders.html delete mode 100644 data/telegram.org/blog/games.html delete mode 100644 data/telegram.org/blog/gif-revolution.html delete mode 100644 data/telegram.org/blog/gifs.html delete mode 100644 data/telegram.org/blog/group-video-calls.html delete mode 100644 data/telegram.org/blog/inline-bots.html delete mode 100644 data/telegram.org/blog/instant-camera.html delete mode 100644 data/telegram.org/blog/instant-view-contest-200K.html delete mode 100644 data/telegram.org/blog/instant-view.html delete mode 100644 data/telegram.org/blog/invite-links.html delete mode 100644 data/telegram.org/blog/link-preview.html delete mode 100644 data/telegram.org/blog/live-locations.html delete mode 100644 data/telegram.org/blog/login.html delete mode 100644 data/telegram.org/blog/masks.html delete mode 100644 data/telegram.org/blog/moar-stickers.html delete mode 100644 data/telegram.org/blog/move-history.html delete mode 100644 data/telegram.org/blog/new-profiles-people-nearby.html delete mode 100644 data/telegram.org/blog/now-you-see-me.html delete mode 100644 data/telegram.org/blog/passport.html delete mode 100644 data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html delete mode 100644 data/telegram.org/blog/payments.html delete mode 100644 data/telegram.org/blog/permissions-groups-undo.html delete mode 100644 data/telegram.org/blog/photo-editor-and-passcodes.html delete mode 100644 data/telegram.org/blog/pin-and-ifttt.html delete mode 100644 data/telegram.org/blog/pinned-messages-locations-playlists.html delete mode 100644 data/telegram.org/blog/pinned-messages-locations-playlists/world.html delete mode 100644 data/telegram.org/blog/polls-2-0-vmq.html delete mode 100644 data/telegram.org/blog/polls.html delete mode 100644 data/telegram.org/blog/privacy-discussions-web-bots.html delete mode 100644 data/telegram.org/blog/privacy-revolution.html delete mode 100644 data/telegram.org/blog/profile-videos-people-nearby-and-more.html delete mode 100644 data/telegram.org/blog/replies-mentions-hashtags.html delete mode 100644 data/telegram.org/blog/replies-mentions-stickers.html delete mode 100644 data/telegram.org/blog/scheduled-reminders-themes.html delete mode 100644 data/telegram.org/blog/search-and-media.html delete mode 100644 data/telegram.org/blog/sessions-and-2-step-verification.html delete mode 100644 data/telegram.org/blog/share-preview.html delete mode 100644 data/telegram.org/blog/shared-files.html delete mode 100644 data/telegram.org/blog/shared-links.html delete mode 100644 data/telegram.org/blog/silent-messages-slow-mode.html delete mode 100644 data/telegram.org/blog/stickers-meet-art-and-history.html delete mode 100644 data/telegram.org/blog/stickers-revolution.html delete mode 100644 data/telegram.org/blog/stickers.html delete mode 100644 data/telegram.org/blog/supergroups.html delete mode 100644 data/telegram.org/blog/supergroups5k.html delete mode 100644 data/telegram.org/blog/tdlib.html delete mode 100644 data/telegram.org/blog/telegram-5-ios.html delete mode 100644 data/telegram.org/blog/telegram-me-change-number-and-pfs.html delete mode 100644 data/telegram.org/blog/telegram-x.html delete mode 100644 data/telegram.org/blog/telegraph.html delete mode 100644 data/telegram.org/blog/themes-accounts.html delete mode 100644 data/telegram.org/blog/translations-iv2.html delete mode 100644 data/telegram.org/blog/trending-stickers.html delete mode 100644 data/telegram.org/blog/unread-replace-2x.html delete mode 100644 data/telegram.org/blog/unsend-and-usage.html delete mode 100644 data/telegram.org/blog/unsend-privacy-emoji.html delete mode 100644 data/telegram.org/blog/usernames-and-secret-chats-v2.html delete mode 100644 data/telegram.org/blog/verifiable-apps-and-more.html delete mode 100644 data/telegram.org/blog/video-1000.html delete mode 100644 data/telegram.org/blog/video-calls.html delete mode 100644 data/telegram.org/blog/video-editor-gifs.html delete mode 100644 data/telegram.org/blog/video-messages-and-telescope.html delete mode 100644 data/telegram.org/blog/voice-2-secret-3.html delete mode 100644 data/telegram.org/blog/voice-chats-on-steroids.html delete mode 100644 data/telegram.org/blog/voice-chats.html delete mode 100644 data/telegram.org/blog/winter-contest-ends.html delete mode 100644 data/telegram.org/crypto_contest.html delete mode 100644 data/telegram.org/css/bootstrap-extra.css delete mode 100644 data/telegram.org/css/bootstrap.min.css delete mode 100644 data/telegram.org/css/telegram.css delete mode 100644 data/telegram.org/evolution.html delete mode 100644 data/telegram.org/faq.html delete mode 100644 data/telegram.org/faq_channels.html delete mode 100644 data/telegram.org/faq_spam.html delete mode 100644 data/telegram.org/jobs.html delete mode 100644 data/telegram.org/js/bootstrap.min.js delete mode 100644 data/telegram.org/js/games.js delete mode 100644 data/telegram.org/js/jquery.min.js delete mode 100644 data/telegram.org/js/main.js delete mode 100644 data/telegram.org/js/telegram-widget.js delete mode 100644 data/telegram.org/js/tgsticker.js delete mode 100644 data/telegram.org/press.html delete mode 100644 data/telegram.org/privacy.html delete mode 100644 data/telegram.org/privacy/gmailbot.html delete mode 100644 data/telegram.org/support.html delete mode 100644 data/telegram.org/template31.html delete mode 100644 data/telegram.org/teststore.html delete mode 100644 data/telegram.org/tos.html delete mode 100644 data/telegram.org/tour.html delete mode 100644 data/telegram.org/tour/channels.html delete mode 100644 data/telegram.org/tour/groups.html delete mode 100644 data/telegram.org/tour/quizbot.html delete mode 100644 data/telegram.org/tour/screenshots.html delete mode 100644 data/telegram.org/verify.html delete mode 100644 data/telegram.org/what-can-you-do-with-Telegram.html delete mode 100644 data/themes.telegram.org.html delete mode 100644 data/themes.telegram.org/auth.html delete mode 100644 data/themes.telegram.org/css/bootstrap-extra.css delete mode 100644 data/themes.telegram.org/css/bootstrap.min.css delete mode 100644 data/themes.telegram.org/css/jquery-ui.min.css delete mode 100644 data/themes.telegram.org/css/telegram.css delete mode 100644 data/themes.telegram.org/css/themes.css delete mode 100644 data/themes.telegram.org/js/bootstrap.min.js delete mode 100644 data/themes.telegram.org/js/jquery-ui.min.js delete mode 100644 data/themes.telegram.org/js/jquery.min.js delete mode 100644 data/themes.telegram.org/js/main-aj.js delete mode 100644 data/themes.telegram.org/js/themes.js delete mode 100644 data/translations.telegram.org.html delete mode 100644 data/translations.telegram.org/en.html delete mode 100644 data/translations.telegram.org/en/android.html delete mode 100644 data/translations.telegram.org/en/android_x.html delete mode 100644 data/translations.telegram.org/en/ios.html delete mode 100644 data/translations.telegram.org/en/macos.html delete mode 100644 data/translations.telegram.org/en/tdesktop.html delete mode 100644 data/tsf.telegram.org.html delete mode 100644 data/tsf.telegram.org/auth.html delete mode 100644 data/tsf.telegram.org/css/billboard.css delete mode 100644 data/tsf.telegram.org/css/bootstrap-extra.css delete mode 100644 data/tsf.telegram.org/css/bootstrap.min.css delete mode 100644 data/tsf.telegram.org/css/health.css delete mode 100644 data/tsf.telegram.org/css/jquery-ui.min.css delete mode 100644 data/tsf.telegram.org/css/tchart.min.css delete mode 100644 data/tsf.telegram.org/css/telegram.css delete mode 100644 data/tsf.telegram.org/css/tsf.css delete mode 100644 data/tsf.telegram.org/js/billboard.min.js delete mode 100644 data/tsf.telegram.org/js/bootstrap.min.js delete mode 100644 data/tsf.telegram.org/js/jquery-ui.min.js delete mode 100644 data/tsf.telegram.org/js/jquery.min.js delete mode 100644 data/tsf.telegram.org/js/main-aj.js delete mode 100644 data/tsf.telegram.org/js/main.js delete mode 100644 data/tsf.telegram.org/js/stats.js delete mode 100644 data/tsf.telegram.org/js/tchart.min.js delete mode 100644 data/tsf.telegram.org/js/tsf.js delete mode 100644 data/tsf.telegram.org/manuals.html delete mode 100644 data/tsf.telegram.org/manuals/answering_questions.html delete mode 100644 data/tsf.telegram.org/manuals/bios.html delete mode 100644 data/tsf.telegram.org/manuals/bug_herding.html delete mode 100644 data/tsf.telegram.org/manuals/bug_hunting.html delete mode 100644 data/tsf.telegram.org/manuals/bugs.html delete mode 100644 data/tsf.telegram.org/manuals/come-and-go.html delete mode 100644 data/tsf.telegram.org/manuals/e2ee-simple.html delete mode 100644 data/tsf.telegram.org/manuals/e2ee.html delete mode 100644 data/tsf.telegram.org/manuals/feature_philosophy.html delete mode 100644 data/web.telegram.org.html diff --git a/data/core.telegram.org.html b/data/core.telegram.org.html deleted file mode 100644 index 3aecca7fd6..0000000000 --- a/data/core.telegram.org.html +++ /dev/null @@ -1,252 +0,0 @@ - - - - - Telegram APIs - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram APIs

- -

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

-

You can also add Telegram Widgets to your website.

-

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

-
-

Bot API

-
- -
- -

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

-

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

-
-

Learn more about the Bot API here »

-
-

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

-
-

TDLib – build your own Telegram

-

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

-

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

-

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

-
-

Learn more about TDLib here »

-
-
-

Telegram API

-

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

- -

Getting started

-

Creating an application

-

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

-

User authorization

-

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

-

Two-factor authentication

-

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

-

QR code login

-

QR code login flow

-

Error handling

-

How to handle API return errors correctly.

-

Handling different data centers

-

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

-

Handling updates

-

How to subscribe to updates and handle them properly.

-

Handling PUSH-notifications

-

How to subscribe and handle them properly.

-

Channels, supergroups and groups

-

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

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

Calling methods

-

Additional options for calling methods.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

Pagination

-

How to fetch results from large lists of objects.

-

Client configuration

-

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

-

Security

-

Secret chats, end-to-end encryption

-

End-to-end-encrypted messaging.

-

Security guidelines

-

Important checks required in your client application.

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

End-to-End Encryption in Voice and Video Calls

-

End-to-end-encrypted calls.

-

Optimization

-

Client optimization

-

Ways to boost API interactions.

-

API methods

-

Available method list

-

A list of available high-level methods.

-

API TL-schema, as JSON

-

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

-

Available layer list

-

A list of available schema versions.

-

Other articles

-

Working with bots, using the MTProto API

-

How to work with bots using the MTProto API.

-

Commands

-

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

-

Buttons

-

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

-

Inline queries

-

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

-

Games

-

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

-

Search & filters

-

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

-

Polls

-

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

-

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

-

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

-

Discussion groups

-

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

-

Channel comments and message threads

-

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

-

Admin log

-

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

-

Pinned messages

-

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

-

Mentions

-

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

-

Scheduled messages

-

Telegram allows scheduling messages.

-

Live geolocations

-

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

-

Min constructors

-

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

-

Account deletion

-

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

-

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/animated_stickers.html b/data/core.telegram.org/animated_stickers.html deleted file mode 100644 index dd12a33112..0000000000 --- a/data/core.telegram.org/animated_stickers.html +++ /dev/null @@ -1,138 +0,0 @@ - - - - - Creating Animated Stickers - - - - - - - - - - - - - -
- -
-
-
-
-

Creating Animated Stickers

- -

Telegram apps support animated stickers as of version 5.9. All artists are welcome to create and upload new packs of animated stickers.

-

Required Tools

-

To create animated stickers for the Telegram platform, you will need the following:

-
    -
  1. Any vector graphics editor that allows exporting vector objects to Adobe After Effects for turning 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. -
-

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

-

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

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

Telegram APIs

- -

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

-

You can also add Telegram Widgets to your website.

-

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

-
-

Bot API

-
- -
- -

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

-

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

-
-

Learn more about the Bot API here »

-
-

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

-
-

TDLib – build your own Telegram

-

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

-

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

-

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

-
-

Learn more about TDLib here »

-
-
-

Telegram API

-

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

- -

Getting started

-

Creating an application

-

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

-

User authorization

-

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

-

Two-factor authentication

-

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

-

QR code login

-

QR code login flow

-

Error handling

-

How to handle API return errors correctly.

-

Handling different data centers

-

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

-

Handling updates

-

How to subscribe to updates and handle them properly.

-

Handling PUSH-notifications

-

How to subscribe and handle them properly.

-

Channels, supergroups and groups

-

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

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

Calling methods

-

Additional options for calling methods.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

Pagination

-

How to fetch results from large lists of objects.

-

Client configuration

-

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

-

Security

-

Secret chats, end-to-end encryption

-

End-to-end-encrypted messaging.

-

Security guidelines

-

Important checks required in your client application.

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

End-to-End Encryption in Voice and Video Calls

-

End-to-end-encrypted calls.

-

Optimization

-

Client optimization

-

Ways to boost API interactions.

-

API methods

-

Available method list

-

A list of available high-level methods.

-

API TL-schema, as JSON

-

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

-

Available layer list

-

A list of available schema versions.

-

Other articles

-

Working with bots, using the MTProto API

-

How to work with bots using the MTProto API.

-

Commands

-

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

-

Buttons

-

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

-

Inline queries

-

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

-

Games

-

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

-

Search & filters

-

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

-

Polls

-

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

-

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

-

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

-

Discussion groups

-

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

-

Channel comments and message threads

-

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

-

Admin log

-

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

-

Pinned messages

-

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

-

Mentions

-

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

-

Scheduled messages

-

Telegram allows scheduling messages.

-

Live geolocations

-

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

-

Min constructors

-

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

-

Account deletion

-

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

-

Telegram Passport

-

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

-

Telegram Payments

-

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

-

Styled text with message entities

-

How to create styled text with message entities

-

Working with animated emojis

-

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

-

Working with animated dice

-

Telegram supports sending animated dice emojis.

-

Message drafts

-

How to handle message drafts

-

Folders

-

Working with folders

-

Top peer rating

-

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

-

Handling file references

-

How to handle file references.

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

-

Web events

-

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

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

Account deletion

- -

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

-

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

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

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

-

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

-

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

-

Related articles

-

User Authorization

-

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

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

Animated Emojis

- -

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

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

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

-

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

-

Animated emojis should loop only once when first sent or received, or when clicked.

-

For 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

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

User Authorization

- -
- -

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

-

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

-

Sending a verification code

-

Example implementations: telegram for android, tdlib.

-

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

-

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

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

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

-

The returned auth.SentCode object will contain multiple parameters:

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

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

-

Sign in/sign up

-

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

-

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

-

2FA

-

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

-

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

-

Test Phone Numbers

-

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 XXXXXX as the login confirmation code (the DC number, repeated six times). Note that the value of X must be in the range of 1-3 because there are only 3 Test DCs. When the flood limit is reached for any particular test number, just choose another number (changing the YYYY random part).

-

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

-

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

-
-

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

-
-

We are authorized

-

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

-

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

- -

Other methods will result in an error: 401 UNAUTHORIZED.

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

Bots

- -
- -

Working with bots, using the MTProto API.

-

See here for more info about bots.

-

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

-

Login

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

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

-

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

-

Commands

-

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

-

Buttons

-

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

-

Inline queries

-

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

-

Games

-

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

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

Buttons

- -
- -

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

-

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

-

Buttons

-
keyboardButton#a2fa4880 text:string = KeyboardButton;
-keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
-keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
-keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
-keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
-inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
-keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-
-replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
-replyKeyboardForceReply#f4108aa0 flags:# single_use:flags.1?true selective:flags.2?true = ReplyMarkup;
-replyKeyboardMarkup#3502758c flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-
-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;
-
----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#e73547e1 flags:# query_id:long user_id:int peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
-updateInlineBotCallbackQuery#f9d27a5a flags:# query_id:long user_id:int msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
----functions---
-
-messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
-

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

-

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

- -

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

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

Commands

- -
- -

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

-

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

-

Getting commands

-
botCommand#c27ac8c7 command:string description:string = BotCommand;
-
-botInfo#98e81d3a user_id:int description:string commands:Vector<BotCommand> = BotInfo;
-
-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;
-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;
-
-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;
-

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#805d46f6 commands:Vector<BotCommand> = Bool;
-

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

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

Games

- -
- -

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

-

Sending a game

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

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

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

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

-

Starting a game

-

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

-

Setting highscores

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

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

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

Getting highscores

-
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
-
-messageService#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;
-
-highScore#58fffcd0 pos:int user_id:int score:int = HighScore;
-
-messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
-
----functions---
-
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;
-

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

-

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

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

Inline

- -
- -

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

-

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

-

Making an inline query

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

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

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

Answering to an inline query

-
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-
-inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;
-
-updateBotInlineQuery#54826690 flags:# query_id:long user_id:int query:string geo:flags.0?GeoPoint 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#e48f964 flags:# user_id:int 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#f9d27a5a flags:# query_id:long user_id:int msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
-inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
-
----functions---
-
-messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
-

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

-

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

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

Channels

- -
- -

Channels, chats & supergroups

-

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.

-

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

-

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

-

Migration

-

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

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

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

-

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

-

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

-

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

-

Rights

-

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

-

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

-

Pinned messages

-

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

-

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

-

Discussion

-

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

-

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

-

Recent actions

-

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

-

See here » for more info.

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

Client configuration

- -
- -

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

-

MTProto configuration

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

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

-

Client configuration

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

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

-

Typical fields included in the resulting JSON object are:

-
    -
  • emojies_animated_zoom - Animated emojis and animated dice should be scaled by this factor before being shown to the user (float)
  • -
  • keep_alive_service - Whether app clients should start a keepalive service to keep the app running and fetch updates even when the app is closed (boolean)
  • -
  • background_connection - Whether app clients should start a background TCP connection for MTProto update fetching (boolean)
  • -
  • emojies_send_dice - A list of supported animated dice stickers (array of strings).
  • -
  • emojies_send_dice_success - For animated dice emojis other than the basic 🎲, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks 🎆 (object with emoji keys and object values, containing value and frame_start float values)
  • -
  • emojies_sounds - A map of soundbites to be played when the user clicks on the specified animated emoji; the file reference field should be base64-decoded before downloading the file (map of file IDs, with emoji string keys)
  • -
  • gif_search_branding - Specifies the name of the service providing GIF search through gif_search_username (string)
  • -
  • gif_search_emojies - Specifies a list of emojies that should be suggested as search term in a bar above the GIF search box (array of string emojis)
  • -
  • 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)
  • -
-

Example value:

-
{
-    "test": 1,
-    "emojies_animated_zoom": 0.625,
-    "keep_alive_service": true,
-    "background_connection": true,
-    "emojies_send_dice": [
-        "\ud83c\udfb2",
-        "\ud83c\udfaf",
-        "\ud83c\udfc0",
-        "\u26bd",
-        "\u26bd\ufe0f",
-        "\ud83c\udfb0"
-    ],
-    "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
-        }
-    },
-    "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"
-        },
-        "\ud83e\udddf": {
-            "id": "4960929110848176332",
-            "access_hash": "-8929417974289765626",
-            "file_reference_base64": "AF-4ApArGURtGa2KVC-Yovh1kQoW"
-        },
-        "\ud83e\udddf\u200d\u2640": {
-            "id": "4960929110848176333",
-            "access_hash": "9161696144162881753",
-            "file_reference_base64": "AF-4ApD-eOqXvTBmcszAEkzQN615"
-        },
-        "\ud83c\udf51": {
-            "id": "4963180910661861548",
-            "access_hash": "-7431729439735063448",
-            "file_reference_base64": "AF-4ApBimvRxhcXg-iQ5Gw4Eelit"
-        },
-        "\u2764": {
-            "id": "4978826754966683841",
-            "access_hash": "3926211553285686901",
-            "file_reference_base64": "AF-4ApDBkyjgN2Tk9zJvXPhfJXPA"
-        }
-    },
-    "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"
-    ],
-    "qr_login_camera": true,
-    "qr_login_code": "secondary",
-    "dialog_filters_enabled": true,
-    "dialog_filters_tooltip": false
-}
-

App-specific configuration

-
help.appUpdate#1da7158f flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string = 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#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;
-
-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 with match one of the prefixes, if any were returned.

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

Working with Different Data Centers

- -

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

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

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

-

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

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#df969c2d id:int bytes:bytes = auth.ExportedAuthorization;
-auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
----functions---
-auth.importAuthorization#e3ef9613 id:int bytes:bytes = auth.Authorization;
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;
-

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

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

Dice

- -

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

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

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

-

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

-

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

-

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

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

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

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

Discussion groups

- -
- -

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

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
-channelFull#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;
-
-messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-
----functions---
-
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
-

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

-

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

-

Linking a discussion group

-

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

-

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

-

Schema:

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

Message drafts

- -
- -

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

-

Drafts

-

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

-

Saving drafts

-

Drafts can be saved using the messages.saveDraft method.

-

Downloading drafts

-

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

-

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

-

Clearing drafts

-

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

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/end-to-end.html b/data/core.telegram.org/api/end-to-end.html deleted file mode 100644 index 7d9388a89e..0000000000 --- a/data/core.telegram.org/api/end-to-end.html +++ /dev/null @@ -1,237 +0,0 @@ - - - - - End-to-End Encryption, Secret Chats - - - - - - - - - - - - - -
- -
-
-
- -

End-to-End Encryption, Secret Chats

- -
- -
-

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

-

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

-
-
-
Related articles
-

-
-

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

-
- -
- -

A note on MTProto 2.0

-

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

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

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

-

Key Generation

-

Keys are generated using the Diffie-Hellman protocol.

-

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

-

Sending a Request

-

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

-

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

-

Client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 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 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(intial 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 deleted file mode 100644 index 38f16820ab..0000000000 --- a/data/core.telegram.org/api/end-to-end/pfs.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - Perfect Forward Secrecy - - - - - - - - - - - - - -
- -
-
-
- -

Perfect Forward Secrecy

- -
-

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

-
-

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

-

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

-

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

-

Re-keying protocol

-

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

-
1. decryptedMessageActionRequestKey
-

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

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

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

-
2. decryptedMessageActionAcceptKey
-

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

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

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

-

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

-
3. decryptedMessageActionCommitKey
-

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

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

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

-

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

-
4. Final step
-

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

-

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

-

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

-

Aborting protocol

-

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

-
decryptedMessageActionAbortKey exchange_id:long = DecryptedMessageAction;
-

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

-

Discarding Previous Keys

-

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

-
decryptedMessageActionNoop = DecryptedMessageAction;
-

Concurrent Re-Keying

-

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

-

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

-

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

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

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

-
-

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

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

Sequence numbers in Secret Chats

- -

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

-

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

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

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

-
-

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

-
-

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

-

Preventing gaps

-

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

-

Security checks

-

Checking out_seq_no

-

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

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

Proper handling of gaps

-

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

-

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

-

Special cases:

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

Avoiding concurrent gaps

-

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

-

Checking and handling in_seq_no

-

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

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

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

-

Deleting unacknowledged messages

-

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

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

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

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

End-to-End Encrypted Voice and Video Calls

- -

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

-
Related Articles
-

- -
-

Establishing Calls

-

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

-

Key Generation

-

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

-

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

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

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

-

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

-

Encryption

-
-

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

-
-

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

-

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

-

The library starts working with:

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

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

-

Encrypting Call Data

-

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

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

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

-

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

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

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

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

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

-

The resulting aes_key and aes_iv are used to encrypt decrypted_body:

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

The packet that gets sent consists of msg_key and encrypted_body:

-
    -
  • packet_bytes = msg_key + encrypted_body
  • -
-

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

-

Protecting Against Replay Attacks

-

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

-

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

-

Key Verification

-

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

-

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

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

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

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

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

-

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

-

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

-
-

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

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

End-to-End Encrypted Voice Calls

- -
-

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

-
-
Related articles
-

- -

Establishing voice calls

-

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

-

Key Generation

-

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

-

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

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

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

-

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

-

Encryption of voice data

-

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

-

Encapsulation of low-level voice data

-

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

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

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

-

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

-

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

-

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

-

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

-

MTProto encryption

-

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

-

Key Verification

-

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

-

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

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

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

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

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

-

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

-

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

-
-

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

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

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

- -
-

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

-
-
Related articles
-

-
-

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

-
- -
-

Key Generation

-

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

-

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

-

Sending a Request

-

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

-

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

-

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

-

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

-

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

-

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

-

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

-

Accepting a Request

-

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

-

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

-

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

-

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

-

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

-

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

-

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

-

Perfect Forward Secrecy

-

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

-
-

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

-
-

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

-

Sending and Receiving Messages in a Secret Chat

-

Serialization and Encryption of Outgoing Messages

-

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

-

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

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

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

-

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

-

Decrypting an Incoming Message

-

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

-

Sequence numbers

-

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

-
-

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

-
-

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

-

Sending Encrypted Files

-

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

-

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

-

The key fingerprint is computed as follows:

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

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

-

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

-

Working with an Update Box

-

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

-

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

-

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

-

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

-

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

-

Updating to new layers

-

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

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

Notifying the remote client about your local layer

-

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

-

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

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

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

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

Styled text with message entities

- -

Telegram supports styled text using message entities.

-

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

-

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

-

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

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

The following entities can also be used to mention users:

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

Error handling

- -

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

-

An error is characterized by several parameters:

-

Error Code

-

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

-

Error Type

-

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

-
-

Error Constructors

-

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

-

Below is a list of error codes and their meanings:

-

303 SEE_OTHER

-

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

-

Examples of Errors:

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

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

-

400 BAD_REQUEST

-

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

-

Examples of Errors:

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

401 UNAUTHORIZED

-

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

-

Examples of Errors:

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

403 FORBIDDEN

-

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

-

404 NOT_FOUND

-

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

-

406 NOT_ACCEPTABLE

-

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

-

420 FLOOD

-

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

-

Error Example:

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

500 INTERNAL

-

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

-

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

-

Other Error Codes

-

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

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

File references

- -

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

-

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

-

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

-

Another example:

-

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

-

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

-

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

-

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

-

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

-

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

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

Uploading and Downloading Files

- -
- -

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

-

Uploading files

-

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

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

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

-

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

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

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

-

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

-

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

-

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

-

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

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

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

- -

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

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

Albums, grouped media

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

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

-

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

-

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

-

Re-using pre-uploaded files

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

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

-

Uploading profile or chat pictures

-
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-
-photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
-
-inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;
-
-inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
-
-inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
-inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;
-
----functions---
-
-photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
-photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;
-
-messages.editChatPhoto#ca4c79d8 chat_id:int 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#27d69997 flags:# big:flags.0?true peer:InputPeer volume_id:long local_id:int = InputFileLocation;
-inputStickerSetThumb#dbaeae9 stickerset:InputStickerSet volume_id:long local_id:int = InputFileLocation;
-
-inputStickerSetEmpty#ffb62b95 = InputStickerSet;
-inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
-inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
-
-inputPeerSelf#7da07ec9 = InputPeer;
-inputPeerChat#179be863 chat_id:int = InputPeer;
-inputPeerUser#7b8e7de6 user_id:int access_hash:long = InputPeer;
-inputPeerChannel#20adaef8 channel_id:int 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#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;
-
    -
  • -

    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, since in most occasions they are encountered as simple fileLocationToBeDeprecated constructors without an associated photo, inputPeerPhotoFileLocation has to be used:

    -
      -
    • peer is the identifier of the peer whose photo we want to download
    • -
    • volume_id and local_id are extracted from the fileLocationToBeDeprecated of the desired quality (the logic for selecting the quality of profile pictures will be changed soon)
    • -
    -
  • -
  • -

    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 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 previews of sticker sets, inputStickerSetThumb is used (note: to download stickers and previews of stickers use the document method described above):

    - -
  • -
  • -

    For old deprecated photos, if the client has cached some old fileLocations with the deprecated secret identifier, inputFileLocation 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 id, file_reference and access_hash taken from the photo constructor
    • -
    -
  • -
-

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

-

Scheme:

-
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;
-photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
-photoSizeProgressive#5aa86a51 type:string location:FileLocation w:int h:int sizes:Vector<int> = PhotoSize;
-photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
-
-videoSize#e831c556 flags:# type:string location:FileLocation 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#e831c556 flags:# type:string location:FileLocation w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
-

A videoSize constructor is typically used for [animated profile pictures]() and video previews.

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

Downloading webfiles

-

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

-

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

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

The InputWebFileLocation constructor is generated as follows.

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

General Considerations

-

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

-

Related articles

-

Handling file references

-

How to handle file references.

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

Folders

- -
- -

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

-

Scheme:

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

-

Scheme:

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

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

-

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

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

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

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

Nope

- -

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

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

Calling API Methods

- -
- -

Layers

-

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

-

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

-

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

-

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

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

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

-

List of Available Layers

-

Saving Client Info

-

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

-

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

-

initConnection must also be called after each auth.bindTempAuthKey.

-

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

-

Disabling updates

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

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

-

Sequential Requests

-

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

-
-

invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> 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 deleted file mode 100644 index c0e81d1050..0000000000 --- a/data/core.telegram.org/api/layers.html +++ /dev/null @@ -1,1446 +0,0 @@ - - - - - Layers - - - - - - - - - - - - - -
- -
-
-
- -

Layers

- -
- -

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

-

Layer 121

-

Added SVG path previews for animated stickers.

-

Scheme 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.
  • -
-

Scheme

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

Layer 120

-

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

-

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

Scheme

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

-

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

Scheme

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

-

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

Scheme

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

-

Scheme changes

-
New Constructors
- -

Scheme

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

-

Scheme changes

-
New Methods
- -
Changed Methods
- -
New Constructors
- -
Changed Constructors
- -

Scheme

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

-

Scheme changes

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

Scheme

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

Layer 114

-

Added WebRTC signaling methods.

-

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

Scheme

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

-

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

Scheme

-
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

-

Scheme changes

-
New Methods
- -
Changed Constructors
- -

Scheme

-
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

-

Scheme changes

-
New Methods
- -
Changed Methods
- -
New Constructors
- -
Changed Constructors
- -

Scheme

-
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

-

Scheme changes

-
New Methods
- -
Changed Methods
- -
New Constructors
- -

Scheme

-
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

-

Scheme changes

-
New Methods
- -
Changed Methods
- -
New Constructors
- -
Changed Constructors
- -

Scheme

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

-

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

Scheme

-
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

-

Scheme changes

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

Scheme

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

-
New Constructors
- -

End-to-end scheme

-
===20===
-decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction; -decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction; -decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction; -decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction; -decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = 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.Im portedContacts;
-
-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. More...

-

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 deleted file mode 100644 index d6b8d19956..0000000000 --- a/data/core.telegram.org/api/live-location.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - Live geolocation - - - - - - - - - - - - - -
- -
-
-
- -

Live geolocation

- -
- -

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

-

Sending live locations

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

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

-

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

-

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

-

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

-

Receiving live locations

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

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

-

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

-

Live location previews

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

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

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

The image is then downloaded as specified here »

-

Proximity alert

-
messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
-
-messageService#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;
-

If:

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

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

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

Mentions

- -
- -

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

-
messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityMentionName#352dca58 offset:int length:int user_id:int = MessageEntity;
-inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
-
-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;
-
-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#123e05e9 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:int = channels.ChannelParticipants;
-

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

- -

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

-

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

-

Dialog mentions

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

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

-

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

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

Min constructors

- -

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

-

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

-

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

-

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

- -

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

-

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

-

Example

-

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

-

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

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

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

-

The same can be done with min channels.

-

Example implementations: Telegram for iOS, tdlib.

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

Creating your Telegram Application

- -

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

-
-

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

-
-

Obtaining api_id

-

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

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

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

-

Using the api_id

-

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

-

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

-

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

-

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

-

Using Telegram's open source code

-

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

-
-

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

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

Pagination in the API

- -
- -

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

-

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

-

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

-

limit parameter

-

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

-

offset-based pagination

-

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

-

offset_id-based pagination

-

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

-

Sample use cases:

-
    -
  • -

    Loading 20 messages, older than message with ID MSGID:

    -

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

    -
  • -
  • -

    Loading 20 messages, newer than message with ID MSGID:

    -

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

    -
  • -
  • -

    Loading 20 messages around message with ID MSGID:

    -

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

    -
  • -
-

Additional filtering

-

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

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

Hash generation

-

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

-

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

-
hash = 0
-for id in ids:
-    hash = (((hash * 0x4F25) & 0x7FFFFFFF) + id) & 0x7FFFFFFF
-

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

-

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

-

Example methods

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

Client-Side Optimization

- -

Simplified Acknowledgment of Message Delivery

-

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

-

Server Salt

-

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

-

Downloading Files and Uploading Data to the Server

-

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

-

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

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

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

-

Sending Messages in Bulk

-

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

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

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

-

Grouping Updates

-

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

-

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

-

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

-

Setting the Typing Status

-

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

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

Telegram passport

- -
- -

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

-

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

-

Overview

-

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

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

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

-

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

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

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

-

As a bot

-

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

-

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

-
-

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

-
-

Setting Up Telegram Passport

-

As per the bot API.

-

Requesting Information

-

As per the bot API.

-

Receiving information

-

Scheme:

-
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#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;
-
-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 scheme 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#d8292816 user_id:int 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:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParametersTypeRequiredDescription
domainStringYesAlways telegrampassport for Passport authorization requests.
tg:// URI are also used to resolve usernames, stickersets, translation packs and more, the domain parameter identifies the action to take when opening the link.
bot_idIntegerYesUnique identifier for the bot. You can get it from bot token. For example, for the bot token 1234567:4TT8bAc8GHUspu3ERYn-KGcvsvGB9u_n4ddy, the bot id is 1234567.
scopeUriPassportScopeYesA more compact JSON-serialized object describing the data you want to request
public_keyStringYesPublic key of the bot
nonceStringYesBot-specified nonce. Important: For security purposes it should be a cryptographically secure unique identifier of the request. In particular, it should be long enough and it should be generated using a cryptographically secure pseudorandom number generator. You should never accept credentials with the same nonce twice.
callback_urlStringOptionalSupported by some Telegram clients, specifies a callback URL to open once the process is finished or canceled.
payloadStringOptionalDeprecated parameter from Telegram Passport 1.0 that had the same function of the nonce parameter.
Services that still use a legacy version of the SDK may provide this parameter instead of the nonce.
In some cases, both the nonce and the payload parameters may be found in a URI, for backwards compatibility: in this case, the nonce parameter should always be used instead of payload.
-

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#b86ba8e1 bot_id:int 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#e7027c94 bot_id:int 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#b86ba8e1 bot_id:int scope:string public_key:string = account.AuthorizationForm;
-

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

-

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

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

Pattern matching

- -

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

-

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

-

Same with email verification codes.

-

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

-

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

-

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

-

Example implementation: telegram for android.

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

Payments API

- -
- -

You can accept payments from Telegram users via Telegram Bots.

-
-

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

-
-

Introducing Payments

-

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

-

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

-
-

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

-
-

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

-

Then, we work with payments as follows.

-

1. Create Invoice

-
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;
-
-labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
-
-invoice#c30aa358 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> = Invoice;
-
-inputMediaInvoice#f4e096c3 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param: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#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;
-
-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#c30aa358 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> = 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#3f56aea3 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true 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;
-
----functions---
-
-payments.getPaymentForm#99f09745 msg_id:int = 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#c30aa358 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> = 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#770a8e74 flags:# save:flags.0?true 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#e0cdc940 query_id:long user_id:int 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;
-inputPaymentCredentialsAndroidPay#ca05d50e payment_token:DataJSON google_transaction_id:string = InputPaymentCredentials;
-
-
-payments.paymentForm#3f56aea3 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true 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;
-

3.1 Web payment

-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-
-payments.paymentForm#3f56aea3 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true 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;
-

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#3f56aea3 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true 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;
-

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#3f56aea3 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true 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;
-

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

-
inputPaymentCredentialsAndroidPay#ca05d50e payment_token:DataJSON google_transaction_id:string = InputPaymentCredentials;
-

On Android devices, Google Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsAndroidPay 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#3f56aea3 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true 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;
-
-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;
-inputPaymentCredentialsAndroidPay#ca05d50e payment_token:DataJSON google_transaction_id:string = InputPaymentCredentials;
-
-payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
-payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
-
----functions---
-
-payments.sendPaymentForm#2b8879b3 flags:# msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials = 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#5d2f3aa9 flags:# query_id:long user_id:int 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#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;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-
-payments.paymentReceipt#500911e1 flags:# date:int bot_id:int invoice:Invoice provider_id:int info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
-
----functions---
-
-payments.getPaymentReceipt#a092a980 msg_id:int = payments.PaymentReceipt;
-

In case the bot confirms the order, Telegram requests the payment provider to complete the transaction. If the payment information was entered correctly and the payment goes through, the Telegram API will modify the invoice message and send a service message as described below. Once your bot receives this message, it should proceed with delivering the goods or services purchased by the user.

-

If all is OK, the user receives a payments.paymentResult in reply to the payments.sendPaymentForm query, containing info about the updated invoice message in the form of an updateEditMessage.

-

The invoice message will be updated as follows: the attached messageMediaInvoice will now have a receipt_msg_id field. -Clients should treat invoice messages with a receipt_msg_id field as receipt messages, locally modifying the label of the keyboardButtonBuy button to a localized version of the word Receipt. -From this point, clicking on the Receipt button should trigger a call to payments.getPaymentReceipt, providing the receipt_msg_id to the msg_id field, which will return info about the transaction.

-

The payment will also generate one service message of type messageActionPaymentSent or messageActionPaymentSentMe, replying to the invoice. -For bots, the service message will be of type messageActionPaymentSentMe, for users it will be a messageActionPaymentSent.

-
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
-messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/pfs.html b/data/core.telegram.org/api/pfs.html deleted file mode 100644 index fb931f0d94..0000000000 --- a/data/core.telegram.org/api/pfs.html +++ /dev/null @@ -1,138 +0,0 @@ - - - - - Perfect Forward Secrecy - - - - - - - - - - - - - -
- -
-
-
- -

Perfect Forward Secrecy

- -
Related articles
-

-
-

This article is about Perfect Forward Secrecy in cloud chats, see also PFS in Secret Chats.

-
-
-

Telegram supports Perfect Forward Secrecy (PFS).

-

To make this possible, the client generates a permanent authorization key using p_q_inner_data and a temporary key using p_q_inner_data_temp. (See Creating an Authorization Key for more info.) These 2 operations may be done in parallel and even using the same connection. The client must save an expires_at unix timestamp expires_at = time + expires_in.

-

Important: in order to achieve PFS, the client must never use the permanent auth_key_id directly. Every message that is sent to MTProto, must be encrypted by a temp_auth_key_id, that was bound to the perm_auth_key_id.

-

An unbound temp_auth_key_id may only be used with the following methods:

- -

In order to bind a temporary authorization key to the permanent key the client creates a special binding message and executes the auth.bindTempAuthKey method using temp_auth_key. Once auth.bindTempAuthKey has been executed successfully, the client may signUp / signIn using other auth.* methods and continue using the API as usual; the client must also rewrite client info using initConnection after each binding. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

-

Once the temporary key expires, the client needs to generate a new temporary key using p_q_inner_data_temp. Then it needs to re-bind that new temporary key to the initial permanent key. A new key can also be generated in advance, so that the client has a new key ready by the time the old one has expired.

-

For additional security, the client can store the temporary authorization key in RAM only and never save it in persistent storage.

-

A temporary authorization key may expire at any moment before expires_at, since such keys are also stored only in the RAM on the server-side. Be prepared to handle resulting MTProto errors correctly (non-existent auth_key_id results in a 404 error).

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/pin.html b/data/core.telegram.org/api/pin.html deleted file mode 100644 index 51e6db24c0..0000000000 --- a/data/core.telegram.org/api/pin.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - Pinned messages - - - - - - - - - - - - - -
- -
-
-
- -

Pinned messages

- -
- -

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

-
message#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;
-
-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;
-
----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#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;
-chatFull#1b7c9db3 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 = ChatFull;
-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;
-
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;
-
----functions---
-
-messages.search#c352eec 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;
-

The pinned_msg_id of userFull, chatFull, channelFull contains the ID of only the latest pinned message.
-To obtain a full list, use messages.search with inputMessagesFilterPinned filter.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/poll.html b/data/core.telegram.org/api/poll.html deleted file mode 100644 index b6a24f8418..0000000000 --- a/data/core.telegram.org/api/poll.html +++ /dev/null @@ -1,199 +0,0 @@ - - - - - Poll - - - - - - - - - - - - - -
- -
-
-
- -

Poll

- -
- -

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

-

Sending a poll

-
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
-
-poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
-
-inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

To send a poll in a chat, call messages.sendMedia, providing an inputMediaPoll:

-
    -
  • -

    poll is the actual poll constructor, containing:

    -
      -
    • question - The poll title, aka the poll's title
    • -
    • answers - A vector of possible answers (2-10), each with a visible title text , and a unique option identifier (1-100 bytes)
    • -
    • closed - Whether the poll is closed
    • -
    • public_voters - Whether cast votes are publicly visible to all users (non-anonymous poll)
    • -
    • multiple_choice - Whether multiple options can be chosen as answer
    • -
    • quiz - Whether this is a quiz with correct answer IDs specified in inputMediaPoll.correct_answers
    • -
    • close_period - Amount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date .
    • -
    • close_date - Point in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period .
      -These last two parameters are exactly the same, except that one uses absolute, the other relative unixtime.
    • -
    -
  • -
  • -

    correct_answers - For quizes, option ID of the only correct answer

    -
  • -
  • -

    solution - Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds

    -
  • -
  • -

    solution_entities - Styled text message entities for the solution explanation

    -
  • -
-

In order to prematurely close the poll, preventing further votes, use messages.editMessage, setting the poll.closed flag to true.

-

Voting in polls

-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
-
-pollResults#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;
-
-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#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;
-
-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#a28e5559 user_id:int option:bytes date:int = MessageUserVote;
-messageUserVoteInputOption#36377430 user_id:int date:int = MessageUserVote;
-messageUserVoteMultiple#e8fe0de user_id:int 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#42f88f2c poll_id:long user_id:int options:Vector<bytes> = Update;
-
----functions---
-
-messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList; 
-

messages.getPollVotes can be used to get poll results for non-anonymous polls, to see how each user voted for a poll option.
-Bots will also receive an updateMessagePollVote every time a user their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/push-updates.html b/data/core.telegram.org/api/push-updates.html deleted file mode 100644 index e5bd34b668..0000000000 --- a/data/core.telegram.org/api/push-updates.html +++ /dev/null @@ -1,985 +0,0 @@ - - - - - Handling PUSH-notifications - - - - - - - - - - - - - -
- -
-
-
- -

Handling PUSH-notifications

- -
- -

Configuring the application

-

To be able to send APNS notifications to Apple servers or GCM notifications to Google servers, application certificates (APNS) or an application key (GCM) must be specified in the application settings.

-

Subscribing to notifications

-

To subscribe to notifications, the client must invoke the account.registerDevice query, passing in token_type and token as parameters that identify the current device. It is useful to repeat this query at least once every 24 hours or when restarting the application. Use account.unregisterDevice to unsubscribe.

-

The following modes are supported:

-
    -
  • 1 - APNS (device token for apple push)
  • -
  • 2 - FCM (firebase token for google firebase)
  • -
  • 3 - MPNS (channel URI for microsoft push)
  • -
  • 4 - Deprecated: Simple push (endpoint for firefox's simple push API)
  • -
  • 5 - Ubuntu phone (token for ubuntu push)
  • -
  • 6 - Blackberry (token for blackberry push)
  • -
  • 7 - MTProto separate session
  • -
  • 8 - WNS (windows push)
  • -
  • 9 - APNS VoIP (token for apple push VoIP)
  • -
  • 10 - Web push (web push, see below)
  • -
  • 11 - MPNS VoIP (token for microsoft push VoIP)
  • -
  • 12 - Tizen (token for tizen push)
  • -
-

For 10 web push, the token must be a JSON-encoded object with the following keys:

-
    -
  • endpoint: Absolute URL exposed by the push service where the application server can send push messages
  • -
  • keys: P-256 elliptic curve Diffie-Hellman parameters in the following object
      -
    • p256dh: Base64url-encoded P-256 elliptic curve Diffie-Hellman public key
    • -
    • auth: Base64url-encoded authentication secret
    • -
    -
  • -
-

Notification encryption

-

For FCM and APNS VoIP, an optional encryption key used to encrypt push notifications can be passed to account.registerDevice (secret). This key (auth_key) is used to encrypt the payloads using MTProto v2.

-

The FCM payload will be a JSON payload, containing a p field with the base64-encoded encrypted MTProto payload. After decryption, the result will be a JSON object, prefixed by a 32-bit little-endian integer with the length of the JSON payload. As usual, make sure to follow all security checks as described in the MTProto docs.

-

Example implementation.

-

As mentioned above, payloads can also be encrypted using P-256 Elliptic Curve Diffie-Hellman when using web push.

-

Notification structure

-

An (optionally encrypted) notification is provided as a JSON object in the following format:

-
{
-  "data": {
-    "loc_key": "CHAT_MESSAGE_CONTACT",
-    "loc_args": ["John Doe", "My magical group", "Contact Exchange"],
-    "user_id": 14124122,
-    "custom": {
-      "chat_id": 241233,
-      "msg_id": 123
-    },
-    "sound": "sound1.mp3",
-  }
-}
-

Each notification has several parameters that describe it.

-

Notification type

-

data.loc_key - A string literal in the form /[A-Z_0-9]+/, which summarizes the notification. For example, CHAT_MESSAGE_TEXT.

-

Notification text arguments

-

data.loc_args - A list or arguments which, when inserted into a template, produce a readable notification.

-

Custom parameters

-

data.custom - Parameters which are be passed into the application when a notification is opened.

-

Sound

-

data.sound - The name of an audio file to be played.

-

User id

-

data.user_id - ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

-

Processing notifications

-

In principle, data.loc_key, data.custom, and an Internet connection are sufficient to generate a notification. Obviously, if possible, when generating a visual notification you need not use all of the transmitted data and may rely on the information already stored on the client. But if a user or a chat is not cached locally, the values passed in loc_args may also be used. data.user_id is the ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

-

Service notifications

-

The following notifications can be used to update app settings.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeExtra custom argumentsDescription
DC_UPDATEdc - number of the data-center
addr - server address with port number in the format 111.112.113.114:443
In case the client gets this notification, it is necessary to add the received server address to the list of possible addresses. In case the address of the first DC was passed (dc=1), it is recommended to call it immediately using help.getConfig to update dc-configuration.
MESSAGE_DELETEDchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
messages: Comma-separated IDs of messages that were deleted
Messages were deleted, remove multiple notifications for this chat
READ_HISTORYchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
max_id: Maximum ID of read messages
Message history was read, remove multiple notifications for this chat
GEO_LIVE_PENDING Any of the live locations currently being shared should be updated
SESSION_REVOKE Logout and remove DB for specified session by data.user_id, only apply if coming from an MTProto-encrypted payload
MESSAGE_MUTED Sent rarely, every 10th message in chats or once per 15 sec in PM, to update badge or download messages
-

Possible Notifications

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeTemplate exampleArgumentsExtra custom arguments
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_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)
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_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)
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_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)
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_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_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_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_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)
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_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_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_STICKER{1} sent you a {2}sticker1. User name
2. Sticker emoji with included trailing space or empty string
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_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_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_GEO{1} sent you a map1. 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} started sharing their 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_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_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_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_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_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_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_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)
MESSAGES{1} sent you an album1. User namefrom_id: author identifier
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_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_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_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_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_STICKER{1} posted a {2}sticker1. Channel name
2. Sticker emoji with included trailing space or empty string
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_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_GEO{1} posted a map1. 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_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_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_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_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_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_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)
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)
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_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_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_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_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_STICKER{1} sent a {3}sticker to the group {2}1. User name
2. Group name
3. Sticker emoji with included trailing space or empty string
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_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_GEO{1} sent a map 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} started sharing their live location with {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_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_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_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_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_CREATED{1} invited you to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_TITLE_EDITED{1} edited the group's {2} name1. User name
2. Group name
chat_id: chat identifier
CHAT_PHOTO_EDITED{1} edited the group's {2} photo1. Message author
2. Chat name
chat_from_id: Message author identifier
chat_id: chat identifier
msg_id: ID of the 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_DELETE_MEMBER{1} kicked {3} from the group {2}1. Message author
2. Chat name
3. Dropped participant name
chat_id: chat identifier
CHAT_DELETE_YOU{1} kicked you from the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_LEFT{1} has left the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_RETURNED{1} has returned to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_JOINED{1} has joined the group {2}1. User name
2. Group name
chat_id: chat identifier
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_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_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_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
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_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_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)
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_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_STICKER{1} pinned a {2}sticker1. User name
2. Sticker emoji with included trailing space or empty string
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 with included trailing space or empty string
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_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_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_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_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_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_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)
CONTACT_JOINED{1} joined Telegram!1. Contact namecontact_id: contact identifier
AUTH_UNKNOWNNew login from unrecognized device {1}1. Device name 
AUTH_REGIONNew login from unrecognized device {1}, location: {2}1. Device name
2. Location
 
ENCRYPTION_REQUESTYou have a new message encryption_id: secret chat identifier
ENCRYPTION_ACCEPTYou have a new message encryption_id: secret chat identifier
ENCRYPTED_MESSAGEYou have a new message encryption_id: secret chat identifier
random_id: message identifier
LOCKED_MESSAGEYou have a new message  
PHONE_CALL_REQUEST{1} is calling you!1. User namecall_ah: Call access hash
call_id: Call ID
PHONE_CALL_MISSEDYou missed a call from {1}1. User name 
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.
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/qr-login.html b/data/core.telegram.org/api/qr-login.html deleted file mode 100644 index 7f6826e861..0000000000 --- a/data/core.telegram.org/api/qr-login.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Login via QR code - - - - - - - - - - - - - -
- -
-
-
- -

Login via QR code

- -
- -

QR code login flow.

-

Related TL schema:

-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
-
-updateLoginToken#564fe691 = Update;
-
-authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
-
----functions---
-
-auth.exportLoginToken#b1b41517 api_id:int api_hash:string except_ids:Vector<int> = auth.LoginToken;
-auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
-

Exporting a login token

-

First of all, auth.exportLoginToken must be called by the app that wants to log in to an existing Telegram account.
-The method will return an auth.loginToken constructor, containing a binary login token and an expiry date (usually 30 seconds).

-

The login token must be encoded using base64url, embedded in a tg://login?token=base64encodedtoken URL and shown in the form of a QR code to the user.
-After the expiration of the current QR code, the auth.exportLoginToken method must be recalled and a new QR code must be generated automatically.

-

Accepting a login token

-

In order to log in, the QR code must be scanned and accepted by an already logged-in Telegram app using auth.acceptLoginToken.
-The token must be extracted from the tg://login URI and base64url-decoded before using it in the method.

-

Possible errors returned by the method are:

-
    -
  • 400 - AUTH_TOKEN_INVALID, an invalid authorization token was provided
  • -
  • 400 - AUTH_TOKEN_EXPIRED, the provided authorization token has expired and the updated QR-code must be re-scanned
  • -
  • 400 - AUTH_TOKEN_ALREADY_ACCEPTED, the authorization token was already used
  • -
-

The method will return an authorization object, containing info about the app and session that we just authorized.

-

Confirming (importing) the login token

-

After the logged-in app calls auth.acceptLoginToken and accepts the login token, the app that is trying to login will receive an updateLoginToken update, which should trigger a second call to the auth.exportLoginToken method.

-

This second call should then return an auth.loginTokenSuccess constructor, indicating successful login, essentially allowing further authorized interaction with the API.

-

If, however, there is a DC mismatch between the two apps, auth.loginTokenMigrateTo is returned instead, to which the app that is trying to login should respond by calling auth.importLoginToken with the specified token, to the specified DC.

-

This call should then finally return a auth.loginTokenSuccess constructor.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/recent-actions.html b/data/core.telegram.org/api/recent-actions.html deleted file mode 100644 index 433be8da35..0000000000 --- a/data/core.telegram.org/api/recent-actions.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Admin log - - - - - - - - - - - - - -
- -
-
-
- -

Admin log

- -
- -

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

-
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
-channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
-channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLinkedChat#a26f881b prev_value:int new_value:int = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
-
-channelAdminLogEvent#3b5a3e40 id:long date:int user_id:int 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 = 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/requests.html b/data/core.telegram.org/api/requests.html deleted file mode 100644 index 2fd75ee2c4..0000000000 --- a/data/core.telegram.org/api/requests.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - Requests - - - - - - - - - - - - - -
- -
-
-
- -

Requests

- -

Let's consider several typical interaction scenarios for two users.

-

One user knows the other's number

-

User A knows phone number of B (for instance, A has B's number in the phone book). But B does not know А's number. User A sends message to B. Immediately prior to sending a message relevant check is executed at the server side and the link between A and B will change automatically: A's number becomes available for B (user A is then presented as constructor userRequest). -The same happens if user B not having A's number sends a message to the latter. A's number also becomes available to B.

-

Users do not know numbers of each other

-

User A has found user B in a chat, geochat or any other way. For both of them phone numbers are not available (in API - constructor userForeign). A starts chat with B. When messaging A's number will not become available for B and vice versa. To provide B with A's number it is necessary to send him personal message with contact info (phone number should be transferred in constructor inputMediaContact using method messages.sendMedia). -Now B having personal message with A's phone number can store it in his phone book and import it using method contacts.importContacts to have it in contacts. With all that, it is not mandatory for him to send his number: after any message later between them B's number will be available for A (see One user knows the other's number).

-

Both user know each other number

-

This is quite obvious: messaging does not change links since target state has been reached.

-

Technical features

-

Since when sending messages to a current user updates on changed links are not sent constructors containing updated links were added to resulting types of messaging methods:

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

To indicate for clients that these constructors are supported one should use 3rd layer.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/rights.html b/data/core.telegram.org/api/rights.html deleted file mode 100644 index d9bbb09f23..0000000000 --- a/data/core.telegram.org/api/rights.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - Admin, banned, default rights - - - - - - - - - - - - - -
- -
-
-
- -

Admin, banned, default rights

- -
- -

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

-

They can be modified as follows:

-

Admin rights

-

channels.editAdmin can be used to modify the admin rights of a user in a channel or supergroup. -Legacy groups do not allow setting granular admin permissions, messages.editChatAdmin has to be used, instead.

-

Permissions are defined by the chatAdminRights constructor, some admin rights can only be used for channels, others both for channels and supergroups (see the constructor page).

-

Banned rights

-

channels.editBanned can be used to modify the rights of a user in a channel or supergroup, to ban/kick a user from the group, or restrict the user from doing certain things. -Legacy groups do not allow setting granular user permissions for single users, single users can only be removed from groups using messages.deleteChatUser: however, setting global granular permissions with legacy groups is supported.

-

Permissions are defined by the chatBannedRights constructor, for more info see the constructor page.

-

Default rights

-

messages.editChatDefaultBannedRights can be used to modify the rights of all users in a channel, supergroup or legacy group, to restrict them from doing certain things.

-

Permissions are defined by the chatBannedRights constructor: all flags can be used except for view_messages, for more info see the constructor page.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/scheduled-messages.html b/data/core.telegram.org/api/scheduled-messages.html deleted file mode 100644 index c32f442277..0000000000 --- a/data/core.telegram.org/api/scheduled-messages.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - Scheduled messages - - - - - - - - - - - - - -
- -
-
-
- -

Scheduled messages

- -

Telegram allows scheduling messages.

-
message#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;
-
-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#e2c2685b peer:InputPeer hash:int = messages.Messages;
-messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
-
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
-

Clients can manually edit the schedule queue of a certain chat, providing the scheduled message ID obtained from updateNewScheduledMessage.

- -

Modifying scheduled messages will generate an updateNewScheduledMessage with the same ID, and updated information.
-Deleting scheduled messages will generate an updateDeleteScheduledMessages.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/search.html b/data/core.telegram.org/api/search.html deleted file mode 100644 index 45f6d282c9..0000000000 --- a/data/core.telegram.org/api/search.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - Search - - - - - - - - - - - - - -
- -
-
-
- -

Search

- -
- -

Telegram allows applying detailed message filters while looking for messages in chats.

-

Search filters

-
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
-inputMessagesFilterPhotos#9609a51c = MessagesFilter;
-inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
-inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
-inputMessagesFilterDocument#9eddf188 = MessagesFilter;
-inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
-inputMessagesFilterGif#ffc86587 = MessagesFilter;
-inputMessagesFilterVoice#50f5c392 = MessagesFilter;
-inputMessagesFilterMusic#3751b49e = MessagesFilter;
-inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
-inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
-inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
-inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
-inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
-inputMessagesFilterGeo#e7026d0d = MessagesFilter;
-inputMessagesFilterContacts#e062db83 = MessagesFilter;
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;
-
-messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
-
----functions---
-
-messages.search#c352eec 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;
-
-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 scheme above.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/srp.html b/data/core.telegram.org/api/srp.html deleted file mode 100644 index 8bc0a6cdfb..0000000000 --- a/data/core.telegram.org/api/srp.html +++ /dev/null @@ -1,255 +0,0 @@ - - - - - Two-factor authentication - - - - - - - - - - - - - -
- -
-
-
- -

Two-factor authentication

- -
- -

Telegram uses the Secure Remote Password protocol version 6a to implement 2FA.

-

Example impementation: tdlib.

-

Checking the password with SRP

-

To login to an account protected by a 2FA password or to perform some other actions (like changing channel owner), you will need to verify the user's knowledge of the current 2FA account password.

-

To do this, first the client needs to obtain SRP parameters and the KDF algorithm to use to check the validity of the password via account.getPassword method. For now, only the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow algorithm is supported, so we'll only explain that.

-

Then, after the user provides a password, the client should generate an InputCheckPasswordSRP object using SRP and a specific KDF algorithm as shown below and pass it to appropriate method (e.g. auth.checkPassword in case of authorization).

-

This extension of the SRP protocol uses the password-based PBKDF2 with 100000 iterations using sha512 (PBKDF2HMACSHA512iter100000).
PBKDF2 is used to additionally rehash the x parameter, obtained using a method similar to the one described in RFC 2945 (H(s | H ( I | password | I) | s) instead of H(s | H ( I | ":" | password)) (see below).

-

Here, | denotes concatenation and + denotes the arithmetical operator +.
In all cases where concatenation of numbers passed to hashing functions is done, the numbers must be used in big-endian form, padded to 2048 bits; all maths is modulo p.
Instead of I, salt1 will be used (see SRP protocol).
Instead of s, salt2 will be used (see SRP protocol).

-

The main hashing function H is sha256:

-
    -
  • H(data) := sha256(data)
  • -
-

The salting hashing function SH is defined as follows:

-
    -
  • SH(data, salt) := H(salt | data | salt)
  • -
-

The primary password hashing function is defined as follows:

-
    -
  • PH1(password, salt1, salt2) := SH(SH(password, salt1), salt2)
  • -
-

The secondary password hashing function is defined as follows:

-
    -
  • PH2(password, salt1, salt2) := SH(pbkdf2(sha512, PH1(password, salt1, salt2), salt1, 100000), salt2)
  • -
-

Client-side, the following parameters are extracted from the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow object, contained in the account.password object.

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

    -

    If the client has an inadequate random number generator, it makes sense to use the secure_random of account.password as additional seed.

    -
  • -
  • password := (user-provided password)

    -
  • -
  • salt1 := algo.salt1
  • -
  • salt2 := algo.salt2
  • -
  • g_b := srp_B
    srp_B and srp_id are extracted from the account.password object.
  • -
-

The k parameter is generated, both on client and server:

-
    -
  • k := H(p | g)
  • -
-

The shared param u is generated: the client does this, and the server does the same with the g_a we will send him later (see below)

-
    -
  • u := H(g_a | g_b)
  • -
-

The final parameters are generated client-side only:

-
    -
  • x := PH2(password, salt1, salt2)
  • -
  • v := pow(g, x) mod p
  • -
-

The server already has v, from when we set the password.

-

A final shared param is generated, for commodity:

-
    -
  • k_v := (k * v) mod p
  • -
-

Finally, the key exchange process starts on both parties.

-

The client computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and generates:

-
    -
  • g_a := pow(g, a) mod p.
  • -
-

The server computes a 2048-bit number b using sufficient entropy and generates the g_b parameter that was sent to us (see above).

-
    -
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • -
-

Finally, the SRP session keys are generated:

-

Client side:

-
    -
  • t := (g_b - k_v) mod p (positive modulo, if the result is negative increment by p)
  • -
  • s_a := pow(t, a + u * x) mod p
  • -
  • k_a := H(s_a)
  • -
-

Server side:

-
    -
  • s_b := pow(g_a * (pow(v, u) mod p), b) mod p
  • -
  • k_b := H(s_b)
  • -
-

Since:

-
    -
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • -
  • t := (g_b - k_v) mod p
  • -
  • t := ((k_v + (pow(g, b) mod p)) - k_v) mod p
  • -
  • t := pow(g, b) mod p
  • -
  • s_a := pow(t, a + u * x) mod p
  • -
  • s_a := pow(pow(g, b) mod p, a + u * x) mod p
  • -
-

And:

-
    -
  • g_a := pow(g, a) mod p
  • -
  • v := pow(g, x) mod p
  • -
  • s_b := pow(g_a * (pow(v, u) mod p), b) mod p
  • -
  • s_b := pow((pow(g, a) mod p) * (pow(pow(g, x) mod p, u) mod p), b) mod p
  • -
  • s_b := pow(pow(g, a + x * u) mod p, b) mod p
  • -
  • s_b := pow(pow(g, b) mod p, a + u * x) mod p

    -
  • -
  • s_a := pow(pow(g, b) mod p, a + u * x) mod p

    -
  • -
-

This means:

-
    -
  • s_b === s_a
  • -
  • k_b === k_a
  • -
-

Finally, as per SRP:

-
    -
  • M1 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_a)
  • -
-

M1 is passed to inputCheckPasswordSRP, along with g_a (as A parameter) and the srp_id, extracted from the account.password object.

-

The server then computes:

-
    -
  • M2 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_b)
  • -
-

Since we said that:

-
    -
  • s_b === s_a
  • -
  • k_b === k_a
  • -
-

This means, if everything was done correctly,

-
    -
  • M1 === M2
  • -
-

If the password isn't correct, 400 PASSWORD_HASH_INVALID will be returned.

-

Setting a new 2FA password

-

To set a new 2FA password use the account.updatePasswordSettings method.
If a password is already set, generate an InputCheckPasswordSRP object as per checking passwords with SRP, and insert it in the password field of the account.updatePasswordSettings method.
To remove the current password, pass an empty new_password_hash in the account.PasswordInputSettings object.

-

To set a new password, use the SRP parameters and the KDF algorithm obtained using account.getPassword when generating the password field.
Then generate a new new_password_hash using the KDF algorithm specified in the new_settings, just append 32 sufficiently random bytes to the salt1, first.
Proceed as for checking passwords with SRP, just stop at the generation of the v parameter, and use it as new_password_hash:

-
    -
  • v := pow(g, x) mod p
  • -
-

As usual in big endian form, padded to 2048 bits.

-

Email verification

-

When setting up two-factor authorization, it is recommended to set up a recovery email, to allow recovery of the password through the user's email address, in case they forget it.

-

To set up a recovery email, it must first be verified.
This can be done directly when setting the new password using account.updatePasswordSettings by setting the email parameter and flag in the account.passwordInputSettings constructor.
If the email isn't verified, an EMAIL_UNCONFIRMED_X 400 error will be returned, where X is the length of the verification code that was just sent to the email.
Use account.confirmPasswordEmail to enter the received verification code and enable the recovery email.
Use account.resendPasswordEmail to resend the verification code.
Use account.cancelPasswordEmail to cancel the verification code.

-

To get the current recovery email, use account.getPasswordSettings.

-

Email recovery

-

In order to recover a forgotten 2FA password, an email must be sent to the previously specified address using the auth.requestPasswordRecovery method.
Then use auth.recoverPassword with the received code to delete the current 2FA password, to set a new one follow these instructions.

-

Related pages

-

SRP design

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/stats.html b/data/core.telegram.org/api/stats.html deleted file mode 100644 index 61391864a5..0000000000 --- a/data/core.telegram.org/api/stats.html +++ /dev/null @@ -1,297 +0,0 @@ - - - - - Channel statistics - - - - - - - - - - - - - -
- -
-
-
- -

Channel statistics

- -
- -

Telegram offers detailed channel statistics for channels and supergroups.

-

Channel statistics

-

Scheme:

-
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

-

Scheme:

-
statsGroupTopPoster#18f3d0f7 user_id:int messages:int avg_chars:int = StatsGroupTopPoster;
-statsGroupTopInviter#31962a4c user_id:int invitations:int = StatsGroupTopInviter;
-statsGroupTopAdmin#6014f412 user_id:int deleted:int kicked:int banned:int = StatsGroupTopAdmin;
-
-stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
-
----functions---
-
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;
-

Administrators of supergroups of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMegagroupStats to get detailed supergroup statistics.
-The returned stats.broadcastStats contains multiple statistics, see the constructor page for more info ».

-

Message statistics

-
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
-
----functions---
-
-stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;
-

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMessageStats to get statistics of a specific message.
-The returned stats.messageStats contains the view graph of the message.

-

Graph visualization

-

There are four available visualizations for graph types:

- -

Graph modifiers (see various graphs for examples):

-
    -
  • y_scaled - Indicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph
  • -
  • percentage - Indicates whether value percentages should be shown in labels
  • -
  • stacked - Depending on the graph type, indicates stacking of multiple columns in the same graph
  • -
-

Graph syntax

-
statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Certain graphs are not directly sent in the stats.broadcastStats constructor to reduce server load: instead, those graphs will be sent as a statsGraphAsync constructor, and should be fetched separately using stats.loadAsyncGraph.

-

After obtaining the full statsGraph constructor, clients should parse the JSON graph object in the json field.

-

Object structure:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
KeyGraph title
columnsArray of all data column arrays in the chart. Each column array has its label at position 0, followed by values.
typesGraphs types for each of the column arrays (object, "label": "type"):
- line - line graph
- area - area graph
- step - step graph
- bar - bar graph
- x - x axis values for each of the charts at the corresponding positions, UNIX timestamps in milliseconds.
colorsColor for each type (object, "label": "colorKey#AAAAAA"; see chart colors).
namesLocalized name for each variable (object, "label": "Name")
subchartObject indicating the default zoom range for the graph, this is object's structure:
- show - Whether to use the specified zoom range (boolean)
- defaultZoom - An array with two x values, indicating the two ends of the default zoom range
y_scaledIndicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph (boolean, see various graphs for examples)
percentageIndicates whether value percentages should be shown in labels (boolean, see various graphs for examples)
stackedDepending on the graph type, indicates stacking of multiple columns in the same graph (boolean, see various graphs for examples)
- -

The following chart restrictions apply:

-
    -
  • Up to 50 columns on one graph must be supported.
  • -
  • Chart types are always the same for every column in the graph.
  • -
  • The bar chart type and stacked option are always used together.
  • -
  • percentage is always used with the area graph. - -
  • -
-

Chart zooming

-
statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Graphs that support zooming will contain a zoom_token in the statsGraph constructor.
-Said token should be then used as token in a new stats.loadAsyncGraph call triggered when the user clicks on the label, related to a certain x axis in the graph (see graph examples).
-The x coordinate of the label should be provided to the x parameter; the method will then return (if available) a more detailed subgraph.
-If not enough data is available, a localized statsGraphError will be returned.

-

Typical zoom visualization rules:

- -

Chart colors

-

Chart colors can be provided as a color key, followed by the primary color value in hex format:

-
red#e05356
-

The color key can be one of red, lightblue, lightgreen, golden, green, orange, blue, indigo.
-Apps can choose to use a color value specified by the currently loaded theme: for example, the android app uses statisticChartLine_* themekeys for each of the color keys, check out the assets directory for a bunch of default themes with various colors for channel statistics.

-

However, the server may also choose to return just a plain color value in hex format:

-
#e05356
-

In this case, the dark flag of the stats.getBroadcastStats method can be used to choose the palette of returned colors.

-

Graph examples

-

Line graph

-

Simple single line graph

-

Step graph

-

Step graph, always "stacked" (to indicate multiple lines)

-

Bar graph

-

Bar graph with multiple lines, always "stacked" (to indicate actual stacked bars, biggest bars first)

-

Area graph

-

Mixed bar/line graph, always "stacked" (to indicate actual stacked bars, biggest bars first)

-

Piechart

-

Piechart, typically obtained only when zooming into percentage graphs

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/terms.html b/data/core.telegram.org/api/terms.html deleted file mode 100644 index 434e3efd4d..0000000000 --- a/data/core.telegram.org/api/terms.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - Telegram API Terms of Service - - - - - - - - - - - - - -
- -
-
-
- -

Telegram API Terms of Service

- -
- -

We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge. In order to ensure consistency and security across the Telegram ecosystem, all third-party client apps must comply with the following Terms of Service.

-

1. Privacy & Security

-

1.1. Telegram is a privacy-oriented platform. All client apps must, therefore, guard their users' privacy with utmost care and comply with our Security Guidelines.
-1.2. Developers are welcome to add new features or improve and extend existing Telegram features provided that these modifications do not violate these Terms of Service.
-1.3. As a client developer, you must make sure that all the basic features of the main Telegram apps function correctly and in an expected way both in your app and when users of your app communicate with other Telegram users. It is forbidden to force users of other Telegram clients to download your app in order to view certain messages and content sent using your app.
-1.4. It is forbidden to interfere with the basic functionality of Telegram. This includes but is not limited to: making actions on behalf of the user without the user's knowledge and consent, preventing self-destructing content from disappearing, preventing last seen and online statuses from being displayed correctly, tampering with the 'read' statuses of messages (e.g. implementing a 'ghost mode'), preventing typing statuses from being sent/displayed, etc.

-

2. Transparency

-

2.1. You must obtain your own api_id for your application.
-2.2. We offer our API free of charge, but your users must be aware of the fact that your app uses the Telegram API and is part of the Telegram ecosystem. This fact must be featured prominently in the app's description in the app stores and in the in-app intro if your app has it.
-2.3. To avoid confusion, the title of your app must not include the word “Telegram”. An exception can be made if the word “Telegram” is preceded with the word “Unofficial” in the title.
-2.4. You must not use the official Telegram logo for your app. Both the Telegram brand and its logo are registered trademarks protected by law in almost every country.

-

3. Advertising & Monetization

-

3.1. Developers are allowed to monetize their coding efforts through advertising or other legitimate means.
-3.2. If you decide to monetize your app, you must clearly mention all the methods of monetization that are used in your app in all its app store descriptions.

-

4. Breach of terms

-

4.1. If your app violates these terms, we will notify the Telegram account responsible for the app about the breach of terms.
-4.2. If you do not update the app to fix the highlighted issues within 10 days, we will have to discontinue your access to Telegram API and contact the app stores about the removal of your apps that are using the Telegram API in violation of these terms.

-

We reserve the right to expand these terms and guidelines as the need arises. We will inform client developers of such changes via an in-app notification to their accounts connected to the app in question.

-
-

Back to Creating Your Telegram Application »

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/threads.html b/data/core.telegram.org/api/threads.html deleted file mode 100644 index 49791d653f..0000000000 --- a/data/core.telegram.org/api/threads.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - Threads - - - - - - - - - - - - - -
- -
-
-
- -

Threads

- -
- -

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

-

Message threads

-

Schema:

-
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
-
-messageReplies#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;
-
-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;
-
----functions---
-
-messages.search#c352eec 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;
-

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

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:# 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#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;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
-
----functions---
-
-contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
-
-contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
-

Since a user can comment in channel posts without joining the actual discussion supergroup, there must be a way for them to receive notifications about replies in comment sections.
-For this reason, a special @replies username is provided. -Its ID for main and testing endpoints can be seen in the tdlib sources.

-

When someone replies to one of our messages in the comment section of a channel post, and the user is not subscribed to the discussion group, the client will receive two updates:

-
    -
  • An updateNewChannelMessage from the discussion group itself, structured just like any other update coming from a subscribed group, with:
      -
    • id set to the ID of the reply
    • -
    • from_id set to the peer that replied to us
    • -
    • peer_id set to the peer of the discussion group
    • -
    • reply_to.reply_to_msg_id set to the ID of our message
    • -
    • reply_to.reply_to_top_id set to the thread ID.
    • -
    -
  • -
  • An updateNewMessage
      -
    • id set to the common ID sequence for users
    • -
    • from_id set to the peer of @replies
    • -
    • peer_id set to our own peer
    • -
    • fwd_from.saved_from_msg_id set to the ID of the reply
    • -
    • fwd_from.from_id set to the the peer that replied to us
    • -
    • reply_to.reply_to_peer_id set to the peer of the discussion group
    • -
    • reply_to.reply_to_msg_id set to the ID of our message
    • -
    • reply_to.reply_to_top_id set to the thread ID
    • -
    -
  • -
-

Clients should display messages coming from @replies as a read-only supergroup, with each reply displayed as a separate message from the author of the reply, with a "View in chat" button like for channel comments.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/top-rating.html b/data/core.telegram.org/api/top-rating.html deleted file mode 100644 index a4860d908e..0000000000 --- a/data/core.telegram.org/api/top-rating.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - Top peer rating - - - - - - - - - - - - - -
- -
-
-
- -

Top peer rating

- -

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

-

Schema:

-
topPeer#edcdc05b peer:Peer rating:double = TopPeer;
-
-topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
-topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
-topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
-topPeerCategoryGroups#bd17a14a = TopPeerCategory;
-topPeerCategoryChannels#161d9628 = TopPeerCategory;
-topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
-topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
-topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;
-
-topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;
-
-contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
-contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
-contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
-
----functions---
-
-contacts.getTopPeers#d4982db5 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:int = 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 scheme described above, it is the time when they were received.
  • -
-
topPeer.rating += e^((dateOpened - normalizeRate) / config.rating_e_decay)
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/updates.html b/data/core.telegram.org/api/updates.html deleted file mode 100644 index 5bcca1471a..0000000000 --- a/data/core.telegram.org/api/updates.html +++ /dev/null @@ -1,226 +0,0 @@ - - - - - Working with Updates - - - - - - - - - - - - - -
- -
-
-
- -

Working with Updates

- -
- -

When a client is being actively used, events will occur that affect the current user and that they must learn about as soon as possible, e.g. when a new message is received. To eliminate the need for the client itself to periodically download these events, there is an update delivery mechanism in which the server sends the user notifications over one of its available connections with the client.

-

Subscribing to Updates

-

Update events are sent to an authorized user into the last active connection (except for connections needed for downloading / uploading files).

-

So to start receiving updates the client needs to init connection and call API method, e.g. to fetch current state.

-

Event sequences

-

All events are received from the socket as a sequence of TL-serialized Updates objects, which might be optionally gzip-compressed in the same way as responses to queries.

-

Each Updates object may contain single or multiple Update objects, representing different events happening.

-

In order to apply all updates in precise order and to guarantee that no update is missed or applied twice there is seq attribute in Updates constructors, and pts (with pts_count) or qts attributes in Update constructors. The client must use those attributes values in combination with locally stored state to correctly apply incoming updates.

-

When a gap in updates sequence occurs, it must be filled via calling one of the API methods. More below »

-

Updates sequence

-

As said earlier, each payload with updates has a TL-type Updates. It can be seen from the schema below that this type has several constructors.

-
updatesTooLong#e317af7e = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updateShortMessage#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;
-updateShortSentMessage#11f1331c flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> 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 chats).

-

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. -User's Secret chats have yet another common secret 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)
    • -
    • Secret message box 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 secret chat 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
-

The whole process is very similar for secret chats, but there is qts instead of pts, and events are never grouped, so it's assumed that qts_count is always equal to 1.

-

seq: checking and applying

-

On top level when handling received updates and updatesCombined there are three possible cases: -If local_seq + 1 === seq_start, the updates can be applied. -If local_seq + 1 > seq_start, the updates were already applied, and must be ignored. -If local_seq + 1 < seq_start, there's an updates gap that must be filled (updates.getDifference must be used as with common and secret event sequences).

-

If the updates were applied, local Updates state must be updated with seq and date from the constructor.

-

For all the other Updates type constructors there is no need to check seq or change a local state.

-

Recovering gaps

-

To do this, updates.getDifference (common/secret state) or updates.getChannelDifference (channel state) with the respective local states must be called. -These methods should also be called on startup, to fetch new updates (preferably with some flags to reduce server load, see the method's docs). -Manually obtaining updates is also required in the following situations:

-
    -
  • Loss of sync: a gap was found in seq / pts / qts (as described above). It may be useful to wait up to 0.5 seconds in this situation and abort the sync in case a new update arrives, that fills the gap.
  • -
  • Session loss on the server: the client receives a new session created notification. This can be caused by garbage collection on the MTProto server or a server reboot.
  • -
  • Incorrect update: the client cannot deserialize the received data.
  • -
  • Incomplete update: the client is missing data about a chat/user from one of the shortened constructors, such as updateShortChatMessage, etc.
  • -
  • Long period without updates: no updates for 15 minutes or longer.
  • -
  • The server requests the client to fetch the difference using updateChannelTooLong or updatesTooLong.
  • -
-

When calling updates.getDifference if the updates.differenceSlice constructor is returned in response, the full difference was too large to be received in one request. The intermediate status, intermediate_state, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

-

To fetch the updates difference of a channel, updates.getChannelDifference is used. -If the difference is too large to be received in one request, the final flag of the result is not set (see docs). -The intermediate status, represented by the pts, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

-

For perfomance reasons and for better user experience, client can set maximum gap size to be filled: pts_total_limit parameter of updates.getDifference and limit parameter for updates.getChannelDifference can be used.

-

If the gap is too large and there are too many updates to fetch, a *TooLong constructor will be returned. In this case, the client must re-fetch the state, re-start fetching updates from that state and follow the instructions that can be found here.

-

It is recommended to use limit 10-100 for channels and 1000-10000 otherwise.

-

Example implementations

-

Implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence.

-

Example implementations: tdlib, MadelineProto.

-

An interesting and easy way this can be implemented, instead of using various locks, is by running background loops, like in MadelineProto ».

-

PUSH Notifications about Updates

-

If a client does not have an active connection at the time of an event, PUSH Notifications will also be useful.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/url-authorization.html b/data/core.telegram.org/api/url-authorization.html deleted file mode 100644 index 144dd648fa..0000000000 --- a/data/core.telegram.org/api/url-authorization.html +++ /dev/null @@ -1,130 +0,0 @@ - - - - - Seamless Telegram Login - - - - - - - - - - - - - -
- -
-
-
- -

Seamless Telegram Login

- -

Bots may ask users to login to a certain website via Telegram when clicking on certain URL buttons in inline keyboards.

-

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.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/web-events.html b/data/core.telegram.org/api/web-events.html deleted file mode 100644 index b82ec4ec1a..0000000000 --- a/data/core.telegram.org/api/web-events.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - Web events - - - - - - - - - - - - - -
- -
-
-
- -

Web events

- -
- -

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose APIs to allow receiving data and events from the websites.

-

Event APIs

-

Games and payment gateways can generate events that are meant to be received by the Telegram apps. -Typically events are generated by using the postEvent method of the GamingCommunication library. -The postEvent function will try sending the event to the Telegram app in a number of different ways.

-

WebviewProxy

-

In mobile apps, the event receiver API should be typically exposed as a window.TelegramWebviewProxy object with a postEvent method.

-
window.TelegramWebviewProxy.postEvent(eventType, eventData)
-

window.external

-

Alternatively, a window.external.notify method can be exposed, accepting a string JSON payload with the event type and payload:

-
window.external.notify(JSON.stringify({eventType: eventType, eventData: eventData}));
-

postMessage API

-

Finally, web MTProto clients that need to open a game or process a payment in an iframe can use the postMessage API to receive events from iframes. -The GamingCommunication library by defaultwill use '*' as targetOrigin, sending messages to parent pages regardless of the origin of the embedder.

-
window.parent.postMessage(JSON.stringify({eventType: eventType, eventData: eventData}), targetOrigin);
-

Event types

-

eventType is a simple string indicating the event type, and eventData is a payload with an object that will be parsed by the Telegram app.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
eventTypeeventDataDescription
payment_form_submitJSON object with data and title fieldstitle is the censored credit card title.
data is a service-specific JSON payload with information about the payment credentials provided by the user to the payment system.
Neither Telegram, nor bots will have access to your credit card information.
Credit card details will be handled only by the payment system.
share_scorenullWill be called by games when the user explicitly clicks on the share score button to share the game, along with his score.
Typically done by using messages.forwardMessages on the game message with the with_my_score flag.
share_gamenullWill be called by games when the user explicitly clicks on the share game button to share the game, without sharing his score.
Typically done by using messages.forwardMessages on the game message without the with_my_score flag, or by sharing the game's short URL.
game_overnullCan be called by games when the user loses a game
game_loadednullCan be called by games once the game fully loads
resize_frameJSON object with height fieldCalled by supported pages inside of IV iframe embeds, indicates the new size of the embed frame.
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/apple_privacy.html b/data/core.telegram.org/apple_privacy.html deleted file mode 100644 index 5467eec0f9..0000000000 --- a/data/core.telegram.org/apple_privacy.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - Page moved - - - - - - - - - - - - - -
- -
-
-
-
-

Page moved

- -

This is not the droid you're looking for.
The page has been moved.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots.html b/data/core.telegram.org/bots.html deleted file mode 100644 index b0da60094a..0000000000 --- a/data/core.telegram.org/bots.html +++ /dev/null @@ -1,434 +0,0 @@ - - - - - Bots: An introduction for developers - - - - - - - - - - - - - -
- -
-
-
-
-

Bots: An introduction for developers

- -
- -

Bots are third-party applications that run inside Telegram. Users can interact with bots by sending them messages, commands and inline requests. You control your bots using HTTPS requests to our Bot API.

-

1. What can I do with bots?

-
- -
- -

To name just a few things, you could use bots to:

-
    -
  • Get customized notifications and news. A bot can act as a smart newspaper, sending you relevant content as soon as it's published.

    -
  • -
  • Integrate with other services. A bot can enrich Telegram chats with content from external services.
    Gmail Bot, GIF bot, IMDB bot, Wiki bot, Music bot, Youtube bot, GitHubBot

    -
  • -
  • Accept payments from Telegram users. A bot can offer paid services or work as a virtual storefront. Read more »
    Demo Shop Bot, Demo Store

    -
  • -
  • Create custom tools. A bot may provide you with alerts, weather forecasts, translations, formatting or other services.
    Markdown bot, Sticker bot, Vote bot, Like bot

    -
  • -
  • Build single- and multiplayer games. A bot can offer rich HTML5 experiences, from simple arcades and puzzles to 3D-shooters and real-time strategy games.
    GameBot, Gamee

    -
  • -
  • Build social services. A bot could connect people looking for conversation partners based on common interests or proximity.

    -
  • -
  • Do virtually anything else. Except for dishes — bots are terrible at doing the dishes.

    -
  • -
-

2. How do bots work?

-

At the core, Telegram Bots are special accounts that do not require an additional phone number to set up. Users can interact with bots in two ways:

-
    -
  • Send messages and commands to bots by opening a chat with them or by adding them to groups.
  • -
  • Send requests directly from the input field by typing the bot's @username and a query. This allows sending content from inline bots directly into any chat, group or channel.
  • -
-

Messages, commands and requests sent by users are passed to the software running on your servers. Our intermediary server handles all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API. We call that interface our Bot API.

-
-

A detailed description of the Bot API is available on this page »

-
-

3. How do I create a bot?

-
- -
- -

There's a… bot for that. Just talk to BotFather (described below) and follow a few simple steps. Once you've created a bot and received your authorization 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 auth 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 authorization 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 authorization token

-

If your existing token is compromised or you lost it for some reason, use the /token command to generate a new one.

-

Botfather commands

-

The remaining commands are pretty self-explanatory:

-
    -
  • /mybots — returns a list of your bots with handy controls to edit their settings
  • -
  • /mygames — does the same for your games
  • -
-

Edit bots

-
    -
  • /setname – change your bot's name.
  • -
  • /setdescription — change the bot's description, a short text of up to 512 characters, describing your bot. Users will see this text at the beginning of the conversation with the bot, titled 'What can this bot do?'.
  • -
  • /setabouttext — change the bot's about info, an even shorter text of up to 120 characters. Users will see this text on the bot's profile page. When they share your bot with someone, this text is sent together with the link.
  • -
  • /setuserpic — change the bot's profile pictures. It's always nice to put a face to a name.
  • -
  • /setcommands — change the list of commands supported by your bot. Users will see these commands as suggestions when they type / in the chat with your bot. Each command has a name (must start with a slash ‘/’, alphanumeric plus underscores, no more than 32 characters, case-insensitive), parameters, and a text description. Users will see the list of commands whenever they type '/' in a conversation with your bot.
  • -
  • /deletebot — delete your bot and free its username.
  • -
-

Edit settings

-
    -
  • /setinline — toggle inline mode for your bot.
  • -
  • /setinlinegeo - request location data to provide location-based inline results.
  • -
  • /setjoingroups — toggle whether your bot can be added to groups or not. Any bot must be able to process private messages, but if your bot was not designed to work in groups, you can disable this.
  • -
  • /setprivacy — set which messages your bot will receive when added to a group. With privacy mode disabled, the bot will receive all messages. We recommend leaving privacy mode enabled. You will need to re-add the bot to existing groups for this change to take effect.
  • -
-

Manage games

-
    -
  • /newgame — create a new game.
  • -
  • /listgames — get a list of your games.
  • -
  • /editgame — edit a game.
  • -
  • /deletegame — delete an existing game.
  • -
-
-

Please note, that it may take a few minutes for changes to take effect.

-
-

Status alerts

-

Millions choose Telegram for its speed. To stay competitive in this environment, your bot also needs to be responsive. In order to help developers keep their bots in shape, Botfather will send status alerts if it sees something is wrong.

-

We will be checking the number of replies and the request/response conversion rate for popular bots (~300 requests per minute: but don't write this down as the value may change in the future). If we get abnormally low readings, you will receive a notification from Botfather.

-
Responding to alerts
-

By default, you will only get one alert per bot per hour. Each alert has the following buttons:

-
    -
  • Fixed. Use this if you found an issue with your bot and fixed it. If you press the fix button, we will resume sending alerts in the regular way so that you can see if your fix worked within 5-10 minutes instead of having to wait for an hour.
  • -
  • Support. Use this to open a chat with @BotSupport if you don't see any issues with your bot or if you think the problem is on our side.
  • -
  • Mute for 8h/1w. Use this if you can't fix your bot at the moment. This will disable all alerts for the bot in question for the specified period of time. We do not recommend using this option since your users may migrate to a more stable bot. You can unmute alerts in your bot's settings via Botfather.
  • -
-
Monitored issues
-

We will currently notify you about the following issues:

-

1.

-
Too few **private messages** are sent compared to previous weeks: **{value}**
-

Your bot is sending much fewer messages than it did in the previous weeks. This is useful for newsletter-style bots that send out messages without prompts from the users. The larger the value, the more significant the difference.

-

2.

-
Too few replies to incoming **private messages**. Conversion rate: **{value}**
-

Your bot is not replying to all messages that are being sent to it (the request/response conversion rate for your bot was too low for at least two of the last three 5-minute periods). To provide a good user experience, please respond to all messages that are sent to your bot. Respond to message updates by calling send… methods (e.g. sendMessage).

-

3.

-
Too few answers to **inline queries**. Conversion rate: **{value}**
-

Your bot is not replying to all inline queries that are being sent to it, calculated in the same way as above. Respond to inline_query updates by calling answerInlineQuery.

-

4.

-
Too few answers to **callback queries**. Conversion rate: **{value}**
-Too few answers to **callback game queries**. Conversion rate: **{value}**
-

Your bot is not replying to all callback queries that are being sent to it (with or without games), calculated in the same way as above. Respond to callback_query updates by calling answerCallbackQuery.

-
-

Please note that the status alerts feature is still being tested and will be improved in the future.

-
-
-

That's it for the introduction. You are now definitely ready to proceed to the BOT API MANUAL.

-

If you've got any questions, please check out our Bot FAQ »

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/2-0-intro.html b/data/core.telegram.org/bots/2-0-intro.html deleted file mode 100644 index eaf0513a80..0000000000 --- a/data/core.telegram.org/bots/2-0-intro.html +++ /dev/null @@ -1,230 +0,0 @@ - - - - - Introducing Bot API 2.0 - - - - - - - - - - - - - -
- -
-
-
-
-

Introducing Bot API 2.0

- -
- -
-

Howdy! This text assumes that you‘re familiar with Telegram’s bot platform.
If this is not the case, kindly check out our Introduction to Bots.

-
-

Today we‘re introducing the biggest change to Telegram’s Bot Platform since June 2015. These new tools will help you create fluid and intuitive interfaces for your bots. And bots are becoming a lot more capable. They can now send any type of content supported on Telegram, provide location-based services and integrate with other services deeply based on users' phone numbers.

-

If you'd like a more concise changelog, you can find one in the Bot API Manual.

-

New Inline Keyboards

-

To begin with, we're adding a new type of keyboard that is integrated directly into the message it belongs to. Inline keyboards are available for messages sent both in chat mode and inline mode.

-
- - - -

- - - -
- -

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

-
-

Manual: Inline keyboards »

-
-

Callback buttons

-

When a user presses a callback button, no messages are sent to the chat. Instead, your bot simply receives the relevant query. Upon receiving the query, your bot can display some result in a notification at the top of the chat screen or in an alert.

-
-

-
- -

Sample bot
@music – This sample music bot uses inline callback buttons to flip pages and reload random results.

-

Read on to updating messages to find out how callback buttons can get even cooler.

-

URL buttons

-

Buttons of this type have a small arrow icon to help the user understand that tapping on a URL button will open an external link. Naturally, we'll show them a confirmation alert before opening the link in the browser.

-
-
-
- -

Switch to Inline buttons

-

Pressing a switch to inline button prompts the user to select a chat, opens it and inserts the bot's username into the input field. You can also pass a query that will be inserted along with the username – this way your users will immediately get some inline results they can share.

-
-

-
- -

Sample bot
@sticker – This sticker search bot offers a ‘switch to inline’ button to teach users how to use it in inline mode.

-

Updating Messages

-

Since inline keyboards don‘t send additional messages to the chat, it made sense to give bots a way of manipulating their existing messages, so that they don’t have to send a new message each time they need to update something. This helps reduce clutter and build more fluid interfaces.

-
-
- -
-
- -

Sample bot
@music – Watch how the music bot updates its messages with search results when you press the navigation buttons.

-
-

Manual: Updating messages »

-
-

Locations and Numbers

-

Some bots need extra data from the user to work properly. For example, knowing the user‘s location helps provide more relevant geo-specific results. The user’s phone number can be very useful for integrations with other services, like banks, etc.

-

We've added an easy way for bots to ask the user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

-
-

-
- -

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

-
-

Manual: Number and location buttons »

-
-

Inline bots can also request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

-

Sample bot
@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

-

Inline Bots 2.0

-

Speaking of inline bots, they are also getting a major upgrade today.

-

New types of content

-

Inline bots now support all types of content available in Telegram (19 in all), they are now capable of sending stickers, videos, music, locations, documents and more.

-
-

-
- -

Sample bots
@sticker – This sticker bot will accept one or more emoji and search for relevant stickers.
@music – The music bot allows users to send mp3 tracks from a database of public domain classical music.

-
-

Manual: Types of inline content »

-
-

Switching between inline mode and private chat

-

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

-
-

-
- -

You can now display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

-

Sample bots
@youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.

-
-

Manual: Switch to PM

-
-

Better inline UI

-

Since sending content via inline bots works differently from sending ordinary messages, we‘ve changed the interface a little. There’s hardly a more effective way of explaining that there‘s no need to hit ’Send':

-
-

-
- -

Tapping on the cross icon once will clear the query, tapping twice will give the ‘Send’ button back to the user.

-

Group Admins

-

As a dessert, we‘re beginning to roll out tools that will allow you to create bot solutions for group admins. As the first step, we’ve added methods to remove members from groups and supergroups.

-
-

Manual: Group management »

-
-

And that's about it for now. Stay tuned for more updates and subscribe to our official @Botnews channel on Telegram.

-
-

Read the full changelog for this update »

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/api-changelog.html b/data/core.telegram.org/bots/api-changelog.html deleted file mode 100644 index 15191ee4c4..0000000000 --- a/data/core.telegram.org/bots/api-changelog.html +++ /dev/null @@ -1,626 +0,0 @@ - - - - - Bot API changelog - - - - - - - - - - - - - -
- -
-
-
-
-

Bot API changelog

- -
- -
-

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots »

-
-

You will find all changes to our Bot API on this page.

-

Recent changes

-
-

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

-
-

June 25, 2021

-

Bot API 5.3

-

Personalized Commands

-
    -
  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • -
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • -
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • -
  • Added the parameters scope and language_code to the method getMyCommands.
  • -
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • -
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
  • -
-

Custom Placeholders

- -

And More

-
    -
  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • -
  • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
  • -
  • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
  • -
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
  • -
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

April 26, 2021

-

Bot API 5.2

-
    -
  • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
  • -
  • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
  • -
  • Allowed sending invoices to group, supergroup and channel chats.
  • -
  • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
  • -
  • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
  • -
  • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
  • -
  • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
  • -
  • Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
  • -
-
-
-

⚠️ WARNING! ⚠️
After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

-
-
-
-

⚠️ WARNING! ⚠️
Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.

-
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

March 9, 2021

-

Bot API 5.1

-

Added two new update types

-
    -
  • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
  • -
-

Improved Invite Links

-
    -
  • Added the class ChatInviteLink, representing an invite link to a chat.
  • -
  • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
  • -
  • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
  • -
  • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
  • -
-

Voice Chat Info

- -

And More

-
    -
  • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
  • -
  • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
  • -
  • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
  • -
  • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

November 4, 2020

-

Introducing Bot API 5.0

-

Run Your Own Bot API Server

-
    -
  • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance.
  • -
  • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
  • -
  • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
  • -
-

Transfer Bot Ownership

-
    -
  • You can now use @BotFather to transfer your existing bots to another Telegram account.
  • -
-

Webhooks

-
    -
  • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
  • -
  • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
  • -
  • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
  • -
-

Working with Groups

-
    -
  • The getChat request now returns the user's bio for private chats if available.
  • -
  • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
  • -
  • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
  • -
  • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
  • -
-

Working with Files

-
    -
  • Added the field file_name to the classes Audio and Video, containing the name of the original file.
  • -
  • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
  • -
-

Multiple Pinned Messages

-
    -
  • Added the ability to pin messages in private chats.
  • -
  • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
  • -
  • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
  • -
-

File Albums

-
    -
  • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
  • -
-

Live Locations

- -

Anonymous Admins

-
    -
  • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
  • -
  • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
  • -
  • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
  • -
  • Added the custom title of an anonymous message sender to the class Message as author_signature.
  • -
-

And More

- -

And Last but not Least

-
    -
  • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-

June 4, 2020

-

Bot API 4.9

-
    -
  • Added the new field via_bot to the Message object. You can now know which bot was used to send a message.
  • -
  • Supported video thumbnails for inline GIF and MPEG4 animations.
  • -
  • Supported the new basketball animation for the random dice. Choose between different animations (dice, darts, basketball) by specifying the emoji parameter in the method sendDice.
  • -
-

April 24, 2020

-

Bot API 4.8

-
    -
  • Supported explanations for Quizzes 2.0. Add explanations by specifying the parameters explanation and explanation_parse_mode in the method sendPoll.
  • -
  • Added the fields explanation and explanation_entities to the Poll object.
  • -
  • Supported timed polls that automatically close at a certain date and time. Set up by specifying the parameter open_period or close_date in the method sendPoll.
  • -
  • Added the fields open_period and close_date to the Poll object.
  • -
  • Supported the new darts animation for the dice mini-game. Choose between the default dice animation and darts animation by specifying the parameter emoji in the method sendDice.
  • -
  • Added the field emoji to the Dice object.
  • -
-

March 30, 2020

-

Bot API 4.7

-
    -
  • Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the “proper” singular of die. But it's awkward, and we decided to help it change. One dice at a time!)
  • -
  • Added the field dice to the Message object.
  • -
  • Added the method getMyCommands for getting the current list of the bot's commands.
  • -
  • Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather.
  • -
  • Added the ability to create animated sticker sets by specifying the parameter tgs_sticker instead of png_sticker in the method createNewStickerSet.
  • -
  • Added the ability to add animated stickers to sets created by the bot by specifying the parameter tgs_sticker instead of png_sticker in the method addStickerToSet.
  • -
  • Added the field thumb to the StickerSet object.
  • -
  • Added the ability to change thumbnails of sticker sets created by the bot using the method setStickerSetThumb.
  • -
-

January 23, 2020

-

Bot API 4.6

-
    -
  • Supported Polls 2.0.
  • -
  • Added the ability to send non-anonymous, multiple answer, and quiz-style polls: added the parameters is_anonymous, type, allows_multiple_answers, correct_option_id, is_closed options to the method sendPoll.
  • -
  • Added the object KeyboardButtonPollType and the field request_poll to the object KeyboardButton.
  • -
  • Added updates about changes of user answers in non-anonymous polls, represented by the object PollAnswer and the field poll_answer in the Update object.
  • -
  • Added the fields total_voter_count, is_anonymous, type, allows_multiple_answers, correct_option_id to the Poll object.
  • -
  • Bots can now send polls to private chats.
  • -
  • Added more information about the bot in response to the getMe request: added the fields can_join_groups, can_read_all_group_messages and supports_inline_queries to the User object.
  • -
  • Added the optional field language to the MessageEntity object.
  • -
-

December 31, 2019

-

Bot API 4.5

-
    -
  • Added support for two new MessageEntity types, underline and strikethrough.
  • -
  • Added support for nested MessageEntity objects. Entities can now contain other entities. If two entities have common characters then one of them is fully contained inside the other.
  • -
  • Added support for nested entities and the new tags <u>/<ins> (for underlined text) and <s>/<strike>/<del> (for strikethrough text) in parse mode HTML.
  • -
  • Added a new parse mode, MarkdownV2, which supports nested entities and two new entities __ (for underlined text) and ~ (for strikethrough text). Parse mode Markdown remains unchanged for backward compatibility.
  • -
  • Added the field file_unique_id to the objects Animation, Audio, Document, PassportFile, PhotoSize, Sticker, Video, VideoNote, Voice, File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto. The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
  • -
  • Added the field custom_title to the ChatMember object.
  • -
  • Added the new method setChatAdministratorCustomTitle to manage the custom titles of administrators promoted by the bot.
  • -
  • Added the field slow_mode_delay to the Chat object.
  • -
-

July 29, 2019

-

Bot API 4.4

-
    -
  • Added support for animated stickers. New field is_animated in Sticker and StickerSet objects, animated stickers can now be used in sendSticker and InlineQueryResultCachedSticker.
  • -
  • Added support for default permissions in groups. New object ChatPermissions, containing actions which a member can take in a chat. New field permissions in the Chat object; new method setChatPermissions.
  • -
  • The field all_members_are_administrators has been removed from the documentation for the Chat object. The field is still returned in the object for backward compatibility, but new bots should use the permissions field instead.
  • -
  • Added support for more permissions for group and supergroup members: added the new field can_send_polls to ChatMember object, added can_change_info, can_invite_users, can_pin_messages in ChatMember object for restricted users (previously available only for administrators).
  • -
  • The method restrictChatMember now takes the new user permissions in a single argument of the type ChatPermissions. The old way of passing parameters will keep working for a while for backward compatibility.
  • -
  • Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method.
  • -
  • Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
  • -
  • File identifiers from the ChatPhoto object are now invalidated and can no longer be used whenever the photo is changed.
  • -
  • All webhook requests from the Bot API are now coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
  • As of the next Bot API update (version 4.5), nested MessageEntity objects will be allowed in message texts and captions. Please make sure that your code can correctly handle such entities.
  • -
-

May 31, 2019

-

Bot API 4.3

-
    -
  • Added support for Seamless Telegram Login on external websites.
  • -
  • Added the new object LoginUrl and the new field login_url to the InlineKeyboardButton object which allows to automatically authorize users before they go to a URL specified by the bot. Users will be asked to confirm authorization in their Telegram app (needs version 5.7 or higher) when they press the button:
  • -
-
- TITLE -
- -

Also in this update:

-
    -
  • Added the field reply_markup to the Message object, containing the inline keyboard attached to the message.
  • -
  • If a message with an inline keyboard is forwarded, the forwarded message will now have an inline keyboard if the keyboard contained only url and login_url buttons or if the message was sent via a bot and the keyboard contained only url, login_url, switch_inline_query or switch_inline_query_current_chat buttons. In the latter case, switch_inline_query_current_chat buttons are replaced with switch_inline_query buttons.
  • -
  • Bots now receive the edited_message Update even if only Message.reply_markup has changed.
  • -
  • Bots that have the can_edit_messages right in a channel can now use the method editMessageReplyMarkup for messages written by other administrators forever without the 48 hours limit.
  • -
  • Don't forget that starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
-

April 14, 2019

-

Bot API 4.2

-
    -
  • Added support for native polls: added the object Poll, the methods sendPoll and stopPoll and the field poll in the Message and Update objects.
  • -
  • The method deleteMessage can now be used to delete messages sent by a user to the bot in private chats within 48 hours.
  • -
  • Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage, and receive the pinned group message in Chat object.
  • -
  • Added the field is_member to the ChatMember object, which can be used to find whether a restricted user is a member of the chat.
  • -
  • Added the field forward_sender_name to the Message object, containing name of the sender who has opted to hide their account.
  • -
  • Starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
  • Document thumbnails now should be inscribed in a 320x320 square instead of 90x90.
  • -
-

August 27, 2018

-

Bot API 4.1

- -

July 26, 2018

-

Bot API 4.0.

-
    -
  • Added support for Telegram Passport. See the official announcement on the blog and the manual for details.
  • -
  • Added support for editing the media content of messages: added the method editMessageMedia and new types InputMediaAnimation, InputMediaAudio, and InputMediaDocument.
  • -
  • Added the field thumb to the Audio object to contain the thumbnail of the album cover to which the music file belongs.
  • -
  • Added support for attaching custom thumbnails to uploaded files. For animations, audios, videos and video notes, which are less than 10 MB in size, thumbnails are generated automatically.
  • -
  • tg:// URLs now can be used in inline keyboard url buttons and text_link message entities.
  • -
  • Added the method sendAnimation, which can be used instead of sendDocument to send animations, specifying their duration, width and height.
  • -
  • Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set.
  • -
  • Added two new MessageEntity types: cashtag and phone_number.
  • -
  • Added support for Foursquare venues: added the new field foursquare_type to the objects Venue, InlineQueryResultVenue and InputVenueMessageContent, and the parameter foursquare_type to the sendVenue method.
  • -
  • You can now create inline mentions of users, who have pressed your bot's callback buttons.
  • -
  • You can now use the Retry-After response header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook.
  • -
  • If a webhook returns the HTTP error 410 Gone for all requests for more than 23 hours successively, it can be automatically removed.
  • -
  • Added vCard support when sharing contacts: added the field vcard to the objects Contact, InlineQueryResultContact, InputContactMessageContent and the method sendContact.
  • -
-

February 13, 2018

-

Bot API 3.6.

-
    -
  • Supported text formatting in media captions. Specify the desired parse_mode (Markdown or HTML) when you provide a caption.
  • -
  • In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot).
  • -
  • Added the new field connected_website to Message. The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
  • -
  • Added the new parameter supports_streaming to the sendVideo method and a field with the same name to the InputMediaVideo object.
  • -
-

November 17, 2017

-

Bot API 3.5.

- -

October 11, 2017

-

Bot API 3.4.

- -

August 23, 2017

-

Bot API 3.3.

-
    -
  • Bots can now mention users via inline mentions, without using usernames.
  • -
  • getChat now also returns pinned messages in supergroups, if present. Added the new field pinned_message to the Chat object.
  • -
  • Added the new fields author_signature and forward_signature to the Message object.
  • -
  • Added the new field is_bot to the User object.
  • -
-

July 21, 2017

-

Bot API 3.2. Teach your bot to handle stickers and sticker sets.

- -

June 30, 2017

-

Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:

- -

May 18, 2017

-

Introducing Bot API 3.0.

-

NEW Payment Platform

-

See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.

- -

NEW Video Messages

-
    -
  • As of Telegram v.4.0, users can send short rounded video messages, using an interface similar to that of voice notes.
  • -
  • Added the sendVideoNote method, the new field video_note to Message, the fields record_video_note or upload_video_note to sendChatAction.
  • -
-

NEW Multilingual Bots

-
    -
  • The User object now may have a language_code field that contains the IETF language tag of the user's language.
  • -
  • Thanks to this, your bot can now offer localized responses to users that speak different languages.
  • -
-

More power to admin bots

-
    -
  • unbanChatMemeber now also works in channels!
  • -
  • New method deleteMessage that allows the bot to delete its own messages, as well as messages posted by other in groups and channels where the bot is an administrator.
  • -
-

Minor Changes

-
    -
  • Replaced the field new_chat_member in Message with new_chat_members (the old field will still be available for a while for compatibility purposes).
  • -
  • Inline keyboards with switch_inline_query and switch_inline_query_current_chat can no longer be sent to channels because they are useless there.
  • -
  • New fields gif_duration in InlineQueryResultGif and mpeg4_duration in InlineQueryResultMpeg4Gif.
  • -
-

December 4, 2016

-

Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.

-
    -
  • Use the new field max_connections in setWebhook to optimize your bot's server load
  • -
  • Use allowed_updates in setWebhook and getUpdates to selectively subscribe to updates of a certain type. Among other things, this allows you to stop getting updates about new posts in channels where your bot is an admin.
  • -
  • deleteWebhook moved out of setWebhook to get a whole separate method for itself.
  • -
-

November 21, 2016

-

Bot API 2.3

-
    -
  • Modified bot privacy mode for the sake of consistency.
  • -
  • Your bot can now get updates about posts in channels. Added new fields channel_post and edited_channel_post to Update.

    -
  • -
  • You can now update high scores to a lower value by using the new force parameter in setGameScore. Handy for punishing cheaters or fixing errors in your game's High Score table.

    -
  • -
  • Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
  • -
  • The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
  • -
  • Added the new field forward_from_message_id to Message.
  • -
  • Added the new parameter cache_time to answerCallbackQuery. Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
  • -
  • Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
  • -
-

October 3, 2016

-

Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.

- -

Other changes

- -
    -
  • New field all_members_are_administrators in the Chat object.
  • -
  • Certain server responses may now contain the new parameters field with expanded info on errors that occurred while processing your requests.
  • -
-

May 25, 2016

- -

May 22, 2016

- -

May 12, 2016

- -

May 6, 2016

-
    -
  • Added the field emoji to the Sticker object. Your bot can now know the emoji a sticker corresponds to.
  • -
  • Added the field forward_from_chat to the Message object for messages forwarded from channels.
  • -
-

April 9, 2016

-

Introducing Bot API 2.0. Check out this page for a review of this major update.

- -

Inline bots

-
    -
  • Added support for all content types available on Telegram. 19 types of InlineQueryResult objects are now supported.
  • -
  • Inline bots can now substitute all kinds of content with text. Added 4 types of InputMessageContent objects.
  • -
  • Your inline bot can also ask users for permission to use their location. Added the new Botfather command /setinlinegeo, added field location to the InlineQuery object, added fields location and inline_message_id to the ChosenInlineResult object.
  • -
  • Added an easy way to switch between inline mode and a private chat with the bot – useful for settings, establishing external connections and teaching users how to use your bot in inline mode. Added parameters switch_pm_text and switch_pm_parameter to the method answerInlineQuery.
  • -
-

Miscellaneous

- -

February 20, 2016

-
    -
  • Added the disable_notification parameter to all methods that send messages or any kind.
  • -
  • Removed backward compatibility from the method sendAudio. Voice messages now must be sent using the method sendVoice. There is no more need to specify a non-empty title or performer while sending the audio by file_id.
  • -
-

January 20, 2016

-
    -
  • By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
  • -
-

January 14, 2016

-
    -
  • You can now collect feedback on which results provided by your inline bot get chosen by the users. Added the setinlinefeedback command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object.
  • -
-

January 4, 2016

- -

November, 2015

-
    -
  • Added support for supergroups. The Type field in the Chat object can now contain 'supergroup'.
  • -
  • New optional fields added to the Message object: supergroup_chat_created, migrate_to_chat_id, migrate_from_chat_id and channel_chat_created.
  • -
-

October 8, 2015

-
    -
  • Added initial channel support for bots (no Telegram clients support this at the moment, please wait for updates):
  • -
  • The Chat field in the Message is now of the new type Chat.
  • -
  • You can now pass a channel username (in the format @channelusername) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).
  • -
-

September 18, 2015

-
    -
  • Bots can now download files and media sent by users.
  • -
  • Added getFile and File.
  • -
-

September 7, 2015

-
    -
  • You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
  • -
  • Added very basic markdown support. New field parse_mode added to sendMessage. For the moment messages with markdown will be displayed correctly only in Telegram for Android. Other official apps will catch up soon.
  • -
-

August 29, 2015

-
    -
  • Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.
  • -
  • You can now make new requests when responding to webhook updates.
  • -
-

August 15, 2015

-
    -
  • Added new type Voice and new method sendVoice for sending voice messages.
  • -
  • Earlier Audio and sendAudio should now be used for sending music files. Telegram clients will show such files in the in-app music player. If you were using sendAudio for your bot to send voice messages, please use sendVoice instead.
  • -
  • Added optional fields performer, title to the Audio object and sendAudio method.
  • -
  • Added optional field voice to the Message object.
  • -
-

July 2015

-
    -
  • The thumb field is now optional for Video, Sticker and Document objects
  • -
  • The API now supports both video and photo captions. The caption field has been removed from the Video object and added to the Message object instead.
  • -
  • caption and duration optional fields have been added to the sendVideo method.
  • -
  • Fixed typo: user_id in the Contact object is now correctly labeled as Integer, not String
  • -
-

June 24, 2015

-

The bot platform was officially launched.

-
-

Back to the Bot API Manual »

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/api.html b/data/core.telegram.org/bots/api.html deleted file mode 100644 index 57bb9d007b..0000000000 --- a/data/core.telegram.org/bots/api.html +++ /dev/null @@ -1,9256 +0,0 @@ - - - - - Telegram Bot API - - - - - - - - - - - - - -
- -
-
-
- -

Telegram Bot API

- -
- -
-

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots and Bot FAQ.

-
-

Recent changes

-
-

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

-
-

June 25, 2021

-

Bot API 5.3

-

Personalized Commands

-
    -
  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • -
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • -
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • -
  • Added the parameters scope and language_code to the method getMyCommands.
  • -
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • -
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
  • -
-

Custom Placeholders

- -

And More

-
    -
  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • -
  • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
  • -
  • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
  • -
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
  • -
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

April 26, 2021

-

Bot API 5.2

-
    -
  • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
  • -
  • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
  • -
  • Allowed sending invoices to group, supergroup and channel chats.
  • -
  • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
  • -
  • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
  • -
  • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
  • -
  • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
  • -
  • Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
  • -
-
-
-

⚠️ WARNING! ⚠️
After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

-
-
-
-

⚠️ WARNING! ⚠️
Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.

-
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

March 9, 2021

-

Bot API 5.1

-

Added two new update types

-
    -
  • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
  • -
-

Improved Invite Links

-
    -
  • Added the class ChatInviteLink, representing an invite link to a chat.
  • -
  • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
  • -
  • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
  • -
  • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
  • -
-

Voice Chat Info

- -

And More

-
    -
  • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
  • -
  • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
  • -
  • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
  • -
  • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

November 4, 2020

-

Introducing Bot API 5.0

-

Run Your Own Bot API Server

-
    -
  • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance (check this out to see if this will benefit your project).
  • -
  • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
  • -
  • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
  • -
-

Transfer Bot Ownership

-
    -
  • You can now use @BotFather to transfer your existing bots to another Telegram account.
  • -
-

Webhooks

-
    -
  • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
  • -
  • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
  • -
  • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
  • -
-

Working with Groups

-
    -
  • The getChat request now returns the user's bio for private chats if available.
  • -
  • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
  • -
  • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
  • -
  • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
  • -
-

Working with Files

-
    -
  • Added the field file_name to the classes Audio and Video, containing the name of the original file.
  • -
  • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
  • -
-

Multiple Pinned Messages

-
    -
  • Added the ability to pin messages in private chats.
  • -
  • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
  • -
  • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
  • -
-

File Albums

-
    -
  • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
  • -
-

Live Locations

- -

Anonymous Admins

-
    -
  • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
  • -
  • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
  • -
  • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
  • -
  • Added the custom title of an anonymous message sender to the class Message as author_signature.
  • -
-

And More

- -

And Last but bot Least

-
    -
  • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-

See earlier changes »

-

Authorizing your bot

-

Each bot is given a unique authentication token when it is created. The token looks something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11, but we'll use simply <token> in this document instead. You can learn about obtaining tokens and generating new ones in this document.

-

Making requests

-

All queries to the Telegram Bot API must be served over HTTPS and need to be presented in this form: https://api.telegram.org/bot<token>/METHOD_NAME. Like this for example:

-
https://api.telegram.org/bot123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11/getMe
-

We support GET and POST HTTP methods. We support four ways of passing parameters in Bot API requests:

-
    -
  • URL query string
  • -
  • application/x-www-form-urlencoded
  • -
  • application/json (except for uploading files)
  • -
  • multipart/form-data (use to upload files)
  • -
-

The response contains a JSON object, which always has a Boolean field 'ok' and may have an optional String field 'description' with a human-readable description of the result. If 'ok' equals true, the request was successful and the result of the query can be found in the 'result' field. In case of an unsuccessful request, 'ok' equals false and the error is explained in the 'description'. An Integer 'error_code' field is also returned, but its contents are subject to change in the future. Some errors may also have an optional field 'parameters' of the type ResponseParameters, which can help to automatically handle the error.

-
    -
  • All methods in the Bot API are case-insensitive.
  • -
  • All queries must be made using UTF-8.
  • -
-

Making requests when getting updates

-

If you're using webhooks, you can perform a request to the Bot API while sending an answer to the webhook. Use either application/json or application/x-www-form-urlencoded or multipart/form-data response content type for passing parameters. Specify the method to be invoked in the method parameter of the request. It's not possible to know that such a request was successful or get its result.

-
-

Please see our FAQ for examples.

-
-

Using a Local Bot API Server

-

The Bot API server source code is available at telegram-bot-api. You can run it locally and send the requests to your own server instead of https://api.telegram.org. If you switch to a local Bot API server, your bot will be able to:

-
    -
  • Download files without a size limit.
  • -
  • Upload files up to 2000 MB.
  • -
  • Upload files using their local path and the file URI scheme.
  • -
  • Use an HTTP URL for the webhook.
  • -
  • Use any local IP address for the webhook.
  • -
  • Use any port for the webhook.
  • -
  • Set max_webhook_connections up to 100000.
  • -
  • Receive the absolute local path as a value of the file_path field without the need to download the file after a getFile request.
  • -
-

Do I need a Local Bot API Server

-

The majority of bots will be OK with the default configuration, running on our servers. But if you feel that you need one of these features, you're welcome to switch to your own at any time.

-

Getting updates

-

There are two mutually exclusive ways of receiving updates for your bot — the getUpdates method on one hand and Webhooks on the other. Incoming updates are stored on the server until the bot receives them either way, but they will not be kept longer than 24 hours.

-

Regardless of which option you choose, you will receive JSON-serialized Update objects as a result.

-

Update

-

This object represents an incoming update.
At most one of the optional parameters can be present in any given update.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
update_idIntegerThe update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using Webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.
messageMessageOptional. New incoming message of any kind — text, photo, sticker, etc.
edited_messageMessageOptional. New version of a message that is known to the bot and was edited
channel_postMessageOptional. New incoming channel post of any kind — text, photo, sticker, etc.
edited_channel_postMessageOptional. New version of a channel post that is known to the bot and was edited
inline_queryInlineQueryOptional. New incoming inline query
chosen_inline_resultChosenInlineResultOptional. The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
callback_queryCallbackQueryOptional. New incoming callback query
shipping_queryShippingQueryOptional. New incoming shipping query. Only for invoices with flexible price
pre_checkout_queryPreCheckoutQueryOptional. New incoming pre-checkout query. Contains full information about checkout
pollPollOptional. New poll state. Bots receive only updates about stopped polls and polls, which are sent by the bot
poll_answerPollAnswerOptional. A user changed their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.
my_chat_memberChatMemberUpdatedOptional. The bot's chat member status was updated in a chat. For private chats, this update is received only when the bot is blocked or unblocked by the user.
chat_memberChatMemberUpdatedOptional. A chat member's status was updated in a chat. The bot must be an administrator in the chat and must explicitly specify “chat_member” in the list of allowed_updates to receive these updates.
-

getUpdates

-

Use this method to receive incoming updates using long polling (wiki). An Array of Update objects is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
offsetIntegerOptionalIdentifier of the first update to be returned. Must be greater by one than the highest among the identifiers of previously received updates. By default, updates starting with the earliest unconfirmed update are returned. An update is considered confirmed as soon as getUpdates is called with an offset higher than its update_id. The negative offset can be specified to retrieve updates starting from -offset update from the end of the updates queue. All previous updates will forgotten.
limitIntegerOptionalLimits the number of updates to be retrieved. Values between 1-100 are accepted. Defaults to 100.
timeoutIntegerOptionalTimeout in seconds for long polling. Defaults to 0, i.e. usual short polling. Should be positive, short polling should be used for testing purposes only.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify [“message”, “edited_channel_post”, “callback_query”] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.

Please note that this parameter doesn't affect updates created before the call to the getUpdates, so unwanted updates may be received for a short period of time.
-
-

Notes
1. This method will not work if an outgoing webhook is set up.
2. In order to avoid getting duplicate updates, recalculate offset after each server response.

-
-

setWebhook

-

Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized Update. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns True on success.

-

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. https://www.example.com/<token>. Since nobody else knows your bot's token, you can be pretty sure it's us.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
urlStringYesHTTPS url to send updates to. Use an empty string to remove webhook integration
certificateInputFileOptionalUpload your public key certificate so that the root certificate in use can be checked. See our self-signed guide for details.
ip_addressStringOptionalThe fixed IP address which will be used to send webhook requests instead of the IP address resolved through DNS
max_connectionsIntegerOptionalMaximum allowed number of simultaneous HTTPS connections to the webhook for update delivery, 1-100. Defaults to 40. Use lower values to limit the load on your bot's server, and higher values to increase your bot's throughput.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify [“message”, “edited_channel_post”, “callback_query”] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.
Please note that this parameter doesn't affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time.
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
-
-

Notes
1. You will not be able to receive updates using getUpdates for as long as an outgoing webhook is set up.
2. To use a self-signed certificate, you need to upload your public key certificate using certificate parameter. Please upload as InputFile, sending a String will not work.
3. Ports currently supported for Webhooks: 443, 80, 88, 8443.

-

NEW! If you're having any trouble setting up webhooks, please check out this amazing guide to Webhooks.

-
-

deleteWebhook

-

Use this method to remove webhook integration if you decide to switch back to getUpdates. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
-

getWebhookInfo

-

Use this method to get current webhook status. Requires no parameters. On success, returns a WebhookInfo object. If the bot is using getUpdates, will return an object with the url field empty.

-

WebhookInfo

-

Contains information about the current status of a webhook.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
urlStringWebhook URL, may be empty if webhook is not set up
has_custom_certificateBooleanTrue, if a custom certificate was provided for webhook certificate checks
pending_update_countIntegerNumber of updates awaiting delivery
ip_addressStringOptional. Currently used webhook IP address
last_error_dateIntegerOptional. Unix time for the most recent error that happened when trying to deliver an update via webhook
last_error_messageStringOptional. Error message in human-readable format for the most recent error that happened when trying to deliver an update via webhook
max_connectionsIntegerOptional. Maximum allowed number of simultaneous HTTPS connections to the webhook for update delivery
allowed_updatesArray of StringOptional. A list of update types the bot is subscribed to. Defaults to all update types except chat_member
-

Available types

-

All types used in the Bot API responses are represented as JSON-objects.

-

It is safe to use 32-bit signed integers for storing all Integer fields unless otherwise noted.

-
-

Optional fields may be not returned when irrelevant.

-
-

User

-

This object represents a Telegram user or bot.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idIntegerUnique identifier for this user or bot. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
is_botBooleanTrue, if this user is a bot
first_nameStringUser's or bot's first name
last_nameStringOptional. User's or bot's last name
usernameStringOptional. User's or bot's username
language_codeStringOptional. IETF language tag of the user's language
can_join_groupsBooleanOptional. True, if the bot can be invited to groups. Returned only in getMe.
can_read_all_group_messagesBooleanOptional. True, if privacy mode is disabled for the bot. Returned only in getMe.
supports_inline_queriesBooleanOptional. True, if the bot supports inline queries. Returned only in getMe.
-

Chat

-

This object represents a chat.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idIntegerUnique identifier for this chat. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
typeStringType of chat, can be either “private”, “group”, “supergroup” or “channel”
titleStringOptional. Title, for supergroups, channels and group chats
usernameStringOptional. Username, for private chats, supergroups and channels if available
first_nameStringOptional. First name of the other party in a private chat
last_nameStringOptional. Last name of the other party in a private chat
photoChatPhotoOptional. Chat photo. Returned only in getChat.
bioStringOptional. Bio of the other party in a private chat. Returned only in getChat.
descriptionStringOptional. Description, for groups, supergroups and channel chats. Returned only in getChat.
invite_linkStringOptional. Primary invite link, for groups, supergroups and channel chats. Returned only in getChat.
pinned_messageMessageOptional. The most recent pinned message (by sending date). Returned only in getChat.
permissionsChatPermissionsOptional. Default chat member permissions, for groups and supergroups. Returned only in getChat.
slow_mode_delayIntegerOptional. For supergroups, the minimum allowed delay between consecutive messages sent by each unpriviledged user. Returned only in getChat.
message_auto_delete_timeIntegerOptional. The time after which all messages sent to the chat will be automatically deleted; in seconds. Returned only in getChat.
sticker_set_nameStringOptional. For supergroups, name of group sticker set. Returned only in getChat.
can_set_sticker_setBooleanOptional. True, if the bot can change the group sticker set. Returned only in getChat.
linked_chat_idIntegerOptional. Unique identifier for the linked chat, i.e. the discussion group identifier for a channel and vice versa; for supergroups and channel chats. This identifier may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier. Returned only in getChat.
locationChatLocationOptional. For supergroups, the location to which the supergroup is connected. Returned only in getChat.
-

Message

-

This object represents a message.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
message_idIntegerUnique message identifier inside this chat
fromUserOptional. Sender, empty for messages sent to channels
sender_chatChatOptional. Sender of the message, sent on behalf of a chat. The channel itself for channel messages. The supergroup itself for messages from anonymous group administrators. The linked channel for messages automatically forwarded to the discussion group
dateIntegerDate the message was sent in Unix time
chatChatConversation the message belongs to
forward_fromUserOptional. For forwarded messages, sender of the original message
forward_from_chatChatOptional. For messages forwarded from channels or from anonymous administrators, information about the original sender chat
forward_from_message_idIntegerOptional. For messages forwarded from channels, identifier of the original message in the channel
forward_signatureStringOptional. For messages forwarded from channels, signature of the post author if present
forward_sender_nameStringOptional. Sender's name for messages forwarded from users who disallow adding a link to their account in forwarded messages
forward_dateIntegerOptional. For forwarded messages, date the original message was sent in Unix time
reply_to_messageMessageOptional. For replies, the original message. Note that the Message object in this field will not contain further reply_to_message fields even if it itself is a reply.
via_botUserOptional. Bot through which the message was sent
edit_dateIntegerOptional. Date the message was last edited in Unix time
media_group_idStringOptional. The unique identifier of a media message group this message belongs to
author_signatureStringOptional. Signature of the post author for messages in channels, or the custom title of an anonymous group administrator
textStringOptional. For text messages, the actual UTF-8 text of the message, 0-4096 characters
entitiesArray of MessageEntityOptional. For text messages, special entities like usernames, URLs, bot commands, etc. that appear in the text
animationAnimationOptional. Message is an animation, information about the animation. For backward compatibility, when this field is set, the document field will also be set
audioAudioOptional. Message is an audio file, information about the file
documentDocumentOptional. Message is a general file, information about the file
photoArray of PhotoSizeOptional. Message is a photo, available sizes of the photo
stickerStickerOptional. Message is a sticker, information about the sticker
videoVideoOptional. Message is a video, information about the video
video_noteVideoNoteOptional. Message is a video note, information about the video message
voiceVoiceOptional. Message is a voice message, information about the file
captionStringOptional. Caption for the animation, audio, document, photo, video or voice, 0-1024 characters
caption_entitiesArray of MessageEntityOptional. For messages with a caption, special entities like usernames, URLs, bot commands, etc. that appear in the caption
contactContactOptional. Message is a shared contact, information about the contact
diceDiceOptional. Message is a dice with random value
gameGameOptional. Message is a game, information about the game. More about games »
pollPollOptional. Message is a native poll, information about the poll
venueVenueOptional. Message is a venue, information about the venue. For backward compatibility, when this field is set, the location field will also be set
locationLocationOptional. Message is a shared location, information about the location
new_chat_membersArray of UserOptional. New members that were added to the group or supergroup and information about them (the bot itself may be one of these members)
left_chat_memberUserOptional. A member was removed from the group, information about them (this member may be the bot itself)
new_chat_titleStringOptional. A chat title was changed to this value
new_chat_photoArray of PhotoSizeOptional. A chat photo was change to this value
delete_chat_photoTrueOptional. Service message: the chat photo was deleted
group_chat_createdTrueOptional. Service message: the group has been created
supergroup_chat_createdTrueOptional. Service message: the supergroup has been created. This field can't be received in a message coming through updates, because bot can't be a member of a supergroup when it is created. It can only be found in reply_to_message if someone replies to a very first message in a directly created supergroup.
channel_chat_createdTrueOptional. Service message: the channel has been created. This field can't be received in a message coming through updates, because bot can't be a member of a channel when it is created. It can only be found in reply_to_message if someone replies to a very first message in a channel.
message_auto_delete_timer_changedMessageAutoDeleteTimerChangedOptional. Service message: auto-delete timer settings changed in the chat
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
migrate_from_chat_idIntegerOptional. The supergroup has been migrated from a group with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
pinned_messageMessageOptional. Specified message was pinned. Note that the Message object in this field will not contain further reply_to_message fields even if it is itself a reply.
invoiceInvoiceOptional. Message is an invoice for a payment, information about the invoice. More about payments »
successful_paymentSuccessfulPaymentOptional. Message is a service message about a successful payment, information about the payment. More about payments »
connected_websiteStringOptional. The domain name of the website on which the user has logged in. More about Telegram Login »
passport_dataPassportDataOptional. Telegram Passport data
proximity_alert_triggeredProximityAlertTriggeredOptional. Service message. A user in the chat triggered another user's proximity alert while sharing Live Location.
voice_chat_scheduledVoiceChatScheduledOptional. Service message: voice chat scheduled
voice_chat_startedVoiceChatStartedOptional. Service message: voice chat started
voice_chat_endedVoiceChatEndedOptional. Service message: voice chat ended
voice_chat_participants_invitedVoiceChatParticipantsInvitedOptional. Service message: new participants invited to a voice chat
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message. login_url buttons are represented as ordinary url buttons.
-

MessageId

-

This object represents a unique message identifier.

- - - - - - - - - - - - - - - -
FieldTypeDescription
message_idIntegerUnique message identifier
-

MessageEntity

-

This object represents one special entity in a text message. For example, hashtags, usernames, URLs, etc.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the entity. Can be “mention” (@username), “hashtag” (#hashtag), “cashtag” ($USD), “bot_command” (/start@jobs_bot), “url” (https://telegram.org), “email” (do-not-reply@telegram.org), “phone_number” (+1-212-555-0123), “bold” (bold text), “italic” (italic text), “underline” (underlined text), “strikethrough” (strikethrough text), “code” (monowidth string), “pre” (monowidth block), “text_link” (for clickable text URLs), “text_mention” (for users without usernames)
offsetIntegerOffset in UTF-16 code units to the start of the entity
lengthIntegerLength of the entity in UTF-16 code units
urlStringOptional. For “text_link” only, url that will be opened after user taps on the text
userUserOptional. For “text_mention” only, the mentioned user
languageStringOptional. For “pre” only, the programming language of the entity text
-

PhotoSize

-

This object represents one size of a photo or a file / sticker thumbnail.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerPhoto width
heightIntegerPhoto height
file_sizeIntegerOptional. File size
-

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
-

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

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
-

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
-

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
-

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

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 auth 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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)
permissionsChatPermissionsYesNew 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 MessageEntityOptionalList 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 MessageEntityOptionalList 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
-

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
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
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
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/core.telegram.org/bots/faq.html b/data/core.telegram.org/bots/faq.html deleted file mode 100644 index c69a177090..0000000000 --- a/data/core.telegram.org/bots/faq.html +++ /dev/null @@ -1,243 +0,0 @@ - - - - - Bots FAQ - - - - - - - - - - - - - -
- -
-
-
- -

Bots FAQ

- -
-

If you are new to Telegram bots, we recommend checking out our Introduction to Bots first.
You may also find the Bot API Manual useful.

-
-

- -
-

General Questions

-

How do I create a bot?

-

Creating Telegram bots is super-easy, but you will need at least some skills at computer programming. In order for a bot to work, set up a bot account with @BotFather, then connect it to your backend server via our API.

-

Unfortunately, there are no out-of-the-box ways to create a working bot if you are not a developer. But we're sure you'll soon find plenty of bots created by other people to play with.

-

I'm a developer. Where can I find some examples?

-

Here are two sample bots, both written in PHP:

-
    -
  • Hello Bot demonstrates the basics of the Telegram bot API.
  • -
  • Simple Poll bot is a more complete example, it supports both long-polling and Webhooks for updates.
  • -
-
-

Many members of our community are building bots and publishing sources.
We're collecting them on this page »

-
-

Ping us on @BotSupport if you've built a bot and would like to share it with others.

-

Will you add X to the Bot API?

-

The bot API is still pretty young. There are many potential features to consider and implement. We'll be studying what people do with their bots for a while to see which directions will be most important for the platform.

-

All bot developers are welcome to share ideas for our Bot API with our @BotSupport account.

-

What messages will my bot get?

-

1. All bots, regardless of settings, will receive:

-
    -
  • All service messages.
  • -
  • All messages from private chats with users.
  • -
  • All messages from channels where they are a member.
  • -
-

2. Bot admins and bots with privacy mode disabled will receive all messages except messages sent by other bots.

-

3. Bots with privacy mode enabled will receive:

-
    -
  • Commands explicitly meant for them (e.g., /command@this_bot).
  • -
  • General commands from users (e.g. /start) if the bot was the last bot to send a message to the group.
  • -
  • Messages sent via this bot.
  • -
  • Replies to any messages implicitly or explicitly meant for this bot.
  • -
-

Note that each particular message can only be available to one privacy-enabled bot at a time, i.e., a reply to bot A containing an explicit command for bot B or sent via bot C will only be available to bot A. Replies have the highest priority.

-

Why doesn't my bot see messages from other bots?

-

Bots talking to each other could potentially get stuck in unwelcome loops. To avoid this, we decided that bots will not be able to see messages from other bots regardless of mode.

-

Getting Updates

-

How do I get updates?

-

There are currently two ways of getting updates. You can either use long polling or Webhooks. Please note that it's not possible to get updates via long polling while an outgoing Webhook is set.

-

Long polling gives me the same updates again and again!

-

The getUpdates method returns the earliest 100 unconfirmed updates. To confirm an update, use the offset parameter when calling getUpdates like this:

-
offset = update_id of last processed update + 1
-

All updates with update_id less than or equal to offset will be marked as confirmed on the server and will no longer be returned.

-

I'm having problems with Webhooks.

-

If you've set up your webhook successfully, but are not getting any updates, please remember:

-
    -
  • You need a valid SSL certificate for webhooks to work.
  • -
  • To use a self-signed certificate, you need to upload your public key certificate using the certificate parameter in setWebhook. Please upload as InputFile, sending a String will not work.
  • -
  • Ports currently supported for Webhooks: 443, 80, 88, 8443.
  • -
  • Wildcard certificates may not be supported.
  • -
  • Redirects are not supported.
  • -
  • CN must exactly match your domain.
  • -
-
-

Please check out this new WEBHOOK GUIDE to learn all there is to know about webhooks!

-
-

I'm having trouble with my self-signed certificate!

-

Please take a look at this self-signed certificate guide we made just for you. If you've read it and still have a question, ping us on botsupport.

-

How can I make sure that Webhook requests are coming from Telegram?

-

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL you give us, e.g. www.example.com/your_token. Since nobody else knows your bot's token, you can be pretty sure it's us.

-

How can I make requests in response to updates?

-

This is possible if you're using webhooks. The upside is that you need less requests, the downside — that in this case it's not possible to know that such a request was successful or get its result.

-

Whenever you receive a webhook update, you have two options:

-

1. Issue POST to https://api.telegram.org/bot<token>/method

-
- -
- -

2. Reply directly and give method as JSON payload in the reply

-
-
- -
-

You may also want to look at our sample HelloBot, it offers a PHP implementation of this.

-
-

Handling Media

-

How do I download files?

-

Use the getFile method. Please note that this will only work with files of up to 20 MB in size.

-

How do I upload a large file?

-

Bots can currently send files of any type of up to 50 MB in size, so yes, very large files won't work for now. Sorry. This limit may be changed in the future.

-

Can I count on file_ids to be persistent?

-

Yes, file_ids can be treated as persistent.

-

Broadcasting to Users

-

My bot is hitting limits, how do I avoid this?

-

When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.

-

If you're sending bulk notifications to multiple users, the API will not allow more than 30 messages per second or so. Consider spreading out notifications over large intervals of 8—12 hours for best results.

-

Also note that your bot will not be able to send more than 20 messages per minute to the same group.

-

How can I message all of my bot's subscribers at once?

-

Unfortunately, at this moment we don't have methods for sending bulk messages, e.g. notifications. We may add something along these lines in the future.

-

In order to avoid hitting our limits when sending out mass notifications, consider spreading them over longer intervals, e.g. 8-12 hours. The API will not allow bulk notifications to more than ~30 users per second, if you go over that, you'll start getting 429 errors.

-

See also: How to avoid hitting limits?

-
-
-

If you've got questions that are not answered on this page, ping us at @BotSupport in Telegram.
We welcome any suggestions for the Bot Platform and API.

-
-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots/games.html b/data/core.telegram.org/bots/games.html deleted file mode 100644 index aba4ca2be2..0000000000 --- a/data/core.telegram.org/bots/games.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - Gaming Platform - - - - - - - - - - - - - -
- -
-
-
- -

Gaming Platform

- -
- -
- -
- -

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Games are a new type of content on Telegram that your bot can send to users.

-
-

-
- -
-

This introduction is meant for bot developers. Click here, in case you'd like something more user-friendly.
Check out the @gamebot and @gamee bots for examples of what you can do using the new Gaming Platform.

-
-

Creating a Game

-

To get started, send the /newgame command to @BotFather.You will be prompted for a description text and a photo. You can also upload an optional GIF animation that demostrates your game to the users to make messages with the game more attractive (check out Lumberjack or Corsairs for examples).

-

Launching the Game

-

Once the game is created, your bot can send it to chats as regular messages, or offer them via inline mode. The game message will always have an inline Play button.

-

When this button is pressed, your bot gets a callback query that indicates the requested game. You provide the correct URL for this particular user and the app automatically opens the game in the in-app browser.

-

Adding Buttons

-

If you send the game message without any buttons, it will automatically have a 'Play GameName' button. You can manually add multiple buttons to your game message. Please note that the first button in the first row must always be the one that launches the game. You can add more buttons: e.g., for a description of the rules, or a button that links to the game's official community.

-

Tracking High Scores

-

The message with your game will also display high scores for the current chat. When a new high score is set, a service message will be sent to the chat and the message with the current scoreboard will be updated. You can also request the necessary data for building in-game high score tables.

-
-
- -

- -

- -

Sharing Your Game to Telegram Chats

-

There are many way for users to spread your game virally if they like it. The interface will always have the standard system button for sharing the game in the top right corner:

-
- - -

- -
- - - -

You can also create an additional Share button inside your HTML page. Pressing this button will send the game to a desired chat along with the user's best score in the game.

-
- - - - - -

- - -

To add the sharing button, include this script at the end of the <body> tag on your page:

-
<script src="https://telegram.org/js/games.js"></script>
-

Then use the method TelegramGameProxy.shareScore() to call the sharing option.

-
-

Warning: Do not call this method without consent and direct action from the user.

-
-

Example:

-
<button onclick="TelegramGameProxy.shareScore()">Share score</button>
-

This library will only work when launched from inside Telegram, so please don't use it on ordinary web pages.

-

Using URL Parameters

-

If your URL is using a fragment identifier, please note that Telegram Apps could add certain service parameters to the fragment id. The names for such parameters will start in tg (you can check the code that adds them here). Use the TelegramGameProxy.initParams object if you need to read your own parameters from the fragment id.

-

Creating a Great HTML5 Experience

-

Please make sure that your HTML5 page is responsive and works well on all Telegram apps and supported platforms. If you find it impossible to support certain conditions or platforms, don't leave your users hanging and at least provide a notification.

-
-

See the Bot API Manual for the relevant methods and objects.

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/inline.html b/data/core.telegram.org/bots/inline.html deleted file mode 100644 index 7aac930537..0000000000 --- a/data/core.telegram.org/bots/inline.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - Inline Bots - - - - - - - - - - - - - -
- -
-
-
- -

Inline Bots

- -
- -
- -
- -

Beyond sending commands in private messages or groups, users can interact with your bot via inline queries. If inline queries are enabled, users can call your bot by typing its username and a query in the text input field in any chat. The query is sent to your bot in an update. This way, people can request content from your bot in any of their chats, groups, or channels without sending any messages at all.

-
-
-
- - -

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot’s name.

-
-

See the Bot API Manual for the relevant methods and objects.

-
-

Inline results

-

Inline bots support all types of content available in Telegram (20 in all). They are capable of sending stickers, videos, music, locations, documents and more.

-
-

-
- -

Clients can display the results with vertical or horizontal scrolling, depending on the type of content:

-
- - - - - -
-
- -

As soon as the user taps on an item, it's immediately sent to the recipient, and the input field is cleared.

-

Switching inline/PM modes

-

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

-
-

-
- -

You can display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

-

Sample bots
@youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.

-
-

Manual: Switch to PM

-
-

Location-based results

-

Inline bots can request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

-

Sample bot
@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

-

Spreading virally

-

Messages sent with the help of your bot will show its username next to the sender's name.

-
- - - - - -

- -

When a user taps on the bot username in the message header, the mention is automatically inserted into the input field. Entering the @ symbol in the input field brings up a list of suggestions, featuring recently used inline bots.

-

Collecting feedback

-

To know which of the provided results your users are sending to their chat partners, send @Botfather the /setinlinefeedback command. With this enabled, you will receive updates on the results chosen by your users.

-

Please note that this can create load issues for popular bots – you may receive more results than actual requests due to caching (see the cache_time parameter in answerInlineQuery). For these cases, we recommend adjusting the probability setting to receive 1/10, 1/100 or 1/1000 of the results.

-

Inline bot samples

-

Here are some sample inline bots, in case you’re curious to see one in action. Try any of these:
@gif – GIF search
@vid – Video search
@pic – Yandex image search
@bing – Bing image search
@wiki – Wikipedia search
@imdb – IMDB search
@bold – Make bold, italic or fixed sys text

-

NEW
@youtube - Connect your account for personalized results
@music - Search and send classical music
@foursquare – Find and send venue addresses
@sticker – Find and send stickers based on emoji

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/samples.html b/data/core.telegram.org/bots/samples.html deleted file mode 100644 index fa0c518df4..0000000000 --- a/data/core.telegram.org/bots/samples.html +++ /dev/null @@ -1,247 +0,0 @@ - - - - - Bot Code Examples - - - - - - - - - - - - - -
- -
-
-
- -

Bot Code Examples

- -
-

If you want to learn more about Telegram bots, start with our Introduction to Bots »
Check out the FAQ, if you have questions.

-
-

Many members of our community are building bots and libraries and publishing their source code. We collect these examples here. Ping us on BotSupport if you've built a bot and would like to share its code with others.

-

PHP

- -

Node.js

- -

Rust

- -

Python

- -

Ruby

- -

Swift

- -

Kotlin

- -

Java

- -

Go

- -

Other Languages

- -
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots/samples/hellobot.html b/data/core.telegram.org/bots/samples/hellobot.html deleted file mode 100644 index a60f383356..0000000000 --- a/data/core.telegram.org/bots/samples/hellobot.html +++ /dev/null @@ -1,287 +0,0 @@ - - - - - Hellobot - - - - - - - - - - - - - -
- -
-
-
- -

Hellobot

- -
-

This sample PHP bot demonstrates the basics of the Telegram Bot API.
If you have questions, try our FAQ or check out this page for more examples.

-
-

- -
<?php
-
-define('BOT_TOKEN', '12345678:replace-me-with-real-token');
-define('API_URL', 'https://api.telegram.org/bot'.BOT_TOKEN.'/');
-
-function apiRequestWebhook($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  $parameters["method"] = $method;
-
-  $payload = json_encode($parameters);
-  header('Content-Type: application/json');
-  header('Content-Length: '.strlen($payload));
-  echo $payload;
-
-  return true;
-}
-
-function exec_curl_request($handle) {
-  $response = curl_exec($handle);
-
-  if ($response === false) {
-    $errno = curl_errno($handle);
-    $error = curl_error($handle);
-    error_log("Curl returned error $errno: $error\n");
-    curl_close($handle);
-    return false;
-  }
-
-  $http_code = intval(curl_getinfo($handle, CURLINFO_HTTP_CODE));
-  curl_close($handle);
-
-  if ($http_code >= 500) {
-    // do not wat to DDOS server if something goes wrong
-    sleep(10);
-    return false;
-  } else if ($http_code != 200) {
-    $response = json_decode($response, true);
-    error_log("Request has failed with error {$response['error_code']}: {$response['description']}\n");
-    if ($http_code == 401) {
-      throw new Exception('Invalid access token provided');
-    }
-    return false;
-  } else {
-    $response = json_decode($response, true);
-    if (isset($response['description'])) {
-      error_log("Request was successful: {$response['description']}\n");
-    }
-    $response = $response['result'];
-  }
-
-  return $response;
-}
-
-function apiRequest($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  foreach ($parameters as $key => &$val) {
-    // encoding to JSON array parameters, for example reply_markup
-    if (!is_numeric($val) && !is_string($val)) {
-      $val = json_encode($val);
-    }
-  }
-  $url = API_URL.$method.'?'.http_build_query($parameters);
-
-  $handle = curl_init($url);
-  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
-  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
-  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
-
-  return exec_curl_request($handle);
-}
-
-function apiRequestJson($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  $parameters["method"] = $method;
-
-  $handle = curl_init(API_URL);
-  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
-  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
-  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
-  curl_setopt($handle, CURLOPT_POST, true);
-  curl_setopt($handle, CURLOPT_POSTFIELDS, json_encode($parameters));
-  curl_setopt($handle, CURLOPT_HTTPHEADER, array("Content-Type: application/json"));
-
-  return exec_curl_request($handle);
-}
-
-function processMessage($message) {
-  // process incoming message
-  $message_id = $message['message_id'];
-  $chat_id = $message['chat']['id'];
-  if (isset($message['text'])) {
-    // incoming text message
-    $text = $message['text'];
-
-    if (strpos($text, "/start") === 0) {
-      apiRequestJson("sendMessage", array('chat_id' => $chat_id, "text" => 'Hello', 'reply_markup' => array(
-        'keyboard' => array(array('Hello', 'Hi')),
-        'one_time_keyboard' => true,
-        'resize_keyboard' => true)));
-    } else if ($text === "Hello" || $text === "Hi") {
-      apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'Nice to meet you'));
-    } else if (strpos($text, "/stop") === 0) {
-      // stop now
-    } else {
-      apiRequestWebhook("sendMessage", array('chat_id' => $chat_id, "reply_to_message_id" => $message_id, "text" => 'Cool'));
-    }
-  } else {
-    apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'I understand only text messages'));
-  }
-}
-
-
-define('WEBHOOK_URL', 'https://my-site.example.com/secret-path-for-webhooks/');
-
-if (php_sapi_name() == 'cli') {
-  // if run from console, set or delete webhook
-  apiRequest('setWebhook', array('url' => isset($argv[1]) && $argv[1] == 'delete' ? '' : WEBHOOK_URL));
-  exit;
-}
-
-
-$content = file_get_contents("php://input");
-$update = json_decode($content, true);
-
-if (!$update) {
-  // receive wrong update, must not happen
-  exit;
-}
-
-if (isset($update["message"])) {
-  processMessage($update["message"]);
-}
-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots/self-signed.html b/data/core.telegram.org/bots/self-signed.html deleted file mode 100644 index efe82919b4..0000000000 --- a/data/core.telegram.org/bots/self-signed.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - Using self-signed certificates - - - - - - - - - - - - - -
- -
-
-
- -

Using self-signed certificates

- -

Upload your certificate using the certificate parameter in the setWebhook method. The certificate supplied should be PEM encoded (ASCII BASE64), the pem file should only contain the public key (including BEGIN and END portions). When converting from a bundle format, please split the file to only include the public key.

-

Generating a self-signed certificate pair (PEM):

-

Openssl

-
-

Windows binaries for Openssl are available online

-
-

openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"

-

YOURPUBLIC.pem has to be used as input for setting the self-signed webhook.

-

You can inspect the generated certificate with:
openssl x509 -text -noout -in YOURPUBLIC.pem

-

Converting from a previously generated DER:
openssl x509 -inform der -in YOURDER.der -out YOURPEM.pem

-

Converting from a previously generated PKCS12:
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

-
-

More information: https://www.openssl.org/

-
-

Java keystore

-

Generate self-signed JKS:
keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

-

Converting JKS to pkcs12 (intermediate step for conversion to PEM):
keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

-

Convert PKCS12 to PEM (requires openssl):
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

-
-

More information: https://docs.oracle.com

-
-

Windows

-

Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.

-

On the commandline:
certreq -new TEMPLATE.txt RequestFileOut

-

TEMPLATE.txt example file:

-
[NewRequest]
-
-; At least one value must be set in this section
-Subject = "CN=DOMAIN.EXAMPLE"
-KeyLength = 2048
-KeyAlgorithm = RSA
-HashAlgorithm = sha256
-;MachineKeySet = true
-RequestType = Cert
-UseExistingKeySet=false ;generates a new private key (for export)
-Exportable = true ;makes the private key exportable with the PFX
-

A self-signed certificate will be generated and installed, to view the certificate:
certutil -store -user my

-

To export in DER format (intermediate step for conversion to PEM)
certutil -user -store -split my SERIALNUMBER YOURDER.crt

-

Converting to PEM (used for setting the webhook)
certutil -encode YOURDER.crt YOURPEM.cer

-

To delete a certificate from your store:
certutil -delstore -user my SERIALNUMBER (from view)

-

To export in PFX(PKCS12) format
certutil -exportpfx -user YOURDOMAIN.EXAMPLE YOURPKCS.pfx NoChain

-
-

More information: https://technet.microsoft.com

-
-

Converting YOURPKCS.pfx to PEM including the private key is best done with OpenSSL:
openssl pkcs12 -in YOURPKCS.pfx -out YOURPEM.cer

-

Remember that only the public key is needed as input for the self-signed webhook certificate parameter. certmgr.msc can also be used as a GUI to export the public part of self-signed certificates to PEM.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots/webhooks.html b/data/core.telegram.org/bots/webhooks.html deleted file mode 100644 index f22400f08f..0000000000 --- a/data/core.telegram.org/bots/webhooks.html +++ /dev/null @@ -1,827 +0,0 @@ - - - - - Marvin's Marvellous Guide to All Things Webhook - - - - - - - - - - - - - -
- -
-
-
- -

Marvin's Marvellous Guide to All Things Webhook

- -
- -

We currently support two ways of processing bot updates, getUpdates and setWebhook. getUpdates is a pull mechanism, setwebhook is push. Although the concept of a webhook is fairly simple, the setup of the individual components has proven to be tricky for many. This guide provides some extra information for those of you brave enough to venture into the art of the webhook.

-

There are some advantages of using a webhook over getUpdates. As soon as an update arrives, we’ll kindly deliver it to your bot for processing.

-

This:

-
1. Avoids your bot having to ask for updates frequently.
-2. Avoids the need for some kind of polling mechanism in your code.
-

Other advantages may include saving some potential CPU cycles and an increase in response time, these things however depend heavily on the usage pattern of your bot.

-

Setting a webhook means you supplying Telegram with a location in the form of a URL, on which your bot listens for updates. We need to be able to connect and post updates to that URL.

-

To ensure that we can do that, there are some basic requirements:

-

The short version

-

You'll need a server that:

-
    -
  • Supports IPv4, IPv6 is currently not supported for webhooks.
  • -
  • Accepts incoming POSTs from subnets 149.154.160.0/20 and 91.108.4.0/22 on port 443, 80, 88, or 8443.
  • -
  • Is able to handle TLS1.2(+) HTTPS-traffic.
  • -
  • Provides a supported, non-wildcard, verified or self-signed certificate.
  • -
  • Uses a CN or SAN that matches the domain you’ve supplied on setup.
  • -
  • Supplies all intermediate certificates to complete a verification chain.
  • -
-

That’s almost all there’s to it.
If you decide to limit traffic to our specific range of addresses, keep an eye on this document whenever you seem to run into trouble. Our IP-range might change in the future.

-

The longer version

-
    -
  • A domain name

    -

    Setting a webhook needs a URL for us to post to. For that you'll need a server with a domain name. If you don't have one, you'll need to obtain one first. Telegram currently doesn't offer hosting or domain name services. There are quite a few VPS/Web hosting providers around the internet, feel free to pick one to your liking.
    If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    How do I get a server with a domain name?

    -
  • -
  • An open port

    -

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    -
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
    -Whenever something stops working in the future, please check this document again as 
    -the range might expand or change.
    -

    How do I check for open ports or limit access to my bot?

    -
  • -
  • Always SSL/TLS

    -

    A webhook requires SSL/TLS encryption, no matter which port is used. It's not possible to use a plain-text HTTP webhook. You shouldn't want to either, for the sake of your bot and users.
    SSL/TLS, why do I have to handle this for a webhook?

    -
  • -
  • Not all SSL/TLS is equal

    -

    We support any SSL/TLS version TLS1.2 and up for your webhook. This means that SSLV2/3/TLS1.0/TSL1.1 are NOT supported, due to security issues associated with those older versions.
    How do I check that I’m handling the right version?

    -
  • -
  • SSL needs a certificate

    -

    The common name (CN) of your certificate (self-signed or verified) has to match the domain name where your bot is hosted. You may also use a subject alternative name (SAN), that matches the domain for your webhook. Server Name Indication (SNI)-routing is supported. If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    A certificate, where do I get one, and how?

    -
  • -
  • Verified or self-signed

    -

    A certificate can either be verified or self-signed. Setting a webhook with a self-signed certificate differs a little from setting a webhook with a verified certificate. Ensure you're using the correct setup for the type of certificate you've chosen for your webhook.
    How do I set a webhook for either type?

    -
  • -
  • Supported certificates

    -

    Not all verified certificates are supported. Certificates are based on a network of trust and come in a chain. Trusting your verified certificate means we have to trust the provider of that certificate, the Certificate Authority (and hence its root certificate). Before you pick a certificate provider, Check this list to make sure that we actually trust their root certificate.
    What if my root certificate isn’t on that list?

    -
  • -
  • An Untrusted root

    -

    Ok, so you already had a certificate installed and just discovered it’s not on our list.
    Start by ignoring it, and just try to set it. We occasionally add extra root certificates to keep up with popular demand, so the list isn't always exhaustive. Unlucky after all? We'll allow you to supply an unsupported root certificate when setting the webhook. This method is nearly identical to setting a self-signed certificate webhook. Instead of your self-signed certificate you'll be sending us the root certificate as inputFile.
    Setting a verified webhook with an untrusted root

    -
  • -
  • Intermediate certificates

    -

    Some verified certificates require an intermediate certificate. In this construction the provider of your verified certificate has used their root certificate to sign an intermediate certificate. This intermediate certificate is then used to sign your verified certificate. You'll need to provide the intermediate certificate for us to be able to verify the chain of trust. CA's that use this type of chain supply an intermediate certificate.
    Supplying an intermediate certificate

    -
  • -
  • More information

    -

    Since we know webhooks can be a tad overwhelming, we’re working on a little digital assistant that’ll try and help you with the most common problems, it's not nearly perfect, but you may try using @CanOfWormsBot to check if your chain of certificates is installed correctly before contacting support.

    -
  • -
  • Testing your bot

    -

    We took the liberty of adding a set of example updates. They come in handy when testing your bot, no matter which method of getting updates you might be using.

    -
  • -
  • Don't panic.

    -

    If by now you're looking for your fishing gear because we've mentioned ports and hooks or you're about to Google what kind of bait URL and TLS exactly are, this guide might not be completely for you. You’re quite likely still a brilliant bot programmer, don’t worry. Perhaps this whole webhook thing is just new to you, not all is lost. If you currently have a working getUpdates situation, it's a good idea to pick up this guide again on a rainy Sunday afternoon and take your time to read up on some subjects around the internet. This guide can only contain a finite amount of information after all.

    -
  • -
-

The verbose version

-
How do I get a server with a domain name?
-

If you use a webhook, we have to deliver requests to your bot to a server we can reach. So yes, you need a server we can connect to. It can be anywhere in the galaxy, if you ensure we can reach the server by domain name (or at least via IP for a self-signed certificate), it will work just fine.

-

There are quite a few ways to get this done, as a novice however it's likely that you're not directly jumping at the chance of crafting this from scratch. Actually, as a novice, we recommend you don't. It's likely to be a complex and long ride.

-

If you got stuck here, make a choice:

-
    -
  • You use getUpdates at the moment and it works, keep it that way. Especially if you're running your bot from a nice machine that does well. There is nothing wrong with using getUpdates.

    -
  • -
  • Go with a hosted service and let a bunch of professionals worry about things like registering a domain, setting up DNS, a web server, securing it and so on.

    -
  • -
-
If you're going with a hosted service, make sure to look for a hosting provider that 
-not only supports your code’s needs, for example: support for your PHP version,
-but one that also handles SSL and allows you to create/deploy certificates.
-
    -
  • Go crazy, dive on the internet and start reading. Once you’re confident that you’ve got all the basic theories down, find yourself a nice hosted VPS or roll your own machine at home and get back to us here.
  • -
-
How do I check for open ports or limit access to my bot?
-

So you have the hosting thing down and all is good so far, however, when you enter the address of your bot in your browser it seems unreachable.

-

Explaining every firewall or web server solution in detail isn't possible for us, which we hope you understand. If you’re running a hosted solution, you’re more likely to have a nice UI where you configure these settings. Head to your configuration panel and check all of them. If you’re on a Linux based VPS with shell access, we have some tips for you:

-
    -
  • Make sure your bot process is indeed configured to listen on the port you're using.
    netstat –ln | grep portnumber
    Shows you if your bot is actually listening for incoming requests on the port you expect.
    sudo lsof -i | grep process name
    Is a simple way to check if that’s actually being listened on by the process your bot is using.
  • -
-
    -
  • Make sure it’s listening correctly.
    Your bot has to listen on the address you’ve exposed to the outside (your public IP), it can also listen on all addresses (*: or 0.0.0.0).
    The netstat and lsof-commands mentioned above assist in checking this. If nothing shows up, it is time to check your configuration and fix it. Set the correct IP, make sure it’s listening on a supported port and fire away! Just use a Web Browser to check if you’re reachable. The problem can be in the configuration of your bot, your web server virtual host configuration, or the servers binding configuration.
  • -
-
    -
  • If you still can’t reach your address, check your firewall.
    sudo iptables –L
    OR
    sudo ufw status verbose (Ubuntu)
    Gives you some insight in the current firewall settings.

    -
  • -
  • If it looks like you’re blocking incoming traffic, let’s fix that.
    sudo iptables –A INPUT –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow portnumber/tcp
    Allows incoming traffic on all interfaces to the specified tcp port.
    sudo iptables –A INPUT –i interfacename –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp
    Allows incoming traffic to a specific interface and a specific port from everywhere.
    sudo ifconfig
    Helps you find the interface with the public address you’re going to use.

    -
  • -
-
If you use iptables, make sure to actually SAVE after changing the configuration.
-On a Debian based system the iptables-persistent package is be a good option.
-RHEL/CentOS offers a service iptables save -command.
-A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.
-
    -
  • If you’re just looking for some hints on how to limit incoming traffic:
    sudo iptables –A INPUT –i interfacename –p tcp –m iprange –src-range 149.154.167.197-149.154.167.233 –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp from 149.154.167.192/26
    Allows incoming traffic to a specific interface and a specific port from a specific range of addresses. (ufw is using a subnet mask in the example, ranging from 192-255)
  • -
-

That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

-
SSL/TLS, what is it and why do I have to handle this for a webhook?
-

You’re already familiar with it in some form or another. Whenever you see that (nicely green) lock in your browser bar, you know it’s reasonably safe to assume that you’ve landed on the site you actually wanted to visit. If you see the green lock, that's SSL/TLS in action. If you want to learn more about how SSL/TLS works in general, it's best to search the internet.

-

The main difference between getUpdates and a webhook is the way the connection takes place. getUpdates means you'll connect to our server, a webhook means we'll be connecting to your server instead. Connecting to your server has to be done secure, we have to know for sure it's you we're talking to after all. This means you'll have to handle all that server side encryption stuff, virtually presenting us with a green lock. If you use a web server for us to post to, you need to support SSL/TLS handling on the port/virtual host of your choice. An online search for “YOURWEBSERVER enable HTTPS” will help you.

-

Not using a regular web server? Have a look at our example page, most examples there include code for handling SSL/TLS in a webhook setup.

-
How do I check that I’m handling the right version?
-

You just read up on the whole SSL/TLS stuff, figured out that it’s not all that bad to setup and we add some more requirements. Here are some tips to check if you’re indeed supporting at least TLS1.2.

-
    -
  • Several online services exist that allow you to check your certificate installation,
    They give you an overview of your supported TLS versions/Cipher suites and other details. Search online for Symantec crypto report or Qualys ssl. Both supply tools to verify your setup.

    -
  • -
  • Checking locally can also be done, in several ways, here are three options,

    -
      -
    • Go simple:
      Using Chrome as a browser? Open up the URL to your bot and inspect the certificate details. If you’re supporting TLS Chrome tells you so in the security overview tab. Other browsers are likely able to give you similar basic information.

      -
    • -
    • Using curl:
      curl --tlsv1.2 -v -k https://yourbotdomain:yourbotport/
      You can add --tlsv1.2 to force curl into using TLS1.2 when trying to connect. -k is optional and used to check against a self-signed certificate. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using.

      -
    • -
    • Using OpenSSL
      openssl s_client -tls1_2 -connect yourbotdomain:yourbotport -servername yourbotdomain
      You can add -tls1_2 to force OpenSSL into using TLS1.2 when trying to connect. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using. Note that https:// isn’t used for OpenSSL. -servername is optional, and included here for some shared hosters, which use SNI to route traffic to the correct domain. When SNI is used you’ll notice that your server appears to be returning a certificate for a different domain than your own. Adding -servername yourbotdomain ensures that SNI negotiation is done, and the correct certificate is returned.

      -
    • -
    -
  • -
  • Some additional configuration pointers

    -
      -
    • Forcing TLS in your virtual host on Apache:
      SSLProtocol -all +TLSv1.2
    • -
    • Forcing TLS in your virtual host on Nginx:
      ssl_protocols TLSv1.2;
    • -
    • Force TLS for your Java virtual machine through system properties:
      -Dhttps.protocols=TLSv1.2 -Djdk.tls.client.protocols=TLSv1.2
    • -
    • Enabling ssl debug for your JVM:
      -Djavax.net.debug=ssl,handshake,record
    • -
    -
  • -
  • Other tools that may help in debugging issues:

    -
      -
    • Wireshark: excellent packet capturing
    • -
    • Tcpdump: equally excellent and doesn’t need a GUI
    • -
    • Charles: web debugging proxy
    • -
    • Fiddler: web debugging proxy
    • -
    -
  • -
-
A certificate, where do I get one and how?
-

You need a certificate, pick on of these types;

-
    -
  • A verified, supported certificate
  • -
  • A self-signed certificate

    -
  • -
  • A verified, supported certificate
    -

    Using a verified certificate means you already have, or will obtain, a certificate backed by a trusted certificate authority (CA). There are many ways to acquire a verified certificate, paid or free. Two popular examples of free suppliers are StartSSL and Let’s Encrypt. You’re welcome to pick another. Just make sure first the supplier is likely to be supported.
    Check this list before selecting a CA.
    Once you’ve picked a CA and validated your identity with them, you can craft your certificate. This frequently starts by generating a CSR (Certificate Signing Request). Generating a CSR is done either through your host machine, or online via the tools provided by the CA.

    -
  • -
  • Here is an example (PEM format output).

    -
      -
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -keyout yourprivatekey.key -out yoursigningrequest.csr
    • -
    -
  • -
-
----
-Generating a 2048 bit RSA private keywriting new private key to yourprivatekey.key
-Enter PEM pass phrase: enter a password for your key here 
-Verifying - Enter PEM pass phrase: confirm the entered password
------
-You are about to be asked to enter information that will be incorporated
-into your certificate request.
-What you are about to enter is what is called a Distinguished Name or a DN.
-There are quite a few fields but you can leave some blank
-For some fields there will be a default value,If you enter '.',
-the field will be left blank.-----
-Country Name (2 letter code) [AU]:
-State or Province Name (full name) [Some-State]:
-Locality Name (eg, city) []:
-Organization Name (eg, company) [Internet Widgits Pty Ltd]:
-Organizational Unit Name (eg, section) []:
-Common Name (e.g. server FQDN or YOUR name) []: yourbotdomainname
-Email Address []:
-Please enter the following 'extra' attributes
-to be sent with your certificate request
-A challenge password []:
-An optional company name []:
----
-
    -
  • Another example:

    -
      -
    • Using Java keytool:
      keytool -genkey -alias yourbotdomainname -keyalg RSA -keystore yourkeystore.jks -keysize 2048
    • -
    -
  • -
-
---
-Enter keystore password:  
-Re-enter new password: 
-What is your first and last name?  [Unknown]: yourbotdomainname
-What is the name of your organizational unit?  [Unknown]:  
-What is the name of your organization?  [Unknown]:  
-What is the name of your City or Locality?  [Unknown]:  
-What is the name of your State or Province?  [Unknown]:  
-What is the two-letter country code for this unit?  [Unknown]:  
-Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?  
-[no]:  yes
-Enter key password for yourbotdomainname   
-(RETURN if same as keystore password): 
----
-

This generates the initial keystore, from which you can then create a CSR like this:

-

keytool -certreq -alias yourbotdomainname -keystore yourkeystore.jks -file yourbotdomainname.csr

-
---
-Enter keystore password:
----
-

To validate your certificate the Common Name (CN) has to match your webhook domain. Example, if you’re using https://www.example.com/example.php as a webhook address, the certificate CN has to be www.example.com.
So you need an exact match of the FQDN you’re setting for the webhook

-

There is an exception, if you’re using a SAN (Subject Alternative Name) the webhook address can either match the CN of your certificate, OR one of the SANs provided in the certificate. In most cases you’ll be using the CN.

-

Create your CSR and supply the contents of the file to your CA. Most CA’s are kind enough to give you an example command of the input format they expect.

-

cat yoursigningrequest.csr or cat yourbotdomainname.csr
Lets you have a look at the CSR we just generated:

-
- -
- -

That doesn’t seem to informative, but we can deduce that the file is in PEM format (ASCII base64 encoded) and contains a certificate signing request. Luckily it is possible to look at the human readable contents of the CSR. Use the following commands to double check if all fields are set correctly.

-
    -
  • Using OpenSSL
    openssl req -text -noout -verify -in yoursigningrequest.csr

    -
  • -
  • Using Java keytool
    keytool -printcertreq -v -file yourbotdomainname.csr

    -
  • -
-

Verify your CSR and supply it to your CA to get a certificate. We’ll use StartSSL as an example here. StartSSL allows you to set up to 5 names (SAN), Their intermediate certificate is also needed for a webhook to work, which makes for a nice complete example.

-

Go to the certificates wizard, enter the required hostname(s) for your SSL certificate (this is the CN you’ve also set in the CSR and an optional SAN).

-
- -
- -

In the example above we’ve chosen to set a CN (test.telegram.org), but also a SAN (sanexample.telegram.org) The CN given has to match the CN used for generating the CSR.
Set your CN (and optional SAN) and copy the contents of the yoursigningrequest.csr file.

-
- -
- -

Paste the contents, submit and you’re done.

-
- -
- -

Now you can download the created certificate directly. In the example used above you’ll receive a zip file with several PEM certificates. The root, intermediate and yourdomain certificate.
You need the intermediate and yourdomain to set a webhook with a StartSSL certificate.

-

You can inspect the set of certificates you’ve just downloaded.

-
    -
  • Here are some example commands:

    -
      -
    • Using OpenSSL:
      openssl x509 -in yourdomain.crt -text -noout

      -
    • -
    • Using Java keytool:
      keytool -printcert -v -yourdomain.crt

      -
    • -
    • Using Windows:
      StartSSL supplies certificates in PEM format with a .crt extension, on Windows you can view the contents of them with a quick double click. Extract the files or open the “Otherserver.zip” and double click each of the certificates for inspection. The details tab supplies you with extra information.
      Make sure you have a correct CN in the Subject-field of the yourdomain-certificate. If you're using a SAN, make sure that it is listed in the Subject Alternative Name-field.

      -
    • -
    -
  • -
-
- -
- -

With your fresh certificates at hand, you can now continue setting your webhook.

-
    -
  • A self-signed certificate
    -

    Using a self-signed certificate means you’ll forfeit on the chain of trust backed by a CA. Instead you are the CA. For this to work, a slight difference in setup is required. Because Telegram will have no chain of trust to verify your certificate, you have to use the generated public certificate as an input file when setting the webhook. Keep in mind that the certificate file has to be uploaded as multipart/form data in PEM encoded (ASCII BASE64) format.

    -
  • -
  • First let’s generate some certificates:

    -
      -
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"
      You’ll end up with 2 files, a private key and the public certificate file. Use YOURPUBLIC.PEM as input file for setting the webhook.

      -
    • -
    • Using Java keytool:
      keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

      -
      What is your first and last name?
      -[test.telegram.org]:
      -What is the name of your organizational unit?
      -[Unknown]:  
      -What is the name of your organization?
      -[Unknown]:  
      -What is the name of your City or Locality?
      -[Unknown]:  
      -What is the name of your State or Province?
      -[Unknown]:  
      -What is the two-letter country code for this unit?
      -[Unknown]:  
      -Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
      -[no]: yes
      -

      Once done you’ll need 2 more commands to export the public certificate file from the generated store (you’ll be using the store for your JVM and the PEM for setting the webhook)

      -
    • -
    • Convert the JKS to pkcs12 (intermediate step for conversion to PEM):
      keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

      -
    • -
    • Convert PKCS12 to PEM (requires OpenSSL)
      openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem -nokeys

      -
    • -
    • Using Windows:
      Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.
      certreq -new TEMPLATE.txt RequestFileOut generates a CSR.

      -
    • -
    • TEMPLATE.txt example file:

      -
      [NewRequest]
      -; At least one value must be set in this section
      -Subject = "CN=DOMAIN.EXAMPLE"
      -KeyLength = 2048
      -KeyAlgorithm = RSA
      -HashAlgorithm = sha256
      -;MachineKeySet = true
      -RequestType = Cert
      -UseExistingKeySet=false ;generates a new private key (for export)
      -Exportable = true ;makes the private key exportable with the PFX
      -
    • -
    -
  • -
-

A self-signed certificate is generated and installed, to use the certificate for a self-signed webhook you'll have to export it in PEM format.

-
    -
  • Windows continued:

    -
      -
    • You can have a look at the certificates in your store with:
      certutil -store -user my

      -
    • -
    • To export the installed certificate in DER format (intermediate step for conversion to PEM):
      certutil -user -store -split my SERIALNUMBER YOURDER.der

      -
    • -
    • Now you can convert the certificate to PEM:
      certutil -encode YOURDER.der YOURPEM.pem
      Remember that only the public certificate is needed as input for the self-signed webhook certificate parameter.
      certmgr.msc can also be used as a GUI to export the public part of self-signed certificate to PEM.

      -
    • -
    -
  • -
-

After following the above you'll end up with a nice self-signed certificate. You’ll still have to set the webhook, and handle SSL correctly.

-
How do I set a webhook for either type?
-

The setWebhook method is needed for both types. For a verified certificate with a trusted root CA, it’s enough to use the setWebhook method with just the URL parameter.

-
    -
  • A curl example for a verified certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

For a self-signed certificate an extra parameter is needed, certificate, with the public certificate in PEM format as data.

-
    -
  • A curl example for a self-signed certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" -F "certificate=@<YOURCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

The -F means we’re using the multipart/form-data-type to supply the certificate, the type of the certificate parameter is inputFile. Make sure that you’re supplying the correct type.

-

Both parameters for the setWebhook method are classed as optional. Calling the method with an empty URL parameter can be used to clear a previously set webhook.

-
    -
  • A curl example to clear a previous webhook :
    curl -F "url=" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

Keep in mind that the URL parameter starts with https:// when setting a webhook. By default that means we’re knocking at your door on port 443. If you want to use another port (80,88 or 8443), you’ll have to specify the port in the URL parameter.

-
    -
  • Example:
    url=https://<YOURDOMAIN.EXAMPLE>:88/<WEBHOOKLOCATION>
  • -
-
Setting a verified webhook with an untrusted root
-

If you already have a verified certificate and our servers don’t trust your root CA, we have an alternative way for you to set a webhook. Instead of using the setWebhook method without the certificate parameter, you can use the self-signed method. Your CA's root certificate has to be used as an inputFile for the certificate parameter.

-
    -
  • A curl example to supply an untrusted root certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>" -F "certificate=@<YOURCAROOTCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
    Before you can do this, you need the root certificate of your certificate’s CA. Most CA’s supply their root certificates in several different formats (PEM/DER/etc.). Visit your CA’s website, and download the Root certificate indicated for your verified certificate.
  • -
-

You can use these commands to quickly convert a DER formatted root certificate to PEM:

-
    -
  • Using OpenSSL:
    openssl x509 -inform der -in root.cer -out root.pem

    -
  • -
  • Using Java keytool:
    keytool -import -alias Root -keystore YOURKEYSTORE.JKS -trustcacerts -file ROOTCERT.CER
    The root certificate needs to be imported in your keystore first:
    keytool -exportcert -alias Root -file <YOURROOTPEMFILE.PEM> -rfc -keystore YOURKEYSTORE.JKS

    -
  • -
-

Once done, set your webhook with the root-pem-file and you’ll be good to go. If you need more pointers, have a look at the self-signed part of this guide.

-
Supplying an intermediate certificate
-

Once you’ve crafted your certificate, your CA might present you with a nice bundle. Most bundles contain a root certificate, your public certificate and sometimes an intermediate certificate. StartSSL is one of many CA’s that’ll supply such an intermediate beast. This certificate has to be supplied in the chain of certificates you’re presenting to us when we connect to your server. If an intermediate was used to sign your certificate but isn’t supplied to our servers, we won’t be able to verify the chain of trust and your webhook will not work.

-

If your webhook isn’t working and you’re wondering if the chain is complete:

-
    -
  • Check with your certificate provider if you need an intermediate certificate.
  • -
  • Verify your certificate chain.
    Search online for Symantec crypto report or Qualys ssl. 
    -Both supply tools to verify your setup.
    -
  • -
-

Here’s an example of a complete chain, note that in this case 2 intermediate certificates have been supplied.

-
- -
- -

Even though your browser might not complain when visiting your page, an incomplete chain will not work for your webhook. If your chain is incomplete we have some tips to add them to your current setup:

-
    -
  • Apache:
    Add the intermediate certificate to the end of the file configured in the SSLCertificateFile directive of your virtual host configuration. If you’re using an older version than Apache 2.4.8, you may use the SSLCertificateChainFile directive instead.

    -
  • -
  • Nginx:
    Add the intermediate certificate to the end of the file configured in the ssl_certificate_key directive of your virtual host configuration.

    -
  • -
  • A quick command for doing this correctly:
    cat your_domain_name.pem intermediate.pem >> bundle.pem
    Make sure the order is correct, expect failure otherwise.

    -
  • -
  • Java keytool:
    keytool -import -trustcacerts -alias intermediate -file intermediate.pem -keystore YOURKEYSTORE.jks

    -
  • -
-

The end result of all this is a complete certificate chain, backed by either a root certificate we trust or, in the case of an untrusted root, a root certificate you're supplying to us. Make sure to verify your setup again after adding the intermediate, once done, you're good to go!

-
Testing your bot with updates
-
    -
  • Update examples
    A set of example updates, which comes in handy for testing your bot.

    -
      -
    • Message with text using curl:

      -
      curl --tlsv1.2 -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test",
      -     "username":"Test"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test",
      -     "username":"Test"
      -  },
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -

      --tlsv1.2 will force using TLS1.2.

      -
    • -
    • Message with text using Postman:

      -
      - -
      -
    • -
    -
  • -
  • More examples in curl:

    -
      -
    • Message with text:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "type": "private",
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Forwarded message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "type": "private",
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "forward_from": {
      -     "last_name":"Forward Lastname",
      -     "id": 222222,
      -     "first_name":"Forward Firstname"
      -  },
      -  "forward_date":1441645550,
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Forwarded channel message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "forward_from": {
      -     "id": -10000000000,
      -     "type": "channel",
      -     "title": "Test channel"
      -  },
      -  "forward_date":1441645550,
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with a reply:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"/start",
      -  "reply_to_message":{
      -      "date":1441645000,
      -      "chat":{
      -          "last_name":"Reply Lastname",
      -          "type": "private",
      -          "id":1111112,
      -          "first_name":"Reply Firstname",
      -          "username":"Testusername"
      -      },
      -      "message_id":1334,
      -      "text":"Original"
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Edited message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"edited_message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"Edited text",
      -  "edit_date": 1441646600
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with entities:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"Bold and italics",
      -  "entities": [
      -      {
      -          "type": "italic",
      -          "offset": 9,
      -          "length": 7
      -      },
      -      {
      -          "type": "bold",
      -          "offset": 0,
      -          "length": 4
      -      }
      -      ]
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with audio:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "audio": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "duration": 243,
      -      "mime_type": "audio/mpeg",
      -      "file_size": 3897500,
      -      "title": "Test music file"
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Voice message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "voice": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "duration": 5,
      -      "mime_type": "audio/ogg",
      -      "file_size": 23000
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with a document:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "document": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "file_name": "Testfile.pdf",
      -      "mime_type": "application/pdf",
      -      "file_size": 536392
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"inline_query":{
      -  "id": 134567890097,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "query": "inline query",
      -  "offset": ""
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Chosen inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"chosen_inline_result":{
      -  "result_id": "12",
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "query": "inline query",
      -  "inline_message_id": "1234csdbsk4839"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Callback query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"callback_query":{
      -  "id": "4382bfdwdsb323b2d9",
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "data": "Data from button callback",
      -  "inline_message_id": "1234csdbsk4839"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -That's all we have for now!
    • -
    -
  • -
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/cdn.html b/data/core.telegram.org/cdn.html deleted file mode 100644 index 2d0397674b..0000000000 --- a/data/core.telegram.org/cdn.html +++ /dev/null @@ -1,210 +0,0 @@ - - - - - Encrypted CDNs for Speed and Security - - - - - - - - - - - - - -
- -
-
-
-
-

Encrypted CDNs for Speed and Security

- -

Following the launch of version 4.2 of the official apps, Telegram client apps may be required to download popular files that were published in public channels with more than 100,000 members from secondary Content Delivery Network data centers. These CDN DCs are located in regions with significant Telegram traffic where we wouldn't want to place Telegram servers for various reasons.

-

The CDN DCs are not a part of the Telegram cloud and should be considered enemy territory. For this reason, each file that is to be sent to these CDN DCs is encrypted with a unique key using AES-256-CTR encryption. The CDN can't access the data it stores because these keys are only accessible to the main MTProto server and to the authorized client.

-
-

See also: More about CDNs and governments in the Advanced FAQ

-
-

How this works

-

When a file from a public channel with ~100,000 members becomes popular in a particular region, the Telegram server may encrypt this file with a unique AES-256-CTR key and send it to a relevant CDN DC for storage.

-

When a file is stored in a CDN DC close to the end user, the download speed will be much higher because the data needs to travel smaller distances and will likely avoid many bottlenecks that exist between regions.

-

This is secure because CDN DCs are treated the same way as internet providers / random third parties:

-
    -
  • CDN DCs don‘t have the keys to decrypt files that are stored there, so they can’t access the data even if a DC becomes compromised.
  • -
  • Encrypted files fragments are protected from tampering by their SHA-256 hash which is checked on the client upon receipt.
  • -
  • No private data is stored in or passed to the CDN DCs.
  • -
  • The server only allows media from public channels with more than 100,000 subscribers to be cached in CDN DCs (this includes media forwarded from those channels and viral media that originated from other large public channels).
  • -
-
- -
- -

CDNs are very limited when it comes to communication: the master data center only uploads encrypted files for storage and will accept no data from the CDN. The client apps only download encrypted files and accept no other updates. The client apps obtain the keys necessary to decrypt the file from the main Telegram server and verify the integrity of the file by its hash, which means that the CDN may only supply the correct file – anything different will be immediately discarded by the client.

-

CDN DCs do not store files on hard disks – only in memory. When a CDN server runs out of memory, a simple LRU algorithm is used to replace the least popular files with new ones.

-

How CDN DCs are different from the master DCs

-
    -
  • CDNs may not be trusted.
  • -
  • Client developers can use help.getCdnConfig to obtain a list of public RSA keys for CDN DCs, which are different from public RSA keys of the master DCs.
  • -
  • CDNs support only the following methods: upload.getCdnFile, initConnection, invokeWithLayer.
  • -
  • When working with CDNs, client developers must remember that auth_key may be deleted at any given moment (resulting in a -404 error, in which case a new key must be generated).
  • -
  • Client apps must not accept updates from CDN DCs (apps should only accept updates from their main connection to the master DC).
  • -
  • Clients must not allow the CDN DCs to substitute replies to queries sent to other DCs.
  • -
  • Clients must not send private user info that is passed in initConnection to the CDNs.
  • -
-

Getting files from a CDN

-

The API may return the upload.fileCdnRedirect constructor after an upload.getFile query. In this case, the client must request the required file from a CDN DC. The dc_id in the response is the id of the new CDN. The IP address for the connection will be available in help.getConfig, same as with the master DCs. The corresponding dcOption will have the flag cdn:flags.3?true.

-

Once a successful connection to the CDN-dc_id is established, the client must generate an auth_key (after confirming that the public RSA MTProto key of the CDN DC matches one from the list returned in help.getCdnConfig). Then the client must perform an upload.getCdnFile for each offset. For files of an unknown size it is necessary to repeat the query until an empty reply is returned.

-

upload.getCdnFile may return the upload.cdnFileReuploadNeeded constructor. In this case, the client needs to send an upload.reuploadCdnFile request to the DC that got the original upload.getFile request. Once upload.reuploadCdnFile is successfull, the app needs to request the file from the CDN DC again.

-

The main DC for a file is the DC where its main copy is stored (not to be confused with the main DC of the user) – either userProfilePhoto.dc_id, chatPhoto.dc_id, photo.dc_id, or document.dc_id.

-

Decrypting files

-

In upload.fileCdnRedirect, the server sends a decryption key and IV for the file (the fields encryption_key:bytes and encryption_iv:bytes respectively).

-

Having received a portion of encrypted data from the CDN DC inside upload.cdnFile, the client must decrypt this data using AES-256-CTR. For IV, it should use the value of encryption_iv, modified in the following manner: for each offset replace the last 4 bytes of the encryption_iv with offset / 16 in big-endian. This allows to effectively decrypt a file and to use random access to a file's content (e.g., for streaming).

-

Verifying files

-

In order to confirm that the CDN DC passed an untampered file, clients must verify hashes for each downloaded part. upload.fileCdnRedirect, upload.reuploadCdnFile and upload.getCdnFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

-

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

-

Schema

-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
-
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
-
-upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
-
-
-dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
-
-cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
-
-
-cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
-
----functions---
-
-// CDN DC
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
-
-// Master DC
-upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
-upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
-
-help.getCdnConfig#52029342 = CdnConfig;
-

Restrictions on upload.getFile and upload.getCdnFile parameters

-
    -
  • offset must be divisible by 4096 bytes
  • -
  • limit must be divisible by 4096 bytes
  • -
  • 1048576 (1MB) must be divisible by limit
  • -
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024)
    (file parts that are being downloaded must always be inside the same megabyte-sized fragment)
  • -
-

Possible errors and their meanings

- - - - - - - - - - - - - - - - - - -
upload.getCdnFileFILE_TOKEN_INVALIDThe CDN DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileFILE_TOKEN_INVALIDThe master DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileREQUEST_TOKEN_INVALIDThe master DC did not accept the request_token from the CDN DC. Continue downloading the file from the master DC using upload.getFile.
-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/cdn/faq_ir.html b/data/core.telegram.org/cdn/faq_ir.html deleted file mode 100644 index 288c222a9e..0000000000 --- a/data/core.telegram.org/cdn/faq_ir.html +++ /dev/null @@ -1,142 +0,0 @@ - - - - - شبکه‌های تحویل محتوا (CDN) رمزنگاری شده - - - - - - - - - - - - - -
- -
-
-
-
-

شبکه‌های تحویل محتوا (CDN) رمزنگاری شده

- -
- - -

از نسخهٔ ۴.۲ تلگرام ما از CDN رمزنگاری شده برای ذخیره فایل‌های کانال های عمومی با بیش از ۱۰۰٫۰۰۰ عضو پشتیبانی می‌کنیم. نقاط ذخیره سازی CDN در مناطقی در نظر گرفته شده اند که تلگرام ترافیک زیادی دارد ولی ما به دلایل مختلف تمایلی به قرارگیری سرورهای تلگرام در آن مناطق نداریم.

-
-

برای اطلاعات فنی در خصوص نحوه پیاده سازی، رمزنگاری و تایید اعتبار داده‌ها راهنمای CDN در این لینک را ببینید. همچنین برای توضیحات سیستم از طرف پاول دورُف به این پست مراجعه کنید.

-
-

سوال: چرا تصمیم به استفاده از CDN گرفتید؟

-

ما از سرور‌های توزیع شده خود برای افزایش سرعت دانلود در مناطق بدون سانسور که در آنها آزادی بیان تضمین شده‌است استفاده می‌کنیم. و حتی در آن مناطق نیز به آنها اعتماد نمی‌کنیم. اما وقتی تلگرام در مناطق دیگر به شدت محبوب می‌شود، فقط می‌توانیم روی CDNها تکیه کنیم؛ که با آنها از نقطه نظر فنی مانند سرویس‌دهنده‌‌های اینترنت (ISP) رفتار می‌کنیم و آنها فقط داده‌های رمزنگاری شده‌ای را که قادر به کشف رمز آن نیستند دریافت می‌کنند.
به لطف این فناوری، سرعت دانلود عکس‌ها و فیلم‌هایی که به صورت عمومی منتشر می‌شوند در مناطقی نظیر ترکیه، اندونزی،‌ عربستان سعودی، هند، ایران و عراق به مراتب افزایش می‌یابد، بدون اینکه کمترین خدشه‌ای به امنیت وارد شود.

-

سوال: آیا CDN می‌تواند فایل‌ها را رمزگشایی کند؟

-

خیر. هر فایلی که به مراکز داده CDN ارسال می‌شود، با یک کلید منحصر به فرد با استفاده از تکنولوژی AES-256-CTR رمزگذاری می‌شود. CDN دسترسی به اطلاعاتی که ذخیره می‌کند ندارد، چرا که این کلید‌ها تنها در سرور MTProto (سرور رمزگذاری) اصلی و دستگاه کاربر قابل دسترسی هستند.

-

سوال: آیا CDNها می‌توانند اطلاعات را با اطلاعات دلخواه خودشان جایگزین کنند؟

-

خیر. اطلاعات و داده‌های دانلود شده (دریافتی)‌ از سمت نقاط ذخیره سازی CDN همیشه از طرف Telegram بوسیله رمزنگاری hash تایید و بررسی می‌شود: بدين ترتیب هکرها یا افراد متجاوز نمی‌توانند هیچ فایلی را جایگزین کنند.

-

سوال: آيا CDN مى‌تواند هر نوع فايل را حذف كند؟

-

خير. CDNها فقط كپى‌ فايل هاى رمزنگارى شده را ذخيره مى‌كنند، فايل‌هاى اصلي در سرورهای تلگرام ذخيره مى‌شوند. كاربر تنها اعلان دريافت فايل را از طريق سرور تلگرام مى‌گيرد. اگر كه CDN فايل مورد نظر را به كاربر ارسال نكند، كاربر اين فايل را مستقيماً از سرور تلگرام دريافت خواهد كرد.

-

سوال: آيا CDN ها مى توانند برای سانسور استفاده بشوند؟

-

خير. تمامى فايل‌هاى اصلي در سرورهای تلگرام ذخيره مى‌شوند. CDN ها فقط داده هاى رمزگذاري شده را دريافت مى‌كنند و قادر نيستند آن را رمزگشايى و يا هيچ گونه داده را جايگزين كنند. اگر مشكلى پيش آيد، فايل مورد نظر مستقيما از سرور هاى تلگرام به كاربران ارسال می‌شود. كاربران هميشه داده هایشان را دريافت مى‌كنند و هيچ كس نمى‌تواند مانع آنها بشود.

-

سوال: آیا می‌توانم این موضوع را بررسی کنم؟

-

بله. همه می‌توانند روش ما برای پیاده‌سازی CDN را با بررسی کد‌های Source Code برنامه‌های تلگرام و بررسی ترافیک داده بررسی کنند.

-

سوال: آیا این شامل اطلاعات خصوصی هم می‌شود؟

-

خیر. نقاط ذخیره سازی CDN بخشی از سرور اَبری تلگرام نیستند. CDNها فقط برای ذخیره‌سازی فایل‌های پر طرفدار از کانال‌های پر بازدید استفاده می‌شوند. اطلاعات خصوصی و شخصی هرگز به آنها راه پیدا نمی‌کنند.

-

سوال: آیا این با درخواست‌های دولت‌ها برای انتقال اطلاعات خصوصی به قلمرو آن‌ها مرتبط هست؟

-

خیر. ما وارد هیچ توافق یا تفاهمی با دولت‌ها در این مورد نشده‌ایم و CDNها بخشی از هیچ معامله‌ای نیستند. این به دلیل غیر منطقی بودن قوانین محلی نیست – ما هیچ‌گاه سرورهایمان را به کشوری با سابقه سانسور اینترنتی انتقال نمی‌دهیم.

-

تنها هدف استفاده از CDNها این است که کیفیت اتصال در مناطق با تقاضای بالا، که تلگرام نمی‌تواند سرورهای خود را به آنجا منتقل کند، با روشی ایمن، افزایش یابد.

-

سوال: آیا این موضوع می‌تواند به برخی کشورها، قدرت تسلط بر تلگرام بدهد؟

-

خیر. ما احتیاط ویژه‌ای به خرج داده‌ایم تا مطمئن شویم هیچ کشوری از طریق نقاط ذخیره سازی CDN به قدرت نفوذ روی تلگرام دست نیابد:
- CDNها و نقاط آن به تلگرام تعلق نداشته و همه ریسک آن به گردن شرکت ثالثی که نقاط ذخیره سازی CDN در سراسر دنیا را برای ما تامین می‌کند خواهد بود.
- ما هیچ سرمایه‌گذاری‌ای روی این CDNها انجام نمی‌دهیم و تنها بابت ترافیک مصرفی برای انتقال موارد ذخیره شده از خوشهٔ کامپیوترهای اصلی خودمان به کاربر نهایی، هزینه پرداخت می‌کنیم.

-

در نتیجه، اگر کشوری تصمیم به دستکاری CDN در منطقه خودش بگیرد، به چیزی جز پایین آوردن کیفیت اتصال شهروندان خودشان دست نمی‌یابد – و تلگرام هیچ چیز با ارزشی را از دست نخواهد داد.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/cdn/faq_ir/durov.html b/data/core.telegram.org/cdn/faq_ir/durov.html deleted file mode 100644 index 4db4f4fe7d..0000000000 --- a/data/core.telegram.org/cdn/faq_ir/durov.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - توضيحات CDNهاى رمزنگارى شده - - - - - - - - - - - - - -
- -
-
-
-
-

توضيحات CDNهاى رمزنگارى شده

- -
- -
-

ترجمه فارسى اين پست از كانال رسمى پاول دورُف در تلگرام در زير آمده است:

-
-

همانطور که پیشتر قول داده بودم، جزئیات بیشتری درباره اینکه چطور نقاط ذخیره سازی CDN ثالث می‌توانند سرعت دانلود محتوای عمومیِ پربازدید را در مناطقی که تلگرام تمایل به نصب سرورهای خود در آنجا ندارد، به روشی امن بالا ببرد، منتشر می‌کنم.

- -

همانطور که مشاهده می‌کنید، نقاط ذخیره سازی CDN هیچ ارتباطی با مساله انتقال سرورهای تلگرام یا رعایت قوانین غیر منطقی محلی ندارند. CDNها صرفا ابزاری جهت ارتقا کیفیت اتصال میلیون‌ها کاربر، به روشی امن، هستند. ما با این نقاط CDN دقیقا همانطور رفتار می‌کنیم که با مراکز تامین کننده اینترنت (ISP) شما رفتار می‌کنیم. آنها صرفا مشتی دادهٔ رمزنگاری شده دریافت می‌کنند که قادر به کشف رمز آن نخواهند بود.

-

خوبی تلگرام این است که وقتی بحث امنیت مطرح می‌شود، لازم نیست صرفا روی گفته‌های من حساب کنید. هر کسی می‌تواند نحوه اجرای نقاط CDN در نسخه بروز شده تلگرام برای iOS و اندروید را بررسی کند. همچنین اگر تمایل داشته‌باشید می‌توانید نگاهی به اسناد ما در لینک فوق بیندازید، تا مطمئن شوید همه چیز امن است.

-

ما با یک تامین کننده بین‌المللی CDN همکاری می‌کنیم که با نقاط ذخیره سازی خود در سراسر دنیا به ما کمک می‌کند. اگر یک دولت محلی تصمیم به توقیف یک نقطه ذخیره سازی در مرزهای خود بگیرد، تلگرام چیزی از دست نخواهد داد؛ چرا که آن CDN جز اموال ما نیست و حتی در تئوری کوچکترین اطلاعات خصوصی تحت تاثیر این عمل قرار نخواهد گرفت. بنابراین به قوانین و دولت‌های محلی وابستگی پیدا نمی‌کنیم و هیچ ریسک حقوقی یا مالی نخواهیم داشت، اما سرعت دانلود محتوای عمومی را بطور چشمگیری افزایش می‌دهیم.

-

چنانچه، با وجود توضیحات فوق، باز هم برخی رسانه‌ها از تیتر های جنجالی مانند «تلگرام سرورهایش را به کره شمالی انتقال داد» استفاده کردند، لطفا مارا با اطلاع رسانی در مورد حقیقت ماجرا که در لینک‌های این پیام آمده است، یاری کنید. بابت مطالعه این مطلب از شما تشکر می‌کنم و مثل همیشه، در همین کانال، شما را از هر خبر بین المللی در مورد تلگرام مطلع خواهم کرد.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.authorizationForm b/data/core.telegram.org/constructor/account.authorizationForm deleted file mode 100644 index 5e691638c4..0000000000 --- a/data/core.telegram.org/constructor/account.authorizationForm +++ /dev/null @@ -1,174 +0,0 @@ - - - - - account.authorizationForm - - - - - - - - - - - - - -
- -
-
-
- -

account.authorizationForm

- -

Telegram Passport authorization form

-

-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
required_typesVector<SecureRequiredType>Required Telegram Passport documents
valuesVector<SecureValue>Already submitted Telegram Passport documents
errorsVector<SecureValueError>Telegram Passport errors
usersVector<User>Info about the bot to which the form will be submitted
privacy_policy_urlflags.0?stringURL of the service's privacy policy
-

Type

-

account.AuthorizationForm

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.authorizations b/data/core.telegram.org/constructor/account.authorizations deleted file mode 100644 index a8366528f3..0000000000 --- a/data/core.telegram.org/constructor/account.authorizations +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.authorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.authorizations

- -

Logged-in sessions

-

-
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
authorizationsVector<Authorization>Logged-in sessions
-

Type

-

account.Authorizations

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.autoDownloadSettings b/data/core.telegram.org/constructor/account.autoDownloadSettings deleted file mode 100644 index 2d1e589682..0000000000 --- a/data/core.telegram.org/constructor/account.autoDownloadSettings +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.autoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.autoDownloadSettings

- -

Media autodownload settings

-

-
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lowAutoDownloadSettingsLow data usage preset
mediumAutoDownloadSettingsMedium data usage preset
highAutoDownloadSettingsHigh data usage preset
-

Type

-

account.AutoDownloadSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.contentSettings b/data/core.telegram.org/constructor/account.contentSettings deleted file mode 100644 index 7bcc0e5edf..0000000000 --- a/data/core.telegram.org/constructor/account.contentSettings +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.contentSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.contentSettings

- -

Sensitive content settings

-

-
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueWhether viewing of sensitive (NSFW) content is enabled
sensitive_can_changeflags.1?trueWhether the current client can change the sensitive content settings to view NSFW content
-

Type

-

account.ContentSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.password b/data/core.telegram.org/constructor/account.password deleted file mode 100644 index ab2814775f..0000000000 --- a/data/core.telegram.org/constructor/account.password +++ /dev/null @@ -1,208 +0,0 @@ - - - - - account.password - - - - - - - - - - - - - -
- -
-
-
- -

account.password

- -

Configuration for two-factor authorization

-

-
account.password#ad2641f8 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 = 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
-

Type

-

account.Password

-

Related pages

-

Telegram Passport Manual

-

Two-factor authentication

-

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

-

Pattern matching

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.passwordInputSettings b/data/core.telegram.org/constructor/account.passwordInputSettings deleted file mode 100644 index 1c243493ab..0000000000 --- a/data/core.telegram.org/constructor/account.passwordInputSettings +++ /dev/null @@ -1,176 +0,0 @@ - - - - - account.passwordInputSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.passwordInputSettings

- -

Settings for setting up a new password

-

-
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
new_algoflags.0?PasswordKdfAlgoThe SRP algorithm to use
new_password_hashflags.0?bytesThe computed password hash
hintflags.0?stringText hint for the password
emailflags.1?stringPassword recovery email
new_secure_settingsflags.2?SecureSecretSettingsTelegram passport settings
-

Type

-

account.PasswordInputSettings

-

Related pages

-

Two-factor authentication

-

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

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.passwordSettings b/data/core.telegram.org/constructor/account.passwordSettings deleted file mode 100644 index 81cba281d2..0000000000 --- a/data/core.telegram.org/constructor/account.passwordSettings +++ /dev/null @@ -1,161 +0,0 @@ - - - - - account.passwordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.passwordSettings

- -

Private info associated to the password info (recovery email, telegram passport info & so on)

-

-
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
emailflags.0?string2FA Recovery email
secure_settingsflags.1?SecureSecretSettingsTelegram passport settings
-

Type

-

account.PasswordSettings

-

Related pages

-

Two-factor authentication

-

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

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.privacyRules b/data/core.telegram.org/constructor/account.privacyRules deleted file mode 100644 index ba339e86d8..0000000000 --- a/data/core.telegram.org/constructor/account.privacyRules +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.privacyRules - - - - - - - - - - - - - -
- -
-
-
- -

account.privacyRules

- -

Privacy rules

-

-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
rulesVector<PrivacyRule>Privacy rules
chatsVector<Chat>Chats to which the rules apply
usersVector<User>Users to which the rules apply
-

Type

-

account.PrivacyRules

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.sentChangePhoneCode b/data/core.telegram.org/constructor/account.sentChangePhoneCode deleted file mode 100644 index 5f981a22dc..0000000000 --- a/data/core.telegram.org/constructor/account.sentChangePhoneCode +++ /dev/null @@ -1,161 +0,0 @@ - - - - - account.sentChangePhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sentChangePhoneCode

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.sentEmailCode b/data/core.telegram.org/constructor/account.sentEmailCode deleted file mode 100644 index 854b294fd0..0000000000 --- a/data/core.telegram.org/constructor/account.sentEmailCode +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.sentEmailCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sentEmailCode

- -

The sent email code

-

-
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
email_patternstringThe email (to which the code was sent) must match this pattern
lengthintThe length of the verification code
-

Type

-

account.SentEmailCode

-

Related pages

-

Pattern matching

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.takeout b/data/core.telegram.org/constructor/account.takeout deleted file mode 100644 index 802cfb3326..0000000000 --- a/data/core.telegram.org/constructor/account.takeout +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.takeout - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.themes b/data/core.telegram.org/constructor/account.themes deleted file mode 100644 index bad55380a1..0000000000 --- a/data/core.telegram.org/constructor/account.themes +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.themes - - - - - - - - - - - - - -
- -
-
-
- -

account.themes

- -

Installed themes

-

-
account.themes#7f676421 hash:int themes:Vector<Theme> = account.Themes;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
themesVector<Theme>Themes
-

Type

-

account.Themes

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.themesNotModified b/data/core.telegram.org/constructor/account.themesNotModified deleted file mode 100644 index 525f64b26b..0000000000 --- a/data/core.telegram.org/constructor/account.themesNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.themesNotModified - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.tmpPassword b/data/core.telegram.org/constructor/account.tmpPassword deleted file mode 100644 index bb79d741c8..0000000000 --- a/data/core.telegram.org/constructor/account.tmpPassword +++ /dev/null @@ -1,152 +0,0 @@ - - - - - account.tmpPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.tmpPassword

- -

Temporary payment password

-

-
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
tmp_passwordbytesTemporary password
valid_untilintValidity period
-

Type

-

account.TmpPassword

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.wallPapers b/data/core.telegram.org/constructor/account.wallPapers deleted file mode 100644 index 898dc30e3c..0000000000 --- a/data/core.telegram.org/constructor/account.wallPapers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.wallPapers - - - - - - - - - - - - - -
- -
-
-
- -

account.wallPapers

- -

Installed wallpapers

-

-
account.wallPapers#702b65a9 hash:int wallpapers:Vector<WallPaper> = account.WallPapers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
wallpapersVector<WallPaper>Wallpapers
-

Type

-

account.WallPapers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.wallPapersNotModified b/data/core.telegram.org/constructor/account.wallPapersNotModified deleted file mode 100644 index 2ee4467b9f..0000000000 --- a/data/core.telegram.org/constructor/account.wallPapersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.wallPapersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

account.wallPapersNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.webAuthorizations b/data/core.telegram.org/constructor/account.webAuthorizations deleted file mode 100644 index 16ba6f99a9..0000000000 --- a/data/core.telegram.org/constructor/account.webAuthorizations +++ /dev/null @@ -1,152 +0,0 @@ - - - - - account.webAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.webAuthorizations

- -

Web authorizations

-

-
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
authorizationsVector<WebAuthorization>Web authorization list
usersVector<User>Users
-

Type

-

account.WebAuthorizations

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/accountDaysTTL.html b/data/core.telegram.org/constructor/accountDaysTTL.html deleted file mode 100644 index 11f289125a..0000000000 --- a/data/core.telegram.org/constructor/accountDaysTTL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - accountDaysTTL - - - - - - - - - - - - - -
- -
-
-
- -

accountDaysTTL

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.authorization b/data/core.telegram.org/constructor/auth.authorization deleted file mode 100644 index 2e09059f36..0000000000 --- a/data/core.telegram.org/constructor/auth.authorization +++ /dev/null @@ -1,159 +0,0 @@ - - - - - auth.authorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.authorization

- -

Contains user authorization info.

-

-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
tmp_sessionsflags.0?intTemporary passport sessions
userUserInfo on authorized user
-

Type

-

auth.Authorization

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.authorizationSignUpRequired b/data/core.telegram.org/constructor/auth.authorizationSignUpRequired deleted file mode 100644 index 5dd5ec25a8..0000000000 --- a/data/core.telegram.org/constructor/auth.authorizationSignUpRequired +++ /dev/null @@ -1,155 +0,0 @@ - - - - - auth.authorizationSignUpRequired - - - - - - - - - - - - - -
- -
-
-
- -

auth.authorizationSignUpRequired

- -

An account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up

-

-
auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
terms_of_serviceflags.0?help.TermsOfServiceTelegram's terms of service: the user must read and accept the terms of service before signing up to telegram
-

Type

-

auth.Authorization

-

Related pages

-

User Authorization

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.codeTypeCall b/data/core.telegram.org/constructor/auth.codeTypeCall deleted file mode 100644 index 02ad30bc18..0000000000 --- a/data/core.telegram.org/constructor/auth.codeTypeCall +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeCall

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.codeTypeFlashCall b/data/core.telegram.org/constructor/auth.codeTypeFlashCall deleted file mode 100644 index 9cbbaa2a71..0000000000 --- a/data/core.telegram.org/constructor/auth.codeTypeFlashCall +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeFlashCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeFlashCall

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.codeTypeSms b/data/core.telegram.org/constructor/auth.codeTypeSms deleted file mode 100644 index 807262aadb..0000000000 --- a/data/core.telegram.org/constructor/auth.codeTypeSms +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeSms - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeSms

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.exportedAuthorization b/data/core.telegram.org/constructor/auth.exportedAuthorization deleted file mode 100644 index 23a2293ef9..0000000000 --- a/data/core.telegram.org/constructor/auth.exportedAuthorization +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.exportedAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.exportedAuthorization

- -

Data for copying of authorization between data centres.

-

-
auth.exportedAuthorization#df969c2d id:int bytes:bytes = auth.ExportedAuthorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintcurrent user identifier
bytesbytesauthorizes key
-

Type

-

auth.ExportedAuthorization

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.loginToken b/data/core.telegram.org/constructor/auth.loginToken deleted file mode 100644 index 668fa6be34..0000000000 --- a/data/core.telegram.org/constructor/auth.loginToken +++ /dev/null @@ -1,155 +0,0 @@ - - - - - auth.loginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.loginToken

- -

Login token (for QR code login)

-

-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
expiresintExpiry date of QR code
tokenbytesToken to render in QR code
-

Type

-

auth.LoginToken

-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.loginTokenMigrateTo b/data/core.telegram.org/constructor/auth.loginTokenMigrateTo deleted file mode 100644 index 4582abc3ab..0000000000 --- a/data/core.telegram.org/constructor/auth.loginTokenMigrateTo +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.loginTokenMigrateTo - - - - - - - - - - - - - -
- -
-
-
- -

auth.loginTokenMigrateTo

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.loginTokenSuccess b/data/core.telegram.org/constructor/auth.loginTokenSuccess deleted file mode 100644 index c6ce95ee3a..0000000000 --- a/data/core.telegram.org/constructor/auth.loginTokenSuccess +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.loginTokenSuccess - - - - - - - - - - - - - -
- -
-
-
- -

auth.loginTokenSuccess

- -

Login via token (QR code) succeded!

-

-
auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
authorizationauth.AuthorizationAuthorization info
-

Type

-

auth.LoginToken

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.passwordRecovery b/data/core.telegram.org/constructor/auth.passwordRecovery deleted file mode 100644 index 4fa316772a..0000000000 --- a/data/core.telegram.org/constructor/auth.passwordRecovery +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.passwordRecovery - - - - - - - - - - - - - -
- -
-
-
- -

auth.passwordRecovery

- -

Recovery info of a 2FA password, only for accounts with a recovery email configured.

-

-
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
email_patternstringThe email to which the recovery code was sent must match this pattern.
-

Type

-

auth.PasswordRecovery

-

Related pages

-

Pattern matching

-

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

-

Two-factor authentication

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentAppCode b/data/core.telegram.org/constructor/auth.sentAppCode deleted file mode 100644 index 631be2127d..0000000000 --- a/data/core.telegram.org/constructor/auth.sentAppCode +++ /dev/null @@ -1,163 +0,0 @@ - - - - - auth.sentAppCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentAppCode

- -

Contains info on a confirmation code message sent via Telegram.

-

You can force resending the message via SMS by invoking the method auth.sendSms.

-

-
Constructor schema is available as of layer 50. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_registeredBoolThe given number corresponds to a registered Telegram user
phone_code_hashstringMessage identifier
send_call_timeoutintDelay in seconds before calling auth.sendCall
is_passwordBoolThe sent code is a text password
-

Type

-

auth.SentCode

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCode b/data/core.telegram.org/constructor/auth.sentCode deleted file mode 100644 index ed8f48d14d..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCode +++ /dev/null @@ -1,172 +0,0 @@ - - - - - auth.sentCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCode

- -

Contains info about a sent verification code.

-

-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;

-

Parameters

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

Type

-

auth.SentCode

-

Related pages

-

auth.signIn

-

Signs in a user with a validated phone number.

-

auth.resendCode

-

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeApp b/data/core.telegram.org/constructor/auth.sentCodeTypeApp deleted file mode 100644 index 79ae3f2c22..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCodeTypeApp +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.sentCodeTypeApp - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeApp

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeCall b/data/core.telegram.org/constructor/auth.sentCodeTypeCall deleted file mode 100644 index 041167b080..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCodeTypeCall +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.sentCodeTypeCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeCall

- -

The code will be sent via a phone call: a synthesized voice will tell the user which verification code to input.

-

-
auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lengthintLength of the verification code
-

Type

-

auth.SentCodeType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall b/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall deleted file mode 100644 index 2eb2e61508..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall +++ /dev/null @@ -1,150 +0,0 @@ - - - - - auth.sentCodeTypeFlashCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeFlashCall

- -

The code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.

-

-
auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
patternstringpattern to match
-

Type

-

auth.SentCodeType

-

Related pages

-

Pattern matching

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeSms b/data/core.telegram.org/constructor/auth.sentCodeTypeSms deleted file mode 100644 index 8123d72cbb..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCodeTypeSms +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.sentCodeTypeSms - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeSms

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/authorization.html b/data/core.telegram.org/constructor/authorization.html deleted file mode 100644 index 12e5bd7ac6..0000000000 --- a/data/core.telegram.org/constructor/authorization.html +++ /dev/null @@ -1,225 +0,0 @@ - - - - - authorization - - - - - - - - - - - - - -
- -
-
-
- -

authorization

- -

Logged-in session

-

-
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
currentflags.0?trueWhether this is the current session
official_appflags.1?trueWhether the session is from an official app
password_pendingflags.2?trueWhether the session is still waiting for a 2FA password
hashlongIdentifier
device_modelstringDevice model
platformstringPlatform
system_versionstringSystem version
api_idintAPI ID
app_namestringApp name
app_versionstringApp version
date_createdintWhen was the session created
date_activeintWhen was the session last active
ipstringLast known IP
countrystringCountry determined from IP
regionstringRegion determined from IP
-

Type

-

Authorization

-

Related pages

-

Creating your Telegram Application

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/autoDownloadSettings.html b/data/core.telegram.org/constructor/autoDownloadSettings.html deleted file mode 100644 index 9365406844..0000000000 --- a/data/core.telegram.org/constructor/autoDownloadSettings.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - autoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

autoDownloadSettings

- -

Autodownload settings

-

-
autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
disabledflags.0?trueDisable automatic media downloads?
video_preload_largeflags.1?trueWhether to preload the first seconds of videos larger than the specified limit
audio_preload_nextflags.2?trueWhether to preload the next audio track when you're listening to music
phonecalls_less_dataflags.3?trueWhether to enable data saving mode in phone calls
photo_size_maxintMaximum size of photos to preload
video_size_maxintMaximum size of videos to preload
file_size_maxintMaximum size of other files to preload
video_upload_maxbitrateintMaximum suggested bitrate for uploading videos
-

Type

-

AutoDownloadSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/bankCardOpenUrl.html b/data/core.telegram.org/constructor/bankCardOpenUrl.html deleted file mode 100644 index 1b2c15974a..0000000000 --- a/data/core.telegram.org/constructor/bankCardOpenUrl.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - bankCardOpenUrl - - - - - - - - - - - - - -
- -
-
-
- -

bankCardOpenUrl

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeArctic.html b/data/core.telegram.org/constructor/baseThemeArctic.html deleted file mode 100644 index a66f40b8fd..0000000000 --- a/data/core.telegram.org/constructor/baseThemeArctic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeArctic - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeClassic.html b/data/core.telegram.org/constructor/baseThemeClassic.html deleted file mode 100644 index b16ada4c20..0000000000 --- a/data/core.telegram.org/constructor/baseThemeClassic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeClassic - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeDay.html b/data/core.telegram.org/constructor/baseThemeDay.html deleted file mode 100644 index 448b90268e..0000000000 --- a/data/core.telegram.org/constructor/baseThemeDay.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeDay - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeNight.html b/data/core.telegram.org/constructor/baseThemeNight.html deleted file mode 100644 index a36b8ef06e..0000000000 --- a/data/core.telegram.org/constructor/baseThemeNight.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeNight - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeTinted.html b/data/core.telegram.org/constructor/baseThemeTinted.html deleted file mode 100644 index 08c3fbad53..0000000000 --- a/data/core.telegram.org/constructor/baseThemeTinted.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeTinted - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/boolFalse.html b/data/core.telegram.org/constructor/boolFalse.html deleted file mode 100644 index 2c5bbd76f0..0000000000 --- a/data/core.telegram.org/constructor/boolFalse.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - boolFalse - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/boolTrue.html b/data/core.telegram.org/constructor/boolTrue.html deleted file mode 100644 index 5eca498dbc..0000000000 --- a/data/core.telegram.org/constructor/boolTrue.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - boolTrue - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommand.html b/data/core.telegram.org/constructor/botCommand.html deleted file mode 100644 index 685b932fcf..0000000000 --- a/data/core.telegram.org/constructor/botCommand.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - botCommand - - - - - - - - - - - - - -
- -
-
-
- -

botCommand

- -

Describes a bot command that can be used in a chat

-

-
botCommand#c27ac8c7 command:string description:string = BotCommand;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
commandstring/command name
descriptionstringDescription of the command
-

Type

-

BotCommand

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInfo.html b/data/core.telegram.org/constructor/botInfo.html deleted file mode 100644 index 97ca7abee0..0000000000 --- a/data/core.telegram.org/constructor/botInfo.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - botInfo - - - - - - - - - - - - - -
- -
-
-
- -

botInfo

- -

Info about bots (available bot commands, etc)

-

-
botInfo#98e81d3a user_id:int description:string commands:Vector<BotCommand> = BotInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintID of the bot
descriptionstringDescription of the bot
commandsVector<BotCommand>Bot commands that can be used in the chat
-

Type

-

BotInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMediaResult.html b/data/core.telegram.org/constructor/botInlineMediaResult.html deleted file mode 100644 index d671c44dbd..0000000000 --- a/data/core.telegram.org/constructor/botInlineMediaResult.html +++ /dev/null @@ -1,186 +0,0 @@ - - - - - botInlineMediaResult - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMediaResult

- -

Media result

-

-
botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
photoflags.0?PhotoIf type is photo, the photo to send
documentflags.1?DocumentIf type is document, the document to send
titleflags.2?stringResult title
descriptionflags.3?stringDescription
send_messageBotInlineMessageDepending on the type and on the constructor, contains the caption of the media or the content of the message to be sent instead of the media
-

Type

-

BotInlineResult

-

Related pages

-

Telegram Bot API

-

BotInlineMessage

-

Inline message

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html b/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html deleted file mode 100644 index 79e0486389..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - botInlineMessageMediaAuto - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaAuto

- -

Send whatever media is attached to the botInlineMediaResult

-

-
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

botInlineMediaResult

-

Media result

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaContact.html b/data/core.telegram.org/constructor/botInlineMessageMediaContact.html deleted file mode 100644 index 95e9948494..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaContact.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - botInlineMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaContact

- -

Send a contact

-

-
botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html b/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html deleted file mode 100644 index 0f4a395192..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - botInlineMessageMediaGeo - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaGeo

- -

Send a geolocation

-

-
botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360.
periodflags.1?intValidity period
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000).
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Live geolocation

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html b/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html deleted file mode 100644 index 9df1322e13..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - botInlineMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaVenue

- -

Send a venue

-

-
botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageText.html b/data/core.telegram.org/constructor/botInlineMessageText.html deleted file mode 100644 index 44c585d8be..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageText.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - botInlineMessageText - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageText

- -

Send a simple text message

-

-
botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringThe message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineResult.html b/data/core.telegram.org/constructor/botInlineResult.html deleted file mode 100644 index c47f13cc64..0000000000 --- a/data/core.telegram.org/constructor/botInlineResult.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - botInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

botInlineResult

- -

Generic result

-

-
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of article or webpage
thumbflags.4?WebDocumentThumbnail for the result
contentflags.5?WebDocumentContent of the result
send_messageBotInlineMessageMessage to send
-

Type

-

BotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/cdnConfig.html b/data/core.telegram.org/constructor/cdnConfig.html deleted file mode 100644 index a370928748..0000000000 --- a/data/core.telegram.org/constructor/cdnConfig.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - cdnConfig - - - - - - - - - - - - - -
- -
-
-
- -

cdnConfig

- -

Configuration for CDN file downloads.

-

-
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
public_keysVector<CdnPublicKey>Vector of public keys to use only during handshakes to CDN DCs.
-

Type

-

CdnConfig

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/cdnPublicKey.html b/data/core.telegram.org/constructor/cdnPublicKey.html deleted file mode 100644 index f7bc68012b..0000000000 --- a/data/core.telegram.org/constructor/cdnPublicKey.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - cdnPublicKey - - - - - - - - - - - - - -
- -
-
-
- -

cdnPublicKey

- -

Public key to use only during handshakes to CDN DCs.

-

-
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintCDN DC ID
public_keystringRSA public key
-

Type

-

CdnPublicKey

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channel.html b/data/core.telegram.org/constructor/channel.html deleted file mode 100644 index 19dab5153e..0000000000 --- a/data/core.telegram.org/constructor/channel.html +++ /dev/null @@ -1,272 +0,0 @@ - - - - - channel - - - - - - - - - - - - - -
- -
-
-
- -

channel

- -

Channel/supergroup info

-

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

-

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
idintID 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
versionintVersion of the channel (always 0)
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.

-

Admin, banned, default rights

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEvent.html b/data/core.telegram.org/constructor/channelAdminLogEvent.html deleted file mode 100644 index 8d2bef4a24..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEvent.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - channelAdminLogEvent - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEvent

- -

Admin log event

-

-
channelAdminLogEvent#3b5a3e40 id:long date:int user_id:int action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongEvent ID
dateintDate
user_idintUser ID
actionChannelAdminLogEventActionAction
-

Type

-

ChannelAdminLogEvent

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html deleted file mode 100644 index 6829beeb74..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeAbout - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeAbout

- -

The description was changed

-

-
channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringPrevious description
new_valuestringNew description
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html deleted file mode 100644 index df924edc89..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeLinkedChat - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeLinkedChat

- -

The linked chat was changed

-

-
channelAdminLogEventActionChangeLinkedChat#a26f881b prev_value:int new_value:int = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueintPrevious linked chat
new_valueintNew linked chat
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html deleted file mode 100644 index 5184e025d7..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeLocation - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeLocation

- -

The geogroup location was changed

-

-
channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueChannelLocationPrevious location
new_valueChannelLocationNew location
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html deleted file mode 100644 index e60839a5f6..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangePhoto - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangePhoto

- -

The channel/supergroup's picture was changed

-

-
channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_photoPhotoPrevious picture
new_photoPhotoNew picture
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html deleted file mode 100644 index f194bf6a5a..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeStickerSet

- -

The supergroup's stickerset was changed

-

-
channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_stickersetInputStickerSetPrevious stickerset
new_stickersetInputStickerSetNew stickerset
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html deleted file mode 100644 index 81300abd70..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeTitle - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeTitle

- -

Channel/supergroup title was changed

-

-
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringPrevious title
new_valuestringNew title
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html deleted file mode 100644 index 19e1c9c5b2..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeUsername - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeUsername

- -

Channel/supergroup username was changed

-

-
channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringOld username
new_valuestringNew username
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html b/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html deleted file mode 100644 index 9924cad4ae..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionDefaultBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionDefaultBannedRights

- -

The default banned rights were modified

-

-
channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_banned_rightsChatBannedRightsPrevious global banned rights
new_banned_rightsChatBannedRightsNew glboal banned rights.
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html b/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html deleted file mode 100644 index 9df70f8568..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionDeleteMessage - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionDeleteMessage

- -

A message was deleted

-

-
channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe message that was deleted
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html b/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html deleted file mode 100644 index afddb693f8..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionEditMessage - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionEditMessage

- -

A message was edited

-

-
channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_messageMessageOld message
new_messageMessageNew message
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html deleted file mode 100644 index a63b19e9ab..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionParticipantInvite - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantInvite

- -

A user was invited to the group

-

-
channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantChannelParticipantThe user that was invited
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html deleted file mode 100644 index 7cfc106df2..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelAdminLogEventActionParticipantJoin - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantJoin

- -

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

-

-
channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html deleted file mode 100644 index f18080610f..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelAdminLogEventActionParticipantLeave - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantLeave

- -

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

-

-
channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html deleted file mode 100644 index d4661050c5..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionParticipantToggleAdmin - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantToggleAdmin

- -

The admin rights of a user were changed

-

-
channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_participantChannelParticipantPrevious admin rights
new_participantChannelParticipantNew admin rights
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html deleted file mode 100644 index 233cb8e381..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionParticipantToggleBan - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantToggleBan

- -

The banned rights of a user were changed

-

-
channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_participantChannelParticipantOld banned rights of user
new_participantChannelParticipantNew banned rights of user
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html b/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html deleted file mode 100644 index 6e02ae5dcd..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionStopPoll - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionStopPoll

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html deleted file mode 100644 index 7256ba2dfa..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionToggleInvites - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleInvites

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html b/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html deleted file mode 100644 index a41742a4f9..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - channelAdminLogEventActionTogglePreHistoryHidden - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionTogglePreHistoryHidden

- -

The hidden prehistory setting was changed

-

-
channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
new_valueBoolNew value
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

channels.togglePreHistoryHidden

-

Hide/unhide message history for new channel/supergroup users

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html deleted file mode 100644 index 7b716aadb8..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionToggleSignatures - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleSignatures

- -

Channel signatures were enabled/disabled

-

-
channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
new_valueBoolNew value
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html deleted file mode 100644 index 6027ab610a..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionToggleSlowMode - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleSlowMode

- -

Slow mode setting for supergroups was changed

-

-
channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueintPrevious slow mode value
new_valueintNew slow mode value
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

channels.toggleSlowMode

-

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html b/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html deleted file mode 100644 index 48cc489efa..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionUpdatePinned - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionUpdatePinned

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html b/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html deleted file mode 100644 index 52db2ccc45..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html +++ /dev/null @@ -1,256 +0,0 @@ - - - - - channelAdminLogEventsFilter - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventsFilter

- -

Filter only certain admin log events

-

-
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true = 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
-

Type

-

ChannelAdminLogEventsFilter

-

Related pages

-

channelAdminLogEventActionParticipantJoin

-

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

-

channelAdminLogEventActionParticipantLeave

-

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

-

channelAdminLogEventActionParticipantInvite

-

A user was invited to the group

-

channelAdminLogEventActionParticipantToggleBan

-

The banned rights of a user were changed

-

channelAdminLogEventActionParticipantToggleAdmin

-

The admin rights of a user were changed

-

channelAdminLogEventActionChangeAbout

-

The description was changed

-

channelAdminLogEventActionChangeLinkedChat

-

The linked chat was changed

-

channelAdminLogEventActionChangeLocation

-

The geogroup location was changed

-

channelAdminLogEventActionChangePhoto

-

The channel/supergroup's picture was changed

-

channelAdminLogEventActionChangeStickerSet

-

The supergroup's stickerset was changed

-

channelAdminLogEventActionChangeTitle

-

Channel/supergroup title was changed

-

channelAdminLogEventActionChangeUsername

-

Channel/supergroup username was changed

-

channelAdminLogEventActionToggleInvites

-

Invites were enabled/disabled

-

channelAdminLogEventActionTogglePreHistoryHidden

-

The hidden prehistory setting was changed

-

channelAdminLogEventActionToggleSignatures

-

Channel signatures were enabled/disabled

-

channelAdminLogEventActionDefaultBannedRights

-

The default banned rights were modified

-

channelAdminLogEventActionUpdatePinned

-

A message was pinned

-

channelAdminLogEventActionEditMessage

-

A message was edited

-

channelAdminLogEventActionDeleteMessage

-

A message was deleted

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelForbidden.html b/data/core.telegram.org/constructor/channelForbidden.html deleted file mode 100644 index a8589dc915..0000000000 --- a/data/core.telegram.org/constructor/channelForbidden.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - channelForbidden - - - - - - - - - - - - - -
- -
-
-
- -

channelForbidden

- -

Indicates a channel/supergroup we can't access because we were banned, or for some other reason.

-

-
channelForbidden#289da732 flags:# broadcast:flags.5?true megagroup:flags.8?true id:int 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
idintChannel ID
access_hashlongAccess hash
titlestringTitle
until_dateflags.16?intThe ban is valid until the specified date
-

Type

-

Chat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelFull.html b/data/core.telegram.org/constructor/channelFull.html deleted file mode 100644 index cfa2b9d034..0000000000 --- a/data/core.telegram.org/constructor/channelFull.html +++ /dev/null @@ -1,334 +0,0 @@ - - - - - channelFull - - - - - - - - - - - - - -
- -
-
-
- -

channelFull

- -

Full info about a channel/supergroup

-

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

-

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
idintID 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_inviteExportedChatInviteInvite link
bot_infoVector<BotInfo>Info about bots in the channel/supergrup
migrated_from_chat_idflags.4?intThe 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?intID 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
-

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.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelLocation.html b/data/core.telegram.org/constructor/channelLocation.html deleted file mode 100644 index 899dbb9698..0000000000 --- a/data/core.telegram.org/constructor/channelLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelLocation - - - - - - - - - - - - - -
- -
-
-
- -

channelLocation

- -

Geographical location of supergroup (geogroups)

-

-
channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointGeoPointGeographical location of supergrup
addressstringTextual description of the address
-

Type

-

ChannelLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelLocationEmpty.html b/data/core.telegram.org/constructor/channelLocationEmpty.html deleted file mode 100644 index e8bd0931e7..0000000000 --- a/data/core.telegram.org/constructor/channelLocationEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelLocationEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelMessagesFilter.html b/data/core.telegram.org/constructor/channelMessagesFilter.html deleted file mode 100644 index b3d4b7a845..0000000000 --- a/data/core.telegram.org/constructor/channelMessagesFilter.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channelMessagesFilter - - - - - - - - - - - - - -
- -
-
-
- -

channelMessagesFilter

- -

Filter for getting only certain types of channel messages

-

-
channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_new_messagesflags.1?trueWhether to exclude new messages from the search
rangesVector<MessageRange>A range of messages to fetch
-

Type

-

ChannelMessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html b/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html deleted file mode 100644 index a4bcd21627..0000000000 --- a/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelMessagesFilterEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipant.html b/data/core.telegram.org/constructor/channelParticipant.html deleted file mode 100644 index 51fbbcac9b..0000000000 --- a/data/core.telegram.org/constructor/channelParticipant.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipant

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantAdmin.html b/data/core.telegram.org/constructor/channelParticipantAdmin.html deleted file mode 100644 index 4f03d82ef3..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantAdmin.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - channelParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantAdmin

- -

Admin

-

-
channelParticipantAdmin#ccbebbaf flags:# can_edit:flags.0?true self:flags.1?true user_id:int inviter_id:flags.1?int promoted_by:int 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_idintAdmin user ID
inviter_idflags.1?intUser that invited the admin to the channel/group
promoted_byintUser that promoted the user to admin
dateintWhen did the user join
admin_rightsChatAdminRightsAdmin rights
rankflags.2?stringThe role (rank) of the admin in the group: just an arbitrary string, admin by default
-

Type

-

ChannelParticipant

-

Related pages

-

Admin, banned, default rights

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantBanned.html b/data/core.telegram.org/constructor/channelParticipantBanned.html deleted file mode 100644 index 5df7493602..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantBanned.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - channelParticipantBanned - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantBanned

- -

Banned/kicked user

-

-
channelParticipantBanned#1c0facaf flags:# left:flags.0?true user_id:int kicked_by:int date:int banned_rights:ChatBannedRights = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
leftflags.0?trueWhether the user has left the group
user_idintUser ID
kicked_byintUser was kicked by the specified admin
dateintWhen did the user join the group
banned_rightsChatBannedRightsBanned rights
-

Type

-

ChannelParticipant

-

Related pages

-

Admin, banned, default rights

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantCreator.html b/data/core.telegram.org/constructor/channelParticipantCreator.html deleted file mode 100644 index c7c3ec2014..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantCreator.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - channelParticipantCreator - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantCreator

- -

Channel/supergroup creator

-

-
channelParticipantCreator#447dca4b flags:# user_id:int admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
user_idintUser ID
admin_rightsChatAdminRightsCreator admin rights
rankflags.0?stringThe role (rank) of the group creator in the group: just an arbitrary string, admin by default
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantLeft.html b/data/core.telegram.org/constructor/channelParticipantLeft.html deleted file mode 100644 index ae8d1baccf..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantLeft.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantLeft - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantLeft

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantSelf.html b/data/core.telegram.org/constructor/channelParticipantSelf.html deleted file mode 100644 index 58defa03e8..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantSelf.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channelParticipantSelf - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantSelf

- -

Myself

-

-
channelParticipantSelf#a3289a6d user_id:int inviter_id:int date:int = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser ID
inviter_idintUser that invited me to the channel/supergroup
dateintWhen did I join the channel/supergroup
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsAdmins.html b/data/core.telegram.org/constructor/channelParticipantsAdmins.html deleted file mode 100644 index bc981016c4..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsAdmins.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsAdmins - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsAdmins

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsBanned.html b/data/core.telegram.org/constructor/channelParticipantsBanned.html deleted file mode 100644 index 8d1abca9f1..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsBanned.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsBanned - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsBanned

- -

Fetch only banned participants

-

-
channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional filter for searching banned participants by name (otherwise empty)
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsBots.html b/data/core.telegram.org/constructor/channelParticipantsBots.html deleted file mode 100644 index 2bb6268a29..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsBots.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsBots - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsBots

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsContacts.html b/data/core.telegram.org/constructor/channelParticipantsContacts.html deleted file mode 100644 index ee374fb1ac..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsContacts.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsContacts - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsContacts

- -

Fetch only participants that are also contacts

-

-
channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional search query for searching contact participants by name
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsKicked.html b/data/core.telegram.org/constructor/channelParticipantsKicked.html deleted file mode 100644 index ce6b0157ae..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsKicked.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsKicked - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsKicked

- -

Fetch only kicked participants

-

-
channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional filter for searching kicked participants by name (otherwise empty)
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsMentions.html b/data/core.telegram.org/constructor/channelParticipantsMentions.html deleted file mode 100644 index 5c933055a5..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsMentions.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - channelParticipantsMentions - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsMentions

- -

This filter is used when looking for supergroup members to mention.
-This filter will automatically remove anonymous admins, and return even non-participant users that replied to a specific thread through the comment section of a channel.

-

-
channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
qflags.0?stringFilter by user name or username
top_msg_idflags.1?intLook only for users that posted in this thread
-

Type

-

ChannelParticipantsFilter

-

Related pages

-

Threads

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsRecent.html b/data/core.telegram.org/constructor/channelParticipantsRecent.html deleted file mode 100644 index a00ba54d16..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsRecent.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsRecent - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsRecent

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsSearch.html b/data/core.telegram.org/constructor/channelParticipantsSearch.html deleted file mode 100644 index cac36c2956..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsSearch.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsSearch - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsSearch

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channels.adminLogResults b/data/core.telegram.org/constructor/channels.adminLogResults deleted file mode 100644 index 3bf7720834..0000000000 --- a/data/core.telegram.org/constructor/channels.adminLogResults +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channels.adminLogResults - - - - - - - - - - - - - -
- -
-
-
- -

channels.adminLogResults

- -

Admin log events

-

-
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
eventsVector<ChannelAdminLogEvent>Admin log events
chatsVector<Chat>Chats mentioned in events
usersVector<User>Users mentioned in events
-

Type

-

channels.AdminLogResults

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channels.channelParticipant b/data/core.telegram.org/constructor/channels.channelParticipant deleted file mode 100644 index a94b9aca6d..0000000000 --- a/data/core.telegram.org/constructor/channels.channelParticipant +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channels.channelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

channels.channelParticipant

- -

Represents a channel participant

-

-
channels.channelParticipant#d0d9b163 participant:ChannelParticipant users:Vector<User> = channels.ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
participantChannelParticipantThe channel participant
usersVector<User>Users
-

Type

-

channels.ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channels.channelParticipants b/data/core.telegram.org/constructor/channels.channelParticipants deleted file mode 100644 index f8796cf1c9..0000000000 --- a/data/core.telegram.org/constructor/channels.channelParticipants +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channels.channelParticipants - - - - - - - - - - - - - -
- -
-
-
- -

channels.channelParticipants

- -

Represents multiple channel participants

-

-
channels.channelParticipants#f56ee2a8 count:int participants:Vector<ChannelParticipant> users:Vector<User> = channels.ChannelParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of participants that correspond to the given query
participantsVector<ChannelParticipant>Participants
usersVector<User>Users mentioned in participant info
-

Type

-

channels.ChannelParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channels.channelParticipantsNotModified b/data/core.telegram.org/constructor/channels.channelParticipantsNotModified deleted file mode 100644 index d4bd7dae88..0000000000 --- a/data/core.telegram.org/constructor/channels.channelParticipantsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channels.channelParticipantsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

channels.channelParticipantsNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chat.html b/data/core.telegram.org/constructor/chat.html deleted file mode 100644 index efdba142ad..0000000000 --- a/data/core.telegram.org/constructor/chat.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - chat - - - - - - - - - - - - - -
- -
-
-
- -

chat

- -

Info about a group

-

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

-

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
idintID of the group
titlestringTitle
photoChatPhotoChat photo
participants_countintParticipant count
dateintDate of creation of the group
versionintUsed in basic groups to reorder updates and make sure that all of them were received.
migrated_toflags.6?InputChannelMeans this chat was upgraded to a supergroup
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in the group
default_banned_rightsflags.18?ChatBannedRightsDefault banned rights of all users in the group
-

Type

-

Chat

-

Related pages

-

Channels

-

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

-

Admin, banned, default rights

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatAdminRights.html b/data/core.telegram.org/constructor/chatAdminRights.html deleted file mode 100644 index 7db70930a7..0000000000 --- a/data/core.telegram.org/constructor/chatAdminRights.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - chatAdminRights - - - - - - - - - - - - - -
- -
-
-
- -

chatAdminRights

- -

Represents the rights of an admin in a channel/supergroup.

-

-
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
change_infoflags.0?trueIf set, allows the admin to modify the description of the channel/supergroup
post_messagesflags.1?trueIf set, allows the admin to post messages in the channel
edit_messagesflags.2?trueIf set, allows the admin to also edit messages from other admins in the channel
delete_messagesflags.3?trueIf set, allows the admin to also delete messages from other admins in the channel
ban_usersflags.4?trueIf set, allows the admin to ban users from the channel/supergroup
invite_usersflags.5?trueIf set, allows the admin to invite users in the channel/supergroup
pin_messagesflags.7?trueIf set, allows the admin to pin messages in the channel/supergroup
add_adminsflags.9?trueIf set, allows the admin to add other admins with the same (or more limited) permissions in the channel/supergroup
anonymousflags.10?trueWhether this admin is anonymous
-

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 deleted file mode 100644 index a0060d06d3..0000000000 --- a/data/core.telegram.org/constructor/chatBannedRights.html +++ /dev/null @@ -1,215 +0,0 @@ - - - - - chatBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

chatBannedRights

- -

Represents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.

-

-
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
view_messagesflags.0?trueIf set, does not allow a user to view messages in a supergroup/channel/chat
send_messagesflags.1?trueIf set, does not allow a user to send messages in a supergroup/chat
send_mediaflags.2?trueIf set, does not allow a user to send any media in a supergroup/chat
send_stickersflags.3?trueIf set, does not allow a user to send stickers in a supergroup/chat
send_gifsflags.4?trueIf set, does not allow a user to send gifs in a supergroup/chat
send_gamesflags.5?trueIf set, does not allow a user to send games in a supergroup/chat
send_inlineflags.6?trueIf set, does not allow a user to use inline bots in a supergroup/chat
embed_linksflags.7?trueIf set, does not allow a user to embed links in the messages of a supergroup/chat
send_pollsflags.8?trueIf set, does not allow a user to send stickers in a supergroup/chat
change_infoflags.10?trueIf set, does not allow any user to change the description of a supergroup/chat
invite_usersflags.15?trueIf set, does not allow any user to invite users in a supergroup/chat
pin_messagesflags.17?trueIf set, does not allow any user to pin messages in a supergroup/chat
until_dateintValidity of said permissions (it is considered forever any value less then 30 seconds or more then 366 days).
-

Type

-

ChatBannedRights

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatEmpty.html b/data/core.telegram.org/constructor/chatEmpty.html deleted file mode 100644 index a6dc055b22..0000000000 --- a/data/core.telegram.org/constructor/chatEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatForbidden.html b/data/core.telegram.org/constructor/chatForbidden.html deleted file mode 100644 index c8bb986822..0000000000 --- a/data/core.telegram.org/constructor/chatForbidden.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - chatForbidden - - - - - - - - - - - - - -
- -
-
-
- -

chatForbidden

- -

A group to which the user has no access. E.g., because the user was kicked from the group.

-

-
chatForbidden#7328bdb id:int title:string = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintUser identifier
titlestringGroup name
-

Type

-

Chat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatFull.html b/data/core.telegram.org/constructor/chatFull.html deleted file mode 100644 index 72e49fa2a8..0000000000 --- a/data/core.telegram.org/constructor/chatFull.html +++ /dev/null @@ -1,209 +0,0 @@ - - - - - chatFull - - - - - - - - - - - - - -
- -
-
-
- -

chatFull

- -

Detailed chat info

-

-
chatFull#1b7c9db3 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 = 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
idintID of the chat
aboutstringAbout string for this chat
participantsChatParticipantsParticipant list
chat_photoflags.2?PhotoChat photo
notify_settingsPeerNotifySettingsNotification settings
exported_inviteExportedChatInviteChat 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
-

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.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInvite.html b/data/core.telegram.org/constructor/chatInvite.html deleted file mode 100644 index 6eed68e1b2..0000000000 --- a/data/core.telegram.org/constructor/chatInvite.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - chatInvite - - - - - - - - - - - - - -
- -
-
-
- -

chatInvite

- -

Chat invite info

-

-
chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channelflags.0?trueWhether this is a channel/supergroup or a normal group
broadcastflags.1?trueWhether this is a channel
publicflags.2?trueWhether this is a public channel/supergroup
megagroupflags.3?trueWhether this is a supergroup
titlestringChat/supergroup/channel title
photoPhotoChat/supergroup/channel photo
participants_countintParticipant count
participantsflags.4?Vector<User>A few of the participants that are in the group
-

Type

-

ChatInvite

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInviteAlready.html b/data/core.telegram.org/constructor/chatInviteAlready.html deleted file mode 100644 index b65dbbdf90..0000000000 --- a/data/core.telegram.org/constructor/chatInviteAlready.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatInviteAlready - - - - - - - - - - - - - -
- -
-
-
- -

chatInviteAlready

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInviteEmpty.html b/data/core.telegram.org/constructor/chatInviteEmpty.html deleted file mode 100644 index a97594710f..0000000000 --- a/data/core.telegram.org/constructor/chatInviteEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - chatInviteEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInviteExported.html b/data/core.telegram.org/constructor/chatInviteExported.html deleted file mode 100644 index fbf2a5f75c..0000000000 --- a/data/core.telegram.org/constructor/chatInviteExported.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatInviteExported - - - - - - - - - - - - - -
- -
-
-
- -

chatInviteExported

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInvitePeek.html b/data/core.telegram.org/constructor/chatInvitePeek.html deleted file mode 100644 index 4e4f7431b4..0000000000 --- a/data/core.telegram.org/constructor/chatInvitePeek.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - chatInvitePeek - - - - - - - - - - - - - -
- -
-
-
- -

chatInvitePeek

- -

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

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chatChatChat information
expiresintRead-only anonymous access to this group will be revoked at this date
-

Type

-

ChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatOnlines.html b/data/core.telegram.org/constructor/chatOnlines.html deleted file mode 100644 index 6f41ce1855..0000000000 --- a/data/core.telegram.org/constructor/chatOnlines.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatOnlines - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatParticipant.html b/data/core.telegram.org/constructor/chatParticipant.html deleted file mode 100644 index de5cc4743d..0000000000 --- a/data/core.telegram.org/constructor/chatParticipant.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipant - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipant

- -

Group member.

-

-
chatParticipant#c8d7493e user_id:int inviter_id:int date:int = ChatParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintMember user ID
inviter_idintID 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 deleted file mode 100644 index 34ee67e7ad..0000000000 --- a/data/core.telegram.org/constructor/chatParticipantAdmin.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantAdmin

- -

Chat admin

-

-
chatParticipantAdmin#e2d6e436 user_id:int inviter_id:int date:int = ChatParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintID of a group member that is admin
inviter_idintID of the user that added the member to the group
dateintDate when the user was added
-

Type

-

ChatParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatParticipantCreator.html b/data/core.telegram.org/constructor/chatParticipantCreator.html deleted file mode 100644 index 4a17e99103..0000000000 --- a/data/core.telegram.org/constructor/chatParticipantCreator.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatParticipantCreator - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantCreator

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatParticipants.html b/data/core.telegram.org/constructor/chatParticipants.html deleted file mode 100644 index 76983c45af..0000000000 --- a/data/core.telegram.org/constructor/chatParticipants.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipants

- -

Group members.

-

-
chatParticipants#3f460fed chat_id:int participants:Vector<ChatParticipant> version:int = ChatParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintGroup identifier
participantsVector<ChatParticipant>List of group members
versionintGroup version number
-

Type

-

ChatParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatParticipantsForbidden.html b/data/core.telegram.org/constructor/chatParticipantsForbidden.html deleted file mode 100644 index 27061e7669..0000000000 --- a/data/core.telegram.org/constructor/chatParticipantsForbidden.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipantsForbidden - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantsForbidden

- -

Info on members is unavailable

-

-
chatParticipantsForbidden#fc900c2b flags:# chat_id:int self_participant:flags.0?ChatParticipant = ChatParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
chat_idintGroup ID
self_participantflags.0?ChatParticipantInfo about the group membership of the current user
-

Type

-

ChatParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatPhoto.html b/data/core.telegram.org/constructor/chatPhoto.html deleted file mode 100644 index 2159f121b6..0000000000 --- a/data/core.telegram.org/constructor/chatPhoto.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - chatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

chatPhoto

- -

Group profile photo.

-

-
chatPhoto#d20b9f3c flags:# has_video:flags.0?true photo_small:FileLocation photo_big:FileLocation dc_id:int = ChatPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether the user has an animated profile picture
photo_smallFileLocationLocation of the file corresponding to the small thumbnail for group profile photo
photo_bigFileLocationLocation of the file corresponding to the small thumbnail for group profile photo
dc_idintDC where this photo is stored
-

Type

-

ChatPhoto

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatPhotoEmpty.html b/data/core.telegram.org/constructor/chatPhotoEmpty.html deleted file mode 100644 index 26e9ad7546..0000000000 --- a/data/core.telegram.org/constructor/chatPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - chatPhotoEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/codeSettings.html b/data/core.telegram.org/constructor/codeSettings.html deleted file mode 100644 index d665c901cd..0000000000 --- a/data/core.telegram.org/constructor/codeSettings.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - codeSettings - - - - - - - - - - - - - -
- -
-
-
- -

codeSettings

- -

Settings used by telegram servers for sending the confirm code.

-

Example implementations: telegram for android, tdlib.

-

-
codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
allow_flashcallflags.0?trueWhether to allow phone verification via phone calls.
current_numberflags.1?truePass true if the phone number is used on the current device. Ignored if allow_flashcall is not set.
allow_app_hashflags.4?trueIf a token that will be included in eventually sent SMSs is required: required in newer versions of android, to use the android SMS receiver APIs
-

Type

-

CodeSettings

-

Related pages

-

User Authorization

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/config.html b/data/core.telegram.org/constructor/config.html deleted file mode 100644 index 525355fe0b..0000000000 --- a/data/core.telegram.org/constructor/config.html +++ /dev/null @@ -1,420 +0,0 @@ - - - - - config - - - - - - - - - - - - - -
- -
-
-
- -

config

- -

Current configuration

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phonecalls_enabledflags.1?trueWhether phone calls can be used
default_p2p_contactsflags.3?trueWhether the client should use P2P by default for phone calls with contacts
preload_featured_stickersflags.4?trueWhether the client should preload featured stickers
ignore_phone_entitiesflags.5?trueWhether the client should ignore phone entities
revoke_pm_inboxflags.6?trueWhether incoming private messages can be deleted for both participants
blocked_modeflags.8?trueIndicates that telegram is probably censored by governments/ISPs in the current region
pfs_enabledflags.13?trueWhether pfs was used
dateintCurrent date at the server
expiresintExpiration date of this config: when it expires it'll have to be refetched using help.getConfig
test_modeBoolWhether we're connected to the test DCs
this_dcintID of the DC that returned the reply
dc_optionsVector<DcOption>DC IP list
dc_txt_domain_namestringDomain name for fetching encrypted DC list from DNS TXT record
chat_size_maxintMaximum member count for normal groups
megagroup_size_maxintMaximum member count for supergroups
forwarded_count_maxintMaximum number of messages that can be forwarded at once using messages.forwardMessages.
online_update_period_msintThe client should update its online status every N milliseconds
offline_blur_timeout_msintDelay before offline status needs to be sent to the server
offline_idle_timeout_msintTime without any user activity after which it should be treated offline
online_cloud_timeout_msintIf we are offline, but were online from some other client in last online_cloud_timeout_ms milliseconds after we had gone offline, then delay offline notification for notify_cloud_delay_ms milliseconds.
notify_cloud_delay_msintIf we are offline, but online from some other client then delay sending the offline notification for notify_cloud_delay_ms milliseconds.
notify_default_delay_msintIf some other client is online, then delay notification for notification_default_delay_ms milliseconds
push_chat_period_msintNot for client use
push_chat_limitintNot for client use
saved_gifs_limitintMaximum count of saved gifs
edit_time_limitintOnly messages with age smaller than the one specified can be edited
revoke_time_limitintOnly channel/supergroup messages with age smaller than the specified can be deleted
revoke_pm_time_limitintOnly private messages with age smaller than the specified can be deleted
rating_e_decayintExponential decay rate for computing top peer rating
stickers_recent_limitintMaximum number of recent stickers
stickers_faved_limitintMaximum number of faved stickers
channels_read_media_periodintIndicates that round videos (video notes) and voice messages sent in channels and older than the specified period must be marked as read
tmp_sessionsflags.0?intTemporary passport sessions
pinned_dialogs_count_maxintMaximum count of pinned dialogs
pinned_infolder_count_maxintMaximum count of dialogs per folder
call_receive_timeout_msintMaximum allowed outgoing ring time in VoIP calls: if the user we're calling doesn't reply within the specified time (in milliseconds), we should hang up the call
call_ring_timeout_msintMaximum allowed incoming ring time in VoIP calls: if the current user doesn't reply within the specified time (in milliseconds), the call will be automatically refused
call_connect_timeout_msintVoIP connection timeout: if the instance of libtgvoip on the other side of the call doesn't connect to our instance of libtgvoip within the specified time (in milliseconds), the call must be aborted
call_packet_timeout_msintIf during a VoIP call a packet isn't received for the specified period of time, the call must be aborted
me_url_prefixstringThe domain to use to parse in-app links.
For example t.me indicates that t.me/username links should parsed to @username, t.me/addsticker/name should be parsed to the appropriate stickerset and so on...
autoupdate_url_prefixflags.7?stringURL to use to auto-update the current app
gif_search_usernameflags.9?stringUsername of the bot to use to search for GIFs
venue_search_usernameflags.10?stringUsername of the bot to use to search for venues
img_search_usernameflags.11?stringUsername of the bot to use for image search
static_maps_providerflags.12?stringID of the map provider to use for venues
caption_length_maxintMaximum length of caption (length in utf8 codepoints)
message_length_maxintMaximum length of messages (length in utf8 codepoints)
webfile_dc_idintDC ID to use to download webfiles
suggested_lang_codeflags.2?stringSuggested language code
lang_pack_versionflags.2?intLanguage pack version
base_lang_pack_versionflags.2?intBasic language pack version
-

Type

-

Config

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

help.getConfig

-

Returns current configuration, including data center configuration.

-

Channels

-

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

-

messages.forwardMessages

-

Forwards messages by their IDs.

-

account.updateStatus

-

Updates online user status.

-

Top peer rating

-

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

-

Telegram Passport Manual

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contact.html b/data/core.telegram.org/constructor/contact.html deleted file mode 100644 index 98424d3721..0000000000 --- a/data/core.telegram.org/constructor/contact.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - contact - - - - - - - - - - - - - -
- -
-
-
- -

contact

- -

A contact of the current user that is registered in the system.

-

-
contact#f911c994 user_id:int mutual:Bool = Contact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser identifier
mutualBoolCurrent user is in the user's contact list
-

Type

-

Contact

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contactStatus.html b/data/core.telegram.org/constructor/contactStatus.html deleted file mode 100644 index 6d320c3bcf..0000000000 --- a/data/core.telegram.org/constructor/contactStatus.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - contactStatus - - - - - - - - - - - - - -
- -
-
-
- -

contactStatus

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.blocked b/data/core.telegram.org/constructor/contacts.blocked deleted file mode 100644 index df17d7108c..0000000000 --- a/data/core.telegram.org/constructor/contacts.blocked +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.blocked - - - - - - - - - - - - - -
- -
-
-
- -

contacts.blocked

- -

Full list of blocked users.

-

-
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
-

Type

-

contacts.Blocked

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.blockedSlice b/data/core.telegram.org/constructor/contacts.blockedSlice deleted file mode 100644 index 78c9e45e3f..0000000000 --- a/data/core.telegram.org/constructor/contacts.blockedSlice +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.blockedSlice - - - - - - - - - - - - - -
- -
-
-
- -

contacts.blockedSlice

- -

Incomplete list of blocked users.

-

-
contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of elements in the list
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
-

Type

-

contacts.Blocked

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.contacts b/data/core.telegram.org/constructor/contacts.contacts deleted file mode 100644 index d9e2ad9576..0000000000 --- a/data/core.telegram.org/constructor/contacts.contacts +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.contacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.contacts

- -

The current user's contact list and info on users.

-

-
contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
contactsVector<Contact>Contact list
saved_countintNumber of contacts that were saved successfully
usersVector<User>User list
-

Type

-

contacts.Contacts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.contactsNotModified b/data/core.telegram.org/constructor/contacts.contactsNotModified deleted file mode 100644 index 29b516a96a..0000000000 --- a/data/core.telegram.org/constructor/contacts.contactsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.contactsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

contacts.contactsNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.found b/data/core.telegram.org/constructor/contacts.found deleted file mode 100644 index f30e310da1..0000000000 --- a/data/core.telegram.org/constructor/contacts.found +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.found - - - - - - - - - - - - - -
- -
-
-
- -

contacts.found

- -

Users found by name substring and auxiliary data.

-

-
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
my_resultsVector<Peer>Personalized results
resultsVector<Peer>List of found user identifiers
chatsVector<Chat>Found chats
usersVector<User>List of users
-

Type

-

contacts.Found

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.importedContacts b/data/core.telegram.org/constructor/contacts.importedContacts deleted file mode 100644 index 767830fffd..0000000000 --- a/data/core.telegram.org/constructor/contacts.importedContacts +++ /dev/null @@ -1,165 +0,0 @@ - - - - - contacts.importedContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.importedContacts

- -

Info on succesfully imported contacts.

-

-
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
importedVector<ImportedContact>List of succesfully imported contacts
popular_invitesVector<PopularContact>Popular contacts
retry_contactsVector<long>List of contact ids that could not be imported due to system limitation and will need to be imported at a later date.
Parameter added in Layer 13
usersVector<User>List of users
-

Type

-

contacts.ImportedContacts

-

Related pages

-

Layers

-

Below you will find information on scheme 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 deleted file mode 100644 index 5a979bbe60..0000000000 --- a/data/core.telegram.org/constructor/contacts.resolvedPeer +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.resolvedPeer - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resolvedPeer

- -

Resolved peer

-

-
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

contacts.ResolvedPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.topPeers b/data/core.telegram.org/constructor/contacts.topPeers deleted file mode 100644 index b60fbbbc9b..0000000000 --- a/data/core.telegram.org/constructor/contacts.topPeers +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.topPeers - - - - - - - - - - - - - -
- -
-
-
- -

contacts.topPeers

- -

Top peers

-

-
contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
categoriesVector<TopPeerCategoryPeers>Top peers by top peer category
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

contacts.TopPeers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.topPeersDisabled b/data/core.telegram.org/constructor/contacts.topPeersDisabled deleted file mode 100644 index bc9fcf7044..0000000000 --- a/data/core.telegram.org/constructor/contacts.topPeersDisabled +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.topPeersDisabled - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.topPeersNotModified b/data/core.telegram.org/constructor/contacts.topPeersNotModified deleted file mode 100644 index 80f09d3c3c..0000000000 --- a/data/core.telegram.org/constructor/contacts.topPeersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.topPeersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

contacts.topPeersNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dataJSON.html b/data/core.telegram.org/constructor/dataJSON.html deleted file mode 100644 index d7d2d31bb8..0000000000 --- a/data/core.telegram.org/constructor/dataJSON.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - dataJSON - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/dcOption.html b/data/core.telegram.org/constructor/dcOption.html deleted file mode 100644 index e0880ce148..0000000000 --- a/data/core.telegram.org/constructor/dcOption.html +++ /dev/null @@ -1,197 +0,0 @@ - - - - - dcOption - - - - - - - - - - - - - -
- -
-
-
- -

dcOption

- -

Data centre

-

-
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
ipv6flags.0?trueWhether the specified IP is an IPv6 address
media_onlyflags.1?trueWhether this DC should only be used to download or upload files
tcpo_onlyflags.2?trueWhether this DC only supports connection with transport obfuscation
cdnflags.3?trueWhether this is a CDN DC.
staticflags.4?trueIf set, this IP should be used when connecting through a proxy
idintDC ID
ip_addressstringIP address of DC
portintPort
secretflags.10?bytesIf the tcpo_only flag is set, specifies the secret to use when connecting using transport obfuscation
-

Type

-

DcOption

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

MTProto transports

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessage.html b/data/core.telegram.org/constructor/decryptedMessage.html deleted file mode 100644 index aef16e9a26..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessage.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - decryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessage

- -

Contents of an encrypted message.

-

-
===8===
-decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
-
-===17===
-decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
-
-===45===
-decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
-
-===73===
-decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields (added in layer 45)
no_webpageflags.1?trueWhether the webpage preview is disabled
silentflags.5?trueWhether this is a silent message (no notification triggered)
random_idlongRandom message ID, assigned by the author of message.
Must be equal to the ID passed to sending method.
ttlintMessage lifetime. Has higher priority than decryptedMessageActionSetMessageTTL.
Parameter added in Layer 17.
messagestringMessage text
mediaflags.9?DecryptedMessageMediaMedia content
entitiesflags.7?Vector<MessageEntity>Message entities for styled text (parameter added in layer 45)
via_bot_nameflags.11?stringSpecifies the ID of the inline bot that generated the message (parameter added in layer 45)
reply_to_random_idflags.3?longRandom message ID of the message this message replies to (parameter added in layer 45)
grouped_idflags.17?longRandom group ID, assigned by the author of message.
Multiple encrypted messages with a photo attached and with the same group ID indicate an album or grouped media (parameter added in layer 45)
-

Type

-

DecryptedMessage

-

Related pages

-

decryptedMessageActionSetMessageTTL

-

Setting of a message lifetime after reading.

-

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

-

Layers

-

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

-

Styled text with message entities

-

How to create styled text with message entities

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html b/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html deleted file mode 100644 index 1ff212bf50..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionAbortKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionAbortKey

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html b/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html deleted file mode 100644 index b8e1b16c4f..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - decryptedMessageActionAcceptKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionAcceptKey

- -

Accept new key

-

-
===20===
-decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID
g_bbytesB parameter, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
-

Type

-

DecryptedMessageAction

-

Related pages

-

Perfect Forward Secrecy

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html b/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html deleted file mode 100644 index 53b57d2e22..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionCommitKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionCommitKey

- -

Commit new key, see rekeying process

-

-
===20===
-decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
-

Type

-

DecryptedMessageAction

-

Related pages

-

Perfect Forward Secrecy

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html deleted file mode 100644 index 53ebf03019..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionDeleteMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionDeleteMessages

- -

Deleted messages.

-

-
===8===
-decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of deleted message IDs
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html b/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html deleted file mode 100644 index fbd24979cf..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - decryptedMessageActionFlushHistory - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionFlushHistory

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionNoop.html b/data/core.telegram.org/constructor/decryptedMessageActionNoop.html deleted file mode 100644 index b5c513beeb..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionNoop.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - decryptedMessageActionNoop - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionNoop

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html b/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html deleted file mode 100644 index 52b89dad0c..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - decryptedMessageActionNotifyLayer - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionNotifyLayer

- -

A notification stating the API layer that is used by the client. You should use your current layer and take notice of the layer used on the other side of a conversation when sending messages.

-

-
===17===
-decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
layerintLayer number, must be 17 or higher (this contructor was introduced in Layer 17).
-

Type

-

DecryptedMessageAction

-

Related pages

-

Layers

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html deleted file mode 100644 index 3f968d0078..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionReadMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionReadMessages

- -

Messages marked as read.

-

-
===8===
-decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of message IDs
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html b/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html deleted file mode 100644 index 7917d5d473..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionRequestKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionRequestKey

- -

Request rekeying, see rekeying process

-

-
===20===
-decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID
g_abytesg_a, see rekeying process
-

Type

-

DecryptedMessageAction

-

Related pages

-

Perfect Forward Secrecy

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionResend.html b/data/core.telegram.org/constructor/decryptedMessageActionResend.html deleted file mode 100644 index 2fd3de2b58..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionResend.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionResend - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionResend

- -

Request for the other party in a Secret Chat to automatically resend a contiguous range of previously sent messages, as explained in Sequence number is Secret Chats.

-

-
===17===
-decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
start_seq_nointout_seq_no of the first message to be resent, with correct parity
end_seq_nointout_seq_no of the last message to be resent, with same parity.
-

Type

-

DecryptedMessageAction

-

Related pages

-

Sequence numbers in Secret Chats

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html deleted file mode 100644 index 81ba8b7d01..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionScreenshotMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionScreenshotMessages

- -

A screenshot was taken.

-

-
===8===
-decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of affected message ids (that appeared on the screenshot)
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html b/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html deleted file mode 100644 index cc4d6651e7..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - decryptedMessageActionSetMessageTTL - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionSetMessageTTL

- -

Setting of a message lifetime after reading.

-

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

-

-
===8===
-decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
ttl_secondsintLifetime in seconds
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionTyping.html b/data/core.telegram.org/constructor/decryptedMessageActionTyping.html deleted file mode 100644 index 1d23f2e882..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionTyping.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionTyping - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionTyping

- -

User is preparing a message: typing, recording, uploading, etc.

-

-
===17===
-decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
actionSendMessageActionType of action
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageLayer.html b/data/core.telegram.org/constructor/decryptedMessageLayer.html deleted file mode 100644 index 834201b2e3..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageLayer.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - decryptedMessageLayer - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageLayer

- -

Sets the layer number for the contents of an encrypted message.

-

-
===17===
-decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_bytesbytesSet of random bytes to prevent content recognition in short encrypted messages.
Clients are required to check that there are at least 15 random bytes included in each message. Messages with less than 15 random bytes must be ignored.
Parameter moved here from decryptedMessage in Layer 17.
layerintLayer number. Mimimal value - 17 (the layer in which the constructor was added).
in_seq_noint2x the number of messages in the sender's inbox (including deleted and service messages), incremented by 1 if current user was not the chat creator
Parameter added in Layer 17.
out_seq_noint2x the number of messages in the recipient's inbox (including deleted and service messages), incremented by 1 if current user was the chat creator
Parameter added in Layer 17.
messageDecryptedMessageThe content of message itself
-

Type

-

DecryptedMessageLayer

-

Related pages

-

decryptedMessage

-

Contents of an encrypted message.

-

Layers

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html b/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html deleted file mode 100644 index 2231da96c7..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html +++ /dev/null @@ -1,174 +0,0 @@ - - - - - decryptedMessageMediaAudio - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaAudio

- -

Audio file attached to a secret chat message.

-

-
===8===
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
durationintAudio duration in seconds
mime_typestringMIME-type of the audio file
Parameter added in Layer 13.
sizeintFile size
keybytesKey to decrypt the attached media file
ivbytesInitialization vector
-

Type

-

DecryptedMessageMedia

-

Related pages

-

Layers

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaContact.html b/data/core.telegram.org/constructor/decryptedMessageMediaContact.html deleted file mode 100644 index 8d6d7eae6a..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaContact.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - decryptedMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaContact

- -

Contact attached to an encrypted message.

-

-
===8===
-decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
user_idintTelegram User ID of signed-up contact
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html b/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html deleted file mode 100644 index 7f35a6b824..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - - decryptedMessageMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaDocument

- -

Document attached to a message in a secret chat.

-

-
===8===
-decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesThumbnail-file contents (JPEG-file, quality 55, set in a 90x90 square)
thumb_wintThumbnail width
thumb_hintThumbnail height
mime_typestringFile MIME-type
sizeintDocument size
keybytesKey to decrypt the attached document file
ivbytesInitialization
attributesVector<DocumentAttribute>Document attributes for media types
captionstringCaption
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html b/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html deleted file mode 100644 index fefe75ebcb..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - decryptedMessageMediaEmpty - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaEmpty

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html b/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html deleted file mode 100644 index 8a486544be..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - decryptedMessageMediaExternalDocument - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaExternalDocument

- -

Non-e2e documented forwarded from non-secret chat

-

-
===23===
-decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess hash
dateintDate
mime_typestringMime type
sizeintSize
thumbPhotoSizeThumbnail
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html b/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html deleted file mode 100644 index 70b028a15d..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - decryptedMessageMediaGeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaGeoPoint

- -

GeoPont attached to an encrypted message.

-

-
===8===
-decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
latdoubleLatitude of point
longdoubleLongtitude of point
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html b/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html deleted file mode 100644 index bfd6167d2c..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - - decryptedMessageMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaPhoto

- -

Photo attached to an encrypted message.

-

-
===8===
-decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesContent of thumbnail file (JPEGfile, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
wintPhoto width
hintPhoto height
sizeintSize of the photo in bytes
keybytesKey to decrypt an attached file with a full version
ivbytesInitialization vector
captionstringCaption
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html b/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html deleted file mode 100644 index 7cfa09dbe7..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - decryptedMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaVenue

- -

Venue

-

-
===45===
-decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
latdoubleLatitude of venue
longdoubleLongitude of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html b/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html deleted file mode 100644 index 56f021246f..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html +++ /dev/null @@ -1,207 +0,0 @@ - - - - - decryptedMessageMediaVideo - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaVideo

- -

Video attached to an encrypted message.

-

-
===8===
-decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesContent of thumbnail file (JPEG file, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
durationintDuration of video in seconds
mime_typestringMIME-type of the video file
Parameter added in Layer 17.
wintImage width
hintImage height
sizeintFile size
keybytesKey to decrypt the attached video file
ivbytesInitialization vector
captionstringCaption
-

Type

-

DecryptedMessageMedia

-

Related pages

-

Layers

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html b/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html deleted file mode 100644 index e312bd108f..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageMediaWebPage - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaWebPage

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageService.html b/data/core.telegram.org/constructor/decryptedMessageService.html deleted file mode 100644 index 47ea730538..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageService.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - decryptedMessageService - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageService

- -

Contents of an encrypted service message.

-

-
===8===
-decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
-
-===17===
-decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the message author.
Must be equal to the ID passed to the sending method.
actionDecryptedMessageActionAction relevant to the service message
-

Type

-

DecryptedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialog.html b/data/core.telegram.org/constructor/dialog.html deleted file mode 100644 index 2dac3f423c..0000000000 --- a/data/core.telegram.org/constructor/dialog.html +++ /dev/null @@ -1,214 +0,0 @@ - - - - - dialog - - - - - - - - - - - - - -
- -
-
-
- -

dialog

- -

Chat

-

-
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs the dialog pinned
unread_markflags.3?trueWhether the chat was manually marked as unread
peerPeerThe chat
top_messageintThe latest message ID
read_inbox_max_idintPosition up to which all incoming messages are read.
read_outbox_max_idintPosition up to which all outgoing messages are read.
unread_countintNumber of unread messages
unread_mentions_countintNumber of unread mentions
notify_settingsPeerNotifySettingsNotification settings
ptsflags.0?intPTS
draftflags.1?DraftMessageMessage draft
folder_idflags.4?intPeer folder ID, for more info click here
-

Type

-

Dialog

-

Related pages

-

Mentions

-

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

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogFilter.html b/data/core.telegram.org/constructor/dialogFilter.html deleted file mode 100644 index 5856688eb8..0000000000 --- a/data/core.telegram.org/constructor/dialogFilter.html +++ /dev/null @@ -1,220 +0,0 @@ - - - - - dialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

dialogFilter

- -

Dialog filter AKA folder

-

-
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to include all contacts in this folder
non_contactsflags.1?trueWhether to include all non-contacts in this folder
groupsflags.2?trueWhether to include all groups in this folder
broadcastsflags.3?trueWhether to include all channels in this folder
botsflags.4?trueWhether to include all bots in this folder
exclude_mutedflags.11?trueWhether to exclude muted chats from this folder
exclude_readflags.12?trueWhether to exclude read chats from this folder
exclude_archivedflags.13?trueWhether to exclude archived chats from this folder
idintFolder ID
titlestringFolder name
emoticonflags.25?stringFolder emoticon
pinned_peersVector<InputPeer>Pinned chats, folders can have unlimited pinned chats
include_peersVector<InputPeer>Include the following chats in this folder
exclude_peersVector<InputPeer>Exclude the following chats from this folder
-

Type

-

DialogFilter

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogFilterSuggested.html b/data/core.telegram.org/constructor/dialogFilterSuggested.html deleted file mode 100644 index 6ddc48adfc..0000000000 --- a/data/core.telegram.org/constructor/dialogFilterSuggested.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - dialogFilterSuggested - - - - - - - - - - - - - -
- -
-
-
- -

dialogFilterSuggested

- -

Suggested folders

-

-
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
filterDialogFilterFolder info
descriptionstringFolder description
-

Type

-

DialogFilterSuggested

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogFolder.html b/data/core.telegram.org/constructor/dialogFolder.html deleted file mode 100644 index daaa4f6a68..0000000000 --- a/data/core.telegram.org/constructor/dialogFolder.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - dialogFolder - - - - - - - - - - - - - -
- -
-
-
- -

dialogFolder

- -

Dialog in folder

-

-
dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs this folder pinned
folderFolderThe folder
peerPeerPeer in folder
top_messageintLatest message ID of dialog
unread_muted_peers_countintNumber of unread muted peers in folder
unread_unmuted_peers_countintNumber of unread unmuted peers in folder
unread_muted_messages_countintNumber of unread messages from muted peers in folder
unread_unmuted_messages_countintNumber of unread messages from unmuted peers in folder
-

Type

-

Dialog

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogPeer.html b/data/core.telegram.org/constructor/dialogPeer.html deleted file mode 100644 index 88d4c07287..0000000000 --- a/data/core.telegram.org/constructor/dialogPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - dialogPeer - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogPeerFolder.html b/data/core.telegram.org/constructor/dialogPeerFolder.html deleted file mode 100644 index 8e1ea4fae8..0000000000 --- a/data/core.telegram.org/constructor/dialogPeerFolder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - dialogPeerFolder - - - - - - - - - - - - - -
- -
-
-
- -

dialogPeerFolder

- -

Peer folder

-

-
dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Type

-

DialogPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/disabledFeature.html b/data/core.telegram.org/constructor/disabledFeature.html deleted file mode 100644 index 45f9a9498a..0000000000 --- a/data/core.telegram.org/constructor/disabledFeature.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - disabledFeature - - - - - - - - - - - - - -
- -
-
-
- -

disabledFeature

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/document.html b/data/core.telegram.org/constructor/document.html deleted file mode 100644 index fe468ceb8b..0000000000 --- a/data/core.telegram.org/constructor/document.html +++ /dev/null @@ -1,200 +0,0 @@ - - - - - document - - - - - - - - - - - - - -
- -
-
-
- -

document

- -

Document

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongDocument ID
access_hashlongCheck sum, dependant on document ID
file_referencebytesFile reference
dateintCreation date
mime_typestringMIME type
sizeintSize
thumbsflags.0?Vector<PhotoSize>Thumbnails
video_thumbsflags.1?Vector<VideoSize>Video thumbnails
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes
-

Type

-

Document

-

Related pages

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeAnimated.html b/data/core.telegram.org/constructor/documentAttributeAnimated.html deleted file mode 100644 index dfbfb04e42..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeAnimated.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - documentAttributeAnimated - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeAudio.html b/data/core.telegram.org/constructor/documentAttributeAudio.html deleted file mode 100644 index 891a106dea..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeAudio.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - documentAttributeAudio - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeAudio

- -

Represents an audio file

-

-
documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
voiceflags.10?trueWhether this is a voice message
durationintDuration in seconds
titleflags.0?stringName of song
performerflags.1?stringPerformer
waveformflags.2?bytesWaveform
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeFilename.html b/data/core.telegram.org/constructor/documentAttributeFilename.html deleted file mode 100644 index b9a5741df1..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeFilename.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - documentAttributeFilename - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeFilename

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeHasStickers.html b/data/core.telegram.org/constructor/documentAttributeHasStickers.html deleted file mode 100644 index b5afcf9cdc..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeHasStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - documentAttributeHasStickers - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeHasStickers

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeImageSize.html b/data/core.telegram.org/constructor/documentAttributeImageSize.html deleted file mode 100644 index b24384e936..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeImageSize.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - documentAttributeImageSize - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeImageSize

- -

Defines the width and height of an image uploaded as document

-

-
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
wintWidth of image
hintHeight of image
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeSticker.html b/data/core.telegram.org/constructor/documentAttributeSticker.html deleted file mode 100644 index ce9cd3a723..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeSticker.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - documentAttributeSticker - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeSticker

- -

Defines a sticker

-

-
documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
maskflags.1?trueWhether this is a mask sticker
altstringAlternative emoji representation of sticker
stickersetInputStickerSetAssociated stickerset
mask_coordsflags.0?MaskCoordsMask coordinates (if this is a mask sticker, attached to a photo)
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeVideo.html b/data/core.telegram.org/constructor/documentAttributeVideo.html deleted file mode 100644 index 06a0b7806e..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeVideo.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - documentAttributeVideo - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeVideo

- -

Defines a video

-

-
documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
round_messageflags.0?trueWhether this is a round video
supports_streamingflags.1?trueWhether the video supports streaming
durationintDuration in seconds
wintVideo width
hintVideo height
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentEmpty.html b/data/core.telegram.org/constructor/documentEmpty.html deleted file mode 100644 index b9b690343d..0000000000 --- a/data/core.telegram.org/constructor/documentEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - documentEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/draftMessage.html b/data/core.telegram.org/constructor/draftMessage.html deleted file mode 100644 index 8d39a03d6e..0000000000 --- a/data/core.telegram.org/constructor/draftMessage.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - draftMessage - - - - - - - - - - - - - -
- -
-
-
- -

draftMessage

- -

Represents a message draft.

-

-
draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueWhether no webpage preview will be generated
reply_to_msg_idflags.0?intThe message this message will reply to
messagestringThe draft
entitiesflags.3?Vector<MessageEntity>Message entities for styled text.
dateintDate of last update of the draft.
-

Type

-

DraftMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/draftMessageEmpty.html b/data/core.telegram.org/constructor/draftMessageEmpty.html deleted file mode 100644 index f9aadc2853..0000000000 --- a/data/core.telegram.org/constructor/draftMessageEmpty.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - draftMessageEmpty - - - - - - - - - - - - - -
- -
-
-
- -

draftMessageEmpty

- -

Empty draft

-

-
draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
dateflags.0?intWhen was the draft last updated
-

Type

-

DraftMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiKeyword.html b/data/core.telegram.org/constructor/emojiKeyword.html deleted file mode 100644 index 95ec5b08b2..0000000000 --- a/data/core.telegram.org/constructor/emojiKeyword.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - emojiKeyword - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeyword

- -

Emoji keyword

-

-
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis associated to keyword
-

Type

-

EmojiKeyword

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiKeywordDeleted.html b/data/core.telegram.org/constructor/emojiKeywordDeleted.html deleted file mode 100644 index 71635fb927..0000000000 --- a/data/core.telegram.org/constructor/emojiKeywordDeleted.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - emojiKeywordDeleted - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeywordDeleted

- -

Deleted emoji keyword

-

-
emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis that were associated to keyword
-

Type

-

EmojiKeyword

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiKeywordsDifference.html b/data/core.telegram.org/constructor/emojiKeywordsDifference.html deleted file mode 100644 index 04afb8ee1c..0000000000 --- a/data/core.telegram.org/constructor/emojiKeywordsDifference.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - emojiKeywordsDifference - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeywordsDifference

- -

Changes to emoji keywords

-

-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code for keywords
from_versionintPrevious emoji keyword list version
versionintCurrent version of emoji keyword list
keywordsVector<EmojiKeyword>Emojis associated to keywords
-

Type

-

EmojiKeywordsDifference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiLanguage.html b/data/core.telegram.org/constructor/emojiLanguage.html deleted file mode 100644 index 2e16892867..0000000000 --- a/data/core.telegram.org/constructor/emojiLanguage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - emojiLanguage - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiURL.html b/data/core.telegram.org/constructor/emojiURL.html deleted file mode 100644 index f1daa8cf2e..0000000000 --- a/data/core.telegram.org/constructor/emojiURL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - emojiURL - - - - - - - - - - - - - -
- -
-
-
- -

emojiURL

- -

An HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

-

-
emojiURL#a575739d url:string = EmojiURL;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
-

Type

-

EmojiURL

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedChat.html b/data/core.telegram.org/constructor/encryptedChat.html deleted file mode 100644 index 0a9b51649b..0000000000 --- a/data/core.telegram.org/constructor/encryptedChat.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - encryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChat

- -

Encrypted chat

-

-
encryptedChat#fa56ce36 id:int access_hash:long date:int admin_id:int participant_id:int 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_idintChat creator ID
participant_idintID of the second chat participant
g_a_or_bbytesB = g ^ b mod p, if the currently authorized user is the chat's creator,
or A = g ^ a mod p otherwise
See Wikipedia for more info
key_fingerprintlong64-bit fingerprint of received key
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedChatDiscarded.html b/data/core.telegram.org/constructor/encryptedChatDiscarded.html deleted file mode 100644 index 72bbcae260..0000000000 --- a/data/core.telegram.org/constructor/encryptedChatDiscarded.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - encryptedChatDiscarded - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedChatEmpty.html b/data/core.telegram.org/constructor/encryptedChatEmpty.html deleted file mode 100644 index 43c03a7b62..0000000000 --- a/data/core.telegram.org/constructor/encryptedChatEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - encryptedChatEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedChatRequested.html b/data/core.telegram.org/constructor/encryptedChatRequested.html deleted file mode 100644 index e1580a0f91..0000000000 --- a/data/core.telegram.org/constructor/encryptedChatRequested.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - encryptedChatRequested - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatRequested

- -

Request to create an encrypted chat.

-

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

-

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_idintChat creator ID
participant_idintID 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 deleted file mode 100644 index ec8b1ed959..0000000000 --- a/data/core.telegram.org/constructor/encryptedChatWaiting.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - encryptedChatWaiting - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatWaiting

- -

Chat waiting for approval of second participant.

-

-
encryptedChatWaiting#3bf703dc id:int access_hash:long date:int admin_id:int participant_id:int = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintChat ID
access_hashlongChecking sum depending on user ID
dateintDate of chat creation
admin_idintChat creator ID
participant_idintID of second chat participant
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedFile.html b/data/core.telegram.org/constructor/encryptedFile.html deleted file mode 100644 index cac1023d61..0000000000 --- a/data/core.telegram.org/constructor/encryptedFile.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - encryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

encryptedFile

- -

Encrypted file.

-

-
encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID
access_hashlongChecking sum depending on user ID
sizeintFile size in bytes
dc_idintNumber of data centre
key_fingerprintint32-bit fingerprint of key used for file encryption
-

Type

-

EncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedFileEmpty.html b/data/core.telegram.org/constructor/encryptedFileEmpty.html deleted file mode 100644 index 051067e048..0000000000 --- a/data/core.telegram.org/constructor/encryptedFileEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - encryptedFileEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedMessage.html b/data/core.telegram.org/constructor/encryptedMessage.html deleted file mode 100644 index dfca893bb9..0000000000 --- a/data/core.telegram.org/constructor/encryptedMessage.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - encryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

encryptedMessage

- -

Encrypted message.

-

-
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
fileEncryptedFileAttached encrypted file
-

Type

-

EncryptedMessage

-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedMessageService.html b/data/core.telegram.org/constructor/encryptedMessageService.html deleted file mode 100644 index 8b2d38076b..0000000000 --- a/data/core.telegram.org/constructor/encryptedMessageService.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - encryptedMessageService - - - - - - - - - - - - - -
- -
-
-
- -

encryptedMessageService

- -

Encrypted service message

-

-
encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
-

Type

-

EncryptedMessage

-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/error.html b/data/core.telegram.org/constructor/error.html deleted file mode 100644 index e15504ea0a..0000000000 --- a/data/core.telegram.org/constructor/error.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - error - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/exportedMessageLink.html b/data/core.telegram.org/constructor/exportedMessageLink.html deleted file mode 100644 index 85c35030ca..0000000000 --- a/data/core.telegram.org/constructor/exportedMessageLink.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - exportedMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

exportedMessageLink

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/fileHash.html b/data/core.telegram.org/constructor/fileHash.html deleted file mode 100644 index 10060bb4f1..0000000000 --- a/data/core.telegram.org/constructor/fileHash.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - FileHash - - - - - - - - - - - - - -
- -
-
-
- -

FileHash

- -

SHA256 Hash of an uploaded file, to be checked for validity after download

-

-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset from where to start computing SHA-256 hash
limitintLength
hashbytesSHA-256 Hash of file chunk, to be checked for validity after download
-

Type

-

FileHash

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/fileLocation.html b/data/core.telegram.org/constructor/fileLocation.html deleted file mode 100644 index f9bf845025..0000000000 --- a/data/core.telegram.org/constructor/fileLocation.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - fileLocation - - - - - - - - - - - - - -
- -
-
-
- -

fileLocation

- -

File location.

-

-
Constructor schema is available as of layer 86. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintNumber of the data center holding the file
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
-

Type

-

FileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/fileLocationToBeDeprecated.html b/data/core.telegram.org/constructor/fileLocationToBeDeprecated.html deleted file mode 100644 index 48e325ca4e..0000000000 --- a/data/core.telegram.org/constructor/fileLocationToBeDeprecated.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - fileLocationToBeDeprecated - - - - - - - - - - - - - -
- -
-
-
- -

fileLocationToBeDeprecated

- -

Indicates the location of a photo, will be deprecated soon

-

-
fileLocationToBeDeprecated#bc7fc6cd volume_id:long local_id:int = FileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
volume_idlongVolume ID
local_idintLocal ID
-

Type

-

FileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/fileLocationUnavailable.html b/data/core.telegram.org/constructor/fileLocationUnavailable.html deleted file mode 100644 index 361ebf6d88..0000000000 --- a/data/core.telegram.org/constructor/fileLocationUnavailable.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - fileLocationUnavailable - - - - - - - - - - - - - -
- -
-
-
- -

fileLocationUnavailable

- -

File is currently unavailable.

-

-
Constructor schema is available as of layer 98. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
-

Type

-

FileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/folder.html b/data/core.telegram.org/constructor/folder.html deleted file mode 100644 index a3561b8c91..0000000000 --- a/data/core.telegram.org/constructor/folder.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - folder - - - - - - - - - - - - - -
- -
-
-
- -

folder

- -

Folder

-

-
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
autofill_new_broadcastsflags.0?trueAutomatically add new channels to this folder
autofill_public_groupsflags.1?trueAutomatically add joined new public supergroups to this folder
autofill_new_correspondentsflags.2?trueAutomatically add new private chats to this folder
idintFolder ID
titlestringFolder title
photoflags.3?ChatPhotoFolder picture
-

Type

-

Folder

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/folderPeer.html b/data/core.telegram.org/constructor/folderPeer.html deleted file mode 100644 index 16e3e9dc8c..0000000000 --- a/data/core.telegram.org/constructor/folderPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - folderPeer - - - - - - - - - - - - - -
- -
-
-
- -

folderPeer

- -

Peer in a folder

-

-
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerFolder peer info
folder_idintPeer folder ID, for more info click here
-

Type

-

FolderPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/game.html b/data/core.telegram.org/constructor/game.html deleted file mode 100644 index 77710d351c..0000000000 --- a/data/core.telegram.org/constructor/game.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - game - - - - - - - - - - - - - -
- -
-
-
- -

game

- -

Indicates an already sent game

-

-
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongID of the game
access_hashlongAccess hash of the game
short_namestringShort name for the game
titlestringTitle of the game
descriptionstringGame description
photoPhotoGame preview
documentflags.0?DocumentOptional attached document
-

Type

-

Game

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/geoPoint.html b/data/core.telegram.org/constructor/geoPoint.html deleted file mode 100644 index 074d7fdc26..0000000000 --- a/data/core.telegram.org/constructor/geoPoint.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - geoPoint - - - - - - - - - - - - - -
- -
-
-
- -

geoPoint

- -

GeoPoint.

-

-
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
longdoubleLongtitude
latdoubleLatitude
access_hashlongAccess hash
accuracy_radiusflags.0?intThe estimated horizontal accuracy of the location, in meters; as defined by the sender.
-

Type

-

GeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/geoPointEmpty.html b/data/core.telegram.org/constructor/geoPointEmpty.html deleted file mode 100644 index 8c08f7b5eb..0000000000 --- a/data/core.telegram.org/constructor/geoPointEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - geoPointEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/globalPrivacySettings.html b/data/core.telegram.org/constructor/globalPrivacySettings.html deleted file mode 100644 index d2be57e42b..0000000000 --- a/data/core.telegram.org/constructor/globalPrivacySettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - globalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

globalPrivacySettings

- -

Global privacy settings

-

-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
archive_and_mute_new_noncontact_peersflags.0?BoolWhether to archive and mute new chats from non-contacts
-

Type

-

GlobalPrivacySettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.appUpdate b/data/core.telegram.org/constructor/help.appUpdate deleted file mode 100644 index fdbaa74fb7..0000000000 --- a/data/core.telegram.org/constructor/help.appUpdate +++ /dev/null @@ -1,185 +0,0 @@ - - - - - help.appUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.appUpdate

- -

An update is available for the application.

-

-
help.appUpdate#1da7158f flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string = 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
-

Type

-

help.AppUpdate

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.countriesList b/data/core.telegram.org/constructor/help.countriesList deleted file mode 100644 index d1c1d041a5..0000000000 --- a/data/core.telegram.org/constructor/help.countriesList +++ /dev/null @@ -1,155 +0,0 @@ - - - - - help.countriesList - - - - - - - - - - - - - -
- -
-
-
- -

help.countriesList

- -

Name, ISO code, localized name and phone codes/patterns of all available countries

-

-
help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countriesVector<help.Country>Name, ISO code, localized name and phone codes/patterns of all available countries
hashintHash for pagination, for more info click here
-

Type

-

help.CountriesList

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.countriesListNotModified b/data/core.telegram.org/constructor/help.countriesListNotModified deleted file mode 100644 index cccd39dd0d..0000000000 --- a/data/core.telegram.org/constructor/help.countriesListNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.countriesListNotModified - - - - - - - - - - - - - -
- -
-
-
- -

help.countriesListNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.country b/data/core.telegram.org/constructor/help.country deleted file mode 100644 index 34e35e6976..0000000000 --- a/data/core.telegram.org/constructor/help.country +++ /dev/null @@ -1,172 +0,0 @@ - - - - - help.country - - - - - - - - - - - - - -
- -
-
-
- -

help.country

- -

Name, ISO code, localized name and phone codes/patterns of a specific country

-

-
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
hiddenflags.0?trueWhether this country should not be shown in the list
iso2stringISO code of country
default_namestringName of the country in the country's language
nameflags.1?stringName of the country in the user's language, if different from the original name
country_codesVector<help.CountryCode>Phone codes/patterns
-

Type

-

help.Country

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.countryCode b/data/core.telegram.org/constructor/help.countryCode deleted file mode 100644 index 685cf34a20..0000000000 --- a/data/core.telegram.org/constructor/help.countryCode +++ /dev/null @@ -1,162 +0,0 @@ - - - - - help.countryCode - - - - - - - - - - - - - -
- -
-
-
- -

help.countryCode

- -

Country code and phone number pattern of a specific country

-

-
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
country_codestringISO country code
prefixesflags.0?Vector<string>Possible phone prefixes
patternsflags.1?Vector<string>Phone patterns: for example, XXX XXX XXX
-

Type

-

help.CountryCode

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.deepLinkInfo b/data/core.telegram.org/constructor/help.deepLinkInfo deleted file mode 100644 index 0ec33aaa43..0000000000 --- a/data/core.telegram.org/constructor/help.deepLinkInfo +++ /dev/null @@ -1,165 +0,0 @@ - - - - - help.deepLinkInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.deepLinkInfo

- -

Deep linking info

-

-
help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
update_appflags.0?trueAn update of the app is required to parse this link
messagestringMessage to show to the user
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
-

Type

-

help.DeepLinkInfo

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.deepLinkInfoEmpty b/data/core.telegram.org/constructor/help.deepLinkInfoEmpty deleted file mode 100644 index af5fc6beb9..0000000000 --- a/data/core.telegram.org/constructor/help.deepLinkInfoEmpty +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.deepLinkInfoEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.inviteText b/data/core.telegram.org/constructor/help.inviteText deleted file mode 100644 index 4035ff9afa..0000000000 --- a/data/core.telegram.org/constructor/help.inviteText +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.inviteText - - - - - - - - - - - - - -
- -
-
-
- -

help.inviteText

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.noAppUpdate b/data/core.telegram.org/constructor/help.noAppUpdate deleted file mode 100644 index 8a4fd1fc2e..0000000000 --- a/data/core.telegram.org/constructor/help.noAppUpdate +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.noAppUpdate - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.passportConfig b/data/core.telegram.org/constructor/help.passportConfig deleted file mode 100644 index 385fa7a242..0000000000 --- a/data/core.telegram.org/constructor/help.passportConfig +++ /dev/null @@ -1,156 +0,0 @@ - - - - - help.passportConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.passportConfig

- -

Telegram passport configuration

-

-
help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
countries_langsDataJSONLocalization
-

Type

-

help.PassportConfig

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.passportConfigNotModified b/data/core.telegram.org/constructor/help.passportConfigNotModified deleted file mode 100644 index 6aebd7523e..0000000000 --- a/data/core.telegram.org/constructor/help.passportConfigNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.passportConfigNotModified - - - - - - - - - - - - - -
- -
-
-
- -

help.passportConfigNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.promoData b/data/core.telegram.org/constructor/help.promoData deleted file mode 100644 index 19d69273dd..0000000000 --- a/data/core.telegram.org/constructor/help.promoData +++ /dev/null @@ -1,182 +0,0 @@ - - - - - help.promoData - - - - - - - - - - - - - -
- -
-
-
- -

help.promoData

- -

MTProxy/Public Service Announcement information

-

-
help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
proxyflags.0?trueMTProxy-related channel
expiresintExpiry of PSA/MTProxy info
peerPeerMTProxy/PSA peer
chatsVector<Chat>Chat info
usersVector<User>User info
psa_typeflags.1?stringPSA type
psa_messageflags.2?stringPSA message
-

Type

-

help.PromoData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.promoDataEmpty b/data/core.telegram.org/constructor/help.promoDataEmpty deleted file mode 100644 index bdc2f99481..0000000000 --- a/data/core.telegram.org/constructor/help.promoDataEmpty +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.promoDataEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.promoDataEmpty

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.recentMeUrls b/data/core.telegram.org/constructor/help.recentMeUrls deleted file mode 100644 index a8921bd018..0000000000 --- a/data/core.telegram.org/constructor/help.recentMeUrls +++ /dev/null @@ -1,157 +0,0 @@ - - - - - help.recentMeUrls - - - - - - - - - - - - - -
- -
-
-
- -

help.recentMeUrls

- -

Recent t.me URLs

-

-
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlsVector<RecentMeUrl>URLs
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

help.RecentMeUrls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.support b/data/core.telegram.org/constructor/help.support deleted file mode 100644 index 8f83bab3a7..0000000000 --- a/data/core.telegram.org/constructor/help.support +++ /dev/null @@ -1,152 +0,0 @@ - - - - - help.support - - - - - - - - - - - - - -
- -
-
-
- -

help.support

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.supportName b/data/core.telegram.org/constructor/help.supportName deleted file mode 100644 index 8bfc1babd4..0000000000 --- a/data/core.telegram.org/constructor/help.supportName +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.supportName - - - - - - - - - - - - - -
- -
-
-
- -

help.supportName

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.termsOfService b/data/core.telegram.org/constructor/help.termsOfService deleted file mode 100644 index 5cea618eb5..0000000000 --- a/data/core.telegram.org/constructor/help.termsOfService +++ /dev/null @@ -1,175 +0,0 @@ - - - - - help.termsOfService - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfService

- -

Info about the latest telegram Terms Of Service

-

-
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?trueWhether a prompt must be showed to the user, in order to accept the new terms.
idDataJSONID of the new terms
textstringText of the new terms
entitiesVector<MessageEntity>Message entities for styled text
min_age_confirmflags.1?intMinimum age required to sign up to telegram, the user must confirm that they is older than the minimum age.
-

Type

-

help.TermsOfService

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.termsOfServiceUpdate b/data/core.telegram.org/constructor/help.termsOfServiceUpdate deleted file mode 100644 index 0653940f6e..0000000000 --- a/data/core.telegram.org/constructor/help.termsOfServiceUpdate +++ /dev/null @@ -1,157 +0,0 @@ - - - - - help.termsOfServiceUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfServiceUpdate

- -

Info about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"

-

-
help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
terms_of_servicehelp.TermsOfServiceNew terms of service
-

Type

-

help.TermsOfServiceUpdate

-

Related pages

-

help.getTermsOfServiceUpdate

-

Look for updates of telegram's terms of service

-

account.deleteAccount

-

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty b/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty deleted file mode 100644 index dfd91f34c2..0000000000 --- a/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.termsOfServiceUpdateEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfServiceUpdateEmpty

- -

No changes were made to telegram's terms of service

-

-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
-

Type

-

help.TermsOfServiceUpdate

-

Related pages

-

help.getTermsOfServiceUpdate

-

Look for updates of telegram's terms of service

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.userInfo b/data/core.telegram.org/constructor/help.userInfo deleted file mode 100644 index 139b469803..0000000000 --- a/data/core.telegram.org/constructor/help.userInfo +++ /dev/null @@ -1,165 +0,0 @@ - - - - - help.userInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.userInfo

- -

Internal use

-

-
help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagestringInfo
entitiesVector<MessageEntity>Message entities for styled text
authorstringAuthor
dateintDate
-

Type

-

help.UserInfo

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.userInfoEmpty b/data/core.telegram.org/constructor/help.userInfoEmpty deleted file mode 100644 index fc3a30bfa4..0000000000 --- a/data/core.telegram.org/constructor/help.userInfoEmpty +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.userInfoEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/highScore.html b/data/core.telegram.org/constructor/highScore.html deleted file mode 100644 index bd216b1db1..0000000000 --- a/data/core.telegram.org/constructor/highScore.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - highScore - - - - - - - - - - - - - -
- -
-
-
- -

highScore

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/importedContact.html b/data/core.telegram.org/constructor/importedContact.html deleted file mode 100644 index fcf6fa35b1..0000000000 --- a/data/core.telegram.org/constructor/importedContact.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - importedContact - - - - - - - - - - - - - -
- -
-
-
- -

importedContact

- -

Successfully imported contact.

-

-
importedContact#d0028438 user_id:int client_id:long = ImportedContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser identifier
client_idlongThe contact's client identifier (passed to one of the InputContact constructors)
-

Type

-

ImportedContact

-

Related pages

-

InputContact

-

Object defines a contact from the user's phonebook.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inlineBotSwitchPM.html b/data/core.telegram.org/constructor/inlineBotSwitchPM.html deleted file mode 100644 index 1fe76b46ad..0000000000 --- a/data/core.telegram.org/constructor/inlineBotSwitchPM.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inlineBotSwitchPM - - - - - - - - - - - - - -
- -
-
-
- -

inlineBotSwitchPM

- -

The bot requested the user to message him in private

-

-
inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textstringText for the button that switches the user to a private chat with the bot and sends the bot a start message with the parameter start_parameter (can be empty)
start_paramstringThe parameter for the /start parameter
-

Type

-

InlineBotSwitchPM

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputAppEvent.html b/data/core.telegram.org/constructor/inputAppEvent.html deleted file mode 100644 index 4ce3bc5fd5..0000000000 --- a/data/core.telegram.org/constructor/inputAppEvent.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputAppEvent - - - - - - - - - - - - - -
- -
-
-
- -

inputAppEvent

- -

Event that occured in the application.

-

-
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
timedoubleClient's exact timestamp for the event
typestringType of event
peerlongArbitrary numeric value for more convenient selection of certain event types, or events referring to a certain object
dataJSONValueDetails of the event
-

Type

-

InputAppEvent

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageGame.html b/data/core.telegram.org/constructor/inputBotInlineMessageGame.html deleted file mode 100644 index 71357ea049..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageGame.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputBotInlineMessageGame - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageGame

- -

A game

-

-
inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageID.html b/data/core.telegram.org/constructor/inputBotInlineMessageID.html deleted file mode 100644 index cdbb7a33b8..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageID.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputBotInlineMessageID - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageID

- -

Represents a sent inline message from the perspective of a bot

-

-
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
access_hashlongAccess hash of message
-

Type

-

InputBotInlineMessageID

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html deleted file mode 100644 index 3e07227ed5..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputBotInlineMessageMediaAuto - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaAuto

- -

A media

-

-
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html deleted file mode 100644 index bb271462af..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputBotInlineMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaContact

- -

A contact

-

-
inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html deleted file mode 100644 index ca05cefc23..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - inputBotInlineMessageMediaGeo - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaGeo

- -

Geolocation

-

-
inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodflags.1?intValidity period
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
reply_markupflags.2?ReplyMarkupReply markup for bot/inline keyboards
-

Type

-

InputBotInlineMessage

-

Related pages

-

Live geolocation

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html deleted file mode 100644 index bbc302623a..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - inputBotInlineMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaVenue

- -

Venue

-

-
inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageText.html b/data/core.telegram.org/constructor/inputBotInlineMessageText.html deleted file mode 100644 index c94963ea67..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageText.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - inputBotInlineMessageText - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageText

- -

Simple text message

-

-
inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringMessage
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineResult.html b/data/core.telegram.org/constructor/inputBotInlineResult.html deleted file mode 100644 index 6ef051cb0c..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineResult.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - inputBotInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResult

- -

An inline bot result

-

-
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringID of result
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of result
thumbflags.4?InputWebDocumentThumbnail for result
contentflags.5?InputWebDocumentResult contents
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineResultDocument.html b/data/core.telegram.org/constructor/inputBotInlineResultDocument.html deleted file mode 100644 index 99c3bba4c9..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineResultDocument.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - inputBotInlineResultDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultDocument

- -

Document (media of any type except for photos)

-

-
inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
documentInputDocumentDocument to send
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineResultGame.html b/data/core.telegram.org/constructor/inputBotInlineResultGame.html deleted file mode 100644 index d8f81c0794..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineResultGame.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputBotInlineResultGame - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultGame

- -

Game

-

-
inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringResult ID
short_namestringGame short name
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html b/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html deleted file mode 100644 index 027673aebe..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - inputBotInlineResultPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultPhoto

- -

Photo

-

-
inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringResult ID
typestringResult type (see bot API docs)
photoInputPhotoPhoto to send
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChannel.html b/data/core.telegram.org/constructor/inputChannel.html deleted file mode 100644 index fc4ca89d96..0000000000 --- a/data/core.telegram.org/constructor/inputChannel.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputChannel - - - - - - - - - - - - - -
- -
-
-
- -

inputChannel

- -

Represents a channel

-

-
inputChannel#afeb712e channel_id:int access_hash:long = InputChannel;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel ID
access_hashlongAccess hash taken from the channel constructor
-

Type

-

InputChannel

-

Related pages

-

channel

-

Channel/supergroup info

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChannelEmpty.html b/data/core.telegram.org/constructor/inputChannelEmpty.html deleted file mode 100644 index bfac096be5..0000000000 --- a/data/core.telegram.org/constructor/inputChannelEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputChannelEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChannelFromMessage.html b/data/core.telegram.org/constructor/inputChannelFromMessage.html deleted file mode 100644 index 12a755d56f..0000000000 --- a/data/core.telegram.org/constructor/inputChannelFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputChannelFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputChannelFromMessage

- -

Defines a min channel that was seen in a certain message of a certain chat.

-

-
inputChannelFromMessage#2a286531 peer:InputPeer msg_id:int channel_id:int = InputChannel;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the channel was seen
msg_idintThe message ID in the chat where the channel was seen
channel_idintThe 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 deleted file mode 100644 index 0667230122..0000000000 --- a/data/core.telegram.org/constructor/inputChatPhoto.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputChatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputChatPhoto

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChatPhotoEmpty.html b/data/core.telegram.org/constructor/inputChatPhotoEmpty.html deleted file mode 100644 index 0e41004e2d..0000000000 --- a/data/core.telegram.org/constructor/inputChatPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputChatPhotoEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChatUploadedPhoto.html b/data/core.telegram.org/constructor/inputChatUploadedPhoto.html deleted file mode 100644 index bf008426c4..0000000000 --- a/data/core.telegram.org/constructor/inputChatUploadedPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputChatUploadedPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputChatUploadedPhoto

- -

New photo to be set as group profile photo.

-

-
inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts using the method upload.saveFilePart
videoflags.1?InputFileSquare video for animated profile picture
video_start_tsflags.2?doubleTimestamp that should be shown as static preview to the user (seconds)
-

Type

-

InputChatPhoto

-

Related pages

-

upload.saveFilePart

-

Saves a part of file for futher sending to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html b/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html deleted file mode 100644 index 2851845617..0000000000 --- a/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputCheckPasswordEmpty - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputCheckPasswordSRP.html b/data/core.telegram.org/constructor/inputCheckPasswordSRP.html deleted file mode 100644 index b7c2204a6e..0000000000 --- a/data/core.telegram.org/constructor/inputCheckPasswordSRP.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputCheckPasswordSRP - - - - - - - - - - - - - -
- -
-
-
- -

inputCheckPasswordSRP

- -

Constructor for checking the validity of a 2FA SRP password (see SRP)

-

-
inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
srp_idlongSRP ID
AbytesA parameter (see SRP)
M1bytesM1 parameter (see SRP)
-

Type

-

InputCheckPasswordSRP

-

Related pages

-

Two-factor authentication

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputClientProxy.html b/data/core.telegram.org/constructor/inputClientProxy.html deleted file mode 100644 index a2dbe17739..0000000000 --- a/data/core.telegram.org/constructor/inputClientProxy.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - inputClientProxy - - - - - - - - - - - - - -
- -
-
-
- -

inputClientProxy

- -

Info about an MTProxy used to connect.

-

-
inputClientProxy#75588b3f address:string port:int = InputClientProxy;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
addressstringProxy address
portintProxy port
-

Type

-

InputClientProxy

-

Related pages

-

MTProto transports

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDialogPeer.html b/data/core.telegram.org/constructor/inputDialogPeer.html deleted file mode 100644 index 8115240d8b..0000000000 --- a/data/core.telegram.org/constructor/inputDialogPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputDialogPeer - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDialogPeerFolder.html b/data/core.telegram.org/constructor/inputDialogPeerFolder.html deleted file mode 100644 index 1171e953b5..0000000000 --- a/data/core.telegram.org/constructor/inputDialogPeerFolder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputDialogPeerFolder - - - - - - - - - - - - - -
- -
-
-
- -

inputDialogPeerFolder

- -

All peers in a peer folder

-

-
inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Type

-

InputDialogPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDocument.html b/data/core.telegram.org/constructor/inputDocument.html deleted file mode 100644 index 2a0a466ac0..0000000000 --- a/data/core.telegram.org/constructor/inputDocument.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputDocument

- -

Defines a video for subsequent interaction.

-

-
inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
-

Type

-

InputDocument

-

Related pages

-

document

-

Document

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDocumentEmpty.html b/data/core.telegram.org/constructor/inputDocumentEmpty.html deleted file mode 100644 index dec99d82eb..0000000000 --- a/data/core.telegram.org/constructor/inputDocumentEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputDocumentEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDocumentFileLocation.html b/data/core.telegram.org/constructor/inputDocumentFileLocation.html deleted file mode 100644 index fcfea2dc5d..0000000000 --- a/data/core.telegram.org/constructor/inputDocumentFileLocation.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - inputDocumentFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputDocumentFileLocation

- -

Document location (video, voice, audio, basically every type except photo)

-

-
inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
thumb_sizestringThumbnail size to download the thumbnail
-

Type

-

InputFileLocation

-

Related pages

-

document

-

Document

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedChat.html b/data/core.telegram.org/constructor/inputEncryptedChat.html deleted file mode 100644 index a34e8990f4..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedChat.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - inputEncryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedChat

- -

Creates an encrypted chat.

-

-
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
access_hashlongChecking sum from constructor encryptedChat, encryptedChatWaiting or encryptedChatRequested
-

Type

-

InputEncryptedChat

-

Related pages

-

encryptedChat

-

Encrypted chat

-

encryptedChatWaiting

-

Chat waiting for approval of second participant.

-

encryptedChatRequested

-

Request to create an encrypted chat.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFile.html b/data/core.telegram.org/constructor/inputEncryptedFile.html deleted file mode 100644 index f4a1af1ee6..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFile.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFile

- -

Sets forwarded encrypted file for attachment.

-

-
inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID, value of id parameter from encryptedFile
access_hashlongChecking sum, value of access_hash parameter from encryptedFile
-

Type

-

InputEncryptedFile

-

Related pages

-

encryptedFile

-

Encrypted file.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html b/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html deleted file mode 100644 index eaabaa1db6..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputEncryptedFileBigUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileBigUploaded

- -

Assigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.

-

-
inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of saved parts
key_fingerprintint32-bit imprint of the key used to encrypt the file
-

Type

-

InputEncryptedFile

-

Related pages

-

upload.saveBigFilePart

-

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html b/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html deleted file mode 100644 index 5a11560a5b..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputEncryptedFileEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFileLocation.html b/data/core.telegram.org/constructor/inputEncryptedFileLocation.html deleted file mode 100644 index ccc51c78c9..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFileLocation.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputEncryptedFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileLocation

- -

Location of encrypted secret chat file.

-

-
inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID, id parameter value from encryptedFile
access_hashlongChecksum, access_hash parameter value from encryptedFile
-

Type

-

InputFileLocation

-

Related pages

-

encryptedFile

-

Encrypted file.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html b/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html deleted file mode 100644 index 40deccc4db..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputEncryptedFileUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileUploaded

- -

Sets new encrypted file saved by parts using upload.saveFilePart method.

-

-
inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file ID created by clien
partsintNumber of saved parts
md5_checksumstringIn case md5-HASH of the (already encrypted) file was transmitted, file content will be checked prior to use
key_fingerprintint32-bit fingerprint of the key used to encrypt a file
-

Type

-

InputEncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputFile.html b/data/core.telegram.org/constructor/inputFile.html deleted file mode 100644 index 814583c2b2..0000000000 --- a/data/core.telegram.org/constructor/inputFile.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputFile - - - - - - - - - - - - - -
- -
-
-
- -

inputFile

- -

Defines a file saved in parts using the method upload.saveFilePart.

-

-
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file identifier created by the client
partsintNumber of parts saved
namestringFull name of the file
md5_checksumstringIn case the file's md5-hash was passed, contents of the file will be checked prior to use
-

Type

-

InputFile

-

Related pages

-

upload.saveFilePart

-

Saves a part of file for futher sending to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputFileBig.html b/data/core.telegram.org/constructor/inputFileBig.html deleted file mode 100644 index 67cd90696b..0000000000 --- a/data/core.telegram.org/constructor/inputFileBig.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputFileBig - - - - - - - - - - - - - -
- -
-
-
- -

inputFileBig

- -

Assigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.

-

-
inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of parts saved
namestringFull file name
-

Type

-

InputFile

-

Related pages

-

upload.saveBigFilePart

-

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputFileLocation.html b/data/core.telegram.org/constructor/inputFileLocation.html deleted file mode 100644 index b629d88554..0000000000 --- a/data/core.telegram.org/constructor/inputFileLocation.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputFileLocation

- -

DEPRECATED location of a photo

-

-
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
volume_idlongServer volume
local_idintFile identifier
secretlongCheck sum to access the file
file_referencebytesFile reference
-

Type

-

InputFileLocation

-

Related pages

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputFolderPeer.html b/data/core.telegram.org/constructor/inputFolderPeer.html deleted file mode 100644 index 8dc9163264..0000000000 --- a/data/core.telegram.org/constructor/inputFolderPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputFolderPeer - - - - - - - - - - - - - -
- -
-
-
- -

inputFolderPeer

- -

Peer in a folder

-

-
inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
folder_idintPeer folder ID, for more info click here
-

Type

-

InputFolderPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGameID.html b/data/core.telegram.org/constructor/inputGameID.html deleted file mode 100644 index d4c58c043c..0000000000 --- a/data/core.telegram.org/constructor/inputGameID.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputGameID - - - - - - - - - - - - - -
- -
-
-
- -

inputGameID

- -

Indicates an already sent game

-

-
inputGameID#32c3e77 id:long access_hash:long = InputGame;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlonggame ID from Game constructor
access_hashlongaccess hash from Game constructor
-

Type

-

InputGame

-

Related pages

-

Game

-

Indicates an already sent game

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGameShortName.html b/data/core.telegram.org/constructor/inputGameShortName.html deleted file mode 100644 index 189efb94ae..0000000000 --- a/data/core.telegram.org/constructor/inputGameShortName.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputGameShortName - - - - - - - - - - - - - -
- -
-
-
- -

inputGameShortName

- -

Game by short name

-

-
inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
bot_idInputUserThe bot that provides the game
short_namestringThe game's short name
-

Type

-

InputGame

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGeoPoint.html b/data/core.telegram.org/constructor/inputGeoPoint.html deleted file mode 100644 index e3daec7d01..0000000000 --- a/data/core.telegram.org/constructor/inputGeoPoint.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputGeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

inputGeoPoint

- -

Defines a GeoPoint by its coordinates.

-

-
inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
latdoubleLatitide
longdoubleLongtitude
accuracy_radiusflags.0?intThe estimated horizontal accuracy of the location, in meters; as defined by the sender.
-

Type

-

InputGeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGeoPointEmpty.html b/data/core.telegram.org/constructor/inputGeoPointEmpty.html deleted file mode 100644 index 57bbf29f9a..0000000000 --- a/data/core.telegram.org/constructor/inputGeoPointEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputGeoPointEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html b/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html deleted file mode 100644 index 573e612684..0000000000 --- a/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - inputKeyboardButtonUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

inputKeyboardButtonUrlAuth

- -

Button to request a user to authorize via URL using Seamless Telegram Login.

-

-
inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueSet this flag to request the permission for your bot to send messages to the user.
textstringButton text
fwd_textflags.1?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.
NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
botInputUserUsername of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
-

Type

-

KeyboardButton

-

Related pages

-

Telegram Login Widget

-

messages.acceptUrlAuth

-

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaContact.html b/data/core.telegram.org/constructor/inputMediaContact.html deleted file mode 100644 index 615e6798d4..0000000000 --- a/data/core.telegram.org/constructor/inputMediaContact.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaContact

- -

Phonebook contact

-

-
inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringContact vcard
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaDice.html b/data/core.telegram.org/constructor/inputMediaDice.html deleted file mode 100644 index 9c1bf04e89..0000000000 --- a/data/core.telegram.org/constructor/inputMediaDice.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputMediaDice - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDice

- -

Send a dice-based animated sticker

-

-
inputMediaDice#e66fbf7b emoticon:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
-

Type

-

InputMedia

-

Related pages

-

Dice

-

Telegram supports sending animated dice emojis.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaDocument.html b/data/core.telegram.org/constructor/inputMediaDocument.html deleted file mode 100644 index 87b355e15d..0000000000 --- a/data/core.telegram.org/constructor/inputMediaDocument.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDocument

- -

Forwarded document

-

-
inputMediaDocument#23ab23d2 flags:# id:InputDocument ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idInputDocumentThe document to be forwarded.
ttl_secondsflags.0?intTime to live of self-destructing document
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaDocumentExternal.html b/data/core.telegram.org/constructor/inputMediaDocumentExternal.html deleted file mode 100644 index 8cb0f3f012..0000000000 --- a/data/core.telegram.org/constructor/inputMediaDocumentExternal.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaDocumentExternal - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDocumentExternal

- -

Document that will be downloaded by the telegram servers

-

-
inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the document
ttl_secondsflags.0?intSelf-destruct time to live of document
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaEmpty.html b/data/core.telegram.org/constructor/inputMediaEmpty.html deleted file mode 100644 index db9ed3ea93..0000000000 --- a/data/core.telegram.org/constructor/inputMediaEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMediaEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaGame.html b/data/core.telegram.org/constructor/inputMediaGame.html deleted file mode 100644 index 255e2159f6..0000000000 --- a/data/core.telegram.org/constructor/inputMediaGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMediaGame - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaGeoLive.html b/data/core.telegram.org/constructor/inputMediaGeoLive.html deleted file mode 100644 index e849836184..0000000000 --- a/data/core.telegram.org/constructor/inputMediaGeoLive.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - inputMediaGeoLive - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaGeoLive

- -

Live geolocation

-

-
inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
stoppedflags.0?trueWhether sending of the geolocation was stopped
geo_pointInputGeoPointCurrent geolocation
headingflags.2?intFor live locations, a direction in which the location moves, in degrees; 1-360.
periodflags.1?intValidity period of the current location
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
-

Type

-

InputMedia

-

Related pages

-

Live geolocation

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaGeoPoint.html b/data/core.telegram.org/constructor/inputMediaGeoPoint.html deleted file mode 100644 index 7be17f2c2c..0000000000 --- a/data/core.telegram.org/constructor/inputMediaGeoPoint.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMediaGeoPoint - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaInvoice.html b/data/core.telegram.org/constructor/inputMediaInvoice.html deleted file mode 100644 index fe818423e1..0000000000 --- a/data/core.telegram.org/constructor/inputMediaInvoice.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - inputMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaInvoice

- -

Generated invoice of a bot payment

-

-
inputMediaInvoice#f4e096c3 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param: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_paramstringStart parameter
-

Type

-

InputMedia

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaPhoto.html b/data/core.telegram.org/constructor/inputMediaPhoto.html deleted file mode 100644 index 2014ef96fd..0000000000 --- a/data/core.telegram.org/constructor/inputMediaPhoto.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaPhoto

- -

Forwarded photo

-

-
inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idInputPhotoPhoto to be forwarded
ttl_secondsflags.0?intTime to live in seconds of self-destructing photo
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaPhotoExternal.html b/data/core.telegram.org/constructor/inputMediaPhotoExternal.html deleted file mode 100644 index 64da98b1f8..0000000000 --- a/data/core.telegram.org/constructor/inputMediaPhotoExternal.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaPhotoExternal - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaPhotoExternal

- -

New photo that will be uploaded by the server using the specified URL

-

-
inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the photo
ttl_secondsflags.0?intSelf-destruct time to live of photo
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaPoll.html b/data/core.telegram.org/constructor/inputMediaPoll.html deleted file mode 100644 index 6d6240baf7..0000000000 --- a/data/core.telegram.org/constructor/inputMediaPoll.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - inputMediaPoll - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaPoll

- -

A poll

-

-
inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pollPollThe poll to send
correct_answersflags.0?Vector<bytes>Correct answer IDs (for quiz polls)
solutionflags.1?stringExplanation of quiz solution
solution_entitiesflags.1?Vector<MessageEntity>Message entities for styled text
-

Type

-

InputMedia

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaUploadedDocument.html b/data/core.telegram.org/constructor/inputMediaUploadedDocument.html deleted file mode 100644 index d982af80c9..0000000000 --- a/data/core.telegram.org/constructor/inputMediaUploadedDocument.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - inputMediaUploadedDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaUploadedDocument

- -

New document

-

-
inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
nosound_videoflags.3?trueWhether the specified document is a video file with no audio tracks (a GIF animation (even as MPEG4), for example)
force_fileflags.4?trueForce the media file to be uploaded as document
fileInputFileThe uploaded file
thumbflags.2?InputFileThumbnail of the document, uploaded as for the file
mime_typestringMIME type of document
attributesVector<DocumentAttribute>Attributes that specify the type of the document (video, audio, voice, sticker, etc.)
stickersflags.0?Vector<InputDocument>Attached stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing document
-

Type

-

InputMedia

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html b/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html deleted file mode 100644 index b206754e1d..0000000000 --- a/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputMediaUploadedPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaUploadedPhoto

- -

Photo

-

-
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileThe uploaded file
stickersflags.0?Vector<InputDocument>Attached mask stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing photo
-

Type

-

InputMedia

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html b/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html deleted file mode 100644 index 39fffd0454..0000000000 --- a/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - inputMediaUploadedThumbDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaUploadedThumbDocument

- -

New document with a thumbnail.

-

-
Constructor schema is available as of layer 22. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
fileInputFileDocument, saved in parts by using the methods upload.saveFilePart or upload.saveBigFilePart
thumbInputFileThumbnail file, saved in parts by using upload.saveFilePart
file_namestringFile name with extension
mime_typestringFile MIME-type
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaVenue.html b/data/core.telegram.org/constructor/inputMediaVenue.html deleted file mode 100644 index a47520c245..0000000000 --- a/data/core.telegram.org/constructor/inputMediaVenue.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaVenue

- -

Can be used to send a venue geolocation.

-

-
inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringPhysical address of the venue
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessageCallbackQuery.html b/data/core.telegram.org/constructor/inputMessageCallbackQuery.html deleted file mode 100644 index fc2edaba24..0000000000 --- a/data/core.telegram.org/constructor/inputMessageCallbackQuery.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputMessageCallbackQuery - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageCallbackQuery

- -

Used by bots for fetching information about the message that originated a callback query

-

-
inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID
query_idlongCallback query ID
-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessageEntityMentionName.html b/data/core.telegram.org/constructor/inputMessageEntityMentionName.html deleted file mode 100644 index 317716c1df..0000000000 --- a/data/core.telegram.org/constructor/inputMessageEntityMentionName.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputMessageEntityMentionName - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageEntityMentionName

- -

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

-

-
inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idInputUserIdentifier of the user that was mentioned
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

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

-

messageEntityMentionName

-

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessageID.html b/data/core.telegram.org/constructor/inputMessageID.html deleted file mode 100644 index 22913e6fa8..0000000000 --- a/data/core.telegram.org/constructor/inputMessageID.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMessageID - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagePinned.html b/data/core.telegram.org/constructor/inputMessagePinned.html deleted file mode 100644 index 9a78971329..0000000000 --- a/data/core.telegram.org/constructor/inputMessagePinned.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagePinned - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessageReplyTo.html b/data/core.telegram.org/constructor/inputMessageReplyTo.html deleted file mode 100644 index dad53bc175..0000000000 --- a/data/core.telegram.org/constructor/inputMessageReplyTo.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMessageReplyTo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageReplyTo

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html b/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html deleted file mode 100644 index cbcc4ad9b8..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterChatPhotos - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterChatPhotos

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterContacts.html b/data/core.telegram.org/constructor/inputMessagesFilterContacts.html deleted file mode 100644 index c57c223963..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterContacts - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterContacts

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterDocument.html b/data/core.telegram.org/constructor/inputMessagesFilterDocument.html deleted file mode 100644 index 179af182d3..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterDocument.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterDocument

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html b/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html deleted file mode 100644 index d1a506c9fe..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterGeo.html b/data/core.telegram.org/constructor/inputMessagesFilterGeo.html deleted file mode 100644 index 3377fea746..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterGeo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterGeo - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterGif.html b/data/core.telegram.org/constructor/inputMessagesFilterGif.html deleted file mode 100644 index bc12e26303..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterGif.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterGif - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterMusic.html b/data/core.telegram.org/constructor/inputMessagesFilterMusic.html deleted file mode 100644 index 7678d37b96..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterMusic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterMusic - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterMusic

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html b/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html deleted file mode 100644 index 147838e562..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inputMessagesFilterMyMentions - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterMyMentions

- -

Return only messages where the current user was mentioned.

-

-
inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

-

Related pages

-

Mentions

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html b/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html deleted file mode 100644 index 6f5eece17a..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputMessagesFilterPhoneCalls - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhoneCalls

- -

Return only phone calls

-

-
inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
missedflags.0?trueReturn only missed phone calls
-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html deleted file mode 100644 index 20a4944a46..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterPhotoVideo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhotoVideo

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html b/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html deleted file mode 100644 index 748934af2f..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterPhotos - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhotos

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPinned.html b/data/core.telegram.org/constructor/inputMessagesFilterPinned.html deleted file mode 100644 index d7c425b661..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterPinned.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterPinned - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html deleted file mode 100644 index a6e086efce..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterRoundVideo - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html b/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html deleted file mode 100644 index d778aff556..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterRoundVoice - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterRoundVoice

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterUrl.html b/data/core.telegram.org/constructor/inputMessagesFilterUrl.html deleted file mode 100644 index be3c935f14..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterUrl.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterUrl - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterVideo.html deleted file mode 100644 index 65904b89b5..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterVideo - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterVoice.html b/data/core.telegram.org/constructor/inputMessagesFilterVoice.html deleted file mode 100644 index 3524915f17..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterVoice.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterVoice - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterVoice

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputNotifyBroadcasts.html b/data/core.telegram.org/constructor/inputNotifyBroadcasts.html deleted file mode 100644 index c7640574e4..0000000000 --- a/data/core.telegram.org/constructor/inputNotifyBroadcasts.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inputNotifyBroadcasts - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyBroadcasts

- -

All channels

-

-
inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputNotifyPeer

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputNotifyChats.html b/data/core.telegram.org/constructor/inputNotifyChats.html deleted file mode 100644 index d459248c43..0000000000 --- a/data/core.telegram.org/constructor/inputNotifyChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputNotifyChats - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputNotifyPeer.html b/data/core.telegram.org/constructor/inputNotifyPeer.html deleted file mode 100644 index f56aee94b4..0000000000 --- a/data/core.telegram.org/constructor/inputNotifyPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputNotifyPeer - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyPeer

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputNotifyUsers.html b/data/core.telegram.org/constructor/inputNotifyUsers.html deleted file mode 100644 index de9e270113..0000000000 --- a/data/core.telegram.org/constructor/inputNotifyUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputNotifyUsers - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPaymentCredentials.html b/data/core.telegram.org/constructor/inputPaymentCredentials.html deleted file mode 100644 index cef314919d..0000000000 --- a/data/core.telegram.org/constructor/inputPaymentCredentials.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputPaymentCredentials - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentials

- -

Payment credentials

-

-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
saveflags.0?trueSave payment credential for future use
dataDataJSONPayment credentials
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsAndroidPay.html b/data/core.telegram.org/constructor/inputPaymentCredentialsAndroidPay.html deleted file mode 100644 index 40fd3588ca..0000000000 --- a/data/core.telegram.org/constructor/inputPaymentCredentialsAndroidPay.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputPaymentCredentialsAndroidPay - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsAndroidPay

- -

Android pay payment credentials

-

-
inputPaymentCredentialsAndroidPay#ca05d50e payment_token:DataJSON google_transaction_id:string = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
payment_tokenDataJSONAndroid pay payment token
google_transaction_idstringGoogle transaction ID
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html b/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html deleted file mode 100644 index ec4f299d4c..0000000000 --- a/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPaymentCredentialsApplePay - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsApplePay

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html b/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html deleted file mode 100644 index bc6e70b76f..0000000000 --- a/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputPaymentCredentialsSaved - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsSaved

- -

Saved payment credentials

-

-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringCredential ID
tmp_passwordbytesTemporary password
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerChannel.html b/data/core.telegram.org/constructor/inputPeerChannel.html deleted file mode 100644 index ece151e6f8..0000000000 --- a/data/core.telegram.org/constructor/inputPeerChannel.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputPeerChannel - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerChannel

- -

Defines a channel for further interaction.

-

-
inputPeerChannel#20adaef8 channel_id:int access_hash:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel 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 deleted file mode 100644 index 6e2061d59f..0000000000 --- a/data/core.telegram.org/constructor/inputPeerChannelFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputPeerChannelFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerChannelFromMessage

- -

Defines a min channel that was seen in a certain message of a certain chat.

-

-
inputPeerChannelFromMessage#9c95f7bb peer:InputPeer msg_id:int channel_id:int = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the channel's message was seen
msg_idintThe message ID
channel_idintThe identifier of the channel that was seen
-

Type

-

InputPeer

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerChat.html b/data/core.telegram.org/constructor/inputPeerChat.html deleted file mode 100644 index 558896fbf6..0000000000 --- a/data/core.telegram.org/constructor/inputPeerChat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPeerChat - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerEmpty.html b/data/core.telegram.org/constructor/inputPeerEmpty.html deleted file mode 100644 index e9552ec1b5..0000000000 --- a/data/core.telegram.org/constructor/inputPeerEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPeerEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerNotifySettings.html b/data/core.telegram.org/constructor/inputPeerNotifySettings.html deleted file mode 100644 index 867c79bd40..0000000000 --- a/data/core.telegram.org/constructor/inputPeerNotifySettings.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - inputPeerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerNotifySettings

- -

Notification settings.

-

-
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolIf the text of the message shall be displayed in notification
silentflags.1?BoolPeer was muted?
mute_untilflags.2?intDate until which all notifications shall be switched off
soundflags.3?stringName of an audio file for notification
-

Type

-

InputPeerNotifySettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html b/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html deleted file mode 100644 index deb768cbc9..0000000000 --- a/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - inputPeerPhotoFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerPhotoFileLocation

- -

Location of profile photo of channel/group/supergroup/user

-

-
inputPeerPhotoFileLocation#27d69997 flags:# big:flags.0?true peer:InputPeer volume_id:long local_id:int = 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
volume_idlongVolume ID from FileLocation met in the profile photo container.
local_idintLocal ID from FileLocation met in the profile photo container.
-

Type

-

InputFileLocation

-

Related pages

-

FileLocation

-

Indicates the location of a photo, will be deprecated soon

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerSelf.html b/data/core.telegram.org/constructor/inputPeerSelf.html deleted file mode 100644 index 30d3449355..0000000000 --- a/data/core.telegram.org/constructor/inputPeerSelf.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPeerSelf - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerUser.html b/data/core.telegram.org/constructor/inputPeerUser.html deleted file mode 100644 index 07071ee6a0..0000000000 --- a/data/core.telegram.org/constructor/inputPeerUser.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputPeerUser - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerUser

- -

Defines a user for further interaction.

-

-
inputPeerUser#7b8e7de6 user_id:int access_hash:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser identifier
access_hashlongaccess_hash value from the user constructor
-

Type

-

InputPeer

-

Related pages

-

user

-

Indicates info about a certain user

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerUserFromMessage.html b/data/core.telegram.org/constructor/inputPeerUserFromMessage.html deleted file mode 100644 index abd028ec9a..0000000000 --- a/data/core.telegram.org/constructor/inputPeerUserFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputPeerUserFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerUserFromMessage

- -

Defines a min user that was seen in a certain message of a certain chat.

-

-
inputPeerUserFromMessage#17bae2e6 peer:InputPeer msg_id:int user_id:int = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idintThe identifier of the user that was seen
-

Type

-

InputPeer

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhoneCall.html b/data/core.telegram.org/constructor/inputPhoneCall.html deleted file mode 100644 index d4471702ca..0000000000 --- a/data/core.telegram.org/constructor/inputPhoneCall.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoneCall

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhoneContact.html b/data/core.telegram.org/constructor/inputPhoneContact.html deleted file mode 100644 index 80325df0c6..0000000000 --- a/data/core.telegram.org/constructor/inputPhoneContact.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - inputPhoneContact - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoneContact

- -

Phone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.

-

-
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
client_idlongUser identifier on the client
phonestringPhone number
first_namestringContact's first name
last_namestringContact's last name
-

Type

-

InputContact

-

Related pages

-

contacts.importContacts

-

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

-

Use contacts.addContact to add Telegram contacts without actually using their phone number.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhoto.html b/data/core.telegram.org/constructor/inputPhoto.html deleted file mode 100644 index 4c1b458a92..0000000000 --- a/data/core.telegram.org/constructor/inputPhoto.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoto

- -

Defines a photo for further interaction.

-

-
inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto identifier
access_hashlongaccess_hash value from the photo constructor
file_referencebytesFile reference
-

Type

-

InputPhoto

-

Related pages

-

photo

-

Photo

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhotoEmpty.html b/data/core.telegram.org/constructor/inputPhotoEmpty.html deleted file mode 100644 index 5c0f3af2ed..0000000000 --- a/data/core.telegram.org/constructor/inputPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPhotoEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhotoFileLocation.html b/data/core.telegram.org/constructor/inputPhotoFileLocation.html deleted file mode 100644 index e4dde1e831..0000000000 --- a/data/core.telegram.org/constructor/inputPhotoFileLocation.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - inputPhotoFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputPhotoFileLocation

- -

Use this object to download a photo with upload.getFile method

-

-
inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto ID, obtained from the photo object
access_hashlongPhoto's access hash, obtained from the photo object
file_referencebytesFile reference
thumb_sizestringThe PhotoSize to download: must be set to the type field of the desired PhotoSize object of the photo
-

Type

-

InputFileLocation

-

Related pages

-

photo

-

Photo

-

File references

-

How to handle file references.

-

PhotoSize

-

Location of a certain size of a picture

-

upload.getFile

-

Returns content of a whole file or its part.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html b/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html deleted file mode 100644 index fbb851dd5b..0000000000 --- a/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputPhotoLegacyFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputPhotoLegacyFileLocation

- -

Legacy photo file location

-

-
inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto ID
access_hashlongAccess hash
file_referencebytesFile reference
volume_idlongVolume ID
local_idintLocal ID
secretlongSecret
-

Type

-

InputFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html b/data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html deleted file mode 100644 index aa4d8e2fd9..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyAddedByPhone - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyAddedByPhone

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html b/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html deleted file mode 100644 index 52cd205577..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyChatInvite

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html b/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html deleted file mode 100644 index 2f4ae857c0..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyForwards - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyForwards

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html deleted file mode 100644 index 79c1539382..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneCall

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html deleted file mode 100644 index c508014bbb..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneNumber - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneNumber

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html deleted file mode 100644 index 3e64fc7bcc..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneP2P - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneP2P

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html b/data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html deleted file mode 100644 index 128c90fb8c..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyProfilePhoto

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html b/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html deleted file mode 100644 index c669e1eea6..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyStatusTimestamp - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyStatusTimestamp

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html deleted file mode 100644 index bb42e0093b..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueAllowAll - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html deleted file mode 100644 index ba502455aa..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueAllowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowChatParticipants

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowContacts.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowContacts.html deleted file mode 100644 index 61c25a58f8..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueAllowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueAllowContacts - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html deleted file mode 100644 index dfcf8868a1..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueAllowUsers - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowUsers

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html deleted file mode 100644 index e152f534b9..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueDisallowAll - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html deleted file mode 100644 index fea361efb0..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueDisallowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowChatParticipants

- -

Disallow only participants of certain chats

-

-
inputPrivacyValueDisallowChatParticipants#d82363af chats:Vector<int> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<int>Disallowed chat IDs
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowContacts.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowContacts.html deleted file mode 100644 index 8d70e2fbcc..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueDisallowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueDisallowContacts - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowContacts

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html deleted file mode 100644 index 7c8f54a4de..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueDisallowUsers - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowUsers

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html b/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html deleted file mode 100644 index 29bcd6b79b..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonChildAbuse - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonCopyright.html b/data/core.telegram.org/constructor/inputReportReasonCopyright.html deleted file mode 100644 index 7bb58109c8..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonCopyright.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonCopyright - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html b/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html deleted file mode 100644 index fa8d772fd4..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonGeoIrrelevant - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonGeoIrrelevant

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonOther.html b/data/core.telegram.org/constructor/inputReportReasonOther.html deleted file mode 100644 index f0537461bc..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonOther.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputReportReasonOther - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonPornography.html b/data/core.telegram.org/constructor/inputReportReasonPornography.html deleted file mode 100644 index 8e2e990c74..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonPornography.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonPornography - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonSpam.html b/data/core.telegram.org/constructor/inputReportReasonSpam.html deleted file mode 100644 index 899b0f8f05..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonSpam.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonSpam - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonViolence.html b/data/core.telegram.org/constructor/inputReportReasonViolence.html deleted file mode 100644 index d579f7bcfa..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonViolence.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonViolence - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSecureFile.html b/data/core.telegram.org/constructor/inputSecureFile.html deleted file mode 100644 index a174824eb9..0000000000 --- a/data/core.telegram.org/constructor/inputSecureFile.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputSecureFile - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureFile

- -

Preuploaded passport file, for more info see the passport docs »

-

-
inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongSecure file ID
access_hashlongSecure file access hash
-

Type

-

InputSecureFile

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSecureFileLocation.html b/data/core.telegram.org/constructor/inputSecureFileLocation.html deleted file mode 100644 index 285fdc7f0c..0000000000 --- a/data/core.telegram.org/constructor/inputSecureFileLocation.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - inputSecureFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureFileLocation

- -

Location of encrypted telegram passport file.

-

-
inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID, id parameter value from secureFile
access_hashlongChecksum, access_hash parameter value from secureFile
-

Type

-

InputFileLocation

-

Related pages

-

secureFile

-

Secure passport file, for more info see the passport docs »

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSecureFileUploaded.html b/data/core.telegram.org/constructor/inputSecureFileUploaded.html deleted file mode 100644 index 923e8e2a8f..0000000000 --- a/data/core.telegram.org/constructor/inputSecureFileUploaded.html +++ /dev/null @@ -1,169 +0,0 @@ - - - - - inputSecureFileUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureFileUploaded

- -

Uploaded secure file, for more info see the passport docs »

-

-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongSecure file ID
partsintSecure file part count
md5_checksumstringMD5 hash of encrypted uploaded file, to be checked server-side
file_hashbytesFile hash
secretbytesSecret
-

Type

-

InputSecureFile

-

Related pages

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSecureValue.html b/data/core.telegram.org/constructor/inputSecureValue.html deleted file mode 100644 index 6c7e284ad1..0000000000 --- a/data/core.telegram.org/constructor/inputSecureValue.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - inputSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureValue

- -

Secure value, for more info see the passport docs »

-

-
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
-

Type

-

InputSecureValue

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSingleMedia.html b/data/core.telegram.org/constructor/inputSingleMedia.html deleted file mode 100644 index 6c03c8c5f2..0000000000 --- a/data/core.telegram.org/constructor/inputSingleMedia.html +++ /dev/null @@ -1,174 +0,0 @@ - - - - - inputSingleMedia - - - - - - - - - - - - - -
- -
-
-
- -

inputSingleMedia

- -

A single media in an album or grouped media sent with messages.sendMultiMedia.

-

-
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
mediaInputMediaThe media
random_idlongUnique client media ID required to prevent message resending
messagestringA caption for the media
entitiesflags.0?Vector<MessageEntity>Message entities for styled text
-

Type

-

InputSingleMedia

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

messages.sendMultiMedia

-

Send an album or grouped media

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetAnimatedEmoji.html b/data/core.telegram.org/constructor/inputStickerSetAnimatedEmoji.html deleted file mode 100644 index c30ad1fa81..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetAnimatedEmoji.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputStickerSetAnimatedEmoji - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetDice.html b/data/core.telegram.org/constructor/inputStickerSetDice.html deleted file mode 100644 index 06fc8994fe..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetDice.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputStickerSetDice - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetDice

- -

Used for fetching animated dice stickers

-

-
inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
-

Type

-

InputStickerSet

-

Related pages

-

Dice

-

Telegram supports sending animated dice emojis.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetEmpty.html b/data/core.telegram.org/constructor/inputStickerSetEmpty.html deleted file mode 100644 index 0ad0a16932..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputStickerSetEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetID.html b/data/core.telegram.org/constructor/inputStickerSetID.html deleted file mode 100644 index 53717e523a..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetID.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputStickerSetID - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetID

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetItem.html b/data/core.telegram.org/constructor/inputStickerSetItem.html deleted file mode 100644 index 16e3d031c8..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetItem.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputStickerSetItem - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetItem

- -

Sticker in a stickerset

-

-
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
documentInputDocumentThe sticker
emojistringAssociated emoji
mask_coordsflags.0?MaskCoordsCoordinates for mask sticker
-

Type

-

InputStickerSetItem

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetShortName.html b/data/core.telegram.org/constructor/inputStickerSetShortName.html deleted file mode 100644 index 33f12db5d7..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetShortName.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickerSetShortName - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetShortName

- -

Stickerset by short name, from tg://addstickers?set=short_name

-

-
inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
short_namestringFrom tg://addstickers?set=short_name
-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetThumb.html b/data/core.telegram.org/constructor/inputStickerSetThumb.html deleted file mode 100644 index 488108cf15..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetThumb.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputStickerSetThumb - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetThumb

- -

Location of stickerset thumbnail (see files)

-

-
inputStickerSetThumb#dbaeae9 stickerset:InputStickerSet volume_id:long local_id:int = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetSticker set
volume_idlongVolume ID
local_idintLocal ID
-

Type

-

InputFileLocation

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickeredMediaDocument.html b/data/core.telegram.org/constructor/inputStickeredMediaDocument.html deleted file mode 100644 index e2a994c87a..0000000000 --- a/data/core.telegram.org/constructor/inputStickeredMediaDocument.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickeredMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputStickeredMediaDocument

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html b/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html deleted file mode 100644 index 1d8ad48280..0000000000 --- a/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickeredMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputStickeredMediaPhoto

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputTakeoutFileLocation.html b/data/core.telegram.org/constructor/inputTakeoutFileLocation.html deleted file mode 100644 index 03f078df84..0000000000 --- a/data/core.telegram.org/constructor/inputTakeoutFileLocation.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputTakeoutFileLocation - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputTheme.html b/data/core.telegram.org/constructor/inputTheme.html deleted file mode 100644 index 7189a67de4..0000000000 --- a/data/core.telegram.org/constructor/inputTheme.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputTheme - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputThemeSettings.html b/data/core.telegram.org/constructor/inputThemeSettings.html deleted file mode 100644 index c4c7c723c5..0000000000 --- a/data/core.telegram.org/constructor/inputThemeSettings.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - inputThemeSettings - - - - - - - - - - - - - -
- -
-
-
- -

inputThemeSettings

- -

Theme settings

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
base_themeBaseThemeDefault theme on which this theme is based
accent_colorintAccent color, RGB24 format
message_top_colorflags.0?intMessage gradient color (top), RGB24 format
message_bottom_colorflags.0?intMessage gradient color (bottom), RGB24 format
wallpaperflags.1?InputWallPaperWallpaper
wallpaper_settingsflags.1?WallPaperSettingsWallpaper settings
-

Type

-

InputThemeSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputThemeSlug.html b/data/core.telegram.org/constructor/inputThemeSlug.html deleted file mode 100644 index 51be2ac4fd..0000000000 --- a/data/core.telegram.org/constructor/inputThemeSlug.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputThemeSlug - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputUser.html b/data/core.telegram.org/constructor/inputUser.html deleted file mode 100644 index 37e2c1a806..0000000000 --- a/data/core.telegram.org/constructor/inputUser.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputUser - - - - - - - - - - - - - -
- -
-
-
- -

inputUser

- -

Defines a user for further interaction.

-

-
inputUser#d8292816 user_id:int access_hash:long = InputUser;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser identifier
access_hashlongaccess_hash value from the user constructor
-

Type

-

InputUser

-

Related pages

-

user

-

Indicates info about a certain user

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputUserEmpty.html b/data/core.telegram.org/constructor/inputUserEmpty.html deleted file mode 100644 index be35722a15..0000000000 --- a/data/core.telegram.org/constructor/inputUserEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputUserEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputUserFromMessage.html b/data/core.telegram.org/constructor/inputUserFromMessage.html deleted file mode 100644 index e2720267d3..0000000000 --- a/data/core.telegram.org/constructor/inputUserFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputUserFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputUserFromMessage

- -

Defines a min user that was seen in a certain message of a certain chat.

-

-
inputUserFromMessage#2d117597 peer:InputPeer msg_id:int user_id:int = InputUser;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idintThe identifier of the user that was seen
-

Type

-

InputUser

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputUserSelf.html b/data/core.telegram.org/constructor/inputUserSelf.html deleted file mode 100644 index 887d46cc49..0000000000 --- a/data/core.telegram.org/constructor/inputUserSelf.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputUserSelf - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWallPaper.html b/data/core.telegram.org/constructor/inputWallPaper.html deleted file mode 100644 index 311a4f0526..0000000000 --- a/data/core.telegram.org/constructor/inputWallPaper.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

inputWallPaper

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWallPaperNoFile.html b/data/core.telegram.org/constructor/inputWallPaperNoFile.html deleted file mode 100644 index e2d8222196..0000000000 --- a/data/core.telegram.org/constructor/inputWallPaperNoFile.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputWallPaperNoFile - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWallPaperSlug.html b/data/core.telegram.org/constructor/inputWallPaperSlug.html deleted file mode 100644 index 8662176d16..0000000000 --- a/data/core.telegram.org/constructor/inputWallPaperSlug.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputWallPaperSlug - - - - - - - - - - - - - -
- -
-
-
- -

inputWallPaperSlug

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWebDocument.html b/data/core.telegram.org/constructor/inputWebDocument.html deleted file mode 100644 index f8695cc856..0000000000 --- a/data/core.telegram.org/constructor/inputWebDocument.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputWebDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputWebDocument

- -

The document

-

-
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringRemote document URL to be downloaded using the appropriate method
sizeintRemote file size
mime_typestringMime type
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

InputWebDocument

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html b/data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html deleted file mode 100644 index ee8704648f..0000000000 --- a/data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputWebFileGeoPointLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputWebFileGeoPointLocation

- -

Geolocation

-

-
inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointInputGeoPointGeolocation
access_hashlongAccess hash
wintMap width in pixels before applying scale; 16-1024
hintMap height in pixels before applying scale; 16-1024
zoomintMap zoom level; 13-20
scaleintMap scale; 1-3
-

Type

-

InputWebFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWebFileLocation.html b/data/core.telegram.org/constructor/inputWebFileLocation.html deleted file mode 100644 index 17dd3f456c..0000000000 --- a/data/core.telegram.org/constructor/inputWebFileLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputWebFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputWebFileLocation

- -

Location of a remote HTTP(s) file

-

-
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringHTTP URL of file
access_hashlongAccess hash
-

Type

-

InputWebFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/invoice.html b/data/core.telegram.org/constructor/invoice.html deleted file mode 100644 index 4262fbf464..0000000000 --- a/data/core.telegram.org/constructor/invoice.html +++ /dev/null @@ -1,199 +0,0 @@ - - - - - invoice - - - - - - - - - - - - - -
- -
-
-
- -

invoice

- -

Invoice

-

-
invoice#c30aa358 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> = 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.)
-

Type

-

Invoice

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonArray.html b/data/core.telegram.org/constructor/jsonArray.html deleted file mode 100644 index 69c9337c30..0000000000 --- a/data/core.telegram.org/constructor/jsonArray.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonArray - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonBool.html b/data/core.telegram.org/constructor/jsonBool.html deleted file mode 100644 index d97c239c12..0000000000 --- a/data/core.telegram.org/constructor/jsonBool.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonBool - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonNull.html b/data/core.telegram.org/constructor/jsonNull.html deleted file mode 100644 index 647c80022e..0000000000 --- a/data/core.telegram.org/constructor/jsonNull.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - jsonNull - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonNumber.html b/data/core.telegram.org/constructor/jsonNumber.html deleted file mode 100644 index 08a4197b32..0000000000 --- a/data/core.telegram.org/constructor/jsonNumber.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonNumber - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonObject.html b/data/core.telegram.org/constructor/jsonObject.html deleted file mode 100644 index a24bc1656e..0000000000 --- a/data/core.telegram.org/constructor/jsonObject.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonObject - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonObjectValue.html b/data/core.telegram.org/constructor/jsonObjectValue.html deleted file mode 100644 index 4a568a9deb..0000000000 --- a/data/core.telegram.org/constructor/jsonObjectValue.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - jsonObjectValue - - - - - - - - - - - - - -
- -
-
-
- -

jsonObjectValue

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonString.html b/data/core.telegram.org/constructor/jsonString.html deleted file mode 100644 index e8e55cf737..0000000000 --- a/data/core.telegram.org/constructor/jsonString.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonString - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButton.html b/data/core.telegram.org/constructor/keyboardButton.html deleted file mode 100644 index 1d8023310a..0000000000 --- a/data/core.telegram.org/constructor/keyboardButton.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButton - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonBuy.html b/data/core.telegram.org/constructor/keyboardButtonBuy.html deleted file mode 100644 index b36258b582..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonBuy.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonBuy - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonCallback.html b/data/core.telegram.org/constructor/keyboardButtonCallback.html deleted file mode 100644 index aa7bd59c32..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonCallback.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - keyboardButtonCallback - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonCallback

- -

Callback button

-

-
keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
requires_passwordflags.0?trueWhether the user should verify his identity by entering his 2FA SRP parameters to the messages.getBotCallbackAnswer method. NOTE: telegram and the bot WILL NOT have access to the plaintext password, thanks to SRP. This button is mainly used by the official @botfather bot, for verifying the user's identity before transferring ownership of a bot to another user.
textstringButton text
databytesCallback data
-

Type

-

KeyboardButton

-

Related pages

-

Two-factor authentication

-

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

-

messages.getBotCallbackAnswer

-

Press an inline callback button and get a callback answer from the bot

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonGame.html b/data/core.telegram.org/constructor/keyboardButtonGame.html deleted file mode 100644 index 0d0011f303..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonGame - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html b/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html deleted file mode 100644 index c63ada53fc..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRequestGeoLocation - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestGeoLocation

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html b/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html deleted file mode 100644 index 3faf91a9de..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRequestPhone - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestPhone

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html b/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html deleted file mode 100644 index 429f723ee2..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - keyboardButtonRequestPoll - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestPoll

- -

A button that allows the user to create and send a poll when pressed; available only in private

-

-
keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
quizflags.0?BoolIf set, only quiz polls can be sent
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonRow.html b/data/core.telegram.org/constructor/keyboardButtonRow.html deleted file mode 100644 index d5c5104af0..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonRow.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRow - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRow

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html b/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html deleted file mode 100644 index 16eb76dad1..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - keyboardButtonSwitchInline - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonSwitchInline

- -

Button to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.

-

-
keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
same_peerflags.0?trueIf set, pressing the button will insert the bot‘s username and the specified inline query in the current chat's input field.
textstringButton label
querystringThe inline query to use
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonUrl.html b/data/core.telegram.org/constructor/keyboardButtonUrl.html deleted file mode 100644 index 104da0b62e..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonUrl.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - keyboardButtonUrl - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonUrl

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html b/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html deleted file mode 100644 index 3822175cef..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - keyboardButtonUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonUrlAuth

- -

Button to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.

-

-
keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
textstringButton label
fwd_textflags.0?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: Services must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
button_idintID of the button to pass to messages.requestUrlAuth
-

Type

-

KeyboardButton

-

Related pages

-

Telegram Login Widget

-

messages.requestUrlAuth

-

Get more info about a Seamless Telegram Login authorization request, for more info click here »

-

urlAuthResultRequest

-

Details about the authorization request, for more info click here »

-

messages.acceptUrlAuth

-

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

-

urlAuthResultAccepted

-

Details about an accepted authorization request, for more info click here »

-

urlAuthResultDefault

-

Details about an accepted authorization request, for more info click here »

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/labeledPrice.html b/data/core.telegram.org/constructor/labeledPrice.html deleted file mode 100644 index 187e7aef80..0000000000 --- a/data/core.telegram.org/constructor/labeledPrice.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - labeledPrice - - - - - - - - - - - - - -
- -
-
-
- -

labeledPrice

- -

This object represents a portion of the price for goods or services.

-

-
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
labelstringPortion label
amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Type

-

LabeledPrice

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackDifference.html b/data/core.telegram.org/constructor/langPackDifference.html deleted file mode 100644 index 7ee49e5ba0..0000000000 --- a/data/core.telegram.org/constructor/langPackDifference.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - langPackDifference - - - - - - - - - - - - - -
- -
-
-
- -

langPackDifference

- -

Changes to the app's localization pack

-

-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious version number
versionintNew version number
stringsVector<LangPackString>Localized strings
-

Type

-

LangPackDifference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackLanguage.html b/data/core.telegram.org/constructor/langPackLanguage.html deleted file mode 100644 index d7b419e2d5..0000000000 --- a/data/core.telegram.org/constructor/langPackLanguage.html +++ /dev/null @@ -1,202 +0,0 @@ - - - - - langPackLanguage - - - - - - - - - - - - - -
- -
-
-
- -

langPackLanguage

- -

Identifies a localization pack

-

-
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
officialflags.0?trueWhether the language pack is official
rtlflags.2?trueIs this a localization pack for an RTL language
betaflags.3?trueIs this a beta localization pack?
namestringLanguage name
native_namestringLanguage name in the language itself
lang_codestringLanguage code (pack identifier)
base_lang_codeflags.1?stringIdentifier of a base language pack; may be empty. If a string is missed in the language pack, then it should be fetched from base language pack. Unsupported in custom language packs
plural_codestringA language code to be used to apply plural forms. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
strings_countintTotal number of non-deleted strings from the language pack
translated_countintTotal number of translated strings from the language pack
translations_urlstringLink to language translation interface; empty for custom local language packs
-

Type

-

LangPackLanguage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackString.html b/data/core.telegram.org/constructor/langPackString.html deleted file mode 100644 index 3fde904173..0000000000 --- a/data/core.telegram.org/constructor/langPackString.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - langPackString - - - - - - - - - - - - - -
- -
-
-
- -

langPackString

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackStringDeleted.html b/data/core.telegram.org/constructor/langPackStringDeleted.html deleted file mode 100644 index 1a6cc2cffb..0000000000 --- a/data/core.telegram.org/constructor/langPackStringDeleted.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - langPackStringDeleted - - - - - - - - - - - - - -
- -
-
-
- -

langPackStringDeleted

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackStringPluralized.html b/data/core.telegram.org/constructor/langPackStringPluralized.html deleted file mode 100644 index ee87c92eb6..0000000000 --- a/data/core.telegram.org/constructor/langPackStringPluralized.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - langPackStringPluralized - - - - - - - - - - - - - -
- -
-
-
- -

langPackStringPluralized

- -

A language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info

-

-
langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
keystringLocalization key
zero_valueflags.0?stringValue for zero objects
one_valueflags.1?stringValue for one object
two_valueflags.2?stringValue for two objects
few_valueflags.3?stringValue for a few objects
many_valueflags.4?stringValue for many objects
other_valuestringDefault value
-

Type

-

LangPackString

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/maskCoords.html b/data/core.telegram.org/constructor/maskCoords.html deleted file mode 100644 index 277044aae9..0000000000 --- a/data/core.telegram.org/constructor/maskCoords.html +++ /dev/null @@ -1,169 +0,0 @@ - - - - - maskCoords - - - - - - - - - - - - - -
- -
-
-
- -

maskCoords

- -

Position on a photo where a mask should be placed

-

The n position indicates where the mask should be placed:

-
    -
  • 0 => Relative to the forehead
  • -
  • 1 => Relative to the eyes
  • -
  • 2 => Relative to the mouth
  • -
  • 3 => Relative to the chin
  • -
-

-
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
nintPart of the face, relative to which the mask should be placed
xdoubleShift by X-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
ydoubleShift by Y-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
zoomdoubleMask scaling coefficient. (For example, 2.0 means a doubled size)
-

Type

-

MaskCoords

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/message.html b/data/core.telegram.org/constructor/message.html deleted file mode 100644 index 9c8cb01ddb..0000000000 --- a/data/core.telegram.org/constructor/message.html +++ /dev/null @@ -1,297 +0,0 @@ - - - - - message - - - - - - - - - - - - - -
- -
-
-
- -

message

- -

A message

-

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

-

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?intID 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.
-

Type

-

Message

-

Related pages

-

Mentions

-

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

-

Scheduled messages

-

Telegram allows scheduling messages

-

Pinned messages

-

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

-

Styled text with message entities

-

How to create styled text with message entities

-

Threads

-

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

-

messages.sendMultiMedia

-

Send an album or grouped media

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionBotAllowed.html b/data/core.telegram.org/constructor/messageActionBotAllowed.html deleted file mode 100644 index 794d93cbeb..0000000000 --- a/data/core.telegram.org/constructor/messageActionBotAllowed.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messageActionBotAllowed - - - - - - - - - - - - - -
- -
-
-
- -

messageActionBotAllowed

- -

The domain name of the website on which the user has logged in. More about Telegram Login »

-

-
messageActionBotAllowed#abe9affe domain:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
domainstringThe domain name of the website on which the user has logged in.
-

Type

-

MessageAction

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChannelCreate.html b/data/core.telegram.org/constructor/messageActionChannelCreate.html deleted file mode 100644 index 77c5c1fde3..0000000000 --- a/data/core.telegram.org/constructor/messageActionChannelCreate.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChannelCreate - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChannelCreate

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html b/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html deleted file mode 100644 index cc2eaf3592..0000000000 --- a/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageActionChannelMigrateFrom - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChannelMigrateFrom

- -

Indicates the channel was migrated from the specified chat

-

-
messageActionChannelMigrateFrom#b055eaee title:string chat_id:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titlestringThe old chat tite
chat_idintThe old chat ID
-

Type

-

MessageAction

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatAddUser.html b/data/core.telegram.org/constructor/messageActionChatAddUser.html deleted file mode 100644 index ec868e957e..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatAddUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatAddUser - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatAddUser

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatCreate.html b/data/core.telegram.org/constructor/messageActionChatCreate.html deleted file mode 100644 index 414359ff0a..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatCreate.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageActionChatCreate - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatCreate

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatDeletePhoto.html b/data/core.telegram.org/constructor/messageActionChatDeletePhoto.html deleted file mode 100644 index f723e8a4d8..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatDeletePhoto.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionChatDeletePhoto - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatDeleteUser.html b/data/core.telegram.org/constructor/messageActionChatDeleteUser.html deleted file mode 100644 index 3034993fd3..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatDeleteUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatDeleteUser - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatDeleteUser

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatEditPhoto.html b/data/core.telegram.org/constructor/messageActionChatEditPhoto.html deleted file mode 100644 index 59cd241360..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatEditPhoto.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatEditPhoto - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatEditPhoto

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatEditTitle.html b/data/core.telegram.org/constructor/messageActionChatEditTitle.html deleted file mode 100644 index e53767f5a6..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatEditTitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatEditTitle - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatEditTitle

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html b/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html deleted file mode 100644 index bfd245d3e5..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatJoinedByLink - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatJoinedByLink

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatMigrateTo.html b/data/core.telegram.org/constructor/messageActionChatMigrateTo.html deleted file mode 100644 index 3e6ef4bed5..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatMigrateTo.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messageActionChatMigrateTo - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatMigrateTo

- -

Indicates the chat was migrated to the specified supergroup

-

-
messageActionChatMigrateTo#51bdb021 channel_id:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintThe supergroup it was migrated to
-

Type

-

MessageAction

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionContactSignUp.html b/data/core.telegram.org/constructor/messageActionContactSignUp.html deleted file mode 100644 index d2e8d454ee..0000000000 --- a/data/core.telegram.org/constructor/messageActionContactSignUp.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionContactSignUp - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionCustomAction.html b/data/core.telegram.org/constructor/messageActionCustomAction.html deleted file mode 100644 index 8de910f277..0000000000 --- a/data/core.telegram.org/constructor/messageActionCustomAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionCustomAction - - - - - - - - - - - - - -
- -
-
-
- -

messageActionCustomAction

- -

Custom action (most likely not supported by the current layer, an upgrade might be needed)

-

-
messageActionCustomAction#fae69f56 message:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messagestringAction message
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionEmpty.html b/data/core.telegram.org/constructor/messageActionEmpty.html deleted file mode 100644 index aeb7d971a8..0000000000 --- a/data/core.telegram.org/constructor/messageActionEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionGameScore.html b/data/core.telegram.org/constructor/messageActionGameScore.html deleted file mode 100644 index ce12250501..0000000000 --- a/data/core.telegram.org/constructor/messageActionGameScore.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageActionGameScore - - - - - - - - - - - - - -
- -
-
-
- -

messageActionGameScore

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionGeoProximityReached.html b/data/core.telegram.org/constructor/messageActionGeoProximityReached.html deleted file mode 100644 index b29e7704fb..0000000000 --- a/data/core.telegram.org/constructor/messageActionGeoProximityReached.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messageActionGeoProximityReached - - - - - - - - - - - - - -
- -
-
-
- -

messageActionGeoProximityReached

- -

A user of the chat is now in proximity of another user

-

-
messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
from_idPeerThe user or chat that is now in proximity of to_id
to_idPeerThe user or chat that subscribed to live geolocation proximity alerts
distanceintDistance, in meters (0-100000)
-

Type

-

MessageAction

-

Related pages

-

Live geolocation

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionHistoryClear.html b/data/core.telegram.org/constructor/messageActionHistoryClear.html deleted file mode 100644 index 1cb9ef60e0..0000000000 --- a/data/core.telegram.org/constructor/messageActionHistoryClear.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionHistoryClear - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPaymentSent.html b/data/core.telegram.org/constructor/messageActionPaymentSent.html deleted file mode 100644 index d3bc255bfb..0000000000 --- a/data/core.telegram.org/constructor/messageActionPaymentSent.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messageActionPaymentSent - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPaymentSent

- -

A payment was sent

-

-
messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Type

-

MessageAction

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPaymentSentMe.html b/data/core.telegram.org/constructor/messageActionPaymentSentMe.html deleted file mode 100644 index 51576239dc..0000000000 --- a/data/core.telegram.org/constructor/messageActionPaymentSentMe.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - messageActionPaymentSentMe - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPaymentSentMe

- -

A user just sent a payment to me (a bot)

-

-
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
chargePaymentChargeProvider payment identifier
-

Type

-

MessageAction

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPhoneCall.html b/data/core.telegram.org/constructor/messageActionPhoneCall.html deleted file mode 100644 index 339d63d6e2..0000000000 --- a/data/core.telegram.org/constructor/messageActionPhoneCall.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messageActionPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPhoneCall

- -

A phone call

-

-
messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.2?trueIs this a video call?
call_idlongCall ID
reasonflags.0?PhoneCallDiscardReasonIf the call has ended, the reason why it ended
durationflags.1?intDuration of the call in seconds
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPinMessage.html b/data/core.telegram.org/constructor/messageActionPinMessage.html deleted file mode 100644 index 3025f23424..0000000000 --- a/data/core.telegram.org/constructor/messageActionPinMessage.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionPinMessage - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionScreenshotTaken.html b/data/core.telegram.org/constructor/messageActionScreenshotTaken.html deleted file mode 100644 index 8ae3fc3607..0000000000 --- a/data/core.telegram.org/constructor/messageActionScreenshotTaken.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionScreenshotTaken - - - - - - - - - - - - - -
- -
-
-
- -

messageActionScreenshotTaken

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionSecureValuesSent.html b/data/core.telegram.org/constructor/messageActionSecureValuesSent.html deleted file mode 100644 index a48098c816..0000000000 --- a/data/core.telegram.org/constructor/messageActionSecureValuesSent.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messageActionSecureValuesSent - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSecureValuesSent

- -

Request for secure telegram passport values was sent

-

-
messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureValueType>Secure value types
-

Type

-

MessageAction

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html b/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html deleted file mode 100644 index 62b7ac8b02..0000000000 --- a/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messageActionSecureValuesSentMe - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSecureValuesSentMe

- -

Secure telegram passport values were received

-

-
messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
valuesVector<SecureValue>Vector with information about documents and other Telegram Passport elements that were shared with the bot
credentialsSecureCredentialsEncryptedEncrypted credentials required to decrypt the data
-

Type

-

MessageAction

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEmpty.html b/data/core.telegram.org/constructor/messageEmpty.html deleted file mode 100644 index 1ceb9dfc46..0000000000 --- a/data/core.telegram.org/constructor/messageEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityBankCard.html b/data/core.telegram.org/constructor/messageEntityBankCard.html deleted file mode 100644 index 2d8937b4e3..0000000000 --- a/data/core.telegram.org/constructor/messageEntityBankCard.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBankCard - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBankCard

- -

Indicates a credit card number

-

-
messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityBlockquote.html b/data/core.telegram.org/constructor/messageEntityBlockquote.html deleted file mode 100644 index 113a7e8a08..0000000000 --- a/data/core.telegram.org/constructor/messageEntityBlockquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBlockquote - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBlockquote

- -

Message entity representing a block quote.

-

-
messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityBold.html b/data/core.telegram.org/constructor/messageEntityBold.html deleted file mode 100644 index 865abed448..0000000000 --- a/data/core.telegram.org/constructor/messageEntityBold.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBold - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBold

- -

Message entity representing bold text.

-

-
messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityBotCommand.html b/data/core.telegram.org/constructor/messageEntityBotCommand.html deleted file mode 100644 index 49459d3703..0000000000 --- a/data/core.telegram.org/constructor/messageEntityBotCommand.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBotCommand - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBotCommand

- -

Message entity representing a bot /command

-

-
messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityCashtag.html b/data/core.telegram.org/constructor/messageEntityCashtag.html deleted file mode 100644 index 333aee1185..0000000000 --- a/data/core.telegram.org/constructor/messageEntityCashtag.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityCashtag - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityCashtag

- -

Message entity representing a $cashtag.

-

-
messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityCode.html b/data/core.telegram.org/constructor/messageEntityCode.html deleted file mode 100644 index 61b3eddbdd..0000000000 --- a/data/core.telegram.org/constructor/messageEntityCode.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityCode - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityCode

- -

Message entity representing a codeblock.

-

-
messageEntityCode#28a20571 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityEmail.html b/data/core.telegram.org/constructor/messageEntityEmail.html deleted file mode 100644 index ed06330f40..0000000000 --- a/data/core.telegram.org/constructor/messageEntityEmail.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityEmail - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityEmail

- -

Message entity representing an email@example.com.

-

-
messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityHashtag.html b/data/core.telegram.org/constructor/messageEntityHashtag.html deleted file mode 100644 index 7d453988df..0000000000 --- a/data/core.telegram.org/constructor/messageEntityHashtag.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityHashtag - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityHashtag

- -

#hashtag message entity

-

-
messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityItalic.html b/data/core.telegram.org/constructor/messageEntityItalic.html deleted file mode 100644 index 20abf931eb..0000000000 --- a/data/core.telegram.org/constructor/messageEntityItalic.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityItalic - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityItalic

- -

Message entity representing italic text.

-

-
messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityMention.html b/data/core.telegram.org/constructor/messageEntityMention.html deleted file mode 100644 index 3939197791..0000000000 --- a/data/core.telegram.org/constructor/messageEntityMention.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageEntityMention - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityMention

- -

Message entity mentioning the current user

-

-
messageEntityMention#fa04579d offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityMentionName.html b/data/core.telegram.org/constructor/messageEntityMentionName.html deleted file mode 100644 index 1bd0750a72..0000000000 --- a/data/core.telegram.org/constructor/messageEntityMentionName.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messageEntityMentionName - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityMentionName

- -

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

-

-
messageEntityMentionName#352dca58 offset:int length:int user_id:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idintIdentifier of the user that was mentioned
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

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

-

inputMessageEntityMentionName

-

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityPhone.html b/data/core.telegram.org/constructor/messageEntityPhone.html deleted file mode 100644 index 043b738752..0000000000 --- a/data/core.telegram.org/constructor/messageEntityPhone.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityPhone - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityPhone

- -

Message entity representing a phone number.

-

-
messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityPre.html b/data/core.telegram.org/constructor/messageEntityPre.html deleted file mode 100644 index 8739000e9a..0000000000 --- a/data/core.telegram.org/constructor/messageEntityPre.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageEntityPre - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityPre

- -

Message entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.

-

-
messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
languagestringProgramming language of the code
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityStrike.html b/data/core.telegram.org/constructor/messageEntityStrike.html deleted file mode 100644 index 4b56146f08..0000000000 --- a/data/core.telegram.org/constructor/messageEntityStrike.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityStrike - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityStrike

- -

Message entity representing strikethrough text.

-

-
messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityTextUrl.html b/data/core.telegram.org/constructor/messageEntityTextUrl.html deleted file mode 100644 index 8ba3440605..0000000000 --- a/data/core.telegram.org/constructor/messageEntityTextUrl.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messageEntityTextUrl - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityTextUrl

- -

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

-

-
messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
urlstringThe actual URL
-

Type

-

MessageEntity

-

Related pages

-

messageEntityUrl

-

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityUnderline.html b/data/core.telegram.org/constructor/messageEntityUnderline.html deleted file mode 100644 index f186408270..0000000000 --- a/data/core.telegram.org/constructor/messageEntityUnderline.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityUnderline - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUnderline

- -

Message entity representing underlined text.

-

-
messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityUnknown.html b/data/core.telegram.org/constructor/messageEntityUnknown.html deleted file mode 100644 index 1c3da0abeb..0000000000 --- a/data/core.telegram.org/constructor/messageEntityUnknown.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityUnknown - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUnknown

- -

Unknown message entity

-

-
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityUrl.html b/data/core.telegram.org/constructor/messageEntityUrl.html deleted file mode 100644 index 9f01f7a78d..0000000000 --- a/data/core.telegram.org/constructor/messageEntityUrl.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageEntityUrl - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUrl

- -

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

-

-
messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

-

Related pages

-

messageEntityTextUrl

-

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageFwdHeader.html b/data/core.telegram.org/constructor/messageFwdHeader.html deleted file mode 100644 index 1f4d465d0c..0000000000 --- a/data/core.telegram.org/constructor/messageFwdHeader.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messageFwdHeader - - - - - - - - - - - - - -
- -
-
-
- -

messageFwdHeader

- -

Info about a forwarded message

-

-
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageInteractionCounters.html b/data/core.telegram.org/constructor/messageInteractionCounters.html deleted file mode 100644 index 66547e274e..0000000000 --- a/data/core.telegram.org/constructor/messageInteractionCounters.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageInteractionCounters - - - - - - - - - - - - - -
- -
-
-
- -

messageInteractionCounters

- -

Message interaction counters

-

-
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
msg_idintMessage ID
viewsintViews
forwardsintNumber of times this message was forwarded
-

Type

-

MessageInteractionCounters

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaAudio.html b/data/core.telegram.org/constructor/messageMediaAudio.html deleted file mode 100644 index b95eaa4bff..0000000000 --- a/data/core.telegram.org/constructor/messageMediaAudio.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaAudio - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaContact.html b/data/core.telegram.org/constructor/messageMediaContact.html deleted file mode 100644 index 6fe19ca54e..0000000000 --- a/data/core.telegram.org/constructor/messageMediaContact.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaContact

- -

Attached contact.

-

-
messageMediaContact#cbf24940 phone_number:string first_name:string last_name:string vcard:string user_id:int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringVCARD of contact
user_idintUser 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 deleted file mode 100644 index 6796b774c9..0000000000 --- a/data/core.telegram.org/constructor/messageMediaDice.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageMediaDice - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaDice

- -

Dice-based animated sticker

-

-
messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
valueintDice value
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
-

Type

-

MessageMedia

-

Related pages

-

Dice

-

Telegram supports sending animated dice emojis.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaDocument.html b/data/core.telegram.org/constructor/messageMediaDocument.html deleted file mode 100644 index 5c3cc0db2f..0000000000 --- a/data/core.telegram.org/constructor/messageMediaDocument.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaDocument

- -

Document (video, audio, voice, sticker, any media type except photo)

-

-
messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
documentflags.0?DocumentAttached document
ttl_secondsflags.2?intTime to live of self-destructing document
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaEmpty.html b/data/core.telegram.org/constructor/messageMediaEmpty.html deleted file mode 100644 index 8df0fa3999..0000000000 --- a/data/core.telegram.org/constructor/messageMediaEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageMediaEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaGame.html b/data/core.telegram.org/constructor/messageMediaGame.html deleted file mode 100644 index 0cbea0b69d..0000000000 --- a/data/core.telegram.org/constructor/messageMediaGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaGame - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaGeo.html b/data/core.telegram.org/constructor/messageMediaGeo.html deleted file mode 100644 index f3061c607f..0000000000 --- a/data/core.telegram.org/constructor/messageMediaGeo.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaGeo - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaGeoLive.html b/data/core.telegram.org/constructor/messageMediaGeoLive.html deleted file mode 100644 index 55bfb60b92..0000000000 --- a/data/core.telegram.org/constructor/messageMediaGeoLive.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messageMediaGeoLive - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaGeoLive

- -

Indicates a live geolocation

-

-
messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodintValidity period of provided geolocation
proximity_notification_radiusflags.1?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000).
-

Type

-

MessageMedia

-

Related pages

-

Live geolocation

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaInvoice.html b/data/core.telegram.org/constructor/messageMediaInvoice.html deleted file mode 100644 index e3c712941e..0000000000 --- a/data/core.telegram.org/constructor/messageMediaInvoice.html +++ /dev/null @@ -1,198 +0,0 @@ - - - - - messageMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaInvoice

- -

Invoice

-

-
messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueWhether the shipping address was requested
testflags.3?trueWhether this is an example invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
receipt_msg_idflags.2?intMessage ID of receipt: if set, clients should change the text of the first keyboardButtonBuy button always attached to the message to a localized version of the word Receipt
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
start_paramstringUnique bot deep-linking parameter that can be used to generate this invoice
-

Type

-

MessageMedia

-

Related pages

-

keyboardButtonBuy

-

Button to buy a product

-

message

-

A message

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaPhoto.html b/data/core.telegram.org/constructor/messageMediaPhoto.html deleted file mode 100644 index 9e880c91bf..0000000000 --- a/data/core.telegram.org/constructor/messageMediaPhoto.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaPhoto

- -

Attached photo.

-

-
messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
photoflags.0?PhotoPhoto
ttl_secondsflags.2?intTime to live in seconds of self-destructing photo
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaPoll.html b/data/core.telegram.org/constructor/messageMediaPoll.html deleted file mode 100644 index ea5666ab6c..0000000000 --- a/data/core.telegram.org/constructor/messageMediaPoll.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageMediaPoll - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaPoll

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaUnsupported.html b/data/core.telegram.org/constructor/messageMediaUnsupported.html deleted file mode 100644 index a9b80acb7f..0000000000 --- a/data/core.telegram.org/constructor/messageMediaUnsupported.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageMediaUnsupported - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaUnsupported

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaVenue.html b/data/core.telegram.org/constructor/messageMediaVenue.html deleted file mode 100644 index 7386fac385..0000000000 --- a/data/core.telegram.org/constructor/messageMediaVenue.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaVenue

- -

Venue

-

-
messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaVideo.html b/data/core.telegram.org/constructor/messageMediaVideo.html deleted file mode 100644 index 29438e0667..0000000000 --- a/data/core.telegram.org/constructor/messageMediaVideo.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaVideo - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaWebPage.html b/data/core.telegram.org/constructor/messageMediaWebPage.html deleted file mode 100644 index 90f9c097a6..0000000000 --- a/data/core.telegram.org/constructor/messageMediaWebPage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaWebPage - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaWebPage

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageRange.html b/data/core.telegram.org/constructor/messageRange.html deleted file mode 100644 index b0c4886bb6..0000000000 --- a/data/core.telegram.org/constructor/messageRange.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageRange - - - - - - - - - - - - - -
- -
-
-
- -

messageRange

- -

Indicates a range of chat messages

-

-
messageRange#ae30253 min_id:int max_id:int = MessageRange;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
min_idintStart of range (message ID)
max_idintEnd of range (message ID)
-

Type

-

MessageRange

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageReplies.html b/data/core.telegram.org/constructor/messageReplies.html deleted file mode 100644 index b7b161ffa1..0000000000 --- a/data/core.telegram.org/constructor/messageReplies.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - messageReplies - - - - - - - - - - - - - -
- -
-
-
- -

messageReplies

- -

Info about the comment section of a channel post, or a simple message thread

-

-
messageReplies#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;

-

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?intFor channel post comments, contains the ID of the associated discussion supergroup
max_idflags.2?intID of the latest message in this thread or comment section.
read_max_idflags.3?intContains the ID of the latest read message in this thread or comment section.
-

Type

-

MessageReplies

-

Related pages

-

Threads

-

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

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Discussion groups

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageReplyHeader.html b/data/core.telegram.org/constructor/messageReplyHeader.html deleted file mode 100644 index d539711b68..0000000000 --- a/data/core.telegram.org/constructor/messageReplyHeader.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messageReplyHeader - - - - - - - - - - - - - -
- -
-
-
- -

messageReplyHeader

- -

Message replies and thread information

-

-
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
reply_to_msg_idintID of message to which this message is replying
reply_to_peer_idflags.0?PeerFor replies sent in channel discussion threads of which the current user is not a member, the discussion group ID
reply_to_top_idflags.1?intID of the message that started this message thread
-

Type

-

MessageReplyHeader

-

Related pages

-

Threads

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageService.html b/data/core.telegram.org/constructor/messageService.html deleted file mode 100644 index c03299cd5c..0000000000 --- a/data/core.telegram.org/constructor/messageService.html +++ /dev/null @@ -1,207 +0,0 @@ - - - - - messageService - - - - - - - - - - - - - -
- -
-
-
- -

messageService

- -

Indicates a service 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;

-

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
-

Type

-

Message

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageUserVote.html b/data/core.telegram.org/constructor/messageUserVote.html deleted file mode 100644 index ed517f127f..0000000000 --- a/data/core.telegram.org/constructor/messageUserVote.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageUserVote - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVote

- -

How a user voted in a poll

-

-
messageUserVote#a28e5559 user_id:int option:bytes date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser ID
optionbytesThe option chosen by the user
dateintWhen did the user cast the vote
-

Type

-

MessageUserVote

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageUserVoteInputOption.html b/data/core.telegram.org/constructor/messageUserVoteInputOption.html deleted file mode 100644 index 5e7f48772e..0000000000 --- a/data/core.telegram.org/constructor/messageUserVoteInputOption.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageUserVoteInputOption - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVoteInputOption

- -

How a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)

-

-
messageUserVoteInputOption#36377430 user_id:int date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintThe user that voted for the queried option
dateintWhen did the user cast the vote
-

Type

-

MessageUserVote

-

Related pages

-

messages.getPollVotes

-

Get poll results for non-anonymous polls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageUserVoteMultiple.html b/data/core.telegram.org/constructor/messageUserVoteMultiple.html deleted file mode 100644 index 2695454e97..0000000000 --- a/data/core.telegram.org/constructor/messageUserVoteMultiple.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageUserVoteMultiple - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVoteMultiple

- -

How a user voted in a multiple-choice poll

-

-
messageUserVoteMultiple#e8fe0de user_id:int options:Vector<bytes> date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser ID
optionsVector<bytes>Options chosen by the user
dateintWhen did the user cast their votes
-

Type

-

MessageUserVote

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageViews.html b/data/core.telegram.org/constructor/messageViews.html deleted file mode 100644 index c0a0f6f0a5..0000000000 --- a/data/core.telegram.org/constructor/messageViews.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messageViews - - - - - - - - - - - - - -
- -
-
-
- -

messageViews

- -

View, forward counter + info about replies of a specific message

-

-
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
viewsflags.0?intViewcount of message
forwardsflags.1?intForward count of message
repliesflags.2?MessageRepliesReply and thread information of message
-

Type

-

MessageViews

-

Related pages

-

Threads

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.affectedHistory b/data/core.telegram.org/constructor/messages.affectedHistory deleted file mode 100644 index feb4b8e889..0000000000 --- a/data/core.telegram.org/constructor/messages.affectedHistory +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.affectedHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.affectedHistory

- -

Affected part of communication history with the user or in a chat.

-

-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintNumber of events occured in a text box
pts_countintNumber of affected events
offsetintIf a parameter contains positive value, it is necessary to repeat the method call using the given value; during the proceeding of all the history the value itself shall gradually decrease
-

Type

-

messages.AffectedHistory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.affectedMessages b/data/core.telegram.org/constructor/messages.affectedMessages deleted file mode 100644 index 6b37d48ced..0000000000 --- a/data/core.telegram.org/constructor/messages.affectedMessages +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.affectedMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.affectedMessages

- -

Events affected by operation

-

-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

messages.AffectedMessages

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.allStickers b/data/core.telegram.org/constructor/messages.allStickers deleted file mode 100644 index 2f8ea7c527..0000000000 --- a/data/core.telegram.org/constructor/messages.allStickers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.allStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.allStickers

- -

Info about all installed stickers

-

-
messages.allStickers#edfd405f hash:int sets:Vector<StickerSet> = messages.AllStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
setsVector<StickerSet>All stickersets
-

Type

-

messages.AllStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.allStickersNotModified b/data/core.telegram.org/constructor/messages.allStickersNotModified deleted file mode 100644 index 050ac36dcb..0000000000 --- a/data/core.telegram.org/constructor/messages.allStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.allStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.allStickersNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.archivedStickers b/data/core.telegram.org/constructor/messages.archivedStickers deleted file mode 100644 index f375b92684..0000000000 --- a/data/core.telegram.org/constructor/messages.archivedStickers +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.archivedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.archivedStickers

- -

Archived stickersets

-

-
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of archived stickers
setsVector<StickerSetCovered>Archived stickersets
-

Type

-

messages.ArchivedStickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.botCallbackAnswer b/data/core.telegram.org/constructor/messages.botCallbackAnswer deleted file mode 100644 index dc1a901223..0000000000 --- a/data/core.telegram.org/constructor/messages.botCallbackAnswer +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.botCallbackAnswer - - - - - - - - - - - - - -
- -
-
-
- -

messages.botCallbackAnswer

- -

Callback answer sent by the bot in response to a button press

-

-
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
alertflags.1?trueWhether an alert should be shown to the user instead of a toast notification
has_urlflags.3?trueWhether an URL is present
native_uiflags.4?trueWhether to show games in WebView or in native UI.
messageflags.0?stringAlert to show
urlflags.2?stringURL to open
cache_timeintFor how long should this answer be cached
-

Type

-

messages.BotCallbackAnswer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.botResults b/data/core.telegram.org/constructor/messages.botResults deleted file mode 100644 index 1379173f8a..0000000000 --- a/data/core.telegram.org/constructor/messages.botResults +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.botResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.botResults

- -

Result of a query to an inline bot

-

-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueWhether the result is a picture gallery
query_idlongQuery ID
next_offsetflags.1?stringThe next offset to use when navigating through results
switch_pmflags.2?InlineBotSwitchPMWhether the bot requested the user to message him in private
resultsVector<BotInlineResult>The results
cache_timeintCaching validity of the results
usersVector<User>Users mentioned in the results
-

Type

-

messages.BotResults

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.channelMessages b/data/core.telegram.org/constructor/messages.channelMessages deleted file mode 100644 index 588eaf134b..0000000000 --- a/data/core.telegram.org/constructor/messages.channelMessages +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.channelMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.channelMessages

- -

Channel messages

-

-
messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, returned results may be inexact
ptsintEvent count after generation
countintTotal number of results were found server-side (may not be all included here)
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>Found messages
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

messages.Messages

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.chatFull b/data/core.telegram.org/constructor/messages.chatFull deleted file mode 100644 index cab43152c5..0000000000 --- a/data/core.telegram.org/constructor/messages.chatFull +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.chatFull - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatFull

- -

Extended info on chat and auxiliary data.

-

-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
full_chatChatFullExtended info on a chat
chatsVector<Chat>List containing basic info on chat
usersVector<User>List of users mentioned above
-

Type

-

messages.ChatFull

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.chats b/data/core.telegram.org/constructor/messages.chats deleted file mode 100644 index fc61513b39..0000000000 --- a/data/core.telegram.org/constructor/messages.chats +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.chats - - - - - - - - - - - - - -
- -
-
-
- -

messages.chats

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.chatsSlice b/data/core.telegram.org/constructor/messages.chatsSlice deleted file mode 100644 index e02e2c0166..0000000000 --- a/data/core.telegram.org/constructor/messages.chatsSlice +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.chatsSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatsSlice

- -

Partial list of chats, more would have to be fetched with pagination

-

-
messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of results that were found server-side (not all are included in chats)
chatsVector<Chat>Chats
-

Type

-

messages.Chats

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dhConfig b/data/core.telegram.org/constructor/messages.dhConfig deleted file mode 100644 index 215b0532cd..0000000000 --- a/data/core.telegram.org/constructor/messages.dhConfig +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.dhConfig - - - - - - - - - - - - - -
- -
-
-
- -

messages.dhConfig

- -

New set of configuring parameters.

-

-
messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
gintNew value prime, see Wikipedia
pbytesNew value primitive root, see Wikipedia
versionintVestion of set of parameters
randombytesRandom sequence of bytes of assigned length
-

Type

-

messages.DhConfig

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dhConfigNotModified b/data/core.telegram.org/constructor/messages.dhConfigNotModified deleted file mode 100644 index 9c86700137..0000000000 --- a/data/core.telegram.org/constructor/messages.dhConfigNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.dhConfigNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.dhConfigNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dialogs b/data/core.telegram.org/constructor/messages.dialogs deleted file mode 100644 index 8d03ea693c..0000000000 --- a/data/core.telegram.org/constructor/messages.dialogs +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.dialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.dialogs

- -

Full list of chats with messages and auxiliary data.

-

-
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dialogsVector<Dialog>List of chats
messagesVector<Message>List of last messages from each chat
chatsVector<Chat>List of groups mentioned in the chats
usersVector<User>List of users mentioned in messages and groups
-

Type

-

messages.Dialogs

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dialogsNotModified b/data/core.telegram.org/constructor/messages.dialogsNotModified deleted file mode 100644 index a92be2f9b8..0000000000 --- a/data/core.telegram.org/constructor/messages.dialogsNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.dialogsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.dialogsNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dialogsSlice b/data/core.telegram.org/constructor/messages.dialogsSlice deleted file mode 100644 index 735a489a9d..0000000000 --- a/data/core.telegram.org/constructor/messages.dialogsSlice +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.dialogsSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.dialogsSlice

- -

Incomplete list of dialogs with messages and auxiliary data.

-

-
messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of dialogs
dialogsVector<Dialog>List of dialogs
messagesVector<Message>List of last messages from dialogs
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
-

Type

-

messages.Dialogs

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.discussionMessage b/data/core.telegram.org/constructor/messages.discussionMessage deleted file mode 100644 index 2b8b285857..0000000000 --- a/data/core.telegram.org/constructor/messages.discussionMessage +++ /dev/null @@ -1,180 +0,0 @@ - - - - - messages.discussionMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.discussionMessage

- -

Information about a message thread

-

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

-

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
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.favedStickers b/data/core.telegram.org/constructor/messages.favedStickers deleted file mode 100644 index 30256acb84..0000000000 --- a/data/core.telegram.org/constructor/messages.favedStickers +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.favedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.favedStickers

- -

Favorited stickers

-

-
messages.favedStickers#f37f2f16 hash:int packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Favorited stickers
-

Type

-

messages.FavedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.favedStickersNotModified b/data/core.telegram.org/constructor/messages.favedStickersNotModified deleted file mode 100644 index 3be4785417..0000000000 --- a/data/core.telegram.org/constructor/messages.favedStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.favedStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.favedStickersNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.featuredStickers b/data/core.telegram.org/constructor/messages.featuredStickers deleted file mode 100644 index 5f8536e59c..0000000000 --- a/data/core.telegram.org/constructor/messages.featuredStickers +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.featuredStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.featuredStickers

- -

Featured stickersets

-

-
messages.featuredStickers#b6abc341 hash:int count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
countintTotal number of featured stickers
setsVector<StickerSetCovered>Featured stickersets
unreadVector<long>IDs of new featured stickersets
-

Type

-

messages.FeaturedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.featuredStickersNotModified b/data/core.telegram.org/constructor/messages.featuredStickersNotModified deleted file mode 100644 index 0d431e3c4d..0000000000 --- a/data/core.telegram.org/constructor/messages.featuredStickersNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.featuredStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.featuredStickersNotModified

- -

Featured stickers haven't changed

-

-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of featured stickers
-

Type

-

messages.FeaturedStickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.foundStickerSets b/data/core.telegram.org/constructor/messages.foundStickerSets deleted file mode 100644 index 25d8a2cca1..0000000000 --- a/data/core.telegram.org/constructor/messages.foundStickerSets +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.foundStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.foundStickerSets

- -

Found stickersets

-

-
messages.foundStickerSets#5108d648 hash:int sets:Vector<StickerSetCovered> = messages.FoundStickerSets;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
setsVector<StickerSetCovered>Found stickersets
-

Type

-

messages.FoundStickerSets

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified b/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified deleted file mode 100644 index 29d8f82771..0000000000 --- a/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.foundStickerSetsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.foundStickerSetsNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.highScores b/data/core.telegram.org/constructor/messages.highScores deleted file mode 100644 index 1d72c57527..0000000000 --- a/data/core.telegram.org/constructor/messages.highScores +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.highScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.highScores

- -

Highscores in a game

-

-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scoresVector<HighScore>Highscores
usersVector<User>Users, associated to the highscores
-

Type

-

messages.HighScores

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.inactiveChats b/data/core.telegram.org/constructor/messages.inactiveChats deleted file mode 100644 index 86e9be4d0b..0000000000 --- a/data/core.telegram.org/constructor/messages.inactiveChats +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.inactiveChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.inactiveChats

- -

Inactive chat list

-

-
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
datesVector<int>When was the chat last active
chatsVector<Chat>Chat list
usersVector<User>Users mentioned in the chat list
-

Type

-

messages.InactiveChats

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messageEditData b/data/core.telegram.org/constructor/messages.messageEditData deleted file mode 100644 index 33528cd05e..0000000000 --- a/data/core.telegram.org/constructor/messages.messageEditData +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.messageEditData - - - - - - - - - - - - - -
- -
-
-
- -

messages.messageEditData

- -

Message edit data for media

-

-
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
captionflags.0?trueMedia caption, if the specified media's caption can be edited
-

Type

-

messages.MessageEditData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messageViews b/data/core.telegram.org/constructor/messages.messageViews deleted file mode 100644 index 3113b43e43..0000000000 --- a/data/core.telegram.org/constructor/messages.messageViews +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.messageViews - - - - - - - - - - - - - -
- -
-
-
- -

messages.messageViews

- -

View, forward counter + info about replies

-

-
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
viewsVector<MessageViews>View, forward counter + info about replies
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
-

Type

-

messages.MessageViews

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messages b/data/core.telegram.org/constructor/messages.messages deleted file mode 100644 index 8c732b0062..0000000000 --- a/data/core.telegram.org/constructor/messages.messages +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.messages - - - - - - - - - - - - - -
- -
-
-
- -

messages.messages

- -

Full list of messages with auxilary data.

-

-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
-

Type

-

messages.Messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messagesNotModified b/data/core.telegram.org/constructor/messages.messagesNotModified deleted file mode 100644 index 54bd265920..0000000000 --- a/data/core.telegram.org/constructor/messages.messagesNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.messagesNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.messagesNotModified

- -

No new messages matching the query were found

-

-
messages.messagesNotModified#74535f21 count:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of results found server-side by the given query
-

Type

-

messages.Messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messagesSlice b/data/core.telegram.org/constructor/messages.messagesSlice deleted file mode 100644 index f1c3b9969a..0000000000 --- a/data/core.telegram.org/constructor/messages.messagesSlice +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.messagesSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.messagesSlice

- -

Incomplete list of messages and auxiliary data.

-

-
messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, indicates that the results may be inexact
countintTotal number of messages in the list
next_rateflags.0?intRate to use in the offset_rate parameter in the next call to messages.searchGlobal
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in messages
usersVector<User>List of users mentioned in messages and chats
-

Type

-

messages.Messages

-

Related pages

-

messages.searchGlobal

-

Search for messages and peers globally

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.peerDialogs b/data/core.telegram.org/constructor/messages.peerDialogs deleted file mode 100644 index 0f1ac84a2e..0000000000 --- a/data/core.telegram.org/constructor/messages.peerDialogs +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.peerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.peerDialogs

- -

Dialog info of multiple peers

-

-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dialogsVector<Dialog>Dialog info
messagesVector<Message>Messages mentioned in dialog info
chatsVector<Chat>Chats
usersVector<User>Users
stateupdates.StateCurrent update state of dialog
-

Type

-

messages.PeerDialogs

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.recentStickers b/data/core.telegram.org/constructor/messages.recentStickers deleted file mode 100644 index 56afa717dc..0000000000 --- a/data/core.telegram.org/constructor/messages.recentStickers +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.recentStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.recentStickers

- -

Recently used stickers

-

-
messages.recentStickers#22f3afb3 hash:int packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Recent stickers
datesVector<int>When was each sticker last used
-

Type

-

messages.RecentStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.recentStickersNotModified b/data/core.telegram.org/constructor/messages.recentStickersNotModified deleted file mode 100644 index da573e04ff..0000000000 --- a/data/core.telegram.org/constructor/messages.recentStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.recentStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.recentStickersNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.savedGifs b/data/core.telegram.org/constructor/messages.savedGifs deleted file mode 100644 index da90baa97c..0000000000 --- a/data/core.telegram.org/constructor/messages.savedGifs +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.savedGifs - - - - - - - - - - - - - -
- -
-
-
- -

messages.savedGifs

- -

Saved gifs

-

-
messages.savedGifs#2e0709a5 hash:int gifs:Vector<Document> = messages.SavedGifs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
gifsVector<Document>List of saved gifs
-

Type

-

messages.SavedGifs

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.savedGifsNotModified b/data/core.telegram.org/constructor/messages.savedGifsNotModified deleted file mode 100644 index e4b836368c..0000000000 --- a/data/core.telegram.org/constructor/messages.savedGifsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.savedGifsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.savedGifsNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.searchCounter b/data/core.telegram.org/constructor/messages.searchCounter deleted file mode 100644 index 0b28a0f585..0000000000 --- a/data/core.telegram.org/constructor/messages.searchCounter +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.searchCounter - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchCounter

- -

Indicates how many results would be found by a messages.search call with the same parameters

-

-
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, the results may be inexact
filterMessagesFilterProvided message filter
countintNumber of results that were found server-side
-

Type

-

messages.SearchCounter

-

Related pages

-

messages.search

-

Gets back found messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.sentEncryptedFile b/data/core.telegram.org/constructor/messages.sentEncryptedFile deleted file mode 100644 index 114ab246c0..0000000000 --- a/data/core.telegram.org/constructor/messages.sentEncryptedFile +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.sentEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

messages.sentEncryptedFile

- -

Message with a file enclosure sent to a protected chat

-

-
messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dateintSending date
fileEncryptedFileAttached file
-

Type

-

messages.SentEncryptedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.sentEncryptedMessage b/data/core.telegram.org/constructor/messages.sentEncryptedMessage deleted file mode 100644 index 86945a674c..0000000000 --- a/data/core.telegram.org/constructor/messages.sentEncryptedMessage +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.sentEncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.sentEncryptedMessage

- -

Message without file attachemts sent to an encrypted file.

-

-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dateintDate of sending
-

Type

-

messages.SentEncryptedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.sentMessageLink b/data/core.telegram.org/constructor/messages.sentMessageLink deleted file mode 100644 index 0b546e1d09..0000000000 --- a/data/core.telegram.org/constructor/messages.sentMessageLink +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.sentMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

messages.sentMessageLink

- -

Info on successfully sent message and on changes links.

-

-
Constructor schema is available as of layer 24. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID
dateintDate of sending
ptsintNew value of pts parameter of a current state
seqintNew value of seq parameter of a current state
linksVector<contacts.Link>List of changes links
-

Type

-

messages.SentMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.statedMessageLink b/data/core.telegram.org/constructor/messages.statedMessageLink deleted file mode 100644 index 66b2ab9a74..0000000000 --- a/data/core.telegram.org/constructor/messages.statedMessageLink +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.statedMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

messages.statedMessageLink

- -

Message with auxiliary data, state data and the list of changed links.

-

-
Constructor schema is available as of layer 24. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageMessage
chatsVector<Chat>List of chats mentioned in message
usersVector<User>List of users mentioned in message and chats
linksVector<contacts.Link>List of changed links
ptsintNumber of events occurred in text box
seqintNumber of sent updates
-

Type

-

messages.StatedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.statedMessagesLinks b/data/core.telegram.org/constructor/messages.statedMessagesLinks deleted file mode 100644 index 355f29d8d4..0000000000 --- a/data/core.telegram.org/constructor/messages.statedMessagesLinks +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.statedMessagesLinks - - - - - - - - - - - - - -
- -
-
-
- -

messages.statedMessagesLinks

- -

Message with auxiliary data, state data and the list of changed links.

-

-
Constructor schema is available as of layer 24. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of cats mentioned in messages
usersVector<User>List of users mentioned in messages and cahts
linksVector<contacts.Link>List of changed links
ptsintNumber of event occurred in a text box
seqintNumber of sent updates
-

Type

-

messages.StatedMessages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickerSet b/data/core.telegram.org/constructor/messages.stickerSet deleted file mode 100644 index 884407e3de..0000000000 --- a/data/core.telegram.org/constructor/messages.stickerSet +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.stickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSet

- -

Stickerset and stickers inside it

-

-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetThe stickerset
packsVector<StickerPack>Emoji info for stickers
documentsVector<Document>Stickers in stickerset
-

Type

-

messages.StickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive b/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive deleted file mode 100644 index 5586c3d087..0000000000 --- a/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.stickerSetInstallResultArchive - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSetInstallResultArchive

- -

The stickerset was installed, but since there are too many stickersets some were archived

-

-
messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
setsVector<StickerSetCovered>Archived stickersets
-

Type

-

messages.StickerSetInstallResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess b/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess deleted file mode 100644 index 7e8be726b2..0000000000 --- a/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.stickerSetInstallResultSuccess - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSetInstallResultSuccess

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickers b/data/core.telegram.org/constructor/messages.stickers deleted file mode 100644 index 873f8c0ecd..0000000000 --- a/data/core.telegram.org/constructor/messages.stickers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.stickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickers

- -

Found stickers

-

-
messages.stickers#e4599bbd hash:int stickers:Vector<Document> = messages.Stickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
stickersVector<Document>Stickers
-

Type

-

messages.Stickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickersNotModified b/data/core.telegram.org/constructor/messages.stickersNotModified deleted file mode 100644 index e615263628..0000000000 --- a/data/core.telegram.org/constructor/messages.stickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.stickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickersNotModified

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.votesList b/data/core.telegram.org/constructor/messages.votesList deleted file mode 100644 index 05491ec304..0000000000 --- a/data/core.telegram.org/constructor/messages.votesList +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.votesList - - - - - - - - - - - - - -
- -
-
-
- -

messages.votesList

- -

How users voted in a poll

-

-
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
countintTotal number of votes for all options (or only for the chosen option, if provided to messages.getPollVotes)
votesVector<MessageUserVote>Vote info for each user
usersVector<User>Info about users that voted in the poll
next_offsetflags.0?stringOffset to use with the next messages.getPollVotes request, empty string if no more results are available.
-

Type

-

messages.VotesList

-

Related pages

-

messages.getPollVotes

-

Get poll results for non-anonymous polls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/nearestDc.html b/data/core.telegram.org/constructor/nearestDc.html deleted file mode 100644 index fe4cc3c48e..0000000000 --- a/data/core.telegram.org/constructor/nearestDc.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - nearestDc - - - - - - - - - - - - - -
- -
-
-
- -

nearestDc

- -

Nearest data centre, according to geo-ip.

-

-
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countrystringCountry code determined by geo-ip
this_dcintNumber of current data centre
nearest_dcintNumber of nearest data centre
-

Type

-

NearestDc

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/notifyBroadcasts.html b/data/core.telegram.org/constructor/notifyBroadcasts.html deleted file mode 100644 index 96427b9891..0000000000 --- a/data/core.telegram.org/constructor/notifyBroadcasts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyBroadcasts - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/notifyChats.html b/data/core.telegram.org/constructor/notifyChats.html deleted file mode 100644 index cbed4e3be6..0000000000 --- a/data/core.telegram.org/constructor/notifyChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyChats - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/notifyPeer.html b/data/core.telegram.org/constructor/notifyPeer.html deleted file mode 100644 index c82ca4a92d..0000000000 --- a/data/core.telegram.org/constructor/notifyPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - notifyPeer - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/notifyUsers.html b/data/core.telegram.org/constructor/notifyUsers.html deleted file mode 100644 index 1bcb66bda0..0000000000 --- a/data/core.telegram.org/constructor/notifyUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyUsers - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/null.html b/data/core.telegram.org/constructor/null.html deleted file mode 100644 index 78547af02e..0000000000 --- a/data/core.telegram.org/constructor/null.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - null - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/page.html b/data/core.telegram.org/constructor/page.html deleted file mode 100644 index fdae0c0394..0000000000 --- a/data/core.telegram.org/constructor/page.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - page - - - - - - - - - - - - - -
- -
-
-
- -

page

- -

Instant view page

-

-
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
partflags.0?trueIndicates that not full page preview is available to the client and it will need to fetch full Instant View from the server using messages.getWebPagePreview.
rtlflags.1?trueWhether the page contains RTL text
v2flags.2?trueWhether this is an IV v2 page
urlstringOriginal page HTTP URL
blocksVector<PageBlock>Page elements (like with HTML elements, only as TL constructors)
photosVector<Photo>Photos in page
documentsVector<Document>Media in page
viewsflags.3?intViewcount
-

Type

-

Page

-

Related pages

-

messages.getWebPagePreview

-

Get preview of webpage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockAnchor.html b/data/core.telegram.org/constructor/pageBlockAnchor.html deleted file mode 100644 index 714b734bf1..0000000000 --- a/data/core.telegram.org/constructor/pageBlockAnchor.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockAnchor - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAnchor

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockAudio.html b/data/core.telegram.org/constructor/pageBlockAudio.html deleted file mode 100644 index 2b17835ec4..0000000000 --- a/data/core.telegram.org/constructor/pageBlockAudio.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - pageBlockAudio - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAudio

- -

Audio

-

-
pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
audio_idlongAudio ID (to be fetched from the container page constructor
captionPageCaptionAudio caption
-

Type

-

PageBlock

-

Related pages

-

page

-

Instant view page

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockAuthorDate.html b/data/core.telegram.org/constructor/pageBlockAuthorDate.html deleted file mode 100644 index 1c256fb359..0000000000 --- a/data/core.telegram.org/constructor/pageBlockAuthorDate.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockAuthorDate - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAuthorDate

- -

Author and date of creation of article

-

-
pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
authorRichTextAuthor name
published_dateintDate of pubblication
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockBlockquote.html b/data/core.telegram.org/constructor/pageBlockBlockquote.html deleted file mode 100644 index 43858c9ddd..0000000000 --- a/data/core.telegram.org/constructor/pageBlockBlockquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockBlockquote - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockBlockquote

- -

Quote (equivalent to the HTML <blockquote>)

-

-
pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextQuote contents
captionRichTextCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockChannel.html b/data/core.telegram.org/constructor/pageBlockChannel.html deleted file mode 100644 index 8b22f7afe4..0000000000 --- a/data/core.telegram.org/constructor/pageBlockChannel.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockChannel - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockChannel

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockCollage.html b/data/core.telegram.org/constructor/pageBlockCollage.html deleted file mode 100644 index e7e547b511..0000000000 --- a/data/core.telegram.org/constructor/pageBlockCollage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockCollage - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockCollage

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockCover.html b/data/core.telegram.org/constructor/pageBlockCover.html deleted file mode 100644 index a27f57d3e1..0000000000 --- a/data/core.telegram.org/constructor/pageBlockCover.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockCover - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockDetails.html b/data/core.telegram.org/constructor/pageBlockDetails.html deleted file mode 100644 index bfd78b733b..0000000000 --- a/data/core.telegram.org/constructor/pageBlockDetails.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - pageBlockDetails - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockDetails

- -

A collapsible details block

-

-
pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
openflags.0?trueWhether the block is open by default
blocksVector<PageBlock>Block contents
titleRichTextAlways visible heading for the block
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockDivider.html b/data/core.telegram.org/constructor/pageBlockDivider.html deleted file mode 100644 index 4e65a05f5d..0000000000 --- a/data/core.telegram.org/constructor/pageBlockDivider.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - pageBlockDivider - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockEmbed.html b/data/core.telegram.org/constructor/pageBlockEmbed.html deleted file mode 100644 index 27d2ce30ef..0000000000 --- a/data/core.telegram.org/constructor/pageBlockEmbed.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - pageBlockEmbed - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockEmbed

- -

An embedded webpage

-

-
pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
full_widthflags.0?trueWhether the block should be full width
allow_scrollingflags.3?trueWhether scrolling should be allowed
urlflags.1?stringWeb page URL, if available
htmlflags.2?stringHTML-markup of the embedded page
poster_photo_idflags.4?longPoster photo, if available
wflags.5?intBlock width, if known
hflags.5?intBlock height, if known
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockEmbedPost.html b/data/core.telegram.org/constructor/pageBlockEmbedPost.html deleted file mode 100644 index 131ac1a738..0000000000 --- a/data/core.telegram.org/constructor/pageBlockEmbedPost.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - pageBlockEmbedPost - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockEmbedPost

- -

An embedded post

-

-
pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringWeb page URL
webpage_idlongID of generated webpage preview
author_photo_idlongID of the author's photo
authorstringAuthor name
dateintCreation date
blocksVector<PageBlock>Post contents
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockFooter.html b/data/core.telegram.org/constructor/pageBlockFooter.html deleted file mode 100644 index 3c29d4542b..0000000000 --- a/data/core.telegram.org/constructor/pageBlockFooter.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockFooter - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockHeader.html b/data/core.telegram.org/constructor/pageBlockHeader.html deleted file mode 100644 index 8b4d2328df..0000000000 --- a/data/core.telegram.org/constructor/pageBlockHeader.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockHeader - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockKicker.html b/data/core.telegram.org/constructor/pageBlockKicker.html deleted file mode 100644 index 2f92d65deb..0000000000 --- a/data/core.telegram.org/constructor/pageBlockKicker.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockKicker - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockList.html b/data/core.telegram.org/constructor/pageBlockList.html deleted file mode 100644 index c0b108b3f6..0000000000 --- a/data/core.telegram.org/constructor/pageBlockList.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockList - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockList

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockMap.html b/data/core.telegram.org/constructor/pageBlockMap.html deleted file mode 100644 index e648254227..0000000000 --- a/data/core.telegram.org/constructor/pageBlockMap.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockMap - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockMap

- -

A map

-

-
pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geoGeoPointLocation of the map center
zoomintMap zoom level; 13-20
wintMap width in pixels before applying scale; 16-102
hintMap height in pixels before applying scale; 16-1024
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockOrderedList.html b/data/core.telegram.org/constructor/pageBlockOrderedList.html deleted file mode 100644 index a0e4d2779b..0000000000 --- a/data/core.telegram.org/constructor/pageBlockOrderedList.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockOrderedList - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockOrderedList

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockParagraph.html b/data/core.telegram.org/constructor/pageBlockParagraph.html deleted file mode 100644 index aa07fda5dd..0000000000 --- a/data/core.telegram.org/constructor/pageBlockParagraph.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockParagraph - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockPhoto.html b/data/core.telegram.org/constructor/pageBlockPhoto.html deleted file mode 100644 index aca6ff96be..0000000000 --- a/data/core.telegram.org/constructor/pageBlockPhoto.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockPhoto - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPhoto

- -

A photo

-

-
pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
photo_idlongPhoto ID
captionPageCaptionCaption
urlflags.0?stringHTTP URL of page the photo leads to when clicked
webpage_idflags.0?longID of preview of the page the photo leads to when clicked
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockPreformatted.html b/data/core.telegram.org/constructor/pageBlockPreformatted.html deleted file mode 100644 index ab49cd38fe..0000000000 --- a/data/core.telegram.org/constructor/pageBlockPreformatted.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockPreformatted - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPreformatted

- -

Preformatted (<pre> text)

-

-
pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
languagestringProgramming language of preformatted text
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockPullquote.html b/data/core.telegram.org/constructor/pageBlockPullquote.html deleted file mode 100644 index 503b080e95..0000000000 --- a/data/core.telegram.org/constructor/pageBlockPullquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockPullquote - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPullquote

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockRelatedArticles.html b/data/core.telegram.org/constructor/pageBlockRelatedArticles.html deleted file mode 100644 index 2787e08c28..0000000000 --- a/data/core.telegram.org/constructor/pageBlockRelatedArticles.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockRelatedArticles - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockRelatedArticles

- -

Related articles

-

-
pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titleRichTextTitle
articlesVector<PageRelatedArticle>Related articles
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockSlideshow.html b/data/core.telegram.org/constructor/pageBlockSlideshow.html deleted file mode 100644 index 79c2d2553f..0000000000 --- a/data/core.telegram.org/constructor/pageBlockSlideshow.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockSlideshow - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockSlideshow

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockSubheader.html b/data/core.telegram.org/constructor/pageBlockSubheader.html deleted file mode 100644 index 9af181c860..0000000000 --- a/data/core.telegram.org/constructor/pageBlockSubheader.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockSubheader - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockSubtitle.html b/data/core.telegram.org/constructor/pageBlockSubtitle.html deleted file mode 100644 index df9029f424..0000000000 --- a/data/core.telegram.org/constructor/pageBlockSubtitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockSubtitle - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockTable.html b/data/core.telegram.org/constructor/pageBlockTable.html deleted file mode 100644 index 886d90c6dd..0000000000 --- a/data/core.telegram.org/constructor/pageBlockTable.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockTable - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockTable

- -

Table

-

-
pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
borderedflags.0?trueDoes the table have a visible border?
stripedflags.1?trueIs the table striped?
titleRichTextTitle
rowsVector<PageTableRow>Table rows
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockTitle.html b/data/core.telegram.org/constructor/pageBlockTitle.html deleted file mode 100644 index 5df5909986..0000000000 --- a/data/core.telegram.org/constructor/pageBlockTitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockTitle - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockUnsupported.html b/data/core.telegram.org/constructor/pageBlockUnsupported.html deleted file mode 100644 index 139e3ecf50..0000000000 --- a/data/core.telegram.org/constructor/pageBlockUnsupported.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - pageBlockUnsupported - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockVideo.html b/data/core.telegram.org/constructor/pageBlockVideo.html deleted file mode 100644 index c9952bc4cf..0000000000 --- a/data/core.telegram.org/constructor/pageBlockVideo.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockVideo - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockVideo

- -

Video

-

-
pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
autoplayflags.0?trueWhether the video is set to autoplay
loopflags.1?trueWhether the video is set to loop
video_idlongVideo ID
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageCaption.html b/data/core.telegram.org/constructor/pageCaption.html deleted file mode 100644 index 9542f829c4..0000000000 --- a/data/core.telegram.org/constructor/pageCaption.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageCaption - - - - - - - - - - - - - -
- -
-
-
- -

pageCaption

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageListItemBlocks.html b/data/core.telegram.org/constructor/pageListItemBlocks.html deleted file mode 100644 index a427a33806..0000000000 --- a/data/core.telegram.org/constructor/pageListItemBlocks.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageListItemBlocks - - - - - - - - - - - - - -
- -
-
-
- -

pageListItemBlocks

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageListItemText.html b/data/core.telegram.org/constructor/pageListItemText.html deleted file mode 100644 index cc5b0d4a3b..0000000000 --- a/data/core.telegram.org/constructor/pageListItemText.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageListItemText - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageListOrderedItemBlocks.html b/data/core.telegram.org/constructor/pageListOrderedItemBlocks.html deleted file mode 100644 index 1858394e69..0000000000 --- a/data/core.telegram.org/constructor/pageListOrderedItemBlocks.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageListOrderedItemBlocks - - - - - - - - - - - - - -
- -
-
-
- -

pageListOrderedItemBlocks

- -

Ordered list of IV blocks

-

-
pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
numstringNumber of element within ordered list
blocksVector<PageBlock>Item contents
-

Type

-

PageListOrderedItem

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageListOrderedItemText.html b/data/core.telegram.org/constructor/pageListOrderedItemText.html deleted file mode 100644 index 46c8157088..0000000000 --- a/data/core.telegram.org/constructor/pageListOrderedItemText.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageListOrderedItemText - - - - - - - - - - - - - -
- -
-
-
- -

pageListOrderedItemText

- -

Ordered list of text items

-

-
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
numstringNumber of element within ordered list
textRichTextText
-

Type

-

PageListOrderedItem

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageRelatedArticle.html b/data/core.telegram.org/constructor/pageRelatedArticle.html deleted file mode 100644 index 3adc100ab7..0000000000 --- a/data/core.telegram.org/constructor/pageRelatedArticle.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - pageRelatedArticle - - - - - - - - - - - - - -
- -
-
-
- -

pageRelatedArticle

- -

Related article

-

-
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of article
webpage_idlongWebpage ID of generated IV preview
titleflags.0?stringTitle
descriptionflags.1?stringDescription
photo_idflags.2?longID of preview photo
authorflags.3?stringAuthor name
published_dateflags.4?intDate of pubblication
-

Type

-

PageRelatedArticle

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageTableCell.html b/data/core.telegram.org/constructor/pageTableCell.html deleted file mode 100644 index 5a892a0357..0000000000 --- a/data/core.telegram.org/constructor/pageTableCell.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - pageTableCell - - - - - - - - - - - - - -
- -
-
-
- -

pageTableCell

- -

Table cell

-

-
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
headerflags.0?trueIs this element part of the column header
align_centerflags.3?trueHorizontally centered block
align_rightflags.4?trueRight-aligned block
valign_middleflags.5?trueVertically centered block
valign_bottomflags.6?trueBlock vertically-alligned to the bottom
textflags.7?RichTextContent
colspanflags.1?intFor how many columns should this cell extend
rowspanflags.2?intFor how many rows should this cell extend
-

Type

-

PageTableCell

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageTableRow.html b/data/core.telegram.org/constructor/pageTableRow.html deleted file mode 100644 index 0b37f95a6c..0000000000 --- a/data/core.telegram.org/constructor/pageTableRow.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageTableRow - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html b/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html deleted file mode 100644 index 452a9767b1..0000000000 --- a/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow - - - - - - - - - - - - - -
- -
-
-
- -

passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow

- -

This key derivation algorithm defines that SRP 2FA login must be used

-

-
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
salt1bytesOne of two salts used by the derivation function (see SRP 2FA login)
salt2bytesOne of two salts used by the derivation function (see SRP 2FA login)
gintBase (see SRP 2FA login)
pbytes2048-bit modulus (see SRP 2FA login)
-

Type

-

PasswordKdfAlgo

-

Related pages

-

Two-factor authentication

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html b/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html deleted file mode 100644 index 2563fb219a..0000000000 --- a/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - passwordKdfAlgoUnknown - - - - - - - - - - - - - -
- -
-
-
- -

passwordKdfAlgoUnknown

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/paymentCharge.html b/data/core.telegram.org/constructor/paymentCharge.html deleted file mode 100644 index f58d011623..0000000000 --- a/data/core.telegram.org/constructor/paymentCharge.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - paymentCharge - - - - - - - - - - - - - -
- -
-
-
- -

paymentCharge

- -

Payment identifier

-

-
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringTelegram payment identifier
provider_charge_idstringProvider payment identifier
-

Type

-

PaymentCharge

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/paymentRequestedInfo.html b/data/core.telegram.org/constructor/paymentRequestedInfo.html deleted file mode 100644 index 23f7e9a566..0000000000 --- a/data/core.telegram.org/constructor/paymentRequestedInfo.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - paymentRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

paymentRequestedInfo

- -

Order info provided by the user

-

-
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
nameflags.0?stringUser's full name
phoneflags.1?stringUser's phone number
emailflags.2?stringUser's email address
shipping_addressflags.3?PostAddressUser's shipping address
-

Type

-

PaymentRequestedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html b/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html deleted file mode 100644 index e849ce7336..0000000000 --- a/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - paymentSavedCredentialsCard - - - - - - - - - - - - - -
- -
-
-
- -

paymentSavedCredentialsCard

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo b/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo deleted file mode 100644 index 44ad5e365c..0000000000 --- a/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo +++ /dev/null @@ -1,145 +0,0 @@ - - - - - payments.ValidatedRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.ValidatedRequestedInfo

- -

Validated user-provided info

-

{scheme}

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idflags.0?stringID
shipping_optionsflags.1?Vector<ShippingOption>Shipping options
-

Type

-

payments.ValidatedRequestedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.bankCardData b/data/core.telegram.org/constructor/payments.bankCardData deleted file mode 100644 index ec70b5af75..0000000000 --- a/data/core.telegram.org/constructor/payments.bankCardData +++ /dev/null @@ -1,152 +0,0 @@ - - - - - payments.bankCardData - - - - - - - - - - - - - -
- -
-
-
- -

payments.bankCardData

- -

Credit card info, provided by the card's bank(s)

-

-
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titlestringCredit card title
open_urlsVector<BankCardOpenUrl>Info URL(s) provided by the card's bank(s)
-

Type

-

payments.BankCardData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.paymentForm b/data/core.telegram.org/constructor/payments.paymentForm deleted file mode 100644 index 2979c048ba..0000000000 --- a/data/core.telegram.org/constructor/payments.paymentForm +++ /dev/null @@ -1,207 +0,0 @@ - - - - - payments.paymentForm - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentForm

- -

Payment form

-

-
payments.paymentForm#3f56aea3 flags:# can_save_credentials:flags.2?true password_missing:flags.3?true 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;

-

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)
bot_idintBot ID
invoiceInvoiceInvoice
provider_idintPayment provider ID.
urlstringPayment form URL
native_providerflags.4?stringPayment provider name.
One of the following:
- stripe
native_paramsflags.4?DataJSONContains information about the payment provider, if available, to support it natively without the need for opening the URL.
A JSON object that can contain the following fields:

- apple_pay_merchant_id: Apple Pay merchant ID
- google_pay_public_key: Google Pay public key
- need_country: True, if the user country must be provided,
- need_zip: True, if the user ZIP/postal code must be provided,
- need_cardholder_name: True, if the cardholder name must be provided -
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
saved_credentialsflags.1?PaymentSavedCredentialsContains information about saved card credentials
usersVector<User>Users
-

Type

-

payments.PaymentForm

-

Related pages

-

Two-factor authentication

-

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

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.paymentReceipt b/data/core.telegram.org/constructor/payments.paymentReceipt deleted file mode 100644 index 7dd369cdc6..0000000000 --- a/data/core.telegram.org/constructor/payments.paymentReceipt +++ /dev/null @@ -1,199 +0,0 @@ - - - - - payments.paymentReceipt - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentReceipt

- -

Receipt

-

-
payments.paymentReceipt#500911e1 flags:# date:int bot_id:int invoice:Invoice provider_id:int info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption 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_idintBot ID
invoiceInvoiceInvoice
provider_idintProvider ID
infoflags.0?PaymentRequestedInfoInfo
shippingflags.1?ShippingOptionSelected shipping option
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
credentials_titlestringPayment credential name
usersVector<User>Users
-

Type

-

payments.PaymentReceipt

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.paymentResult b/data/core.telegram.org/constructor/payments.paymentResult deleted file mode 100644 index 2c49955c23..0000000000 --- a/data/core.telegram.org/constructor/payments.paymentResult +++ /dev/null @@ -1,147 +0,0 @@ - - - - - payments.paymentResult - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentResult

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.paymentVerificationNeeded b/data/core.telegram.org/constructor/payments.paymentVerificationNeeded deleted file mode 100644 index 44e9e33978..0000000000 --- a/data/core.telegram.org/constructor/payments.paymentVerificationNeeded +++ /dev/null @@ -1,147 +0,0 @@ - - - - - payments.paymentVerificationNeeded - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentVerificationNeeded

- -

Payment was not successful, additional verification is needed

-

-
payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL for additional payment credentials verification
-

Type

-

payments.PaymentResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.savedInfo b/data/core.telegram.org/constructor/payments.savedInfo deleted file mode 100644 index 11d5847028..0000000000 --- a/data/core.telegram.org/constructor/payments.savedInfo +++ /dev/null @@ -1,157 +0,0 @@ - - - - - payments.savedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.savedInfo

- -

Saved server-side order information

-

-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_saved_credentialsflags.1?trueWhether the user has some saved payment credentials
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
-

Type

-

payments.SavedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerBlocked.html b/data/core.telegram.org/constructor/peerBlocked.html deleted file mode 100644 index 3bc1959efd..0000000000 --- a/data/core.telegram.org/constructor/peerBlocked.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - peerBlocked - - - - - - - - - - - - - -
- -
-
-
- -

peerBlocked

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerChannel.html b/data/core.telegram.org/constructor/peerChannel.html deleted file mode 100644 index f2adf42043..0000000000 --- a/data/core.telegram.org/constructor/peerChannel.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerChannel - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerChat.html b/data/core.telegram.org/constructor/peerChat.html deleted file mode 100644 index 08219e89e1..0000000000 --- a/data/core.telegram.org/constructor/peerChat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerChat - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerLocated.html b/data/core.telegram.org/constructor/peerLocated.html deleted file mode 100644 index 3e5bf86cfe..0000000000 --- a/data/core.telegram.org/constructor/peerLocated.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - peerLocated - - - - - - - - - - - - - -
- -
-
-
- -

peerLocated

- -

Peer geolocated nearby

-

-
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
expiresintValidity period of current data
distanceintDistance from the peer in meters
-

Type

-

PeerLocated

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerNotifySettings.html b/data/core.telegram.org/constructor/peerNotifySettings.html deleted file mode 100644 index 52b2fcb8c0..0000000000 --- a/data/core.telegram.org/constructor/peerNotifySettings.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - peerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

peerNotifySettings

- -

Notification settings.

-

-
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolDisplay text in notifications
silentflags.1?BoolMute peer?
mute_untilflags.2?intMute all notifications until this date
soundflags.3?stringAudio file name for notifications
-

Type

-

PeerNotifySettings

-

Event flags (events_mask)

- - - - - - - - - - - - - -
0x00000001Profile photo update notification
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerSelfLocated.html b/data/core.telegram.org/constructor/peerSelfLocated.html deleted file mode 100644 index 7490606777..0000000000 --- a/data/core.telegram.org/constructor/peerSelfLocated.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerSelfLocated - - - - - - - - - - - - - -
- -
-
-
- -

peerSelfLocated

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerSettings.html b/data/core.telegram.org/constructor/peerSettings.html deleted file mode 100644 index 57e991b84e..0000000000 --- a/data/core.telegram.org/constructor/peerSettings.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - peerSettings - - - - - - - - - - - - - -
- -
-
-
- -

peerSettings

- -

Peer settings

-

-
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
report_spamflags.0?trueWhether we can still report the user for spam
add_contactflags.1?trueWhether we can add the user as contact
block_contactflags.2?trueWhether we can block the user
share_contactflags.3?trueWhether we can share the user's contact
need_contacts_exceptionflags.4?trueWhether a special exception for contacts is needed
report_geoflags.5?trueWhether we can report a geogroup is irrelevant for this location
autoarchivedflags.7?trueWhether this peer was automatically archived according to privacy settings
geo_distanceflags.6?intDistance in meters between us and this peer
-

Type

-

PeerSettings

-

Related pages

-

globalPrivacySettings

-

Global privacy settings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerUser.html b/data/core.telegram.org/constructor/peerUser.html deleted file mode 100644 index 318e2b3a30..0000000000 --- a/data/core.telegram.org/constructor/peerUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerUser - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/phone.phoneCall b/data/core.telegram.org/constructor/phone.phoneCall deleted file mode 100644 index 2c4ffdc687..0000000000 --- a/data/core.telegram.org/constructor/phone.phoneCall +++ /dev/null @@ -1,152 +0,0 @@ - - - - - phone.phoneCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.phoneCall

- -

A VoIP phone call

-

-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_callPhoneCallThe VoIP phone call
usersVector<User>VoIP phone call participants
-

Type

-

phone.PhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCall.html b/data/core.telegram.org/constructor/phoneCall.html deleted file mode 100644 index 7a951d936c..0000000000 --- a/data/core.telegram.org/constructor/phoneCall.html +++ /dev/null @@ -1,209 +0,0 @@ - - - - - phoneCall - - - - - - - - - - - - - -
- -
-
-
- -

phoneCall

- -

Phone call

-

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

-

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_idintUser ID of the creator of the call
participant_idintUser ID of the other participant in the call
g_a_or_bbytesParameter for key exchange
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
connectionsVector<PhoneConnection>List of endpoints the user can connect to to exchange call data
start_dateintWhen was the call actually started
-

Type

-

PhoneCall

-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallAccepted.html b/data/core.telegram.org/constructor/phoneCallAccepted.html deleted file mode 100644 index f2e4ccef2e..0000000000 --- a/data/core.telegram.org/constructor/phoneCallAccepted.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - phoneCallAccepted - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallAccepted

- -

An accepted phone call

-

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

-

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_idintID of the call creator
participant_idintID of the other user in the call
g_bbytesB parameter for secure E2E phone call key exchange
protocolPhoneCallProtocolProtocol to use for phone call
-

Type

-

PhoneCall

-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html deleted file mode 100644 index cbbda4fcbb..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonBusy - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonBusy

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html deleted file mode 100644 index 12aecd88f7..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonDisconnect - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonDisconnect

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html deleted file mode 100644 index c7cb9efb08..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonHangup - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonHangup

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html deleted file mode 100644 index 46e60f23e5..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonMissed - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonMissed

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscarded.html b/data/core.telegram.org/constructor/phoneCallDiscarded.html deleted file mode 100644 index cb59da4f72..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscarded.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - phoneCallDiscarded - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscarded

- -

Indicates a discarded phone call

-

-
phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
need_ratingflags.2?trueWhether the server required the user to rate the call
need_debugflags.3?trueWhether the server required the client to send the libtgvoip call debug data
videoflags.6?trueWhether the call was a video call
idlongCall ID
reasonflags.0?PhoneCallDiscardReasonWhy was the phone call discarded
durationflags.1?intDuration of the phone call in seconds
-

Type

-

PhoneCall

-

Related pages

-

phone.setCallRating

-

Rate a call

-

phone.saveCallDebug

-

Send phone call debug data to server

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallEmpty.html b/data/core.telegram.org/constructor/phoneCallEmpty.html deleted file mode 100644 index 0427b8dd57..0000000000 --- a/data/core.telegram.org/constructor/phoneCallEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - phoneCallEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallProtocol.html b/data/core.telegram.org/constructor/phoneCallProtocol.html deleted file mode 100644 index 264d6d9a17..0000000000 --- a/data/core.telegram.org/constructor/phoneCallProtocol.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - phoneCallProtocol - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallProtocol

- -

Protocol info for libtgvoip

-

-
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
udp_p2pflags.0?trueWhether to allow P2P connection to the other participant
udp_reflectorflags.1?trueWhether to allow connection to the other participants through the reflector servers
min_layerintMinimum layer for remote libtgvoip
max_layerintMaximum layer for remote libtgvoip
library_versionsVector<string>When using phone.requestCall and phone.acceptCall, specify all library versions supported by the client.
The server will merge and choose the best library version supported by both peers, returning only the best value in the result of the callee's phone.acceptCall and in the phoneCallAccepted update received by the caller.
-

Type

-

PhoneCallProtocol

-

Related pages

-

phone.requestCall

-

Start a telegram phone call

-

phone.acceptCall

-

Accept incoming call

-

phoneCallAccepted

-

An accepted phone call

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallRequested.html b/data/core.telegram.org/constructor/phoneCallRequested.html deleted file mode 100644 index 9fe04d4505..0000000000 --- a/data/core.telegram.org/constructor/phoneCallRequested.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - phoneCallRequested - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallRequested

- -

Requested phone call

-

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

-

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_idintID of the creator of the phone call
participant_idintID of the other participant of the phone call
g_a_hashbytesParameter for key exchange
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
-

Type

-

PhoneCall

-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallWaiting.html b/data/core.telegram.org/constructor/phoneCallWaiting.html deleted file mode 100644 index 914d1259dd..0000000000 --- a/data/core.telegram.org/constructor/phoneCallWaiting.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - phoneCallWaiting - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallWaiting

- -

Incoming phone call

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueIs this a video call
idlongCall ID
access_hashlongAccess hash
dateintDate
admin_idintAdmin ID
participant_idintParticipant ID
protocolPhoneCallProtocolPhone call protocol info
receive_dateflags.0?intWhen was the phone call received
-

Type

-

PhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneConnection.html b/data/core.telegram.org/constructor/phoneConnection.html deleted file mode 100644 index abdc79a533..0000000000 --- a/data/core.telegram.org/constructor/phoneConnection.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - phoneConnection - - - - - - - - - - - - - -
- -
-
-
- -

phoneConnection

- -

Identifies an endpoint that can be used to connect to the other user in a phone call

-

-
phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongEndpoint ID
ipstringIP address of endpoint
ipv6stringIPv6 address of endpoint
portintPort ID
peer_tagbytesOur peer tag
-

Type

-

PhoneConnection

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneConnectionWebrtc.html b/data/core.telegram.org/constructor/phoneConnectionWebrtc.html deleted file mode 100644 index daf6f94546..0000000000 --- a/data/core.telegram.org/constructor/phoneConnectionWebrtc.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - phoneConnectionWebrtc - - - - - - - - - - - - - -
- -
-
-
- -

phoneConnectionWebrtc

- -

WebRTC connection parameters

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
turnflags.0?trueWhether this is a TURN endpoint
stunflags.1?trueWhether this is a STUN endpoint
idlongEndpoint ID
ipstringIP address
ipv6stringIPv6 address
portintPort
usernamestringUsername
passwordstringPassword
-

Type

-

PhoneConnection

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photo.html b/data/core.telegram.org/constructor/photo.html deleted file mode 100644 index 975cd46ee7..0000000000 --- a/data/core.telegram.org/constructor/photo.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - photo - - - - - - - - - - - - - -
- -
-
-
- -

photo

- -

Photo

-

-
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_stickersflags.0?trueWhether the photo has mask stickers attached to it
idlongID
access_hashlongAccess hash
file_referencebytesfile reference
dateintDate of upload
sizesVector<PhotoSize>Available sizes for download
video_sizesflags.1?Vector<VideoSize>For animated profiles, the MPEG4 videos
dc_idintDC ID to use for download
-

Type

-

Photo

-

Related pages

-

File references

-

How to handle file references.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoCachedSize.html b/data/core.telegram.org/constructor/photoCachedSize.html deleted file mode 100644 index 2f6efa019b..0000000000 --- a/data/core.telegram.org/constructor/photoCachedSize.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - photoCachedSize - - - - - - - - - - - - - -
- -
-
-
- -

photoCachedSize

- -

Description of an image and its content.

-

-
photoCachedSize#e9a734fa type:string location:FileLocation w:int h:int bytes:bytes = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
locationFileLocationFile location
wintImage width
hintImage height
bytesbytesBinary data, file content
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See here.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoEmpty.html b/data/core.telegram.org/constructor/photoEmpty.html deleted file mode 100644 index 18ff534822..0000000000 --- a/data/core.telegram.org/constructor/photoEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - photoEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoPathSize.html b/data/core.telegram.org/constructor/photoPathSize.html deleted file mode 100644 index 516cf9463d..0000000000 --- a/data/core.telegram.org/constructor/photoPathSize.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - photoPathSize - - - - - - - - - - - - - -
- -
-
-
- -

photoPathSize

- -

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringAlways j
bytesbytesCompressed SVG path payload, see here for decompression instructions
-

Type

-

PhotoSize

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoSize.html b/data/core.telegram.org/constructor/photoSize.html deleted file mode 100644 index f0a581c810..0000000000 --- a/data/core.telegram.org/constructor/photoSize.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - photoSize - - - - - - - - - - - - - -
- -
-
-
- -

photoSize

- -

Image description.

-

-
photoSize#77bfb61b type:string location:FileLocation w:int h:int size:int = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
locationFileLocationFile location
wintImage width
hintImage height
sizeintFile size
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See here.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoSizeEmpty.html b/data/core.telegram.org/constructor/photoSizeEmpty.html deleted file mode 100644 index b5b911a269..0000000000 --- a/data/core.telegram.org/constructor/photoSizeEmpty.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - photoSizeEmpty - - - - - - - - - - - - - -
- -
-
-
- -

photoSizeEmpty

- -

Empty constructor. Image with this thumbnail is unavailable.

-

-
photoSizeEmpty#e17e23c type:string = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type (see. photoSize)
-

Type

-

PhotoSize

-

Related pages

-

photoSize

-

Image description.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoSizeProgressive.html b/data/core.telegram.org/constructor/photoSizeProgressive.html deleted file mode 100644 index 6e4fefb363..0000000000 --- a/data/core.telegram.org/constructor/photoSizeProgressive.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - photoSizeProgressive - - - - - - - - - - - - - -
- -
-
-
- -

photoSizeProgressive

- -

Progressively encoded photosize

-

-
photoSizeProgressive#5aa86a51 type:string location:FileLocation w:int h:int sizes:Vector<int> = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringPhotosize type
locationFileLocationFile location
wintPhoto width
hintPhoto height
sizesVector<int>Sizes of progressive JPEG file prefixes, which can be used to preliminarily show the image.
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See here.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoStrippedSize.html b/data/core.telegram.org/constructor/photoStrippedSize.html deleted file mode 100644 index c9cdb2218c..0000000000 --- a/data/core.telegram.org/constructor/photoStrippedSize.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - photoStrippedSize - - - - - - - - - - - - - -
- -
-
-
- -

photoStrippedSize

- -

A low-resolution compressed JPG payload

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
bytesbytesThumbnail data, see here for more info on decompression »
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See the photoSize constructor.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

photoSize

-

Image description.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photos.photo b/data/core.telegram.org/constructor/photos.photo deleted file mode 100644 index 1c58ff2f7b..0000000000 --- a/data/core.telegram.org/constructor/photos.photo +++ /dev/null @@ -1,152 +0,0 @@ - - - - - photos.photo - - - - - - - - - - - - - -
- -
-
-
- -

photos.photo

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photos.photos b/data/core.telegram.org/constructor/photos.photos deleted file mode 100644 index 4ae25160ba..0000000000 --- a/data/core.telegram.org/constructor/photos.photos +++ /dev/null @@ -1,152 +0,0 @@ - - - - - photos.photos - - - - - - - - - - - - - -
- -
-
-
- -

photos.photos

- -

Full list of photos with auxiliary data.

-

-
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
-

Type

-

photos.Photos

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photos.photosSlice b/data/core.telegram.org/constructor/photos.photosSlice deleted file mode 100644 index cab6b753b1..0000000000 --- a/data/core.telegram.org/constructor/photos.photosSlice +++ /dev/null @@ -1,157 +0,0 @@ - - - - - photos.photosSlice - - - - - - - - - - - - - -
- -
-
-
- -

photos.photosSlice

- -

Incomplete list of photos with auxiliary data.

-

-
photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of photos
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
-

Type

-

photos.Photos

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/poll.html b/data/core.telegram.org/constructor/poll.html deleted file mode 100644 index 1ab2df6b22..0000000000 --- a/data/core.telegram.org/constructor/poll.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - poll - - - - - - - - - - - - - -
- -
-
-
- -

poll

- -

Poll

-

-
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID of the poll
flags#Flags, see TL conditional fields
closedflags.0?trueWhether the poll is closed and doesn't accept any more answers
public_votersflags.1?trueWhether cast votes are publicly visible to all users (non-anonymous poll)
multiple_choiceflags.2?trueWhether multiple options can be chosen as answer
quizflags.3?trueWhether this is a quiz (with wrong and correct answers, results shown in the return type)
questionstringThe question of the poll
answersVector<PollAnswer>The possible answers, vote using messages.sendVote.
close_periodflags.4?intAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateflags.5?intPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period.
-

Type

-

Poll

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pollAnswer.html b/data/core.telegram.org/constructor/pollAnswer.html deleted file mode 100644 index 4ecd48ca73..0000000000 --- a/data/core.telegram.org/constructor/pollAnswer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - pollAnswer - - - - - - - - - - - - - -
- -
-
-
- -

pollAnswer

- -

A possible answer of a poll

-

-
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textstringTextual representation of the answer
optionbytesThe param that has to be passed to messages.sendVote.
-

Type

-

PollAnswer

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pollAnswerVoters.html b/data/core.telegram.org/constructor/pollAnswerVoters.html deleted file mode 100644 index 403fe8f686..0000000000 --- a/data/core.telegram.org/constructor/pollAnswerVoters.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - pollAnswerVoters - - - - - - - - - - - - - -
- -
-
-
- -

pollAnswerVoters

- -

A poll answer, and how users voted on it

-

-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
chosenflags.0?trueWhether we have chosen this answer
correctflags.1?trueFor quizes, whether the option we have chosen is correct
optionbytesThe param that has to be passed to messages.sendVote.
votersintHow many users voted for this option
-

Type

-

PollAnswerVoters

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pollResults.html b/data/core.telegram.org/constructor/pollResults.html deleted file mode 100644 index f65e55a4f3..0000000000 --- a/data/core.telegram.org/constructor/pollResults.html +++ /dev/null @@ -1,184 +0,0 @@ - - - - - pollResults - - - - - - - - - - - - - -
- -
-
-
- -

pollResults

- -

Results of 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;

-

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<int>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 deleted file mode 100644 index 2b11ac1af4..0000000000 --- a/data/core.telegram.org/constructor/popularContact.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - popularContact - - - - - - - - - - - - - -
- -
-
-
- -

popularContact

- -

Popular contact

-

-
popularContact#5ce14175 client_id:long importers:int = PopularContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
client_idlongContact identifier
importersintHow many people imported this contact
-

Type

-

PopularContact

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/postAddress.html b/data/core.telegram.org/constructor/postAddress.html deleted file mode 100644 index ef865ba13d..0000000000 --- a/data/core.telegram.org/constructor/postAddress.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - postAddress - - - - - - - - - - - - - -
- -
-
-
- -

postAddress

- -

Shipping address

-

-
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
street_line1stringFirst line for the address
street_line2stringSecond line for the address
citystringCity
statestringState, if applicable (empty otherwise)
country_iso2stringISO 3166-1 alpha-2 country code
post_codestringAddress post code
-

Type

-

PostAddress

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html b/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html deleted file mode 100644 index a856fb6740..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyAddedByPhone - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyAddedByPhone

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyChatInvite.html b/data/core.telegram.org/constructor/privacyKeyChatInvite.html deleted file mode 100644 index c727e9bb63..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyChatInvite.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyChatInvite - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyForwards.html b/data/core.telegram.org/constructor/privacyKeyForwards.html deleted file mode 100644 index be8641d55f..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyForwards.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyForwards - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyForwards

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyPhoneCall.html b/data/core.telegram.org/constructor/privacyKeyPhoneCall.html deleted file mode 100644 index 9400641de5..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyPhoneCall.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneCall - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyPhoneNumber.html b/data/core.telegram.org/constructor/privacyKeyPhoneNumber.html deleted file mode 100644 index 45df27cc77..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyPhoneNumber.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneNumber - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html b/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html deleted file mode 100644 index 2c5c7c671c..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneP2P - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyProfilePhoto.html b/data/core.telegram.org/constructor/privacyKeyProfilePhoto.html deleted file mode 100644 index 55b3ad5e75..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyProfilePhoto.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyProfilePhoto - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html b/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html deleted file mode 100644 index 5acf4034b1..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyStatusTimestamp - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueAllowAll.html b/data/core.telegram.org/constructor/privacyValueAllowAll.html deleted file mode 100644 index 2519224637..0000000000 --- a/data/core.telegram.org/constructor/privacyValueAllowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueAllowAll - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html b/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html deleted file mode 100644 index 4445ec5a04..0000000000 --- a/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueAllowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowChatParticipants

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueAllowContacts.html b/data/core.telegram.org/constructor/privacyValueAllowContacts.html deleted file mode 100644 index f8f9d65754..0000000000 --- a/data/core.telegram.org/constructor/privacyValueAllowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueAllowContacts - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueAllowUsers.html b/data/core.telegram.org/constructor/privacyValueAllowUsers.html deleted file mode 100644 index 1693133a03..0000000000 --- a/data/core.telegram.org/constructor/privacyValueAllowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueAllowUsers - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowUsers

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueDisallowAll.html b/data/core.telegram.org/constructor/privacyValueDisallowAll.html deleted file mode 100644 index 34c612d7a8..0000000000 --- a/data/core.telegram.org/constructor/privacyValueDisallowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueDisallowAll - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueDisallowChatParticipants.html b/data/core.telegram.org/constructor/privacyValueDisallowChatParticipants.html deleted file mode 100644 index b9275a1a74..0000000000 --- a/data/core.telegram.org/constructor/privacyValueDisallowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueDisallowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowChatParticipants

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueDisallowContacts.html b/data/core.telegram.org/constructor/privacyValueDisallowContacts.html deleted file mode 100644 index 4413899dff..0000000000 --- a/data/core.telegram.org/constructor/privacyValueDisallowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueDisallowContacts - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueDisallowUsers.html b/data/core.telegram.org/constructor/privacyValueDisallowUsers.html deleted file mode 100644 index 99d3910cac..0000000000 --- a/data/core.telegram.org/constructor/privacyValueDisallowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueDisallowUsers - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowUsers

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/receivedNotifyMessage.html b/data/core.telegram.org/constructor/receivedNotifyMessage.html deleted file mode 100644 index 5de11fa8f5..0000000000 --- a/data/core.telegram.org/constructor/receivedNotifyMessage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - receivedNotifyMessage - - - - - - - - - - - - - -
- -
-
-
- -

receivedNotifyMessage

- -

Message ID, for which PUSH-notifications were cancelled.

-

-
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID, for which PUSH-notifications were canceled
flagsintReserved for future use
-

Type

-

ReceivedNotifyMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlChat.html b/data/core.telegram.org/constructor/recentMeUrlChat.html deleted file mode 100644 index e49954a84c..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlChat.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlChat - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlChat

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlChatInvite.html b/data/core.telegram.org/constructor/recentMeUrlChatInvite.html deleted file mode 100644 index 5be8115fb8..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlChatInvite.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlChatInvite

- -

Recent t.me invite link to a chat

-

-
recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringt.me URL
chat_inviteChatInviteChat invitation
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlStickerSet.html b/data/core.telegram.org/constructor/recentMeUrlStickerSet.html deleted file mode 100644 index c99cc11f0c..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlStickerSet.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlStickerSet

- -

Recent t.me stickerset installation URL

-

-
recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringt.me URL
setStickerSetCoveredStickerset
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlUnknown.html b/data/core.telegram.org/constructor/recentMeUrlUnknown.html deleted file mode 100644 index 858df884b4..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlUnknown.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - recentMeUrlUnknown - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlUser.html b/data/core.telegram.org/constructor/recentMeUrlUser.html deleted file mode 100644 index 2a956e9e92..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlUser.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlUser - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlUser

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/replyInlineMarkup.html b/data/core.telegram.org/constructor/replyInlineMarkup.html deleted file mode 100644 index 8d3491bfd2..0000000000 --- a/data/core.telegram.org/constructor/replyInlineMarkup.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - replyInlineMarkup - - - - - - - - - - - - - -
- -
-
-
- -

replyInlineMarkup

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/replyKeyboardForceReply.html b/data/core.telegram.org/constructor/replyKeyboardForceReply.html deleted file mode 100644 index e56a81b0d7..0000000000 --- a/data/core.telegram.org/constructor/replyKeyboardForceReply.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - replyKeyboardForceReply - - - - - - - - - - - - - -
- -
-
-
- -

replyKeyboardForceReply

- -

Force the user to send a reply

-

-
replyKeyboardForceReply#f4108aa0 flags:# single_use:flags.1?true selective:flags.2?true = 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.
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/replyKeyboardHide.html b/data/core.telegram.org/constructor/replyKeyboardHide.html deleted file mode 100644 index d9d8fae180..0000000000 --- a/data/core.telegram.org/constructor/replyKeyboardHide.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - replyKeyboardHide - - - - - - - - - - - - - -
- -
-
-
- -

replyKeyboardHide

- -

Hide sent bot keyboard

-

-
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
selectiveflags.2?trueUse this flag if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/replyKeyboardMarkup.html b/data/core.telegram.org/constructor/replyKeyboardMarkup.html deleted file mode 100644 index 0a54061141..0000000000 --- a/data/core.telegram.org/constructor/replyKeyboardMarkup.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - replyKeyboardMarkup - - - - - - - - - - - - - -
- -
-
-
- -

replyKeyboardMarkup

- -

Bot keyboard

-

-
replyKeyboardMarkup#3502758c flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> = 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
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/restrictionReason.html b/data/core.telegram.org/constructor/restrictionReason.html deleted file mode 100644 index f10a81ba73..0000000000 --- a/data/core.telegram.org/constructor/restrictionReason.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - restrictionReason - - - - - - - - - - - - - -
- -
-
-
- -

restrictionReason

- -

Restriction reason.

-

Contains the reason why access to a certain object must be restricted. Clients are supposed to deny access to the channel if the platform field is equal to all or to the current platform (ios, android, wp, etc.). Platforms can be concatenated (ios-android, ios-wp), unknown platforms are to be ignored. The text is the error message that should be shown to the user.

-

-
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
platformstringPlatform identifier (ios, android, wp, all, etc.), can be concatenated with a dash as separator (android-ios, ios-wp, etc)
reasonstringRestriction reason (porno, terms, etc.)
textstringError message to be shown to the user
-

Type

-

RestrictionReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/savedPhoneContact.html b/data/core.telegram.org/constructor/savedPhoneContact.html deleted file mode 100644 index 24432b64aa..0000000000 --- a/data/core.telegram.org/constructor/savedPhoneContact.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - savedPhoneContact - - - - - - - - - - - - - -
- -
-
-
- -

savedPhoneContact

- -

Saved contact

-

-
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phonestringPhone number
first_namestringFirst name
last_namestringLast name
dateintDate added
-

Type

-

SavedContact

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureCredentialsEncrypted.html b/data/core.telegram.org/constructor/secureCredentialsEncrypted.html deleted file mode 100644 index 9b264835d3..0000000000 --- a/data/core.telegram.org/constructor/secureCredentialsEncrypted.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - secureCredentialsEncrypted - - - - - - - - - - - - - -
- -
-
-
- -

secureCredentialsEncrypted

- -

Encrypted credentials required to decrypt telegram passport data.

-

-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
databytesEncrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication, as described in decrypting data »
hashbytesData hash for data authentication as described in decrypting data »
secretbytesSecret, encrypted with the bot's public RSA key, required for data decryption as described in decrypting data »
-

Type

-

SecureCredentialsEncrypted

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureData.html b/data/core.telegram.org/constructor/secureData.html deleted file mode 100644 index b6348caf11..0000000000 --- a/data/core.telegram.org/constructor/secureData.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - secureData - - - - - - - - - - - - - -
- -
-
-
- -

secureData

- -

Secure passport data, for more info see the passport docs »

-

-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
databytesData
data_hashbytesData hash
secretbytesSecret
-

Type

-

SecureData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureFile.html b/data/core.telegram.org/constructor/secureFile.html deleted file mode 100644 index e4fe25fde3..0000000000 --- a/data/core.telegram.org/constructor/secureFile.html +++ /dev/null @@ -1,180 +0,0 @@ - - - - - secureFile - - - - - - - - - - - - - -
- -
-
-
- -

secureFile

- -

Secure passport file, for more info see the passport docs »

-

-
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID
access_hashlongAccess hash
sizeintFile size
dc_idintDC ID
dateintDate of upload
file_hashbytesFile hash
secretbytesSecret
-

Type

-

SecureFile

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureFileEmpty.html b/data/core.telegram.org/constructor/secureFileEmpty.html deleted file mode 100644 index f4bd72ea3f..0000000000 --- a/data/core.telegram.org/constructor/secureFileEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureFileEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html deleted file mode 100644 index 3f84cb75e7..0000000000 --- a/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoPBKDF2HMACSHA512iter100000

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html deleted file mode 100644 index 1f006522f3..0000000000 --- a/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - securePasswordKdfAlgoSHA512 - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoSHA512

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html deleted file mode 100644 index 8dec999284..0000000000 --- a/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - securePasswordKdfAlgoUnknown - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoUnknown

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePlainEmail.html b/data/core.telegram.org/constructor/securePlainEmail.html deleted file mode 100644 index d90616c39a..0000000000 --- a/data/core.telegram.org/constructor/securePlainEmail.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - securePlainEmail - - - - - - - - - - - - - -
- -
-
-
- -

securePlainEmail

- -

Email address to use in telegram passport: it must be verified, first ».

-

-
securePlainEmail#21ec5a5f email:string = SecurePlainData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emailstringEmail address
-

Type

-

SecurePlainData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePlainPhone.html b/data/core.telegram.org/constructor/securePlainPhone.html deleted file mode 100644 index e050daa6fd..0000000000 --- a/data/core.telegram.org/constructor/securePlainPhone.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - securePlainPhone - - - - - - - - - - - - - -
- -
-
-
- -

securePlainPhone

- -

Phone number to use in telegram passport: it must be verified, first ».

-

-
securePlainPhone#7d6099dd phone:string = SecurePlainData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phonestringPhone number
-

Type

-

SecurePlainData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureRequiredType.html b/data/core.telegram.org/constructor/secureRequiredType.html deleted file mode 100644 index 80bdb04db2..0000000000 --- a/data/core.telegram.org/constructor/secureRequiredType.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - secureRequiredType - - - - - - - - - - - - - -
- -
-
-
- -

secureRequiredType

- -

Required type

-

-
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
native_namesflags.0?trueNative names
selfie_requiredflags.1?trueIs a selfie required
translation_requiredflags.2?trueIs a translation required
typeSecureValueTypeSecure value type
-

Type

-

SecureRequiredType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureRequiredTypeOneOf.html b/data/core.telegram.org/constructor/secureRequiredTypeOneOf.html deleted file mode 100644 index 6a511b31a0..0000000000 --- a/data/core.telegram.org/constructor/secureRequiredTypeOneOf.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - secureRequiredTypeOneOf - - - - - - - - - - - - - -
- -
-
-
- -

secureRequiredTypeOneOf

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureSecretSettings.html b/data/core.telegram.org/constructor/secureSecretSettings.html deleted file mode 100644 index 078823b72f..0000000000 --- a/data/core.telegram.org/constructor/secureSecretSettings.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - secureSecretSettings - - - - - - - - - - - - - -
- -
-
-
- -

secureSecretSettings

- -

Secure settings

-

-
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
secure_algoSecurePasswordKdfAlgoSecure KDF algo
secure_secretbytesSecure secret
secure_secret_idlongSecret ID
-

Type

-

SecureSecretSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValue.html b/data/core.telegram.org/constructor/secureValue.html deleted file mode 100644 index 6f4d4eaf4d..0000000000 --- a/data/core.telegram.org/constructor/secureValue.html +++ /dev/null @@ -1,194 +0,0 @@ - - - - - secureValue - - - - - - - - - - - - - -
- -
-
-
- -

secureValue

- -

Secure value

-

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

-

Parameters

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

Type

-

SecureValue

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueError.html b/data/core.telegram.org/constructor/secureValueError.html deleted file mode 100644 index 06b2d4e891..0000000000 --- a/data/core.telegram.org/constructor/secureValueError.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - secureValueError - - - - - - - - - - - - - -
- -
-
-
- -

secureValueError

- -

Secure value error

-

-
secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeType of element which has the issue
hashbytesHash
textstringError message
-

Type

-

SecureValueError

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorData.html b/data/core.telegram.org/constructor/secureValueErrorData.html deleted file mode 100644 index 3ca6cd4601..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorData.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - secureValueErrorData - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorData

- -

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

-

-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeThe section of the user's Telegram Passport which has the error, one of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeAddress
data_hashbytesData hash
fieldstringName of the data field which has the error
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeAddress

-

Address

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorFile.html b/data/core.telegram.org/constructor/secureValueErrorFile.html deleted file mode 100644 index 84a251349c..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorFile.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - secureValueErrorFile - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFile

- -

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

-

-
secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorFiles.html b/data/core.telegram.org/constructor/secureValueErrorFiles.html deleted file mode 100644 index 6f7bf63ab4..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorFiles.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - secureValueErrorFiles - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFiles

- -

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

-

-
secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>File hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorFrontSide.html b/data/core.telegram.org/constructor/secureValueErrorFrontSide.html deleted file mode 100644 index f7b2dd7889..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorFrontSide.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - secureValueErrorFrontSide - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFrontSide

- -

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

-

-
secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorReverseSide.html b/data/core.telegram.org/constructor/secureValueErrorReverseSide.html deleted file mode 100644 index 4c1c149eae..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorReverseSide.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - secureValueErrorReverseSide - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorReverseSide

- -

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

-

-
secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeDriverLicense, secureValueTypeIdentityCard
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorSelfie.html b/data/core.telegram.org/constructor/secureValueErrorSelfie.html deleted file mode 100644 index 7d359d5a0d..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorSelfie.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - secureValueErrorSelfie - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorSelfie

- -

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

-

-
secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html b/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html deleted file mode 100644 index c022023ad2..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - secureValueErrorTranslationFile - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorTranslationFile

- -

Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

-

-
secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html b/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html deleted file mode 100644 index 1c817d5ebd..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - secureValueErrorTranslationFiles - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorTranslationFiles

- -

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation changes.

-

-
secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>Hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueHash.html b/data/core.telegram.org/constructor/secureValueHash.html deleted file mode 100644 index 0aac3cbd15..0000000000 --- a/data/core.telegram.org/constructor/secureValueHash.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - secureValueHash - - - - - - - - - - - - - -
- -
-
-
- -

secureValueHash

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeAddress.html b/data/core.telegram.org/constructor/secureValueTypeAddress.html deleted file mode 100644 index b31a85db46..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeAddress.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeAddress - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeBankStatement.html b/data/core.telegram.org/constructor/secureValueTypeBankStatement.html deleted file mode 100644 index 69f1e69fe4..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeBankStatement.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeBankStatement - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html b/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html deleted file mode 100644 index 4bacb3a060..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeDriverLicense - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeEmail.html b/data/core.telegram.org/constructor/secureValueTypeEmail.html deleted file mode 100644 index c191a46878..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeEmail.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeEmail - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html b/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html deleted file mode 100644 index 551e975046..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeIdentityCard - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html b/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html deleted file mode 100644 index 60b6e0706e..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - secureValueTypeInternalPassport - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeInternalPassport

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypePassport.html b/data/core.telegram.org/constructor/secureValueTypePassport.html deleted file mode 100644 index 5b81ca1af1..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypePassport.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePassport - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html b/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html deleted file mode 100644 index ce79aafd3b..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - secureValueTypePassportRegistration - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePassportRegistration

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypePersonalDetails.html b/data/core.telegram.org/constructor/secureValueTypePersonalDetails.html deleted file mode 100644 index 5992af1e29..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypePersonalDetails.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePersonalDetails - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypePhone.html b/data/core.telegram.org/constructor/secureValueTypePhone.html deleted file mode 100644 index 8592b4e0d9..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypePhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePhone - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html b/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html deleted file mode 100644 index e3bf002518..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeRentalAgreement - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html b/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html deleted file mode 100644 index 1cbaf54183..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeTemporaryRegistration - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeTemporaryRegistration

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html b/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html deleted file mode 100644 index b67f552164..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeUtilityBill - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageCancelAction.html b/data/core.telegram.org/constructor/sendMessageCancelAction.html deleted file mode 100644 index a894626046..0000000000 --- a/data/core.telegram.org/constructor/sendMessageCancelAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageCancelAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageCancelAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageChooseContactAction.html b/data/core.telegram.org/constructor/sendMessageChooseContactAction.html deleted file mode 100644 index 99d4547b01..0000000000 --- a/data/core.telegram.org/constructor/sendMessageChooseContactAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageChooseContactAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageChooseContactAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageGamePlayAction.html b/data/core.telegram.org/constructor/sendMessageGamePlayAction.html deleted file mode 100644 index fe4d61e011..0000000000 --- a/data/core.telegram.org/constructor/sendMessageGamePlayAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageGamePlayAction - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html b/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html deleted file mode 100644 index 6d7f77e83e..0000000000 --- a/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageGeoLocationAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageGeoLocationAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html b/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html deleted file mode 100644 index 0686f70693..0000000000 --- a/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordAudioAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordAudioAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html b/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html deleted file mode 100644 index cc113b171e..0000000000 --- a/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordRoundAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordRoundAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html b/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html deleted file mode 100644 index ca8bfc0983..0000000000 --- a/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordVideoAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordVideoAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageTypingAction.html b/data/core.telegram.org/constructor/sendMessageTypingAction.html deleted file mode 100644 index e9c652edcf..0000000000 --- a/data/core.telegram.org/constructor/sendMessageTypingAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageTypingAction - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html b/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html deleted file mode 100644 index 935694469c..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadAudioAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadAudioAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html b/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html deleted file mode 100644 index 0ed8dbad29..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadDocumentAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadDocumentAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html b/data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html deleted file mode 100644 index d0e071d26d..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadPhotoAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadPhotoAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadRoundAction.html b/data/core.telegram.org/constructor/sendMessageUploadRoundAction.html deleted file mode 100644 index cb00b21b6f..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadRoundAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadRoundAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadRoundAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html b/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html deleted file mode 100644 index 0ad378d458..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadVideoAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadVideoAction

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/shippingOption.html b/data/core.telegram.org/constructor/shippingOption.html deleted file mode 100644 index 1a410cd4db..0000000000 --- a/data/core.telegram.org/constructor/shippingOption.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - shippingOption - - - - - - - - - - - - - -
- -
-
-
- -

shippingOption

- -

Shipping option

-

-
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringOption ID
titlestringTitle
pricesVector<LabeledPrice>List of price portions
-

Type

-

ShippingOption

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stats.broadcastStats b/data/core.telegram.org/constructor/stats.broadcastStats deleted file mode 100644 index f62c321618..0000000000 --- a/data/core.telegram.org/constructor/stats.broadcastStats +++ /dev/null @@ -1,220 +0,0 @@ - - - - - stats.broadcastStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.broadcastStats

- -

Channel statistics.

-

-
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
followersStatsAbsValueAndPrevFollower count change for period in consideration
views_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
shares_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date)
enabled_notificationsStatsPercentValuePercentage of subscribers with enabled notifications
growth_graphStatsGraphChannel growth graph (absolute subscriber count)
followers_graphStatsGraphFollowers growth graph (relative subscriber count)
mute_graphStatsGraphMuted users graph (relative)
top_hours_graphStatsGraphViews per hour graph (absolute)
interactions_graphStatsGraphInteractions graph (absolute)
iv_interactions_graphStatsGraphIV interactions graph (absolute)
views_by_source_graphStatsGraphViews by source graph (absolute)
new_followers_by_source_graphStatsGraphNew followers by source graph (absolute)
languages_graphStatsGraphSubscriber language graph (piechart)
recent_message_interactionsVector<MessageInteractionCounters>Recent message interactions
-

Type

-

stats.BroadcastStats

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stats.megagroupStats b/data/core.telegram.org/constructor/stats.megagroupStats deleted file mode 100644 index edfb000450..0000000000 --- a/data/core.telegram.org/constructor/stats.megagroupStats +++ /dev/null @@ -1,230 +0,0 @@ - - - - - stats.megagroupStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.megagroupStats

- -

Supergroup statistics

-

-
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
membersStatsAbsValueAndPrevMember count change for period in consideration
messagesStatsAbsValueAndPrevMessage number change for period in consideration
viewersStatsAbsValueAndPrevNumber of users that viewed messages, for range in consideration
postersStatsAbsValueAndPrevNumber of users that posted messages, for range in consideration
growth_graphStatsGraphSupergroup growth graph (absolute subscriber count)
members_graphStatsGraphMembers growth (relative subscriber count)
new_members_by_source_graphStatsGraphNew members by source graph
languages_graphStatsGraphSubscriber language graph (piechart)
messages_graphStatsGraphMessage activity graph (stacked bar graph, message type)
actions_graphStatsGraphGroup activity graph (deleted, modified messages, blocked users)
top_hours_graphStatsGraphActivity per hour graph (absolute)
weekdays_graphStatsGraphActivity per day of week graph (absolute)
top_postersVector<StatsGroupTopPoster>Info about most active group members
top_adminsVector<StatsGroupTopAdmin>Info about most active group admins
top_invitersVector<StatsGroupTopInviter>Info about most active group inviters
usersVector<User>Info about users mentioned in statistics
-

Type

-

stats.MegagroupStats

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stats.messageStats b/data/core.telegram.org/constructor/stats.messageStats deleted file mode 100644 index d3e4ad5c5e..0000000000 --- a/data/core.telegram.org/constructor/stats.messageStats +++ /dev/null @@ -1,147 +0,0 @@ - - - - - stats.messageStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.messageStats

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsAbsValueAndPrev.html b/data/core.telegram.org/constructor/statsAbsValueAndPrev.html deleted file mode 100644 index 2b695fa832..0000000000 --- a/data/core.telegram.org/constructor/statsAbsValueAndPrev.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - statsAbsValueAndPrev - - - - - - - - - - - - - -
- -
-
-
- -

statsAbsValueAndPrev

- -

Statistics value couple; intial and final value for period of time currently in consideration

-

-
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
currentdoubleCurrent value
previousdoublePrevious value
-

Type

-

StatsAbsValueAndPrev

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsDateRangeDays.html b/data/core.telegram.org/constructor/statsDateRangeDays.html deleted file mode 100644 index ba8179edad..0000000000 --- a/data/core.telegram.org/constructor/statsDateRangeDays.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - statsDateRangeDays - - - - - - - - - - - - - -
- -
-
-
- -

statsDateRangeDays

- -

Channel statistics date range

-

-
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
min_dateintInitial date
max_dateintFinal date
-

Type

-

StatsDateRangeDays

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGraph.html b/data/core.telegram.org/constructor/statsGraph.html deleted file mode 100644 index d3ff8af24a..0000000000 --- a/data/core.telegram.org/constructor/statsGraph.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - statsGraph - - - - - - - - - - - - - -
- -
-
-
- -

statsGraph

- -

Channel statistics graph

-

-
statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
jsonDataJSONStatistics data
zoom_tokenflags.0?stringZoom token
-

Type

-

StatsGraph

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGraphAsync.html b/data/core.telegram.org/constructor/statsGraphAsync.html deleted file mode 100644 index 170c52637f..0000000000 --- a/data/core.telegram.org/constructor/statsGraphAsync.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - statsGraphAsync - - - - - - - - - - - - - -
- -
-
-
- -

statsGraphAsync

- -

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

-

-
statsGraphAsync#4a27eb2d token:string = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
tokenstringToken to use for fetching the async graph
-

Type

-

StatsGraph

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

stats.loadAsyncGraph

-

Load channel statistics graph asynchronously

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGraphError.html b/data/core.telegram.org/constructor/statsGraphError.html deleted file mode 100644 index 7933b666b8..0000000000 --- a/data/core.telegram.org/constructor/statsGraphError.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - statsGraphError - - - - - - - - - - - - - -
- -
-
-
- -

statsGraphError

- -

An error occurred while generating the statistics graph

-

-
statsGraphError#bedc9822 error:string = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
errorstringThe error
-

Type

-

StatsGraph

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGroupTopAdmin.html b/data/core.telegram.org/constructor/statsGroupTopAdmin.html deleted file mode 100644 index ec8bbd4a29..0000000000 --- a/data/core.telegram.org/constructor/statsGroupTopAdmin.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - statsGroupTopAdmin - - - - - - - - - - - - - -
- -
-
-
- -

statsGroupTopAdmin

- -

Information about an active admin in a supergroup

-

-
statsGroupTopAdmin#6014f412 user_id:int deleted:int kicked:int banned:int = StatsGroupTopAdmin;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser ID
deletedintNumber of deleted messages for statistics period in consideration
kickedintNumber of kicked users for statistics period in consideration
bannedintNumber of banned users for statistics period in consideration
-

Type

-

StatsGroupTopAdmin

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGroupTopInviter.html b/data/core.telegram.org/constructor/statsGroupTopInviter.html deleted file mode 100644 index d6205370e2..0000000000 --- a/data/core.telegram.org/constructor/statsGroupTopInviter.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - statsGroupTopInviter - - - - - - - - - - - - - -
- -
-
-
- -

statsGroupTopInviter

- -

Information about an active supergroup inviter

-

-
statsGroupTopInviter#31962a4c user_id:int invitations:int = StatsGroupTopInviter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser ID
invitationsintNumber of invitations for statistics period in consideration
-

Type

-

StatsGroupTopInviter

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGroupTopPoster.html b/data/core.telegram.org/constructor/statsGroupTopPoster.html deleted file mode 100644 index 392a88b38b..0000000000 --- a/data/core.telegram.org/constructor/statsGroupTopPoster.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - statsGroupTopPoster - - - - - - - - - - - - - -
- -
-
-
- -

statsGroupTopPoster

- -

Information about an active user in a supergroup

-

-
statsGroupTopPoster#18f3d0f7 user_id:int messages:int avg_chars:int = StatsGroupTopPoster;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser 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 deleted file mode 100644 index c28edcfca4..0000000000 --- a/data/core.telegram.org/constructor/statsPercentValue.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - statsPercentValue - - - - - - - - - - - - - -
- -
-
-
- -

statsPercentValue

- -

Channel statistics percentage.
-Compute the percentage simply by doing part * total / 100

-

-
statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
partdoublePartial value
totaldoubleTotal value
-

Type

-

StatsPercentValue

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsURL.html b/data/core.telegram.org/constructor/statsURL.html deleted file mode 100644 index dda45aac13..0000000000 --- a/data/core.telegram.org/constructor/statsURL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - statsURL - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickerPack.html b/data/core.telegram.org/constructor/stickerPack.html deleted file mode 100644 index 1996882fbd..0000000000 --- a/data/core.telegram.org/constructor/stickerPack.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - stickerPack - - - - - - - - - - - - - -
- -
-
-
- -

stickerPack

- -

A stickerpack is a group of stickers associated to the same emoji.
-It is not a sticker pack the way it is usually intended, you may be looking for a StickerSet.

-

-
stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringEmoji
documentsVector<long>Stickers
-

Type

-

StickerPack

-

Related pages

-

StickerSet

-

Represents a stickerset (stickerpack)

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickerSet.html b/data/core.telegram.org/constructor/stickerSet.html deleted file mode 100644 index 5f56397125..0000000000 --- a/data/core.telegram.org/constructor/stickerSet.html +++ /dev/null @@ -1,212 +0,0 @@ - - - - - stickerSet - - - - - - - - - - - - - -
- -
-
-
- -

stickerSet

- -

Represents a stickerset (stickerpack)

-

-
stickerSet#eeb46f27 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 thumb:flags.4?PhotoSize thumb_dc_id: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
thumbflags.4?PhotoSizeThumbnail for stickerset
thumb_dc_idflags.4?intDC ID of thumbnail
countintNumber of stickers in pack
hashintHash
-

Type

-

StickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickerSetCovered.html b/data/core.telegram.org/constructor/stickerSetCovered.html deleted file mode 100644 index 4a4aec53aa..0000000000 --- a/data/core.telegram.org/constructor/stickerSetCovered.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - stickerSetCovered - - - - - - - - - - - - - -
- -
-
-
- -

stickerSetCovered

- -

Stickerset, with a specific sticker as preview

-

-
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetStickerset
coverDocumentPreview
-

Type

-

StickerSetCovered

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickerSetMultiCovered.html b/data/core.telegram.org/constructor/stickerSetMultiCovered.html deleted file mode 100644 index 52f44c9859..0000000000 --- a/data/core.telegram.org/constructor/stickerSetMultiCovered.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - stickerSetMultiCovered - - - - - - - - - - - - - -
- -
-
-
- -

stickerSetMultiCovered

- -

Stickerset, with a specific stickers as preview

-

-
stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetStickerset
coversVector<Document>Preview stickers
-

Type

-

StickerSetCovered

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileGif b/data/core.telegram.org/constructor/storage.fileGif deleted file mode 100644 index 1e7b1f19c0..0000000000 --- a/data/core.telegram.org/constructor/storage.fileGif +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileGif - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileJpeg b/data/core.telegram.org/constructor/storage.fileJpeg deleted file mode 100644 index 04291dbf0a..0000000000 --- a/data/core.telegram.org/constructor/storage.fileJpeg +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileJpeg - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileMov b/data/core.telegram.org/constructor/storage.fileMov deleted file mode 100644 index bcd077e67b..0000000000 --- a/data/core.telegram.org/constructor/storage.fileMov +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMov - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileMp3 b/data/core.telegram.org/constructor/storage.fileMp3 deleted file mode 100644 index 2dd19d2a6b..0000000000 --- a/data/core.telegram.org/constructor/storage.fileMp3 +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMp3 - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileMp4 b/data/core.telegram.org/constructor/storage.fileMp4 deleted file mode 100644 index e961a35ec9..0000000000 --- a/data/core.telegram.org/constructor/storage.fileMp4 +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMp4 - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.filePartial b/data/core.telegram.org/constructor/storage.filePartial deleted file mode 100644 index b84c92b9c8..0000000000 --- a/data/core.telegram.org/constructor/storage.filePartial +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePartial - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.filePdf b/data/core.telegram.org/constructor/storage.filePdf deleted file mode 100644 index 8eaa480571..0000000000 --- a/data/core.telegram.org/constructor/storage.filePdf +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePdf - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.filePng b/data/core.telegram.org/constructor/storage.filePng deleted file mode 100644 index 3013c52b14..0000000000 --- a/data/core.telegram.org/constructor/storage.filePng +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePng - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileUnknown b/data/core.telegram.org/constructor/storage.fileUnknown deleted file mode 100644 index d5f13c82a4..0000000000 --- a/data/core.telegram.org/constructor/storage.fileUnknown +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileUnknown - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileWebp b/data/core.telegram.org/constructor/storage.fileWebp deleted file mode 100644 index 3f82f6bf46..0000000000 --- a/data/core.telegram.org/constructor/storage.fileWebp +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileWebp - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textAnchor.html b/data/core.telegram.org/constructor/textAnchor.html deleted file mode 100644 index 16e030b560..0000000000 --- a/data/core.telegram.org/constructor/textAnchor.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - textAnchor - - - - - - - - - - - - - -
- -
-
-
- -

textAnchor

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textBold.html b/data/core.telegram.org/constructor/textBold.html deleted file mode 100644 index 35b8e69fe5..0000000000 --- a/data/core.telegram.org/constructor/textBold.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textBold - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textConcat.html b/data/core.telegram.org/constructor/textConcat.html deleted file mode 100644 index 6e747cc8bf..0000000000 --- a/data/core.telegram.org/constructor/textConcat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textConcat - - - - - - - - - - - - - -
- -
-
- - -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textEmail.html b/data/core.telegram.org/constructor/textEmail.html deleted file mode 100644 index 540f9b17db..0000000000 --- a/data/core.telegram.org/constructor/textEmail.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - textEmail - - - - - - - - - - - - - -
- -
-
-
- -

textEmail

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textEmpty.html b/data/core.telegram.org/constructor/textEmpty.html deleted file mode 100644 index 7267395f2e..0000000000 --- a/data/core.telegram.org/constructor/textEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - textEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textFixed.html b/data/core.telegram.org/constructor/textFixed.html deleted file mode 100644 index 28ccd9ee1b..0000000000 --- a/data/core.telegram.org/constructor/textFixed.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textFixed - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textImage.html b/data/core.telegram.org/constructor/textImage.html deleted file mode 100644 index f9c882a39d..0000000000 --- a/data/core.telegram.org/constructor/textImage.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - textImage - - - - - - - - - - - - - -
- -
-
-
- -

textImage

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textItalic.html b/data/core.telegram.org/constructor/textItalic.html deleted file mode 100644 index 8051d54b4f..0000000000 --- a/data/core.telegram.org/constructor/textItalic.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textItalic - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textMarked.html b/data/core.telegram.org/constructor/textMarked.html deleted file mode 100644 index 0a9ecef831..0000000000 --- a/data/core.telegram.org/constructor/textMarked.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textMarked - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textPhone.html b/data/core.telegram.org/constructor/textPhone.html deleted file mode 100644 index b96db3a232..0000000000 --- a/data/core.telegram.org/constructor/textPhone.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - textPhone - - - - - - - - - - - - - -
- -
-
-
- -

textPhone

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textPlain.html b/data/core.telegram.org/constructor/textPlain.html deleted file mode 100644 index 0a4826a82d..0000000000 --- a/data/core.telegram.org/constructor/textPlain.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textPlain - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textStrike.html b/data/core.telegram.org/constructor/textStrike.html deleted file mode 100644 index a383d359d4..0000000000 --- a/data/core.telegram.org/constructor/textStrike.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textStrike - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textSubscript.html b/data/core.telegram.org/constructor/textSubscript.html deleted file mode 100644 index 6f56aa43c9..0000000000 --- a/data/core.telegram.org/constructor/textSubscript.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textSubscript - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textSuperscript.html b/data/core.telegram.org/constructor/textSuperscript.html deleted file mode 100644 index 0cbff4e876..0000000000 --- a/data/core.telegram.org/constructor/textSuperscript.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textSuperscript - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textUnderline.html b/data/core.telegram.org/constructor/textUnderline.html deleted file mode 100644 index f7b0395686..0000000000 --- a/data/core.telegram.org/constructor/textUnderline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textUnderline - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/textUrl.html b/data/core.telegram.org/constructor/textUrl.html deleted file mode 100644 index 2abe1b0c17..0000000000 --- a/data/core.telegram.org/constructor/textUrl.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - textUrl - - - - - - - - - - - - - -
- -
-
-
- -

textUrl

- -

Link

-

-
textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText of link
urlstringWebpage HTTP URL
webpage_idlongIf a preview was already generated for the page, the page ID
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/theme.html b/data/core.telegram.org/constructor/theme.html deleted file mode 100644 index 141e9fee81..0000000000 --- a/data/core.telegram.org/constructor/theme.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - theme - - - - - - - - - - - - - -
- -
-
-
- -

theme

- -

Theme

-

-
theme#28f1114 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;

-

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
idlongTheme ID
access_hashlongTheme access hash
slugstringUnique theme ID
titlestringTheme name
documentflags.2?DocumentTheme
settingsflags.3?ThemeSettingsTheme settings
installs_countintInstallation count
-

Type

-

Theme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/themeSettings.html b/data/core.telegram.org/constructor/themeSettings.html deleted file mode 100644 index f2c84291ca..0000000000 --- a/data/core.telegram.org/constructor/themeSettings.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - themeSettings - - - - - - - - - - - - - -
- -
-
-
- -

themeSettings

- -

Theme settings

-

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

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
base_themeBaseThemeBase theme
accent_colorintAccent color, RGB24 format
message_top_colorflags.0?intMessage gradient color (top), RGB24 format
message_bottom_colorflags.0?intMessage gradient color (bottom), RGB24 format
wallpaperflags.1?WallPaperWallpaper
-

Type

-

ThemeSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeer.html b/data/core.telegram.org/constructor/topPeer.html deleted file mode 100644 index 721fd6fb32..0000000000 --- a/data/core.telegram.org/constructor/topPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - topPeer - - - - - - - - - - - - - -
- -
-
-
- -

topPeer

- -

Top peer

-

-
topPeer#edcdc05b peer:Peer rating:double = TopPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
ratingdoubleRating as computed in top peer rating »
-

Type

-

TopPeer

-

Related pages

-

Top peer rating

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html b/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html deleted file mode 100644 index 0893720813..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryBotsInline - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html b/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html deleted file mode 100644 index 86cfabcdce..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryBotsPM - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryChannels.html b/data/core.telegram.org/constructor/topPeerCategoryChannels.html deleted file mode 100644 index 5325a9a510..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryChannels.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryChannels - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html b/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html deleted file mode 100644 index 3bfaf3c834..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryCorrespondents - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryCorrespondents

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html b/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html deleted file mode 100644 index d8bfa3f13a..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryForwardChats - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryForwardChats

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html b/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html deleted file mode 100644 index 75581c3657..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryForwardUsers - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryForwardUsers

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryGroups.html b/data/core.telegram.org/constructor/topPeerCategoryGroups.html deleted file mode 100644 index d646f86aeb..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryGroups.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryGroups - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryPeers.html b/data/core.telegram.org/constructor/topPeerCategoryPeers.html deleted file mode 100644 index f745725ed4..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryPeers.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - topPeerCategoryPeers - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryPeers

- -

Top peer category

-

-
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
categoryTopPeerCategoryTop peer category of peers
countintCount of peers
peersVector<TopPeer>Peers
-

Type

-

TopPeerCategoryPeers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html b/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html deleted file mode 100644 index 02940b1063..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryPhoneCalls - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/true.html b/data/core.telegram.org/constructor/true.html deleted file mode 100644 index bdf4783d00..0000000000 --- a/data/core.telegram.org/constructor/true.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - true - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotCallbackQuery.html b/data/core.telegram.org/constructor/updateBotCallbackQuery.html deleted file mode 100644 index 6e130b6659..0000000000 --- a/data/core.telegram.org/constructor/updateBotCallbackQuery.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - updateBotCallbackQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotCallbackQuery

- -

A callback button was pressed, and the button data was sent to the bot that created the button

-

-
updateBotCallbackQuery#e73547e1 flags:# query_id:long user_id:int 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_idintID 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/updateBotInlineQuery.html b/data/core.telegram.org/constructor/updateBotInlineQuery.html deleted file mode 100644 index eb964d7b5f..0000000000 --- a/data/core.telegram.org/constructor/updateBotInlineQuery.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updateBotInlineQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotInlineQuery

- -

An incoming inline query

-

-
updateBotInlineQuery#54826690 flags:# query_id:long user_id:int query:string geo:flags.0?GeoPoint offset:string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idintUser that sent the query
querystringText of query
geoflags.0?GeoPointAttached geolocation
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 deleted file mode 100644 index 1b4e031266..0000000000 --- a/data/core.telegram.org/constructor/updateBotInlineSend.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updateBotInlineSend - - - - - - - - - - - - - -
- -
-
-
- -

updateBotInlineSend

- -

The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.

-

-
updateBotInlineSend#e48f964 flags:# user_id:int query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
user_idintThe 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 deleted file mode 100644 index 65e7cc8f88..0000000000 --- a/data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html +++ /dev/null @@ -1,184 +0,0 @@ - - - - - updateBotPrecheckoutQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotPrecheckoutQuery

- -

This object contains information about an incoming pre-checkout query.

-

-
updateBotPrecheckoutQuery#5d2f3aa9 flags:# query_id:long user_id:int 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_idintUser 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 deleted file mode 100644 index ca0f567cca..0000000000 --- a/data/core.telegram.org/constructor/updateBotShippingQuery.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateBotShippingQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotShippingQuery

- -

This object contains information about an incoming shipping query.

-

-
updateBotShippingQuery#e0cdc940 query_id:long user_id:int payload:bytes shipping_address:PostAddress = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
query_idlongUnique query identifier
user_idintUser who sent the query
payloadbytesBot specified invoice payload
shipping_addressPostAddressUser specified shipping address
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotWebhookJSON.html b/data/core.telegram.org/constructor/updateBotWebhookJSON.html deleted file mode 100644 index 1cd2ae6f25..0000000000 --- a/data/core.telegram.org/constructor/updateBotWebhookJSON.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateBotWebhookJSON - - - - - - - - - - - - - -
- -
-
-
- -

updateBotWebhookJSON

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html b/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html deleted file mode 100644 index a8cfc8eb4c..0000000000 --- a/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateBotWebhookJSONQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotWebhookJSONQuery

- -

A new incoming query; for bots only

-

-
updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
query_idlongQuery identifier
dataDataJSONQuery data
timeoutintQuery timeout
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannel.html b/data/core.telegram.org/constructor/updateChannel.html deleted file mode 100644 index a479ea7ebc..0000000000 --- a/data/core.telegram.org/constructor/updateChannel.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateChannel - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelAvailableMessages.html b/data/core.telegram.org/constructor/updateChannelAvailableMessages.html deleted file mode 100644 index 7980ade874..0000000000 --- a/data/core.telegram.org/constructor/updateChannelAvailableMessages.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateChannelAvailableMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelAvailableMessages

- -

The history of a channel/supergroup was hidden.

-

-
updateChannelAvailableMessages#70db6837 channel_id:int available_min_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel/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/updateChannelMessageForwards.html b/data/core.telegram.org/constructor/updateChannelMessageForwards.html deleted file mode 100644 index 55f38e333a..0000000000 --- a/data/core.telegram.org/constructor/updateChannelMessageForwards.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateChannelMessageForwards - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelMessageForwards

- -

The forward counter of a message in a channel has changed

-

-
updateChannelMessageForwards#6e8a84df channel_id:int id:int forwards:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel ID
idintID of the message
forwardsintNew forward counter
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelMessageViews.html b/data/core.telegram.org/constructor/updateChannelMessageViews.html deleted file mode 100644 index 84ad52ffc9..0000000000 --- a/data/core.telegram.org/constructor/updateChannelMessageViews.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateChannelMessageViews - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelMessageViews

- -

The view counter of a message in a channel has changed

-

-
updateChannelMessageViews#98a12b4b channel_id:int id:int views:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel ID
idintID of the message
viewsintNew view counter
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelParticipant.html b/data/core.telegram.org/constructor/updateChannelParticipant.html deleted file mode 100644 index 7b0a3bd8b2..0000000000 --- a/data/core.telegram.org/constructor/updateChannelParticipant.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - updateChannelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelParticipant

- -

A participant has left, joined, was banned or admined in a channel or supergroup.

-

-
Constructor schema is available as of layer 124. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idintChannel ID
dateintDate of the event
user_idintUser in question
prev_participantflags.0?ChannelParticipantPrevious participant status
new_participantflags.1?ChannelParticipantNew participant status
qtsintPTS
-

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/updateChannelReadMessagesContents.html b/data/core.telegram.org/constructor/updateChannelReadMessagesContents.html deleted file mode 100644 index 64ac1d7c5a..0000000000 --- a/data/core.telegram.org/constructor/updateChannelReadMessagesContents.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateChannelReadMessagesContents - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelReadMessagesContents

- -

The specified channel/supergroup messages were read

-

-
updateChannelReadMessagesContents#89893b45 channel_id:int messages:Vector<int> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel/supergroup ID
messagesVector<int>IDs of messages that were read
-

Type

-

Update

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelTooLong.html b/data/core.telegram.org/constructor/updateChannelTooLong.html deleted file mode 100644 index 398633de3f..0000000000 --- a/data/core.telegram.org/constructor/updateChannelTooLong.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - updateChannelTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelTooLong

- -

There are new updates in the specified channel, the client must fetch them.
-If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.

-

-
updateChannelTooLong#eb0467fb flags:# channel_id:int pts:flags.0?int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idintThe channel
ptsflags.0?intThe PTS.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelUserTyping.html b/data/core.telegram.org/constructor/updateChannelUserTyping.html deleted file mode 100644 index 82f1b1a9b0..0000000000 --- a/data/core.telegram.org/constructor/updateChannelUserTyping.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updateChannelUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelUserTyping

- -

A user is typing in a supergroup, channel or message thread

-

-
updateChannelUserTyping#ff2abe9f flags:# channel_id:int top_msg_id:flags.0?int user_id:int action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idintChannel ID
top_msg_idflags.0?intThread ID
user_idintUser ID
actionSendMessageActionWhether the user is typing, sending a media or doing something else
-

Type

-

Update

-

Related pages

-

Threads

-

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

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelWebPage.html b/data/core.telegram.org/constructor/updateChannelWebPage.html deleted file mode 100644 index 4e8b1a9755..0000000000 --- a/data/core.telegram.org/constructor/updateChannelWebPage.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateChannelWebPage - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelWebPage

- -

A webpage preview of a link in a channel/supergroup message was generated

-

-
updateChannelWebPage#40771900 channel_id:int webpage:WebPage pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel/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/updateChatDefaultBannedRights.html b/data/core.telegram.org/constructor/updateChatDefaultBannedRights.html deleted file mode 100644 index b05a114b22..0000000000 --- a/data/core.telegram.org/constructor/updateChatDefaultBannedRights.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateChatDefaultBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

updateChatDefaultBannedRights

- -

Default banned rights in a normal chat were updated

-

-
updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe chat
default_banned_rightsChatBannedRightsNew default banned rights
versionintVersion
-

Type

-

Update

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatParticipantAdd.html b/data/core.telegram.org/constructor/updateChatParticipantAdd.html deleted file mode 100644 index 3e8dc3e60c..0000000000 --- a/data/core.telegram.org/constructor/updateChatParticipantAdd.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateChatParticipantAdd - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipantAdd

- -

New group member.

-

-
updateChatParticipantAdd#ea4b0e5c chat_id:int user_id:int inviter_id:int date:int version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintGroup ID
user_idintID of the new member
inviter_idintID of the user, who added member to the group
dateintWhen was the participant added
versionintChat version number
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatParticipantAdmin.html b/data/core.telegram.org/constructor/updateChatParticipantAdmin.html deleted file mode 100644 index 375df3277b..0000000000 --- a/data/core.telegram.org/constructor/updateChatParticipantAdmin.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateChatParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipantAdmin

- -

Admin permissions of a user in a legacy group were changed

-

-
updateChatParticipantAdmin#b6901959 chat_id:int user_id:int is_admin:Bool version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
user_idintID of the (de)admined user
is_adminBoolWhether the user was rendered admin
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
-

Type

-

Update

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatParticipantDelete.html b/data/core.telegram.org/constructor/updateChatParticipantDelete.html deleted file mode 100644 index fabe33a983..0000000000 --- a/data/core.telegram.org/constructor/updateChatParticipantDelete.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateChatParticipantDelete - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipantDelete

- -

A member has left the group.

-

-
updateChatParticipantDelete#6e5f8c22 chat_id:int user_id:int version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintGroup ID
user_idintID of the user
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatParticipants.html b/data/core.telegram.org/constructor/updateChatParticipants.html deleted file mode 100644 index 77d6eedd99..0000000000 --- a/data/core.telegram.org/constructor/updateChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipants

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatUserTyping.html b/data/core.telegram.org/constructor/updateChatUserTyping.html deleted file mode 100644 index 9a87b9f494..0000000000 --- a/data/core.telegram.org/constructor/updateChatUserTyping.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateChatUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateChatUserTyping

- -

The user is preparing a message in a group; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

-

-
updateChatUserTyping#9a65ea1f chat_id:int user_id:int action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintGroup id
user_idintUser id
actionSendMessageActionType of action
Parameter added in Layer 17.
-

Type

-

Update

-

Related pages

-

Layers

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateConfig.html b/data/core.telegram.org/constructor/updateConfig.html deleted file mode 100644 index bdf12c40d5..0000000000 --- a/data/core.telegram.org/constructor/updateConfig.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateConfig - - - - - - - - - - - - - -
- -
-
-
- -

updateConfig

- -

The server-side configuration has changed; the client should re-fetch the config using help.getConfig

-

-
updateConfig#a229dd06 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

help.getConfig

-

Returns current configuration, including data center configuration.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateContactsReset.html b/data/core.telegram.org/constructor/updateContactsReset.html deleted file mode 100644 index f6e145b9c7..0000000000 --- a/data/core.telegram.org/constructor/updateContactsReset.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateContactsReset - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDcOptions.html b/data/core.telegram.org/constructor/updateDcOptions.html deleted file mode 100644 index d294406053..0000000000 --- a/data/core.telegram.org/constructor/updateDcOptions.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateDcOptions - - - - - - - - - - - - - -
- -
-
-
- -

updateDcOptions

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDeleteChannelMessages.html b/data/core.telegram.org/constructor/updateDeleteChannelMessages.html deleted file mode 100644 index 9959ef2b5d..0000000000 --- a/data/core.telegram.org/constructor/updateDeleteChannelMessages.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateDeleteChannelMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateDeleteChannelMessages

- -

Some messages in a supergroup/channel were deleted

-

-
updateDeleteChannelMessages#c37521c9 channel_id:int messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel ID
messagesVector<int>IDs of messages that were deleted
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDeleteMessages.html b/data/core.telegram.org/constructor/updateDeleteMessages.html deleted file mode 100644 index 36246f8e99..0000000000 --- a/data/core.telegram.org/constructor/updateDeleteMessages.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateDeleteMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateDeleteMessages

- -

Messages were deleted.

-

-
updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<int>List of identifiers of deleted messages
ptsintNew quality of actions in a message box
pts_countintNumber of generated events
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html b/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html deleted file mode 100644 index f91e7157b3..0000000000 --- a/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateDeleteScheduledMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateDeleteScheduledMessages

- -

Some scheduled messages were deleted from the schedule queue of a chat

-

-
updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
messagesVector<int>Deleted scheduled messages
-

Type

-

Update

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogFilter.html b/data/core.telegram.org/constructor/updateDialogFilter.html deleted file mode 100644 index 3c2e9bcfb6..0000000000 --- a/data/core.telegram.org/constructor/updateDialogFilter.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateDialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogFilter

- -

A new folder was added

-

-
updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogFilterOrder.html b/data/core.telegram.org/constructor/updateDialogFilterOrder.html deleted file mode 100644 index 32521a95af..0000000000 --- a/data/core.telegram.org/constructor/updateDialogFilterOrder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateDialogFilterOrder - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogFilterOrder

- -

New folder order

-

-
updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
orderVector<int>Ordered folder IDs
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogFilters.html b/data/core.telegram.org/constructor/updateDialogFilters.html deleted file mode 100644 index 03615594ba..0000000000 --- a/data/core.telegram.org/constructor/updateDialogFilters.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateDialogFilters - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogFilters

- -

Clients should update folder info

-

-
updateDialogFilters#3504914f = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogPinned.html b/data/core.telegram.org/constructor/updateDialogPinned.html deleted file mode 100644 index 54788087a1..0000000000 --- a/data/core.telegram.org/constructor/updateDialogPinned.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateDialogPinned - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogPinned

- -

A dialog was pinned/unpinned

-

-
updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the dialog was pinned
folder_idflags.1?intPeer folder ID, for more info click here
peerDialogPeerThe dialog
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogUnreadMark.html b/data/core.telegram.org/constructor/updateDialogUnreadMark.html deleted file mode 100644 index 1cc9ff3629..0000000000 --- a/data/core.telegram.org/constructor/updateDialogUnreadMark.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateDialogUnreadMark - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogUnreadMark

- -

The manual unread mark of a chat was changed

-

-
updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueWas the chat marked or unmarked as read
peerDialogPeerThe dialog
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDraftMessage.html b/data/core.telegram.org/constructor/updateDraftMessage.html deleted file mode 100644 index 417a66e1be..0000000000 --- a/data/core.telegram.org/constructor/updateDraftMessage.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateDraftMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateDraftMessage

- -

Notifies a change of a message draft.

-

-
updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer to which the draft is associated
draftDraftMessageThe draft
-

Type

-

Update

-

Related pages

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEditChannelMessage.html b/data/core.telegram.org/constructor/updateEditChannelMessage.html deleted file mode 100644 index c682b0d65d..0000000000 --- a/data/core.telegram.org/constructor/updateEditChannelMessage.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateEditChannelMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateEditChannelMessage

- -

A message was edited in a channel/supergroup

-

-
updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe new message
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEditMessage.html b/data/core.telegram.org/constructor/updateEditMessage.html deleted file mode 100644 index 39e4021718..0000000000 --- a/data/core.telegram.org/constructor/updateEditMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateEditMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateEditMessage

- -

A message was edited

-

-
updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe new edited message
ptsintPTS
pts_countintPTS count
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEncryptedChatTyping.html b/data/core.telegram.org/constructor/updateEncryptedChatTyping.html deleted file mode 100644 index ad3c6546c7..0000000000 --- a/data/core.telegram.org/constructor/updateEncryptedChatTyping.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateEncryptedChatTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryptedChatTyping

- -

Interlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.

-

-
updateEncryptedChatTyping#1710f156 chat_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html b/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html deleted file mode 100644 index 4668a5faa9..0000000000 --- a/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateEncryptedMessagesRead - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryptedMessagesRead

- -

Communication history in an encrypted chat was marked as read.

-

-
updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
max_dateintMaximum value of data for read messages
dateintTime when messages were read
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEncryption.html b/data/core.telegram.org/constructor/updateEncryption.html deleted file mode 100644 index 7578f9e34e..0000000000 --- a/data/core.telegram.org/constructor/updateEncryption.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateEncryption - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryption

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateFavedStickers.html b/data/core.telegram.org/constructor/updateFavedStickers.html deleted file mode 100644 index cd6ddc4e83..0000000000 --- a/data/core.telegram.org/constructor/updateFavedStickers.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateFavedStickers - - - - - - - - - - - - - -
- -
-
-
- -

updateFavedStickers

- -

The list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list

-

-
updateFavedStickers#e511996d = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

messages.getFavedStickers

-

Get faved stickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateFolderPeers.html b/data/core.telegram.org/constructor/updateFolderPeers.html deleted file mode 100644 index fdfc71a6ac..0000000000 --- a/data/core.telegram.org/constructor/updateFolderPeers.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateFolderPeers - - - - - - - - - - - - - -
- -
-
-
- -

updateFolderPeers

- -

The peer list of a peer folder was updated

-

-
updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
folder_peersVector<FolderPeer>New peer list
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateGeoLiveViewed.html b/data/core.telegram.org/constructor/updateGeoLiveViewed.html deleted file mode 100644 index 88bd32b821..0000000000 --- a/data/core.telegram.org/constructor/updateGeoLiveViewed.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateGeoLiveViewed - - - - - - - - - - - - - -
- -
-
-
- -

updateGeoLiveViewed

- -

Live geoposition message was viewed

-

-
updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe user that viewed the live geoposition
msg_idintMessage ID of geoposition message
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html b/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html deleted file mode 100644 index 7417324d1e..0000000000 --- a/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updateInlineBotCallbackQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateInlineBotCallbackQuery

- -

This notification is received by bots when a button is pressed

-

-
updateInlineBotCallbackQuery#f9d27a5a flags:# query_id:long user_id:int 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_idintID 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 deleted file mode 100644 index ca276e2597..0000000000 --- a/data/core.telegram.org/constructor/updateLangPack.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateLangPack - - - - - - - - - - - - - -
- -
-
-
- -

updateLangPack

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateLangPackTooLong.html b/data/core.telegram.org/constructor/updateLangPackTooLong.html deleted file mode 100644 index eb405caf47..0000000000 --- a/data/core.telegram.org/constructor/updateLangPackTooLong.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateLangPackTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updateLangPackTooLong

- -

A language pack has changed, the client should manually fetch the changed strings using langpack.getDifference

-

-
updateLangPackTooLong#46560264 lang_code:string = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
-

Type

-

Update

-

Related pages

-

langpack.getDifference

-

Get new strings in languagepack

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateLoginToken.html b/data/core.telegram.org/constructor/updateLoginToken.html deleted file mode 100644 index 2cc8d90250..0000000000 --- a/data/core.telegram.org/constructor/updateLoginToken.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateLoginToken - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateMessageID.html b/data/core.telegram.org/constructor/updateMessageID.html deleted file mode 100644 index 1d8905c90c..0000000000 --- a/data/core.telegram.org/constructor/updateMessageID.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateMessageID - - - - - - - - - - - - - -
- -
-
-
- -

updateMessageID

- -

Sent message with random_id client identifier was assigned an identifier.

-

-
updateMessageID#4e90bfd6 id:int random_id:long = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintid identifier of a respective Message
random_idlongPreviuosly transferred client random_id identifier
-

Type

-

Update

-

Related pages

-

Message

-

Object describing a message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateMessagePoll.html b/data/core.telegram.org/constructor/updateMessagePoll.html deleted file mode 100644 index f331bb269a..0000000000 --- a/data/core.telegram.org/constructor/updateMessagePoll.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateMessagePoll - - - - - - - - - - - - - -
- -
-
-
- -

updateMessagePoll

- -

The results of a poll have changed

-

-
updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
poll_idlongPoll ID
pollflags.0?PollIf the server knows the client hasn't cached this poll yet, the poll itself
resultsPollResultsNew poll results
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateMessagePollVote.html b/data/core.telegram.org/constructor/updateMessagePollVote.html deleted file mode 100644 index 90ba44ee1d..0000000000 --- a/data/core.telegram.org/constructor/updateMessagePollVote.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateMessagePollVote - - - - - - - - - - - - - -
- -
-
-
- -

updateMessagePollVote

- -

A specific user has voted in a poll

-

-
updateMessagePollVote#42f88f2c poll_id:long user_id:int options:Vector<bytes> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
poll_idlongPoll ID
user_idintUser ID
optionsVector<bytes>Chosen option(s)
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewChannelMessage.html b/data/core.telegram.org/constructor/updateNewChannelMessage.html deleted file mode 100644 index f5b83f8a4a..0000000000 --- a/data/core.telegram.org/constructor/updateNewChannelMessage.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateNewChannelMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewChannelMessage

- -

A new message was sent in a channel/supergroup

-

-
updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageNew message
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewEncryptedMessage.html b/data/core.telegram.org/constructor/updateNewEncryptedMessage.html deleted file mode 100644 index 24e8f49755..0000000000 --- a/data/core.telegram.org/constructor/updateNewEncryptedMessage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateNewEncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewEncryptedMessage

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewMessage.html b/data/core.telegram.org/constructor/updateNewMessage.html deleted file mode 100644 index bd469c4450..0000000000 --- a/data/core.telegram.org/constructor/updateNewMessage.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateNewMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewMessage

- -

New message in a private chat or in a legacy group.

-

-
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageMessage
ptsintNew quantity of actions in a message box
pts_countintNumber of generated events
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewScheduledMessage.html b/data/core.telegram.org/constructor/updateNewScheduledMessage.html deleted file mode 100644 index b84b55f6ad..0000000000 --- a/data/core.telegram.org/constructor/updateNewScheduledMessage.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateNewScheduledMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewScheduledMessage

- -

A message was added to the schedule queue of a chat

-

-
updateNewScheduledMessage#39a51dfb message:Message = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageMessage
-

Type

-

Update

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewStickerSet.html b/data/core.telegram.org/constructor/updateNewStickerSet.html deleted file mode 100644 index 93db78b719..0000000000 --- a/data/core.telegram.org/constructor/updateNewStickerSet.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateNewStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

updateNewStickerSet

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNotifySettings.html b/data/core.telegram.org/constructor/updateNotifySettings.html deleted file mode 100644 index de60ff1319..0000000000 --- a/data/core.telegram.org/constructor/updateNotifySettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

updateNotifySettings

- -

Changes in notification settings.

-

-
updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerNotifyPeerNofication source
notify_settingsPeerNotifySettingsNew notification settings
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePeerBlocked.html b/data/core.telegram.org/constructor/updatePeerBlocked.html deleted file mode 100644 index 51f9aa65cb..0000000000 --- a/data/core.telegram.org/constructor/updatePeerBlocked.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePeerBlocked - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerBlocked

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePeerLocated.html b/data/core.telegram.org/constructor/updatePeerLocated.html deleted file mode 100644 index 854cf6bbcf..0000000000 --- a/data/core.telegram.org/constructor/updatePeerLocated.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updatePeerLocated - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerLocated

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePeerSettings.html b/data/core.telegram.org/constructor/updatePeerSettings.html deleted file mode 100644 index 8c058b2fa9..0000000000 --- a/data/core.telegram.org/constructor/updatePeerSettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePeerSettings - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerSettings

- -

Settings of a certain peer have changed

-

-
updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer
settingsPeerSettingsAssociated peer settings
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePhoneCall.html b/data/core.telegram.org/constructor/updatePhoneCall.html deleted file mode 100644 index 31d3306a52..0000000000 --- a/data/core.telegram.org/constructor/updatePhoneCall.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updatePhoneCall - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html b/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html deleted file mode 100644 index 2116bd99ba..0000000000 --- a/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePhoneCallSignalingData - - - - - - - - - - - - - -
- -
-
-
- -

updatePhoneCallSignalingData

- -

Incoming phone call signaling payload

-

-
updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_call_idlongPhone call ID
databytesSignaling payload
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePinnedChannelMessages.html b/data/core.telegram.org/constructor/updatePinnedChannelMessages.html deleted file mode 100644 index 3f3e5d5e86..0000000000 --- a/data/core.telegram.org/constructor/updatePinnedChannelMessages.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updatePinnedChannelMessages - - - - - - - - - - - - - -
- -
-
-
- -

updatePinnedChannelMessages

- -

Messages were pinned/unpinned in a channel/supergroup

-

-
updatePinnedChannelMessages#8588878b flags:# pinned:flags.0?true channel_id:int 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_idintChannel ID
messagesVector<int>Messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePinnedDialogs.html b/data/core.telegram.org/constructor/updatePinnedDialogs.html deleted file mode 100644 index 2ac7b6d762..0000000000 --- a/data/core.telegram.org/constructor/updatePinnedDialogs.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updatePinnedDialogs - - - - - - - - - - - - - -
- -
-
-
- -

updatePinnedDialogs

- -

Pinned dialogs were updated

-

-
updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.1?intPeer folder ID, for more info click here
orderflags.0?Vector<DialogPeer>New order of pinned dialogs
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePinnedMessages.html b/data/core.telegram.org/constructor/updatePinnedMessages.html deleted file mode 100644 index 224bcc0dc2..0000000000 --- a/data/core.telegram.org/constructor/updatePinnedMessages.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - updatePinnedMessages - - - - - - - - - - - - - -
- -
-
-
- -

updatePinnedMessages

- -

Some messages were pinned in a chat

-

-
updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
peerPeerPeer
messagesVector<int>Message IDs
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePrivacy.html b/data/core.telegram.org/constructor/updatePrivacy.html deleted file mode 100644 index fcc9a832c8..0000000000 --- a/data/core.telegram.org/constructor/updatePrivacy.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePrivacy - - - - - - - - - - - - - -
- -
-
-
- -

updatePrivacy

- -

Privacy rules were changed

-

-
updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keyPrivacyKeyPeers to which the privacy rules apply
rulesVector<PrivacyRule>New privacy rules
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePtsChanged.html b/data/core.telegram.org/constructor/updatePtsChanged.html deleted file mode 100644 index fca86f17dd..0000000000 --- a/data/core.telegram.org/constructor/updatePtsChanged.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updatePtsChanged - - - - - - - - - - - - - -
- -
-
-
- -

updatePtsChanged

- -

Common message box sequence PTS has changed, state has to be refetched using updates.getState

-

-
updatePtsChanged#3354678f = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadChannelDiscussionInbox.html b/data/core.telegram.org/constructor/updateReadChannelDiscussionInbox.html deleted file mode 100644 index 89bed32f07..0000000000 --- a/data/core.telegram.org/constructor/updateReadChannelDiscussionInbox.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updateReadChannelDiscussionInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelDiscussionInbox

- -

Incoming comments in a discussion thread were marked as read

-

-
updateReadChannelDiscussionInbox#1cc7de54 flags:# channel_id:int top_msg_id:int read_max_id:int broadcast_id:flags.0?int broadcast_post:flags.0?int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idintDiscussion 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?intIf set, contains the ID of the channel that contains the post that started the comment thread in the discussion group (channel_id)
broadcast_postflags.0?intIf set, contains the ID of the channel post that started the the comment thread
-

Type

-

Update

-

Related pages

-

Channels

-

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

-

Threads

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html b/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html deleted file mode 100644 index 428ba34767..0000000000 --- a/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateReadChannelDiscussionOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelDiscussionOutbox

- -

Outgoing comments in a discussion thread were marked as read

-

-
updateReadChannelDiscussionOutbox#4638a26c channel_id:int top_msg_id:int read_max_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintSupergroup ID
top_msg_idintID of the group message that started the thread
read_max_idintMessage ID of latest read outgoing message for this thread
-

Type

-

Update

-

Related pages

-

Channels

-

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

-

Threads

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadChannelInbox.html b/data/core.telegram.org/constructor/updateReadChannelInbox.html deleted file mode 100644 index 7055ffb333..0000000000 --- a/data/core.telegram.org/constructor/updateReadChannelInbox.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - updateReadChannelInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelInbox

- -

Incoming messages in a channel/supergroup were read

-

-
updateReadChannelInbox#330b5424 flags:# folder_id:flags.0?int channel_id:int 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_idintChannel/supergroup ID
max_idintPosition up to which all incoming messages are read.
still_unread_countintCount of messages weren't read yet
ptsintEvent count after generation
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadChannelOutbox.html b/data/core.telegram.org/constructor/updateReadChannelOutbox.html deleted file mode 100644 index c56483f6c2..0000000000 --- a/data/core.telegram.org/constructor/updateReadChannelOutbox.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateReadChannelOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelOutbox

- -

Outgoing messages in a channel/supergroup were read

-

-
updateReadChannelOutbox#25d6c9c7 channel_id:int max_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idintChannel/supergroup ID
max_idintPosition up to which all outgoing messages are read.
-

Type

-

Update

-

Related pages

-

Channels

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadFeaturedStickers.html b/data/core.telegram.org/constructor/updateReadFeaturedStickers.html deleted file mode 100644 index 8ea8b73c49..0000000000 --- a/data/core.telegram.org/constructor/updateReadFeaturedStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateReadFeaturedStickers - - - - - - - - - - - - - -
- -
- -
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadHistoryInbox.html b/data/core.telegram.org/constructor/updateReadHistoryInbox.html deleted file mode 100644 index 662e49d6d0..0000000000 --- a/data/core.telegram.org/constructor/updateReadHistoryInbox.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - updateReadHistoryInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadHistoryInbox

- -

Incoming messages were read

-

-
updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
peerPeerPeer
max_idintMaximum ID of messages read
still_unread_countintNumber of messages that are still unread
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadHistoryOutbox.html b/data/core.telegram.org/constructor/updateReadHistoryOutbox.html deleted file mode 100644 index be1b2578b0..0000000000 --- a/data/core.telegram.org/constructor/updateReadHistoryOutbox.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateReadHistoryOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadHistoryOutbox

- -

Outgoing messages were read

-

-
updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
max_idintMaximum ID of read outgoing messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadMessagesContents.html b/data/core.telegram.org/constructor/updateReadMessagesContents.html deleted file mode 100644 index 4a9e8929ad..0000000000 --- a/data/core.telegram.org/constructor/updateReadMessagesContents.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateReadMessagesContents - - - - - - - - - - - - - -
- -
-
-
- -

updateReadMessagesContents

- -

Contents of messages in the common message box were read

-

-
updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<int>IDs of read messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateRecentStickers.html b/data/core.telegram.org/constructor/updateRecentStickers.html deleted file mode 100644 index a1e448e3db..0000000000 --- a/data/core.telegram.org/constructor/updateRecentStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateRecentStickers - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateSavedGifs.html b/data/core.telegram.org/constructor/updateSavedGifs.html deleted file mode 100644 index 3983a3680c..0000000000 --- a/data/core.telegram.org/constructor/updateSavedGifs.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateSavedGifs - - - - - - - - - - - - - -
- -
-
-
- -

updateSavedGifs

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateServiceNotification.html b/data/core.telegram.org/constructor/updateServiceNotification.html deleted file mode 100644 index d36a5d76b6..0000000000 --- a/data/core.telegram.org/constructor/updateServiceNotification.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - updateServiceNotification - - - - - - - - - - - - - -
- -
-
-
- -

updateServiceNotification

- -

A service message for the user.

-

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

-

-
updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?true(boolTrue) if the message must be displayed in a popup.
inbox_dateflags.1?intWhen was the notification received
The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
typestringString, identical in format and contents to the type field in API errors. Describes type of service message. It is acceptable to ignore repeated messages of the same type within a short period of time (15 minutes).
messagestringMessage text
mediaMessageMediaMedia content (optional)
entitiesVector<MessageEntity>Message entities for styled text
-

Type

-

Update

-

Related pages

-

Error handling

-

How to handle API return errors correctly.

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateShort.html b/data/core.telegram.org/constructor/updateShort.html deleted file mode 100644 index 1aca702b6e..0000000000 --- a/data/core.telegram.org/constructor/updateShort.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateShort - - - - - - - - - - - - - -
- -
-
-
- -

updateShort

- -

Shortened constructor containing info on one update not requiring auxiliary data

-

-
updateShort#78d4dec1 update:Update date:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updateUpdateUpdate
dateintDate of event
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateShortChatMessage.html b/data/core.telegram.org/constructor/updateShortChatMessage.html deleted file mode 100644 index 84eab81b33..0000000000 --- a/data/core.telegram.org/constructor/updateShortChatMessage.html +++ /dev/null @@ -1,227 +0,0 @@ - - - - - updateShortChatMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateShortChatMessage

- -

Shortened constructor containing info on one new incoming text message from a chat

-

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

-

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_idintID of the sender of the message
chat_idintID 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?intInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply (thread) information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
-

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/updateShortMessage.html b/data/core.telegram.org/constructor/updateShortMessage.html deleted file mode 100644 index 164fe4d615..0000000000 --- a/data/core.telegram.org/constructor/updateShortMessage.html +++ /dev/null @@ -1,224 +0,0 @@ - - - - - updateShortMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateShortMessage

- -

Info about a message sent to (received from) another user

-

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

-

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_idintThe 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?intInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply and thread information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
-

Type

-

Updates

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Threads

-

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

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateShortSentMessage.html b/data/core.telegram.org/constructor/updateShortSentMessage.html deleted file mode 100644 index 47341bb123..0000000000 --- a/data/core.telegram.org/constructor/updateShortSentMessage.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - updateShortSentMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateShortSentMessage

- -

Shortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).

-

-
updateShortSentMessage#11f1331c flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> = 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
-

Type

-

Updates

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateStickerSets.html b/data/core.telegram.org/constructor/updateStickerSets.html deleted file mode 100644 index 9127b1715c..0000000000 --- a/data/core.telegram.org/constructor/updateStickerSets.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

updateStickerSets

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateStickerSetsOrder.html b/data/core.telegram.org/constructor/updateStickerSetsOrder.html deleted file mode 100644 index 4ddc059f0f..0000000000 --- a/data/core.telegram.org/constructor/updateStickerSetsOrder.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateStickerSetsOrder - - - - - - - - - - - - - -
- -
-
-
- -

updateStickerSetsOrder

- -

The order of stickersets was changed

-

-
updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether the updated stickers are mask stickers
orderVector<long>New sticker order by sticker ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateTheme.html b/data/core.telegram.org/constructor/updateTheme.html deleted file mode 100644 index f677cc66aa..0000000000 --- a/data/core.telegram.org/constructor/updateTheme.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateTheme - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserBlocked.html b/data/core.telegram.org/constructor/updateUserBlocked.html deleted file mode 100644 index 613249be7d..0000000000 --- a/data/core.telegram.org/constructor/updateUserBlocked.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - updateUserBlocked - - - - - - - - - - - - - -
- -
-
-
- -

updateUserBlocked

- -

User was added to the blacklist (method contacts.block) or removed from the blacklist (method contacts.unblock).

-

-
Constructor schema is available as of layer 119. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser id
blockedBool(boolTrue) if the the user is blocked
-

Type

-

Update

-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

-

contacts.block

-

Adds the user to the blacklist.

-

contacts.unblock

-

Deletes the user from the blacklist.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserName.html b/data/core.telegram.org/constructor/updateUserName.html deleted file mode 100644 index 9de000404d..0000000000 --- a/data/core.telegram.org/constructor/updateUserName.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateUserName - - - - - - - - - - - - - -
- -
-
-
- -

updateUserName

- -

Changes the user's first name, last name and username.

-

-
updateUserName#a7332b73 user_id:int first_name:string last_name:string username:string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser 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 scheme changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserPhone.html b/data/core.telegram.org/constructor/updateUserPhone.html deleted file mode 100644 index 47d5929e8d..0000000000 --- a/data/core.telegram.org/constructor/updateUserPhone.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateUserPhone - - - - - - - - - - - - - -
- -
-
-
- -

updateUserPhone

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserPhoto.html b/data/core.telegram.org/constructor/updateUserPhoto.html deleted file mode 100644 index 1e4769d32e..0000000000 --- a/data/core.telegram.org/constructor/updateUserPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateUserPhoto - - - - - - - - - - - - - -
- -
-
-
- -

updateUserPhoto

- -

Change of contact's profile photo.

-

-
updateUserPhoto#95313b0c user_id:int date:int photo:UserProfilePhoto previous:Bool = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser identifier
dateintDate of photo update.
photoUserProfilePhotoNew profile photo
previousBool(boolTrue), if one of the previously used photos is set a profile photo.
-

Type

-

Update

-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserStatus.html b/data/core.telegram.org/constructor/updateUserStatus.html deleted file mode 100644 index 820d1d06fa..0000000000 --- a/data/core.telegram.org/constructor/updateUserStatus.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateUserStatus - - - - - - - - - - - - - -
- -
-
-
- -

updateUserStatus

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserTyping.html b/data/core.telegram.org/constructor/updateUserTyping.html deleted file mode 100644 index da41e6e52f..0000000000 --- a/data/core.telegram.org/constructor/updateUserTyping.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateUserTyping

- -

The user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

-

-
updateUserTyping#5c486927 user_id:int action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser id
actionSendMessageActionAction type
Param added in Layer 17.
-

Type

-

Update

-

Related pages

-

Layers

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateWebPage.html b/data/core.telegram.org/constructor/updateWebPage.html deleted file mode 100644 index 209527cc75..0000000000 --- a/data/core.telegram.org/constructor/updateWebPage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateWebPage - - - - - - - - - - - - - -
- -
-
-
- -

updateWebPage

- -

An instant view webpage preview was generated

-

-
updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
webpageWebPageWebpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.channelDifference b/data/core.telegram.org/constructor/updates.channelDifference deleted file mode 100644 index 11c96aa924..0000000000 --- a/data/core.telegram.org/constructor/updates.channelDifference +++ /dev/null @@ -1,185 +0,0 @@ - - - - - updates.channelDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifference

- -

The new updates

-

-
updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates to be fetched using getDifference, starting from the provided pts
ptsintThe PTS from which to start getting updates the next time
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
new_messagesVector<Message>New messages
other_updatesVector<Update>Other updates
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.channelDifferenceEmpty b/data/core.telegram.org/constructor/updates.channelDifferenceEmpty deleted file mode 100644 index 6b04602f2d..0000000000 --- a/data/core.telegram.org/constructor/updates.channelDifferenceEmpty +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updates.channelDifferenceEmpty - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifferenceEmpty

- -

There are no new updates

-

-
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
ptsintThe latest PTS
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.channelDifferenceTooLong b/data/core.telegram.org/constructor/updates.channelDifferenceTooLong deleted file mode 100644 index b17c4991ea..0000000000 --- a/data/core.telegram.org/constructor/updates.channelDifferenceTooLong +++ /dev/null @@ -1,190 +0,0 @@ - - - - - updates.channelDifferenceTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifferenceTooLong

- -

The provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

-
    -
  1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
  2. -
  3. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
  4. -
  5. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
  6. -
  7. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
  8. -
-

-
updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
dialogDialogDialog containing the latest PTS that can be used to reset the channel state
messagesVector<Message>The latest messages
chatsVector<Chat>Chats from messages
usersVector<User>Users from messages
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

messages.getHistory

-

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

-

messages.getMessages

-

Returns the list of messages by their IDs.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.difference b/data/core.telegram.org/constructor/updates.difference deleted file mode 100644 index 7621c66d72..0000000000 --- a/data/core.telegram.org/constructor/updates.difference +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updates.difference - - - - - - - - - - - - - -
- -
-
-
- -

updates.difference

- -

Full list of occurred events.

-

-
updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
new_messagesVector<Message>List of new messages
new_encrypted_messagesVector<EncryptedMessage>List of new encrypted secret chat messages
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
stateupdates.StateCurrent state
-

Type

-

updates.Difference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.differenceEmpty b/data/core.telegram.org/constructor/updates.differenceEmpty deleted file mode 100644 index 8e9ebdc63e..0000000000 --- a/data/core.telegram.org/constructor/updates.differenceEmpty +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updates.differenceEmpty - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceEmpty

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.differenceSlice b/data/core.telegram.org/constructor/updates.differenceSlice deleted file mode 100644 index 860cc86a6a..0000000000 --- a/data/core.telegram.org/constructor/updates.differenceSlice +++ /dev/null @@ -1,175 +0,0 @@ - - - - - updates.differenceSlice - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceSlice

- -

Incomplete list of occurred events.

-

-
updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
new_messagesVector<Message>List of new messgaes
new_encrypted_messagesVector<EncryptedMessage>New messages from the encrypted event sequence
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
intermediate_stateupdates.StateIntermediary state
-

Type

-

updates.Difference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.differenceTooLong b/data/core.telegram.org/constructor/updates.differenceTooLong deleted file mode 100644 index fa90eee145..0000000000 --- a/data/core.telegram.org/constructor/updates.differenceTooLong +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updates.differenceTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceTooLong

- -

The difference is too long, and the specified state must be used to refetch updates.

-

-
updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
ptsintThe new state to use.
-

Type

-

updates.Difference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.html b/data/core.telegram.org/constructor/updates.html deleted file mode 100644 index 1be0825140..0000000000 --- a/data/core.telegram.org/constructor/updates.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Updates - - - - - - - - - - - - - -
- -
-
-
- -

Updates

- -

Full constructor of updates

-

-
updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seqintTotal number of sent updates
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.state b/data/core.telegram.org/constructor/updates.state deleted file mode 100644 index 74569e17e9..0000000000 --- a/data/core.telegram.org/constructor/updates.state +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updates.state - - - - - - - - - - - - - -
- -
-
-
- -

updates.state

- -

Updates state.

-

-
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintNumber of events occured in a text box
qtsintPosition in a sequence of updates in secret chats. For further detailes refer to article secret chats
Parameter was added in eigth layer.
dateintDate of condition
seqintNumber of sent updates
unread_countintNumber of unread messages
-

Type

-

updates.State

-

Related pages

-

End-to-End Encryption, Secret Chats

-

New feature for end-to-end-encrypted messaging.

-

Layers

-

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

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatesCombined.html b/data/core.telegram.org/constructor/updatesCombined.html deleted file mode 100644 index d37063f429..0000000000 --- a/data/core.telegram.org/constructor/updatesCombined.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updatesCombined - - - - - - - - - - - - - -
- -
-
-
- -

updatesCombined

- -

Constructor for a group of updates.

-

-
updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seq_startintValue seq for the earliest update in a group
seqintValue seq for the latest update in a group
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatesTooLong.html b/data/core.telegram.org/constructor/updatesTooLong.html deleted file mode 100644 index 66da3e8a78..0000000000 --- a/data/core.telegram.org/constructor/updatesTooLong.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updatesTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updatesTooLong

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.cdnFile b/data/core.telegram.org/constructor/upload.cdnFile deleted file mode 100644 index 38a06924a8..0000000000 --- a/data/core.telegram.org/constructor/upload.cdnFile +++ /dev/null @@ -1,149 +0,0 @@ - - - - - upload.cdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.cdnFile

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded b/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded deleted file mode 100644 index 85bfcb1f10..0000000000 --- a/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded +++ /dev/null @@ -1,149 +0,0 @@ - - - - - upload.cdnFileReuploadNeeded - - - - - - - - - - - - - -
- -
-
-
- -

upload.cdnFileReuploadNeeded

- -

The file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.

-

-
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
request_tokenbytesRequest token (see CDN)
-

Type

-

upload.CdnFile

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.file b/data/core.telegram.org/constructor/upload.file deleted file mode 100644 index 8aee3c656e..0000000000 --- a/data/core.telegram.org/constructor/upload.file +++ /dev/null @@ -1,157 +0,0 @@ - - - - - upload.file - - - - - - - - - - - - - -
- -
-
-
- -

upload.file

- -

File content.

-

-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestorage.FileTypeFile type
mtimeintModification type
bytesbytesBinary data, file content
-

Type

-

upload.File

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.fileCdnRedirect b/data/core.telegram.org/constructor/upload.fileCdnRedirect deleted file mode 100644 index 1ac3c8853c..0000000000 --- a/data/core.telegram.org/constructor/upload.fileCdnRedirect +++ /dev/null @@ -1,169 +0,0 @@ - - - - - upload.fileCdnRedirect - - - - - - - - - - - - - -
- -
-
-
- -

upload.fileCdnRedirect

- -

The file must be downloaded from a CDN DC.

-

-
upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintCDN DC ID
file_tokenbytesFile token (see CDN files)
encryption_keybytesEncryption key (see CDN files)
encryption_ivbytesEncryption IV (see CDN files)
file_hashesVector<FileHash>File hashes (see CDN files)
-

Type

-

upload.File

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.webFile b/data/core.telegram.org/constructor/upload.webFile deleted file mode 100644 index e81229b507..0000000000 --- a/data/core.telegram.org/constructor/upload.webFile +++ /dev/null @@ -1,170 +0,0 @@ - - - - - upload.webFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.webFile

- -

Represents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers

-

-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
sizeintFile size
mime_typestringMime type
file_typestorage.FileTypeFile type
mtimeintModified time
bytesbytesData
-

Type

-

upload.WebFile

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/urlAuthResultAccepted.html b/data/core.telegram.org/constructor/urlAuthResultAccepted.html deleted file mode 100644 index 3c088929e0..0000000000 --- a/data/core.telegram.org/constructor/urlAuthResultAccepted.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - urlAuthResultAccepted - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultAccepted

- -

Details about an accepted authorization request, for more info click here »

-

-
urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringThe URL name of the website on which the user has logged in.
-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/urlAuthResultDefault.html b/data/core.telegram.org/constructor/urlAuthResultDefault.html deleted file mode 100644 index 84e580963d..0000000000 --- a/data/core.telegram.org/constructor/urlAuthResultDefault.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - urlAuthResultDefault - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultDefault

- -

Details about an accepted authorization request, for more info click here »

-

-
urlAuthResultDefault#a9d6db1f = UrlAuthResult;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/urlAuthResultRequest.html b/data/core.telegram.org/constructor/urlAuthResultRequest.html deleted file mode 100644 index fc9eb7bda5..0000000000 --- a/data/core.telegram.org/constructor/urlAuthResultRequest.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - urlAuthResultRequest - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultRequest

- -

Details about the authorization request, for more info click here »

-

-
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueWhether the bot would like to send messages to the user
botUserUsername of a bot, which will be used for user authorization. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
domainstringThe domain name of the website on which the user will log in.
-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/user.html b/data/core.telegram.org/constructor/user.html deleted file mode 100644 index 1ec5965d9b..0000000000 --- a/data/core.telegram.org/constructor/user.html +++ /dev/null @@ -1,282 +0,0 @@ - - - - - user - - - - - - - - - - - - - -
- -
-
-
- -

user

- -

Indicates info about a certain user

-

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

-

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
idintID 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 deleted file mode 100644 index 8a75a41760..0000000000 --- a/data/core.telegram.org/constructor/userEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - userEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/userForeign.html b/data/core.telegram.org/constructor/userForeign.html deleted file mode 100644 index e080eac64b..0000000000 --- a/data/core.telegram.org/constructor/userForeign.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - userForeign - - - - - - - - - - - - - -
- -
-
-
- -

userForeign

- -

A user that is not a contact of the current user.

-

-
Constructor schema is available as of layer 18. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintUser identifier
first_namestringFirst name as supplied by the user
last_namestringLast name as supplied by the user
access_hashlongChecksum dependent on the user identifier
photoUserProfilePhotoProfile photo
statusUserStatusCurrent status
usernamestringUsername
Parameter added in Layer 18.
-

Type

-

User

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userFull.html b/data/core.telegram.org/constructor/userFull.html deleted file mode 100644 index 4d10ad3abd..0000000000 --- a/data/core.telegram.org/constructor/userFull.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - userFull - - - - - - - - - - - - - -
- -
-
-
- -

userFull

- -

Extended user info

-

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

-

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
-

Type

-

UserFull

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

-

Pinned messages

-

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

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userProfilePhoto.html b/data/core.telegram.org/constructor/userProfilePhoto.html deleted file mode 100644 index e3b72bd986..0000000000 --- a/data/core.telegram.org/constructor/userProfilePhoto.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - userProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

userProfilePhoto

- -

User profile photo.

-

-
userProfilePhoto#69d3ab26 flags:# has_video:flags.0?true photo_id:long photo_small:FileLocation photo_big:FileLocation 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
photo_smallFileLocationLocation of the file, corresponding to the small profile photo thumbnail
photo_bigFileLocationLocation of the file, corresponding to the big profile photo 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 scheme changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userProfilePhotoEmpty.html b/data/core.telegram.org/constructor/userProfilePhotoEmpty.html deleted file mode 100644 index 884b419182..0000000000 --- a/data/core.telegram.org/constructor/userProfilePhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userProfilePhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

userProfilePhotoEmpty

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userRequest.html b/data/core.telegram.org/constructor/userRequest.html deleted file mode 100644 index 970414f6c4..0000000000 --- a/data/core.telegram.org/constructor/userRequest.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - userRequest - - - - - - - - - - - - - -
- -
-
-
- -

userRequest

- -

A user that is not a contact of the current user, but whose phone number is available.

-

-
Constructor schema is available as of layer 18. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintUser identifier
first_namestringFirst name the user supplied
last_namestringLast name the user supplied
access_hashlongChecksum dependent on the user identifier
phonestringPhone number
photoUserProfilePhotoProfile photo
statusUserStatusCurrent status
usernamestringUsername
Parameter added in Layer 18.
-

Type

-

User

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusEmpty.html b/data/core.telegram.org/constructor/userStatusEmpty.html deleted file mode 100644 index a277a06165..0000000000 --- a/data/core.telegram.org/constructor/userStatusEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusLastMonth.html b/data/core.telegram.org/constructor/userStatusLastMonth.html deleted file mode 100644 index 4a3ee5f5b6..0000000000 --- a/data/core.telegram.org/constructor/userStatusLastMonth.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusLastMonth - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusLastWeek.html b/data/core.telegram.org/constructor/userStatusLastWeek.html deleted file mode 100644 index 375e0ee11f..0000000000 --- a/data/core.telegram.org/constructor/userStatusLastWeek.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusLastWeek - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusOffline.html b/data/core.telegram.org/constructor/userStatusOffline.html deleted file mode 100644 index 008dc4c0fa..0000000000 --- a/data/core.telegram.org/constructor/userStatusOffline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - userStatusOffline - - - - - - - - - - - - - -
- -
-
-
- -

userStatusOffline

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusOnline.html b/data/core.telegram.org/constructor/userStatusOnline.html deleted file mode 100644 index 633cc8a802..0000000000 --- a/data/core.telegram.org/constructor/userStatusOnline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - userStatusOnline - - - - - - - - - - - - - -
- -
-
-
- -

userStatusOnline

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusRecently.html b/data/core.telegram.org/constructor/userStatusRecently.html deleted file mode 100644 index 32c3612607..0000000000 --- a/data/core.telegram.org/constructor/userStatusRecently.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusRecently - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/vector.html b/data/core.telegram.org/constructor/vector.html deleted file mode 100644 index 28f3c03fad..0000000000 --- a/data/core.telegram.org/constructor/vector.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - vector - - - - - - - - - - - - - -
- -
-
-
- -

vector

- -

A universal vector constructor.

-

-
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Vector t

-

Params additional

-

For serialization write the constructor id 0x1cb5c415:int, then the number of vector elements - #:int, then, one after another, the # of the elements of the type t, that was implicitly passed to the constructor.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/videoSize.html b/data/core.telegram.org/constructor/videoSize.html deleted file mode 100644 index 12931646d0..0000000000 --- a/data/core.telegram.org/constructor/videoSize.html +++ /dev/null @@ -1,180 +0,0 @@ - - - - - videoSize - - - - - - - - - - - - - -
- -
-
-
- -

videoSize

- -

Animated profile picture in MPEG4 format

-

-
videoSize#e831c556 flags:# type:string location:FileLocation 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
locationFileLocationFile location
wintVideo width
hintVideo height
sizeintFile size
video_start_tsflags.0?doubleTimestamp that should be shown as static preview to the user (seconds)
-

Type

-

VideoSize

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/wallPaper.html b/data/core.telegram.org/constructor/wallPaper.html deleted file mode 100644 index 5565f05212..0000000000 --- a/data/core.telegram.org/constructor/wallPaper.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - wallPaper - - - - - - - - - - - - - -
- -
-
-
- -

wallPaper

- -

Wallpaper settings.

-

-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongIdentifier
flags#Flags, see TL conditional fields
creatorflags.0?trueCreator of the wallpaper
defaultflags.1?trueWhether this is the default wallpaper
patternflags.3?truePattern
darkflags.4?trueDark mode
access_hashlongAccess hash
slugstringUnique wallpaper ID
documentDocumentThe actual wallpaper
settingsflags.2?WallPaperSettingsWallpaper settings
-

Type

-

WallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/wallPaperNoFile.html b/data/core.telegram.org/constructor/wallPaperNoFile.html deleted file mode 100644 index a4f77bb5ce..0000000000 --- a/data/core.telegram.org/constructor/wallPaperNoFile.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - wallPaperNoFile - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperNoFile

- -

No file wallpaper

-

-
wallPaperNoFile#8af40b25 flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
defaultflags.1?trueWhether this is the default wallpaper
darkflags.4?trueDark mode
settingsflags.2?WallPaperSettingsWallpaper settings
-

Type

-

WallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/wallPaperSettings.html b/data/core.telegram.org/constructor/wallPaperSettings.html deleted file mode 100644 index 81f3390763..0000000000 --- a/data/core.telegram.org/constructor/wallPaperSettings.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - wallPaperSettings - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperSettings

- -

Wallpaper settings

-

-
wallPaperSettings#5086cf8 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;

-

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
intensityflags.3?intIntensity of the pattern when it is shown above the main background color, 0-100
rotationflags.4?intClockwise rotation angle of the gradient, in degrees; 0-359. Should be always divisible by 45
-

Type

-

WallPaperSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/wallPaperSolid.html b/data/core.telegram.org/constructor/wallPaperSolid.html deleted file mode 100644 index e7f3679044..0000000000 --- a/data/core.telegram.org/constructor/wallPaperSolid.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - wallPaperSolid - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperSolid

- -

One-color background wallpaper (no image).

-

-
Constructor schema is available as of layer 93. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintIdentifier
titlestringName
bg_colorintBackground color (RGB)
colorintBasic background color (RGB)
-

Type

-

WallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webAuthorization.html b/data/core.telegram.org/constructor/webAuthorization.html deleted file mode 100644 index c8ad67c4cd..0000000000 --- a/data/core.telegram.org/constructor/webAuthorization.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - webAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

webAuthorization

- -

Represents a bot logged in using the Telegram login widget

-

-
webAuthorization#cac943f2 hash:long bot_id:int domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongAuthorization hash
bot_idintBot ID
domainstringThe domain name of the website on which the user has logged in.
browserstringBrowser user-agent
platformstringPlatform
date_createdintWhen was the web session created
date_activeintWhen was the web session last active
ipstringIP address
regionstringRegion, determined from IP address
-

Type

-

WebAuthorization

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webDocument.html b/data/core.telegram.org/constructor/webDocument.html deleted file mode 100644 index e9d6e39446..0000000000 --- a/data/core.telegram.org/constructor/webDocument.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - webDocument - - - - - - - - - - - - - -
- -
-
-
- -

webDocument

- -

Remote document

-

-
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringDocument URL
access_hashlongAccess hash
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

WebDocument

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webDocumentNoProxy.html b/data/core.telegram.org/constructor/webDocumentNoProxy.html deleted file mode 100644 index 95f656d424..0000000000 --- a/data/core.telegram.org/constructor/webDocumentNoProxy.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - webDocumentNoProxy - - - - - - - - - - - - - -
- -
-
-
- -

webDocumentNoProxy

- -

Remote document that can be downloaded without proxying through telegram

-

-
webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringDocument URL
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

WebDocument

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPage.html b/data/core.telegram.org/constructor/webPage.html deleted file mode 100644 index 7501af065f..0000000000 --- a/data/core.telegram.org/constructor/webPage.html +++ /dev/null @@ -1,240 +0,0 @@ - - - - - webPage - - - - - - - - - - - - - -
- -
-
-
- -

webPage

- -

Webpage preview

-

-
webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongPreview ID
urlstringURL of previewed webpage
display_urlstringWebpage URL to be displayed to the user
hashintHash for pagination, for more info click here
typeflags.0?stringType of the web page. Can be: article, photo, audio, video, document, profile, app, or something else
site_nameflags.1?stringShort name of the site (e.g., Google Docs, App Store)
titleflags.2?stringTitle of the content
descriptionflags.3?stringContent description
photoflags.4?PhotoImage representing the content
embed_urlflags.5?stringURL to show in the embedded preview
embed_typeflags.5?stringMIME type of the embedded preview, (e.g., text/html or video/mp4)
embed_widthflags.6?intWidth of the embedded preview
embed_heightflags.6?intHeight of the embedded preview
durationflags.7?intDuration of the content, in seconds
authorflags.8?stringAuthor of the content
documentflags.9?DocumentPreview of the content as a media file
cached_pageflags.10?PagePage contents in instant view format
attributesflags.12?Vector<WebPageAttribute>Webpage attributes
-

Type

-

WebPage

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPageAttributeTheme.html b/data/core.telegram.org/constructor/webPageAttributeTheme.html deleted file mode 100644 index 03ffe97771..0000000000 --- a/data/core.telegram.org/constructor/webPageAttributeTheme.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - webPageAttributeTheme - - - - - - - - - - - - - -
- -
-
-
- -

webPageAttributeTheme

- -

Page theme

-

-
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
documentsflags.0?Vector<Document>Theme files
settingsflags.1?ThemeSettingsTheme settings
-

Type

-

WebPageAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPageEmpty.html b/data/core.telegram.org/constructor/webPageEmpty.html deleted file mode 100644 index 1a19eab897..0000000000 --- a/data/core.telegram.org/constructor/webPageEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - webPageEmpty - - - - - - - - - - - - - -
- - - -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPageNotModified.html b/data/core.telegram.org/constructor/webPageNotModified.html deleted file mode 100644 index e7a1c86498..0000000000 --- a/data/core.telegram.org/constructor/webPageNotModified.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - webPageNotModified - - - - - - - - - - - - - -
- -
-
-
- -

webPageNotModified

- -

The preview of the webpage hasn't changed

-

-
webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
cached_page_viewsflags.0?intPage view count
-

Type

-

WebPage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPagePending.html b/data/core.telegram.org/constructor/webPagePending.html deleted file mode 100644 index 682abad338..0000000000 --- a/data/core.telegram.org/constructor/webPagePending.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - webPagePending - - - - - - - - - - - - - -
- -
-
-
- -

webPagePending

- - - -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/contest300K.html b/data/core.telegram.org/contest300K.html deleted file mode 100644 index d88b5642be..0000000000 --- a/data/core.telegram.org/contest300K.html +++ /dev/null @@ -1,237 +0,0 @@ - - - - - Telegram Cracking Contest Description - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Cracking Contest Description

- -

« Back to Contest Announcement

-
-

The current round of the contest is over. Go to results »

-
-

In this contest you assume the role of a malicious entity in control of Telegram's servers. Your goal is to extract sensitive data (a secret email and password) from a conversation between two peers — Paul and Nick. They are represented by two virtual users that communicate via Secret Chats in Telegram.

-

Paul and Nick are both using clients that perform all the checks from Telegram Security Guidelines and compare their key visualizations over an independent channel as soon as a new Secret Chat is established. If any of these checks fails, they stop accepting messages in that Secret Chat. You control the entire process by sending commands to the Telegram user @CryptoContest, used as an interface for this contest. This enables contestants to try CPA, KPA, MITM and other kinds of active attacks and data tampering.

-

Protocol

-

The protocol used by Paul and Nick to establish Secret Сhats and exchange messages is identical to the one used for Secret Chats in Telegram. Since we assume that the attacker is already in full control of the Telegram servers, basic MTProto encryption is bypassed altogether. In order to further simplify the task for contestants, we have removed irrelevant parameters, such as user_id and random_id.

-

The following TL scheme is used to establish Secret Chats in this contest:

-
contest.dhConfig#01e00a51 g:int p:64*[int] random:64*[int] = contest.DhConfig;
-contest.requestEncryption#3a73a74c g_a:64*[int] = contest.Message;
-contest.acceptEncryption#068e4342 g_b:64*[int] fingerprint:int = contest.Message;
-contest.encryptedMessage#11a6d4b1 id:long message:string = contest.Message;
----functions---
-contest.getDhConfig#369ee1a6 = contest.DhConfig;
-

For exchange of encrypted messages (see documentation), the up-to-date layer 17 scheme with sequence numbers is used, but with plain text message support only.

-

Each plaintext message is first created as a layer 17 decryptedMessage, then embedded in a decryptedMessageLayer and encrypted as explained in the Secret Chat documentation. For the purpose of this contest, it is the result of this encryption (ciphertext) that is exchanged between the parties.

-

Notice that sending messages in an actual Telegram Secret Chat involves further embedding of that ciphertext into an API call and an additional layer of MTProto encryption for client-server interaction. This step is omitted here, since we assume the attacker to be in control of the Telegram servers, not just of the communication lines between the clients and Telegram servers.

-

Interface

-

To access the interface, find the Telegram user @CryptoContest using the Global Search by username in any of the Telegram apps. This is a special bot we created for this contest. You can control communication between Paul and Nick by sending particularly formed text messages to this bot and processing automatically generated answers to these messages (you may find the unofficial Linux CLI convenient for mass automated queries).

-

You can create as many parallel Secret Chats between Paul and Nick as you like using the bot — each of them will have a separate session_id. All data is represented in hexadecimal format, with the exception of the session_id.

-

Commands

-

Below, A stands for the creator of the Secret Chat, B stands for the second party, S — the Telegram Server.

-

Each Secret Chat session in this contest is divided in two phases:

- -
1. Creating a Secret Chat
-

In order to create a new Secret Chat, six messages need to be exchanged:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SourceDestinationMessage
AScontest.getDhConfig
SAcontest.DhConfig
ABcontest.requestEncryption
BScontest.getDhConfig
SBcontest.DhConfig
BAcontest.acceptEncryption
-

To create a Secret Chat in this contest:

-
    -
  • Send the START command to the user @CryptoContest in Telegram. You'll get the getDhConfig query, sent by A to the Server, and the answer that the server would normally send to A. You shall also receive the new session_id as the first 32-bit integer. All further messages related to this particular session (Secret Chat instance) must be prefixed with this session_id in decimal form.
  • -
  • After that, use the PASS command to pass the server's answer to A or ANSWER bytes to send a different answer instead. Bytes is represented by a string of an even number of hexadecimal digits. You'll receive the requestEncryption query as the result.
  • -
  • After that, use the PASS command to pass this query to B or ANSWER bytes to arbitrarily change it. You‘ll receive B’s getDhConfig to the server as the result.
  • -
  • As before, you can use either PASS or ANSWER bytes. You'll receive acceptEncryption as the result.
  • -
  • As before, you can use either PASS or ANSWER bytes. You'll receive “Ok” as the result.
  • -
-

You will receive an error text as the result after any of these steps in case the participating clients perceive that something went wrong. This can happen if a security check is failed, or in the case that the first 128 bits of the SHA-1 of the newly created encryption key don‘t match on both parties’ clients when this stage is completed (this corresponds to Paul and Nick comparing the key visualizations for the Secret Chat in their Telegram apps).

-

If you obtain such an error, the session is failed and can no longer be used. You'll have to start new session. Note that the time to complete this phase is limited. Each step should not take longer than one hour, otherwise the Secret Chat will get cancelled.

-

Example:

-
START
-15 a6e19e36 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b202d33053c2340fd84dd024e8012277e9c6442ad7cd09fe85955c13196e2d32861ad0d8f8139ce5870f1c3563fbff77428632897352abd91cd0a6497a0f64a33d87cd8b53470cf1bc6a052bba7d0121623e9611c0de83ffeb63b7d15831a70187093373cb20df5613bdfab12a54bbc6fff94598d95a8dcdb1374631b021e77c350261bca9ffc16c59b19d3041bee011a20b06fc9806d633b6b9cdd79cbb8b02fe8ef9dde29b6d31d80b030c69d67d6fc4a7edb33ffab532d085796cf3e7635fd42ee72ea24840082186fd40c3c45cf0acef886533d4de7468f88942a662d302928470aa8704529180a6aec2f877398efb91893cc9b549e5123d7269adfe7b6ee
-15 PASS
-15 4ca7733a1a7823b420111d8e86e3fe9a7cff9fc611ce339d6999fc3053973ef6c8276af841b53547fdebdcb057cbad16aff6178be3fb8747889937dec082c984227c974a19232b85ad85ef457521fcf17d5f697a17b7e62952306f0ed086deb1ebcff0c8a32787789fe7afaa4035c2d0e07c10db46c0df6930a1729d3607fb035154e90c02036318862c5a9537e87a55bc656e3fc53db08f41a07f834e4917ebaaace1214409ffb44c5a806a9cb4def209bfb8ab2e59f1cb6257e422f37dfab288170bdc5666e6a63d1b0447a7b935ad3bdac8d53f64278d433b45925c84dc60214473363d57a30e31324d9b3cc42fb56d375aac2d9d1af16331ad3a92b43a9d64e47813
-15 PASS
-15 a6e19e36 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b1ccd9c752428f0bca9ac9060bb85b8f90acb9374cd8d5a03110635f591a18f131cb7cc204407efec0687a8b77ba6c4e6732c35174e79e36aaa7fa6ab685257710e074065961ce1b16d21fed8a83cd95efcc4be7111cd33b5704fe759dfab21fc3e8aaa86d44609dc0b073354f8160c653f4fbde3ae7c28c87c3667e0797fac24b32e5c1a870cd898b2a9c517709bb0b8e4ee875ff857868eb56548e6dc993f198fd78c8a77cf997ed42a15f99a9b6265c7cf9bedc7580a11514047b881f717b233f3570ec21856bd2b9791e4c43b125e9260ac3fd48b9a10de5f9d5080e53d92d194adb796766684d905cca35e691fab0c76d6b5f49242f81eb92fcc8adc5a64
-15 ANSWER 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b1ccd9c752428f0bca9ac9060bb85b8f90acb9374cd8d5a03110635f591a18f131cb7cc204407efec0687a8b77ba6c4e6732c35174e79e36aaa7fa6ab685257710e074065961ce1b16d21fed8a83cd95efcc4be7111cd33b5704fe759dfab21fc3e8aaa86d44609dc0b073354f8160c653f4fbde3ae7c28c87c3667e0797fac24b32e5c1a870cd898b2a9c517709bb0b8e4ee875ff857868eb56548e6dc993f198fd78c8a77cf997ed42a15f99a9b6265c7cf9bedc7580a11514047b881f717b233f3570ec21856bd2b9791e4c43b125e9260ac3fd48b9a10de5f9d5080e53d92d194adb796766684d905cca35e691fab0c76d6b5f49242f81eb92fcc8ad00000
-15 42438e06bbb424bba5fd95122ec2f206c9b502f1f6d4e4fdbf74ed2c946ad60abaefd6fbd6a08e3ef418709d15bc557ef5e486a51d1e304f6c1e943faad948fde4e6273c0cad0df07068ad028fb01dc0fd7221aeed6ed5dc510dbe4824939036b0f3a45e740b40cef86a32f0b73b20234efc41d573f3e14efc08b3f65e9f7be52d5b930de52d41c7aadc4e0e85dfcf3bb1dd2e9cdf94fc236082879aea27207415cb846a5d5969e619040416a7f0f708f56a5b340a8fd0be1a26bfdc3de365a950532d363b427d6d905af7534af574ae8afd3f47658de5da3fa02dd818a31523122ff53dd31ffd7aa22e53cbf2da7772a1589e9a242f28f9cb1130f54553fcb355b3398fc877b80b3ef2cc3d
-15 PASS
-15 Ok
-
2. Sending Text Messages
-

Once the Secret Chat has been established, you can use the following queries to make Paul and Nick exchange text messages inside the Secret Chat:

-
    -
  • ASK [A|B] — asks A or B to send a random plaintext message to the other party. It is guaranteed that at least one of the first ten generated messages will contain the secret email and password that are the goal of this contest. It is also guaranteed that apart from that, all messages will contain only dictionary English words, spaces, line breaks and punctuation marks. The result to this query is the ciphertext corresponding to the randomly generated plaintext.
  • -
  • TXT [A|B] bytes — asks A or B to encrypt bytes as the (plaintext) contents of a text message and send it to the other party. Note that bytes can be any byte sequence, not necessarily a valid UTF-8 sequence. The result to this query is the ciphertext corresponding to the given plaintext.
  • -
  • MSG [A|B] bytes — send a specified (ciphertext) message (for example, obtained as an answer to an ASK or TXT query) to A or B. You will receive ‘Ok’ if this message was decrypted successfully and accepted by the client, or ‘Fail’ otherwise.
  • -
-

Example:

-
15 ASK A
-15 b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b5
-15 MSG B b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b0
-15 Fail
-15 MSG B b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b5
-15 Ok
-15 TXT B abac
-15 b1d4a61101771d42f62323e6fe680000c877b80b3ef2cc3df751e68b935b083a6f5c15ba8d95b94388fc34453a1e7b9b20222402b7698be5dd8a6ff69a5141b01ca2488b0dada8f2b0e47980218f48912168ddd2cebd3b61b1edf2f557c7ec44768595ce1cb42a01f7c14dd4e6e6e7601cb17ab0b6d5a274
-
-

Objectives

-

We are offering a $300,000 reward to the first person to break Telegram's encryption protocol in this contest.

-

Your goal is to extract a secret email address from one of the random messages that are exchanged between Nick and Paul when you use the ASK command. It is guaranteed that at least one of the first ten generated messages within a session will contain the secret address. It is also guaranteed that apart from that, all messages will contain only dictionary English words, spaces, line breaks and punctuation marks.

-

Once you have the address, you will need to send an email to it. That email must contain:
- The entire text of the message that contained the secret email.
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $300,000 prize.

-

Decrypting messages

-

To prove that the competition was fair, we will add a command that returns the keys used for a particular session by its session_id at the end of the contest. This will be done as soon as a winner is announced, or on February 4, 2015 in case no winner is announced to that date.

-

Bonus objective

-

We are also offering an independent $100,000 reward to the first person to make the bot accept a ciphertext message (i.e. the first person to send a message using MSG [A|B] bytes and receive the result ‘OK’), provided that that ciphertext deciphers to a plaintext that was never encrypted by the bot itself within this session.

-

Should you succeed at this, kindly send an email to security@telegram.org and include the following:
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $100,000 prize.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/contestfaq.html b/data/core.telegram.org/contestfaq.html deleted file mode 100644 index daadde049f..0000000000 --- a/data/core.telegram.org/contestfaq.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - Security Contest Winter 2013-2014 FAQ - - - - - - - - - - - - - -
- -
-
-
-
- -
- -
-

Security Contest Winter 2013-2014 FAQ

- -
-

This contest has ended. Check out our new contest »

-
-

Q: Why did you launch this contest?

-

The goal of this contest is to solve a real-life problem. The question at hand is whether your internet-provider or another entity that intercepts your traffic would be able to decrypt your conversations over Telegram. We are inviting hackers and security experts to find ways of decrypting Telegram traffic. As a result we will either find a vulnerability in our encryption algorithm and fix it, or or get indirect evidence that decrypting our traffic is no easy task.

-

Q: What happens if someone wins?

-

If we have a winner in the current competition, we will start a new competition with an even larger prize. Of course, before launching a new competition we will have to fix the vulnerability that allowed the winner to decipher the traffic of Telegram.

-

Q: What do I have access to?

-

You have access to a detailed description of the encryption system we use, app source code, as well as complete traffic logs for the target ‘Paul’ (+79112317383) from the day he signed up for Telegram, updated in real time.

-

You need to decipher the secret email address, that Paul sends daily in one of the messages to ‘Nick’ (+79218944725), and describe the successful attack in an email to that address.

-

Q: What is the structure of your traffic log?

-

The structure of the traffic log is as follows:

-
    Unixtime Length-in-bytes Direction (in/out) ServerIP:Port Hexdump.
-

For your convenience, only high-level TCP stream bytes are shown, ignoring IP packet boundaries and omitting TCP/IP headers.

-

Q: Does Paul send the same message to Nick every day?

-

No, just as in real life, Paul‘s messages to Nick can be different each time. The only thing that doesn’t change is the secret email address in his daily messages.

-

Q: Could you provide an example of a Paul's message to Nick?

-

Sure. The message may look like “Hey Nick, so here is the secret email address for the bounty hunters – {here goes the email}”.

-

Q: I want to try active attacks in the current contest, how can I do that?

-

At this stage, it is possible to analyze the traffic and send modified packets to the server, therefore perfoming length extension attacks, replay attacks etc. In case nobody achieves the goal of the current contest (deciphering intercepted Telegram traffic) by March 2014, we are willing to facilitate the task and provide the contestants with tools for performing more complicated active attacks.

-

Q: What if I don‘t trust bitcoins and don’t want them as a prize?

-

If the winner prefers conventional money over bitcoin, we will be happy to transfer them 200,000 regular USD instead of BTC.

-

Q: It is only 2,5 months. I need more time to find bugs in your protocol!

-

The contests to crack Telegram's encrypted protocol are a permanent feature of our project. We will always be launching a new contest after the end of the previous one, and the amount of the prize money is likely to increase. So whenever you are the first person to find vulnerabilities in our encryption system, you will be able to claim a prize — even after the current competition is over.

-
- -
- -

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/css/bootstrap-extra.css b/data/core.telegram.org/css/bootstrap-extra.css deleted file mode 100644 index 8a35b6069b..0000000000 --- a/data/core.telegram.org/css/bootstrap-extra.css +++ /dev/null @@ -1,3274 +0,0 @@ -/* glyph */ -@font-face { - font-family: 'Glyphicons Halflings'; - src: url('../fonts/glyphicons-halflings-regular.eot'); - src: url('../fonts/glyphicons-halflings-regular.eot?#iefix') format('embedded-opentype'), url('../fonts/glyphicons-halflings-regular.woff') format('woff'), url('../fonts/glyphicons-halflings-regular.ttf') format('truetype'), url('../fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular') format('svg'); -} -.glyphicon { - position: relative; - top: 1px; - display: inline-block; - font-family: 'Glyphicons Halflings'; - font-style: normal; - font-weight: normal; - line-height: 1; - -webkit-font-smoothing: antialiased; - -moz-osx-font-smoothing: grayscale; -} -.glyphicon-asterisk:before { - content: "\2a"; -} -.glyphicon-plus:before { - content: "\2b"; -} -.glyphicon-euro:before { - content: "\20ac"; -} -.glyphicon-minus:before { - content: "\2212"; -} -.glyphicon-cloud:before { - content: "\2601"; -} -.glyphicon-envelope:before { - content: "\2709"; -} -.glyphicon-pencil:before { - content: "\270f"; -} -.glyphicon-glass:before { - content: "\e001"; -} -.glyphicon-music:before { - content: "\e002"; -} -.glyphicon-search:before { - content: "\e003"; -} -.glyphicon-heart:before { - content: "\e005"; -} -.glyphicon-star:before { - content: "\e006"; -} -.glyphicon-star-empty:before { - content: "\e007"; -} -.glyphicon-user:before { - content: "\e008"; -} -.glyphicon-film:before { - content: "\e009"; -} -.glyphicon-th-large:before { - content: "\e010"; -} -.glyphicon-th:before { - content: "\e011"; -} -.glyphicon-th-list:before { - content: "\e012"; -} -.glyphicon-ok:before { - content: "\e013"; -} -.glyphicon-remove:before { - content: "\e014"; -} -.glyphicon-zoom-in:before { - content: "\e015"; -} -.glyphicon-zoom-out:before { - content: "\e016"; -} -.glyphicon-off:before { - content: "\e017"; -} -.glyphicon-signal:before { - content: "\e018"; -} -.glyphicon-cog:before { - content: "\e019"; -} -.glyphicon-trash:before { - content: "\e020"; -} -.glyphicon-home:before { - content: "\e021"; -} -.glyphicon-file:before { - content: "\e022"; -} -.glyphicon-time:before { - content: "\e023"; -} -.glyphicon-road:before { - content: "\e024"; -} -.glyphicon-download-alt:before { - content: "\e025"; -} -.glyphicon-download:before { - content: "\e026"; -} -.glyphicon-upload:before { - content: "\e027"; -} -.glyphicon-inbox:before { - content: "\e028"; -} -.glyphicon-play-circle:before { - content: "\e029"; -} -.glyphicon-repeat:before { - content: "\e030"; -} -.glyphicon-refresh:before { - content: "\e031"; -} -.glyphicon-list-alt:before { - content: "\e032"; -} -.glyphicon-lock:before { - content: "\e033"; -} -.glyphicon-flag:before { - content: "\e034"; -} -.glyphicon-headphones:before { - content: "\e035"; -} -.glyphicon-volume-off:before { - content: "\e036"; -} -.glyphicon-volume-down:before { - content: "\e037"; -} -.glyphicon-volume-up:before { - content: "\e038"; -} -.glyphicon-qrcode:before { - content: "\e039"; -} -.glyphicon-barcode:before { - content: "\e040"; -} -.glyphicon-tag:before { - content: "\e041"; -} -.glyphicon-tags:before { - content: "\e042"; -} -.glyphicon-book:before { - content: "\e043"; -} -.glyphicon-bookmark:before { - content: "\e044"; -} -.glyphicon-print:before { - content: "\e045"; -} -.glyphicon-camera:before { - content: "\e046"; -} -.glyphicon-font:before { - content: "\e047"; -} -.glyphicon-bold:before { - content: "\e048"; -} -.glyphicon-italic:before { - content: "\e049"; -} -.glyphicon-text-height:before { - content: "\e050"; -} -.glyphicon-text-width:before { - content: "\e051"; -} -.glyphicon-align-left:before { - content: "\e052"; -} -.glyphicon-align-center:before { - content: "\e053"; -} -.glyphicon-align-right:before { - content: "\e054"; -} -.glyphicon-align-justify:before { - content: "\e055"; -} -.glyphicon-list:before { - content: "\e056"; -} -.glyphicon-indent-left:before { - content: "\e057"; -} -.glyphicon-indent-right:before { - content: "\e058"; -} -.glyphicon-facetime-video:before { - content: "\e059"; -} -.glyphicon-picture:before { - content: "\e060"; -} -.glyphicon-map-marker:before { - content: "\e062"; -} -.glyphicon-adjust:before { - content: "\e063"; -} -.glyphicon-tint:before { - content: "\e064"; -} -.glyphicon-edit:before { - content: "\e065"; -} -.glyphicon-share:before { - content: "\e066"; -} -.glyphicon-check:before { - content: "\e067"; -} -.glyphicon-move:before { - content: "\e068"; -} -.glyphicon-step-backward:before { - content: "\e069"; -} -.glyphicon-fast-backward:before { - content: "\e070"; -} -.glyphicon-backward:before { - content: "\e071"; -} -.glyphicon-play:before { - content: "\e072"; -} -.glyphicon-pause:before { - content: "\e073"; -} -.glyphicon-stop:before { - content: "\e074"; -} -.glyphicon-forward:before { - content: "\e075"; -} -.glyphicon-fast-forward:before { - content: "\e076"; -} -.glyphicon-step-forward:before { - content: "\e077"; -} -.glyphicon-eject:before { - content: "\e078"; -} -.glyphicon-chevron-left:before { - content: "\e079"; -} -.glyphicon-chevron-right:before { - content: "\e080"; -} -.glyphicon-plus-sign:before { - content: "\e081"; -} -.glyphicon-minus-sign:before { - content: "\e082"; -} -.glyphicon-remove-sign:before { - content: "\e083"; -} -.glyphicon-ok-sign:before { - content: "\e084"; -} -.glyphicon-question-sign:before { - content: "\e085"; -} -.glyphicon-info-sign:before { - content: "\e086"; -} -.glyphicon-screenshot:before { - content: "\e087"; -} -.glyphicon-remove-circle:before { - content: "\e088"; -} -.glyphicon-ok-circle:before { - content: "\e089"; -} -.glyphicon-ban-circle:before { - content: "\e090"; -} -.glyphicon-arrow-left:before { - content: "\e091"; -} -.glyphicon-arrow-right:before { - content: "\e092"; -} -.glyphicon-arrow-up:before { - content: "\e093"; -} -.glyphicon-arrow-down:before { - content: "\e094"; -} -.glyphicon-share-alt:before { - content: "\e095"; -} -.glyphicon-resize-full:before { - content: "\e096"; -} -.glyphicon-resize-small:before { - content: "\e097"; -} -.glyphicon-exclamation-sign:before { - content: "\e101"; -} -.glyphicon-gift:before { - content: "\e102"; -} -.glyphicon-leaf:before { - content: "\e103"; -} -.glyphicon-fire:before { - content: "\e104"; -} -.glyphicon-eye-open:before { - content: "\e105"; -} -.glyphicon-eye-close:before { - content: "\e106"; -} -.glyphicon-warning-sign:before { - content: "\e107"; -} -.glyphicon-plane:before { - content: "\e108"; -} -.glyphicon-calendar:before { - content: "\e109"; -} -.glyphicon-random:before { - content: "\e110"; -} -.glyphicon-comment:before { - content: "\e111"; -} -.glyphicon-magnet:before { - content: "\e112"; -} -.glyphicon-chevron-up:before { - content: "\e113"; -} -.glyphicon-chevron-down:before { - content: "\e114"; -} -.glyphicon-retweet:before { - content: "\e115"; -} -.glyphicon-shopping-cart:before { - content: "\e116"; -} -.glyphicon-folder-close:before { - content: "\e117"; -} -.glyphicon-folder-open:before { - content: "\e118"; -} -.glyphicon-resize-vertical:before { - content: "\e119"; -} -.glyphicon-resize-horizontal:before { - content: "\e120"; -} -.glyphicon-hdd:before { - content: "\e121"; -} -.glyphicon-bullhorn:before { - content: "\e122"; -} -.glyphicon-bell:before { - content: "\e123"; -} -.glyphicon-certificate:before { - content: "\e124"; -} -.glyphicon-thumbs-up:before { - content: "\e125"; -} -.glyphicon-thumbs-down:before { - content: "\e126"; -} -.glyphicon-hand-right:before { - content: "\e127"; -} -.glyphicon-hand-left:before { - content: "\e128"; -} -.glyphicon-hand-up:before { - content: "\e129"; -} -.glyphicon-hand-down:before { - content: "\e130"; -} -.glyphicon-circle-arrow-right:before { - content: "\e131"; -} -.glyphicon-circle-arrow-left:before { - content: "\e132"; -} -.glyphicon-circle-arrow-up:before { - content: "\e133"; -} -.glyphicon-circle-arrow-down:before { - content: "\e134"; -} -.glyphicon-globe:before { - content: "\e135"; -} -.glyphicon-wrench:before { - content: "\e136"; -} -.glyphicon-tasks:before { - content: "\e137"; -} -.glyphicon-filter:before { - content: "\e138"; -} -.glyphicon-briefcase:before { - content: "\e139"; -} -.glyphicon-fullscreen:before { - content: "\e140"; -} -.glyphicon-dashboard:before { - content: "\e141"; -} -.glyphicon-paperclip:before { - content: "\e142"; -} -.glyphicon-heart-empty:before { - content: "\e143"; -} -.glyphicon-link:before { - content: "\e144"; -} -.glyphicon-phone:before { - content: "\e145"; -} -.glyphicon-pushpin:before { - content: "\e146"; -} -.glyphicon-usd:before { - content: "\e148"; -} -.glyphicon-gbp:before { - content: "\e149"; -} -.glyphicon-sort:before { - content: "\e150"; -} -.glyphicon-sort-by-alphabet:before { - content: "\e151"; -} -.glyphicon-sort-by-alphabet-alt:before { - content: "\e152"; -} -.glyphicon-sort-by-order:before { - content: "\e153"; -} -.glyphicon-sort-by-order-alt:before { - content: "\e154"; -} -.glyphicon-sort-by-attributes:before { - content: "\e155"; -} -.glyphicon-sort-by-attributes-alt:before { - content: "\e156"; -} -.glyphicon-unchecked:before { - content: "\e157"; -} -.glyphicon-expand:before { - content: "\e158"; -} -.glyphicon-collapse-down:before { - content: "\e159"; -} -.glyphicon-collapse-up:before { - content: "\e160"; -} -.glyphicon-log-in:before { - content: "\e161"; -} -.glyphicon-flash:before { - content: "\e162"; -} -.glyphicon-log-out:before { - content: "\e163"; -} -.glyphicon-new-window:before { - content: "\e164"; -} -.glyphicon-record:before { - content: "\e165"; -} -.glyphicon-save:before { - content: "\e166"; -} -.glyphicon-open:before { - content: "\e167"; -} -.glyphicon-saved:before { - content: "\e168"; -} -.glyphicon-import:before { - content: "\e169"; -} -.glyphicon-export:before { - content: "\e170"; -} -.glyphicon-send:before { - content: "\e171"; -} -.glyphicon-floppy-disk:before { - content: "\e172"; -} -.glyphicon-floppy-saved:before { - content: "\e173"; -} -.glyphicon-floppy-remove:before { - content: "\e174"; -} -.glyphicon-floppy-save:before { - content: "\e175"; -} -.glyphicon-floppy-open:before { - content: "\e176"; -} -.glyphicon-credit-card:before { - content: "\e177"; -} -.glyphicon-transfer:before { - content: "\e178"; -} -.glyphicon-cutlery:before { - content: "\e179"; -} -.glyphicon-header:before { - content: "\e180"; -} -.glyphicon-compressed:before { - content: "\e181"; -} -.glyphicon-earphone:before { - content: "\e182"; -} -.glyphicon-phone-alt:before { - content: "\e183"; -} -.glyphicon-tower:before { - content: "\e184"; -} -.glyphicon-stats:before { - content: "\e185"; -} -.glyphicon-sd-video:before { - content: "\e186"; -} -.glyphicon-hd-video:before { - content: "\e187"; -} -.glyphicon-subtitles:before { - content: "\e188"; -} -.glyphicon-sound-stereo:before { - content: "\e189"; -} -.glyphicon-sound-dolby:before { - content: "\e190"; -} -.glyphicon-sound-5-1:before { - content: "\e191"; -} -.glyphicon-sound-6-1:before { - content: "\e192"; -} -.glyphicon-sound-7-1:before { - content: "\e193"; -} -.glyphicon-copyright-mark:before { - content: "\e194"; -} -.glyphicon-registration-mark:before { - content: "\e195"; -} -.glyphicon-cloud-download:before { - content: "\e197"; -} -.glyphicon-cloud-upload:before { - content: "\e198"; -} -.glyphicon-tree-conifer:before { - content: "\e199"; -} -.glyphicon-tree-deciduous:before { - content: "\e200"; -} - - -/*btn*/ -.btn { - display: inline-block; - margin-bottom: 0; - font-weight: normal; - text-align: center; - vertical-align: middle; - cursor: pointer; - background-image: none; - border: 1px solid transparent; - white-space: nowrap; - padding: 6px 12px; - font-size: 12px; - line-height: 1.42857143; - border-radius: 4px; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - user-select: none; -} -.btn:focus, -.btn:active:focus, -.btn.active:focus { - outline: thin dotted; - outline: 5px auto -webkit-focus-ring-color; - outline-offset: -2px; -} -.btn:hover, -.btn:focus { - color: #333333; - text-decoration: none; -} -.btn:active, -.btn.active { - outline: 0; - background-image: none; - -webkit-box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125); - box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125); -} -.btn.disabled, -.btn[disabled], -fieldset[disabled] .btn { - cursor: not-allowed; - pointer-events: none; - opacity: 0.65; - filter: alpha(opacity=65); - -webkit-box-shadow: none; - box-shadow: none; -} -.btn-default { - color: #333333; - background-color: #ffffff; - border-color: #cccccc; -} -.btn-default:hover, -.btn-default:focus, -.btn-default:active, -.btn-default.active, -.open > .dropdown-toggle.btn-default { - color: #333333; - background-color: #e6e6e6; - border-color: #adadad; -} -.btn-default:active, -.btn-default.active, -.open > .dropdown-toggle.btn-default { - background-image: none; -} -.btn-default.disabled, -.btn-default[disabled], -fieldset[disabled] .btn-default, -.btn-default.disabled:hover, -.btn-default[disabled]:hover, -fieldset[disabled] .btn-default:hover, -.btn-default.disabled:focus, -.btn-default[disabled]:focus, -fieldset[disabled] .btn-default:focus, -.btn-default.disabled:active, -.btn-default[disabled]:active, -fieldset[disabled] .btn-default:active, -.btn-default.disabled.active, -.btn-default[disabled].active, -fieldset[disabled] .btn-default.active { - background-color: #ffffff; - border-color: #cccccc; -} -.btn-default .badge { - color: #ffffff; - background-color: #333333; -} -.btn-primary { - color: #ffffff; - background-color: #428bca; - border-color: #357ebd; -} -.btn-primary:hover, -.btn-primary:focus, -.btn-primary:active, -.btn-primary.active, -.open > .dropdown-toggle.btn-primary { - color: #ffffff; - background-color: #3071a9; - border-color: #285e8e; -} -.btn-primary:active, -.btn-primary.active, -.open > .dropdown-toggle.btn-primary { - background-image: none; -} -.btn-primary.disabled, -.btn-primary[disabled], -fieldset[disabled] .btn-primary, -.btn-primary.disabled:hover, -.btn-primary[disabled]:hover, -fieldset[disabled] .btn-primary:hover, -.btn-primary.disabled:focus, -.btn-primary[disabled]:focus, -fieldset[disabled] .btn-primary:focus, -.btn-primary.disabled:active, -.btn-primary[disabled]:active, -fieldset[disabled] .btn-primary:active, -.btn-primary.disabled.active, -.btn-primary[disabled].active, -fieldset[disabled] .btn-primary.active { - background-color: #428bca; - border-color: #357ebd; -} -.btn-primary .badge { - color: #428bca; - background-color: #ffffff; -} -.btn-success { - color: #ffffff; - background-color: #5cb85c; - border-color: #4cae4c; -} -.btn-success:hover, -.btn-success:focus, -.btn-success:active, -.btn-success.active, -.open > .dropdown-toggle.btn-success { - color: #ffffff; - background-color: #449d44; - border-color: #398439; -} -.btn-success:active, -.btn-success.active, -.open > .dropdown-toggle.btn-success { - background-image: none; -} -.btn-success.disabled, -.btn-success[disabled], -fieldset[disabled] .btn-success, -.btn-success.disabled:hover, -.btn-success[disabled]:hover, -fieldset[disabled] .btn-success:hover, -.btn-success.disabled:focus, -.btn-success[disabled]:focus, -fieldset[disabled] .btn-success:focus, -.btn-success.disabled:active, -.btn-success[disabled]:active, -fieldset[disabled] .btn-success:active, -.btn-success.disabled.active, -.btn-success[disabled].active, -fieldset[disabled] .btn-success.active { - background-color: #5cb85c; - border-color: #4cae4c; -} -.btn-success .badge { - color: #5cb85c; - background-color: #ffffff; -} -.btn-info { - color: #ffffff; - background-color: #5bc0de; - border-color: #46b8da; -} -.btn-info:hover, -.btn-info:focus, -.btn-info:active, -.btn-info.active, -.open > .dropdown-toggle.btn-info { - color: #ffffff; - background-color: #31b0d5; - border-color: #269abc; -} -.btn-info:active, -.btn-info.active, -.open > .dropdown-toggle.btn-info { - background-image: none; -} -.btn-info.disabled, -.btn-info[disabled], -fieldset[disabled] .btn-info, -.btn-info.disabled:hover, -.btn-info[disabled]:hover, -fieldset[disabled] .btn-info:hover, -.btn-info.disabled:focus, -.btn-info[disabled]:focus, -fieldset[disabled] .btn-info:focus, -.btn-info.disabled:active, -.btn-info[disabled]:active, -fieldset[disabled] .btn-info:active, -.btn-info.disabled.active, -.btn-info[disabled].active, -fieldset[disabled] .btn-info.active { - background-color: #5bc0de; - border-color: #46b8da; -} -.btn-info .badge { - color: #5bc0de; - background-color: #ffffff; -} -.btn-warning { - color: #ffffff; - background-color: #f0ad4e; - border-color: #eea236; -} -.btn-warning:hover, -.btn-warning:focus, -.btn-warning:active, -.btn-warning.active, -.open > .dropdown-toggle.btn-warning { - color: #ffffff; - background-color: #ec971f; - border-color: #d58512; -} -.btn-warning:active, -.btn-warning.active, -.open > .dropdown-toggle.btn-warning { - background-image: none; -} -.btn-warning.disabled, -.btn-warning[disabled], -fieldset[disabled] .btn-warning, -.btn-warning.disabled:hover, -.btn-warning[disabled]:hover, -fieldset[disabled] .btn-warning:hover, -.btn-warning.disabled:focus, -.btn-warning[disabled]:focus, -fieldset[disabled] .btn-warning:focus, -.btn-warning.disabled:active, -.btn-warning[disabled]:active, -fieldset[disabled] .btn-warning:active, -.btn-warning.disabled.active, -.btn-warning[disabled].active, -fieldset[disabled] .btn-warning.active { - background-color: #f0ad4e; - border-color: #eea236; -} -.btn-warning .badge { - color: #f0ad4e; - background-color: #ffffff; -} -.btn-danger { - color: #ffffff; - background-color: #d9534f; - border-color: #d43f3a; -} -.btn-danger:hover, -.btn-danger:focus, -.btn-danger:active, -.btn-danger.active, -.open > .dropdown-toggle.btn-danger { - color: #ffffff; - background-color: #c9302c; - border-color: #ac2925; -} -.btn-danger:active, -.btn-danger.active, -.open > .dropdown-toggle.btn-danger { - background-image: none; -} -.btn-danger.disabled, -.btn-danger[disabled], -fieldset[disabled] .btn-danger, -.btn-danger.disabled:hover, -.btn-danger[disabled]:hover, -fieldset[disabled] .btn-danger:hover, -.btn-danger.disabled:focus, -.btn-danger[disabled]:focus, -fieldset[disabled] .btn-danger:focus, -.btn-danger.disabled:active, -.btn-danger[disabled]:active, -fieldset[disabled] .btn-danger:active, -.btn-danger.disabled.active, -.btn-danger[disabled].active, -fieldset[disabled] .btn-danger.active { - background-color: #d9534f; - border-color: #d43f3a; -} -.btn-danger .badge { - color: #d9534f; - background-color: #ffffff; -} -.btn-link { - color: #0088cc; - font-weight: normal; - cursor: pointer; - border-radius: 0; -} -.btn-link, -.btn-link:active, -.btn-link[disabled], -fieldset[disabled] .btn-link { - background-color: transparent; - -webkit-box-shadow: none; - box-shadow: none; -} -.btn-link, -.btn-link:hover, -.btn-link:focus, -.btn-link:active { - border-color: transparent; -} -.btn-link:hover, -.btn-link:focus { - color: #0088cc; - text-decoration: underline; - background-color: transparent; -} -.btn-link[disabled]:hover, -fieldset[disabled] .btn-link:hover, -.btn-link[disabled]:focus, -fieldset[disabled] .btn-link:focus { - color: #777777; - text-decoration: none; -} -.btn-lg { - padding: 10px 16px; - font-size: 15px; - line-height: 1.33; - border-radius: 6px; -} -.btn-sm { - padding: 5px 10px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -.btn-xs { - padding: 1px 5px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -.btn-block { - display: block; - width: 100%; -} -.btn-block + .btn-block { - margin-top: 5px; -} -input[type="submit"].btn-block, -input[type="reset"].btn-block, -input[type="button"].btn-block { - width: 100%; -} - -.img-responsive { - display: block; - width: 100% \9; - max-width: 100%; - height: auto; -} -.img-rounded { - border-radius: 6px; -} -.img-thumbnail { - padding: 4px; - line-height: 1.42857143; - background-color: #ffffff; - border: 1px solid #dddddd; - border-radius: 0; - -webkit-transition: all 0.2s ease-in-out; - -o-transition: all 0.2s ease-in-out; - transition: all 0.2s ease-in-out; - display: inline-block; - width: 100% \9; - max-width: 100%; - height: auto; -} -.img-circle { - border-radius: 50%; -} - - - -.row { - margin-left: -15px; - margin-right: -15px; -} -.col-xs-1, .col-sm-1, .col-md-1, .col-lg-1, .col-xs-2, .col-sm-2, .col-md-2, .col-lg-2, .col-xs-3, .col-sm-3, .col-md-3, .col-lg-3, .col-xs-4, .col-sm-4, .col-md-4, .col-lg-4, .col-xs-5, .col-sm-5, .col-md-5, .col-lg-5, .col-xs-6, .col-sm-6, .col-md-6, .col-lg-6, .col-xs-7, .col-sm-7, .col-md-7, .col-lg-7, .col-xs-8, .col-sm-8, .col-md-8, .col-lg-8, .col-xs-9, .col-sm-9, .col-md-9, .col-lg-9, .col-xs-10, .col-sm-10, .col-md-10, .col-lg-10, .col-xs-11, .col-sm-11, .col-md-11, .col-lg-11, .col-xs-12, .col-sm-12, .col-md-12, .col-lg-12 { - position: relative; - min-height: 1px; - padding-left: 15px; - padding-right: 15px; -} -.col-xs-1, .col-xs-2, .col-xs-3, .col-xs-4, .col-xs-5, .col-xs-6, .col-xs-7, .col-xs-8, .col-xs-9, .col-xs-10, .col-xs-11, .col-xs-12 { - float: left; -} -.col-xs-12 { - width: 100%; -} -.col-xs-11 { - width: 91.66666667%; -} -.col-xs-10 { - width: 83.33333333%; -} -.col-xs-9 { - width: 75%; -} -.col-xs-8 { - width: 66.66666667%; -} -.col-xs-7 { - width: 58.33333333%; -} -.col-xs-6 { - width: 50%; -} -.col-xs-5 { - width: 41.66666667%; -} -.col-xs-4 { - width: 33.33333333%; -} -.col-xs-3 { - width: 25%; -} -.col-xs-2 { - width: 16.66666667%; -} -.col-xs-1 { - width: 8.33333333%; -} -.col-xs-pull-12 { - right: 100%; -} -.col-xs-pull-11 { - right: 91.66666667%; -} -.col-xs-pull-10 { - right: 83.33333333%; -} -.col-xs-pull-9 { - right: 75%; -} -.col-xs-pull-8 { - right: 66.66666667%; -} -.col-xs-pull-7 { - right: 58.33333333%; -} -.col-xs-pull-6 { - right: 50%; -} -.col-xs-pull-5 { - right: 41.66666667%; -} -.col-xs-pull-4 { - right: 33.33333333%; -} -.col-xs-pull-3 { - right: 25%; -} -.col-xs-pull-2 { - right: 16.66666667%; -} -.col-xs-pull-1 { - right: 8.33333333%; -} -.col-xs-pull-0 { - right: auto; -} -.col-xs-push-12 { - left: 100%; -} -.col-xs-push-11 { - left: 91.66666667%; -} -.col-xs-push-10 { - left: 83.33333333%; -} -.col-xs-push-9 { - left: 75%; -} -.col-xs-push-8 { - left: 66.66666667%; -} -.col-xs-push-7 { - left: 58.33333333%; -} -.col-xs-push-6 { - left: 50%; -} -.col-xs-push-5 { - left: 41.66666667%; -} -.col-xs-push-4 { - left: 33.33333333%; -} -.col-xs-push-3 { - left: 25%; -} -.col-xs-push-2 { - left: 16.66666667%; -} -.col-xs-push-1 { - left: 8.33333333%; -} -.col-xs-push-0 { - left: auto; -} -.col-xs-offset-12 { - margin-left: 100%; -} -.col-xs-offset-11 { - margin-left: 91.66666667%; -} -.col-xs-offset-10 { - margin-left: 83.33333333%; -} -.col-xs-offset-9 { - margin-left: 75%; -} -.col-xs-offset-8 { - margin-left: 66.66666667%; -} -.col-xs-offset-7 { - margin-left: 58.33333333%; -} -.col-xs-offset-6 { - margin-left: 50%; -} -.col-xs-offset-5 { - margin-left: 41.66666667%; -} -.col-xs-offset-4 { - margin-left: 33.33333333%; -} -.col-xs-offset-3 { - margin-left: 25%; -} -.col-xs-offset-2 { - margin-left: 16.66666667%; -} -.col-xs-offset-1 { - margin-left: 8.33333333%; -} -.col-xs-offset-0 { - margin-left: 0%; -} -@media (min-width: 768px) { - .col-sm-1, .col-sm-2, .col-sm-3, .col-sm-4, .col-sm-5, .col-sm-6, .col-sm-7, .col-sm-8, .col-sm-9, .col-sm-10, .col-sm-11, .col-sm-12 { - float: left; - } - .col-sm-12 { - width: 100%; - } - .col-sm-11 { - width: 91.66666667%; - } - .col-sm-10 { - width: 83.33333333%; - } - .col-sm-9 { - width: 75%; - } - .col-sm-8 { - width: 66.66666667%; - } - .col-sm-7 { - width: 58.33333333%; - } - .col-sm-6 { - width: 50%; - } - .col-sm-5 { - width: 41.66666667%; - } - .col-sm-4 { - width: 33.33333333%; - } - .col-sm-3 { - width: 25%; - } - .col-sm-2 { - width: 16.66666667%; - } - .col-sm-1 { - width: 8.33333333%; - } - .col-sm-pull-12 { - right: 100%; - } - .col-sm-pull-11 { - right: 91.66666667%; - } - .col-sm-pull-10 { - right: 83.33333333%; - } - .col-sm-pull-9 { - right: 75%; - } - .col-sm-pull-8 { - right: 66.66666667%; - } - .col-sm-pull-7 { - right: 58.33333333%; - } - .col-sm-pull-6 { - right: 50%; - } - .col-sm-pull-5 { - right: 41.66666667%; - } - .col-sm-pull-4 { - right: 33.33333333%; - } - .col-sm-pull-3 { - right: 25%; - } - .col-sm-pull-2 { - right: 16.66666667%; - } - .col-sm-pull-1 { - right: 8.33333333%; - } - .col-sm-pull-0 { - right: auto; - } - .col-sm-push-12 { - left: 100%; - } - .col-sm-push-11 { - left: 91.66666667%; - } - .col-sm-push-10 { - left: 83.33333333%; - } - .col-sm-push-9 { - left: 75%; - } - .col-sm-push-8 { - left: 66.66666667%; - } - .col-sm-push-7 { - left: 58.33333333%; - } - .col-sm-push-6 { - left: 50%; - } - .col-sm-push-5 { - left: 41.66666667%; - } - .col-sm-push-4 { - left: 33.33333333%; - } - .col-sm-push-3 { - left: 25%; - } - .col-sm-push-2 { - left: 16.66666667%; - } - .col-sm-push-1 { - left: 8.33333333%; - } - .col-sm-push-0 { - left: auto; - } - .col-sm-offset-12 { - margin-left: 100%; - } - .col-sm-offset-11 { - margin-left: 91.66666667%; - } - .col-sm-offset-10 { - margin-left: 83.33333333%; - } - .col-sm-offset-9 { - margin-left: 75%; - } - .col-sm-offset-8 { - margin-left: 66.66666667%; - } - .col-sm-offset-7 { - margin-left: 58.33333333%; - } - .col-sm-offset-6 { - margin-left: 50%; - } - .col-sm-offset-5 { - margin-left: 41.66666667%; - } - .col-sm-offset-4 { - margin-left: 33.33333333%; - } - .col-sm-offset-3 { - margin-left: 25%; - } - .col-sm-offset-2 { - margin-left: 16.66666667%; - } - .col-sm-offset-1 { - margin-left: 8.33333333%; - } - .col-sm-offset-0 { - margin-left: 0%; - } -} -@media (min-width: 992px) { - .col-md-1, .col-md-2, .col-md-3, .col-md-4, .col-md-5, .col-md-6, .col-md-7, .col-md-8, .col-md-9, .col-md-10, .col-md-11, .col-md-12 { - float: left; - } - .col-md-12 { - width: 100%; - } - .col-md-11 { - width: 91.66666667%; - } - .col-md-10 { - width: 83.33333333%; - } - .col-md-9 { - width: 75%; - } - .col-md-8 { - width: 66.66666667%; - } - .col-md-7 { - width: 58.33333333%; - } - .col-md-6 { - width: 50%; - } - .col-md-5 { - width: 41.66666667%; - } - .col-md-4 { - width: 33.33333333%; - } - .col-md-3 { - width: 25%; - } - .col-md-2 { - width: 16.66666667%; - } - .col-md-1 { - width: 8.33333333%; - } - .col-md-pull-12 { - right: 100%; - } - .col-md-pull-11 { - right: 91.66666667%; - } - .col-md-pull-10 { - right: 83.33333333%; - } - .col-md-pull-9 { - right: 75%; - } - .col-md-pull-8 { - right: 66.66666667%; - } - .col-md-pull-7 { - right: 58.33333333%; - } - .col-md-pull-6 { - right: 50%; - } - .col-md-pull-5 { - right: 41.66666667%; - } - .col-md-pull-4 { - right: 33.33333333%; - } - .col-md-pull-3 { - right: 25%; - } - .col-md-pull-2 { - right: 16.66666667%; - } - .col-md-pull-1 { - right: 8.33333333%; - } - .col-md-pull-0 { - right: auto; - } - .col-md-push-12 { - left: 100%; - } - .col-md-push-11 { - left: 91.66666667%; - } - .col-md-push-10 { - left: 83.33333333%; - } - .col-md-push-9 { - left: 75%; - } - .col-md-push-8 { - left: 66.66666667%; - } - .col-md-push-7 { - left: 58.33333333%; - } - .col-md-push-6 { - left: 50%; - } - .col-md-push-5 { - left: 41.66666667%; - } - .col-md-push-4 { - left: 33.33333333%; - } - .col-md-push-3 { - left: 25%; - } - .col-md-push-2 { - left: 16.66666667%; - } - .col-md-push-1 { - left: 8.33333333%; - } - .col-md-push-0 { - left: auto; - } - .col-md-offset-12 { - margin-left: 100%; - } - .col-md-offset-11 { - margin-left: 91.66666667%; - } - .col-md-offset-10 { - margin-left: 83.33333333%; - } - .col-md-offset-9 { - margin-left: 75%; - } - .col-md-offset-8 { - margin-left: 66.66666667%; - } - .col-md-offset-7 { - margin-left: 58.33333333%; - } - .col-md-offset-6 { - margin-left: 50%; - } - .col-md-offset-5 { - margin-left: 41.66666667%; - } - .col-md-offset-4 { - margin-left: 33.33333333%; - } - .col-md-offset-3 { - margin-left: 25%; - } - .col-md-offset-2 { - margin-left: 16.66666667%; - } - .col-md-offset-1 { - margin-left: 8.33333333%; - } - .col-md-offset-0 { - margin-left: 0%; - } -} -@media (min-width: 1200px) { - .col-lg-1, .col-lg-2, .col-lg-3, .col-lg-4, .col-lg-5, .col-lg-6, .col-lg-7, .col-lg-8, .col-lg-9, .col-lg-10, .col-lg-11, .col-lg-12 { - float: left; - } - .col-lg-12 { - width: 100%; - } - .col-lg-11 { - width: 91.66666667%; - } - .col-lg-10 { - width: 83.33333333%; - } - .col-lg-9 { - width: 75%; - } - .col-lg-8 { - width: 66.66666667%; - } - .col-lg-7 { - width: 58.33333333%; - } - .col-lg-6 { - width: 50%; - } - .col-lg-5 { - width: 41.66666667%; - } - .col-lg-4 { - width: 33.33333333%; - } - .col-lg-3 { - width: 25%; - } - .col-lg-2 { - width: 16.66666667%; - } - .col-lg-1 { - width: 8.33333333%; - } - .col-lg-pull-12 { - right: 100%; - } - .col-lg-pull-11 { - right: 91.66666667%; - } - .col-lg-pull-10 { - right: 83.33333333%; - } - .col-lg-pull-9 { - right: 75%; - } - .col-lg-pull-8 { - right: 66.66666667%; - } - .col-lg-pull-7 { - right: 58.33333333%; - } - .col-lg-pull-6 { - right: 50%; - } - .col-lg-pull-5 { - right: 41.66666667%; - } - .col-lg-pull-4 { - right: 33.33333333%; - } - .col-lg-pull-3 { - right: 25%; - } - .col-lg-pull-2 { - right: 16.66666667%; - } - .col-lg-pull-1 { - right: 8.33333333%; - } - .col-lg-pull-0 { - right: auto; - } - .col-lg-push-12 { - left: 100%; - } - .col-lg-push-11 { - left: 91.66666667%; - } - .col-lg-push-10 { - left: 83.33333333%; - } - .col-lg-push-9 { - left: 75%; - } - .col-lg-push-8 { - left: 66.66666667%; - } - .col-lg-push-7 { - left: 58.33333333%; - } - .col-lg-push-6 { - left: 50%; - } - .col-lg-push-5 { - left: 41.66666667%; - } - .col-lg-push-4 { - left: 33.33333333%; - } - .col-lg-push-3 { - left: 25%; - } - .col-lg-push-2 { - left: 16.66666667%; - } - .col-lg-push-1 { - left: 8.33333333%; - } - .col-lg-push-0 { - left: auto; - } - .col-lg-offset-12 { - margin-left: 100%; - } - .col-lg-offset-11 { - margin-left: 91.66666667%; - } - .col-lg-offset-10 { - margin-left: 83.33333333%; - } - .col-lg-offset-9 { - margin-left: 75%; - } - .col-lg-offset-8 { - margin-left: 66.66666667%; - } - .col-lg-offset-7 { - margin-left: 58.33333333%; - } - .col-lg-offset-6 { - margin-left: 50%; - } - .col-lg-offset-5 { - margin-left: 41.66666667%; - } - .col-lg-offset-4 { - margin-left: 33.33333333%; - } - .col-lg-offset-3 { - margin-left: 25%; - } - .col-lg-offset-2 { - margin-left: 16.66666667%; - } - .col-lg-offset-1 { - margin-left: 8.33333333%; - } - .col-lg-offset-0 { - margin-left: 0%; - } -} - - - - -.form-control { - display: block; - width: 100%; - height: 31px; - padding: 6px 12px; - font-size: 12px; - line-height: 1.42857143; - color: #555555; - background-color: #ffffff; - background-image: none; - border: 1px solid #cccccc; - border-radius: 0; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - -webkit-transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; - -o-transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; - transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; -} -.form-control:focus { - border-color: #66afe9; - outline: 0; - -webkit-box-shadow: inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6); - box-shadow: inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6); -} -.form-control::-moz-placeholder { - color: #777777; - opacity: 1; -} -.form-control:-ms-input-placeholder { - color: #777777; -} -.form-control::-webkit-input-placeholder { - color: #777777; -} -.form-control[disabled], -.form-control[readonly], -fieldset[disabled] .form-control { - cursor: not-allowed; - background-color: #eeeeee; - opacity: 1; -} -textarea.form-control { - height: auto; -} -input[type="search"] { - -webkit-appearance: none; -} -input[type="date"], -input[type="time"], -input[type="datetime-local"], -input[type="month"] { - line-height: 31px; - line-height: 1.42857143 \0; -} -input[type="date"].input-sm, -input[type="time"].input-sm, -input[type="datetime-local"].input-sm, -input[type="month"].input-sm { - line-height: 28px; -} -input[type="date"].input-lg, -input[type="time"].input-lg, -input[type="datetime-local"].input-lg, -input[type="month"].input-lg { - line-height: 42px; -} -.form-group { - margin-bottom: 15px; -} -.radio, -.checkbox { - position: relative; - display: block; - min-height: 17px; - margin-top: 10px; - margin-bottom: 10px; -} -.radio label, -.checkbox label { - padding-left: 20px; - margin-bottom: 0; - font-weight: normal; - cursor: pointer; -} -.radio input[type="radio"], -.radio-inline input[type="radio"], -.checkbox input[type="checkbox"], -.checkbox-inline input[type="checkbox"] { - position: absolute; - margin-left: -20px; - margin-top: 4px \9; -} -.radio + .radio, -.checkbox + .checkbox { - margin-top: -5px; -} -.radio-inline, -.checkbox-inline { - display: inline-block; - padding-left: 20px; - margin-bottom: 0; - vertical-align: middle; - font-weight: normal; - cursor: pointer; -} -.radio-inline + .radio-inline, -.checkbox-inline + .checkbox-inline { - margin-top: 0; - margin-left: 10px; -} -input[type="radio"][disabled], -input[type="checkbox"][disabled], -input[type="radio"].disabled, -input[type="checkbox"].disabled, -fieldset[disabled] input[type="radio"], -fieldset[disabled] input[type="checkbox"] { - cursor: not-allowed; -} -.radio-inline.disabled, -.checkbox-inline.disabled, -fieldset[disabled] .radio-inline, -fieldset[disabled] .checkbox-inline { - cursor: not-allowed; -} -.radio.disabled label, -.checkbox.disabled label, -fieldset[disabled] .radio label, -fieldset[disabled] .checkbox label { - cursor: not-allowed; -} -.form-control-static { - padding-top: 7px; - padding-bottom: 7px; - margin-bottom: 0; -} -.form-control-static.input-lg, -.form-control-static.input-sm { - padding-left: 0; - padding-right: 0; -} -.input-sm, -.form-horizontal .form-group-sm .form-control { - height: 28px; - padding: 5px 10px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -select.input-sm { - height: 28px; - line-height: 28px; -} -textarea.input-sm, -select[multiple].input-sm { - height: auto; -} -.input-lg, -.form-horizontal .form-group-lg .form-control { - height: 42px; - padding: 10px 16px; - font-size: 15px; - line-height: 1.33; - border-radius: 6px; -} -select.input-lg { - height: 42px; - line-height: 42px; -} -textarea.input-lg, -select[multiple].input-lg { - height: auto; -} -.has-feedback { - position: relative; -} -.has-feedback .form-control { - padding-right: 38.75px; -} -.form-control-feedback { - position: absolute; - top: 22px; - right: 0; - z-index: 2; - display: block; - width: 31px; - height: 31px; - line-height: 31px; - text-align: center; -} -.input-lg + .form-control-feedback { - width: 42px; - height: 42px; - line-height: 42px; -} -.input-sm + .form-control-feedback { - width: 28px; - height: 28px; - line-height: 28px; -} -.has-success .help-block, -.has-success .control-label, -.has-success .radio, -.has-success .checkbox, -.has-success .radio-inline, -.has-success .checkbox-inline { - color: #3c763d; -} -.has-success .form-control { - border-color: #3c763d; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-success .form-control:focus { - border-color: #2b542c; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #67b168; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #67b168; -} -.has-success .input-group-addon { - color: #3c763d; - border-color: #3c763d; - background-color: #dff0d8; -} -.has-success .form-control-feedback { - color: #3c763d; -} -.has-warning .help-block, -.has-warning .control-label, -.has-warning .radio, -.has-warning .checkbox, -.has-warning .radio-inline, -.has-warning .checkbox-inline { - color: #8a6d3b; -} -.has-warning .form-control { - border-color: #8a6d3b; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-warning .form-control:focus { - border-color: #66512c; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #c0a16b; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #c0a16b; -} -.has-warning .input-group-addon { - color: #8a6d3b; - border-color: #8a6d3b; - background-color: #fcf8e3; -} -.has-warning .form-control-feedback { - color: #8a6d3b; -} -.has-error .help-block, -.has-error .control-label, -.has-error .radio, -.has-error .checkbox, -.has-error .radio-inline, -.has-error .checkbox-inline { - color: #a94442; -} -.has-error .form-control { - border-color: #a94442; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-error .form-control:focus { - border-color: #843534; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #ce8483; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #ce8483; -} -.has-error .input-group-addon { - color: #a94442; - border-color: #a94442; - background-color: #f2dede; -} -.has-error .form-control-feedback { - color: #a94442; -} -.has-feedback label.sr-only ~ .form-control-feedback { - top: 0; -} -.help-block { - display: block; - margin-top: 5px; - margin-bottom: 10px; - color: #737373; -} -@media (min-width: 768px) { - .form-inline .form-group { - display: inline-block; - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .form-control { - display: inline-block; - width: auto; - vertical-align: middle; - } - .form-inline .input-group { - display: inline-table; - vertical-align: middle; - } - .form-inline .input-group .input-group-addon, - .form-inline .input-group .input-group-btn, - .form-inline .input-group .form-control { - width: auto; - } - .form-inline .input-group > .form-control { - width: 100%; - } - .form-inline .control-label { - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .radio, - .form-inline .checkbox { - display: inline-block; - margin-top: 0; - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .radio label, - .form-inline .checkbox label { - padding-left: 0; - } - .form-inline .radio input[type="radio"], - .form-inline .checkbox input[type="checkbox"] { - position: relative; - margin-left: 0; - } - .form-inline .has-feedback .form-control-feedback { - top: 0; - } -} -.form-horizontal .radio, -.form-horizontal .checkbox, -.form-horizontal .radio-inline, -.form-horizontal .checkbox-inline { - margin-top: 0; - margin-bottom: 0; - padding-top: 7px; -} -.form-horizontal .radio, -.form-horizontal .checkbox { - min-height: 24px; -} -.form-horizontal .form-group { - margin-left: -15px; - margin-right: -15px; -} -@media (min-width: 768px) { - .form-horizontal .control-label { - text-align: right; - margin-bottom: 0; - padding-top: 7px; - } -} -.form-horizontal .has-feedback .form-control-feedback { - top: 0; - right: 15px; -} -@media (min-width: 768px) { - .form-horizontal .form-group-lg .control-label { - padding-top: 14.3px; - } -} -@media (min-width: 768px) { - .form-horizontal .form-group-sm .control-label { - padding-top: 6px; - } -} - -.tooltip { - position: absolute; - z-index: 1070; - display: block; - visibility: visible; - font-size: 11px; - line-height: 1.4; - opacity: 0; - filter: alpha(opacity=0); -} -.tooltip.in { - opacity: 0.9; - filter: alpha(opacity=90); -} -.tooltip.top { - margin-top: -3px; - padding: 5px 0; -} -.tooltip.right { - margin-left: 3px; - padding: 0 5px; -} -.tooltip.bottom { - margin-top: 3px; - padding: 5px 0; -} -.tooltip.left { - margin-left: -3px; - padding: 0 5px; -} -.tooltip-inner { - max-width: 200px; - padding: 3px 8px; - color: #ffffff; - text-align: center; - text-decoration: none; - background-color: #000000; - border-radius: 4px; -} -.tooltip-arrow { - position: absolute; - width: 0; - height: 0; - border-color: transparent; - border-style: solid; -} -.tooltip.top .tooltip-arrow { - bottom: 0; - left: 50%; - margin-left: -5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.top-left .tooltip-arrow { - bottom: 0; - left: 5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.top-right .tooltip-arrow { - bottom: 0; - right: 5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.right .tooltip-arrow { - top: 50%; - left: 0; - margin-top: -5px; - border-width: 5px 5px 5px 0; - border-right-color: #000000; -} -.tooltip.left .tooltip-arrow { - top: 50%; - right: 0; - margin-top: -5px; - border-width: 5px 0 5px 5px; - border-left-color: #000000; -} -.tooltip.bottom .tooltip-arrow { - top: 0; - left: 50%; - margin-left: -5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} -.tooltip.bottom-left .tooltip-arrow { - top: 0; - left: 5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} -.tooltip.bottom-right .tooltip-arrow { - top: 0; - right: 5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} - -.modal-open { - overflow: hidden; -} -.modal { - display: none; - overflow: hidden; - position: fixed; - top: 0; - right: 0; - bottom: 0; - left: 0; - z-index: 1050; - -webkit-overflow-scrolling: touch; - outline: 0; -} -.modal.fade .modal-dialog { - -webkit-transform: translate3d(0, -25%, 0); - transform: translate3d(0, -25%, 0); - -webkit-transition: -webkit-transform 0.3s ease-out; - -moz-transition: -moz-transform 0.3s ease-out; - -o-transition: -o-transform 0.3s ease-out; - transition: transform 0.3s ease-out; -} -.modal.in .modal-dialog { - -webkit-transform: translate3d(0, 0, 0); - transform: translate3d(0, 0, 0); -} -.modal-open .modal { - overflow-x: hidden; - overflow-y: auto; -} -.modal-dialog { - position: relative; - width: auto; - margin: 10px; -} -.modal-content { - position: relative; - background-color: #ffffff; - border: 1px solid #999999; - border: 1px solid rgba(0, 0, 0, 0.2); - border-radius: 6px; - -webkit-box-shadow: 0 3px 9px rgba(0, 0, 0, 0.5); - box-shadow: 0 3px 9px rgba(0, 0, 0, 0.5); - background-clip: padding-box; - outline: 0; -} -.modal-backdrop { - position: fixed; - top: 0; - right: 0; - bottom: 0; - left: 0; - z-index: 1040; - background-color: #000000; -} -.modal-backdrop.fade { - opacity: 0; - filter: alpha(opacity=0); -} -.modal-backdrop.in { - opacity: 0.5; - filter: alpha(opacity=50); -} -.modal-header { - padding: 15px; - border-bottom: 1px solid #e5e5e5; - min-height: 16.42857143px; -} -.modal-header .close { - margin-top: -2px; -} -.modal-title { - margin: 0; - line-height: 1.42857143; -} -.modal-body { - position: relative; - padding: 15px; -} -.modal-footer { - padding: 15px; - text-align: right; - border-top: 1px solid #e5e5e5; -} -.modal-footer .btn + .btn { - margin-left: 5px; - margin-bottom: 0; -} -.modal-footer .btn-group .btn + .btn { - margin-left: -1px; -} -.modal-footer .btn-block + .btn-block { - margin-left: 0; -} -.modal-scrollbar-measure { - position: absolute; - top: -9999px; - width: 50px; - height: 50px; - overflow: scroll; -} -@media (min-width: 768px) { - .modal-dialog { - width: 600px; - margin: 30px auto; - } - .modal-content { - -webkit-box-shadow: 0 5px 15px rgba(0, 0, 0, 0.5); - box-shadow: 0 5px 15px rgba(0, 0, 0, 0.5); - } - .modal-sm { - width: 300px; - } -} -@media (min-width: 992px) { - .modal-lg { - width: 900px; - } -} - -.modal-footer:before, -.modal-footer:after { - content: " "; - display: table; -} -.navbar-collapse:after, -.modal-footer:after { - clear: both; -} - - -.alert { - padding: 15px; - margin-bottom: 17px; - border: 1px solid transparent; - border-radius: 0; -} -.alert h4 { - margin-top: 0; - color: inherit; -} -.alert .alert-link { - font-weight: bold; -} -.alert > p, -.alert > ul { - margin-bottom: 0; -} -.alert > p + p { - margin-top: 5px; -} -.alert-dismissable, -.alert-dismissible { - padding-right: 35px; -} -.alert-dismissable .close, -.alert-dismissible .close { - position: relative; - top: -2px; - right: -21px; - color: inherit; -} -.alert-success { - background-color: #dff0d8; - border-color: #d6e9c6; - color: #3c763d; -} -.alert-success hr { - border-top-color: #c9e2b3; -} -.alert-success .alert-link { - color: #2b542c; -} -.alert-info { - background-color: #d9edf7; - border-color: #bce8f1; - color: #31708f; -} -.alert-info hr { - border-top-color: #a6e1ec; -} -.alert-info .alert-link { - color: #245269; -} -.alert-warning { - background-color: #fcf8e3; - border-color: #faebcc; - color: #8a6d3b; -} -.alert-warning hr { - border-top-color: #f7e1b5; -} -.alert-warning .alert-link { - color: #66512c; -} -.alert-danger { - background-color: #f2dede; - border-color: #ebccd1; - color: #a94442; -} -.alert-danger hr { - border-top-color: #e4b9c0; -} - -.well { - min-height: 20px; - padding: 19px; - margin-bottom: 20px; - background-color: #f5f5f5; - border: 1px solid #e3e3e3; - border-radius: 4px; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); -} -.well blockquote { - border-color: #ddd; - border-color: rgba(0, 0, 0, 0.15); -} -.well-lg { - padding: 24px; - border-radius: 6px; -} -.well-sm { - padding: 9px; - border-radius: 3px; -} -.close { - float: right; - font-size: 18px; - font-weight: bold; - line-height: 1; - color: #000000; - text-shadow: 0 1px 0 #ffffff; - opacity: 0.2; - filter: alpha(opacity=20); -} -.close:hover, -.close:focus { - color: #000000; - text-decoration: none; - cursor: pointer; - opacity: 0.5; - filter: alpha(opacity=50); -} -button.close { - padding: 0; - cursor: pointer; - background: transparent; - border: 0; - -webkit-appearance: none; -} - - -/* Manually added pager */ -.pagination { - display: inline-block; - padding-left: 0; - margin: 20px 0; - border-radius: 4px; -} -.pagination > li { - display: inline; -} -.pagination > li > a, -.pagination > li > span { - position: relative; - float: left; - padding: 6px 12px; - line-height: 1.42857143; - text-decoration: none; - color: #337ab7; - background-color: #ffffff; - border: 1px solid #dddddd; - margin-left: -1px; -} -.pagination > li:first-child > a, -.pagination > li:first-child > span { - margin-left: 0; - border-bottom-left-radius: 4px; - border-top-left-radius: 4px; -} -.pagination > li:last-child > a, -.pagination > li:last-child > span { - border-bottom-right-radius: 4px; - border-top-right-radius: 4px; -} -.pagination > li > a:hover, -.pagination > li > span:hover, -.pagination > li > a:focus, -.pagination > li > span:focus { - z-index: 2; - color: #23527c; - background-color: #eeeeee; - border-color: #dddddd; -} -.pagination > .active > a, -.pagination > .active > span, -.pagination > .active > a:hover, -.pagination > .active > span:hover, -.pagination > .active > a:focus, -.pagination > .active > span:focus { - z-index: 3; - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; - cursor: default; -} -.pagination > .disabled > span, -.pagination > .disabled > span:hover, -.pagination > .disabled > span:focus, -.pagination > .disabled > a, -.pagination > .disabled > a:hover, -.pagination > .disabled > a:focus { - color: #777777; - background-color: #ffffff; - border-color: #dddddd; - cursor: not-allowed; -} -.pagination-lg > li > a, -.pagination-lg > li > span { - padding: 10px 16px; - font-size: 18px; - line-height: 1.3333333; -} -.pagination-lg > li:first-child > a, -.pagination-lg > li:first-child > span { - border-bottom-left-radius: 6px; - border-top-left-radius: 6px; -} -.pagination-lg > li:last-child > a, -.pagination-lg > li:last-child > span { - border-bottom-right-radius: 6px; - border-top-right-radius: 6px; -} -.pagination-sm > li > a, -.pagination-sm > li > span { - padding: 5px 10px; - font-size: 12px; - line-height: 1.5; -} -.pagination-sm > li:first-child > a, -.pagination-sm > li:first-child > span { - border-bottom-left-radius: 3px; - border-top-left-radius: 3px; -} -.pagination-sm > li:last-child > a, -.pagination-sm > li:last-child > span { - border-bottom-right-radius: 3px; - border-top-right-radius: 3px; -} -.pager { - padding-left: 0; - margin: 20px 0; - list-style: none; - text-align: center; -} -.pager li { - display: inline; -} -.pager li > a, -.pager li > span { - display: inline-block; - padding: 5px 14px; - background-color: #ffffff; - border: 1px solid #dddddd; - border-radius: 15px; -} -.pager li > a:hover, -.pager li > a:focus { - text-decoration: none; - background-color: #eeeeee; -} -.pager .next > a, -.pager .next > span { - float: right; -} -.pager .previous > a, -.pager .previous > span { - float: left; -} -.pager .disabled > a, -.pager .disabled > a:hover, -.pager .disabled > a:focus, -.pager .disabled > span { - color: #777777; - background-color: #ffffff; - cursor: not-allowed; -} -.pager:before, -.pager:after { - content: " "; - display: table; -} -.pager:after { - clear: both; -} - -/* List and panel */ -.list-group { - margin-bottom: 20px; - padding-left: 0; -} -.list-group-item { - position: relative; - display: block; - padding: 10px 15px; - margin-bottom: -1px; - background-color: #ffffff; - border: 1px solid #dddddd; -} -.list-group-item:first-child { - border-top-right-radius: 4px; - border-top-left-radius: 4px; -} -.list-group-item:last-child { - margin-bottom: 0; - border-bottom-right-radius: 4px; - border-bottom-left-radius: 4px; -} -a.list-group-item, -button.list-group-item { - color: #555555; -} -a.list-group-item .list-group-item-heading, -button.list-group-item .list-group-item-heading { - color: #333333; -} -a.list-group-item:hover, -button.list-group-item:hover, -a.list-group-item:focus, -button.list-group-item:focus { - text-decoration: none; - color: #555555; - background-color: #f5f5f5; -} -button.list-group-item { - width: 100%; - text-align: left; -} -.list-group-item.disabled, -.list-group-item.disabled:hover, -.list-group-item.disabled:focus { - background-color: #eeeeee; - color: #777777; - cursor: not-allowed; -} -.list-group-item.disabled .list-group-item-heading, -.list-group-item.disabled:hover .list-group-item-heading, -.list-group-item.disabled:focus .list-group-item-heading { - color: inherit; -} -.list-group-item.disabled .list-group-item-text, -.list-group-item.disabled:hover .list-group-item-text, -.list-group-item.disabled:focus .list-group-item-text { - color: #777777; -} -.list-group-item.active, -.list-group-item.active:hover, -.list-group-item.active:focus { - z-index: 2; - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; -} -.list-group-item.active .list-group-item-heading, -.list-group-item.active:hover .list-group-item-heading, -.list-group-item.active:focus .list-group-item-heading, -.list-group-item.active .list-group-item-heading > small, -.list-group-item.active:hover .list-group-item-heading > small, -.list-group-item.active:focus .list-group-item-heading > small, -.list-group-item.active .list-group-item-heading > .small, -.list-group-item.active:hover .list-group-item-heading > .small, -.list-group-item.active:focus .list-group-item-heading > .small { - color: inherit; -} -.list-group-item.active .list-group-item-text, -.list-group-item.active:hover .list-group-item-text, -.list-group-item.active:focus .list-group-item-text { - color: #c7ddef; -} -.list-group-item-success { - color: #3c763d; - background-color: #dff0d8; -} -a.list-group-item-success, -button.list-group-item-success { - color: #3c763d; -} -a.list-group-item-success .list-group-item-heading, -button.list-group-item-success .list-group-item-heading { - color: inherit; -} -a.list-group-item-success:hover, -button.list-group-item-success:hover, -a.list-group-item-success:focus, -button.list-group-item-success:focus { - color: #3c763d; - background-color: #d0e9c6; -} -a.list-group-item-success.active, -button.list-group-item-success.active, -a.list-group-item-success.active:hover, -button.list-group-item-success.active:hover, -a.list-group-item-success.active:focus, -button.list-group-item-success.active:focus { - color: #fff; - background-color: #3c763d; - border-color: #3c763d; -} -.list-group-item-info { - color: #31708f; - background-color: #d9edf7; -} -a.list-group-item-info, -button.list-group-item-info { - color: #31708f; -} -a.list-group-item-info .list-group-item-heading, -button.list-group-item-info .list-group-item-heading { - color: inherit; -} -a.list-group-item-info:hover, -button.list-group-item-info:hover, -a.list-group-item-info:focus, -button.list-group-item-info:focus { - color: #31708f; - background-color: #c4e3f3; -} -a.list-group-item-info.active, -button.list-group-item-info.active, -a.list-group-item-info.active:hover, -button.list-group-item-info.active:hover, -a.list-group-item-info.active:focus, -button.list-group-item-info.active:focus { - color: #fff; - background-color: #31708f; - border-color: #31708f; -} -.list-group-item-warning { - color: #8a6d3b; - background-color: #fcf8e3; -} -a.list-group-item-warning, -button.list-group-item-warning { - color: #8a6d3b; -} -a.list-group-item-warning .list-group-item-heading, -button.list-group-item-warning .list-group-item-heading { - color: inherit; -} -a.list-group-item-warning:hover, -button.list-group-item-warning:hover, -a.list-group-item-warning:focus, -button.list-group-item-warning:focus { - color: #8a6d3b; - background-color: #faf2cc; -} -a.list-group-item-warning.active, -button.list-group-item-warning.active, -a.list-group-item-warning.active:hover, -button.list-group-item-warning.active:hover, -a.list-group-item-warning.active:focus, -button.list-group-item-warning.active:focus { - color: #fff; - background-color: #8a6d3b; - border-color: #8a6d3b; -} -.list-group-item-danger { - color: #a94442; - background-color: #f2dede; -} -a.list-group-item-danger, -button.list-group-item-danger { - color: #a94442; -} -a.list-group-item-danger .list-group-item-heading, -button.list-group-item-danger .list-group-item-heading { - color: inherit; -} -a.list-group-item-danger:hover, -button.list-group-item-danger:hover, -a.list-group-item-danger:focus, -button.list-group-item-danger:focus { - color: #a94442; - background-color: #ebcccc; -} -a.list-group-item-danger.active, -button.list-group-item-danger.active, -a.list-group-item-danger.active:hover, -button.list-group-item-danger.active:hover, -a.list-group-item-danger.active:focus, -button.list-group-item-danger.active:focus { - color: #fff; - background-color: #a94442; - border-color: #a94442; -} -.list-group-item-muted { - color: #777777; - background-color: #f7f7f7; -} -a.list-group-item-muted, -button.list-group-item-muted { - color: #777777; -} -a.list-group-item-muted .list-group-item-heading, -button.list-group-item-muted .list-group-item-heading { - color: inherit; -} -a.list-group-item-muted:hover, -button.list-group-item-muted:hover, -a.list-group-item-muted:focus, -button.list-group-item-muted:focus { - color: #777777; - background-color: #f1f1f1; -} -a.list-group-item-muted.active, -button.list-group-item-muted.active, -a.list-group-item-muted.active:hover, -button.list-group-item-muted.active:hover, -a.list-group-item-muted.active:focus, -button.list-group-item-muted.active:focus { - color: #fff; - background-color: #777777; - border-color: #777777; -} -.list-group-item-heading { - margin-top: 0; - margin-bottom: 0; -} -.list-group-item-text { - margin-top: 5px; - margin-bottom: 0; - line-height: 1.3; -} -.list-group-item-text:empty { - margin-top: 0; -} -.panel { - margin-bottom: 20px; - background-color: #ffffff; - border: 1px solid transparent; - border-radius: 4px; - -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.05); - box-shadow: 0 1px 1px rgba(0, 0, 0, 0.05); -} -.panel-body { - padding: 15px; -} -.panel-heading { - padding: 10px 15px; - border-bottom: 1px solid transparent; - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel-heading > .dropdown .dropdown-toggle { - color: inherit; -} -.panel-title { - margin-top: 0; - margin-bottom: 0; - font-size: 16px; - color: inherit; -} -.panel-title > a, -.panel-title > small, -.panel-title > .small, -.panel-title > small > a, -.panel-title > .small > a { - color: inherit; -} -.panel-footer { - padding: 10px 15px; - background-color: #f5f5f5; - border-top: 1px solid #dddddd; - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .list-group, -.panel > .panel-collapse > .list-group { - margin-bottom: 0; -} -.panel > .list-group .list-group-item, -.panel > .panel-collapse > .list-group .list-group-item { - border-width: 1px 0; - border-radius: 0; -} -.panel > .list-group:first-child .list-group-item:first-child, -.panel > .panel-collapse > .list-group:first-child .list-group-item:first-child { - border-top: 0; - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel > .list-group:last-child .list-group-item:last-child, -.panel > .panel-collapse > .list-group:last-child .list-group-item:last-child { - border-bottom: 0; - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .panel-heading + .panel-collapse > .list-group .list-group-item:first-child { - border-top-right-radius: 0; - border-top-left-radius: 0; -} -.panel-heading + .list-group .list-group-item:first-child { - border-top-width: 0; -} -.list-group + .panel-footer { - border-top-width: 0; -} -.panel > .table, -.panel > .table-responsive > .table, -.panel > .panel-collapse > .table { - margin-bottom: 0; -} -.panel > .table caption, -.panel > .table-responsive > .table caption, -.panel > .panel-collapse > .table caption { - padding-left: 15px; - padding-right: 15px; -} -.panel > .table:first-child, -.panel > .table-responsive:first-child > .table:first-child { - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child { - border-top-left-radius: 3px; - border-top-right-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child td:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child td:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child td:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child td:first-child, -.panel > .table:first-child > thead:first-child > tr:first-child th:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child th:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child th:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child th:first-child { - border-top-left-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child td:last-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child td:last-child, -.panel > .table:first-child > tbody:first-child > tr:first-child td:last-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child td:last-child, -.panel > .table:first-child > thead:first-child > tr:first-child th:last-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child th:last-child, -.panel > .table:first-child > tbody:first-child > tr:first-child th:last-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child th:last-child { - border-top-right-radius: 3px; -} -.panel > .table:last-child, -.panel > .table-responsive:last-child > .table:last-child { - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child { - border-bottom-left-radius: 3px; - border-bottom-right-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child td:first-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child td:first-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child td:first-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child td:first-child, -.panel > .table:last-child > tbody:last-child > tr:last-child th:first-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child th:first-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child th:first-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child th:first-child { - border-bottom-left-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child td:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child td:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child td:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child td:last-child, -.panel > .table:last-child > tbody:last-child > tr:last-child th:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child th:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child th:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child th:last-child { - border-bottom-right-radius: 3px; -} -.panel > .panel-body + .table, -.panel > .panel-body + .table-responsive, -.panel > .table + .panel-body, -.panel > .table-responsive + .panel-body { - border-top: 1px solid #dddddd; -} -.panel > .table > tbody:first-child > tr:first-child th, -.panel > .table > tbody:first-child > tr:first-child td { - border-top: 0; -} -.panel > .table-bordered, -.panel > .table-responsive > .table-bordered { - border: 0; -} -.panel > .table-bordered > thead > tr > th:first-child, -.panel > .table-responsive > .table-bordered > thead > tr > th:first-child, -.panel > .table-bordered > tbody > tr > th:first-child, -.panel > .table-responsive > .table-bordered > tbody > tr > th:first-child, -.panel > .table-bordered > tfoot > tr > th:first-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > th:first-child, -.panel > .table-bordered > thead > tr > td:first-child, -.panel > .table-responsive > .table-bordered > thead > tr > td:first-child, -.panel > .table-bordered > tbody > tr > td:first-child, -.panel > .table-responsive > .table-bordered > tbody > tr > td:first-child, -.panel > .table-bordered > tfoot > tr > td:first-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > td:first-child { - border-left: 0; -} -.panel > .table-bordered > thead > tr > th:last-child, -.panel > .table-responsive > .table-bordered > thead > tr > th:last-child, -.panel > .table-bordered > tbody > tr > th:last-child, -.panel > .table-responsive > .table-bordered > tbody > tr > th:last-child, -.panel > .table-bordered > tfoot > tr > th:last-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > th:last-child, -.panel > .table-bordered > thead > tr > td:last-child, -.panel > .table-responsive > .table-bordered > thead > tr > td:last-child, -.panel > .table-bordered > tbody > tr > td:last-child, -.panel > .table-responsive > .table-bordered > tbody > tr > td:last-child, -.panel > .table-bordered > tfoot > tr > td:last-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > td:last-child { - border-right: 0; -} -.panel > .table-bordered > thead > tr:first-child > td, -.panel > .table-responsive > .table-bordered > thead > tr:first-child > td, -.panel > .table-bordered > tbody > tr:first-child > td, -.panel > .table-responsive > .table-bordered > tbody > tr:first-child > td, -.panel > .table-bordered > thead > tr:first-child > th, -.panel > .table-responsive > .table-bordered > thead > tr:first-child > th, -.panel > .table-bordered > tbody > tr:first-child > th, -.panel > .table-responsive > .table-bordered > tbody > tr:first-child > th { - border-bottom: 0; -} -.panel > .table-bordered > tbody > tr:last-child > td, -.panel > .table-responsive > .table-bordered > tbody > tr:last-child > td, -.panel > .table-bordered > tfoot > tr:last-child > td, -.panel > .table-responsive > .table-bordered > tfoot > tr:last-child > td, -.panel > .table-bordered > tbody > tr:last-child > th, -.panel > .table-responsive > .table-bordered > tbody > tr:last-child > th, -.panel > .table-bordered > tfoot > tr:last-child > th, -.panel > .table-responsive > .table-bordered > tfoot > tr:last-child > th { - border-bottom: 0; -} -.panel > .table-responsive { - border: 0; - margin-bottom: 0; -} -.panel-group { - margin-bottom: 20px; -} -.panel-group .panel { - margin-bottom: 0; - border-radius: 4px; -} -.panel-group .panel + .panel { - margin-top: 5px; -} -.panel-group .panel-heading { - border-bottom: 0; -} -.panel-group .panel-heading + .panel-collapse > .panel-body, -.panel-group .panel-heading + .panel-collapse > .list-group { - border-top: 1px solid #dddddd; -} -.panel-group .panel-footer { - border-top: 0; -} -.panel-group .panel-footer + .panel-collapse .panel-body { - border-bottom: 1px solid #dddddd; -} -.panel-default { - border-color: #dddddd; -} -.panel-default > .panel-heading { - color: #333333; - background-color: #f5f5f5; - border-color: #dddddd; -} -.panel-default > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #dddddd; -} -.panel-default > .panel-heading .badge { - color: #f5f5f5; - background-color: #333333; -} -.panel-default > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #dddddd; -} -.panel-primary { - border-color: #337ab7; -} -.panel-primary > .panel-heading { - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; -} -.panel-primary > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #337ab7; -} -.panel-primary > .panel-heading .badge { - color: #337ab7; - background-color: #ffffff; -} -.panel-primary > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #337ab7; -} -.panel-success { - border-color: #d6e9c6; -} -.panel-success > .panel-heading { - color: #3c763d; - background-color: #dff0d8; - border-color: #d6e9c6; -} -.panel-success > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #d6e9c6; -} -.panel-success > .panel-heading .badge { - color: #dff0d8; - background-color: #3c763d; -} -.panel-success > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #d6e9c6; -} -.panel-info { - border-color: #bce8f1; -} -.panel-info > .panel-heading { - color: #31708f; - background-color: #d9edf7; - border-color: #bce8f1; -} -.panel-info > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #bce8f1; -} -.panel-info > .panel-heading .badge { - color: #d9edf7; - background-color: #31708f; -} -.panel-info > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #bce8f1; -} -.panel-warning { - border-color: #faebcc; -} -.panel-warning > .panel-heading { - color: #8a6d3b; - background-color: #fcf8e3; - border-color: #faebcc; -} -.panel-warning > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #faebcc; -} -.panel-warning > .panel-heading .badge { - color: #fcf8e3; - background-color: #8a6d3b; -} -.panel-warning > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #faebcc; -} -.panel-danger { - border-color: #ebccd1; -} -.panel-danger > .panel-heading { - color: #a94442; - background-color: #f2dede; - border-color: #ebccd1; -} -.panel-danger > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #ebccd1; -} -.panel-danger > .panel-heading .badge { - color: #f2dede; - background-color: #a94442; -} -.panel-danger > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #ebccd1; -} - -/* Inline Group */ - -.input-group { - position: relative; - display: table; - border-collapse: separate; -} -.input-group[class*="col-"] { - float: none; - padding-left: 0; - padding-right: 0; -} -.input-group .form-control { - position: relative; - z-index: 2; - float: left; - width: 100%; - margin-bottom: 0; -} -.input-group .form-control:focus { - z-index: 3; -} -.input-group-lg > .form-control, -.input-group-lg > .input-group-addon, -.input-group-lg > .input-group-btn > .btn { - height: 41px; - padding: 10px 16px; - font-size: 15px; - line-height: 1.3333333; - border-radius: 6px; -} -select.input-group-lg > .form-control, -select.input-group-lg > .input-group-addon, -select.input-group-lg > .input-group-btn > .btn { - height: 41px; - line-height: 41px; -} -textarea.input-group-lg > .form-control, -textarea.input-group-lg > .input-group-addon, -textarea.input-group-lg > .input-group-btn > .btn, -select[multiple].input-group-lg > .form-control, -select[multiple].input-group-lg > .input-group-addon, -select[multiple].input-group-lg > .input-group-btn > .btn { - height: auto; -} -.input-group-sm > .form-control, -.input-group-sm > .input-group-addon, -.input-group-sm > .input-group-btn > .btn { - height: 30px; - padding: 5px 10px; - font-size: 12px; - line-height: 1.5; - border-radius: 3px; -} -select.input-group-sm > .form-control, -select.input-group-sm > .input-group-addon, -select.input-group-sm > .input-group-btn > .btn { - height: 30px; - line-height: 30px; -} -textarea.input-group-sm > .form-control, -textarea.input-group-sm > .input-group-addon, -textarea.input-group-sm > .input-group-btn > .btn, -select[multiple].input-group-sm > .form-control, -select[multiple].input-group-sm > .input-group-addon, -select[multiple].input-group-sm > .input-group-btn > .btn { - height: auto; -} -.input-group-addon, -.input-group-btn, -.input-group .form-control { - display: table-cell; -} -.input-group-addon:not(:first-child):not(:last-child), -.input-group-btn:not(:first-child):not(:last-child), -.input-group .form-control:not(:first-child):not(:last-child) { - border-radius: 0; -} -.input-group-addon, -.input-group-btn { - width: 1%; - white-space: nowrap; - vertical-align: middle; -} -.input-group-addon { - padding: 6px 12px; - font-size: 14px; - font-weight: normal; - line-height: 1; - color: #555555; - text-align: center; - background-color: #eeeeee; - border: 1px solid #cccccc; - border-radius: 4px; -} -.input-group-addon.input-sm { - padding: 5px 10px; - font-size: 12px; - border-radius: 3px; -} -.input-group-addon.input-lg { - padding: 10px 16px; - font-size: 15px; - border-radius: 6px; -} -.input-group-addon input[type="radio"], -.input-group-addon input[type="checkbox"] { - margin-top: 0; -} -.input-group .form-control:first-child, -.input-group-addon:first-child, -.input-group-btn:first-child > .btn, -.input-group-btn:first-child > .btn-group > .btn, -.input-group-btn:first-child > .dropdown-toggle, -.input-group-btn:last-child > .btn:not(:last-child):not(.dropdown-toggle), -.input-group-btn:last-child > .btn-group:not(:last-child) > .btn { - border-bottom-right-radius: 0; - border-top-right-radius: 0; -} -.input-group-addon:first-child { - border-right: 0; -} -.input-group .form-control:last-child, -.input-group-addon:last-child, -.input-group-btn:last-child > .btn, -.input-group-btn:last-child > .btn-group > .btn, -.input-group-btn:last-child > .dropdown-toggle, -.input-group-btn:first-child > .btn:not(:first-child), -.input-group-btn:first-child > .btn-group:not(:first-child) > .btn { - border-bottom-left-radius: 0; - border-top-left-radius: 0; -} -.input-group-addon:last-child { - border-left: 0; -} -.input-group-btn { - position: relative; - font-size: 0; - white-space: nowrap; -} -.input-group-btn > .btn { - position: relative; -} -.input-group-btn > .btn + .btn { - margin-left: -1px; -} -.input-group-btn > .btn:hover, -.input-group-btn > .btn:focus, -.input-group-btn > .btn:active { - z-index: 2; -} -.input-group-btn:first-child > .btn, -.input-group-btn:first-child > .btn-group { - margin-right: -1px; -} -.input-group-btn:last-child > .btn, -.input-group-btn:last-child > .btn-group { - z-index: 2; - margin-left: -1px; -} -.clearfix:before, -.clearfix:after, -.form-horizontal .form-group:before, -.form-horizontal .form-group:after { - content: " "; - display: table; -} -.clearfix:after, -.form-horizontal .form-group:after { - clear: both; -} diff --git a/data/core.telegram.org/css/bootstrap.min.css b/data/core.telegram.org/css/bootstrap.min.css deleted file mode 100644 index b59e0626ca..0000000000 --- a/data/core.telegram.org/css/bootstrap.min.css +++ /dev/null @@ -1,10 +0,0 @@ -/*! - * Bootstrap v3.2.0 (http://getbootstrap.com) - * Copyright 2011-2014 Twitter, Inc. - * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE) - */ - -/*! - * Generated using the Bootstrap Customizer (http://getbootstrap.com/customize/?id=92d2ac1b31978642b6b6) - * Config saved to config.json and https://gist.github.com/92d2ac1b31978642b6b6 - *//*! normalize.css v3.0.1 | MIT License | git.io/normalize */html{font-family:sans-serif;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%}body{margin:0}article,aside,details,figcaption,figure,footer,header,hgroup,main,nav,section,summary{display:block}audio,canvas,progress,video{display:inline-block;vertical-align:baseline}audio:not([controls]){display:none;height:0}[hidden],template{display:none}a{background:transparent}a:active,a:hover{outline:0}abbr[title]{border-bottom:1px dotted}b,strong{font-weight:bold}dfn{font-style:italic}h1{font-size:2em;margin:0.67em 0}mark{background:#ff0;color:#000}small{font-size:80%}sub,sup{font-size:75%;line-height:0;position:relative;vertical-align:baseline}sup{top:-0.5em}sub{bottom:-0.25em}img{border:0}svg:not(:root){overflow:hidden}figure{margin:1em 40px}hr{-moz-box-sizing:content-box;box-sizing:content-box;height:0}pre{overflow:auto}code,kbd,pre,samp{font-family:monospace, monospace;font-size:1em}button,input,optgroup,select,textarea{color:inherit;font:inherit;margin:0}button{overflow:visible}button,select{text-transform:none}button,html input[type="button"],input[type="reset"],input[type="submit"]{-webkit-appearance:button;cursor:pointer}button[disabled],html input[disabled]{cursor:default}button::-moz-focus-inner,input::-moz-focus-inner{border:0;padding:0}input{line-height:normal}input[type="checkbox"],input[type="radio"]{box-sizing:border-box;padding:0}input[type="number"]::-webkit-inner-spin-button,input[type="number"]::-webkit-outer-spin-button{height:auto}input[type="search"]{-webkit-appearance:textfield;-moz-box-sizing:content-box;-webkit-box-sizing:content-box;box-sizing:content-box}input[type="search"]::-webkit-search-cancel-button,input[type="search"]::-webkit-search-decoration{-webkit-appearance:none}fieldset{border:1px solid #c0c0c0;margin:0 2px;padding:0.35em 0.625em 0.75em}legend{border:0;padding:0}textarea{overflow:auto}optgroup{font-weight:bold}table{border-collapse:collapse;border-spacing:0}td,th{padding:0}*{-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box}*:before,*:after{-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box}html{font-size:10px;-webkit-tap-highlight-color:rgba(0,0,0,0)}body{font-family:"Lucida Grande","Lucida Sans Unicode",Arial,Helvetica,Verdana,sans-serif;font-size:12px;line-height:1.42857143;color:#333;background-color:#fff}input,button,select,textarea{font-family:inherit;font-size:inherit;line-height:inherit}a{color:#2e87ca;text-decoration:none}a:hover,a:focus{color:#2e87ca;text-decoration:underline}a:focus{outline:thin dotted;outline:5px auto -webkit-focus-ring-color;outline-offset:-2px}figure{margin:0}img{vertical-align:middle}.img-responsive{display:block;width:100% \9;max-width:100%;height:auto}.img-rounded{border-radius:6px}.img-thumbnail{padding:4px;line-height:1.42857143;background-color:#fff;border:1px solid #ddd;border-radius:4px;-webkit-transition:all .2s ease-in-out;-o-transition:all .2s ease-in-out;transition:all .2s ease-in-out;display:inline-block;width:100% \9;max-width:100%;height:auto}.img-circle{border-radius:50%}hr{margin-top:17px;margin-bottom:17px;border:0;border-top:1px solid #eee}.sr-only{position:absolute;width:1px;height:1px;margin:-1px;padding:0;overflow:hidden;clip:rect(0, 0, 0, 0);border:0}.sr-only-focusable:active,.sr-only-focusable:focus{position:static;width:auto;height:auto;margin:0;overflow:visible;clip:auto}h1,h2,h3,h4,h5,h6,.h1,.h2,.h3,.h4,.h5,.h6{font-family:inherit;font-weight:500;line-height:1.1;color:inherit}h1 small,h2 small,h3 small,h4 small,h5 small,h6 small,.h1 small,.h2 small,.h3 small,.h4 small,.h5 small,.h6 small,h1 .small,h2 .small,h3 .small,h4 .small,h5 .small,h6 .small,.h1 .small,.h2 .small,.h3 .small,.h4 .small,.h5 .small,.h6 .small{font-weight:normal;line-height:1;color:#777}h1,.h1,h2,.h2,h3,.h3{margin-top:17px;margin-bottom:8.5px}h1 small,.h1 small,h2 small,.h2 small,h3 small,.h3 small,h1 .small,.h1 .small,h2 .small,.h2 .small,h3 .small,.h3 .small{font-size:65%}h4,.h4,h5,.h5,h6,.h6{margin-top:8.5px;margin-bottom:8.5px}h4 small,.h4 small,h5 small,.h5 small,h6 small,.h6 small,h4 .small,.h4 .small,h5 .small,.h5 .small,h6 .small,.h6 .small{font-size:75%}h1,.h1{font-size:31px}h2,.h2{font-size:25px}h3,.h3{font-size:21px}h4,.h4{font-size:15px}h5,.h5{font-size:12px}h6,.h6{font-size:11px}p{margin:0 0 8.5px}.lead{margin-bottom:17px;font-size:13px;font-weight:300;line-height:1.4}@media (min-width:768px){.lead{font-size:18px}}small,.small{font-size:91%}cite{font-style:normal}mark,.mark{background-color:#fcf8e3;padding:.2em}.text-left{text-align:left}.text-right{text-align:right}.text-center{text-align:center}.text-justify{text-align:justify}.text-nowrap{white-space:nowrap}.text-lowercase{text-transform:lowercase}.text-uppercase{text-transform:uppercase}.text-capitalize{text-transform:capitalize}.text-muted{color:#777}.text-primary{color:#428bca}a.text-primary:hover{color:#3071a9}.text-success{color:#3c763d}a.text-success:hover{color:#2b542c}.text-info{color:#31708f}a.text-info:hover{color:#245269}.text-warning{color:#8a6d3b}a.text-warning:hover{color:#66512c}.text-danger{color:#a94442}a.text-danger:hover{color:#843534}.bg-primary{color:#fff;background-color:#428bca}a.bg-primary:hover{background-color:#3071a9}.bg-success{background-color:#dff0d8}a.bg-success:hover{background-color:#c1e2b3}.bg-info{background-color:#d9edf7}a.bg-info:hover{background-color:#afd9ee}.bg-warning{background-color:#fcf8e3}a.bg-warning:hover{background-color:#f7ecb5}.bg-danger{background-color:#f2dede}a.bg-danger:hover{background-color:#e4b9b9}.page-header{padding-bottom:7.5px;margin:34px 0 17px;border-bottom:1px solid #eee}ul,ol{margin-top:0;margin-bottom:8.5px}ul ul,ol ul,ul ol,ol ol{margin-bottom:0}.list-unstyled{padding-left:0;list-style:none}.list-inline{padding-left:0;list-style:none;margin-left:-5px}.list-inline>li{display:inline-block;padding-left:5px;padding-right:5px}dl{margin-top:0;margin-bottom:17px}dt,dd{line-height:1.42857143}dt{font-weight:bold}dd{margin-left:0}@media (min-width:1px){.dl-horizontal dt{float:left;width:160px;clear:left;text-align:right;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}.dl-horizontal dd{margin-left:180px}}abbr[title],abbr[data-original-title]{cursor:help;border-bottom:1px dotted #777}.initialism{font-size:90%;text-transform:uppercase}blockquote{padding:8.5px 17px;margin:0 0 17px;font-size:15px;border-left:5px solid #eee}blockquote p:last-child,blockquote ul:last-child,blockquote ol:last-child{margin-bottom:0}blockquote footer,blockquote small,blockquote .small{display:block;font-size:80%;line-height:1.42857143;color:#777}blockquote footer:before,blockquote small:before,blockquote .small:before{content:'\2014 \00A0'}.blockquote-reverse,blockquote.pull-right{padding-right:15px;padding-left:0;border-right:5px solid #eee;border-left:0;text-align:right}.blockquote-reverse footer:before,blockquote.pull-right footer:before,.blockquote-reverse small:before,blockquote.pull-right small:before,.blockquote-reverse .small:before,blockquote.pull-right .small:before{content:''}.blockquote-reverse footer:after,blockquote.pull-right footer:after,.blockquote-reverse small:after,blockquote.pull-right small:after,.blockquote-reverse .small:after,blockquote.pull-right .small:after{content:'\00A0 \2014'}blockquote:before,blockquote:after{content:""}address{margin-bottom:17px;font-style:normal;line-height:1.42857143}code,kbd,pre,samp{font-family:Menlo,Monaco,Consolas,"Courier New",monospace}code{padding:2px 4px;font-size:90%;color:#c61717;background-color:#feeae4;border-radius:4px}kbd{padding:2px 4px;font-size:90%;color:#fff;background-color:#333;border-radius:3px;box-shadow:inset 0 -1px 0 rgba(0,0,0,0.25)}kbd kbd{padding:0;font-size:100%;box-shadow:none}pre{display:block;padding:8px;margin:0 0 8.5px;font-size:11px;line-height:1.42857143;word-break:break-all;word-wrap:break-word;color:#546172;background-color:#ecf3f8;border:1px solid #ccc;border-radius:4px}pre code{padding:0;font-size:inherit;color:inherit;white-space:pre-wrap;background-color:transparent;border-radius:0}.pre-scrollable{max-height:340px;overflow-y:scroll}table{background-color:transparent}th{text-align:left}.table{width:100%;max-width:100%;margin-bottom:17px}.table>thead>tr>th,.table>tbody>tr>th,.table>tfoot>tr>th,.table>thead>tr>td,.table>tbody>tr>td,.table>tfoot>tr>td{padding:8px;line-height:1.42857143;vertical-align:top;border-top:1px solid #eee}.table>thead>tr>th{vertical-align:bottom;border-bottom:2px solid #eee}.table>caption+thead>tr:first-child>th,.table>colgroup+thead>tr:first-child>th,.table>thead:first-child>tr:first-child>th,.table>caption+thead>tr:first-child>td,.table>colgroup+thead>tr:first-child>td,.table>thead:first-child>tr:first-child>td{border-top:0}.table>tbody+tbody{border-top:2px solid #eee}.table .table{background-color:#fff}.table-condensed>thead>tr>th,.table-condensed>tbody>tr>th,.table-condensed>tfoot>tr>th,.table-condensed>thead>tr>td,.table-condensed>tbody>tr>td,.table-condensed>tfoot>tr>td{padding:5px}.table-bordered{border:1px solid #eee}.table-bordered>thead>tr>th,.table-bordered>tbody>tr>th,.table-bordered>tfoot>tr>th,.table-bordered>thead>tr>td,.table-bordered>tbody>tr>td,.table-bordered>tfoot>tr>td{border:1px solid #eee}.table-bordered>thead>tr>th,.table-bordered>thead>tr>td{border-bottom-width:2px}.table-striped>tbody>tr:nth-child(odd)>td,.table-striped>tbody>tr:nth-child(odd)>th{background-color:#f9f9f9}.table-hover>tbody>tr:hover>td,.table-hover>tbody>tr:hover>th{background-color:#f5f5f5}table col[class*="col-"]{position:static;float:none;display:table-column}table td[class*="col-"],table th[class*="col-"]{position:static;float:none;display:table-cell}.table>thead>tr>td.active,.table>tbody>tr>td.active,.table>tfoot>tr>td.active,.table>thead>tr>th.active,.table>tbody>tr>th.active,.table>tfoot>tr>th.active,.table>thead>tr.active>td,.table>tbody>tr.active>td,.table>tfoot>tr.active>td,.table>thead>tr.active>th,.table>tbody>tr.active>th,.table>tfoot>tr.active>th{background-color:#f5f5f5}.table-hover>tbody>tr>td.active:hover,.table-hover>tbody>tr>th.active:hover,.table-hover>tbody>tr.active:hover>td,.table-hover>tbody>tr:hover>.active,.table-hover>tbody>tr.active:hover>th{background-color:#e8e8e8}.table>thead>tr>td.success,.table>tbody>tr>td.success,.table>tfoot>tr>td.success,.table>thead>tr>th.success,.table>tbody>tr>th.success,.table>tfoot>tr>th.success,.table>thead>tr.success>td,.table>tbody>tr.success>td,.table>tfoot>tr.success>td,.table>thead>tr.success>th,.table>tbody>tr.success>th,.table>tfoot>tr.success>th{background-color:#dff0d8}.table-hover>tbody>tr>td.success:hover,.table-hover>tbody>tr>th.success:hover,.table-hover>tbody>tr.success:hover>td,.table-hover>tbody>tr:hover>.success,.table-hover>tbody>tr.success:hover>th{background-color:#d0e9c6}.table>thead>tr>td.info,.table>tbody>tr>td.info,.table>tfoot>tr>td.info,.table>thead>tr>th.info,.table>tbody>tr>th.info,.table>tfoot>tr>th.info,.table>thead>tr.info>td,.table>tbody>tr.info>td,.table>tfoot>tr.info>td,.table>thead>tr.info>th,.table>tbody>tr.info>th,.table>tfoot>tr.info>th{background-color:#d9edf7}.table-hover>tbody>tr>td.info:hover,.table-hover>tbody>tr>th.info:hover,.table-hover>tbody>tr.info:hover>td,.table-hover>tbody>tr:hover>.info,.table-hover>tbody>tr.info:hover>th{background-color:#c4e3f3}.table>thead>tr>td.warning,.table>tbody>tr>td.warning,.table>tfoot>tr>td.warning,.table>thead>tr>th.warning,.table>tbody>tr>th.warning,.table>tfoot>tr>th.warning,.table>thead>tr.warning>td,.table>tbody>tr.warning>td,.table>tfoot>tr.warning>td,.table>thead>tr.warning>th,.table>tbody>tr.warning>th,.table>tfoot>tr.warning>th{background-color:#fcf8e3}.table-hover>tbody>tr>td.warning:hover,.table-hover>tbody>tr>th.warning:hover,.table-hover>tbody>tr.warning:hover>td,.table-hover>tbody>tr:hover>.warning,.table-hover>tbody>tr.warning:hover>th{background-color:#faf2cc}.table>thead>tr>td.danger,.table>tbody>tr>td.danger,.table>tfoot>tr>td.danger,.table>thead>tr>th.danger,.table>tbody>tr>th.danger,.table>tfoot>tr>th.danger,.table>thead>tr.danger>td,.table>tbody>tr.danger>td,.table>tfoot>tr.danger>td,.table>thead>tr.danger>th,.table>tbody>tr.danger>th,.table>tfoot>tr.danger>th{background-color:#f2dede}.table-hover>tbody>tr>td.danger:hover,.table-hover>tbody>tr>th.danger:hover,.table-hover>tbody>tr.danger:hover>td,.table-hover>tbody>tr:hover>.danger,.table-hover>tbody>tr.danger:hover>th{background-color:#ebcccc}@media screen and (max-width:767px){.table-responsive{width:100%;margin-bottom:12.75px;overflow-y:hidden;overflow-x:auto;-ms-overflow-style:-ms-autohiding-scrollbar;border:1px solid #eee;-webkit-overflow-scrolling:touch}.table-responsive>.table{margin-bottom:0}.table-responsive>.table>thead>tr>th,.table-responsive>.table>tbody>tr>th,.table-responsive>.table>tfoot>tr>th,.table-responsive>.table>thead>tr>td,.table-responsive>.table>tbody>tr>td,.table-responsive>.table>tfoot>tr>td{white-space:nowrap}.table-responsive>.table-bordered{border:0}.table-responsive>.table-bordered>thead>tr>th:first-child,.table-responsive>.table-bordered>tbody>tr>th:first-child,.table-responsive>.table-bordered>tfoot>tr>th:first-child,.table-responsive>.table-bordered>thead>tr>td:first-child,.table-responsive>.table-bordered>tbody>tr>td:first-child,.table-responsive>.table-bordered>tfoot>tr>td:first-child{border-left:0}.table-responsive>.table-bordered>thead>tr>th:last-child,.table-responsive>.table-bordered>tbody>tr>th:last-child,.table-responsive>.table-bordered>tfoot>tr>th:last-child,.table-responsive>.table-bordered>thead>tr>td:last-child,.table-responsive>.table-bordered>tbody>tr>td:last-child,.table-responsive>.table-bordered>tfoot>tr>td:last-child{border-right:0}.table-responsive>.table-bordered>tbody>tr:last-child>th,.table-responsive>.table-bordered>tfoot>tr:last-child>th,.table-responsive>.table-bordered>tbody>tr:last-child>td,.table-responsive>.table-bordered>tfoot>tr:last-child>td{border-bottom:0}}fieldset{padding:0;margin:0;border:0;min-width:0}legend{display:block;width:100%;padding:0;margin-bottom:17px;font-size:18px;line-height:inherit;color:#333;border:0;border-bottom:1px solid #e5e5e5}label{display:inline-block;max-width:100%;margin-bottom:5px;font-weight:bold}input[type="search"]{-webkit-box-sizing:border-box;-moz-box-sizing:border-box;box-sizing:border-box}input[type="radio"],input[type="checkbox"]{margin:4px 0 0;margin-top:1px \9;line-height:normal}input[type="file"]{display:block}input[type="range"]{display:block;width:100%}select[multiple],select[size]{height:auto}input[type="file"]:focus,input[type="radio"]:focus,input[type="checkbox"]:focus{outline:thin dotted;outline:5px auto -webkit-focus-ring-color;outline-offset:-2px}output{display:block;padding-top:7px;font-size:12px;line-height:1.42857143;color:#555}.form-control{display:block;width:100%;height:31px;padding:6px 12px;font-size:12px;line-height:1.42857143;color:#555;background-color:#fff;background-image:none;border:1px solid #ccc;border-radius:4px;-webkit-box-shadow:inset 0 1px 1px rgba(0,0,0,0.075);box-shadow:inset 0 1px 1px rgba(0,0,0,0.075);-webkit-transition:border-color ease-in-out .15s, box-shadow ease-in-out .15s;-o-transition:border-color ease-in-out .15s, box-shadow ease-in-out .15s;transition:border-color ease-in-out .15s, box-shadow ease-in-out .15s}.form-control:focus{border-color:#66afe9;outline:0;-webkit-box-shadow:inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6);box-shadow:inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6)}.form-control::-moz-placeholder{color:#777;opacity:1}.form-control:-ms-input-placeholder{color:#777}.form-control::-webkit-input-placeholder{color:#777}.form-control[disabled],.form-control[readonly],fieldset[disabled] .form-control{cursor:not-allowed;background-color:#eee;opacity:1}textarea.form-control{height:auto}input[type="search"]{-webkit-appearance:none}input[type="date"],input[type="time"],input[type="datetime-local"],input[type="month"]{line-height:31px;line-height:1.42857143 \0}input[type="date"].input-sm,input[type="time"].input-sm,input[type="datetime-local"].input-sm,input[type="month"].input-sm{line-height:28px}input[type="date"].input-lg,input[type="time"].input-lg,input[type="datetime-local"].input-lg,input[type="month"].input-lg{line-height:42px}.form-group{margin-bottom:15px}.radio,.checkbox{position:relative;display:block;min-height:17px;margin-top:10px;margin-bottom:10px}.radio label,.checkbox label{padding-left:20px;margin-bottom:0;font-weight:normal;cursor:pointer}.radio input[type="radio"],.radio-inline input[type="radio"],.checkbox input[type="checkbox"],.checkbox-inline input[type="checkbox"]{position:absolute;margin-left:-20px;margin-top:4px \9}.radio+.radio,.checkbox+.checkbox{margin-top:-5px}.radio-inline,.checkbox-inline{display:inline-block;padding-left:20px;margin-bottom:0;vertical-align:middle;font-weight:normal;cursor:pointer}.radio-inline+.radio-inline,.checkbox-inline+.checkbox-inline{margin-top:0;margin-left:10px}input[type="radio"][disabled],input[type="checkbox"][disabled],input[type="radio"].disabled,input[type="checkbox"].disabled,fieldset[disabled] input[type="radio"],fieldset[disabled] input[type="checkbox"]{cursor:not-allowed}.radio-inline.disabled,.checkbox-inline.disabled,fieldset[disabled] .radio-inline,fieldset[disabled] .checkbox-inline{cursor:not-allowed}.radio.disabled label,.checkbox.disabled label,fieldset[disabled] .radio label,fieldset[disabled] .checkbox label{cursor:not-allowed}.form-control-static{padding-top:7px;padding-bottom:7px;margin-bottom:0}.form-control-static.input-lg,.form-control-static.input-sm{padding-left:0;padding-right:0}.input-sm,.form-horizontal .form-group-sm .form-control{height:28px;padding:5px 10px;font-size:11px;line-height:1.5;border-radius:3px}select.input-sm{height:28px;line-height:28px}textarea.input-sm,select[multiple].input-sm{height:auto}.input-lg,.form-horizontal .form-group-lg .form-control{height:42px;padding:10px 16px;font-size:15px;line-height:1.33;border-radius:6px}select.input-lg{height:42px;line-height:42px}textarea.input-lg,select[multiple].input-lg{height:auto}.has-feedback{position:relative}.has-feedback .form-control{padding-right:38.75px}.form-control-feedback{position:absolute;top:22px;right:0;z-index:2;display:block;width:31px;height:31px;line-height:31px;text-align:center}.input-lg+.form-control-feedback{width:42px;height:42px;line-height:42px}.input-sm+.form-control-feedback{width:28px;height:28px;line-height:28px}.has-success .help-block,.has-success .control-label,.has-success .radio,.has-success .checkbox,.has-success .radio-inline,.has-success .checkbox-inline{color:#3c763d}.has-success .form-control{border-color:#3c763d;-webkit-box-shadow:inset 0 1px 1px rgba(0,0,0,0.075);box-shadow:inset 0 1px 1px rgba(0,0,0,0.075)}.has-success .form-control:focus{border-color:#2b542c;-webkit-box-shadow:inset 0 1px 1px rgba(0,0,0,0.075),0 0 6px #67b168;box-shadow:inset 0 1px 1px rgba(0,0,0,0.075),0 0 6px #67b168}.has-success .input-group-addon{color:#3c763d;border-color:#3c763d;background-color:#dff0d8}.has-success .form-control-feedback{color:#3c763d}.has-warning .help-block,.has-warning .control-label,.has-warning .radio,.has-warning .checkbox,.has-warning .radio-inline,.has-warning .checkbox-inline{color:#8a6d3b}.has-warning .form-control{border-color:#8a6d3b;-webkit-box-shadow:inset 0 1px 1px rgba(0,0,0,0.075);box-shadow:inset 0 1px 1px rgba(0,0,0,0.075)}.has-warning .form-control:focus{border-color:#66512c;-webkit-box-shadow:inset 0 1px 1px rgba(0,0,0,0.075),0 0 6px #c0a16b;box-shadow:inset 0 1px 1px rgba(0,0,0,0.075),0 0 6px #c0a16b}.has-warning .input-group-addon{color:#8a6d3b;border-color:#8a6d3b;background-color:#fcf8e3}.has-warning .form-control-feedback{color:#8a6d3b}.has-error .help-block,.has-error .control-label,.has-error .radio,.has-error .checkbox,.has-error .radio-inline,.has-error .checkbox-inline{color:#a94442}.has-error .form-control{border-color:#a94442;-webkit-box-shadow:inset 0 1px 1px rgba(0,0,0,0.075);box-shadow:inset 0 1px 1px rgba(0,0,0,0.075)}.has-error .form-control:focus{border-color:#843534;-webkit-box-shadow:inset 0 1px 1px rgba(0,0,0,0.075),0 0 6px #ce8483;box-shadow:inset 0 1px 1px rgba(0,0,0,0.075),0 0 6px #ce8483}.has-error .input-group-addon{color:#a94442;border-color:#a94442;background-color:#f2dede}.has-error .form-control-feedback{color:#a94442}.has-feedback label.sr-only~.form-control-feedback{top:0}.help-block{display:block;margin-top:5px;margin-bottom:10px;color:#737373}@media (min-width:768px){.form-inline .form-group{display:inline-block;margin-bottom:0;vertical-align:middle}.form-inline .form-control{display:inline-block;width:auto;vertical-align:middle}.form-inline .input-group{display:inline-table;vertical-align:middle}.form-inline .input-group .input-group-addon,.form-inline .input-group .input-group-btn,.form-inline .input-group .form-control{width:auto}.form-inline .input-group>.form-control{width:100%}.form-inline .control-label{margin-bottom:0;vertical-align:middle}.form-inline .radio,.form-inline .checkbox{display:inline-block;margin-top:0;margin-bottom:0;vertical-align:middle}.form-inline .radio label,.form-inline .checkbox label{padding-left:0}.form-inline .radio input[type="radio"],.form-inline .checkbox input[type="checkbox"]{position:relative;margin-left:0}.form-inline .has-feedback .form-control-feedback{top:0}}.form-horizontal .radio,.form-horizontal .checkbox,.form-horizontal .radio-inline,.form-horizontal .checkbox-inline{margin-top:0;margin-bottom:0;padding-top:7px}.form-horizontal .radio,.form-horizontal .checkbox{min-height:24px}.form-horizontal .form-group{margin-left:-15px;margin-right:-15px}@media (min-width:768px){.form-horizontal .control-label{text-align:right;margin-bottom:0;padding-top:7px}}.form-horizontal .has-feedback .form-control-feedback{top:0;right:15px}@media (min-width:768px){.form-horizontal .form-group-lg .control-label{padding-top:14.3px}}@media (min-width:768px){.form-horizontal .form-group-sm .control-label{padding-top:6px}}.fade{opacity:0;-webkit-transition:opacity .15s linear;-o-transition:opacity .15s linear;transition:opacity .15s linear}.fade.in{opacity:1}.collapse{display:none}.collapse.in{display:block}tr.collapse.in{display:table-row}tbody.collapse.in{display:table-row-group}.collapsing{position:relative;height:0;overflow:hidden;-webkit-transition:height .35s ease;-o-transition:height .35s ease;transition:height .35s ease}.caret{display:inline-block;width:0;height:0;margin-left:2px;vertical-align:middle;border-top:4px solid;border-right:4px solid transparent;border-left:4px solid transparent}.dropdown{position:relative}.dropdown-toggle:focus{outline:0}.dropdown-menu{position:absolute;top:100%;left:0;z-index:1000;display:none;float:left;min-width:160px;padding:5px 0;margin:2px 0 0;list-style:none;font-size:12px;text-align:left;background-color:#fff;border:1px solid #ccc;border:1px solid rgba(0,0,0,0.15);border-radius:4px;-webkit-box-shadow:0 6px 12px rgba(0,0,0,0.175);box-shadow:0 6px 12px rgba(0,0,0,0.175);background-clip:padding-box}.dropdown-menu.pull-right{right:0;left:auto}.dropdown-menu .divider{height:1px;margin:7.5px 0;overflow:hidden;background-color:#e5e5e5}.dropdown-menu>li>a{display:block;padding:3px 20px;clear:both;font-weight:normal;line-height:1.42857143;color:#333;white-space:nowrap}.dropdown-menu>li>a:hover,.dropdown-menu>li>a:focus{text-decoration:none;color:#262626;background-color:#f5f5f5}.dropdown-menu>.active>a,.dropdown-menu>.active>a:hover,.dropdown-menu>.active>a:focus{color:#fff;text-decoration:none;outline:0;background-color:#428bca}.dropdown-menu>.disabled>a,.dropdown-menu>.disabled>a:hover,.dropdown-menu>.disabled>a:focus{color:#777}.dropdown-menu>.disabled>a:hover,.dropdown-menu>.disabled>a:focus{text-decoration:none;background-color:transparent;background-image:none;filter:progid:DXImageTransform.Microsoft.gradient(enabled = false);cursor:not-allowed}.open>.dropdown-menu{display:block}.open>a{outline:0}.dropdown-menu-right{left:auto;right:0}.dropdown-menu-left{left:0;right:auto}.dropdown-header{display:block;padding:3px 20px;font-size:11px;line-height:1.42857143;color:#777;white-space:nowrap}.dropdown-backdrop{position:fixed;left:0;right:0;bottom:0;top:0;z-index:990}.pull-right>.dropdown-menu{right:0;left:auto}.dropup .caret,.navbar-fixed-bottom .dropdown .caret{border-top:0;border-bottom:4px solid;content:""}.dropup .dropdown-menu,.navbar-fixed-bottom .dropdown .dropdown-menu{top:auto;bottom:100%;margin-bottom:1px}@media (min-width:1px){.navbar-right .dropdown-menu{left:auto;right:0}.navbar-right .dropdown-menu-left{left:0;right:auto}}.nav{margin-bottom:0;padding-left:0;list-style:none}.nav>li{position:relative;display:block}.nav>li>a{position:relative;display:block;padding:10px 15px}.nav>li>a:hover,.nav>li>a:focus{text-decoration:none;background-color:#eee}.nav>li.disabled>a{color:#777}.nav>li.disabled>a:hover,.nav>li.disabled>a:focus{color:#777;text-decoration:none;background-color:transparent;cursor:not-allowed}.nav .open>a,.nav .open>a:hover,.nav .open>a:focus{background-color:#eee;border-color:#2e87ca}.nav .nav-divider{height:1px;margin:7.5px 0;overflow:hidden;background-color:#e5e5e5}.nav>li>a>img{max-width:none}.nav-tabs{border-bottom:1px solid #ddd}.nav-tabs>li{float:left;margin-bottom:-1px}.nav-tabs>li>a{margin-right:2px;line-height:1.42857143;border:1px solid transparent;border-radius:4px 4px 0 0}.nav-tabs>li>a:hover{border-color:#eee #eee #ddd}.nav-tabs>li.active>a,.nav-tabs>li.active>a:hover,.nav-tabs>li.active>a:focus{color:#555;background-color:#fff;border:1px solid #ddd;border-bottom-color:transparent;cursor:default}.nav-tabs.nav-justified{width:100%;border-bottom:0}.nav-tabs.nav-justified>li{float:none}.nav-tabs.nav-justified>li>a{text-align:center;margin-bottom:5px}.nav-tabs.nav-justified>.dropdown .dropdown-menu{top:auto;left:auto}@media (min-width:768px){.nav-tabs.nav-justified>li{display:table-cell;width:1%}.nav-tabs.nav-justified>li>a{margin-bottom:0}}.nav-tabs.nav-justified>li>a{margin-right:0;border-radius:4px}.nav-tabs.nav-justified>.active>a,.nav-tabs.nav-justified>.active>a:hover,.nav-tabs.nav-justified>.active>a:focus{border:1px solid #ddd}@media (min-width:768px){.nav-tabs.nav-justified>li>a{border-bottom:1px solid #ddd;border-radius:4px 4px 0 0}.nav-tabs.nav-justified>.active>a,.nav-tabs.nav-justified>.active>a:hover,.nav-tabs.nav-justified>.active>a:focus{border-bottom-color:#fff}}.nav-pills>li{float:left}.nav-pills>li>a{border-radius:4px}.nav-pills>li+li{margin-left:2px}.nav-pills>li.active>a,.nav-pills>li.active>a:hover,.nav-pills>li.active>a:focus{color:#fff;background-color:#428bca}.nav-stacked>li{float:none}.nav-stacked>li+li{margin-top:2px;margin-left:0}.nav-justified{width:100%}.nav-justified>li{float:none}.nav-justified>li>a{text-align:center;margin-bottom:5px}.nav-justified>.dropdown .dropdown-menu{top:auto;left:auto}@media (min-width:768px){.nav-justified>li{display:table-cell;width:1%}.nav-justified>li>a{margin-bottom:0}}.nav-tabs-justified{border-bottom:0}.nav-tabs-justified>li>a{margin-right:0;border-radius:4px}.nav-tabs-justified>.active>a,.nav-tabs-justified>.active>a:hover,.nav-tabs-justified>.active>a:focus{border:1px solid #ddd}@media (min-width:768px){.nav-tabs-justified>li>a{border-bottom:1px solid #ddd;border-radius:4px 4px 0 0}.nav-tabs-justified>.active>a,.nav-tabs-justified>.active>a:hover,.nav-tabs-justified>.active>a:focus{border-bottom-color:#fff}}.tab-content>.tab-pane{display:none}.tab-content>.active{display:block}.nav-tabs .dropdown-menu{margin-top:-1px;border-top-right-radius:0;border-top-left-radius:0}.navbar{position:relative;min-height:48px;margin-bottom:17px;border:1px solid transparent}@media (min-width:1px){.navbar{border-radius:4px}}@media (min-width:1px){.navbar-header{float:left}}.navbar-collapse{overflow-x:visible;padding-right:15px;padding-left:15px;border-top:1px solid transparent;box-shadow:inset 0 1px 0 rgba(255,255,255,0.1);-webkit-overflow-scrolling:touch}.navbar-collapse.in{overflow-y:auto}@media (min-width:1px){.navbar-collapse{width:auto;border-top:0;box-shadow:none}.navbar-collapse.collapse{display:block !important;height:auto !important;padding-bottom:0;overflow:visible !important}.navbar-collapse.in{overflow-y:visible}.navbar-fixed-top .navbar-collapse,.navbar-static-top .navbar-collapse,.navbar-fixed-bottom .navbar-collapse{padding-left:0;padding-right:0}}.navbar-fixed-top .navbar-collapse,.navbar-fixed-bottom .navbar-collapse{max-height:340px}@media (max-width:480px) and (orientation:landscape){.navbar-fixed-top .navbar-collapse,.navbar-fixed-bottom .navbar-collapse{max-height:200px}}.container>.navbar-header,.container-fluid>.navbar-header,.container>.navbar-collapse,.container-fluid>.navbar-collapse{margin-right:-15px;margin-left:-15px}@media (min-width:1px){.container>.navbar-header,.container-fluid>.navbar-header,.container>.navbar-collapse,.container-fluid>.navbar-collapse{margin-right:0;margin-left:0}}.navbar-static-top{z-index:1000;border-width:0 0 1px}@media (min-width:1px){.navbar-static-top{border-radius:0}}.navbar-fixed-top,.navbar-fixed-bottom{position:fixed;right:0;left:0;z-index:1030;-webkit-transform:translate3d(0, 0, 0);transform:translate3d(0, 0, 0)}@media (min-width:1px){.navbar-fixed-top,.navbar-fixed-bottom{border-radius:0}}.navbar-fixed-top{top:0;border-width:0 0 1px}.navbar-fixed-bottom{bottom:0;margin-bottom:0;border-width:1px 0 0}.navbar-brand{float:left;padding:15.5px 15px;font-size:15px;line-height:17px;height:48px}.navbar-brand:hover,.navbar-brand:focus{text-decoration:none}@media (min-width:1px){.navbar>.container .navbar-brand,.navbar>.container-fluid .navbar-brand{margin-left:-15px}}.navbar-toggle{position:relative;float:right;margin-right:15px;padding:9px 10px;margin-top:7px;margin-bottom:7px;background-color:transparent;background-image:none;border:1px solid transparent;border-radius:4px}.navbar-toggle:focus{outline:0}.navbar-toggle .icon-bar{display:block;width:22px;height:2px;border-radius:1px}.navbar-toggle .icon-bar+.icon-bar{margin-top:4px}@media (min-width:1px){.navbar-toggle{display:none}}.navbar-nav{margin:7.75px -15px}.navbar-nav>li>a{padding-top:10px;padding-bottom:10px;line-height:17px}@media (max-width:0){.navbar-nav .open .dropdown-menu{position:static;float:none;width:auto;margin-top:0;background-color:transparent;border:0;box-shadow:none}.navbar-nav .open .dropdown-menu>li>a,.navbar-nav .open .dropdown-menu .dropdown-header{padding:5px 15px 5px 25px}.navbar-nav .open .dropdown-menu>li>a{line-height:17px}.navbar-nav .open .dropdown-menu>li>a:hover,.navbar-nav .open .dropdown-menu>li>a:focus{background-image:none}}@media (min-width:1px){.navbar-nav{float:left;margin:0}.navbar-nav>li{float:left}.navbar-nav>li>a{padding-top:15.5px;padding-bottom:15.5px}.navbar-nav.navbar-right:last-child{margin-right:-15px}}@media (min-width:1px){.navbar-left{float:left !important}.navbar-right{float:right !important}}.navbar-form{margin-left:-15px;margin-right:-15px;padding:10px 15px;border-top:1px solid transparent;border-bottom:1px solid transparent;-webkit-box-shadow:inset 0 1px 0 rgba(255,255,255,0.1),0 1px 0 rgba(255,255,255,0.1);box-shadow:inset 0 1px 0 rgba(255,255,255,0.1),0 1px 0 rgba(255,255,255,0.1);margin-top:8.5px;margin-bottom:8.5px}@media (min-width:768px){.navbar-form .form-group{display:inline-block;margin-bottom:0;vertical-align:middle}.navbar-form .form-control{display:inline-block;width:auto;vertical-align:middle}.navbar-form .input-group{display:inline-table;vertical-align:middle}.navbar-form .input-group .input-group-addon,.navbar-form .input-group .input-group-btn,.navbar-form .input-group .form-control{width:auto}.navbar-form .input-group>.form-control{width:100%}.navbar-form .control-label{margin-bottom:0;vertical-align:middle}.navbar-form .radio,.navbar-form .checkbox{display:inline-block;margin-top:0;margin-bottom:0;vertical-align:middle}.navbar-form .radio label,.navbar-form .checkbox label{padding-left:0}.navbar-form .radio input[type="radio"],.navbar-form .checkbox input[type="checkbox"]{position:relative;margin-left:0}.navbar-form .has-feedback .form-control-feedback{top:0}}@media (max-width:0){.navbar-form .form-group{margin-bottom:5px}}@media (min-width:1px){.navbar-form{width:auto;border:0;margin-left:0;margin-right:0;padding-top:0;padding-bottom:0;-webkit-box-shadow:none;box-shadow:none}.navbar-form.navbar-right:last-child{margin-right:-15px}}.navbar-nav>li>.dropdown-menu{margin-top:0;border-top-right-radius:0;border-top-left-radius:0}.navbar-fixed-bottom .navbar-nav>li>.dropdown-menu{border-bottom-right-radius:0;border-bottom-left-radius:0}.navbar-btn{margin-top:8.5px;margin-bottom:8.5px}.navbar-btn.btn-sm{margin-top:10px;margin-bottom:10px}.navbar-btn.btn-xs{margin-top:13px;margin-bottom:13px}.navbar-text{margin-top:15.5px;margin-bottom:15.5px}@media (min-width:1px){.navbar-text{float:left;margin-left:15px;margin-right:15px}.navbar-text.navbar-right:last-child{margin-right:0}}.navbar-default{background-color:#fcfcfc;border-color:#e8e8e8}.navbar-default .navbar-brand{color:#0a76ba}.navbar-default .navbar-brand:hover,.navbar-default .navbar-brand:focus{color:#0a76ba;background-color:transparent}.navbar-default .navbar-text{color:#666}.navbar-default .navbar-nav>li>a{color:#666}.navbar-default .navbar-nav>li>a:hover,.navbar-default .navbar-nav>li>a:focus{color:#0a76ba;background-color:transparent}.navbar-default .navbar-nav>.active>a,.navbar-default .navbar-nav>.active>a:hover,.navbar-default .navbar-nav>.active>a:focus{color:#0a76ba;background-color:#fcfcfc}.navbar-default .navbar-nav>.disabled>a,.navbar-default .navbar-nav>.disabled>a:hover,.navbar-default .navbar-nav>.disabled>a:focus{color:#ccc;background-color:transparent}.navbar-default .navbar-toggle{border-color:#ddd}.navbar-default .navbar-toggle:hover,.navbar-default .navbar-toggle:focus{background-color:#ddd}.navbar-default .navbar-toggle .icon-bar{background-color:#888}.navbar-default .navbar-collapse,.navbar-default .navbar-form{border-color:#e8e8e8}.navbar-default .navbar-nav>.open>a,.navbar-default .navbar-nav>.open>a:hover,.navbar-default .navbar-nav>.open>a:focus{background-color:#fcfcfc;color:#0a76ba}@media (max-width:0){.navbar-default .navbar-nav .open .dropdown-menu>li>a{color:#666}.navbar-default .navbar-nav .open .dropdown-menu>li>a:hover,.navbar-default .navbar-nav .open .dropdown-menu>li>a:focus{color:#0a76ba;background-color:transparent}.navbar-default .navbar-nav .open .dropdown-menu>.active>a,.navbar-default .navbar-nav .open .dropdown-menu>.active>a:hover,.navbar-default .navbar-nav .open .dropdown-menu>.active>a:focus{color:#0a76ba;background-color:#fcfcfc}.navbar-default .navbar-nav .open .dropdown-menu>.disabled>a,.navbar-default .navbar-nav .open .dropdown-menu>.disabled>a:hover,.navbar-default .navbar-nav .open .dropdown-menu>.disabled>a:focus{color:#ccc;background-color:transparent}}.navbar-default .navbar-link{color:#666}.navbar-default .navbar-link:hover{color:#0a76ba}.navbar-default .btn-link{color:#666}.navbar-default .btn-link:hover,.navbar-default .btn-link:focus{color:#0a76ba}.navbar-default .btn-link[disabled]:hover,fieldset[disabled] .navbar-default .btn-link:hover,.navbar-default .btn-link[disabled]:focus,fieldset[disabled] .navbar-default .btn-link:focus{color:#ccc}.navbar-inverse{background-color:#222;border-color:#080808}.navbar-inverse .navbar-brand{color:#777}.navbar-inverse .navbar-brand:hover,.navbar-inverse .navbar-brand:focus{color:#fff;background-color:transparent}.navbar-inverse .navbar-text{color:#777}.navbar-inverse .navbar-nav>li>a{color:#777}.navbar-inverse .navbar-nav>li>a:hover,.navbar-inverse .navbar-nav>li>a:focus{color:#fff;background-color:transparent}.navbar-inverse .navbar-nav>.active>a,.navbar-inverse .navbar-nav>.active>a:hover,.navbar-inverse .navbar-nav>.active>a:focus{color:#fff;background-color:#080808}.navbar-inverse .navbar-nav>.disabled>a,.navbar-inverse .navbar-nav>.disabled>a:hover,.navbar-inverse .navbar-nav>.disabled>a:focus{color:#444;background-color:transparent}.navbar-inverse .navbar-toggle{border-color:#333}.navbar-inverse .navbar-toggle:hover,.navbar-inverse .navbar-toggle:focus{background-color:#333}.navbar-inverse .navbar-toggle .icon-bar{background-color:#fff}.navbar-inverse .navbar-collapse,.navbar-inverse .navbar-form{border-color:#101010}.navbar-inverse .navbar-nav>.open>a,.navbar-inverse .navbar-nav>.open>a:hover,.navbar-inverse .navbar-nav>.open>a:focus{background-color:#080808;color:#fff}@media (max-width:0){.navbar-inverse .navbar-nav .open .dropdown-menu>.dropdown-header{border-color:#080808}.navbar-inverse .navbar-nav .open .dropdown-menu .divider{background-color:#080808}.navbar-inverse .navbar-nav .open .dropdown-menu>li>a{color:#777}.navbar-inverse .navbar-nav .open .dropdown-menu>li>a:hover,.navbar-inverse .navbar-nav .open .dropdown-menu>li>a:focus{color:#fff;background-color:transparent}.navbar-inverse .navbar-nav .open .dropdown-menu>.active>a,.navbar-inverse .navbar-nav .open .dropdown-menu>.active>a:hover,.navbar-inverse .navbar-nav .open .dropdown-menu>.active>a:focus{color:#fff;background-color:#080808}.navbar-inverse .navbar-nav .open .dropdown-menu>.disabled>a,.navbar-inverse .navbar-nav .open .dropdown-menu>.disabled>a:hover,.navbar-inverse .navbar-nav .open .dropdown-menu>.disabled>a:focus{color:#444;background-color:transparent}}.navbar-inverse .navbar-link{color:#777}.navbar-inverse .navbar-link:hover{color:#fff}.navbar-inverse .btn-link{color:#777}.navbar-inverse .btn-link:hover,.navbar-inverse .btn-link:focus{color:#fff}.navbar-inverse .btn-link[disabled]:hover,fieldset[disabled] .navbar-inverse .btn-link:hover,.navbar-inverse .btn-link[disabled]:focus,fieldset[disabled] .navbar-inverse .btn-link:focus{color:#444}.breadcrumb{padding:8px 15px;margin-bottom:17px;list-style:none;background-color:#f5f5f5;border-radius:4px}.breadcrumb>li{display:inline-block}.breadcrumb>li+li:before{content:"/\00a0";padding:0 5px;color:#ccc}.breadcrumb>.active{color:#777}.clearfix:before,.clearfix:after,.dl-horizontal dd:before,.dl-horizontal dd:after,.form-horizontal .form-group:before,.form-horizontal .form-group:after,.nav:before,.nav:after,.navbar:before,.navbar:after,.navbar-header:before,.navbar-header:after,.navbar-collapse:before,.navbar-collapse:after{content:" ";display:table}.clearfix:after,.dl-horizontal dd:after,.form-horizontal .form-group:after,.nav:after,.navbar:after,.navbar-header:after,.navbar-collapse:after{clear:both}.center-block{display:block;margin-left:auto;margin-right:auto}.pull-right{float:right !important}.pull-left{float:left !important}.hide{display:none !important}.show{display:block !important}.invisible{visibility:hidden}.text-hide{font:0/0 a;color:transparent;text-shadow:none;background-color:transparent;border:0}.hidden{display:none !important;visibility:hidden !important}.affix{position:fixed;-webkit-transform:translate3d(0, 0, 0);transform:translate3d(0, 0, 0)}@-ms-viewport{width:device-width}.visible-xs,.visible-sm,.visible-md,.visible-lg{display:none !important}.visible-xs-block,.visible-xs-inline,.visible-xs-inline-block,.visible-sm-block,.visible-sm-inline,.visible-sm-inline-block,.visible-md-block,.visible-md-inline,.visible-md-inline-block,.visible-lg-block,.visible-lg-inline,.visible-lg-inline-block{display:none !important}@media (max-width:767px){.visible-xs{display:block !important}table.visible-xs{display:table}tr.visible-xs{display:table-row !important}th.visible-xs,td.visible-xs{display:table-cell !important}}@media (max-width:767px){.visible-xs-block{display:block !important}}@media (max-width:767px){.visible-xs-inline{display:inline !important}}@media (max-width:767px){.visible-xs-inline-block{display:inline-block !important}}@media (min-width:768px) and (max-width:991px){.visible-sm{display:block !important}table.visible-sm{display:table}tr.visible-sm{display:table-row !important}th.visible-sm,td.visible-sm{display:table-cell !important}}@media (min-width:768px) and (max-width:991px){.visible-sm-block{display:block !important}}@media (min-width:768px) and (max-width:991px){.visible-sm-inline{display:inline !important}}@media (min-width:768px) and (max-width:991px){.visible-sm-inline-block{display:inline-block !important}}@media (min-width:992px) and (max-width:1199px){.visible-md{display:block !important}table.visible-md{display:table}tr.visible-md{display:table-row !important}th.visible-md,td.visible-md{display:table-cell !important}}@media (min-width:992px) and (max-width:1199px){.visible-md-block{display:block !important}}@media (min-width:992px) and (max-width:1199px){.visible-md-inline{display:inline !important}}@media (min-width:992px) and (max-width:1199px){.visible-md-inline-block{display:inline-block !important}}@media (min-width:1200px){.visible-lg{display:block !important}table.visible-lg{display:table}tr.visible-lg{display:table-row !important}th.visible-lg,td.visible-lg{display:table-cell !important}}@media (min-width:1200px){.visible-lg-block{display:block !important}}@media (min-width:1200px){.visible-lg-inline{display:inline !important}}@media (min-width:1200px){.visible-lg-inline-block{display:inline-block !important}}@media (max-width:767px){.hidden-xs{display:none !important}}@media (min-width:768px) and (max-width:991px){.hidden-sm{display:none !important}}@media (min-width:992px) and (max-width:1199px){.hidden-md{display:none !important}}@media (min-width:1200px){.hidden-lg{display:none !important}}.visible-print{display:none !important}@media print{.visible-print{display:block !important}table.visible-print{display:table}tr.visible-print{display:table-row !important}th.visible-print,td.visible-print{display:table-cell !important}}.visible-print-block{display:none !important}@media print{.visible-print-block{display:block !important}}.visible-print-inline{display:none !important}@media print{.visible-print-inline{display:inline !important}}.visible-print-inline-block{display:none !important}@media print{.visible-print-inline-block{display:inline-block !important}}@media print{.hidden-print{display:none !important}} \ No newline at end of file diff --git a/data/core.telegram.org/css/core-widgets.css b/data/core.telegram.org/css/core-widgets.css deleted file mode 100644 index 6b86cfbf74..0000000000 --- a/data/core.telegram.org/css/core-widgets.css +++ /dev/null @@ -1,105 +0,0 @@ -.widget-accent-colors { - display: flex; - flex-wrap: nowrap; - justify-content: space-between; - max-width: 480px; - margin: 3px 0 0; -} -.widget-accent-colors .widget-accent-color-item { - position: relative; - flex-basis: 42px; - font-weight: normal; - text-align: center; - cursor: pointer; -} -.widget-accent-color-item input.radio { - position: absolute; - left: -5000px; -} -.widget-accent-color-item input.radio + .widget-color-circle:after { - position: absolute; - left: 0; - display: inline-block; - content: ''; - width: 100%; - height: 100%; - border-radius: 50%; - vertical-align: top; - background: url('data:image/svg+xml,%3Csvg height="15" viewBox="0 0 18 15" width="18" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%23fff" fill-rule="evenodd"%3E%3Crect height="8" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -5.753048 6.110913)" width="3" x="3" y="6"/%3E%3Crect height="3" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -2.081475 9.974874)" width="16" x="3" y="6"/%3E%3C/g%3E%3C/svg%3E') no-repeat center 11px; - transition: transform 0.12s linear; - transform: scale3d(0, 0, 1); -} -.widget-accent-color-item input.radio + .widget-color-circle.bordered, -.widget-accent-color-item input.radio:checked + .widget-color-circle-custom.bordered { - box-shadow: inset 0 0 0 1px #eaeaea; -} -.widget-accent-color-item input.radio + .widget-color-circle-custom.bordered { - border: none; -} -.widget-accent-color-item input.radio + .widget-color-circle.light:after { - background-image: url('data:image/svg+xml,%3Csvg height="15" viewBox="0 0 18 15" width="18" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%2315202b" fill-rule="evenodd"%3E%3Crect height="8" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -5.753048 6.110913)" width="3" x="3" y="6"/%3E%3Crect height="3" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -2.081475 9.974874)" width="16" x="3" y="6"/%3E%3C/g%3E%3C/svg%3E'); -} -.widget-accent-color-item input.radio:checked + .widget-color-circle:after { - transform: scale3d(1, 1, 1); -} -.widget-color-circle { - position: relative; - display: inline-block; - vertical-align: top; - width: 36px; - height: 36px; - border-radius: 50%; - background-color: #319BE6; - transition: background-color 0.12s ease, box-shadow 0.12s ease; -} -.widget-color-circle-custom { - background-color: #F5F5F5; - color: #F5F5F5; -} -.widget-accent-color-item input.radio + .widget-color-circle-custom:before { - position: absolute; - left: 0; - display: inline-block; - content: ''; - width: 100%; - height: 100%; - vertical-align: top; - background: url('data:image/svg+xml,%3Csvg height="14" viewBox="0 0 15 14" width="15" xmlns="http://www.w3.org/2000/svg"%3E%3Cpath d="m3.9468491 8.55631162c-1.3103539 0-2.36810946 1.04207749-2.36810946 2.33300928 0 1.0187474-.91566899 1.5553396-1.57873964 1.5553396.72622023.9487571 1.96553085 1.5553395 3.15747928 1.5553395 1.7445073 0 3.15747928-1.3920289 3.15747928-3.1106791 0-1.29093179-1.05775556-2.33300928-2.36810946-2.33300928zm10.8222602-7.28676572-1.0577555-1.04207749c-.3078543-.30329121-.8051572-.30329121-1.1130115 0l-7.07275356 6.96792112 2.170767 2.13859186 7.07275356-6.96792112c.3078543-.30329121.3078543-.79322316 0-1.09651437z" fill="%23bdbdbd"/%3E%3C/svg%3E') no-repeat center; - transition: opacity 0.12s ease; -} -.widget-color-label { - font-size: 12px; - line-height: 14px; - margin-top: 8px; - color: #333; -} -.widget-color-label-custom { - transition: opacity 0.12s ease; - position: absolute; - width: 100%; -} -.widget-accent-color-field-item { - transition: all .2s ease; - opacity: 0; -} -.widget-accent-color-field-item input.widget-accent-color-field { - font-size: 12px !important; - line-height: 14px !important; - text-transform: uppercase; - position: relative; - text-align: center; - margin-top: 3px !important; - padding: 5px 0 !important; - color: #222 !important; - width: 52px !important; -} -.widget-accent-color-item input.radio:checked ~ .widget-accent-color-field-item { - opacity: 1; -} -.widget-accent-color-item input.radio:checked ~ .widget-color-circle-custom { - background-color: currentColor !important; -} -.widget-accent-color-item input.radio:checked + .widget-color-circle-custom:before, -.widget-accent-color-item input.radio:checked ~ .widget-color-label-custom { - opacity: 0; -} diff --git a/data/core.telegram.org/css/telegram-extra.css b/data/core.telegram.org/css/telegram-extra.css deleted file mode 100644 index 6b408d1ae4..0000000000 --- a/data/core.telegram.org/css/telegram-extra.css +++ /dev/null @@ -1,246 +0,0 @@ -.telegram-passport-wrap { - overflow: hidden; -} -.telegram-passport-form { - position: relative; -} -.telegram-passport-form .control-label { - line-height: 20px; - padding-top: 11px; -} -.telegram-passport-header { - font-size: 18px; - line-height: 27px; -} -.telegram-passport-greeting { - margin-right: 10px; -} -.telegram-passport-greeting a, -.telegram-passport-greeting a:hover { - color: inherit; -} -.telegram-passport-logout { - font-size: 16px; - font-weight: normal; -} -.telegram-passport-login-wrap { - margin: 10px 0 50px; - text-align: center; -} -.telegram-passport-relogin-wrap { - margin: 10px 0 50px; - text-align: center; -} -.telegram-passport-pending { - padding: 20px 0 40px; - text-align: center; -} -.telegram-passport-block-header, -.telegram-passport-item { - border-bottom: 1px solid #e7e7e7; -} -.telegram-passport-block-header, -.telegram-passport-item-name, -.telegram-passport-item-value { - padding: 15px 0; - line-height: 20px; -} -.telegram-passport-block-header { - margin: 25px 0 0; -} -.telegram-passport-item-name { - margin-right: 15px; - margin-bottom: -5px; - padding-bottom: 0; - float: left; -} -.telegram-passport-item-files, -.telegram-passport-item-value { - clear: left; - font-weight: bold; -} -.telegram-passport-item-value { - transition: color .12s linear; -} -.telegram-passport-item-files { - padding: 6px 0; -} -.telegram-passport-item-file { - padding: 6px 0; - min-height: 60px; -} -.telegram-passport-item .telegram-passport-checkbox-right .checkbox-input { - margin: 0; -} -.telegram-passport-item .telegram-passport-checkbox-right { - float: right; - margin: 40px -5px 10px; - padding: 5px; -} -.telegram-passport-item-files .checkbox-item-block { - margin: 6px 0; -} -.telegram-passport-item-file .telegram-passport-checkbox-right { - margin: 9px -5px; -} -.telegram-passport-scan-thumb { - display: inline-block; - width: 64px; - height: 48px; - background: #f7f7f7 no-repeat center; - background-size: cover; - float: left; - border-radius: 3px; - margin-right: 15px; -} -.telegram-passport-scan-name { - display: inline-block; - font-size: 14px; - padding: 3px 0 0; - transition: color .12s linear; - color: #2e87ca; -} -.telegram-passport-scan-size { - font-size: 13px; - padding: 1px 0 0; - font-weight: normal; - transition: color .12s linear; - color: #999; -} -.telegram-passport-item-value, -.telegram-passport-scan-info { - margin-right: 42px; -} -.telegram-passport-item .checkbox-item-block .checkbox-label { - transition: color .12s linear; -} -.telegram-passport-item.item-rejected .telegram-passport-item-value, -.telegram-passport-item-file.item-rejected .telegram-passport-scan-name, -.telegram-passport-item-file.item-rejected .telegram-passport-scan-size, -.telegram-passport-item .checkbox-item-block.item-rejected .checkbox-label { - color: #c93c3c; -} - -.telegram-passport-item .checkbox-item-block .checkbox-input-icon:before { - border-color: #eb5454; - background-color: #eb5454; - background-position: -3px -119px; -} -.telegram-passport-item .checkbox-item-block input.checkbox:checked + .checkbox-input .ripple { - background-color: rgba(235, 84, 84, .2); -} -.telegram-passport-errors-wrap { - text-align: right; - margin: 20px 16px 0; -} -.btn.telegram-passport-errors { - font-size: 15px; - font-weight: 500; - line-height: 20px; - border-radius: 6px; - background-color: transparent; - padding: 8px 16px 10px; - margin: 4px -16px; - border: none; - color: #c93c3c; - position: relative; - z-index: 1; -} -.btn.telegram-passport-errors:hover { - background-color: #f7e3e3; -} -.btn.telegram-passport-errors:focus { - outline: none; -} -.btn.telegram-passport-errors:active { - box-shadow: none; -} -.telegram-passport-errors-icon { - display: inline-block; - vertical-align: top; - width: 18px; - height: 19px; - margin: 1px 12px 0 0; - background: url(/img/passport_bug.png) no-repeat 0 0; -} -@media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 192dpi) { - .telegram-passport-errors-icon { - background-image: url(/img/passport_bug_2x.png); - background-size: 18px 19px; - } -} -.telegram-passport-errors-sent { - font-size: 14px; - line-height: 20px; - padding: 13px 24px 0 0; - color: #999; - transition: opacity .12s linear; - opacity: 0; -} -.telegram-passport-errors-sent.shown { - opacity: 1; -} - -@media (min-width: 768px) { - .telegram-passport-login-wrap { - text-align: left; - } - .telegram-passport-relogin-wrap { - text-align: left; - margin: 50px 0 50px 240px; - } - .telegram-passport-item-files, - .telegram-passport-item-value { - clear: none; - margin-left: 240px; - } - .telegram-passport-item .telegram-passport-checkbox-right { - margin-top: 10px; - } - .telegram-passport-item-file .telegram-passport-checkbox-right { - margin: 9px -5px; - } - .telegram-passport-errors-wrap { - position: absolute; - right: 0; - margin: 50px 0 0; - } -} - -.telegram-passport-form .sub-control-label { - text-align: left; - margin: 11px 0 6px; -} -.telegram-passport-form .sub-control-label .radio-label { - font-weight: bold; -} -.telegram-passport-form .sub-control-label .radio-item + .radio-item, -.telegram-passport-form .sub-control-label .checkbox-item + .checkbox-item { - margin-left: 25px; -} -.telegram-passport-form label.control-label .radio-label { - font-weight: bold; -} -.passport-opt, -.passport-opt-col { - display: inline-block; - margin-left: 31px; - margin-top: -10px; -} -.passport-opt + .passport-opt, -.passport-opt-col + .passport-opt-col { - margin-left: 0; -} -@media (min-width: 992px) { - .passport-opt-col { - margin-left: 0; - margin-top: 0; - text-align: center; - } - .passport-opt-col .checkbox-label { - text-align: left; - } - .passport-opt-col .checkbox-item input.checkbox ~ .checkbox-label { - display: none; - } -} diff --git a/data/core.telegram.org/css/telegram.css b/data/core.telegram.org/css/telegram.css deleted file mode 100644 index 607f550a96..0000000000 --- a/data/core.telegram.org/css/telegram.css +++ /dev/null @@ -1,4866 +0,0 @@ -body { - font: 12px/18px "Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, Verdana, sans-serif; - /*-webkit-font-smoothing: antialiased;*/ -} -html.lang_rtl { - direction: rtl; -} - -a, -a:hover { - color: #0088cc; -} -a:focus { - text-decoration: none; -} -a:hover { - text-decoration: underline; -} - -.container { - margin-right: auto; - margin-left: auto; - padding-left: 15px; - padding-right: 15px; -} -@media (min-width: 768px) { - .container { - width: 750px; - } -} -@media (min-width: 992px) { - .container { - width: 970px; - } -} -@media (min-width: 1200px) { - .container { - width: 1170px; - } -} -.container-fluid { - margin-right: auto; - margin-left: auto; - padding-left: 15px; - padding-right: 15px; -} -.row { - margin-left: -15px; - margin-right: -15px; -} - -.container:before { - content: " "; - display: table; -} -.container:after { - content: " "; - display: table; - clear: both; -} - -@media (min-width: 1px) { - .lang_rtl .navbar-nav, - .lang_rtl .navbar-nav > li { - float: right; - } - .lang_rtl .navbar-right { - float: left !important; - } -} - -.tl_page_head { - margin-bottom: 0; -} -.navbar-tg .navbar-inner { - box-shadow: none; - -webkit-box-shadow: none; - border-bottom: 1px solid #e8e8e8; -} -.navbar-tg .nav a { - color: #0088cc; -} -.navbar-tg .nav a:hover, -.navbar-tg .nav .active a { - color: #0088cc; -} -.navbar-tg .nav > .active > a, -.navbar-tg .nav > .open > a, -.navbar-tg .nav > li > a:hover { - position: relative; -} -.navbar-tg .nav > li > a:after { - display: block; - height: 3px; - background: #179cde; - position: absolute; - border-radius: 2px 2px 0 0; - content: ""; - left: 4px; - right: 4px; - opacity: 0; - bottom: -1px; - -webkit-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - -moz-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - -ms-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - - transform-origin: bottom;; - transform: scaleX(0.3) scaleY(0); - -} -.navbar-tg .nav > .active > a:after, -.navbar-tg .nav > .open > a:after, -.navbar-tg .nav > li > a:hover:after { - opacity: 1; - transform: scaleX(1.0) scaleY(1.0); -} -.navbar-tg .nav > li > a, -.navbar-tg .nav > li > a:hover, -.navbar-tg .nav > li > a:focus { - background-color: transparent; -} - -.nav { - color: #a2a2a2; - font-size: 15px; - padding-left: 0; - padding-right: 0; -} - - -.caret { - display: inline-block; - background: url(../img/dropdown_1x.png) -2px -5px no-repeat; - border: 0; - width: 14px; - height: 6px; - margin-left: 2px; - vertical-align: middle; -} - - -.nav-pills > li > a { - font-size: 15px; - padding: 8px 17px; - border-radius: 0; -} - -.nav > li > a:hover, -.nav > li > a:focus { - background-color: #f0f6fa; - text-decoration: none; -} - -.nav .open > a, -.nav .open > a:hover, -.nav .open > a:focus, -.nav-pills > li.active > a, -.nav-pills > li.active > a:hover, -.nav-pills > li.active > a:focus { - box-shadow: none; - background-color: #1e98d4; - color: #FFF; - border: 0; -} - -.nav .open > a .caret, -.nav .open > a:hover .caret, -.nav .open > a:focus .caret { - background-position: -2px -15px; -} - -.dropdown-menu { - min-width: 177px; - padding: 0; - margin: 7px 0 0 0; - list-style: none; - font-size: 13px; - text-align: left; - background-color: #fff; - border-radius: 0; - border: 1px solid rgba(29,92,123,0.3); - box-shadow: 0 1px 1px rgba(20,60,83,0.1); - -webkit-box-shadow: 0 1px 1px rgba(20,60,83,0.1); -} -.dropdown-menu > li > a { - padding: 8px 18px; - margin: 0 -1px; - color: #08c; -} -.dropdown-menu > li > a:first-child { - margin-top: -1px; - padding-top: 9px; -} -.dropdown-menu > li > a:last-child { - margin-bottom: -1px; - padding-bottom: 9px; -} -.dropdown-menu > li > a:hover, -.dropdown-menu > li > a:focus, -.dropdown-menu > li.active > a { - text-decoration: none; - color: #FFF; - background-color: #1e98d4; -} - -#dev_page_content > ul:not(.nav), -#dev_page_content ul.bulleted, -#dev_page_content > ul:not(.nav) ul:not(.nav), -#dev_page_content > ol:not(.nav) ul:not(.nav), -#dev_page_content ul.bulleted ul.bulleted { - list-style-type: none; - padding-left: 10px; -} -.is_rtl #dev_page_content > ul:not(.nav), -.is_rtl #dev_page_content ul.bulleted, -.is_rtl #dev_page_content > ul:not(.nav) ul:not(.nav), -.is_rtl #dev_page_content > ol:not(.nav) ul:not(.nav), -.is_rtl #dev_page_content ul.bulleted ul.bulleted { - padding-right: 10px; - padding-left: 0; -} -#dev_page_content > ol { - padding-left: 25px; -} -#dev_page_content > ol > li { - padding-left: 5px; -} - - -#dev_page_content > ul:not(.nav) li, -#dev_page_content > ol:not(.nav) ul:not(.nav) li, -#dev_page_content ul.bulleted li { - background-image: url(../img/bullet.png?3); - background-repeat: no-repeat; - background-position: 0px 8px; - padding-left: 20px; -} - -.is_rtl #dev_page_content > ul:not(.nav) li, -.is_rtl #dev_page_content > ol:not(.nav) ul:not(.nav) li, -.is_rtl #dev_page_content ul.bulleted li { - background-position: 100% 8px; - padding-left: 0; - padding-right: 20px; -} - - - -.breadcrumb > li { - text-shadow: none; -} -.breadcrumb > li > .divider { - color: #c1d3e4; -} - -pre, code { - border: 0; -} -pre { - font-size: 13px; - color: #546172; - background: #ecf3f8; - border-radius: 0; -} -code { - background: #feeae4; - color: #c61717; - padding: 3px 5px; - border-radius: 0; -} -blockquote { - border-left-color: #179cde; -} -blockquote p { - font-size: 14px; - font-weight: normal; - line-height: 20px; - margin-bottom: 10px; -} -ul ul, ol ul, ul ol, ol ol { - margin-bottom: 8.5px; -} -.table td, .table th { - border-top-color: #eee; -} -h1, h2, h3, h4, h5, h6 { - font-weight: bold; - margin: 20px 0 10px 0; - position: relative; -} -h1 { - font-size: 20px; - margin-top: 32px; - margin-bottom: 12px; -} -h2 { - font-size: 20px; - margin-top: 32px; - margin-bottom: 12px; -} -h3 { - font-size: 20px; - margin-top: 32px; - margin-bottom: 10px; -} -h4 { - font-size: 16px; - margin-top: 29px; - margin-bottom: 7px; -} -h5 { - font-size: 16px; - margin-top: 29px; - margin-bottom: 7px; -} - -mark { - padding: .2em .4em; -} - -a.btn, -button.btn { - border-radius: 0; -} - -.form-control { - border-radius: 0; - box-shadow: none; -} - - -a.anchor { - text-decoration: none; - line-height: 1; - margin-left: -22px; - - cursor: default; - display: block; - position: absolute; - top: 0; - left: 0; - bottom: 0; - - border-top: 10px solid transparent; - margin-top: -10px; - -webkit-background-clip:padding-box; - -moz-background-clip:padding; - background-clip:padding-box; - outline: 0; -} -.is_rtl a.anchor { - margin-right: -22px; - margin-left: 0; -} - -a.anchor i.anchor-icon { - display: inline-block; - width: 18px; - height: 20px; - margin-top: 2px; - line-height: 14px; - vertical-align: text-top; - background: url(../img/link-icon.png) 0 0 no-repeat; - background-size: 17px 18px; - opacity: 0; - - cursor: pointer; - padding: 0; - position: relative; - z-index: 10; - - -webkit-transition: opacity .15s ease-in-out; - -moz-transition: opacity .15s ease-in-out; - -ms-transition: opacity .15s ease-in-out; - -o-transition: opacity .15s ease-in-out; - transition: opacity .15s ease-in-out; -} - -h1 a.anchor i.anchor-icon {margin-top: 2px;} -h2 a.anchor i.anchor-icon {margin-top: 2px;} -h3 a.anchor i.anchor-icon {margin-top: 2px;} -h4 a.anchor i.anchor-icon {margin-top: 0px;} - - -h1:hover a.anchor i.anchor-icon, -h2:hover a.anchor i.anchor-icon, -h3:hover a.anchor i.anchor-icon, -h4:hover a.anchor i.anchor-icon, -h5:hover a.anchor i.anchor-icon, -h6:hover a.anchor i.anchor-icon { - opacity: 0.6; -} -i.anchor-icon:hover { - opacity: 1 !important; -} - -.breadcrumb { - background-color: #ecf3fa; -} -.breadcrumb { - white-space: nowrap; - text-overflow: ellipsis; - overflow: hidden; -} -.breadcrumb li { - display: inline-block; - float: none; - white-space: nowrap; - text-overflow: ellipsis; -} -.breadcrumb > li + li:before { - padding: 0; - content: ""; -} -.icon-breadcrumb-divider { - display: inline-block; - background: url(../img/breadcrumb_divider_1x.png) 0 50% no-repeat; - width: 5px; - height: 18px; - line-height: 18px; - margin: 0 8px; - vertical-align: top; -} - -.slightly-pull-right { - float: right; -} -.slightly-pull-left { - float: left; -} - - -.back_to_top_wrap { - display: block; - pointer-events: none; - cursor: default; - position: fixed; - left: 0; - top: 0; - bottom: 0; - outline: none; - box-shadow: none; - opacity: 0; - /*display: none;*/ - transition: opacity ease-in-out 0.2s; - -webkit-transition: opacity ease-in-out 0.2s; - direction: ltr; -} -.back_to_top_wrap.is_rtl { - left: auto; - right: 0; - direction: rtl; -} -.back_to_top_wrap.back_to_top_shown { - cursor: pointer; - pointer-events: all; - /*display: block;*/ - opacity: 1; -} -.back_to_top_wrap:hover { - text-decoration: none; -} -.back_to_top { - font-size: 15px; - width: 120px; - text-align: center; - padding: 18px 15px 18px 7px; - transition: background ease-in-out 0.2s; - -webkit-transition: background ease-in-out 0.2s; -} -.back_to_top_wrap:hover .back_to_top { - background: #ecf3f8; - background: rgba(174, 198, 215, 0.2); -} -.icon-to-top { - display: inline-block; - background: url(../img/back_to_top_1x.png) 0 50% no-repeat; - width: 16px; - height: 7px; - margin-right: 12px; - margin-top: 7px; - vertical-align: text-top; -} -.back_to_top_wrap.is_rtl .icon-to-top { - margin-left: 12px; - margin-right: 0; -} - - -.navbar-tg .navbar-twitter a { - padding-top: 14.5px; - padding-bottom: 14.5px; -} - -.tl_main_page_container { - padding: 0; -} - -.tl_main_wrap { - margin-top: 17px; -} -.tl_main_wrap h3 { - color: #222222; - font-size: 23px; - font-weight: 500; -} -.tl_main_award { - width: 100px; - height: 100px; - display: block; - background: url(../img/SiteAward.gif) 0 0 no-repeat; - margin: 2px; -} -.tl_main_card_animated { - width: 160px; - margin: 0 auto; -} -.tl_main_card_animated div { - padding-top: 100%; -} - -.no_access_wrap { - color: #999; - padding: 100px 40px; - text-align: center; - font-size: 18px; -} - -.side_blog_wrap { - background: #ecf3fa; - padding: 15px 20px 20px; - font-size: 12px; - width: 200px; -} -.tl_blog_side_blog .side_blog_wrap { - width: 180px; -} -.side_blog_header { - display: block; - color: #0088cc; - font-weight: bold; - font-size: 16px; - margin-bottom: 15px; -} -a.side_blog_entry { - display: block; - margin-top: 10px; -} -a.side_blog_entry:hover { - text-decoration: none; -} -.side_blog_date { - color: #000; - font-weight: bold; -} -.side_blog_title { - color: #0088cc; -} -a.side_blog_entry:hover .side_blog_title { - text-decoration: underline; -} -.side_tour_entry .side_blog_title { - font-size: 14px; -} - -.tl_main_bottom_blog, -.tl_blog_bottom_blog { - display: none; -} -.tl_main_side_blog { - position: relative; -} -.tl_main_side_blog .side_blog_wrap { - position: absolute; - margin-top: 20px; - right: 137px; -} -.lang_rtl .tl_main_side_blog .side_blog_wrap { - left: 137px; - right: auto; -} -.tl_main_bottom_blog { - margin: 0px 15px 20px; -} -.side_blog_wrap { - background: none; - padding: 5px 17px 5px 0; - margin: 0 0 17px 26px; - display: flex; - flex-wrap: nowrap; - flex-direction: row; - justify-content: start; - align-items: stretch; - align-content: start -} -.tl_blog_bottom_blog .side_blog_wrap { - margin: 0 0 0 10px; -} -.tl_blog_side_blog { - position: relative; -} -.tl_blog_side_blog .side_blog_wrap { - position: absolute; - margin-top: 50px; - right: -200px; -} -.lang_rtl .tl_blog_side_blog .side_blog_wrap { - left: -200px; - right: auto; -} -.side_blog_wrap:before { - content: ' '; - display: block; - width: 5px; - background: #179cde; - border-radius: 5px; - overflow: hidden; - flex: 0 0 auto; - margin: 0 17px 0 0; -} -.lang_rtl .side_blog_wrap:before { - margin: 0 0 0 17px; -} - - - -.tl_main_logo_wrap { - max-width: 400px; - margin: 0 auto; - padding: 20px 0 20px; -} -a.tl_main_logo { - display: block; - line-height: 0; - text-decoration: none !important; -} -svg.tl_main_logo, -image.tl_main_logo, -img.tl_main_logo { - display: block; - width: 128px; - height: 128px; - margin: 0 auto; -} - -.tl_main_logo_title, -.tl_main_logo_title:hover { - font-size: 34px; - color: #222222; - text-align: center; - margin-top: 18px; - margin-bottom: 6px; - font-weight: normal; - letter-spacing: -2px; -} -.tl_main_logo_title_image { - width: 144px; - height: 36px; - background: url(../img/Telegram_1x.png) 0 0 no-repeat; - margin: 18px auto 6px; -} -.tl_main_logo_lead { - font-size: 20px; - line-height: 148%; - max-width: 285px; - margin: 0 auto; - color: #8c8c8c; - text-align: center; - padding: 1px 0 10px; - - font-family: "HelveticaNeue-Light", "Helvetica Neue Light", "Helvetica Light", Helvetica, Arial , Verdana, sans-serif; - font-weight: 300; -} - - -.tl_main_head_download { - margin: 6px auto 35px; - max-width: 798px; - text-align: center; -} -.tl_main_download_btn { - display: inline-block; - color: #FFF; - font-size: 16px; - background: #a19481; - border-radius: 4px; - padding: 10px 15px; - line-height: 35px; - overflow: hidden; - width: 220px; - margin: 5px 8px; - text-align: center; -} -.tl_main_download_btn:hover { - background-color: #a99d8b; - color: #FFF; - text-decoration: none; -} -.tl_main_download_btn:active { - background-color: #998e7e; -} - -.tl_main_download_mobile { - text-align: center; - max-width: 1028px; - margin: 0 auto; -} -.tl_main_download_link { - text-align: center; - display: inline-block; - height: 300px; - padding-top: 262px; - padding-bottom: 20px; - margin: 40px 0; - font-size: 15px; - max-width: 100%; - position: relative; -} -a.tl_main_download_link:hover { - text-decoration: none; -} -a.tl_main_download_link:after { - display: block; - height: 3px; - background: #179cde; - position: absolute; - border-radius: 2px; - content: ""; - left: 4px; - right: 4px; - opacity: 0; - bottom: -1px; - -webkit-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - -moz-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - -ms-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - - transform-origin: bottom;; - transform: scaleX(0.3) scaleY(0); -} -a.tl_main_download_link:hover:after { - opacity: 1; - transform: scaleX(1.0) scaleY(1.0); -} - -.tl_main_download_link_android { - width: 28.210116857923%; - min-width: 245px; -} -.tl_main_download_link_ios { - width: 42.9961%; - min-width: 350px; -} -.tl_main_download_link_tdesktop { - display: none; - min-width: 320px; - background: url(../img/SiteTDesktop.jpg) 50% 0 no-repeat; -} - -.tl_main_download_image__ios, -.tl_main_download_image__android { - display: block; - position: absolute; - top: 50%; - left: 50%; - transform-origin: 50% 50%; - opacity: 1.0; - pointer-events: none; - -webkit-transition: opacity .1s ease-in-out; - -moz-transition: opacity .1s ease-in-out; - -ms-transition: opacity .1s ease-in-out; - padding: 0; - border: 0; -} -.tl_main_download_image__ios { - margin: -150px 0 0 -152px; - width: 304px; - height: 240px; - background: url(../img/SiteiOS.jpg?2) 50% 0 no-repeat; -} -.tl_main_download_image__android { - margin: -150px 0 0 -152px; - width: 304px; - height: 240px; - background: url(../img/SiteAndroid.jpg?2) 50% 0 no-repeat; -} - -.tl_main_video_player { - display: block; - position: absolute; - top: 50%; - left: 50%; - transform-origin: 50% 50%; - opacity: 0; - pointer-events: none; - -webkit-transition: opacity .1s ease-in-out; - -moz-transition: opacity .1s ease-in-out; - -ms-transition: opacity .1s ease-in-out; - padding: 0; - border: 0; -} -.tl_main_video_player.video__init_retina { - display: none; -} -.tl_main_video_player__android { - margin: -150px 0 0 -96px; - width: 192px; - height: 240px; -} -.tl_main_video_player__ios { - margin: -150px 0 0 -152px; - width: 304px; - height: 240px; -} -.video_play .tl_main_video_player { - opacity: 1; -} - - - - -.tl_main_download_more_btn { - margin-bottom: 0; - font-weight: normal; - text-align: center; - vertical-align: middle; - cursor: pointer; - background-image: none; - border: 0; - white-space: nowrap; - padding: 10px 16px; - font-size: 15px; - line-height: 1.33; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - user-select: none; - color: #ffffff; - background-color: #318fd3; - margin-top: 5px; - display: none; - border-radius: 3px; -} -.tl_main_download_more_btn:hover { - color: #FFF; -} -.icon-arrow-more { - display: inline-block; - vertical-align: baseline; - width: 6px; - height: 11px; - background: url(../img/tl_arrow.png) 0 0 no-repeat; - margin-left: 10px; -} - -.tl_main_download_desktop_header { - text-align: center; -} -.tl_main_download_desktop_wrap1 { - height: 291px; - overflow: hidden; -} -.tl_main_download_desktop_wrap { - position: absolute; - left: 0; - right: 0; -} -.tl_main_download_desktop { - position: absolute; - left: 0; - right: 0; - min-width: 804px; - background: url(../img/SiteDesktop.jpg?2) 50% 19px no-repeat; - /*overflow: hidden;*/ -} - - - -.tl_main_download_desktop_links { - width: 595px; - margin: 0 auto; -} -.tl_main_download_desktop_link { - text-align: center; - display: inline-block; - padding: 270px 0 20px; - font-size: 15px; - vertical-align: top; - -webkit-transition: box-shadow .2s ease-in-out; - -moz-transition: box-shadow .2s ease-in-out; - -ms-transition: box-shadow .2s ease-in-out; - position: relative; - float: left; -} -.tl_main_download_desktop_link:hover { - text-decoration: none; -} -a.tl_main_download_desktop_link:hover { - text-decoration: none; -} -a.tl_main_download_desktop_link:after { - display: block; - height: 3px; - background: #179cde; - position: absolute; - border-radius: 2px; - content: ""; - left: 4px; - right: 4px; - opacity: 0; - bottom: -1px; - -webkit-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - -moz-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - -ms-transition: opacity .2s ease-in-out, transform .2s ease-in-out; - - transform-origin: bottom;; - transform: scaleX(0.3) scaleY(0); -} -a.tl_main_download_desktop_link:hover:after { - opacity: 1; - transform: scaleX(1.0) scaleY(1.0); -} -.tl_main_download_link_td { - width: 52%; - padding-left: 20px; - padding-right: 20px; -} -.tl_main_download_link_osx { - width: 48%; -} -.tl_main_body { - margin-top: 40px; - padding-top: 5px; -} -.tl_main_body_header { - text-align: center; - margin-top: 0; - padding-top: 20px; -} - -.icon-android, -.icon-ios, -.icon-wp { - display: inline-block; - vertical-align: text-top; - width: 25px; - height: 30px; - background: url(../img/SiteLogos.png) 0 0 no-repeat; - margin-right: 10px; -} -.lang_rtl .icon-android, -.lang_rtl .icon-ios, -.lang_rtl .icon-wp { - margin-right: 0; - margin-left: 10px; -} - -.icon-ios { - background-position: 0 0px; - height: 26px; - margin-top: -5px; -} -.icon-android { - background-position: 0 -46px; - height: 23px; - margin-top: -3px; -} -.icon-wp { - background-position: 0 -90px; - height: 20px; - margin-top: -1px; -} - -.icon { - display: inline-block; -} -.icon-twitter { - width: 21px; - height: 17px; - vertical-align: text-top; - background: url(../img/twitter.png) 0 0 no-repeat; - opacity: 0.9; -} -a:hover .icon-twitter { - opacity: 0.99; -} - -.app-icon { - display: inline-block; - width: 30px; - height: 30px; - line-height: 30px; - margin-right: 7px; - vertical-align: -9px; - background: no-repeat left; - background-size: cover; -} -.is_rtl .app-icon { - margin-right: 0; - margin-left: 7px; -} -.app-icon-android { - background-image: url(/img/app_icon_android.svg); -} -.app-icon-ios { - background-image: url(/img/app_icon_ios.svg); -} -.app-icon-macos { - background-image: url(/img/app_icon_macos.svg); -} -.app-icon-desktop { - background-image: url(/img/app_icon_desktop.svg); -} -.app-icon-webk { - background-image: url(/img/app_icon_webk.svg); -} -.app-icon-webz { - background-image: url(/img/app_icon_webz.svg); -} - - -.tl_main_cards { - max-width: 950px; - margin: 18px auto 0; - padding: 0; - display: flex; - flex-wrap: wrap; - justify-content: center; -} -.tl_main_card_cell { - position: relative; - min-height: 1px; - padding-left: 15px; - padding-right: 15px; - flex: 0 1 auto; - width: 100%; -} -@media (min-width: 768px) { - .tl_main_card_cell { - width: 50%; - } -} -@media (min-width: 992px) { - .tl_main_card_cell { - width: 33.33333%; - } -} - -.tl_main_card_wrap { - max-width: 260px; - margin: 0 auto; - padding: 20px 0 9px; -} -.tl_main_card { - background: url(../img/tl_card_fast.gif) 0 0 no-repeat; - background-size: 160px 160px; - width: 160px; - height: 160px; - margin: 0 auto; -} - -.tl_main_card_fast { - background-image: url(../img/tl_card_fast.gif); -} -.tl_main_card_powerful { - background-image: url(../img/tl_card_powerful.gif); -} -.tl_main_card_free { - background-image: url(../img/tl_card_free.gif); -} -.tl_main_card_secure { - background-image: url(../img/tl_card_secure.gif); -} -.tl_main_card_cloud { - background-image: url(../img/tl_card_cloud.gif); -} -.tl_main_card_private { - background-image: url(../img/tl_card_private.gif); -} -.tl_main_card_decentralized { - background-image: url(../img/tl_card_decentralized.gif); -} -.tl_main_card_open { - background-image: url(../img/tl_card_open.gif); -} -.tl_main_card_wecandoit { - background-image: url(../img/tl_card_wecandoit.gif); -} - -.tl_main_card_connect { - background-image: url(../img/tl_card_connect.gif); -} -.tl_main_card_coordinate { - background-image: url(../img/tl_card_coordinate.gif); -} -.tl_main_card_synchronize { - background-image: url(../img/tl_card_synchronize.gif); -} -.tl_main_card_build { - background-image: url(../img/tl_card_build.gif); -} -.tl_main_card_encrypt { - background-image: url(../img/tl_card_encrypt.gif); -} -.tl_main_card_send { - background-image: url(../img/tl_card_send.gif); -} -.tl_main_card_process { - background-image: url(../img/tl_card_process.gif); -} -.tl_main_card_destruct { - background-image: url(../img/tl_card_destruct.gif); -} -.tl_main_card_store { - background-image: url(../img/tl_card_store.gif); -} - -h3.tl_main_card_header { - color: #a19679; - text-align: center; - margin: 15px 0 6px; - font-size: 26px; - font-weight: normal; - letter-spacing: -1px; -} -.tl_main_cards_animated_wrap h3.tl_main_body_header { - padding: 0 10px; -} -.tl_main_cards_animated_wrap h3.tl_main_card_header { - color: #0088cc; -} -.tl_main_cards_animated_wrap { - padding-bottom: 20px; -} - -.tl_main_card_lead { - font-size: 15px; - line-height: 158%; - text-align: center; -} - -.tl_main_share { - margin: 24px auto 40px; - /*padding-bottom: 30px;*/ - max-width: 330px; - text-align: center; -} -.lang_rtl .tl_main_share { - max-width: none; -} -.tl_main_noshare { - height: 50px; -} -.tl_main_twitter_widget_wrap { - /*float: left;*/ - display: inline-block; -} -.tl_main_facebook_widget_wrap { - /*float: left;*/ - margin-right: 20px; - display: inline-block; -} -.fb_iframe_widget span { - vertical-align: baseline !important; -} - -.tl_blog_comments_widget { - margin: 0 -8px 40px; -} -.tl_blog_comments_widget iframe { - max-width: 100%; -} - -.tl_main_gplus_widget_wrap { - /*float: left;*/ - display: inline-block; -} - -.tl_twitter_share_btn { - display: inline-block; - border-radius: 16px; - background-color: #54a9eb; - cursor: pointer; - margin-right: 15px; - padding: 7px 17px; - color:#FFF; - font-weight: bold; -} -.lang_rtl .tl_twitter_share_btn { - margin-right: 0; - margin-left: 15px; -} -.tl_twitter_share_btn:hover, -.tl_twitter_share_btn:active, -.tl_twitter_share_btn:focus { - text-decoration: none; - color: #FFF; - outline: none; -} -.tl_twitter_share_cnt { - display: none; - color: #c4e3fb; -} - -.tl_blog_list_page_wrap { - max-width: 800px; - margin: 0 auto; -} -.tl_blog_list_page_wrap.tl_main_recent_news_wrap { - margin-top: 22px; - margin-bottom: 20px; -} -.tl_main_recent_news_header { - font-size: 16px; - font-weight: bold; - text-align: center; - margin-top: 42px; -} -.tlb_other_news_wrap .tl_main_recent_news_header { - margin-top: 22px; - font-size: 18px; -} -.tl_main_wrap .tl_main_recent_news_header { - margin-top: 66px; -} -.tl_main_download_mobile + .tl_main_recent_news_wrap .tl_main_recent_news_header, -.tl_main_download_mobile + .tl_main_recent_news_wrap { - margin-top: 12px; -} -.dev_blog_card_link_wrap:nth-child(odd) { - clear: left; -} -.dev_blog_card_link_wrap { - display: block; - max-width: 50%; - float: left; - padding: 15px 10px; -} -@media (max-width: 640px) { - .dev_blog_card_link_wrap { - max-width: 100%; - } -} -@media (min-width: 801px) { - .tl_main_recent_news_cards { - margin: 0 -15px; - } -} -.tlb_blog_page .dev_blog_card_link_wrap { - padding: 15px 0; -} -a.dev_blog_card_link_wrap:hover, -a.dev_blog_card_link_wrap:active, -a.dev_blog_card_link_wrap:focus { - text-decoration: none; -} -.dev_blog_card_image { - display: block; - max-width: 100%; - height: auto; - max-height: 220px; - margin: 0 auto; - -webkit-transition: opacity .2s ease-in-out; - -moz-transition: opacity .2s ease-in-out; - -ms-transition: opacity .2s ease-in-out; - opacity: 1; -} -.preload .dev_blog_card_image { - height: 220px; - max-height: initial; -} -a:hover .dev_blog_card_image { - opacity: 0.9; -} -.dev_blog_card_title { - margin: 12px 0 2px; - padding: 0 15px; - font-size: 16px; - line-height: 160%; -} -a.dev_blog_card_link_wrap:hover .dev_blog_card_title { - text-decoration: underline; -} -.dev_blog_card_lead { - color: #333; - font-size: 14px; - line-height: 160%; - padding: 0 15px; -} -.dev_blog_card_date { - margin-top: 4px; - font-size: 14px; - color: #888; - padding: 0 15px; -} -.tlb_blog_page .dev_blog_card_title, -.tlb_blog_page .dev_blog_card_lead, -.tlb_blog_page .dev_blog_card_date { - padding: 0 5px; -} -.pager_wrap { - margin-top: 40px; - clear: both; -} - - -.footer_wrap { - border-top: 1px solid #e8e8e8; - max-width: 925px; - margin: 10px auto 0; - padding: 28px 0 34px; -} -.footer_columns_wrap { - display: -ms-flexbox; - display: -webkit-flex; - display: flex; - -webkit-flex-direction: row; - -ms-flex-direction: row; - flex-direction: row; - -webkit-flex-wrap: nowrap; - -ms-flex-wrap: nowrap; - flex-wrap: nowrap; - -webkit-justify-content: space-between; - -ms-flex-pack: justify; - justify-content: space-between; - -webkit-align-content: stretch; - -ms-flex-line-pack: stretch; - align-content: stretch; - -webkit-align-items: stretch; - -ms-flex-align: stretch; - align-items: stretch; - - margin: 0 auto; - max-width: 800px; - padding-left: 0; -} -.footer_mobile { - display: none; -} -.footer_column { - flex: 0 1 auto; - align-self: auto; -} -.footer_column_telegram { - flex: 0 1 290px; -} -.footer_column:last-child { - padding-right: 0; -} -.footer_column:first-child { - padding-left: 0; -} -.footer_column h5 { - font-size: 14px; - margin-top: 0; - margin-bottom: 9px; -} -.footer_column h5 a { - color: inherit; -} -.footer_column ul, -.footer_column ul li { - list-style: none; - margin: 0; - padding: 0; -} -.footer_column ul li { - font-size: 14px; - line-height: 23px; -} -.footer_privacy_description { - padding-top: 3px; - font-size: 13px; - line-height: 160%; -} -.footer_privacy_description p { - margin-bottom: 6px; -} -.footer_telegram_description { - font-size: 13px; -} - - - -.tl_mission_wrap #dev_page_content, -.tl_mission_wrap #dev_page_content p { - font-family: "HelveticaNeue-Light", "Helvetica Neue Light", "Helvetica Light", Helvetica, Arial , Verdana, sans-serif; - font-weight: 300; - line-height: 160%; - font-size: 16px; -} - - - -/* Team */ -#dev_page_content.tl_team_wrap, -#dev_page_content.tl_team_wrap p { - line-height: 1.6; -} -.tl_team_lead { - margin-bottom: 30px; -} -.tl_team_member { - min-height: 120px; - position: relative; - margin-bottom: 30px; -} -.tl_team_member_photo_wrap { - position: absolute; - // float: left; - // margin-right: 25px; -} -.tl_team_member_photo { - width: 120px; - height: 120px; - display: block; - background: url('../img/team-sprite.png') 0 0 no-repeat; - background-size: 120px 1810px; -} - -.tl_team_member_pavel .tl_team_member_photo { - background-position: 0 0; -} -.tl_team_member_nikolay .tl_team_member_photo { - background-position: 0 -130px; -} -.tl_team_member_aliaksei .tl_team_member_photo { - background-position: 0 -260px; -} -.tl_team_member_vitalik .tl_team_member_photo { - background-position: 0 -390px; -} -.tl_team_member_arseny .tl_team_member_photo { - background-position: 0 -520px; -} -.tl_team_member_igor .tl_team_member_photo { - background-position: 0 -650px; -} -.tl_team_member_drklo .tl_team_member_photo { - background-position: 0 -780px; -} -.tl_team_member_peter .tl_team_member_photo { - background-position: 0 -910px; -} -.tl_team_member_john .tl_team_member_photo { - background-position: 0 -1040px; -} -.tl_team_member_kolar .tl_team_member_photo { - background-position: 0 -1170px; -} -.tl_team_member_ilya .tl_team_member_photo { - background-position: 0 -1300px; -} -.tl_team_member_igor1 .tl_team_member_photo { - background-position: 0 -1690px; -} -.tl_team_member_mike .tl_team_member_photo { - background-position: 0 -1560px; -} -.tl_team_member_grisha .tl_team_member_photo { - background-position: 0 -1430px; -} - - -.tl_team_member_name { - margin-left: 146px; -} -.tl_team_member_body { - margin-left: 146px; -} - -.tl_team_member_name { - margin-top: 5px; - font-size: 17px; -} -.tl_team_member_awards { - margin-top: 20px; - margin-bottom: 18px; - color: #0088cc; - font-size: 15px; -} -.tl_team_member_experience, -.tl_team_member_awards_list { - line-height: 1.8; -} -.tl_team_member_description { - margin-top: 20px; -} - - - -/* Core / dev */ - -.dev_page { - background: #FFF; - min-height: 500px; -} -#dev_page_content_wrap { - padding: 20px 0; - max-width: 800px; - margin: 0 auto; - direction: ltr; -} -#dev_page_content_wrap.is_rtl { - direction: rtl; -} -#dev_page_content, -#dev_page_content p { - font-size: 14px; - line-height: 1.5; -} -#dev_page_content img.emoji { - vertical-align: top; - -webkit-user-drag: none; - user-drag: none; - cursor: text; -} -.dev_page_bread_crumbs .breadcrumb { - margin-bottom: 10px; - border-radius: 0; -} -#dev_page_title { - position: static; -} - -.dev_page_head { - margin-bottom: 0; -} -.dev_page_head .dev_page_head_logo { - margin-left: 0; -} -#dev_page_content_wrap blockquote { - padding: 5px 17px; -} -#dev_page_content_wrap pre { - overflow-x: auto; - border-radius: 0; -} - -#dev_page_content_wrap pre::-webkit-scrollbar { - visibility: visible; - display: block; - height: 15px; -} -#dev_page_content_wrap pre::-webkit-scrollbar-track:horizontal { - background: rgba(93, 144, 177, 0.2); - border-radius: 0; - height: 15px; -} -#dev_page_content_wrap pre::-webkit-scrollbar-thumb:horizontal { - background: rgba(93, 144, 177, 0.4); - border-radius: 0; - height: 15px; -} - -#dev_page_content_wrap .richcode { - display: block; - padding: 9.5px; - margin: 0 0 10px; - font-size: 13px; - line-height: 20px; - -webkit-border-radius: 4px; - -moz-border-radius: 4px; - border-radius: 4px; - - color: #546172; - background: #ecf3f8; - - font-family: Monaco,Menlo,Consolas,"Courier New",monospace; -} -#dev_page_content_wrap .richcode code { - background: #FFF; -} -.richcode p:last-child { - margin-bottom: 0; -} - -#dev_page_content_wrap pre code { - overflow-wrap: normal; - white-space: pre; -} -#dev_page_content_wrap a.current_page_link { - color: #468847; - text-decoration: underline; -} - -#dev_page_content_wrap a.nonexisting_page_link { - color: #FF0000; - text-decoration: underline; -} - -.dev_side_image { - max-width: 200px; - float: right; - padding: 0 0 0 20px; -} -.dev_side_image img { - max-width: 180px; -} -.dev_side_image picture { - max-width: 180px; -} - - -#dev_page_content_wrap pre.page_scheme { - margin: 20px 0 30px; -} -.dev_page_edit_form { - border-top: 1px solid #DDD; - padding-top: 50px; - max-width: 800px; - margin: 30px auto 0; - direction: ltr; -} -.dev_page_edit_form .CodeMirror { - font-size: 14px; - line-height: 20px; - font-family: Monaco, Menlo, Consolas, "Courier New", monospace; - border: 1px solid #eee; - height: auto; - position: relative; - - margin-bottom: 9px; - color: #555555; - border: 1px solid #ccc; - -webkit-border-radius: 3px; - -moz-border-radius: 3px; - border-radius: 3px; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - -moz-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - -webkit-transition: border linear 0.2s, box-shadow linear 0.2s; - -moz-transition: border linear 0.2s, box-shadow linear 0.2s; - -ms-transition: border linear 0.2s, box-shadow linear 0.2s; - -o-transition: border linear 0.2s, box-shadow linear 0.2s; - transition: border linear 0.2s, box-shadow linear 0.2s; -} - -.dev_page_edit_form .CodeMirror-focused { - border-color: rgba(82, 168, 236, 0.8); - outline: 0; - outline: thin dotted \9; - - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 8px rgba(82, 168, 236, 0.6); - -moz-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 8px rgba(82, 168, 236, 0.6); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 8px rgba(82, 168, 236, 0.6); -} - -.dev_page_edit_form .CodeMirror-scroll { - overflow-y: hidden; - overflow-x: auto; -} - -.dev_page_edit_form .CodeMirror pre { - white-space: pre-wrap; - word-break: break-all; - word-wrap: break-word; -} - -.dev_page_edit_form #dev_page_diff .CodeMirror { - font-size: 12px; - margin-bottom: 0; -} -#dev_page_diff .CodeMirror-merge, -#dev_page_diff .CodeMirror-merge .CodeMirror { - height: auto; -} -#dev_page_diff .CodeMirror-merge-2pane { - display: flex; - border: 0; - margin-bottom: 9px; -} -#dev_page_diff .CodeMirror-merge-2pane .CodeMirror-merge-pane { - width: 48%; -} -#dev_page_diff .CodeMirror-merge-2pane .CodeMirror-merge-gap { - height: auto; - width: 4%; -} -#dev_page_diff .CodeMirror-merge-pane-rightmost { - position: static; - right: auto; -} -#dev_page_diff .CodeMirror-merge-scrolllock-wrap { - display: none; -} -#dev_page_diff .CodeMirror-merge-left .CodeMirror { - background: rgba(0,0,0,0.06); -} -#dev_page_diff .CodeMirror-merge-l-inserted, -#dev_page_diff .CodeMirror-merge-l-deleted { - background: none; -} -#dev_page_diff.dev_page_diff__wcolor .CodeMirror-merge-l-inserted { - /*background: rgba(0,200,0,0.18);*/ - background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAMAAAACCAYAAACddGYaAAAAGUlEQVQI12MwuCXy3+CWyH8GBgYGJgYkAABZbAQ9ELXurwAAAABJRU5ErkJggg==); - background-position: bottom left; - background-repeat: repeat-x; - background-color: #dfd; - /*border: 1px solid #4e4;*/ -} -#dev_page_diff.dev_page_diff__wcolor .CodeMirror-merge-l-deleted { - /*background: rgba(200,0,0,0.18);*/ - background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAMAAAACCAYAAACddGYaAAAAGUlEQVQI12M4Kyb2/6yY2H8GBgYGJgYkAABURgPz6Ks7wQAAAABJRU5ErkJggg==); - background-position: bottom left; - background-repeat: repeat-x; - background-color: #fdd; - /*border: 1px solid #e44;*/ -} - -.table-msg-schema td { - text-align: center; -} -.table-msg-schema>thead>tr>th, -.table-msg-schema>tbody>tr>th, -.table-msg-schema>tfoot>tr>th, -.table-msg-schema>thead>tr>td, -.table-msg-schema>tbody>tr>td, -.table-msg-schema>tfoot>tr>td { - border: 1px solid #d5d5d5; -} - -#dev_upload_btn { - cursor: pointer; - overflow: hidden; - position: relative; -} -.dev_upload_input { - cursor: pointer; - font-size: 72px !important; - opacity: 0.01; - position: absolute; - z-index: 100; - margin: 0; - padding: 0; - top: 0; - right: 0; -} - - -.app_edit_page { - width: 700px; - margin: 40px auto; -} -.app_lock_tt { - padding: 3px; - display: inline-block; -} -.app_lock_text { - font-size: 13px; -} - -.tg-table-stats { - font-size: 12px; -} -.tg-table-stats th a.active { - color: inherit; -} - -.dev_side_nav_wrap { - position: relative; -} -.dev_side_nav { - position: absolute; - width: 200px; - right: -200px; - z-index: 1; -} -.is_rtl .dev_side_nav { - left: -200px; - right: auto; -} -.is_rtl .dev_side_nav .nav { - padding-right: 0; - padding-left: 0; - padding-right: 0; -} -.dev_side_nav > ul { - width: 200px; - background: none; - padding: 10px 0 10px; -} -.dev_side_nav > ul::-webkit-scrollbar { - display: none; -} -.dev_side_nav > ul.affix-top { - position: relative; -} -.dev_side_nav > ul.affix { - position: fixed; - top: 0; - max-height: 100%; - overflow-y: scroll; -} -.dev_side_nav > ul.affix-bottom { - position: relative; - height: auto; - overflow-y: scroll; -} -.dev_side_nav li { - float: none !important; -} -.dev_side_nav li a { - border-left: 2px solid transparent; - padding: 10px 10px; - background: none !important; - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} -.is_rtl .dev_side_nav li a { - border-right: 2px solid transparent; - border-left: 0; -} -.dev_side_nav li a { - display: block; - font-size: 13px; - font-weight: 500; - padding: 4px 20px 4px 18px; - font-weight: 700; - background-color: transparent; -} -.is_rtl .dev_side_nav li a { - padding: 4px 18px 4px 20px; -} -.dev_side_nav li li a { - padding-left: 15px; - padding: 1px 18px 1px 30px; - font-size: 12px; - font-weight: 400; -} -.is_rtl .dev_side_nav li li a { - padding: 1px 30px 1px 18px; -} -.dev_side_nav li a:hover { - border-color: rgba(23, 156, 222, 0.6); -} -.dev_side_nav li.active > a { - border-color: #179cde; -} -.dev_side_nav li ul { - display: none; -} -.dev_side_nav li.active ul { - display: block; -} - - -/* Core / dev end*/ - - - -/* Support */ -.support_wrap { - max-width: 800px; - background: #FFF; - margin: 0 auto; - padding: 20px 0; -} -.support_submit { -} - - -/* FAQ */ -.twitter_timeline_wrap { - width: 300px; - padding-top: 14px; -} -.is_rtl .dev_layer_select .dropdown-menu { - right: auto; - left: 0; -} - -.is_rtl { - direction: rtl; -} - -.is_rtl blockquote { - padding: 0 15px 0 0; - margin: 0 0 20px; - border-left: 0; - border-right: 5px solid #179cde; -} - -.is_rtl .pull-right, -.is_rtl .slightly-pull-right { - float: left; -} -.is_rtl .pull-left, -.is_rtl .slightly-pull-left { - float: right; -} - -.is_rtl .anchor { - left: auto; - right: 0; -} - -.top_lang_select.tlb_top_lang_select { - float: right; - margin: -4px -5px -4px 0; -} -.lang_rtl .top_lang_select.tlb_top_lang_select { - float: left; -} -.top_lang_select .dropdown-toggle { - display: block; - text-align: center; - padding-top: 15.5px; - padding-bottom: 15.5px; - font-size: 15px; - line-height: 17px; -} -.top_lang_select.tlb_top_lang_select a.dropdown-toggle { - padding: 8px 6px 8px 8px; - border-radius: 6px; - /*transition: background-color ease-in-out 0.2s, color ease-in-out 0.2s;*/ -} -.navbar-tg .top_lang_select.open a.dropdown-toggle:active, -.navbar-tg .top_lang_select.open a.dropdown-toggle:hover, -.navbar-tg .top_lang_select.open a.dropdown-toggle { - background: transparent; - color: #0088cc; -} -.top_lang_select.tlb_top_lang_select.open a.dropdown-toggle:hover, -.top_lang_select.tlb_top_lang_select.open a.dropdown-toggle:active, -.top_lang_select.tlb_top_lang_select.open a.dropdown-toggle { - background-color: #3faee8; - color: #fff; -} -.dev_top_lang_icon { - display: inline-block; - width: 16px; - height: 16px; - vertical-align: top; - line-height: 100%; - margin-right: 4px; - background: url("data:image/svg+xml;utf8,") no-repeat 0 0; -} -.lang_rtl .dev_top_lang_icon { - margin-right: 0; - margin-left: 4px; -} -.tlb_top_lang_select.open .dev_top_lang_icon { - background: url("data:image/svg+xml;utf8,") no-repeat 0 0; -} -.navbar-nav > li.top_lang_select > .dropdown-menu, -.top_lang_select.tlb_top_lang_select > .dropdown-menu { - width: 280px; - min-width: 280px; - border-radius: 8px; - padding: 14px; - right: 0; - left: auto; - margin-top: 4px; - box-shadow: 1px 1px 3px 1px rgba(0, 0, 0, .10); - border-color: #e8e8e8; - - transition: transform ease-in-out 0.15s, opacity ease-out 0.15s; - transform-origin: top right; - transform: scaleX(0.15) scaleY(0.15); - display: block; - opacity: 0; - pointer-events: none; -} -.lang_rtl .navbar-nav > li.top_lang_select > .dropdown-menu, -.lang_rtl .top_lang_select.tlb_top_lang_select > .dropdown-menu { - transform-origin: top left; - right: auto; - left: 0; -} -body.preload .top_lang_select > .dropdown-menu, -.top_lang_select.tlb_top_lang_select > .dropdown-menu { - transition: none !important; -} -.navbar-nav > li.top_lang_select.open > .dropdown-menu, -.top_lang_select.tlb_top_lang_select.open > .dropdown-menu { - transform: scaleX(1.0) scaleY(1.0); - opacity: 1; - pointer-events: all; -} -.navbar-nav > li.top_lang_select > .dropdown-menu.dropdown-menu--short, -.top_lang_select.tlb_top_lang_select > .dropdown-menu.dropdown-menu--short { - width: 155px; - min-width: 155px; -} -@media (max-width: 640px) { - .navbar-nav > li.dev_top_lang_select > .dropdown-menu { - left: 0; - right: auto; - } -} -.top_lang_select .dropdown-menu li { - float: left; - display: block; - width: 125px; -} -.lang_rtl .top_lang_select .dropdown-menu li { - float: right; - text-align: right; -} - -.top_lang_select .dropdown-menu li.divider { - float: none; - clear: left; - width: auto; - margin: 6px 0; -} -.top_lang_select .dropdown-menu li a { - display: inline-block; - font-size: 13px; - max-width: 125px; - padding: 9px 10px; - border-radius: 4px; - white-space: normal; - white-space: nowrap; - text-overflow: ellipsis; - overflow: hidden; - line-height: 15px; - margin: 0; -} -.top_lang_select .dropdown-menu li.long a { - font-size: 12px; -} -.top_lang_select .dropdown-menu li.missing a { - color: #777; -} -.navbar-nav > .top_lang_select .dropdown-menu li a:hover { - background: #e8f3fa; - color: #0088cc; -} -.top_lang_select.tlb_top_lang_select .dropdown-menu li a:hover { - background: #3faee8; - color: #fff; -} -.top_lang_select .dropdown-menu li.chosen a, -.top_lang_select .dropdown-menu li.chosen a:hover { - color: #000; - background: #fff; -} -.top_lang_select .minicaret { - display: inline-block; - width: 0; - height: 0; - margin-left: 2px; - vertical-align: middle; - border-top: 4px solid; - border-right: 4px solid transparent; - border-left: 4px solid transparent; -} -.lang_rtl .top_lang_select .minicaret { - margin-left: 0; - margin-right: 2px; -} - -#login_widget_config { - margin: 40px auto; -} -.form-group .dropdown + .dropdown { - margin-left: 15px; -} -.dropdown-label { - margin-right: 7px; - display: inline-block; - max-width: 300px; - white-space: nowrap; - text-overflow: ellipsis; - overflow: hidden; - vertical-align: top; -} -.dropdown-label .muted { - color: #999; -} - -.textfield-item input.form-control, -.form-control-dropdown-select, -.form-control-static-item, -.textfield-item-placeholder { - font-size: 14px; - line-height: 20px; - font-weight: normal; -} -.textfield-item input.form-control, -.form-control-dropdown-select { - padding: 11px 0 10px; - border: none; - height: auto; - resize: none; - color: inherit; - background: transparent; - border-bottom: 1px solid #e0e0e0; - box-shadow: none; -} -.textfield-item input.form-control:focus { - box-shadow: none; -} -.form-control-static-item { - padding: 11px 0; -} - -.textfield-item { - display: block; - position: relative; -} -.textfield-item-underline { - display: block; - position: absolute; - bottom: 0; - left: 50%; - right: 50%; - height: 2px; - background: #39ade7; - transition: opacity .2s ease-out, left 0s .2s linear, right 0s .2s linear; - opacity: 0; -} -.textfield-item input.form-control:focus ~ .textfield-item-underline { - transition: left .2s ease-out, right .2s ease-out; - left: 0; - right: 0; - opacity: 1; -} -.textfield-item-placeholder { - bottom: 0; - color: #ccc; - color: rgba(0,0,0,.26); - left: 0; - right: 0; - pointer-events: none; - position: absolute; - display: block; - top: 11px; - width: 100%; - overflow: hidden; - white-space: nowrap; - text-align: left -} - -.textfield-item input.form-control::-webkit-input-placeholder { - color: #999; - color: rgba(0,0,0,.42); -} -.textfield-item input.form-control::-moz-placeholder { - color: #999; - color: rgba(0,0,0,.42); -} -.textfield-item input.form-control:-ms-input-placeholder { - color: #999; - color: rgba(0,0,0,.42); -} -.textfield-item input.form-control:focus::-webkit-input-placeholder { - color: #ccc; - color: rgba(0,0,0,.26); -} -.textfield-item input.form-control:focus::-moz-placeholder { - color: #ccc; - color: rgba(0,0,0,.26); -} -.textfield-item input.form-control:focus:-ms-input-placeholder { - color: #ccc; - color: rgba(0,0,0,.26); -} -.textfield-item-error { - color: #d45a58; - position: absolute; - font-size: 14px; - line-height: 19px; - min-height: 19px; - margin: 5px 0 -19px; - background: #fff; - width: 100%; - padding-bottom: 7px; - visibility: hidden; - display: block; -} -.textfield-item.is-invalid .textfield-item-error { - visibility: visible -} -.textfield-item.is-invalid input.form-control { - border-bottom: 1px solid #d50000; -} -.textfield-item.is-invalid .textfield-item-underline { - background: #d50000; -} -.control-label-item, -.form-telegram .control-label { - text-align: right; - margin-bottom: 0; - line-height: 20px; - padding-top: 11px; -} -.form-telegram .help-block { - font-size: 13px; - color: #808080; - margin-top: 10px; - margin-bottom: 5px; -} -.form-telegram .form-group { - margin-bottom: 20px; -} -.form-telegram textarea.form-control { - margin-top: 7px; -} -.form-telegram .form-control[readonly] { - cursor: text; - background: #fff; -} -.form-telegram .form-control[readonly]:focus { - border: 1px solid #ccc; - box-shadow: none; -} -.form-control-dropdown { - position: relative; -} -.form-control-dropdown.has-items:before { - content: ''; - position: absolute; - display: inline-block; - margin: 16px 10px 0; - width: 14px; - height: 9px; - background: url(/img/rc_icons.png?1) no-repeat -3px -144px; - right: 0; - top: 0; -} -.form-control-dropdown .form-control-dropdown-search { - position: absolute; - top: 0; - left: 0; - right: 0; - visibility: hidden; - opacity: 0; -} -.form-control-dropdown.open .form-control-dropdown-search { - visibility: visible; - opacity: 1; -} -.form-control-dropdown.open .form-control-dropdown-select { - visibility: hidden; - opacity: 0; -} -.form-control-dropdown-select { - color: #ccc; - color: rgba(0,0,0,.26); - cursor: pointer; - position: relative; - white-space: nowrap; - text-overflow: ellipsis; - overflow: hidden; -} -.form-control-dropdown-select:focus { - outline: none; -} -.form-control-dropdown-select.is-dirty { - color: inherit; -} -.form-control-dropdown-button { - position: absolute; - display: inline-block; - transition: all .2s ease; - border: none; - padding: 0; - background: none !important; - visibility: hidden; - opacity: 0; - top: 0; - right: 0; -} -.form-control-dropdown-button:active { - box-shadow: none !important; -} -.form-control-dropdown-button:before { - content: ''; - display: inline-block; - margin: 16px 10px; - width: 14px; - height: 9px; - background: url(/img/rc_icons.png?1) no-repeat -3px -144px; - vertical-align: top; -} -.form-control-dropdown-list { - position: absolute; - left: -15px; - right: -15px; - margin: -2px 0; - background: #fff; - text-align: left; - padding: 7px 0; - box-shadow: 0 0 2px 1px rgba(0, 0, 0, .15); - border: none; - transition: all .2s ease; - visibility: hidden; - opacity: 0; - max-height: 220px; - overflow: auto; - overflow-x: hidden; - -webkit-overflow-scrolling: touch; - z-index: 10; -} -.form-control-dropdown.has-items .form-control-dropdown-button, -.form-control-dropdown.has-items.open .form-control-dropdown-list { - visibility: visible; - opacity: 1; -} -.form-control-dropdown-list-item, -.form-control-dropdown-list-no-results { - font-size: 14px; - line-height: 18px; - padding: 8px 15px; - cursor: pointer; -} -.form-control-static-item .small, -.form-control-dropdown-select .small, -.form-control-dropdown-list-item .small { - font-size: 13px; - line-height: 16px; - color: #a8a8a8; - padding-left: 8px; -} -.form-control-dropdown-search .form-control-dropdown-list-item:hover { - background: none; -} -.form-control-dropdown-search .form-control-dropdown-list-item.selected, -.form-control-dropdown-list-item:hover { - background: #f2f2f2; -} -.form-control-dropdown-list-no-results { - color: #a8a8a8; - cursor: auto; -} -.form-control-dropdown-select, -.form-control-dropdown input.form-control { - padding-right: 33px; -} -.help-block-item { - display: block; - font-size: 14px; - line-height: 18px; - margin-top: 5px; - margin-bottom: 0; - color: #a8a8a8; -} -.help-block-item a { - color: #76bfeb; -} - -.radio-item, -.checkbox-item { - display: inline-block; - vertical-align: top; - margin-bottom: 0; - font-size: 14px; - line-height: 20px; - font-weight: normal; -} -.radio-item-block, -.checkbox-item-block { - display: block; - margin: 6px 0 1px; - padding: 5px 0; - line-height: 20px; -} -.radio-item-block + .radio-item-block, -.checkbox-item-block + .checkbox-item-block { - margin-top: 1px; -} -.radio-item input.radio, -.checkbox-item input.checkbox { - position: absolute; - left: -5000px; -} -body.rtl .radio-item input.radio, -body.rtl .checkbox-item input.checkbox { - right: -5000px; - left: auto; -} -.radio-item input.radio ~ .radio-label, -.checkbox-item input.checkbox ~ .checkbox-label { - display: inline-block; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - -o-user-select: none; - user-select: none; - max-width: calc(100% - 31px); -} -.radio-item .radio-input, -.checkbox-item .checkbox-input { - display: inline-block; - vertical-align: top; - position: relative; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - -o-user-select: none; - user-select: none; - transition: opacity 0.12s linear; -} -.radio-item .radio-input + .radio-label, -.checkbox-item .checkbox-input + .checkbox-label { - margin-left: 11px; -} -body.rtl .radio-item .radio-input + .radio-label, -body.rtl .checkbox-item .checkbox-input + .checkbox-label { - margin-right: 11px; - margin-left: 0; -} -.radio-item .radio-input-icon, -.checkbox-item .checkbox-input-icon { - display: inline-block; - content: ''; - width: 20px; - height: 20px; - border: 2px solid #b3b3b3; - background: #fff; - border-radius: 10px; - vertical-align: top; - padding: 0; - cursor: pointer; - position: relative; -} -.radio-item .radio-input-icon:before, -.checkbox-item .checkbox-input-icon:before { - display: inline-block; - content: ''; - position: absolute; - width: 20px; - height: 20px; - border: 2px solid #54a9eb; - border-radius: 10px; - top: -2px; - left: -2px; - transition: opacity 0.12s linear; - opacity: 0; -} -.radio-item .radio-input-icon:after { - display: inline-block; - content: ''; - position: absolute; - width: 10px; - height: 10px; - background: #54a9eb; - border-radius: 5px; - top: 3px; - left: 3px; - transition: transform 0.12s linear; - transform: scale3d(0, 0, 1); -} -.radio-item input.radio:checked + .radio-input .radio-input-icon:before, -.checkbox-item input.checkbox:checked + .checkbox-input .checkbox-input-icon:before { - opacity: 1; -} -.radio-item input.radio:checked + .radio-input .radio-input-icon:after { - transform: scale3d(1, 1, 1); -} -.checkbox-item .checkbox-input-icon, -.checkbox-item .checkbox-input-icon:before { - width: 18px; - height: 18px; - margin: 1px; - border-radius: 3px; -} -.checkbox-item .checkbox-input-icon:before { - margin: 0; - background: #54a9eb url('data:image/svg+xml,%3Csvg height="20" viewBox="0 0 20 20" width="20" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%23fff" fill-rule="evenodd"%3E%3Crect height="6" rx="1" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -6.746804 8.368629)" width="2" x="5.728427" y="9.328427"/%3E%3Crect height="11.5" rx="1" transform="matrix(.70710678 .70710678 -.70710678 .70710678 10.712311 -5.169417)" width="2" x="10.596194" y="4.596194"/%3E%3C/g%3E%3C/svg%3E') no-repeat center; -} -.radio-item input.radio:disabled + .radio-input, -.checkbox-item input.checkbox:disabled + .checkbox-input { - cursor: default; - pointer-events: none; - opacity: .65; -} - -.button-item { - font-size: 14px; - font-weight: 500; - line-height: 18px; - color: #fff; - background: #4ca3e2; - border-radius: 19px; - display: inline-block; - padding: 10px 26px; - text-transform: uppercase; - text-align: center; - vertical-align: middle; - border: none; - transition: background-color .2s ease; - white-space: nowrap; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - user-select: none; -} -.button-item-flat { - color: #1385d8; - background: transparent; -} -.button-item:hover { - background: #4199d9; -} -.button-item-flat:hover { - background: #e7f4fd; -} -.button-item-label { - display: inline-block; - max-width: 100%; - overflow: hidden; - text-overflow: ellipsis; - vertical-align: top; - position: relative; - z-index: 1; -} - -.button-item.ripple-handler, -.button-nostyle-item.ripple-handler { - position: relative; -} -.ripple-mask { - position: absolute; - left: 0; right: 0; - top: 0; bottom: 0; - transform: translateZ(0); - overflow: hidden; - pointer-events: none; -} -.radio-item .ripple-mask, -.checkbox-item .ripple-mask { - width: 32px; - height: 32px; - left: -6px; - top: -6px; - border-radius: 16px; -} -.button-nostyle-item .ripple-mask, -.button-item .ripple-mask { - border-radius: 19px; -} -.radio-item .ripple, -.checkbox-item .ripple { - position: absolute; - width: 80px; - height: 80px; - left: -24px; - top: -24px; - border-radius: 50%; - background-color: rgba(179, 179, 179, .2); - transition: transform .65s ease-out, opacity .65s ease-out, background-color .65s ease-out; - opacity: 0; -} -.radio-item input.radio:checked + .radio-input .ripple, -.checkbox-item input.checkbox:checked + .checkbox-input .ripple { - background-color: rgba(84, 169, 235, .2); -} -.button-nostyle-item .ripple, -.button-item .ripple { - position: absolute; - width: 200%; - left: 50%; top: 50%; - margin: -100% 0 0 -100%; - padding-top: 200%; - border-radius: 50%; - background-color: #3790cf; - transition: transform .65s ease-out, opacity .65s ease-out, background-color .65s ease-out; - opacity: 0; -} -.button-nostyle-item .ripple, -.button-item-flat .ripple { - background-color: #d9ebf7; -} - -.radio-item input.radio + .radio-label:before, -.checkbox-item input.checkbox + .checkbox-label:before { - display: inline-block; - content: ''; - width: 20px; - height: 20px; - vertical-align: top; - margin-right: 11px; - padding: 0; - background: url(/img/rc_icons.png?1) no-repeat; - cursor: pointer; -} -.radio-item input.radio + .radio-label:before { - background-position: 0 0; -} -.radio-item input.radio:checked + .radio-label:before { - background-position: 0 -30px; -} -.checkbox-item input.checkbox + .checkbox-label:before { - background-position: 0 -60px; -} -.checkbox-item input.checkbox:checked + .checkbox-label:before { - background-position: 0 -88px; -} -.radio-item-justified .radio-input { - float: left; -} -.radio-item-justified .radio-label { - float: left; - margin-right: 16px; -} -.radio-item-justified .radio-label:after { - content: ':'; - opacity: 0; - transition: opacity .2s ease; -} -.radio-item-justified .justified-wrap { - display: block; - padding: 5px 0; - margin: -5px 0; - overflow: hidden; - opacity: 0; - transition: opacity .2s ease; -} -.radio-item-justified .justified-wrap input.form-control { - cursor: inherit; -} -.radio-item-justified input.radio:checked ~ .justified-wrap, -.radio-item-justified input.radio:checked ~ .radio-label:after { - opacity: 1; -} -.radio-item-justified input.radio:checked ~ .justified-wrap input.form-control { - cursor: auto; -} -.radio-item-justified .textfield-item { - margin: -5px 0; -} -.radio-item-justified input.form-control { - padding: 5px 0 4px; -} - -.bgcolor0 { background: #e17076; } -.bgcolor1 { background: #faa774; } -.bgcolor2 { background: #a695e7; } -.bgcolor3 { background: #7bc862; } -.bgcolor4 { background: #6ec9cb; } -.bgcolor5 { background: #65aadd; } -.bgcolor6 { background: #ee7aae; } - -.dots-animated:after { - display: inline-block; - animation: dotty steps(1, end) 1s infinite; - content: '...'; - position: absolute; -} - -@-webkit-keyframes dotty { - 0%, 100% { content: ''; } - 25% { content: '.'; } - 50% { content: '..'; } - 75% { content: '...'; } -} -@keyframes dotty { - 0%, 100% { content: ''; } - 25% { content: '.'; } - 50% { content: '..'; } - 75% { content: '...'; } -} - -.widget_container { - padding: 10px 20px; - margin: -10px 0; - text-align: center; -} -.widget_container.dark { - background: #15202b; -} -.widget_container iframe { - vertical-align: top; -} - -button.dropdown-toggle:focus, -button.dropdown-toggle:active:focus { - outline: none; -} -.embed_code { - font-family: Menlo, Monaco, Consolas, "Courier New", monospace; - white-space: pre-wrap; - word-break: break-all; - word-wrap: break-word; - text-align: left; - -webkit-appearance: none; -} - -.dev_page_nav_wrap > p > a:first-child { - color: #333; -} - -#dev_page_content .dev_page_nav_wrap ul { - list-style-type: none; - margin: 0; - padding: 0 0 20px; -} -#dev_page_content .dev_page_nav_wrap ul + h4 { - margin-top: 4px; -} -#dev_page_content .dev_page_nav_wrap ul li { - background: none; - padding-left: 0; - padding-top: 1px; - padding-bottom: 2px; -} - -.dev_page_image { - display: block; - max-width: 800px; - margin: 0 auto; - padding: 10px 0px 5px; -} -.tl_contest_page_wrap .dev_page_image { - max-width: 600px; -} - -.dev_page_tgsticker { - position: relative; - display: block; - max-width: 256px; -} -.dev_page_tgsticker img, -.dev_page_tgsticker canvas { - position: absolute; - top: 0; bottom: 0; - left: 0; right: 0; - width: 100%; - height: 100%; -} - -.dev_page_widget_item { - display: block; - width: 300px; - vertical-align: top; - max-width: 100%; - margin: 30px auto 10px; -} -.dev_page_widget_thumb { - display: inline-block; - vertical-align: top; - width: 100%; - padding-top: 66.6667%; - border-radius: 12px; - background: #f7f7f7 no-repeat center; - background-size: 100%; - -webkit-filter: brightness(100%); - -webkit-transition: all .2s ease; - -moz-transition: all .2s ease; - -o-transition: all .2s ease; - -ms-transition: all .2s ease; - transition: all .2s ease; -} -.dev_page_widget_thumb:hover { - -webkit-filter: brightness(94%); -} -.dev_page_widget_thumb_share { - background-image: url(/img/Widget_Share.svg?1); -} -.dev_page_widget_thumb_post { - background-image: url(/img/Widget_Post.svg?1); -} -.dev_page_widget_thumb_login { - background-image: url(/img/Widget_Login.svg?1); -} -.dev_page_widget_thumb_comments { - background-image: url(/img/Widget_Comments.svg?1); -} -.dev_page_widget_title { - font-size: 15px; - line-height: 1.5; - margin: 12px 0 0; - font-weight: bold; - text-align: center; -} -@media (min-width: 670px) { - .dev_page_widgets_list { - margin-right: -36px; - } - .dev_page_widget_item { - float: left; - margin-left: 0; - margin-right: 36px; - } - .dev_page_widget_title { - margin-top: 17px; - } -} - -/* Contest */ - -.tl_contest_page_wrap { - padding: 0 0 20px; - max-width: 600px; - margin: 0 auto; -} -.tl_contest_intro { - margin: 0; -} -.tl_contest_side_image_wrap { - position: relative; -} -.tl_contest_side_image { - margin: 50px 0 0 -180px; - width: 160px; - height: 160px; - position: absolute; -} -.tl_contest_side_image2 { - margin-top: 0px; -} -.tl_contest_side_image3 { - margin-top: 10px; -} -.tl_contest_page_wrap .tl_main_share { - margin: 0 0 20px; - text-align: left; -} -.lang_rtl .tl_contest_page_wrap .tl_main_share { - text-align: right; -} -.tl_contest_page_wrap #dev_page_title { - font-size: 24.5px; - line-height: 33px; - margin: 20px 0 10px 0; -} -.tl_contest_dl_btn { - padding: 0; -} -#traffic_log_wrap { - min-height: 300px; - /*max-height: 600px;*/ - /*overflow: auto;*/ - overflow-wrap: normal; - white-space: pre; -} - -.tl_contest_log { - padding-top: 10px; -} -.tl_contest_log h3 { - margin-top: 0; -} - -/* Blog */ -.blog_side_image_wrap { - position: relative; - direction: ltr; -} -.lang_rtl .blog_side_image_wrap { - direction: rtl; -} -.blog_side_image { - margin: -41px 0 0 -180px; - width: 160px; - height: 160px; - position: absolute; -} -.lang_rtl .blog_side_image { - margin: -41px -180px 0 0; -} - -.blog_side_centered_image_wrap { - position: relative; -} -a.blog_side_cetered_image, -a.blog_side_centered_image { - display: block; - width: 160px; - height: 160px; - margin: 10px auto 20px; -} -img.blog_side_cetered_image, -img.blog_side_centered_image { - width: 160px; - height: 160px; -} - -.tlb_blog_page .blog_side_image_wrap { - position: static; -} -.tlb_blog_page .blog_side_image { - display: block; - margin: 20px auto; - width: 160px; - height: 160px; - position: static; -} - -.blog_wide_image img { - width: 100%; - padding-bottom: 20px; -} -.blog_image_wrap { - width: 275px; - margin: 10px auto 20px; -} -.blog_image_wrap a { - -} -.blog_image_wrap img { - width: 275px; - padding: 10px 5px; -} -.blog_medium_image_wrap, -.blog_medium_image_wrap img { - width: 400px; -} - -.blog_wide_image_wrap, -.blog_wide_image_wrap img { - width: 100%; - max-width: auto; -} -#dev_page_content .blog_image_wrap p, -.tlb_page_wrap .tl_contest_page_wrap #dev_page_content .blog_image_wrap p { - text-align: center; - color: #808080; - font-size: 12px; - margin: 10px 0 0; - line-height: 150%; - padding: 0 10px; -} -.blog_footer { - font-style: italic; -} - -.blog_2images_wrap, -.blog_3images_wrap { - width: 564px; - margin: 20px auto 20px; -} -.blog_3images_wrap { - width: 575px; -} -.blog_2images_wrap:before, -.blog_2images_wrap:after, -.blog_3images_wrap:before, -.blog_3images_wrap:after { - content: " "; - display: table; -} -.blog_2images_wrap:after, -.blog_3images_wrap:after { - clear: both; -} -.blog_2images_wrap .blog_image_wrap, -.blog_3images_wrap .blog_image_wrap { - float: left; - margin-left: 0; - margin-right: 14px; -} -.blog_3images_wrap .blog_image_wrap { - margin-right: 10px; -} -.blog_2images_wrap .blog_image_wrap:last-child, -.blog_3images_wrap .blog_image_wrap:last-child { - margin-right: 0; -} - - -.blog_video_player_wrap { - max-width: 640px; - margin: 10px auto 20px; -} -.blog_video_player { - width: 100%; -} - - -/* My page */ -.my_page_wrap { - margin-top: 50px; - font-size: 14px; - line-height: 20px; -} -.my_page_wrap .container { - max-width: 570px; -} - -.my_page_wrap .tl_main_card { - margin: 0; -} -#my_login_form_wrap { - max-width: 400px; -} -.my_login_form_details { - margin: 10px 0 20px; -} - - -#my_login_form_wrap .btn { - box-shadow: none; - margin-bottom: 0; - font-size: 14px; - font-weight: normal; - line-height: 1.428571429; - text-align: center; - white-space: nowrap; - vertical-align: middle; - cursor: pointer; - background-image: none; - border: 1px solid transparent; - border: 0; - border-radius: 4px; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - -o-user-select: none; - user-select: none; - text-shadow: none; -} -#my_login_form_wrap .btn-primary { - color: #fff; - background-color: #428bca; - border-color: #357ebd; -} -#my_login_form_wrap .btn-danger { - color: #fff; - background-color: #d9534f; - border-color: #d43f3a; -} -#my_login_form_wrap .btn-success { - color: #fff; - background-color: #5cb85c; - border-color: #4cae4c; -} -.modal-header h4 { - position: static; -} - -.my_email_confirmation_result_wrap { - margin-top: 40px; -} -.my_email_confirmation_result_text { - padding: 10px; - font-size: 24px; - font-weight: bold; - line-height: 1.2; - text-align: center; -} - - -.smartphone_video_player_wrap { - width: 270px; - height: 555px; - margin: 20px auto; - position: relative; - background: #000 url(../img/iPhone6.png) 0 0 no-repeat; - background-size: 270px 555px; -} -.smartphone_video_player_iphone { - position: absolute; - margin-top: 69px; - margin-left: 18px; - border-radius: 3px; - overflow: hidden; - line-height: 0; -} -video.smartphone_video_player { - cursor: pointer; - width: 234px; - height: 416px; - line-height: 0; - margin: 0; - vertical-align: top; -} - - -.smarphone_device_nexus { - margin: 40px auto; - padding: 45px 14px 45px 14px; - width: 290px; - height: 514px; - background: #1e1e1e; - border-radius: 18.125px; - display: block; - position: relative; - box-sizing: content-box; -} -.smarphone_device_nexus:before { - -webkit-border-radius: 540px / 45px; - border-radius: 540px / 45px; - background: inherit; - content: ''; - top: 0; - position: absolute; - height: 103.1%; - width: calc(100% - 23px); - top: 50%; - left: 50%; - -moz-transform: translateX(-50%) translateY(-50%); - -webkit-transform: translateX(-50%) translateY(-50%); - -o-transform: translateX(-50%) translateY(-50%); - -ms-transform: translateX(-50%) translateY(-50%); - transform: translateX(-50%) translateY(-50%); - box-sizing: content-box; -} -.smarphone_device_nexus .top-bar { - width: calc(100% - 7px); - height: calc(100% - 5px); - position: absolute; - top: 3px; - left: 4px; - -webkit-border-radius: 18px; - border-radius: 18px; - background: #181818; - box-sizing: content-box; -} -.smarphone_device_nexus .top-bar:before { - -webkit-border-radius: 540px / 45px; - border-radius: 540px / 45px; - background: inherit; - content: ''; - top: 0; - position: absolute; - height: 103.0%; - width: calc(100% - 26px); - top: 50%; - left: 50%; - -moz-transform: translateX(-50%) translateY(-50%); - -webkit-transform: translateX(-50%) translateY(-50%); - -o-transform: translateX(-50%) translateY(-50%); - -ms-transform: translateX(-50%) translateY(-50%); - transform: translateX(-50%) translateY(-50%); - box-sizing: content-box; -} -.smarphone_device_nexus .bottom-bar{ - display: none; - box-sizing: content-box; -} -.smarphone_device_nexus .sleep { - width: 3px; - position: absolute; - left: -3px; - top: 99px; - height: 90px; - background: inherit; - -webkit-border-radius: 2px 0px 0px 2px; - border-radius: 2px 0px 0px 2px; - box-sizing: content-box; -} -.smarphone_device_nexus .volume { - width: 3px; - position: absolute; - right: -3px; - top: 63px; - height: 45px; - background: inherit; - -webkit-border-radius: 0px 2px 2px 0px; - border-radius: 0px 2px 2px 0px; - box-sizing: content-box; -} -.smarphone_device_nexus .camera { - background: #3c3d3d; - width: 9px; - height: 9px; - position: absolute; - top: 18px; - left: 50%; - z-index: 3; - margin-left: -5px; - border-radius: 100%; - box-sizing: content-box; -} -.smarphone_device_nexus .camera:before { - background: #3c3d3d; - width: 6px; - height: 6px; - content: ''; - display: block; - position: absolute; - top: 2px; - left: -90px; - z-index: 3; - border-radius: 100%; - box-sizing: content-box; -} -.smarphone_device_nexus .screen { - position: relative; - box-sizing: content-box; -} -.smarphone_device_nexus video { - display: block; - width: 290px; - height: 514px; - margin: 0 auto; -} - - -/* Telegram Me */ -.tgme_page_wrap { - font-family: 'Roboto', sans-serif;; - color: #2b2d2e; -} -.tgme_page_wrap a, -.tgme_page_wrap a:hover, -.tgme_page_wrap a:active { - color: #3ca2d9; -} - -.tgme_head_wrap { - background: #FFF; - height: 59px; - padding: 14px 16px; - -webkit-box-shadow: 0px 1px 3px 0px rgba(0,0,0,0.15); - -moz-box-shadow: 0px 1px 3px 0px rgba(0,0,0,0.15); - box-shadow: 0px 1px 3px 0px rgba(0,0,0,0.15); -} -.tgme_logo { - display: inline-block; - background: url('data:image/svg+xml,%3Csvg height="34" viewBox="0 0 133 34" width="133" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="none" fill-rule="evenodd"%3E%3Ccircle cx="17" cy="17" fill="%2327a7e5" r="17"/%3E%3Cpath d="m7.06510669 16.9258959c5.22739451-2.1065178 8.71314291-3.4952633 10.45724521-4.1662364 4.9797665-1.9157646 6.0145193-2.2485535 6.6889567-2.2595423.1483363-.0024169.480005.0315855.6948461.192827.1814076.1361492.23132.3200675.2552048.4491519.0238847.1290844.0536269.4231419.0299841.65291-.2698553 2.6225356-1.4375148 8.986738-2.0315537 11.9240228-.2513602 1.2428753-.7499132 1.5088847-1.2290685 1.5496672-1.0413153.0886298-1.8284257-.4857912-2.8369905-1.0972863-1.5782048-.9568691-2.5327083-1.3984317-4.0646293-2.3321592-1.7703998-1.0790837-.212559-1.583655.7963867-2.5529189.2640459-.2536609 4.7753906-4.3097041 4.755976-4.431706-.0070494-.0442984-.1409018-.481649-.2457499-.5678447-.104848-.0861957-.2595946-.0567202-.3712641-.033278-.1582881.0332286-2.6794907 1.5745492-7.5636077 4.6239616-.715635.4545193-1.3638349.6759763-1.9445998.6643712-.64024672-.0127938-1.87182452-.334829-2.78737602-.6100966-1.12296117-.3376271-1.53748501-.4966332-1.45976769-1.0700283.04048-.2986597.32581586-.610598.8560076-.935815z" fill="%23fff"/%3E%3Cpath d="m49.4 24v-12.562h-4.224v-2.266h11.198v2.266h-4.268v12.562zm16.094-4.598h-7.172c.066 1.936 1.562 2.772 3.3 2.772 1.254 0 2.134-.198 2.97-.484l.396 1.848c-.924.396-2.2.682-3.74.682-3.476 0-5.522-2.134-5.522-5.412 0-2.97 1.804-5.764 5.236-5.764 3.476 0 4.62 2.86 4.62 5.214 0 .506-.044.902-.088 1.144zm-7.172-1.892h4.708c.022-.99-.418-2.618-2.222-2.618-1.672 0-2.376 1.518-2.486 2.618zm9.538 6.49v-15.62h2.706v15.62zm14.84-4.598h-7.172c.066 1.936 1.562 2.772 3.3 2.772 1.254 0 2.134-.198 2.97-.484l.396 1.848c-.924.396-2.2.682-3.74.682-3.476 0-5.522-2.134-5.522-5.412 0-2.97 1.804-5.764 5.236-5.764 3.476 0 4.62 2.86 4.62 5.214 0 .506-.044.902-.088 1.144zm-7.172-1.892h4.708c.022-.99-.418-2.618-2.222-2.618-1.672 0-2.376 1.518-2.486 2.618zm19.24-1.144v6.072c0 2.244-.462 3.85-1.584 4.862-1.1.99-2.662 1.298-4.136 1.298-1.364 0-2.816-.308-3.74-.858l.594-2.046c.682.396 1.826.814 3.124.814 1.76 0 3.08-.924 3.08-3.234v-.924h-.044c-.616.946-1.694 1.584-3.124 1.584-2.662 0-4.554-2.2-4.554-5.236 0-3.52 2.288-5.654 4.862-5.654 1.65 0 2.596.792 3.102 1.672h.044l.11-1.43h2.354c-.044.726-.088 1.606-.088 3.08zm-2.706 2.948v-1.738c0-.264-.022-.506-.088-.726-.286-.99-1.056-1.738-2.2-1.738-1.518 0-2.64 1.32-2.64 3.498 0 1.826.924 3.3 2.618 3.3 1.012 0 1.892-.66 2.2-1.65.088-.264.11-.638.11-.946zm5.622 4.686v-7.26c0-1.452-.022-2.508-.088-3.454h2.332l.11 2.024h.066c.528-1.496 1.782-2.266 2.948-2.266.264 0 .418.022.638.066v2.53c-.242-.044-.484-.066-.814-.066-1.276 0-2.178.814-2.42 2.046-.044.242-.066.528-.066.814v5.566zm16.05-6.424v3.85c0 .968.044 1.914.176 2.574h-2.442l-.198-1.188h-.066c-.638.836-1.76 1.43-3.168 1.43-2.156 0-3.366-1.562-3.366-3.19 0-2.684 2.398-4.07 6.358-4.048v-.176c0-.704-.286-1.87-2.178-1.87-1.056 0-2.156.33-2.882.792l-.528-1.76c.792-.484 2.178-.946 3.872-.946 3.432 0 4.422 2.178 4.422 4.532zm-2.64 2.662v-1.474c-1.914-.022-3.74.374-3.74 2.002 0 1.056.682 1.54 1.54 1.54 1.1 0 1.87-.704 2.134-1.474.066-.198.066-.396.066-.594zm5.6 3.762v-7.524c0-1.232-.044-2.266-.088-3.19h2.31l.132 1.584h.066c.506-.836 1.474-1.826 3.3-1.826 1.408 0 2.508.792 2.97 1.98h.044c.374-.594.814-1.034 1.298-1.342.616-.418 1.298-.638 2.2-.638 1.76 0 3.564 1.21 3.564 4.642v6.314h-2.64v-5.918c0-1.782-.616-2.838-1.914-2.838-.924 0-1.606.66-1.892 1.43-.088.242-.132.594-.132.902v6.424h-2.64v-6.204c0-1.496-.594-2.552-1.848-2.552-1.012 0-1.694.792-1.958 1.518-.088.286-.132.594-.132.902v6.336z" fill="%23363b40" fill-rule="nonzero"/%3E%3C/g%3E%3C/svg%3E') 0 0 no-repeat; - width: 133px; - height: 34px; - margin: -1px 0; -} -a.tgme_head_dl_button { - display: block; - font-size: 16px; - line-height: 100%; - color: #FFF; - background: #32afed; - padding: 2px 15px 0 16px; - height: 45px; - line-height: 43px; - text-align: center; -} -.tlb_page_wrap a.tgme_head_dl_button { - color: #FFF; -} -a.tgme_head_dl_button:hover, -a.tgme_head_dl_button:active, -.tlb_page_wrap a.tgme_head_dl_button:hover, -.tlb_page_wrap a.tgme_head_dl_button:active { - color: #FFF; - background: #32afed; - text-decoration: none; -} -.tgme_icon_arrow { - display: inline-block; - background: url(/img/tgme/Arrow_1x.png) 0 0 no-repeat; - width: 8px; - height: 12px; - background-size: 8px 12px; - vertical-align: top; - margin-top: 15px; - margin-left: 9px; -} - -.tgme_page { - position: relative; - margin: 52px auto 50px; - max-width: 424px; -} -.tgme_page_post { - max-width: 455px; - padding: 52px 0 50px; - margin: 0 auto; -} -.tgme_page_icon { - text-align: center; - margin-bottom: 20px; -} -.tgme_icon_user { - display: inline-block; - width: 40px; - height: 39px; - background: url(/img/tgme/Web1x.png?1) -2px -38px no-repeat; - background-size: 44px 177px; -} -.tgme_icon_group { - display: inline-block; - width: 44px; - height: 28px; - background: url(/img/tgme/Web1x.png?1) 0 0 no-repeat; - background-size: 44px 177px; -} -.tgme_icon_stickers { - display: inline-block; - width: 40px; - height: 40px; - background: url(/img/tgme/Web1x.png?1) -2px -87px no-repeat; - background-size: 44px 177px; -} -.tgme_icon_share { - display: inline-block; - width: 44px; - height: 23px; - background: url(/img/tgme/Web1x.png?1) 0 -137px no-repeat; - background-size: 44px 177px; -} -.tgme_page_photo { - text-align: center; - margin-top: -15px; - margin-bottom: 15px; -} -.tgme_page_photo_image { - width: 122px; - height: 122px; - border-radius: 61px; -} -.tgme_page_title { - font-size: 26px; - line-height: 32px; - font-weight: bold; - text-align: center; - max-width: 340px; - padding: 0 10px; - margin: 0 auto; - color: #333; - overflow: hidden; - text-overflow: ellipsis; -} -.verified-icon { - display: inline-block; - width: 1em; - height: 1em; - padding: 1px; - color: transparent; - background: url('data:image/svg+xml,%3Csvg height="26" viewBox="0 0 26 26" width="26" xmlns="http://www.w3.org/2000/svg"%3E%3Cpath d="m14.378741 1.509638 1.818245 1.818557c.365651.365716.861601.571194 1.378741.571259l2.574273.000312c1.01361.000117 1.846494.773578 1.940861 1.762436l.008905.187798-.000312 2.5727c-.000065.517322.205439 1.013454.571259 1.379222l1.819649 1.819337c.714441.713427.759174 1.843179.134563 2.609139l-.134797.148109-1.819181 1.8182502c-.365963.3657823-.571558.8620196-.571493 1.3794456l.000312 2.5737972c.000559 1.0136048-.772668 1.846676-1.7615 1.9412861l-.188266.0084786-2.573792-.0003107c-.517426-.0000624-1.013675.2055248-1.379456.5714956l-1.818245 1.8191823c-.71331.7145515-1.843049.7594886-2.609113.1349998l-.148135-.1347645-1.8193435-1.8196542c-.3657628-.3658252-.8618987-.5713214-1.3792103-.571259l-2.5727052.0003107c-1.0136048.0001222-1.846676-.7731321-1.9412861-1.761968l-.0089492-.1877967-.0003107-2.5742678c-.0000624-.5171478-.2055495-1.0130926-.571259-1.3787397l-1.8185622-1.8182515c-.7139886-.713869-.758706-1.843647-.1340846-2.609607l.1338493-.148109 1.8190328-1.81935c.3655665-.365625.5709613-.861471.5710237-1.378494l.0003107-2.573181c.0006006-1.076777.8734635-1.949636 1.9502353-1.950234l2.5731758-.000312c.5170321-.000065 1.0128768-.205452 1.3785044-.571025l1.8193448-1.819038c.761592-.761449 1.996254-.761345 2.757716.000247zm3.195309 8.047806c-.426556-.34125-1.032655-.306293-1.417455.060333l-.099151.108173-4.448444 5.55815-1.7460313-1.74707-.1104961-.096564c-.4229264-.32188-1.0291801-.289692-1.4154413.096564-.3862612.386269-.4184492.992511-.0965653 1.41544l.0965653.1105 2.5999987 2.5999987.109876.0961467c.419874.320359 1.015131.2873897 1.397071-.0773773l.098579-.107692 5.2-6.4999961.083772-.120484c.273208-.455884.174278-1.054885-.252278-1.396122z" fill="%2333AFED" fill-rule="evenodd"/%3E%3C/svg%3E') no-repeat 0 0; - background-size: 100%; - vertical-align: -4px; - margin-left: 8px; -} -.tgme_page_extra { - font-size: 15px; - line-height: 27px; - text-align: center; - margin-bottom: 6px; - color: #808080; -} -.tgme_page_description, -.tgme_page_additional { - font-size: 16px; - line-height: 25px; - text-align: center; - max-width: 340px; - padding: 0 10px; - margin: 0 auto; - overflow: hidden; - text-overflow: ellipsis; -} -.tgme_page_description { - display: -webkit-box; - -webkit-line-clamp: 5; - -webkit-box-orient: vertical; - overflow: hidden; - text-overflow: ellipsis; - max-height: 125px; - word-break: break-word; -} -.tgme_page_long_description { - max-height: none; - -webkit-line-clamp: unset; -} -.tgme_page_additional { - display: none; - font-size: 14px; - line-height: 23px; - margin-top: 32px; - color: #808080; -} -a.tgme_username_link, -a.tgme_username_link:hover, -a.tgme_username_link:active { - text-decoration: none; -} -.tgme_page_action { - text-align: center; - margin-top: 32px; - line-height: 0; -} -a.tgme_action_button, -a.tgme_action_button_new { - font-size: 14px; - font-weight: bold; - line-height: 100%; - color: #FFF; - background: #5dc390; - border-radius: 22px; - overflow: hidden; - display: inline-block; - padding: 15px 27px 13px; - text-transform: uppercase; -} -a.tgme_action_button:hover, -a.tgme_action_button:active, -a.tgme_action_button_new:hover, -a.tgme_action_button_new:active { - color: #FFF; - background: #4bbc87; - text-decoration: none; -} -a.tgme_action_button_new { - background: #33d684; -} -a.tgme_action_button_new:hover, -a.tgme_action_button_new:active { - background: #28c979; -} - -.tgme_page_web_action { - margin-top: 18px; -} -.tgme_page_web_action a.tgme_action_button { - color: #5dc390;; - background: #fff; - border: 2px solid #5dc390; - padding: 13px 25px 11px; -} -.tgme_page_web_action a.tgme_action_button:hover, -.tgme_page_web_action a.tgme_action_button:active { - color: #5dc390;; - background: #FFF;; - text-decoration: none; -} -.tgme_action_privacy_action { - margin-top: 12px; -} -.tgme_action_privacy_action a.tgme_action_privacy_button { - color: #5dc390;; - background: #fff; - border: 0; - padding: 13px 25px 11px; - font-size: 12px; -} -.tgme_action_privacy_action a.tgme_action_privacy_button:hover, -.tgme_action_privacy_action a.tgme_action_privacy_button:active { - color: #5dc390;; - background: #FFF;; - text-decoration: none; -} - -.tgme_footer { - margin: 0 auto 50px; - border-top: 1px solid #e0e0e0; - max-width: 424px; - padding-top: 38px; -} - -.tgme_footer_description { - font-size: 17px; - line-height: 27px; - text-align: center; - max-width: 330px; - padding: 0 10px; - margin: 0 auto 0; -} -.tgme_footer_action { - text-align: center; - margin-top: 28px; - line-height: 0; -} -a.tgme_footer_dl_button { - background: #32afed; -} -a.tgme_footer_dl_button:hover, -a.tgme_footer_dl_button:active { - background: #1ca4e7; -} - -.tgme_page_widget { - margin-left: -45px; -} -.tgme_page_widget_action { - text-align: center; - line-height: 0; -} -.tgme_page_widget iframe { - vertical-align: top; - max-width: 100%; -} -.tgme_page_widget_actions { - position: relative; - max-width: 595px; - padding: 30px 0; -} -.fixed_actions .tgme_page_widget_actions { - position: fixed; - left: 0; - right: 0; - bottom: 0; - border-top: 1px solid #d7e3ec; - padding: 30px 70px; - margin: 0 auto; - background: #fff; -} -.tgme_page_widget_actions_cont { - max-width: 455px; - margin: 0 auto; - display: flex; - justify-content: space-between; - flex-wrap: wrap; -} -.tgme_page_widget_actions .tgme_page_action { - position: relative; - margin: 0 auto; -} -.tgme_page_widget_action_right, -.tgme_page_widget_action_left { - width: 120px; - flex-grow: 2; -} -.tgme_page_widget_action_right { - float: right; - text-align: right; - order: 1; -} -.tgme_page_widget_action_left { - float: left; - text-align: left; -} -.tgme_page_widget_actions a.tgme_action_web_button { - border: none; - background: none; - padding: 15px 10px 13px; -} -.tgme_page_widget_actions a.tgme_action_web_button:hover { - text-decoration: underline; -} -.tgme_page_widget_actions a.tgme_action_web_button:before { - content: ''; - display: none; - width: 24px; - height: 24px; - margin: -7px 0 -7px 0; - background: url(/img/tgme/web_icon.png) 0 0 no-repeat; -} -.tgme_page_widget_actions .tgme_page_web_action { - margin-top: 0; - text-align: inherit; -} -.tgme_page_context_action { - margin-top: 8px; -} -.tgme_page_context_action a.tgme_action_button_new { - font-weight: normal; - text-transform: none; -} -.tgme_page_embed_action { - text-align: center; - margin-top: 30px; - display: none; - order: 3; - flex-basis: 100%; -} -.embed_opened .tgme_page_embed_action { - display: block; -} -.tgme_page_embed_btn { - line-height: 0; -} -.tgme_page_copy_action { - text-align: center; - margin-top: 18px; - margin-bottom: -16px; -} -.tgme_page_embed_btn a.tgme_action_button_new, -.tgme_page_context_btn a.tgme_action_button_new, -.tgme_page_copy_action a.tgme_action_button_new { - color: #8197af; - padding: 15px 10px 13px; - background: none; - cursor: pointer; -} -.tgme_page_embed_btn a.tgme_action_button_new:before { - content: ''; - display: inline-block; - width: 24px; - height: 24px; - margin: -7px 7px -7px 0; - background: url(/img/tgme/embed_icon.png?1) 0 0 no-repeat; -} -.embed_opened .tgme_page_embed_btn a.tgme_action_button_new:before { - background-position: -24px 0; -} -.tgme_page_copy_action a.tgme_action_button_new:before { - content: ''; - display: inline-block; - width: 24px; - height: 24px; - margin: -7px 7px -7px 0; - background: url(/img/tgme/embed_copy.png) 0 0 no-repeat; -} -.embed_opened .tgme_page_embed_btn a.tgme_action_button_new { - color: #2481cc; -} -.tgme_page_embed_action a.tgme_action_button_new:hover, -.tgme_page_embed_action a.tgme_action_button_new:active, -.tgme_page_copy_action a.tgme_action_button_new:hover, -.tgme_page_copy_action a.tgme_action_button_new:active { - color: #8197af; - text-decoration: none; - background: none; -} -.tgme_page_embed_code { - font-size: 13px; - color: #546172; - background: #ecf3f8; - font-family: Menlo, Monaco, Consolas, "Courier New", monospace; - width: 100%; - padding: 11px 17px; - border: 1px solid #d7e3ec; - border-radius: 10px; - white-space: pre-wrap; - word-break: break-all; - word-wrap: break-word; - text-align: left; - -webkit-appearance: none; - vertical-align: top; -} -.tgme_page_embed_code:focus { - outline: none; -} -@media (max-width: 595px) { - .tgme_page_widget { - padding: 0 10px; - margin-left: 0; - } - .tgme_page_widget_actions, - .fixed_actions .tgme_page_widget_actions { - padding: 20px 0; - } - .tgme_page_widget_action_right, - .tgme_page_widget_action_left { - text-align: center; - width: 20%; - } - .tgme_page_widget_actions .tgme_action_button_label { - display: none; - } - .tgme_page_widget_actions a.tgme_action_web_button:before { - display: inline-block; - } - .tgme_page_embed_btn a.tgme_action_button_new:before { - margin-right: 0; - } - .tgme_page_embed_action { - margin-top: 20px; - margin-left: 10px; - margin-right: 10px; - } - .tgme_page_copy_action { - margin-top: 8px; - } - #embed_code { - margin-top: 24px; - } -} - -.tgme_page_bg { - margin: 0; - max-width: none; -} -.tgme_bg_wrap { - height: 100%; - height: calc(100vh - 104px); - display: -ms-flexbox; - display: -webkit-flex; - display: flex; - -webkit-justify-content: center; - -ms-flex-pack: center; - justify-content: center; - -webkit-align-items: center; - -ms-flex-align: center; - align-items: center; -} -.tgme_bg_image_wrap { - position: absolute; - width: 100%; - height: 100%; - height: calc(100vh - 104px); - overflow: hidden; -} -.tgme_bg_image { - width: 110%; - width: calc(100vw + 40px); - height: 110%; - height: calc(100vh - 104px + 40px); - margin: -20px; - - background-repeat: no-repeat; - background-size: cover; - z-index: 1; - - -webkit-filter: blur(5px); - -moz-filter: blur(5px); - -o-filter: blur(5px); - -ms-filter: blur(5px); - filter: blur(5px); -} -.tgme_bg_wrap_pattern1 .tgme_bg_image { - -webkit-filter: blur(8px); - -moz-filter: blur(8px); - -o-filter: blur(8px); - -ms-filter: blur(8px); - filter: blur(8px); -} -.tgme_bg_wrap_full .tgme_bg_image { - -webkit-filter: none; - -moz-filter: none; - -o-filter: none; - -ms-filter: none; - filter: none; -} -.tgme_bg { - position: relative; - z-index: 2; -} -.tgme_bg_popup_wrap { - background: #fff; - border-radius: 10px; - flex: 1 0 auto; - padding: 40px 40px 30px; - margin: 0 40px; - max-width: 390px; - text-align: center; -} -.tgme_bg_title { - font-size: 18px; - font-weight: bold; - margin: 0 0 10px; -} -.tgme_bg_size { - color: #64686B; - font-size: 14px; - margin: 10px 0 17px; -} - - -#tgme_frame_cont { - position: absolute; - left: -10000px; - top: -10000px; -} - -/* New mobile blog */ -.tlb_page_wrap { - font-family: 'Roboto', sans-serif;; -} -.tlb_page_wrap a, -.tlb_page_wrap a:hover, -.tlb_page_wrap a:active { - color: #1497d9; -} -.tlb_page_head { - background: #FFF; - height: 47px; - padding: 12px 12px; -} -.tlb_blog_logo { - display: inline-block; - background: url(/img/blog/BlogLogo1x.png?1) 0 0 no-repeat; - width: 146px; - height: 20px; - background-size: 146px 20px; - line-height: 0; - margin-top: 2px; -} -.tlb_head_home { - float: right; - display: inline-block; - line-height: 24px; - height: 24px; - vertical-align: top; - font-size: 14px; -} -a.tlb_blog_head_more_link { - display: block; - font-size: 15px; - color: #FFF; - background: #3faee8; - padding: 0 15px 0 15px; - height: 42px; - line-height: 42px; -} -a.tlb_blog_head_more_link:hover, -a.tlb_blog_head_more_link:active { - color: #FFF; - background: #3faee8; - text-decoration: none; -} - -a.tlb_blog_head_more_link .tlb_head_more_active, -.tlb_blog_head_recent_active a.tlb_blog_head_more_link .tlb_head_more_inactive, -.tlb_head_more_entries { - display: none; -} -.tlb_blog_head_recent_active a.tlb_blog_head_more_link .tlb_head_more_active, -.tlb_blog_head_recent_active .tlb_head_more_entries { - display: block; -} -.tlb_head_more_icon_wrap { - float: right; - vertical-align: top; - margin-top: 15px; - line-height: 0; -} -.lang_rtl .tlb_head_more_icon_wrap { - float: left; -} -.tlb_head_more_icon { - display: inline-block; - border: 2px solid #FFF; - border-left: 0; - border-bottom: 0; - width: 10px; - height: 10px; - - -moz-transform: rotate(135deg); - -webkit-transform: rotate(135deg); - -o-transform: rotate(135deg); - -ms-transform: rotate(135deg); - transform: rotate(135deg); - - /*-webkit-transition: all linear 0.2s; - -moz-transition: all linear 0.2s; - -ms-transition: all linear 0.2s; - -o-transition: all linear 0.2s; - transition: all linear 0.2s;*/ -} -.tlb_blog_head_recent_active .tlb_head_more_icon_wrap { - margin-top: 18px; -} -.tlb_blog_head_recent_active .tlb_head_more_icon { - -moz-transform: rotate(-45deg); - -webkit-transform: rotate(-45deg); - -o-transform: rotate(-45deg); - -ms-transform: rotate(-45deg); - transform: rotate(-45deg); -} - -.tlb_page_wrap .side_blog_wrap { - margin: 22px 0 0 16px; - padding: 0 10px 0 0; - font-size: 13px; -} -.tlb_page_wrap .side_blog_wrap:before { - width: 4px; - background: #3faee8; - border-radius: 4px; - margin: 0 15px 0 0; -} -.lang_rtl .tlb_page_wrap .side_blog_wrap:before { - margin: 0 0 0 15px; -} - -.tlb_page_wrap .side_blog_header { - font-size: 15px; - font-weight: bold; -} -.tlb_page_wrap .side_blog_entry { - margin-top: 12px; -} -.tlb_page_wrap .side_blog_date { - color: #444; - font-size: 14px; -} -.tlb_page_wrap .side_blog_title { - margin-top: 2px; - font-size: 15px; -} - - - -.tlb_page_wrap #dev_page_title a, -.tlb_page_wrap #dev_page_title a:hover, -.tlb_page_wrap #dev_page_title a:active { - color: #444; -} -.tlb_page_wrap .tl_contest_page_wrap #dev_page_title { - text-align: center; - max-width: 250px; - margin-left: auto; - margin-right: auto; - margin-bottom: 20px; -} -.tlb_page_wrap .tl_contest_page_wrap #dev_page_title, -.tlb_page_wrap .tl_contest_page_wrap h4 { - color: #444; - font-size: 18px; - line-height: 25px; -} - -.tlb_page_wrap .tl_contest_page_wrap #dev_page_content, -.tlb_page_wrap .tl_contest_page_wrap #dev_page_content p { - color: #333333; - font-size: 15px; -} -.tlb_page_wrap .tl_contest_page_wrap #dev_page_content p { - margin-bottom: 15px; -} -.tlb_page_wrap .tl_contest_page_wrap #dev_page_content blockquote p:last-child { - margin-bottom: 0; -} - -.tlb_page_wrap a.tl_twitter_share_btn { - background: #3faee8; - color: #FFF; - font-size: 14px; - line-height: 18px; - border-radius: 17px; - padding-top: 8px; -} -.tlb_page_wrap span.tl_twitter_share_cnt { - color: #c2eaff; -} -.tlb_page_wrap a.tl_twitter_share_btn:hover, -.tlb_page_wrap a.tl_twitter_share_btn:active { - color: #c2eaff; -} - - -.tl_telegram_share_btn { - display: inline-block; - border-radius: 16px; - background-color: #54a9eb; - cursor: pointer; - line-height: 22px; - margin-right: 10px; - padding: 5px 17px 5px 11px; - color: #FFF; - font-weight: bold; -} -.tl_telegram_share_btn:hover, -.tl_telegram_share_btn:active, -.tl_telegram_share_btn:focus { - text-decoration: none; - color: #FFF; - outline: none; -} -.lang_rtl .tl_telegram_share_btn { - margin-right: 0; - margin-left: 10px; -} -i.tl_telegram_share_icon { - display: inline-block; - width: 20px; - height: 20px; - background: url('data:image/svg+xml,%3Csvg height="20" viewBox="0 0 20 20" width="20" xmlns="http://www.w3.org/2000/svg"%3E%3Cpath d="m1.77404283 9.58769086c4.67714245-1.99564845 7.79596997-3.31130205 9.35648257-3.9469608 4.4555806-1.81493491 5.381412-2.13020854 5.984856-2.14061906.1327219-.0022897.4294781.02992311.6217044.18267827.162312.12898346.2069705.30322179.2283411.42551228.0213705.12229049.047982.40087134.0268279.61854631-.2414495 2.48450744-1.2861975 8.51375174-1.817706 11.29644264-.2249011 1.1774608-.6709749 1.4294697-1.0996928 1.4681058-.9317032.0839651-1.6359598-.4602232-2.5383599-1.0395344-1.412078-.9065075-1.9311138-1.1506648-3.30178003-2.0352487-1.58404193-1.0222898-.71982554-1.5573792.18291533-2.4756292.23625159-.2403103 4.3705401-3.98382431 4.4499945-4.31554914.0099371-.04148774-.12607-.45629906-.2198814-.53795815s-.2322689-.05373486-.3321837-.03152647c-.1416262.03147972-2.397439 1.49167812-6.76743852 4.38059516-.64030496.4305972-1.22027332.6403987-1.73990507.6294043-.5728523-.0121204-1.67479033-.3172064-2.49396798-.5779863-1.00475474-.3198572-1.37564449-.4704946-1.30610794-1.013711.03621894-.2829407.29151946-.57846124.76590154-.88656154z" fill="%23fff" fill-rule="evenodd"/%3E%3C/svg%3E') 0 0 no-repeat; - margin-right: 11px; - vertical-align: top; -} -.lang_rtl i.tl_telegram_share_icon { - margin-right: 0; - margin-left: 11px; -} -.tl_telegram_share_label { - line-height: 21px; - vertical-align: top; - display: inline-block; - /*margin-top: 1px;*/ -} - -.tlb_page_wrap a.tl_telegram_share_btn { - background: #3faee8; - color: #FFF; - font-size: 14px; - border-radius: 17px; - padding: 6px 12px 5px 6px; -} -.tlb_page_wrap a.tl_telegram_share_btn:hover, -.tlb_page_wrap a.tl_telegram_share_btn:active { - color: #c2eaff; -} - - -/* Telegram Desktop */ -.td_btn_hidden, -.td_all_shown .td_show_all_platforms { - display: none; -} -.td_all_shown span.td_btn_hidden { - display: inline; -} -.td_all_shown div.td_btn_hidden { - display: block; -} -.td_content_wrap { - width: 420px; - margin: 0 auto; - font-size: 16px; -} -.td_content_title { - font-size: 28px; - color: #383a3b; - text-align: center; - margin-top: 32px; - margin-bottom: 14px; - font-weight: normal; - letter-spacing: -1px; -} -.tl_content_title_link, -.tl_content_title_link:hover { - text-decoration: none; -} -.td_screenshot { - background: url(../img/td_laptop.png) 50% 0 no-repeat; - background-size: contain; - padding-top: 58%; - margin-top: 48px; -} -.td_download_wrap, -.td_download_wrap_low { - margin: 0 -130px; - width: 680px; - text-align: center; -} -.td_download_wrap_low { - margin-bottom: 30px; -} -.td_download_icon { - display: inline-block; - vertical-align: top; - width: 25px; - height: 30px; - background: url(../img/td_icons.png) 0 2px no-repeat; - background-size: 25px 105px; - margin: -2px 5px 0 0; -} -.td_osx .td_download_icon { - background-position: 0 -33px; -} -.td_linux .td_download_icon { - background-position: 0 -68px; -} -.td_download_add_wrap { - width: 680px; - margin: 0 -130px 10px; - text-align: center; -} -.td_download_add { - min-width: 256px; - padding: 0 15px 20px; - margin: 5px 10px; - text-align: center; - display: inline-block; - cursor: pointer; -} -.td_download_btn { - display: inline-block; - vertical-align: top; - font-weight: normal; - text-align: center; - vertical-align: middle; - cursor: pointer; - background-image: none; - white-space: nowrap; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - user-select: none; - color: #fff; - border-color: #357ebd; - padding: 10px 14px; - min-width: 266px; - font-size: 15px; - line-height: 2; - border-radius: 30px; - background-color: #1d98dc; - margin: 5px 10px; -} -.td_download_btn_wrap { - display: inline-block; - vertical-align: top; -} -.td_download_btn_wrap .td_download_btn, -.td_download_btn_wrap .td_download_add { - display: block; -} -.td_download_btn_wrap .td_download_add { - margin-top: 10px; -} -.td_download_divider { - font-size: 9px; - color: #777; - margin: 0 4px; - vertical-align: text-bottom; -} - -.td_download_btn:hover { - outline: 0px; - text-decoration: none; - color: #fff; - background-color: #0e8ed4; -} -.td_download_btn:active, -.td_download_btn:focus { - outline: 0px; - text-decoration: none; - color: #fff; -} -.td_about_license { - font-size: 14px; - color: #67696a; - text-align: center; - margin-top: 50px; - margin-bottom: 30px; - line-height: 170%; -} - -#td_versions { - opacity: 1; - -webkit-transition: opacity 200ms linear; - -moz-transition: opacity 200ms linear; - -o-transition: opacity 200ms linear; - transition: opacity 200ms linear; -} -#td_versions.td_hidden { - opacity: 0.1; -} - -#td_about_osx { - font-size: 20px; - color: #525252; - padding: 9px 0 5px; - font-weight: normal; -} -#td_about_osx { - position: absolute; - width: 600px; - opacity: 0; - margin-top: -32px; - text-align: center; - -webkit-transition: opacity 200ms linear; - -moz-transition: opacity 200ms linear; - -o-transition: opacity 200ms linear; - transition: opacity 200ms linear; -} -#td_about_osx.td_shown { - opacity: 1; -} -#td_about_tdesktop, -#td_open_from_desktop { - font-family: 'HelveticaNeue-Light', 'Helvetica Neue Light', 'Helvetica Light', Helvetica, Arial , Verdana, sans-serif; - line-height: 148%; - text-align: center; -} -#td_about_tdesktop { - font-size: 17px; - margin: 0 auto; - color: #67696a; - margin: 14px 10px 24px; - font-weight: 300; -} -#td_open_from_desktop { - font-size: 17px; - color: #0088cc; - border: 1px solid #179cde; - border-radius: 10px; - padding: 13px 24px; - margin: 24px 0 40px; -} -.td_changelog_wrap { - padding: 0 15px; -} -.td_changelog_wrap h3 { - margin-top: 20px; - font-size: 16px; - font-weight: normal; -} -.td_changelog_wrap h3 strong { - color: #999; - font-size: 14px; - font-weight: normal; -} - -.td_screenshot_macos { - background: url(https://osx.telegram.org/updates/site/artboard.png) 50% 0 no-repeat; - background-size: 420px 280px; - height: 280px; -} - -.td_screenshot_tdirect { - background: url(/img/tdirect.jpg?1) 50% 0 no-repeat; - background-size: 300px 360px; - height: 360px; - margin: 40px 20px; -} -.td_content_tdirect_title { - font-size: 26px; - color: #383a3b; - text-align: center; - margin-top: 32px; - margin-bottom: 14px; - font-weight: 600; - letter-spacing: -1px; -} -.td_about_tdirect { - font-size: 14px; - margin: 14px 10px 24px; - line-height: 1.5; - text-align: center; -} -.td_download_btn.td_tdirect { - border-radius: 5px; - font-weight: bold; - margin: 10px; -} -.td_howto_install_wrap { - text-align: center; - margin: 50px 0 40px; -} -.td_about_tdirect_store { - margin-top: 60px; -} -.td_download_store_wrap { - margin: 20px 0 10px; - text-align: center; -} - - - - - - - -@media only screen and (-webkit-min-device-pixel-ratio: 1.5), only screen and (-o-min-device-pixel-ratio: 3/2), only screen and (min--moz-device-pixel-ratio: 1.5), only screen and (min-device-pixel-ratio: 1.5) { - .tl_main_logo_title_image { - background-image: url(../img/Telegram_2x.png); - background-size: 144px 36px; - } - .caret { - background-image: url(../img/dropdown.png); - background-size: 18px 26px; - } - .icon-twitter { - background-image: url(../img/twitter_2x.png); - background-size: 21px 17px; - } - .icon-breadcrumb-divider { - background-image: url(../img/breadcrumb_divider.png); - background-size: 5px 10px; - } - .icon-to-top { - background-image: url(../img/back_to_top.png); - background-size: 16px 7px; - } - .tl_main_award { - background-image: url(../img/SiteAward_2x.gif); - background-size: 100px 100px; - } - .icon-arrow-more { - background-image: url(../img/tl_arrow_2x.png); - background-size: 6px 11px; - } - .tl_main_download_desktop { - background-image: url(../img/SiteDesktop_2x.jpg?2); - background-size: 1246px 260px; - } - - .icon-android, - .icon-ios, - .icon-wp { - background-image: url(../img/SiteLogos_2x.png); - background-size: 21px 120px; - } - - .tl_main_download_image__android { - background-image: url(../img/SiteAndroid_2x.jpg?2); - background-size: 290px 270px; - } - .tl_main_download_image__ios { - background-image: url(../img/SiteiOS_2x.jpg?2); - background-size: 442px 270px; - } - .tl_main_download_link_tdesktop { - background-image: url(../img/SiteTDesktop_2x.jpg?1); - background-size: 320px 157px; - } - - #dev_page_content > ul:not(.nav) li, - #dev_page_content > ol:not(.nav) ul:not(.nav) li { - background-image: url(../img/bullet_2x.png?3); - background-size: 7px 7px; - } - - .tgme_icon_arrow { - background-image: url(/img/tgme/Arrow_2x.png); - } - .tgme_icon_user, - .tgme_icon_group, - .tgme_icon_stickers, - .tgme_icon_share { - background-image: url(/img/tgme/Web2x.png?1); - background-size: 44px 177px; - } - - .tgme_page_widget_actions a.tgme_action_web_button:before { - background-image: url(/img/tgme/web_icon_2x.png); - background-size: 24px 24px; - } - .tgme_page_embed_btn a.tgme_action_button_new:before { - background-image: url(/img/tgme/embed_icon_2x.png?1); - background-size: 48px 24px; - } - .tgme_page_copy_action a.tgme_action_button_new:before { - background-image: url(/img/tgme/embed_copy_2x.png); - background-size: 24px 24px; - } - - .tlb_blog_logo { - background-image: url(/img/blog/BlogLogo2x.png?1); - background-size: 146px 20px; - } - - .radio-item input.radio + .radio-label:before, - .checkbox-item input.checkbox + .checkbox-label:before, - .form-control-dropdown-button:before { - background-image: url(/img/rc_icons_2x.png?1); - background-size: 20px 152px; - } - - .form-control-dropdown.has-items:before { - background-image: url(/img/rc_icons_2x.png?1); - background-size: 20px 152px; - } - .td_screenshot_macos { - background-image: url(https://osx.telegram.org/updates/site/artboard_2x.png); - background-size: 420px 280px; - height: 280px; - } - .td_screenshot_tdirect { - background-image: url(/img/tdirect_2x.jpg?1); - } -} - -@media only screen and (-webkit-min-device-pixel-ratio: 2.5), only screen and (-o-min-device-pixel-ratio: 3/2), only screen and (min--moz-device-pixel-ratio: 2.5), only screen and (min-device-pixel-ratio: 2.5) { - - .tlb_blog_logo { - background-image: url(/img/blog/BlogLogo3x.png); - background-size: 146px 20px; - } -} - -@media (max-width: 1200px) { - .dev_side_nav_wrap { - display: none; - } -} - -/* Mobile */ -@media (max-width: 1000px) { - a.anchor { - margin-left: -19px; - } - .footer_wrap { - padding: 16px 0 16px; - padding-bottom: calc(max(16px, env(safe-area-inset-bottom))); - } - .footer_desktop { - display: none; - } - .footer_mobile { - display: flex; - justify-content: center; - } - .footer_columns_wrap { - text-align: center; - } - .footer_column { - margin: 0 6px; - } - .footer_column h5 { - color: #08c; - font-size: 12px; - font-weight: normal; - text-transform: uppercase; - margin: 0; - } - - .blog_side_image_wrap { - position: static; - } - .blog_side_image { - display: block; - margin: 20px auto; - width: 160px; - height: 160px; - position: static; - } - .blog_side_image.js-tgsticker_image { - position: relative; - } - - .tl_blog_side_blog { - display: none; - } - .tl_blog_bottom_blog { - display: block; - } - .tl_main_side_blog .side_blog_wrap { - position: static; - margin: 22px 0 0 16px; - padding: 0 10px 0 15px; - border-width: 4px; - border-color: #3faee8; - } - .side_blog_wrap { - width: auto; - } - - .tl_main_side_blog .side_blog_header { - font-size: 14px; - } - .tl_main_side_blog a.side_blog_entry { - margin-top: 12px; - } - .tl_main_side_blog .side_blog_date { - color: #444; - font-size: 13px; - } - .tl_main_side_blog .side_blog_title { - font-size: 14px; - margin-top: 2px; - } - -} - -@media (max-width: 640px) { - a:hover { - text-decoration: none; - } - h1 { - font-size: 19px; - } - h2 { - font-size: 19px; - } - h3 { - font-size: 16px; - } - h4 { - font-size: 16px; - } - h5 { - font-size: 14px; - } - .dropdown-menu { - min-width: 210px; - } - .dropdown-menu > li > a { - white-space: normal; - } - .tl_main_body { - margin-top: 25px; - padding-top: 5px; - } - .tl_main_body_header { - font-size: 20px; - } - .tl_main_download_mobile { - padding: 0 20px; - } - - .tl_main_download_link { - width: auto; - min-width: 0; - display: block; - margin-top: 20px; - margin-bottom: 30px; - } - a.tl_main_download_link:after { - display: none; - } - .tl_main_download_link_ios/*, - .tl_main_download_link_tdesktop*/ { - padding-top: 210px; - height: 245px; - padding-bottom: 15px; - } - .tl_main_download_image__ios { - margin: -123px 0 0 -121px; - background-size: 360px 220px; - width: 248px; - height: 198px; - } - .tl_main_video_player__ios { - margin: -124px 0 0 -121px; - width: 248px; - height: 198px; - } - - .tl_main_download_link_tdesktop { - display: block; - padding-top: 156px; - height: 188px; - } - .tl_main_download_desktop_section, - .tl_main_download_desktop_wrap1 { - display: none; - } - .tl_main_download_more_btn { - display: inline-block; - } - - .dev_page_bread_crumbs .breadcrumb { - margin-bottom: 15px; - } - #dev_page_content_wrap { - padding-top: 12px; - } - #dev_page_title { - margin-top: 10px; - margin-bottom: 21px; - } - .nav-pills > li > a { - padding: 8px 10px; - } - .dev_page_nav_wrap { - margin-top: 25px; - } - .dev_page_nav_wrap > p { - margin-bottom: 3.5px; - } - .dev_page_nav_wrap > p > a:first-child { - font-size: 15px; - } - #dev_page_content .dev_page_nav_wrap ul li { - padding: 3px 0 4px; - } - #dev_page_content .dev_page_nav_wrap ul li a:first-child { - font-size: 14px; - display: inline-block; - line-height: 22px; - padding: 2px 6px 1px; - margin-left: -6px; - } - #dev_page_content .dev_page_nav_wrap ul li a:first-child:hover { - border-radius: 2px; - background: #e6f1f7; - } - #dev_page_content .dev_page_nav_wrap hr { - display: none; - } - .dev_faq_page h4 { - font-size: 15px; - line-height: 140%; - margin-top: 26px; - margin-bottom: 5px; - } - .dev_page_image, - .tl_contest_page_wrap .dev_page_image { - max-width: 100%; - max-height: 400px; - margin: 0 auto; - } - .dev_page_image img, - .tl_contest_page_wrap .dev_page_image img { - max-width: 100%; - max-height: 400px; - } - - .tl_main_download_link:hover, - .tl_main_download_desktop_link:hover { - box-shadow: none; - } - - .dev_side_image { - width: auto; - max-width: none; - float: none; - text-align: center; - padding: 0; - } - .dev_side_image img { - display: block; - margin: 20px auto; - width: 180px; - } - - - .tl_team_member_photo_wrap { - margin-bottom: 10px; - } - .tl_team_member_photo { - width: 60px; - height: 60px; - background-size: 60px 905px; - } - .tl_team_member_pavel .tl_team_member_photo { - background-position: 0 0; - } - .tl_team_member_nikolay .tl_team_member_photo { - background-position: 0 -65px; - } - .tl_team_member_aliaksei .tl_team_member_photo { - background-position: 0 -130px; - } - .tl_team_member_vitalik .tl_team_member_photo { - background-position: 0 -195px; - } - .tl_team_member_arseny .tl_team_member_photo { - background-position: 0 -260px; - } - .tl_team_member_igor .tl_team_member_photo { - background-position: 0 -325px; - } - .tl_team_member_drklo .tl_team_member_photo { - background-position: 0 -390px; - } - .tl_team_member_peter .tl_team_member_photo { - background-position: 0 -455px; - } - .tl_team_member_john .tl_team_member_photo { - background-position: 0 -520px; - } - .tl_team_member_kolar .tl_team_member_photo { - background-position: 0 -585px; - } - .tl_team_member_ilya .tl_team_member_photo { - background-position: 0 -650px; - } - .tl_team_member_igor1 .tl_team_member_photo { - background-position: 0 -845px; - } - .tl_team_member_mike .tl_team_member_photo { - background-position: 0 -780px; - } - .tl_team_member_grisha .tl_team_member_photo { - background-position: 0 -715px; - } - .tl_team_member_name { - margin-top: 20px; - margin-left: 80px; - margin-bottom: 40px; - } - .tl_team_member_body { - margin-left: 0; - } -} - -@media (max-width: 480px) { - .navbar-tg .container { - padding: 0; - } - h3 a.anchor i.anchor-icon {margin-top: 1px;} - a.anchor { - margin-left: -16px; - } - .tl_main_award { - display: none; - } - .tl_main_logo_wrap { - padding-top: 10px; - padding-bottom: 2px; - } - svg.tl_main_logo, - image.tl_main_logo, - img.tl_main_logo { - width: 85px !important; - height: 85px !important; - } - .tl_main_logo_title, - .tl_main_logo_title:hover { - font-size: 23px; - margin-top: 15px; - margin-bottom: 5px; - letter-spacing: -1px; - } - .tl_main_logo_lead { - font-size: 16px; - max-width: 224px; - } - - .tl_main_head_download { - margin-bottom: 10px; - } - .tl_main_download_btn { - max-width: 200px; - width: auto; - padding: 6px 9px; - line-height: 20px; - font-size: 13px; - margin: 5px 10px; - } - - .tl_main_cards { - margin-top: 10px; - } - - .tl_main_card_header { - margin: 10px 0 6px; - font-size: 21px; - font-weight: normal; - letter-spacing: -1px; - } - - .tl_main_card_lead { - font-size: 15px; - } - .smartphone_video_player_wrap { - /*display: none;*/ - } - - .td_content_wrap { - width: auto; - font-size: 14px; - margin: 0 20px; - } - .td_screenshot { - margin-top: 26px; - } - .td_content_title { - font-size: 22px; - margin-top: 21px; - margin-bottom: 10px; - } - .td_download_wrap, - .td_download_wrap_low { - margin: 0 auto; - width: 320px; - } - .td_download_wrap_low { - margin-bottom: 30px; - } - .td_download_add_wrap { - width: 280px; - margin: 0 auto 10px; - } - #td_about_osx { - width: 320px; - font-size: 16px; - } - .td_about_osx_team { - display: none; - } - .td_about_license { - font-size: 12px; - } - #td_about_tdesktop { - font-size: 16px; - margin: 10px 15px 24px; - } - .td_screenshot_tdirect { - background-size: 225px 270px; - height: 270px; - margin: 40px 20px 20px; - } - .td_content_tdirect_title { - font-size: 20px; - margin-top: 21px; - margin-bottom: 10px; - letter-spacing: 0; - } - - - /* Telegram.me */ - .tgme_head_wrap { - background: #FFF; - height: 59px; - padding: 14px 16px; - -webkit-box-shadow: none; - -moz-box-shadow: none; - box-shadow: none; - } - a.tgme_head_dl_button { - text-align: left; - -webkit-box-shadow: inset 0px 1px 3px 0px rgba(0,0,0,0.15); - -moz-box-shadow: inset 0px 1px 3px 0px rgba(0,0,0,0.15); - box-shadow: inset 0px 1px 3px 0px rgba(0,0,0,0.15); - } - .tgme_icon_arrow { - float: right; - } - .tgme_page_photo_image { - width: 110px; - height: 110px; - border-radius: 55px; - } - .tgme_icon_user { - width: 30px; - height: 30px; - background: url(/img/tgme/Mobile1x.png?1) -2px -31px no-repeat; - background-size: 33px 148px; - } - .tgme_icon_group { - width: 32px; - height: 18px; - background: url(/img/tgme/Mobile1x.png?1) 0 0 no-repeat; - background-size: 33px 148px; - } - .tgme_icon_stickers { - width: 28px; - height: 28px; - background: url(/img/tgme/Mobile1x.png?1) -2px -70px no-repeat; - background-size: 33px 148px; - } - .tgme_icon_share { - width: 31px; - height: 17px; - background: url(/img/tgme/Mobile1x.png?1) -1px -108px no-repeat; - background-size: 33px 148px; - } - - .tgme_page_additional { - display: block; - } - .tgme_footer { - display: none; - } - - .blog_2images_wrap, - .blog_3images_wrap, - .blog_medium_image_wrap, - .blog_medium_image_wrap img, - .blog_image_wrap, - .blog_image_wrap img { - width: auto; - max-width: 275px; - } - .blog_2images_wrap, - .blog_3images_wrap { - margin: 20px auto 20px; - } - .blog_2images_wrap .blog_image_wrap, - .blog_3images_wrap .blog_image_wrap { - float: none; - margin: 20px 0 20px; - } -} - -@media (max-width: 340px) { - .tl_main_download_image__android { - margin: -109px 0 0 -101px; - background-size: 196px 183px; - width: 205px; - height: 162px; - } - .tl_main_download_image__ios { - margin: -103px 0 0 -101px; - background-size: 300px 183px; - width: 206px; - height: 165px; - } - .tl_main_video_player__android { - margin: -109px 0 0 -101px; - width: 205px; - height: 162px; - } - .tl_main_video_player__ios { - /*margin: -103px 0 0 -101px;*/ - margin: -104px 0 0 -101px; - width: 206px; - height: 165px; - } -} - -@media (max-width: 320px) { - #td_about_tdesktop { - font-size: 14px; - } - #td_open_from_desktop { - font-size: 15px; - padding: 13px 18px; - } -} - -.tl_contest_page_wrap + .pager_wrap { - max-width: 600px; - margin: 0 auto; -} - -@media only screen and (-webkit-min-device-pixel-ratio: 1.5) and (max-width: 480px), only screen and (-o-min-device-pixel-ratio: 3/2) and (max-width: 480px), only screen and (min--moz-device-pixel-ratio: 1.5) and (max-width: 480px), only screen and (min-device-pixel-ratio: 1.5) and (max-width: 480px) { - - .tgme_icon_user, - .tgme_icon_group, - .tgme_icon_stickers, - .tgme_icon_share { - background-image: url(/img/tgme/Mobile2x.png?1); - } -} diff --git a/data/core.telegram.org/import-stickers.html b/data/core.telegram.org/import-stickers.html deleted file mode 100644 index d218ab9fda..0000000000 --- a/data/core.telegram.org/import-stickers.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - Importing Stickers to Telegram - - - - - - - - - - - - - -
- -
-
-
-
-

Importing Stickers to Telegram

- -

The easiest way to create stickers on Telegram is to simply upload them using the @stickers bot. This bot can help you upload new stickers, create sticker packs and get usage stats for your stickers and packs.

-

Telegram also offers a platform for developers of apps that help users make their own stickers. For example, apps that allow people to upload pictures of themselves and turn them into stickers.

-

Who is this for?

-

USE this:

-
    -
  • To help people make their own unique custom stickers.
  • -
  • To help people migrate their unique custom stickers they created from another platform.
  • -
-

DON'T use this:

- -

In short, if a set of stickers is already available on Telegram – there's no need to import it!

-

Sticker Importing Apps

-

As of version 7.8, Telegram apps support a simple API for importing stickers.

-
- -
- -
-

WARNING: Each time a user imports stickers, a new sticker pack is created on Telegram. Do not use the importing feature to share stickers you made with other users. If you want to share your stickers, simply upload them using @stickers and share the link of your pack. For example, here's a link to install some Duck Stickers.

-
-

Importing SDKs

-

We have created libraries and sample apps for iOS and Android which you can use to implement importing stickers to Telegram from your app.

-

Sticker Formats

-

Telegram apps support two sticker types. Regardless of the type, each sticker must be associated with at least one emoji that expresses the emotion corresponding to the sticker.

-

Animated Stickers

-

Must be in TGS format, created using the Bodymovin-TG plugin for Adobe After Effects.

-
-

Note: Animated webp is NOT supported, only static webp is supported for static stickers. Animated stickers must be in TGS format.

-
-

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.

-
-

Static Stickers

-

Must be in PNG or WEBP format with a transparent layer. All static stickers should use white stroke and shadow, exactly like in this example: StickerExample.psd

-

Max. size: 512 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/js/bootstrap.min.js b/data/core.telegram.org/js/bootstrap.min.js deleted file mode 100644 index ab0c4b1bf2..0000000000 --- a/data/core.telegram.org/js/bootstrap.min.js +++ /dev/null @@ -1,11 +0,0 @@ -/*! - * Bootstrap v3.2.0 (http://getbootstrap.com) - * Copyright 2011-2014 Twitter, Inc. - * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE) - */ - -/*! - * Generated using the Bootstrap Customizer (http://getbootstrap.com/customize/?id=cc2c54fe9eb3aea36d65) - * Config saved to config.json and https://gist.github.com/cc2c54fe9eb3aea36d65 - */ -if("undefined"==typeof jQuery)throw new Error("Bootstrap's JavaScript requires jQuery");+function(t){"use strict";function e(e){return this.each(function(){var i=t(this),s=i.data("bs.alert");s||i.data("bs.alert",s=new o(this)),"string"==typeof e&&s[e].call(i)})}var i='[data-dismiss="alert"]',o=function(e){t(e).on("click",i,this.close)};o.VERSION="3.2.0",o.prototype.close=function(e){function i(){n.detach().trigger("closed.bs.alert").remove()}var o=t(this),s=o.attr("data-target");s||(s=o.attr("href"),s=s&&s.replace(/.*(?=#[^\s]*$)/,""));var n=t(s);e&&e.preventDefault(),n.length||(n=o.hasClass("alert")?o:o.parent()),n.trigger(e=t.Event("close.bs.alert")),e.isDefaultPrevented()||(n.removeClass("in"),t.support.transition&&n.hasClass("fade")?n.one("bsTransitionEnd",i).emulateTransitionEnd(150):i())};var s=t.fn.alert;t.fn.alert=e,t.fn.alert.Constructor=o,t.fn.alert.noConflict=function(){return t.fn.alert=s,this},t(document).on("click.bs.alert.data-api",i,o.prototype.close)}(jQuery),+function(t){"use strict";function e(e){return this.each(function(){var o=t(this),s=o.data("bs.button"),n="object"==typeof e&&e;s||o.data("bs.button",s=new i(this,n)),"toggle"==e?s.toggle():e&&s.setState(e)})}var i=function(e,o){this.$element=t(e),this.options=t.extend({},i.DEFAULTS,o),this.isLoading=!1};i.VERSION="3.2.0",i.DEFAULTS={loadingText:"loading..."},i.prototype.setState=function(e){var i="disabled",o=this.$element,s=o.is("input")?"val":"html",n=o.data();e+="Text",null==n.resetText&&o.data("resetText",o[s]()),o[s](null==n[e]?this.options[e]:n[e]),setTimeout(t.proxy(function(){"loadingText"==e?(this.isLoading=!0,o.addClass(i).attr(i,i)):this.isLoading&&(this.isLoading=!1,o.removeClass(i).removeAttr(i))},this),0)},i.prototype.toggle=function(){var t=!0,e=this.$element.closest('[data-toggle="buttons"]');if(e.length){var i=this.$element.find("input");"radio"==i.prop("type")&&(i.prop("checked")&&this.$element.hasClass("active")?t=!1:e.find(".active").removeClass("active")),t&&i.prop("checked",!this.$element.hasClass("active")).trigger("change")}t&&this.$element.toggleClass("active")};var o=t.fn.button;t.fn.button=e,t.fn.button.Constructor=i,t.fn.button.noConflict=function(){return t.fn.button=o,this},t(document).on("click.bs.button.data-api",'[data-toggle^="button"]',function(i){var o=t(i.target);o.hasClass("btn")||(o=o.closest(".btn")),e.call(o,"toggle"),i.preventDefault()})}(jQuery),+function(t){"use strict";function e(e){return this.each(function(){var o=t(this),s=o.data("bs.carousel"),n=t.extend({},i.DEFAULTS,o.data(),"object"==typeof e&&e),r="string"==typeof e?e:n.slide;s||o.data("bs.carousel",s=new i(this,n)),"number"==typeof e?s.to(e):r?s[r]():n.interval&&s.pause().cycle()})}var i=function(e,i){this.$element=t(e).on("keydown.bs.carousel",t.proxy(this.keydown,this)),this.$indicators=this.$element.find(".carousel-indicators"),this.options=i,this.paused=this.sliding=this.interval=this.$active=this.$items=null,"hover"==this.options.pause&&this.$element.on("mouseenter.bs.carousel",t.proxy(this.pause,this)).on("mouseleave.bs.carousel",t.proxy(this.cycle,this))};i.VERSION="3.2.0",i.DEFAULTS={interval:5e3,pause:"hover",wrap:!0},i.prototype.keydown=function(t){switch(t.which){case 37:this.prev();break;case 39:this.next();break;default:return}t.preventDefault()},i.prototype.cycle=function(e){return e||(this.paused=!1),this.interval&&clearInterval(this.interval),this.options.interval&&!this.paused&&(this.interval=setInterval(t.proxy(this.next,this),this.options.interval)),this},i.prototype.getItemIndex=function(t){return this.$items=t.parent().children(".item"),this.$items.index(t||this.$active)},i.prototype.to=function(e){var i=this,o=this.getItemIndex(this.$active=this.$element.find(".item.active"));return e>this.$items.length-1||0>e?void 0:this.sliding?this.$element.one("slid.bs.carousel",function(){i.to(e)}):o==e?this.pause().cycle():this.slide(e>o?"next":"prev",t(this.$items[e]))},i.prototype.pause=function(e){return e||(this.paused=!0),this.$element.find(".next, .prev").length&&t.support.transition&&(this.$element.trigger(t.support.transition.end),this.cycle(!0)),this.interval=clearInterval(this.interval),this},i.prototype.next=function(){return this.sliding?void 0:this.slide("next")},i.prototype.prev=function(){return this.sliding?void 0:this.slide("prev")},i.prototype.slide=function(e,i){var o=this.$element.find(".item.active"),s=i||o[e](),n=this.interval,r="next"==e?"left":"right",a="next"==e?"first":"last",l=this;if(!s.length){if(!this.options.wrap)return;s=this.$element.find(".item")[a]()}if(s.hasClass("active"))return this.sliding=!1;var h=s[0],p=t.Event("slide.bs.carousel",{relatedTarget:h,direction:r});if(this.$element.trigger(p),!p.isDefaultPrevented()){if(this.sliding=!0,n&&this.pause(),this.$indicators.length){this.$indicators.find(".active").removeClass("active");var c=t(this.$indicators.children()[this.getItemIndex(s)]);c&&c.addClass("active")}var d=t.Event("slid.bs.carousel",{relatedTarget:h,direction:r});return t.support.transition&&this.$element.hasClass("slide")?(s.addClass(e),s[0].offsetWidth,o.addClass(r),s.addClass(r),o.one("bsTransitionEnd",function(){s.removeClass([e,r].join(" ")).addClass("active"),o.removeClass(["active",r].join(" ")),l.sliding=!1,setTimeout(function(){l.$element.trigger(d)},0)}).emulateTransitionEnd(1e3*o.css("transition-duration").slice(0,-1))):(o.removeClass("active"),s.addClass("active"),this.sliding=!1,this.$element.trigger(d)),n&&this.cycle(),this}};var o=t.fn.carousel;t.fn.carousel=e,t.fn.carousel.Constructor=i,t.fn.carousel.noConflict=function(){return t.fn.carousel=o,this},t(document).on("click.bs.carousel.data-api","[data-slide], [data-slide-to]",function(i){var o,s=t(this),n=t(s.attr("data-target")||(o=s.attr("href"))&&o.replace(/.*(?=#[^\s]+$)/,""));if(n.hasClass("carousel")){var r=t.extend({},n.data(),s.data()),a=s.attr("data-slide-to");a&&(r.interval=!1),e.call(n,r),a&&n.data("bs.carousel").to(a),i.preventDefault()}}),t(window).on("load",function(){t('[data-ride="carousel"]').each(function(){var i=t(this);e.call(i,i.data())})})}(jQuery),+function(t){"use strict";function e(e){e&&3===e.which||(t(s).remove(),t(n).each(function(){var o=i(t(this)),s={relatedTarget:this};o.hasClass("open")&&(o.trigger(e=t.Event("hide.bs.dropdown",s)),e.isDefaultPrevented()||o.removeClass("open").trigger("hidden.bs.dropdown",s))}))}function i(e){var i=e.attr("data-target");i||(i=e.attr("href"),i=i&&/#[A-Za-z]/.test(i)&&i.replace(/.*(?=#[^\s]*$)/,""));var o=i&&t(i);return o&&o.length?o:e.parent()}function o(e){return this.each(function(){var i=t(this),o=i.data("bs.dropdown");o||i.data("bs.dropdown",o=new r(this)),"string"==typeof e&&o[e].call(i)})}var s=".dropdown-backdrop",n='[data-toggle="dropdown"]',r=function(e){t(e).on("click.bs.dropdown",this.toggle)};r.VERSION="3.2.0",r.prototype.toggle=function(o){var s=t(this);if(!s.is(".disabled, :disabled")){var n=i(s),r=n.hasClass("open");if(e(),!r){"ontouchstart"in document.documentElement&&!n.closest(".navbar-nav").length&&t('